[web] adding draft version to web
Laura
lnovich at fedoraproject.org
Tue May 28 13:58:47 UTC 2013
commit 384a8e39cab19f166ff852f2924a5cd664ce0088
Author: Laura Novich <lnovich at redhat.com>
Date: Tue May 28 16:56:55 2013 +0300
adding draft version to web
fedoradocs.db | Bin 941056 -> 941056 bytes
public_html/Sitemap | 24 +
public_html/as-IN/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/as-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/as-IN/opds-Fedora_Core.xml | 2 +-
.../as-IN/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/as-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/as-IN/opds.xml | 14 +-
public_html/as-IN/toc.html | 13 +-
public_html/bg-BG/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/bg-BG/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/bg-BG/opds-Fedora_Core.xml | 2 +-
.../bg-BG/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/bg-BG/opds-Fedora_Security_Team.xml | 2 +-
public_html/bg-BG/opds.xml | 14 +-
public_html/bg-BG/toc.html | 13 +-
public_html/bn-IN/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/bn-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/bn-IN/opds-Fedora_Core.xml | 2 +-
.../bn-IN/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/bn-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/bn-IN/opds.xml | 14 +-
public_html/bn-IN/toc.html | 13 +-
public_html/bs-BA/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/bs-BA/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/bs-BA/opds-Fedora_Core.xml | 2 +-
.../bs-BA/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/bs-BA/opds-Fedora_Security_Team.xml | 2 +-
public_html/bs-BA/opds.xml | 14 +-
public_html/bs-BA/toc.html | 13 +-
public_html/ca-ES/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ca-ES/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ca-ES/opds-Fedora_Core.xml | 2 +-
.../ca-ES/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/ca-ES/opds-Fedora_Security_Team.xml | 2 +-
public_html/ca-ES/opds.xml | 14 +-
public_html/ca-ES/toc.html | 13 +-
public_html/cs-CZ/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/cs-CZ/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/cs-CZ/opds-Fedora_Core.xml | 2 +-
.../cs-CZ/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/cs-CZ/opds-Fedora_Security_Team.xml | 2 +-
public_html/cs-CZ/opds.xml | 14 +-
public_html/cs-CZ/toc.html | 13 +-
public_html/da-DK/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/da-DK/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/da-DK/opds-Fedora_Core.xml | 2 +-
.../da-DK/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/da-DK/opds-Fedora_Security_Team.xml | 2 +-
public_html/da-DK/opds.xml | 14 +-
public_html/da-DK/toc.html | 13 +-
public_html/de-DE/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/de-DE/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/de-DE/opds-Fedora_Core.xml | 2 +-
.../de-DE/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/de-DE/opds-Fedora_Security_Team.xml | 2 +-
public_html/de-DE/opds.xml | 14 +-
public_html/de-DE/toc.html | 13 +-
public_html/el-GR/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/el-GR/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/el-GR/opds-Fedora_Core.xml | 2 +-
.../el-GR/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/el-GR/opds-Fedora_Security_Team.xml | 2 +-
public_html/el-GR/opds.xml | 14 +-
public_html/el-GR/toc.html | 13 +-
..._Deployment_and_Administration_Guide-en-US.epub | Bin 0 -> 17465296 bytes
.../Common_Content/css/common.css | 1528 +++
.../Common_Content/css/default.css | 3 +
.../Common_Content/css/lang.css | 2 +
.../Common_Content/css/menu.css | 48 +
.../Common_Content/css/overrides.css | 46 +
.../Common_Content/css/pdf.css | 138 +
.../Common_Content/css/print.css | 16 +
.../Common_Content/images/1.png | Bin 0 -> 640 bytes
.../Common_Content/images/1.svg | 27 +
.../Common_Content/images/10.png | Bin 0 -> 942 bytes
.../Common_Content/images/10.svg | 31 +
.../Common_Content/images/11.png | Bin 0 -> 741 bytes
.../Common_Content/images/11.svg | 31 +
.../Common_Content/images/12.png | Bin 0 -> 943 bytes
.../Common_Content/images/12.svg | 31 +
.../Common_Content/images/13.png | Bin 0 -> 983 bytes
.../Common_Content/images/13.svg | 31 +
.../Common_Content/images/14.png | Bin 0 -> 862 bytes
.../Common_Content/images/14.svg | 31 +
.../Common_Content/images/15.png | Bin 0 -> 936 bytes
.../Common_Content/images/15.svg | 31 +
.../Common_Content/images/16.png | Bin 0 -> 975 bytes
.../Common_Content/images/16.svg | 31 +
.../Common_Content/images/17.png | Bin 0 -> 838 bytes
.../Common_Content/images/17.svg | 31 +
.../Common_Content/images/18.png | Bin 0 -> 1013 bytes
.../Common_Content/images/18.svg | 31 +
.../Common_Content/images/19.png | Bin 0 -> 989 bytes
.../Common_Content/images/19.svg | 31 +
.../Common_Content/images/2.png | Bin 0 -> 814 bytes
.../Common_Content/images/2.svg | 27 +
.../Common_Content/images/20.png | Bin 0 -> 1086 bytes
.../Common_Content/images/20.svg | 31 +
.../Common_Content/images/21.png | Bin 0 -> 925 bytes
.../Common_Content/images/21.svg | 31 +
.../Common_Content/images/22.png | Bin 0 -> 1059 bytes
.../Common_Content/images/22.svg | 31 +
.../Common_Content/images/23.png | Bin 0 -> 1152 bytes
.../Common_Content/images/23.svg | 31 +
.../Common_Content/images/24.png | Bin 0 -> 1013 bytes
.../Common_Content/images/24.svg | 31 +
.../Common_Content/images/25.png | Bin 0 -> 1108 bytes
.../Common_Content/images/25.svg | 31 +
.../Common_Content/images/26.png | Bin 0 -> 1149 bytes
.../Common_Content/images/26.svg | 31 +
.../Common_Content/images/27.png | Bin 0 -> 1007 bytes
.../Common_Content/images/27.svg | 31 +
.../Common_Content/images/28.png | Bin 0 -> 1177 bytes
.../Common_Content/images/28.svg | 31 +
.../Common_Content/images/29.png | Bin 0 -> 1135 bytes
.../Common_Content/images/29.svg | 31 +
.../Common_Content/images/3.png | Bin 0 -> 889 bytes
.../Common_Content/images/3.svg | 27 +
.../Common_Content/images/30.png | Bin 0 -> 1179 bytes
.../Common_Content/images/30.svg | 31 +
.../Common_Content/images/31.png | Bin 0 -> 1012 bytes
.../Common_Content/images/31.svg | 31 +
.../Common_Content/images/32.png | Bin 0 -> 1151 bytes
.../Common_Content/images/32.svg | 31 +
.../Common_Content/images/33.png | Bin 0 -> 1213 bytes
.../Common_Content/images/33.svg | 31 +
.../Common_Content/images/34.png | Bin 0 -> 1107 bytes
.../Common_Content/images/34.svg | 31 +
.../Common_Content/images/35.png | Bin 0 -> 1176 bytes
.../Common_Content/images/35.svg | 31 +
.../Common_Content/images/36.png | Bin 0 -> 1222 bytes
.../Common_Content/images/36.svg | 31 +
.../Common_Content/images/37.png | Bin 0 -> 1085 bytes
.../Common_Content/images/37.svg | 31 +
.../Common_Content/images/38.png | Bin 0 -> 1256 bytes
.../Common_Content/images/38.svg | 31 +
.../Common_Content/images/39.png | Bin 0 -> 1226 bytes
.../Common_Content/images/39.svg | 31 +
.../Common_Content/images/4.png | Bin 0 -> 783 bytes
.../Common_Content/images/4.svg | 27 +
.../Common_Content/images/40.png | Bin 0 -> 1082 bytes
.../Common_Content/images/40.svg | 31 +
.../Common_Content/images/5.png | Bin 0 -> 839 bytes
.../Common_Content/images/5.svg | 27 +
.../Common_Content/images/6.png | Bin 0 -> 868 bytes
.../Common_Content/images/6.svg | 27 +
.../Common_Content/images/7.png | Bin 0 -> 757 bytes
.../Common_Content/images/7.svg | 27 +
.../Common_Content/images/8.png | Bin 0 -> 914 bytes
.../Common_Content/images/8.svg | 27 +
.../Common_Content/images/9.png | Bin 0 -> 877 bytes
.../Common_Content/images/9.svg | 27 +
.../Common_Content/images/bkgrnd_greydots.png | Bin 0 -> 157 bytes
.../Common_Content/images/bullet_arrowblue.png | Bin 0 -> 177 bytes
.../Common_Content/images/documentation.png | Bin 0 -> 1358 bytes
.../Common_Content/images/dot.png | Bin 0 -> 98 bytes
.../Common_Content/images/dot2.png | Bin 0 -> 98 bytes
.../Common_Content/images/green.png | Bin 0 -> 176 bytes
.../Common_Content/images/h1-bg.png | Bin 0 -> 142 bytes
.../Common_Content/images/image_left.png | Bin 0 -> 2278 bytes
.../Common_Content/images/image_right.png | Bin 0 -> 1358 bytes
.../Common_Content/images/important.png | Bin 0 -> 1918 bytes
.../Common_Content/images/important.svg | 30 +
.../Common_Content/images/note.png | Bin 0 -> 1616 bytes
.../Common_Content/images/note.svg | 28 +
.../Common_Content/images/red.png | Bin 0 -> 163 bytes
.../Common_Content/images/redhat-logo.svg | 94 +
.../Common_Content/images/rhlogo.png | Bin 0 -> 2278 bytes
.../Common_Content/images/shade.png | Bin 0 -> 101 bytes
.../Common_Content/images/shine.png | Bin 0 -> 146 bytes
.../Common_Content/images/stock-go-back.png | Bin 0 -> 571 bytes
.../Common_Content/images/stock-go-forward.png | Bin 0 -> 531 bytes
.../Common_Content/images/stock-go-up.png | Bin 0 -> 582 bytes
.../Common_Content/images/stock-home.png | Bin 0 -> 772 bytes
.../Common_Content/images/title_logo.png | Bin 0 -> 2278 bytes
.../Common_Content/images/title_logo.svg | 94 +
.../Common_Content/images/warning.png | Bin 0 -> 1940 bytes
.../Common_Content/images/warning.svg | 32 +
.../Common_Content/images/watermark-draft.png | Bin 0 -> 25365 bytes
.../Common_Content/images/yellow.png | Bin 0 -> 175 bytes
.../images/1-7RHEL_local_install.png | Bin 0 -> 13795 bytes
.../images/1-Iso_general.png | Bin 0 -> 66439 bytes
.../images/1-files_PV-win.png | Bin 0 -> 58708 bytes
.../images/10-7RHEL_local_install.png | Bin 0 -> 40128 bytes
.../images/10-w7x86driverchosen.png | Bin 0 -> 70168 bytes
.../images/10-w7x86driverchosen_win7.png | Bin 0 -> 19979 bytes
.../images/10-w7x86driverstart.png | Bin 0 -> 67481 bytes
.../images/10-w7x86driverstart_win7.png | Bin 0 -> 20672 bytes
.../images/11-7RHEL_local_install.png | Bin 0 -> 42123 bytes
.../images/12-DriverInstalled.png | Bin 0 -> 42765 bytes
.../images/14-StartInstallSerial.png | Bin 0 -> 89324 bytes
.../images/2-7RHEL_local_install.png | Bin 0 -> 31149 bytes
.../images/2-Iso_Balloon_Os.png | Bin 0 -> 58380 bytes
.../images/3-7RHEL_local_install.png | Bin 0 -> 26452 bytes
.../images/3-Iso_Balloon_Os_arch.png | Bin 0 -> 58272 bytes
.../images/3_PCI_Device.png | Bin 0 -> 179475 bytes
.../images/4-7RHEL_local_install.png | Bin 0 -> 29310 bytes
.../images/4-Iso_balloon_files.png | Bin 0 -> 69579 bytes
.../images/4_finish.png | Bin 0 -> 24479 bytes
.../images/5-7RHEL_local_install.png | Bin 0 -> 29133 bytes
.../images/6-7RHEL_local_install.png | Bin 0 -> 19657 bytes
.../images/6.4-2.png | Bin 0 -> 24447 bytes
.../images/6.4-3.png | Bin 0 -> 25646 bytes
.../images/6.4-4.png | Bin 0 -> 35108 bytes
.../images/7-7RHEL_local_install.png | Bin 0 -> 24996 bytes
.../images/8-7RHEL_local_install.png | Bin 0 -> 21005 bytes
.../images/8-BrowseForDriver.png | Bin 0 -> 76374 bytes
.../images/8-BrowseForDriver_win7.png | Bin 0 -> 20271 bytes
.../images/9-7RHEL_local_install.png | Bin 0 -> 34205 bytes
.../images/9-BrowseToDirectory.png | Bin 0 -> 17326 bytes
.../images/9-BrowseToDirectory_win7.png | Bin 0 -> 15823 bytes
.../images/COPYME.png | Bin 0 -> 60798 bytes
.../images/ChangeType.png | Bin 0 -> 119508 bytes
.../images/Connection_Details.png | Bin 0 -> 17102 bytes
.../images/Create-1.png | Bin 0 -> 68190 bytes
.../images/DevManagerStart.png | Bin 0 -> 115214 bytes
.../images/DevManagerStart_win7.png | Bin 0 -> 51206 bytes
.../images/DriverInstall-Expand.png | Bin 0 -> 111352 bytes
.../images/DriverInstall-OpenWizard.png | Bin 0 -> 10335 bytes
.../images/DriverInstall-OpenWizard_win7.png | Bin 0 -> 9493 bytes
.../images/DriverInstallExpand_win7.png | Bin 0 -> 92965 bytes
.../images/DuringInstallation.png | Bin 0 -> 25758 bytes
.../images/Iso_Balloon_files.png | Bin 0 -> 64585 bytes
.../images/Iso_general.png | Bin 0 -> 60798 bytes
.../images/ManageStart.png | Bin 0 -> 225210 bytes
.../images/Network_hardware.png | Bin 0 -> 52560 bytes
.../images/Network_hardware_virtio.png | Bin 0 -> 51598 bytes
.../images/PCIremoval.png | Bin 0 -> 55777 bytes
.../images/PXEguest_5of5.png | Bin 0 -> 46145 bytes
.../images/RHEL6_cpu+ram.png | Bin 0 -> 26155 bytes
.../images/RHEL6_finish_advanced.png | Bin 0 -> 49113 bytes
.../images/RHEL6_storage.png | Bin 0 -> 36029 bytes
.../images/RHEL6_storage_local.png | Bin 0 -> 33867 bytes
.../images/RHEL6_virt-manager_new_1.png | Bin 0 -> 38313 bytes
.../images/RHEL6local_choose.png | Bin 0 -> 52384 bytes
.../images/RHEL6local_selectedISO.png | Bin 0 -> 36710 bytes
.../images/RHELKVMpackages-2.png | Bin 0 -> 77122 bytes
.../images/RHELKVMpackages.png | Bin 0 -> 79030 bytes
.../images/RHELcustomize14.png | Bin 0 -> 104378 bytes
.../images/RHELcustomize15.png | Bin 0 -> 69240 bytes
.../images/RHELkvmSelect.png | Bin 0 -> 78106 bytes
.../images/SR-IOV_implementation.png | Bin 0 -> 75739 bytes
.../images/Screenshot-VIrt-Manager-fig31pt18.png | Bin 0 -> 27887 bytes
.../images/Screenshot-Virt-Manager-fig31pt1.png | Bin 0 -> 23228 bytes
.../images/Screenshot-Virt-Manager-fig31pt11.png | Bin 0 -> 27810 bytes
.../images/Screenshot-Virt-Manager-fig31pt13.png | Bin 0 -> 62072 bytes
.../images/Screenshot-Virt-Manager-fig31pt14.png | Bin 0 -> 80532 bytes
.../images/Screenshot-Virt-Manager-fig31pt15.png | Bin 0 -> 52668 bytes
.../images/Screenshot-Virt-Manager-fig31pt16.png | Bin 0 -> 72095 bytes
.../images/Screenshot-Virt-Manager-fig31pt17.png | Bin 0 -> 50464 bytes
.../images/Screenshot-Virt-Manager-fig31pt19.png | Bin 0 -> 22060 bytes
.../images/Screenshot-Virt-Manager-fig31pt2.png | Bin 0 -> 25861 bytes
.../images/Screenshot-Virt-Manager-fig31pt24.png | Bin 0 -> 29361 bytes
.../images/Screenshot-Virt-Manager-fig31pt24a.png | Bin 0 -> 29080 bytes
.../images/Screenshot-Virt-Manager-fig31pt27.png | Bin 0 -> 22828 bytes
.../images/Screenshot-Virt-Manager-fig31pt28.png | Bin 0 -> 33316 bytes
.../images/Screenshot-Virt-Manager-fig31pt29.png | Bin 0 -> 24925 bytes
.../images/Screenshot-Virt-Manager-fig31pt3.png | Bin 0 -> 69957 bytes
.../images/Screenshot-Virt-Manager-fig31pt4.png | Bin 0 -> 68968 bytes
.../images/Screenshot-Virt-Manager-fig31pt5.png | Bin 0 -> 548594 bytes
.../images/Screenshot-Virt-Manager-fig31pt6.png | Bin 0 -> 22883 bytes
.../images/Screenshot-Virt-Manager-fig31pt7.png | Bin 0 -> 25774 bytes
.../images/Screenshot-Virt-Manager_fig31pt25.png | Bin 0 -> 25748 bytes
.../images/Screenshot-Virt-Manager_fig31pt25a.png | Bin 0 -> 23533 bytes
.../images/Screenshot-Virt-Manager_fig31pt26.png | Bin 0 -> 30226 bytes
.../images/Screenshot-admin-18pt7-pic1.png | Bin 0 -> 38526 bytes
.../images/Screenshot-admin-18pt7-pic10.png | Bin 0 -> 48685 bytes
.../images/Screenshot-admin-18pt7-pic11.png | Bin 0 -> 60824 bytes
.../images/Screenshot-admin-18pt7-pic2.png | Bin 0 -> 38421 bytes
.../images/Screenshot-admin-18pt7-pic3.png | Bin 0 -> 19836 bytes
.../images/Screenshot-admin-18pt7-pic4.png | Bin 0 -> 38995 bytes
.../images/Screenshot-admin-18pt7-pic5.png | Bin 0 -> 33897 bytes
.../images/Screenshot-admin-18pt7-pic6.png | Bin 0 -> 29663 bytes
.../images/Screenshot-admin-18pt7-pic7.png | Bin 0 -> 32043 bytes
.../images/Screenshot-admin-18pt7-pic8.png | Bin 0 -> 46321 bytes
.../images/Screenshot-admin-18pt7-pic9.png | Bin 0 -> 70468 bytes
.../images/Screenshot-pic1-virt-mgr-guests.png | Bin 0 -> 22245 bytes
.../Screenshot-pic2-add-connection-pull-down.png | Bin 0 -> 22169 bytes
.../images/Screenshot-pic3-Add Connection.png | Bin 0 -> 18516 bytes
.../images/Screenshot-pic3-Add-Connection.png | Bin 0 -> 21410 bytes
.../images/Screenshot-pic4-OpenSSH.png | Bin 0 -> 11280 bytes
.../Screenshot-pic5-guest-select-migrate.png | Bin 0 -> 34896 bytes
.../Screenshot-pic6-final-before-migrate.png | Bin 0 -> 36898 bytes
.../Screenshot-pic7-Migrating-guest1-rhel6-64.png | Bin 0 -> 14788 bytes
.../images/Screenshot-pic8-migrated.png | Bin 0 -> 30438 bytes
.../images/Screenshot-rhel6pv-virt-method.png | Bin 0 -> 47301 bytes
.../images/Screenshot-sevenpt1-pic1.png | Bin 0 -> 23889 bytes
.../images/Screenshot-sevenpt1-pic2.png | Bin 0 -> 66922 bytes
.../images/Screenshot-sevenpt1-pic4.png | Bin 0 -> 62475 bytes
.../images/Screenshot-sevenpt1-pic5.png | Bin 0 -> 69613 bytes
.../images/Screenshot-sevenpt1-pic6.png | Bin 0 -> 46457 bytes
.../images/Screenshot-sevenpt1-pic7-managed.png | Bin 0 -> 36200 bytes
.../images/Screenshot-sevenpt1-pic7.png | Bin 0 -> 68403 bytes
.../images/Screenshot-sevenpt1-pic8-create-lvm.png | Bin 0 -> 42013 bytes
...Screenshot-sevenpt1-pic8-new-storage-volume.png | Bin 0 -> 76048 bytes
.../Screenshot-sevenpt1-pic9-local-storage.png | Bin 0 -> 100054 bytes
.../Screenshot-sevenpt1-pic9-storage-volume.png | Bin 0 -> 87492 bytes
.../images/Screenshot-sevenpt2-pic2.png | Bin 0 -> 82712 bytes
.../images/Screenshot-sevenpt2-pic3.png | Bin 0 -> 68632 bytes
.../images/Screenshot-sevenpt3-pic2.png | Bin 0 -> 68105 bytes
.../images/Screenshot-sevenpt3-pic3.png | Bin 0 -> 40893 bytes
.../images/Screenshot-sevenpt3-pic4.png | Bin 0 -> 41498 bytes
.../images/Screenshot-sevenpt3-pic5.png | Bin 0 -> 68403 bytes
.../images/Screenshot-sevenpt3-pic6.png | Bin 0 -> 83457 bytes
.../images/Screenshot-virtlab22-Host-Details.png | Bin 0 -> 49786 bytes
.../Section_11_pt_2_pt_2_step3_substep_c.png | Bin 0 -> 70469 bytes
.../Section_11_pt_2_pt_2_step3_substep_d.png | Bin 0 -> 67795 bytes
.../images/Select_storage_pools.png | Bin 0 -> 39490 bytes
.../images/StartDevManagerInVM.png | Bin 0 -> 330244 bytes
.../images/StartDevManagerInVM_win7.png | Bin 0 -> 223816 bytes
.../images/StartInstallingBalloon-1.png | Bin 0 -> 152903 bytes
.../images/StartInstallingBalloon-1_win7.png | Bin 0 -> 72036 bytes
.../images/Virt-Manager-Add-Connection.png | Bin 0 -> 21414 bytes
.../images/Virtual_Machine_Name-guest-install.png | Bin 0 -> 40239 bytes
...ual_Machine_Name-guest-install_STEP2-cpumem.png | Bin 0 -> 28224 bytes
...ual_Machine_Name-guest-install_STEP2-import.png | Bin 0 -> 29326 bytes
...tual_Machine_Name-guest-install_STEP2-local.png | Bin 0 -> 34657 bytes
.../Virtual_Machine_Name-guest-install_STEP4.png | Bin 0 -> 36303 bytes
...ual_Machine_Name-guest-install_STEP5-finish.png | Bin 0 -> 48968 bytes
...l_Machine_Name-guest-install_final-hardware.png | Bin 0 -> 76768 bytes
.../images/XP-driver-capture.png | Bin 0 -> 11814 bytes
.../images/XP-driver-select-driver.png | Bin 0 -> 240846 bytes
.../images/XP-driver-select2.png | Bin 0 -> 51574 bytes
.../images/after_virtualization.png | Bin 0 -> 39557 bytes
.../images/before_virtualization.png | Bin 0 -> 38000 bytes
.../images/block_finish-virtio-win.png | Bin 0 -> 61150 bytes
.../images/block_start-virtio-win.png | Bin 0 -> 24334 bytes
.../images/bridgePXE.png | Bin 0 -> 40131 bytes
.../images/bridgefinish.png | Bin 0 -> 49050 bytes
.../images/bz734652-step3.png | Bin 0 -> 302675 bytes
.../images/done-KVM_PV.png | Bin 0 -> 34673 bytes
.../images/exception-virtio-win.png | Bin 0 -> 23524 bytes
.../images/icon.svg | 19 +
.../images/ide-to-virtio-add-hardware.png | Bin 0 -> 129326 bytes
.../images/ide-to-virtio-remove-dev.png | Bin 0 -> 12609 bytes
.../images/ide-to-virtio1.png | Bin 0 -> 93665 bytes
.../images/ide-to-virtio1replacement.png | Bin 0 -> 81885 bytes
.../images/ide-to-virtio2.png | Bin 0 -> 97191 bytes
.../images/ide-to-virtio3.png | Bin 0 -> 94899 bytes
.../images/ide-to-virtio4.png | Bin 0 -> 107743 bytes
.../images/ide-to-virtio5.png | Bin 0 -> 108511 bytes
.../images/ide-to-virtio5replacement.png | Bin 0 -> 140191 bytes
.../images/ide-to-virtio6.png | Bin 0 -> 106978 bytes
.../images/ide-to-virtio6replacement.png | Bin 0 -> 17285 bytes
.../images/ide-to-virtio7.png | Bin 0 -> 95349 bytes
.../images/ide-to-virtio7replacement.png | Bin 0 -> 130528 bytes
.../images/infotabbutton.png | Bin 0 -> 1982 bytes
.../images/installmedia-blank.png | Bin 0 -> 28277 bytes
.../images/installmedia-select-os1.png | Bin 0 -> 31898 bytes
.../images/installmedia-select-volume.png | Bin 0 -> 26046 bytes
.../images/network_finish-virtio-win.png | Bin 0 -> 131791 bytes
.../images/network_performance-virtio-win.png | Bin 0 -> 21864 bytes
.../images/network_start-virtio-win.png | Bin 0 -> 63822 bytes
.../paravirt-0-click-configure-before-install.png | Bin 0 -> 32637 bytes
...avirt-0-click-configure-before-install_win7.png | Bin 0 -> 28916 bytes
.../images/paravirt-1-click-add-hardware.png | Bin 0 -> 2281 bytes
.../paravirt-10-select-custom-installation.png | Bin 0 -> 33229 bytes
.../images/paravirt-11-load-driver.png | Bin 0 -> 1659 bytes
.../images/paravirt-12-insert-disk.png | Bin 0 -> 19618 bytes
.../images/paravirt-13-select-driver-arch.png | Bin 0 -> 12390 bytes
.../images/paravirt-14-view-drivers-loaded.png | Bin 0 -> 11244 bytes
.../images/paravirt-2-disk-type.png | Bin 0 -> 4464 bytes
.../images/paravirt-2a-select-existing-storage.png | Bin 0 -> 5537 bytes
.../images/paravirt-2b-select-browse-local.png | Bin 0 -> 2319 bytes
.../images/paravirt-2c-virtio-win-vfd.png | Bin 0 -> 7385 bytes
.../images/paravirt-2z-select-storage.png | Bin 0 -> 67646 bytes
.../images/paravirt-3-floppy-advanced-options.png | Bin 0 -> 8673 bytes
.../images/paravirt-4-after-adding-virtio-disk.png | Bin 0 -> 66487 bytes
.../images/paravirt-5-begin-installation.png | Bin 0 -> 4211 bytes
.../images/paravirt-6-windows-install.png | Bin 0 -> 6419 bytes
.../paravirt-6a-select-installation-type.png | Bin 0 -> 28819 bytes
.../images/paravirt-8-agree-to-license-terms.png | Bin 0 -> 1138 bytes
.../images/paravirt-adding-virtio-disk.png | Bin 0 -> 65258 bytes
.../images/paravirt-click-begin-installation.png | Bin 0 -> 4230 bytes
.../images/paravirt-confirm-floppy-settings.png | Bin 0 -> 56639 bytes
.../images/paravirt-confirm-settings.png | Bin 0 -> 56545 bytes
.../images/paravirt-confirm-virtio-disk-in-use.png | Bin 0 -> 16477 bytes
.../images/paravirt-device-type-virtio-finish.png | Bin 0 -> 65699 bytes
.../images/paravirt-device-type-virtiodisk.png | Bin 0 -> 4683 bytes
.../images/paravirt-remove-disk1-2.png | Bin 0 -> 1493 bytes
.../images/paravirt-remove-disk1.png | Bin 0 -> 70993 bytes
.../images/paravirt-review-virtio-settings.png | Bin 0 -> 66335 bytes
.../images/paravirt-select-device-type-floppy.png | Bin 0 -> 4814 bytes
.../images/paravirt-storage-win7.png | Bin 0 -> 63115 bytes
.../images/pci_host_device.png | Bin 0 -> 129981 bytes
.../images/rhel5_rhel6pv_create_vm.png | Bin 0 -> 29497 bytes
.../images/rhel5_rhel6pv_finish.png | Bin 0 -> 49265 bytes
.../images/rhel5_rhel6pv_finish_3.png | Bin 0 -> 66701 bytes
.../images/rhel5_rhel6pv_install_method.png | Bin 0 -> 75364 bytes
.../images/rhel5_rhel6pv_install_source_2.png | Bin 0 -> 63977 bytes
.../images/rhel5_rhel6pv_mem_n_cpu_alloc.png | Bin 0 -> 90621 bytes
.../images/rhel5_rhel6pv_network.png | Bin 0 -> 70040 bytes
.../images/rhel5_rhel6pv_storage.png | Bin 0 -> 87583 bytes
.../images/rhel5_rhel6pv_virt_install.png | Bin 0 -> 27712 bytes
.../rhel6-Screenshot-step2-existing-disk-image.png | Bin 0 -> 36736 bytes
.../rhel6_Screenshot-guest1-rhel5-64-final.png | Bin 0 -> 64451 bytes
.../images/rhel6_Screenshot-step1.png | Bin 0 -> 39198 bytes
.../images/rhel6_Screenshot-step2.png | Bin 0 -> 35789 bytes
.../images/rhel6_Screenshot-step3.png | Bin 0 -> 26469 bytes
.../images/rhel6_Screenshot-step4.png | Bin 0 -> 34920 bytes
.../images/rhel6_Screenshot-step5.png | Bin 0 -> 52176 bytes
.../images/rhel6_virt_manager.png | Bin 0 -> 11628 bytes
.../images/selinux_uuid_block.png | Bin 0 -> 42886 bytes
.../images/shutter-9-3_win7-1.png | Bin 0 -> 53637 bytes
.../images/shutter-9-3_win7-2.png | Bin 0 -> 53447 bytes
.../images/shutter-9-3_win7-3.png | Bin 0 -> 60345 bytes
.../images/shutter-9-3_win7-4.png | Bin 0 -> 62326 bytes
.../images/step-1-1.png | Bin 0 -> 17359 bytes
.../images/step1-1.png | Bin 0 -> 17467 bytes
.../images/step1-2.png | Bin 0 -> 14463 bytes
.../images/step2-1.png | Bin 0 -> 58452 bytes
.../images/step2-2.png | Bin 0 -> 25501 bytes
.../images/step2-3.png | Bin 0 -> 36016 bytes
.../images/step2-4.png | Bin 0 -> 47641 bytes
.../images/step3-1.png | Bin 0 -> 40153 bytes
.../images/step4-1.png | Bin 0 -> 43876 bytes
.../images/step4-2.png | Bin 0 -> 17810 bytes
.../images/step5-1.png | Bin 0 -> 45055 bytes
.../images/step5-2.png | Bin 0 -> 32497 bytes
.../images/step5-3.png | Bin 0 -> 32720 bytes
.../images/type_assigned-KVM_PV.png | Bin 0 -> 61786 bytes
.../images/type_assigned-KVM_PV_new.png | Bin 0 -> 63191 bytes
.../images/v2v-add_storagepool.png | Bin 0 -> 23510 bytes
.../images/v2v-select_host.png | Bin 0 -> 12194 bytes
.../images/v2v-storage_tab.png | Bin 0 -> 44510 bytes
.../images/virt-manager-enable-disk-io.png | Bin 0 -> 18245 bytes
.../images/virt-manager-enable-networkio.png | Bin 0 -> 18218 bytes
.../images/virt-manager_add_nfs_step1.png | Bin 0 -> 27760 bytes
.../images/virt-manager_add_nfs_step2.png | Bin 0 -> 35312 bytes
.../images/virt-manager_add_storage_pool1.png | Bin 0 -> 27075 bytes
.../images/virt-manager_add_storage_pool2.png | Bin 0 -> 37625 bytes
.../images/virt-manager_hardware.png | Bin 0 -> 125992 bytes
.../images/virt-manager_hardware_wizard1.png | Bin 0 -> 36804 bytes
.../images/virt-manager_home.png | Bin 0 -> 32772 bytes
.../images/virt-manager_host_details_storage.png | Bin 0 -> 53958 bytes
.../images/virt-manager_main.png | Bin 0 -> 21512 bytes
.../images/virt-manager_newicon.png | Bin 0 -> 1475 bytes
.../images/virt-manager_select_host.png | Bin 0 -> 26025 bytes
..._storage_pools_add_dir_step_1_name_and_type.png | Bin 0 -> 26371 bytes
...er_storage_pools_add_dir_step_2_target_path.png | Bin 0 -> 33949 bytes
...manager_storage_pools_add_dir_step_3_result.png | Bin 0 -> 45724 bytes
...r_storage_pools_add_fs_step_1_name_and_type.png | Bin 0 -> 26216 bytes
...torage_pools_add_fs_step_2_paths_and_format.png | Bin 0 -> 32029 bytes
...-manager_storage_pools_add_fs_step_3_result.png | Bin 0 -> 46654 bytes
..._storage_pools_add_lvm_step_1_name_and_type.png | Bin 0 -> 26188 bytes
...torage_pools_add_lvm_step_2a_paths_and_pool.png | Bin 0 -> 32081 bytes
...torage_pools_add_lvm_step_2b_format_warning.png | Bin 0 -> 10141 bytes
...manager_storage_pools_add_lvm_step_3_result.png | Bin 0 -> 104017 bytes
.../images/virt-manager_virtualization_method.png | Bin 0 -> 71057 bytes
.../images/virtio-disk2.png | Bin 0 -> 47633 bytes
.../images/virtio-network-finish3.png | Bin 0 -> 31957 bytes
.../images/virtio-network-step1.png | Bin 0 -> 36985 bytes
.../images/virtio-network-step2.png | Bin 0 -> 40243 bytes
.../images/virtio-storage-finish3.png | Bin 0 -> 34181 bytes
.../images/virtio-storage-step1-new.png | Bin 0 -> 62145 bytes
.../images/virtio-storage-step1.png | Bin 0 -> 37033 bytes
.../images/virtio-storage-step2-new.png | Bin 0 -> 64041 bytes
.../images/virtio-storage-step2.png | Bin 0 -> 61079 bytes
.../images/virtio0-customize.png | Bin 0 -> 58502 bytes
.../images/virtio3-finished.png | Bin 0 -> 27470 bytes
.../images/virtual_machine_overview.png | Bin 0 -> 73963 bytes
.../images/vm-add_hardware1.png | Bin 0 -> 79211 bytes
.../images/vm_add_hardware.png | Bin 0 -> 6306 bytes
.../images/vm_add_hardware_new.png | Bin 0 -> 2266 bytes
.../images/vm_info_button.png | Bin 0 -> 4964 bytes
.../images/vm_info_button_new.png | Bin 0 -> 3557 bytes
.../images/vmm_vnet_create1.png | Bin 0 -> 38424 bytes
.../images/vmm_vnet_create2.png | Bin 0 -> 19689 bytes
.../images/vmm_vnet_create3_ipv4addspace.png | Bin 0 -> 38805 bytes
.../images/vmm_vnet_create4_dhcprange.png | Bin 0 -> 33089 bytes
.../images/vmm_vnet_create5_connectphysnet.png | Bin 0 -> 29901 bytes
.../images/vmm_vnet_create6_finish.png | Bin 0 -> 31511 bytes
.../images/vmm_vnet_create7_maintab.png | Bin 0 -> 43333 bytes
.../images/vmm_vnet_maintab.png | Bin 0 -> 41593 bytes
.../images/vmm_vnet_menuselect.png | Bin 0 -> 20814 bytes
.../images/vn-01-switch.png | Bin 0 -> 10406 bytes
.../images/vn-02-switchandtwoguests.png | Bin 0 -> 42987 bytes
.../images/vn-03-hostwithswitch.png | Bin 0 -> 25369 bytes
.../images/vn-04-hostwithnatswitch.png | Bin 0 -> 135903 bytes
.../images/vn-05-switchwithdnsmasq.jpg | Bin 0 -> 216332 bytes
.../images/vn-06-routed-switch.png | Bin 0 -> 139243 bytes
.../images/vn-07-isolated-switch.png | Bin 0 -> 131466 bytes
.../images/vn-08-network-overview.png | Bin 0 -> 364520 bytes
.../images/vn-09-routed-mode-DMZ.png | Bin 0 -> 635464 bytes
.../images/vn-10-routed-mode-datacenter.png | Bin 0 -> 415490 bytes
.../images/vn-11-router-mode-mac-restricted.png | Bin 0 -> 398974 bytes
.../images/vn-12-network-tab-default.png | Bin 0 -> 39835 bytes
.../images/w7x86driverchosen.png | Bin 0 -> 22359 bytes
.../images/win2003_select_hal.png | Bin 0 -> 8979 bytes
...win7paravirt-click-configure-before-install.png | Bin 0 -> 28908 bytes
.../index.html |12710 ++++++++++++++++++++
.../App_Bridge_Device.html | 46 +
.../App_DHCP_Response_Checksums.html | 18 +
.../App_Domain_Console.html | 29 +
.../App_Domain_Monitor_Socket.html | 33 +
.../App_Domain_Not_Booting.html | 86 +
.../App_Domain_Processor.html | 20 +
.../App_Generic_Ethernet.html | 45 +
.../App_Hypervisor_Connection_Fail.html | 26 +
.../App_Macvtap.html | 44 +
.../App_Migration_Address.html | 34 +
.../App_Migration_Disk_Image.html | 34 +
.../App_No_Guest_Machines.html | 44 +
.../App_PXE_Guest_Boot_Fail.html | 71 +
.../App_TCP_Ports.html | 33 +
.../App_Virt_Net_Not_Starting.html | 40 +
.../App_XML_Errors.html | 28 +
.../Common_Content/css/common.css | 1528 +++
.../Common_Content/css/default.css | 3 +
.../Common_Content/css/lang.css | 2 +
.../Common_Content/css/menu.css | 48 +
.../Common_Content/css/overrides.css | 46 +
.../Common_Content/css/pdf.css | 138 +
.../Common_Content/css/print.css | 16 +
.../Common_Content/images/1.png | Bin 0 -> 640 bytes
.../Common_Content/images/1.svg | 27 +
.../Common_Content/images/10.png | Bin 0 -> 942 bytes
.../Common_Content/images/10.svg | 31 +
.../Common_Content/images/11.png | Bin 0 -> 741 bytes
.../Common_Content/images/11.svg | 31 +
.../Common_Content/images/12.png | Bin 0 -> 943 bytes
.../Common_Content/images/12.svg | 31 +
.../Common_Content/images/13.png | Bin 0 -> 983 bytes
.../Common_Content/images/13.svg | 31 +
.../Common_Content/images/14.png | Bin 0 -> 862 bytes
.../Common_Content/images/14.svg | 31 +
.../Common_Content/images/15.png | Bin 0 -> 936 bytes
.../Common_Content/images/15.svg | 31 +
.../Common_Content/images/16.png | Bin 0 -> 975 bytes
.../Common_Content/images/16.svg | 31 +
.../Common_Content/images/17.png | Bin 0 -> 838 bytes
.../Common_Content/images/17.svg | 31 +
.../Common_Content/images/18.png | Bin 0 -> 1013 bytes
.../Common_Content/images/18.svg | 31 +
.../Common_Content/images/19.png | Bin 0 -> 989 bytes
.../Common_Content/images/19.svg | 31 +
.../Common_Content/images/2.png | Bin 0 -> 814 bytes
.../Common_Content/images/2.svg | 27 +
.../Common_Content/images/20.png | Bin 0 -> 1086 bytes
.../Common_Content/images/20.svg | 31 +
.../Common_Content/images/21.png | Bin 0 -> 925 bytes
.../Common_Content/images/21.svg | 31 +
.../Common_Content/images/22.png | Bin 0 -> 1059 bytes
.../Common_Content/images/22.svg | 31 +
.../Common_Content/images/23.png | Bin 0 -> 1152 bytes
.../Common_Content/images/23.svg | 31 +
.../Common_Content/images/24.png | Bin 0 -> 1013 bytes
.../Common_Content/images/24.svg | 31 +
.../Common_Content/images/25.png | Bin 0 -> 1108 bytes
.../Common_Content/images/25.svg | 31 +
.../Common_Content/images/26.png | Bin 0 -> 1149 bytes
.../Common_Content/images/26.svg | 31 +
.../Common_Content/images/27.png | Bin 0 -> 1007 bytes
.../Common_Content/images/27.svg | 31 +
.../Common_Content/images/28.png | Bin 0 -> 1177 bytes
.../Common_Content/images/28.svg | 31 +
.../Common_Content/images/29.png | Bin 0 -> 1135 bytes
.../Common_Content/images/29.svg | 31 +
.../Common_Content/images/3.png | Bin 0 -> 889 bytes
.../Common_Content/images/3.svg | 27 +
.../Common_Content/images/30.png | Bin 0 -> 1179 bytes
.../Common_Content/images/30.svg | 31 +
.../Common_Content/images/31.png | Bin 0 -> 1012 bytes
.../Common_Content/images/31.svg | 31 +
.../Common_Content/images/32.png | Bin 0 -> 1151 bytes
.../Common_Content/images/32.svg | 31 +
.../Common_Content/images/33.png | Bin 0 -> 1213 bytes
.../Common_Content/images/33.svg | 31 +
.../Common_Content/images/34.png | Bin 0 -> 1107 bytes
.../Common_Content/images/34.svg | 31 +
.../Common_Content/images/35.png | Bin 0 -> 1176 bytes
.../Common_Content/images/35.svg | 31 +
.../Common_Content/images/36.png | Bin 0 -> 1222 bytes
.../Common_Content/images/36.svg | 31 +
.../Common_Content/images/37.png | Bin 0 -> 1085 bytes
.../Common_Content/images/37.svg | 31 +
.../Common_Content/images/38.png | Bin 0 -> 1256 bytes
.../Common_Content/images/38.svg | 31 +
.../Common_Content/images/39.png | Bin 0 -> 1226 bytes
.../Common_Content/images/39.svg | 31 +
.../Common_Content/images/4.png | Bin 0 -> 783 bytes
.../Common_Content/images/4.svg | 27 +
.../Common_Content/images/40.png | Bin 0 -> 1082 bytes
.../Common_Content/images/40.svg | 31 +
.../Common_Content/images/5.png | Bin 0 -> 839 bytes
.../Common_Content/images/5.svg | 27 +
.../Common_Content/images/6.png | Bin 0 -> 868 bytes
.../Common_Content/images/6.svg | 27 +
.../Common_Content/images/7.png | Bin 0 -> 757 bytes
.../Common_Content/images/7.svg | 27 +
.../Common_Content/images/8.png | Bin 0 -> 914 bytes
.../Common_Content/images/8.svg | 27 +
.../Common_Content/images/9.png | Bin 0 -> 877 bytes
.../Common_Content/images/9.svg | 27 +
.../Common_Content/images/bkgrnd_greydots.png | Bin 0 -> 157 bytes
.../Common_Content/images/bullet_arrowblue.png | Bin 0 -> 177 bytes
.../Common_Content/images/documentation.png | Bin 0 -> 1358 bytes
.../Common_Content/images/dot.png | Bin 0 -> 98 bytes
.../Common_Content/images/dot2.png | Bin 0 -> 98 bytes
.../Common_Content/images/green.png | Bin 0 -> 176 bytes
.../Common_Content/images/h1-bg.png | Bin 0 -> 142 bytes
.../Common_Content/images/image_left.png | Bin 0 -> 2278 bytes
.../Common_Content/images/image_right.png | Bin 0 -> 1358 bytes
.../Common_Content/images/important.png | Bin 0 -> 1918 bytes
.../Common_Content/images/important.svg | 30 +
.../Common_Content/images/note.png | Bin 0 -> 1616 bytes
.../Common_Content/images/note.svg | 28 +
.../Common_Content/images/red.png | Bin 0 -> 163 bytes
.../Common_Content/images/redhat-logo.svg | 94 +
.../Common_Content/images/rhlogo.png | Bin 0 -> 2278 bytes
.../Common_Content/images/shade.png | Bin 0 -> 101 bytes
.../Common_Content/images/shine.png | Bin 0 -> 146 bytes
.../Common_Content/images/stock-go-back.png | Bin 0 -> 571 bytes
.../Common_Content/images/stock-go-forward.png | Bin 0 -> 531 bytes
.../Common_Content/images/stock-go-up.png | Bin 0 -> 582 bytes
.../Common_Content/images/stock-home.png | Bin 0 -> 772 bytes
.../Common_Content/images/title_logo.png | Bin 0 -> 2278 bytes
.../Common_Content/images/title_logo.svg | 94 +
.../Common_Content/images/warning.png | Bin 0 -> 1940 bytes
.../Common_Content/images/warning.svg | 32 +
.../Common_Content/images/watermark-draft.png | Bin 0 -> 25365 bytes
.../Common_Content/images/yellow.png | Bin 0 -> 175 bytes
.../Live_migration_and_RHEL_compatibility.html | 18 +
.../Sect_Failed_to_connect_socket.html | 22 +
.../Sect_Other_Connectivity_Errors.html | 14 +
.../apas02.html | 120 +
.../apas04.html | 14 +
.../apb.html | 173 +
.../apbs17s02.html | 38 +
.../apbs17s02s02.html | 21 +
.../apbs17s02s03.html | 41 +
.../apbs17s02s04.html | 20 +
.../apbs17s03.html | 22 +
.../apbs17s03s02.html | 30 +
.../apds02.html | 62 +
.../apds03.html | 72 +
.../apds04.html | 106 +
.../apds05.html | 32 +
.../apds06.html | 458 +
.../apds07.html | 18 +
.../apds08.html | 60 +
.../apds09.html | 18 +
.../apds10.html | 24 +
.../apes05.html | 26 +
.../apes06.html | 22 +
.../apes07.html | 40 +
.../apes08.html | 26 +
.../apes09.html | 19 +
.../apes10.html | 119 +
.../apes11.html | 55 +
.../apes14s03.html | 95 +
.../apes14s04.html | 32 +
.../apjs14.html | 53 +
...oyment_and_Administration-Revision_History.html | 19 +
.../appe-Virtualization-Additional_resources.html | 32 +
.../ch-lib-dom-xml.html | 54 +
.../ch01s02.html | 46 +
.../ch03s02.html | 75 +
.../ch07s02.html | 34 +
.../ch07s03.html | 30 +
.../ch08.html | 16 +
.../ch08s02.html | 12 +
.../ch10s04.html | 69 +
.../ch11s02.html | 23 +
.../ch12s03.html | 87 +
.../ch12s04.html | 28 +
.../ch13s03.html | 29 +
.../ch15s02.html | 29 +
.../ch15s02s02.html | 28 +
.../ch18s04.html | 28 +
.../ch19s02.html | 52 +
.../ch24s02.html | 20 +
.../ch25s05.html | 179 +
.../ch25s07.html | 42 +
.../ch29s02.html | 27 +
.../ch29s03.html | 18 +
.../ch29s04.html | 19 +
.../ch29s05.html | 41 +
.../ch29s06.html | 24 +
.../chap-KSM.html | 101 +
...Virtualization-Security_for_virtualization.html | 26 +
...dministration_Guide-Guest_Disks_libguestfs.html | 34 +
...on_Administration_Guide-KVM_live_migration.html | 64 +
...h_the_Virtual_Machine_Manager_virt_manager.html | 38 +
...istration_Guide-Managing_guests_with_virsh.html | 400 +
...on_Administration_Guide-QEMU_KVM_Whitelist.html | 22 +
...de-Remote_management_of_virtualized_guests.html | 76 +
...Administration_Guide-Server_best_practices.html | 23 +
...tion_Administration_Guide-Storage_Concepts.html | 30 +
...stration_Guide-Storage_Pools-Storage_Pools.html | 793 ++
...ation_Administration_Guide-Storage_Volumes.html | 39 +
...ation_Administration_Guide-Tips_and_tricks.html | 26 +
...ation_Administration_Guide-Troubleshooting.html | 78 +
...on_Administration_Guide-Virtual_Networking.html | 34 +
...irtualization_Administration_GuideAdvanced.html | 18 +
...uest_Installation_Guide-Guest_Installation.html | 28 +
..._Manager-Creating_guests_with_virt_manager.html | 62 +
...Guest_Installation_Guide-Host_Installation.html | 43 +
..._and_Guest_Installation_Guide-Introduction.html | 18 +
...Guest_Installation_Guide-KVM_Compatibility.html | 24 +
...allation_Guide-KVM_guest_timing_management.html | 79 +
...Installation_Guide-Libvirt_network_booting.html | 39 +
...t_Installation_Guide-Network_Configuration.html | 57 +
...Guest_Installation_Guide-PCI_Device_Config.html | 161 +
...nstallation_Guide-Para_virtualized_drivers.html | 76 +
...and_Guest_Installation_Guide-RHEL6_Install.html | 94 +
...ration_and_Guest_Installation_Guide-SR_IOV.html | 34 +
...est_Installation_Guide-System_Requirements.html | 62 +
...tion_Restrictions-Application_Restrictions.html | 24 +
...ualization_Restrictions-Other_Restrictions.html | 12 +
...allation_Guide-Virtualization_Restrictions.html | 78 +
.../chap-sVirt.html | 24 +
...irtual_machine_XML_dump_configuration_file.html | 123 +
...-Installing_with_a_virtualized_floppy_disk.html | 84 +
...ivers-Mounting_the_image_with_virt_manager.html | 82 +
...a_virtualized_drivers_for_existing_devices.html | 32 +
.../images/1-7RHEL_local_install.png | Bin 0 -> 13795 bytes
.../images/1-Iso_general.png | Bin 0 -> 66439 bytes
.../images/1-files_PV-win.png | Bin 0 -> 58708 bytes
.../images/10-7RHEL_local_install.png | Bin 0 -> 40128 bytes
.../images/10-w7x86driverchosen.png | Bin 0 -> 70168 bytes
.../images/10-w7x86driverchosen_win7.png | Bin 0 -> 19979 bytes
.../images/10-w7x86driverstart.png | Bin 0 -> 67481 bytes
.../images/10-w7x86driverstart_win7.png | Bin 0 -> 20672 bytes
.../images/11-7RHEL_local_install.png | Bin 0 -> 42123 bytes
.../images/12-DriverInstalled.png | Bin 0 -> 42765 bytes
.../images/14-StartInstallSerial.png | Bin 0 -> 89324 bytes
.../images/2-7RHEL_local_install.png | Bin 0 -> 31149 bytes
.../images/2-Iso_Balloon_Os.png | Bin 0 -> 58380 bytes
.../images/3-7RHEL_local_install.png | Bin 0 -> 26452 bytes
.../images/3-Iso_Balloon_Os_arch.png | Bin 0 -> 58272 bytes
.../images/3_PCI_Device.png | Bin 0 -> 179475 bytes
.../images/4-7RHEL_local_install.png | Bin 0 -> 29310 bytes
.../images/4-Iso_balloon_files.png | Bin 0 -> 69579 bytes
.../images/4_finish.png | Bin 0 -> 24479 bytes
.../images/5-7RHEL_local_install.png | Bin 0 -> 29133 bytes
.../images/6-7RHEL_local_install.png | Bin 0 -> 19657 bytes
.../images/6.4-2.png | Bin 0 -> 24447 bytes
.../images/6.4-3.png | Bin 0 -> 25646 bytes
.../images/6.4-4.png | Bin 0 -> 35108 bytes
.../images/7-7RHEL_local_install.png | Bin 0 -> 24996 bytes
.../images/8-7RHEL_local_install.png | Bin 0 -> 21005 bytes
.../images/8-BrowseForDriver.png | Bin 0 -> 76374 bytes
.../images/8-BrowseForDriver_win7.png | Bin 0 -> 20271 bytes
.../images/9-7RHEL_local_install.png | Bin 0 -> 34205 bytes
.../images/9-BrowseToDirectory.png | Bin 0 -> 17326 bytes
.../images/9-BrowseToDirectory_win7.png | Bin 0 -> 15823 bytes
.../images/COPYME.png | Bin 0 -> 60798 bytes
.../images/ChangeType.png | Bin 0 -> 119508 bytes
.../images/Connection_Details.png | Bin 0 -> 17102 bytes
.../images/Create-1.png | Bin 0 -> 68190 bytes
.../images/DevManagerStart.png | Bin 0 -> 115214 bytes
.../images/DevManagerStart_win7.png | Bin 0 -> 51206 bytes
.../images/DriverInstall-Expand.png | Bin 0 -> 111352 bytes
.../images/DriverInstall-OpenWizard.png | Bin 0 -> 10335 bytes
.../images/DriverInstall-OpenWizard_win7.png | Bin 0 -> 9493 bytes
.../images/DriverInstallExpand_win7.png | Bin 0 -> 92965 bytes
.../images/DuringInstallation.png | Bin 0 -> 25758 bytes
.../images/Iso_Balloon_files.png | Bin 0 -> 64585 bytes
.../images/Iso_general.png | Bin 0 -> 60798 bytes
.../images/ManageStart.png | Bin 0 -> 225210 bytes
.../images/Network_hardware.png | Bin 0 -> 52560 bytes
.../images/Network_hardware_virtio.png | Bin 0 -> 51598 bytes
.../images/PCIremoval.png | Bin 0 -> 55777 bytes
.../images/PXEguest_5of5.png | Bin 0 -> 46145 bytes
.../images/RHEL6_cpu+ram.png | Bin 0 -> 26155 bytes
.../images/RHEL6_finish_advanced.png | Bin 0 -> 49113 bytes
.../images/RHEL6_storage.png | Bin 0 -> 36029 bytes
.../images/RHEL6_storage_local.png | Bin 0 -> 33867 bytes
.../images/RHEL6_virt-manager_new_1.png | Bin 0 -> 38313 bytes
.../images/RHEL6local_choose.png | Bin 0 -> 52384 bytes
.../images/RHEL6local_selectedISO.png | Bin 0 -> 36710 bytes
.../images/RHELKVMpackages-2.png | Bin 0 -> 77122 bytes
.../images/RHELKVMpackages.png | Bin 0 -> 79030 bytes
.../images/RHELcustomize14.png | Bin 0 -> 104378 bytes
.../images/RHELcustomize15.png | Bin 0 -> 69240 bytes
.../images/RHELkvmSelect.png | Bin 0 -> 78106 bytes
.../images/SR-IOV_implementation.png | Bin 0 -> 75739 bytes
.../images/Screenshot-VIrt-Manager-fig31pt18.png | Bin 0 -> 27887 bytes
.../images/Screenshot-Virt-Manager-fig31pt1.png | Bin 0 -> 23228 bytes
.../images/Screenshot-Virt-Manager-fig31pt11.png | Bin 0 -> 27810 bytes
.../images/Screenshot-Virt-Manager-fig31pt13.png | Bin 0 -> 62072 bytes
.../images/Screenshot-Virt-Manager-fig31pt14.png | Bin 0 -> 80532 bytes
.../images/Screenshot-Virt-Manager-fig31pt15.png | Bin 0 -> 52668 bytes
.../images/Screenshot-Virt-Manager-fig31pt16.png | Bin 0 -> 72095 bytes
.../images/Screenshot-Virt-Manager-fig31pt17.png | Bin 0 -> 50464 bytes
.../images/Screenshot-Virt-Manager-fig31pt19.png | Bin 0 -> 22060 bytes
.../images/Screenshot-Virt-Manager-fig31pt2.png | Bin 0 -> 25861 bytes
.../images/Screenshot-Virt-Manager-fig31pt24.png | Bin 0 -> 29361 bytes
.../images/Screenshot-Virt-Manager-fig31pt24a.png | Bin 0 -> 29080 bytes
.../images/Screenshot-Virt-Manager-fig31pt27.png | Bin 0 -> 22828 bytes
.../images/Screenshot-Virt-Manager-fig31pt28.png | Bin 0 -> 33316 bytes
.../images/Screenshot-Virt-Manager-fig31pt29.png | Bin 0 -> 24925 bytes
.../images/Screenshot-Virt-Manager-fig31pt3.png | Bin 0 -> 69957 bytes
.../images/Screenshot-Virt-Manager-fig31pt4.png | Bin 0 -> 68968 bytes
.../images/Screenshot-Virt-Manager-fig31pt5.png | Bin 0 -> 548594 bytes
.../images/Screenshot-Virt-Manager-fig31pt6.png | Bin 0 -> 22883 bytes
.../images/Screenshot-Virt-Manager-fig31pt7.png | Bin 0 -> 25774 bytes
.../images/Screenshot-Virt-Manager_fig31pt25.png | Bin 0 -> 25748 bytes
.../images/Screenshot-Virt-Manager_fig31pt25a.png | Bin 0 -> 23533 bytes
.../images/Screenshot-Virt-Manager_fig31pt26.png | Bin 0 -> 30226 bytes
.../images/Screenshot-admin-18pt7-pic1.png | Bin 0 -> 38526 bytes
.../images/Screenshot-admin-18pt7-pic10.png | Bin 0 -> 48685 bytes
.../images/Screenshot-admin-18pt7-pic11.png | Bin 0 -> 60824 bytes
.../images/Screenshot-admin-18pt7-pic2.png | Bin 0 -> 38421 bytes
.../images/Screenshot-admin-18pt7-pic3.png | Bin 0 -> 19836 bytes
.../images/Screenshot-admin-18pt7-pic4.png | Bin 0 -> 38995 bytes
.../images/Screenshot-admin-18pt7-pic5.png | Bin 0 -> 33897 bytes
.../images/Screenshot-admin-18pt7-pic6.png | Bin 0 -> 29663 bytes
.../images/Screenshot-admin-18pt7-pic7.png | Bin 0 -> 32043 bytes
.../images/Screenshot-admin-18pt7-pic8.png | Bin 0 -> 46321 bytes
.../images/Screenshot-admin-18pt7-pic9.png | Bin 0 -> 70468 bytes
.../images/Screenshot-pic1-virt-mgr-guests.png | Bin 0 -> 22245 bytes
.../Screenshot-pic2-add-connection-pull-down.png | Bin 0 -> 22169 bytes
.../images/Screenshot-pic3-Add Connection.png | Bin 0 -> 18516 bytes
.../images/Screenshot-pic3-Add-Connection.png | Bin 0 -> 21410 bytes
.../images/Screenshot-pic4-OpenSSH.png | Bin 0 -> 11280 bytes
.../Screenshot-pic5-guest-select-migrate.png | Bin 0 -> 34896 bytes
.../Screenshot-pic6-final-before-migrate.png | Bin 0 -> 36898 bytes
.../Screenshot-pic7-Migrating-guest1-rhel6-64.png | Bin 0 -> 14788 bytes
.../images/Screenshot-pic8-migrated.png | Bin 0 -> 30438 bytes
.../images/Screenshot-rhel6pv-virt-method.png | Bin 0 -> 47301 bytes
.../images/Screenshot-sevenpt1-pic1.png | Bin 0 -> 23889 bytes
.../images/Screenshot-sevenpt1-pic2.png | Bin 0 -> 66922 bytes
.../images/Screenshot-sevenpt1-pic4.png | Bin 0 -> 62475 bytes
.../images/Screenshot-sevenpt1-pic5.png | Bin 0 -> 69613 bytes
.../images/Screenshot-sevenpt1-pic6.png | Bin 0 -> 46457 bytes
.../images/Screenshot-sevenpt1-pic7-managed.png | Bin 0 -> 36200 bytes
.../images/Screenshot-sevenpt1-pic7.png | Bin 0 -> 68403 bytes
.../images/Screenshot-sevenpt1-pic8-create-lvm.png | Bin 0 -> 42013 bytes
...Screenshot-sevenpt1-pic8-new-storage-volume.png | Bin 0 -> 76048 bytes
.../Screenshot-sevenpt1-pic9-local-storage.png | Bin 0 -> 100054 bytes
.../Screenshot-sevenpt1-pic9-storage-volume.png | Bin 0 -> 87492 bytes
.../images/Screenshot-sevenpt2-pic2.png | Bin 0 -> 82712 bytes
.../images/Screenshot-sevenpt2-pic3.png | Bin 0 -> 68632 bytes
.../images/Screenshot-sevenpt3-pic2.png | Bin 0 -> 68105 bytes
.../images/Screenshot-sevenpt3-pic3.png | Bin 0 -> 40893 bytes
.../images/Screenshot-sevenpt3-pic4.png | Bin 0 -> 41498 bytes
.../images/Screenshot-sevenpt3-pic5.png | Bin 0 -> 68403 bytes
.../images/Screenshot-sevenpt3-pic6.png | Bin 0 -> 83457 bytes
.../images/Screenshot-virtlab22-Host-Details.png | Bin 0 -> 49786 bytes
.../Section_11_pt_2_pt_2_step3_substep_c.png | Bin 0 -> 70469 bytes
.../Section_11_pt_2_pt_2_step3_substep_d.png | Bin 0 -> 67795 bytes
.../images/Select_storage_pools.png | Bin 0 -> 39490 bytes
.../images/StartDevManagerInVM.png | Bin 0 -> 330244 bytes
.../images/StartDevManagerInVM_win7.png | Bin 0 -> 223816 bytes
.../images/StartInstallingBalloon-1.png | Bin 0 -> 152903 bytes
.../images/StartInstallingBalloon-1_win7.png | Bin 0 -> 72036 bytes
.../images/Virt-Manager-Add-Connection.png | Bin 0 -> 21414 bytes
.../images/Virtual_Machine_Name-guest-install.png | Bin 0 -> 40239 bytes
...ual_Machine_Name-guest-install_STEP2-cpumem.png | Bin 0 -> 28224 bytes
...ual_Machine_Name-guest-install_STEP2-import.png | Bin 0 -> 29326 bytes
...tual_Machine_Name-guest-install_STEP2-local.png | Bin 0 -> 34657 bytes
.../Virtual_Machine_Name-guest-install_STEP4.png | Bin 0 -> 36303 bytes
...ual_Machine_Name-guest-install_STEP5-finish.png | Bin 0 -> 48968 bytes
...l_Machine_Name-guest-install_final-hardware.png | Bin 0 -> 76768 bytes
.../images/XP-driver-capture.png | Bin 0 -> 11814 bytes
.../images/XP-driver-select-driver.png | Bin 0 -> 240846 bytes
.../images/XP-driver-select2.png | Bin 0 -> 51574 bytes
.../images/after_virtualization.png | Bin 0 -> 39557 bytes
.../images/before_virtualization.png | Bin 0 -> 38000 bytes
.../images/block_finish-virtio-win.png | Bin 0 -> 61150 bytes
.../images/block_start-virtio-win.png | Bin 0 -> 24334 bytes
.../images/bridgePXE.png | Bin 0 -> 40131 bytes
.../images/bridgefinish.png | Bin 0 -> 49050 bytes
.../images/bz734652-step3.png | Bin 0 -> 302675 bytes
.../images/done-KVM_PV.png | Bin 0 -> 34673 bytes
.../images/exception-virtio-win.png | Bin 0 -> 23524 bytes
.../images/icon.svg | 19 +
.../images/ide-to-virtio-add-hardware.png | Bin 0 -> 129326 bytes
.../images/ide-to-virtio-remove-dev.png | Bin 0 -> 12609 bytes
.../images/ide-to-virtio1.png | Bin 0 -> 93665 bytes
.../images/ide-to-virtio1replacement.png | Bin 0 -> 81885 bytes
.../images/ide-to-virtio2.png | Bin 0 -> 97191 bytes
.../images/ide-to-virtio3.png | Bin 0 -> 94899 bytes
.../images/ide-to-virtio4.png | Bin 0 -> 107743 bytes
.../images/ide-to-virtio5.png | Bin 0 -> 108511 bytes
.../images/ide-to-virtio5replacement.png | Bin 0 -> 140191 bytes
.../images/ide-to-virtio6.png | Bin 0 -> 106978 bytes
.../images/ide-to-virtio6replacement.png | Bin 0 -> 17285 bytes
.../images/ide-to-virtio7.png | Bin 0 -> 95349 bytes
.../images/ide-to-virtio7replacement.png | Bin 0 -> 130528 bytes
.../images/infotabbutton.png | Bin 0 -> 1982 bytes
.../images/installmedia-blank.png | Bin 0 -> 28277 bytes
.../images/installmedia-select-os1.png | Bin 0 -> 31898 bytes
.../images/installmedia-select-volume.png | Bin 0 -> 26046 bytes
.../images/network_finish-virtio-win.png | Bin 0 -> 131791 bytes
.../images/network_performance-virtio-win.png | Bin 0 -> 21864 bytes
.../images/network_start-virtio-win.png | Bin 0 -> 63822 bytes
.../paravirt-0-click-configure-before-install.png | Bin 0 -> 32637 bytes
...avirt-0-click-configure-before-install_win7.png | Bin 0 -> 28916 bytes
.../images/paravirt-1-click-add-hardware.png | Bin 0 -> 2281 bytes
.../paravirt-10-select-custom-installation.png | Bin 0 -> 33229 bytes
.../images/paravirt-11-load-driver.png | Bin 0 -> 1659 bytes
.../images/paravirt-12-insert-disk.png | Bin 0 -> 19618 bytes
.../images/paravirt-13-select-driver-arch.png | Bin 0 -> 12390 bytes
.../images/paravirt-14-view-drivers-loaded.png | Bin 0 -> 11244 bytes
.../images/paravirt-2-disk-type.png | Bin 0 -> 4464 bytes
.../images/paravirt-2a-select-existing-storage.png | Bin 0 -> 5537 bytes
.../images/paravirt-2b-select-browse-local.png | Bin 0 -> 2319 bytes
.../images/paravirt-2c-virtio-win-vfd.png | Bin 0 -> 7385 bytes
.../images/paravirt-2z-select-storage.png | Bin 0 -> 67646 bytes
.../images/paravirt-3-floppy-advanced-options.png | Bin 0 -> 8673 bytes
.../images/paravirt-4-after-adding-virtio-disk.png | Bin 0 -> 66487 bytes
.../images/paravirt-5-begin-installation.png | Bin 0 -> 4211 bytes
.../images/paravirt-6-windows-install.png | Bin 0 -> 6419 bytes
.../paravirt-6a-select-installation-type.png | Bin 0 -> 28819 bytes
.../images/paravirt-8-agree-to-license-terms.png | Bin 0 -> 1138 bytes
.../images/paravirt-adding-virtio-disk.png | Bin 0 -> 65258 bytes
.../images/paravirt-click-begin-installation.png | Bin 0 -> 4230 bytes
.../images/paravirt-confirm-floppy-settings.png | Bin 0 -> 56639 bytes
.../images/paravirt-confirm-settings.png | Bin 0 -> 56545 bytes
.../images/paravirt-confirm-virtio-disk-in-use.png | Bin 0 -> 16477 bytes
.../images/paravirt-device-type-virtio-finish.png | Bin 0 -> 65699 bytes
.../images/paravirt-device-type-virtiodisk.png | Bin 0 -> 4683 bytes
.../images/paravirt-remove-disk1-2.png | Bin 0 -> 1493 bytes
.../images/paravirt-remove-disk1.png | Bin 0 -> 70993 bytes
.../images/paravirt-review-virtio-settings.png | Bin 0 -> 66335 bytes
.../images/paravirt-select-device-type-floppy.png | Bin 0 -> 4814 bytes
.../images/paravirt-storage-win7.png | Bin 0 -> 63115 bytes
.../images/pci_host_device.png | Bin 0 -> 129981 bytes
.../images/rhel5_rhel6pv_create_vm.png | Bin 0 -> 29497 bytes
.../images/rhel5_rhel6pv_finish.png | Bin 0 -> 49265 bytes
.../images/rhel5_rhel6pv_finish_3.png | Bin 0 -> 66701 bytes
.../images/rhel5_rhel6pv_install_method.png | Bin 0 -> 75364 bytes
.../images/rhel5_rhel6pv_install_source_2.png | Bin 0 -> 63977 bytes
.../images/rhel5_rhel6pv_mem_n_cpu_alloc.png | Bin 0 -> 90621 bytes
.../images/rhel5_rhel6pv_network.png | Bin 0 -> 70040 bytes
.../images/rhel5_rhel6pv_storage.png | Bin 0 -> 87583 bytes
.../images/rhel5_rhel6pv_virt_install.png | Bin 0 -> 27712 bytes
.../rhel6-Screenshot-step2-existing-disk-image.png | Bin 0 -> 36736 bytes
.../rhel6_Screenshot-guest1-rhel5-64-final.png | Bin 0 -> 64451 bytes
.../images/rhel6_Screenshot-step1.png | Bin 0 -> 39198 bytes
.../images/rhel6_Screenshot-step2.png | Bin 0 -> 35789 bytes
.../images/rhel6_Screenshot-step3.png | Bin 0 -> 26469 bytes
.../images/rhel6_Screenshot-step4.png | Bin 0 -> 34920 bytes
.../images/rhel6_Screenshot-step5.png | Bin 0 -> 52176 bytes
.../images/rhel6_virt_manager.png | Bin 0 -> 11628 bytes
.../images/selinux_uuid_block.png | Bin 0 -> 42886 bytes
.../images/shutter-9-3_win7-1.png | Bin 0 -> 53637 bytes
.../images/shutter-9-3_win7-2.png | Bin 0 -> 53447 bytes
.../images/shutter-9-3_win7-3.png | Bin 0 -> 60345 bytes
.../images/shutter-9-3_win7-4.png | Bin 0 -> 62326 bytes
.../images/step-1-1.png | Bin 0 -> 17359 bytes
.../images/step1-1.png | Bin 0 -> 17467 bytes
.../images/step1-2.png | Bin 0 -> 14463 bytes
.../images/step2-1.png | Bin 0 -> 58452 bytes
.../images/step2-2.png | Bin 0 -> 25501 bytes
.../images/step2-3.png | Bin 0 -> 36016 bytes
.../images/step2-4.png | Bin 0 -> 47641 bytes
.../images/step3-1.png | Bin 0 -> 40153 bytes
.../images/step4-1.png | Bin 0 -> 43876 bytes
.../images/step4-2.png | Bin 0 -> 17810 bytes
.../images/step5-1.png | Bin 0 -> 45055 bytes
.../images/step5-2.png | Bin 0 -> 32497 bytes
.../images/step5-3.png | Bin 0 -> 32720 bytes
.../images/type_assigned-KVM_PV.png | Bin 0 -> 61786 bytes
.../images/type_assigned-KVM_PV_new.png | Bin 0 -> 63191 bytes
.../images/v2v-add_storagepool.png | Bin 0 -> 23510 bytes
.../images/v2v-select_host.png | Bin 0 -> 12194 bytes
.../images/v2v-storage_tab.png | Bin 0 -> 44510 bytes
.../images/virt-manager-enable-disk-io.png | Bin 0 -> 18245 bytes
.../images/virt-manager-enable-networkio.png | Bin 0 -> 18218 bytes
.../images/virt-manager_add_nfs_step1.png | Bin 0 -> 27760 bytes
.../images/virt-manager_add_nfs_step2.png | Bin 0 -> 35312 bytes
.../images/virt-manager_add_storage_pool1.png | Bin 0 -> 27075 bytes
.../images/virt-manager_add_storage_pool2.png | Bin 0 -> 37625 bytes
.../images/virt-manager_hardware.png | Bin 0 -> 125992 bytes
.../images/virt-manager_hardware_wizard1.png | Bin 0 -> 36804 bytes
.../images/virt-manager_home.png | Bin 0 -> 32772 bytes
.../images/virt-manager_host_details_storage.png | Bin 0 -> 53958 bytes
.../images/virt-manager_main.png | Bin 0 -> 21512 bytes
.../images/virt-manager_newicon.png | Bin 0 -> 1475 bytes
.../images/virt-manager_select_host.png | Bin 0 -> 26025 bytes
..._storage_pools_add_dir_step_1_name_and_type.png | Bin 0 -> 26371 bytes
...er_storage_pools_add_dir_step_2_target_path.png | Bin 0 -> 33949 bytes
...manager_storage_pools_add_dir_step_3_result.png | Bin 0 -> 45724 bytes
...r_storage_pools_add_fs_step_1_name_and_type.png | Bin 0 -> 26216 bytes
...torage_pools_add_fs_step_2_paths_and_format.png | Bin 0 -> 32029 bytes
...-manager_storage_pools_add_fs_step_3_result.png | Bin 0 -> 46654 bytes
..._storage_pools_add_lvm_step_1_name_and_type.png | Bin 0 -> 26188 bytes
...torage_pools_add_lvm_step_2a_paths_and_pool.png | Bin 0 -> 32081 bytes
...torage_pools_add_lvm_step_2b_format_warning.png | Bin 0 -> 10141 bytes
...manager_storage_pools_add_lvm_step_3_result.png | Bin 0 -> 104017 bytes
.../images/virt-manager_virtualization_method.png | Bin 0 -> 71057 bytes
.../images/virtio-disk2.png | Bin 0 -> 47633 bytes
.../images/virtio-network-finish3.png | Bin 0 -> 31957 bytes
.../images/virtio-network-step1.png | Bin 0 -> 36985 bytes
.../images/virtio-network-step2.png | Bin 0 -> 40243 bytes
.../images/virtio-storage-finish3.png | Bin 0 -> 34181 bytes
.../images/virtio-storage-step1-new.png | Bin 0 -> 62145 bytes
.../images/virtio-storage-step1.png | Bin 0 -> 37033 bytes
.../images/virtio-storage-step2-new.png | Bin 0 -> 64041 bytes
.../images/virtio-storage-step2.png | Bin 0 -> 61079 bytes
.../images/virtio0-customize.png | Bin 0 -> 58502 bytes
.../images/virtio3-finished.png | Bin 0 -> 27470 bytes
.../images/virtual_machine_overview.png | Bin 0 -> 73963 bytes
.../images/vm-add_hardware1.png | Bin 0 -> 79211 bytes
.../images/vm_add_hardware.png | Bin 0 -> 6306 bytes
.../images/vm_add_hardware_new.png | Bin 0 -> 2266 bytes
.../images/vm_info_button.png | Bin 0 -> 4964 bytes
.../images/vm_info_button_new.png | Bin 0 -> 3557 bytes
.../images/vmm_vnet_create1.png | Bin 0 -> 38424 bytes
.../images/vmm_vnet_create2.png | Bin 0 -> 19689 bytes
.../images/vmm_vnet_create3_ipv4addspace.png | Bin 0 -> 38805 bytes
.../images/vmm_vnet_create4_dhcprange.png | Bin 0 -> 33089 bytes
.../images/vmm_vnet_create5_connectphysnet.png | Bin 0 -> 29901 bytes
.../images/vmm_vnet_create6_finish.png | Bin 0 -> 31511 bytes
.../images/vmm_vnet_create7_maintab.png | Bin 0 -> 43333 bytes
.../images/vmm_vnet_maintab.png | Bin 0 -> 41593 bytes
.../images/vmm_vnet_menuselect.png | Bin 0 -> 20814 bytes
.../images/vn-01-switch.png | Bin 0 -> 10406 bytes
.../images/vn-02-switchandtwoguests.png | Bin 0 -> 42987 bytes
.../images/vn-03-hostwithswitch.png | Bin 0 -> 25369 bytes
.../images/vn-04-hostwithnatswitch.png | Bin 0 -> 135903 bytes
.../images/vn-05-switchwithdnsmasq.jpg | Bin 0 -> 216332 bytes
.../images/vn-06-routed-switch.png | Bin 0 -> 139243 bytes
.../images/vn-07-isolated-switch.png | Bin 0 -> 131466 bytes
.../images/vn-08-network-overview.png | Bin 0 -> 364520 bytes
.../images/vn-09-routed-mode-DMZ.png | Bin 0 -> 635464 bytes
.../images/vn-10-routed-mode-datacenter.png | Bin 0 -> 415490 bytes
.../images/vn-11-router-mode-mac-restricted.png | Bin 0 -> 398974 bytes
.../images/vn-12-network-tab-default.png | Bin 0 -> 39835 bytes
.../images/w7x86driverchosen.png | Bin 0 -> 22359 bytes
.../images/win2003_select_hal.png | Bin 0 -> 8979 bytes
...win7paravirt-click-configure-before-install.png | Bin 0 -> 28908 bytes
.../index.html | 44 +
.../live-migration-errors.html | 14 +
.../migrating_guests-with-virsh.html | 12 +
.../netkvm-parameters.html | 90 +
...tion_Deployment_and_Administration-Preface.html | 95 +
.../pt01.html | 10 +
.../pt02.html | 10 +
.../pt03.html | 10 +
.../qemu-ga.html | 30 +
.../run-virt-df.html | 44 +
.../sec-known-issues-windows-xp-guests.html | 12 +
...Attaching_and_updating_a_device_with_virsh.html | 12 +
.../sect-Augeas-and-libguestfs-scripting.html | 53 +
...-Guide-Guest_Disks_libguestfs-installation.html | 18 +
...ct-Managing_storage_controllers_in_a_guest.html | 42 +
.../sect-Modifying-files-with-guestfish.html | 29 +
.../sect-Network_Address_Translation-libvirt.html | 14 +
.../sect-Other-actions-with-guestfish.html | 12 +
.../sect-RedHat-We_Need_Feedback.html | 16 +
.../sect-Shell-scripting-with-guestfish.html | 21 +
.../sect-Terminology-Guest_Disks_libguestfs.html | 22 +
.../sect-Using-API-Programming-Languages.html | 243 +
..._drives_and_other_block_devices_to_a_guest.html | 45 +
...ditional_resources-Installed_documentation.html | 20 +
...ve_migration-Live_KVM_migration_with_virsh.html | 120 +
...live_migration-Migrating_with_virt_manager.html | 57 +
..._Manager_virt_manager-Displaying_CPU_usage.html | 16 +
...ne_Manager_virt_manager-Displaying_Disk_IO.html | 20 +
...Manager_virt_manager-Displaying_Network_IO.html | 20 +
...ager_virt_manager-Displaying_guest_details.html | 34 +
...ger_virt_manager-Displaying_host-CPU_usage.html | 16 +
...ine_Manager_virt_manager-Status_monitoring.html | 20 +
...he_Virtual_Machine_Manager_details_window_.html | 14 +
...er-The_Virtual_Machine_Manager_main_window.html | 12 +
...er_virt_manager-The_open_connection_window.html | 20 +
...manager-Virtual_Machine_graphical_console_.html | 20 +
...ts_with_virsh-Connecting_to_the_hypervisor.html | 14 +
..._guests-Remote_management_over_TLS_and_SSL.html | 90 +
...ment_of_virtualized_guests-Transport_modes.html | 109 +
..._virtualization-SELinux_and_virtualization.html | 43 +
..._for_virtualization-SELinux_considerations.html | 16 +
...ct-Virtualization-Storage_Concepts-Volumes.html | 63 +
...ualization-Storage_Volumes-Cloning_volumes.html | 36 +
...alization-Storage_Volumes-Deleting_volumes.html | 15 +
...n-Tips_and_tricks-Configuring_a_VNC_Server.html | 16 +
...s-Disable_SMART_disk_monitoring_for_guests.html | 14 +
...tricks-Generating_a_new_unique_MAC_address.html | 41 +
...ion-Tips_and_tricks-Libvirt_Managed_Timers.html | 156 +
...on-Tips_and_tricks-Overcommitting_with_KVM.html | 44 +
...tualization-Tips_and_tricks-Using_qemu_img.html | 103 +
...tricks-Verifying_virtualization_extensions.html | 39 +
...virtualization_hardware_extensions_in_BIOS.html | 36 +
...Troubleshooting-KVM_networking_performance.html | 60 +
...ization-Troubleshooting-Loop_device_errors.html | 15 +
...Characters_Guest_Console_Japanese_Keyboard.html | 38 +
...ting_-Troubleshooting_with_serial_consoles.html | 38 +
...working-Attaching_virtual_network_to_guest.html | 22 +
...tual_Networking-Creating_a_virtual_network.html | 32 +
...ation-Virtual_Networking-Example_scenarios.html | 20 +
...tual_Networking-Managing_a_virtual_network.html | 18 +
...k_devices-Adding_storage_devices_to_guests.html | 99 +
...allation-Creating_guests_with_virt_install.html | 37 +
...st_Installation-Installing_guests_with_PXE.html | 28 +
...n_existing_Red_Hat_Enterprise_Linux_system.html | 84 +
...figuration-Bridged_networking_with_libvirt.html | 21 +
...I_Assignment-Adding_a_PCI_device_to_a_host.html | 20 +
...M_para_virtualized_drivers_for_new_devices.html | 56 +
...tion_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html | 169 +
...ng_Windows_XP_as_a_fully_virtualized_guest.html | 46 +
.../sect-applying-network-filtering.html | 52 +
.../sect-attch-nic-physdev.html | 70 +
.../sect-cpu-allocation.html | 26 +
.../sect-cpu-tuning.html | 67 +
.../sect-dom-xml-op-sys-boot.html | 57 +
.../sect-dynamic-vNIC.html | 51 +
.../sect-expand-disk-image.html | 84 +
.../sect-gracefully-shut-down-guests.html | 27 +
.../sect-guest-cpu-model-config.html | 12 +
.../sect-learn-about-host-cpu.html | 44 +
.../sect-libguestfs-more-docs.html | 12 +
.../sect-libguestfs-troubleshoot.html | 16 +
.../sect-libvirt-dom-xml-blk-io-tuning.html | 46 +
.../sect-libvirt-dom-xml-cpu-model-top.html | 124 +
.../sect-libvirt-dom-xml-devices.html | 201 +
.../sect-libvirt-dom-xml-event-config.html | 91 +
.../sect-libvirt-dom-xml-mem-tuning.html | 49 +
.../sect-libvirt-dom-xml-numa-node-tuning.html | 36 +
.../sect-libvirt-dom-xml-pwr-man.html | 23 +
.../sect-libvirt-dom-xml-res-part.html | 23 +
.../sect-libvirt-dom-xml-time-keep.html | 74 +
.../sect-limit-redirection.html | 45 +
.../sect-man-disk-image.html | 74 +
.../sect-mem-back.html | 24 +
.../sect-mem-dump-off.html | 49 +
.../sect-network-protocols.html | 14 +
.../sect-other-commands.html | 29 +
.../sect-perf-mon.html | 20 +
.../sect-qemu-ga.html | 35 +
.../sect-run-virt-rescue.html | 57 +
.../sect-s3-s4.html | 21 +
.../sect-smbios-sys-info.html | 38 +
.../sect-the-Default_Configuration-libvirt.html | 14 +
.../sect-the_guestfish_shell.html | 122 +
.../sect-virt-df.html | 12 +
.../sect-virt-inspector-install.html | 16 +
.../sect-virt-inspector-run.html | 82 +
.../sect-virt-inspector.html | 12 +
.../sect-virt-rescue.html | 16 +
.../sect-virt-resize.html | 12 +
.../sect-virt-win-reg-install.html | 14 +
.../sect-virt-win-reg-use.html | 29 +
.../sect-virt-win-reg.html | 12 +
...ct_RedHat-Getting_Help_and_Giving_Feedback.html | 20 +
.../section-libvirt-dom-xml-example.html | 69 +
...ction-libvirt-dom-xml-memory-baloon-device.html | 34 +
.../section-libvirt-dom-xml-random-number-gen.html | 37 +
.../section-libvirt-dom-xml-security-label.html | 53 +
.../section-libvirt-dom-xml-sound-devices.html | 32 +
.../section-libvirt-dom-xml-tpm-device.html | 26 +
.../section-libvirt-dom-xml-watchdog.html | 51 +
.../shared-storage-nfs-migration.html | 33 +
.../sub-sect-adv-filt-topics.html | 24 +
.../sub-sect-auto-IP-add-detect-dhcp-snoop.html | 18 +
.../sub-sect-blkresize.html | 20 +
.../sub-sect-blockpull.html | 58 +
.../sub-sect-element-oview.html | 12 +
.../sub-sect-filt-chain-props.html | 48 +
.../sub-sect-filt-chain.html | 67 +
.../sub-sect-filter-rules.html | 51 +
.../sub-sect-iso-mode.html | 12 +
.../sub-sect-isolated-mode.html | 12 +
...sect-limitations-filters-network-subsystem.html | 18 +
.../sub-sect-nat-mode.html | 12 +
.../sub-sect-op-sys-cont-boot.html | 25 +
.../sub-sect-op-sys-dir-kern-boot.html | 51 +
.../sub-sect-op-sys-host-boot.html | 31 +
.../sub-sect-ref-filter.html | 28 +
.../sub-sect-routed-mode-libvirt.html | 12 +
.../sub-sect-supp-pros.html | 97 +
.../sub-sect-vars-in-filters.html | 72 +
.../sub-sect-vars-reserved.html | 40 +
...libvirt-dom-xml-devices-Network-interfaces.html | 56 +
...ub-section-libvirt-dom-xml-devices-channel.html | 42 +
...b-section-libvirt-dom-xml-devices-consoles.html | 38 +
...ection-libvirt-dom-xml-devices-controllers.html | 44 +
...n-libvirt-dom-xml-devices-device-addresses.html | 58 +
...tion-libvirt-dom-xml-devices-device-leases.html | 33 +
...ection-libvirt-dom-xml-devices-filesystems.html | 62 +
...irt-dom-xml-devices-graphical-framebuffers.html | 95 +
...on-libvirt-dom-xml-devices-guest-interface.html | 82 +
...irt-dom-xml-devices-host-device-assignment.html | 78 +
...ion-libvirt-dom-xml-devices-host-interface.html | 193 +
...ection-libvirt-dom-xml-devices-hub-devices.html | 23 +
...tion-libvirt-dom-xml-devices-input-devices.html | 26 +
...libvirt-dom-xml-devices-redirected-devices.html | 44 +
...-section-libvirt-dom-xml-devices-smartcard.html | 55 +
.../sub-section-libvirt-dom-xml-devices-video.html | 47 +
.../sub-sub-sect-DHCP-snooping.html | 25 +
.../sub-sub-sect-chars-IPv6.html | 104 +
.../sub-sub-sect-chars-tcp-udp.html | 128 +
.../sub-sub-sect-icmp.html | 128 +
.../sub-sub-sect-icmpv6.html | 110 +
.../sub-sub-sect-igmp-esp-ah-etc.html | 116 +
...sub-sub-sect-igmp-esp-ah-udplite-over-ipv6.html | 98 +
.../sub-sub-sect-lim-numb-conns.html | 43 +
.../sub-sub-sect-pre-exist-net-filter.html | 42 +
.../sub-sub-sect-prot-ARP-RARP-explained.html | 98 +
.../sub-sub-sect-prot-Ipv4-explained.html | 104 +
.../sub-sub-sect-prot-STP-explained.html | 158 +
.../sub-sub-sect-samp-filter.html | 146 +
.../sub-sub-sect-tcp-utp-sctp-over-ipv6.html | 122 +
.../sub-sub-sect-vlan.html | 62 +
.../sub-sub-sect-write-own-filters.html | 80 +
...-xml-devices-Network-interfaces-boot-order.html | 25 +
...l-devices-Network-interfaces-bridge-to-lan.html | 37 +
...faces-direct-attachment-to-physical-device.html | 114 +
...ork-interfaces-generic-ethernet-connection.html | 26 +
...evices-Network-interfaces-multicast-tunnel.html | 22 +
...k-interfaces-overriding-the-target-element.html | 24 +
...devices-Network-interfaces-pci-passthrough.html | 30 +
...rfaces-setting-nic-driver-specific-options.html | 45 +
...-xml-devices-Network-interfaces-tcp-tunnel.html | 27 +
...s-Network-interfaces-userspace-slirp-stack.html | 25 +
...-device-assignment-block-character-devices.html | 61 +
...l-devices-interface-ROM-BIOS-configuration.html | 25 +
...m-xml-devices-modifying-virtual-link-state.html | 25 +
...ub-sub-section-libvirt-dom-xml-devices-qos.html | 32 +
...n-libvirt-dom-xml-devices-setting-vlan-tag.html | 30 +
.../sub-sub-subsect-command-line-tools.html | 22 +
.../subsect-guest-synch-delimited.html | 26 +
.../vhostmd.html | 18 +
.../virsh-migration-arguements.html | 46 +
...n_Deployment_and_Administration_Guide-en-US.pdf | Bin 0 -> 9515328 bytes
..._Deployment_and_Administration_Guide-en-US.epub | Bin 0 -> 17460926 bytes
.../Common_Content/css/common.css | 1528 +++
.../Common_Content/css/default.css | 3 +
.../Common_Content/css/lang.css | 2 +
.../Common_Content/css/menu.css | 48 +
.../Common_Content/css/overrides.css | 55 +
.../Common_Content/css/pdf.css | 138 +
.../Common_Content/css/print.css | 16 +
.../Common_Content/images/1.png | Bin 0 -> 690 bytes
.../Common_Content/images/1.svg | 22 +
.../Common_Content/images/10.png | Bin 0 -> 982 bytes
.../Common_Content/images/10.svg | 22 +
.../Common_Content/images/11.png | Bin 0 -> 806 bytes
.../Common_Content/images/11.svg | 22 +
.../Common_Content/images/12.png | Bin 0 -> 953 bytes
.../Common_Content/images/12.svg | 22 +
.../Common_Content/images/13.png | Bin 0 -> 1015 bytes
.../Common_Content/images/13.svg | 22 +
.../Common_Content/images/14.png | Bin 0 -> 933 bytes
.../Common_Content/images/14.svg | 22 +
.../Common_Content/images/15.png | Bin 0 -> 996 bytes
.../Common_Content/images/15.svg | 22 +
.../Common_Content/images/16.png | Bin 0 -> 1030 bytes
.../Common_Content/images/16.svg | 22 +
.../Common_Content/images/17.png | Bin 0 -> 870 bytes
.../Common_Content/images/17.svg | 22 +
.../Common_Content/images/18.png | Bin 0 -> 1001 bytes
.../Common_Content/images/18.svg | 22 +
.../Common_Content/images/19.png | Bin 0 -> 1013 bytes
.../Common_Content/images/19.svg | 22 +
.../Common_Content/images/2.png | Bin 0 -> 808 bytes
.../Common_Content/images/2.svg | 22 +
.../Common_Content/images/20.png | Bin 0 -> 1121 bytes
.../Common_Content/images/20.svg | 22 +
.../Common_Content/images/21.png | Bin 0 -> 981 bytes
.../Common_Content/images/21.svg | 22 +
.../Common_Content/images/22.png | Bin 0 -> 1057 bytes
.../Common_Content/images/22.svg | 22 +
.../Common_Content/images/23.png | Bin 0 -> 1120 bytes
.../Common_Content/images/23.svg | 22 +
.../Common_Content/images/24.png | Bin 0 -> 1083 bytes
.../Common_Content/images/24.svg | 31 +
.../Common_Content/images/25.png | Bin 0 -> 1182 bytes
.../Common_Content/images/25.svg | 31 +
.../Common_Content/images/26.png | Bin 0 -> 1215 bytes
.../Common_Content/images/26.svg | 31 +
.../Common_Content/images/27.png | Bin 0 -> 1086 bytes
.../Common_Content/images/27.svg | 31 +
.../Common_Content/images/28.png | Bin 0 -> 1251 bytes
.../Common_Content/images/28.svg | 31 +
.../Common_Content/images/29.png | Bin 0 -> 1212 bytes
.../Common_Content/images/29.svg | 31 +
.../Common_Content/images/3.png | Bin 0 -> 868 bytes
.../Common_Content/images/3.svg | 22 +
.../Common_Content/images/30.png | Bin 0 -> 1267 bytes
.../Common_Content/images/30.svg | 31 +
.../Common_Content/images/31.png | Bin 0 -> 1083 bytes
.../Common_Content/images/31.svg | 31 +
.../Common_Content/images/32.png | Bin 0 -> 1244 bytes
.../Common_Content/images/32.svg | 31 +
.../Common_Content/images/33.png | Bin 0 -> 1279 bytes
.../Common_Content/images/33.svg | 31 +
.../Common_Content/images/34.png | Bin 0 -> 1178 bytes
.../Common_Content/images/34.svg | 31 +
.../Common_Content/images/35.png | Bin 0 -> 1235 bytes
.../Common_Content/images/35.svg | 31 +
.../Common_Content/images/36.png | Bin 0 -> 1286 bytes
.../Common_Content/images/36.svg | 31 +
.../Common_Content/images/37.png | Bin 0 -> 1155 bytes
.../Common_Content/images/37.svg | 31 +
.../Common_Content/images/38.png | Bin 0 -> 1325 bytes
.../Common_Content/images/38.svg | 31 +
.../Common_Content/images/39.png | Bin 0 -> 1300 bytes
.../Common_Content/images/39.svg | 31 +
.../Common_Content/images/4.png | Bin 0 -> 794 bytes
.../Common_Content/images/4.svg | 22 +
.../Common_Content/images/40.png | Bin 0 -> 1145 bytes
.../Common_Content/images/40.svg | 31 +
.../Common_Content/images/5.png | Bin 0 -> 853 bytes
.../Common_Content/images/5.svg | 22 +
.../Common_Content/images/6.png | Bin 0 -> 865 bytes
.../Common_Content/images/6.svg | 22 +
.../Common_Content/images/7.png | Bin 0 -> 742 bytes
.../Common_Content/images/7.svg | 22 +
.../Common_Content/images/8.png | Bin 0 -> 862 bytes
.../Common_Content/images/8.svg | 22 +
.../Common_Content/images/9.png | Bin 0 -> 860 bytes
.../Common_Content/images/9.svg | 22 +
.../Common_Content/images/bkgrnd_greydots.png | Bin 0 -> 157 bytes
.../Common_Content/images/bullet_arrowblue.png | Bin 0 -> 177 bytes
.../Common_Content/images/documentation.png | Bin 0 -> 623 bytes
.../Common_Content/images/dot.png | Bin 0 -> 98 bytes
.../Common_Content/images/dot2.png | Bin 0 -> 98 bytes
.../Common_Content/images/green.png | Bin 0 -> 176 bytes
.../Common_Content/images/h1-bg.png | Bin 0 -> 565 bytes
.../Common_Content/images/image_left.png | Bin 0 -> 1114 bytes
.../Common_Content/images/image_right.png | Bin 0 -> 4092 bytes
.../Common_Content/images/important.png | Bin 0 -> 2080 bytes
.../Common_Content/images/important.svg | 106 +
.../Common_Content/images/logo.png | Bin 0 -> 1114 bytes
.../Common_Content/images/note.png | Bin 0 -> 1241 bytes
.../Common_Content/images/note.svg | 111 +
.../Common_Content/images/red.png | Bin 0 -> 163 bytes
.../Common_Content/images/redhat-logo.svg | 94 +
.../Common_Content/images/rhlogo.png | Bin 0 -> 2278 bytes
.../Common_Content/images/shade.png | Bin 0 -> 101 bytes
.../Common_Content/images/shine.png | Bin 0 -> 146 bytes
.../Common_Content/images/stock-go-back.png | Bin 0 -> 828 bytes
.../Common_Content/images/stock-go-forward.png | Bin 0 -> 828 bytes
.../Common_Content/images/stock-go-up.png | Bin 0 -> 760 bytes
.../Common_Content/images/stock-home.png | Bin 0 -> 808 bytes
.../Common_Content/images/title_logo.png | Bin 0 -> 13399 bytes
.../Common_Content/images/title_logo.svg | 109 +
.../Common_Content/images/warning.png | Bin 0 -> 1340 bytes
.../Common_Content/images/warning.svg | 89 +
.../Common_Content/images/watermark-draft.png | Bin 0 -> 25365 bytes
.../Common_Content/images/yellow.png | Bin 0 -> 175 bytes
.../images/1-7RHEL_local_install.png | Bin 0 -> 13795 bytes
.../images/1-Iso_general.png | Bin 0 -> 66439 bytes
.../images/1-files_PV-win.png | Bin 0 -> 58708 bytes
.../images/10-7RHEL_local_install.png | Bin 0 -> 40128 bytes
.../images/10-w7x86driverchosen.png | Bin 0 -> 70168 bytes
.../images/10-w7x86driverchosen_win7.png | Bin 0 -> 19979 bytes
.../images/10-w7x86driverstart.png | Bin 0 -> 67481 bytes
.../images/10-w7x86driverstart_win7.png | Bin 0 -> 20672 bytes
.../images/11-7RHEL_local_install.png | Bin 0 -> 42123 bytes
.../images/12-DriverInstalled.png | Bin 0 -> 42765 bytes
.../images/14-StartInstallSerial.png | Bin 0 -> 89324 bytes
.../images/2-7RHEL_local_install.png | Bin 0 -> 31149 bytes
.../images/2-Iso_Balloon_Os.png | Bin 0 -> 58380 bytes
.../images/3-7RHEL_local_install.png | Bin 0 -> 26452 bytes
.../images/3-Iso_Balloon_Os_arch.png | Bin 0 -> 58272 bytes
.../images/3_PCI_Device.png | Bin 0 -> 179475 bytes
.../images/4-7RHEL_local_install.png | Bin 0 -> 29310 bytes
.../images/4-Iso_balloon_files.png | Bin 0 -> 69579 bytes
.../images/4_finish.png | Bin 0 -> 24479 bytes
.../images/5-7RHEL_local_install.png | Bin 0 -> 29133 bytes
.../images/6-7RHEL_local_install.png | Bin 0 -> 19657 bytes
.../images/6.4-2.png | Bin 0 -> 24447 bytes
.../images/6.4-3.png | Bin 0 -> 25646 bytes
.../images/6.4-4.png | Bin 0 -> 35108 bytes
.../images/7-7RHEL_local_install.png | Bin 0 -> 24996 bytes
.../images/8-7RHEL_local_install.png | Bin 0 -> 21005 bytes
.../images/8-BrowseForDriver.png | Bin 0 -> 76374 bytes
.../images/8-BrowseForDriver_win7.png | Bin 0 -> 20271 bytes
.../images/9-7RHEL_local_install.png | Bin 0 -> 34205 bytes
.../images/9-BrowseToDirectory.png | Bin 0 -> 17326 bytes
.../images/9-BrowseToDirectory_win7.png | Bin 0 -> 15823 bytes
.../images/COPYME.png | Bin 0 -> 60798 bytes
.../images/ChangeType.png | Bin 0 -> 119508 bytes
.../images/Connection_Details.png | Bin 0 -> 17102 bytes
.../images/Create-1.png | Bin 0 -> 68190 bytes
.../images/DevManagerStart.png | Bin 0 -> 115214 bytes
.../images/DevManagerStart_win7.png | Bin 0 -> 51206 bytes
.../images/DriverInstall-Expand.png | Bin 0 -> 111352 bytes
.../images/DriverInstall-OpenWizard.png | Bin 0 -> 10335 bytes
.../images/DriverInstall-OpenWizard_win7.png | Bin 0 -> 9493 bytes
.../images/DriverInstallExpand_win7.png | Bin 0 -> 92965 bytes
.../images/DuringInstallation.png | Bin 0 -> 25758 bytes
.../images/Iso_Balloon_files.png | Bin 0 -> 64585 bytes
.../images/Iso_general.png | Bin 0 -> 60798 bytes
.../images/ManageStart.png | Bin 0 -> 225210 bytes
.../images/Network_hardware.png | Bin 0 -> 52560 bytes
.../images/Network_hardware_virtio.png | Bin 0 -> 51598 bytes
.../images/PCIremoval.png | Bin 0 -> 55777 bytes
.../images/PXEguest_5of5.png | Bin 0 -> 46145 bytes
.../images/RHEL6_cpu+ram.png | Bin 0 -> 26155 bytes
.../images/RHEL6_finish_advanced.png | Bin 0 -> 49113 bytes
.../images/RHEL6_storage.png | Bin 0 -> 36029 bytes
.../images/RHEL6_storage_local.png | Bin 0 -> 33867 bytes
.../images/RHEL6_virt-manager_new_1.png | Bin 0 -> 38313 bytes
.../images/RHEL6local_choose.png | Bin 0 -> 52384 bytes
.../images/RHEL6local_selectedISO.png | Bin 0 -> 36710 bytes
.../images/RHELKVMpackages-2.png | Bin 0 -> 77122 bytes
.../images/RHELKVMpackages.png | Bin 0 -> 79030 bytes
.../images/RHELcustomize14.png | Bin 0 -> 104378 bytes
.../images/RHELcustomize15.png | Bin 0 -> 69240 bytes
.../images/RHELkvmSelect.png | Bin 0 -> 78106 bytes
.../images/SR-IOV_implementation.png | Bin 0 -> 75739 bytes
.../images/Screenshot-VIrt-Manager-fig31pt18.png | Bin 0 -> 27887 bytes
.../images/Screenshot-Virt-Manager-fig31pt1.png | Bin 0 -> 23228 bytes
.../images/Screenshot-Virt-Manager-fig31pt11.png | Bin 0 -> 27810 bytes
.../images/Screenshot-Virt-Manager-fig31pt13.png | Bin 0 -> 62072 bytes
.../images/Screenshot-Virt-Manager-fig31pt14.png | Bin 0 -> 80532 bytes
.../images/Screenshot-Virt-Manager-fig31pt15.png | Bin 0 -> 52668 bytes
.../images/Screenshot-Virt-Manager-fig31pt16.png | Bin 0 -> 72095 bytes
.../images/Screenshot-Virt-Manager-fig31pt17.png | Bin 0 -> 50464 bytes
.../images/Screenshot-Virt-Manager-fig31pt19.png | Bin 0 -> 22060 bytes
.../images/Screenshot-Virt-Manager-fig31pt2.png | Bin 0 -> 25861 bytes
.../images/Screenshot-Virt-Manager-fig31pt24.png | Bin 0 -> 29361 bytes
.../images/Screenshot-Virt-Manager-fig31pt24a.png | Bin 0 -> 29080 bytes
.../images/Screenshot-Virt-Manager-fig31pt27.png | Bin 0 -> 22828 bytes
.../images/Screenshot-Virt-Manager-fig31pt28.png | Bin 0 -> 33316 bytes
.../images/Screenshot-Virt-Manager-fig31pt29.png | Bin 0 -> 24925 bytes
.../images/Screenshot-Virt-Manager-fig31pt3.png | Bin 0 -> 69957 bytes
.../images/Screenshot-Virt-Manager-fig31pt4.png | Bin 0 -> 68968 bytes
.../images/Screenshot-Virt-Manager-fig31pt5.png | Bin 0 -> 548594 bytes
.../images/Screenshot-Virt-Manager-fig31pt6.png | Bin 0 -> 22883 bytes
.../images/Screenshot-Virt-Manager-fig31pt7.png | Bin 0 -> 25774 bytes
.../images/Screenshot-Virt-Manager_fig31pt25.png | Bin 0 -> 25748 bytes
.../images/Screenshot-Virt-Manager_fig31pt25a.png | Bin 0 -> 23533 bytes
.../images/Screenshot-Virt-Manager_fig31pt26.png | Bin 0 -> 30226 bytes
.../images/Screenshot-admin-18pt7-pic1.png | Bin 0 -> 38526 bytes
.../images/Screenshot-admin-18pt7-pic10.png | Bin 0 -> 48685 bytes
.../images/Screenshot-admin-18pt7-pic11.png | Bin 0 -> 60824 bytes
.../images/Screenshot-admin-18pt7-pic2.png | Bin 0 -> 38421 bytes
.../images/Screenshot-admin-18pt7-pic3.png | Bin 0 -> 19836 bytes
.../images/Screenshot-admin-18pt7-pic4.png | Bin 0 -> 38995 bytes
.../images/Screenshot-admin-18pt7-pic5.png | Bin 0 -> 33897 bytes
.../images/Screenshot-admin-18pt7-pic6.png | Bin 0 -> 29663 bytes
.../images/Screenshot-admin-18pt7-pic7.png | Bin 0 -> 32043 bytes
.../images/Screenshot-admin-18pt7-pic8.png | Bin 0 -> 46321 bytes
.../images/Screenshot-admin-18pt7-pic9.png | Bin 0 -> 70468 bytes
.../images/Screenshot-pic1-virt-mgr-guests.png | Bin 0 -> 22245 bytes
.../Screenshot-pic2-add-connection-pull-down.png | Bin 0 -> 22169 bytes
.../images/Screenshot-pic3-Add Connection.png | Bin 0 -> 18516 bytes
.../images/Screenshot-pic3-Add-Connection.png | Bin 0 -> 21410 bytes
.../images/Screenshot-pic4-OpenSSH.png | Bin 0 -> 11280 bytes
.../Screenshot-pic5-guest-select-migrate.png | Bin 0 -> 34896 bytes
.../Screenshot-pic6-final-before-migrate.png | Bin 0 -> 36898 bytes
.../Screenshot-pic7-Migrating-guest1-rhel6-64.png | Bin 0 -> 14788 bytes
.../images/Screenshot-pic8-migrated.png | Bin 0 -> 30438 bytes
.../images/Screenshot-rhel6pv-virt-method.png | Bin 0 -> 47301 bytes
.../images/Screenshot-sevenpt1-pic1.png | Bin 0 -> 23889 bytes
.../images/Screenshot-sevenpt1-pic2.png | Bin 0 -> 66922 bytes
.../images/Screenshot-sevenpt1-pic4.png | Bin 0 -> 62475 bytes
.../images/Screenshot-sevenpt1-pic5.png | Bin 0 -> 69613 bytes
.../images/Screenshot-sevenpt1-pic6.png | Bin 0 -> 46457 bytes
.../images/Screenshot-sevenpt1-pic7-managed.png | Bin 0 -> 36200 bytes
.../images/Screenshot-sevenpt1-pic7.png | Bin 0 -> 68403 bytes
.../images/Screenshot-sevenpt1-pic8-create-lvm.png | Bin 0 -> 42013 bytes
...Screenshot-sevenpt1-pic8-new-storage-volume.png | Bin 0 -> 76048 bytes
.../Screenshot-sevenpt1-pic9-local-storage.png | Bin 0 -> 100054 bytes
.../Screenshot-sevenpt1-pic9-storage-volume.png | Bin 0 -> 87492 bytes
.../images/Screenshot-sevenpt2-pic2.png | Bin 0 -> 82712 bytes
.../images/Screenshot-sevenpt2-pic3.png | Bin 0 -> 68632 bytes
.../images/Screenshot-sevenpt3-pic2.png | Bin 0 -> 68105 bytes
.../images/Screenshot-sevenpt3-pic3.png | Bin 0 -> 40893 bytes
.../images/Screenshot-sevenpt3-pic4.png | Bin 0 -> 41498 bytes
.../images/Screenshot-sevenpt3-pic5.png | Bin 0 -> 68403 bytes
.../images/Screenshot-sevenpt3-pic6.png | Bin 0 -> 83457 bytes
.../images/Screenshot-virtlab22-Host-Details.png | Bin 0 -> 49786 bytes
.../Section_11_pt_2_pt_2_step3_substep_c.png | Bin 0 -> 70469 bytes
.../Section_11_pt_2_pt_2_step3_substep_d.png | Bin 0 -> 67795 bytes
.../images/Select_storage_pools.png | Bin 0 -> 39490 bytes
.../images/StartDevManagerInVM.png | Bin 0 -> 330244 bytes
.../images/StartDevManagerInVM_win7.png | Bin 0 -> 223816 bytes
.../images/StartInstallingBalloon-1.png | Bin 0 -> 152903 bytes
.../images/StartInstallingBalloon-1_win7.png | Bin 0 -> 72036 bytes
.../images/Virt-Manager-Add-Connection.png | Bin 0 -> 21414 bytes
.../images/Virtual_Machine_Name-guest-install.png | Bin 0 -> 40239 bytes
...ual_Machine_Name-guest-install_STEP2-cpumem.png | Bin 0 -> 28224 bytes
...ual_Machine_Name-guest-install_STEP2-import.png | Bin 0 -> 29326 bytes
...tual_Machine_Name-guest-install_STEP2-local.png | Bin 0 -> 34657 bytes
.../Virtual_Machine_Name-guest-install_STEP4.png | Bin 0 -> 36303 bytes
...ual_Machine_Name-guest-install_STEP5-finish.png | Bin 0 -> 48968 bytes
...l_Machine_Name-guest-install_final-hardware.png | Bin 0 -> 76768 bytes
.../images/XP-driver-capture.png | Bin 0 -> 11814 bytes
.../images/XP-driver-select-driver.png | Bin 0 -> 240846 bytes
.../images/XP-driver-select2.png | Bin 0 -> 51574 bytes
.../images/after_virtualization.png | Bin 0 -> 39557 bytes
.../images/before_virtualization.png | Bin 0 -> 38000 bytes
.../images/block_finish-virtio-win.png | Bin 0 -> 61150 bytes
.../images/block_start-virtio-win.png | Bin 0 -> 24334 bytes
.../images/bridgePXE.png | Bin 0 -> 40131 bytes
.../images/bridgefinish.png | Bin 0 -> 49050 bytes
.../images/bz734652-step3.png | Bin 0 -> 302675 bytes
.../images/done-KVM_PV.png | Bin 0 -> 34673 bytes
.../images/exception-virtio-win.png | Bin 0 -> 23524 bytes
.../images/icon.svg | 19 +
.../images/ide-to-virtio-add-hardware.png | Bin 0 -> 129326 bytes
.../images/ide-to-virtio-remove-dev.png | Bin 0 -> 12609 bytes
.../images/ide-to-virtio1.png | Bin 0 -> 93665 bytes
.../images/ide-to-virtio1replacement.png | Bin 0 -> 81885 bytes
.../images/ide-to-virtio2.png | Bin 0 -> 97191 bytes
.../images/ide-to-virtio3.png | Bin 0 -> 94899 bytes
.../images/ide-to-virtio4.png | Bin 0 -> 107743 bytes
.../images/ide-to-virtio5.png | Bin 0 -> 108511 bytes
.../images/ide-to-virtio5replacement.png | Bin 0 -> 140191 bytes
.../images/ide-to-virtio6.png | Bin 0 -> 106978 bytes
.../images/ide-to-virtio6replacement.png | Bin 0 -> 17285 bytes
.../images/ide-to-virtio7.png | Bin 0 -> 95349 bytes
.../images/ide-to-virtio7replacement.png | Bin 0 -> 130528 bytes
.../images/infotabbutton.png | Bin 0 -> 1982 bytes
.../images/installmedia-blank.png | Bin 0 -> 28277 bytes
.../images/installmedia-select-os1.png | Bin 0 -> 31898 bytes
.../images/installmedia-select-volume.png | Bin 0 -> 26046 bytes
.../images/network_finish-virtio-win.png | Bin 0 -> 131791 bytes
.../images/network_performance-virtio-win.png | Bin 0 -> 21864 bytes
.../images/network_start-virtio-win.png | Bin 0 -> 63822 bytes
.../paravirt-0-click-configure-before-install.png | Bin 0 -> 32637 bytes
...avirt-0-click-configure-before-install_win7.png | Bin 0 -> 28916 bytes
.../images/paravirt-1-click-add-hardware.png | Bin 0 -> 2281 bytes
.../paravirt-10-select-custom-installation.png | Bin 0 -> 33229 bytes
.../images/paravirt-11-load-driver.png | Bin 0 -> 1659 bytes
.../images/paravirt-12-insert-disk.png | Bin 0 -> 19618 bytes
.../images/paravirt-13-select-driver-arch.png | Bin 0 -> 12390 bytes
.../images/paravirt-14-view-drivers-loaded.png | Bin 0 -> 11244 bytes
.../images/paravirt-2-disk-type.png | Bin 0 -> 4464 bytes
.../images/paravirt-2a-select-existing-storage.png | Bin 0 -> 5537 bytes
.../images/paravirt-2b-select-browse-local.png | Bin 0 -> 2319 bytes
.../images/paravirt-2c-virtio-win-vfd.png | Bin 0 -> 7385 bytes
.../images/paravirt-2z-select-storage.png | Bin 0 -> 67646 bytes
.../images/paravirt-3-floppy-advanced-options.png | Bin 0 -> 8673 bytes
.../images/paravirt-4-after-adding-virtio-disk.png | Bin 0 -> 66487 bytes
.../images/paravirt-5-begin-installation.png | Bin 0 -> 4211 bytes
.../images/paravirt-6-windows-install.png | Bin 0 -> 6419 bytes
.../paravirt-6a-select-installation-type.png | Bin 0 -> 28819 bytes
.../images/paravirt-8-agree-to-license-terms.png | Bin 0 -> 1138 bytes
.../images/paravirt-adding-virtio-disk.png | Bin 0 -> 65258 bytes
.../images/paravirt-click-begin-installation.png | Bin 0 -> 4230 bytes
.../images/paravirt-confirm-floppy-settings.png | Bin 0 -> 56639 bytes
.../images/paravirt-confirm-settings.png | Bin 0 -> 56545 bytes
.../images/paravirt-confirm-virtio-disk-in-use.png | Bin 0 -> 16477 bytes
.../images/paravirt-device-type-virtio-finish.png | Bin 0 -> 65699 bytes
.../images/paravirt-device-type-virtiodisk.png | Bin 0 -> 4683 bytes
.../images/paravirt-remove-disk1-2.png | Bin 0 -> 1493 bytes
.../images/paravirt-remove-disk1.png | Bin 0 -> 70993 bytes
.../images/paravirt-review-virtio-settings.png | Bin 0 -> 66335 bytes
.../images/paravirt-select-device-type-floppy.png | Bin 0 -> 4814 bytes
.../images/paravirt-storage-win7.png | Bin 0 -> 63115 bytes
.../images/pci_host_device.png | Bin 0 -> 129981 bytes
.../images/rhel5_rhel6pv_create_vm.png | Bin 0 -> 29497 bytes
.../images/rhel5_rhel6pv_finish.png | Bin 0 -> 49265 bytes
.../images/rhel5_rhel6pv_finish_3.png | Bin 0 -> 66701 bytes
.../images/rhel5_rhel6pv_install_method.png | Bin 0 -> 75364 bytes
.../images/rhel5_rhel6pv_install_source_2.png | Bin 0 -> 63977 bytes
.../images/rhel5_rhel6pv_mem_n_cpu_alloc.png | Bin 0 -> 90621 bytes
.../images/rhel5_rhel6pv_network.png | Bin 0 -> 70040 bytes
.../images/rhel5_rhel6pv_storage.png | Bin 0 -> 87583 bytes
.../images/rhel5_rhel6pv_virt_install.png | Bin 0 -> 27712 bytes
.../rhel6-Screenshot-step2-existing-disk-image.png | Bin 0 -> 36736 bytes
.../rhel6_Screenshot-guest1-rhel5-64-final.png | Bin 0 -> 64451 bytes
.../images/rhel6_Screenshot-step1.png | Bin 0 -> 39198 bytes
.../images/rhel6_Screenshot-step2.png | Bin 0 -> 35789 bytes
.../images/rhel6_Screenshot-step3.png | Bin 0 -> 26469 bytes
.../images/rhel6_Screenshot-step4.png | Bin 0 -> 34920 bytes
.../images/rhel6_Screenshot-step5.png | Bin 0 -> 52176 bytes
.../images/rhel6_virt_manager.png | Bin 0 -> 11628 bytes
.../images/selinux_uuid_block.png | Bin 0 -> 42886 bytes
.../images/shutter-9-3_win7-1.png | Bin 0 -> 53637 bytes
.../images/shutter-9-3_win7-2.png | Bin 0 -> 53447 bytes
.../images/shutter-9-3_win7-3.png | Bin 0 -> 60345 bytes
.../images/shutter-9-3_win7-4.png | Bin 0 -> 62326 bytes
.../images/step-1-1.png | Bin 0 -> 17359 bytes
.../images/step1-1.png | Bin 0 -> 17467 bytes
.../images/step1-2.png | Bin 0 -> 14463 bytes
.../images/step2-1.png | Bin 0 -> 58452 bytes
.../images/step2-2.png | Bin 0 -> 25501 bytes
.../images/step2-3.png | Bin 0 -> 36016 bytes
.../images/step2-4.png | Bin 0 -> 47641 bytes
.../images/step3-1.png | Bin 0 -> 40153 bytes
.../images/step4-1.png | Bin 0 -> 43876 bytes
.../images/step4-2.png | Bin 0 -> 17810 bytes
.../images/step5-1.png | Bin 0 -> 45055 bytes
.../images/step5-2.png | Bin 0 -> 32497 bytes
.../images/step5-3.png | Bin 0 -> 32720 bytes
.../images/type_assigned-KVM_PV.png | Bin 0 -> 61786 bytes
.../images/type_assigned-KVM_PV_new.png | Bin 0 -> 63191 bytes
.../images/v2v-add_storagepool.png | Bin 0 -> 23510 bytes
.../images/v2v-select_host.png | Bin 0 -> 12194 bytes
.../images/v2v-storage_tab.png | Bin 0 -> 44510 bytes
.../images/virt-manager-enable-disk-io.png | Bin 0 -> 18245 bytes
.../images/virt-manager-enable-networkio.png | Bin 0 -> 18218 bytes
.../images/virt-manager_add_nfs_step1.png | Bin 0 -> 27760 bytes
.../images/virt-manager_add_nfs_step2.png | Bin 0 -> 35312 bytes
.../images/virt-manager_add_storage_pool1.png | Bin 0 -> 27075 bytes
.../images/virt-manager_add_storage_pool2.png | Bin 0 -> 37625 bytes
.../images/virt-manager_hardware.png | Bin 0 -> 125992 bytes
.../images/virt-manager_hardware_wizard1.png | Bin 0 -> 36804 bytes
.../images/virt-manager_home.png | Bin 0 -> 32772 bytes
.../images/virt-manager_host_details_storage.png | Bin 0 -> 53958 bytes
.../images/virt-manager_main.png | Bin 0 -> 21512 bytes
.../images/virt-manager_newicon.png | Bin 0 -> 1475 bytes
.../images/virt-manager_select_host.png | Bin 0 -> 26025 bytes
..._storage_pools_add_dir_step_1_name_and_type.png | Bin 0 -> 26371 bytes
...er_storage_pools_add_dir_step_2_target_path.png | Bin 0 -> 33949 bytes
...manager_storage_pools_add_dir_step_3_result.png | Bin 0 -> 45724 bytes
...r_storage_pools_add_fs_step_1_name_and_type.png | Bin 0 -> 26216 bytes
...torage_pools_add_fs_step_2_paths_and_format.png | Bin 0 -> 32029 bytes
...-manager_storage_pools_add_fs_step_3_result.png | Bin 0 -> 46654 bytes
..._storage_pools_add_lvm_step_1_name_and_type.png | Bin 0 -> 26188 bytes
...torage_pools_add_lvm_step_2a_paths_and_pool.png | Bin 0 -> 32081 bytes
...torage_pools_add_lvm_step_2b_format_warning.png | Bin 0 -> 10141 bytes
...manager_storage_pools_add_lvm_step_3_result.png | Bin 0 -> 104017 bytes
.../images/virt-manager_virtualization_method.png | Bin 0 -> 71057 bytes
.../images/virtio-disk2.png | Bin 0 -> 47633 bytes
.../images/virtio-network-finish3.png | Bin 0 -> 31957 bytes
.../images/virtio-network-step1.png | Bin 0 -> 36985 bytes
.../images/virtio-network-step2.png | Bin 0 -> 40243 bytes
.../images/virtio-storage-finish3.png | Bin 0 -> 34181 bytes
.../images/virtio-storage-step1-new.png | Bin 0 -> 62145 bytes
.../images/virtio-storage-step1.png | Bin 0 -> 37033 bytes
.../images/virtio-storage-step2-new.png | Bin 0 -> 64041 bytes
.../images/virtio-storage-step2.png | Bin 0 -> 61079 bytes
.../images/virtio0-customize.png | Bin 0 -> 58502 bytes
.../images/virtio3-finished.png | Bin 0 -> 27470 bytes
.../images/virtual_machine_overview.png | Bin 0 -> 73963 bytes
.../images/vm-add_hardware1.png | Bin 0 -> 79211 bytes
.../images/vm_add_hardware.png | Bin 0 -> 6306 bytes
.../images/vm_add_hardware_new.png | Bin 0 -> 2266 bytes
.../images/vm_info_button.png | Bin 0 -> 4964 bytes
.../images/vm_info_button_new.png | Bin 0 -> 3557 bytes
.../images/vmm_vnet_create1.png | Bin 0 -> 38424 bytes
.../images/vmm_vnet_create2.png | Bin 0 -> 19689 bytes
.../images/vmm_vnet_create3_ipv4addspace.png | Bin 0 -> 38805 bytes
.../images/vmm_vnet_create4_dhcprange.png | Bin 0 -> 33089 bytes
.../images/vmm_vnet_create5_connectphysnet.png | Bin 0 -> 29901 bytes
.../images/vmm_vnet_create6_finish.png | Bin 0 -> 31511 bytes
.../images/vmm_vnet_create7_maintab.png | Bin 0 -> 43333 bytes
.../images/vmm_vnet_maintab.png | Bin 0 -> 41593 bytes
.../images/vmm_vnet_menuselect.png | Bin 0 -> 20814 bytes
.../images/vn-01-switch.png | Bin 0 -> 10406 bytes
.../images/vn-02-switchandtwoguests.png | Bin 0 -> 42987 bytes
.../images/vn-03-hostwithswitch.png | Bin 0 -> 25369 bytes
.../images/vn-04-hostwithnatswitch.png | Bin 0 -> 135903 bytes
.../images/vn-05-switchwithdnsmasq.jpg | Bin 0 -> 216332 bytes
.../images/vn-06-routed-switch.png | Bin 0 -> 139243 bytes
.../images/vn-07-isolated-switch.png | Bin 0 -> 131466 bytes
.../images/vn-08-network-overview.png | Bin 0 -> 364520 bytes
.../images/vn-09-routed-mode-DMZ.png | Bin 0 -> 635464 bytes
.../images/vn-10-routed-mode-datacenter.png | Bin 0 -> 415490 bytes
.../images/vn-11-router-mode-mac-restricted.png | Bin 0 -> 398974 bytes
.../images/vn-12-network-tab-default.png | Bin 0 -> 39835 bytes
.../images/w7x86driverchosen.png | Bin 0 -> 22359 bytes
.../images/win2003_select_hal.png | Bin 0 -> 8979 bytes
...win7paravirt-click-configure-before-install.png | Bin 0 -> 28908 bytes
.../index.html |12693 +++++++++++++++++++
.../App_Bridge_Device.html | 46 +
.../App_DHCP_Response_Checksums.html | 18 +
.../App_Domain_Console.html | 29 +
.../App_Domain_Monitor_Socket.html | 33 +
.../App_Domain_Not_Booting.html | 86 +
.../App_Domain_Processor.html | 20 +
.../App_Generic_Ethernet.html | 45 +
.../App_Hypervisor_Connection_Fail.html | 26 +
.../App_Macvtap.html | 44 +
.../App_Migration_Address.html | 34 +
.../App_Migration_Disk_Image.html | 34 +
.../App_No_Guest_Machines.html | 44 +
.../App_PXE_Guest_Boot_Fail.html | 71 +
.../App_TCP_Ports.html | 33 +
.../App_Virt_Net_Not_Starting.html | 40 +
.../App_XML_Errors.html | 28 +
.../Common_Content/css/common.css | 1528 +++
.../Common_Content/css/default.css | 3 +
.../Common_Content/css/lang.css | 2 +
.../Common_Content/css/menu.css | 48 +
.../Common_Content/css/overrides.css | 55 +
.../Common_Content/css/pdf.css | 138 +
.../Common_Content/css/print.css | 16 +
.../Common_Content/images/1.png | Bin 0 -> 690 bytes
.../Common_Content/images/1.svg | 22 +
.../Common_Content/images/10.png | Bin 0 -> 982 bytes
.../Common_Content/images/10.svg | 22 +
.../Common_Content/images/11.png | Bin 0 -> 806 bytes
.../Common_Content/images/11.svg | 22 +
.../Common_Content/images/12.png | Bin 0 -> 953 bytes
.../Common_Content/images/12.svg | 22 +
.../Common_Content/images/13.png | Bin 0 -> 1015 bytes
.../Common_Content/images/13.svg | 22 +
.../Common_Content/images/14.png | Bin 0 -> 933 bytes
.../Common_Content/images/14.svg | 22 +
.../Common_Content/images/15.png | Bin 0 -> 996 bytes
.../Common_Content/images/15.svg | 22 +
.../Common_Content/images/16.png | Bin 0 -> 1030 bytes
.../Common_Content/images/16.svg | 22 +
.../Common_Content/images/17.png | Bin 0 -> 870 bytes
.../Common_Content/images/17.svg | 22 +
.../Common_Content/images/18.png | Bin 0 -> 1001 bytes
.../Common_Content/images/18.svg | 22 +
.../Common_Content/images/19.png | Bin 0 -> 1013 bytes
.../Common_Content/images/19.svg | 22 +
.../Common_Content/images/2.png | Bin 0 -> 808 bytes
.../Common_Content/images/2.svg | 22 +
.../Common_Content/images/20.png | Bin 0 -> 1121 bytes
.../Common_Content/images/20.svg | 22 +
.../Common_Content/images/21.png | Bin 0 -> 981 bytes
.../Common_Content/images/21.svg | 22 +
.../Common_Content/images/22.png | Bin 0 -> 1057 bytes
.../Common_Content/images/22.svg | 22 +
.../Common_Content/images/23.png | Bin 0 -> 1120 bytes
.../Common_Content/images/23.svg | 22 +
.../Common_Content/images/24.png | Bin 0 -> 1083 bytes
.../Common_Content/images/24.svg | 31 +
.../Common_Content/images/25.png | Bin 0 -> 1182 bytes
.../Common_Content/images/25.svg | 31 +
.../Common_Content/images/26.png | Bin 0 -> 1215 bytes
.../Common_Content/images/26.svg | 31 +
.../Common_Content/images/27.png | Bin 0 -> 1086 bytes
.../Common_Content/images/27.svg | 31 +
.../Common_Content/images/28.png | Bin 0 -> 1251 bytes
.../Common_Content/images/28.svg | 31 +
.../Common_Content/images/29.png | Bin 0 -> 1212 bytes
.../Common_Content/images/29.svg | 31 +
.../Common_Content/images/3.png | Bin 0 -> 868 bytes
.../Common_Content/images/3.svg | 22 +
.../Common_Content/images/30.png | Bin 0 -> 1267 bytes
.../Common_Content/images/30.svg | 31 +
.../Common_Content/images/31.png | Bin 0 -> 1083 bytes
.../Common_Content/images/31.svg | 31 +
.../Common_Content/images/32.png | Bin 0 -> 1244 bytes
.../Common_Content/images/32.svg | 31 +
.../Common_Content/images/33.png | Bin 0 -> 1279 bytes
.../Common_Content/images/33.svg | 31 +
.../Common_Content/images/34.png | Bin 0 -> 1178 bytes
.../Common_Content/images/34.svg | 31 +
.../Common_Content/images/35.png | Bin 0 -> 1235 bytes
.../Common_Content/images/35.svg | 31 +
.../Common_Content/images/36.png | Bin 0 -> 1286 bytes
.../Common_Content/images/36.svg | 31 +
.../Common_Content/images/37.png | Bin 0 -> 1155 bytes
.../Common_Content/images/37.svg | 31 +
.../Common_Content/images/38.png | Bin 0 -> 1325 bytes
.../Common_Content/images/38.svg | 31 +
.../Common_Content/images/39.png | Bin 0 -> 1300 bytes
.../Common_Content/images/39.svg | 31 +
.../Common_Content/images/4.png | Bin 0 -> 794 bytes
.../Common_Content/images/4.svg | 22 +
.../Common_Content/images/40.png | Bin 0 -> 1145 bytes
.../Common_Content/images/40.svg | 31 +
.../Common_Content/images/5.png | Bin 0 -> 853 bytes
.../Common_Content/images/5.svg | 22 +
.../Common_Content/images/6.png | Bin 0 -> 865 bytes
.../Common_Content/images/6.svg | 22 +
.../Common_Content/images/7.png | Bin 0 -> 742 bytes
.../Common_Content/images/7.svg | 22 +
.../Common_Content/images/8.png | Bin 0 -> 862 bytes
.../Common_Content/images/8.svg | 22 +
.../Common_Content/images/9.png | Bin 0 -> 860 bytes
.../Common_Content/images/9.svg | 22 +
.../Common_Content/images/bkgrnd_greydots.png | Bin 0 -> 157 bytes
.../Common_Content/images/bullet_arrowblue.png | Bin 0 -> 177 bytes
.../Common_Content/images/documentation.png | Bin 0 -> 623 bytes
.../Common_Content/images/dot.png | Bin 0 -> 98 bytes
.../Common_Content/images/dot2.png | Bin 0 -> 98 bytes
.../Common_Content/images/green.png | Bin 0 -> 176 bytes
.../Common_Content/images/h1-bg.png | Bin 0 -> 565 bytes
.../Common_Content/images/image_left.png | Bin 0 -> 1114 bytes
.../Common_Content/images/image_right.png | Bin 0 -> 4092 bytes
.../Common_Content/images/important.png | Bin 0 -> 2080 bytes
.../Common_Content/images/important.svg | 106 +
.../Common_Content/images/logo.png | Bin 0 -> 1114 bytes
.../Common_Content/images/note.png | Bin 0 -> 1241 bytes
.../Common_Content/images/note.svg | 111 +
.../Common_Content/images/red.png | Bin 0 -> 163 bytes
.../Common_Content/images/redhat-logo.svg | 94 +
.../Common_Content/images/rhlogo.png | Bin 0 -> 2278 bytes
.../Common_Content/images/shade.png | Bin 0 -> 101 bytes
.../Common_Content/images/shine.png | Bin 0 -> 146 bytes
.../Common_Content/images/stock-go-back.png | Bin 0 -> 828 bytes
.../Common_Content/images/stock-go-forward.png | Bin 0 -> 828 bytes
.../Common_Content/images/stock-go-up.png | Bin 0 -> 760 bytes
.../Common_Content/images/stock-home.png | Bin 0 -> 808 bytes
.../Common_Content/images/title_logo.png | Bin 0 -> 13399 bytes
.../Common_Content/images/title_logo.svg | 109 +
.../Common_Content/images/warning.png | Bin 0 -> 1340 bytes
.../Common_Content/images/warning.svg | 89 +
.../Common_Content/images/watermark-draft.png | Bin 0 -> 25365 bytes
.../Common_Content/images/yellow.png | Bin 0 -> 175 bytes
.../Live_migration_and_RHEL_compatibility.html | 18 +
.../Sect_Failed_to_connect_socket.html | 22 +
.../Sect_Other_Connectivity_Errors.html | 14 +
.../apas02.html | 120 +
.../apas04.html | 14 +
.../apb.html | 173 +
.../apbs17s02.html | 38 +
.../apbs17s02s02.html | 21 +
.../apbs17s02s03.html | 41 +
.../apbs17s02s04.html | 20 +
.../apbs17s03.html | 22 +
.../apbs17s03s02.html | 30 +
.../apds02.html | 62 +
.../apds03.html | 72 +
.../apds04.html | 106 +
.../apds05.html | 32 +
.../apds06.html | 458 +
.../apds07.html | 18 +
.../apds08.html | 60 +
.../apds09.html | 18 +
.../apds10.html | 24 +
.../apes05.html | 26 +
.../apes06.html | 22 +
.../apes07.html | 40 +
.../apes08.html | 26 +
.../apes09.html | 19 +
.../apes10.html | 119 +
.../apes11.html | 55 +
.../apes14s03.html | 95 +
.../apes14s04.html | 32 +
.../apjs14.html | 53 +
...oyment_and_Administration-Revision_History.html | 19 +
.../appe-Virtualization-Additional_resources.html | 32 +
.../ch-lib-dom-xml.html | 54 +
.../ch01s02.html | 46 +
.../ch03s02.html | 75 +
.../ch07s02.html | 34 +
.../ch07s03.html | 30 +
.../ch08.html | 16 +
.../ch08s02.html | 12 +
.../ch10s04.html | 69 +
.../ch11s02.html | 23 +
.../ch12s03.html | 87 +
.../ch12s04.html | 28 +
.../ch13s03.html | 29 +
.../ch15s02.html | 29 +
.../ch15s02s02.html | 28 +
.../ch18s04.html | 28 +
.../ch19s02.html | 52 +
.../ch24s02.html | 20 +
.../ch25s05.html | 179 +
.../ch25s07.html | 42 +
.../ch29s02.html | 27 +
.../ch29s03.html | 18 +
.../ch29s04.html | 19 +
.../ch29s05.html | 41 +
.../ch29s06.html | 24 +
.../chap-KSM.html | 101 +
...Virtualization-Security_for_virtualization.html | 26 +
...dministration_Guide-Guest_Disks_libguestfs.html | 34 +
...on_Administration_Guide-KVM_live_migration.html | 64 +
...h_the_Virtual_Machine_Manager_virt_manager.html | 38 +
...istration_Guide-Managing_guests_with_virsh.html | 400 +
...on_Administration_Guide-QEMU_KVM_Whitelist.html | 22 +
...de-Remote_management_of_virtualized_guests.html | 76 +
...Administration_Guide-Server_best_practices.html | 23 +
...tion_Administration_Guide-Storage_Concepts.html | 30 +
...stration_Guide-Storage_Pools-Storage_Pools.html | 793 ++
...ation_Administration_Guide-Storage_Volumes.html | 39 +
...ation_Administration_Guide-Tips_and_tricks.html | 26 +
...ation_Administration_Guide-Troubleshooting.html | 78 +
...on_Administration_Guide-Virtual_Networking.html | 34 +
...irtualization_Administration_GuideAdvanced.html | 18 +
...uest_Installation_Guide-Guest_Installation.html | 28 +
..._Manager-Creating_guests_with_virt_manager.html | 62 +
...Guest_Installation_Guide-Host_Installation.html | 43 +
..._and_Guest_Installation_Guide-Introduction.html | 18 +
...Guest_Installation_Guide-KVM_Compatibility.html | 24 +
...allation_Guide-KVM_guest_timing_management.html | 79 +
...Installation_Guide-Libvirt_network_booting.html | 39 +
...t_Installation_Guide-Network_Configuration.html | 57 +
...Guest_Installation_Guide-PCI_Device_Config.html | 161 +
...nstallation_Guide-Para_virtualized_drivers.html | 76 +
...and_Guest_Installation_Guide-RHEL6_Install.html | 94 +
...ration_and_Guest_Installation_Guide-SR_IOV.html | 34 +
...est_Installation_Guide-System_Requirements.html | 62 +
...tion_Restrictions-Application_Restrictions.html | 24 +
...ualization_Restrictions-Other_Restrictions.html | 12 +
...allation_Guide-Virtualization_Restrictions.html | 78 +
.../chap-sVirt.html | 24 +
...irtual_machine_XML_dump_configuration_file.html | 123 +
...-Installing_with_a_virtualized_floppy_disk.html | 84 +
...ivers-Mounting_the_image_with_virt_manager.html | 82 +
...a_virtualized_drivers_for_existing_devices.html | 32 +
.../images/1-7RHEL_local_install.png | Bin 0 -> 13795 bytes
.../images/1-Iso_general.png | Bin 0 -> 66439 bytes
.../images/1-files_PV-win.png | Bin 0 -> 58708 bytes
.../images/10-7RHEL_local_install.png | Bin 0 -> 40128 bytes
.../images/10-w7x86driverchosen.png | Bin 0 -> 70168 bytes
.../images/10-w7x86driverchosen_win7.png | Bin 0 -> 19979 bytes
.../images/10-w7x86driverstart.png | Bin 0 -> 67481 bytes
.../images/10-w7x86driverstart_win7.png | Bin 0 -> 20672 bytes
.../images/11-7RHEL_local_install.png | Bin 0 -> 42123 bytes
.../images/12-DriverInstalled.png | Bin 0 -> 42765 bytes
.../images/14-StartInstallSerial.png | Bin 0 -> 89324 bytes
.../images/2-7RHEL_local_install.png | Bin 0 -> 31149 bytes
.../images/2-Iso_Balloon_Os.png | Bin 0 -> 58380 bytes
.../images/3-7RHEL_local_install.png | Bin 0 -> 26452 bytes
.../images/3-Iso_Balloon_Os_arch.png | Bin 0 -> 58272 bytes
.../images/3_PCI_Device.png | Bin 0 -> 179475 bytes
.../images/4-7RHEL_local_install.png | Bin 0 -> 29310 bytes
.../images/4-Iso_balloon_files.png | Bin 0 -> 69579 bytes
.../images/4_finish.png | Bin 0 -> 24479 bytes
.../images/5-7RHEL_local_install.png | Bin 0 -> 29133 bytes
.../images/6-7RHEL_local_install.png | Bin 0 -> 19657 bytes
.../images/6.4-2.png | Bin 0 -> 24447 bytes
.../images/6.4-3.png | Bin 0 -> 25646 bytes
.../images/6.4-4.png | Bin 0 -> 35108 bytes
.../images/7-7RHEL_local_install.png | Bin 0 -> 24996 bytes
.../images/8-7RHEL_local_install.png | Bin 0 -> 21005 bytes
.../images/8-BrowseForDriver.png | Bin 0 -> 76374 bytes
.../images/8-BrowseForDriver_win7.png | Bin 0 -> 20271 bytes
.../images/9-7RHEL_local_install.png | Bin 0 -> 34205 bytes
.../images/9-BrowseToDirectory.png | Bin 0 -> 17326 bytes
.../images/9-BrowseToDirectory_win7.png | Bin 0 -> 15823 bytes
.../images/COPYME.png | Bin 0 -> 60798 bytes
.../images/ChangeType.png | Bin 0 -> 119508 bytes
.../images/Connection_Details.png | Bin 0 -> 17102 bytes
.../images/Create-1.png | Bin 0 -> 68190 bytes
.../images/DevManagerStart.png | Bin 0 -> 115214 bytes
.../images/DevManagerStart_win7.png | Bin 0 -> 51206 bytes
.../images/DriverInstall-Expand.png | Bin 0 -> 111352 bytes
.../images/DriverInstall-OpenWizard.png | Bin 0 -> 10335 bytes
.../images/DriverInstall-OpenWizard_win7.png | Bin 0 -> 9493 bytes
.../images/DriverInstallExpand_win7.png | Bin 0 -> 92965 bytes
.../images/DuringInstallation.png | Bin 0 -> 25758 bytes
.../images/Iso_Balloon_files.png | Bin 0 -> 64585 bytes
.../images/Iso_general.png | Bin 0 -> 60798 bytes
.../images/ManageStart.png | Bin 0 -> 225210 bytes
.../images/Network_hardware.png | Bin 0 -> 52560 bytes
.../images/Network_hardware_virtio.png | Bin 0 -> 51598 bytes
.../images/PCIremoval.png | Bin 0 -> 55777 bytes
.../images/PXEguest_5of5.png | Bin 0 -> 46145 bytes
.../images/RHEL6_cpu+ram.png | Bin 0 -> 26155 bytes
.../images/RHEL6_finish_advanced.png | Bin 0 -> 49113 bytes
.../images/RHEL6_storage.png | Bin 0 -> 36029 bytes
.../images/RHEL6_storage_local.png | Bin 0 -> 33867 bytes
.../images/RHEL6_virt-manager_new_1.png | Bin 0 -> 38313 bytes
.../images/RHEL6local_choose.png | Bin 0 -> 52384 bytes
.../images/RHEL6local_selectedISO.png | Bin 0 -> 36710 bytes
.../images/RHELKVMpackages-2.png | Bin 0 -> 77122 bytes
.../images/RHELKVMpackages.png | Bin 0 -> 79030 bytes
.../images/RHELcustomize14.png | Bin 0 -> 104378 bytes
.../images/RHELcustomize15.png | Bin 0 -> 69240 bytes
.../images/RHELkvmSelect.png | Bin 0 -> 78106 bytes
.../images/SR-IOV_implementation.png | Bin 0 -> 75739 bytes
.../images/Screenshot-VIrt-Manager-fig31pt18.png | Bin 0 -> 27887 bytes
.../images/Screenshot-Virt-Manager-fig31pt1.png | Bin 0 -> 23228 bytes
.../images/Screenshot-Virt-Manager-fig31pt11.png | Bin 0 -> 27810 bytes
.../images/Screenshot-Virt-Manager-fig31pt13.png | Bin 0 -> 62072 bytes
.../images/Screenshot-Virt-Manager-fig31pt14.png | Bin 0 -> 80532 bytes
.../images/Screenshot-Virt-Manager-fig31pt15.png | Bin 0 -> 52668 bytes
.../images/Screenshot-Virt-Manager-fig31pt16.png | Bin 0 -> 72095 bytes
.../images/Screenshot-Virt-Manager-fig31pt17.png | Bin 0 -> 50464 bytes
.../images/Screenshot-Virt-Manager-fig31pt19.png | Bin 0 -> 22060 bytes
.../images/Screenshot-Virt-Manager-fig31pt2.png | Bin 0 -> 25861 bytes
.../images/Screenshot-Virt-Manager-fig31pt24.png | Bin 0 -> 29361 bytes
.../images/Screenshot-Virt-Manager-fig31pt24a.png | Bin 0 -> 29080 bytes
.../images/Screenshot-Virt-Manager-fig31pt27.png | Bin 0 -> 22828 bytes
.../images/Screenshot-Virt-Manager-fig31pt28.png | Bin 0 -> 33316 bytes
.../images/Screenshot-Virt-Manager-fig31pt29.png | Bin 0 -> 24925 bytes
.../images/Screenshot-Virt-Manager-fig31pt3.png | Bin 0 -> 69957 bytes
.../images/Screenshot-Virt-Manager-fig31pt4.png | Bin 0 -> 68968 bytes
.../images/Screenshot-Virt-Manager-fig31pt5.png | Bin 0 -> 548594 bytes
.../images/Screenshot-Virt-Manager-fig31pt6.png | Bin 0 -> 22883 bytes
.../images/Screenshot-Virt-Manager-fig31pt7.png | Bin 0 -> 25774 bytes
.../images/Screenshot-Virt-Manager_fig31pt25.png | Bin 0 -> 25748 bytes
.../images/Screenshot-Virt-Manager_fig31pt25a.png | Bin 0 -> 23533 bytes
.../images/Screenshot-Virt-Manager_fig31pt26.png | Bin 0 -> 30226 bytes
.../images/Screenshot-admin-18pt7-pic1.png | Bin 0 -> 38526 bytes
.../images/Screenshot-admin-18pt7-pic10.png | Bin 0 -> 48685 bytes
.../images/Screenshot-admin-18pt7-pic11.png | Bin 0 -> 60824 bytes
.../images/Screenshot-admin-18pt7-pic2.png | Bin 0 -> 38421 bytes
.../images/Screenshot-admin-18pt7-pic3.png | Bin 0 -> 19836 bytes
.../images/Screenshot-admin-18pt7-pic4.png | Bin 0 -> 38995 bytes
.../images/Screenshot-admin-18pt7-pic5.png | Bin 0 -> 33897 bytes
.../images/Screenshot-admin-18pt7-pic6.png | Bin 0 -> 29663 bytes
.../images/Screenshot-admin-18pt7-pic7.png | Bin 0 -> 32043 bytes
.../images/Screenshot-admin-18pt7-pic8.png | Bin 0 -> 46321 bytes
.../images/Screenshot-admin-18pt7-pic9.png | Bin 0 -> 70468 bytes
.../images/Screenshot-pic1-virt-mgr-guests.png | Bin 0 -> 22245 bytes
.../Screenshot-pic2-add-connection-pull-down.png | Bin 0 -> 22169 bytes
.../images/Screenshot-pic3-Add Connection.png | Bin 0 -> 18516 bytes
.../images/Screenshot-pic3-Add-Connection.png | Bin 0 -> 21410 bytes
.../images/Screenshot-pic4-OpenSSH.png | Bin 0 -> 11280 bytes
.../Screenshot-pic5-guest-select-migrate.png | Bin 0 -> 34896 bytes
.../Screenshot-pic6-final-before-migrate.png | Bin 0 -> 36898 bytes
.../Screenshot-pic7-Migrating-guest1-rhel6-64.png | Bin 0 -> 14788 bytes
.../images/Screenshot-pic8-migrated.png | Bin 0 -> 30438 bytes
.../images/Screenshot-rhel6pv-virt-method.png | Bin 0 -> 47301 bytes
.../images/Screenshot-sevenpt1-pic1.png | Bin 0 -> 23889 bytes
.../images/Screenshot-sevenpt1-pic2.png | Bin 0 -> 66922 bytes
.../images/Screenshot-sevenpt1-pic4.png | Bin 0 -> 62475 bytes
.../images/Screenshot-sevenpt1-pic5.png | Bin 0 -> 69613 bytes
.../images/Screenshot-sevenpt1-pic6.png | Bin 0 -> 46457 bytes
.../images/Screenshot-sevenpt1-pic7-managed.png | Bin 0 -> 36200 bytes
.../images/Screenshot-sevenpt1-pic7.png | Bin 0 -> 68403 bytes
.../images/Screenshot-sevenpt1-pic8-create-lvm.png | Bin 0 -> 42013 bytes
...Screenshot-sevenpt1-pic8-new-storage-volume.png | Bin 0 -> 76048 bytes
.../Screenshot-sevenpt1-pic9-local-storage.png | Bin 0 -> 100054 bytes
.../Screenshot-sevenpt1-pic9-storage-volume.png | Bin 0 -> 87492 bytes
.../images/Screenshot-sevenpt2-pic2.png | Bin 0 -> 82712 bytes
.../images/Screenshot-sevenpt2-pic3.png | Bin 0 -> 68632 bytes
.../images/Screenshot-sevenpt3-pic2.png | Bin 0 -> 68105 bytes
.../images/Screenshot-sevenpt3-pic3.png | Bin 0 -> 40893 bytes
.../images/Screenshot-sevenpt3-pic4.png | Bin 0 -> 41498 bytes
.../images/Screenshot-sevenpt3-pic5.png | Bin 0 -> 68403 bytes
.../images/Screenshot-sevenpt3-pic6.png | Bin 0 -> 83457 bytes
.../images/Screenshot-virtlab22-Host-Details.png | Bin 0 -> 49786 bytes
.../Section_11_pt_2_pt_2_step3_substep_c.png | Bin 0 -> 70469 bytes
.../Section_11_pt_2_pt_2_step3_substep_d.png | Bin 0 -> 67795 bytes
.../images/Select_storage_pools.png | Bin 0 -> 39490 bytes
.../images/StartDevManagerInVM.png | Bin 0 -> 330244 bytes
.../images/StartDevManagerInVM_win7.png | Bin 0 -> 223816 bytes
.../images/StartInstallingBalloon-1.png | Bin 0 -> 152903 bytes
.../images/StartInstallingBalloon-1_win7.png | Bin 0 -> 72036 bytes
.../images/Virt-Manager-Add-Connection.png | Bin 0 -> 21414 bytes
.../images/Virtual_Machine_Name-guest-install.png | Bin 0 -> 40239 bytes
...ual_Machine_Name-guest-install_STEP2-cpumem.png | Bin 0 -> 28224 bytes
...ual_Machine_Name-guest-install_STEP2-import.png | Bin 0 -> 29326 bytes
...tual_Machine_Name-guest-install_STEP2-local.png | Bin 0 -> 34657 bytes
.../Virtual_Machine_Name-guest-install_STEP4.png | Bin 0 -> 36303 bytes
...ual_Machine_Name-guest-install_STEP5-finish.png | Bin 0 -> 48968 bytes
...l_Machine_Name-guest-install_final-hardware.png | Bin 0 -> 76768 bytes
.../images/XP-driver-capture.png | Bin 0 -> 11814 bytes
.../images/XP-driver-select-driver.png | Bin 0 -> 240846 bytes
.../images/XP-driver-select2.png | Bin 0 -> 51574 bytes
.../images/after_virtualization.png | Bin 0 -> 39557 bytes
.../images/before_virtualization.png | Bin 0 -> 38000 bytes
.../images/block_finish-virtio-win.png | Bin 0 -> 61150 bytes
.../images/block_start-virtio-win.png | Bin 0 -> 24334 bytes
.../images/bridgePXE.png | Bin 0 -> 40131 bytes
.../images/bridgefinish.png | Bin 0 -> 49050 bytes
.../images/bz734652-step3.png | Bin 0 -> 302675 bytes
.../images/done-KVM_PV.png | Bin 0 -> 34673 bytes
.../images/exception-virtio-win.png | Bin 0 -> 23524 bytes
.../images/icon.svg | 19 +
.../images/ide-to-virtio-add-hardware.png | Bin 0 -> 129326 bytes
.../images/ide-to-virtio-remove-dev.png | Bin 0 -> 12609 bytes
.../images/ide-to-virtio1.png | Bin 0 -> 93665 bytes
.../images/ide-to-virtio1replacement.png | Bin 0 -> 81885 bytes
.../images/ide-to-virtio2.png | Bin 0 -> 97191 bytes
.../images/ide-to-virtio3.png | Bin 0 -> 94899 bytes
.../images/ide-to-virtio4.png | Bin 0 -> 107743 bytes
.../images/ide-to-virtio5.png | Bin 0 -> 108511 bytes
.../images/ide-to-virtio5replacement.png | Bin 0 -> 140191 bytes
.../images/ide-to-virtio6.png | Bin 0 -> 106978 bytes
.../images/ide-to-virtio6replacement.png | Bin 0 -> 17285 bytes
.../images/ide-to-virtio7.png | Bin 0 -> 95349 bytes
.../images/ide-to-virtio7replacement.png | Bin 0 -> 130528 bytes
.../images/infotabbutton.png | Bin 0 -> 1982 bytes
.../images/installmedia-blank.png | Bin 0 -> 28277 bytes
.../images/installmedia-select-os1.png | Bin 0 -> 31898 bytes
.../images/installmedia-select-volume.png | Bin 0 -> 26046 bytes
.../images/network_finish-virtio-win.png | Bin 0 -> 131791 bytes
.../images/network_performance-virtio-win.png | Bin 0 -> 21864 bytes
.../images/network_start-virtio-win.png | Bin 0 -> 63822 bytes
.../paravirt-0-click-configure-before-install.png | Bin 0 -> 32637 bytes
...avirt-0-click-configure-before-install_win7.png | Bin 0 -> 28916 bytes
.../images/paravirt-1-click-add-hardware.png | Bin 0 -> 2281 bytes
.../paravirt-10-select-custom-installation.png | Bin 0 -> 33229 bytes
.../images/paravirt-11-load-driver.png | Bin 0 -> 1659 bytes
.../images/paravirt-12-insert-disk.png | Bin 0 -> 19618 bytes
.../images/paravirt-13-select-driver-arch.png | Bin 0 -> 12390 bytes
.../images/paravirt-14-view-drivers-loaded.png | Bin 0 -> 11244 bytes
.../images/paravirt-2-disk-type.png | Bin 0 -> 4464 bytes
.../images/paravirt-2a-select-existing-storage.png | Bin 0 -> 5537 bytes
.../images/paravirt-2b-select-browse-local.png | Bin 0 -> 2319 bytes
.../images/paravirt-2c-virtio-win-vfd.png | Bin 0 -> 7385 bytes
.../images/paravirt-2z-select-storage.png | Bin 0 -> 67646 bytes
.../images/paravirt-3-floppy-advanced-options.png | Bin 0 -> 8673 bytes
.../images/paravirt-4-after-adding-virtio-disk.png | Bin 0 -> 66487 bytes
.../images/paravirt-5-begin-installation.png | Bin 0 -> 4211 bytes
.../images/paravirt-6-windows-install.png | Bin 0 -> 6419 bytes
.../paravirt-6a-select-installation-type.png | Bin 0 -> 28819 bytes
.../images/paravirt-8-agree-to-license-terms.png | Bin 0 -> 1138 bytes
.../images/paravirt-adding-virtio-disk.png | Bin 0 -> 65258 bytes
.../images/paravirt-click-begin-installation.png | Bin 0 -> 4230 bytes
.../images/paravirt-confirm-floppy-settings.png | Bin 0 -> 56639 bytes
.../images/paravirt-confirm-settings.png | Bin 0 -> 56545 bytes
.../images/paravirt-confirm-virtio-disk-in-use.png | Bin 0 -> 16477 bytes
.../images/paravirt-device-type-virtio-finish.png | Bin 0 -> 65699 bytes
.../images/paravirt-device-type-virtiodisk.png | Bin 0 -> 4683 bytes
.../images/paravirt-remove-disk1-2.png | Bin 0 -> 1493 bytes
.../images/paravirt-remove-disk1.png | Bin 0 -> 70993 bytes
.../images/paravirt-review-virtio-settings.png | Bin 0 -> 66335 bytes
.../images/paravirt-select-device-type-floppy.png | Bin 0 -> 4814 bytes
.../images/paravirt-storage-win7.png | Bin 0 -> 63115 bytes
.../images/pci_host_device.png | Bin 0 -> 129981 bytes
.../images/rhel5_rhel6pv_create_vm.png | Bin 0 -> 29497 bytes
.../images/rhel5_rhel6pv_finish.png | Bin 0 -> 49265 bytes
.../images/rhel5_rhel6pv_finish_3.png | Bin 0 -> 66701 bytes
.../images/rhel5_rhel6pv_install_method.png | Bin 0 -> 75364 bytes
.../images/rhel5_rhel6pv_install_source_2.png | Bin 0 -> 63977 bytes
.../images/rhel5_rhel6pv_mem_n_cpu_alloc.png | Bin 0 -> 90621 bytes
.../images/rhel5_rhel6pv_network.png | Bin 0 -> 70040 bytes
.../images/rhel5_rhel6pv_storage.png | Bin 0 -> 87583 bytes
.../images/rhel5_rhel6pv_virt_install.png | Bin 0 -> 27712 bytes
.../rhel6-Screenshot-step2-existing-disk-image.png | Bin 0 -> 36736 bytes
.../rhel6_Screenshot-guest1-rhel5-64-final.png | Bin 0 -> 64451 bytes
.../images/rhel6_Screenshot-step1.png | Bin 0 -> 39198 bytes
.../images/rhel6_Screenshot-step2.png | Bin 0 -> 35789 bytes
.../images/rhel6_Screenshot-step3.png | Bin 0 -> 26469 bytes
.../images/rhel6_Screenshot-step4.png | Bin 0 -> 34920 bytes
.../images/rhel6_Screenshot-step5.png | Bin 0 -> 52176 bytes
.../images/rhel6_virt_manager.png | Bin 0 -> 11628 bytes
.../images/selinux_uuid_block.png | Bin 0 -> 42886 bytes
.../images/shutter-9-3_win7-1.png | Bin 0 -> 53637 bytes
.../images/shutter-9-3_win7-2.png | Bin 0 -> 53447 bytes
.../images/shutter-9-3_win7-3.png | Bin 0 -> 60345 bytes
.../images/shutter-9-3_win7-4.png | Bin 0 -> 62326 bytes
.../images/step-1-1.png | Bin 0 -> 17359 bytes
.../images/step1-1.png | Bin 0 -> 17467 bytes
.../images/step1-2.png | Bin 0 -> 14463 bytes
.../images/step2-1.png | Bin 0 -> 58452 bytes
.../images/step2-2.png | Bin 0 -> 25501 bytes
.../images/step2-3.png | Bin 0 -> 36016 bytes
.../images/step2-4.png | Bin 0 -> 47641 bytes
.../images/step3-1.png | Bin 0 -> 40153 bytes
.../images/step4-1.png | Bin 0 -> 43876 bytes
.../images/step4-2.png | Bin 0 -> 17810 bytes
.../images/step5-1.png | Bin 0 -> 45055 bytes
.../images/step5-2.png | Bin 0 -> 32497 bytes
.../images/step5-3.png | Bin 0 -> 32720 bytes
.../images/type_assigned-KVM_PV.png | Bin 0 -> 61786 bytes
.../images/type_assigned-KVM_PV_new.png | Bin 0 -> 63191 bytes
.../images/v2v-add_storagepool.png | Bin 0 -> 23510 bytes
.../images/v2v-select_host.png | Bin 0 -> 12194 bytes
.../images/v2v-storage_tab.png | Bin 0 -> 44510 bytes
.../images/virt-manager-enable-disk-io.png | Bin 0 -> 18245 bytes
.../images/virt-manager-enable-networkio.png | Bin 0 -> 18218 bytes
.../images/virt-manager_add_nfs_step1.png | Bin 0 -> 27760 bytes
.../images/virt-manager_add_nfs_step2.png | Bin 0 -> 35312 bytes
.../images/virt-manager_add_storage_pool1.png | Bin 0 -> 27075 bytes
.../images/virt-manager_add_storage_pool2.png | Bin 0 -> 37625 bytes
.../images/virt-manager_hardware.png | Bin 0 -> 125992 bytes
.../images/virt-manager_hardware_wizard1.png | Bin 0 -> 36804 bytes
.../images/virt-manager_home.png | Bin 0 -> 32772 bytes
.../images/virt-manager_host_details_storage.png | Bin 0 -> 53958 bytes
.../images/virt-manager_main.png | Bin 0 -> 21512 bytes
.../images/virt-manager_newicon.png | Bin 0 -> 1475 bytes
.../images/virt-manager_select_host.png | Bin 0 -> 26025 bytes
..._storage_pools_add_dir_step_1_name_and_type.png | Bin 0 -> 26371 bytes
...er_storage_pools_add_dir_step_2_target_path.png | Bin 0 -> 33949 bytes
...manager_storage_pools_add_dir_step_3_result.png | Bin 0 -> 45724 bytes
...r_storage_pools_add_fs_step_1_name_and_type.png | Bin 0 -> 26216 bytes
...torage_pools_add_fs_step_2_paths_and_format.png | Bin 0 -> 32029 bytes
...-manager_storage_pools_add_fs_step_3_result.png | Bin 0 -> 46654 bytes
..._storage_pools_add_lvm_step_1_name_and_type.png | Bin 0 -> 26188 bytes
...torage_pools_add_lvm_step_2a_paths_and_pool.png | Bin 0 -> 32081 bytes
...torage_pools_add_lvm_step_2b_format_warning.png | Bin 0 -> 10141 bytes
...manager_storage_pools_add_lvm_step_3_result.png | Bin 0 -> 104017 bytes
.../images/virt-manager_virtualization_method.png | Bin 0 -> 71057 bytes
.../images/virtio-disk2.png | Bin 0 -> 47633 bytes
.../images/virtio-network-finish3.png | Bin 0 -> 31957 bytes
.../images/virtio-network-step1.png | Bin 0 -> 36985 bytes
.../images/virtio-network-step2.png | Bin 0 -> 40243 bytes
.../images/virtio-storage-finish3.png | Bin 0 -> 34181 bytes
.../images/virtio-storage-step1-new.png | Bin 0 -> 62145 bytes
.../images/virtio-storage-step1.png | Bin 0 -> 37033 bytes
.../images/virtio-storage-step2-new.png | Bin 0 -> 64041 bytes
.../images/virtio-storage-step2.png | Bin 0 -> 61079 bytes
.../images/virtio0-customize.png | Bin 0 -> 58502 bytes
.../images/virtio3-finished.png | Bin 0 -> 27470 bytes
.../images/virtual_machine_overview.png | Bin 0 -> 73963 bytes
.../images/vm-add_hardware1.png | Bin 0 -> 79211 bytes
.../images/vm_add_hardware.png | Bin 0 -> 6306 bytes
.../images/vm_add_hardware_new.png | Bin 0 -> 2266 bytes
.../images/vm_info_button.png | Bin 0 -> 4964 bytes
.../images/vm_info_button_new.png | Bin 0 -> 3557 bytes
.../images/vmm_vnet_create1.png | Bin 0 -> 38424 bytes
.../images/vmm_vnet_create2.png | Bin 0 -> 19689 bytes
.../images/vmm_vnet_create3_ipv4addspace.png | Bin 0 -> 38805 bytes
.../images/vmm_vnet_create4_dhcprange.png | Bin 0 -> 33089 bytes
.../images/vmm_vnet_create5_connectphysnet.png | Bin 0 -> 29901 bytes
.../images/vmm_vnet_create6_finish.png | Bin 0 -> 31511 bytes
.../images/vmm_vnet_create7_maintab.png | Bin 0 -> 43333 bytes
.../images/vmm_vnet_maintab.png | Bin 0 -> 41593 bytes
.../images/vmm_vnet_menuselect.png | Bin 0 -> 20814 bytes
.../images/vn-01-switch.png | Bin 0 -> 10406 bytes
.../images/vn-02-switchandtwoguests.png | Bin 0 -> 42987 bytes
.../images/vn-03-hostwithswitch.png | Bin 0 -> 25369 bytes
.../images/vn-04-hostwithnatswitch.png | Bin 0 -> 135903 bytes
.../images/vn-05-switchwithdnsmasq.jpg | Bin 0 -> 216332 bytes
.../images/vn-06-routed-switch.png | Bin 0 -> 139243 bytes
.../images/vn-07-isolated-switch.png | Bin 0 -> 131466 bytes
.../images/vn-08-network-overview.png | Bin 0 -> 364520 bytes
.../images/vn-09-routed-mode-DMZ.png | Bin 0 -> 635464 bytes
.../images/vn-10-routed-mode-datacenter.png | Bin 0 -> 415490 bytes
.../images/vn-11-router-mode-mac-restricted.png | Bin 0 -> 398974 bytes
.../images/vn-12-network-tab-default.png | Bin 0 -> 39835 bytes
.../images/w7x86driverchosen.png | Bin 0 -> 22359 bytes
.../images/win2003_select_hal.png | Bin 0 -> 8979 bytes
...win7paravirt-click-configure-before-install.png | Bin 0 -> 28908 bytes
.../index.html | 37 +
.../live-migration-errors.html | 14 +
.../migrating_guests-with-virsh.html | 12 +
.../netkvm-parameters.html | 90 +
.../pr01s02.html | 16 +
...tion_Deployment_and_Administration-Preface.html | 95 +
.../pt01.html | 10 +
.../pt02.html | 10 +
.../pt03.html | 10 +
.../qemu-ga.html | 30 +
.../run-virt-df.html | 44 +
.../sec-known-issues-windows-xp-guests.html | 12 +
...Attaching_and_updating_a_device_with_virsh.html | 12 +
.../sect-Augeas-and-libguestfs-scripting.html | 53 +
...-Guide-Guest_Disks_libguestfs-installation.html | 18 +
...ct-Managing_storage_controllers_in_a_guest.html | 42 +
.../sect-Modifying-files-with-guestfish.html | 29 +
.../sect-Network_Address_Translation-libvirt.html | 14 +
.../sect-Other-actions-with-guestfish.html | 12 +
.../sect-RedHat-We_Need_Feedback.html | 16 +
.../sect-Shell-scripting-with-guestfish.html | 21 +
.../sect-Terminology-Guest_Disks_libguestfs.html | 22 +
.../sect-Using-API-Programming-Languages.html | 243 +
..._drives_and_other_block_devices_to_a_guest.html | 45 +
...ditional_resources-Installed_documentation.html | 20 +
...ve_migration-Live_KVM_migration_with_virsh.html | 120 +
...live_migration-Migrating_with_virt_manager.html | 57 +
..._Manager_virt_manager-Displaying_CPU_usage.html | 16 +
...ne_Manager_virt_manager-Displaying_Disk_IO.html | 20 +
...Manager_virt_manager-Displaying_Network_IO.html | 20 +
...ager_virt_manager-Displaying_guest_details.html | 34 +
...ger_virt_manager-Displaying_host-CPU_usage.html | 16 +
...ine_Manager_virt_manager-Status_monitoring.html | 20 +
...he_Virtual_Machine_Manager_details_window_.html | 14 +
...er-The_Virtual_Machine_Manager_main_window.html | 12 +
...er_virt_manager-The_open_connection_window.html | 20 +
...manager-Virtual_Machine_graphical_console_.html | 20 +
...ts_with_virsh-Connecting_to_the_hypervisor.html | 14 +
..._guests-Remote_management_over_TLS_and_SSL.html | 90 +
...ment_of_virtualized_guests-Transport_modes.html | 109 +
..._virtualization-SELinux_and_virtualization.html | 43 +
..._for_virtualization-SELinux_considerations.html | 16 +
...ct-Virtualization-Storage_Concepts-Volumes.html | 63 +
...ualization-Storage_Volumes-Cloning_volumes.html | 36 +
...alization-Storage_Volumes-Deleting_volumes.html | 15 +
...n-Tips_and_tricks-Configuring_a_VNC_Server.html | 16 +
...s-Disable_SMART_disk_monitoring_for_guests.html | 14 +
...tricks-Generating_a_new_unique_MAC_address.html | 41 +
...ion-Tips_and_tricks-Libvirt_Managed_Timers.html | 156 +
...on-Tips_and_tricks-Overcommitting_with_KVM.html | 44 +
...tualization-Tips_and_tricks-Using_qemu_img.html | 103 +
...tricks-Verifying_virtualization_extensions.html | 39 +
...virtualization_hardware_extensions_in_BIOS.html | 36 +
...Troubleshooting-KVM_networking_performance.html | 60 +
...ization-Troubleshooting-Loop_device_errors.html | 15 +
...Characters_Guest_Console_Japanese_Keyboard.html | 38 +
...ting_-Troubleshooting_with_serial_consoles.html | 38 +
...working-Attaching_virtual_network_to_guest.html | 22 +
...tual_Networking-Creating_a_virtual_network.html | 32 +
...ation-Virtual_Networking-Example_scenarios.html | 20 +
...tual_Networking-Managing_a_virtual_network.html | 18 +
...k_devices-Adding_storage_devices_to_guests.html | 99 +
...allation-Creating_guests_with_virt_install.html | 37 +
...st_Installation-Installing_guests_with_PXE.html | 28 +
...n_existing_Red_Hat_Enterprise_Linux_system.html | 84 +
...figuration-Bridged_networking_with_libvirt.html | 21 +
...I_Assignment-Adding_a_PCI_device_to_a_host.html | 20 +
...M_para_virtualized_drivers_for_new_devices.html | 56 +
...tion_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html | 169 +
...ng_Windows_XP_as_a_fully_virtualized_guest.html | 46 +
.../sect-applying-network-filtering.html | 52 +
.../sect-attch-nic-physdev.html | 70 +
.../sect-cpu-allocation.html | 26 +
.../sect-cpu-tuning.html | 67 +
.../sect-dom-xml-op-sys-boot.html | 57 +
.../sect-dynamic-vNIC.html | 51 +
.../sect-expand-disk-image.html | 84 +
.../sect-gracefully-shut-down-guests.html | 27 +
.../sect-guest-cpu-model-config.html | 12 +
.../sect-learn-about-host-cpu.html | 44 +
.../sect-libguestfs-more-docs.html | 12 +
.../sect-libguestfs-troubleshoot.html | 16 +
.../sect-libvirt-dom-xml-blk-io-tuning.html | 46 +
.../sect-libvirt-dom-xml-cpu-model-top.html | 124 +
.../sect-libvirt-dom-xml-devices.html | 201 +
.../sect-libvirt-dom-xml-event-config.html | 91 +
.../sect-libvirt-dom-xml-mem-tuning.html | 49 +
.../sect-libvirt-dom-xml-numa-node-tuning.html | 36 +
.../sect-libvirt-dom-xml-pwr-man.html | 23 +
.../sect-libvirt-dom-xml-res-part.html | 23 +
.../sect-libvirt-dom-xml-time-keep.html | 74 +
.../sect-limit-redirection.html | 45 +
.../sect-man-disk-image.html | 74 +
.../sect-mem-back.html | 24 +
.../sect-mem-dump-off.html | 49 +
.../sect-network-protocols.html | 14 +
.../sect-other-commands.html | 29 +
.../sect-perf-mon.html | 20 +
.../sect-qemu-ga.html | 35 +
.../sect-run-virt-rescue.html | 57 +
.../sect-s3-s4.html | 21 +
.../sect-smbios-sys-info.html | 38 +
.../sect-the-Default_Configuration-libvirt.html | 14 +
.../sect-the_guestfish_shell.html | 122 +
.../sect-virt-df.html | 12 +
.../sect-virt-inspector-install.html | 16 +
.../sect-virt-inspector-run.html | 82 +
.../sect-virt-inspector.html | 12 +
.../sect-virt-rescue.html | 16 +
.../sect-virt-resize.html | 12 +
.../sect-virt-win-reg-install.html | 14 +
.../sect-virt-win-reg-use.html | 29 +
.../sect-virt-win-reg.html | 12 +
...ct_RedHat-Getting_Help_and_Giving_Feedback.html | 20 +
.../section-libvirt-dom-xml-example.html | 69 +
...ction-libvirt-dom-xml-memory-baloon-device.html | 34 +
.../section-libvirt-dom-xml-random-number-gen.html | 37 +
.../section-libvirt-dom-xml-security-label.html | 53 +
.../section-libvirt-dom-xml-sound-devices.html | 32 +
.../section-libvirt-dom-xml-tpm-device.html | 26 +
.../section-libvirt-dom-xml-watchdog.html | 51 +
.../shared-storage-nfs-migration.html | 33 +
.../sub-sect-adv-filt-topics.html | 24 +
.../sub-sect-auto-IP-add-detect-dhcp-snoop.html | 18 +
.../sub-sect-blkresize.html | 20 +
.../sub-sect-blockpull.html | 58 +
.../sub-sect-element-oview.html | 12 +
.../sub-sect-filt-chain-props.html | 48 +
.../sub-sect-filt-chain.html | 67 +
.../sub-sect-filter-rules.html | 51 +
.../sub-sect-iso-mode.html | 12 +
.../sub-sect-isolated-mode.html | 12 +
...sect-limitations-filters-network-subsystem.html | 18 +
.../sub-sect-nat-mode.html | 12 +
.../sub-sect-op-sys-cont-boot.html | 25 +
.../sub-sect-op-sys-dir-kern-boot.html | 51 +
.../sub-sect-op-sys-host-boot.html | 31 +
.../sub-sect-ref-filter.html | 28 +
.../sub-sect-routed-mode-libvirt.html | 12 +
.../sub-sect-supp-pros.html | 97 +
.../sub-sect-vars-in-filters.html | 72 +
.../sub-sect-vars-reserved.html | 40 +
...libvirt-dom-xml-devices-Network-interfaces.html | 56 +
...ub-section-libvirt-dom-xml-devices-channel.html | 42 +
...b-section-libvirt-dom-xml-devices-consoles.html | 38 +
...ection-libvirt-dom-xml-devices-controllers.html | 44 +
...n-libvirt-dom-xml-devices-device-addresses.html | 58 +
...tion-libvirt-dom-xml-devices-device-leases.html | 33 +
...ection-libvirt-dom-xml-devices-filesystems.html | 62 +
...irt-dom-xml-devices-graphical-framebuffers.html | 95 +
...on-libvirt-dom-xml-devices-guest-interface.html | 82 +
...irt-dom-xml-devices-host-device-assignment.html | 78 +
...ion-libvirt-dom-xml-devices-host-interface.html | 193 +
...ection-libvirt-dom-xml-devices-hub-devices.html | 23 +
...tion-libvirt-dom-xml-devices-input-devices.html | 26 +
...libvirt-dom-xml-devices-redirected-devices.html | 44 +
...-section-libvirt-dom-xml-devices-smartcard.html | 55 +
.../sub-section-libvirt-dom-xml-devices-video.html | 47 +
.../sub-sub-sect-DHCP-snooping.html | 25 +
.../sub-sub-sect-chars-IPv6.html | 104 +
.../sub-sub-sect-chars-tcp-udp.html | 128 +
.../sub-sub-sect-icmp.html | 128 +
.../sub-sub-sect-icmpv6.html | 110 +
.../sub-sub-sect-igmp-esp-ah-etc.html | 116 +
...sub-sub-sect-igmp-esp-ah-udplite-over-ipv6.html | 98 +
.../sub-sub-sect-lim-numb-conns.html | 43 +
.../sub-sub-sect-pre-exist-net-filter.html | 42 +
.../sub-sub-sect-prot-ARP-RARP-explained.html | 98 +
.../sub-sub-sect-prot-Ipv4-explained.html | 104 +
.../sub-sub-sect-prot-STP-explained.html | 158 +
.../sub-sub-sect-samp-filter.html | 146 +
.../sub-sub-sect-tcp-utp-sctp-over-ipv6.html | 122 +
.../sub-sub-sect-vlan.html | 62 +
.../sub-sub-sect-write-own-filters.html | 80 +
...-xml-devices-Network-interfaces-boot-order.html | 25 +
...l-devices-Network-interfaces-bridge-to-lan.html | 37 +
...faces-direct-attachment-to-physical-device.html | 114 +
...ork-interfaces-generic-ethernet-connection.html | 26 +
...evices-Network-interfaces-multicast-tunnel.html | 22 +
...k-interfaces-overriding-the-target-element.html | 24 +
...devices-Network-interfaces-pci-passthrough.html | 30 +
...rfaces-setting-nic-driver-specific-options.html | 45 +
...-xml-devices-Network-interfaces-tcp-tunnel.html | 27 +
...s-Network-interfaces-userspace-slirp-stack.html | 25 +
...-device-assignment-block-character-devices.html | 61 +
...l-devices-interface-ROM-BIOS-configuration.html | 25 +
...m-xml-devices-modifying-virtual-link-state.html | 25 +
...ub-sub-section-libvirt-dom-xml-devices-qos.html | 32 +
...n-libvirt-dom-xml-devices-setting-vlan-tag.html | 30 +
.../sub-sub-subsect-command-line-tools.html | 22 +
.../subsect-guest-synch-delimited.html | 26 +
.../vhostmd.html | 18 +
.../virsh-migration-arguements.html | 46 +
...n_Deployment_and_Administration_Guide-en-US.pdf | Bin 0 -> 9515328 bytes
...n_Deployment_and_Administration_Guide-en-US.pdf | Bin 0 -> 9475950 bytes
public_html/en-US/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/en-US/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/en-US/opds-Fedora_Core.xml | 2 +-
.../en-US/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/en-US/opds-Fedora_Security_Team.xml | 2 +-
public_html/en-US/opds.xml | 14 +-
public_html/en-US/toc.html | 13 +-
public_html/es-ES/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/es-ES/opds-Fedora.xml | 2 +-
public_html/es-ES/opds-Fedora_15.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/es-ES/opds-Fedora_Core.xml | 2 +-
.../es-ES/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/es-ES/opds-Fedora_Security_Team.xml | 2 +-
public_html/es-ES/opds.xml | 16 +-
public_html/es-ES/toc.html | 13 +-
public_html/fa-IR/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/fa-IR/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/fa-IR/opds-Fedora_Core.xml | 2 +-
.../fa-IR/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/fa-IR/opds-Fedora_Security_Team.xml | 2 +-
public_html/fa-IR/opds.xml | 14 +-
public_html/fa-IR/toc.html | 13 +-
public_html/fi-FI/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/fi-FI/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/fi-FI/opds-Fedora_Core.xml | 2 +-
.../fi-FI/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/fi-FI/opds-Fedora_Security_Team.xml | 2 +-
public_html/fi-FI/opds.xml | 14 +-
public_html/fi-FI/toc.html | 13 +-
public_html/fr-FR/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/fr-FR/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/fr-FR/opds-Fedora_Core.xml | 2 +-
.../fr-FR/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/fr-FR/opds-Fedora_Security_Team.xml | 2 +-
public_html/fr-FR/opds.xml | 14 +-
public_html/fr-FR/toc.html | 13 +-
public_html/gu-IN/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/gu-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/gu-IN/opds-Fedora_Core.xml | 2 +-
.../gu-IN/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/gu-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/gu-IN/opds.xml | 14 +-
public_html/gu-IN/toc.html | 13 +-
public_html/he-IL/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/he-IL/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/he-IL/opds-Fedora_Core.xml | 2 +-
.../he-IL/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/he-IL/opds-Fedora_Security_Team.xml | 2 +-
public_html/he-IL/opds.xml | 14 +-
public_html/he-IL/toc.html | 13 +-
public_html/hi-IN/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/hi-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/hi-IN/opds-Fedora_Core.xml | 2 +-
.../hi-IN/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/hi-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/hi-IN/opds.xml | 14 +-
public_html/hi-IN/toc.html | 13 +-
public_html/hu-HU/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/hu-HU/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/hu-HU/opds-Fedora_Core.xml | 2 +-
.../hu-HU/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/hu-HU/opds-Fedora_Security_Team.xml | 2 +-
public_html/hu-HU/opds.xml | 14 +-
public_html/hu-HU/toc.html | 13 +-
public_html/ia/Site_Statistics.html | 6 +-
.../ia/opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ia/opds-Fedora.xml | 2 +-
.../ia/opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ia/opds-Fedora_Core.xml | 2 +-
public_html/ia/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/ia/opds-Fedora_Security_Team.xml | 2 +-
public_html/ia/opds.xml | 14 +-
public_html/ia/toc.html | 13 +-
public_html/id-ID/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/id-ID/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/id-ID/opds-Fedora_Core.xml | 2 +-
.../id-ID/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/id-ID/opds-Fedora_Security_Team.xml | 2 +-
public_html/id-ID/opds.xml | 14 +-
public_html/id-ID/toc.html | 13 +-
public_html/it-IT/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/it-IT/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/it-IT/opds-Fedora_Core.xml | 2 +-
.../it-IT/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/it-IT/opds-Fedora_Security_Team.xml | 2 +-
public_html/it-IT/opds.xml | 14 +-
public_html/it-IT/toc.html | 13 +-
public_html/ja-JP/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ja-JP/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ja-JP/opds-Fedora_Core.xml | 2 +-
.../ja-JP/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/ja-JP/opds-Fedora_Security_Team.xml | 2 +-
public_html/ja-JP/opds.xml | 14 +-
public_html/ja-JP/toc.html | 13 +-
public_html/kn-IN/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/kn-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/kn-IN/opds-Fedora_Core.xml | 2 +-
.../kn-IN/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/kn-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/kn-IN/opds.xml | 14 +-
public_html/kn-IN/toc.html | 13 +-
public_html/ko-KR/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ko-KR/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ko-KR/opds-Fedora_Core.xml | 2 +-
.../ko-KR/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/ko-KR/opds-Fedora_Security_Team.xml | 2 +-
public_html/ko-KR/opds.xml | 14 +-
public_html/ko-KR/toc.html | 13 +-
public_html/ml-IN/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ml-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ml-IN/opds-Fedora_Core.xml | 2 +-
.../ml-IN/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/ml-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/ml-IN/opds.xml | 14 +-
public_html/ml-IN/toc.html | 13 +-
public_html/mr-IN/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/mr-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/mr-IN/opds-Fedora_Core.xml | 2 +-
.../mr-IN/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/mr-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/mr-IN/opds.xml | 14 +-
public_html/mr-IN/toc.html | 13 +-
public_html/nb-NO/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/nb-NO/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/nb-NO/opds-Fedora_Core.xml | 2 +-
.../nb-NO/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/nb-NO/opds-Fedora_Security_Team.xml | 2 +-
public_html/nb-NO/opds.xml | 14 +-
public_html/nb-NO/toc.html | 13 +-
public_html/nl-NL/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/nl-NL/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/nl-NL/opds-Fedora_Core.xml | 2 +-
.../nl-NL/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/nl-NL/opds-Fedora_Security_Team.xml | 2 +-
public_html/nl-NL/opds.xml | 14 +-
public_html/nl-NL/toc.html | 13 +-
public_html/opds.xml | 90 +-
public_html/or-IN/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/or-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/or-IN/opds-Fedora_Core.xml | 2 +-
.../or-IN/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/or-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/or-IN/opds.xml | 14 +-
public_html/or-IN/toc.html | 13 +-
public_html/pa-IN/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/pa-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pa-IN/opds-Fedora_Core.xml | 2 +-
.../pa-IN/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/pa-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/pa-IN/opds.xml | 14 +-
public_html/pa-IN/toc.html | 13 +-
public_html/pl-PL/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/pl-PL/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pl-PL/opds-Fedora_Core.xml | 2 +-
.../pl-PL/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/pl-PL/opds-Fedora_Security_Team.xml | 2 +-
public_html/pl-PL/opds.xml | 14 +-
public_html/pl-PL/toc.html | 13 +-
public_html/pt-BR/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/pt-BR/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pt-BR/opds-Fedora_Core.xml | 2 +-
.../pt-BR/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/pt-BR/opds-Fedora_Security_Team.xml | 2 +-
public_html/pt-BR/opds.xml | 14 +-
public_html/pt-BR/toc.html | 13 +-
public_html/pt-PT/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/pt-PT/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pt-PT/opds-Fedora_Core.xml | 2 +-
.../pt-PT/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/pt-PT/opds-Fedora_Security_Team.xml | 2 +-
public_html/pt-PT/opds.xml | 14 +-
public_html/pt-PT/toc.html | 13 +-
public_html/ro/Site_Statistics.html | 6 +-
.../ro/opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ro/opds-Fedora.xml | 2 +-
.../ro/opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ro/opds-Fedora_Core.xml | 2 +-
public_html/ro/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/ro/opds-Fedora_Security_Team.xml | 2 +-
public_html/ro/opds.xml | 14 +-
public_html/ro/toc.html | 13 +-
public_html/ru-RU/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ru-RU/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ru-RU/opds-Fedora_Core.xml | 2 +-
.../ru-RU/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/ru-RU/opds-Fedora_Security_Team.xml | 2 +-
public_html/ru-RU/opds.xml | 14 +-
public_html/ru-RU/toc.html | 13 +-
public_html/sk-SK/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/sk-SK/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sk-SK/opds-Fedora_Core.xml | 2 +-
.../sk-SK/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/sk-SK/opds-Fedora_Security_Team.xml | 2 +-
public_html/sk-SK/opds.xml | 14 +-
public_html/sk-SK/toc.html | 13 +-
public_html/sr-Latn-RS/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/sr-Latn-RS/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sr-Latn-RS/opds-Fedora_Core.xml | 2 +-
.../sr-Latn-RS/opds-Fedora_Draft_Documentation.xml | 21 +-
.../sr-Latn-RS/opds-Fedora_Security_Team.xml | 2 +-
public_html/sr-Latn-RS/opds.xml | 14 +-
public_html/sr-Latn-RS/toc.html | 13 +-
public_html/sr-RS/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/sr-RS/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sr-RS/opds-Fedora_Core.xml | 2 +-
.../sr-RS/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/sr-RS/opds-Fedora_Security_Team.xml | 2 +-
public_html/sr-RS/opds.xml | 14 +-
public_html/sr-RS/toc.html | 13 +-
public_html/sv-SE/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/sv-SE/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sv-SE/opds-Fedora_Core.xml | 2 +-
.../sv-SE/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/sv-SE/opds-Fedora_Security_Team.xml | 2 +-
public_html/sv-SE/opds.xml | 14 +-
public_html/sv-SE/toc.html | 13 +-
public_html/ta-IN/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ta-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ta-IN/opds-Fedora_Core.xml | 2 +-
.../ta-IN/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/ta-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/ta-IN/opds.xml | 14 +-
public_html/ta-IN/toc.html | 13 +-
public_html/te-IN/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/te-IN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/te-IN/opds-Fedora_Core.xml | 2 +-
.../te-IN/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/te-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/te-IN/opds.xml | 14 +-
public_html/te-IN/toc.html | 13 +-
public_html/toc.html | 40 +-
public_html/uk-UA/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/uk-UA/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/uk-UA/opds-Fedora_Core.xml | 2 +-
.../uk-UA/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/uk-UA/opds-Fedora_Security_Team.xml | 2 +-
public_html/uk-UA/opds.xml | 14 +-
public_html/uk-UA/toc.html | 13 +-
public_html/zh-CN/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/zh-CN/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/zh-CN/opds-Fedora_Core.xml | 2 +-
.../zh-CN/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/zh-CN/opds-Fedora_Security_Team.xml | 2 +-
public_html/zh-CN/opds.xml | 14 +-
public_html/zh-CN/toc.html | 13 +-
public_html/zh-TW/Site_Statistics.html | 6 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/zh-TW/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/zh-TW/opds-Fedora_Core.xml | 2 +-
.../zh-TW/opds-Fedora_Draft_Documentation.xml | 21 +-
public_html/zh-TW/opds-Fedora_Security_Team.xml | 2 +-
public_html/zh-TW/opds.xml | 14 +-
public_html/zh-TW/toc.html | 13 +-
2715 files changed, 72287 insertions(+), 805 deletions(-)
---
diff --git a/fedoradocs.db b/fedoradocs.db
index 5866266..6c7d653 100644
Binary files a/fedoradocs.db and b/fedoradocs.db differ
diff --git a/public_html/Sitemap b/public_html/Sitemap
index eb58882..0710a00 100644
--- a/public_html/Sitemap
+++ b/public_html/Sitemap
@@ -5113,6 +5113,30 @@
<priority>0.8</priority>
</url>
<url>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</loc>
+ <lastmod>2013-05-28</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html</loc>
+ <lastmod>2013-05-28</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html</loc>
+ <lastmod>2013-05-28</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf</loc>
+ <lastmod>2013-05-28</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
<loc>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</loc>
<lastmod>2011-09-11</lastmod>
<changefreq>monthly</changefreq>
diff --git a/public_html/as-IN/Site_Statistics.html b/public_html/as-IN/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/as-IN/Site_Statistics.html
+++ b/public_html/as-IN/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/as-IN/opds-Community_Services_Infrastructure.xml b/public_html/as-IN/opds-Community_Services_Infrastructure.xml
index 2a5272f..1474014 100644
--- a/public_html/as-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/as-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:01</updated>
+ <updated>2013-05-28T13:53:13</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora.xml b/public_html/as-IN/opds-Fedora.xml
index 9b910f6..03f4ce2 100644
--- a/public_html/as-IN/opds-Fedora.xml
+++ b/public_html/as-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:03</updated>
+ <updated>2013-05-28T13:53:14</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml
index f006d64..6ee72a4 100644
--- a/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:03</updated>
+ <updated>2013-05-28T13:53:15</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora_Core.xml b/public_html/as-IN/opds-Fedora_Core.xml
index 60623bb..08a52ce 100644
--- a/public_html/as-IN/opds-Fedora_Core.xml
+++ b/public_html/as-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:03</updated>
+ <updated>2013-05-28T13:53:15</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora_Draft_Documentation.xml b/public_html/as-IN/opds-Fedora_Draft_Documentation.xml
index 35601d8..c3d7976 100644
--- a/public_html/as-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/as-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:03</updated>
+ <updated>2013-05-28T13:53:15</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>as-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/as-IN/opds-Fedora_Security_Team.xml b/public_html/as-IN/opds-Fedora_Security_Team.xml
index 63f4da7..cbc1e1b 100644
--- a/public_html/as-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/as-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:03</updated>
+ <updated>2013-05-28T13:53:15</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds.xml b/public_html/as-IN/opds.xml
index 10e2fa8..f181cd3 100644
--- a/public_html/as-IN/opds.xml
+++ b/public_html/as-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/as-IN/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/as-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:02</updated>
+ <updated>2013-05-28T13:53:13</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:03</updated>
+ <updated>2013-05-28T13:53:14</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:03</updated>
+ <updated>2013-05-28T13:53:15</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:03</updated>
+ <updated>2013-05-28T13:53:15</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:03</updated>
+ <updated>2013-05-28T13:53:15</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:03</updated>
+ <updated>2013-05-28T13:53:15</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/as-IN/toc.html b/public_html/as-IN/toc.html
index 7fd9cae..6628a75 100644
--- a/public_html/as-IN/toc.html
+++ b/public_html/as-IN/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/bg-BG/Site_Statistics.html b/public_html/bg-BG/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/bg-BG/Site_Statistics.html
+++ b/public_html/bg-BG/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/bg-BG/opds-Community_Services_Infrastructure.xml b/public_html/bg-BG/opds-Community_Services_Infrastructure.xml
index 065e335..4555734 100644
--- a/public_html/bg-BG/opds-Community_Services_Infrastructure.xml
+++ b/public_html/bg-BG/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora.xml b/public_html/bg-BG/opds-Fedora.xml
index d2aebcd..791c8f2 100644
--- a/public_html/bg-BG/opds-Fedora.xml
+++ b/public_html/bg-BG/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml b/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
index a58ee2d..4431dde 100644
--- a/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora_Core.xml b/public_html/bg-BG/opds-Fedora_Core.xml
index 8a7cbe5..8e62b13 100644
--- a/public_html/bg-BG/opds-Fedora_Core.xml
+++ b/public_html/bg-BG/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml b/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml
index fc50722..8357e0d 100644
--- a/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>bg-BG</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/bg-BG/opds-Fedora_Security_Team.xml b/public_html/bg-BG/opds-Fedora_Security_Team.xml
index fa25034..1fe5a3c 100644
--- a/public_html/bg-BG/opds-Fedora_Security_Team.xml
+++ b/public_html/bg-BG/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds.xml b/public_html/bg-BG/opds.xml
index 1d56b25..fbbec84 100644
--- a/public_html/bg-BG/opds.xml
+++ b/public_html/bg-BG/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/bg-BG/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/bg-BG/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/bg-BG/toc.html b/public_html/bg-BG/toc.html
index 17e888d..a59649c 100644
--- a/public_html/bg-BG/toc.html
+++ b/public_html/bg-BG/toc.html
@@ -1480,7 +1480,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1562,6 +1564,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/bn-IN/Site_Statistics.html b/public_html/bn-IN/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/bn-IN/Site_Statistics.html
+++ b/public_html/bn-IN/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/bn-IN/opds-Community_Services_Infrastructure.xml b/public_html/bn-IN/opds-Community_Services_Infrastructure.xml
index 60b5b13..1127c8f 100644
--- a/public_html/bn-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/bn-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora.xml b/public_html/bn-IN/opds-Fedora.xml
index 130664c..7c9ce41 100644
--- a/public_html/bn-IN/opds-Fedora.xml
+++ b/public_html/bn-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml
index a945ae2..04b7822 100644
--- a/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora_Core.xml b/public_html/bn-IN/opds-Fedora_Core.xml
index ff2052c..3f3230f 100644
--- a/public_html/bn-IN/opds-Fedora_Core.xml
+++ b/public_html/bn-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml b/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml
index 37b2484..b1c8a70 100644
--- a/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>bn-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/bn-IN/opds-Fedora_Security_Team.xml b/public_html/bn-IN/opds-Fedora_Security_Team.xml
index ebaf493..275ad0d 100644
--- a/public_html/bn-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/bn-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds.xml b/public_html/bn-IN/opds.xml
index e3fcaa6..fa01dad 100644
--- a/public_html/bn-IN/opds.xml
+++ b/public_html/bn-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/bn-IN/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/bn-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/bn-IN/toc.html b/public_html/bn-IN/toc.html
index 1f31982..d1358a2 100644
--- a/public_html/bn-IN/toc.html
+++ b/public_html/bn-IN/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/bs-BA/Site_Statistics.html b/public_html/bs-BA/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/bs-BA/Site_Statistics.html
+++ b/public_html/bs-BA/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/bs-BA/opds-Community_Services_Infrastructure.xml b/public_html/bs-BA/opds-Community_Services_Infrastructure.xml
index 41aff82..d763a50 100644
--- a/public_html/bs-BA/opds-Community_Services_Infrastructure.xml
+++ b/public_html/bs-BA/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora.xml b/public_html/bs-BA/opds-Fedora.xml
index ec0d029..8dd5a57 100644
--- a/public_html/bs-BA/opds-Fedora.xml
+++ b/public_html/bs-BA/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:16</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml b/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml
index 38bd771..1a6940e 100644
--- a/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:16</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora_Core.xml b/public_html/bs-BA/opds-Fedora_Core.xml
index d259ec9..11f67ac 100644
--- a/public_html/bs-BA/opds-Fedora_Core.xml
+++ b/public_html/bs-BA/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:16</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml b/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml
index aa89257..e9443a9 100644
--- a/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:16</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>bs-BA</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/bs-BA/opds-Fedora_Security_Team.xml b/public_html/bs-BA/opds-Fedora_Security_Team.xml
index ede2868..a3e9350 100644
--- a/public_html/bs-BA/opds-Fedora_Security_Team.xml
+++ b/public_html/bs-BA/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:16</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds.xml b/public_html/bs-BA/opds.xml
index 4da179e..6b95e12 100644
--- a/public_html/bs-BA/opds.xml
+++ b/public_html/bs-BA/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/bs-BA/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:16</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/bs-BA/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:16</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:16</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:16</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:16</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:16</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/bs-BA/toc.html b/public_html/bs-BA/toc.html
index a91967c..dd46c23 100644
--- a/public_html/bs-BA/toc.html
+++ b/public_html/bs-BA/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/ca-ES/Site_Statistics.html b/public_html/ca-ES/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/ca-ES/Site_Statistics.html
+++ b/public_html/ca-ES/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/ca-ES/opds-Community_Services_Infrastructure.xml b/public_html/ca-ES/opds-Community_Services_Infrastructure.xml
index 4ca55b8..38c0a7f 100644
--- a/public_html/ca-ES/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ca-ES/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:16</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora.xml b/public_html/ca-ES/opds-Fedora.xml
index d4b7bc9..81e9e1a 100644
--- a/public_html/ca-ES/opds-Fedora.xml
+++ b/public_html/ca-ES/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:16</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml b/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml
index c3b3d59..b978145 100644
--- a/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:16</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora_Core.xml b/public_html/ca-ES/opds-Fedora_Core.xml
index 6f8314f..514d090 100644
--- a/public_html/ca-ES/opds-Fedora_Core.xml
+++ b/public_html/ca-ES/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:16</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml b/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml
index 444ef11..6b7af4b 100644
--- a/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:16</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>ca-ES</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/ca-ES/opds-Fedora_Security_Team.xml b/public_html/ca-ES/opds-Fedora_Security_Team.xml
index dd3ede7..ff250ec 100644
--- a/public_html/ca-ES/opds-Fedora_Security_Team.xml
+++ b/public_html/ca-ES/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:16</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds.xml b/public_html/ca-ES/opds.xml
index f6f4284..5ff5e4a 100644
--- a/public_html/ca-ES/opds.xml
+++ b/public_html/ca-ES/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ca-ES/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:16</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/ca-ES/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:16</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:16</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:16</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:16</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:16</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:16</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ca-ES/toc.html b/public_html/ca-ES/toc.html
index bd9b226..c2f7140 100644
--- a/public_html/ca-ES/toc.html
+++ b/public_html/ca-ES/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/cs-CZ/Site_Statistics.html b/public_html/cs-CZ/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/cs-CZ/Site_Statistics.html
+++ b/public_html/cs-CZ/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/cs-CZ/opds-Community_Services_Infrastructure.xml b/public_html/cs-CZ/opds-Community_Services_Infrastructure.xml
index f6fcb2b..2b3c14c 100644
--- a/public_html/cs-CZ/opds-Community_Services_Infrastructure.xml
+++ b/public_html/cs-CZ/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:16</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora.xml b/public_html/cs-CZ/opds-Fedora.xml
index 2d17616..baabce8 100644
--- a/public_html/cs-CZ/opds-Fedora.xml
+++ b/public_html/cs-CZ/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:16</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml b/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml
index c58c19c..1874db2 100644
--- a/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:16</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora_Core.xml b/public_html/cs-CZ/opds-Fedora_Core.xml
index 82b0412..c67495f 100644
--- a/public_html/cs-CZ/opds-Fedora_Core.xml
+++ b/public_html/cs-CZ/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:16</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml b/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml
index 8b18fe9..7b7e8ae 100644
--- a/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:16</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>cs-CZ</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/cs-CZ/opds-Fedora_Security_Team.xml b/public_html/cs-CZ/opds-Fedora_Security_Team.xml
index 44f8101..d65156b 100644
--- a/public_html/cs-CZ/opds-Fedora_Security_Team.xml
+++ b/public_html/cs-CZ/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:17</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds.xml b/public_html/cs-CZ/opds.xml
index 1590929..f6ae7b5 100644
--- a/public_html/cs-CZ/opds.xml
+++ b/public_html/cs-CZ/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/cs-CZ/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:17</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/cs-CZ/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:16</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:16</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:16</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:16</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:16</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:17</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/cs-CZ/toc.html b/public_html/cs-CZ/toc.html
index d2707c4..ba8c2ca 100644
--- a/public_html/cs-CZ/toc.html
+++ b/public_html/cs-CZ/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/da-DK/Site_Statistics.html b/public_html/da-DK/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/da-DK/Site_Statistics.html
+++ b/public_html/da-DK/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/da-DK/opds-Community_Services_Infrastructure.xml b/public_html/da-DK/opds-Community_Services_Infrastructure.xml
index 52d6a4a..9bfd814 100644
--- a/public_html/da-DK/opds-Community_Services_Infrastructure.xml
+++ b/public_html/da-DK/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:17</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora.xml b/public_html/da-DK/opds-Fedora.xml
index f06891f..fdb9005 100644
--- a/public_html/da-DK/opds-Fedora.xml
+++ b/public_html/da-DK/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:17</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml b/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml
index 924154d..3294ff8 100644
--- a/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:17</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora_Core.xml b/public_html/da-DK/opds-Fedora_Core.xml
index 9a2b354..f084457 100644
--- a/public_html/da-DK/opds-Fedora_Core.xml
+++ b/public_html/da-DK/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:17</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora_Draft_Documentation.xml b/public_html/da-DK/opds-Fedora_Draft_Documentation.xml
index 2847c63..a41c2f5 100644
--- a/public_html/da-DK/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/da-DK/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:17</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>da-DK</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/da-DK/opds-Fedora_Security_Team.xml b/public_html/da-DK/opds-Fedora_Security_Team.xml
index 56d1778..dbbbdde 100644
--- a/public_html/da-DK/opds-Fedora_Security_Team.xml
+++ b/public_html/da-DK/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:17</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds.xml b/public_html/da-DK/opds.xml
index f1e0833..4c79c05 100644
--- a/public_html/da-DK/opds.xml
+++ b/public_html/da-DK/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/da-DK/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:17</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/da-DK/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:17</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:17</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:17</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:17</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:17</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:17</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/da-DK/toc.html b/public_html/da-DK/toc.html
index a31001f..7bb4d1d 100644
--- a/public_html/da-DK/toc.html
+++ b/public_html/da-DK/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/de-DE/Site_Statistics.html b/public_html/de-DE/Site_Statistics.html
index e8f9289..f535d02 100644
--- a/public_html/de-DE/Site_Statistics.html
+++ b/public_html/de-DE/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Sprachen gesamt: </b>44<br />
- <b>Pakete gesamt: </b>861
+ <b>Pakete gesamt: </b>862
</div>
</body>
</html>
diff --git a/public_html/de-DE/opds-Community_Services_Infrastructure.xml b/public_html/de-DE/opds-Community_Services_Infrastructure.xml
index 120cd84..65417f3 100644
--- a/public_html/de-DE/opds-Community_Services_Infrastructure.xml
+++ b/public_html/de-DE/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:17</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora.xml b/public_html/de-DE/opds-Fedora.xml
index 393a960..6a9cfa9 100644
--- a/public_html/de-DE/opds-Fedora.xml
+++ b/public_html/de-DE/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:17</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml b/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml
index 8f704bb..55f716f 100644
--- a/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:17</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora_Core.xml b/public_html/de-DE/opds-Fedora_Core.xml
index 9e8cbdb..423e479 100644
--- a/public_html/de-DE/opds-Fedora_Core.xml
+++ b/public_html/de-DE/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:17</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora_Draft_Documentation.xml b/public_html/de-DE/opds-Fedora_Draft_Documentation.xml
index 49f08a6..c00ce64 100644
--- a/public_html/de-DE/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/de-DE/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:17</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>de-DE</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/de-DE/opds-Fedora_Security_Team.xml b/public_html/de-DE/opds-Fedora_Security_Team.xml
index 6d1836b..6241d58 100644
--- a/public_html/de-DE/opds-Fedora_Security_Team.xml
+++ b/public_html/de-DE/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:17</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds.xml b/public_html/de-DE/opds.xml
index cb2c262..0cfb88a 100644
--- a/public_html/de-DE/opds.xml
+++ b/public_html/de-DE/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/de-DE/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:17</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/de-DE/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:17</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:17</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:17</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:17</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:17</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:17</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/de-DE/toc.html b/public_html/de-DE/toc.html
index 8cb0a0b..6b2fd8e 100644
--- a/public_html/de-DE/toc.html
+++ b/public_html/de-DE/toc.html
@@ -1536,7 +1536,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Nicht übersetzt</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1618,6 +1620,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/el-GR/Site_Statistics.html b/public_html/el-GR/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/el-GR/Site_Statistics.html
+++ b/public_html/el-GR/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/el-GR/opds-Community_Services_Infrastructure.xml b/public_html/el-GR/opds-Community_Services_Infrastructure.xml
index 791db41..24a31be 100644
--- a/public_html/el-GR/opds-Community_Services_Infrastructure.xml
+++ b/public_html/el-GR/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:18</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora.xml b/public_html/el-GR/opds-Fedora.xml
index 4e02424..eaf0e92 100644
--- a/public_html/el-GR/opds-Fedora.xml
+++ b/public_html/el-GR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:18</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml b/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml
index cf6e3e4..7de1757 100644
--- a/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:18</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora_Core.xml b/public_html/el-GR/opds-Fedora_Core.xml
index f7b5328..d91c785 100644
--- a/public_html/el-GR/opds-Fedora_Core.xml
+++ b/public_html/el-GR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:18</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora_Draft_Documentation.xml b/public_html/el-GR/opds-Fedora_Draft_Documentation.xml
index 2d60040..aa5ff18 100644
--- a/public_html/el-GR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/el-GR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:18</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>el-GR</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/el-GR/opds-Fedora_Security_Team.xml b/public_html/el-GR/opds-Fedora_Security_Team.xml
index 24f4e57..53e1332 100644
--- a/public_html/el-GR/opds-Fedora_Security_Team.xml
+++ b/public_html/el-GR/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:18</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds.xml b/public_html/el-GR/opds.xml
index 74e091d..ef1a3d8 100644
--- a/public_html/el-GR/opds.xml
+++ b/public_html/el-GR/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/el-GR/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:18</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/el-GR/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:18</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:18</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:18</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:18</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:18</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:18</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/el-GR/toc.html b/public_html/el-GR/toc.html
index d42be5e..c1cdfd1 100644
--- a/public_html/el-GR/toc.html
+++ b/public_html/el-GR/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/en-US/Fedora/19/epub/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.epub b/public_html/en-US/Fedora/19/epub/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.epub
new file mode 100644
index 0000000..4657ca4
Binary files /dev/null and b/public_html/en-US/Fedora/19/epub/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.epub differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/common.css b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/common.css
new file mode 100644
index 0000000..d7dc3f2
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/common.css
@@ -0,0 +1,1528 @@
+* {
+ widows: 2 !important;
+ orphans: 2 !important;
+}
+
+body, h1, h2, h3, h4, h5, h6, pre, li, div {
+ line-height: 1.29em;
+}
+
+body {
+ background-color: white;
+ margin:0 auto;
+ font-family: "liberation sans", "Myriad ", "Bitstream Vera Sans", "Lucida Grande", "Luxi Sans", "Trebuchet MS", helvetica, verdana, arial, sans-serif;
+ font-size:12px;
+ max-width:55em;
+ color:black;
+}
+
+body.toc_embeded {
+ /*for web hosting system only*/
+ margin-left: 300px;
+}
+
+object.toc, iframe.toc {
+ /*for web hosting system only*/
+ border-style:none;
+ position:fixed;
+ width:290px;
+ height:99.99%;
+ top:0;
+ left:0;
+ z-index: 100;
+ border-style:none;
+ border-right:1px solid #999;
+}
+
+/* Hide web menu */
+
+body.notoc {
+ margin-left: 3em;
+}
+
+iframe.notoc {
+ border-style:none;
+ border: none;
+ padding: 0em;
+ position:fixed;
+ width: 21px;
+ height: 29px;
+ top: 0px;
+ left:0;
+ overflow: hidden;
+ margin: 0em;
+ margin-left: -3px;
+}
+/* End hide web menu */
+
+/* desktop styles */
+body.desktop {
+ margin-left: 26em;
+}
+
+body.desktop .book > .toc {
+ display:block;
+ width:24em;
+ height:99%;
+ position:fixed;
+ overflow:auto;
+ top:0px;
+ left:0px;
+ padding-left:1em;
+ background-color:#EEEEEE;
+}
+
+.toc {
+ line-height:1.35em;
+}
+
+.toc .glossary,
+.toc .chapter, .toc .appendix {
+ margin-top:1em;
+}
+
+.toc .part {
+ margin-top:1em;
+ display:block;
+}
+
+span.glossary,
+span.appendix {
+ display:block;
+ margin-top:0.5em;
+}
+
+div {
+ padding-top:0px;
+}
+
+div.section {
+ padding-top:1em;
+}
+
+p, div.para, div.formalpara {
+ padding-top:0px;
+ margin-top:0.3em;
+ padding-bottom:0px;
+ margin-bottom:1em;
+}
+
+/*Links*/
+a {
+ outline: none;
+}
+
+a:link {
+ text-decoration:none;
+ border-bottom: 1px dotted ;
+ color:#3366cc;
+}
+
+a:visited {
+ text-decoration:none;
+ border-bottom: 1px dotted ;
+ color:#003366;
+}
+
+div.longdesc-link {
+ float:right;
+ color:#999;
+}
+
+.toc a, .qandaset a {
+ font-weight:normal;
+ border:none;
+}
+
+.toc a:hover, .qandaset a:hover
+{
+ border-bottom: 1px dotted;
+}
+
+/*headings*/
+h1, h2, h3, h4, h5, h6 {
+ color: #336699;
+ margin-top: 0em;
+ margin-bottom: 0em;
+ background-color: transparent;
+ page-break-inside: avoid;
+ page-break-after: avoid;
+}
+
+h1 {
+ font-size:2.0em;
+}
+
+.titlepage h1.title {
+ font-size: 3.0em;
+ padding-top: 1em;
+ text-align:left;
+}
+
+.book > .titlepage h1.title {
+ text-align:center;
+}
+
+.article > .titlepage h1.title {
+ text-align:center;
+}
+
+.set .titlepage > div > div > h1.title {
+ text-align:center;
+}
+
+.producttitle {
+ margin-top: 0em;
+ margin-bottom: 0em;
+ font-size: 3.0em;
+ font-weight: bold;
+ background: #003d6e url(../images/h1-bg.png) top left repeat-x;
+ color: white;
+ text-align: center;
+ padding: 0.7em;
+}
+
+.titlepage .corpauthor {
+ margin-top: 1em;
+ text-align: center;
+}
+
+.section h1.title {
+ font-size: 1.6em;
+ padding: 0em;
+ color: #336699;
+ text-align: left;
+ background: white;
+}
+
+h2 {
+ font-size:1.6em;
+}
+
+
+h2.subtitle, h3.subtitle {
+ margin-top: 1em;
+ margin-bottom: 1em;
+ font-size: 1.4em;
+ text-align: center;
+}
+
+.preface > div > div > div > h2.title {
+ margin-top: 1em;
+ font-size: 2.0em;
+}
+
+.appendix h2 {
+ margin-top: 1em;
+ font-size: 2.0em;
+}
+
+
+
+h3 {
+ font-size:1.3em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+h4 {
+ font-size:1.1em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+
+h5 {
+ font-size:1em;
+}
+
+h6 {
+ font-size:1em;
+}
+
+h5.formalpara {
+ font-size:1em;
+ margin-top:2em;
+ margin-bottom:.8em;
+}
+
+.abstract h6 {
+ margin-top:1em;
+ margin-bottom:.5em;
+ font-size:2em;
+}
+
+/*element rules*/
+hr {
+ border-collapse: collapse;
+ border-style:none;
+ border-top: 1px dotted #ccc;
+ width:100%;
+ margin-top: 3em;
+}
+
+/* web site rules */
+ul.languages, .languages li {
+ display:inline;
+ padding:0em;
+}
+
+.languages li a {
+ padding:0em .5em;
+ text-decoration: none;
+}
+
+.languages li p, .languages li div.para {
+ display:inline;
+}
+
+.languages li a:link, .languages li a:visited {
+ color:#444;
+}
+
+.languages li a:hover, .languages li a:focus, .languages li a:active {
+ color:black;
+}
+
+ul.languages {
+ display:block;
+ background-color:#eee;
+ padding:.5em;
+}
+
+/*supporting stylesheets*/
+
+/*unique to the webpage only*/
+.books {
+ position:relative;
+}
+
+.versions li {
+ width:100%;
+ clear:both;
+ display:block;
+}
+
+a.version {
+ font-size:2em;
+ text-decoration:none;
+ width:100%;
+ display:block;
+ padding:1em 0em .2em 0em;
+ clear:both;
+}
+
+a.version:before {
+ content:"Version";
+ font-size:smaller;
+}
+
+a.version:visited, a.version:link {
+ color:#666;
+}
+
+a.version:focus, a.version:hover {
+ color:black;
+}
+
+.books {
+ display:block;
+ position:relative;
+ clear:both;
+ width:100%;
+}
+
+.books li {
+ display:block;
+ width:200px;
+ float:left;
+ position:relative;
+ clear: none ;
+}
+
+.books .html {
+ width:170px;
+ display:block;
+}
+
+.books .pdf {
+ position:absolute;
+ left:170px;
+ top:0px;
+ font-size:smaller;
+}
+
+.books .pdf:link, .books .pdf:visited {
+ color:#555;
+}
+
+.books .pdf:hover, .books .pdf:focus {
+ color:#000;
+}
+
+.books li a {
+ text-decoration:none;
+}
+
+.books li a:hover {
+ color:black;
+}
+
+/*products*/
+.products li {
+ display: block;
+ width:300px;
+ float:left;
+}
+
+.products li a {
+ width:300px;
+ padding:.5em 0em;
+}
+
+.products ul {
+ clear:both;
+}
+
+/*revision history*/
+.revhistory {
+ display:block;
+}
+
+.revhistory table {
+ background-color:transparent;
+ border-color:#fff;
+ padding:0em;
+ margin: 0;
+ border-collapse:collapse;
+ border-style:none;
+}
+
+.revhistory td {
+ text-align :left;
+ padding:0em;
+ border: none;
+ border-top: 1px solid #fff;
+ font-weight: bold;
+}
+
+.revhistory .simplelist td {
+ font-weight: normal;
+}
+
+.revhistory .simplelist {
+ margin-bottom: 1.5em;
+ margin-left: 1em;
+}
+
+.revhistory table th {
+ display: none;
+}
+
+
+/*credits*/
+.authorgroup div {
+ clear:both;
+ text-align: center;
+}
+
+h3.author {
+ margin: 0em;
+ padding: 0em;
+ padding-top: 1em;
+}
+
+.authorgroup h4 {
+ padding: 0em;
+ margin: 0em;
+ padding-top: 1em;
+ margin-top: 1em;
+}
+
+.author,
+.editor,
+.translator,
+.othercredit,
+.contrib {
+ display: block;
+}
+
+.revhistory .author {
+ display: inline;
+}
+
+.othercredit h3 {
+ padding-top: 1em;
+}
+
+
+.othercredit {
+ margin:0em;
+ padding:0em;
+}
+
+.releaseinfo {
+ clear: both;
+}
+
+.copyright {
+ margin-top: 1em;
+}
+
+/* qanda sets */
+.answer {
+ margin-bottom:1em;
+ border-bottom:1px dotted #ccc;
+}
+
+.qandaset .toc {
+ border-bottom:1px dotted #ccc;
+}
+
+.question {
+ font-weight:bold;
+}
+
+.answer .data, .question .data {
+ padding-left: 2.6em;
+}
+
+.answer label, .question label {
+ float:left;
+ font-weight:bold;
+}
+
+/* inline syntax highlighting */
+.perl_Alert {
+ color: #0000ff;
+}
+
+.perl_BaseN {
+ color: #007f00;
+}
+
+.perl_BString {
+ color: #5C3566;
+}
+
+.perl_Char {
+ color: #ff00ff;
+}
+
+.perl_Comment {
+ color: #FF00FF;
+}
+
+
+.perl_DataType {
+ color: #0000ff;
+}
+
+
+.perl_DecVal {
+ color: #00007f;
+}
+
+
+.perl_Error {
+ color: #ff0000;
+}
+
+
+.perl_Float {
+ color: #00007f;
+}
+
+
+.perl_Function {
+ color: #007f00;
+}
+
+
+.perl_IString {
+ color: #5C3566;
+}
+
+
+.perl_Keyword {
+ color: #002F5D;
+}
+
+
+.perl_Operator {
+ color: #ffa500;
+}
+
+
+.perl_Others {
+ color: #b03060;
+}
+
+
+.perl_RegionMarker {
+ color: #96b9ff;
+}
+
+
+.perl_Reserved {
+ color: #9b30ff;
+}
+
+
+.perl_String {
+ color: #5C3566;
+}
+
+
+.perl_Variable {
+ color: #0000ff;
+}
+
+
+.perl_Warning {
+ color: #0000ff;
+}
+
+/*Lists*/
+ul {
+ padding-left:1.6em;
+ list-style-image:url(../images/dot.png);
+ list-style-type: circle;
+}
+
+ul ul {
+ list-style-image:url(../images/dot2.png);
+ list-style-type: circle;
+}
+
+ol {
+ list-style-image:none;
+ list-style-type: decimal;
+}
+
+ol ol {
+ list-style-type: lower-alpha;
+}
+
+ol.arabic {
+ list-style-type: decimal;
+}
+
+ol.loweralpha {
+ list-style-type: lower-alpha;
+}
+
+ol.lowerroman {
+ list-style-type: lower-roman;
+}
+
+ol.upperalpha {
+ list-style-type: upper-alpha;
+}
+
+ol.upperroman {
+ list-style-type: upper-roman;
+}
+
+dt {
+ font-weight:bold;
+ margin-bottom:0em;
+ padding-bottom:0em;
+}
+
+dd {
+ margin:0em;
+ margin-left:2em;
+ padding-top:0em;
+ padding-bottom: 1em;
+}
+
+li {
+ padding-top:0px;
+ margin-top:0em;
+ padding-bottom:0px;
+ margin-bottom:0.4em;
+}
+
+li p, li div.para {
+ padding-top:0px;
+ margin-top:0em;
+ padding-bottom:0px;
+ margin-bottom:0.3em;
+}
+
+/*images*/
+img {
+ display:block;
+ margin: 2em 0;
+}
+
+.inlinemediaobject, .inlinemediaobject img {
+ display:inline;
+ margin:0em;
+}
+
+.figure img {
+ display:block;
+ margin:0;
+ page-break-inside: avoid;
+}
+
+.figure .title {
+ margin:0em;
+ margin-bottom:2em;
+ padding:0px;
+}
+
+/*document modes*/
+.confidential {
+ background-color:#900;
+ color:White;
+ padding:.5em .5em;
+ text-transform:uppercase;
+ text-align:center;
+}
+
+.longdesc-link {
+ display:none;
+}
+
+.longdesc {
+ display:none;
+}
+
+.prompt {
+ padding:0em .3em;
+}
+
+/*user interface styles*/
+.screen .replaceable {
+}
+
+.guibutton, .guilabel {
+ font-family: "liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight: bold;
+ white-space: nowrap;
+}
+
+.example {
+ background-color: #ffffff;
+ border-left: 3px solid #aaaaaa;
+ padding-top: 1em;
+ padding-bottom: 0.1em;
+}
+
+.example h6 {
+ padding-left: 10px;
+}
+
+.example-contents {
+ padding-left: 10px;
+ background-color: #ffffff;
+}
+
+.example-contents .para {
+/* padding: 10px;*/
+}
+
+/*terminal/console text*/
+.computeroutput,
+.option {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight:bold;
+}
+
+.replaceable {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-style: italic;
+}
+
+.command, .filename, .keycap, .classname, .literal {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight:bold;
+}
+
+/* no bold in toc */
+.toc * {
+ font-weight: inherit;
+}
+
+pre {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ display:block;
+ background-color: #f5f5f5;
+ color: #000000;
+ border: 1px solid #aaaaaa;
+ margin-bottom: 0.3em;
+ padding:.5em 1em;
+ white-space: pre-wrap; /* css-3 */
+ white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
+ white-space: -pre-wrap; /* Opera 4-6 */
+ white-space: -o-pre-wrap; /* Opera 7 */
+ word-wrap: break-word; /* Internet Explorer 5.5+ */
+ font-size: 0.9em;
+}
+
+pre .replaceable,
+pre .keycap {
+}
+
+code {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+/* white-space: nowrap;*/
+ white-space: pre-wrap;
+ word-wrap: break-word;
+ font-weight:bold;
+}
+
+.parameter code {
+ display: inline;
+ white-space: pre-wrap; /* css-3 */
+ white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
+ white-space: -pre-wrap; /* Opera 4-6 */
+ white-space: -o-pre-wrap; /* Opera 7 */
+ word-wrap: break-word; /* Internet Explorer 5.5+ */
+}
+
+/*Notifications*/
+div.warning:before {
+ content:url(../images/warning.png);
+ padding-left: 5px;
+}
+
+div.note:before {
+ content:url(../images/note.png);
+ padding-left: 5px;
+}
+
+div.important:before {
+ content:url(../images/important.png);
+ padding-left: 5px;
+}
+
+div.warning, div.note, div.important {
+ color: black;
+ margin: 0em;
+ padding: 0em;
+ background: none;
+ background-color: white;
+ margin-bottom: 1em;
+ border-bottom: 1px solid #aaaaaa;
+ page-break-inside: avoid;
+}
+
+div.warning h2, div.note h2,div.important h2 {
+ margin: 0em;
+ padding: 0em;
+ color: #eeeeec;
+ padding-top: 0px;
+ padding-bottom: 0px;
+ height: 1.4em;
+ line-height: 1.4em;
+ font-size: 1.4em;
+ display:inline;
+}
+
+div.admonition_header {
+ clear: both;
+ margin: 0em;
+ padding: 0em;
+ margin-top: -3.3em;
+ padding-left: 58px;
+ line-height: 1.0em;
+ font-size: 1.0em;
+}
+
+div.warning div.admonition_header {
+ background: url(../images/red.png) top left repeat-x;
+ background-color: #590000;
+}
+
+div.note div.admonition_header {
+ background: url(../images/green.png) top right repeat-x;
+ background-color: #597800;
+}
+
+div.important div.admonition_header {
+ background: url(../images/yellow.png) top right repeat-x;
+ background-color: #a6710f;
+}
+
+div.warning p, div.warning div.para,
+div.note p, div.note div.para,
+div.important p, div.important div.para {
+ padding: 0em;
+ margin: 0em;
+}
+
+div.admonition {
+ border: none;
+ border-left: 1px solid #aaaaaa;
+ border-right: 1px solid #aaaaaa;
+ padding:0em;
+ margin:0em;
+ padding-top: 1.5em;
+ padding-bottom: 1em;
+ padding-left: 2em;
+ padding-right: 1em;
+ background-color: #eeeeec;
+ -moz-border-radius: 0px;
+ -webkit-border-radius: 0px;
+ border-radius: 0px;
+}
+
+/*Page Title*/
+#title {
+ display:block;
+ height:45px;
+ padding-bottom:1em;
+ margin:0em;
+}
+
+#title a.left{
+ display:inline;
+ border:none;
+}
+
+#title a.left img{
+ border:none;
+ float:left;
+ margin:0em;
+ margin-top:.7em;
+}
+
+#title a.right {
+ padding-bottom:1em;
+}
+
+#title a.right img {
+ border:none;
+ float:right;
+ margin:0em;
+ margin-top:.7em;
+}
+
+/*Table*/
+div.table {
+ page-break-inside: avoid;
+}
+
+table {
+ border:1px solid #6c614b;
+ width:100%;
+ border-collapse:collapse;
+}
+
+table.simplelist, .calloutlist table {
+ border-style: none;
+}
+
+table th {
+ text-align:left;
+ background-color:#6699cc;
+ padding:.3em .5em;
+ color:white;
+}
+
+table td {
+ padding:.15em .5em;
+}
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+table th p:first-child, table td p:first-child, table li p:first-child,
+table th div.para:first-child, table td div.para:first-child, table li div.para:first-child {
+ margin-top:0em;
+ padding-top:0em;
+ display:inline;
+}
+
+th, td {
+ border-style:none;
+ vertical-align: top;
+ border: 1px solid #000;
+}
+
+.simplelist th, .simplelist td {
+ border: none;
+}
+
+table table td {
+ border-bottom:1px dotted #aaa;
+ background-color:white;
+ padding:.6em 0em;
+}
+
+table table {
+ border:1px solid white;
+}
+
+td.remarkval {
+ color:#444;
+}
+
+td.fieldval {
+ font-weight:bold;
+}
+
+.lbname, .lbtype, .lbdescr, .lbdriver, .lbhost {
+ color:white;
+ font-weight:bold;
+ background-color:#999;
+ width:120px;
+}
+
+td.remarkval {
+ width:230px;
+}
+
+td.tname {
+ font-weight:bold;
+}
+
+th.dbfield {
+ width:120px;
+}
+
+th.dbtype {
+ width:70px;
+}
+
+th.dbdefault {
+ width:70px;
+}
+
+th.dbnul {
+ width:70px;
+}
+
+th.dbkey {
+ width:70px;
+}
+
+span.book {
+ margin-top:4em;
+ display:block;
+ font-size:11pt;
+}
+
+span.book a{
+ font-weight:bold;
+}
+span.chapter {
+ display:block;
+ margin-top:0.5em;
+}
+
+table.simplelist td, .calloutlist table td {
+ border-style: none;
+}
+
+/*Breadcrumbs*/
+#breadcrumbs ul li.first:before {
+ content:" ";
+}
+
+#breadcrumbs {
+ color:#900;
+ padding:3px;
+ margin-bottom:25px;
+}
+
+#breadcrumbs ul {
+ margin-left:0;
+ padding-left:0;
+ display:inline;
+ border:none;
+}
+
+#breadcrumbs ul li {
+ margin-left:0;
+ padding-left:2px;
+ border:none;
+ list-style:none;
+ display:inline;
+}
+
+#breadcrumbs ul li:before {
+ content:"\0020 \0020 \0020 \00BB \0020";
+ color:#333;
+}
+
+/*index*/
+.glossary h3,
+.index h3 {
+ font-size: 2em;
+ color:#aaa;
+ margin:0em;
+}
+
+.indexdiv {
+ margin-bottom:1em;
+}
+
+.glossary dt,
+.index dt {
+ color:#444;
+ padding-top:.5em;
+}
+
+.glossary dl dl dt,
+.index dl dl dt {
+ color:#777;
+ font-weight:normal;
+ padding-top:0em;
+}
+
+.index dl dl dt:before {
+ content:"- ";
+ color:#ccc;
+}
+
+/*changes*/
+.footnote {
+ font-size: .7em;
+ margin:0em;
+ color:#222;
+}
+
+table .footnote {
+}
+
+sup {
+ color:#999;
+ margin:0em;
+ padding:0em;
+ line-height: .4em;
+ font-size: 1em;
+ padding-left:0em;
+}
+
+.footnote {
+ position:relative;
+}
+
+.footnote sup {
+ color:#e3dcc0;
+ position:absolute;
+ left: .4em;
+}
+
+.footnote sup a:link,
+.footnote sup a:visited {
+ color:#92917d;
+ text-decoration:none;
+}
+
+.footnote:hover sup a {
+ text-decoration:none;
+}
+
+.footnote p,.footnote div.para {
+ padding-left:2em;
+}
+
+.footnote a:link,
+.footnote a:visited {
+ color:#00537c;
+}
+
+.footnote a:hover {
+}
+
+/**/
+div.chapter {
+ margin-top:3em;
+ page-break-inside: avoid;
+}
+
+div.preface {
+ page-break-inside: avoid;
+}
+
+div.section {
+ margin-top:1em;
+ page-break-inside: auto;
+}
+
+div.note .replaceable,
+div.important .replaceable,
+div.warning .replaceable,
+div.note .keycap,
+div.important .keycap,
+div.warning .keycap
+{
+}
+
+ul li p:last-child, ul li div.para:last-child {
+ margin-bottom:0em;
+ padding-bottom:0em;
+}
+
+/*document navigation*/
+.docnav a, .docnav strong {
+ border:none;
+ text-decoration:none;
+ font-weight:normal;
+}
+
+.docnav {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+ position:relative;
+ width:100%;
+ padding-bottom:2em;
+ padding-top:1em;
+ border-top:1px dotted #ccc;
+}
+
+.docnav li {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+ display:inline;
+ font-size:.8em;
+}
+
+.docnav li:before {
+ content:" ";
+}
+
+.docnav li.previous, .docnav li.next {
+ position:absolute;
+ top:1em;
+}
+
+.docnav li.up, .docnav li.home {
+ margin:0em 1.5em;
+}
+
+.docnav li.previous {
+ left:0px;
+ text-align:left;
+}
+
+.docnav li.next {
+ right:0px;
+ text-align:right;
+}
+
+.docnav li.previous strong, .docnav li.next strong {
+ height:22px;
+ display:block;
+}
+
+.docnav {
+ margin:0 auto;
+ text-align:center;
+}
+
+.docnav li.next a strong {
+ background: url(../images/stock-go-forward.png) top right no-repeat;
+ padding-top:3px;
+ padding-bottom:4px;
+ padding-right:28px;
+ font-size:1.2em;
+}
+
+.docnav li.previous a strong {
+ background: url(../images/stock-go-back.png) top left no-repeat;
+ padding-top:3px;
+ padding-bottom:4px;
+ padding-left:28px;
+ padding-right:0.5em;
+ font-size:1.2em;
+}
+
+.docnav li.home a strong {
+ background: url(../images/stock-home.png) top left no-repeat;
+ padding:5px;
+ padding-left:28px;
+ font-size:1.2em;
+}
+
+.docnav li.up a strong {
+ background: url(../images/stock-go-up.png) top left no-repeat;
+ padding:5px;
+ padding-left:28px;
+ font-size:1.2em;
+}
+
+.docnav a:link, .docnav a:visited {
+ color:#666;
+}
+
+.docnav a:hover, .docnav a:focus, .docnav a:active {
+ color:black;
+}
+
+.docnav a {
+ max-width: 10em;
+ overflow:hidden;
+}
+
+.docnav a:link strong {
+ text-decoration:none;
+}
+
+.docnav {
+ margin:0 auto;
+ text-align:center;
+}
+
+ul.docnav {
+ margin-bottom: 1em;
+}
+/* Reports */
+.reports ul {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+}
+
+.reports li{
+ margin:0em;
+ padding:0em;
+}
+
+.reports li.odd {
+ background-color: #eeeeee;
+ margin:0em;
+ padding:0em;
+}
+
+.reports dl {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ float:right;
+ margin-right: 17em;
+ margin-top:-1.3em;
+}
+
+.reports dt {
+ display:inline;
+ margin:0em;
+ padding:0em;
+}
+
+.reports dd {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ padding-right:.5em;
+}
+
+.reports h2, .reports h3{
+ display:inline;
+ padding-right:.5em;
+ font-size:10pt;
+ font-weight:normal;
+}
+
+.reports div.progress {
+ display:inline;
+ float:right;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ margin:0em;
+ margin-top:-1.3em;
+ padding:0em;
+ border:none;
+}
+
+/*uniform*/
+body.results, body.reports {
+ max-width:57em ;
+ padding:0em;
+}
+
+/*Progress Bar*/
+div.progress {
+ display:block;
+ float:left;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ height:1em;
+}
+
+div.progress span {
+ height:1em;
+ float:left;
+}
+
+div.progress span.translated {
+ background:#6c3 url(../images/shine.png) top left repeat-x;
+}
+
+div.progress span.fuzzy {
+ background:#ff9f00 url(../images/shine.png) top left repeat-x;
+}
+
+
+/*Results*/
+
+.results ul {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+}
+
+.results li{
+ margin:0em;
+ padding:0em;
+}
+
+.results li.odd {
+ background-color: #eeeeee;
+ margin:0em;
+ padding:0em;
+}
+
+.results dl {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ float:right;
+ margin-right: 17em;
+ margin-top:-1.3em;
+}
+
+.results dt {
+ display:inline;
+ margin:0em;
+ padding:0em;
+}
+
+.results dd {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ padding-right:.5em;
+}
+
+.results h2, .results h3 {
+ display:inline;
+ padding-right:.5em;
+ font-size:10pt;
+ font-weight:normal;
+}
+
+.results div.progress {
+ display:inline;
+ float:right;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ margin:0em;
+ margin-top:-1.3em;
+ padding:0em;
+ border:none;
+}
+
+/* Dirty EVIL Mozilla hack for round corners */
+pre {
+ -moz-border-radius:11px;
+ -webkit-border-radius:11px;
+ border-radius: 11px;
+ page-break-inside: avoid;
+}
+
+.example {
+ -moz-border-radius:0px;
+ -webkit-border-radius:0px;
+ border-radius: 0px;
+ page-break-inside: avoid;
+}
+
+.package, .citetitle {
+ font-style: italic;
+}
+
+.titlepage .edition {
+ color: #336699;
+ background-color: transparent;
+ margin-top: 1em;
+ margin-bottom: 1em;
+ font-size: 1.4em;
+ font-weight: bold;
+ text-align: center;
+}
+
+span.remark {
+ background-color: #ff00ff;
+}
+
+.draft {
+ background-image: url(../images/watermark-draft.png);
+ background-repeat: repeat-y;
+ background-position: center;
+}
+
+.foreignphrase {
+ font-style: inherit;
+}
+
+dt {
+ clear:both;
+}
+
+dt img {
+ border-style: none;
+ max-width: 112px;
+}
+
+dt object {
+ max-width: 112px;
+}
+
+dt .inlinemediaobject, dt object {
+ display: inline;
+ float: left;
+ margin-bottom: 1em;
+ padding-right: 1em;
+ width: 112px;
+}
+
+dl:after {
+ display: block;
+ clear: both;
+ content: "";
+}
+
+.toc dd {
+ padding-bottom: 0em;
+ margin-bottom: 1em;
+ padding-left: 1.3em;
+ margin-left: 0em;
+}
+
+div.toc > dl > dt {
+ padding-bottom: 0em;
+ margin-bottom: 0em;
+ margin-top: 1em;
+}
+
+
+.strikethrough {
+ text-decoration: line-through;
+}
+
+.underline {
+ text-decoration: underline;
+}
+
+.calloutlist img, .callout {
+ padding: 0em;
+ margin: 0em;
+ width: 12pt;
+ display: inline;
+ vertical-align: middle;
+}
+
+.stepalternatives {
+ list-style-image: none;
+ list-style-type: none;
+}
+
+
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/default.css b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/default.css
new file mode 100644
index 0000000..bf38ebb
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/default.css
@@ -0,0 +1,3 @@
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/lang.css b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/lang.css
new file mode 100644
index 0000000..81c3115
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/lang.css
@@ -0,0 +1,2 @@
+/* place holder */
+
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/menu.css b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/menu.css
new file mode 100644
index 0000000..f574cc5
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/menu.css
@@ -0,0 +1,48 @@
+a:link {
+ color:#0066cc;
+}
+
+a:visited {
+ color:#6699cc;
+}
+
+h1,h2,h3,h4,h5,h6 {
+ color:#a70000;
+}
+
+div.producttitle {
+ color:#a70000;
+}
+
+.section h1.title {
+ color:#a70000;
+}
+
+table {
+ border:1px solid #aaa;
+}
+
+table th {
+ background-color:#900;
+}
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+.revhistory table th {
+ color:#a70000;
+}
+
+.titlepage .edition {
+ color: #a70000;
+}
+
+span.remark{
+ background-color: #ffff00;
+}
+
+.home{
+ color: #a70000;
+}
+
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/overrides.css b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/overrides.css
new file mode 100644
index 0000000..0498ded
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/overrides.css
@@ -0,0 +1,46 @@
+a:link {
+ color:#0066cc;
+}
+
+a:visited {
+ color:#6699cc;
+}
+
+h1,h2,h3,h4,h5,h6 {
+ color:#a70000;
+}
+
+div.producttitle {
+/* background: #a70000 url(../images/h1-bg.png) top left repeat; */
+ color:#a70000;
+}
+
+.section h1.title {
+ color:#a70000;
+}
+
+
+
+table {
+ border:1px solid #aaa;
+}
+
+table th {
+ background-color:#900;
+}
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+.revhistory table th {
+ color:#a70000;
+}
+
+.titlepage .edition {
+ color: #a70000;
+}
+
+span.remark{
+ background-color: #ffff00;
+}
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/pdf.css b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/pdf.css
new file mode 100644
index 0000000..cbeab47
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/pdf.css
@@ -0,0 +1,138 @@
+
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
+
+/* Cover Page styles */
+
+html {
+ height: 260mm;
+}
+
+body.cover {
+ height: 100%;
+ background-color: white;
+/* margin-left: 10em;
+ margin-right: 10em;
+*/ padding: 0px;
+ font-family: "overpass", sans-serif;
+ font-weight:300;
+}
+
+body.cover > div {
+ height: 100%;
+}
+
+body.cover * {
+ text-align: left;
+ box-sizing: border-box;
+ -moz-box-sizing: border-box;
+ -webkit-box-sizing: border-box;
+}
+
+body.cover div.logo {
+ height: 30%;
+ background-position: 50% 0%;
+ margin-top: 15mm;
+ background-image: url(../images/title_logo.svg);
+ background-repeat: no-repeat;
+}
+
+
+body.cover div.leader {
+ display: inline-block;
+ font-size: 40px;
+ font-weight: 600;
+ margin-top: 2em;
+}
+
+body.cover div.product {
+ display: inline;
+}
+
+
+body.cover div.edition {
+ display: inline;
+}
+
+body.cover div.docname {
+ font-size: 40px;
+ font-weight: 600;
+ height: 10%;
+}
+
+body.cover div.subtitle {
+ height: 20%;
+ font-weight:300;
+ font-size: 20px;
+ color: black;
+ border-top: .1em solid black;
+ padding-top: 40px;
+}
+body.cover div.authors {
+}
+
+body.cover div.author {
+ float: left;
+ min-width: 33%;
+ font-weight: 300;
+ font-size: 20px;
+}
+
+div.draft {
+ background-image: url(../images/watermark-draft.png);
+ background-repeat: repeat-y;
+ background-position: center;
+}
+
+body.titlepages {
+ text-align: left;
+}
+
+body.titlepages > div {
+ height: 100%;
+}
+body.titlepages .legalnotice {
+ page-break-before: always;
+}
+
+body.titlepages .title {
+ font-size: 20px;
+ color: black;
+ font-weight: normal;
+ margin-bottom: 0.1em;
+}
+
+body.titlepages .subtitle {
+ color: black;
+ font-weight: normal;
+ text-align: left;
+ font-size: 12px;
+ margin-top: 0.1em;
+ margin-bottom: 2em;
+}
+
+body.titlepages .contributor {
+ margin-bottom: 1em;
+ font-size: 12px;
+}
+
+body.titlepages .abstract {
+ page-break-before: avoid !important;
+ font-size: 14px;
+}
+
+body.titlepages h1 {
+ color: black;
+ font-size: 14px;
+ font-weight: normal;
+}
+
+body.titlepages .editors h1,
+body.titlepages .othercredit h1,
+body.titlepages .legalnotice h1,
+body.titlepages .keywords h1,
+body.titlepages .abstract h1 {
+ font-weight: bold;
+}
+
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/print.css b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/print.css
new file mode 100644
index 0000000..773d8ae
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/print.css
@@ -0,0 +1,16 @@
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
+
+#tocframe {
+ display: none;
+}
+
+body.toc_embeded {
+ margin-left: 30px;
+}
+
+.producttitle {
+ color: #336699;
+}
+
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/1.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/1.png
new file mode 100644
index 0000000..270707b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/1.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/1.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/1.svg
new file mode 100644
index 0000000..0a7036e
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/1.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;fill:#000000;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 17.853468,22.008438 -2.564941,0 0,-7.022461 c -5e-6,-0.143873 -5e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224122,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08854,0.08302 -0.17432,0.157723 -0.257324,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/10.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/10.png
new file mode 100644
index 0000000..ec548f3
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/10.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/10.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/10.svg
new file mode 100644
index 0000000..d1c32c7
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/10.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/11.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/11.png
new file mode 100644
index 0000000..f59d84b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/11.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/11.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/11.svg
new file mode 100644
index 0000000..872d14a
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/11.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/12.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/12.png
new file mode 100644
index 0000000..c8a3906
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/12.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/12.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/12.svg
new file mode 100644
index 0000000..6bc95d2
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/12.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c 0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141 0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801 0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648 -0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083 -1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l -1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/13.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/13.png
new file mode 100644
index 0000000..2db6743
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/13.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/13.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/13.svg
new file mode 100644
index 0000000..cf105bc
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/13.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883 -0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579 2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273 -0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534 -1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l 0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961 0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414 0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289 -0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032 -0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269 0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026 -0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l -1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868 0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393 1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/14.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/14.png
new file mode 100644
index 0000000..1a12fb3
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/14.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/14.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/14.svg
new file mode 100644
index 0000000..1009bce
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/14.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/15.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/15.png
new file mode 100644
index 0000000..2532d13
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/15.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/15.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/15.svg
new file mode 100644
index 0000000..52daf8d
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/15.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2839"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2841"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/16.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/16.png
new file mode 100644
index 0000000..3b3f17f
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/16.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/16.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/16.svg
new file mode 100644
index 0000000..95dedc2
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/16.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/17.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/17.png
new file mode 100644
index 0000000..d0f12f7
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/17.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/17.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/17.svg
new file mode 100644
index 0000000..7b3e327
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/17.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/18.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/18.png
new file mode 100644
index 0000000..ed2f1fe
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/18.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/18.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/18.svg
new file mode 100644
index 0000000..fc744d5
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/18.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/19.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/19.png
new file mode 100644
index 0000000..a145b4a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/19.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/19.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/19.svg
new file mode 100644
index 0000000..69c6f5f
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/19.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/2.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/2.png
new file mode 100644
index 0000000..126f8fd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/2.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/2.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/2.svg
new file mode 100644
index 0000000..15424b2
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/2.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.89546,22.008438 -8.143066,0 0,-1.784668 2.855468,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979493,-1.0708 0.293289,-0.326492 0.545079,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.373529,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.17431,-0.666821 0.174316,-1.037598 -6e-6,-0.409496 -0.124517,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827313,0.522958 -1.270019,0.921386 l -1.394531,-1.651855 c 0.249022,-0.226877 0.509113,-0.442698 0.780273,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079102,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319824,-0.1494141 0.58105,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187012,0.6889648 0.326489,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.893727 0.265625,1.41
9433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/20.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/20.png
new file mode 100644
index 0000000..b23618f
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/20.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/20.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/20.svg
new file mode 100644
index 0000000..7abd11e
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/20.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/21.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/21.png
new file mode 100644
index 0000000..91b602b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/21.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/21.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/21.svg
new file mode 100644
index 0000000..8d33472
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/21.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/22.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/22.png
new file mode 100644
index 0000000..33e0374
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/22.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/22.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/22.svg
new file mode 100644
index 0000000..0224965
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/22.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c 0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141 0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801 0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648 -0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083 -1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l -1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/23.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/23.png
new file mode 100644
index 0000000..cc961c1
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/23.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/23.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/23.svg
new file mode 100644
index 0000000..72609f4
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/23.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883 -0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579 2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273 -0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534 -1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l 0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961 0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414 0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289 -0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032 -0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269 0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026 -0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l -1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868 0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393 1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/24.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/24.png
new file mode 100644
index 0000000..17b1531
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/24.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/24.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/24.svg
new file mode 100644
index 0000000..5b34c33
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/24.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/25.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/25.png
new file mode 100644
index 0000000..193686c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/25.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/25.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/25.svg
new file mode 100644
index 0000000..4f57373
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/25.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/26.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/26.png
new file mode 100644
index 0000000..e8bf82a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/26.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/26.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/26.svg
new file mode 100644
index 0000000..aff5a90
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/26.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/27.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/27.png
new file mode 100644
index 0000000..06dfc67
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/27.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/27.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/27.svg
new file mode 100644
index 0000000..0769006
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/27.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/28.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/28.png
new file mode 100644
index 0000000..065ce1a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/28.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/28.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/28.svg
new file mode 100644
index 0000000..60cf157
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/28.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/29.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/29.png
new file mode 100644
index 0000000..8f28d5b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/29.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/29.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/29.svg
new file mode 100644
index 0000000..6dc6635
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/29.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/3.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/3.png
new file mode 100644
index 0000000..9e3ae40
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/3.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/3.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/3.svg
new file mode 100644
index 0000000..2e88abd
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/3.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.422316,12.587051 c -9e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.23243,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315437,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.392911,0.332031 -0.890957,0.592122 -1.494141,0.780273 -0.597661,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267255,-0.05534 -1.842773,-0.166016 -0.575523,-0.105143 -1.112306,-0.268392 -1.610352,-0.489746 l 0,-2.183105 c 0.249023,0.132815 0.511881,0.249025 0.788574,0.348632 0.276692,0.09961 0.553384,0.185387 0.830079,0.257325 0.27669,0.06641 0.547848,0.116212 0.813476,0.149414 0.271156,0.0332 0.525713,0.04981 0.763672,0.0498 0.475907,2e-6 0.871577,-0.04427 1.187012,-0.132812 0.315424,-
0.08854 0.567214,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320957,-0.351397 0.398437,-0.572754 0.083,-0.226885 0.124506,-0.473141 0.124512,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.265631,-0.376297 -0.498047,-0.514648 -0.226893,-0.143876 -0.525721,-0.254553 -0.896484,-0.332032 -0.370773,-0.07747 -0.827315,-0.116205 -1.369629,-0.116211 l -0.863281,0 0,-1.801269 0.846679,0 c 0.509111,7e-6 0.932451,-0.04426 1.27002,-0.132813 0.33756,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.43164,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.68897,-0.365224 -1.27002,-0.365234 -0.265629,10e-6 -0.514652,0.02768 -0.74707,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193688,0.07748 -0.373538,0.166026 -0.539551,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439941,0.282227 l -1.294922,-1.70
9961 c 0.232421,-0.171538 0.484211,-0.329253 0.755371,-0.473145 0.276691,-0.143868 0.575519,-0.26838 0.896484,-0.373535 0.320961,-0.1106647 0.666827,-0.1964393 1.037598,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492506,0.1272911 0.913079,0.3154421 1.261718,0.5644531 0.348626,0.243501 0.617017,0.545096 0.805176,0.904786 0.193677,0.354177 0.290519,0.760914 0.290528,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/30.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/30.png
new file mode 100644
index 0000000..d583185
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/30.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/30.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/30.svg
new file mode 100644
index 0000000..717ae1c
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/30.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/31.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/31.png
new file mode 100644
index 0000000..9146925
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/31.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/31.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/31.svg
new file mode 100644
index 0000000..25c7b52
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/31.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/32.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/32.png
new file mode 100644
index 0000000..cbc972e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/32.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/32.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/32.svg
new file mode 100644
index 0000000..79866e8
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/32.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c 0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141 0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801 0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648 -0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083 -1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l -1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/33.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/33.png
new file mode 100644
index 0000000..7c1ab6a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/33.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/33.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/33.svg
new file mode 100644
index 0000000..01c3222
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/33.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883 -0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579 2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273 -0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534 -1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l 0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961 0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414 0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289 -0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032 -0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269 0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026 -0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l -1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868 0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393 1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/34.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/34.png
new file mode 100644
index 0000000..2585ddc
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/34.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/34.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/34.svg
new file mode 100644
index 0000000..cf9cf7c
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/34.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/35.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/35.png
new file mode 100644
index 0000000..86ff09c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/35.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/35.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/35.svg
new file mode 100644
index 0000000..948ed84
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/35.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/36.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/36.png
new file mode 100644
index 0000000..c4a7f79
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/36.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/36.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/36.svg
new file mode 100644
index 0000000..cff32b5
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/36.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/37.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/37.png
new file mode 100644
index 0000000..91cf6ae
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/37.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/37.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/37.svg
new file mode 100644
index 0000000..6694ee4
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/37.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/38.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/38.png
new file mode 100644
index 0000000..882f8cd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/38.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/38.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/38.svg
new file mode 100644
index 0000000..26ded93
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/38.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/39.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/39.png
new file mode 100644
index 0000000..cc0726d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/39.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/39.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/39.svg
new file mode 100644
index 0000000..082c1b1
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/39.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/4.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/4.png
new file mode 100644
index 0000000..266e714
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/4.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/4.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/4.svg
new file mode 100644
index 0000000..25888e4
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/4.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 20.078077,19.493301 -1.460937,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460937,0 0,1.992187 m -3.959472,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09962,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.12175,0.2601 -0.262863,0.520191 -0.42334,0.780274 l -2.025391,3.071289 2.75586,0"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/40.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/40.png
new file mode 100644
index 0000000..b92fd2f
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/40.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/40.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/40.svg
new file mode 100644
index 0000000..33ef96a
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/40.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.440535,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.0136719,0 0,-1.784668 5.1547849,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262863,0.520191 -0.42334,0.780274 l -2.0253904,3.071289 2.7558594,0"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/5.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/5.png
new file mode 100644
index 0000000..94153bd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/5.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/5.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/5.svg
new file mode 100644
index 0000000..7d1dabd
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/5.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 16.035597,14.255508 c 0.520177,8e-6 1.004388,0.08025 1.452637,0.240723 0.448235,0.160489 0.838371,0.395678 1.17041,0.705566 0.332023,0.309903 0.592114,0.697272 0.780273,1.16211 0.188143,0.459315 0.282218,0.987797 0.282227,1.585449 -9e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.204761,0.520184 -0.506356,0.962892 -0.904785,1.328125 -0.398445,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261724,0.290528 -2.025391,0.290528 -0.304365,0 -0.60596,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863281,-0.124512 -0.271161,-0.04981 -0.531252,-0.116211 -0.780274,-0.199219 -0.24349,-0.08301 -0.464844,-0.17985 -0.664062,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672363,0.31543 0.254556,0.09408 0.517414,0.177086 0.788574,0.249024 0.276691,0.06641 0.553383,0.121746 0.830078,0.166015 0.27669,0.03874 0.539548,0.05811 0.788575,0.05811 0.741532,2e-6 1.305984,-0.152179 1.693359,-0.456543 0.387364,-0.309893 0.5810
49,-0.799639 0.581055,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751465,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320966,0.03874 -0.481445,0.06641 -0.154951,0.02768 -0.304365,0.05811 -0.448242,0.09131 -0.143883,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456542,-6.1840821 6.408204,0 0,2.1748051 -4.183594,0 -0.199219,2.382324 c 0.17708,-0.03873 0.381832,-0.07747 0.614258,-0.116211 0.237951,-0.03873 0.542313,-0.0581 0.913086,-0.05811"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/6.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/6.png
new file mode 100644
index 0000000..792940e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/6.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/6.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/6.svg
new file mode 100644
index 0000000..3ab7c39
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/6.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 11.702589,16.853653 c -10e-7,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.0664,-0.575514 0.179849,-1.126132 0.340332,-1.651856 0.166014,-0.531241 0.387368,-1.023753 0.664062,-1.477539 0.282225,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431638,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603186,-0.1936727 1.305984,-0.2905151 2.108399,-0.2905274 0.116204,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.138339,0.00555 0.276685,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251782,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210295,-0.04979 -0.434416,-0.08853 -0.672364,-0.116211 -0.232429,-0.03319 -0.467617,-0.04979 -0.705566,-0.0498 -0.747076,1e-5 -1.361334,0.09408 -1.842774,0.282226 -0.481449,0.182627 -0.863285,0.439951 -1.145507,0.771973 -0.28223,0.33204 -0.484216,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.215821,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243486,-0.384596 0.39843
7,-0.556153 0.160478,-0.177076 0.345862,-0.32649 0.556153,-0.448242 0.210282,-0.127271 0.44547,-0.22688 0.705566,-0.298828 0.26562,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419433,0.257324 0.420566,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.15494,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282226,1.768066 -0.182626,0.520184 -0.445484,0.962892 -0.788575,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643554,0.282227 -0.597661,0 -1.15658,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.973961,-0.542317 -1.361328,-0.979492 -0.381838,-0.437173 -0.683433,-0.987791 -0.904785,-1.651856 -0.215822,-0.669593 -0.323732,-1.460933 -0.323731,-2.374023 m 4.216797,3.270508 c 0.226883,2e-6 0.431635,-0.0415 0.614258,-0.124512 0.188145,-0.08854 0.348627,-0.218585 0.481445,-0.390137 0.13834,-0.17708 0.243483,-0.3
98434 0.31543,-0.664062 0.07747,-0.265622 0.116204,-0.581051 0.116211,-0.946289 -7e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243496,-0.343094 -0.617031,-0.514643 -1.120606,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.39014,0.229661 -0.53955,0.390137 -0.149418,0.160487 -0.265629,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.31543,0.755371 0.143876,0.221357 0.318193,0.401207 0.522949,0.539551 0.210282,0.138349 0.453772,0.207522 0.730469,0.20752"
+ id="path2846"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/7.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/7.png
new file mode 100644
index 0000000..59eaefd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/7.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/7.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/7.svg
new file mode 100644
index 0000000..ab9cb5d
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/7.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 12.789991,22.008438 4.316407,-9.960937 -5.578125,0 0,-2.1582035 8.367187,0 0,1.6103515 -4.424316,10.508789 -2.681153,0"
+ id="path2832"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/8.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/8.png
new file mode 100644
index 0000000..6aad94b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/8.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/8.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/8.svg
new file mode 100644
index 0000000..23b1e20
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/8.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.761671,9.7149811 c 0.503576,1.23e-5 0.979487,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337558,0.243501 0.60595,0.547862 0.805176,0.913086 0.199211,0.365244 0.29882,0.794118 0.298828,1.286621 -8e-6,0.365243 -0.05535,0.697274 -0.166015,0.996094 -0.110686,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193693,0.237963 -0.423348,0.451017 -0.688965,0.639161 -0.265632,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.633619,0.362473 0.937988,0.572754 0.309888,0.210292 0.583814,0.448247 0.821777,0.713867 0.237948,0.260096 0.428866,0.55339 0.572754,0.879883 0.143872,0.326501 0.215812,0.691735 0.21582,1.095703 -8e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478686,0.758139 -0.838379,1.045898 -0.359707,0.287761 -0.791348,0.509115 -1.294921,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651856,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.9379
9,-0.362467 -1.286621,-0.639161 -0.348634,-0.276691 -0.614259,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265626,-0.857744 -0.265625,-1.361328 -10e-7,-0.415035 0.06087,-0.78857 0.182617,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498047,-0.896485 0.210285,-0.265619 0.456541,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271162,-0.171543 -0.525719,-0.356927 -0.763672,-0.556152 -0.237958,-0.204746 -0.445477,-0.428866 -0.622559,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -10e-7,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478677,-0.669585 0.821778,-0.913086 0.343096,-0.249012 0.738766,-0.434396 1.187011,-0.5561527 0.448239,-0.1217326 0.918616,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.107911,0.614258 0.07194,0.18262 0.17708,0.340334 0.315429,0.473145 0.143877,0.132814 0.32
096,0.237957 0.53125,0.315429 0.210283,0.07194 0.453772,0.107912 0.730469,0.10791 0.581049,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.43164,-1.087402 -6e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218593,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.320969,-0.307125 -0.514648,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 15.662062,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664063,0.398438 -0.199222,0.138351 -0.370772,0.293299 -0.514648,0.464844 -0.13835,0.16602 -0.24626,0.348637 -0.323731,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.701661,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514649,0.08301 -0.154952,0.05535 -0.290531,0.13559 -0.406738,0.240723 -0.110681,0.105153 -0.199223,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.31543
8 0.282226,0.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160478,0.09962 0.32926,0.199226 0.506348,0.298828 0.171545,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154943,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.12174,-0.138338 0.218582,-0.293286 0.290528,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.157721,-0.284984 -0.273926,-0.390137 -0.116217,-0.105133 -0.254563,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/9.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/9.png
new file mode 100644
index 0000000..2478355
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/9.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/9.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/9.svg
new file mode 100644
index 0000000..80db11b
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/9.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.829054,15.052383 c -9e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340333,1.651856 -0.160489,0.525719 -0.381843,1.018232 -0.664062,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426113,0.332032 -0.940761,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.30046,0.282227 -2.108399,0.282227 -0.116214,0 -0.243492,-0.0028 -0.381836,-0.0083 -0.138348,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273927,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237954,0.02767 0.478676,0.04151 0.722168,0.0415 0.747067,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.481441,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.282221,-0.337562 0.481439,-0.738766 0.597657,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.107911,0 c -0.110683,0.199225 -0.243495,0.384609 -0.398437,0.556153 -0.
154954,0.171554 -0.337571,0.320968 -0.547852,0.448242 -0.210291,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.265629,0.07194 -0.56169,0.107914 -0.888183,0.10791 -0.52572,4e-6 -0.998864,-0.08577 -1.419434,-0.257324 -0.420575,-0.171545 -0.777508,-0.420568 -1.070801,-0.74707 -0.287761,-0.326492 -0.509115,-0.727696 -0.664062,-1.203614 -0.154949,-0.475904 -0.232423,-1.020988 -0.232422,-1.635253 -10e-7,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453774,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758135,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043127,-0.2905151 1.651855,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520176,0.210298 0.971184,0.534028 1.353027,0.971192 0.381829,0.437185 0.683423,0.990569 0.904786,1.660156 0.221345,0.669605 0.332022,1.458178 0.332031,2.365722 m -4.216797,-3.262207 c -0.226892,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188154,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132815,0.17155
9 -0.237959,0.392913 -0.315429,0.664062 -0.07194,0.265634 -0.107914,0.581063 -0.107911,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373536,1.394532 0.249019,0.343105 0.625321,0.514654 1.128906,0.514648 0.254552,6e-6 0.486974,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.53955,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124506,-0.401197 0.124512,-0.605958 -6e-6,-0.282218 -0.03598,-0.561677 -0.10791,-0.838378 -0.06641,-0.282218 -0.171556,-0.534008 -0.31543,-0.755372 -0.138352,-0.226878 -0.312668,-0.409495 -0.522949,-0.547851 -0.204758,-0.138336 -0.44548,-0.207509 -0.722168,-0.20752"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/bkgrnd_greydots.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/bkgrnd_greydots.png
new file mode 100644
index 0000000..2333a6d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/bkgrnd_greydots.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/bullet_arrowblue.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/bullet_arrowblue.png
new file mode 100644
index 0000000..c235534
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/bullet_arrowblue.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/documentation.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/documentation.png
new file mode 100644
index 0000000..7ae45bd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/documentation.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/dot.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/dot.png
new file mode 100644
index 0000000..36a6859
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/dot.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/dot2.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/dot2.png
new file mode 100644
index 0000000..40aff92
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/dot2.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/green.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/green.png
new file mode 100644
index 0000000..ebb3c24
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/green.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/h1-bg.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/h1-bg.png
new file mode 100644
index 0000000..31397b5
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/h1-bg.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/image_left.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/image_left.png
new file mode 100644
index 0000000..ecd4856
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/image_left.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/image_right.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/image_right.png
new file mode 100644
index 0000000..7ae45bd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/image_right.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/important.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/important.png
new file mode 100644
index 0000000..eb42966
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/important.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/important.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/important.svg
new file mode 100644
index 0000000..064c783
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/important.svg
@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg2">
+ <defs
+ id="defs5" />
+ <path
+ d="M 255.25,-411.29002 L 261.86798,-400.85887 L 273.83367,-397.7882 L 265.95811,-388.27072 L 266.73534,-375.94179 L 255.25,-380.49082 L 243.76466,-375.94179 L 244.54189,-388.27072 L 236.66633,-397.7882 L 248.63202,-400.85887 L 255.25,-411.29002 z "
+ transform="matrix(1.1071323,0,0,1.1071323,-258.4137,459.98052)"
+ style="fill:#2e3436;fill-opacity:1;stroke:#2e3436;stroke-width:4.25880718;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1"
+ id="path4450" />
+ <path
+ d="M 255.25,-411.29002 L 261.86798,-400.85887 L 273.83367,-397.7882 L 265.95811,-388.27072 L 266.73534,-375.94179 L 255.25,-380.49082 L 243.76466,-375.94179 L 244.54189,-388.27072 L 236.66633,-397.7882 L 248.63202,-400.85887 L 255.25,-411.29002 z "
+ transform="matrix(1.1071323,0,0,1.1071323,-258.4137,459.98052)"
+ style="fill:#fac521;fill-opacity:1;stroke-width:3.4070456;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1"
+ id="path4452" />
+ <path
+ d="M 24.175987,4.476098 L 16.980534,16.087712 L 3.9317841,19.443104 L 16.980534,20.076901 L 24.175987,10.383543 L 31.408721,20.076901 L 44.457471,19.443104 L 31.468862,16.027571 L 24.175987,4.476098 z "
+ style="fill:#feeaab;fill-opacity:1;stroke-width:3.4070456;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1"
+ id="path4531" />
+ <path
+ d="M 12.456856,24.055852 C 11.65845,24.299685 14.436112,29.177769 14.436112,32.041127 C 14.436112,37.343117 13.010825,39.831516 15.971742,37.364645 C 18.711008,35.08244 21.184735,34.873512 24.195894,34.873512 C 27.207053,34.873512 29.646656,35.08244 32.38592,37.364645 C 35.346837,39.831516 33.921551,37.343117 33.92155,32.041127 C 33.92155,28.223316 38.868232,20.827013 33.682674,25.591482 C 31.458295,27.635233 27.413886,29.481744 24.195894,29.481744 C 20.977903,29.481744 16.933493,27.635233 14.709113,25.591482 C 13.412724,24.400365 12.722992,23.974574 12.456856,24.055852 z "
+ style="fill:#fcd867;fill-opacity:1;stroke-width:3.4070456;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1"
+ id="path2185" />
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/note.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/note.png
new file mode 100644
index 0000000..2b421d2
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/note.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/note.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/note.svg
new file mode 100644
index 0000000..abe5a60
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/note.svg
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg2">
+ <defs
+ id="defs5" />
+ <path
+ d="M 30.27396,4.1232594 L 18.765811,4.1232594 C 11.476786,4.1232594 5.5574109,10.546411 5.5574109,19.960741 C 5.5574109,24.746615 7.0844878,29.075948 9.5403943,32.177328 C 9.4616811,32.681104 9.414455,33.200619 9.414455,33.720144 C 9.414455,39.308917 13.554865,43.591015 18.891751,44.267966 C 17.506371,42.693663 16.656245,40.914707 16.656245,38.616218 C 16.656245,38.01799 16.719219,37.419752 16.82942,36.837262 C 17.459135,36.963202 18.104599,37.026176 18.750063,37.026176 L 30.258211,37.026176 C 37.547237,37.026176 43.466612,29.39081 43.466612,19.960741 C 43.466612,10.530672 37.578724,4.1232594 30.27396,4.1232594 z "
+ style="fill:#2e3436;fill-opacity:1;stroke:#2e3436;stroke-width:4.7150631;stroke-miterlimit:4;stroke-dasharray:none"
+ id="path4317" />
+ <path
+ d="M 30.27396,4.1232594 L 18.765811,4.1232594 C 11.476786,4.1232594 5.5574109,10.546411 5.5574109,19.960741 C 5.5574109,24.746615 7.0844878,29.075948 9.5403943,32.177328 C 9.4616811,32.681104 9.414455,33.200619 9.414455,33.720144 C 9.414455,39.308917 13.554865,43.591015 18.891751,44.267966 C 17.506371,42.693663 16.656245,40.914707 16.656245,38.616218 C 16.656245,38.01799 16.719219,37.419752 16.82942,36.837262 C 17.459135,36.963202 18.104599,37.026176 18.750063,37.026176 L 30.258211,37.026176 C 37.547237,37.026176 43.466612,29.39081 43.466612,19.960741 C 43.466612,10.530672 37.578724,4.1232594 30.27396,4.1232594 z "
+ style="fill:#bfdce8;fill-opacity:1"
+ id="path142" />
+ <path
+ d="M 19.200879,5.5648899 C 12.490241,5.5648899 7.0622987,11.295775 7.0622987,19.690323 C 7.0622987,22.890926 7.8418023,25.879852 9.1910836,28.332288 C 8.6113289,26.599889 8.2852163,24.667826 8.2852163,22.673336 C 8.2852163,14.629768 13.495502,9.1620492 19.925575,9.1620492 L 30.071259,9.1620492 C 36.515213,9.1620492 41.711609,14.616311 41.711609,22.673336 C 41.864688,21.709218 41.983366,20.710908 41.983366,19.690323 C 41.983366,11.281743 36.524624,5.5648899 29.799492,5.5648899 L 19.200879,5.5648899 z "
+ style="fill:#ffffff"
+ id="path2358" />
+ <path
+ d="M 28.241965,33.725087 L 20.792252,33.725087 C 16.073756,33.725087 12.241894,32.944782 12.241894,26.850486 C 12.241894,25.10387 12.368512,23.572125 15.515722,23.567487 L 33.508301,23.540969 C 36.182481,23.537028 36.782127,24.950794 36.782127,26.850486 C 36.782127,32.95497 32.970649,33.725087 28.241965,33.725087 z "
+ style="fill:#d0ecf9;fill-opacity:1"
+ id="path2173" />
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/red.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/red.png
new file mode 100644
index 0000000..d32d5e2
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/red.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/redhat-logo.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/redhat-logo.svg
new file mode 100644
index 0000000..1001776
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/redhat-logo.svg
@@ -0,0 +1,94 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://web.resource.org/cc/"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:xlink="http://www.w3.org/1999/xlink"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ width="300"
+ height="140"
+ id="svg2812"
+ sodipodi:version="0.32"
+ inkscape:version="0.45+devel"
+ version="1.0"
+ sodipodi:docname="redhat-logo.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape">
+ <defs
+ id="defs3" />
+ <sodipodi:namedview
+ inkscape:document-units="mm"
+ id="base"
+ pagecolor="#ffffff"
+ bordercolor="#666666"
+ borderopacity="1.0"
+ inkscape:pageopacity="0.0"
+ inkscape:pageshadow="2"
+ inkscape:zoom="1"
+ inkscape:cx="174.26394"
+ inkscape:cy="40.358463"
+ inkscape:current-layer="layer1"
+ inkscape:window-width="722"
+ inkscape:window-height="523"
+ inkscape:window-x="71"
+ inkscape:window-y="636"
+ width="300px"
+ height="140px" />
+ <metadata
+ id="metadata4">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <g
+ inkscape:label="Layer 1"
+ inkscape:groupmode="layer"
+ id="layer1"
+ transform="translate(-13.714282,-252.57246)">
+ <g
+ transform="matrix(2.1166666,0,0,2.1166666,-32.193429,187.76029)"
+ id="shadowman">
+ <path
+ d="M 55.68466,68.503937 C 55.68466,79.688581 46.617715,88.755526 35.433071,88.755526 C 24.248427,88.755526 15.181482,79.688581 15.181482,68.503937 C 15.181482,57.319293 24.248427,48.252348 35.433071,48.252348 C 46.617715,48.252348 55.68466,57.319293 55.68466,68.503937 z"
+ transform="matrix(1.10693,0,0,1.10693,5.005761,-12.00975)"
+ style="fill:#ffffff"
+ id="path4548" />
+ <path
+ d="M 147.81332,72.126073 C 147.81332,73.329962 147.86057,74.57586 148.03519,75.740362 L 146.64882,75.740362 L 146.42826,73.559712 L 146.35605,73.559712 C 145.61822,74.733404 143.92333,76.086957 141.50635,76.086957 C 138.4461,76.086957 137.02164,73.933874 137.02164,71.904202 C 137.02164,68.394942 140.11998,66.27862 146.30878,66.34295 L 146.30878,65.937278 C 146.30878,64.432747 146.01471,61.431561 142.41879,61.45388 C 141.08756,61.45388 139.70118,61.810976 138.5997,62.588186 L 138.1205,61.494579 C 139.51083,60.551948 141.20703,60.180411 142.58291,60.180411 C 146.97178,60.180411 147.81201,63.475677 147.81201,66.194597 L 147.81201,72.126073 L 147.81332,72.126073 z M 146.30878,67.609855 C 142.99645,67.514016 138.62333,68.015527 138.62333,71.667888 C 138.62333,73.853791 140.06616,74.835806 141.65077,74.835806 C 144.1859,74.835806 145.62742,73.266945 146.15124,71.786044 C 146.26152,71.460456 146.3101,71.134869 146.3101,70.874924 L 146.3101,67.609855 L 146.30878,67.609855 z
M 153.80387,57.175286 L 153.80387,60.527004 L 158.13891,60.527004 L 158.13891,61.747959 L 153.80387,61.747959 L 153.80387,71.635066 C 153.80387,73.568902 154.40385,74.780665 156.03835,74.780665 C 156.82343,74.780665 157.37877,74.676951 157.76606,74.541727 L 157.94856,75.707542 C 157.45754,75.912347 156.76567,76.072514 155.84798,76.072514 C 154.73862,76.072514 153.81831,75.723296 153.22358,74.994662 C 152.53566,74.195133 152.29934,72.917726 152.29934,71.365932 L 152.29934,61.746646 L 149.7314,61.746646 L 149.7314,60.525692 L 152.29934,60.525692 L 152.29934,57.729312 L 153.80387,57.175286 z M 129.02767,60.179099 C 127.87105,60.179099 126.8339,60.512563 125.96348,61.052146 C 125.05891,61.581226 124.3224,62.399135 123.88522,63.247239 L 123.8222,63.247239 L 123.8222,55.719331 L 122.31767,55.309721 L 122.31767,75.740362 L 123.8222,75.740362 L 123.8222,66.437475 C 123.8222,65.819121 123.86947,65.39113 124.02832,64.938196 C 124.67818,63.046372 126.45974,61.493265 128.61545,61.49326
5 C 131.72953,61.493265 132.80739,63.990315 132.80739,66.730242 L 132.80739,75.73905 L 134.31191,75.73905 L 134.31191,66.564822 C 134.31191,60.899855 130.4692,60.179099 129.02767,60.179099 z"
+ id="path620" />
+ <path
+ d="M 78.208384,65.270348 C 78.208384,63.205228 78.16506,61.686255 78.08235,60.311696 L 81.460325,60.311696 L 81.604739,63.240675 L 81.713705,63.240675 C 82.473849,61.069213 84.273772,59.961164 85.938472,59.961164 C 86.319199,59.961164 86.541071,59.976918 86.853532,60.045187 L 86.853532,63.719867 C 86.488557,63.648972 86.147215,63.609587 85.677213,63.609587 C 83.819525,63.609587 82.528988,64.792469 82.181081,66.560884 C 82.115438,66.904852 82.079992,67.318401 82.079992,67.738514 L 82.079992,75.73905 L 78.176875,75.73905 L 78.208384,65.270348 z M 91.56274,69.076313 C 91.666455,71.871381 93.83004,73.093647 96.328402,73.093647 C 98.123074,73.093647 99.405732,72.814009 100.58599,72.379455 L 101.16365,75.064243 C 99.842914,75.623519 98.010169,76.042319 95.771752,76.042319 C 90.763211,76.042319 87.82767,72.949234 87.82767,68.220332 C 87.82767,63.961432 90.411366,59.933594 95.372644,59.933594 C 100.38906,59.933594 102.02225,64.059896 102.02225,67.436558 C 102.02225,68.16256
6 101.95792,68.744161 101.88309,69.103883 L 91.56274,69.076313 z M 98.348885,66.358704 C 98.365952,64.929006 97.743659,62.59869 95.129766,62.59869 C 92.728556,62.59869 91.730785,64.778027 91.554863,66.358704 L 98.348885,66.358704 z M 118.82942,54.363153 L 114.93024,53.307617 L 114.93024,61.97377 L 114.8659,61.97377 C 114.17665,60.834212 112.65375,59.962477 110.54268,59.962477 C 106.83386,59.962477 103.60162,63.033244 103.62656,68.201952 C 103.62656,72.945296 106.54372,76.086957 110.22759,76.086957 C 112.45288,76.086957 114.31582,75.024857 115.23745,73.297141 L 115.30703,73.297141 L 115.48164,75.73905 L 118.95675,75.73905 C 118.88586,74.690078 118.82809,72.991246 118.82809,71.411881 L 118.82809,54.363153 L 118.82942,54.363153 z M 114.92893,69.050056 C 114.92893,69.459667 114.90136,69.840395 114.81077,70.189614 C 114.41823,71.877945 113.0371,72.966301 111.44198,72.966301 C 108.98563,72.966301 107.57957,70.894617 107.57957,68.060164 C 107.57957,65.198141 108.97382,62.983355 111
.48662,62.983355 C 113.2406,62.983355 114.49568,64.220064 114.84228,65.72197 C 114.90922,66.038368 114.92893,66.428286 114.92893,66.738119 L 114.92893,69.050056 L 114.92893,69.050056 z"
+ id="path616" />
+ <path
+ d="M 161.80517,73.528501 C 160.90479,73.528501 160.18937,74.243893 160.18939,75.144292 C 160.18939,76.044668 160.90478,76.760094 161.80517,76.760081 C 162.70554,76.760081 163.42095,76.041202 163.42097,75.144292 C 163.42097,74.24046 162.70554,73.528501 161.80517,73.528501 z M 161.80517,73.803529 C 162.54687,73.803529 163.14594,74.402585 163.14593,75.144292 C 163.14593,75.882533 162.54342,76.485053 161.80517,76.485053 C 161.06348,76.485053 160.46441,75.882523 160.46441,75.144292 C 160.46441,74.402596 161.06346,73.80354 161.80517,73.803529 z M 161.25512,74.319207 L 161.25512,75.969376 L 161.49577,75.969376 L 161.49577,75.247426 L 161.80517,75.247426 L 162.2521,75.969376 L 162.52712,75.969376 L 162.04582,75.247426 C 162.29078,75.216382 162.49274,75.06625 162.49274,74.766128 C 162.49273,74.438393 162.30159,74.319207 161.90832,74.319207 L 161.25512,74.319207 z M 161.49577,74.525479 L 161.83955,74.525479 C 162.0155,74.525467 162.21771,74.562596 162.21771,74.766128 C 162.21
773,75.02142 162.01906,75.041156 161.80517,75.041156 L 161.49577,75.041156 L 161.49577,74.525479 z"
+ id="path650" />
+ <path
+ d="M 63.115808,76.090895 C 60.810796,75.504093 58.522203,75.797079 56.285026,76.486064 C 56.010655,76.526189 56.159301,76.830359 56.114355,76.953441 C 56.240389,77.319727 56.032958,77.717522 54.998429,77.944646 C 53.465014,78.282048 52.496128,79.864039 51.942103,80.389181 C 51.290927,81.007536 49.45293,81.388262 49.729943,81.01935 C 49.946565,80.730522 50.773662,79.83253 51.276485,78.861018 C 51.726795,77.99322 52.127215,77.746405 52.678614,76.919305 C 52.841408,76.676428 53.46764,75.824385 53.650127,75.149578 C 53.854932,74.490525 53.786663,73.663427 53.865435,73.323398 C 53.97834,72.83239 54.440465,71.767665 54.477226,71.166377 C 54.496918,70.825035 53.056716,71.650821 52.372719,71.650821 C 51.688722,71.650821 51.024417,71.242523 50.412627,71.21364 C 49.657736,71.17688 49.17198,71.795235 48.489295,71.68758 C 48.098065,71.625877 47.769852,71.281909 47.087167,71.255652 C 46.115654,71.220205 44.928834,71.795235 42.698294,71.724341 C 40.507139,71.653447 38.480092,68.9
52905 38.204394,68.523601 C 37.880118,68.019465 37.484949,68.019465 37.054333,68.414634 C 36.622404,68.809804 36.090697,68.498657 35.939718,68.234773 C 35.652203,67.73195 34.882871,66.258927 33.692111,65.951719 C 32.044479,65.523729 31.210817,66.864153 31.31847,67.928878 C 31.427438,69.010669 32.127189,69.31394 32.451465,69.887656 C 32.77574,70.462687 32.94116,70.834225 33.54901,71.088919 C 33.980939,71.267467 34.142421,71.53529 34.013762,71.888448 C 33.900856,72.198281 33.451859,72.269175 33.156467,72.282304 C 31.933813,72.291845 31.468231,71.67907 30.76576,70.807968 C 30.388969,70.188301 29.79556,69.919166 29.103685,69.919166 C 28.774159,69.919166 28.465638,70.005814 28.191252,70.147603 C 27.106833,70.710817 25.817611,71.045595 24.429922,71.045595 L 22.863688,71.045595 C 22.102232,68.784859 21.688683,66.365268 21.688683,63.847213 C 21.688683,51.409229 31.770093,41.32782 44.208077,41.32782 C 56.646061,41.32782 66.72747,51.410542 66.72747,63.847213 C 66.730097,68.36212 65.40
1488,72.565881 63.115808,76.090895 z M 49.170707,74.025807 C 49.286239,74.138712 49.485793,74.518127 49.241602,75.001258 C 49.105065,75.257265 48.956712,75.437126 48.694141,75.647183 C 48.37643,75.900564 47.758075,76.194643 46.908658,75.65506 C 46.451785,75.364919 46.424215,75.267768 45.794044,75.349165 C 45.343735,75.408243 45.163874,74.953995 45.326668,74.575893 C 45.488149,74.199104 46.152454,73.893208 46.980865,74.378965 C 47.353716,74.598211 47.932685,75.059024 48.44076,74.649413 C 48.65213,74.481367 48.778164,74.368462 49.069618,74.031058 C 49.082746,74.015304 49.101126,74.007427 49.122132,74.007427 C 49.140512,74.007427 49.157579,74.013991 49.170707,74.025807 z"
+ id="path632" />
+ <path
+ d="M 63.115853,76.089615 C 65.401534,72.564599 66.72883,68.36215 66.72883,63.849868 C 66.72883,51.411879 56.647417,41.330466 44.209428,41.330466 C 31.77144,41.330466 21.690027,51.413192 21.690027,63.849868 C 21.690027,66.367923 22.103576,68.787515 22.865032,71.046939 C 25.868844,79.95466 34.290809,86.367957 44.209428,86.367957 C 52.133821,86.367957 59.101143,82.275788 63.115853,76.089615 z"
+ style="fill:none"
+ id="path646" />
+ <path
+ d="M 56.917822,57.857972 C 56.694636,58.606299 56.378238,59.562056 54.970858,60.285439 C 54.766053,60.390468 54.687282,60.218483 54.781807,60.057003 C 55.313513,59.151133 55.409352,58.925322 55.562956,58.568226 C 55.779577,58.047022 55.892482,57.303946 55.463179,55.754779 C 54.615075,52.707643 52.849285,48.633855 51.564001,47.31181 C 50.32598,46.037029 48.079686,45.677306 46.050011,46.19851 C 45.302998,46.390186 43.839164,47.151642 41.126807,46.539852 C 36.433353,45.483004 35.738853,47.833013 35.468405,48.857041 C 35.197956,49.881066 34.552032,52.791666 34.552032,52.791666 C 34.33541,53.977174 34.05446,56.038354 41.342116,57.426043 C 44.737158,58.071966 44.910455,58.950266 45.060119,59.58175 C 45.329254,60.712117 45.761183,61.360667 46.245627,61.682316 C 46.731383,62.006591 46.245627,62.274414 45.707356,62.329554 C 44.260592,62.480532 38.917273,60.947118 35.754607,59.151133 C 33.168283,57.570457 33.124958,56.147322 33.717056,54.939495 C 29.808689,54.516756 26.877084
,55.304469 26.345378,57.155594 C 25.431631,60.330077 33.324513,65.752165 42.311003,68.473712 C 51.741236,71.329172 61.440606,69.336258 62.519772,63.40872 C 63.012093,60.71343 60.74348,58.721829 56.917822,57.857972 z M 42.458041,52.053841 C 39.857276,52.241579 39.586829,52.52253 39.099759,53.041108 C 38.411824,53.772368 37.507268,52.090601 37.507268,52.090601 C 36.965059,51.976382 36.306006,51.100708 36.661789,50.2828 C 37.012321,49.474082 37.658246,49.71696 37.860425,49.969029 C 38.107242,50.274923 38.633697,50.777747 39.315068,50.759366 C 39.997753,50.7423 40.785465,50.597886 41.884324,50.597886 C 42.998938,50.597886 43.745953,51.014061 43.789276,51.371156 C 43.823411,51.675739 43.698689,51.964567 42.458041,52.053841 z M 45.191406,47.754243 C 45.187466,47.754243 45.183528,47.755556 45.179589,47.755556 C 45.138891,47.755556 45.107383,47.72536 45.107383,47.687287 C 45.107383,47.659717 45.123137,47.636085 45.14808,47.625583 C 45.652218,47.359073 46.404482,47.147704 47.265715,4
7.059743 C 47.524347,47.032172 47.776416,47.019045 48.019294,47.016418 C 48.062617,47.016418 48.103316,47.016418 48.147954,47.017731 C 49.592094,47.04924 50.746092,47.622957 50.729025,48.299078 C 50.711958,48.973884 49.527763,49.495088 48.084936,49.46358 C 47.617561,49.453076 47.179067,49.384807 46.800965,49.275842 C 46.756328,49.264025 46.723506,49.225952 46.723506,49.181315 C 46.723506,49.135365 46.756328,49.097292 46.802278,49.08679 C 47.702895,48.878046 48.310747,48.538016 48.268737,48.215055 C 48.212283,47.788376 47.03334,47.557315 45.637776,47.696476 C 45.484171,47.713544 45.334507,47.733237 45.191406,47.754243 z"
+ style="fill:#cc0000"
+ id="path648" />
+ <use
+ transform="translate(-94.61853,1.913321)"
+ id="use4312"
+ x="0"
+ y="0"
+ width="744.09448"
+ height="1052.3622"
+ xlink:href="#path650" />
+ </g>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/rhlogo.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/rhlogo.png
new file mode 100644
index 0000000..ecd4856
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/rhlogo.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/shade.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/shade.png
new file mode 100644
index 0000000..a73afdf
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/shade.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/shine.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/shine.png
new file mode 100644
index 0000000..a18f7c4
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/shine.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-back.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-back.png
new file mode 100644
index 0000000..8160290
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-back.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-forward.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-forward.png
new file mode 100644
index 0000000..be86474
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-forward.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-up.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-up.png
new file mode 100644
index 0000000..52a31ed
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-up.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-home.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-home.png
new file mode 100644
index 0000000..b9ce2b8
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-home.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/title_logo.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/title_logo.png
new file mode 100644
index 0000000..ecd4856
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/title_logo.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/title_logo.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/title_logo.svg
new file mode 100644
index 0000000..1001776
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/title_logo.svg
@@ -0,0 +1,94 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://web.resource.org/cc/"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:xlink="http://www.w3.org/1999/xlink"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ width="300"
+ height="140"
+ id="svg2812"
+ sodipodi:version="0.32"
+ inkscape:version="0.45+devel"
+ version="1.0"
+ sodipodi:docname="redhat-logo.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape">
+ <defs
+ id="defs3" />
+ <sodipodi:namedview
+ inkscape:document-units="mm"
+ id="base"
+ pagecolor="#ffffff"
+ bordercolor="#666666"
+ borderopacity="1.0"
+ inkscape:pageopacity="0.0"
+ inkscape:pageshadow="2"
+ inkscape:zoom="1"
+ inkscape:cx="174.26394"
+ inkscape:cy="40.358463"
+ inkscape:current-layer="layer1"
+ inkscape:window-width="722"
+ inkscape:window-height="523"
+ inkscape:window-x="71"
+ inkscape:window-y="636"
+ width="300px"
+ height="140px" />
+ <metadata
+ id="metadata4">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <g
+ inkscape:label="Layer 1"
+ inkscape:groupmode="layer"
+ id="layer1"
+ transform="translate(-13.714282,-252.57246)">
+ <g
+ transform="matrix(2.1166666,0,0,2.1166666,-32.193429,187.76029)"
+ id="shadowman">
+ <path
+ d="M 55.68466,68.503937 C 55.68466,79.688581 46.617715,88.755526 35.433071,88.755526 C 24.248427,88.755526 15.181482,79.688581 15.181482,68.503937 C 15.181482,57.319293 24.248427,48.252348 35.433071,48.252348 C 46.617715,48.252348 55.68466,57.319293 55.68466,68.503937 z"
+ transform="matrix(1.10693,0,0,1.10693,5.005761,-12.00975)"
+ style="fill:#ffffff"
+ id="path4548" />
+ <path
+ d="M 147.81332,72.126073 C 147.81332,73.329962 147.86057,74.57586 148.03519,75.740362 L 146.64882,75.740362 L 146.42826,73.559712 L 146.35605,73.559712 C 145.61822,74.733404 143.92333,76.086957 141.50635,76.086957 C 138.4461,76.086957 137.02164,73.933874 137.02164,71.904202 C 137.02164,68.394942 140.11998,66.27862 146.30878,66.34295 L 146.30878,65.937278 C 146.30878,64.432747 146.01471,61.431561 142.41879,61.45388 C 141.08756,61.45388 139.70118,61.810976 138.5997,62.588186 L 138.1205,61.494579 C 139.51083,60.551948 141.20703,60.180411 142.58291,60.180411 C 146.97178,60.180411 147.81201,63.475677 147.81201,66.194597 L 147.81201,72.126073 L 147.81332,72.126073 z M 146.30878,67.609855 C 142.99645,67.514016 138.62333,68.015527 138.62333,71.667888 C 138.62333,73.853791 140.06616,74.835806 141.65077,74.835806 C 144.1859,74.835806 145.62742,73.266945 146.15124,71.786044 C 146.26152,71.460456 146.3101,71.134869 146.3101,70.874924 L 146.3101,67.609855 L 146.30878,67.609855 z
M 153.80387,57.175286 L 153.80387,60.527004 L 158.13891,60.527004 L 158.13891,61.747959 L 153.80387,61.747959 L 153.80387,71.635066 C 153.80387,73.568902 154.40385,74.780665 156.03835,74.780665 C 156.82343,74.780665 157.37877,74.676951 157.76606,74.541727 L 157.94856,75.707542 C 157.45754,75.912347 156.76567,76.072514 155.84798,76.072514 C 154.73862,76.072514 153.81831,75.723296 153.22358,74.994662 C 152.53566,74.195133 152.29934,72.917726 152.29934,71.365932 L 152.29934,61.746646 L 149.7314,61.746646 L 149.7314,60.525692 L 152.29934,60.525692 L 152.29934,57.729312 L 153.80387,57.175286 z M 129.02767,60.179099 C 127.87105,60.179099 126.8339,60.512563 125.96348,61.052146 C 125.05891,61.581226 124.3224,62.399135 123.88522,63.247239 L 123.8222,63.247239 L 123.8222,55.719331 L 122.31767,55.309721 L 122.31767,75.740362 L 123.8222,75.740362 L 123.8222,66.437475 C 123.8222,65.819121 123.86947,65.39113 124.02832,64.938196 C 124.67818,63.046372 126.45974,61.493265 128.61545,61.49326
5 C 131.72953,61.493265 132.80739,63.990315 132.80739,66.730242 L 132.80739,75.73905 L 134.31191,75.73905 L 134.31191,66.564822 C 134.31191,60.899855 130.4692,60.179099 129.02767,60.179099 z"
+ id="path620" />
+ <path
+ d="M 78.208384,65.270348 C 78.208384,63.205228 78.16506,61.686255 78.08235,60.311696 L 81.460325,60.311696 L 81.604739,63.240675 L 81.713705,63.240675 C 82.473849,61.069213 84.273772,59.961164 85.938472,59.961164 C 86.319199,59.961164 86.541071,59.976918 86.853532,60.045187 L 86.853532,63.719867 C 86.488557,63.648972 86.147215,63.609587 85.677213,63.609587 C 83.819525,63.609587 82.528988,64.792469 82.181081,66.560884 C 82.115438,66.904852 82.079992,67.318401 82.079992,67.738514 L 82.079992,75.73905 L 78.176875,75.73905 L 78.208384,65.270348 z M 91.56274,69.076313 C 91.666455,71.871381 93.83004,73.093647 96.328402,73.093647 C 98.123074,73.093647 99.405732,72.814009 100.58599,72.379455 L 101.16365,75.064243 C 99.842914,75.623519 98.010169,76.042319 95.771752,76.042319 C 90.763211,76.042319 87.82767,72.949234 87.82767,68.220332 C 87.82767,63.961432 90.411366,59.933594 95.372644,59.933594 C 100.38906,59.933594 102.02225,64.059896 102.02225,67.436558 C 102.02225,68.16256
6 101.95792,68.744161 101.88309,69.103883 L 91.56274,69.076313 z M 98.348885,66.358704 C 98.365952,64.929006 97.743659,62.59869 95.129766,62.59869 C 92.728556,62.59869 91.730785,64.778027 91.554863,66.358704 L 98.348885,66.358704 z M 118.82942,54.363153 L 114.93024,53.307617 L 114.93024,61.97377 L 114.8659,61.97377 C 114.17665,60.834212 112.65375,59.962477 110.54268,59.962477 C 106.83386,59.962477 103.60162,63.033244 103.62656,68.201952 C 103.62656,72.945296 106.54372,76.086957 110.22759,76.086957 C 112.45288,76.086957 114.31582,75.024857 115.23745,73.297141 L 115.30703,73.297141 L 115.48164,75.73905 L 118.95675,75.73905 C 118.88586,74.690078 118.82809,72.991246 118.82809,71.411881 L 118.82809,54.363153 L 118.82942,54.363153 z M 114.92893,69.050056 C 114.92893,69.459667 114.90136,69.840395 114.81077,70.189614 C 114.41823,71.877945 113.0371,72.966301 111.44198,72.966301 C 108.98563,72.966301 107.57957,70.894617 107.57957,68.060164 C 107.57957,65.198141 108.97382,62.983355 111
.48662,62.983355 C 113.2406,62.983355 114.49568,64.220064 114.84228,65.72197 C 114.90922,66.038368 114.92893,66.428286 114.92893,66.738119 L 114.92893,69.050056 L 114.92893,69.050056 z"
+ id="path616" />
+ <path
+ d="M 161.80517,73.528501 C 160.90479,73.528501 160.18937,74.243893 160.18939,75.144292 C 160.18939,76.044668 160.90478,76.760094 161.80517,76.760081 C 162.70554,76.760081 163.42095,76.041202 163.42097,75.144292 C 163.42097,74.24046 162.70554,73.528501 161.80517,73.528501 z M 161.80517,73.803529 C 162.54687,73.803529 163.14594,74.402585 163.14593,75.144292 C 163.14593,75.882533 162.54342,76.485053 161.80517,76.485053 C 161.06348,76.485053 160.46441,75.882523 160.46441,75.144292 C 160.46441,74.402596 161.06346,73.80354 161.80517,73.803529 z M 161.25512,74.319207 L 161.25512,75.969376 L 161.49577,75.969376 L 161.49577,75.247426 L 161.80517,75.247426 L 162.2521,75.969376 L 162.52712,75.969376 L 162.04582,75.247426 C 162.29078,75.216382 162.49274,75.06625 162.49274,74.766128 C 162.49273,74.438393 162.30159,74.319207 161.90832,74.319207 L 161.25512,74.319207 z M 161.49577,74.525479 L 161.83955,74.525479 C 162.0155,74.525467 162.21771,74.562596 162.21771,74.766128 C 162.21
773,75.02142 162.01906,75.041156 161.80517,75.041156 L 161.49577,75.041156 L 161.49577,74.525479 z"
+ id="path650" />
+ <path
+ d="M 63.115808,76.090895 C 60.810796,75.504093 58.522203,75.797079 56.285026,76.486064 C 56.010655,76.526189 56.159301,76.830359 56.114355,76.953441 C 56.240389,77.319727 56.032958,77.717522 54.998429,77.944646 C 53.465014,78.282048 52.496128,79.864039 51.942103,80.389181 C 51.290927,81.007536 49.45293,81.388262 49.729943,81.01935 C 49.946565,80.730522 50.773662,79.83253 51.276485,78.861018 C 51.726795,77.99322 52.127215,77.746405 52.678614,76.919305 C 52.841408,76.676428 53.46764,75.824385 53.650127,75.149578 C 53.854932,74.490525 53.786663,73.663427 53.865435,73.323398 C 53.97834,72.83239 54.440465,71.767665 54.477226,71.166377 C 54.496918,70.825035 53.056716,71.650821 52.372719,71.650821 C 51.688722,71.650821 51.024417,71.242523 50.412627,71.21364 C 49.657736,71.17688 49.17198,71.795235 48.489295,71.68758 C 48.098065,71.625877 47.769852,71.281909 47.087167,71.255652 C 46.115654,71.220205 44.928834,71.795235 42.698294,71.724341 C 40.507139,71.653447 38.480092,68.9
52905 38.204394,68.523601 C 37.880118,68.019465 37.484949,68.019465 37.054333,68.414634 C 36.622404,68.809804 36.090697,68.498657 35.939718,68.234773 C 35.652203,67.73195 34.882871,66.258927 33.692111,65.951719 C 32.044479,65.523729 31.210817,66.864153 31.31847,67.928878 C 31.427438,69.010669 32.127189,69.31394 32.451465,69.887656 C 32.77574,70.462687 32.94116,70.834225 33.54901,71.088919 C 33.980939,71.267467 34.142421,71.53529 34.013762,71.888448 C 33.900856,72.198281 33.451859,72.269175 33.156467,72.282304 C 31.933813,72.291845 31.468231,71.67907 30.76576,70.807968 C 30.388969,70.188301 29.79556,69.919166 29.103685,69.919166 C 28.774159,69.919166 28.465638,70.005814 28.191252,70.147603 C 27.106833,70.710817 25.817611,71.045595 24.429922,71.045595 L 22.863688,71.045595 C 22.102232,68.784859 21.688683,66.365268 21.688683,63.847213 C 21.688683,51.409229 31.770093,41.32782 44.208077,41.32782 C 56.646061,41.32782 66.72747,51.410542 66.72747,63.847213 C 66.730097,68.36212 65.40
1488,72.565881 63.115808,76.090895 z M 49.170707,74.025807 C 49.286239,74.138712 49.485793,74.518127 49.241602,75.001258 C 49.105065,75.257265 48.956712,75.437126 48.694141,75.647183 C 48.37643,75.900564 47.758075,76.194643 46.908658,75.65506 C 46.451785,75.364919 46.424215,75.267768 45.794044,75.349165 C 45.343735,75.408243 45.163874,74.953995 45.326668,74.575893 C 45.488149,74.199104 46.152454,73.893208 46.980865,74.378965 C 47.353716,74.598211 47.932685,75.059024 48.44076,74.649413 C 48.65213,74.481367 48.778164,74.368462 49.069618,74.031058 C 49.082746,74.015304 49.101126,74.007427 49.122132,74.007427 C 49.140512,74.007427 49.157579,74.013991 49.170707,74.025807 z"
+ id="path632" />
+ <path
+ d="M 63.115853,76.089615 C 65.401534,72.564599 66.72883,68.36215 66.72883,63.849868 C 66.72883,51.411879 56.647417,41.330466 44.209428,41.330466 C 31.77144,41.330466 21.690027,51.413192 21.690027,63.849868 C 21.690027,66.367923 22.103576,68.787515 22.865032,71.046939 C 25.868844,79.95466 34.290809,86.367957 44.209428,86.367957 C 52.133821,86.367957 59.101143,82.275788 63.115853,76.089615 z"
+ style="fill:none"
+ id="path646" />
+ <path
+ d="M 56.917822,57.857972 C 56.694636,58.606299 56.378238,59.562056 54.970858,60.285439 C 54.766053,60.390468 54.687282,60.218483 54.781807,60.057003 C 55.313513,59.151133 55.409352,58.925322 55.562956,58.568226 C 55.779577,58.047022 55.892482,57.303946 55.463179,55.754779 C 54.615075,52.707643 52.849285,48.633855 51.564001,47.31181 C 50.32598,46.037029 48.079686,45.677306 46.050011,46.19851 C 45.302998,46.390186 43.839164,47.151642 41.126807,46.539852 C 36.433353,45.483004 35.738853,47.833013 35.468405,48.857041 C 35.197956,49.881066 34.552032,52.791666 34.552032,52.791666 C 34.33541,53.977174 34.05446,56.038354 41.342116,57.426043 C 44.737158,58.071966 44.910455,58.950266 45.060119,59.58175 C 45.329254,60.712117 45.761183,61.360667 46.245627,61.682316 C 46.731383,62.006591 46.245627,62.274414 45.707356,62.329554 C 44.260592,62.480532 38.917273,60.947118 35.754607,59.151133 C 33.168283,57.570457 33.124958,56.147322 33.717056,54.939495 C 29.808689,54.516756 26.877084
,55.304469 26.345378,57.155594 C 25.431631,60.330077 33.324513,65.752165 42.311003,68.473712 C 51.741236,71.329172 61.440606,69.336258 62.519772,63.40872 C 63.012093,60.71343 60.74348,58.721829 56.917822,57.857972 z M 42.458041,52.053841 C 39.857276,52.241579 39.586829,52.52253 39.099759,53.041108 C 38.411824,53.772368 37.507268,52.090601 37.507268,52.090601 C 36.965059,51.976382 36.306006,51.100708 36.661789,50.2828 C 37.012321,49.474082 37.658246,49.71696 37.860425,49.969029 C 38.107242,50.274923 38.633697,50.777747 39.315068,50.759366 C 39.997753,50.7423 40.785465,50.597886 41.884324,50.597886 C 42.998938,50.597886 43.745953,51.014061 43.789276,51.371156 C 43.823411,51.675739 43.698689,51.964567 42.458041,52.053841 z M 45.191406,47.754243 C 45.187466,47.754243 45.183528,47.755556 45.179589,47.755556 C 45.138891,47.755556 45.107383,47.72536 45.107383,47.687287 C 45.107383,47.659717 45.123137,47.636085 45.14808,47.625583 C 45.652218,47.359073 46.404482,47.147704 47.265715,4
7.059743 C 47.524347,47.032172 47.776416,47.019045 48.019294,47.016418 C 48.062617,47.016418 48.103316,47.016418 48.147954,47.017731 C 49.592094,47.04924 50.746092,47.622957 50.729025,48.299078 C 50.711958,48.973884 49.527763,49.495088 48.084936,49.46358 C 47.617561,49.453076 47.179067,49.384807 46.800965,49.275842 C 46.756328,49.264025 46.723506,49.225952 46.723506,49.181315 C 46.723506,49.135365 46.756328,49.097292 46.802278,49.08679 C 47.702895,48.878046 48.310747,48.538016 48.268737,48.215055 C 48.212283,47.788376 47.03334,47.557315 45.637776,47.696476 C 45.484171,47.713544 45.334507,47.733237 45.191406,47.754243 z"
+ style="fill:#cc0000"
+ id="path648" />
+ <use
+ transform="translate(-94.61853,1.913321)"
+ id="use4312"
+ x="0"
+ y="0"
+ width="744.09448"
+ height="1052.3622"
+ xlink:href="#path650" />
+ </g>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/warning.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/warning.png
new file mode 100644
index 0000000..3745cf6
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/warning.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/warning.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/warning.svg
new file mode 100644
index 0000000..484138d
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/warning.svg
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg2">
+ <defs
+ id="defs5" />
+ <path
+ d="M 26.553837,7.3026447 C 25.283816,5.0882437 23.199663,5.0882437 21.945919,7.3026447 L 3.9376032,38.711367 C 2.6675727,40.925778 3.7259346,42.749404 6.2822626,42.749404 L 42.217493,42.749404 C 44.77383,42.749404 45.832183,40.925778 44.545876,38.711367 L 26.553837,7.3026447 z "
+ style="fill:#2e3436;fill-opacity:1;stroke:#2e3436;stroke-width:4.7150631;stroke-miterlimit:4;stroke-dasharray:none"
+ id="use2812" />
+ <path
+ d="M 26.553837,7.3026447 C 25.283816,5.0882437 23.199663,5.0882437 21.945919,7.3026447 L 3.9376032,38.711367 C 2.6675727,40.925778 3.7259346,42.749404 6.2822626,42.749404 L 42.217493,42.749404 C 44.77383,42.749404 45.832183,40.925778 44.545876,38.711367 L 26.553837,7.3026447 z "
+ style="fill:#fde8a6;fill-opacity:1;stroke-width:4;stroke-miterlimit:4;stroke-dasharray:none"
+ id="path4309" />
+ <path
+ d="M 26.220057,12.491166 C 25.133792,10.597163 23.351196,10.597163 22.278859,12.491166 L 6.8761436,39.355379 C 5.789878,41.249382 6.6951041,42.809153 8.8815542,42.809153 L 39.617353,42.809153 C 41.803812,42.809153 42.709038,41.249382 41.608844,39.355379 L 26.220057,12.491166 z "
+ style="fill:#fac521;fill-opacity:1"
+ id="path2991" />
+ <path
+ d="M 28.470282,37.445157 C 28.470282,38.878008 27.2491,39.952646 25.392902,39.952646 L 25.36034,39.952646 C 23.520438,39.952646 22.282969,38.878008 22.282969,37.445157 C 22.282969,35.947181 23.553,34.921391 25.392902,34.921391 C 27.216538,34.921391 28.437711,35.947181 28.470282,37.445157 z M 28.144632,33.146613 L 29.21927,19.990446 L 21.517696,19.990446 L 22.592334,33.146613 L 28.144632,33.146613 z "
+ style="fill:#fef2cb;fill-opacity:1;stroke:#fef2cb;stroke-width:0.9430126;stroke-linecap:round;stroke-linejoin:round;stroke-opacity:1"
+ id="path4468" />
+ <path
+ d="M 27.089325,36.371084 C 27.089325,37.803935 25.868143,38.878574 24.011955,38.878574 L 23.979392,38.878574 C 22.139481,38.878574 20.902022,37.803935 20.902022,36.371084 C 20.902022,34.873109 22.172043,33.847319 24.011955,33.847319 C 25.835581,33.847319 27.056763,34.873109 27.089325,36.371084 z M 26.763675,32.072531 L 27.838313,18.916364 L 20.136748,18.916364 L 21.211386,32.072531 L 26.763675,32.072531 z "
+ style="fill:#2e3436"
+ id="path4470" />
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/watermark-draft.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/watermark-draft.png
new file mode 100644
index 0000000..0ead5af
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/watermark-draft.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/yellow.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/yellow.png
new file mode 100644
index 0000000..223865d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/yellow.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/1-7RHEL_local_install.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/1-7RHEL_local_install.png
new file mode 100644
index 0000000..68ad5bb
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/1-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/1-Iso_general.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/1-Iso_general.png
new file mode 100644
index 0000000..564c85d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/1-Iso_general.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/1-files_PV-win.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/1-files_PV-win.png
new file mode 100644
index 0000000..bfb31dc
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/1-files_PV-win.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-7RHEL_local_install.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-7RHEL_local_install.png
new file mode 100644
index 0000000..309f788
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverchosen.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverchosen.png
new file mode 100644
index 0000000..92e56a0
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverchosen.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverchosen_win7.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverchosen_win7.png
new file mode 100644
index 0000000..abd28c8
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverchosen_win7.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverstart.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverstart.png
new file mode 100644
index 0000000..83b8d25
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverstart.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverstart_win7.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverstart_win7.png
new file mode 100644
index 0000000..e02377c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverstart_win7.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/11-7RHEL_local_install.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/11-7RHEL_local_install.png
new file mode 100644
index 0000000..c11a72a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/11-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/12-DriverInstalled.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/12-DriverInstalled.png
new file mode 100644
index 0000000..cb71880
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/12-DriverInstalled.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/14-StartInstallSerial.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/14-StartInstallSerial.png
new file mode 100644
index 0000000..ad1a744
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/14-StartInstallSerial.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/2-7RHEL_local_install.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/2-7RHEL_local_install.png
new file mode 100644
index 0000000..5cc3eef
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/2-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/2-Iso_Balloon_Os.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/2-Iso_Balloon_Os.png
new file mode 100644
index 0000000..7280b22
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/2-Iso_Balloon_Os.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/3-7RHEL_local_install.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/3-7RHEL_local_install.png
new file mode 100644
index 0000000..ec3adc0
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/3-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/3-Iso_Balloon_Os_arch.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/3-Iso_Balloon_Os_arch.png
new file mode 100644
index 0000000..72ed471
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/3-Iso_Balloon_Os_arch.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/3_PCI_Device.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/3_PCI_Device.png
new file mode 100644
index 0000000..6d45920
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/3_PCI_Device.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/4-7RHEL_local_install.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/4-7RHEL_local_install.png
new file mode 100644
index 0000000..ba41670
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/4-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/4-Iso_balloon_files.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/4-Iso_balloon_files.png
new file mode 100644
index 0000000..bc73a65
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/4-Iso_balloon_files.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/4_finish.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/4_finish.png
new file mode 100644
index 0000000..92a37ea
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/4_finish.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/5-7RHEL_local_install.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/5-7RHEL_local_install.png
new file mode 100644
index 0000000..05c4e27
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/5-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/6-7RHEL_local_install.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/6-7RHEL_local_install.png
new file mode 100644
index 0000000..211498b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/6-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/6.4-2.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/6.4-2.png
new file mode 100644
index 0000000..88f6dd9
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/6.4-2.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/6.4-3.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/6.4-3.png
new file mode 100644
index 0000000..985c268
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/6.4-3.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/6.4-4.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/6.4-4.png
new file mode 100644
index 0000000..ee00ec2
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/6.4-4.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/7-7RHEL_local_install.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/7-7RHEL_local_install.png
new file mode 100644
index 0000000..9bca57c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/7-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/8-7RHEL_local_install.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/8-7RHEL_local_install.png
new file mode 100644
index 0000000..accbc04
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/8-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/8-BrowseForDriver.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/8-BrowseForDriver.png
new file mode 100644
index 0000000..9adc468
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/8-BrowseForDriver.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/8-BrowseForDriver_win7.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/8-BrowseForDriver_win7.png
new file mode 100644
index 0000000..cdc6ad1
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/8-BrowseForDriver_win7.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/9-7RHEL_local_install.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/9-7RHEL_local_install.png
new file mode 100644
index 0000000..0b5c0eb
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/9-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/9-BrowseToDirectory.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/9-BrowseToDirectory.png
new file mode 100644
index 0000000..fa98b9c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/9-BrowseToDirectory.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/9-BrowseToDirectory_win7.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/9-BrowseToDirectory_win7.png
new file mode 100644
index 0000000..a41edd6
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/9-BrowseToDirectory_win7.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/COPYME.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/COPYME.png
new file mode 100644
index 0000000..f99eaad
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/COPYME.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ChangeType.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ChangeType.png
new file mode 100644
index 0000000..5b78310
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ChangeType.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Connection_Details.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Connection_Details.png
new file mode 100644
index 0000000..27f542b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Connection_Details.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Create-1.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Create-1.png
new file mode 100644
index 0000000..4e3e649
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Create-1.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/DevManagerStart.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/DevManagerStart.png
new file mode 100644
index 0000000..930a787
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/DevManagerStart.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/DevManagerStart_win7.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/DevManagerStart_win7.png
new file mode 100644
index 0000000..2fba9a8
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/DevManagerStart_win7.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-Expand.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-Expand.png
new file mode 100644
index 0000000..3b49f18
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-Expand.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-OpenWizard.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-OpenWizard.png
new file mode 100644
index 0000000..74918fc
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-OpenWizard.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-OpenWizard_win7.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-OpenWizard_win7.png
new file mode 100644
index 0000000..aeaa604
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-OpenWizard_win7.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/DriverInstallExpand_win7.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/DriverInstallExpand_win7.png
new file mode 100644
index 0000000..d906057
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/DriverInstallExpand_win7.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/DuringInstallation.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/DuringInstallation.png
new file mode 100644
index 0000000..389ed9a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/DuringInstallation.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Iso_Balloon_files.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Iso_Balloon_files.png
new file mode 100644
index 0000000..e024530
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Iso_Balloon_files.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Iso_general.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Iso_general.png
new file mode 100644
index 0000000..f99eaad
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Iso_general.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ManageStart.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ManageStart.png
new file mode 100644
index 0000000..3ab0161
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ManageStart.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Network_hardware.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Network_hardware.png
new file mode 100644
index 0000000..a4d305b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Network_hardware.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Network_hardware_virtio.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Network_hardware_virtio.png
new file mode 100644
index 0000000..4c18960
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Network_hardware_virtio.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/PCIremoval.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/PCIremoval.png
new file mode 100644
index 0000000..5817e55
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/PCIremoval.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/PXEguest_5of5.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/PXEguest_5of5.png
new file mode 100644
index 0000000..1348bf3
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/PXEguest_5of5.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_cpu+ram.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_cpu+ram.png
new file mode 100644
index 0000000..ad33769
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_cpu+ram.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_finish_advanced.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_finish_advanced.png
new file mode 100644
index 0000000..057d47d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_finish_advanced.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_storage.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_storage.png
new file mode 100644
index 0000000..fcd4b8a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_storage.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_storage_local.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_storage_local.png
new file mode 100644
index 0000000..613e684
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_storage_local.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_virt-manager_new_1.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_virt-manager_new_1.png
new file mode 100644
index 0000000..73bf11f
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_virt-manager_new_1.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6local_choose.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6local_choose.png
new file mode 100644
index 0000000..0178c2c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6local_choose.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6local_selectedISO.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6local_selectedISO.png
new file mode 100644
index 0000000..de74827
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6local_selectedISO.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELKVMpackages-2.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELKVMpackages-2.png
new file mode 100644
index 0000000..65aa27a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELKVMpackages-2.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELKVMpackages.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELKVMpackages.png
new file mode 100644
index 0000000..ef73b85
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELKVMpackages.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELcustomize14.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELcustomize14.png
new file mode 100644
index 0000000..83050fc
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELcustomize14.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELcustomize15.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELcustomize15.png
new file mode 100644
index 0000000..597f744
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELcustomize15.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELkvmSelect.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELkvmSelect.png
new file mode 100644
index 0000000..6b897c6
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELkvmSelect.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/SR-IOV_implementation.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/SR-IOV_implementation.png
new file mode 100644
index 0000000..7327f39
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/SR-IOV_implementation.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-VIrt-Manager-fig31pt18.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-VIrt-Manager-fig31pt18.png
new file mode 100644
index 0000000..1299ffa
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-VIrt-Manager-fig31pt18.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt1.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt1.png
new file mode 100644
index 0000000..2319393
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt1.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt11.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt11.png
new file mode 100644
index 0000000..8cad81e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt11.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt13.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt13.png
new file mode 100644
index 0000000..caf6608
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt13.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt14.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt14.png
new file mode 100644
index 0000000..3254d26
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt14.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt15.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt15.png
new file mode 100644
index 0000000..362e28b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt15.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt16.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt16.png
new file mode 100644
index 0000000..841484e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt16.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt17.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt17.png
new file mode 100644
index 0000000..cd88714
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt17.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt19.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt19.png
new file mode 100644
index 0000000..e0d075d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt19.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt2.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt2.png
new file mode 100644
index 0000000..95665bc
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt2.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt24.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt24.png
new file mode 100644
index 0000000..c1c6edf
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt24.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt24a.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt24a.png
new file mode 100644
index 0000000..48c1808
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt24a.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt27.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt27.png
new file mode 100644
index 0000000..541d6d9
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt27.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt28.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt28.png
new file mode 100644
index 0000000..fb670c0
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt28.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt29.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt29.png
new file mode 100644
index 0000000..4b1904b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt29.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt3.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt3.png
new file mode 100644
index 0000000..d19603a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt3.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt4.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt4.png
new file mode 100644
index 0000000..c4439e4
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt4.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt5.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt5.png
new file mode 100644
index 0000000..9801530
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt5.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt6.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt6.png
new file mode 100644
index 0000000..baf2a69
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt6.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt7.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt7.png
new file mode 100644
index 0000000..955b48b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt7.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt25.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt25.png
new file mode 100644
index 0000000..6cc2283
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt25.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt25a.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt25a.png
new file mode 100644
index 0000000..bd59c7e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt25a.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt26.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt26.png
new file mode 100644
index 0000000..08eca7b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt26.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic1.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic1.png
new file mode 100644
index 0000000..7c133fa
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic1.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic10.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic10.png
new file mode 100644
index 0000000..2967923
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic10.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic11.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic11.png
new file mode 100644
index 0000000..ddd69b4
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic11.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic2.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic2.png
new file mode 100644
index 0000000..52a4bec
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic2.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic3.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic3.png
new file mode 100644
index 0000000..7be870b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic3.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic4.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic4.png
new file mode 100644
index 0000000..79d74a5
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic4.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic5.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic5.png
new file mode 100644
index 0000000..67e8ac5
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic5.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic6.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic6.png
new file mode 100644
index 0000000..5a53e96
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic6.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic7.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic7.png
new file mode 100644
index 0000000..4e17f51
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic7.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic8.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic8.png
new file mode 100644
index 0000000..ceee7d9
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic8.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic9.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic9.png
new file mode 100644
index 0000000..97d8476
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic9.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic1-virt-mgr-guests.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic1-virt-mgr-guests.png
new file mode 100644
index 0000000..ea86b26
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic1-virt-mgr-guests.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic2-add-connection-pull-down.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic2-add-connection-pull-down.png
new file mode 100644
index 0000000..82c0542
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic2-add-connection-pull-down.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic3-Add Connection.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic3-Add Connection.png
new file mode 100644
index 0000000..ffff21f
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic3-Add Connection.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic3-Add-Connection.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic3-Add-Connection.png
new file mode 100644
index 0000000..bc5028e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic3-Add-Connection.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic4-OpenSSH.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic4-OpenSSH.png
new file mode 100644
index 0000000..314c36a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic4-OpenSSH.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic5-guest-select-migrate.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic5-guest-select-migrate.png
new file mode 100644
index 0000000..70018bf
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic5-guest-select-migrate.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic6-final-before-migrate.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic6-final-before-migrate.png
new file mode 100644
index 0000000..f244ff7
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic6-final-before-migrate.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic7-Migrating-guest1-rhel6-64.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic7-Migrating-guest1-rhel6-64.png
new file mode 100644
index 0000000..12202b4
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic7-Migrating-guest1-rhel6-64.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic8-migrated.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic8-migrated.png
new file mode 100644
index 0000000..3cce087
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic8-migrated.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-rhel6pv-virt-method.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-rhel6pv-virt-method.png
new file mode 100644
index 0000000..5f6957a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-rhel6pv-virt-method.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic1.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic1.png
new file mode 100644
index 0000000..604e0d8
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic1.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic2.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic2.png
new file mode 100644
index 0000000..7807aa3
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic2.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic4.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic4.png
new file mode 100644
index 0000000..09e2781
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic4.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic5.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic5.png
new file mode 100644
index 0000000..6950418
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic5.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic6.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic6.png
new file mode 100644
index 0000000..c267406
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic6.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic7-managed.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic7-managed.png
new file mode 100644
index 0000000..a635499
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic7-managed.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic7.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic7.png
new file mode 100644
index 0000000..c642653
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic7.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic8-create-lvm.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic8-create-lvm.png
new file mode 100644
index 0000000..010c7d0
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic8-create-lvm.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic8-new-storage-volume.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic8-new-storage-volume.png
new file mode 100644
index 0000000..542c15d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic8-new-storage-volume.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic9-local-storage.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic9-local-storage.png
new file mode 100644
index 0000000..8875f30
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic9-local-storage.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic9-storage-volume.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic9-storage-volume.png
new file mode 100644
index 0000000..9d58e09
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic9-storage-volume.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt2-pic2.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt2-pic2.png
new file mode 100644
index 0000000..b6e48c8
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt2-pic2.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt2-pic3.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt2-pic3.png
new file mode 100644
index 0000000..135ac84
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt2-pic3.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic2.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic2.png
new file mode 100644
index 0000000..b1b8667
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic2.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic3.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic3.png
new file mode 100644
index 0000000..17becd5
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic3.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic4.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic4.png
new file mode 100644
index 0000000..4d42817
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic4.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic5.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic5.png
new file mode 100644
index 0000000..c642653
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic5.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic6.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic6.png
new file mode 100644
index 0000000..2135749
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic6.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-virtlab22-Host-Details.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-virtlab22-Host-Details.png
new file mode 100644
index 0000000..d5a3eb3
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-virtlab22-Host-Details.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Section_11_pt_2_pt_2_step3_substep_c.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Section_11_pt_2_pt_2_step3_substep_c.png
new file mode 100644
index 0000000..1cb3707
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Section_11_pt_2_pt_2_step3_substep_c.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Section_11_pt_2_pt_2_step3_substep_d.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Section_11_pt_2_pt_2_step3_substep_d.png
new file mode 100644
index 0000000..650b0bb
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Section_11_pt_2_pt_2_step3_substep_d.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Select_storage_pools.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Select_storage_pools.png
new file mode 100644
index 0000000..7e4c07d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Select_storage_pools.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/StartDevManagerInVM.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/StartDevManagerInVM.png
new file mode 100644
index 0000000..438e32b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/StartDevManagerInVM.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/StartDevManagerInVM_win7.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/StartDevManagerInVM_win7.png
new file mode 100644
index 0000000..4b59a25
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/StartDevManagerInVM_win7.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/StartInstallingBalloon-1.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/StartInstallingBalloon-1.png
new file mode 100644
index 0000000..e496e60
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/StartInstallingBalloon-1.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/StartInstallingBalloon-1_win7.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/StartInstallingBalloon-1_win7.png
new file mode 100644
index 0000000..c03a94a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/StartInstallingBalloon-1_win7.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virt-Manager-Add-Connection.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virt-Manager-Add-Connection.png
new file mode 100644
index 0000000..44d5e61
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virt-Manager-Add-Connection.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install.png
new file mode 100644
index 0000000..a7ef6cc
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-cpumem.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-cpumem.png
new file mode 100644
index 0000000..20afcae
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-cpumem.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-import.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-import.png
new file mode 100644
index 0000000..1b8a5c1
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-import.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-local.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-local.png
new file mode 100644
index 0000000..5cb5c11
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-local.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP4.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP4.png
new file mode 100644
index 0000000..304089a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP4.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP5-finish.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP5-finish.png
new file mode 100644
index 0000000..55f87df
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP5-finish.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_final-hardware.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_final-hardware.png
new file mode 100644
index 0000000..def864d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_final-hardware.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-capture.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-capture.png
new file mode 100644
index 0000000..aaf7cdb
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-capture.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-select-driver.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-select-driver.png
new file mode 100644
index 0000000..bc2449f
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-select-driver.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-select2.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-select2.png
new file mode 100644
index 0000000..22f75f7
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-select2.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/after_virtualization.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/after_virtualization.png
new file mode 100644
index 0000000..96bd1ee
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/after_virtualization.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/before_virtualization.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/before_virtualization.png
new file mode 100644
index 0000000..e47e9e0
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/before_virtualization.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/block_finish-virtio-win.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/block_finish-virtio-win.png
new file mode 100644
index 0000000..61fb164
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/block_finish-virtio-win.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/block_start-virtio-win.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/block_start-virtio-win.png
new file mode 100644
index 0000000..35abf5e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/block_start-virtio-win.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/bridgePXE.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/bridgePXE.png
new file mode 100644
index 0000000..4c5945f
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/bridgePXE.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/bridgefinish.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/bridgefinish.png
new file mode 100644
index 0000000..7ecb971
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/bridgefinish.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/bz734652-step3.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/bz734652-step3.png
new file mode 100644
index 0000000..5f9cd87
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/bz734652-step3.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/done-KVM_PV.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/done-KVM_PV.png
new file mode 100644
index 0000000..5176b1c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/done-KVM_PV.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/exception-virtio-win.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/exception-virtio-win.png
new file mode 100644
index 0000000..f7df9dd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/exception-virtio-win.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/icon.svg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/icon.svg
new file mode 100644
index 0000000..b2f16d0
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/icon.svg
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<svg xmlns:svg="http://www.w3.org/2000/svg" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.0" width="32" height="32" id="svg3017">
+ <defs id="defs3019">
+ <linearGradient id="linearGradient2381">
+ <stop id="stop2383" style="stop-color:#ffffff;stop-opacity:1" offset="0"/>
+ <stop id="stop2385" style="stop-color:#ffffff;stop-opacity:0" offset="1"/>
+ </linearGradient>
+ <linearGradient x1="296.4996" y1="188.81061" x2="317.32471" y2="209.69398" id="linearGradient2371" xlink:href="#linearGradient2381" gradientUnits="userSpaceOnUse" gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)"/>
+ </defs>
+ <g transform="matrix(0.437808,-0.437808,0.437808,0.437808,-220.8237,43.55311)" id="g5089">
+ <path d="m 8.4382985,-6.28125 c -0.6073916,0 -4.3132985,5.94886271 -4.3132985,8.25 l 0,26.71875 c 0,0.846384 0.5818159,1.125 1.15625,1.125 l 25.5625,0 c 0.632342,0 1.125001,-0.492658 1.125,-1.125 l 0,-5.21875 0.28125,0 c 0.49684,0 0.906249,-0.409411 0.90625,-0.90625 l 0,-27.9375 c 0,-0.4968398 -0.40941,-0.90625 -0.90625,-0.90625 l -23.8117015,0 z" transform="translate(282.8327,227.1903)" id="path5091" style="fill:#5c5c4f;stroke:#000000;stroke-width:3.23021388;stroke-miterlimit:4;stroke-dasharray:none"/>
+ <rect width="27.85074" height="29.369793" rx="1.1414107" ry="1.1414107" x="286.96509" y="227.63805" id="rect5093" style="fill:#032c87"/>
+ <path d="m 288.43262,225.43675 25.2418,0 0,29.3698 -26.37615,0.0241 1.13435,-29.39394 z" id="rect5095" style="fill:#ffffff"/>
+ <path d="m 302.44536,251.73726 c 1.38691,7.85917 -0.69311,11.28365 -0.69311,11.28365 2.24384,-1.60762 3.96426,-3.47694 4.90522,-5.736 0.96708,2.19264 1.83294,4.42866 4.27443,5.98941 0,0 -1.59504,-7.2004 -1.71143,-11.53706 l -6.77511,0 z" id="path5097" style="fill:#a70000;fill-opacity:1;stroke-width:2"/>
+ <rect width="25.241802" height="29.736675" rx="0.89682275" ry="0.89682275" x="290.73544" y="220.92249" id="rect5099" style="fill:#809cc9"/>
+ <path d="m 576.47347,725.93939 6.37084,0.41502 0.4069,29.51809 c -1.89202,-1.31785 -6.85427,-3.7608 -8.26232,-1.68101 l 0,-26.76752 c 0,-0.82246 0.66212,-1.48458 1.48458,-1.48458 z" transform="matrix(0.499065,-0.866565,0,1,0,0)" id="rect5101" style="fill:#4573b3;fill-opacity:1"/>
+ <path d="m 293.2599,221.89363 20.73918,0 c 0.45101,0 0.8141,0.3631 0.8141,0.81411 0.21547,6.32836 -19.36824,21.7635 -22.36739,17.59717 l 0,-17.59717 c 0,-0.45101 0.3631,-0.81411 0.81411,-0.81411 z" id="path5103" style="opacity:0.65536726;fill:url(#linearGradient2371);fill-opacity:1"/>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio-add-hardware.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio-add-hardware.png
new file mode 100644
index 0000000..16c8abd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio-add-hardware.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio-remove-dev.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio-remove-dev.png
new file mode 100644
index 0000000..d21be2c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio-remove-dev.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio1.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio1.png
new file mode 100755
index 0000000..4fe8553
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio1.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio1replacement.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio1replacement.png
new file mode 100644
index 0000000..e7f1805
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio1replacement.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio2.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio2.png
new file mode 100755
index 0000000..b31e7c7
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio2.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio3.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio3.png
new file mode 100755
index 0000000..3fbefbe
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio3.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio4.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio4.png
new file mode 100755
index 0000000..bbefebc
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio4.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio5.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio5.png
new file mode 100755
index 0000000..d3888d7
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio5.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio5replacement.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio5replacement.png
new file mode 100644
index 0000000..8941fd0
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio5replacement.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio6.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio6.png
new file mode 100755
index 0000000..a843646
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio6.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio6replacement.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio6replacement.png
new file mode 100644
index 0000000..530f0aa
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio6replacement.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio7.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio7.png
new file mode 100755
index 0000000..35fbb90
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio7.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio7replacement.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio7replacement.png
new file mode 100644
index 0000000..9fe1ad5
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio7replacement.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/infotabbutton.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/infotabbutton.png
new file mode 100644
index 0000000..31082a3
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/infotabbutton.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/installmedia-blank.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/installmedia-blank.png
new file mode 100644
index 0000000..365f435
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/installmedia-blank.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/installmedia-select-os1.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/installmedia-select-os1.png
new file mode 100644
index 0000000..19b7495
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/installmedia-select-os1.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/installmedia-select-volume.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/installmedia-select-volume.png
new file mode 100644
index 0000000..e6344cd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/installmedia-select-volume.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/network_finish-virtio-win.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/network_finish-virtio-win.png
new file mode 100644
index 0000000..b387250
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/network_finish-virtio-win.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/network_performance-virtio-win.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/network_performance-virtio-win.png
new file mode 100644
index 0000000..130bd7e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/network_performance-virtio-win.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/network_start-virtio-win.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/network_start-virtio-win.png
new file mode 100644
index 0000000..0db3f0e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/network_start-virtio-win.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-0-click-configure-before-install.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-0-click-configure-before-install.png
new file mode 100644
index 0000000..71783ad
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-0-click-configure-before-install.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-0-click-configure-before-install_win7.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-0-click-configure-before-install_win7.png
new file mode 100644
index 0000000..0a9ce10
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-0-click-configure-before-install_win7.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-1-click-add-hardware.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-1-click-add-hardware.png
new file mode 100644
index 0000000..e8b7783
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-1-click-add-hardware.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-10-select-custom-installation.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-10-select-custom-installation.png
new file mode 100644
index 0000000..3b12745
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-10-select-custom-installation.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-11-load-driver.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-11-load-driver.png
new file mode 100644
index 0000000..94bb9a0
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-11-load-driver.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-12-insert-disk.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-12-insert-disk.png
new file mode 100644
index 0000000..8fe079e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-12-insert-disk.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-13-select-driver-arch.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-13-select-driver-arch.png
new file mode 100644
index 0000000..21e58f3
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-13-select-driver-arch.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-14-view-drivers-loaded.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-14-view-drivers-loaded.png
new file mode 100644
index 0000000..b6be79f
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-14-view-drivers-loaded.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2-disk-type.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2-disk-type.png
new file mode 100644
index 0000000..940a1ec
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2-disk-type.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2a-select-existing-storage.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2a-select-existing-storage.png
new file mode 100644
index 0000000..eae4416
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2a-select-existing-storage.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2b-select-browse-local.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2b-select-browse-local.png
new file mode 100644
index 0000000..0068c9c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2b-select-browse-local.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2c-virtio-win-vfd.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2c-virtio-win-vfd.png
new file mode 100644
index 0000000..76529b4
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2c-virtio-win-vfd.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2z-select-storage.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2z-select-storage.png
new file mode 100644
index 0000000..bf7cc17
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2z-select-storage.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-3-floppy-advanced-options.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-3-floppy-advanced-options.png
new file mode 100644
index 0000000..2448048
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-3-floppy-advanced-options.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-4-after-adding-virtio-disk.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-4-after-adding-virtio-disk.png
new file mode 100644
index 0000000..3350be3
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-4-after-adding-virtio-disk.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-5-begin-installation.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-5-begin-installation.png
new file mode 100644
index 0000000..54eb223
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-5-begin-installation.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-6-windows-install.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-6-windows-install.png
new file mode 100644
index 0000000..8df17e7
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-6-windows-install.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-6a-select-installation-type.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-6a-select-installation-type.png
new file mode 100644
index 0000000..01196df
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-6a-select-installation-type.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-8-agree-to-license-terms.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-8-agree-to-license-terms.png
new file mode 100644
index 0000000..63a83f8
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-8-agree-to-license-terms.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-adding-virtio-disk.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-adding-virtio-disk.png
new file mode 100644
index 0000000..e87cc64
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-adding-virtio-disk.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-click-begin-installation.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-click-begin-installation.png
new file mode 100644
index 0000000..b5da7ee
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-click-begin-installation.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-floppy-settings.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-floppy-settings.png
new file mode 100644
index 0000000..f3a29de
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-floppy-settings.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-settings.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-settings.png
new file mode 100644
index 0000000..3a2ea73
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-settings.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-virtio-disk-in-use.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-virtio-disk-in-use.png
new file mode 100644
index 0000000..78d5e93
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-virtio-disk-in-use.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-device-type-virtio-finish.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-device-type-virtio-finish.png
new file mode 100644
index 0000000..2219703
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-device-type-virtio-finish.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-device-type-virtiodisk.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-device-type-virtiodisk.png
new file mode 100644
index 0000000..44ffd8e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-device-type-virtiodisk.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-remove-disk1-2.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-remove-disk1-2.png
new file mode 100644
index 0000000..4f4f38d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-remove-disk1-2.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-remove-disk1.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-remove-disk1.png
new file mode 100644
index 0000000..634439d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-remove-disk1.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-review-virtio-settings.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-review-virtio-settings.png
new file mode 100644
index 0000000..5c5f00c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-review-virtio-settings.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-select-device-type-floppy.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-select-device-type-floppy.png
new file mode 100644
index 0000000..c62349c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-select-device-type-floppy.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-storage-win7.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-storage-win7.png
new file mode 100644
index 0000000..1236b8d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-storage-win7.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/pci_host_device.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/pci_host_device.png
new file mode 100644
index 0000000..a4a3ea2
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/pci_host_device.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_create_vm.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_create_vm.png
new file mode 100644
index 0000000..211647e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_create_vm.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_finish.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_finish.png
new file mode 100644
index 0000000..d76cba1
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_finish.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_finish_3.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_finish_3.png
new file mode 100644
index 0000000..7fce9df
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_finish_3.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_install_method.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_install_method.png
new file mode 100644
index 0000000..2f9d04f
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_install_method.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_install_source_2.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_install_source_2.png
new file mode 100644
index 0000000..2293268
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_install_source_2.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_mem_n_cpu_alloc.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_mem_n_cpu_alloc.png
new file mode 100644
index 0000000..93dccd9
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_mem_n_cpu_alloc.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_network.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_network.png
new file mode 100644
index 0000000..56f4ec9
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_network.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_storage.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_storage.png
new file mode 100644
index 0000000..e71f549
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_storage.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_virt_install.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_virt_install.png
new file mode 100644
index 0000000..c9c3557
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_virt_install.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6-Screenshot-step2-existing-disk-image.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6-Screenshot-step2-existing-disk-image.png
new file mode 100644
index 0000000..3805b84
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6-Screenshot-step2-existing-disk-image.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-guest1-rhel5-64-final.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-guest1-rhel5-64-final.png
new file mode 100644
index 0000000..a0685cd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-guest1-rhel5-64-final.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step1.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step1.png
new file mode 100644
index 0000000..a2d0836
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step1.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step2.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step2.png
new file mode 100644
index 0000000..e55c49a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step2.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step3.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step3.png
new file mode 100644
index 0000000..f5bc777
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step3.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step4.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step4.png
new file mode 100644
index 0000000..4791de4
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step4.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step5.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step5.png
new file mode 100644
index 0000000..5aa1fa0
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step5.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_virt_manager.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_virt_manager.png
new file mode 100644
index 0000000..d2538a7
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_virt_manager.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/selinux_uuid_block.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/selinux_uuid_block.png
new file mode 100644
index 0000000..d1a69a9
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/selinux_uuid_block.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-1.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-1.png
new file mode 100644
index 0000000..eddb949
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-1.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-2.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-2.png
new file mode 100644
index 0000000..3738c87
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-2.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-3.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-3.png
new file mode 100644
index 0000000..5f3de0f
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-3.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-4.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-4.png
new file mode 100644
index 0000000..b17a6fb
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-4.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step-1-1.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step-1-1.png
new file mode 100644
index 0000000..ed6dc3b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step-1-1.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step1-1.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step1-1.png
new file mode 100644
index 0000000..87a0e0b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step1-1.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step1-2.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step1-2.png
new file mode 100644
index 0000000..871e7bb
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step1-2.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step2-1.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step2-1.png
new file mode 100644
index 0000000..b7f01ae
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step2-1.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step2-2.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step2-2.png
new file mode 100644
index 0000000..25f3edd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step2-2.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step2-3.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step2-3.png
new file mode 100644
index 0000000..99b51fc
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step2-3.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step2-4.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step2-4.png
new file mode 100644
index 0000000..8910ab3
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step2-4.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step3-1.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step3-1.png
new file mode 100644
index 0000000..689a2a7
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step3-1.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step4-1.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step4-1.png
new file mode 100644
index 0000000..f12e5fd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step4-1.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step4-2.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step4-2.png
new file mode 100644
index 0000000..de53e6c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step4-2.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step5-1.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step5-1.png
new file mode 100644
index 0000000..d636dcd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step5-1.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step5-2.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step5-2.png
new file mode 100644
index 0000000..b76a181
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step5-2.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step5-3.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step5-3.png
new file mode 100644
index 0000000..bd1e219
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/step5-3.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/type_assigned-KVM_PV.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/type_assigned-KVM_PV.png
new file mode 100644
index 0000000..cdc7c6d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/type_assigned-KVM_PV.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/type_assigned-KVM_PV_new.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/type_assigned-KVM_PV_new.png
new file mode 100644
index 0000000..adb335f
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/type_assigned-KVM_PV_new.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/v2v-add_storagepool.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/v2v-add_storagepool.png
new file mode 100644
index 0000000..82710ae
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/v2v-add_storagepool.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/v2v-select_host.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/v2v-select_host.png
new file mode 100644
index 0000000..b9b1c99
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/v2v-select_host.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/v2v-storage_tab.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/v2v-storage_tab.png
new file mode 100644
index 0000000..fea967c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/v2v-storage_tab.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager-enable-disk-io.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager-enable-disk-io.png
new file mode 100644
index 0000000..9840461
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager-enable-disk-io.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager-enable-networkio.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager-enable-networkio.png
new file mode 100644
index 0000000..6260da0
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager-enable-networkio.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_nfs_step1.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_nfs_step1.png
new file mode 100644
index 0000000..43d4e7e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_nfs_step1.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_nfs_step2.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_nfs_step2.png
new file mode 100644
index 0000000..7e5d6c8
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_nfs_step2.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_storage_pool1.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_storage_pool1.png
new file mode 100644
index 0000000..3896a18
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_storage_pool1.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_storage_pool2.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_storage_pool2.png
new file mode 100644
index 0000000..1a29807
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_storage_pool2.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_hardware.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_hardware.png
new file mode 100644
index 0000000..08568e6
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_hardware.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_hardware_wizard1.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_hardware_wizard1.png
new file mode 100644
index 0000000..b45e590
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_hardware_wizard1.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_home.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_home.png
new file mode 100644
index 0000000..62dbd94
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_home.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_host_details_storage.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_host_details_storage.png
new file mode 100644
index 0000000..e4c7c00
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_host_details_storage.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_main.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_main.png
new file mode 100644
index 0000000..e6b7b0d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_main.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_newicon.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_newicon.png
new file mode 100644
index 0000000..9c0a829
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_newicon.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_select_host.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_select_host.png
new file mode 100644
index 0000000..cf2fc41
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_select_host.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_1_name_and_type.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_1_name_and_type.png
new file mode 100644
index 0000000..4c1aa23
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_1_name_and_type.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_2_target_path.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_2_target_path.png
new file mode 100644
index 0000000..67d9310
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_2_target_path.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_3_result.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_3_result.png
new file mode 100644
index 0000000..c2dc6ba
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_3_result.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_1_name_and_type.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_1_name_and_type.png
new file mode 100644
index 0000000..516a12c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_1_name_and_type.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_2_paths_and_format.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_2_paths_and_format.png
new file mode 100644
index 0000000..86a2e05
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_2_paths_and_format.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_3_result.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_3_result.png
new file mode 100644
index 0000000..20ee4b6
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_3_result.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_1_name_and_type.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_1_name_and_type.png
new file mode 100644
index 0000000..7879370
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_1_name_and_type.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_2a_paths_and_pool.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_2a_paths_and_pool.png
new file mode 100644
index 0000000..1547ee7
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_2a_paths_and_pool.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_2b_format_warning.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_2b_format_warning.png
new file mode 100644
index 0000000..0b88899
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_2b_format_warning.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_3_result.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_3_result.png
new file mode 100644
index 0000000..9510682
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_3_result.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_virtualization_method.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_virtualization_method.png
new file mode 100644
index 0000000..6dab167
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_virtualization_method.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-disk2.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-disk2.png
new file mode 100644
index 0000000..cebc522
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-disk2.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-finish3.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-finish3.png
new file mode 100644
index 0000000..afaed72
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-finish3.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-step1.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-step1.png
new file mode 100644
index 0000000..1f8e7c4
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-step1.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-step2.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-step2.png
new file mode 100644
index 0000000..bdef1fd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-step2.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-finish3.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-finish3.png
new file mode 100644
index 0000000..700e4bc
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-finish3.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step1-new.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step1-new.png
new file mode 100644
index 0000000..3c24dd8
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step1-new.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step1.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step1.png
new file mode 100644
index 0000000..3235be4
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step1.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step2-new.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step2-new.png
new file mode 100644
index 0000000..293c735
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step2-new.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step2.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step2.png
new file mode 100644
index 0000000..f61cc79
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step2.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio0-customize.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio0-customize.png
new file mode 100644
index 0000000..49e56bb
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio0-customize.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio3-finished.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio3-finished.png
new file mode 100644
index 0000000..603725e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio3-finished.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtual_machine_overview.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtual_machine_overview.png
new file mode 100644
index 0000000..8a60772
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtual_machine_overview.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm-add_hardware1.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm-add_hardware1.png
new file mode 100644
index 0000000..e4e761d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm-add_hardware1.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm_add_hardware.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm_add_hardware.png
new file mode 100644
index 0000000..ca4b140
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm_add_hardware.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm_add_hardware_new.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm_add_hardware_new.png
new file mode 100644
index 0000000..406dc05
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm_add_hardware_new.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm_info_button.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm_info_button.png
new file mode 100644
index 0000000..7c080f7
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm_info_button.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm_info_button_new.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm_info_button_new.png
new file mode 100644
index 0000000..4156307
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm_info_button_new.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create1.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create1.png
new file mode 100644
index 0000000..1768ae8
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create1.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create2.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create2.png
new file mode 100644
index 0000000..6adb9fe
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create2.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create3_ipv4addspace.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create3_ipv4addspace.png
new file mode 100644
index 0000000..6b884c5
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create3_ipv4addspace.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create4_dhcprange.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create4_dhcprange.png
new file mode 100644
index 0000000..f72639a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create4_dhcprange.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create5_connectphysnet.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create5_connectphysnet.png
new file mode 100644
index 0000000..0219a18
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create5_connectphysnet.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create6_finish.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create6_finish.png
new file mode 100644
index 0000000..632def4
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create6_finish.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create7_maintab.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create7_maintab.png
new file mode 100644
index 0000000..b7df642
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create7_maintab.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_maintab.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_maintab.png
new file mode 100644
index 0000000..d2104e8
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_maintab.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_menuselect.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_menuselect.png
new file mode 100644
index 0000000..7a7623d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_menuselect.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-01-switch.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-01-switch.png
new file mode 100644
index 0000000..9aa78c1
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-01-switch.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-02-switchandtwoguests.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-02-switchandtwoguests.png
new file mode 100644
index 0000000..9256a76
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-02-switchandtwoguests.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-03-hostwithswitch.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-03-hostwithswitch.png
new file mode 100644
index 0000000..d41424a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-03-hostwithswitch.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-04-hostwithnatswitch.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-04-hostwithnatswitch.png
new file mode 100644
index 0000000..e94c04d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-04-hostwithnatswitch.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-05-switchwithdnsmasq.jpg b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-05-switchwithdnsmasq.jpg
new file mode 100644
index 0000000..204d854
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-05-switchwithdnsmasq.jpg differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-06-routed-switch.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-06-routed-switch.png
new file mode 100644
index 0000000..5b5af96
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-06-routed-switch.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-07-isolated-switch.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-07-isolated-switch.png
new file mode 100644
index 0000000..1c234cb
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-07-isolated-switch.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-08-network-overview.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-08-network-overview.png
new file mode 100644
index 0000000..61c1342
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-08-network-overview.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-09-routed-mode-DMZ.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-09-routed-mode-DMZ.png
new file mode 100644
index 0000000..f1ea4e9
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-09-routed-mode-DMZ.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-10-routed-mode-datacenter.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-10-routed-mode-datacenter.png
new file mode 100644
index 0000000..35cd345
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-10-routed-mode-datacenter.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-11-router-mode-mac-restricted.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-11-router-mode-mac-restricted.png
new file mode 100644
index 0000000..bbf3882
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-11-router-mode-mac-restricted.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-12-network-tab-default.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-12-network-tab-default.png
new file mode 100644
index 0000000..63d3582
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-12-network-tab-default.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/w7x86driverchosen.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/w7x86driverchosen.png
new file mode 100644
index 0000000..3f1a832
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/w7x86driverchosen.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/win2003_select_hal.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/win2003_select_hal.png
new file mode 100644
index 0000000..c8d4ecd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/win2003_select_hal.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/win7paravirt-click-configure-before-install.png b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/win7paravirt-click-configure-before-install.png
new file mode 100644
index 0000000..b692e68
Binary files /dev/null and b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/images/win7paravirt-click-configure-before-install.png differ
diff --git a/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/index.html b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/index.html
new file mode 100644
index 0000000..57578c3
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html-single/Virtualization_Deployment_and_Administration_Guide/index.html
@@ -0,0 +1,12710 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Virtualization Deployment and Administration Guide</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><meta name="description" content="This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization." /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><div xml:lang="en-US" class="book" id="idm4419440" lang="en-US"><div class="titlepage"><div><div class="producttitle"><span class="productname">Fedora</span> <span class="productnumber">19</span></div><div><h1 id="idm4419440" class="title">Virtualization Deployment and Administration Guide</h1></div><div><h2 class="subtitle">Virtualization Documentation</h2></div><p class="edition">Edition 1.0</p><div><h3 class="corpauthor">
+ <span class="inlinemediaobject"><object data="Common_Content/images/title_logo.svg" type="image/svg+xml"> </object></span>
+
+ </h3></div><div><div xml:lang="en-US" class="authorgroup" lang="en-US"><div class="author"><h3 class="author"><span class="firstname">Laura</span> <span class="surname">Novich</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div></div><div class="author"><h3 class="author"><span class="firstname">Tahlia</span> <span class="surname">Richardson</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div></div><div class="author"><h3 class="author"><span class="firstname">Laura</span> <span class="surname">Bailey</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div></div><div class="author"><h3 class="author"><span class="firstname">Dayle</span> <span class="surname">Parker</span></h3><div class="affiliation"><span class="orgname">Red Hat</sp
an> <span class="orgdiv">Engineering Content Services</span></div></div></div></div><hr /><div><div id="idm76806832" class="legalnotice"><h1 class="legalnotice">Legal Notice</h1><div class="para">
+ Copyright <span class="trademark"></span>© 2013 Red Hat, Inc.
+ </div><div class="para">
+ The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at <a href="http://creativecommons.org/licenses/by-sa/3.0/">http://creativecommons.org/licenses/by-sa/3.0/</a>. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
+ </div><div class="para">
+ Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
+ </div><div class="para">
+ Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
+ </div><div class="para">
+ <span class="trademark">Linux</span>® is the registered trademark of Linus Torvalds in the United States and other countries.
+ </div><div class="para">
+ <span class="trademark">Java</span>® is a registered trademark of Oracle and/or its affiliates.
+ </div><div class="para">
+ <span class="trademark">XFS</span>® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
+ </div><div class="para">
+ <span class="trademark">MySQL</span>® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
+ </div><div class="para">
+ All other trademarks are the property of their respective owners.
+ </div><div class="para">
+
+<div class="address"><p><br />
+ <span class="street">1801 Varsity Drive</span><br />
+ <span class="city">Raleigh</span>, <span class="state">NC</span> <span class="postcode">27606-2072</span> <span class="country">USA</span><br />
+ <span class="phone">Phone: +1 919 754 3700</span><br />
+ <span class="phone">Phone: 888 733 4281</span><br />
+ <span class="fax">Fax: +1 919 754 3701</span></p></div>
+
+ </div></div></div><div><div class="abstract"><h6>Abstract</h6><div class="para">
+
+ </div><div class="para">
+ This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization.
+ </div></div></div></div><hr /></div><div class="toc"><dl><dt><span class="preface"><a href="#pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface">Preface</a></span></dt><dd><dl><dt><span class="section"><a href="#idm116128128">1. Document Conventions</a></span></dt><dd><dl><dt><span class="section"><a href="#idm120150544">1.1. Typographic Conventions</a></span></dt><dt><span class="section"><a href="#idm84430624">1.2. Pull-quote Conventions</a></span></dt><dt><span class="section"><a href="#idm88510976">1.3. Notes and Warnings</a></span></dt></dl></dd><dt><span class="section"><a href="#sect_RedHat-Getting_Help_and_Giving_Feedback">2. Getting Help and Giving Feedback</a></span></dt><dd><dl><dt><span class="section"><a href="#sect_RedHat-Do_You_Need_Help">2.1. Do You Need Help?</a></span></dt><dt><span class="section"><a href="#sect-RedHat-We_Need_Feedback">2.2. We Need Feedback!</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a hre
f="#idm104601248">I. Deployment</a></span></dt><dd><dl><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction">1. Introduction</a></span></dt><dd><dl><dt><span class="section"><a href="#idm100577568">1.1. What is in this guide?</a></span></dt><dt><span class="section"><a href="#idm98088880">1.2. Virtualization Documentation Suite</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_Requirements">2. System requirements</a></span></dt><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility">3. KVM guest virtual machine compatibility</a></span></dt><dd><dl><dt><span class="section"><a href="#idm94056592">3.1. Fedora 6 support limits</a></span></dt><dt><span class="section"><a href="#idm114183024">3.2. Supported CPU Models</a></span></dt><dd><dl><dt><span class="section">
<a href="#para-CPU_Models">3.2.1. Guest CPU models</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions">4. Virtualization restrictions</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-KVM_Restrictions">4.1. KVM restrictions</a></span></dt><dt><span class="section"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions">4.2. Application restrictions</a></span></dt><dt><span class="section"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions">4.3. Other restrictions</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installatio
n">5. Installing the virtualization packages</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_with_a_new_Red_Hat_Enterprise_Linux_installation">5.1. Configuring a Virtualization Host installation</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system">5.2. Installing virtualization packages on an existing Fedora system</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation">6. Guest virtual machine installation overview</a></span></dt><dd><dl><dt><span class="section"><a href="#idm87172080">6.1. Guest virtual machine prerequisites and considerations</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_
Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install">6.2. Creating guests with virt-install</a></span></dt><dt><span class="section"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager">6.3. Creating guests with virt-manager</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE">6.4. Installing guest virtual machines with PXE</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install">7. Installing a Red Hat Enterprise Linux 6 guest virtual machine on a Red Hat Enterprise Linux 6 host</a></span></dt><dd><dl><dt><span class="section"><a href="#idm97583616">7.1. Creating a Red Hat Enterprise Linux 6 guest with local installation media</a></span></dt><d
t><span class="section"><a href="#idm79824096">7.2. Creating a Red Hat Enterprise Linux 6 guest with a network installation tree</a></span></dt><dt><span class="section"><a href="#idm79226176">7.3. Creating a Red Hat Enterprise Linux 6 guest with PXE</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idm59023216">8. Virtualizing Fedora on Other Platforms</a></span></dt><dd><dl><dt><span class="section"><a href="#idm14786592">8.1. On VMWare</a></span></dt><dt><span class="section"><a href="#idm99614112">8.2. On Hyper-V</a></span></dt></dl></dd><dt><span class="chapter"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest">9. Installing a fully-virtualized Windows guest</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_virt-install">9.1. Using virt-instal
l to create a guest</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers">10. KVM Para-virtualized Drivers</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers">10.1. Installing the KVM Windows para-virtualized drivers</a></span></dt><dt><span class="section"><a href="#form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager">10.2. Installing the drivers on an installed Windows guest virtual machine</a></span></dt><dt><span class="section"><a href="#form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk">10.3. Installing drivers during the Windows installation</a></span></dt><d
t><span class="section"><a href="#idm115640352">10.4. Using the para-virtualized drivers with Red Hat Enterprise Linux 3.9 guests</a></span></dt><dt><span class="section"><a href="#form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices">10.5. Using KVM para-virtualized drivers for existing devices</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices">10.6. Using KVM para-virtualized drivers for new devices</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration">11. Network configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Insta
llation_Guide-Network_Configuration-Network_address_translation_NAT_with_libvirt">11.1. Network Address Translation (NAT) with libvirt</a></span></dt><dt><span class="section"><a href="#idm100800224">11.2. Disabling vhost-net</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt">11.3. Bridged networking with libvirt</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config">12. PCI device configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-AI_device_to_a_host">12.1. Assigning a PCI device with virsh</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_de
vice_to_a_host">12.2. Assigning a PCI device with virt-manager</a></span></dt><dt><span class="section"><a href="#idm103587632">12.3. PCI device assignment with virt-install</a></span></dt><dt><span class="section"><a href="#idm114484096">12.4. Detaching an assigned PCI device</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV">13. SR-IOV</a></span></dt><dd><dl><dt><span class="section"><a href="#idm118056880">13.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works">13.2. Using SR-IOV</a></span></dt><dt><span class="section"><a href="#idm75436048">13.3. Troubleshooting SR-IOV</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management">14. KVM guest timing management</a></span></dt><d
t><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting">15. Network booting with libvirt</a></span></dt><dd><dl><dt><span class="section"><a href="#idm108542864">15.1. Preparing the boot server</a></span></dt><dd><dl><dt><span class="section"><a href="#idm94566704">15.1.1. Setting up a PXE boot server on a private libvirt network</a></span></dt></dl></dd><dt><span class="section"><a href="#idm111619024">15.2. Booting a guest using PXE</a></span></dt><dd><dl><dt><span class="section"><a href="#idm88744848">15.2.1. Using bridged networking</a></span></dt><dt><span class="section"><a href="#idm99814048">15.2.2. Using a private libvirt network</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#qemu-ga">16. QEMU Guest Agent</a></span></dt><dd><dl><dt><span class="section"><a href="#idm84408672">16.1. Set Up Communication between Guest Agent and Host</a></span></dt></dl></dd></dl></dd><dt><s
pan class="part"><a href="#idm110765328">II. Administration</a></span></dt><dd><dl><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-Server_best_practices">17. Server best practices</a></span></dt><dt><span class="chapter"><a href="#chap-Virtualization-Security_for_virtualization">18. Security for virtualization</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Security_for_virtualization-Storage_security_issues">18.1. Storage security issues</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization">18.2. SELinux and virtualization</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Security_for_virtualization-SELinux_considerations">18.3. SELinux</a></span></dt><dt><span class="section"><a href="#idm89964272">18.4. Virtualization firewall information</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-sVirt">19. sVirt<
/a></span></dt><dd><dl><dt><span class="section"><a href="#idm121820688">19.1. Security and Virtualization</a></span></dt><dt><span class="section"><a href="#idm98075168">19.2. sVirt labeling</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-KVM_live_migration">20. KVM live migration</a></span></dt><dd><dl><dt><span class="section"><a href="#Live_migration_requirements">20.1. Live migration requirements</a></span></dt><dt><span class="section"><a href="#Live_migration_and_RHEL_compatibility">20.2. Live migration and Fedora version compatibility </a></span></dt><dt><span class="section"><a href="#shared-storage-nfs-migration">20.3. Shared storage example: NFS for a simple migration</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh">20.4. Live KVM migration with virsh</a></span></dt><dd><dl><dt><span class="section"><a href="#add-notes">20.4.1. Additonal ti
ps for migration with virsh </a></span></dt><dt><span class="section"><a href="#virsh-migration-arguements">20.4.2. Additional options for the virsh migrate command</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager">20.5. Migrating with virt-manager</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests">21. Remote management of guests</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_with_SSH">21.1. Remote management with SSH</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL">21.2. Remote management over TLS and SSL</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Remote_management_of_virtualized_guests-Transpo
rt_modes">21.3. Transport modes</a></span></dt></dl></dd><dt><span class="chapter"><a href="#sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM">22. Overcommitting with KVM</a></span></dt><dt><span class="chapter"><a href="#chap-KSM">23. KSM</a></span></dt><dt><span class="chapter"><a href="#chap-Virtualization_Administration_GuideAdvanced">24. Advanced virtualization administration</a></span></dt><dd><dl><dt><span class="section"><a href="#idm82218240">24.1. Control Groups (cgroups)</a></span></dt><dt><span class="section"><a href="#idm118488944">24.2. Hugepage support</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-Tips_and_tricks">25. Miscellaneous administration tasks</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Automatically_starting_guests">25.1. Automatically starting guests</a></span></dt><dt><span class="section"><a href="#sect-mem-dump-off">25.2. Guest m
emory allocation</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Using_qemu_img">25.3. Using qemu-img</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions">25.4. Verifying virtualization extensions</a></span></dt><dt><span class="section"><a href="#idm71657744">25.5. Setting KVM processor affinities</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address">25.6. Generating a new unique MAC address</a></span></dt><dt><span class="section"><a href="#idm96083232">25.7. Improving guest response time</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests">25.8. Disable SMART disk monitoring for guests</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server">25.9. Configuring a VNC
Server</a></span></dt><dt><span class="section"><a href="#sect-gracefully-shut-down-guests">25.10. Gracefully shutting down guests</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers">25.11. Virtual machine timer management with libvirt</a></span></dt><dt><span class="section"><a href="#sect-perf-mon">25.12. Using PMU to monitor guest performance</a></span></dt><dt><span class="section"><a href="#sect-s3-s4">25.13. Guest virtual machine power management</a></span></dt><dt><span class="section"><a href="#sect-qemu-ga">25.14. QEMU Guest Agent Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-guest-synch">25.14.1. guest-sync</a></span></dt><dt><span class="section"><a href="#subsect-guest-synch-delimited">25.14.2. guest-sync-delimited</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-limit-redirection">25.15. Setting a limit on device redirection</a></span></dt><dt><span class="sect
ion"><a href="#sect-dynamic-vNIC">25.16. Dynamically changing a host or a network bridge that is attached to a virtual NIC</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-Storage_Concepts">26. Storage concepts</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Storage_Concepts-Storage_Pools">26.1. Storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Concepts-Volumes">26.2. Volumes </a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools">27. Storage pools</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating_Storage_Pools">27.1. Creating storage pools </a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-Dedicated_Disk_Devices">27.1.1. Disk-based storage pools</a></span></dt><dt><span
class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-File_Systems">27.1.2. Partition-based storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-Local_Directories">27.1.3. Directory-based storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-LVM">27.1.4. LVM-based storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-iSCSI">27.1.5. iSCSI-based storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-NFS">27.1.6. NFS-based storage pools</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-Storage_Volumes">28. Volumes </a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Storage_Volumes-Creating_volumes">28.1. Creating volumes</a></span></dt><dt><span class="section">
<a href="#sect-Virtualization-Storage_Volumes-Cloning_volumes">28.2. Cloning volumes</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests">28.3. Adding storage devices to guests</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Adding_storage_devices_to_guests-Adding_file_based_storage_to_a_guest">28.3.1. Adding file based storage to a guest</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest">28.3.2. Adding hard drives and other block devices to a guest</a></span></dt><dt><span class="section"><a href="#sect-Managing_storage_controllers_in_a_guest">28.3.3. Managing storage controllers in a guest</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Virtualization-Storage_Volumes-Deleting_volumes">28.4. Deleting and removing volumes</a></span></dt></dl></
dd><dt><span class="chapter"><a href="#vhostmd">29. The Virtual Host Metrics Daemon (vhostmd)</a></span></dt><dd><dl><dt><span class="section"><a href="#idm110570048">29.1. Installing vhostmd on the host</a></span></dt><dt><span class="section"><a href="#idm80150944">29.2. Configuration of vhostmd</a></span></dt><dt><span class="section"><a href="#idm12488144">29.3. Starting and stopping the daemon</a></span></dt><dt><span class="section"><a href="#idm106196464">29.4. Verifying that vhostmd is working from the host</a></span></dt><dt><span class="section"><a href="#idm86879104">29.5. Configuring guests to see the metrics</a></span></dt><dt><span class="section"><a href="#idm91330288">29.6. Using vm-dump-metrics in Fedora guests to verify operation</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="#idm95247120">III. Appendicies</a></span></dt><dd><dl><dt><span class="appendix"><a href="#chap-Virtualization_Administration_Guide-Troubleshooting">A. Troubleshoot
ing</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Troubleshooting_-Debugging_and_troubleshooting_">A.1. Debugging and troubleshooting tools</a></span></dt><dt><span class="section"><a href="#idm79846544">A.2. kvm_stat</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles">A.3. Troubleshooting with serial consoles</a></span></dt><dt><span class="section"><a href="#idm12647232">A.4. Virtualization log files</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Troubleshooting-Loop_device_errors">A.5. Loop device errors</a></span></dt><dt><span class="section"><a href="#live-migration-errors">A.6. Live Migration Errors</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS">A.7. Enabling Intel VT-x and AMD-V virtualization hardware extensions in BIOS</a></sp
an></dt><dt><span class="section"><a href="#sect-Virtualization-Troubleshooting-KVM_networking_performance">A.8. KVM networking performance</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard">A.9. Missing characters on guest console with Japanese keyboard</a></span></dt><dt><span class="section"><a href="#sec-known-issues-windows-xp-guests">A.10. Known Windows XP guest issues</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idm105767440">B. Common <span class="application"><strong>libvirt</strong></span> errors and troubleshooting</a></span></dt><dd><dl><dt><span class="section"><a href="#App_Libvirt_Daemon">B.1. <span class="application"><strong>libvirtd</strong></span> failed to start</a></span></dt><dt><span class="section"><a href="#App_Hypervisor_Connection_Fail">B.2. The URI failed to connect to the hypervisor</a></span></dt><dd><dl><dt><span class="section"><a href="#Se
ct_Cannot_read_CA_certificate">B.2.1. Cannot read CA certificate</a></span></dt><dt><span class="section"><a href="#Sect_Failed_to_connect_socket">B.2.2. Failed to connect socket ... : Permission denied</a></span></dt><dt><span class="section"><a href="#Sect_Other_Connectivity_Errors">B.2.3. Other connectivity errors</a></span></dt></dl></dd><dt><span class="section"><a href="#App_Domain_Processor">B.3. The guest virtual machine cannot be started: <code class="computeroutput">internal error guest CPU is not compatible with host CPU</code></a></span></dt><dt><span class="section"><a href="#App_Domain_Monitor_Socket">B.4. Guest starting fails with error: <code class="computeroutput">monitor socket did not show up</code></a></span></dt><dt><span class="section"><a href="#App_Domain_Console">B.5. <code class="computeroutput">Internal error cannot find character device (null)</code></a></span></dt><dt><span class="section"><a href="#App_Domain_Not_Booting">B.6. Guest virtual mach
ine booting stalls with error: <code class="computeroutput">No boot device</code></a></span></dt><dt><span class="section"><a href="#App_Virt_Net_Not_Starting">B.7. Virtual network <em class="replaceable"><code>default</code></em> has not been started</a></span></dt><dt><span class="section"><a href="#App_PXE_Guest_Boot_Fail">B.8. PXE boot (or DHCP) on guest failed</a></span></dt><dt><span class="section"><a href="#App_Macvtap">B.9. Guest can reach outside network, but cannot reach host when using macvtap interface</a></span></dt><dt><span class="section"><a href="#App_DHCP_Response_Checksums">B.10. Could not add rule to fixup DHCP response checksums on network <em class="replaceable"><code>'default'</code></em></a></span></dt><dt><span class="section"><a href="#App_Bridge_Device">B.11. Unable to add bridge br0 port vnet0: No such device</a></span></dt><dt><span class="section"><a href="#App_Generic_Ethernet">B.12. Guest is unable to start with error: <code class="computerou
tput">warning: could not open /dev/net/tun</code></a></span></dt><dt><span class="section"><a href="#App_Migration_Address">B.13. Migration fails with <code class="computeroutput">Error: unable to resolve address</code></a></span></dt><dt><span class="section"><a href="#App_Migration_Disk_Image">B.14. Migration fails with <code class="computeroutput">Unable to allow access for disk path: No such file or directory</code></a></span></dt><dt><span class="section"><a href="#App_No_Guest_Machines">B.15. No guest virtual machines are present when <span class="application"><strong>libvirtd</strong></span> is started</a></span></dt><dt><span class="section"><a href="#App_TCP_Ports">B.16. Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor</a></span></dt><dt><span class="section"><a href="#App_XML_Errors">B.17. Common XML errors</a></span></dt><dd><dl><dt><span class="section"><a href="#idm115036144">B.17.1. Editing domain de
finition</a></span></dt><dt><span class="section"><a href="#idm98827392">B.17.2. XML syntax errors</a></span></dt><dt><span class="section"><a href="#idm99205120">B.17.3. Logic and configuration errors</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#netkvm-parameters">C. NetKVM Driver Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idm84429120">C.1. Configurable parameters for NetKVM</a></span></dt></dl></dd><dt><span class="appendix"><a href="#chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist">D. qemu-kvm Whitelist</a></span></dt><dd><dl><dt><span class="section"><a href="#idm115407088">D.1. Introduction</a></span></dt><dt><span class="section"><a href="#idm88207680">D.2. Basic options</a></span></dt><dt><span class="section"><a href="#idm19048240">D.3. Disk options</a></span></dt><dt><span class="section"><a href="#idm99806304">D.4. Display options</a></span></dt><dt><span class="section"><a href="#idm97967728">D.5. N
etwork options</a></span></dt><dt><span class="section"><a href="#idm95825168">D.6. Device options</a></span></dt><dt><span class="section"><a href="#idm110926144">D.7. Linux/Multiboot boot </a></span></dt><dt><span class="section"><a href="#idm85902736">D.8. Expert options</a></span></dt><dt><span class="section"><a href="#idm75543056">D.9. Help and information options</a></span></dt><dt><span class="section"><a href="#idm101602032">D.10. Miscellaneous options</a></span></dt></dl></dd><dt><span class="appendix"><a href="#chap-Virtualization_Administration_Guide-Managing_guests_with_virsh">E. Managing guests with virsh</a></span></dt><dd><dl><dt><span class="section"><a href="#idm76402464">E.1. virsh command quick reference</a></span></dt><dt><span class="section"><a href="#sect-Attaching_and_updating_a_device_with_virsh">E.2. Attaching and updating a device with virsh</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_virsh-Connectin
g_to_the_hypervisor">E.3. Connecting to the hypervisor</a></span></dt><dt><span class="section"><a href="#form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file">E.4. Creating a virtual machine XML dump (configuration file)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-multifunction-pci-install">E.4.1. Adding multifunction PCI devices to KVM guests</a></span></dt></dl></dd><dt><span class="section"><a href="#idm15093120">E.5. Suspending, resuming, saving and restoring a guest</a></span></dt><dt><span class="section"><a href="#idm111188384">E.6. Shutting down, rebooting and force-shutdown of a guest</a></span></dt><dt><span class="section"><a href="#idm124247680">E.7. Retrieving guest information</a></span></dt><dt><span class="section"><a href="#idm80557872">E.8. Retrieving node information</a></span></dt><dt><span class="section"><a href="#idm75574976">E.9. Storage pool information</a></span></dt><dt><span cla
ss="section"><a href="#idm99238304">E.10. Displaying per-guest information</a></span></dt><dt><span class="section"><a href="#idm115752416">E.11. Managing virtual networks</a></span></dt><dt><span class="section"><a href="#migrating_guests-with-virsh">E.12. Migrating guests with virsh</a></span></dt><dt><span class="section"><a href="#sect-man-disk-image">E.13. Disk image management with live block copy</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-blockcommit">E.13.1. Using blockcommit to shorten a backing chain</a></span></dt><dt><span class="section"><a href="#sub-sect-blockpull">E.13.2. Using blockpull to shorten a backing chain</a></span></dt><dt><span class="section"><a href="#sub-sect-blkresize">E.13.3. Using blockresize to change the size of a domain path</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-guest-cpu-model-config">E.14. Guest CPU model configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-guest-c
pu-intro">E.14.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-learn-about-host-cpu">E.14.2. Learning about the host CPU model</a></span></dt><dt><span class="section"><a href="#idm118920304">E.14.3. Determining a compatible CPU model to suit a pool of hosts</a></span></dt><dt><span class="section"><a href="#idm122440672">E.14.4. Configuring the guest CPU model</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager">F. Managing guests with the Virtual Machine Manager (virt-manager)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Starting_virt_manager">F.1. Starting virt-manager</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_w
indow">F.2. The Virtual Machine Manager main window</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_">F.3. The virtual hardware details window</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_">F.4. Virtual Machine graphical console</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window">F.5. Adding a remote connection</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details">F.6. Displaying guest details</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_man
ager-Status_monitoring">F.7. Performance monitoring</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage">F.8. Displaying CPU usage for guests</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage">F.9. Displaying CPU usage for hosts</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO">F.10. Displaying Disk I/O</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO">F.11. Displaying Network I/O</a></span></dt></dl></dd><dt><span class="appendix"><a href="#chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs">G. Guest disk access with offline tools</a></span></dt><dd
><dl><dt><span class="section"><a href="#sect-introduction-Virtualization_Administration_Guide-Guest_Disks_libguestfs">G.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-Terminology-Guest_Disks_libguestfs">G.2. Terminology</a></span></dt><dt><span class="section"><a href="#sect-Guide-Guest_Disks_libguestfs-installation">G.3. Installation</a></span></dt><dt><span class="section"><a href="#sect-the_guestfish_shell">G.4. The guestfish shell</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Viewing_file_systems_with_guestfish">G.4.1. Viewing file systems with guestfish</a></span></dt><dt><span class="section"><a href="#sect-Modifying-files-with-guestfish">G.4.2. Modifying files with guestfish</a></span></dt><dt><span class="section"><a href="#sect-Other-actions-with-guestfish">G.4.3. Other actions with guestfish</a></span></dt><dt><span class="section"><a href="#sect-Shell-scripting-with-guestfish">G.4.4. Shell scripting with guestfish</a></s
pan></dt><dt><span class="section"><a href="#sect-Augeas-and-libguestfs-scripting">G.4.5. Augeas and libguestfs scripting</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-other-commands">G.5. Other commands</a></span></dt><dt><span class="section"><a href="#sect-virt-rescue">G.6. virt-rescue: The rescue shell</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-virt-rescue-intro">G.6.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-run-virt-rescue">G.6.2. Running virt-rescue</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-virt-df">G.7. virt-df: Monitoring disk usage</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-virt-df-intro">G.7.1. Introduction</a></span></dt><dt><span class="section"><a href="#run-virt-df">G.7.2. Running virt-df</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-virt-resize">G.8. virt-resize: resizing guests offline</a></span></dt><dd><dl><dt><span class="
section"><a href="#sect-virt-resize-intro">G.8.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-expand-disk-image">G.8.2. Expanding a disk image</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-virt-inspector">G.9. virt-inspector: inspecting guests</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-virt-inspector-intro">G.9.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-virt-inspector-install">G.9.2. Installation</a></span></dt><dt><span class="section"><a href="#sect-virt-inspector-run">G.9.3. Running virt-inspector</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-virt-win-reg">G.10. virt-win-reg: Reading and editing the Windows Registry</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-virt-win-reg-intro">G.10.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-virt-win-reg-install">G.10.2. Installation</a></span></dt><dt><span class="section"><a
href="#sect-virt-win-reg-use">G.10.3. Using virt-win-reg</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Using-API-Programming-Languages">G.11. Using the API from Programming Languages</a></span></dt><dd><dl><dt><span class="section"><a href="#API-and-C">G.11.1. Interaction with the API via a C program</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-libguestfs-troubleshoot">G.12. Troubleshooting</a></span></dt><dt><span class="section"><a href="#sect-libguestfs-more-docs">G.13. Where to find further documentation</a></span></dt></dl></dd><dt><span class="appendix"><a href="#chap-Virtualization_Administration_Guide-Virtual_Networking">H. Virtual Networking</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-virtual_network-switches-livbvirt">H.1. Virtual network switches</a></span></dt><dt><span class="section"><a href="#sect-Network_Address_Translation-libvirt">H.2. Network Address Translation</a></span></dt><dt><span class="s
ection"><a href="#sect-network-protocols">H.3. Networking protocols</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-DNS_and_DHCP-protocols-libvirt">H.3.1. DNS and DHCP</a></span></dt><dt><span class="section"><a href="#sub-sect-routed-mode-libvirt">H.3.2. Routed mode</a></span></dt><dt><span class="section"><a href="#sub-sect-iso-mode">H.3.3. Isolated mode</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-the-Default_Configuration-libvirt">H.4. The default configuration</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Virtual_Networking-Example_scenarios">H.5. Examples of common scenarios</a></span></dt><dd><dl><dt><span class="section"><a href="#sub-sect-routed-mode">H.5.1. Routed mode</a></span></dt><dt><span class="section"><a href="#sub-sect-nat-mode">H.5.2. NAT mode</a></span></dt><dt><span class="section"><a href="#sub-sect-isolated-mode">H.5.3. Isolated mode</a></span></dt></dl></dd><dt><span class="section"><a hre
f="#sect-Virtualization-Virtual_Networking-Managing_a_virtual_network">H.6. Managing a virtual network</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Virtual_Networking-Creating_a_virtual_network">H.7. Creating a virtual network</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest">H.8. Attaching a virtual network to a guest</a></span></dt><dt><span class="section"><a href="#sect-attch-nic-physdev">H.9. Directly attaching to physical interface</a></span></dt><dt><span class="section"><a href="#sect-applying-network-filtering">H.10. Applying network filtering</a></span></dt><dd><dl><dt><span class="section"><a href="#intro-sub-sect-applying-network-filtering">H.10.1. Introduction</a></span></dt><dt><span class="section"><a href="#sub-sect-filt-chain">H.10.2. Filtering chains</a></span></dt><dt><span class="section"><a href="#sub-sect-filt-chain-props">H.10.3. Filtering chain priori
ties</a></span></dt><dt><span class="section"><a href="#sub-sect-vars-in-filters">H.10.4. Usage of variables in filters</a></span></dt><dt><span class="section"><a href="#sub-sect-auto-IP-add-detect-dhcp-snoop">H.10.5. Automatic IP address detection and DHCP snooping</a></span></dt><dt><span class="section"><a href="#sub-sect-vars-reserved">H.10.6. Reserved Variables</a></span></dt><dt><span class="section"><a href="#sub-sect-element-oview">H.10.7. Element and attribute overview</a></span></dt><dt><span class="section"><a href="#sub-sect-ref-filter">H.10.8. References to other filters</a></span></dt><dt><span class="section"><a href="#sub-sect-filter-rules">H.10.9. Filter rules</a></span></dt><dt><span class="section"><a href="#sub-sect-supp-pros">H.10.10. Supported protocols</a></span></dt><dt><span class="section"><a href="#sub-sect-adv-filt-topics">H.10.11. Advanced Filter Configuration Topics</a></span></dt><dt><span class="section"><a href="#sub-sect-limitations-filters
-network-subsystem">H.10.12. Limitations</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#appe-Virtualization-Additional_resources">I. Additional resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Additional_resources-Online_resources">I.1. Online resources</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Additional_resources-Installed_documentation">I.2. Installed documentation</a></span></dt></dl></dd><dt><span class="appendix"><a href="#ch-lib-dom-xml">J. Manipulating the domain xml</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-gen-metadata">J.1. General information and metadata</a></span></dt><dt><span class="section"><a href="#sect-dom-xml-op-sys-boot">J.2. Operating system booting</a></span></dt><dd><dl><dt><span class="section"><a href="#sub-sect-op-sys-boot-bios-boot">J.2.1. BIOS bootloader</a></span></dt><dt><span class="section"><a href="#sub-sect-op-sys-host-boot">
J.2.2. Host bootloader</a></span></dt><dt><span class="section"><a href="#sub-sect-op-sys-dir-kern-boot">J.2.3. Direct kernel boot</a></span></dt><dt><span class="section"><a href="#sub-sect-op-sys-cont-boot">J.2.4. Container boot</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-smbios-sys-info">J.3. SMBIOS system information</a></span></dt><dt><span class="section"><a href="#sect-cpu-allocation">J.4. CPU allocation</a></span></dt><dt><span class="section"><a href="#sect-cpu-tuning">J.5. CPU tuning</a></span></dt><dt><span class="section"><a href="#sect-mem-back">J.6. Memory backing</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-mem-tuning">J.7. Memory tuning</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-numa-node-tuning">J.8. NUMA node tuning</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-blk-io-tuning">J.9. Block I/O tuning</a></span></dt><dt><span class="section"><a href="#sect-li
bvirt-dom-xml-res-part">J.10. Resource partitioning</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-cpu-model-top">J.11. CPU model and topology</a></span></dt><dd><dl><dt><span class="section"><a href="#sub-sect-libvirt-dom-xml-res-part-guest-numa">J.11.1. Guest NUMA topology</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-libvirt-dom-xml-event-config">J.12. Events configuration</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-pwr-man">J.13. Power Management</a></span></dt><dt><span class="section"><a href="#idm83056320">J.14. Hypervisor features</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-time-keep">J.15. Time keeping</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-devices">J.16. Devices</a></span></dt><dd><dl><dt><span class="section"><a href="#sub-sect-libvirt-dom-xml-devices">J.16.1. Hard drives, floppy disks, CDROMs</a></span></dt><dt><span class="section
"><a href="#sub-section-libvirt-dom-xml-devices-filesystems">J.16.2. Filesystems</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-device-addresses">J.16.3. Device addresses</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-controllers">J.16.4. Controllers</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-device-leases">J.16.5. Device leases</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-host-device-assignment">J.16.6. Host device assignment</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-redirected-devices">J.16.7. Redirected devices</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-smartcard">J.16.8. Smartcard devices</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-Network-interfaces">J.16.9. Network interfaces<
/a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-input-devices">J.16.10. Input devices</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-hub-devices">J.16.11. Hub devices</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-graphical-framebuffers">J.16.12. Graphical framebuffers</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-video">J.16.13. Video devices</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-consoles">J.16.14. Consoles, serial, parallel, and channel devices</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-guest-interface">J.16.15. Guest interfaces</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-channel">J.16.16. Channel</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices
-host-interface">J.16.17. Host interface</a></span></dt></dl></dd><dt><span class="section"><a href="#section-libvirt-dom-xml-sound-devices">J.17. Sound devices</a></span></dt><dt><span class="section"><a href="#section-libvirt-dom-xml-watchdog">J.18. Watchdog device</a></span></dt><dt><span class="section"><a href="#section-libvirt-dom-xml-memory-baloon-device">J.19. Memory balloon device</a></span></dt><dt><span class="section"><a href="#section-libvirt-dom-xml-random-number-gen">J.20. Random number generator device</a></span></dt><dt><span class="section"><a href="#section-libvirt-dom-xml-tpm-device">J.21. TPM devices</a></span></dt><dt><span class="section"><a href="#section-libvirt-dom-xml-security-label">J.22. Security label</a></span></dt><dt><span class="section"><a href="#section-libvirt-dom-xml-example">J.23. Example domain XML configuration</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#appe-Red_Hat_Enterprise_Linux-Virtualization_Deployme
nt_and_Administration-Revision_History">K. Revision History</a></span></dt></dl></div><div xml:lang="en-US" class="preface" id="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Preface</h1></div></div></div><div xml:lang="en-US" class="section" id="idm116128128" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="idm116128128">1. 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" id="idm120150544"><div class="titlepage"><div><div><h3 class="title" id="idm120150544">1.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 keycaps 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 keycap, all presented in mono-spaced bold and all distinguishable thanks to context.
+ </div><div class="para">
+ Key combinations can be distinguished from keycaps 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>F2</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>F1</strong></span> to return to your X-Windows session.
+ </div></blockquote></div><div class="para">
+ The first paragraph highlights the particular keycap to press. The second highlights two key combinations (each a set of three keycaps with 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; dialog box text; labeled 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</strong></span> → <span class="guisubmenu"><strong>Preferences</strong></span> → <span class="guimenuitem"><strong>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</strong></span> → <span class="guisubmenu"><strong>Accessories</strong></span> → <span class="guimenuitem"><strong>Character Map</strong></span> from the main menu bar. Next, choose <span class="guimenu"><strong>Search</strong></span> → <span class="guimenuitem"><strong>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"><stron
g>Copy</strong></span> button. Now switch back to your document and choose <span class="guimenu"><strong>Edit</strong></span> → <span class="guimenuitem"><strong>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">
+ <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">
+ Publican is a <em class="firstterm">DocBook</em> publishing system.
+ </div></blockquote></div></div><div class="section" id="idm84430624"><div class="titlepage"><div><div><h3 class="title" id="idm84430624">1.2. Pull-quote Conventions</h3></div></div></div><div class="para">
+ Terminal output and source code listings 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 add syntax highlighting as follows:
+ </div><pre class="programlisting">package org.<span class="perl_Function">jboss</span>.<span class="perl_Function">book</span>.<span class="perl_Function">jca</span>.<span class="perl_Function">ex1</span>;
+
+<span class="perl_Keyword">import</span> javax.naming.InitialContext;
+
+<span class="perl_Keyword">public</span> <span class="perl_Keyword">class</span> ExClient
+{
+ <span class="perl_Keyword">public</span> <span class="perl_DataType">static</span> <span class="perl_DataType">void</span> <span class="perl_Function">main</span>(String args[])
+ <span class="perl_Keyword">throws</span> Exception
+ {
+ InitialContext iniCtx = <span class="perl_Keyword">new</span> InitialContext();
+ Object ref = iniCtx.<span class="perl_Function">lookup</span>(<span class="perl_String">"EchoBean"</span>);
+ EchoHome home = (EchoHome) ref;
+ Echo echo = home.<span class="perl_Function">create</span>();
+
+ System.<span class="perl_Function">out</span>.<span class="perl_Function">println</span>(<span class="perl_String">"Created Echo"</span>);
+
+ System.<span class="perl_Function">out</span>.<span class="perl_Function">println</span>(<span class="perl_String">"Echo.echo('Hello') = "</span> + echo.<span class="perl_Function">echo</span>(<span class="perl_String">"Hello"</span>));
+ }
+}</pre></div><div class="section" id="idm88510976"><div class="titlepage"><div><div><h3 class="title" id="idm88510976">1.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"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Notes are tips, shortcuts or alternative approaches 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><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><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 a box labeled 'Important' will not cause data loss but may cause irritation and frustration.
+ </div></div></div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Warnings should not be ignored. Ignoring warnings will most likely cause data loss.
+ </div></div></div></div></div><div xml:lang="en-US" class="section" id="sect_RedHat-Getting_Help_and_Giving_Feedback" lang="en-US"><div class="titlepage"><div><div><h2 class="title">2. Getting Help and Giving Feedback</h2></div></div></div><div class="section" id="sect_RedHat-Do_You_Need_Help"><div class="titlepage"><div><div><h3 class="title">2.1. Do You Need Help?</h3></div></div></div><a id="idm121363696" class="indexterm"></a><div class="para">
+ If you experience difficulty with a procedure described in this documentation, visit the Red Hat Customer Portal at <a href="http://access.redhat.com">http://access.redhat.com</a>. Through the customer portal, you can:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ search or browse through a knowledgebase of technical support articles about Red Hat products.
+ </div></li><li class="listitem"><div class="para">
+ submit a support case to Red Hat Global Support Services (GSS).
+ </div></li><li class="listitem"><div class="para">
+ access other product documentation.
+ </div></li></ul></div><div class="para">
+ Red Hat also hosts a large number of electronic mailing lists for discussion of Red Hat software and technology. You can find a list of publicly available mailing lists at <a href="https://www.redhat.com/mailman/listinfo">https://www.redhat.com/mailman/listinfo</a>. Click on the name of any mailing list to subscribe to that list or to access the list archives.
+ </div></div><div class="section" id="sect-RedHat-We_Need_Feedback"><div class="titlepage"><div><div><h3 class="title">2.2. We Need Feedback!</h3></div></div></div><a id="idm110213200" class="indexterm"></a><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/">http://bugzilla.redhat.com/</a> against the product <span class="application"><strong>Documentation.</strong></span>
+ </div><div class="para">
+ When submitting a bug report, be sure to mention the manual's identifier: <em class="citetitle">doc-Virtualization_Deployment_and_Administration_Guide</em>
+ </div><div class="para">
+ If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.
+ </div></div></div></div><div class="part" id="idm104601248"><div class="titlepage"><div><div><h1 class="title">Part I. Deployment</h1></div></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction">1. Introduction</a></span></dt><dd><dl><dt><span class="section"><a href="#idm100577568">1.1. What is in this guide?</a></span></dt><dt><span class="section"><a href="#idm98088880">1.2. Virtualization Documentation Suite</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_Requirements">2. System requirements</a></span></dt><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility">3. KVM guest virtual machine compatibility</a></span></dt><dd><dl><dt><span class="section"><a href="#idm94056592">3.1. F
edora 6 support limits</a></span></dt><dt><span class="section"><a href="#idm114183024">3.2. Supported CPU Models</a></span></dt><dd><dl><dt><span class="section"><a href="#para-CPU_Models">3.2.1. Guest CPU models</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions">4. Virtualization restrictions</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-KVM_Restrictions">4.1. KVM restrictions</a></span></dt><dt><span class="section"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions">4.2. Application restrictions</a></span></dt><dt><span class="section"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions">4.3. O
ther restrictions</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation">5. Installing the virtualization packages</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_with_a_new_Red_Hat_Enterprise_Linux_installation">5.1. Configuring a Virtualization Host installation</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system">5.2. Installing virtualization packages on an existing Fedora system</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation">6. Guest virtual machine installation overview</a></span></dt><dd><dl><dt><span class="secti
on"><a href="#idm87172080">6.1. Guest virtual machine prerequisites and considerations</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install">6.2. Creating guests with virt-install</a></span></dt><dt><span class="section"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager">6.3. Creating guests with virt-manager</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE">6.4. Installing guest virtual machines with PXE</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install">7. Installing a Red Hat Enterprise Linux 6 guest virtual machine on a Red Hat Enterprise Linux 6 host</a></
span></dt><dd><dl><dt><span class="section"><a href="#idm97583616">7.1. Creating a Red Hat Enterprise Linux 6 guest with local installation media</a></span></dt><dt><span class="section"><a href="#idm79824096">7.2. Creating a Red Hat Enterprise Linux 6 guest with a network installation tree</a></span></dt><dt><span class="section"><a href="#idm79226176">7.3. Creating a Red Hat Enterprise Linux 6 guest with PXE</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idm59023216">8. Virtualizing Fedora on Other Platforms</a></span></dt><dd><dl><dt><span class="section"><a href="#idm14786592">8.1. On VMWare</a></span></dt><dt><span class="section"><a href="#idm99614112">8.2. On Hyper-V</a></span></dt></dl></dd><dt><span class="chapter"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest">9. Installing a fully-virtualized Windows guest</a></span></dt><dd><dl><dt><span class="s
ection"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_virt-install">9.1. Using virt-install to create a guest</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers">10. KVM Para-virtualized Drivers</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers">10.1. Installing the KVM Windows para-virtualized drivers</a></span></dt><dt><span class="section"><a href="#form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager">10.2. Installing the drivers on an installed Windows guest virtual machine</a></span></dt><dt><span class="section"><a href="#form-Virtualization_Host_Configuration_and_Gues
t_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk">10.3. Installing drivers during the Windows installation</a></span></dt><dt><span class="section"><a href="#idm115640352">10.4. Using the para-virtualized drivers with Red Hat Enterprise Linux 3.9 guests</a></span></dt><dt><span class="section"><a href="#form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices">10.5. Using KVM para-virtualized drivers for existing devices</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices">10.6. Using KVM para-virtualized drivers for new devices</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide
-Network_Configuration">11. Network configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_address_translation_NAT_with_libvirt">11.1. Network Address Translation (NAT) with libvirt</a></span></dt><dt><span class="section"><a href="#idm100800224">11.2. Disabling vhost-net</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt">11.3. Bridged networking with libvirt</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config">12. PCI device configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-AI_device_to_a_host">12.1. Assigning a PCI devi
ce with virsh</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host">12.2. Assigning a PCI device with virt-manager</a></span></dt><dt><span class="section"><a href="#idm103587632">12.3. PCI device assignment with virt-install</a></span></dt><dt><span class="section"><a href="#idm114484096">12.4. Detaching an assigned PCI device</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV">13. SR-IOV</a></span></dt><dd><dl><dt><span class="section"><a href="#idm118056880">13.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works">13.2. Using SR-IOV</a></span></dt><dt><span class="section"><a href="#idm75436048">13.3. Troubleshooting SR-IOV</a></span></dt></dl></dd><dt><span class="ch
apter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management">14. KVM guest timing management</a></span></dt><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting">15. Network booting with libvirt</a></span></dt><dd><dl><dt><span class="section"><a href="#idm108542864">15.1. Preparing the boot server</a></span></dt><dd><dl><dt><span class="section"><a href="#idm94566704">15.1.1. Setting up a PXE boot server on a private libvirt network</a></span></dt></dl></dd><dt><span class="section"><a href="#idm111619024">15.2. Booting a guest using PXE</a></span></dt><dd><dl><dt><span class="section"><a href="#idm88744848">15.2.1. Using bridged networking</a></span></dt><dt><span class="section"><a href="#idm99814048">15.2.2. Using a private libvirt network</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#qemu-ga">16. QEMU Guest Agent</a></s
pan></dt><dd><dl><dt><span class="section"><a href="#idm84408672">16.1. Set Up Communication between Guest Agent and Host</a></span></dt></dl></dd></dl></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 1. Introduction</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#idm100577568">1.1. What is in this guide?</a></span></dt><dt><span class="section"><a href="#idm98088880">1.2. Virtualization Documentation Suite</a></span></dt></dl></div><div class="section" id="idm100577568"><div class="titlepage"><div><div><h2 class="title" id="idm100577568">1.1. What is in this guide?</h2></div></div></div><div class="para">
+ The <em class="citetitle">Virtualization Deployment and Administration Guide</em>, introduced in Fedora 19, resulted from the merger of the <em class="citetitle">Virtualization Host Installation and Guest Configuration Guide</em> and the <em class="citetitle">Virtualization Administration Guide</em>. This new guide provides complete information on both deploying a virtual setup on a Fedora virtualization host as well as how to administer and maintain the system. As such, this guide has 2 main parts:Deployment and Adminsitration. The appendix sections contain references and troubleshooting.
+ </div><div class="para">
+ The initial chapters in this guide outline the prerequisites to enable a Fedora host machine to deploy virtualization. System requirements, compatible hardware, support and product restrictions are covered in detail. The first part of this guide (Deployment) covers basic host configuration, including mandatory and optional virtualization packages, which are covered in <a class="xref" href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation">Chapter 5, <em>Installing the virtualization packages</em></a>. Later chapters in this part include guest virtual machine installation, which is covered in detail starting from <a class="xref" href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation">Chapter 6, <em>Guest virtual machine installation overview</em></a>, with procedures for installing fully virtualized Fedora guests and Windows para-virtualized guests using virt-manager and virsh. The part conclude
s with More detailed information on networking, PCI device configuration, SR-IOV, KVM guest timing management, and troubleshooting help for libvirt and SR-IOV is included later in the guide.
+ </div><div class="para">
+ The second part of this guide (Administration) covers more advanced configuration tactics, creating various storage pools and volumes, manipulating and finetuning memory and other resources, as well as administration tasks that can be performed using virsh and virt-manager to administer both hosts and guests.
+ </div><div class="para">
+ The last part of this guide (Appendix) contains troubleshooting information with steps that should be done before getting technical support (if possible), detailed reference guides for using QEMU-KVM flags, describing the Domain XML, and a complete CLI description of the commands used in Virsh and the screens used in Virt-manager. Additional tools that may be useful are also described in this part as well.
+ </div></div><div class="section" id="idm98088880"><div class="titlepage"><div><div><h2 class="title" id="idm98088880">1.2. Virtualization Documentation Suite</h2></div></div></div><div class="para">
+ Fedora offers a wealth of documentation solutions across its various virtualization products. Coverage of Fedora and its inbuilt virtualization products include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="citetitle">Fedora — Virtualization Getting Started Guide</em>: This guide provides an introduction to virtualization concepts, advantages, and tools, and an overview of Red Hat virtualization documentation and products.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Fedora — Virtualization Deployment and Administration Guide</em> covers the installation, configuration, and maintenance of virtualization hosts and virtual machines.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Fedora — Virtualization Security Guide</em>: This guide provides an overview of virtualization security technologies provided by Red Hat. Also included are recommendations for securing hosts, guests, and shared infrastructure and resources in virtualized environments.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Fedora — Virtualization Tuning and Optimization Guide</em>: This guide provides tips, tricks and suggestions for making full use of virtualization performance features and options for your systems and guest virtual machines.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Fedora — V2V Guide</em> describes importing virtual machines from KVM, Xen and VMware ESX/ESX(i) hypervisors to Red Hat Enterprise Virtualization and KVM managed by libvirt.
+ </div></li></ul></div><div class="para">
+ The oVirt documentation suite provides information on installation, development of applications, configuration and usage of the Red Hat Enterprise Virtualization platform and its related products.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Administration Guide</em> describes how to set up, configure and manage Red Hat Enterprise Virtualization. It assumes that you have successfully installed the Red Hat Enterprise Virtualization Manager and hosts.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Command Line Shell Guide</em> contains information for installing and using the Red Hat Enterprise Virtualization Manager command line shell.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Developer Guide</em> explains how to use the REST API. It covers the fundamentals of the REST architectural concepts in the context of a virtualization environment and provides examples of the API in operation. It also documents the installation and use of the Python Software Development Kit.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Evaluation Guide</em> enables prospective customers to evaluate the features of Red Hat Enterprise Virtualization. Use this guide if you have an evaluation license.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Installation Guide</em> describes the installation prerequisites and procedures. Read this if you need to install Red Hat Enterprise Virtualization. The installation of hosts, Manager and storage are covered in this guide. You will need to refer to the <em class="citetitle">Red Hat Enterprise Virtualization Administration Guide</em> to configure the system before you can start using the platform.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Manager Release Notes</em> contain release specific information for Red Hat Enterprise Virtualization Managers.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Power User Portal Guide</em> describes how power users can create and manage virtual machines from the Red Hat Enterprise Virtualization User Portal.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Quick Start Guide</em> provides quick and simple instructions for first time users to set up a basic Red Hat Enterprise Virtualization environment.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Technical Notes</em> describe the changes made between the current release and the previous one.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Red Hat Enterprise Virtualization — Technical Reference Guide</em> describes the technical architecture of Red Hat Enterprise Virtualization and its interactions with existing infrastructure.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Red Hat Enterprise Virtualization — User Portal Guide</em> describes how users of the Red Hat Enterprise Virtualization system can access and use virtual desktops from the User Portal.
+ </div></li></ul></div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_Requirements" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 2. System requirements</h2></div></div></div><div class="para">
+ This chapter lists system requirements for successfully running virtual machines, referred to as VMs on Fedora. Virtualization is available for Fedora on the Intel 64 and AMD64 architecture.
+ </div><div class="para">
+ The KVM hypervisor is provided with Fedora 16.
+ </div><div class="para">
+ For information on installing the virtualization packages, see <a class="xref" href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation">Chapter 5, <em>Installing the virtualization packages</em></a>.
+ </div><div class="itemizedlist" id="item-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_requirements-Minimum_system_requirements"><h6>Minimum system requirements</h6><ul><li class="listitem"><div class="para">
+ 6 GB free disk space.
+ </div></li><li class="listitem"><div class="para">
+ 2 GB of RAM.
+ </div></li></ul></div><div class="itemizedlist" id="item-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_requirements-Recommended_system_requirements"><h6>Recommended system requirements</h6><ul><li class="listitem"><div class="para">
+ One processor core or hyper-thread for the maximum number of virtualized CPUs in a guest virtual machine and one for the host.
+ </div></li><li class="listitem"><div class="para">
+ 2 GB of RAM plus additional RAM for virtual machines.
+ </div></li><li class="listitem"><div class="para">
+ 6 GB disk space for the host, plus the required disk space for each virtual machine.
+ </div><div class="para">
+ Most guest operating systems will require at least 6GB of disk space, but the additional storage space required for each guest depends on its image format.
+ </div><div class="para">
+ For guest virtual machines using raw images, the guest's total required space <code class="literal">(total for raw format)</code> is equal to or greater than the sum of the space required by the guest's raw image files <code class="literal">(images)</code>, the 6GB space required by the host operating system <code class="literal">(host)</code>, and the swap space that guest will require <code class="literal">(swap)</code>.
+ </div><div class="equation"><h6>Equation 2.1. Calculating required space for guest virtual machines using raw images</h6><div class="equation-contents"><span class="mathphrase">total for raw format = images + host + swap</span></div></div><br class="equation-break" /><div class="para">
+ For qcow images, you must also calculate the expected maximum storage requirements of the guest <code class="literal">(total for qcow format)</code>, as qcow and qcow2 images grow as required. To allow for this expansion, first multiply the expected maximum storage requirements of the guest <code class="literal">(expected maximum guest storage)</code> by 1.01, and add to this the space required by the host <code class="literal">(host)</code>, and the necessary swap space <code class="literal">(swap)</code>.
+ </div><div class="equation"><h6>Equation 2.2. Calculating required space for guest virtual machines using qcow images</h6><div class="equation-contents"><span class="mathphrase">total for qcow format = (expected maximum guest storage * 1.01) + host + swap</span></div></div><br class="equation-break" /></li></ul></div><div class="para">
+ For more information on Guest virtual machine requirements refer to <a class="xref" href="#sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM">Chapter 22, <em>Overcommitting with KVM</em></a>.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm74332464">Calculating swap space</h5>
+ Using swap space can provide additional memory beyond the available physical memory. 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 the physical RAM of the host.
+ </div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_requirements-KVM_requirements"><h5 class="formalpara">KVM requirements</h5>
+ The KVM hypervisor requires:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ an Intel processor with the Intel VT-x and Intel 64 extensions for x86-based systems, or
+ </div></li><li class="listitem"><div class="para">
+ an AMD processor with the AMD-V and the AMD64 extensions.
+ </div></li></ul></div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_requirements-Storage_support"><h5 class="formalpara">Storage support</h5>
+ The guest virtual machine storage methods are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ files on local storage,
+ </div></li><li class="listitem"><div class="para">
+ physical disk partitions,
+ </div></li><li class="listitem"><div class="para">
+ locally connected physical LUNs,
+ </div></li><li class="listitem"><div class="para">
+ LVM partitions,
+ </div></li><li class="listitem"><div class="para">
+ NFS shared file systems,
+ </div></li><li class="listitem"><div class="para">
+ iSCSI,
+ </div></li><li class="listitem"><div class="para">
+ GFS2 clustered file systems,
+ </div></li><li class="listitem"><div class="para">
+ Fibre Channel-based LUNs, and
+ </div></li><li class="listitem"><div class="para">
+ Fibre Channel over Ethernet (FCoE).
+ </div></li></ul></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 3. KVM guest virtual machine compatibility</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#idm94056592">3.1. Fedora 6 support limits</a></span></dt><dt><span class="section"><a href="#idm114183024">3.2. Supported CPU Models</a></span></dt><dd><dl><dt><span class="section"><a href="#para-CPU_Models">3.2.1. Guest CPU models</a></span></dt></dl></dd></dl></div><div class="para">
+ To verify whether your processor supports the virtualization extensions and for information on enabling the virtualization extensions if they are disabled, refer to the <em class="citetitle">Fedora Virtualization Administration Guide</em>.
+ </div><div class="section" id="idm94056592"><div class="titlepage"><div><div><h2 class="title" id="idm94056592">3.1. Fedora 6 support limits</h2></div></div></div><div class="para">
+ Fedora 19 servers have certain support limits.
+ </div><div class="para">
+ The following URLs explain the processor and memory amount limitations for Fedora 19:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ For host systems: <a href="http://www.redhat.com/resourcelibrary/articles/articles-red-hat-enterprise-linux-6-technology-capabilities-and-limits">http://www.redhat.com/resourcelibrary/articles/articles-red-hat-enterprise-linux-6-technology-capabilities-and-limits</a>
+ </div></li><li class="listitem"><div class="para">
+ For hypervisors: <a href="http://www.redhat.com/resourcelibrary/articles/virtualization-limits-rhel-hypervisors">http://www.redhat.com/resourcelibrary/articles/virtualization-limits-rhel-hypervisors</a>
+ </div></li></ul></div><div class="para">
+ The following URL is a complete reference showing supported operating systems and host and guest combinations:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.redhat.com/resourcelibrary/articles/enterprise-linux-virtualization-support">http://www.redhat.com/resourcelibrary/articles/enterprise-linux-virtualization-support</a>
+ </div></li></ul></div></div><div class="section" id="idm114183024"><div class="titlepage"><div><div><h2 class="title" id="idm114183024">3.2. Supported CPU Models</h2></div></div></div><div class="para">
+ Fedora 19 supports the use of the following QEMU CPU model definitions:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><em class="parameter"><code>Opteron_G4</code></em></span></dt><dd><div class="para">
+ AMD Opteron 62xx (Gen 4 Class Opteron)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Opteron_G3</code></em></span></dt><dd><div class="para">
+ AMD Opteron 23xx (Gen 3 Class Opteron)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Opteron_G2</code></em></span></dt><dd><div class="para">
+ AMD Opteron 22xx (Gen 2 Class Opteron)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Opteron_G1</code></em></span></dt><dd><div class="para">
+ AMD Opteron 240 (Gen 1 Class Opteron)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>SandyBridge</code></em></span></dt><dd><div class="para">
+ Intel Xeon E312xx (Sandy Bridge)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Nehalem</code></em></span></dt><dd><div class="para">
+ Intel Core i7 9xx (Nehalem Class Core i7)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Penryn</code></em></span></dt><dd><div class="para">
+ Intel Core 2 Duo P9xxx (Penryn Class Core 2)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Conroe</code></em></span></dt><dd><div class="para">
+ Intel Celeron_4x0 (Conroe/Merom Class Core 2)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Westmere</code></em></span></dt><dd><div class="para">
+ Westmere E56xx/L56xx/X56xx (Nehalem-C)
+ </div></dd></dl></div><div class="section" id="para-CPU_Models"><div class="titlepage"><div><div><h3 class="title">3.2.1. Guest CPU models</h3></div></div></div><div class="para">
+ Historically, CPU model definitions were hard-coded in <span class="application"><strong>qemu</strong></span>. This method of defining CPU models was inflexible, and made it difficult to create virtual CPUs with feature sets that matched existing physical CPUs. Typically, users modified a basic CPU model definition with feature flags in order to provide the CPU characteristics required by a virtual machine. Unless these feature sets were carefully controlled, safe migration — which requires feature sets between current and prospective hosts to match — was difficult to support.
+ </div><div class="para">
+ <span class="application"><strong>qemu-kvm</strong></span> has now replaced most hard-wired definitions with configuration file based CPU model definitions. Definitions for a number of current processor models are now included by default, allowing users to specify features more accurately and migrate more safely.
+ </div><div class="para">
+ A list of supported guest CPU models can be viewed with the <code class="command">/usr/libexec/qemu-kvm -cpu ?model</code> command. This command outputs the <em class="parameter"><code>name</code></em> used to select the CPU model at the command line, and a model identifier that corresponds to a commercial instance of that processor class.
+ </div><div class="para">
+ Configuration details for all of these CPU models can be viewed with the <code class="command">/usr/libexec/qemu-kvm -cpu ?dump</code> command, but they are also stored in the <code class="filename">/usr/share/qemu-kvm/cpu-model/cpu-x86_64.conf</code> file by default. Each CPU model definition begins with <code class="literal">[cpudef]</code>, as shown:
+ </div><pre class="screen">[cpudef]
+ name = "Nehalem"
+ level = "2"
+ vendor = "GenuineIntel"
+ family = "6"
+ model = "26"
+ stepping = "3"
+ feature_edx = "sse2 sse fxsr mmx clflush pse36 pat cmov mca \
+ pge mtrr sep apic cx8 mce pae msr tsc pse de fpu"
+ feature_ecx = "popcnt x2apic sse4.2 sse4.1 cx16 ssse3 sse3"
+ extfeature_edx = "i64 syscall xd"
+ extfeature_ecx = "lahf_lm"
+ xlevel = "0x8000000A"
+ model_id = "Intel Core i7 9xx (Nehalem Class Core i7)"</pre><div class="para">
+ The four CPUID fields, <code class="literal">feature_edx</code>, <code class="literal">feature_ecx</code>, <code class="literal">extfeature_edx</code> and <code class="literal">extfeature_ecx</code>, accept named flag values from the corresponding feature sets listed by the <code class="command">/usr/libexec/qemu-kvm -cpu ?cpuid</code> command, as shown:
+ </div><pre class="screen"># /usr/libexec/qemu-kvm -cpu ?cpuid
+Recognized CPUID flags:
+ f_edx: pbe ia64 tm ht ss sse2 sse fxsr mmx acpi ds clflush pn \
+ pse36 pat cmov mca pge mtrr sep apic cx8 mce pae msr tsc \
+ pse de vme fpu
+ f_ecx: hypervisor avx osxsave xsave aes popcnt movbe x2apic \
+ sse4.2|sse4_2 sse4.1|sse4_1 dca pdcm xtpr cx16 fma cid \
+ ssse3 tm2 est smx vmx ds_cpl monitor dtes64 pclmuldq \
+ pni|sse3
+ extf_edx: 3dnow 3dnowext lm rdtscp pdpe1gb fxsr_opt fxsr mmx \
+ mmxext nx pse36 pat cmov mca pge mtrr syscall apic cx8 \
+ mce pae msr tsc pse de vme fpu
+ extf_ecx: nodeid_msr cvt16 fma4 wdt skinit xop ibs osvw \
+ 3dnowprefetch misalignsse sse4a abm cr8legacy extapic svm \
+ cmp_legacy lahf_lm</pre><div class="para">
+ These feature sets are described in greater detail in the appropriate Intel and AMD specifications.
+ </div><div class="para">
+ It is important to use the <code class="code">check</code> flag to verify that all configured features are available.
+ </div><pre class="screen"># /usr/libexec/qemu-kvm -cpu Nehalem,check
+warning: host cpuid 0000_0001 lacks requested flag 'sse4.2|sse4_2' [0x00100000]
+warning: host cpuid 0000_0001 lacks requested flag 'popcnt' [0x00800000]</pre><div class="para">
+ If a defined feature is not available, those features will fail silently by default.
+ </div></div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 4. Virtualization restrictions</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-KVM_Restrictions">4.1. KVM restrictions</a></span></dt><dt><span class="section"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions">4.2. Application restrictions</a></span></dt><dt><span class="section"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions">4.3. Other restrictions</a></span></dt></dl></div><div class="para">
+ This chapter covers additional support and product restrictions of the virtualization packages in Fedora 19.
+ </div><div class="section" id="sect-chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-KVM_Restrictions"><div class="titlepage"><div><div><h2 class="title">4.1. KVM restrictions</h2></div></div></div><div class="para">
+ The following restrictions apply to the KVM hypervisor:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Maximum vCPUs per guest</span></dt><dd><div class="para">
+ Guest virtual machines support up to a maximum of 160 virtual CPUs in Fedora 19.
+ </div></dd><dt class="varlistentry"><span class="term">Constant TSC bit</span></dt><dd><div class="para">
+ Systems without a Constant Time Stamp Counter require additional configuration. Refer to <a class="xref" href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management">Chapter 14, <em>KVM guest timing management</em></a> for details on determining whether you have a Constant Time Stamp Counter and configuration steps for fixing any related issues.
+ </div></dd><dt class="varlistentry"><span class="term">Memory overcommit</span></dt><dd><div class="para">
+ KVM supports memory overcommit and can store the memory of guest virtual machines in swap. A virtual machine will run slower if it is swapped frequently. Fedora Knowledgebase has an article on safely and efficiently determining the size of the swap partition, available here: <a href="https://access.redhat.com/knowledge/solutions/15244">https://access.redhat.com/knowledge/solutions/15244</a>. When KSM is used for memory overcommitting, make sure that the swap size follows the recommendations described in this article.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ When device assignment is in use, all virtual machine memory must be statically pre-allocated to enable DMA with the assigned device. Memory overcommit is therefore not supported with device assignment.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">CPU overcommit</span></dt><dd><div class="para">
+ It is not recommended to have more than 10 virtual CPUs per physical processor core. Customers are encouraged to use a capacity planning tool in order to determine the CPU overcommit ratio. Estimating an ideal ratio is difficult as it is highly dependent on each workload. For instance, a guest virtual machine may consume 100% CPU on one use case, and multiple guests may be completely idle on another.
+ </div><div class="para">
+ Fedora does not support running more vCPUs to a single guest than the amount of overall physical cores that exist on the system. While Hyperthreads can be considered as cores, their performance can also vary from one scenario to the next, and they should not be expected to perform as well as regular cores.
+ </div><div class="para">
+ Refer to the <em class="citetitle">Fedora Virtualization Administration Guide</em> for tips and recommendations on overcommitting CPUs.
+ </div></dd><dt class="varlistentry"><span class="term">Virtualized SCSI devices</span></dt><dd><div class="para">
+ SCSI emulation is not supported with KVM in Fedora.
+ </div></dd><dt class="varlistentry"><span class="term">Virtualized IDE devices</span></dt><dd><div class="para">
+ KVM is limited to a maximum of four virtualized (emulated) IDE devices per guest virtual machine.
+ </div></dd><dt class="varlistentry"><span class="term">Para-virtualized devices</span></dt><dd><div class="para">
+ Para-virtualized devices are also known as Virtio devices. They are purely virtual devices designed to work optimally in a virtual machine.
+ </div><div class="para">
+ Fedora 19 supports 32 PCI device slots per virtual machine, and 8 PCI functions per device slot. This gives a theoretical maximum of 256 PCI functions per guest when multi-function capabilities are enabled.
+ </div><div class="para">
+ However, this theoretical maximum is subject to the following limitations:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Each virtual machine supports a maximum of 8 assigned device functions.
+ </div></li><li class="listitem"><div class="para">
+ 4 PCI device slots are configured with emulated devices by default. However, users can explicitly remove 2 of the emulated devices that are configured by default (the video adapter device in slot 2, and the memory balloon driver device in slot 3). This gives users a supported functional maximum of 30 PCI device slots per virtual machine.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term">Migration restrictions</span></dt><dd><div class="para">
+ Device assignment refers to physical devices that have been exposed to a virtual machine, for the exclusive use of that virtual machine. Because device assignment uses hardware on the specific host where the virtual machine runs, migration and save/restore are not supported when device assignment is in use. If the guest operating system supports hot-plugging, assigned devices can be removed prior to the migration or save/restore operation to enable this feature.
+ </div><div class="para">
+ Live migration is only possible between hosts with the same CPU type (that is, Intel to Intel or AMD to AMD only).
+ </div><div class="para">
+ For live migration, both hosts must have the same value set for the No eXecution (NX) bit, either <code class="literal">on</code> or <code class="literal">off</code>.
+ </div><div class="para">
+ For migration to work, <code class="code">cache=none</code> must be specified for all block devices opened in write mode.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Failing to include the <code class="code">cache=none</code> option can result in disk corruption.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">Storage restrictions</span></dt><dd><div class="para">
+ There are risks associated with giving guest virtual machines write access to entire disks or block devices (such as <code class="filename">/dev/sdb</code>). If a guest virtual machine has access to an entire block device, it can share any volume label or partition table with the host machine. If bugs exist in the host system's partition recognition code, this can create a security risk. Avoid this risk by configuring the host machine to ignore devices assigned to a guest virtual machine.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Failing to adhere to storage restrictions can result in risks to security.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">SR-IOV restrictions</span></dt><dd><div class="para">
+ SR-IOV is only thoroughly tested with the following devices (other SR-IOV devices may work but have not been tested at the time of release):
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Intel® 82576NS Gigabit Ethernet Controller (<code class="command">igb</code> driver)
+ </div></li><li class="listitem"><div class="para">
+ Intel® 82576EB Gigabit Ethernet Controller (<code class="command">igb</code> driver)
+ </div></li><li class="listitem"><div class="para">
+ Intel® 82599ES 10 Gigabit Ethernet Controller (<code class="command">ixgbe</code> driver)
+ </div></li><li class="listitem"><div class="para">
+ Intel® 82599EB 10 Gigabit Ethernet Controller (<code class="command">ixgbe</code> driver)
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term">Core dumping restrictions</span></dt><dd><div class="para">
+ Because core dumping is currently implemented on top of migration, it is not supported when device assignment is in use.
+ </div></dd><dt class="varlistentry"><span class="term">PCI device assignment restrictions</span></dt><dd><div class="para">
+ PCI device assignment (attaching PCI devices to virtual machines) requires host systems to have AMD IOMMU or Intel VT-d support to enable device assignment of PCI-e devices.
+ </div><div class="para">
+ For parallel/legacy PCI, only single devices behind a PCI bridge are supported.
+ </div><div class="para">
+ Multiple PCIe endpoints connected through a non-root PCIe switch require ACS support in the PCIe bridges of the PCIe switch. To disable this restriction, edit the <code class="filename">/etc/libvirt/qemu.conf</code> file and insert the line:
+ </div><pre class="programlisting">relaxed_acs_check=1</pre><div class="para">
+ Fedora 19 has limited PCI configuration space access by guest device drivers. This limitation could cause drivers that are dependent on PCI configuration space to fail configuration.
+ </div><div class="para">
+ Fedora 17 introduced interrupt remapping as a requirement for PCI device assignment. If your platform does not provide support for interrupt remapping, circumvent the KVM check for this support with the following command as the root user at the command line prompt:
+ </div><pre class="screen"># echo 1 > /sys/module/kvm/parameters/allow_unsafe_assigned_interrupts</pre></dd></dl></div></div><div class="section" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions"><div class="titlepage"><div><div><h2 class="title">4.2. Application restrictions</h2></div></div></div><div class="para">
+ There are aspects of virtualization which make it unsuitable for certain types of applications.
+ </div><div class="para">
+ Applications with high I/O throughput requirements should use the para-virtualized drivers for fully-virtualized guests. Without the para-virtualized drivers certain applications may be unpredictable under heavy I/O loads.
+ </div><div class="para">
+ The following applications should be avoided due to high I/O requirements:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>kdump</strong></span> server
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>netdump</strong></span> server
+ </div></li></ul></div><div class="para">
+ You should carefully evaluate applications and tools that heavily utilize I/O or those that require real-time performance. Consider the para-virtualized drivers or PCI device assignment for increased I/O performance. Refer to <a class="xref" href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers">Chapter 10, <em>KVM Para-virtualized Drivers</em></a> for more information on the para-virtualized drivers for fully virtualized guests. Refer to <a class="xref" href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config">Chapter 12, <em>PCI device configuration</em></a> for more information on PCI device assignment.
+ </div><div class="para">
+ Applications suffer a small performance loss from running in virtualized environments. The performance benefits of virtualization through consolidating to newer and faster hardware should be evaluated against the potential application performance issues associated with using virtualization.
+ </div></div><div class="section" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions"><div class="titlepage"><div><div><h2 class="title">4.3. Other restrictions</h2></div></div></div><div class="para">
+ For the list of all other restrictions and issues affecting virtualization read the <em class="citetitle">Fedora 19 Release Notes</em>. The <em class="citetitle">Fedora 19 Release Notes</em> cover the present new features, known issues and restrictions as they are updated or discovered.
+ </div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 5. Installing the virtualization packages</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_with_a_new_Red_Hat_Enterprise_Linux_installation">5.1. Configuring a Virtualization Host installation</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system">5.2. Installing virtualization 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 your computer. Virtualization packages can be installed either during the host installation sequence or after host installation using the <code class="command">yum</code> command and the Fedora Project download page.
+ </div><div class="para">
+ The KVM hypervisor uses the default Fedora kernel with the <span class="package">kvm</span> kernel module.
+ </div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_with_a_new_Red_Hat_Enterprise_Linux_installation"><div class="titlepage"><div><div><h2 class="title">5.1. Configuring a Virtualization Host installation</h2></div></div></div><div class="para">
+ This section covers installing virtualization tools and virtualization packages as part of a fresh Fedora installation.
+ </div><div class="procedure"><h6>Procedure 5.1. Installing the virtualization package group</h6><ol class="1"><li class="step"><p class="title"><strong>Launch the Fedora installation program</strong></p><div class="para">
+ Start an interactive Fedora installation from the Fedora Installation CD-ROM, DVD or PXE.
+ </div></li><li class="step"><p class="title"><strong>Continue installation up to package selection</strong></p><div class="para">
+ Complete the other steps up to the package selection step.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/RHELcustomize15.png" width="444" alt="The Fedora package selection screen showing options to select a different set of software from regular installation. Virtualization Host is selected in the upper menu, and Fedora is selected from the list of additional repositories. Customize now is selected at the bottom of the window, with Back and Next buttons shown at the bottom right corner of the window." /></div></div><h6>Figure 5.1. The Fedora package selection screen</h6></div><br class="figure-break" /><div class="para">
+ Select the <span class="guilabel"><strong>Virtualization Host</strong></span> server role to install a platform for guest virtual machines. Alternatively, ensure that the <span class="guilabel"><strong>Customize Now</strong></span> radio button is selected before proceeding, to specify individual packages.
+ </div></li><li class="step"><p class="title"><strong>Select the <span class="guilabel"><strong>Virtualization</strong></span> package group.</strong></p><div class="para">
+ This selects the qemu-kvm emulator, <code class="command">virt-manager</code>, <code class="command">libvirt</code> and <code class="command">virt-viewer</code> for installation.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/RHELkvmSelect.png" width="444" alt="The Fedora package selection screen with Virtualization selected in the left menu." /></div></div><h6>Figure 5.2. The Fedora package selection screen</h6></div><br class="figure-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If you wish to create virtual machines in a graphical user interface (<span class="application"><strong>virt-manager</strong></span>) later, you should also select the <code class="systemitem">General Purpose Desktop</code> package group.
+ </div></div></div></li><li class="step" id="step-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Customize_the_packages_if_required"><p class="title"><strong>Customize the packages (if required)</strong></p><div class="para">
+ Customize the <span class="guilabel"><strong>Virtualization</strong></span> group if you require other virtualization packages.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/RHELKVMpackages-2.png" width="444" alt="The Fedora package selection screen with a pop-up Packages in Virtualization window showing the packages available to be installed." /></div></div><h6>Figure 5.3. The Fedora package selection screen</h6></div><br class="figure-break" /><div class="para">
+ Click on the <span class="guilabel"><strong>Close</strong></span> button, then the <span class="guilabel"><strong>Next</strong></span> button to continue the installation.
+ </div></li></ol></div><div class="para">
+ When the installation is complete, reboot the system.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ You require a valid RHN virtualization entitlement to receive updates for the virtualization packages.
+ </div></div></div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_with_Kickstart_files"><h5 class="formalpara">Installing KVM packages with Kickstart files</h5>
+ Kickstart files allow for large, automated installations without a user manually installing each individual host system. This section describes how to create and use 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 groups:
+ </div><pre class="screen">@virtualization
+ at virtualization-client
+ at virtualization-platform
+ at virtualization-tools</pre><div class="para">
+ For more information about Kickstart files, refer to the Fedora <em class="citetitle">Installation Guide</em>, available from <a href="https://access.redhat.com/knowledge/docs/Red_Hat_Enterprise_Linux/">https://access.redhat.com/knowledge/docs/Red_Hat_Enterprise_Linux/</a>.
+ </div></div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system"><div class="titlepage"><div><div><h2 class="title">5.2. Installing virtualization packages on an existing Fedora system</h2></div></div></div><div class="para">
+ This section describes the steps for installing the KVM hypervisor on a working Fedora 16 or newer system.
+ </div><div class="para">
+ To install the packages, your machines must be registered. There are two methods of registering an unregistered installation of Fedora:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ To register via RHN Classic, run the <code class="command">rhn_register</code> command and follow the prompts.
+ </div></li><li class="listitem"><div class="para">
+ To register via Fedora, run the <code class="command">subscription-manager register</code> command and follow the prompts.
+ </div></li></ol></div><div class="para">
+ If you do not have a valid Fedora subscription, visit the <a href="https://www.redhat.com/wapps/store/catalog.html">Fedora online store</a> to obtain one.
+ </div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_the_KVM_hypervisor_with_yum"><h5 class="formalpara">Installing the virtualization packages with <code class="command">yum</code></h5>
+ To use virtualization on Fedora you require at least the <code class="filename">qemu-kvm</code> and <code class="filename">qemu-img</code> packages. These packages provide the user-level KVM emulator and disk image manager on the host Fedora system.
+ </div><div class="para">
+ To install the <code class="filename">qemu-kvm</code> and <code class="filename">qemu-img</code> packages, run the following command:
+ </div><pre class="screen"># yum install qemu-kvm qemu-img</pre><div class="para">
+ Several additional virtualization management packages are also available:
+ </div><div class="variablelist" id="vari-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Recommended_virtualization_packages"><h6>Recommended virtualization packages</h6><dl class="variablelist"><dt class="varlistentry"><span class="term"><span class="package">python-virtinst</span></span></dt><dd><div class="para">
+ Provides the <code class="command">virt-install</code> command for creating virtual machines.
+ </div></dd><dt class="varlistentry"><span class="term"><span class="package">libvirt</span></span></dt><dd><div class="para">
+ The <span class="package">libvirt</span> package provides the server and host side libraries for interacting with hypervisors and host systems. The <span class="package">libvirt</span> package provides the <code class="systemitem">libvirtd</code> daemon that handles the library calls, manages virtual machines and controls the hypervisor.
+ </div></dd><dt class="varlistentry"><span class="term"><span class="package">libvirt-python</span></span></dt><dd><div class="para">
+ The <span class="package">libvirt-python</span> package contains a module that permits applications written in the Python programming language to use the interface supplied by the <span class="package">libvirt</span> API.
+ </div></dd><dt class="varlistentry"><span class="term"><span class="package">virt-manager</span></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 <span class="package">libvirt-client</span> library as the management API.
+ </div></dd><dt class="varlistentry"><span class="term"><span class="package">libvirt-client</span></span></dt><dd><div class="para">
+ The <span class="package">libvirt-client</span> package provides the client-side APIs and libraries for accessing <span class="package">libvirt</span> servers. The <span class="package">libvirt-client</span> package includes the <code class="command">virsh</code> command line tool to manage and control virtual machines and hypervisors from the command line or a special virtualization shell.
+ </div></dd></dl></div><div class="para">
+ Install all of these recommended virtualization packages with the following command:
+ </div><pre class="screen"># yum install virt-manager libvirt libvirt-python python-virtinst libvirt-client</pre><div class="formalpara"><h5 class="formalpara" id="idm21430352">Installing Virtualization package groups</h5>
+ The virtualization packages can also be installed from package groups. The following table describes the virtualization package groups and what they provide.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Note that the <code class="command">qemu-img</code> package is installed as a dependency of the <code class="literal">Virtualization</code> package group if it is not already installed on the system. It can also be installed manually with the <code class="command">yum install qemu-img</code> command as described previously.
+ </div></div></div><div class="table"><h6>Table 5.1. Virtualization Package Groups</h6><div class="table-contents"><table summary="Virtualization Package Groups" border="1"><colgroup><col align="left" class="c1" width="25%" /><col align="left" class="c2" width="25%" /><col align="left" class="c3" width="25%" /><col align="left" class="c4" width="25%" /></colgroup><thead><tr><th class="" align="left">
+ Package Group
+ </th><th class="" align="left">
+ Description
+ </th><th class="" align="left">
+ Mandatory Packages
+ </th><th class="" align="left">
+ Optional Packages
+ </th></tr></thead><tbody><tr><td class="" align="left">
+ Virtualization
+ </td><td class="" align="left">
+ Provides an environment for hosting virtual machines
+ </td><td class="" align="left">
+ qemu-kvm
+ </td><td class="" align="left">
+ qemu-guest-agent, qemu-kvm-tools
+ </td></tr><tr><td class="" align="left">
+ Virtualization Client
+ </td><td class="" align="left">
+ Clients for installing and managing virtualization instances
+ </td><td class="" align="left">
+ python-virtinst, virt-manager, virt-viewer
+ </td><td class="" align="left">
+ virt-top
+ </td></tr><tr><td class="" align="left">
+ Virtualization Platform
+ </td><td class="" align="left">
+ Provides an interface for accessing and controlling virtual machines and containers
+ </td><td class="" align="left">
+ libvirt, libvirt-client, virt-who, virt-what
+ </td><td class="" align="left">
+ fence-virtd-libvirt, fence-virtd-multicast, fence-virtd-serial, libvirt-cim, libvirt-java, libvirt-qmf, libvirt-snmp, perl-Sys-Virt
+ </td></tr><tr><td class="" align="left">
+ Virtualization Tools
+ </td><td class="" align="left">
+ Tools for offline virtual image management
+ </td><td class="" align="left">
+ libguestfs
+ </td><td class="" align="left">
+ libguestfs-java, libguestfs-tools, virt-v2v
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ To install a package group, run the <code class="command">yum groupinstall <groupname></code> command. For instance, to install the <span class="bold bold"><strong>Virtualization Tools</strong></span> package group, run the <code class="command">yum groupinstall "Virtualization Tools"</code> command.
+ </div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 6. Guest virtual machine installation overview</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#idm87172080">6.1. Guest virtual machine prerequisites and considerations</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install">6.2. Creating guests with virt-install</a></span></dt><dt><span class="section"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager">6.3. Creating guests with virt-manager</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Inst
allation-Installing_guests_with_PXE">6.4. Installing guest virtual machines 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 guest virtual machines 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 in the following chapters for specific versions of Fedora and Microsoft Windows.
+ </div><div class="section" id="idm87172080"><div class="titlepage"><div><div><h2 class="title" id="idm87172080">6.1. Guest virtual machine prerequisites and considerations</h2></div></div></div><div class="para">
+ Various factors should be considered before creating any guest virtual machines. Not only should the role of a virtual machine be considered before deployment, but regular ongoing monitoring and assessment based on variable factors (load, amount of clients) should be performed. Some factors include:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Performance</span></dt><dd><div class="para">
+ Guest virtual machines should be deployed and configured based on their intended tasks. Some guest systems (for instance, guests running a database server) may require special performance considerations. Guests may require more assigned CPUs or memory based on their role and projected system load.
+ </div></dd><dt class="varlistentry"><span class="term">Input/Output requirements and types of Input/Output</span></dt><dd><div class="para">
+ Some guest virtual machines may have a particularly high I/O requirement or may require further considerations or projections based on the type of I/O (for instance, typical disk block size access, or the amount of clients).
+ </div></dd><dt class="varlistentry"><span class="term">Storage</span></dt><dd><div class="para">
+ Some guest virtual machines may require higher priority access to storage or faster disk types, or may require exclusive access to areas of storage. The amount of storage used by guests should also be regularly monitored and taken into account when deploying and maintaining storage.
+ </div></dd><dt class="varlistentry"><span class="term">Networking and network infrastructure</span></dt><dd><div class="para">
+ Depending upon your environment, some guest virtual machines could require faster network links than other guests. Bandwidth or latency are often factors when deploying and maintaining guests, especially as requirements or load changes.
+ </div></dd><dt class="varlistentry"><span class="term">Request requirements</span></dt><dd><div class="para">
+ SCSI requests can only be issued to guest virtual machines on virtio drives if the virtio drives are backed by whole disks, and the disk device parameter is set to <code class="literal">lun</code>, as shown in the following example:
+ </div><pre class="screen"><devices>
+ <emulator>/usr/libexec/qemu-kvm</emulator>
+ <disk type='block' device='lun'></pre></dd></dl></div></div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install"><div class="titlepage"><div><div><h2 class="title">6.2. 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 guest virtual machines 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 that can be passed on the command line. To see a complete list of options run the following command:
+ </div><pre class="screen"># virt-install --help</pre><div class="para">
+ Note that you need root privileges in order for <code class="command">virt-install</code> commands to complete successfully. 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>--graphics</code></em> option which allows graphical installation of a virtual machine.
+ </div><div class="example" id="exam-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Using_virt_install_with_KVM_to_create_a_Red_Hat_Enterprise_Linux_3_guest"><h6>Example 6.1. Using virt-install to install a Fedora 19 guest virtual machine</h6><div class="example-contents"><div class="para">
+ This example creates a Fedora 19 guest:
+ </div><pre class="screen">virt-install \
+ --name=guest1-rhel5-64 \
+ --file=/var/lib/libvirt/images/guest1-rhel5-64.dsk \
+ --file-size=8 \
+ --nonsparse --graphics spice \
+ --vcpus=2 --ram=2048 \
+ --location=http://example1.com/installation_tree/RHEL5.6-Server-x86_64/os \
+ --network bridge=br0 \
+ --os-type=linux \
+ --os-variant=rhel5.4</pre></div></div><br class="example-break" /><div class="para">
+ Ensure that you select the correct <em class="parameter"><code>os-type</code></em> for your operating system when running this command.
+ </div><div class="para">
+ Refer to <code class="command">man virt-install</code> for more examples.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ When installing a Windows guest with <code class="command">virt-install</code>, the <code class="command">--os-type=<em class="replaceable"><code>windows</code></em></code> option is recommended. This option prevents the CD-ROM from disconnecting when rebooting during the installation procedure. The <code class="command">--os-variant</code> option further optimizes the configuration for a specific guest operating system.
+ </div></div></div></div><div xml:lang="en-US" class="section" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager" lang="en-US"><div class="titlepage"><div><div><h2 class="title">6.3. 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 guest virtual machines.
+ </div><div class="procedure" id="proc-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_a_virtualized_guest_with_virt_manager"><h6>Procedure 6.1. Creating a guest virtual machine with <span class="application"><strong>virt-manager</strong></span></h6><ol class="1"><li class="step"><p class="title"><strong>Open virt-manager</strong></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 class="step"><p class="title"><strong>Optional: Open a remote hypervisor</strong></p><div class="para">
+ Select the hypervisor and press the <span class="guibutton"><strong>Connect</strong></span> button to connect to the remote hypervisor.
+ </div></li><li class="step"><p class="title"><strong>Create a new virtual machine</strong></p><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>Create a new virtual machine</strong></span> button (<a class="xref" href="#virt-manager_main-png">Figure 6.1, “Virtual Machine Manager window”</a>) to open the <span class="guimenu"><strong>New VM</strong></span> wizard.
+ </div><div class="figure" id="virt-manager_main-png"><div class="figure-contents"><div class="mediaobject"><img src="images/rhel6_virt_manager.png" alt="Virtual Machine Manager window" /></div></div><h6>Figure 6.1. Virtual Machine Manager window</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guimenu"><strong>New VM</strong></span> wizard breaks down the virtual machine creation process into five steps:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Naming the guest virtual machine and choosing the installation type
+ </div></li><li class="listitem"><div class="para">
+ Locating and configuring the installation media
+ </div></li><li class="listitem"><div class="para">
+ Configuring memory and CPU options
+ </div></li><li class="listitem"><div class="para">
+ Configuring the virtual machine's storage
+ </div></li><li class="listitem"><div class="para">
+ Configuring networking, architecture, and other hardware settings
+ </div></li></ol></div><div class="para">
+ Ensure that <code class="command">virt-manager</code> can access the installation media (whether locally or over the network) before you continue.
+ </div></li><li class="step"><p class="title"><strong>Specify name and installation type</strong></p><div class="para">
+ The guest virtual machine creation process starts with the selection of a name and installation type. Virtual machine names can have underscores (<code class="computeroutput">_</code>), periods (<code class="computeroutput">.</code>), and hyphens (<code class="computeroutput">-</code>).
+ </div><div class="figure" id="Virtual_Machine_Name-guest-install-png"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt2-pic2.png" alt="Name virtual machine and select installation method" /></div></div><h6>Figure 6.2. Name virtual machine and select installation method</h6></div><br class="figure-break" /><div class="para">
+ Type in a virtual machine name and choose an installation type:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Local install media (ISO image or CDROM)</span></dt><dd><div class="para">
+ This method uses a CD-ROM, DVD, or image of an installation disk (for example, <code class="filename">.iso</code>).
+ </div></dd><dt class="varlistentry"><span class="term">Network Install (HTTP, FTP, or NFS)</span></dt><dd><div class="para">
+ Network installing involves the use of a mirrored Fedora installation tree to install a guest. The installation tree must be accessible through either HTTP, FTP, or NFS.
+ </div></dd><dt class="varlistentry"><span class="term">Network Boot (PXE)</span></dt><dd><div class="para">
+ This method uses a Preboot eXecution Environment (PXE) server to install the guest virtual machine. Setting up a PXE server is covered in the <em class="citetitle">Deployment Guide</em>. To install via network boot, the guest must have a routable IP address or shared network device. For information on the required networking configuration for PXE installation, refer to <a class="xref" href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE">Section 6.4, “Installing guest virtual machines with PXE”</a>.
+ </div></dd><dt class="varlistentry"><span class="term">Import existing disk image</span></dt><dd><div class="para">
+ This method allows you to create a new guest virtual machine and import a disk image (containing a pre-installed, bootable operating system) to it.
+ </div></dd></dl></div><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Configure installation</strong></p><div class="para">
+ Next, configure the <span class="guimenuitem"><strong>OS type</strong></span> and <span class="guimenuitem"><strong>Version</strong></span> of the installation. Ensure that you select the appropriate OS type for your virtual machine. Depending on the method of installation, provide the install URL or existing storage path.
+ </div><div class="figure" id="Virtual_Machine_Name-guest-install_STEP2-local-png"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt2-pic3.png" alt="Remote installation URL" /></div></div><h6>Figure 6.3. Remote installation URL</h6></div><br class="figure-break" /><div class="figure" id="Virtual_Machine_Name-guest-install_STEP2-import-png"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt1-pic5.png" alt="Local ISO image installation" /></div></div><h6>Figure 6.4. Local ISO image installation</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Configure CPU and memory</strong></p><div class="para">
+ The next step involves configuring the number of CPUs and amount of memory to allocate to the virtual machine. The wizard shows the number of CPUs and amount of memory you can allocate; configure these settings and click <span class="guibutton"><strong>Forward</strong></span>.
+ </div><div class="figure" id="Virtual_Machine_Name-guest-install_STEP2-cpumem-png"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt1-pic6.png" alt="Configuring CPU and Memory" /></div></div><h6>Figure 6.5. Configuring CPU and Memory</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Configure storage</strong></p><div class="para">
+ Assign storage to the guest virtual machine.
+ </div><div class="figure" id="Virtual_Machine_Name-guest-install_STEP4-png"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt1-pic7.png" alt="Configuring virtual storage" /></div></div><h6>Figure 6.6. Configuring virtual storage</h6></div><br class="figure-break" /><div class="para">
+ If you chose to import an existing disk image during the first step, <code class="command">virt-manager</code> will skip this step.
+ </div><div class="para">
+ Assign sufficient space for your virtual machine and any applications it requires, then click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Final configuration</strong></p><div class="para">
+ Verify the settings of the virtual machine and click <span class="guibutton"><strong>Finish</strong></span> when you are satisfied; doing so will create the virtual machine with default networking settings, virtualization type, and architecture.
+ </div><div class="figure" id="Virtual_Machine_Name-guest-install_STEP5-finish-png"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt1-pic9-local-storage.png" alt="Verifying the configuration" /></div></div><h6>Figure 6.7. Verifying the configuration</h6></div><br class="figure-break" /><div class="para">
+ If you prefer to further configure the virtual machine's hardware first, check the <span class="guimenuitem"><strong>Customize configuration before install</strong></span> box first before clicking <span class="guibutton"><strong>Finish</strong></span>. Doing so will open another wizard that will allow you to add, remove, and configure the virtual machine's hardware settings.
+ </div><div class="para">
+ After configuring the virtual machine's hardware, click <span class="guibutton"><strong>Apply</strong></span>. <code class="command">virt-manager</code> will then create the virtual machine with your specified hardware settings.
+ </div></li></ol></div></div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE"><div class="titlepage"><div><div><h2 class="title">6.4. Installing guest virtual machines with PXE</h2></div></div></div><div class="formalpara"><h5 class="formalpara" id="idm116019568">Requirements</h5>
+ PXE guest installation requires a PXE server running on the same subnet as the guest virtual machines you wish to install. The method of accomplishing this depends on how the virtual machines are connected to the network. Contact Support if you require assistance setting up a PXE server.
+ </div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE-PXE_installation_with_virt_install"><h5 class="formalpara">PXE installation with virt-install</h5>
+ <code class="command">virt-install</code> PXE installations require both the <code class="command">--network=bridge:installation</code> parameter, where <em class="parameter"><code>installation</code></em> is the name of your bridge, and the <em class="parameter"><code>--pxe</code></em> parameter.
+ </div><div class="para">
+ By default, if no network is found, the guest virtual machine attempts to boot from alternative bootable devices. If there is no other bootable device found, the guest pauses. You can use the <span class="application"><strong>qemu-kvm</strong></span> boot parameter <em class="parameter"><code>reboot-timeout</code></em> to allow the guest to retry booting if no bootable device is found, like so:
+ </div><pre class="screen"># qemu-kvm -boot reboot-timeout=1000</pre><div class="example" id="exam-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE-PXE_installation_with_virt_install"><h6>Example 6.2. Fully-virtualized PXE installation with virt-install</h6><div class="example-contents"><pre class="screen"># virt-install --hvm --connect qemu:///system \
+--network=bridge:installation --pxe --graphics spice \
+--name rhel6-machine --ram=756 --vcpus=4 \
+--os-type=linux --os-variant=rhel6 \
+--disk path=/var/lib/libvirt/images/rhel6-machine.img,size=10</pre><div class="para">
+ Note that the command above cannot be executed in a text-only environment. A fully-virtualized (<em class="parameter"><code>--hvm</code></em>) guest can only be installed in a text-only environment if the <em class="parameter"><code>--location</code></em> and <em class="parameter"><code>--extra-args "console=<em class="replaceable"><code>console_type</code></em>"</code></em> are provided instead of the <em class="parameter"><code>--graphics spice</code></em> parameter.
+ </div></div></div><br class="example-break" /><div class="procedure" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE-PXE_installation_with_virt_manager"><h6>Procedure 6.2. PXE installation with virt-manager</h6><ol class="1"><li class="step" id="step-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE-Select_PXE"><p class="title"><strong>Select PXE</strong></p><div class="para">
+ Select PXE as the installation method and follow the rest of the steps to configure the OS type, memory, CPU and storage settings.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt3-pic2.png" alt="Step 1 of 5 for creating a new virtual machine with virt-manager, with Network Boot (PXE) chosen for the method of installation." /></div></div><h6>Figure 6.8. Selecting the installation method</h6></div><br class="figure-break" /><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt3-pic3.png" alt="Step 2 of 5 for creating a new virtual machine with virt-manager, with Linux chosen as OS Type and Fedora 19 chosen for version." /></div></div><h6>Figure 6.9. Selecting the installation type</h6></div><br class="figure-break" /><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt3-pic4.png" alt="Step 3 of 5 for creating a new virtual machine with virt-manager showing memory and CPU settings, with 1024MB of RAM and 2 CPUs selected
." /></div></div><h6>Figure 6.10. Specifying virtualized hardware details</h6></div><br class="figure-break" /><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt3-pic5.png" alt="Step 4 of 5 for creating a new virtual machine with virt-manager, with checkboxes selected next to "Enable storage for this virtual machine" and "Allocate entire disk now". 8GB is selected under the heading "Create a disk image on the computer's hard drive"." /></div></div><h6>Figure 6.11. Specifying storage details</h6></div><br class="figure-break" /></li><li class="step" id="step-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Start_the_installation"><p class="title"><strong>Start the installation</strong></p><div class="para">
+ The installation is ready to start.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/PXEguest_5of5.png" width="444" alt="Step 5 of 5 for creating a new virtual machine with virt-manager reads "Ready to begin installation of (guest name)" with a summary of options already chosen, and advanced options to choose from." /></div></div><h6>Figure 6.12. Finalizing virtual machine details</h6></div><br class="figure-break" /></li></ol></div><div class="para">
+ A DHCP request is sent and if a valid PXE server is found the guest virtual machine's installation processes will start.
+ </div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 7. Installing a Red Hat Enterprise Linux 6 guest virtual machine on a Red Hat Enterprise Linux 6 host</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#idm97583616">7.1. Creating a Red Hat Enterprise Linux 6 guest with local installation media</a></span></dt><dt><span class="section"><a href="#idm79824096">7.2. Creating a Red Hat Enterprise Linux 6 guest with a network installation tree</a></span></dt><dt><span class="section"><a href="#idm79226176">7.3. Creating a Red Hat Enterprise Linux 6 guest with PXE</a></span></dt></dl></div><div class="para">
+ This chapter covers how to install a Red Hat Enterprise Linux 6 guest virtual machine on a Red Hat Enterprise Linux 6 host.
+ </div><div class="para">
+ These procedures assume that the KVM hypervisor and all other required packages are installed and the host is configured for virtualization.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ For more information on installing the virtualization packages, refer to <a class="xref" href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation">Chapter 5, <em>Installing the virtualization packages</em></a>.
+ </div></div></div><div class="section" id="idm97583616"><div class="titlepage"><div><div><h2 class="title" id="idm97583616">7.1. Creating a Red Hat Enterprise Linux 6 guest with local installation media</h2></div></div></div><div class="para">
+ This procedure covers creating a Red Hat Enterprise Linux 6 guest virtual machine with a locally stored installation DVD or DVD image. DVD images are available from <a href="http://access.redhat.com">http://access.redhat.com</a> for Red Hat Enterprise Linux 6.
+ </div><div class="procedure"><h6>Procedure 7.1. Creating a Red Hat Enterprise Linux 6 guest virtual machine with virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Optional: Preparation</strong></p><div class="para">
+ Prepare the storage environment for the virtual machine. For more information on preparing storage, refer to the <em class="citetitle">Red Hat Enterprise Linux 6 Virtualization Administration Guide</em>.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Various storage types may be used for storing guest virtual machines. However, for a virtual machine to be able to use migration features the virtual machine must be created on networked storage.
+ </div></div></div><div class="para">
+ Red Hat Enterprise Linux 6 requires at least 1GB of storage space. However, Red Hat recommends at least 5GB of storage space for a Red Hat Enterprise Linux 6 installation and for the procedures in this guide.
+ </div></li><li class="step"><p class="title"><strong>Open virt-manager and start the wizard</strong></p><div class="para">
+ Open virt-manager by executing the <code class="command">virt-manager</code> command as root or opening <span class="guilabel"><strong>Applications</strong></span> → <span class="guilabel"><strong>System Tools</strong></span> → <span class="guilabel"><strong>Virtual Machine Manager</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/1-7RHEL_local_install.png" width="444" alt="The Virtual Machine Manager window" /></div></div><h6>Figure 7.1. The Virtual Machine Manager window</h6></div><br class="figure-break" /><div class="para">
+ Click on the <span class="guibutton"><strong>Create a new virtual machine</strong></span> button to start the new virtualized guest wizard.
+ </div><div class="figure" id="gofigurego"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_newicon.png" alt="The Create a new virtual machine button" /></div></div><h6>Figure 7.2. The Create a new virtual machine button</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guilabel"><strong>New VM</strong></span> window opens.
+ </div></li><li class="step"><p class="title"><strong>Name the virtual machine</strong></p><div class="para">
+ Virtual machine names can contain letters, numbers and the following characters: '<span class="keycap"><strong>_</strong></span>', '<span class="keycap"><strong>.</strong></span>' and '<span class="keycap"><strong>-</strong></span>'. Virtual machine names must be unique for migration and cannot consist only of numbers.
+ </div><div class="para">
+ Choose the <span class="guilabel"><strong>Local install media (ISO image or CDROM)</strong></span> radio button.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/2-7RHEL_local_install.png" width="444" alt="The New VM window - Step 1" /></div></div><h6>Figure 7.3. The New VM window - Step 1</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Select the installation media</strong></p><div class="para">
+ Select the appropriate radio button for your installation media.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/3-7RHEL_local_install.png" width="444" alt="Locate your install media" /></div></div><h6>Figure 7.4. Locate your install media</h6></div><br class="figure-break" /><ul class="stepalternatives">
+ <li class="step"><div class="para">
+ If you wish to install from a CD-ROM or DVD, select the <span class="guilabel"><strong>Use CDROM or DVD</strong></span> radio button, and select the appropriate disk drive from the drop-down list of drives available.
+ </div></li>
+ <li class="step"><div class="para">
+ If you wish to install from an ISO image, select <span class="guilabel"><strong>Use ISO image</strong></span>, and then click the <span class="guibutton"><strong>Browse...</strong></span> button to open the <span class="guilabel"><strong>Locate media volume</strong></span> window.
+ </div><div class="para">
+ Select the installation image you wish to use, and click <span class="guibutton"><strong>Choose Volume</strong></span>.
+ </div><div class="para">
+ If no images are displayed in the <span class="guilabel"><strong>Locate media volume</strong></span> window, click on the <span class="guibutton"><strong>Browse Local</strong></span> button to browse the host machine for the installation image or DVD drive containing the installation disk. Select the installation image or DVD drive containing the installation disk and click <span class="guibutton"><strong>Open</strong></span>; the volume is selected for use and you are returned to the <span class="guilabel"><strong>Create a new virtual machine</strong></span> wizard.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ For ISO image files and guest storage images, the recommended location to use is <code class="filename">/var/lib/libvirt/images/</code>. Any other location may require additional configuration by SELinux. Refer to the Red Hat Enterprise Linux 6 <em class="citetitle">Virtualization Administration Guide</em> for more details on configuring SELinux.
+ </div></div></div></li>
+
+ </ul><div class="para">
+ Select the operating system type and version which match the installation media you have selected.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/5-7RHEL_local_install.png" width="444" alt="The New VM window - Step 2" /></div></div><h6>Figure 7.5. The New VM window - Step 2</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title" id="RAM-and-VCPUs"><strong>Set RAM and virtual CPUs</strong></p><div class="para">
+ Choose appropriate values for the virtual CPUs and RAM allocation. These values affect the host's and guest's performance. Memory and virtual CPUs can be overcommitted. For more information on overcommitting, refer to the <em class="citetitle">Red Hat Enterprise Linux 6 Virtualization Administration Guide</em>.
+ </div><div class="para">
+ Virtual machines require sufficient physical memory (RAM) to run efficiently and effectively. Red Hat supports a minimum of 512MB of RAM for a virtual machine. Red Hat recommends at least 1024MB of RAM for each logical core.
+ </div><div class="para">
+ Assign sufficient virtual CPUs for the virtual machine. If the virtual machine runs a multithreaded application, assign the number of virtual CPUs the guest virtual machine will require to run efficiently.
+ </div><div class="para">
+ You cannot assign more virtual CPUs than there are physical processors (or hyper-threads) available on the host system. The number of virtual CPUs available is noted in the <span class="guilabel"><strong>Up to <em class="replaceable"><code>X</code></em> available</strong></span> field.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/6-7RHEL_local_install.png" width="444" alt="The new VM window - Step 3" /></div></div><h6>Figure 7.6. The new VM window - Step 3</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Storage</strong></p><div class="para">
+ Enable and assign storage for the Red Hat Enterprise Linux 6 guest virtual machine. Assign at least 5GB for a desktop installation or at least 1GB for a minimal installation.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Live and offline migrations require virtual machines to be installed on shared network storage. For information on setting up shared storage for virtual machines, refer to the <em class="citetitle">Red Hat Enterprise Linux Virtualization Administration Guide</em>.
+ </div></div></div><ol class="a"><li class="step"><p class="title"><strong>With the default local storage</strong></p><div class="para">
+ Select the <span class="guilabel"><strong>Create a disk image on the computer's hard drive</strong></span> radio button to create a file-based image in the default storage pool, the <code class="filename">/var/lib/libvirt/images/</code> directory. Enter the size of the disk image to be created. If the <span class="guilabel"><strong>Allocate entire disk now</strong></span> check box is selected, a disk image of the size specified will be created immediately. If not, the disk image will grow as it becomes filled.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/7-7RHEL_local_install.png" width="444" alt="The New VM window - Step 4" /></div></div><h6>Figure 7.7. The New VM window - Step 4</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to create a disk image on the local hard drive. Alternatively, select <span class="guilabel"><strong>Select managed or other existing storage</strong></span>, then select <span class="guilabel"><strong>Browse</strong></span> to configure managed storage.
+ </div></li><li class="step"><p class="title"><strong>With a storage pool</strong></p><div class="para">
+ If you selected <span class="guilabel"><strong>Select managed or other existing storage</strong></span> in the previous step to use a storage pool and clicked <span class="guilabel"><strong>Browse</strong></span>, the <span class="guilabel"><strong>Locate or create storage volume</strong></span> window will appear.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/8-7RHEL_local_install.png" width="444" alt="The Locate or create storage volume window" /></div></div><h6>Figure 7.8. The Locate or create storage volume window</h6></div><br class="figure-break" /><ol class="i"><li class="step"><div class="para">
+ Select a storage pool from the <span class="guilabel"><strong>Storage Pools</strong></span> list.
+ </div></li><li class="step"><div class="para">
+ Optional: Click on the <span class="guilabel"><strong>New Volume</strong></span> button to create a new storage volume. The <span class="guilabel"><strong>Add a Storage Volume</strong></span> screen will appear. Enter the name of the new storage volume.
+ </div><div class="para">
+ Choose a format option from the <span class="guilabel"><strong>Format</strong></span> dropdown menu. Format options include raw, cow, qcow, qcow2, qed, vmdk, and vpc. Adjust other fields as desired.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/9-7RHEL_local_install.png" width="444" alt="The Add a Storage Volume window" /></div></div><h6>Figure 7.9. The Add a Storage Volume window</h6></div><br class="figure-break" /></li></ol></li></ol><div class="para">
+ Click <span class="guibutton"><strong>Finish</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Verify and finish</strong></p><div class="para">
+ Verify there were no errors made during the wizard and everything appears as expected.
+ </div><div class="para">
+ Select the <span class="guilabel"><strong>Customize configuration before install</strong></span> check box to change the guest's storage or network devices, to use the para-virtualized drivers or to add additional devices.
+ </div><div class="para">
+ Click on the <code class="systemitem">Advanced options</code> down arrow to inspect and modify advanced options. For a standard Red Hat Enterprise Linux 6 installation, none of these options require modification.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/11-7RHEL_local_install.png" width="444" alt="The New VM window - local storage" /></div></div><h6>Figure 7.10. The New VM window - local storage</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Finish</strong></span> to continue into the Red Hat Enterprise Linux installation sequence. For more information on installing Red Hat Enterprise Linux 6 refer to the Red Hat Enterprise Linux 6 <em class="citetitle">Installation Guide</em>.
+ </div></li></ol></div><div class="para">
+ A Red Hat Enterprise Linux 6 guest virtual machine is now created from an ISO installation disc image.
+ </div></div><div class="section" id="idm79824096"><div class="titlepage"><div><div><h2 class="title" id="idm79824096">7.2. Creating a Red Hat Enterprise Linux 6 guest with a network installation tree</h2></div></div></div><div class="procedure"><h6>Procedure 7.2. Creating a Red Hat Enterprise Linux 6 guest with virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Optional: Preparation</strong></p><div class="para">
+ Prepare the storage environment for the guest virtual machine. For more information on preparing storage, refer to the <em class="citetitle">Red Hat Enterprise Linux 6 Virtualization Administration Guide</em>.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ >Various storage types may be used for storing guest virtual machines. However, for a virtual machine to be able to use migration features the virtual machine must be created on networked storage.
+ </div></div></div><div class="para">
+ Red Hat Enterprise Linux 6 requires at least 1GB of storage space. However, Red Hat recommends at least 5GB of storage space for a Red Hat Enterprise Linux 6 installation and for the procedures in this guide.
+ </div></li><li class="step"><p class="title"><strong>Open virt-manager and start the wizard</strong></p><div class="para">
+ Open virt-manager by executing the <code class="command">virt-manager</code> command as root or opening <span class="guilabel"><strong>Applications</strong></span> → <span class="guilabel"><strong>System Tools</strong></span> → <span class="guilabel"><strong>Virtual Machine Manager</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt1-pic1.png" alt="The main virt-manager window" /></div></div><h6>Figure 7.11. The main virt-manager window</h6></div><br class="figure-break" /><div class="para">
+ Click on the <span class="guibutton"><strong>Create a new virtual machine</strong></span> button to start the new virtual machine wizard.
+ </div><div class="figure" id="gofigurego2"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_newicon.png" alt="The Create a new virtual machine button" /></div></div><h6>Figure 7.12. The Create a new virtual machine button</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guilabel"><strong>Create a new virtual machine</strong></span> window opens.
+ </div></li><li class="step"><p class="title"><strong>Name the virtual machine</strong></p><div class="para">
+ Virtual machine names can contain letters, numbers and the following characters: '<span class="keycap"><strong>_</strong></span>', '<span class="keycap"><strong>.</strong></span>' and '<span class="keycap"><strong>-</strong></span>'. Virtual machine names must be unique for migration and cannot consist only of numbers.
+ </div><div class="para">
+ Choose the installation method from the list of radio buttons.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/rhel6_Screenshot-step1.png" width="444" alt="The New VM window - Step 1" /></div></div><h6>Figure 7.13. The New VM window - Step 1</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><div class="para">
+ Provide the installation URL, and the Kickstart URL and Kernel options if required.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt2-pic3.png" alt="The New VM window - Step 2" /></div></div><h6>Figure 7.14. The New VM window - Step 2</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><div class="para">
+ The remaining steps are the same as the ISO installation procedure. Continue from <a class="xref" href="#RAM-and-VCPUs">Step 5</a> of the ISO installation procedure.
+ </div></li></ol></div></div><div class="section" id="idm79226176"><div class="titlepage"><div><div><h2 class="title" id="idm79226176">7.3. Creating a Red Hat Enterprise Linux 6 guest with PXE</h2></div></div></div><div class="procedure"><h6>Procedure 7.3. Creating a Red Hat Enterprise Linux 6 guest with virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Optional: Preparation</strong></p><div class="para">
+ Prepare the storage environment for the virtual machine. For more information on preparing storage, refer to the <em class="citetitle">Red Hat Enterprise Linux 6 Virtualization Administration Guide</em>.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Various storage types may be used for storing guest virtual machines. However, for a virtual machine to be able to use migration features the virtual machine must be created on networked storage.
+ </div></div></div><div class="para">
+ Red Hat Enterprise Linux 6 requires at least 1GB of storage space. However, Red Hat recommends at least 5GB of storage space for a Red Hat Enterprise Linux 6 installation and for the procedures in this guide.
+ </div></li><li class="step"><p class="title"><strong>Open virt-manager and start the wizard</strong></p><div class="para">
+ Open virt-manager by executing the <code class="command">virt-manager</code> command as root or opening <span class="guilabel"><strong>Applications</strong></span> → <span class="guilabel"><strong>System Tools</strong></span> → <span class="guilabel"><strong>Virtual Machine Manager</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt1-pic1.png" alt="The main virt-manager window" /></div></div><h6>Figure 7.15. The main virt-manager window</h6></div><br class="figure-break" /><div class="para">
+ Click on the <span class="guibutton"><strong>Create new virtualized guest</strong></span> button to start the new virtualized guest wizard.
+ </div><div class="figure" id="gofigurego3"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_newicon.png" alt="The create new virtualized guest button" /></div></div><h6>Figure 7.16. The create new virtualized guest button</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guilabel"><strong>New VM</strong></span> window opens.
+ </div></li><li class="step"><p class="title"><strong>Name the virtual machine</strong></p><div class="para">
+ Virtual machine names can contain letters, numbers and the following characters: '<span class="keycap"><strong>_</strong></span>', '<span class="keycap"><strong>.</strong></span>' and '<span class="keycap"><strong>-</strong></span>'. Virtual machine names must be unique for migration and cannot consist only of numbers.
+ </div><div class="para">
+ Choose the installation method from the list of radio buttons.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt3-pic2.png" alt="The New VM window - Step 1" /></div></div><h6>Figure 7.17. The New VM window - Step 1</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><div class="para">
+ The remaining steps are the same as the ISO installation procedure. Continue from <a class="xref" href="#RAM-and-VCPUs">Step 5</a> of the ISO installation procedure. From this point, the only difference in this PXE procedure is on the final <span class="guilabel"><strong>New VM</strong></span> screen, which shows the <span class="guilabel"><strong>Install: PXE Install</strong></span> field.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt3-pic6.png" alt="The New VM window - Step 5 - PXE Install" /></div></div><h6>Figure 7.18. The New VM window - Step 5 - PXE Install</h6></div><br class="figure-break" /></li></ol></div></div></div><div xml:lang="en-US" class="chapter" id="idm59023216" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="idm59023216">Chapter 8. Virtualizing Fedora on Other Platforms</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#idm14786592">8.1. On VMWare</a></span></dt><dt><span class="section"><a href="#idm99614112">8.2. On Hyper-V</a></span></dt></dl></div><div class="para">
+ This chapter contains useful reference material for customers running Fedora as a virtualized operating system on other virtualization hosts.
+ </div><div class="section" id="idm14786592"><div class="titlepage"><div><div><h2 class="title" id="idm14786592">8.1. On VMWare</h2></div></div></div><div class="para">
+ Fedora 17 and onwards provide the <code class="systemitem">vmxnet3</code> driver, a para-virtualized network adapter used when running Red Hat Enterprise Linux on VMWare hosts. For further information about this driver, refer to <a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001805">http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001805</a>.
+ </div><div class="para">
+ Fedora 18 and onwards provide the <code class="systemitem">vmw_pvscsi</code> driver, a para-virtualized SCSI adapter used when running Red Hat Enterprise Linux on VMWare hosts. For further information about this driver, refer to <a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010398">http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010398</a>.
+ </div></div><div class="section" id="idm99614112"><div class="titlepage"><div><div><h2 class="title" id="idm99614112">8.2. On Hyper-V</h2></div></div></div><div class="para">
+ Fedora 18 and onwards provide Microsoft's Linux Integration Services, a set of drivers that enable synthetic device support in supported virtualized operating systems. Fedora is a supported virtualized operating system under Linux Integration Services version 3.4. Further details about the drivers provided are available from <a href="http://www.microsoft.com/en-us/download/details.aspx?id=34603">http://www.microsoft.com/en-us/download/details.aspx?id=34603</a>.
+ </div></div></div><div xml:lang="en-US" class="chapter" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 9. Installing a fully-virtualized Windows guest</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_virt-install">9.1. Using virt-install to create a guest</a></span></dt></dl></div><div class="para">
+ This chapter describes how to create a fully-virtualized Windows guest using the command-line (<code class="command">virt-install</code>), launch the operating system's installer inside the guest, and access the installer through <code class="command">virt-viewer</code>.
+ </div><div class="para">
+ To install a Windows operating system on the guest, use the <code class="command">virt-viewer</code> tool. This tool allows you to display the graphical console of a virtual machine (via the VNC protocol). In doing so, <code class="command">virt-viewer</code> allows you to install a fully-virtualized guest's operating system with that operating system's installer (for example, the Windows XP installer).
+ </div><div class="para">
+ Installing a Windows operating system involves two major steps:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Creating the guest virtual machine, using either <code class="command">virt-install</code> or <code class="command">virt-manager</code>.
+ </div></li><li class="listitem"><div class="para">
+ Installing the Windows operating system on the guest virtual machine, using <code class="command">virt-viewer</code>.
+ </div></li></ol></div><div class="para">
+ Refer to <a class="xref" href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation">Chapter 6, <em>Guest virtual machine installation overview</em></a> for details about creating a guest virtual machine with <code class="command">virt-install</code> or <code class="command">virt-manager</code>.
+ </div><div class="para">
+ Note that this chapter does not describe how to install a Windows operating system on a fully-virtualized guest. Rather, it only covers how to create the guest and launch the installer within the guest. For information on how to install a Windows operating system, refer to the relevant Microsoft installation documentation.
+ </div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_virt-install"><div class="titlepage"><div><div><h2 class="title">9.1. Using virt-install to create a guest</h2></div></div></div><div class="para">
+ The <code class="command">virt-install</code> command allows you to create a fully-virtualized guest from a terminal, for example, without a GUI.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Before creating the guest, consider first if the guest needs to use KVM Windows para-virtualized drivers. If it does, keep in mind that you can do so <span class="emphasis"><em>during</em></span> or <span class="emphasis"><em>after</em></span> installing the Windows operating system on the guest. For more information about para-virtualized drivers, refer to <a class="xref" href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers">Chapter 10, <em>KVM Para-virtualized Drivers</em></a>.
+ </div><div class="para">
+ For instructions on how to install KVM para-virtualized drivers, refer to <a class="xref" href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers">Section 10.1, “Installing the KVM Windows para-virtualized drivers”</a>.
+ </div></div></div><div class="para">
+ It is possible to create a fully-virtualized guest with only a single command. To do so, run the following program (replace the values accordingly):
+ </div><pre class="screen"># virt-install \
+ --name=<em class="replaceable"><code>guest-name</code></em> \
+ --os-type=<em class="replaceable"><code>windows</code></em> \
+ --network network=default \
+ --disk path=<em class="replaceable"><code>path-to-disk</code></em>,size=<em class="replaceable"><code>disk-size</code></em> \
+ --cdrom=<em class="replaceable"><code>path-to-install-disk</code></em> \
+ --graphics spice --ram=1024</pre><div class="para">
+ The <code class="command"><em class="replaceable"><code>path-to-disk</code></em></code> must be a device (e.g. <code class="filename">/dev/sda3</code>) or image file (<code class="filename">/var/lib/libvirt/images/<em class="replaceable"><code>name</code></em>.img</code>). It must also have enough free space to support the <code class="command"><em class="replaceable"><code>disk-size</code></em></code>.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ All image files are stored in <code class="filename">/var/lib/libvirt/images/</code> by default. Other directory locations for file-based images are possible, but may require SELinux configuration. If you run SELinux in enforcing mode.
+ </div></div></div><div class="para">
+ You can also run <code class="command">virt-install</code> interactively. To do so, use the <code class="command">--prompt</code> command, as in:
+ </div><pre class="screen"># virt-install --prompt</pre><div class="para">
+ Once the fully-virtualized guest is created, <code class="command">virt-viewer</code> will launch the guest and run the operating system's installer. Refer to to the relevant Microsoft installation documentation for instructions on how to install the operating system.
+ </div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 10. KVM Para-virtualized Drivers</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers">10.1. Installing the KVM Windows para-virtualized drivers</a></span></dt><dt><span class="section"><a href="#form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager">10.2. Installing the drivers on an installed Windows guest virtual machine</a></span></dt><dt><span class="section"><a href="#form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk"
>10.3. Installing drivers during the Windows installation</a></span></dt><dt><span class="section"><a href="#idm115640352">10.4. Using the para-virtualized drivers with Red Hat Enterprise Linux 3.9 guests</a></span></dt><dt><span class="section"><a href="#form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices">10.5. Using KVM para-virtualized drivers for existing devices</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices">10.6. Using KVM para-virtualized drivers for new devices</a></span></dt></dl></div><div class="para">
+ Para-virtualized drivers are available for Windows guest virtual machines 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 the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Red Hat Enterprise Linux 4.8 and newer
+ </div></li><li class="listitem"><div class="para">
+ Red Hat Enterprise Linux 5.3 and newer
+ </div></li><li class="listitem"><div class="para">
+ Red Hat Enterprise Linux 6 and newer
+ </div></li><li class="listitem"><div class="para">
+ Some versions of Linux based on the 2.6.27 kernel or newer kernel versions.
+ </div></li></ul></div><div class="para">
+ Versions of Red Hat Enterprise Linux in the list above detect and install the drivers, additional installation steps are not required.
+ </div><div class="para">
+ In Red Hat Enterprise Linux 3 (3.9 and above), manual installation is required.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ PCI devices are limited by the virtualized system architecture. Refer to <a class="xref" href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config">Chapter 12, <em>PCI device configuration</em></a> for additional limitations when using assigned devices.
+ </div></div></div><div class="para">
+ Using KVM para-virtualized drivers, the following Microsoft Windows versions are expected to run similarly to bare-metal-based systems.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Windows XP Service Pack 3 and newer (32-bit only)
+ </div></li><li class="listitem"><div class="para">
+ Windows Server 2003 (32-bit and 64-bit versions)
+ </div></li><li class="listitem"><div class="para">
+ Windows Server 2008 (32-bit and 64-bit versions)
+ </div></li><li class="listitem"><div class="para">
+ Windows Server 2008 R2 (64-bit only)
+ </div></li><li class="listitem"><div class="para">
+ Windows 7 (32-bit and 64-bit versions)
+ </div></li></ul></div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers"><div class="titlepage"><div><div><h2 class="title">10.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 a guest virtual machine using one of the following methods:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ hosting the installation files on a network accessible to the virtual machine,
+ </div></li><li class="listitem"><div class="para">
+ using a virtualized CD-ROM device of the driver installation disk .iso file, or
+ </div></li><li class="listitem"><div class="para">
+ using a virtualized floppy device to install the drivers during boot time.
+ </div></li></ul></div><div class="para">
+ This guide describes installation from the para-virtualized installer disk as a virtualized CD-ROM device.
+ </div><div class="procedure"><ol class="1"><li class="step" id="step-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Download_the_drivers"><p class="title"><strong>Download the drivers</strong></p><div class="para">
+ The <span class="package">virtio-win</span> package contains the para-virtualized block and network drivers for all supported Windows guest virtual machines.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The <span class="package">virtio-win</span> package can be found here in RHN: <a href="https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=602010">https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=602010</a>. It requires access to one of the following channels:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ RHEL Client Supplementary (v. 6)
+ </div></li><li class="listitem"><div class="para">
+ RHEL Server Supplementary (v. 6)
+ </div></li><li class="listitem"><div class="para">
+ RHEL Workstation Supplementary (v. 6)
+ </div></li></ul></div></div></div><div class="para">
+ Download and install the <span class="package">virtio-win</span> package on the host with the <code class="command">yum</code> command.
+ </div><pre class="screen"> # yum install virtio-win</pre><div class="para">
+ The list of virtio-win packages that are supported on Windows operating systems, and the current certified package version, can be found at the following URL: <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">
+ Note that the Red Hat Enterprise Virtualization Hypervisor and Red Hat Enterprise Linux are created on the same code base so the drivers for the same version (for example, Red Hat Enterprise Virtualization Hypervisor 3.0 and Red Hat Enterprise Linux 6) are supported for both environments.
+ </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 class="step" id="step-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Install_the_para_virtualized_drivers"><p class="title"><strong>Install the para-virtualized drivers</strong></p><div class="para">
+ It is recommended to install the drivers on the virtual machine 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 virtual machine, the drivers must be installed before the device is modified. If the drivers are not installed on the virtual machine and the driver is set to the virtio driver the virtual machine will not boot.
+ </div></li></ol></div></div><div class="section" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager"><div class="titlepage"><div><div><h2 class="title">10.2. Installing the drivers on an installed Windows guest virtual machine</h2></div></div></div><div class="para">
+ This procedure covers installing the para-virtualized drivers with a virtualized CD-ROM after Windows is installed.
+ </div><div class="para">
+ Follow <a class="xref" href="#proc-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_virt_manager_to_mount_a_CD_ROM_image_for_a_Windows_guest">Procedure 10.1, “Installing from the driver CD-ROM image with virt-manager”</a> to add a CD-ROM image with <code class="command">virt-manager</code> and then install the drivers.
+ </div><div class="procedure" id="proc-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_virt_manager_to_mount_a_CD_ROM_image_for_a_Windows_guest"><h6>Procedure 10.1. Installing from the driver CD-ROM image with virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Open virt-manager and the guest virtual machine</strong></p><div class="para">
+ Open <code class="command">virt-manager</code>, then open the guest virtual machine from the list by double-clicking the guest name.
+ </div></li><li class="step"><p class="title"><strong>Open the hardware window</strong></p><div class="para">
+ Click the lightbulb icon on the toolbar at the top of the window to view virtual hardware details.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/vm_info_button_new.png" alt="The Show virtual hardware details button." /></div></div><h6>Figure 10.1. The virtual hardware details button</h6></div><br class="figure-break" /><div class="para">
+ Then click the <span class="guibutton"><strong>Add Hardware</strong></span> button at the bottom of the new view that appears.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/vm_add_hardware_new.png" alt="The Add Hardware button." /></div></div><h6>Figure 10.2. The virtual machine hardware information window</h6></div><br class="figure-break" /><div class="para">
+ This opens a wizard for adding the new device.
+ </div></li><li class="step"><p class="title"><strong>Select the device type — for Red Hat Enterprise Linux 6 versions prior to 6.2</strong></p><div class="para">
+ Skip this step if you are using Red Hat Enterprise Linux 6.2 or later.
+ </div><div class="para">
+ On Red Hat Enterprise Linux 6 versions prior to version 6.2, you must select the type of device you wish to add. In this case, select <span class="guilabel"><strong>Storage</strong></span> from the dropdown menu.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_hardware_wizard1.png" alt="The Add new virtual hardware wizard window in Red Hat Enterprise Linux 6.1 with Storage selected as the hardware type." /></div></div><h6>Figure 10.3. The Add new virtual hardware wizard in Red Hat Enterprise Linux 6.1</h6></div><br class="figure-break" /><div class="para">
+ Click the <span class="guibutton"><strong>Finish</strong></span> button to proceed.
+ </div></li><li class="step"><p class="title"><strong>Select the ISO file</strong></p><div class="para">
+ Ensure that the <span class="guilabel"><strong>Select managed or other existing storage</strong></span> radio button is selected, and browse to the para-virtualized driver's <code class="filename">.iso</code> image file. The default location for the latest version of the drivers is <code class="filename">/usr/share/virtio-win/virtio-win.iso</code>.
+ </div><div class="para">
+ Change the <span class="guilabel"><strong>Device type</strong></span> to <span class="guilabel"><strong>IDE cdrom</strong></span> and click the <span class="guibutton"><strong>Forward</strong></span> button to proceed.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/type_assigned-KVM_PV_new.png" width="444" alt="Selecting the ISO file in the Add new virtual hardware wizard window." /></div></div><h6>Figure 10.4. The Add new virtual hardware wizard</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Finish adding virtual hardware — for Red Hat Enterprise Linux 6 versions prior to 6.2</strong></p><div class="para">
+ If you are using Red Hat Enterprise Linux 6.2 or later, skip this step.
+ </div><div class="para">
+ On Red Hat Enterprise Linux 6 versions prior to version 6.2, click on the <span class="guibutton"><strong>Finish</strong></span> button to finish adding the virtual hardware and close the wizard.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/done-KVM_PV.png" alt="The final screen of the Add new virtual hardware wizard in Red Hat Enterprise Linux 6.1." /></div></div><h6>Figure 10.5. The Add new virtual hardware wizard in Red Hat Enterprise Linux 6.1</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Reboot</strong></p><div class="para">
+ Reboot or start the virtual machine to begin using the driver disc. Virtualized IDE devices require a restart to for the virtual machine to recognize the new device.
+ </div></li></ol></div><div class="para">
+ Once the CD-ROM with the drivers is attached and the virtual machine has started, proceed with <a class="xref" href="#wooras">Procedure 10.2, “Windows installation on a Windows 7 virtual machine”</a>.
+ </div><div class="procedure" id="wooras"><h6>Procedure 10.2. Windows installation on a Windows 7 virtual machine</h6><div class="para">
+ This procedure installs the drivers on a Windows 7 virtual machine as an example. Adapt the Windows installation instructions to your guest's version of Windows.
+ </div><ol class="1"><li class="step"><p class="title"><strong>Open the Computer Management window</strong></p><div class="para">
+ On the desktop of the Windows virtual machine, click the <span class="guibutton"><strong>Windows</strong></span> icon at the bottom corner of the screen to open the Start menu.
+ </div><div class="para">
+ Right-click on <span class="guilabel"><strong>Computer</strong></span> and select <span class="guilabel"><strong>Manage</strong></span> from the pop-up menu.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/StartDevManagerInVM_win7.png" width="444" alt="A menu window opens on the Computer Management window when right-clicking D the My Computer icon on the desktop." /></div></div><h6>Figure 10.6. The Computer Management window</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Open the Device Manager</strong></p><div class="para">
+ Select the <span class="guilabel"><strong>Device Manager</strong></span> from the left-most pane. This can be found under <span class="guilabel"><strong>Computer Management</strong></span> > <span class="guilabel"><strong>System Tools</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/DevManagerStart_win7.png" width="444" alt="Opening the Device Manager on the right hand side of the Computer Management window." /></div></div><h6>Figure 10.7. The Computer Management window</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Start the driver update wizard</strong></p><ol class="a"><li class="step"><p class="title"><strong>View available system devices</strong></p><div class="para">
+ Expand <span class="guilabel"><strong>System devices</strong></span> by clicking on the arrow to its left.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/DriverInstall-Expand.png" width="444" alt="Detail of viewing available system devices from the Computer Management window." /></div></div><h6>Figure 10.8. Viewing available system devices in the Computer Management window</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Locate the appropriate device</strong></p><div class="para">
+ There are up to four drivers available: the balloon driver, the serial driver, the network driver, and the block driver.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">Balloon</code>, the balloon driver, affects the <span class="guilabel"><strong>PCI standard RAM Controller</strong></span> in the <span class="guilabel"><strong>System devices</strong></span> group.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">vioserial</code>, the serial driver, affects the <span class="guilabel"><strong>PCI Simple Communication Controller</strong></span> in the <span class="guilabel"><strong>System devices</strong></span> group.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">NetKVM</code>, the network driver, affects the <span class="guilabel"><strong>Network adapters</strong></span> group. This driver is only available if a virtio NIC is configured. Configurable parameters for this driver are documented in <a class="xref" href="#netkvm-parameters">Appendix C, <em>NetKVM Driver Parameters</em></a>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">viostor</code>, the block driver, affects the <span class="guilabel"><strong>Disk drives</strong></span> group. This driver is only available if a virtio disk is configured.
+ </div></li></ul></div><div class="para">
+ Right-click on the device whose driver you wish to update, and select <span class="guilabel"><strong>Update Driver...</strong></span> from the pop-up menu.
+ </div><div class="para">
+ This example installs the balloon driver, so right-click on <span class="guilabel"><strong>PCI standard RAM Controller</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/StartInstallingBalloon-1_win7.png" width="444" alt="Locate the appropriate device under the expanded System Devices entry in the Computer Management window." /></div></div><h6>Figure 10.9. The Computer Management window</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Open the driver update wizard</strong></p><div class="para">
+ From the drop-down menu, select <span class="guilabel"><strong>Update Driver Software...</strong></span> to access the driver update wizard.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/DriverInstall-OpenWizard_win7.png" alt="Open the driver update wizard by right-clicking the device to be updated and selecting the first menu option, Update Driver Software, in the Computer Management window." /></div></div><h6>Figure 10.10. Opening the driver update wizard</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Specify how to find the driver</strong></p><div class="para">
+ The first page of the driver update wizard asks how you want to search for driver software. Click on the second option, <span class="guilabel"><strong>Browse my computer for driver software</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/8-BrowseForDriver_win7.png" width="444" alt="The driver update wizard provides two options for searching for driver software." /></div></div><h6>Figure 10.11. The driver update wizard</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Select the driver to install</strong></p><ol class="a"><li class="step"><p class="title"><strong>Open a file browser</strong></p><div class="para">
+ Click on <span class="guilabel"><strong>Browse...</strong></span>
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/10-w7x86driverstart_win7.png" width="444" alt="The driver update wizard." /></div></div><h6>Figure 10.12. The driver update wizard</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Browse to the location of the driver</strong></p><div class="para">
+ A separate driver is provided for each of the various combinations of operating system and architecture. The drivers are arranged hierarchically according to their driver type, the operating system, and the architecture on which they will be installed: <code class="filename"><em class="replaceable"><code>driver_type</code></em>/<em class="replaceable"><code>os</code></em>/<em class="replaceable"><code>arch</code></em>/</code>. For example, the Balloon driver for a Windows 7 operating system with an x86 (32-bit) architecture, resides in the <code class="filename">Balloon/w7/x86</code> directory.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/9-BrowseToDirectory_win7.png" alt="The Browse For Folder window, which pops up after choosing "Browse" to search for driver software on your computer. Select the folder that contains drivers for your hardware from this window." /></div></div><h6>Figure 10.13. The Browse for driver software pop-up window</h6></div><br class="figure-break" /><div class="para">
+ Once you have navigated to the correct location, click <span class="guilabel"><strong>OK</strong></span>.
+ </div></li><li class="step"><p class="title"><strong>Click <span class="guilabel"><strong>Next</strong></span> to continue</strong></p><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/10-w7x86driverchosen_win7.png" width="444" alt="The Update Driver Software wizard, with the specified location to search for driver software selected, with the Browse button on the right, and the Next and Cancel buttons at the bottom right of the window." /></div></div><h6>Figure 10.14. The Update Driver Software wizard</h6></div><br class="figure-break" /><div class="para">
+ The following screen is displayed while the driver installs:
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/DuringInstallation.png" width="444" alt="As the driver software installs, a flashing bar in the Update Driver Software wizard window shows the system is busy." /></div></div><h6>Figure 10.15. The Update Driver Software wizard</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Close the installer</strong></p><div class="para">
+ The following screen is displayed when installation is complete:
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/12-DriverInstalled.png" width="444" alt="After the driver software installs, the Update Driver Software wizard window read "Windows has successfully updated your driver software"." /></div></div><h6>Figure 10.16. The Update Driver Software wizard</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guilabel"><strong>Close</strong></span> to close the installer.
+ </div></li><li class="step"><p class="title"><strong>Reboot</strong></p><div class="para">
+ Reboot the virtual machine to complete the driver installation.
+ </div></li></ol></div></div><div class="section" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk"><div class="titlepage"><div><div><h2 class="title">10.3. Installing drivers during the Windows installation</h2></div></div></div><div class="para">
+ This procedure covers installing the para-virtualized drivers during a Windows installation.
+ </div><div class="para">
+ This method allows a Windows guest virtual machine to use the para-virtualized (<code class="command">virtio</code>) drivers for the default storage device.
+ </div><div class="procedure"><h6>Procedure 10.3. Installing para-virtualized drivers during the Windows installation</h6><ol class="1"><li class="step"><div class="para">
+ Install the virtio-win package:
+ </div><pre class="screen"># yum install virtio-win</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The <span class="package">virtio-win</span> package can be found here in RHN: <a href="https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=602010">https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=602010</a>. It requires access to one of the following channels:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ RHEL Client Supplementary (v. 6)
+ </div></li><li class="listitem"><div class="para">
+ RHEL Server Supplementary (v. 6)
+ </div></li><li class="listitem"><div class="para">
+ RHEL Workstation Supplementary (v. 6)
+ </div></li></ul></div></div></div></li><li class="step"><p class="title"><strong>Creating the guest virtual machine</strong></p><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Create the virtual machine, as normal, without starting the virtual machine. Follow one of the procedures below.
+ </div></div></div><div class="para">
+ Select <span class="emphasis"><em>one</em></span> of the following guest-creation methods, and follow the instructions.
+ </div><ol class="a"><li class="step"><p class="title"><strong>Creating the guest virtual machine with virsh</strong></p><div class="para">
+ This method attaches the para-virtualized driver floppy disk to a Windows guest <span class="emphasis"><em>before</em></span> the installation.
+ </div><div class="para">
+ If the virtual machine is created from an XML definition file with <code class="command">virsh</code>, use the <code class="command">virsh define</code> command not the <code class="command">virsh create</code> command.
+ </div><ol class="i"><li class="step"><div class="para">
+ Create, but do not start, the virtual machine. Refer to the <em class="citetitle">Red Hat Enterprise Linux Virtualization Administration Guide</em> for details on creating virtual machines with the <code class="command">virsh</code> command.
+ </div></li><li class="step"><div class="para">
+ Add the driver disk as a virtualized floppy disk with the <code class="command">virsh</code> command. This example can be copied and used if there are no other virtualized floppy devices attached to the guest virtual machine. Note that <em class="replaceable"><code>vm_name</code></em> should be replaced with the name of the virtual machine.
+ </div><pre class="screen"># virsh attach-disk <em class="replaceable"><code>vm_name</code></em> /usr/share/virtio-win/virtio-win.vfd fda --type floppy</pre><div class="para">
+ You can now continue with <a class="xref" href="#aftercreation">Step 3</a>.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Creating the guest virtual machine with virt-manager and changing the disk type</strong></p><ol class="i"><li class="step"><div class="para">
+ At the final step of the virt-manager guest creation wizard, check the <span class="guilabel"><strong>Customize configuration before install</strong></span> checkbox.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-0-click-configure-before-install.png" alt="Step 5 of 5 of creating a new virtual machine with virt-manager, with a checkbox selected under Storage to customize configuration before install." /></div></div><h6>Figure 10.17. The virt-manager guest creation wizard</h6></div><br class="figure-break" /><div class="para">
+ Click on the <span class="guibutton"><strong>Finish</strong></span> button to continue.
+ </div></li><li class="step"><p class="title"><strong>Open the Add Hardware wizard</strong></p><div class="para">
+ Click the <span class="guilabel"><strong>Add Hardware</strong></span> button in the bottom left of the new panel.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-1-click-add-hardware.png" alt="The Add Hardware button." /></div></div><h6>Figure 10.18. The Add Hardware button</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Select storage device</strong></p><div class="para">
+ <span class="guilabel"><strong>Storage</strong></span> is the default selection in the <span class="guilabel"><strong>Hardware type</strong></span> list.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-2z-select-storage.png" width="444" alt="The Add new virtual hardware wizard with Storage selected in the Hardware type field." /></div></div><h6>Figure 10.19. The Add new virtual hardware wizard</h6></div><br class="figure-break" /><div class="para">
+ Ensure the <span class="guilabel"><strong>Select managed or other existing storage</strong></span> radio button is selected. Click <span class="guibutton"><strong>Browse...</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-2a-select-existing-storage.png" alt="The Add new virtual hardware wizard with Storage selected in the Hardware type field, and the Select managed or other existing storage radio button selected." /></div></div><h6>Figure 10.20. Select managed or existing storage</h6></div><br class="figure-break" /><div class="para">
+ In the new window that opens, click <span class="guilabel"><strong>Browse Local</strong></span>. Navigate to <code class="filename">/usr/share/virtio-win/virtio-win.vfd</code>, and click <span class="guibutton"><strong>Select</strong></span> to confirm.
+ </div><div class="para">
+ Change <span class="guilabel"><strong>Device type</strong></span> to <span class="guilabel"><strong>Floppy disk</strong></span>, and click <span class="guibutton"><strong>Finish</strong></span> to continue.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-select-device-type-floppy.png" alt="The Device type field, set to Floppy Disk." /></div></div><h6>Figure 10.21. Change the Device type</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Confirm settings</strong></p><div class="para">
+ Review the device settings.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-confirm-floppy-settings.png" width="444" alt="The virtual machine hardware information window with the target device (Floppy 1) selected." /></div></div><h6>Figure 10.22. The virtual machine hardware information window</h6></div><br class="figure-break" /><div class="para">
+ You have now created a removable device accessible by your virtual machine.
+ </div></li><li class="step"><p class="title"><strong>Change the hard disk type</strong></p><div class="para">
+ To change the hard disk type from <em class="replaceable"><code>IDE Disk</code></em> to <em class="replaceable"><code>Virtio Disk</code></em>, we must first remove the existing hard disk, Disk 1. Select the disk and click on the <span class="guibutton"><strong>Remove</strong></span> button.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-remove-disk1.png" width="444" alt="The virtual machine hardware information window with virtual disk Disk 1 selected, with the Remove button available at the bottom right corner of the window." /></div></div><h6>Figure 10.23. The virtual machine hardware information window</h6></div><br class="figure-break" /><div class="para">
+ Add a new virtual storage device by clicking <span class="guilabel"><strong>Add Hardware</strong></span>. Then, change the <span class="guilabel"><strong>Device type</strong></span> from <em class="replaceable"><code>IDE disk</code></em> to <em class="replaceable"><code>Virtio Disk</code></em>. Click <span class="guibutton"><strong>Finish</strong></span> to confirm the operation.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-device-type-virtio-finish.png" width="444" alt="The virtual machine hardware information window with the Floppy 1 target device selected, and the Add Hardware on the left bottom corner of the window." /></div></div><h6>Figure 10.24. The virtual machine hardware information window</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Ensure settings are correct</strong></p><div class="para">
+ Review the settings for <em class="replaceable"><code>VirtIO Disk 1</code></em>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-review-virtio-settings.png" width="444" alt="The virtual machine hardware information window with the Overview option selected, showing Basic Details, Hypervisor Details, plus expandable headings Machine Setting and Security, in the right part of the window." /></div></div><h6>Figure 10.25. The virtual machine hardware information window</h6></div><br class="figure-break" /><div class="para">
+ When you are satisfied with the configuration details, click the <span class="guilabel"><strong>Begin Installation</strong></span> button.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-5-begin-installation.png" alt="The Begin Installation button." /></div></div><h6>Figure 10.26. The Begin Installation button</h6></div><br class="figure-break" /><div class="para">
+ You can now continue with <a class="xref" href="#aftercreation">Step 3</a>.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Creating the guest virtual machine with virt-install</strong></p><div class="para">
+ Append the following parameter exactly as listed below to add the driver disk to the installation with the <code class="command">virt-install</code> command:
+ </div><pre class="screen">--disk path=/usr/share/virtio-win/virtio-win.vfd,device=floppy</pre><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ If the device you wish to add is a <code class="literal">disk</code> (that is, not a <code class="literal">floppy</code> or a <code class="literal">cdrom</code>), you will also need to add the <code class="code">bus=virtio</code> option to the end of the <em class="parameter"><code>--disk</code></em> parameter, like so:
+ </div><pre class="screen">--disk path=/usr/share/virtio-win/virtio-win.vfd,device=disk,bus=virtio</pre></div></div><div class="para">
+ According to the version of Windows you are installing, append one of the following options to the <code class="command">virt-install</code> command:
+ </div><pre class="screen">--os-variant winxp</pre><pre class="screen">--os-variant win2k3</pre><pre class="screen">--os-variant win7</pre><div class="para">
+ You can now continue with <a class="xref" href="#aftercreation">Step 3</a>.
+ </div></li></ol></li><li class="step" id="aftercreation"><p class="title"><strong>Additional steps for driver installation</strong></p><div class="para">
+ During the installation, additional steps are required to install drivers, depending on the type of Windows guest.
+ </div><ol class="a"><li class="step" id="step-Virtualization-Installing_the_KVM_Windows_para_virtualized_drivers-Windows_Server_2003"><p class="title"><strong>Windows Server 2003 and Windows XP</strong></p><div class="para">
+ Before the installation blue screen repeatedly press <span class="keycap"><strong>F6</strong></span> for third party drivers.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/XP-driver-capture.png" width="444" alt="The Windows pre-installation blue screen reads Window Setup at the top in plain text, and "Press F6 if you need to install a third party SCSI or RAID driver..." at the bottom." /></div></div><h6>Figure 10.27. The Windows Setup screen</h6></div><br class="figure-break" /><div class="para">
+ Press <span class="keycap"><strong>S</strong></span> to install additional device drivers.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/XP-driver-select2.png" width="444" alt="The next Windows pre-installation blue screen reads Window Setup at the top in plain text and details the option to install an additional device. Options at the bottom of the screen include S to "Specify Additional Device", ENTER to continue, or F3 to exit." /></div></div><h6>Figure 10.28. The Windows Setup screen</h6></div><br class="figure-break" /><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/XP-driver-select-driver.png" width="444" alt="The next Windows blue screen reads Window Setup at the top in plain text and provides options to select the SCSI Adapter to be installed. Options at the bottom of the screen include ENTER to select, or F3 to exit." /></div></div><h6>Figure 10.29. The Windows Setup screen</h6></div><br class="figure-break" /><div class="para">
+ Press <span class="keycap"><strong>Enter</strong></span> to continue the installation.
+ </div></li><li class="step" id="step-Virtualization-Installing_the_KVM_Windows_para_virtualized_drivers-Windows_Server_2008"><p class="title"><strong>Windows Server 2008</strong></p><div class="para">
+ Follow the same procedure for Windows Server 2003, but when the installer prompts you for the driver, click on <span class="guilabel"><strong>Load Driver</strong></span>, point the installer to <code class="systemitem">Drive A:</code> and pick the driver that suits your guest operating system and architecture.
+ </div></li></ol></li></ol></div></div><div class="section" id="idm115640352"><div class="titlepage"><div><div><h2 class="title" id="idm115640352">10.4. Using the para-virtualized drivers with Red Hat Enterprise Linux 3.9 guests</h2></div></div></div><div class="para">
+ Para-virtualized drivers for Red Hat Enterprise Linux 3.9 consist of five kernel modules: <code class="command">virtio</code>, <code class="command">virtio_blk</code>, <code class="command">virtio_net</code>, <code class="command">virtio_pci</code> and <code class="command">virtio_ring</code>. All five modules must be loaded to use both the para-virtualized block and network devices drivers.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ For Red Hat Enterprise Linux 3.9 guests, the <span class="package">kmod-virtio</span> package is a requirement for the <code class="command">virtio</code> module.
+ </div></div></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ To use the network device driver only, load the <code class="command">virtio</code>, <code class="command">virtio_net</code> and <code class="command">virtio_pci</code> modules. To use the block device driver only, load the <code class="command">virtio</code>, <code class="command">virtio_ring</code>, <code class="command">virtio_blk</code> and <code class="command">virtio_pci</code> modules.
+ </div></div></div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The <span class="package">virtio</span> package modifies the initrd RAM disk file in the <code class="filename">/boot</code> directory. The original initrd file is saved to <code class="filename">/boot/initrd-<em class="replaceable"><code>kernel-version</code></em>.img.virtio.orig</code>. The original initrd file is replaced with a new initrd RAM disk containing the <code class="command">virtio</code> driver modules. The initrd RAM disk is modified to allow the virtual machine to boot from a storage device using the para-virtualized drivers. To use a different initrd file, you must ensure that drivers are loaded with the <code class="filename">sysinit</code> script (<a class="xref" href="#proc1">Loading the para-virtualized drivers with the sysinit script</a>) or when creating new initrd RAM disk (<a class="xref" href="#proc2">Adding the para-virtualized drivers to the initrd RAM disk</a>).
+ </div></div></div><div class="formalpara" id="proc1"><h5 class="formalpara">Loading the para-virtualized drivers with the sysinit script</h5>
+ This procedure covers loading the para-virtualized driver modules during the boot sequence on a Red Hat Enterprise Linux 3.9 or newer guest with the <code class="filename">sysinit</code> script. Note that the guest virtual machine cannot use the para-virtualized drivers for the default boot disk if the modules are loaded with the <code class="filename">sysinit</code> script.
+ </div><div class="para">
+ The drivers must be loaded in the following order:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <code class="command">virtio</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">virtio_ring</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">virtio_pci</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">virtio_blk</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">virtio_net</code>
+ </div></li></ol></div><div class="para">
+ <code class="command">virtio_net</code> and <code class="command">virtio_blk</code> are the only drivers whose order can be changed. If other drivers are loaded in a different order, they will not work.
+ </div><div class="para">
+ Next, configure the modules. Locate the following section of the <code class="filename">/etc/rc.d/rc.sysinit</code> file.
+ </div><pre class="screen">if [ -f /etc/rc.modules ]; then
+ /etc/rc.modules
+fi</pre><div class="para">
+ Append the following lines after that section:
+ </div><pre class="screen">if [ -f /etc/rc.modules ]; then
+ /etc/rc.modules
+fi
+
+modprobe virtio
+modprobe virtio_ring # Comment this out if you do not need block driver
+modprobe virtio_blk # Comment this out if you do not need block driver
+modprobe virtio_net # Comment this out if you do not need net driver
+modprobe virtio_pci</pre><div class="para">
+ Reboot the guest virtual machine to load the kernel modules.
+ </div><div class="formalpara" id="proc2"><h5 class="formalpara">Adding the para-virtualized drivers to the initrd RAM disk</h5>
+ This procedure covers loading the para-virtualized driver modules with the kernel on a Red Hat Enterprise Linux 3.9 or newer guest by including the modules in the initrd RAM disk. The mkinitrd tool configures the initrd RAM disk to load the modules. Specify the additional modules with the <em class="parameter"><code>--with</code></em> parameter for the <code class="command">mkinitrd</code> command. Append following set of parameters, in the exact order, when using the <code class="command">mkinitrd</code> command to create a custom initrd RAM disk:
+ </div><pre class="screen">--with virtio --with virtio_ring --with virtio_blk --with virtio_net --with virtio_pci</pre><div class="formalpara"><h5 class="formalpara" id="idm79521568">AMD64 and Intel 64 issues</h5>
+ Use the <code class="filename">x86_64</code> version of the <span class="package">virtio</span> package for AMD64 systems.
+ </div><div class="para">
+ Use the <code class="filename">ia32e</code> version of the <span class="package">virtio</span> package for Intel 64 systems. Using the <code class="filename">x86_64</code> version of the <span class="package">virtio</span> may cause a '<code class="computeroutput">Unresolved symbol</code>' error during the boot sequence on Intel 64 systems.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm101747920">Network performance issues</h5>
+ If you experience low performance with the para-virtualized network drivers, verify the setting for the GSO and TSO features on the host system. The para-virtualized network drivers require that the GSO and TSO options are disabled for optimal performance.
+ </div><div class="para">
+ Verify the status of the GSO and TSO settings, use the command on the host (replacing <em class="replaceable"><code>interface</code></em> with the network interface used by the guest):
+ </div><pre class="screen"># ethtool -k <em class="replaceable"><code>interface</code></em></pre><div class="para">
+ Disable the GSO and TSO options with the following commands on the host:
+ </div><pre class="screen"># ethtool -K <em class="replaceable"><code>interface</code></em> gso off
+# ethtool -K <em class="replaceable"><code>interface</code></em> tso off</pre><div class="formalpara"><h5 class="formalpara" id="idm98005968">Para-virtualized driver swap partition issue</h5>
+ After activating the para-virtualized block device driver the swap partition may not be available. This issue is may be caused by a change in disk device name. To fix this issue, open the <code class="filename">/etc/fstab</code> file and locate the lines containing swap partitions, for example:
+ </div><pre class="screen">/dev/hda3 swap swap defaults 0 0</pre><div class="para">
+ The para-virtualized drivers use the <code class="command">/dev/vd*</code> naming convention, not the <code class="command">/dev/hd*</code> naming convention. To resolve this issue modify the incorrect swap entries in the <code class="filename">/etc/fstab</code> file to use the <code class="command">/dev/vd*</code> convention, for the example above:
+ </div><pre class="screen">/dev/vda3 swap swap defaults 0 0</pre><div class="para">
+ Save the changes and reboot the guest virtual machine. The virtual machine should now have swap partitions.
+ </div></div><div class="section" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices"><div class="titlepage"><div><div><h2 class="title">10.5. Using KVM para-virtualized drivers for existing devices</h2></div></div></div><div class="para">
+ You can modify an existing hard disk device attached to the guest to use the <code class="command">virtio</code> driver instead of the virtualized IDE driver. The example shown in this section edits libvirt configuration files. Note that the guest virtual machine does not need to be shut down to perform these steps, however the change will not be applied until the guest is completely shut down and rebooted.
+ </div><div class="procedure"><h6>Procedure 10.4. Using KVM para-virtualized drivers for existing devices</h6><ol class="1"><li class="step"><div class="para">
+ Ensure that you have installed the appropriate driver (<code class="classname">viostor</code>), as described in <a class="xref" href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers">Section 10.1, “Installing the KVM Windows para-virtualized drivers”</a>, before continuing with this procedure.
+ </div></li><li class="step"><div class="para">
+ Run the <code class="command">virsh edit <guestname></code> command as root to edit the XML configuration file for your device. For example, <code class="command">virsh edit guest1</code>. The configuration files are located in <code class="filename">/etc/libvirt/qemu</code>.
+ </div></li><li class="step"><div class="para">
+ Below is a file-based block device using the virtualized IDE driver. This is a typical entry for a virtual machine 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 class="step"><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>. Note that if the disk was previously IDE it will have a target similar to hda, hdb, or hdc and so on. When changing to <span class="bold bold"><strong>bus=virtio</strong></span> the target needs to be changed to vda, vdb, or vdc accordingly.
+ </div><pre class="screen"><disk type='file' device='disk'>
+ <source file='/var/lib/libvirt/images/disk1.img'/>
+ <target <span class="bold bold"><strong>dev='vda'</strong></span> <span class="bold bold"><strong>bus='virtio'/></strong></span>
+</disk></pre></li><li class="step"><div class="para">
+ Remove the <span class="bold bold"><strong>address</strong></span> tag inside the <span class="bold bold"><strong>disk</strong></span> tags. This must be done for this procedure to work. Libvirt will regenerate the <span class="bold bold"><strong>address</strong></span> tag appropriately the next time the virtual machine is started.
+ </div></li></ol></div><div class="para">
+ 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.
+ </div><div class="para">
+ Refer to the libvirt website for more details on using Virtio: <a href="http://www.linux-kvm.org/page/Virtio">http://www.linux-kvm.org/page/Virtio</a>
+ </div></div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices"><div class="titlepage"><div><div><h2 class="title">10.6. Using KVM para-virtualized drivers for new devices</h2></div></div></div><div class="para">
+ 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"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><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><div class="procedure"><h6>Procedure 10.5. Starting the new device wizard</h6><ol class="1"><li class="step"><div class="para">
+ Open the guest virtual machine by double clicking on the name of the guest in <code class="command">virt-manager</code>.
+ </div></li><li class="step"><div class="para">
+ Open the <span class="guilabel"><strong>Show virtual hardware details</strong></span> tab by clicking the <span class="guibutton"><strong>lightbulb</strong></span> button.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/vm_info_button_new.png" alt="The Show virtual hardware details tab" /></div></div><h6>Figure 10.30. The Show virtual hardware details tab</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ In the <span class="guilabel"><strong>Show virtual hardware details</strong></span> tab, click on the <span class="guilabel"><strong>Add Hardware</strong></span> button.
+ </div></li><li class="step"><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. The storage and network device wizards are covered in procedures <a class="xref" href="#procstore">Procedure 10.6, “Adding a storage device using the para-virtualized storage driver”</a> and <a class="xref" href="#procnet">Procedure 10.7, “Adding a network device using the para-virtualized network driver”</a>.
+ </div></li></ol></div><div class="procedure" id="procstore"><h6>Procedure 10.6. Adding a storage device using the para-virtualized storage driver</h6><ol class="1"><li class="step"><div class="para">
+ Open the guest virtual machine by double clicking on the name of the guest in <code class="command">virt-manager</code>.
+ </div></li><li class="step"><div class="para">
+ Open the <span class="guilabel"><strong>Show virtual hardware details</strong></span> tab by clicking the <span class="guibutton"><strong>lightbulb</strong></span> button.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/vm_info_button_new.png" alt="The Show virtual hardware details tab" /></div></div><h6>Figure 10.31. The Show virtual hardware details tab</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ In the <span class="guilabel"><strong>Show virtual hardware details</strong></span> tab, click on the <span class="guilabel"><strong>Add Hardware</strong></span> button.
+ </div></li><li class="step"><p class="title"><strong>Select hardware type</strong></p><div class="para">
+ Select <span class="guilabel"><strong>Network</strong></span> as the <span class="guilabel"><strong>Hardware type</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Network_hardware.png" width="444" alt="The Add new virtual hardware wizard with Storage selected as the hardware type." /></div></div><h6>Figure 10.32. The Add new virtual hardware wizard</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Select the network device and driver</strong></p><div class="para">
+ Create a new disk image or select a storage pool volume.
+ </div><div class="para">
+ Set the <span class="guilabel"><strong>Device type</strong></span> to <span class="guilabel"><strong>Virtio Disk</strong></span> to use the para-virtualized drivers. Choose the desired <span class="guilabel"><strong>Host device</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Network_hardware_virtio.png" width="444" alt="The Add new virtual hardware wizard Storage window, with "Select managed or other existing storage" selected and specified in the field below." /></div></div><h6>Figure 10.33. The Add new virtual hardware wizard</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guilabel"><strong>Finish</strong></span> to complete the procedure.
+ </div></li></ol></div><div class="procedure" id="procnet"><h6>Procedure 10.7. Adding a network device using the para-virtualized network driver</h6><ol class="1"><li class="step"><p class="title"><strong>Select hardware type</strong></p><div class="para">
+ Select <span class="guilabel"><strong>Network</strong></span> as the <span class="guilabel"><strong>Hardware type</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/virtio-network-step1.png" alt="The Add new virtual hardware wizard with Network selected as the hardware type." /></div></div><h6>Figure 10.34. The Add new virtual hardware wizard</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guilabel"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Select the network device and driver</strong></p><div class="para">
+ Select the network device from the <span class="guilabel"><strong>Host device</strong></span> list.
+ </div><div class="para">
+ Create a custom MAC address or use the one provided.
+ </div><div class="para">
+ Set the <span class="guilabel"><strong>Device model</strong></span> to <span class="guilabel"><strong>virtio</strong></span> to use the para-virtualized drivers.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/virtio-network-step2.png" alt="The Add new virtual hardware wizard Network setup, with options for selecting the network device and driver." /></div></div><h6>Figure 10.35. The Add new virtual hardware wizard</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guilabel"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Finish the procedure</strong></p><div class="para">
+ Confirm the details for the new device are correct.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/virtio-network-finish3.png" alt="The Add new virtual hardware wizard showing the details of the newly created network, and the Finish button at the bottom right corner of the window." /></div></div><h6>Figure 10.36. The Add new virtual hardware wizard</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guilabel"><strong>Finish</strong></span> to complete the procedure.
+ </div></li></ol></div><div class="para">
+ Once all new devices are added, reboot the virtual machine. Windows virtual machines may not recognize the devices until the guest is rebooted.
+ </div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 11. Network configuration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_address_translation_NAT_with_libvirt">11.1. Network Address Translation (NAT) with libvirt</a></span></dt><dt><span class="section"><a href="#idm100800224">11.2. Disabling vhost-net</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt">11.3. Bridged networking with libvirt</a></span></dt></dl></div><div class="para">
+ This chapter provides an introduction to the common networking configurations used by libvirt based guest virtual machines. For additional information, consult the libvirt network architecture documentation: <a href="http://libvirt.org/intro.html">http://libvirt.org/intro.html</a>.
+ </div><div class="para">
+ Fedora supports the following networking setups for virtualization:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ virtual networks using Network Address Translation (<em class="firstterm">NAT</em>)
+ </div></li><li class="listitem"><div class="para">
+ directly allocated physical devices using PCI device assignment
+ </div></li><li class="listitem"><div class="para">
+ directly allocated virtual functions using PCIe SR-IOV
+ </div></li><li class="listitem"><div class="para">
+ bridged networks
+ </div></li></ul></div><div class="para">
+ You must enable NAT, network bridging or directly assign a PCI device to allow external hosts access to network services on guest virtual machines.
+ </div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_address_translation_NAT_with_libvirt"><div class="titlepage"><div><div><h2 class="title">11.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 known as virtual networks).
+ </div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_address_translation_NAT_with_libvirt-Host_configuration"><h5 class="formalpara">Host configuration</h5>
+ Every standard <code class="systemitem">libvirt</code> installation provides NAT-based connectivity to virtual machines as the 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. The new device uses NAT and IP forwarding to connect to the physical network. 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 guest virtual machines 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" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_address_translation_NAT_with_libvirt-Guest_configuration"><h5 class="formalpara">Guest virtual machine configuration</h5>
+ Once the host configuration is complete, a guest virtual machine can be connected to the virtual network based on its name. To connect a guest to the 'default' virtual network, the following could be used in the XML configuration file (such as <code class="filename">/etc/libvirtd/qemu/myguest.xml</code>) for the guest:
+ </div><pre class="screen"><interface type='network'>
+ <source network='default'/>
+</interface></pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Defining a MAC address is optional. If you do not define one, a MAC address is automatically generated and used as the MAC address of the bridge device used by the network. Manually setting the MAC address may be useful to maintain consistency or easy reference throughout your environment, or to avoid the very small chance of a conflict.
+ </div><pre class="screen"><interface type='network'>
+ <source network='default'/>
+ <mac address='00:16:3e:1a:b3:4a'/>
+</interface></pre></div></div></div><div class="section" id="idm100800224"><div class="titlepage"><div><div><h2 class="title" id="idm100800224">11.2. Disabling vhost-net</h2></div></div></div><div class="para">
+ The <code class="command">vhost-net</code> module is a kernel-level backend for virtio networking that reduces virtualization overhead by moving virtio packet processing tasks out of user space (the qemu process) and into the kernel (the <code class="systemitem">vhost-net</code> driver). vhost-net is only available for virtio network interfaces. If the vhost-net kernel module is loaded, it is enabled by default for all virtio interfaces, but can be disabled in the interface configuration in the case that a particular workload experiences a degradation in performance when vhost-net is in use.
+ </div><div class="para">
+ Specifically, when UDP traffic is sent from a host machine to a guest virtual machine on that host, performance degradation can occur if the guest virtual machine processes incoming data at a rate slower than the host machine sends it. In this situation, enabling <code class="command">vhost-net</code> causes the UDP socket's receive buffer to overflow more quickly, which results in greater packet loss. It is therefore better to disable <code class="command">vhost-net</code> in this situation to slow the traffic, and improve overall performance.
+ </div><div class="para">
+ To disable <code class="command">vhost-net</code>, edit the <code class="code"><interface></code> sub-element in the guest virtual machine's XML configuration file and define the network as follows:
+ </div><pre class="screen"><interface type="network">
+ ...
+ <model type="virtio"/>
+ <driver name="qemu"/>
+ ...
+</interface></pre><div class="para">
+ Setting the driver name to <code class="literal">qemu</code> forces packet processing into qemu user space, effectively disabling vhost-net for that interface.
+ </div></div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt"><div class="titlepage"><div><div><h2 class="title">11.3. Bridged networking with libvirt</h2></div></div></div><div class="para">
+ Bridged networking (also known as physical device sharing) is used to dedicate 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="para">
+ To create a bridge (<code class="literal">br0</code>) based on the <code class="literal">eth0</code> interface, execute the following command on the host:
+ </div><pre class="screen"># virsh iface-bridge eth0 br0</pre><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ NetworkManager does not support bridging. NetworkManager must be disabled to use networking with the network scripts (located in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory).
+ </div><pre class="screen"># chkconfig NetworkManager off
+# chkconfig network on
+# service NetworkManager stop
+# service network start</pre><div class="para">
+ If you do not want to disable <span class="application"><strong>NetworkManager</strong></span> entirely, add "<em class="parameter"><code>NM_CONTROLLED=no</code></em>" to the <code class="filename">ifcfg-*</code> network script being used for the bridge.
+ </div></div></div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 12. PCI device configuration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-AI_device_to_a_host">12.1. Assigning a PCI device with virsh</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host">12.2. Assigning a PCI device with virt-manager</a></span></dt><dt><span class="section"><a href="#idm103587632">12.3. PCI device assignment with virt-install</a></span></dt><dt><span class="section"><a href="#idm114484096">12.4. Detaching an assigned PCI device</a></span></dt></dl></div><div class="para">
+ Red Hat Enterprise Linux 6 exposes three classes of device to its virtual machines:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="firstterm">Emulated devices</em> are purely virtual devices that mimic real hardware, allowing unmodified guest operating systems to work with them using their standard in-box drivers.
+ </div></li><li class="listitem"><div class="para">
+ <em class="firstterm">Virtio devices</em> are purely virtual devices designed to work optimally in a virtual machine. Virtio devices are similar to emulated devices, however, non-Linux virtual machines do not include the drivers they require by default. Virtualization management software like the Virtual Machine Manager (<span class="application"><strong>virt-manager</strong></span>) and the Red Hat Enterprise Virtualization Hypervisor install these drivers automatically for supported non-Linux guest operating systems.
+ </div></li><li class="listitem"><div class="para">
+ <em class="firstterm">Assigned devices</em> are physical devices that are exposed to the virtual machine. This method is also known as 'passthrough'. Device assignment allows virtual machines exclusive access to PCI devices for a range of tasks, and allows PCI devices to appear and behave as if they were physically attached to the guest operating system.
+ </div><div class="para">
+ Device assignment is supported on PCI Express devices, except graphics cards. Parallel PCI devices may be supported as assigned devices, but they have severe limitations due to security and system configuration conflicts.
+ </div></li></ul></div><div class="para">
+ Red Hat Enterprise Linux 6 supports 32 PCI device slots per virtual machine, and 8 PCI functions per device slot. This gives a theoretical maximum of 256 configurable PCI functions per guest.
+ </div><div class="para">
+ However, this theoretical maximum is subject to the following limitations:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Each virtual machine supports a maximum of 8 assigned device functions.
+ </div></li><li class="listitem"><div class="para">
+ 4 PCI device slots are configured with emulated devices by default. However, users can explicitly remove 2 of the emulated devices that are configured by default (the video adapter device in slot 2, and the memory balloon driver device in slot 3). This gives users a supported functional maximum of 30 PCI device slots per virtual machine.
+ </div></li></ul></div><div class="para">
+ Red Hat Enterprise Linux 6.0 and newer supports hot plugging assigned PCI devices into virtual machines. However, PCI device hot plugging operates at the slot level and therefore does not support multi-function PCI devices. Multi-function PCI devices are recommended for static device configuration only.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Red Hat Enterprise Linux 6.0 limited guest operating system driver access to a device's standard and extended configuration space. Limitations that were present in Red Hat Enterprise Linux 6.0 are significantly reduced in Red Hat Enterprise Linux 6.1, and enable a much larger set of PCI Express devices to be successfully assigned to KVM guests.
+ </div></div></div><div class="para">
+ Secure device assignment also requires interrupt remapping support. If a platform does not support interrupt remapping, device assignment will fail. To use device assignment without interrupt remapping support in a development environment, set the <em class="parameter"><code>allow_unsafe_assigned_interrupts</code></em> KVM module parameter to <code class="literal">1</code>.
+ </div><div class="para">
+ PCI device assignment is only available on hardware platforms supporting either Intel VT-d or AMD IOMMU. These Intel VT-d or AMD IOMMU specifications must be enabled in BIOS for PCI device assignment to function.
+ </div><div class="procedure" id="intel-prep"><h6>Procedure 12.1. Preparing an Intel system for PCI device assignment</h6><ol class="1"><li class="step"><p class="title"><strong>Enable the Intel VT-d specifications</strong></p><div class="para">
+ The Intel VT-d specifications provide hardware support for directly assigning a physical device to a virtual machine. These specifications are required to use PCI device assignment with Red Hat Enterprise Linux.
+ </div><div class="para">
+ The Intel VT-d specifications must be enabled in the BIOS. Some system manufacturers disable these specifications by default. The terms used to refer to these specifications can differ between manufacturers; consult your system manufacturer's documentation for the appropriate terms.
+ </div></li><li class="step"><p class="title"><strong>Activate Intel VT-d in the kernel</strong></p><div class="para">
+ Activate Intel VT-d in the kernel by adding the <em class="parameter"><code>intel_iommu=on</code></em> parameter to the kernel line in the <code class="filename">/boot/grub/grub.conf</code> file.
+ </div><div class="para">
+ The example below is a modified <code class="filename">grub.conf</code> file with Intel VT-d activated.
+ </div><pre class="screen">default=0
+timeout=5
+splashimage=(hd0,0)/grub/splash.xpm.gz
+hiddenmenu
+title Red Hat Enterprise Linux Server (2.6.32-330.x86_645)
+ root (hd0,0)
+ kernel /vmlinuz-2.6.32-330.x86_64 ro root=/dev/VolGroup00/LogVol00 rhgb quiet <span class="bold bold"><strong>intel_iommu=on</strong></span>
+ initrd /initrd-2.6.32-330.x86_64.img</pre></li><li class="step"><p class="title"><strong>Ready to use</strong></p><div class="para">
+ Reboot the system to enable the changes. Your system is now capable of PCI device assignment.
+ </div></li></ol></div><div class="procedure" id="amd-prep"><h6>Procedure 12.2. Preparing an AMD system for PCI device assignment</h6><ol class="1"><li class="step"><p class="title"><strong>Enable the AMD IOMMU specifications</strong></p><div class="para">
+ The AMD IOMMU specifications are required to use PCI device assignment in Red Hat Enterprise Linux. These specifications must be enabled in the BIOS. Some system manufacturers disable these specifications by default.
+ </div></li><li class="step"><p class="title"><strong>Enable IOMMU kernel support</strong></p><div class="para">
+ Append <em class="parameter"><code>amd_iommu=on</code></em> to the kernel command line in <code class="filename">/boot/grub/grub.conf</code> so that AMD IOMMU specifications are enabled at boot.
+ </div></li></ol></div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-AI_device_to_a_host"><div class="titlepage"><div><div><h2 class="title">12.1. Assigning a PCI device with virsh</h2></div></div></div><div class="para">
+ These steps cover assigning a PCI device to a virtual machine on a KVM hypervisor.
+ </div><div class="para">
+ This example uses a PCIe network controller with the PCI identifier code, <code class="computeroutput">pci_0000_01_00_0</code>, and a fully virtualized guest machine named <em class="replaceable"><code>guest1-F19</code></em>.
+ </div><div class="procedure"><h6>Procedure 12.3. Assigning a PCI device to a guest virtual machine with virsh</h6><ol class="1"><li class="step"><p class="title"><strong>Identify the device</strong></p><div class="para">
+ First, identify the PCI device designated for device assignment to the virtual machine. Use the <code class="command">lspci</code> command to list the available PCI devices. You can refine the output of <code class="command">lspci</code> with <code class="command">grep</code>.
+ </div><div class="para">
+ This example uses the Ethernet controller highlighted in the following output:
+ </div><pre class="screen"># lspci | grep Ethernet
+<span class="bold bold"><strong>00:19.0 Ethernet controller: Intel Corporation 82567LM-2 Gigabit Network Connection</strong></span>
+01:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
+01:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)</pre><div class="para">
+ This Ethernet controller is shown with the short identifier <code class="literal">00:19.0</code>. We need to find out the full identifier used by <code class="command">virsh</code> in order to assign this PCI device to a virtual machine.
+ </div><div class="para">
+ To do so, combine the <code class="command">virsh nodedev-list</code> command with the <code class="command">grep</code> command to list all devices of a particular type (<code class="literal">pci</code>) that are attached to the host machine. Then look at the output for the string that maps to the short identifier of the device you wish to use.
+ </div><div class="para">
+ This example highlights the string that maps to the Ethernet controller with the short identifier <code class="literal">00:19.0</code>. Note that the <code class="literal">:</code> and <code class="literal">.</code> characters are replaced with underscores in the full identifier.
+ </div><pre class="screen"># virsh nodedev-list --cap pci
+pci_0000_00_00_0
+pci_0000_00_01_0
+pci_0000_00_03_0
+pci_0000_00_07_0
+pci_0000_00_10_0
+pci_0000_00_10_1
+pci_0000_00_14_0
+pci_0000_00_14_1
+pci_0000_00_14_2
+pci_0000_00_14_3
+pci_0000_<span class="bold bold"><strong>00_19_0</strong></span>
+pci_0000_00_1a_0
+pci_0000_00_1a_1
+pci_0000_00_1a_2
+pci_0000_00_1a_7
+pci_0000_00_1b_0
+pci_0000_00_1c_0
+pci_0000_00_1c_1
+pci_0000_00_1c_4
+pci_0000_00_1d_0
+pci_0000_00_1d_1
+pci_0000_00_1d_2
+pci_0000_00_1d_7
+pci_0000_00_1e_0
+pci_0000_00_1f_0
+pci_0000_00_1f_2
+pci_0000_00_1f_3
+pci_0000_01_00_0
+pci_0000_01_00_1
+pci_0000_02_00_0
+pci_0000_02_00_1
+pci_0000_06_00_0
+pci_0000_07_02_0
+pci_0000_07_03_0</pre><div class="para">
+ Record the PCI device number that maps to the device you want to use; this is required in other steps.
+ </div></li><li class="step"><p class="title"><strong>Review device information</strong></p><div class="para">
+ Information on the domain, bus, and function are available from output of the <code class="command">virsh nodedev-dumpxml</code> command:
+ </div><pre class="screen">virsh nodedev-dumpxml pci_0000_00_19_0
+<device>
+ <name>pci_0000_00_19_0</name>
+ <parent>computer</parent>
+ <driver>
+ <name>e1000e</name>
+ </driver>
+ <capability type='pci'>
+ <domain>0</domain>
+ <bus>0</bus>
+ <slot>25</slot>
+ <function>0</function>
+ <product id='0x1502'>82579LM Gigabit Network Connection</product>
+ <vendor id='0x8086'>Intel Corporation</vendor>
+ <capability type='virt_functions'>
+ </capability>
+ </capability>
+</device></pre></li><li class="step"><p class="title"><strong>Determine required configuration details</strong></p><div class="para">
+ Refer to the output from the <code class="command">virsh nodedev-dumpxml pci_0000_00_19_0</code> command for the values required for the configuration file.
+ </div><div class="para">
+ Optionally, convert slot and function values to hexadecimal values (from decimal) to get the PCI bus addresses. Append "0x" to the beginning of the output to tell the computer that the value is a hexadecimal number.
+ </div><div class="para">
+ The example device has the following values: bus = 0, slot = 25 and function = 0. The decimal configuration uses those three values:
+ </div><pre class="screen">bus='0'
+slot='25'
+function='0'</pre><div class="para">
+ If you want to convert to hexadecimal values, you can use the <code class="command">printf</code> utility to convert from decimal values, as shown in the following example:
+ </div><pre class="screen">$ printf %x 0
+0
+$ printf %x 25
+19
+$ printf %x 0
+0</pre><div class="para">
+ The example device would use the following hexadecimal values in the configuration file:
+ </div><pre class="screen">bus='0x0'
+slot='0x19'
+function='0x0'</pre></li><li class="step"><p class="title"><strong>Add configuration details</strong></p><div class="para">
+ Run <code class="command">virsh edit</code>, specifying the virtual machine name, and add a device entry in the <code class="computeroutput"><source></code> section to assign the PCI device to the guest virtual machine.
+ </div><pre class="screen"># virsh edit <em class="replaceable"><code>guest1-F19</code></em>
+<hostdev mode='subsystem' type='pci' managed='yes'>
+ <source>
+ <address domain='0x0' bus='0x0' slot='0x19' function='0x0'/>
+ </source>
+</hostdev></pre><div class="para">
+ Alternately, run <code class="command">virsh attach-device</code>, specifying the virtual machine name and the guest's XML file:
+ </div><pre class="screen">virsh attach-device <em class="replaceable"><code>guest1-F19</code></em> <code class="filename">file.xml</code></pre></li><li class="step"><p class="title"><strong>Allow device management</strong></p><div class="para">
+ Set an SELinux boolean to allow the management of the PCI device from the virtual machine:
+ </div><pre class="screen"># setsebool -P virt_use_sysfs 1</pre></li><li class="step"><p class="title"><strong>Start the virtual machine</strong></p><pre class="screen"># virsh start <em class="replaceable"><code>guest1-F19</code></em></pre></li></ol></div><div class="para">
+ The PCI device should now be successfully assigned to the virtual machine, and accessible to the guest operating system.
+ </div></div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host"><div class="titlepage"><div><div><h2 class="title">12.2. Assigning a PCI device with virt-manager</h2></div></div></div><div class="para">
+ PCI devices can be added to guest virtual machines using the graphical <code class="command">virt-manager</code> tool. The following procedure adds a Gigabit Ethernet controller to a guest virtual machine.
+ </div><div class="procedure"><h6>Procedure 12.4. Assigning a PCI device to a guest virtual machine using virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Open the hardware settings</strong></p><div class="para">
+ Open the guest virtual machine and click the <span class="guibutton"><strong>Add Hardware</strong></span> button to add a new device to the virtual machine.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_hardware.png" width="444" alt="The virtual machine hardware window with the Information button selected on the top taskbar and Overview selected on the left menu pane." /></div></div><h6>Figure 12.1. The virtual machine hardware information window</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Select a PCI device</strong></p><div class="para">
+ Select <span class="application"><strong>PCI Host Device</strong></span> from the <span class="guilabel"><strong>Hardware</strong></span> list on the left.
+ </div><div class="para">
+ Select an unused PCI device. Note that selecting PCI devices presently in use on the host causes errors. In this example, a spare 82576 network device is used. Click <span class="guilabel"><strong>Finish</strong></span> to complete setup.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/3_PCI_Device.png" width="444" alt="The Add new virtual hardware wizard with PCI Host Device selected on the left menu pane, showing a list of host devices for selection in the right menu pane." /></div></div><h6>Figure 12.2. The Add new virtual hardware wizard</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Add the new device</strong></p><div class="para">
+ The setup is complete and the guest virtual machine now has direct access to the PCI device.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/pci_host_device.png" width="444" alt="The virtual machine hardware window with the Information button selected on the top taskbar and Overview selected on the left menu pane, displaying the newly added PCI Device in the list of virtual machine devices in the left menu pane." /></div></div><h6>Figure 12.3. The virtual machine hardware information window</h6></div><br class="figure-break" /></li></ol></div></div><div class="section" id="idm103587632"><div class="titlepage"><div><div><h2 class="title" id="idm103587632">12.3. PCI device assignment with virt-install</h2></div></div></div><div class="para">
+ To use <span class="application"><strong>virt-install</strong></span> to assign a PCI device, use the <em class="parameter"><code>--host-device</code></em> parameter.
+ </div><div class="procedure"><h6>Procedure 12.5. Assigning a PCI device to a virtual machine with virt-install</h6><ol class="1"><li class="step"><p class="title"><strong>Identify the device</strong></p><div class="para">
+ Identify the PCI device designated for device assignment to the guest virtual machine.
+ </div><pre class="screen"># lspci | grep Ethernet
+00:19.0 Ethernet controller: Intel Corporation 82567LM-2 Gigabit Network Connection
+01:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
+01:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)</pre><div class="para">
+ The <code class="command">virsh nodedev-list</code> command lists all devices attached to the system, and identifies each PCI device with a string. To limit output to only PCI devices, run the following command:
+ </div><pre class="screen"># virsh nodedev-list --cap pci
+pci_0000_00_00_0
+pci_0000_00_01_0
+pci_0000_00_03_0
+pci_0000_00_07_0
+pci_0000_00_10_0
+pci_0000_00_10_1
+pci_0000_00_14_0
+pci_0000_00_14_1
+pci_0000_00_14_2
+pci_0000_00_14_3
+pci_0000_00_19_0
+pci_0000_00_1a_0
+pci_0000_00_1a_1
+pci_0000_00_1a_2
+pci_0000_00_1a_7
+pci_0000_00_1b_0
+pci_0000_00_1c_0
+pci_0000_00_1c_1
+pci_0000_00_1c_4
+pci_0000_00_1d_0
+pci_0000_00_1d_1
+pci_0000_00_1d_2
+pci_0000_00_1d_7
+pci_0000_00_1e_0
+pci_0000_00_1f_0
+pci_0000_00_1f_2
+pci_0000_00_1f_3
+pci_0000_01_00_0
+pci_0000_01_00_1
+pci_0000_02_00_0
+pci_0000_02_00_1
+pci_0000_06_00_0
+pci_0000_07_02_0
+pci_0000_07_03_0</pre><div class="para">
+ Record the PCI device number; the number is needed in other steps.
+ </div><div class="para">
+ Information on the domain, bus and function are available from output of the <code class="command">virsh nodedev-dumpxml</code> command:
+ </div><pre class="screen"># virsh nodedev-dumpxml pci_0000_01_00_0
+<device>
+ <name>pci_0000_01_00_0</name>
+ <parent>pci_0000_00_01_0</parent>
+ <driver>
+ <name>igb</name>
+ </driver>
+ <capability type='pci'>
+ <domain>0</domain>
+ <bus>1</bus>
+ <slot>0</slot>
+ <function>0</function>
+ <product id='0x10c9'>82576 Gigabit Network Connection</product>
+ <vendor id='0x8086'>Intel Corporation</vendor>
+ <capability type='virt_functions'>
+ </capability>
+ </capability>
+</device></pre></li><li class="step"><p class="title"><strong>Add the device</strong></p><div class="para">
+ Use the PCI identifier output from the <code class="command">virsh nodedev</code> command as the value for the <em class="parameter"><code>--host-device</code></em> parameter.
+ </div><pre class="screen">virt-install \
+--name=guest1-F19 \
+--disk path=/var/lib/libvirt/images/guest1-F19.img,size=8 \
+--nonsparse --graphics spice \
+--vcpus=2 --ram=2048 \
+--location=http://example1.com/installation_tree/f19-Server-x86_64/os \
+--nonetworks \
+--os-type=linux \
+--os-variant=fedora
+--host-device=<span class="emphasis"><em>pci_0000_01_00_0</em></span></pre></li><li class="step"><p class="title"><strong>Complete the installation</strong></p><div class="para">
+ Complete the guest installation. The PCI device should be attached to the guest.
+ </div></li></ol></div></div><div class="section" id="idm114484096"><div class="titlepage"><div><div><h2 class="title" id="idm114484096">12.4. Detaching an assigned PCI device</h2></div></div></div><div class="para">
+ When a host PCI device has been assigned to a guest machine, the host can no longer use the device. Read this section to learn how to detach the device from the guest with <code class="command">virsh</code> or <span class="application"><strong>virt-manager</strong></span> so it is available for host use.
+ </div><div class="procedure"><h6>Procedure 12.6. Detaching a PCI device from a guest with virsh</h6><ol class="1"><li class="step"><p class="title"><strong>Detach the device</strong></p><div class="para">
+ Use the following command to detach the PCI device from the guest by removing it in the guest's XML file:
+ </div><pre class="screen"># virsh detach-device <em class="replaceable"><code>name_of_guest</code></em> <em class="replaceable"><code>file.xml</code></em></pre></li><li class="step"><p class="title"><strong>Re-attach the device to the host (optional)</strong></p><div class="para">
+ If the device is in <em class="parameter"><code>managed</code></em> mode, skip this step. The device will be returned to the host automatically.
+ </div><div class="para">
+ If the device is not using <em class="parameter"><code>managed</code></em> mode, use the following command to re-attach the PCI device to the host machine:
+ </div><pre class="screen"># virsh nodedev-reattach <em class="replaceable"><code>device</code></em></pre><div class="para">
+ For example, to re-attach the <code class="literal">pci_0000_01_00_0</code> device to the host:
+ </div><pre class="screen">virsh nodedev-reattach pci_0000_01_00_0</pre><div class="para">
+ The device is now available for host use.
+ </div></li></ol></div><div class="procedure"><h6>Procedure 12.7. Detaching a PCI Device from a guest with virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Open the virtual hardware details screen</strong></p><div class="para">
+ In <span class="application"><strong>virt-manager</strong></span>, double-click on the virtual machine that contains the device. Select the <span class="guilabel"><strong>Show virtual hardware details</strong></span> button to display a list of virtual hardware.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/vm_info_button_new.png" alt="The Show virtual hardware details button." /></div></div><h6>Figure 12.4. The virtual hardware details button</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Select and remove the device</strong></p><div class="para">
+ Select the PCI device to be detached from the list of virtual devices in the left panel.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/PCIremoval.png" width="444" alt="The PCI device details and the Remove button." /></div></div><h6>Figure 12.5. Selecting the PCI device to be detached</h6></div><br class="figure-break" /><div class="para">
+ Click the <span class="guibutton"><strong>Remove</strong></span> button to confirm. The device is now available for host use.
+ </div></li></ol></div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 13. SR-IOV</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#idm118056880">13.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works">13.2. Using SR-IOV</a></span></dt><dt><span class="section"><a href="#idm75436048">13.3. Troubleshooting SR-IOV</a></span></dt></dl></div><div class="section" id="idm118056880"><div class="titlepage"><div><div><h2 class="title" id="idm118056880">13.1. Introduction</h2></div></div></div><div class="para">
+ Developed by the PCI-SIG (PCI Special Interest Group), the Single Root I/O Virtualization (SR-IOV) specification is a standard for a type of PCI device assignment that can share a single device to multiple virtual machines. SR-IOV improves device performance for virtual machines.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/SR-IOV_implementation_2.png" width="444" alt="How SR-IOV works" /></div></div><h6>Figure 13.1. How SR-IOV works</h6></div><br class="figure-break" /><div class="para">
+ SR-IOV enables a Single Root Function (for example, a single Ethernet port), to appear as multiple, separate, physical devices. A physical device with SR-IOV capabilities can be configured to appear in the PCI configuration space as multiple functions. Each device has its own configuration space complete with Base Address Registers (BARs).
+ </div><div class="para">
+ SR-IOV uses two PCI functions:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Physical Functions (PFs) are full PCIe devices that include the SR-IOV capabilities. Physical Functions are discovered, managed, and configured as normal PCI devices. Physical Functions configure and manage the SR-IOV functionality by assigning Virtual Functions.
+ </div></li><li class="listitem"><div class="para">
+ Virtual Functions (VFs) are simple PCIe functions that only process I/O. Each Virtual Function is derived from a Physical Function. The number of Virtual Functions a device may have is limited by the device hardware. A single Ethernet port, the Physical Device, may map to many Virtual Functions that can be shared to virtual machines.
+ </div></li></ul></div><div class="para">
+ The hypervisor can map one or more Virtual Functions to a virtual machine. The Virtual Function's configuration space is then mapped to the configuration space presented to the guest.
+ </div><div class="para">
+ Each Virtual Function can only be mapped to a single guest at a time, as Virtual Functions require real hardware resources. A virtual machine can have multiple Virtual Functions. A Virtual Function appears as a network card in the same way as a normal network card would appear to an operating system.
+ </div><div class="para">
+ The SR-IOV drivers are implemented in the kernel. The core implementation is contained in the PCI subsystem, but there must also be driver support for both the Physical Function (PF) and Virtual Function (VF) devices. An SR-IOV capable device can allocate VFs from a PF. The VFs appear as PCI devices which are backed on the physical PCI device by resources such as queues and register sets.
+ </div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-Libvirt_Strengths"><h5 class="formalpara">Advantages of SR-IOV</h5>
+ SR-IOV devices can share a single physical port with multiple virtual machines.
+ </div><div class="para">
+ Virtual Functions have near-native performance and provide better performance than para-virtualized drivers and emulated access. Virtual Functions provide data protection between virtual machines on the same physical server as the data is managed and controlled by the hardware.
+ </div><div class="para">
+ These features allow for increased virtual machine density on hosts within a data center.
+ </div><div class="para">
+ SR-IOV is better able to utilize the bandwidth of devices with multiple guests.
+ </div></div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works"><div class="titlepage"><div><div><h2 class="title">13.2. Using SR-IOV</h2></div></div></div><div class="para">
+ This section covers the use of PCI passthrough to assign a Virtual Function of an SR-IOV capable multiport network card to a virtual machine as a network device.
+ </div><div class="para">
+ SR-IOV Virtual Functions (VFs) can be assigned to virtual machines by adding a device entry in <em class="parameter"><code><hostdev></code></em> with the <code class="command">virsh edit</code> or <code class="command">virsh attach-device</code> command. However, this can be problematic because unlike a regular network device, an SR-IOV VF network device does not have a permanent unique MAC address, and is assigned a new MAC address each time the host is rebooted. Because of this, even if the guest is assigned the same VF after a reboot, when the host is rebooted the guest determines its network adapter to have a new MAC address. As a result, the guest believes there is new hardware connected each time, and will usually require re-configuration of the guest's network settings.
+ </div><div class="para">
+ <span class="package">libvirt-0.9.10</span> and newer contains the <em class="parameter"><code><interface type='hostdev'></code></em> interface device. Using this interface device, <span class="application"><strong>libvirt</strong></span> will first perform any network-specific hardware/switch initialization indicated (such as setting the MAC address, VLAN tag, or 802.1Qbh virtualport parameters), then perform the PCI device assignment to the guest.
+ </div><div class="para">
+ Using the <em class="parameter"><code><interface type='hostdev'></code></em> interface device requires:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ an SR-IOV-capable network card,
+ </div></li><li class="listitem"><div class="para">
+ host hardware that supports either the Intel VT-d or the AMD IOMMU extensions, and
+ </div></li><li class="listitem"><div class="para">
+ the PCI address of the VF to be assigned.
+ </div></li></ul></div>
+
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Assignment of an SR-IOV device to a virtual machine requires that the host hardware supports the Intel VT-d or the AMD IOMMU specification.
+ </div></div></div><div class="para">
+ To attach an SR-IOV network device on an Intel or an AMD system, follow this procedure:
+ </div><div class="procedure"><h6>Procedure 13.1. Attach an SR-IOV network device on an Intel or AMD system</h6><ol class="1"><li class="step"><p class="title"><strong>Enable Intel VT-d or the AMD IOMMU specifications in the BIOS and kernel</strong></p><div class="para">
+ On an Intel system, enable Intel VT-d in the BIOS if it is not enabled already. Refer to <a class="xref" href="#intel-prep">Procedure 12.1, “Preparing an Intel system for PCI device assignment”</a> for procedural help on enabling Intel VT-d in the BIOS and kernel.
+ </div><div class="para">
+ Skip this step if Intel VT-d is already enabled and working.
+ </div><div class="para">
+ On an AMD system, enable the AMD IOMMU specifications in the BIOS if they are not enabled already. Refer to <a class="xref" href="#amd-prep">Procedure 12.2, “Preparing an AMD system for PCI device assignment”</a> for procedural help on enabling IOMMU in the BIOS.
+ </div></li><li class="step"><p class="title"><strong>Verify support</strong></p><div class="para">
+ Verify if the PCI device with SR-IOV capabilities is detected. This example lists an Intel 82576 network interface card which supports SR-IOV. Use the <code class="command">lspci</code> command to verify whether the device was detected.
+ </div><pre class="screen"># lspci
+03:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
+03:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)</pre><div class="para">
+ Note that the output has been modified to remove all other devices.
+ </div></li><li class="step"><p class="title"><strong>Start the SR-IOV kernel modules</strong></p><div class="para">
+ If the device is supported the driver kernel module should be loaded automatically by the kernel. Optional parameters can be passed to the module using the <code class="command">modprobe</code> command. The Intel 82576 network interface card uses the <code class="command">igb</code> driver kernel module.
+ </div><pre class="screen"># modprobe igb [<option>=<VAL1>,<VAL2>,]
+# lsmod |grep igb
+igb 87592 0
+dca 6708 1 igb</pre></li><li class="step"><p class="title"><strong>Activate Virtual Functions</strong></p><div class="para">
+ The <em class="parameter"><code>max_vfs</code></em> parameter of the <code class="command">igb</code> module allocates the maximum number of Virtual Functions. The <em class="parameter"><code>max_vfs</code></em> parameter causes the driver to spawn, up to the value of the parameter in, Virtual Functions. For this particular card the valid range is <em class="parameter"><code>0</code></em> to <em class="parameter"><code>7</code></em>.
+ </div><div class="para">
+ Remove the module to change the variable.
+ </div><pre class="screen"># modprobe -r igb</pre><div class="para">
+ Restart the module with the <em class="parameter"><code>max_vfs</code></em> set to <em class="parameter"><code>7</code></em> or any number of Virtual Functions up to the maximum supported by your device.
+ </div><pre class="screen"># modprobe igb max_vfs=7</pre></li><li class="step"><p class="title"><strong>Make the Virtual Functions persistent</strong></p><div class="para">
+ Add the line <code class="option">options igb max_vfs=7</code> to any file in <code class="filename">/etc/modprobe.d</code> to make the Virtual Functions persistent. For example:
+ </div><pre class="screen"># echo "options igb max_vfs=7" >>/etc/modprobe.d/igb.conf</pre></li><li class="step"><p class="title"><strong>Inspect the new Virtual Functions</strong></p><div class="para">
+ Using the <code class="command">lspci</code> command, list the newly added Virtual Functions attached to the Intel 82576 network device. (Alternatively, use <code class="command">grep</code> to search for <code class="literal">Virtual Function</code>, to search for devices that support Virtual Functions.)
+ </div><pre class="screen"># lspci | grep 82576
+0b:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
+0b:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
+0b:10.0 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.1 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.2 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.3 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.4 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.5 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.6 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.7 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:11.0 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:11.1 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:11.2 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:11.3 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:11.4 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:11.5 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)</pre><div class="para">
+ The identifier for the PCI device is found with the <em class="parameter"><code>-n</code></em> parameter of the <code class="command">lspci</code> command. The Physical Functions correspond to <code class="computeroutput">0b:00.0</code> and <code class="computeroutput">0b:00.1</code>. All Virtual Functions have <code class="computeroutput">Virtual Function</code> in the description.
+ </div></li><li class="step"><p class="title"><strong>Verify devices exist with virsh</strong></p><div class="para">
+ The <code class="systemitem">libvirt</code> service must recognize the device before adding a device to a virtual machine. <code class="systemitem">libvirt</code> uses a similar notation to the <code class="command">lspci</code> output. All punctuation characters, <span class="keycap"><strong>;</strong></span> and <span class="keycap"><strong>.</strong></span>, in <code class="command">lspci</code> output are changed to underscores (<span class="keycap"><strong>_</strong></span>).
+ </div><div class="para">
+ Use the <code class="command">virsh nodedev-list</code> command and the <code class="command">grep</code> command to filter the Intel 82576 network device from the list of available host devices. <em class="parameter"><code>0b</code></em> is the filter for the Intel 82576 network devices in this example. This may vary for your system and may result in additional devices.
+ </div><pre class="screen"># virsh nodedev-list | grep <em class="parameter"><code>0b</code></em>
+pci_0000_0b_00_0
+pci_0000_0b_00_1
+pci_0000_0b_10_0
+pci_0000_0b_10_1
+pci_0000_0b_10_2
+pci_0000_0b_10_3
+pci_0000_0b_10_4
+pci_0000_0b_10_5
+pci_0000_0b_10_6
+pci_0000_0b_11_7
+pci_0000_0b_11_1
+pci_0000_0b_11_2
+pci_0000_0b_11_3
+pci_0000_0b_11_4
+pci_0000_0b_11_5</pre><div class="para">
+ The serial numbers for the Virtual Functions and Physical Functions should be in the list.
+ </div></li><li class="step"><p class="title"><strong>Get device details with virsh</strong></p><div class="para">
+ The <code class="computeroutput">pci_0000_0b_00_0</code> is one of the Physical Functions and <code class="computeroutput">pci_0000_0b_10_0</code> is the first corresponding Virtual Function for that Physical Function. Use the <code class="command">virsh nodedev-dumpxml</code> command to get advanced output for both devices.
+ </div><pre class="screen"># virsh nodedev-dumpxml pci_0000_0b_00_0
+<device>
+ <name>pci_0000_0b_00_0</name>
+ <parent>pci_0000_00_01_0</parent>
+ <driver>
+ <name>igb</name>
+ </driver>
+ <capability type='pci'>
+ <domain>0</domain>
+ <bus>11</bus>
+ <slot>0</slot>
+ <function>0</function>
+ <product id='0x10c9'>Intel Corporation</product>
+ <vendor id='0x8086'>82576 Gigabit Network Connection</vendor>
+ </capability>
+</device></pre><pre class="screen"># virsh nodedev-dumpxml pci_0000_0b_10_0
+<device>
+ <name>pci_0000_0b_10_0</name>
+ <parent>pci_0000_00_01_0</parent>
+ <driver>
+ <name>igbvf</name>
+ </driver>
+ <capability type='pci'>
+ <domain>0</domain>
+ <bus>11</bus>
+ <slot>16</slot>
+ <function>0</function>
+ <product id='0x10ca'>Intel Corporation</product>
+ <vendor id='0x8086'>82576 Virtual Function</vendor>
+ </capability>
+</device></pre><div class="para">
+ This example adds the Virtual Function <code class="systemitem">pci_0000_0b_10_0</code> to the virtual machine in <a class="xref" href="#step9">Step 9</a>. Note the <code class="computeroutput">bus</code>, <code class="computeroutput">slot</code> and <code class="computeroutput">function</code> parameters of the Virtual Function: these are required for adding the device.
+ </div><div class="para">
+ Copy these parameters into a temporary XML file, such as <code class="filename">/tmp/new-interface.xml</code> for example.
+ </div><pre class="programlisting">
+ <interface type='hostdev' managed='yes'>
+ <source>
+ <address type='pci' domain='0' bus='11' slot='16' function='0'/>
+ </source>
+ </interface></pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If you do not specify a MAC address, one will be automatically generated. The <em class="parameter"><code><virtualport></code></em> element is only used when connecting to an 802.11Qbh hardware switch. The <em class="parameter"><code><vlan></code></em> element was introduced for Fedora 18 and this will transparently put the guest's device on the VLAN tagged <em class="parameter"><code>42</code></em>.
+ </div><div class="para">
+ When the virtual machine starts, it should see a network device of the type provided by the physical adapter, with the configured MAC address. This MAC address will remain unchanged across host and guest reboots.
+ </div><div class="para">
+ The following <em class="parameter"><code><interface></code></em> example shows the syntax for the optional <em class="parameter"><code><mac address></code></em>, <em class="parameter"><code><virtualport></code></em>, and <em class="parameter"><code><vlan></code></em> elements. In practice, use either the <em class="parameter"><code><vlan></code></em> or <em class="parameter"><code><virtualport></code></em> element, not both simultaneously as shown in the example:
+ </div><pre class="programlisting">...
+ <devices>
+ ...
+ <interface type='hostdev' managed='yes'>
+ <source>
+ <address type='pci' domain='0' bus='11' slot='16' function='0'/>
+ </source>
+ <mac address='52:54:00:6d:90:02'>
+ <vlan>
+ <tag id='42'/>
+ </vlan>
+ <virtualport type='802.1Qbh'>
+ <parameters profileid='finance'/>
+ </virtualport>
+ </interface>
+ ...
+ </devices></pre></div></div></li><li class="step" id="step9"><p class="title"><strong>Add the Virtual Function to the virtual machine</strong></p><div class="para">
+ Add the Virtual Function to the virtual machine using the following command with the temporary file created in the previous step. This attaches the new device immediately and saves it for subsequent guest restarts.
+ </div><pre class="screen">
+virsh attach-device <em class="replaceable"><code>MyGuest</code></em> <code class="filename">/tmp/new-interface.xml</code> --live --config
+</pre><div class="para">
+ Specifying the <code class="option">--live</code> option with <code class="command">virsh attach-device</code> attaches the new device to the running guest. Using the <code class="option">--config</code> option ensures the new device is available after future guest restarts.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The <code class="option">--live</code> option is only accepted when the guest is running. <code class="command">virsh</code> will return an error if the <code class="option">--live</code> option is used on a non-running guest.
+ </div></div></div></li></ol></div><div class="para">
+ The virtual machine detects a new network interface card. This new card is the Virtual Function of the SR-IOV device.
+ </div></div><div class="section" id="idm75436048"><div class="titlepage"><div><div><h2 class="title" id="idm75436048">13.3. Troubleshooting SR-IOV</h2></div></div></div><div class="para">
+ This section contains solutions for problems which may affect SR-IOV.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Error starting the guest</span></dt><dd><div class="para">
+ When starting a configured virtual machine, an error occurs as follows:
+ </div><pre class="screen"># virsh start test
+error: Failed to start domain test
+error: internal error unable to start guest: char device redirected to
+/dev/pts/2
+get_real_device: /sys/bus/pci/devices/0000:03:10.0/config: Permission denied
+init_assigned_device: Error: Couldn't get real device (03:10.0)!
+Failed to initialize assigned device host=03:10.0</pre><div class="para">
+ This error is often caused by a device that is already assigned to another guest or to the host itself.
+ </div></dd><dt class="varlistentry"><span class="term">Error migrating, saving, or dumping the guest</span></dt><dd><div class="para">
+ Attempts to migrate and dump the virtual machine cause an error similar to the following:
+ </div><pre class="screen"># virsh dump --crash 5 /tmp/vmcore
+error: Failed to core dump domain 5 to /tmp/vmcore
+error: internal error unable to execute QEMU command 'migrate': An undefined
+error has occurred</pre><div class="para">
+ Because device assignment uses hardware on the specific host where the virtual machine was started, guest migration and save are not supported when device assignment is in use. Currently, the same limitation also applies to core-dumping a guest; this may change in the future.
+ </div></dd></dl></div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 14. KVM guest timing management</h2></div></div></div><div class="para">
+ Virtualization involves several intrinsic challenges for time keeping in guest virtual machines. Interrupts cannot always be delivered simultaneously and instantaneously to all guest virtual machines, because interrupts in virtual machines are not true interrupts; they are injected into the guest virtual machine by the host machine. The host may be running another guest virtual machine, or a different process, meaning that the precise timing typically required by interrupts may not always be possible.
+ </div><div class="para">
+ Guest virtual machines without accurate time keeping may experience issues with network applications and processes, as session validity, migration, and other network activities rely on timestamps to remain correct.
+ </div><div class="para">
+ KVM avoids these issues by providing guest virtual machines with a para-virtualized clock (<span class="application"><strong>kvm-clock</strong></span>). However, it is still vital to test timing before attempting activities that may be affected by time keeping inaccuracies.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Fedora 17 and newer, uses <span class="application"><strong>kvm-clock</strong></span> as their default clock source. Running without <span class="application"><strong>kvm-clock</strong></span> requires special configuration, and is not recommended.
+ </div></div></div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The Network Time Protocol (NTP) daemon should be running on the host and the guest virtual machines. 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">
+ The <code class="systemitem">ntpd</code> service will correct the effects of clock skew as long as the clock runs no more than 0.05% faster or slower than the reference time source. The <code class="systemitem">ntp</code> startup script adjusts the clock offset from the reference time by adjusting the system clock at startup time, if required.
+ </div></div></div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management-Determining_if_your_CPU_has_the_constant_Time_Stamp_Counter"><h5 class="formalpara">Constant Time Stamp Counter (TSC)</h5>
+ Modern Intel and AMD CPUs provide a constant Time Stamp Counter (TSC). The count frequency of the constant TSC does not vary when the CPU core itself changes frequency, for example, to comply with a power saving policy. A CPU with a constant TSC frequency is necessary in order to use the TSC as a clock source for KVM guests.
+ </div><div class="para">
+ 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" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management-Configuring_hosts_without_a_constant_Time_Stamp_Counter"><h5 class="formalpara">Configuring hosts without a constant Time Stamp Counter</h5>
+ Systems without a constant TSC frequency cannot use the TSC as a clock source for virtual machines, and require additional configuration. Power management features interfere with accurate time keeping and must be disabled for guest virtual machines to accurately keep time with KVM.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ These instructions are for AMD revision F CPUs only.
+ </div></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. Deep C sleep states can stop the TSC. To prevent the kernel using deep C states append <code class="command">processor.max_cstate=1</code> to the kernel boot options in the <code class="filename">grub.conf</code> file on the host:
+ </div><pre class="screen">title Fedora (2.6.32-330.x86_64)
+ root (hd0,0)
+ kernel /vmlinuz-2.6.32-330.x86_64 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" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management-Required_parameters_for_RHEL_guests"><h5 class="formalpara">Required parameters for Fedora Linux guests</h5>
+ For certain Fedroa guest virtual machines, additional kernel parameters are required. These parameters can be set by appending them to the end of the <code class="literal">/kernel</code> line in the <code class="filename">/boot/grub/grub.conf</code> file of the guest virtual machine.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The <em class="parameter"><code>lpj</code></em> parameter requires a numeric value equal to the <span class="emphasis"><em>loops per jiffy</em></span> value of the specific CPU on which the guest virtual machine runs. If you do not know this value, do not set the <em class="parameter"><code>lpj</code></em> parameter.
+ </div></div></div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ The <em class="parameter"><code>divider</code></em> kernel parameter was previously recommended for Fedora guest virtual machines that did not have high responsiveness requirements, or exist on systems with high guest density. It is no longer recommended for use with guests running Fedora versions prior to version 16.
+ </div></div></div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management-KVM_guest_timing_management-Using_the_Real_Time_Clock_with_Windows_guests"><h5 class="formalpara">Using the Real-Time Clock with Windows Server 2003 and Windows XP guests</h5>
+ Windows uses the both the Real-Time Clock (RTC) and the Time Stamp Counter (TSC). For Windows guest virtual machines the Real-Time Clock can be used instead of the TSC for all time sources which resolves guest timing issues.
+ </div><div class="para">
+ To enable the Real-Time Clock for the <code class="computeroutput">PMTIMER</code> clock source (the <code class="computeroutput">PMTIMER</code> usually uses the TSC), add the following option to the Windows boot settings. Windows boot settings are stored in the boot.ini file. Add the following option to the end of the Windows boot line in the <code class="filename">boot.ini</code> file:
+ </div><pre class="screen">/usepmtimer
+</pre><div class="para">
+ For more information on Windows boot settings and the usepmtimer 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 class="formalpara"><h5 class="formalpara" id="idm96451936">Using the Real-Time Clock with Windows Server 2008, Windows Server 2008 R2, and Windows 7 guests</h5>
+ Windows uses the both the Real-Time Clock (RTC) and the Time Stamp Counter (TSC). For Windows guest virtual machines the Real-Time Clock can be used instead of the TSC for all time sources, which resolves guest timing issues.
+ </div><div class="para">
+ The <code class="filename">boot.ini</code> file is no longer used as of Windows Server 2008 and newer. Windows Server 2008, Windows Server 2008 R2, and Windows 7 do not use the TSC as a time source if the <code class="literal">hypervisor-present</code> bit is set. The Fedora KVM hypervisor enables this CPUID bit by default, so it is no longer necessary to use the <span class="application"><strong>Boot Configuration Data Editor</strong></span> (<code class="command">bcdedit.exe</code>) to modify the Windows boot parameters.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Open the Windows guest virtual machine.
+ </div></li><li class="step"><div class="para">
+ Open the <span class="guimenuitem"><strong>Accessories</strong></span> menu of the <span class="guimenuitem"><strong>start</strong></span> menu. Right click on the <span class="application"><strong>Command Prompt</strong></span> application, select <span class="guilabel"><strong>Run as Administrator</strong></span>.
+ </div></li><li class="step"><div class="para">
+ Confirm the security exception, if prompted.
+ </div></li><li class="step"><div class="para">
+ Set the boot manager to use the platform clock. This should instruct Windows to use the PM timer for the primary clock source. The system UUID (<em class="parameter"><code>{default}</code></em> in the example below) should be changed if the system UUID is different than the default boot device.
+ </div><pre class="screen">C:\Windows\system32>bcdedit /set {default} USEPLATFORMCLOCK on
+The operation completed successfully</pre></li></ol></div><div class="para">
+ This fix should improve time keeping for Windows Server 2008 and Windows 7 guests.
+ </div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management-Steal_Time_Accounting"><h5 class="formalpara">Steal time accounting</h5>
+ Steal time is the amount of CPU time desired by a guest virtual machine that is not provided by the host. Steal time occurs when the host allocates these resources elsewhere: for example, to another guest.
+ </div><div class="para">
+ Steal time is reported in the CPU time fields in <code class="filename">/proc/stat</code> as <em class="parameter"><code>st</code></em>. It is automatically reported by utilities such as <code class="command">top</code> and <code class="command">vmstat</code>, and cannot be switched off.
+ </div><div class="para">
+ Large amounts of steal time indicate CPU contention, which can reduce guest performance. To relieve CPU contention, increase the guest's CPU priority or CPU quota, or run fewer guests on the host.
+ </div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 15. Network booting with libvirt</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#idm108542864">15.1. Preparing the boot server</a></span></dt><dd><dl><dt><span class="section"><a href="#idm94566704">15.1.1. Setting up a PXE boot server on a private libvirt network</a></span></dt></dl></dd><dt><span class="section"><a href="#idm111619024">15.2. Booting a guest using PXE</a></span></dt><dd><dl><dt><span class="section"><a href="#idm88744848">15.2.1. Using bridged networking</a></span></dt><dt><span class="section"><a href="#idm99814048">15.2.2. Using a private libvirt network</a></span></dt></dl></dd></dl></div><div class="para">
+ Guest virtual machines can be booted with PXE enabled. PXE allows guest virtual machines to boot and load their configuration off the network itself. This section demonstrates some basic configuration steps to configure PXE guests with libvirt.
+ </div><div class="para">
+ This section does not cover the creation of boot images or PXE servers. It is used to explain how to configure libvirt, in a private or bridged network, to boot a guest virtual machine with PXE booting enabled.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ These procedures are provided only as an example. Ensure that you have sufficient backups before proceeding.
+ </div></div></div><div class="section" id="idm108542864"><div class="titlepage"><div><div><h2 class="title" id="idm108542864">15.1. Preparing the boot server</h2></div></div></div><div class="para">
+ To perform the steps in this chapter you will need:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ A PXE Server (DHCP and TFTP) - This can be a libvirt internal server, manually-configured dhcpd and tftpd, dnsmasq, a server configured by Cobbler, or some other server.
+ </div></li><li class="listitem"><div class="para">
+ Boot images - for example, PXELINUX configured manually or by Cobbler.
+ </div></li></ul></div><div class="section" id="idm94566704"><div class="titlepage"><div><div><h3 class="title" id="idm94566704">15.1.1. Setting up a PXE boot server on a private libvirt network</h3></div></div></div><div class="para">
+ This example uses the <span class="emphasis"><em>default</em></span> network. Perform the following steps:
+ </div><div class="procedure"><h6>Procedure 15.1. Configuring the PXE boot server</h6><ol class="1"><li class="step"><div class="para">
+ Place the PXE boot images and configuration in <code class="filename">/var/lib/tftp</code>.
+ </div></li><li class="step"><div class="para">
+ Run the following commands:
+ </div><pre class="screen"># virsh net-destroy default
+# virsh net-edit default</pre></li><li class="step"><div class="para">
+ Edit the <code class="code"><ip></code> element in the configuration file for the <span class="emphasis"><em>default</em></span> network to include the appropriate address, network mask, DHCP address range, and boot file, where <em class="replaceable"><code>BOOT_FILENAME</code></em> represents the file name you are using to boot the guest virtual machine.
+ </div><pre class="screen"><ip address='192.168.122.1' netmask='255.255.255.0'>
+ <tftp root='/var/lib/tftp' />
+ <dhcp>
+ <range start='192.168.122.2' end='192.168.122.254' />
+ <bootp file='<em class="replaceable"><code>BOOT_FILENAME</code></em>' />
+ </dhcp>
+</ip></pre></li><li class="step"><div class="para">
+ Boot the guest using PXE (refer to <a class="xref" href="#booting-guest-with-pxe">Section 15.2, “Booting a guest using PXE”</a>).
+ </div></li></ol></div></div></div><div class="section" id="idm111619024"><div class="titlepage"><div><div><h2 class="title" id="idm111619024">15.2. Booting a guest using PXE</h2></div></div></div><div class="para">
+ This section demonstrates how to boot a guest virtual machine with PXE.
+ </div><div class="section" id="idm88744848"><div class="titlepage"><div><div><h3 class="title" id="idm88744848">15.2.1. Using bridged networking</h3></div></div></div><div class="procedure"><h6>Procedure 15.2. Booting a guest using PXE and bridged networking</h6><ol class="1"><li class="step"><div class="para">
+ Ensure bridging is enabled such that the PXE boot server is available on the network.
+ </div></li><li class="step"><div class="para">
+ Boot a guest virtual machine with PXE booting enabled. You can use the <code class="command">virt-install</code> command to create a new virtual machine with PXE booting enabled, as shown in the following example command:
+ </div><pre class="screen">virt-install --pxe --network bridge=breth0 --prompt</pre><div class="para">
+ Alternatively, ensure that the guest network is configured to use your bridged network, and that the XML guest configuration file has a <code class="code"><boot dev='network'/></code> element inside the <code class="code"><os></code> element, as shown in the following example:
+ </div><pre class="screen"><os>
+ <type arch='x86_64' machine='rhel6.2.0'>hvm</type>
+ <boot dev='network'/>
+ <boot dev='hd'/>
+</os>
+<interface type='bridge'>
+ <mac address='52:54:00:5a:ad:cb'/>
+ <source bridge='breth0'/>
+ <target dev='vnet0'/>
+ <alias name='net0'/>
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
+</interface></pre></li></ol></div></div><div class="section" id="idm99814048"><div class="titlepage"><div><div><h3 class="title" id="idm99814048">15.2.2. Using a private libvirt network</h3></div></div></div><div class="procedure"><h6>Procedure 15.3. Using a private libvirt network</h6><ol class="1"><li class="step"><div class="para">
+ Configure PXE booting on libvirt as shown in <a class="xref" href="#setting-up-server-private">Section 15.1.1, “Setting up a PXE boot server on a private libvirt network”</a>.
+ </div></li><li class="step"><div class="para">
+ Boot a guest virtual machine using libvirt with PXE booting enabled. You can use the <code class="command">virt-install</code> command to create/install a new virtual machine using PXE:
+ </div><pre class="screen">virt-install --pxe --network network=default --prompt</pre></li></ol></div><div class="para">
+ Alternatively, ensure that the guest network is configured to use your bridged network, and that the XML guest configuration file has a <code class="code"><boot dev='network'/></code> element inside the <code class="code"><os></code> element, as shown in the following example:
+ </div><pre class="screen"><os>
+ <type arch='x86_64' machine='rhel6.2.0'>hvm</type>
+ <boot dev='network'/>
+ <boot dev='hd'/>
+</os></pre><div class="para">
+ Also ensure that the guest virtual machine is connected to the private network:
+ </div><pre class="screen"><interface type='network'>
+ <mac address='52:54:00:66:79:14'/>
+ <source network='default'/>
+ <target dev='vnet0'/>
+ <alias name='net0'/>
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
+</interface></pre></div></div></div><div xml:lang="en-US" class="chapter" id="qemu-ga" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 16. QEMU Guest Agent</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#idm84408672">16.1. Set Up Communication between Guest Agent and Host</a></span></dt></dl></div><div class="para">
+ The QEMU Guest Agent allows the host machine to issue commands to the guest operating system. The guest operating system then responds to those commands asynchronously.
+ </div><div class="para">
+ This section covers the options and commands available to the guest agent in detail. It also covers how to run the guest agent in the foreground, or as a daemon in the background.
+ </div><div class="section" id="idm84408672"><div class="titlepage"><div><div><h2 class="title" id="idm84408672">16.1. Set Up Communication between Guest Agent and Host</h2></div></div></div><div class="para">
+ The host machine communicates with the guest agent through a VirtIO serial connection between the host and guest machines. A VirtIO serial channel is connected to the host via a character device driver (typically a Unix socket), and the guest listens on this serial channel. The following procedure shows how to set up the host and guest machines for guest agent use.
+ </div><div class="procedure"><h6>Procedure 16.1. Set Up Host-Agent Communication</h6><ol class="1"><li class="step"><p class="title"><strong>Launch QEMU with a character device driver</strong></p><div class="para">
+ Launch QEMU as usual, with additional definitions for the character device driver required to communicate with the guest agent.
+ </div><div class="para">
+ The following example launches QEMU to communicate over the Unix socket <code class="filename">/tmp/qga.sock</code>.
+ </div><pre class="screen">/usr/libexec/qemu-kvm [...] -chardev socket,path=/tmp/qga.sock,server,nowait,id=qga0 \
+ -device virtio-serial \
+ -device virtserialport,chardev=qga0,name=org.qemu.guest_agent.0</pre></li><li class="step"><p class="title"><strong>Start the Guest Agent</strong></p><div class="para">
+ On the guest, run the following command to start the Guest Agent:
+ </div><pre class="screen">qemu-ga --path <em class="replaceable"><code>device_path</code></em> --method <em class="replaceable"><code>method</code></em></pre><div class="para">
+ The guest agent now parses incoming QMP messages for commands, and acts upon them if valid.
+ </div><div class="para">
+ If no other method or path is specified with the <code class="option">--method</code> or <code class="option">--path</code> options respectively, the Guest Agent listens over <code class="literal">virtio-serial</code>, through the <code class="filename">/dev/virtio-ports/org.qemu.guest_agent.0</code> device path.
+ </div></li></ol></div><div class="para">
+ You can now communicate with the guest by sending valid QMP commands over the established character device driver.
+ </div></div></div></div><div class="part" id="idm110765328"><div class="titlepage"><div><div><h1 class="title">Part II. Administration</h1></div></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-Server_best_practices">17. Server best practices</a></span></dt><dt><span class="chapter"><a href="#chap-Virtualization-Security_for_virtualization">18. Security for virtualization</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Security_for_virtualization-Storage_security_issues">18.1. Storage security issues</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization">18.2. SELinux and virtualization</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Security_for_virtualization-SELinux_considerations">18.3. SELinux</a></span></dt><dt><span class="section"><a href=
"#idm89964272">18.4. Virtualization firewall information</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-sVirt">19. sVirt</a></span></dt><dd><dl><dt><span class="section"><a href="#idm121820688">19.1. Security and Virtualization</a></span></dt><dt><span class="section"><a href="#idm98075168">19.2. sVirt labeling</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-KVM_live_migration">20. KVM live migration</a></span></dt><dd><dl><dt><span class="section"><a href="#Live_migration_requirements">20.1. Live migration requirements</a></span></dt><dt><span class="section"><a href="#Live_migration_and_RHEL_compatibility">20.2. Live migration and Fedora version compatibility </a></span></dt><dt><span class="section"><a href="#shared-storage-nfs-migration">20.3. Shared storage example: NFS for a simple migration</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-KVM_live_migration-Live_KVM_migratio
n_with_virsh">20.4. Live KVM migration with virsh</a></span></dt><dd><dl><dt><span class="section"><a href="#add-notes">20.4.1. Additonal tips for migration with virsh </a></span></dt><dt><span class="section"><a href="#virsh-migration-arguements">20.4.2. Additional options for the virsh migrate command</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager">20.5. Migrating with virt-manager</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests">21. Remote management of guests</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_with_SSH">21.1. Remote management with SSH</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL">21.2. Remote manage
ment over TLS and SSL</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes">21.3. Transport modes</a></span></dt></dl></dd><dt><span class="chapter"><a href="#sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM">22. Overcommitting with KVM</a></span></dt><dt><span class="chapter"><a href="#chap-KSM">23. KSM</a></span></dt><dt><span class="chapter"><a href="#chap-Virtualization_Administration_GuideAdvanced">24. Advanced virtualization administration</a></span></dt><dd><dl><dt><span class="section"><a href="#idm82218240">24.1. Control Groups (cgroups)</a></span></dt><dt><span class="section"><a href="#idm118488944">24.2. Hugepage support</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-Tips_and_tricks">25. Miscellaneous administration tasks</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Automatica
lly_starting_guests">25.1. Automatically starting guests</a></span></dt><dt><span class="section"><a href="#sect-mem-dump-off">25.2. Guest memory allocation</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Using_qemu_img">25.3. Using qemu-img</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions">25.4. Verifying virtualization extensions</a></span></dt><dt><span class="section"><a href="#idm71657744">25.5. Setting KVM processor affinities</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address">25.6. Generating a new unique MAC address</a></span></dt><dt><span class="section"><a href="#idm96083232">25.7. Improving guest response time</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests">25.8. Disable SMART disk monitoring for gues
ts</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server">25.9. Configuring a VNC Server</a></span></dt><dt><span class="section"><a href="#sect-gracefully-shut-down-guests">25.10. Gracefully shutting down guests</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers">25.11. Virtual machine timer management with libvirt</a></span></dt><dt><span class="section"><a href="#sect-perf-mon">25.12. Using PMU to monitor guest performance</a></span></dt><dt><span class="section"><a href="#sect-s3-s4">25.13. Guest virtual machine power management</a></span></dt><dt><span class="section"><a href="#sect-qemu-ga">25.14. QEMU Guest Agent Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-guest-synch">25.14.1. guest-sync</a></span></dt><dt><span class="section"><a href="#subsect-guest-synch-delimited">25.14.2. guest-sync-delimited</a></span></dt></dl></dd><
dt><span class="section"><a href="#sect-limit-redirection">25.15. Setting a limit on device redirection</a></span></dt><dt><span class="section"><a href="#sect-dynamic-vNIC">25.16. Dynamically changing a host or a network bridge that is attached to a virtual NIC</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-Storage_Concepts">26. Storage concepts</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Storage_Concepts-Storage_Pools">26.1. Storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Concepts-Volumes">26.2. Volumes </a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools">27. Storage pools</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating_Storage_Pools">27.1. Creating storage pools </a></span></dt><dd><dl><dt><span class="sect
ion"><a href="#sect-Virtualization-Storage_Pools-Creating-Dedicated_Disk_Devices">27.1.1. Disk-based storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-File_Systems">27.1.2. Partition-based storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-Local_Directories">27.1.3. Directory-based storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-LVM">27.1.4. LVM-based storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-iSCSI">27.1.5. iSCSI-based storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-NFS">27.1.6. NFS-based storage pools</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-Storage_Volumes">28. Volumes </a></span></dt><dd><dl><dt><span clas
s="section"><a href="#sect-Virtualization-Storage_Volumes-Creating_volumes">28.1. Creating volumes</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Volumes-Cloning_volumes">28.2. Cloning volumes</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests">28.3. Adding storage devices to guests</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Adding_storage_devices_to_guests-Adding_file_based_storage_to_a_guest">28.3.1. Adding file based storage to a guest</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest">28.3.2. Adding hard drives and other block devices to a guest</a></span></dt><dt><span class="section"><a href="#sect-Managing_storage_controllers_in_a_guest">28.3.3. Managing storage controllers in a guest</a></span></dt></dl></dd><dt><spa
n class="section"><a href="#sect-Virtualization-Storage_Volumes-Deleting_volumes">28.4. Deleting and removing volumes</a></span></dt></dl></dd><dt><span class="chapter"><a href="#vhostmd">29. The Virtual Host Metrics Daemon (vhostmd)</a></span></dt><dd><dl><dt><span class="section"><a href="#idm110570048">29.1. Installing vhostmd on the host</a></span></dt><dt><span class="section"><a href="#idm80150944">29.2. Configuration of vhostmd</a></span></dt><dt><span class="section"><a href="#idm12488144">29.3. Starting and stopping the daemon</a></span></dt><dt><span class="section"><a href="#idm106196464">29.4. Verifying that vhostmd is working from the host</a></span></dt><dt><span class="section"><a href="#idm86879104">29.5. Configuring guests to see the metrics</a></span></dt><dt><span class="section"><a href="#idm91330288">29.6. Using vm-dump-metrics in Fedora guests to verify operation</a></span></dt></dl></dd></dl></div><div xml:lang="en-US" class="chapter" id="chap-Virtuali
zation_Administration_Guide-Server_best_practices" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 17. 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 host.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Run SELinux in enforcing mode. Set SELinux to run in enforcing mode with the <code class="command">setenforce</code> command.
+ </div><pre class="screen"># setenforce 1
+</pre></li><li class="listitem"><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 class="listitem"><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 class="listitem"><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 class="listitem"><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. Use of shareable, network storage in a central location is highly recommended.
+ </div></li></ul></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization-Security_for_virtualization" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 18. Security for virtualization</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Virtualization-Security_for_virtualization-Storage_security_issues">18.1. Storage security issues</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization">18.2. SELinux and virtualization</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Security_for_virtualization-SELinux_considerations">18.3. SELinux</a></span></dt><dt><span class="section"><a href="#idm89964272">18.4. Virtualization firewall information</a></span></dt></dl></div><div class="para">
+ When deploying virtualization technologies, you must ensure that the host cannot be compromised. The host is a Fedora system that manages the system, devices, memory and networks as well as all virtualized guests. If the host is insecure, all guests 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 class="listitem"><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 class="listitem"><div class="para">
+ Enable SELinux on the hypervisor. Read <a class="xref" href="#sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization">Section 18.2, “SELinux and virtualization”</a> for more information on using SELinux and virtualization.
+ </div></li><li class="listitem"><div class="para">
+ Use a firewall to restrict traffic to the host. You can setup a firewall with default-reject rules that will help secure the host from attacks. It is also important to limit network-facing services.
+ </div></li><li class="listitem"><div class="para">
+ Do not allow normal users to access the host. The host is privileged, and granting access to unprivileged accounts may compromise the level of security.
+ </div></li></ul></div><div class="section" id="sect-Virtualization-Security_for_virtualization-Storage_security_issues"><div class="titlepage"><div><div><h2 class="title">18.1. Storage security issues</h2></div></div></div><div class="para">
+ Administrators of virtualized guests can change the partitions the host boots in certain circumstances. To prevent this administrators should follow these recommendations:
+ </div><div class="para">
+ The host should not use disk labels to identify file systems in the <code class="filename">fstab</code> file, the <code class="filename">initrd</code> file or used by the kernel command line. If less privileged users, especially virtualized guests, have write access to whole partitions or LVM volumes.
+ </div><div class="para">
+ Guests should not be given write access to whole disks or block devices (for example, <code class="filename">/dev/sdb</code>). Use partitions (for example, <code class="filename">/dev/sdb1</code>) or LVM volumes.
+ </div></div><div class="section" id="sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization"><div class="titlepage"><div><div><h2 class="title">18.2. 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 attacker's abilities and works to prevent many common security exploits such as buffer overflow attacks and privilege escalation. It is because of these benefits that all Fedora systems should run with SELinux enabled and in enforcing mode.
+ </div><div class="formalpara" id="form-Virtualization-SELinux_and_virtualization-Adding_LVM_based_storage_with_SELinux_in_enforcing_mode"><h5 class="formalpara">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-SELinux_and_virtualization-Creating_and_mounting_a_logical_volume_on_a_virtualized_guest_with_SELinux_enabled"><h6>Procedure 18.1. Creating and mounting a logical volume on a virtualized guest with SELinux enabled</h6><ol class="1"><li class="step"><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 class="step"><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 class="step"><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 class="step"><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 class="step"><div class="para">
+ Set the correct SELinux type for the libvirt image location.
+ </div><pre class="screen"># semanage fcontext -a -t virt_image_t "/virtstorage(/.*)?"
+</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:virt_image_t:s0
+</pre></li><li class="step"><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">virt_image_t</code> (the <code class="command">restorecon</code> and <code class="command">setfiles</code> commands read the files in <code class="filename">/etc/selinux/targeted/contexts/files/</code>).
+ </div><pre class="screen"># restorecon -R -v /virtstorage
+</pre></li></ol></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Create a new file (using the <code class="command">touch</code> command) on the file system.
+ </div><pre class="screen"># touch <em class="replaceable"><code>/virtstorage/newfile</code></em></pre><div class="para">
+ Verify the file has been relabeled using the following command:
+ </div><pre class="screen"># sudo ls -Z <em class="replaceable"><code>/virtstorage</code></em>
+-rw-------. root root system_u:object_r:virt_image_t:s0 <em class="replaceable"><code>newfile</code></em></pre><div class="para">
+ The output shows that the new file has the correct attribute, <code class="filename">virt_image_t</code>.
+ </div></div></div></div><div class="section" id="sect-Virtualization-Security_for_virtualization-SELinux_considerations"><div class="titlepage"><div><div><h2 class="title">18.3. SELinux</h2></div></div></div><div class="para">
+ This section contains topics to consider when using SELinux with 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. Make sure that you have installed the <code class="filename">policycoreutilis-python</code> package (<code class="command">yum install policycoreutilis-python</code>) before running the command.
+ </div><pre class="screen"># semanage fcontext -a -t virt_image_t -f -b /dev/sda2
+# restorecon /dev/sda2
+</pre><div class="formalpara"><h5 class="formalpara" id="idm115318176">KVM and SELinux</h5>
+ The following table shows the SELinux Booleans which affect KVM when launched by libvirt.
+ </div><div class="segmentedlist"><div class="title"><strong><span class="title">KVM SELinux Booleans</span></strong></div><table border="0"><thead><tr class="segtitle"><th>SELinux Boolean</th><th>Description</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">virt_use_comm</td><td class="seg">Allow virt to use serial/parallel communication ports.</td></tr><tr class="seglistitem"><td class="seg">virt_use_fusefs</td><td class="seg">Allow virt to read fuse files.</td></tr><tr class="seglistitem"><td class="seg">virt_use_nfs</td><td class="seg">Allow virt to manage NFS files.</td></tr><tr class="seglistitem"><td class="seg">virt_use_samba</td><td class="seg">Allow virt to manage CIFS files.</td></tr><tr class="seglistitem"><td class="seg">virt_use_sanlock</td><td class="seg">Allow sanlock to manage virt lib files.</td></tr><tr class="seglistitem"><td class="seg">virt_use_sysfs</td><td class="seg">Allow virt to manage device configuration (PCI).</td></tr><tr class=
"seglistitem"><td class="seg">virt_use_xserver</td><td class="seg">Allow virtual machine to interact with the xserver.</td></tr><tr class="seglistitem"><td class="seg">virt_use_usb</td><td class="seg">Allow virt to use USB devices.</td></tr></tbody></table></div></div><div class="section" id="idm89964272"><div class="titlepage"><div><div><h2 class="title" id="idm89964272">18.4. Virtualization firewall information</h2></div></div></div><div class="para">
+ Various ports are used for communication between virtualized guests and management utilities.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Any network service on a virtualized guest must have the applicable ports open on the guest to allow external access. If a network service on a guest is firewalled it will be inaccessible. Always verify the guests network configuration first.
+ </div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ ICMP requests must be accepted. ICMP packets are used for network testing. You cannot ping guests if ICMP packets are blocked.
+ </div></li><li class="listitem"><div class="para">
+ Port 22 should be open for SSH access and the initial installation.
+ </div></li><li class="listitem"><div class="para">
+ Ports 80 or 443 (depending on the security settings on the RHEV Manager) are used by the vdsm-reg service to communicate information about the host.
+ </div></li><li class="listitem"><div class="para">
+ Ports 5634 to 6166 are used for guest console access with the SPICE protocol.
+ </div></li><li class="listitem"><div class="para">
+ Ports 49152 to 49216 are used for migrations with KVM. Migration may use any port in this range depending on the number of concurrent migrations occurring.
+ </div></li><li class="listitem"><div class="para">
+ Enabling IP forwarding (<code class="computeroutput">net.ipv4.ip_forward = 1</code>) is also required for shared bridges and the default bridge. Note that installing libvirt enables this variable so it will be enabled when the virtualization packages are installed unless it was manually disabled.
+ </div></li></ul></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Note that enabling IP forwarding is <span class="bold bold"><strong>not</strong></span> required for physical bridge devices. When a guest is connected through a physical bridge, traffic only operates at a level that does not require IP configuration such as IP forwarding.
+ </div></div></div></div></div><div xml:lang="en-US" class="chapter" id="chap-sVirt" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 19. sVirt</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#idm121820688">19.1. Security and Virtualization</a></span></dt><dt><span class="section"><a href="#idm98075168">19.2. sVirt labeling</a></span></dt></dl></div><div class="para">
+ sVirt is a technology included in Fedora that integrates SELinux and virtualization. sVirt applies Mandatory Access Control (MAC) to improve security when using virtualized guests. The main reasons for integrating these technologies are to improve security and harden the system against bugs in the hypervisor that might be used as an attack vector aimed toward the host or to another virtualized guest.
+ </div><div class="para">
+ This chapter describes how sVirt integrates with virtualization technologies in Fedora.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm97033904">Non-virtualized environments</h5>
+ In a non-virtualized environment, hosts are separated from each other physically and each host has a self-contained environment, consisting of services such as a web server, or a DNS server. These services communicate directly to their own user space, host kernel and physical host, offering their services directly to the network. The following image represents a non-virtualized environment:
+ </div><div class="mediaobject"><img src="./images/before_virtualization.png" /></div><div class="formalpara"><h5 class="formalpara" id="idm114410528">Virtualized environments</h5>
+ In a virtualized environment, several operating systems can run on a single host kernel and physical host. The following image represents a virtualized environment:
+ </div><div class="mediaobject"><img src="./images/after_virtualization.png" /></div><div class="section" id="idm121820688"><div class="titlepage"><div><div><h2 class="title" id="idm121820688">19.1. Security and Virtualization</h2></div></div></div><div class="para">
+ When services are not virtualized, machines are physically separated. Any exploit is usually contained to the affected machine, with the obvious exception of network attacks. When services are grouped together in a virtualized environment, extra vulnerabilities emerge in the system. If there is a security flaw in the hypervisor that can be exploited by a guest instance, this guest may be able to not only attack the host, but also other guests running on that host. These attacks can extend beyond the guest instance and could expose other guests to attack.
+ </div><div class="para">
+ sVirt is an effort to isolate guests and limit their ability to launch further attacks if exploited. This is demonstrated in the following image, where an attack can not break out of the virtualized guest and extend to another guest instance:
+ </div><div class="mediaobject"><img src="./images/selinux_uuid_block.png" /></div><div class="para">
+ SELinux introduces a pluggable security framework for virtualized instances in its implementation of Mandatory Access Control (MAC). The sVirt framework allows guests and their resources to be uniquely labeled. Once labeled, rules can be applied which can reject access between different guests.
+ </div></div><div class="section" id="idm98075168"><div class="titlepage"><div><div><h2 class="title" id="idm98075168">19.2. sVirt labeling</h2></div></div></div><div class="para">
+ Like other services under the protection of SELinux, sVirt uses process-based mechanisms and restrictions to provide an extra layer of security over guest instances. Under typical use, you should not even notice that sVirt is working in the background. This section describes the labeling features of sVirt.
+ </div><div class="para">
+ As shown in the following output, when using sVirt, each virtualized guest process is labeled and runs with a dynamically generated level. Each process is isolated from other VMs with different levels:
+ </div><pre class="screen">
+# ps -eZ | grep qemu
+
+system_u:system_r:svirt_t:s0:c87,c520 27950 ? 00:00:17 qemu-kvm
+</pre><div class="para">
+ The actual disk images are automatically labeled to match the processes, as shown in the following output:
+ </div><pre class="screen">
+# ls -lZ /var/lib/libvirt/images/*
+
+ system_u:object_r:svirt_image_t:s0:c87,c520 image1
+</pre><div class="para">
+ The following table outlines the different labels that can be assigned when using sVirt:
+ </div><div class="table"><h6>Table 19.1. sVirt labels</h6><div class="table-contents"><table summary="sVirt labels" border="1"><colgroup><col align="left" class="c1" width="50%" /><col align="left" class="c2" width="50%" /></colgroup><thead><tr><th class="" align="left">
+ Type/Description
+ </th><th class="" align="left">
+ SELinux Context
+ </th></tr></thead><tbody><tr><td class="" align="left">
+ Virtualized guest processes. MCS1 is a random MCS field. Approximately 500,000 labels are supported.
+ </td><td class="" align="left">
+ system_u:system_r:svirt_t:MCS1
+ </td></tr><tr><td class="" align="left">
+ Virtualized guest images. Only <span class="emphasis"><em>svirt_t</em></span> processes with the same MCS fields can read/write these images.
+ </td><td class="" align="left">
+ system_u:object_r:svirt_image_t:MCS1
+ </td></tr><tr><td class="" align="left">
+ Virtualized guest shared read/write content. All <span class="emphasis"><em>svirt_t</em></span> processes can write to the svirt_image_t:s0 files.
+ </td><td class="" align="left">
+ system_u:object_r:svirt_image_t:s0
+ </td></tr><tr><td class="" align="left">
+ Virtualized guest shared read only content. All svirt_t processes can read these files/devices.
+ </td><td class="" align="left">
+ system_u:object_r:svirt_content_t:s0
+ </td></tr><tr><td class="" align="left">
+ Virtualized guest images. Default label for when an image exits. No <span class="emphasis"><em>svirt_t</em></span> virtual processes can read files/devices with this label.
+ </td><td class="" align="left">
+ system_u:object_r:virt_content_t:s0
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ It is also possible to perform static labeling when using sVirt. Static labels allow the administrator to select a specific label, including the MCS/MLS field, for a virtualized guest. Administrators who run statically-labeled virtualized guests are responsible for setting the correct label on the image files. The virtualized guest will always be started with that label, and the sVirt system will never modify the label of a statically-labeled virtual machine's content. This allows the sVirt component to run in an MLS environment. You can also run multiple virtualized guests with different sensitivity levels on a system, depending on your requirements.
+ </div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_Guide-KVM_live_migration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 20. KVM live migration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#Live_migration_requirements">20.1. Live migration requirements</a></span></dt><dt><span class="section"><a href="#Live_migration_and_RHEL_compatibility">20.2. Live migration and Fedora version compatibility </a></span></dt><dt><span class="section"><a href="#shared-storage-nfs-migration">20.3. Shared storage example: NFS for a simple migration</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh">20.4. Live KVM migration with virsh</a></span></dt><dd><dl><dt><span class="section"><a href="#add-notes">20.4.1. Additonal tips for migration with virsh </a></span></dt><dt><span class="section"><a href="#virsh-migration-a
rguements">20.4.2. Additional options for the virsh migrate command</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager">20.5. 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 describes the process of moving a guest from one host to another. This is possible because guests are running in a virtualized environment instead of directly on the hardware. Migration is useful for:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Load balancing - guests can be moved to hosts with lower usage when their host becomes overloaded, or another host is under-utilized.
+ </div></li><li class="listitem"><div class="para">
+ Hardware independence - when we need to upgrade, add, or remove hardware devices on the host, we can safely relocate guests to other hosts. This means that guests do not experience any downtime for hardware improvements.
+ </div></li><li class="listitem"><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 class="listitem"><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">
+ Migration works by sending the state of the guest's memory and any virtualized devices to a destination host. It is recommended to use shared, networked storage to store guest images to be migrated. It is also recommended to libvirt-managed storage pools for shared storage when migrating virtual machines.
+ </div><div class="para">
+ Migrations can be performed live or not.
+ </div><div class="para">
+ In a live migration, the guest continues to run on the source host while its memory pages are transferred, in order, to the destination host. During migration, KVM monitors the source for any changes in pages it has already transferred, and begins to transfer these changes when all of the initial pages have been transferred. KVM also estimates transfer speed during migration, so when the remaining amount of data to transfer will take a certain configurable period of time (10ms by default), KVM suspends the original guest, transfers the remaining data, and resumes the guest on the destination host.
+ </div><div class="para">
+ A migration that is not performed live, suspends the guest, then moves an image of the guest's memory to the destination host. The guest is then resumed on the destination host and the memory the guest used on the source host is freed. The time it takes to complete such a migration depends on network bandwidth and latency. If the network is experiencing heavy use or low bandwidth, the migration will take much longer.
+ </div><div class="para">
+ If the original guest modifies pages faster than KVM can transfer them to the destination host, offline migration must be used, as live migration would never complete.
+ </div><div class="section" id="Live_migration_requirements"><div class="titlepage"><div><div><h2 class="title">20.1. Live migration requirements</h2></div></div></div><div class="para">
+ Migrating guests requires the following:
+ </div><div class="itemizedlist" id="item-Virtualization-Live_migration_requirements-Migration_requirements"><h6>Migration requirements</h6><ul><li class="listitem"><div class="para">
+ A guest installed on shared storage using one of the following protocols:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Fibre Channel-based LUNs
+ </div></li><li class="listitem"><div class="para">
+ iSCSI
+ </div></li><li class="listitem"><div class="para">
+ FCoE
+ </div></li><li class="listitem"><div class="para">
+ NFS
+ </div></li><li class="listitem"><div class="para">
+ GFS2
+ </div></li><li class="listitem"><div class="para">
+ SCSI RDMA protocols (SCSI RCP): the block export protocol used in Infiniband and 10GbE iWARP adapters
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Both systems must have the appropriate TCP/IP ports open.
+ </div></li><li class="listitem"><div class="para">
+ A separate system exporting the shared storage medium. Storage should not reside on either of the two hosts being used for migration.
+ </div></li><li class="listitem"><div class="para">
+ Shared storage must mount at the same location on source and destination systems. The mounted directory names must be identical. Although it is possible to keep the images using different paths, it is not recommended. Note that, if you are intending to use virt-manager to perform the migration, the path names must be identical. If however you intend to use virsh to perform the migration, different network configurations and mount directories can be used with the help of --xml option or pre-hooks when doing migrations. Even with out shared storage, migration can still succeed with the command <code class="command">--copy-storage-all</code>. For more information on <code class="command">prehooks</code>, refer to <a href="http://www.libvirt.org/hooks.html"> libvirt.org</a>, and for more information on the XML option, see the virsh manual.
+ </div></li><li class="listitem"><div class="para">
+ When migration is attempted on an existing guest in a public bridge+tap network, the source and destination hosts must be located in the same network. Otherwise, the guest network will not operate after migration.
+ </div></li></ul></div><div class="para">
+ Make sure that the <code class="filename">libvirtd</code> service is enabled (<code class="command"># chkconfig libvirtd on</code>) and running (<code class="command"># service libvirtd start</code>). It is also important to note that the ability to migrate effectively is dependent on the parameter settings in the <code class="filename">/etc/libvirt/libvirtd.conf</code> configuration file.
+ </div><div class="procedure" id="change-libvirt-config"><h6>Procedure 20.1. Configuring libvirtd.conf</h6><ol class="1"><li class="step"><div class="para">
+ Opening the <code class="filename">libvirtd.conf</code> requires running the command as root:
+ </div><pre class="screen"># vim /etc/libvirt/libvirtd.conf</pre></li><li class="step"><div class="para">
+ Change the parameters as needed and save the file.
+ </div></li><li class="step"><div class="para">
+ Restart the <code class="filename">libvirtd</code> service:
+ </div><pre class="screen"># service libvirtd restart</pre></li></ol></div></div><div class="section" id="Live_migration_and_RHEL_compatibility"><div class="titlepage"><div><div><h2 class="title">20.2. Live migration and Fedora version compatibility </h2></div></div></div><div class="para">
+ Live Migration should only be performed in cases where the guest virtual machine and the host physical machine are running the same version of Fedora. Should you perform a live migration using different versions be forwarned that the migration may fail.
+ </div><div class="para">
+ <span class="bold bold"><strong>Issues with the migration protocol</strong></span> — If backward migration ends with "unknown section error", repeating the migration process can repair the issue as it may be a transient error. If not, please report the problem.
+ </div><div class="formalpara" id="form-Virtualization-Live_migration_requirements-Configuring_network_storage"><h5 class="formalpara">Configuring network storage</h5>
+ Configure shared storage and install a guest on the shared storage.
+ </div><div class="para">
+ Alternatively, use the NFS example in <a class="xref" href="#shared-storage-nfs-migration">Section 20.3, “Shared storage example: NFS for a simple migration”</a>
+ </div></div><div class="section" id="shared-storage-nfs-migration"><div class="titlepage"><div><div><h2 class="title">20.3. Shared storage example: NFS for a simple migration</h2></div></div></div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ This example uses NFS to share guest images with other KVM hosts. Although not practical for large installations, it is presented to demonstrate migration techniques only. Do not use this example for migrating or running more than a few guests.
+ </div><div class="para">
+ iSCSI storage is a better choice for large deployments. Refer to <a class="xref" href="#sect-Virtualization-Storage_Pools-Creating-iSCSI">Section 27.1.5, “iSCSI-based storage pools”</a> for configuration details.
+ </div></div></div><div class="para">
+ Also note, that the instructions provided herin are not meant to replace the detailed instructions found in <em class="citetitle">Red Hat Linux Storage Administration Guide</em>. Refer to this guide for information on configuring NFS, opening IP tables, and configuring the firewall.
+ </div><div class="para">
+ Make sure that NFS filelocking is not used as it is not supported in KVM.
+ </div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Export your libvirt image directory</strong></p><div class="para">
+ Migration requires storage to reside on a system that is separate to the migration target systems. On this separate system, export the storage by adding 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>*.example.com</code></em>(rw,no_root_squash,sync)</pre><div class="para">
+ Change the hostname parameter as required for your environment.
+ </div></li><li class="step"><p class="title"><strong>Start NFS</strong></p><ol class="a"><li class="step"><div class="para">
+ Install the NFS packages if they are not yet installed:
+ </div><pre class="screen"># yum install nfs</pre></li><li class="step"><div class="para">
+ Make sure that the ports for NFS in <code class="command">iptables</code> (2049, for example) are opened and add NFS to the <code class="filename">/etc/hosts.allow</code> file.
+ </div></li><li class="step"><div class="para">
+ Start the NFS service:
+ </div><pre class="screen"># service nfs start</pre></li></ol></li><li class="step"><p class="title"><strong>Mount the shared storage on the destination</strong></p><div class="para">
+ On the migration destination system, mount the <code class="filename">/var/lib/libvirt/images</code> directory:
+ </div><pre class="screen"># mount <em class="parameter"><code>storage_host</code></em>:/var/lib/libvirt/images /var/lib/libvirt/images
+</pre><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Whichever directory is chosen for the guests must be exactly the same on host and guest. This applies to all types of shared storage. The directory must be the same or the migration with virt-manager will fail.
+ </div></div></div></li></ol></div></div><div class="section" id="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh"><div class="titlepage"><div><div><h2 class="title">20.4. 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">
+ Note that the <em class="replaceable"><code>--live</code></em> option may be eliminated when live migration is not desired. Additional options are listed in <a class="xref" href="#virsh-migration-arguements">Section 20.4.2, “Additional options for the virsh migrate command”</a>.
+ </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 connection URL of the destination host. 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="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The <em class="parameter"><code>DestinationURL</code></em> parameter for normal migration and peer2peer migration has different semantics:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ normal migration: the <em class="parameter"><code>DestinationURL</code></em> is the URL of the target host as seen from the source guest.
+ </div></li><li class="listitem"><div class="para">
+ peer2peer migration: <em class="parameter"><code>DestinationURL</code></em> is the URL of the target host as seen from the source host.
+ </div></li></ul></div></div></div><div class="para">
+ Once the command is entered, you will be prompted for the root password of the destination system.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ An entry for the destination host, in the <code class="filename">/etc/hosts</code> file on the source server is required for migration to succeed. Enter the IP address and hostname for the destination host in this file as shown in the following example, substituting your destination host's IP address and hostname:
+<pre class="screen">
+10.0.0.20 host2.example.com
+</pre>
+ </div></div></div><div class="formalpara" id="form-Virtualization-Live_KVM_migration_with_virsh-Example_live_migration_with_virsh"><h5 class="formalpara">Example: live migration with virsh</h5>
+ This example migrates from <code class="systemitem">host1.example.com</code> to <code class="systemitem">host2.example.com</code>. Change the host names for your environment. This example migrates a virtual machine named <code class="filename">guest1-F19</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="#item-Virtualization-Live_migration_requirements-Migration_requirements">Migration requirements</a>).
+ </div><div class="procedure"><ol class="1"><li class="step" id="step-Virtualization_Administration_Guide-Live_KVM_migration_with_virsh-Verify_the_guest_is_running"><p class="title"><strong>Verify the guest is running</strong></p><div class="para">
+ From the source system, <code class="systemitem">host1.example.com</code>, verify <code class="systemitem">guest1-F19</code> is running:
+ </div><pre class="screen">[root at host1 ~]# virsh list
+Id Name State
+----------------------------------
+ 10 guest1-F19 running
+</pre></li><li class="step" id="step-Virtualization_Administration_Guide-Live_KVM_migration_with_virsh-Migrate_the_guest"><p class="title"><strong>Migrate the guest</strong></p><div class="para">
+ Execute the following command to live migrate the guest to the destination, <code class="systemitem">host2.example.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>guest1-F19 qemu+ssh://host2.example.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 class="step" id="step-Virtualization_Administration_Guide-Live_KVM_migration_with_virsh-Wait"><p class="title"><strong>Wait</strong></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 class="step" id="step-Virtualization_Administration_Guide-Live_KVM_migration_with_virsh-Verify_the_guest_has_arrived_at_the_destination_host"><p class="title"><strong>Verify the guest has arrived at the destination host</strong></p><div class="para">
+ From the destination system, <code class="systemitem">host2.example.com</code>, verify <code class="systemitem">guest1-F19</code> is running:
+ </div><pre class="screen">[root at host2 ~]# virsh list
+Id Name State
+----------------------------------
+ 10 guest1-F19 running
+</pre></li></ol></div><div class="para">
+ The live migration is now complete.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ libvirt supports a variety of networking methods including TLS/SSL, UNIX sockets, SSH, and unencrypted TCP. Refer to <a class="xref" href="#chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests">Chapter 21, <em>Remote management of guests</em></a> for more information on using other methods.
+ </div></div></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Non-running guests cannot be migrated with the <code class="command">virsh migrate</code> command. To migrate a non-running guest, the following script should be used:
+<pre class="screen">
+virsh dumpxml Guest1 > Guest1.xml
+virsh -c qemu+ssh://<target-system-FQDN> define Guest1.xml
+virsh undefine Guest1
+</pre>
+ </div></div></div><div class="section" id="add-notes"><div class="titlepage"><div><div><h3 class="title">20.4.1. Additonal tips for migration with virsh </h3></div></div></div><div class="para">
+ It is possible to perform multiple, concurrent live migrations where each migration runs in a separate command shell. However, this should be done with caution and should involve careful calculations as each migration instance uses one MAX_CLIENT from each side (source and target). As the default setting is 20, there is enough to run 10 instances without changing the settings. Should you need to change the settings, refer to the procedure <a class="xref" href="#change-libvirt-config">Procedure 20.1, “Configuring libvirtd.conf”</a>.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Open the libvirtd.conf file as described in <a class="xref" href="#change-libvirt-config">Procedure 20.1, “Configuring libvirtd.conf”</a>.
+ </div></li><li class="step"><div class="para">
+ Look for the Processing controls section.
+ </div><pre class="screen">
+#################################################################
+#
+# Processing controls
+#
+
+# The maximum number of concurrent client connections to allow
+# over all sockets combined.
+#max_clients = 20
+
+
+# The minimum limit sets the number of workers to start up
+# initially. If the number of active clients exceeds this,
+# then more threads are spawned, upto max_workers limit.
+# Typically you'd want max_workers to equal maximum number
+# of clients allowed
+#min_workers = 5
+#max_workers = 20
+
+
+# The number of priority workers. If all workers from above
+# pool will stuck, some calls marked as high priority
+# (notably domainDestroy) can be executed in this pool.
+#prio_workers = 5
+
+# Total global limit on concurrent RPC calls. Should be
+# at least as large as max_workers. Beyond this, RPC requests
+# will be read into memory and queued. This directly impact
+# memory usage, currently each request requires 256 KB of
+# memory. So by default upto 5 MB of memory is used
+#
+# XXX this isn't actually enforced yet, only the per-client
+# limit is used so far
+#max_requests = 20
+
+# Limit on concurrent requests from a single client
+# connection. To avoid one client monopolizing the server
+# this should be a small fraction of the global max_requests
+# and max_workers parameter
+#max_client_requests = 5
+
+#################################################################
+</pre></li><li class="step"><div class="para">
+ Change the <em class="parameter"><code>max_clients</code></em> and <em class="parameter"><code>max_workers</code></em> parameters settings. It is recommended that the number be the same in both parameters. The <em class="parameter"><code>max_clients</code></em> will use 2 clients per migration (one per side) and <em class="parameter"><code>max_workers</code></em> will use 1 worker on the source and 0 workers on the destination during the perform phase and 1 worker on the destination during the finish phase.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The <em class="parameter"><code>max_clients</code></em> and <em class="parameter"><code>max_workers</code></em> parameters settings are effected by all guest connections to the libvirtd service. This means that any user that is using the same guest and is performing a migration at the same time will also beholden to the limits set in the the <em class="parameter"><code>max_clients</code></em> and <em class="parameter"><code>max_workers</code></em> parameters settings. This is why the maximum value needs to be considered carefully before performing a concurrent live migration.
+ </div></div></div></li><li class="step"><div class="para">
+ Save the file and restart the service.
+ </div></li></ol></div></div><div class="section" id="virsh-migration-arguements"><div class="titlepage"><div><div><h3 class="title">20.4.2. Additional options for the virsh migrate command</h3></div></div></div><div class="para">
+ In addition to <em class="replaceable"><code>--live</code></em>, virsh migrate accepts the following options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ --direct - used for direct migration
+ </div></li><li class="listitem"><div class="para">
+ --p2p - used for peer-2-peer migration
+ </div></li><li class="listitem"><div class="para">
+ --tunnelled - used for tunnelled migration
+ </div></li><li class="listitem"><div class="para">
+ --persistent - leaves the domain persistent on destination host
+ </div></li><li class="listitem"><div class="para">
+ --undefinesource - undefines the domain on the source host
+ </div></li><li class="listitem"><div class="para">
+ --suspend - leaves the domain paused on the destination host
+ </div></li><li class="listitem"><div class="para">
+ --copy-storage-all - indicates migration with non-shared storage with full disk copy
+ </div></li><li class="listitem"><div class="para">
+ --copy-storage-inc - indicates migration with non-shared storage with incremental copy (same base image shared between source and destination). In both cases the disk images have to exist on the destination host, the --copy-storage-.options only tell libvirt to transfer data from the images on source host to the images found at the same place on the destination host
+ </div></li><li class="listitem"><div class="para">
+ --change-protection - enforces that no incompatible configuration changes will be made to the domain while the migration is underway; this flag is implicitly enabled when supported by the hypervisor, but can be explicitly used to reject the migration if the hypervisor lacks change protection support.
+ </div></li><li class="listitem"><div class="para">
+ --unsafe - forces the migration to occur, ignoring all safety procedures.
+ </div></li><li class="listitem"><div class="para">
+ --verbose displays the progress of migration as it is occurring
+ </div></li><li class="listitem"><div class="para">
+ migrateuri - the migration URI which is usually omitted.
+ </div></li><li class="listitem"><div class="para">
+ --timeout seconds - forces a guest to suspend when the live migration counter exceeds N seconds. It can only be used with a live migration. Once the timeout is initiated, the migration continues on the suspended guest.
+ </div></li><li class="listitem"><div class="para">
+ dname - is used for renaming the domain to new name during migration, which also usually can be omitted
+ </div></li><li class="listitem"><div class="para">
+ s
+ </div></li><li class="listitem"><div class="para">
+ --xml file can be used to supply an alternative XML file for use on the destination to supply a larger set of changes to any host-specific portions of the domain XML, such as accounting for naming differences between source and destination in accessing underlying storage. This option is usually omitted.
+ </div></li></ul></div><div class="para">
+ Refer to the virsh man page for more information.
+ </div></div></div><div class="section" id="sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager"><div class="titlepage"><div><div><h2 class="title">20.5. Migrating with virt-manager</h2></div></div></div><div class="para">
+ This section covers migrating a KVM guest with <code class="command">virt-manager</code> from one host to another.
+ </div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Open virt-manager</strong></p><div class="para">
+ Open <code class="command">virt-manager</code>. Choose <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>Virtual Machine Manager</strong></span> from the main menu bar to launch <code class="command">virt-manager</code>.
+ </div><div class="figure" id="launch-virt-man-mig-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic1-virt-mgr-guests.png" width="444" alt="Virt-Manager main menu" /></div></div><h6>Figure 20.1. Virt-Manager main menu</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Connect to the target host</strong></p><div class="para">
+ Connect to the target host by clicking on the <span class="guimenu"><strong>File</strong></span> menu, then click <span class="guimenuitem"><strong>Add Connection</strong></span>.
+ <div class="figure" id="add-conn-mig-screen-step1"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic2-add-connection-pull-down.png" width="444" alt="Open Add Connection window" /></div></div><h6>Figure 20.2. Open Add Connection window</h6></div><br class="figure-break" />
+
+ </div></li><li class="step"><p class="title"><strong>Add connection</strong></p><div class="para">
+ The <span class="guilabel"><strong>Add Connection</strong></span> window appears.
+ </div><div class="figure" id="add-conn-mig-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic3-Add-Connection.png" alt="Adding a connection to the target host" /></div></div><h6>Figure 20.3. Adding a connection to the target host</h6></div><br class="figure-break" /><div class="para">
+ Enter the following details:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Hypervisor</strong></span>: Select <span class="guimenuitem"><strong>QEMU/KVM</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Method</strong></span>: Select the connection method.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Username</strong></span>: Enter the username for the remote host.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Hostname</strong></span>: Enter the hostname for the remote host.
+ </div></li></ul></div><div class="para">
+ Click the <span class="guibutton"><strong>Connect</strong></span> button. An SSH connection is used in this example, so the specified user's password must be entered in the next step.
+ </div><div class="figure" id="pass-ssh-mig-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic4-OpenSSH.png" alt="Enter password" /></div></div><h6>Figure 20.4. Enter password</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Migrate guest</strong></p><div class="para">
+ Right-click on the host to be migrated (<span class="bold bold"><strong>guest1-F19</strong></span> in this example) and click <span class="guimenuitem"><strong>Migrate</strong></span>.
+ </div><div class="figure" id="choose-host-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic5-guest-select-migrate.png" width="444" alt="Choosing the host to migrate" /></div></div><h6>Figure 20.5. Choosing the host to migrate</h6></div><br class="figure-break" /><div class="para">
+ Select the host you wish to migrate to and click <span class="guimenuitem"><strong>Migrate</strong></span>.
+ </div><div class="figure" id="mig-last-step-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic6-final-before-migrate.png" alt="Migrating the host" /></div></div><h6>Figure 20.6. Migrating the host</h6></div><br class="figure-break" /><div class="para">
+ A progress window will appear.
+ </div><div class="figure" id="mig-status-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic7-Migrating-guest1-rhel6-64.png" alt="Progress window" /></div></div><h6>Figure 20.7. Progress window</h6></div><br class="figure-break" /><div class="para">
+ <code class="command">virt-manager</code> now displays the newly migrated guest.
+ </div><div class="figure" id="mig-results-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic8-migrated.png" width="444" alt="Migrated guest status" /></div></div><h6>Figure 20.8. Migrated guest status</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>View the storage details for the host</strong></p><div class="para">
+ In the <span class="guimenu"><strong>Edit</strong></span> menu, click <span class="guimenuitem"><strong>Connection Details</strong></span>, the Connection Details window appears.
+ </div><div class="para">
+ Click the <span class="guibutton"><strong>Storage</strong></span> tab. The iSCSI target details for this host is shown.
+ </div><div class="figure" id="host-details-screenshot"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-virtlab22-Host-Details.png" width="444" alt="Storage details" /></div></div><h6>Figure 20.9. Storage details</h6></div><br class="figure-break" /><div class="para">
+ This host was defined by the following XML configuration:
+ </div><pre class="screen">
+<pool type='iscsi'>
+ <name>iscsirhel6guest</name>
+ <source>
+ <host name='virtlab22.example.com.'/>
+ <device path='iqn.2001-05.com.iscsivendor:0-8a0906-fbab74a06-a700000017a4cc89-rhevh'/>
+ </source>
+ <target>
+ <path>/dev/disk/by-path</path>
+ </target>
+</pool>
+</pre></li></ol></div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 21. Remote management of guests</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_with_SSH">21.1. Remote management with SSH</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL">21.2. Remote management over TLS and SSL</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes">21.3. Transport modes</a></span></dt></dl></div><div class="para">
+ This section explains how to remotely manage your guests using <code class="command">ssh</code> or TLS and SSL. More information on SSH can be found in the <em class="citetitle">Fedora Deployment Guide</em>
+ </div><div class="section" id="sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_with_SSH"><div class="titlepage"><div><div><h2 class="title">21.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 is tunneled over <span class="application"><strong>SSH</strong></span>.
+ </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><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ you require root log in access to the remote machine for managing virtual machines,
+ </div></li><li class="listitem"><div class="para">
+ the initial connection setup process may be slow,
+ </div></li><li class="listitem"><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 class="listitem"><div class="para">
+ ssh does not scale well with larger numbers of remote machines.
+ </div></li></ul></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Fedora enables remote management of large numbers of virtual machines. Refer to the oVirt documentation for further details.
+ </div></div></div><div class="para">
+ The following packages are required for ssh access:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="package">openssh</span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">openssh-askpass</span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">openssh-clients</span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">openssh-server</span>
+ </div></li></ul></div><div class="formalpara" id="form-Virtualization-Remote_management_with_SSH-Configuring_SSH_access_for_virt_manager"><h5 class="formalpara">Configuring password less or password managed <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. If you have SSH keys set up and copied to the other systems you can skip this procedure.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ SSH keys are user dependent and may only be used by their owners. A key's owner is the one who generated it. Keys may not be shared.
+ </div><div class="para">
+ <code class="command">virt-manager</code> must be run by the user who owns the keys to connect to the remote host. That means, if the remote systems are managed by a non-root user <code class="command">virt-manager</code> must be run in unprivileged mode. If the remote systems are managed by the local root user then the SSH keys must be owned and created by root.
+ </div><div class="para">
+ You cannot manage the local host as an unprivileged user with <code class="command">virt-manager</code>.
+ </div></div></div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Optional: Changing user</strong></p><div class="para">
+ Change user, if required. This example uses the local root user for remotely managing the other hosts and the local host.
+ </div><pre class="screen">$<code class="command"> su -</code></pre></li><li class="step"><p class="title"><strong>Generating the SSH key pair</strong></p><div class="para">
+ Generate a public key pair on the machine <code class="command">virt-manager</code> is used. This example uses the default key location, in the <code class="filename">~/.ssh/</code> directory.
+ </div><pre class="screen"># <code class="command">ssh-keygen -t rsa</code></pre></li><li class="step"><p class="title"><strong>Copying the keys to the remote hosts</strong></p><div class="para">
+ Remote login without a password, or with a passphrase, requires an SSH key to be distributed to the systems being managed. Use the <code class="command">ssh-copy-id</code> command to copy the key to root user at the system address provided (in the example, <em class="parameter"><code>root at host2.example.com</code></em>).
+ </div><pre class="screen"># <code class="command">ssh-copy-id -i ~/.ssh/id_rsa.pub root at host2.example.com</code>
+root at host2.example.com's password:
+</pre><div class="para">
+ Now try logging into the machine, with the <code class="command">ssh root at host2.example.com</code> command and check in the <code class="filename">.ssh/authorized_keys</code> file to make sure unexpected keys have not been added.
+ </div><div class="para">
+ Repeat for other systems, as required.
+ </div></li><li class="step"><p class="title"><strong>Optional: Add the passphrase to the ssh-agent</strong></p><div class="para">
+ The instructions below describe how to add a passphrase to an existing ssh-agent. It will fail to run if the ssh-agent is not running. To avoid errors or conflicts make sure that your SSH parameters are set correctly. Refer to the <em class="citetitle">Fedora Deployment Guide</em> for more information.
+ </div><div class="para">
+ Add the passphrase for the SSH key to the <code class="command">ssh-agent</code>, if required. On the local host, use the following command to add the passphrase (if there was one) to enable password-less login.
+ </div><pre class="screen"># <code class="command">ssh-add ~/.ssh/id_rsa.pub</code></pre><div class="para">
+ The SSH key is added to the remote system.
+ </div></li></ol></div><div class="formalpara" id="form-Virtualization-Remote_management_with_SSH-The_libvirt_daemon_libvirtd"><h5 class="formalpara">The <code class="command">libvirt</code> daemon (<code class="systemitem">libvirtd</code>)</h5>
+ The <code class="systemitem">libvirt</code> daemon provides an interface for managing virtual machines. You must have the <code class="systemitem">libvirtd</code> daemon installed and running on every remote host that needs managing.
+ </div><pre class="screen">$ <code class="command">ssh root@<em class="replaceable"><code>somehost</code></em></code>
+<code class="command"># chkconfig libvirtd on</code>
+<code class="command"># service libvirtd start</code></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 class="formalpara" id="form-Virtualization-Remote_management_with_SSH-Accessing_remote_hosts_with_virt_manager"><h5 class="formalpara">Accessing remote hosts with virt-manager</h5>
+ Remote hosts can be managed with the virt-manager GUI tool. SSH keys must belong to the user executing virt-manager for password-less login to work.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Start virt-manager.
+ </div></li><li class="step"><div class="para">
+ Open the <span class="guimenuitem"><strong>File</strong></span>-><span class="guimenuitem"><strong>Add Connection</strong></span> menu.
+ </div><div class="figure" id="add-connection"><div class="figure-contents"><div class="mediaobject"><img src="images/Virt-Manager-Add-Connection.png" alt="Add connection menu" /></div></div><h6>Figure 21.1. Add connection menu</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Use the drop down menu to select hypervisor type, and click the <span class="guimenuitem"><strong>Connect to remote host</strong></span> check box to open the Connection <span class="guimenuitem"><strong>Method</strong></span> (in this case Remote tunnel over SSH), and enter the desired <span class="guimenuitem"><strong>User name</strong></span> and <span class="guimenuitem"><strong>Hostname</strong></span>, then click <span class="guimenuitem"><strong>Connect</strong></span>.
+ </div></li></ol></div></div><div class="section" id="sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL"><div class="titlepage"><div><div><h2 class="title">21.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="#sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_with_SSH">Section 21.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. The procedures that follow provide instructions on creating and deploying authentication certificates for TLS and SSL management.
+ </div><div class="procedure" id="createCA-key"><h6>Procedure 21.1. Creating a certificate authority (CA) key for TLS management</h6><ol class="1"><li class="step"><div class="para">
+ Before you begin, confirm that <code class="command">certtool</code> is installed. If not:
+ </div><pre class="screen">#<code class="command"> yum install certtool</code></pre></li><li class="step"><div class="para">
+ Generate a private key, using the following command:
+ </div><pre class="screen"># <code class="command">certtool --generate-privkey > cakey.pem</code></pre></li><li class="step"><div class="para">
+ Once the key generates, the next step is to create a signature file so the key can be self-signed. To do this, create a file with signature details and name it <code class="filename">ca.info</code>. This file should contain the following:
+ </div><pre class="screen"># <code class="command">vim ca.info</code></pre><pre class="screen">
+cn = Name of your organization
+ca
+cert_signing_key
+</pre></li><li class="step"><div class="para">
+ Generate the self-signed key with the following command:
+ </div><pre class="screen"># <code class="command">certtool --generate-self-signed --load-privkey cakey.perm --template ca.info --outfile cacert.pem</code></pre><div class="para">
+ Once the file generates, the ca.info file may be deleted using the <code class="command">rm</code> command. The file that results from the generation process is named <code class="filename">cacert.pem</code>. This file is the public key (certificate). The loaded file <code class="filename">cakey.pem</code> is the private key. This file should not be kept in a shared space. Keep this key private.
+ </div></li><li class="step"><div class="para">
+ Install the <code class="filename">cacert.pem</code> Certificate Authority Certificate file on all clients and servers in the <code class="filename">/etc/pki/CA/cacert.pem</code> directory to let them know that the certificate issued by your CA can be trusted. To view the contents of this file, run:
+<pre class="screen"># <code class="command">certtool -i --infile cacert.pem</code></pre>
+
+ </div><div class="para">
+ This is all that is required to set up your CA. Keep the CA's private key safe as you will need it in order to issue certificates for your clients and servers.
+ </div></li></ol></div><div class="procedure" id="issue-server-cetificate-ca"><h6>Procedure 21.2. Issuing a server certificate</h6><div class="para">
+ This procedure demonstrates how to issue a certificate with the X.509 CommonName (CN)field set to the hostname of the server. The CN must match the hostname which clients will be using to connect to the server. In this example, clients will be connecting to the server using the URI: <code class="filename">qemu://mycommonname/system</code>, so the CN field should be identical, ie mycommoname.
+ </div><ol class="1"><li class="step"><div class="para">
+ Create a private key for the server.
+ </div><pre class="screen"># <code class="command">certtool --generate-privkey > serverkey.pem</code></pre></li><li class="step"><div class="para">
+ Generate a signature for the CA's private key by first creating a template file called <code class="filename">server.info </code>. Make sure that the CN is set to be the same as the server's hostname:
+ </div><pre class="screen">
+organization = Name of your organization
+cn = mycommonname
+tls_www_server
+encryption_key
+signing_key
+</pre></li><li class="step"><div class="para">
+ Create the certificate with the following command:
+ </div><pre class="screen">
+# <code class="command">certtool --generate-certificate --load-privkey serverkey.pem --load-ca-certificate cacert.pem --load-ca-privkey cakey.pem \ --template server.info --outfile servercert.pem</code></pre></li><li class="step"><div class="para">
+ This results in two files being generated:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ serverkey.pem - The server's private key
+ </div></li><li class="listitem"><div class="para">
+ servercert.pem - The server's public key
+ </div></li></ul></div><div class="para">
+ Make sure to keep the location of the private key secret. To view the contents of the file, perform the following command:
+ </div><pre class="screen">
+# <code class="command">certtool -i -inifile servercert.pem</code></pre><div class="para">
+ When opening this file the <code class="filename">CN=</code> parameter should be the same as the CN that you set earlier. For example, <code class="filename">mycommonname</code>.
+ </div></li><li class="step"><div class="para">
+ Install the two files in the following locations:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">serverkey.pem</code> - the server's private key. Place this file in the following location: <code class="filename">/etc/pki/libvirt/private/serverkey.pem</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">servercert.pem</code> - the server's certificate. Install it in the following location on the server:<code class="filename"> /etc/pki/libvirt/servercert.pem</code>
+ </div></li></ul></div></li></ol></div><div class="procedure" id="pro-issue-client-certs-CA"><h6>Procedure 21.3. Issuing a client certificate</h6><ol class="1"><li class="step"><div class="para">
+ For every client (ie. any program linked with libvirt, such as virt-manager), you need to issue a certificate with the X.509 Distinguished Name (DN) set to a suitable name. This needs to be decided on a corporate level.
+ </div><div class="para">
+ For example purposes the following information will be used:
+ </div><pre class="screen"><em class="replaceable"><code>C=USA,ST=North Carolina,L=Raleigh,O=Fedora,CN=name_of_client</code></em></pre><div class="para">
+ This process is quite similar to <a class="xref" href="#issue-server-cetificate-ca">Procedure 21.2, “Issuing a server certificate”</a>, with the following exceptions noted.
+ </div></li><li class="step"><div class="para">
+ Make a private key with the following command:
+ </div><pre class="screen"># <code class="command">certtool --generate-privkey > clientkey.pem</code></pre></li><li class="step"><div class="para">
+ Generate a signature for the CA's private key by first creating a template file called <code class="filename">client.info </code>. The file should contain the following (fields should be customized to reflect your region/location):
+ </div><pre class="screen">
+country = USA
+state = North Carolina
+locality = Raleigh
+organization = Fedora
+cn = client1
+tls_www_client
+encryption_key
+signing_key
+</pre></li><li class="step"><div class="para">
+ Sign the certificate with the following command:
+ </div><pre class="screen">
+# <code class="command">certtool --generate-certificate --load-privkey clientkey.pem --load-ca-certificate cacert.pem \ --load-ca-privkey cakey.pem --template client.info --outfile clientcert.pem</code></pre></li><li class="step"><div class="para">
+ Install the certificates on the client machine:
+ </div><pre class="screen">
+# <code class="command">cp clientkey.pem /etc/pki/libvirt/private/clientkey.pem</code>
+# <code class="command">cp clientcert.pem /etc/pki/libvirt/clientcert.pem</code></pre></li></ol></div></div><div class="section" id="sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes"><div class="titlepage"><div><div><h2 class="title">21.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" id="form-Virtualization-Transport_modes-Transport_Layer_Security_TLS"><h5 class="formalpara">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" id="form-Virtualization-Transport_modes-UNIX_sockets"><h5 class="formalpara">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" id="form-Virtualization-Transport_modes-SSH"><h5 class="formalpara">SSH</h5>
+ Transported over a 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" id="form-Virtualization-Transport_modes-ext"><h5 class="formalpara">ext</h5>
+ The <em class="parameter"><code>ext</code></em> parameter is used for any external program which can make a connection to the remote machine by means outside the scope of libvirt. This parameter is unsupported.
+ </div><div class="formalpara" id="form-Virtualization-Transport_modes-tcp"><h5 class="formalpara">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" id="form-Virtualization-Transport_modes-Remote_URIs"><h5 class="formalpara">Remote URIs</h5>
+ A Uniform Resource Identifier (URI) is used by <code class="command">virsh</code> and <span class="package">libvirt</span> 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.
+ </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">
+ The transport method or the hostname must be provided to target an external location.
+ </div><div class="itemizedlist" id="item-Virtualization-Transport_modes-Examples_of_remote_management_parameters"><h6>Examples of remote management parameters</h6><ul><li class="listitem"><div class="para">
+ Connect to a remote KVM host named <code class="systemitem">host2</code>, using SSH transport and the SSH username <code class="systemitem">virtuser</code>.
+ </div><pre class="screen"><code class="command">qemu+ssh://virtuser@host2/</code></pre></li><li class="listitem"><div class="para">
+ Connect to a remote KVM hypervisor on the host named <code class="systemitem">host2</code> using TLS.
+ </div><pre class="screen"><code class="command">qemu://host2/</code></pre></li></ul></div><div class="itemizedlist" id="item-Virtualization-Transport_modes-Testing_examples"><h6>Testing examples</h6><ul><li class="listitem"><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"><code class="command">qemu+unix:///system?socket=/opt/libvirt/run/libvirt/libvirt-sock</code></pre></li><li class="listitem"><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"><code class="command">test+tcp://10.1.1.10:5000/default</code></pre></li></ul></div><div class="formalpara" id="form-Virtualization-Transport_modes-Extra_URI_parameters"><h5 class="formalpara">Extra URI parameters</h5>
+ Extra parameters can be appended to remote URIs. The table below <a class="xref" href="#tabl-Virtualization-Transport_modes-Extra_URI_parameters">Table 21.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-Transport_modes-Extra_URI_parameters"><h6>Table 21.1. Extra URI parameters</h6><div class="table-contents"><table summary="Extra URI parameters" border="1"><colgroup><col width="25%" /><col width="25%" /><col width="25%" /><col width="25%" /></colgroup><thead><tr><th class="">
+ Name
+ </th><th class="">
+ Transport mode
+ </th><th class="">
+ Description
+ </th><th class="">
+ Example usage
+ </th></tr></thead><tbody><tr><td class="">
+ name
+ </td><td class="">
+ all modes
+ </td><td class="">
+ 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 class="">
+ name=qemu:///system
+ </td></tr><tr><td class="">
+ command
+ </td><td class="">
+ ssh and ext
+ </td><td class="">
+ The external command. For ext transport this is required. For ssh the default is ssh. The PATH is searched for the command.
+ </td><td class="">
+ command=/opt/openssh/bin/ssh
+ </td></tr><tr><td class="">
+ socket
+ </td><td class="">
+ unix and ssh
+ </td><td class="">
+ 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 class="">
+ socket=/opt/libvirt/run/libvirt/libvirt-sock
+ </td></tr><tr><td class="">
+ netcat
+ </td><td class="">
+ ssh
+ </td><td class="">
+ <div class="para">
+ The <code class="command">netcat</code> command can be used to connect to remote systems. The default netcat parameter uses the <code class="command">nc</code> command. For SSH transport, libvirt constructs an SSH command using the form below:
+ </div>
+ <div class="para">
+ <em class="parameter"><code>command</code></em> -p <em class="parameter"><code>port</code></em> [-l <em class="parameter"><code>username</code></em>] <em class="parameter"><code>hostname</code></em>
+ </div>
+ <div class="para">
+ <em class="parameter"><code>netcat</code></em> -U socket
+ </div>
+ <div class="para">
+ The <em class="parameter"><code>port</code></em>, <em class="parameter"><code>username</code></em> and <em class="parameter"><code>hostname</code></em> parameters can be specified as part of the remote URI. The <em class="parameter"><code>command</code></em>, <em class="parameter"><code>netcat</code></em> and <em class="parameter"><code>socket</code></em> come from other extra parameters.
+ </div>
+
+ </td><td class="">
+ netcat=/opt/netcat/bin/nc
+ </td></tr><tr><td class="">
+ no_verify
+ </td><td class="">
+ tls
+ </td><td class="">
+ 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 class="">
+ no_verify=1
+ </td></tr><tr><td class="">
+ no_tty
+ </td><td class="">
+ ssh
+ </td><td class="">
+ 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 class="">
+ no_tty=1
+ </td></tr></tbody></table></div></div><br class="table-break" /></div></div><div xml:lang="en-US" class="chapter" id="sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 22. 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 a number of system resources, with the net effect of less power, cooling, and investment in server hardware.
+ </div><div class="formalpara" id="form-Virtualization-Overcommitting_with_KVM-Overcommitting_memory"><h5 class="formalpara">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. KVM can allocate more memory for guests than the host has physically available. Overcommitting requires sufficient swap space for all guests and all host processes.
+ </div><div class="para">
+ With KVM, virtual machines are Linux processes. Guests on the KVM hypervisor do not have dedicated blocks of physical RAM assigned to them, instead guests function as Linux processes. The Linux kernel allocates each process memory when the process requests more memory. KVM guests are allocated memory when requested by the guest operating system.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Ensure that the total sum of swap and memory space is greater than or equal to all the memory configured for running guests. A shortage less than this sum can cause a guest to be forcibly shut down.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="idm19285456">Configuring swap for overcommitting memory</h5>
+ 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 the physical RAM of the host.
+ </div><div class="para">
+ Red Hat <a href="http://kbase.redhat.com/faq/docs/DOC-15252">Knowledgebase</a> has an article on safely and efficiently determining the size of the swap partition.
+ </div><div class="para">
+ The swap partition must be large enough to provide virtual memory for all guests and the host system.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The example below is provided as a guide for configuring swap only. The settings listed may not be appropriate for your environment.
+ </div></div></div><div class="example"><h6>Example 22.1. Memory overcommit example</h6><div class="example-contents"><div class="para">
+ ExampleServer1 has 32GB of physical RAM. The system is being configured to run 56 guests, each with 1GB of virtualized memory. The host system itself needs a maximum of 3GB (apart from the guests).
+ </div><div class="para">
+ The total maximum memory consumption is 56GB + 3GB = 59GB. The system's physical RAM is 32GB, which leaves 27GB. Therefore, the minimum amount of swap that the host should have configured is 27GB.
+ </div></div></div><br class="example-break" /><div class="para">
+ It is possible to overcommit memory over ten times the amount of physical RAM in the system. This only works with certain types of guest, for example, desktop virtualization with minimal intensive usage or running several identical guests with KSM. Configuring swap and memory overcommit is not a formula, each environment and setup is different. Your environment must be tested and customized to ensure stability and performance.
+ </div><div class="para">
+ For more information on KSM and overcommitting, refer to <a class="xref" href="#chap-KSM">Chapter 23, <em>KSM</em></a>.
+ </div><div class="formalpara" id="form-Virtualization-Overcommitting_with_KVM-Overcommitting_virtualized_CPUs"><h5 class="formalpara">Overcommitting virtualized CPUs</h5>
+ The KVM hypervisor supports overcommitting virtualized CPUs. Virtualized CPUs can be overcommitted as far as load limits of 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 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 five VCPUs. Overcommitting single VCPU 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 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"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><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></div><div xml:lang="en-US" class="chapter" id="chap-KSM" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 23. KSM</h2></div></div></div><div class="para">
+ The concept of shared memory is common in modern operating systems. For example, when a program is first started it shares all of its memory with the parent program. When either the child or parent program tries to modify this memory, the kernel allocates a new memory region, copies the original contents and allows the program to modify this new region. This is known as copy on write.
+ </div><div class="para">
+ KSM is a new Linux feature which uses this concept in reverse. KSM enables the kernel to examine two or more already running programs and compare their memory. If any memory regions or pages are identical, KSM reduces multiple identical memory pages to a single page. This page is then marked copy on write. If the contents of the page is modified by a guest, a new page is created for that guest.
+ </div><div class="para">
+ This is useful for virtualization with KVM. When a guest is started, it only inherits the memory from the parent <code class="systemitem">qemu-kvm</code> process. Once the guest is running the contents of the guest operating system image can be shared when guests are running the same operating system or applications. KSM only identifies and merges identical pages which does not interfere with the guest or impact the security of the host or the guests. KSM allows KVM to request that these identical guest memory regions be shared.
+ </div><div class="para">
+ KSM provides enhanced memory speed and utilization. With KSM, common process data is stored in cache or in main memory. This reduces cache misses for the KVM guests which can improve performance for some applications and operating systems. Secondly, sharing memory reduces the overall memory usage of guests which allows for higher densities and greater utilization of resources.
+ </div><div class="para">
+ Starting in Fedora 18, KSM is NUMA aware
+ </div><div class="para">
+ Fedora uses two separate methods for controlling KSM:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <code class="systemitem">ksm</code> service starts and stops the KSM kernel thread.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="systemitem">ksmtuned</code> service controls and tunes the <code class="systemitem">ksm</code>, dynamically managing same-page merging. The <code class="systemitem">ksmtuned</code> service starts <code class="systemitem">ksm</code> and stops the <code class="systemitem">ksm</code> service if memory sharing is not necessary. The <code class="systemitem">ksmtuned</code> service must be told with the <em class="parameter"><code>retune</code></em> parameter to run when new guests are created or destroyed.
+ </div></li></ul></div><div class="para">
+ Both of these services are controlled with the standard service management tools.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm109770288">The KSM service</h5>
+ The <code class="systemitem">ksm</code> service is included in the <span class="package">qemu-kvm</span> package. KSM is off by default on Fedora. When using Fedora as a KVM host, however, it is likely turned on by the <code class="systemitem">ksm/ksmtuned</code> services.
+ </div><div class="para">
+ When the <code class="systemitem">ksm</code> service is not started, KSM shares only 2000 pages. This default is low and provides limited memory saving benefits.
+ </div><div class="para">
+ When the <code class="systemitem">ksm</code> service is started, KSM will share up to half of the host system's main memory. Start the <code class="systemitem">ksm</code> service to enable KSM to share more memory.
+ </div><pre class="screen"># service ksm start
+Starting ksm: [ OK ]</pre><div class="para">
+ The <code class="systemitem">ksm</code> service can be added to the default startup sequence. Make the <code class="systemitem">ksm</code> service persistent with the chkconfig command.
+ </div><pre class="screen"># chkconfig ksm on</pre><div class="formalpara"><h5 class="formalpara" id="idm123469232">The KSM tuning service</h5>
+ The <code class="systemitem">ksmtuned</code> service does not have any options. The <code class="systemitem">ksmtuned</code> service loops and adjusts <code class="systemitem">ksm</code>. The <code class="systemitem">ksmtuned</code> service is notified by libvirt when a guest is created or destroyed.
+ </div><pre class="screen"># service ksmtuned start
+Starting ksmtuned: [ OK ]</pre><div class="para">
+ The <code class="systemitem">ksmtuned</code> service can be tuned with the <em class="parameter"><code>retune</code></em> parameter. The <em class="parameter"><code>retune</code></em> parameter instructs <code class="systemitem">ksmtuned</code> to run tuning functions manually.
+ </div><div class="para">
+ The <code class="filename">/etc/ksmtuned.conf</code> file is the configuration file for the <code class="systemitem">ksmtuned</code> service. The file output below is the default <code class="filename">ksmtuned.conf</code> file.
+ </div><pre class="screen"># Configuration file for ksmtuned.
+
+# How long ksmtuned should sleep between tuning adjustments
+# KSM_MONITOR_INTERVAL=60
+
+# Millisecond sleep between ksm scans for 16Gb server.
+# Smaller servers sleep more, bigger sleep less.
+# KSM_SLEEP_MSEC=10
+
+# KSM_NPAGES_BOOST=300
+# KSM_NPAGES_DECAY=-50
+# KSM_NPAGES_MIN=64
+# KSM_NPAGES_MAX=1250
+
+# KSM_THRES_COEF=20
+# KSM_THRES_CONST=2048
+
+# uncomment the following to enable ksmtuned debug information
+# LOGFILE=/var/log/ksmtuned
+# DEBUG=1
+</pre><div class="formalpara"><h5 class="formalpara" id="idm96780224">KSM variables and monitoring</h5>
+ KSM stores monitoring data in the <code class="filename">/sys/kernel/mm/ksm/</code> directory. Files in this directory are updated by the kernel and are an accurate record of KSM usage and statistics.
+ </div><div class="para">
+ The variables in the list below are also configurable variables in the <code class="filename">/etc/ksmtuned.conf</code> file as noted below.
+ </div><div class="variablelist"><h6>The <code class="filename">/sys/kernel/mm/ksm/</code> files</h6><dl class="variablelist"><dt class="varlistentry"><span class="term">full_scans</span></dt><dd><div class="para">
+ Full scans run.
+ </div></dd><dt class="varlistentry"><span class="term">pages_shared</span></dt><dd><div class="para">
+ Total pages shared.
+ </div></dd><dt class="varlistentry"><span class="term">pages_sharing</span></dt><dd><div class="para">
+ Pages presently shared.
+ </div></dd><dt class="varlistentry"><span class="term">pages_to_scan</span></dt><dd><div class="para">
+ Pages not scanned.
+ </div></dd><dt class="varlistentry"><span class="term">pages_unshared</span></dt><dd><div class="para">
+ Pages no longer shared.
+ </div></dd><dt class="varlistentry"><span class="term">pages_volatile</span></dt><dd><div class="para">
+ Number of volatile pages.
+ </div></dd><dt class="varlistentry"><span class="term">run</span></dt><dd><div class="para">
+ Whether the KSM process is running.
+ </div></dd><dt class="varlistentry"><span class="term">sleep_millisecs</span></dt><dd><div class="para">
+ Sleep milliseconds.
+ </div></dd></dl></div><div class="para">
+ KSM tuning activity is stored in the <code class="filename">/var/log/ksmtuned</code> log file if the <em class="parameter"><code>DEBUG=1</code></em> line is added to the <code class="filename">/etc/ksmtuned.conf</code> file. The log file location can be changed with the <em class="parameter"><code>LOGFILE</code></em> parameter. Changing the log file location is not advised and may require special configuration of SELinux settings.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm96883232">Deactivating KSM</h5>
+ KSM has a performance overhead which may be too large for certain environments or host systems.
+ </div><div class="para">
+ KSM can be deactivated by stopping the <code class="systemitem">ksmtuned</code> and the <code class="systemitem">ksm</code> service. Stopping the services deactivates KSM but does not persist after restarting.
+ </div><pre class="screen">
+# service ksmtuned stop
+Stopping ksmtuned: [ OK ]
+# service ksm stop
+Stopping ksm: [ OK ]
+
+</pre><div class="para">
+ Persistently deactivate KSM with the <code class="command">chkconfig</code> command. To turn off the services, run the following commands:
+ </div><pre class="screen"># chkconfig ksm off
+# chkconfig ksmtuned off</pre><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Ensure the swap size is sufficient for the committed RAM even with KSM. KSM reduces the RAM usage of identical or similar guests. Overcommitting guests with KSM without sufficient swap space may be possible but is not recommended because guest memory use can result in pages becoming unshared.
+ </div></div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_GuideAdvanced" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 24. Advanced virtualization administration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#idm82218240">24.1. Control Groups (cgroups)</a></span></dt><dt><span class="section"><a href="#idm118488944">24.2. Hugepage support</a></span></dt></dl></div><div class="para">
+ This chapter covers advanced administration tools for fine tuning and controlling guests and host system resources.
+ </div><div class="section" id="idm82218240"><div class="titlepage"><div><div><h2 class="title" id="idm82218240">24.1. Control Groups (cgroups)</h2></div></div></div><div class="para">
+ Fedora 19 provides a new kernel feature: <em class="firstterm">control groups</em>, which are often referred to as <em class="firstterm">cgroups</em>. Cgroups allow you to allocate resources such as CPU time, system memory, network bandwidth, or combinations of these resources among user-defined groups of tasks (processes) running on a system. You can monitor the cgroups you configure, deny cgroups access to certain resources, and even reconfigure your cgroups dynamically on a running system.
+ </div><div class="para">
+ The cgroup functionality is fully supported by libvirt. By default, libvirt puts each guest into a separate control group for various controllers (such as memory, cpu, blkio, device).
+ </div><div class="para">
+ When a guest is started, it is already in a cgroup. The only configuration that may be required is the setting of policies on the cgroups. Refer to the <em class="citetitle">Fedora Resource Management Guide</em> for more information on cgroups.
+ </div></div><div class="section" id="idm118488944"><div class="titlepage"><div><div><h2 class="title" id="idm118488944">24.2. Hugepage support</h2></div></div></div><div class="formalpara"><h5 class="formalpara" id="idm84376160">Introduction</h5>
+ x86 CPUs usually address memory in 4kB pages, but they are capable of using larger pages known as <span class="bold bold"><strong>huge pages</strong></span>. KVM guests can be deployed with huge page memory support in order to reduce memory consumption and improve performance by reducing CPU cache usage.
+ </div><div class="para">
+ By using huge pages for a KVM guest, less memory is used for page tables and TLB (Translation Lookaside Buffer) misses are reduced, thereby significantly increasing performance, especially for memory-intensive situations.
+ </div><div class="para">
+ <span class="bold bold"><strong>Transparent Hugepage Support</strong></span> is a kernel feature that reduces TLB entries needed for an application. By also allowing all free memory to be used as cache, performance is increased.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm100188272">Using Transparent Hugepage Support</h5>
+ To use Transparent Hugepage Support, no special configuration in the <code class="filename">qemu.conf</code> file is required. Hugepages are used by default if <code class="filename">/sys/kernel/mm/redhat_transparent_hugepage/enabled</code> is set to <span class="bold bold"><strong>always</strong></span>.
+ </div><div class="para">
+ Transparent Hugepage Support does not prevent the use of hugetlbfs. However, when hugetlbfs is not used, KVM will use transparent hugepages instead of the regular 4kB page size.
+ </div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_Guide-Tips_and_tricks" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 25. Miscellaneous administration tasks</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Automatically_starting_guests">25.1. Automatically starting guests</a></span></dt><dt><span class="section"><a href="#sect-mem-dump-off">25.2. Guest memory allocation</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Using_qemu_img">25.3. Using qemu-img</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions">25.4. Verifying virtualization extensions</a></span></dt><dt><span class="section"><a href="#idm71657744">25.5. Setting KVM processor affinities</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_t
ricks-Generating_a_new_unique_MAC_address">25.6. Generating a new unique MAC address</a></span></dt><dt><span class="section"><a href="#idm96083232">25.7. Improving guest response time</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests">25.8. Disable SMART disk monitoring for guests</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server">25.9. Configuring a VNC Server</a></span></dt><dt><span class="section"><a href="#sect-gracefully-shut-down-guests">25.10. Gracefully shutting down guests</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers">25.11. Virtual machine timer management with libvirt</a></span></dt><dt><span class="section"><a href="#sect-perf-mon">25.12. Using PMU to monitor guest performance</a></span></dt><dt><span class="section"><a href="#sect-s3-s4">25.13. Guest virtual
machine power management</a></span></dt><dt><span class="section"><a href="#sect-qemu-ga">25.14. QEMU Guest Agent Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-guest-synch">25.14.1. guest-sync</a></span></dt><dt><span class="section"><a href="#subsect-guest-synch-delimited">25.14.2. guest-sync-delimited</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-limit-redirection">25.15. Setting a limit on device redirection</a></span></dt><dt><span class="section"><a href="#sect-dynamic-vNIC">25.16. Dynamically changing a host or a network bridge that is attached to a virtual NIC</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" id="sect-Virtualization-Tips_and_tricks-Automatically_starting_guests"><div class="titlepage"><div><div><h2 class="title">25.1. Automatically starting guests</h2></div></div></div><div class="para">
+ This section covers how to make 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 class="section" id="sect-mem-dump-off"><div class="titlepage"><div><div><h2 class="title">25.2. Guest memory allocation</h2></div></div></div><div class="para">
+ The following procedure shows how to allocate memory for a guest. This allocation and assignement works only at boot time and any changes to any of the memory values will not take effect until the next reboot.
+ </div><div class="para">
+ Valid memory units include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="parameter"><code>b</code></em> or <em class="parameter"><code>bytes</code></em> for bytes
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>KB</code></em> for kilobytes (10<sup>3</sup> or blocks of 1,000 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>k</code></em> or <em class="parameter"><code>KiB</code></em> for kibibytes (2<sup>10</sup> or blocks of 1024 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>MB</code></em> for megabytes (10<sup>6</sup> or blocks of 1,000,000 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>M</code></em> or <em class="parameter"><code>MiB</code></em> for mebibytes (2<sup>20</sup> or blocks of 1,048,576 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>GB</code></em> for gigabytes (10<sup>9</sup> or blocks of 1,000,000,000 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>G</code></em> or <em class="parameter"><code>GiB</code></em> for gibibytes (2<sup>30</sup> or blocks of 1,073,741,824 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>TB</code></em> for terabytes (10<sup>12</sup> or blocks of 1,000,000,000,000 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>T</code></em> or <em class="parameter"><code>TiB</code></em> for tebibytes (2<sup>40</sup> or blocks of 1,099,511,627,776 bytes)
+ </div></li></ul></div><div class="para">
+ Note that all values will be rounded up to the nearest kibibyte by libvirt, and may be further rounded to the granularity supported by the hypervisor. Some hypervisors also enforce a minimum, such as 4000KiB (or 4000 x 2<sup>10</sup> or 4,096,000 bytes). The units for this value are determined by the optional attribute <em class="parameter"><code>memory unit</code></em>, which defaults to the kibibytes (KiB) as a unit of measure where the value given is multiplied by 2<sup>10</sup> or blocks of 1024 bytes.
+ </div><div class="para">
+ In the cases where the guest crashes the optional attribute <em class="parameter"><code>dumpCore</code></em> can be used to control whether the guest's memory should be included in the generated coredump (<em class="parameter"><code>dumpCore='on'</code></em>) or not included (<em class="parameter"><code>dumpCore='off'</code></em>). Note that the default setting is <em class="parameter"><code>on</code></em> so if the parameter is not set to <em class="parameter"><code>off</code></em>, the guest memory will be included in the coredump file.
+ </div><div class="para">
+ The <em class="parameter"><code>currentMemory</code></em> attribute determines the actual memory allocation for a guest. This value can be less than the maximum allocation, to allow for ballooning up the guests memory on the fly. If this is omitted, it defaults to the same value as the memory element. The unit attribute behaves the same as for memory.
+ </div><div class="para">
+ In all cases for this section, the domain XML needs to be altered as follows:
+ </div><pre class="screen">
+<domain>
+
+ <memory unit='KiB' dumpCore='off'>524288</memory>
+ <!-- changes the memory unit to KiB and does not allow the guest's memory to be included in the generated coredump file -->
+ <currentMemory unit='KiB'>524288</currentMemory>
+ <!-- makes the current memory unit 524288 KiB -->
+ ...
+</domain>
+</pre></div><div class="section" id="sect-Virtualization-Tips_and_tricks-Using_qemu_img"><div class="titlepage"><div><div><h2 class="title">25.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, modifying and verifying various file systems used by KVM. <code class="command">qemu-img</code> options and usages are listed below.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm102233984">Check</h5>
+ Perform a consistency check on the disk image <em class="replaceable"><code>filename</code></em>.
+ </div><pre class="screen">
+# qemu-img check [-f <em class="parameter"><code>format</code></em>] <em class="replaceable"><code>filename</code></em></pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Only the <em class="replaceable"><code>qcow2</code></em> and <em class="replaceable"><code>vdi</code></em> formats support consistency checks.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="idm97604528">Commit</h5>
+ Commit any changes recorded in the specified file (<em class="replaceable"><code>filename</code></em>) to the file's base image with the <code class="command">qemu-img commit</code> command. Optionally, specify the file's format type (<em class="replaceable"><code>fmt</code></em>).
+ </div><pre class="screen"> # qemu-img commit [-f <em class="parameter"><code>fmt</code></em>] [-t <em class="parameter"><code>cache</code></em>] <em class="replaceable"><code>filename</code></em>
+</pre><div class="formalpara" id="form-Virtualization-Using_qemu_img-Convert_an_existing_image_to_another_format"><h5 class="formalpara">Convert</h5>
+ The <em class="parameter"><code>convert</code></em> option is used to convert one recognized image format to another image format.
+ </div><div class="para">
+ Command format:
+ </div><pre class="screen"># qemu-img convert [-c] [-p] [-f <em class="parameter"><code>fmt</code></em>] [-t <em class="parameter"><code>cache</code></em>] [-O <em class="parameter"><code>output_fmt</code></em>] [-o <em class="parameter"><code>options</code></em>] [-S <em class="parameter"><code>sparse_size</code></em>] <em class="replaceable"><code>filename</code></em> <em class="replaceable"><code>output_filename</code></em></pre><div class="para">
+ The <em class="parameter"><code>-p</code></em> parameter shows the progress of the command (optional and not for every command) and <em class="parameter"><code>-S</code></em> indicates the consecutive number of bytes that must contain only zeros for <code class="command">qemu-img</code> to create a sparse image during conversion.
+ </div><div class="para">
+ Convert the disk image <em class="parameter"><code>filename</code></em> to disk image <em class="parameter"><code>output_filename</code></em> using format <em class="parameter"><code>output_format</code></em>. The disk image can be optionally compressed with the <em class="parameter"><code>-c</code></em> option, or encrypted with the <em class="parameter"><code>-o</code></em> option by setting <code class="code">-o encryption</code>. Note that the options available with the <em class="parameter"><code>-o</code></em> parameter differ with the selected format.
+ </div><div class="para">
+ Only the <code class="filename">qcow2</code> format supports encryption or compression. <code class="filename">qcow2</code> encryption uses the AES format with secure 128-bit keys. <code class="filename">qcow2</code> compression is read-only, so if a compressed sector is converted from <code class="filename">qcow2</code> format, it is written to the new format as uncompressed data.
+ </div><div class="para">
+ Image conversion is also useful to get a 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" id="form-Virtualization-Using_qemu_img-Formatting_and_creating_new_images_or_devices"><h5 class="formalpara">Create</h5>
+ Create the new disk image <em class="replaceable"><code>filename</code></em> of size <em class="parameter"><code>size</code></em> and format <em class="parameter"><code>format</code></em>.
+ </div><pre class="screen"># qemu-img create [-f <em class="parameter"><code>format</code></em>] [-o <em class="replaceable"><code>options</code></em>] <em class="replaceable"><code>filename</code></em> [<em class="parameter"><code>size</code></em>]
+</pre><div class="para">
+ If a base image is specified with <code class="code">-o backing_file=<em class="replaceable"><code>filename</code></em></code>, the image will only record differences between itself and the base image. The backing file will not be modified unless you use the <code class="command">commit</code> command. No size needs to be specified in this case.
+ </div><div class="formalpara" id="form-Virtualization-Using_qemu_img-getting_image_information"><h5 class="formalpara">Info</h5>
+ The <code class="command">info</code> parameter displays information about a disk image <em class="replaceable"><code>filename</code></em>. The format for the <code class="command">info</code> option is as follows:
+ </div><pre class="screen"># qemu-img info [-f <em class="replaceable"><code>format</code></em>] <em class="replaceable"><code>filename</code></em></pre><div class="para">
+ This command is often used to discover the size reserved on disk which can be different from the displayed size. If snapshots are stored in the disk image, they are displayed also.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm79570624">Rebase</h5>
+ Changes the backing file of an image.
+ </div><pre class="screen">
+# qemu-img rebase [-f <em class="replaceable"><code>fmt</code></em>] [-t <em class="replaceable"><code>cache</code></em>] [-p] [-u] -b <em class="replaceable"><code>backing_file</code></em> [-F <em class="replaceable"><code>backing_fmt</code></em>] <em class="replaceable"><code>filename</code></em></pre><div class="para">
+ The backing file is changed to <em class="replaceable"><code>backing_file</code></em> and (if the format of <em class="replaceable"><code>filename</code></em> supports the feature), the backing file format is changed to <em class="replaceable"><code>backing_format</code></em>.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Only the <em class="replaceable"><code>qcow2</code></em> format supports changing the backing file (rebase).
+ </div></div></div><div class="para">
+ There are two different modes in which <em class="replaceable"><code>rebase</code></em> can operate: <span class="bold bold"><strong>Safe</strong></span> and <span class="bold bold"><strong>Unsafe</strong></span>.
+ </div><div class="para">
+ <span class="bold bold"><strong>Safe mode</strong></span> is used by default and performs a real rebase operation. The new backing file may differ from the old one and the <code class="command">qemu-img rebase</code> command will take care of keeping the guest-visible content of <em class="replaceable"><code>filename</code></em> unchanged. In order to achieve this, any clusters that differ between <em class="replaceable"><code>backing_file</code></em> and old backing file of <em class="replaceable"><code>filename</code></em> are merged into <em class="replaceable"><code>filename</code></em> before making any changes to the backing file.
+ </div><div class="para">
+ Note that safe mode is an expensive operation, comparable to converting an image. The old backing file is required for it to complete successfully.
+ </div><div class="para">
+ <span class="bold bold"><strong>Unsafe mode</strong></span> is used if the <em class="replaceable"><code>-u</code></em> option is passed to <code class="command">qemu-img rebase</code>. In this mode, only the backing file name and format of <em class="replaceable"><code>filename</code></em> is changed, without any checks taking place on the file contents. Make sure the new backing file is specified correctly or the guest-visible content of the image will be corrupted.
+ </div><div class="para">
+ This mode is useful for renaming or moving the backing file. It can be used without an accessible old backing file. For instance, it can be used to fix an image whose backing file has already been moved or renamed.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm79559040">Resize</h5>
+ Change the disk image <em class="replaceable"><code>filename</code></em> as if it had been created with size <em class="replaceable"><code>size</code></em>. Only images in raw format can be resized regardless of version. Fedora 17 and later adds the ability to grow (but not shrink) images in qcow2 format.
+ </div><div class="para">
+ Use the following to set the size of the disk image <em class="replaceable"><code>filename</code></em> to <em class="replaceable"><code>size</code></em> bytes:
+ </div><pre class="screen"># qemu-img resize <em class="replaceable"><code>filename</code></em> <em class="replaceable"><code>size</code></em></pre><div class="para">
+ You can also resize relative to the current size of the disk image. To give a size relative to the current size, prefix the number of bytes with <code class="literal">+</code> to grow, or <code class="literal">-</code> to reduce the size of the disk image by that number of bytes. Adding a unit suffix allows you to set the image size in kilobytes (K), megabytes (M), gigabytes (G) or terabytes (T).
+ </div><pre class="screen"># qemu-img resize <em class="replaceable"><code>filename</code></em> [+|-]<em class="replaceable"><code>size</code></em>[K|M|G|T]</pre><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Before using this command to shrink a disk image, you <span class="emphasis"><em>must</em></span> use file system and partitioning tools inside the VM itself to reduce allocated file systems and partition sizes accordingly. Failure to do so will result in data loss.
+ </div><div class="para">
+ After using this command to grow a disk image, you must use file system and partitioning tools inside the VM to actually begin using the new space on the device.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="idm71655008">Snapshot</h5>
+ List, apply, create, or delete an existing snapshot (<em class="replaceable"><code>snapshot</code></em>) of an image (<em class="replaceable"><code>filename</code></em>).
+ </div><pre class="screen"># qemu-img snapshot [ -l | -a <em class="replaceable"><code>snapshot</code></em> | -c <em class="replaceable"><code>snapshot</code></em> | -d <em class="replaceable"><code>snapshot</code></em> ] <em class="replaceable"><code>filename</code></em>
+</pre><div class="para">
+ <code class="command">-l</code> lists all snapshots associated with the specified disk image. The apply option, <code class="command">-a</code>, reverts the disk image (<em class="replaceable"><code>filename</code></em>) to the state of a previously saved <em class="replaceable"><code>snapshot</code></em>. <code class="command">-c</code> creates a snapshot (<em class="replaceable"><code>snapshot</code></em>) of an image (<em class="replaceable"><code>filename</code></em>). <code class="command">-d</code> deletes the specified snapshot.
+ </div><div class="formalpara" id="form-Virtualization-Using_qemu_img-Supported_formats"><h5 class="formalpara">Supported formats</h5>
+ <span class="application"><strong>qemu-img</strong></span> is designed to convert files to one of the following formats:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="command">raw</code> </span></dt><dd><div class="para">
+ Raw disk image format (default). This can be the fastest file-based format. 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 obtain the real size used by the image or <code class="command">ls -ls</code> on Unix/Linux. Although Raw images give optimal performance, only very basic features are available with a Raw image (no snapshots etc.).
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">qcow2</code> </span></dt><dd><div class="para">
+ QEMU image format, the most versatile format with the best feature set. Use it to have optional AES encryption, zlib-based compression, support of multiple VM snapshots, and smaller images, which are useful on file systems that do not support holes (non-NTFS file systems on Windows). Note that this expansive feature set comes at the cost of performance.
+ </div></dd></dl></div><div class="para">
+ Although only the formats above can be used to run on a guest or host machine, <span class="application"><strong>qemu-img</strong></span> also recognizes and supports the following formats in order to convert from them into either <code class="command">raw</code> or <code class="command">qcow2</code> format. The format of an image is usually detected automatically. In addition to converting these formats into <code class="command">raw</code> or <code class="command">qcow2</code> , they can be converted back from <code class="command">raw</code> or <code class="command">qcow2</code> to the original format.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="command">bochs</code></span></dt><dd><div class="para">
+ Bochs disk image format.
+ </div></dd><dt class="varlistentry"><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><dt class="varlistentry"><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 class="varlistentry"><span class="term"><code class="command">dmg</code></span></dt><dd><div class="para">
+ Mac disk image format.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">nbd</code></span></dt><dd><div class="para">
+ Network block device.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">parallels</code></span></dt><dd><div class="para">
+ Parallels virtualization disk image format.
+ </div></dd><dt class="varlistentry"><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 class="varlistentry"><span class="term"><code class="command">vdi</code></span></dt><dd><div class="para">
+ Oracle VM VirtualBox hard disk image format.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">vmdk</code></span></dt><dd><div class="para">
+ VMware 3 and 4 compatible image format.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">vpc</code></span></dt><dd><div class="para">
+ Windows Virtual PC disk image format. Also referred to as <code class="literal">vhd</code>, or Microsoft virtual hard disk image format.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">vvfat</code></span></dt><dd><div class="para">
+ Virtual VFAT disk image format.
+ </div></dd></dl></div></div><div class="section" id="sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions"><div class="titlepage"><div><div><h2 class="title">25.4. 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-x or AMD-V) are required for full virtualization.
+ </div><div class="procedure"><ol class="1"><li class="step"><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></li><li class="step"><div class="para">
+ Analyze the output.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The following output contains a <code class="computeroutput">vmx</code> entry indicating an Intel processor with the Intel VT-x extension:
+ </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></li><li class="listitem"><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></li></ul></div><div class="para">
+ If any output is received, the processor has the hardware virtualization extensions. However in some circumstances manufacturers disable the virtualization extensions in BIOS.
+ </div><div class="para">
+ The "<code class="computeroutput">flags:</code>" output content may appear multiple times, once for each hyperthread, core or CPU on 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="#proc-Virtualization-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS-Enabling_virtualization_extensions_in_BIOS">Procedure A.1, “Enabling virtualization extensions in BIOS”</a>.
+ </div></li><li class="step"><p class="title"><strong>Ensure KVM subsystem is loaded</strong></p><div class="para">
+ As an additional check, verify that the <code class="computeroutput">kvm</code> modules are loaded in the kernel:
+ </div><pre class="screen"># lsmod | grep kvm</pre><div class="para">
+ If the output includes <code class="computeroutput">kvm_intel</code> or <code class="computeroutput">kvm_amd</code> then the <code class="computeroutput">kvm</code> hardware virtualization modules are loaded and your system meets requirements.
+ </div></li></ol></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If the <span class="package">libvirt</span> package is installed, the <code class="command">virsh</code> command can output a full list of virtualization system capabilities. Run <code class="command">virsh capabilities </code> as root to receive the complete list.
+ </div></div></div></div><div xml:lang="en-US" class="section" id="idm71657744" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="idm71657744">25.5. Setting KVM processor affinities</h2></div></div></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ <span class="application"><strong>libvirt</strong></span> refers to a NUMA node as a <span class="emphasis"><em>cell</em></span>.
+ </div></div></div><div class="para">
+ This section covers setting processor and processing core affinities with <span class="application"><strong>libvirt</strong></span> and KVM guests.
+ </div><div class="para">
+ By default, libvirt provisions guests using the hypervisor's default policy. For most hypervisors, the policy is to run guests on any available processing core or CPU. There are times when an explicit policy may be better, particularly for systems with a NUMA (Non-Uniform Memory Access) architecture. A guest on a NUMA system can be pinned to a processing core so that its memory allocations are always local to the node it is running on. This avoids cross-node memory transports which have less bandwidth and can significantly degrade performance.
+ </div><div class="para">
+ On non-NUMA systems some form of explicit placement across the hosts’ sockets, cores and hyperthreads may be more efficient.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm101981152">Identifying CPU and NUMA topology</h5>
+ The first step in deciding which policy to apply is to determine the host’s memory and CPU topology. The <code class="command">virsh nodeinfo</code> command provides information about how many sockets, cores and hyperthreads are attached to a host.
+ </div><pre class="screen"># virsh nodeinfo
+CPU model: x86_64
+CPU(s): 8
+CPU frequency: 1000 MHz
+CPU socket(s): 2
+Core(s) per socket: 4
+Thread(s) per core: 1
+NUMA cell(s): 2
+Memory size: 8179176 kB</pre><div class="para">
+ This output shows that the system has eight CPU cores and two sockets. Each CPU socket has four cores. This splitting of CPU cores across multiple sockets suggests that the system has Non-Uniform Memory Access (NUMA) architecture.
+ </div><div class="para">
+ NUMA architecture can be more complex than other architectures. Use the <code class="command">virsh capabilities</code> command to get additional output data about the CPU configuration.
+ </div><pre class="programlisting"># virsh capabilities
+<capabilities>
+ <host>
+ <cpu>
+ <arch>x86_64</arch>
+ </cpu>
+ <migration_features>
+ <live/>
+ <uri_transports>
+ <uri_transport>tcp</uri_transport>
+ </uri_transports>
+ </migration_features>
+ <topology>
+ <cells num='2'>
+ <cell id='0'>
+ <cpus num='4'>
+ <cpu id='0'/>
+ <cpu id='1'/>
+ <cpu id='2'/>
+ <cpu id='3'/>
+ </cpus>
+ </cell>
+ <cell id='1'>
+ <cpus num='4'>
+ <cpu id='4'/>
+ <cpu id='5'/>
+ <cpu id='6'/>
+ <cpu id='7'/>
+ </cpus>
+ </cell>
+ </cells>
+ </topology>
+ <secmodel>
+ <model>selinux</model>
+ <doi>0</doi>
+ </secmodel>
+ </host>
+
+ <span class="emphasis"><em>[ Additional XML removed ]</em></span>
+
+</capabilities></pre><div class="para">
+ This output shows two NUMA nodes (also know as NUMA cells), each containing four logical CPUs (four processing cores). This system has two sockets, therefore it can be inferred that each socket is a separate NUMA node. For a guest with four virtual CPUs, it is optimal to lock the guest to physical CPUs 0 to 3, or 4 to 7, to avoid accessing non-local memory, which is significantly slower than accessing local memory.
+ </div><div class="para">
+ If a guest requires eight virtual CPUs, you could run two sets of four virtual CPU guests and split the work between them, since each NUMA node only has four physical CPUs. Running across multiple NUMA nodes significantly degrades performance for physical and virtualized tasks.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm87695136">Decide which NUMA node can run the guest</h5>
+ Locking a guest to a particular NUMA node offers no benefit if that node does not have sufficient free memory for that guest. libvirt stores information on the free memory available on each node. Use the <code class="command">virsh freecell --all</code> command to display the free memory on all NUMA nodes.
+ </div><pre class="screen"># virsh freecell --all
+0: 2203620 kB
+1: 3354784 kB</pre><div class="para">
+ If a guest requires 3 GB of RAM allocated, then the guest should be run on NUMA node (cell) 1. Node 0 only has 2.2GB free which may not be sufficient for certain guests.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm79560512">Lock a guest to a NUMA node or physical CPU set</h5>
+ Once you have determined which node to run the guest on, refer to the capabilities data (the output of the <code class="command">virsh capabilities</code> command) about NUMA topology.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Extract from the <code class="command">virsh capabilities</code> output.
+ </div><pre class="screen"><topology>
+ <cells num='2'>
+ <cell id='0'>
+ <cpus num='4'>
+ <cpu id='0'/>
+ <cpu id='1'/>
+ <cpu id='2'/>
+ <cpu id='3'/>
+ </cpus>
+ </cell>
+ <cell id='1'>
+ <cpus num='4'>
+ <cpu id='4'/>
+ <cpu id='5'/>
+ <cpu id='6'/>
+ <cpu id='7'/>
+ </cpus>
+ </cell>
+ </cells>
+</topology></pre></li><li class="step"><div class="para">
+ Observe that the node 1, <code class="computeroutput"><cell id='1'></code>, uses physical CPUs 4 to 7.
+ </div></li><li class="step"><div class="para">
+ The guest can be locked to a set of CPUs by appending the <code class="computeroutput">cpuset</code> attribute to the configuration file.
+ </div><ol class="a"><li class="step"><div class="para">
+ While the guest is offline, open the configuration file with <code class="command">virsh edit</code>.
+ </div></li><li class="step"><div class="para">
+ Locate the guest's virtual CPU count, defined in the <code class="computeroutput">vcpus</code> element.
+ </div><pre class="screen"><vcpus>4</vcpus></pre><div class="para">
+ The guest in this example has four CPUs.
+ </div></li><li class="step"><div class="para">
+ Add a <code class="computeroutput">cpuset</code> attribute with the CPU numbers for the relevant NUMA cell.
+ </div><pre class="screen"><vcpus cpuset='4-7'>4</vcpus></pre></li></ol></li><li class="step"><div class="para">
+ Save the configuration file and restart the guest.
+ </div></li></ol></div><div class="para">
+ The guest has been locked to CPUs 4 to 7.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm117823056">Automatically locking guests to CPUs with virt-install</h5>
+ The <code class="command">virt-install</code> provisioning tool provides a simple way to automatically apply a 'best fit' NUMA policy when guests are created.
+ </div><div class="para">
+ The <em class="parameter"><code>cpuset</code></em> option for <code class="command">virt-install</code> can use a CPU set of processors or the parameter <em class="parameter"><code>auto</code></em>. The <em class="parameter"><code>auto</code></em> parameter automatically determines the optimal CPU locking using the available NUMA data.
+ </div><div class="para">
+ For a NUMA system, use the <em class="parameter"><code>--cpuset=auto</code></em> with the <code class="command">virt-install</code> command when creating new guests.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm101574112">Tuning CPU affinity on running guests</h5>
+ There may be times where modifying CPU affinities on running guests is preferable to rebooting the guest. The <code class="command">virsh vcpuinfo</code> and <code class="command">virsh vcpupin</code> commands can perform CPU affinity changes on running guests.
+ </div><div class="para">
+ The <code class="command">virsh vcpuinfo</code> command gives up to date information about where each virtual CPU is running.
+ </div><div class="para">
+ In this example, <em class="replaceable"><code>guest1</code></em> is a guest with four virtual CPUs is running on a KVM host.
+ </div><pre class="screen"># virsh vcpuinfo <em class="replaceable"><code>guest1</code></em>
+VCPU: 0
+CPU: 3
+State: running
+CPU time: 0.5s
+CPU Affinity: yyyyyyyy
+VCPU: 1
+CPU: 1
+State: running
+CPU Affinity: yyyyyyyy
+VCPU: 2
+CPU: 1
+State: running
+CPU Affinity: yyyyyyyy
+VCPU: 3
+CPU: 2
+State: running
+CPU Affinity: yyyyyyyy</pre><div class="para">
+ The <code class="command">virsh vcpuinfo</code> output (the <code class="computeroutput">yyyyyyyy</code> value of <code class="computeroutput">CPU Affinity</code>) shows that the guest can presently run on any CPU.
+ </div><div class="para">
+ To lock the virtual CPUs to the second NUMA node (CPUs four to seven), run the following commands.
+ </div><pre class="screen"># virsh vcpupin <em class="replaceable"><code>guest1</code></em> 0 4
+# virsh vcpupin <em class="replaceable"><code>guest1</code></em> 1 5
+# virsh vcpupin <em class="replaceable"><code>guest1</code></em> 2 6
+# virsh vcpupin <em class="replaceable"><code>guest1</code></em> 3 7</pre><div class="para">
+ The <code class="command">virsh vcpuinfo</code> command confirms the change in affinity.
+ </div><pre class="screen"># virsh vcpuinfo <em class="replaceable"><code>guest1</code></em>
+VCPU: 0
+CPU: 4
+State: running
+CPU time: 32.2s
+CPU Affinity: ----y---
+VCPU: 1
+CPU: 5
+State: running
+CPU time: 16.9s
+CPU Affinity: -----y--
+VCPU: 2
+CPU: 6
+State: running
+CPU time: 11.9s
+CPU Affinity: ------y-
+VCPU: 3
+CPU: 7
+State: running
+CPU time: 14.6s
+CPU Affinity: -------y</pre></div><div class="section" id="sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address"><div class="titlepage"><div><div><h2 class="title">25.6. Generating a new unique MAC address</h2></div></div></div><div class="para">
+ In some cases you will need to generate a new and unique MAC address 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</pre><pre class="screen">#!/usr/bin/python
+# macgen.py script to generate a MAC address for guests
+#
+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" id="form-Virtualization-Generating_a_new_unique_MAC_address-Another_method_to_generate_a_new_MAC_for_your_guest"><h5 class="formalpara">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><div class="section" id="idm96083232"><div class="titlepage"><div><div><h2 class="title" id="idm96083232">25.7. Improving guest response time</h2></div></div></div><div class="para">
+ Guests can sometimes be slow to respond with certain workloads and usage patterns. Examples of situations which may cause slow or unresponsive guests:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Severely overcommitted memory.
+ </div></li><li class="listitem"><div class="para">
+ Overcommitted memory with high processor usage
+ </div></li><li class="listitem"><div class="para">
+ Other (not <code class="command">qemu-kvm</code> processes) busy or stalled processes on the host.
+ </div></li></ul></div><div class="para">
+ These types of workload may cause guests to appear slow or unresponsive. Usually, the guest's memory is eventually fully loaded into the host's main memory from swap. Once the guest is loaded in main memory, the guest will perform normally. Note, the process of loading a guest from swap to main memory may take several seconds per gigabyte of RAM assigned to the guest, depending on the type of storage used for swap and the performance of the components.
+ </div><div class="para">
+ KVM guests function as Linux processes. Linux processes are not permanently kept in main memory (physical RAM). The kernel scheduler swaps process memory into virtual memory (swap). Swap, with conventional hard disk drives, is thousands of times slower than main memory in modern computers. If a guest is inactive for long periods of time, the guest may be placed into swap by the kernel.
+ </div><div class="para">
+ KVM guests processes may be moved to swap regardless of whether memory is overcommitted or overall memory usage.
+ </div><div class="para">
+ Using unsafe overcommit levels or overcommitting with swap turned off guest processes or other critical processesis not recommended. Always ensure the host has sufficient swap space when overcommitting memory.
+ </div><div class="para">
+ For more information on overcommitting with KVM, refer to <a class="xref" href="#sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM">Chapter 22, <em>Overcommitting with KVM</em></a>.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Virtual memory allows a Linux system to use more memory than there is physical RAM on the system. Underused processes are swapped out which allows active processes to use memory, improving memory utilization. Disabling swap reduces memory utilization as all processes are stored in physical RAM.
+ </div><div class="para">
+ If swap is turned off, do not overcommit guests. Overcommitting guests without any swap can cause guests or the host system to crash.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="idm97846544">Turning off swap</h5>
+ Swap usage can be completely turned off to prevent guests from being unresponsive while they are moved back to main memory. Swap may also not be desired for guests as it can be resource-intensive on some systems.
+ </div><div class="para">
+ The <code class="command">swapoff</code> command can disable all swap partitions and swap files on a system.
+ </div><pre class="screen"># swapoff -a</pre><div class="para">
+ To make this change permanent, remove <em class="parameter"><code>swap</code></em> lines from the <code class="filename">/etc/fstab</code> file and restart the host system.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm90327008">Using SSDs for swap</h5>
+ Using Solid State Drives (SSDs) for swap storage may improve the performance of guests.
+ </div><div class="para">
+ Using RAID arrays, faster disks or separate drives dedicated to swap may also improve performance.
+ </div></div><div class="section" id="sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests"><div class="titlepage"><div><div><h2 class="title">25.8. Disable SMART disk monitoring for guests</h2></div></div></div><div class="para">
+ SMART disk monitoring can be safely disabled as virtual disks and the physical storage devices are managed by the host.
+ </div><pre class="screen"># service smartd stop
+# chkconfig --del smartd
+</pre></div><div class="section" id="sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server"><div class="titlepage"><div><div><h2 class="title">25.9. 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">
+ Use the following step set up a dedicated VNC server session:
+ </div><div class="para">
+ If needed, Create and then 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. For more information on vnc server files refer to the <em class="citetitle">Fedora Installation Guide</em>.
+ </div></div><div class="section" id="sect-gracefully-shut-down-guests"><div class="titlepage"><div><div><h2 class="title">25.10. Gracefully shutting down guests</h2></div></div></div><div class="para">
+ Installing virtualized Fedora 19 guests with the <code class="option">Minimal installation</code> option will not install the <span class="package">acpid</span> package.
+ </div><div class="para">
+ Without the <span class="package">acpid</span> package, the Fedora guest does not shut down when the <code class="command">virsh shutdown</code> command is executed. The <code class="command">virsh shutdown</code> command is designed to gracefully shut down guests.
+ </div><div class="para">
+ Using <code class="command">virsh shutdown</code> is easier and safer for system administration. Without graceful shut down with the <code class="command">virsh shutdown</code> command a system administrator must log into a guest manually or send the <span class="keycap"><strong>Ctrl</strong></span>-<span class="keycap"><strong>Alt</strong></span>-<span class="keycap"><strong>Del</strong></span> key combination to each guest.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Other virtualized operating systems may be affected by this issue. The <code class="command">virsh shutdown</code> command requires that the guest operating system is configured to handle ACPI shut down requests. Many operating systems require additional configuration on the guest operating system to accept ACPI shut down requests.
+ </div></div></div><div class="procedure"><h6>Procedure 25.1. Workaround for Fedora</h6><ol class="1"><li class="step"><p class="title"><strong>Install the acpid package</strong></p><div class="para">
+ The <code class="command">acpid</code> service listen and processes ACPI requests.
+ </div><div class="para">
+ Log into the guest and install the <span class="package">acpid</span> package on the guest:
+ </div><pre class="screen"># yum install acpid</pre></li><li class="step"><p class="title"><strong>Enable the acpid service</strong></p><div class="para">
+ Set the <code class="systemitem">acpid</code> service to start during the guest boot sequence and start the service:
+ </div><pre class="screen"># chkconfig acpid on
+# service acpid start</pre></li></ol></div><div class="para">
+ The guest is now configured to shut down when the <code class="command">virsh shutdown</code> command is used.
+ </div></div><div class="section" id="sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers"><div class="titlepage"><div><div><h2 class="title">25.11. Virtual machine timer management with libvirt</h2></div></div></div><div class="para">
+ Accurate time keeping on guests is a key challenge for virtualization platforms. Different hypervisors attempt to handle the problem of time keeping in a variety of ways. Libvirt provides hypervisor independent configuration settings for time management, using the <clock> and <timer> elements in the domain XML. The domain XML can be edited using the <code class="command">virsh edit</code> command. See <a class="xref" href="#form-Virtualization-Managing_guests_with_virsh-Editing_a_guests_configuration_file">Editing a guest's configuration file</a> for details.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm111543472"><clock></h5>
+ The clock element is used to determine how the guest clock is synchronized with the host clock. The clock element has the following attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm111541248">offset</h5>
+ Determines how the guest clock is offset from the host clock. The offset attribute has the following possible values:
+ </div><div class="table" id="clock_element_offset_attribute_values"><h6>Table 25.1. Offset attribute values</h6><div class="table-contents"><table summary="Offset attribute values" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Value
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ utc
+ </td><td class="">
+ The guest clock will be synchronized to UTC when booted.
+ </td></tr><tr><td class="">
+ localtime
+ </td><td class="">
+ The guest clock will be synchronized to the host's configured timezone when booted, if any.
+ </td></tr><tr><td class="">
+ timezone
+ </td><td class="">
+ The guest clock will be synchronized to a given timezone, specified by the <em class="parameter"><code>timezone</code></em> attribute.
+ </td></tr><tr><td class="">
+ variable
+ </td><td class="">
+ The guest clock will be synchronized to an arbitrary offset from UTC. The delta relative to UTC is specified in seconds, using the <em class="parameter"><code>adjustment</code></em> attribute. The guest is free to adjust the Real Time Clock (RTC) over time and expect that it will be honored following the next reboot. This is in contrast to <em class="parameter"><code>utc</code></em> mode, where any RTC adjustments are lost at each reboot.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The value <span class="bold bold"><strong>utc</strong></span> is set as the clock offset in a virtual machine by default. However, if the guest clock is run with the <span class="bold bold"><strong>localtime</strong></span> value, the clock offset needs to be changed to a different value in order to have the guest clock synchronized with the host clock.
+ </div></div></div></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm113960944">timezone</h5>
+ The timezone to which the guest clock is to be synchronized.
+ </div></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm113959056">adjustment</h5>
+ The delta for guest clock synchronization. In seconds, relative to UTC.
+ </div></li></ul></div><div class="example"><h6>Example 25.1. Always synchronize to UTC</h6><div class="example-contents"><pre class="screen"><clock offset="utc" /></pre></div></div><br class="example-break" /><div class="example"><h6>Example 25.2. Always synchronize to the host timezone</h6><div class="example-contents"><pre class="screen"><clock offset="localtime" /></pre></div></div><br class="example-break" /><div class="example"><h6>Example 25.3. Synchronize to an arbitrary timezone</h6><div class="example-contents"><pre class="screen"><clock offset="timezone" timezone="Europe/Paris" /></pre></div></div><br class="example-break" /><div class="example"><h6>Example 25.4. Synchronize to UTC + arbitrary offset</h6><div class="example-contents"><pre class="screen"><clock offset="variable" adjustment="123456" /></pre></div></div><br class="example-break" /><div class="formalpara"><h5 class="formalpara" id="idm116046512"><timer></h5>
+ A clock element can have zero or more timer elements as children. The timer element specifies a time source used for guest clock synchronization. The timer element has the following attributes. Only the <em class="parameter"><code>name</code></em> is required, all other attributes are optional.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm103201312">name</h5>
+ The name of the time source to use.
+ </div><div class="table" id="timer_element_name_attribute_values"><h6>Table 25.2. name attribute values</h6><div class="table-contents"><table summary="name attribute values" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Value
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ platform
+ </td><td class="">
+ The master virtual time source which may be used to drive the policy of other time sources.
+ </td></tr><tr><td class="">
+ pit
+ </td><td class="">
+ Programmable Interval Timer - a timer with periodic interrupts.
+ </td></tr><tr><td class="">
+ rtc
+ </td><td class="">
+ Real Time Clock - a continuously running timer with periodic interrupts.
+ </td></tr><tr><td class="">
+ hpet
+ </td><td class="">
+ High Precision Event Timer - multiple timers with periodic interrupts.
+ </td></tr><tr><td class="">
+ tsc
+ </td><td class="">
+ Time Stamp Counter - counts the number of ticks since reset, no interrupts.
+ </td></tr><tr><td class="">
+ kvmclock
+ </td><td class="">
+ KVM clock - recommended clock source for KVM guests. KVM pvclock, or kvm-clock lets guests read the host’s wall clock time.
+ </td></tr></tbody></table></div></div><br class="table-break" /></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm79839632">track</h5>
+ The <span class="emphasis"><em>track</em></span> attribute specifies what is tracked by the timer. Only valid for a name value of <em class="parameter"><code>platform</code></em> or <em class="parameter"><code>rtc</code></em>.
+ </div><div class="table" id="timer_element_track_attribute_values"><h6>Table 25.3. track attribute values</h6><div class="table-contents"><table summary="track attribute values" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Value
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ boot
+ </td><td class="">
+ Corresponds to old <span class="emphasis"><em>host</em></span> option, this is an unsupported tracking option.
+ </td></tr><tr><td class="">
+ guest
+ </td><td class="">
+ RTC always tracks guest time.
+ </td></tr><tr><td class="">
+ wall
+ </td><td class="">
+ RTC always tracks host time.
+ </td></tr></tbody></table></div></div><br class="table-break" /></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm112040768">tickpolicy</h5>
+ The policy used to pass ticks on to the guest.
+ </div><div class="table" id="timer_element_policy_attribute_values"><h6>Table 25.4. tickpolicy attribute values</h6><div class="table-contents"><table summary="tickpolicy attribute values" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Value
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ delay
+ </td><td class="">
+ Continue to deliver at normal rate (i.e. ticks are delayed).
+ </td></tr><tr><td class="">
+ catchup
+ </td><td class="">
+ Deliver at a higher rate to catch up.
+ </td></tr><tr><td class="">
+ merge
+ </td><td class="">
+ Ticks merged into one single tick.
+ </td></tr><tr><td class="">
+ discard
+ </td><td class="">
+ All missed ticks are discarded.
+ </td></tr></tbody></table></div></div><br class="table-break" /></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm110409904">frequency</h5>
+ Used to set a fixed frequency, measured in Hz. This attribute is only relevant for a name value of <em class="parameter"><code>tsc</code></em>. All other timers operate at a fixed frequency (<em class="parameter"><code>pit</code></em>, <em class="parameter"><code>rtc</code></em>), or at a frequency fully controlled by the guest (<em class="parameter"><code>hpet</code></em>).
+ </div></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm72794224">mode</h5>
+ Determines how the time source is exposed to the guest. This attribute is only relevant for a name value of <em class="parameter"><code>tsc</code></em>. All other timers are always emulated. Command is as follows: <code class="command"><timer name='tsc' frequency='NNN' mode='auto|native|emulate|smpsafe'/></code>. Mode definitions are given in the table.
+ </div><div class="table" id="timer_element_mode_attribute_values"><h6>Table 25.5. mode attribute values</h6><div class="table-contents"><table summary="mode attribute values" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Value
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ auto
+ </td><td class="">
+ Native if TSC is unstable, otherwise allow native TSC access.
+ </td></tr><tr><td class="">
+ native
+ </td><td class="">
+ Always allow native TSC access.
+ </td></tr><tr><td class="">
+ emulate
+ </td><td class="">
+ Always emulate TSC.
+ </td></tr><tr><td class="">
+ smpsafe
+ </td><td class="">
+ Always emulate TSC and interlock SMP
+ </td></tr></tbody></table></div></div><br class="table-break" /></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm101949504">present</h5>
+ Used to override the default set of timers visible to the guest. For example, to enable or disable the HPET.
+ </div><div class="table" id="timer_element_present_attribute_values"><h6>Table 25.6. present attribute values</h6><div class="table-contents"><table summary="present attribute values" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Value
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ yes
+ </td><td class="">
+ Force this timer to the visible to the guest.
+ </td></tr><tr><td class="">
+ no
+ </td><td class="">
+ Force this timer to not be visible to the guest.
+ </td></tr></tbody></table></div></div><br class="table-break" /></li></ul></div><div class="example"><h6>Example 25.5. Clock synchronizing to local time with RTC and PIT timers, and the HPET timer disabled</h6><div class="example-contents"><pre class="screen"><clock offset="localtime">
+ <timer name="rtc" tickpolicy="catchup" track="guest" />
+ <timer name="pit" tickpolicy="delay" />
+ <timer name="hpet" present="no" />
+</clock></pre></div></div><br class="example-break" /></div><div class="section" id="sect-perf-mon"><div class="titlepage"><div><div><h2 class="title">25.12. Using PMU to monitor guest performance</h2></div></div></div><div class="para">
+ In Fedora 18 and onward, vPMU (virtual PMU )was introduced as technical-preview. vPMU is based on Intel's PMU (Performance Monitoring Units) and may only be used on Intel machines. PMU allows the tracking of statistics which indicate how a guest virtual machine is functioning.
+ </div><div class="para">
+ Using performance monitoring, allows developers to use the CPU's PMU counter while using the performance tool for profiling. The virtual performance monitoring unit feature allows virtual machine users to identify sources of possible performance problems in their guest virtual machines, thereby improving the ability to profile a KVM guest virtual machine.
+ </div><div class="para">
+ To enable the feature, the <code class="command">-cpu host </code>flag must be set.
+ </div><div class="para">
+ This feature is only supported with guests running Fedora and is disabled by default. This feature only works using the Linux perf tool. Make sure the <span class="package">perf</span> package is installed using the command:
+ </div><pre class="screen">#<code class="command"> yum install perf</code>.</pre><div class="para">
+ See the man page on <code class="command">perf</code> for more information on the perf commands.
+ </div></div><div class="section" id="sect-s3-s4"><div class="titlepage"><div><div><h2 class="title">25.13. Guest virtual machine power management</h2></div></div></div><div class="para">
+ It is possible to forcibly enable or disable BIOS advertisements to the guest virtual machine's operating system by changing the following parameters in the Domain XML for Libvirt:
+ </div><pre class="screen">
+...
+ <pm>
+ <suspend-to-disk enabled='no'/>
+ <suspend-to-mem enabled='yes'/>
+ </pm>
+ ...
+</pre><div class="para">
+ The element <em class="parameter"><code>pm</code></em> enables ('yes') or disables ('no') BIOS support for S3 (suspend-to-disk) and S4 (suspend-to-mem) ACPI sleep states. If nothing is specified, then the hypervisor will be left with its default value.
+ </div></div><div class="section" id="sect-qemu-ga"><div class="titlepage"><div><div><h2 class="title">25.14. QEMU Guest Agent Protocol</h2></div></div></div><div class="para">
+ The QEMU guest agent protocol (QEMU-ga), uses the same protocol as QMP. <span class="package">qemu-ga</span>. There are a couple issues regarding its isa-serial/virtio-serial transport, and the following caveats have been noted:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ There is no way for <span class="package">qemu-ga</span> to detect whether or not a client has connected to the channel.
+ </div></li><li class="listitem"><div class="para">
+ There is no way for a client to detect whether or not <span class="package">qemu-ga</span> has disconnected or reconnected to the backend.
+ </div></li><li class="listitem"><div class="para">
+ If the virtio-serial device resets and <span class="package">qemu-ga</span> has not connected to the channel as a result, (generally caused by a reboot or hotplug), data from the client will be dropped.
+ </div></li><li class="listitem"><div class="para">
+ If <span class="package">qemu-ga</span> has connected to the channel following a virtio-serial device reset, data from the client will be queued (and eventually throttled if available buffers are exhausted), regardless of whether or not <span class="package">qemu-ga</span> is still running/connected.
+ </div></li></ul></div><div class="para">
+ qemu-ga uses the guest-sync or guest-sync-delimited command to address the problem of re-synchronizing the channel after re-connection or client-side timeouts. These are described below.
+ </div><div class="section" id="sect-guest-synch"><div class="titlepage"><div><div><h3 class="title">25.14.1. guest-sync</h3></div></div></div><div class="para">
+ The guest-sync request/response exchange is simple. The client provides a unique numerical token, the agent sends it back in a response:
+ </div><pre class="screen">
+ > { "execute": "guest-sync", "arguments": { "id": 123456 } }
+ < { "return": 123456}
+</pre><div class="para">
+ A successful exchange guarantees that the channel is now in sync and no unexpected data/responses will be sent. Note that for the reasons mentioned above there's no guarantee this request will be answered, so a client should implement a timeout and re-issue this periodically until a response is received for the most recent request.
+ </div><div class="para">
+ This alone does not handle synchronization issues in all cases. For example, if <span class="package">qemu-ga</span>'s parser previously received a partial request from a previous client connection, subsequent attempts to issue the guest-sync request can be misconstrued as being part of the previous partial request. Eventually <span class="package">qemu-ga</span> will hit it's recursion or token size limit and flush its parser state, at which point it will begin processing the backlog of requests, but there's no guarantee this will occur before the channel is throttled due to exhausting all available buffers. Thus, there is a potential for a deadlock situation occurring for certain instances.
+ </div><div class="para">
+ To avoid this, <span class="package">qemu-ga/QEMU</span>'s JSON parser has special handling for the 0xFF byte, which is an invalid UTF-8 character. Client requests should precede the guest-sync request with to ensure that <span class="package">qemu-ga</span> flushes it's parser state as soon as possible. As long as all clients abide by this, the deadlock state should be reliably avoidable.
+ </div><div class="para">
+ For more information see the qemu-ga wiki page on <a href="http://wiki.qemu.org/Features/QAPI/GuestAgent">wiki.qemu.org</a>.
+ </div></div><div class="section" id="subsect-guest-synch-delimited"><div class="titlepage"><div><div><h3 class="title">25.14.2. guest-sync-delimited</h3></div></div></div><div class="para">
+ If <span class="package">qemu-ga</span> attempts to communicate with a client, and the client receives a partial response from a previous <span class="package">qemu-ga</span> instance, the client might misconstrue responses to guest-sync as being part of this previous request. For client implementations that treat newlines as a delimiter for <span class="package">qemu-ga</span> responses, use <code class="command">guest-synch-delimited</code>.
+ </div><div class="para">
+ Even in some cases where there are JSON stream-based implementations that do not rely on newline delimiters, it may be considered invasive to implement a client's response/JSON handling, as it is the same deadlock scenario described previously. Using the <code class="command">guest-sync-delimited</code> on the client, tells qemu-ga to place the same 0xFF character in front of the response, thereby preventing confusion.
+ </div><pre class="screen">
+> { "execute": "guest-sync-delimited", "arguments": { "id": 123456 } }
+< { "return": 123456}
+</pre><div class="para">
+ Actual hex values sent:
+ </div><pre class="screen">
+> 7b 27 65 78 65 63 75 74 65 27 3a 27 67 75 65 73 74 2d 73 79 6e 63 2d 64 65
+ 6c 69 6d 69 74 65 64 27 2c 27 61 72 67 75 6d 65 6e 74 73 27 3a 7b 27 69 64
+ 27 3a 31 32 33 34 35 36 7d 7d 0a
+< ff 7b 22 72 65 74 75 72 6e 22 3a 20 31 32 33 34 35 36 7d 0a
+</pre><div class="para">
+ As stated above, the request should also be preceded with a 0xFF to flush <span class="package">qemu-ga</span>'s parser state.
+ </div></div></div><div class="section" id="sect-limit-redirection"><div class="titlepage"><div><div><h2 class="title">25.15. Setting a limit on device redirection</h2></div></div></div><div class="para">
+ To filter out certain devices from redirection, pass the filter property to <em class="parameter"><code>-device usb-redir</code></em>. The filter property takes a string consisting of filter rules, the format for a rule is:
+ </div><pre class="screen"><code class="command"><class>:<vendor>:<product>:<version>:<allow></code></pre><div class="para">
+ Use the value <em class="parameter"><code>-1 </code></em> to designate it to accept any value for a particular field. You may use multiple rules on the same command line using | as a separator. Note that if a device matches none of the passed in rules, redirecting it will not be allowed!
+ </div><div class="example" id="exam-limit-redirect"><h6>Example 25.6. An example of limiting redirection with a windows guest virtual machine </h6><div class="example-contents"><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Prepare a Windows 7 guest.
+ </div></li><li class="step"><div class="para">
+ Add the following code excerpt to the guest's' domain xml file:
+ </div><pre class="screen">
+ <redirdev bus='usb' type='spicevmc'>
+ <alias name='redir0'/>
+ <address type='usb' bus='0' port='3'/>
+ </redirdev>
+ <redirfilter>
+ <usbdev class='0x08' vendor='0x1234' product='0xBEEF' version='2.0' allow='yes'/>
+ <usbdev class='-1' vendor='-1' product='-1' version='-1' allow='no'/>
+ </redirfilter>
+</pre></li><li class="step"><div class="para">
+ Start the guest and confirm the setting changes by running the following:
+ </div><pre class="screen">#<code class="command">ps -ef | grep $guest_name</code></pre><pre class="screen"><code class="command">-device usb-redir,chardev=charredir0,id=redir0,</code>/
+<code class="command">filter=0x08:0x1234:0xBEEF:0x0200:1|-1:-1:-1:-1:0,bus=usb.0,port=3</code></pre></li><li class="step"><div class="para">
+ Plug a USB device into host, and use virt-viewer to connect to the guest.
+ </div></li><li class="step"><div class="para">
+ Click <span class="guimenuitem"><strong>USB device selection</strong></span> in the menu, which will produce the following message: "Some USB devices are blocked by host policy". Click <span class="guimenuitem"><strong>OK</strong></span> to confirm and continue.
+ </div><div class="para">
+ The filter takes effect.
+ </div></li><li class="step"><div class="para">
+ To make sure that the filter captures properly check the USB device vendor and product, then make the following changes in the host's domain XML to allow for USB redirection.
+ </div><pre class="screen">
+ <redirfilter>
+ <usbdev class='0x08' vendor='0x0951' product='0x1625' version='2.0' allow='yes'/>
+ <usbdev allow='no'/>
+ </redirfilter>
+</pre></li><li class="step"><div class="para">
+ Restart the guest, then use <span class="application"><strong>virt-viewer</strong></span> to connect to the guest. The USB device will now redirect traffic to the guest.
+ </div></li></ol></div></div></div><br class="example-break" /></div><div class="section" id="sect-dynamic-vNIC"><div class="titlepage"><div><div><h2 class="title">25.16. Dynamically changing a host or a network bridge that is attached to a virtual NIC</h2></div></div></div><div class="para">
+ This section demonstrates how to move the vNIC of a guest from one bridge to another while the guest is running without compromising the guest
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Prepare guest with a configuration similar to the following:
+ </div><pre class="screen">
+<interface type='bridge'>
+ <mac address='52:54:00:4a:c9:5e'/>
+ <source bridge='virbr0'/>
+ <model type='virtio'/>
+</interface>
+</pre></li><li class="step"><div class="para">
+ Prepare an XML file for interface update:
+ </div><pre class="screen">#<code class="command"> cat br1.xml</code></pre><pre class="screen">
+<interface type='bridge'>
+ <mac address='52:54:00:4a:c9:5e'/>
+ <source bridge='virbr1'/>
+ <model type='virtio'/>
+</interface>
+</pre></li><li class="step"><div class="para">
+ Start the guest, confirm the guest's network functionality, and check that the guest's vnetX is connected to the bridge you indicated.
+ </div><pre class="screen">
+<code class="command"># brctl show</code>
+bridge name bridge id STP enabled interfaces
+virbr0 8000.5254007da9f2 yes virbr0-nic
+
+vnet0
+virbr1 8000.525400682996 yes virbr1-nic
+</pre></li><li class="step"><div class="para">
+ Update the guest's network with the new interface parameters with the following command:
+ </div><pre class="screen">
+<code class="command"># virsh update-device test1 br1.xml </code>
+
+Device updated successfully
+
+</pre></li><li class="step"><div class="para">
+ On the guest, run <code class="command">service network restart</code>. The guest gets a new IP address for virbr1. Check the guest's vnet0 is connected to the new bridge(virbr1)
+ </div><pre class="screen">
+# <code class="command">brctl show</code>
+bridge name bridge id STP enabled interfaces
+virbr0 8000.5254007da9f2 yes virbr0-nic
+virbr1 8000.525400682996 yes virbr1-nic vnet0
+</pre></li></ol></div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_Guide-Storage_Concepts" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 26. Storage concepts</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Virtualization-Storage_Concepts-Storage_Pools">26.1. Storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Concepts-Volumes">26.2. Volumes </a></span></dt></dl></div><div class="para">
+ This chapter introduces the concepts used for describing and managing storage devices. Terms such as Storage Pools and Volumes are explained in the sections that follow.
+ </div><div class="section" id="sect-Virtualization-Storage_Concepts-Storage_Pools"><div class="titlepage"><div><div><h2 class="title">26.1. Storage pools</h2></div></div></div><div class="para">
+ A <em class="firstterm">storage pool</em> is a file, directory, or storage device managed by libvirt for the purpose of providing storage to guests. The storage pool can be local or it can be shared over a network.
+ </div><div class="para">
+ libvirt uses a directory-based storage pool, the <code class="filename">/var/lib/libvirt/images/</code> directory, as the default storage pool. The default storage pool can be changed to another storage pool.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Local storage pools</strong></span> - Local storage pools are directly attached to the host server. Local storage pools include: local directories, directly attached disks, physical partitions, and LVM volume groups. These storage volumes store guest images or are attached to guests as additional storage. As local storage pools are directly attached to the host server, they are useful for development, testing and small deployments that do not require migration or large numbers of guests. Local storage pools are not suitable for many production environments as local storage pools do not support live migration.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Networked (shared) storage pools</strong></span> - Networked storage pools include storage devices shared over a network using standard protocols. Networked storage is required when migrating virtual machines between hosts with virt-manager, but is optional when migrating with virsh. Networked storage pools are managed by libvirt. Supported protocols for networked storage pools include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Fibre Channel-based LUNs
+ </div></li><li class="listitem"><div class="para">
+ iSCSI
+ </div></li><li class="listitem"><div class="para">
+ NFS
+ </div></li><li class="listitem"><div class="para">
+ GFS2
+ </div></li><li class="listitem"><div class="para">
+ SCSI RDMA protocols (SCSI RCP), the block export protocol used in InfiniBand and 10GbE iWARP adapters.
+ </div></li></ul></div></li></ul></div></div><div class="section" id="sect-Virtualization-Storage_Concepts-Volumes"><div class="titlepage"><div><div><h2 class="title">26.2. Volumes </h2></div></div></div><div class="para">
+ Storage pools are divided into storage volumes. Storage volumes are an abstraction of physical partitions, LVM logical volumes, file-based disk images and other storage types handled by libvirt. Storage volumes are presented to guests as local storage devices regardless of the underlying hardware.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm94164768"> Referencing volumes</h5>
+ To reference a specific volume, three approaches are possible:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">The name of the volume and the storage pool</span></dt><dd><div class="para">
+ A volume may be referred to by name, along with an identifier for the storage pool it belongs in. On the virsh command line, this takes the form <em class="parameter"><code>--pool</code></em> <em class="replaceable"><code>storage_pool</code></em> <em class="replaceable"><code>volume_name</code></em>.
+ </div><div class="para">
+ For example, a volume named <em class="replaceable"><code>firstimage</code></em> in the <em class="replaceable"><code>guest_images</code></em> pool.
+ </div><pre class="screen"># virsh vol-info --pool <em class="replaceable"><code>guest_images</code></em> <em class="replaceable"><code>firstimage</code></em>
+Name: <em class="replaceable"><code>firstimage</code></em>
+Type: block
+Capacity: 20.00 GB
+Allocation: 20.00 GB
+
+virsh #</pre></dd><dt class="varlistentry"><span class="term">The full path to the storage on the host system</span></dt><dd><div class="para">
+ A volume may also be referred to by its full path on the file system. When using this approach, a pool identifier does not need to be included.
+ </div><div class="para">
+ For example, a volume named <em class="replaceable"><code>secondimage.img</code></em>, visible to the host system as <em class="replaceable"><code>/images/secondimage.img</code></em>. The image can be referred to as <em class="replaceable"><code>/images/secondimage.img</code></em>.
+ </div><pre class="screen"># virsh vol-info <em class="replaceable"><code>/images/secondimage.img</code></em>
+Name: <em class="replaceable"><code>secondimage.img</code></em>
+Type: file
+Capacity: 20.00 GB
+Allocation: 136.00 kB
+</pre></dd><dt class="varlistentry"><span class="term">The unique volume key</span></dt><dd><div class="para">
+ When a volume is first created in the virtualization system, a unique identifier is generated and assigned to it. The unique identifier is termed the <em class="firstterm">volume key</em>. The format of this volume key varies upon the storage used.
+ </div><div class="para">
+ When used with block based storage such as LVM, the volume key may follow this format:
+ </div><pre class="screen">c3pKz4-qPVc-Xf7M-7WNM-WJc8-qSiz-mtvpGn</pre><div class="para">
+ When used with file based storage, the volume key may instead be a copy of the full path to the volume storage.
+ </div><pre class="screen">/images/secondimage.img</pre><div class="para">
+ For example, a volume with the volume key of <em class="replaceable"><code>Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr</code></em>:
+ </div><pre class="screen"># virsh vol-info Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr
+Name: <em class="replaceable"><code>firstimage</code></em>
+Type: block
+Capacity: 20.00 GB
+Allocation: 20.00 GB
+</pre></dd></dl></div><div class="para">
+ <code class="command">virsh</code> provides commands for converting between a volume name, volume path, or volume key:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> vol-name </span></dt><dd><div class="para">
+ Returns the volume name when provided with a volume path or volume key.
+ </div><pre class="screen"># virsh vol-name /dev/<em class="replaceable"><code>guest_images</code></em>/<em class="replaceable"><code>firstimage</code></em>
+<em class="replaceable"><code>firstimage</code></em>
+# virsh vol-name <em class="replaceable"><code>Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr</code></em></pre></dd><dt class="varlistentry"><span class="term">vol-path</span></dt><dd><div class="para">
+ Returns the volume path when provided with a volume key, or a storage pool identifier and volume name.
+ </div><pre class="screen"># virsh vol-path Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr
+/dev/<em class="replaceable"><code>guest_images</code></em>/<em class="replaceable"><code>firstimage</code></em>
+# virsh vol-path --pool <em class="replaceable"><code>guest_images</code></em> <em class="replaceable"><code>firstimage</code></em>
+/dev/<em class="replaceable"><code>guest_images</code></em>/<em class="replaceable"><code>firstimage</code></em></pre></dd><dt class="varlistentry"><span class="term">The vol-key command</span></dt><dd><div class="para">
+ Returns the volume key when provided with a volume path, or a storage pool identifier and volume name.
+ </div><pre class="screen"># virsh vol-key /dev/<em class="replaceable"><code>guest_images</code></em>/<em class="replaceable"><code>firstimage</code></em>
+Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr
+# virsh vol-key --pool <em class="replaceable"><code>guest_images</code></em> <em class="replaceable"><code>firstimage</code></em>
+Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr
+</pre></dd></dl></div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 27. Storage pools</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating_Storage_Pools">27.1. Creating storage pools </a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-Dedicated_Disk_Devices">27.1.1. Disk-based storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-File_Systems">27.1.2. Partition-based storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-Local_Directories">27.1.3. Directory-based storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-LVM">27.1.4. LVM-based storage po
ols</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-iSCSI">27.1.5. iSCSI-based storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-NFS">27.1.6. NFS-based storage pools</a></span></dt></dl></dd></dl></div><div class="para">
+ This chapter includes instructions on creating storage pools of assorted types. A <em class="firstterm">storage pool</em> is a quantity of storage set aside by an administrator, often a dedicated storage administrator, for use by virtual machines. Storage pools are often divided into storage volumes either by the storage administrator or the system administrator, and the volumes are assigned to guest virtual machines as block devices.
+ </div><div class="example"><h6>Example 27.1. NFS storage pool</h6><div class="example-contents"><div class="para">
+ Suppose a storage administrator responsible for an NFS server creates a share to store guest virtual machines' data. The system administrator defines a pool on the host with the details of the share (nfs.example.com:<code class="filename">/path/to/share</code> should be mounted on <code class="filename">/vm_data</code>). When the pool is started, libvirt mounts the share on the specified directory, just as if the system administrator logged in and executed <code class="command">mount nfs.example.com:/path/to/share /vmdata</code>. If the pool is configured to autostart, libvirt ensures that the NFS share is mounted on the directory specified when libvirt is started.
+ </div><div class="para">
+ Once the pool starts, the files that the NFS share, are reported as volumes, and the storage volumes' paths are then queried using the libvirt APIs. The volumes' paths can then be copied into the section of a guest virtual machine's XML definition file describing the source storage for the guest virtual machine's block devices. With NFS, applications using the libvirt APIs can create and delete volumes in the pool (files within the NFS share) up to the limit of the size of the pool (the maximum storage capacity of the share). Not all pool types support creating and deleting volumes. Stopping the pool negates the start operation, in this case, unmounts the NFS share. The data on the share is not modified by the destroy operation, despite the name. See man virsh for more details.
+ </div></div></div><br class="example-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Storage pools and volumes are not required for the proper operation of guest virtual machines. Pools and volumes provide a way for libvirt to ensure that a particular piece of storage will be available for a guest virtual machine, but some administrators will prefer to manage their own storage and guest virtual machines will operate properly without any pools or volumes defined. On systems that do not use pools, system administrators must ensure the availability of the guest virtual machines' storage using whatever tools they prefer, for example, adding the NFS share to the host's fstab so that the share is mounted at boot time.
+ </div></div></div><div class="section" id="sect-Virtualization-Storage_Pools-Creating_Storage_Pools"><div class="titlepage"><div><div><h2 class="title">27.1. Creating storage pools </h2></div></div></div><div xml:lang="en-US" class="section" id="sect-Virtualization-Storage_Pools-Creating-Dedicated_Disk_Devices" lang="en-US"><div class="titlepage"><div><div><h3 class="title">27.1.1. Disk-based storage pools</h3></div></div></div><div class="para">
+ This section covers creating disk based storage devices for guest virtual machines.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Guests should not be given write access to whole disks or block devices (for example, <code class="filename">/dev/sdb</code>). Use partitions (for example, <code class="filename">/dev/sdb1</code>) or LVM volumes.
+ </div><div class="para">
+ If you pass an entire block device to the guest, the guest will likely partition it or create its own LVM groups on it. This can cause the host to detect these partitions or LVM groups and cause errors.
+ </div></div></div><div class="section" id="idm82341264"><div class="titlepage"><div><div><h4 class="title" id="idm82341264">27.1.1.1. Creating a disk based storage pool using virsh</h4></div></div></div><div class="para">
+ This procedure creates a new storage pool using a disk device with the <code class="command">virsh</code> command.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Dedicating a disk to a storage pool will reformat and erase all data presently stored on the disk device! It is strongly recommended to back up the storage device before commencing with the following procedure:
+ </div></div></div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong> Create a GPT disk label on the disk </strong></p><div class="para">
+ The disk must be relabeled with a <em class="firstterm">GUID Partition Table</em> (GPT) disk label. GPT disk labels allow for creating a large numbers of partitions, up to 128 partitions, on each device. GPT partition tables can store partition data for far more partitions than the MS-DOS partition table.
+ </div><pre class="screen"># parted /dev/sdb
+GNU Parted 2.1
+Using /dev/sdb
+Welcome to GNU Parted! Type 'help' to view a list of commands.
+(parted) mklabel
+New disk label type? gpt
+(parted) quit
+Information: You may need to update /etc/fstab.
+#
+</pre></li><li class="step"><p class="title"><strong>Create the storage pool configuration file</strong></p><div class="para">
+ Create a temporary XML text file containing the storage pool information required for the new device.
+ </div><div class="para">
+ The file must be in the format shown below, and contain the following fields:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><name>guest_images_disk</name></span></dt><dd><div class="para">
+ The <em class="parameter"><code>name</code></em> parameter determines the name of the storage pool. This example uses the name <em class="replaceable"><code>guest_images_disk</code></em> in the example below.
+ </div></dd><dt class="varlistentry"><span class="term"> <device path='<em class="replaceable"><code>/dev/sdb</code></em>'/></span></dt><dd><div class="para">
+ The <em class="parameter"><code>device</code></em> parameter with the <em class="parameter"><code>path</code></em> attribute specifies the device path of the storage device. This example uses the device <em class="replaceable"><code>/dev/sdb</code></em>.
+ </div></dd><dt class="varlistentry"><span class="term"><target> <path><em class="replaceable"><code>/dev</code></em></path></target></span></dt><dd><div class="para">
+ The file system <em class="parameter"><code>target</code></em> parameter with the <em class="parameter"><code>path</code></em> sub-parameter determines the location on the host file system to attach volumes created with this storage pool.
+ </div><div class="para">
+ For example, sdb1, sdb2, sdb3. Using <em class="replaceable"><code>/dev/</code></em>, as in the example below, means volumes created from this storage pool can be accessed as <em class="replaceable"><code>/dev</code></em>/sdb1, <em class="replaceable"><code>/dev</code></em>/sdb2, <em class="replaceable"><code>/dev</code></em>/sdb3.
+ </div></dd><dt class="varlistentry"><span class="term"><format type='<em class="replaceable"><code>gpt</code></em>'/></span></dt><dd><div class="para">
+ The <em class="parameter"><code>format</code></em> parameter specifies the partition table type. This example uses the <em class="replaceable"><code>gpt</code></em> in the example below, to match the GPT disk label type created in the previous step.
+ </div></dd></dl></div><div class="para">
+ Create the XML file for the storage pool device with a text editor.
+ </div><div class="example"><h6>Example 27.2. Disk based storage device storage pool</h6><div class="example-contents"><pre class="screen">
+<pool type='disk'>
+ <name><em class="replaceable"><code>guest_images_disk</code></em></name>
+ <source>
+ <device path='<em class="replaceable"><code>/dev/sdb</code></em>'/>
+ <format type='<em class="replaceable"><code>gpt</code></em>'/>
+ </source>
+ <target>
+ <path><em class="replaceable"><code>/dev</code></em></path>
+ </target>
+</pool>
+</pre></div></div><br class="example-break" /></li><li class="step"><p class="title"><strong>Attach the device</strong></p><div class="para">
+ Add the storage pool definition using the <code class="command">virsh pool-define</code> command with the XML configuration file created in the previous step.
+ </div><pre class="screen"># virsh pool-define ~/guest_images_disk.xml
+Pool guest_images_disk defined from /root/guest_images_disk.xml
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_disk inactive no
+</pre></li><li class="step"><p class="title"><strong>Start the storage pool</strong></p><div class="para">
+ Start the storage pool with the <code class="command">virsh pool-start</code> command. Verify the pool is started with the <code class="command">virsh pool-list --all</code> command.
+ </div><pre class="screen"># virsh pool-start <em class="replaceable"><code>guest_images_disk</code></em>
+Pool guest_images_disk started
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_disk active no
+</pre></li><li class="step"><p class="title"><strong>Turn on autostart</strong></p><div class="para">
+ Turn on <em class="parameter"><code>autostart</code></em> for the storage pool. Autostart configures the <code class="systemitem">libvirtd</code> service to start the storage pool when the service starts.
+ </div><pre class="screen"># virsh pool-autostart <em class="replaceable"><code>guest_images_disk</code></em>
+Pool guest_images_disk marked as autostarted
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_disk active yes
+</pre></li><li class="step"><p class="title"><strong>Verify the storage pool configuration</strong></p><div class="para">
+ Verify the storage pool was created correctly, the sizes reported correctly, and the state reports as <code class="computeroutput">running</code>.
+ </div><pre class="screen"># virsh pool-info <em class="replaceable"><code>guest_images_disk</code></em>
+Name: guest_images_disk
+UUID: 551a67c8-5f2a-012c-3844-df29b167431c
+State: running
+Capacity: 465.76 GB
+Allocation: 0.00
+Available: 465.76 GB
+# ls -la /dev/sdb
+brw-rw----. 1 root disk 8, 16 May 30 14:08 /dev/sdb
+# virsh vol-list guest_images_disk
+Name Path
+-----------------------------------------
+</pre></li><li class="step"><p class="title"><strong>Optional: Remove the temporary configuration file</strong></p><div class="para">
+ Remove the temporary storage pool XML configuration file if it is not needed.
+ </div><pre class="screen"># rm ~/<em class="replaceable"><code>guest_images_disk</code></em>.xml</pre></li></ol></div><div class="para">
+ A disk based storage pool is now available.
+ </div></div><div class="section" id="delete-ded-disk-storage-pool"><div class="titlepage"><div><div><h4 class="title">27.1.1.2. Deleting a storage pool using virsh</h4></div></div></div><div class="para">
+ The following demonstrates how to delete a storage pool using virsh:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it.
+ </div><pre class="screen"># virsh pool-destroy <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Remove the storage pool's definition
+ </div><pre class="screen"># virsh pool-undefine <em class="replaceable"><code>guest_images_disk</code></em></pre></li></ol></div></div></div><div xml:lang="en-US" class="section" id="sect-Virtualization-Storage_Pools-Creating-File_Systems" lang="en-US"><div class="titlepage"><div><div><h3 class="title">27.1.2. Partition-based storage pools</h3></div></div></div><div class="para">
+ This section covers using a pre-formatted block device, a partition, as a storage pool.
+ </div><div class="para">
+ For the following examples, a host has a 500GB hard drive (<code class="systemitem">/dev/sdc</code>) partitioned into one 500GB, ext4 formatted partition (<code class="systemitem">/dev/sdc1</code>). We set up a storage pool for it using the procedure below.
+ </div><div class="section" id="create-part-stor-pool"><div class="titlepage"><div><div><h4 class="title">27.1.2.1. Creating a partition-based storage pool using virt-manager</h4></div></div></div><div class="para">
+ This procedure creates a new storage pool using a partition of a storage device.
+ </div><div class="procedure"><h6>Procedure 27.1. Creating a partition-based storage pool with virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Open the storage pool settings</strong></p><ol class="a"><li class="step"><div class="para">
+ In the <code class="command">virt-manager</code> graphical interface, select the host from the main window.
+ </div><div class="para">
+ Open the <span class="guilabel"><strong>Edit</strong></span> menu and select <span class="guilabel"><strong>Connection Details</strong></span>
+ </div><div class="figure" id="connection_details"><div class="figure-contents"><div class="mediaobject"><img src="images/Connection_Details.png" width="444" alt="Connection Details" /></div></div><h6>Figure 27.1. Connection Details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Click on the <span class="guilabel"><strong>Storage</strong></span> tab of the <span class="guilabel"><strong>Connection Details</strong></span> window.
+ </div><div class="figure" id="storage-tab"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Storage tab" /></div></div><h6>Figure 27.2. Storage tab</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Create the new storage pool</strong></p><ol class="a"><li class="step"><p class="title"><strong>Add a new pool (part 1)</strong></p><div class="para">
+ Press the <span class="guilabel"><strong>+</strong></span> button (the add pool button). The <span class="guilabel"><strong>Add a New Storage Pool</strong></span> wizard appears.
+ </div><div class="para">
+ Choose a <span class="guibutton"><strong>Name</strong></span> for the storage pool. This example uses the name <em class="replaceable"><code>guest_images_fs</code></em>. Change the <span class="guibutton"><strong>Type</strong></span> to <code class="command">fs: Pre-Formatted Block Device</code>.
+ </div><div class="figure" id="name-and-type"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_fs_step_1_name_and_type.png" width="444" alt="Storage pool name and type" /></div></div><h6>Figure 27.3. Storage pool name and type</h6></div><br class="figure-break" /><div class="para">
+ Press the <span class="guibutton"><strong>Forward</strong></span> button to continue.
+ </div></li><li class="step"><p class="title"><strong>Add a new pool (part 2)</strong></p><div class="para">
+ Change the <span class="guibutton"><strong>Target Path</strong></span>, <span class="guibutton"><strong>Format</strong></span>, and <span class="guibutton"><strong>Source Path</strong></span> fields.
+ </div><div class="figure" id="path-and-format"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_fs_step_2_paths_and_format.png" width="444" alt="Storage pool path and format" /></div></div><h6>Figure 27.4. Storage pool path and format</h6></div><br class="figure-break" /><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Target Path</span></dt><dd><div class="para">
+ Enter the location to mount the source device for the storage pool in the <span class="guibutton"><strong>Target Path</strong></span> field. If the location does not already exist, <code class="command">virt-manager</code> will create the directory.
+ </div></dd><dt class="varlistentry"><span class="term">Format</span></dt><dd><div class="para">
+ Select a format from the <span class="guibutton"><strong>Format</strong></span> list. The device is formatted with the selected format.
+ </div><div class="para">
+ This example uses the <em class="replaceable"><code>ext4</code></em> file system, the default Fedora file system.
+ </div></dd><dt class="varlistentry"><span class="term">Source Path</span></dt><dd><div class="para">
+ Enter the device in the <code class="command">Source Path</code> field.
+ </div><div class="para">
+ This example uses the <em class="replaceable"><code>/dev/sdc1</code></em> device.
+ </div></dd></dl></div><div class="para">
+ Verify the details and press the <span class="guibutton"><strong>Finish</strong></span> button to create the storage pool.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Verify the new storage pool</strong></p><div class="para">
+ The new storage pool appears in the storage list on the left after a few seconds. Verify the size is reported as expected, <em class="replaceable"><code>458.20 GB Free</code></em> in this example. Verify the <span class="guibutton"><strong>State</strong></span> field reports the new storage pool as <em class="replaceable"><code>Active</code></em>.
+ </div><div class="para">
+ Select the storage pool. In the <span class="guibutton"><strong>Autostart</strong></span> field, click the <span class="guibutton"><strong>On Boot</strong></span> checkbox. This will make sure the storage device starts whenever the <code class="systemitem">libvirtd</code> service starts.
+ </div><div class="figure" id="confirmation"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_fs_step_3_result.png" width="444" alt="Storage list confirmation" /></div></div><h6>Figure 27.5. Storage list confirmation</h6></div><br class="figure-break" /><div class="para">
+ The storage pool is now created, close the <span class="guilabel"><strong>Connection Details</strong></span> window.
+ </div></li></ol></div></div><div class="section" id="del-stor-pool-vmana-part"><div class="titlepage"><div><div><h4 class="title">27.1.2.2. Deleting a storage pool using virt-manager</h4></div></div></div><div class="para">
+ This procedure demonstrates how to delete a storage pool.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it. To do this, select the storage pool you want to stop and click the red X icon at the bottom of the Storage window.
+ </div><div class="figure" id="stop-icon"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Stop Icon" /></div></div><h6>Figure 27.6. Stop Icon</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Delete the storage pool by clicking the Trash can icon. This icon is only enabled if you stop the storage pool first.
+ </div></li></ol></div></div><div class="section" id="idm104698080"><div class="titlepage"><div><div><h4 class="title" id="idm104698080">27.1.2.3. Creating a partition-based storage pool using virsh</h4></div></div></div><div class="para">
+ This section covers creating a partition-based storage pool with the <code class="command">virsh</code> command.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Do not use this procedure to assign an entire disk as a storage pool (for example, <code class="filename">/dev/sdb</code>). Guests should not be given write access to whole disks or block devices. Only use this method to assign partitions (for example, <code class="filename">/dev/sdb1</code>) to storage pools.
+ </div></div></div><div class="procedure"><h6>Procedure 27.2. Creating pre-formatted block device storage pools using virsh</h6><ol class="1"><li class="step"><p class="title"><strong> Create the storage pool definition </strong></p><div class="para">
+ Use the virsh <code class="command">pool-define-as</code> command to create a new storage pool definition. There are three options that must be provided to define a pre-formatted disk as a storage pool:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Partition name</span></dt><dd><div class="para">
+ The <em class="parameter"><code>name</code></em> parameter determines the name of the storage pool. This example uses the name <em class="replaceable"><code>guest_images_fs</code></em> in the example below.
+ </div></dd><dt class="varlistentry"><span class="term">device</span></dt><dd><div class="para">
+ The <em class="parameter"><code>device</code></em> parameter with the <em class="parameter"><code>path</code></em> attribute specifies the device path of the storage device. This example uses the partition <em class="replaceable"><code>/dev/sdc1</code></em>.
+ </div></dd><dt class="varlistentry"><span class="term">mountpoint</span></dt><dd><div class="para">
+ The <em class="parameter"><code>mountpoint</code></em> on the local file system where the formatted device will be mounted. If the mount point directory does not exist, the <code class="command">virsh</code> command can create the directory.
+ </div><div class="para">
+ The directory <em class="replaceable"><code>/guest_images</code></em> is used in this example.
+ </div></dd></dl></div><pre class="screen"># virsh pool-define-as <em class="replaceable"><code>guest_images_fs</code></em> fs - - <em class="replaceable"><code>/dev/sdc1</code></em> - "<em class="replaceable"><code>/guest_images</code></em>"
+Pool guest_images_fs defined
+</pre><div class="para">
+ The new pool and mount points are now created.
+ </div></li><li class="step"><p class="title"><strong>Verify the new pool</strong></p><div class="para">
+ List the present storage pools.
+ </div><pre class="screen">
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+<em class="replaceable"><code>guest_images_fs</code></em> inactive no
+</pre></li><li class="step"><p class="title"><strong> Create the mount point </strong></p><div class="para">
+ Use the <code class="command">virsh pool-build</code> command to create a mount point for a pre-formatted file system storage pool.
+ </div><pre class="screen">
+# virsh pool-build <em class="replaceable"><code>guest_images_fs</code></em>
+Pool guest_images_fs built
+# ls -la /<em class="replaceable"><code>guest_images</code></em>
+total 8
+drwx------. 2 root root 4096 May 31 19:38 .
+dr-xr-xr-x. 25 root root 4096 May 31 19:38 ..
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_fs inactive no
+</pre></li><li class="step"><p class="title"><strong> Start the storage pool </strong></p><div class="para">
+ Use the <code class="command">virsh pool-start</code> command to mount the file system onto the mount point and make the pool available for use.
+ </div><pre class="screen">
+# virsh pool-start <em class="replaceable"><code>guest_images_fs</code></em>
+Pool guest_images_fs started
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_fs active no
+</pre></li><li class="step"><p class="title"><strong> Turn on autostart </strong></p><div class="para">
+ By default, a storage pool is defined with <code class="command">virsh</code> is not set to automatically start each time <code class="systemitem">libvirtd</code> starts. Turn on automatic start with the <code class="command">virsh pool-autostart</code> command. The storage pool is now automatically started each time <code class="systemitem">libvirtd</code> starts.
+ </div><pre class="screen">
+# virsh pool-autostart <em class="replaceable"><code>guest_images_fs</code></em>
+Pool guest_images_fs marked as autostarted
+
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_fs active yes
+</pre></li><li class="step"><p class="title"><strong> Verify the storage pool </strong></p><div class="para">
+ Verify the storage pool was created correctly, the sizes reported are as expected, and the state is reported as <code class="command">running</code>. Verify there is a "lost+found" directory in the mount point on the file system, indicating the device is mounted.
+ </div><pre class="screen">
+# virsh pool-info <em class="replaceable"><code>guest_images_fs</code></em>
+Name: guest_images_fs
+UUID: c7466869-e82a-a66c-2187-dc9d6f0877d0
+State: running
+Persistent: yes
+Autostart: yes
+Capacity: 458.39 GB
+Allocation: 197.91 MB
+Available: 458.20 GB
+# mount | grep /guest_images
+/dev/sdc1 on /guest_images type ext4 (rw)
+# ls -la /guest_images
+total 24
+drwxr-xr-x. 3 root root 4096 May 31 19:47 .
+dr-xr-xr-x. 25 root root 4096 May 31 19:38 ..
+drwx------. 2 root root 16384 May 31 14:18 lost+found
+</pre></li></ol></div></div><div class="section" id="delete-ded-part-storage-pool-virsh"><div class="titlepage"><div><div><h4 class="title">27.1.2.4. Deleting a storage pool using virsh</h4></div></div></div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it.
+ </div><pre class="screen"># virsh pool-destroy <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Optionally, if you want to remove the directory where the storage pool resides use the following command:
+ </div><pre class="screen"># virsh pool-delete <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Remove the storage pool's definition
+ </div><pre class="screen"># virsh pool-undefine <em class="replaceable"><code>guest_images_disk</code></em></pre></li></ol></div></div></div><div xml:lang="en-US" class="section" id="sect-Virtualization-Storage_Pools-Creating-Local_Directories" lang="en-US"><div class="titlepage"><div><div><h3 class="title">27.1.3. Directory-based storage pools</h3></div></div></div><div class="para">
+ This section covers storing guests in a directory on the host.
+ </div><div class="para">
+ Directory-based storage pools can be created with <code class="command">virt-manager</code> or the <code class="command">virsh</code> command line tools.
+ </div><div class="section" id="idm75859568"><div class="titlepage"><div><div><h4 class="title" id="idm75859568">27.1.3.1. Creating a directory-based storage pool with virt-manager</h4></div></div></div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Create the local directory</strong></p><ol class="a"><li class="step"><p class="title"><strong>Optional: Create a new directory for the storage pool</strong></p><div class="para">
+ Create the directory on the host for the storage pool. This example uses a directory named <em class="replaceable"><code>/guest_images</code></em>.
+ </div><pre class="screen"># mkdir <em class="replaceable"><code>/guest_images</code></em></pre></li><li class="step"><p class="title"><strong>Set directory ownership</strong></p><div class="para">
+ Change the user and group ownership of the directory. The directory must be owned by the root user.
+ </div><pre class="screen"># chown root:root <em class="replaceable"><code>/guest_images</code></em></pre></li><li class="step"><p class="title"><strong>Set directory permissions</strong></p><div class="para">
+ Change the file permissions of the directory.
+ </div><pre class="screen"># chmod 700 <em class="replaceable"><code>/guest_images</code></em></pre></li><li class="step"><p class="title"><strong>Verify the changes</strong></p><div class="para">
+ Verify the permissions were modified. The output shows a correctly configured empty directory.
+ </div><pre class="screen"># ls -la <em class="replaceable"><code>/guest_images</code></em>
+total 8
+drwx------. 2 root root 4096 May 28 13:57 .
+dr-xr-xr-x. 26 root root 4096 May 28 13:57 ..
+</pre></li></ol></li><li class="step"><p class="title"><strong>Configure SELinux file contexts</strong></p><div class="para">
+ Configure the correct SELinux context for the new directory. Note that the name of the pool and the directory do not have to match. However, when you shutdown the guest virtual machine, libvirt has to set the context back to a default value. The context of the directory determines what this default value is. It is worth explicitly labelling the directory virt_image_t, so that when the guest virtual machine is shutdown, the images get labeled 'virt_image_t' and are thus isolated from other processes running on the host.
+ </div><pre class="screen">
+# semanage fcontext -a -t virt_image_t '/guest_images(/.*)?'
+# restorecon -R /guest_images
+</pre></li><li class="step"><p class="title"><strong>Open the storage pool settings</strong></p><ol class="a"><li class="step"><div class="para">
+ In the <code class="command">virt-manager</code> graphical interface, select the host from the main window.
+ </div><div class="para">
+ Open the <span class="guilabel"><strong>Edit</strong></span> menu and select <span class="guilabel"><strong>Connection Details</strong></span>
+ </div><div class="figure" id="conn-details-screenshot"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_select_host.png" width="444" alt="Connection details window" /></div></div><h6>Figure 27.7. Connection details window</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Click on the <span class="guilabel"><strong>Storage</strong></span> tab of the <span class="guilabel"><strong>Connection Details</strong></span> window.
+ </div><div class="figure" id="host-details-screenshot-storagepools-dir"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Storage tab" /></div></div><h6>Figure 27.8. Storage tab</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Create the new storage pool</strong></p><ol class="a"><li class="step"><p class="title"><strong>Add a new pool (part 1)</strong></p><div class="para">
+ Press the <span class="guilabel"><strong>+</strong></span> button (the add pool button). The <span class="guilabel"><strong>Add a New Storage Pool</strong></span> wizard appears.
+ </div><div class="para">
+ Choose a <span class="guibutton"><strong>Name</strong></span> for the storage pool. This example uses the name <em class="replaceable"><code>guest_images</code></em>. Change the <span class="guibutton"><strong>Type</strong></span> to <code class="command">dir: Filesystem Directory</code>.
+ </div><div class="figure" id="screenshot-pick-pool-name"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_dir_step_1_name_and_type.png" width="444" alt="Name the storage pool" /></div></div><h6>Figure 27.9. Name the storage pool</h6></div><br class="figure-break" /><div class="para">
+ Press the <span class="guibutton"><strong>Forward</strong></span> button to continue.
+ </div></li><li class="step"><p class="title"><strong>Add a new pool (part 2)</strong></p><div class="para">
+ Change the <span class="guibutton"><strong>Target Path</strong></span> field. For example, <em class="replaceable"><code>/guest_images</code></em>.
+ </div><div class="para">
+ Verify the details and press the <span class="guibutton"><strong>Finish</strong></span> button to create the storage pool.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Verify the new storage pool</strong></p><div class="para">
+ The new storage pool appears in the storage list on the left after a few seconds. Verify the size is reported as expected, <em class="replaceable"><code>36.41 GB Free</code></em> in this example. Verify the <span class="guibutton"><strong>State</strong></span> field reports the new storage pool as <em class="replaceable"><code>Active</code></em>.
+ </div><div class="para">
+ Select the storage pool. In the <span class="guibutton"><strong>Autostart</strong></span> field, confirm that the <span class="guibutton"><strong>On Boot</strong></span> checkbox is checked. This will make sure the storage pool starts whenever the <code class="systemitem">libvirtd</code> service starts.
+ </div><div class="figure" id="verify-pool-screenshot"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_dir_step_3_result.png" width="444" alt="Verify the storage pool information" /></div></div><h6>Figure 27.10. Verify the storage pool information</h6></div><br class="figure-break" /><div class="para">
+ The storage pool is now created, close the <span class="guilabel"><strong>Connection Details</strong></span> window.
+ </div></li></ol></div></div><div class="section" id="del-stor-pool-dir"><div class="titlepage"><div><div><h4 class="title">27.1.3.2. Deleting a storage pool using virt-manager</h4></div></div></div><div class="para">
+ This procedure demonstrates how to delete a storage pool.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it. To do this, select the storage pool you want to stop and click the red X icon at the bottom of the Storage window.
+ </div><div class="figure" id="stop-icon2"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Stop Icon" /></div></div><h6>Figure 27.11. Stop Icon</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Delete the storage pool by clicking the Trash can icon. This icon is only enabled if you stop the storage pool first.
+ </div></li></ol></div></div><div class="section" id="idm112732384"><div class="titlepage"><div><div><h4 class="title" id="idm112732384">27.1.3.3. Creating a directory-based storage pool with virsh</h4></div></div></div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong> Create the storage pool definition </strong></p><div class="para">
+ Use the <code class="command">virsh pool-define-as</code> command to define a new storage pool. There are two options required for creating directory-based storage pools:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <code class="command">name</code> of the storage pool.
+ </div><div class="para">
+ This example uses the name <em class="replaceable"><code>guest_images</code></em>. All further <code class="command">virsh</code> commands used in this example use this name.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="command">path</code> to a file system directory for storing guest image files. If this directory does not exist, <code class="command">virsh</code> will create it.
+ </div><div class="para">
+ This example uses the <em class="replaceable"><code>/guest_images</code></em> directory.
+ </div></li></ul></div><pre class="screen"> # virsh pool-define-as <em class="replaceable"><code>guest_images</code></em> dir - - - - "<em class="replaceable"><code>/guest_images</code></em>"
+Pool guest_images defined</pre></li><li class="step"><p class="title"><strong>Verify the storage pool is listed</strong></p><div class="para">
+ Verify the storage pool object is created correctly and the state reports it as <code class="computeroutput">inactive</code>.
+ </div><pre class="screen"># virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images inactive no</pre></li><li class="step"><p class="title"><strong> Create the local directory </strong></p><div class="para">
+ Use the <code class="command">virsh pool-build</code> command to build the directory-based storage pool for the directory <em class="replaceable"><code>guest_images</code></em> (for example), as shown:
+ </div><pre class="screen"># virsh pool-build <em class="replaceable"><code>guest_images</code></em>
+Pool guest_images built
+# ls -la /<em class="replaceable"><code>guest_images</code></em>
+total 8
+drwx------. 2 root root 4096 May 30 02:44 .
+dr-xr-xr-x. 26 root root 4096 May 30 02:44 ..
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images inactive no</pre></li><li class="step"><p class="title"><strong>Start the storage pool</strong></p><div class="para">
+ Use the virsh command <code class="command">pool-start</code> to enable a directory storage pool, thereby allowing allowing volumes of the pool to be used as guest disk images.
+ </div><pre class="screen"># virsh pool-start <em class="replaceable"><code>guest_images</code></em>
+Pool guest_images started
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images active no
+</pre></li><li class="step"><p class="title"><strong>Turn on autostart</strong></p><div class="para">
+ Turn on <em class="parameter"><code>autostart</code></em> for the storage pool. Autostart configures the <code class="systemitem">libvirtd</code> service to start the storage pool when the service starts.
+ </div><pre class="screen"># virsh pool-autostart <em class="replaceable"><code>guest_images</code></em>
+Pool guest_images marked as autostarted
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images active yes
+</pre></li><li class="step"><p class="title"><strong>Verify the storage pool configuration</strong></p><div class="para">
+ Verify the storage pool was created correctly, the size is reported correctly, and the state is reported as <code class="computeroutput">running</code>. If you want the pool to be accessible even if the guest is not running, make sure that <code class="computeroutput">Persistent</code> is reported as <code class="computeroutput">yes</code>. If you want the pool to start automatically when the service starts, make sure that <code class="computeroutput">Autostart</code> is reported as <code class="computeroutput">yes</code>.
+ </div><pre class="screen"># virsh pool-info <em class="replaceable"><code>guest_images</code></em>
+Name: guest_images
+UUID: 779081bf-7a82-107b-2874-a19a9c51d24c
+State: running
+Persistent: yes
+Autostart: yes
+Capacity: 49.22 GB
+Allocation: 12.80 GB
+Available: 36.41 GB
+
+# ls -la /guest_images
+total 8
+drwx------. 2 root root 4096 May 30 02:44 .
+dr-xr-xr-x. 26 root root 4096 May 30 02:44 ..
+#
+</pre></li></ol></div><div class="para">
+ A directory-based storage pool is now available.
+ </div></div><div class="section" id="delete-dir-storage-pool-virsh"><div class="titlepage"><div><div><h4 class="title">27.1.3.4. Deleting a storage pool using virsh</h4></div></div></div><div class="para">
+ The following demonstrates how to delete a storage pool using virsh:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it.
+ </div><pre class="screen"># virsh pool-destroy <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Optionally, if you want to remove the directory where the storage pool resides use the following command:
+ </div><pre class="screen"># virsh pool-delete <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Remove the storage pool's definition
+ </div><pre class="screen"># virsh pool-undefine <em class="replaceable"><code>guest_images_disk</code></em></pre></li></ol></div></div></div><div xml:lang="en-US" class="section" id="sect-Virtualization-Storage_Pools-Creating-LVM" lang="en-US"><div class="titlepage"><div><div><h3 class="title">27.1.4. LVM-based storage pools</h3></div></div></div><div class="para">
+ This chapter covers using LVM volume groups as storage pools.
+ </div><div class="para">
+ LVM-based storage groups provide the full flexibility of LVM.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Please refer to the <em class="citetitle">Fedora Storage Administration Guide</em> for more details on LVM.
+ </div></div></div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ LVM-based storage pools require a full disk partition. If activating a new partition/device with these procedures, the partition will be formatted and all data will be erased. If using the host's existing Volume Group (VG) nothing will be erased. It is recommended to back up the storage device before commencing the following procedure.
+ </div></div></div><div class="section" id="idm76640480"><div class="titlepage"><div><div><h4 class="title" id="idm76640480">27.1.4.1. Creating an LVM-based storage pool with virt-manager</h4></div></div></div><div class="para">
+ LVM-based storage pools can use existing LVM volume groups or create new LVM volume groups on a blank partition.
+ </div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Optional: Create new partition for LVM volumes</strong></p><div class="para">
+ These steps describe how to create a new partition and LVM volume group on a new hard disk drive.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ This procedure will remove all data from the selected storage device.
+ </div></div></div><ol class="a"><li class="step"><p class="title"><strong>Create a new partition</strong></p><div class="para">
+ Use the <code class="command">fdisk</code> command to create a new disk partition from the command line. The following example creates a new partition that uses the entire disk on the storage device <code class="computeroutput">/dev/sdb</code>.
+ </div><pre class="screen"># fdisk /dev/sdb
+Command (m for help):
+</pre><div class="para">
+ Press <em class="parameter"><code>n</code></em> for a new partition.
+ </div></li><li class="step"><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 class="step"><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 class="step"><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 class="step"><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 class="step"><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 class="step"><div class="para">
+ Choose the partition you created in the previous steps. In this example, the partition number is <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 class="step"><div class="para">
+ Enter <em class="parameter"><code>8e</code></em> for a Linux LVM partition.
+ </div><pre class="screen">Hex code (type L to list codes): <em class="parameter"><code>8e</code></em>
+</pre></li><li class="step"><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 class="step"><p class="title"><strong>Create a new LVM volume group</strong></p><div class="para">
+ Create a new LVM volume group with the <code class="command">vgcreate</code> command. This example creates a volume group named <em class="replaceable"><code>guest_images_lvm</code></em>.
+ </div><pre class="screen"># vgcreate <em class="replaceable"><code>guest_images_lvm</code></em> /dev/sdb1
+ Physical volume "/dev/vdb1" successfully created
+ Volume group "<em class="replaceable"><code>guest_images_lvm</code></em>" successfully created
+</pre></li></ol><div class="para">
+ The new LVM volume group, <em class="replaceable"><code>guest_images_lvm</code></em>, can now be used for an LVM-based storage pool.
+ </div></li><li class="step"><p class="title"><strong>Open the storage pool settings</strong></p><ol class="a"><li class="step"><div class="para">
+ In the <code class="command">virt-manager</code> graphical interface, select the host from the main window.
+ </div><div class="para">
+ Open the <span class="guilabel"><strong>Edit</strong></span> menu and select <span class="guilabel"><strong>Connection Details</strong></span>
+ </div><div class="figure" id="connection-details"><div class="figure-contents"><div class="mediaobject"><img src="images/Connection_Details.png" width="444" alt="Connection details" /></div></div><h6>Figure 27.12. Connection details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Click on the <span class="guilabel"><strong>Storage</strong></span> tab.
+ </div><div class="figure" id="lvm-storage-tab"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Storage tab" /></div></div><h6>Figure 27.13. Storage tab</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Create the new storage pool</strong></p><ol class="a"><li class="step"><p class="title"><strong>Start the Wizard</strong></p><div class="para">
+ Press the <span class="guilabel"><strong>+</strong></span> button (the add pool button). The <span class="guilabel"><strong>Add a New Storage Pool</strong></span> wizard appears.
+ </div><div class="para">
+ Choose a <span class="guibutton"><strong>Name</strong></span> for the storage pool. We use <em class="replaceable"><code>guest_images_lvm</code></em> for this example. Then change the <span class="guibutton"><strong>Type</strong></span> to <code class="command">logical: LVM Volume Group</code>, and
+ </div><div class="figure" id="lvm-add"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_lvm_step_1_name_and_type.png" width="444" alt="Add LVM storage pool" /></div></div><h6>Figure 27.14. Add LVM storage pool</h6></div><br class="figure-break" /><div class="para">
+ Press the <span class="guibutton"><strong>Forward</strong></span> button to continue.
+ </div></li><li class="step"><p class="title"><strong>Add a new pool (part 2)</strong></p><div class="para">
+ Change the <span class="guibutton"><strong>Target Path</strong></span> field. This example uses <em class="replaceable"><code>/guest_images</code></em>.
+ </div><div class="para">
+ Now fill in the <span class="guibutton"><strong>Target Path</strong></span> and <span class="guibutton"><strong>Source Path</strong></span> fields, then tick the <span class="guibutton"><strong>Build Pool</strong></span> check box.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Use the <span class="guibutton"><strong>Target Path</strong></span> field to <span class="emphasis"><em>either</em></span> select an existing LVM volume group or as the name for a new volume group. The default format is <code class="computeroutput">/dev/</code><em class="replaceable"><code>storage_pool_name</code></em>.
+ </div><div class="para">
+ This example uses a new volume group named <em class="replaceable"><code>/dev/guest_images_lvm</code></em>.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="command">Source Path</code> field is optional if an existing LVM volume group is used in the <span class="guibutton"><strong>Target Path</strong></span>.
+ </div><div class="para">
+ For new LVM volume groups, input the location of a storage device in the <code class="command">Source Path</code> field. This example uses a blank partition <em class="replaceable"><code>/dev/sdc</code></em>.
+ </div></li><li class="listitem"><div class="para">
+ The <span class="guibutton"><strong>Build Pool</strong></span> checkbox instructs <code class="command">virt-manager</code> to create a new LVM volume group. If you are using an existing volume group you should not select the <span class="guibutton"><strong>Build Pool</strong></span> checkbox.
+ </div><div class="para">
+ This example is using a blank partition to create a new volume group so the <span class="guibutton"><strong>Build Pool</strong></span> checkbox must be selected.
+ </div></li></ul></div><div class="figure" id="lvm-pool-step2"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_lvm_step_2a_paths_and_pool.png" width="444" alt="Add target and source" /></div></div><h6>Figure 27.15. Add target and source</h6></div><br class="figure-break" /><div class="para">
+ Verify the details and press the <span class="guibutton"><strong>Finish</strong></span> button format the LVM volume group and create the storage pool.
+ </div></li><li class="step"><p class="title"><strong>Confirm the device to be formatted</strong></p><div class="para">
+ A warning message appears.
+ </div><div class="figure" id="lvm-warning-message"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_lvm_step_2b_format_warning.png" alt="Warning message" /></div></div><h6>Figure 27.16. Warning message</h6></div><br class="figure-break" /><div class="para">
+ Press the <span class="guilabel"><strong>Yes</strong></span> button to proceed to erase all data on the storage device and create the storage pool.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Verify the new storage pool</strong></p><div class="para">
+ The new storage pool will appear in the list on the left after a few seconds. Verify the details are what you expect, <em class="replaceable"><code>465.76 GB Free</code></em> in our example. Also verify the <span class="guibutton"><strong>State</strong></span> field reports the new storage pool as <em class="replaceable"><code>Active</code></em>.
+ </div><div class="para">
+ It is generally a good idea to have the <span class="guibutton"><strong>Autostart</strong></span> check box enabled, to ensure the storage pool starts automatically with libvirtd.
+ </div><div class="figure" id="confirm-lvm-pool"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_lvm_step_3_result.png" width="444" alt="Confirm LVM storage pool details" /></div></div><h6>Figure 27.17. Confirm LVM storage pool details</h6></div><br class="figure-break" /><div class="para">
+ Close the Host Details dialog, as the task is now complete.
+ </div></li></ol></div></div><div class="section" id="del-stor-pool-lvm"><div class="titlepage"><div><div><h4 class="title">27.1.4.2. Deleting a storage pool using virt-manager</h4></div></div></div><div class="para">
+ This procedure demonstrates how to delete a storage pool.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it. To do this, select the storage pool you want to stop and click the red X icon at the bottom of the Storage window.
+ </div><div class="figure" id="stop-icon3"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Stop Icon" /></div></div><h6>Figure 27.18. Stop Icon</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Delete the storage pool by clicking the Trash can icon. This icon is only enabled if you stop the storage pool first.
+ </div></li></ol></div></div><div class="section" id="idm99828496"><div class="titlepage"><div><div><h4 class="title" id="idm99828496">27.1.4.3. Creating an LVM-based storage pool with virsh</h4></div></div></div><div class="para">
+ This section outlines the steps required to create an LVM-based storage pool with the <code class="command">virsh</code> command. It uses the example of a pool named <span class="bold bold"><strong>guest_images_lvm</strong></span> from a single drive (<code class="filename">/dev/sdc</code>). This is only an example and your settings should be substituted as appropriate.
+ </div><div class="procedure"><h6>Procedure 27.3. Creating an LVM-based storage pool with virsh</h6><ol class="1"><li class="step"><div class="para">
+ Define the pool name <span class="bold bold"><strong>guest_images_lvm</strong></span>.
+ </div><pre class="screen"># virsh pool-define-as <em class="replaceable"><code>guest_images_lvm</code></em> logical - - <em class="replaceable"><code>/dev/sdc</code></em> <em class="replaceable"><code>libvirt_lvm</code></em> \ /dev/<em class="replaceable"><code>libvirt_lvm</code></em>
+Pool guest_images_lvm defined
+</pre></li><li class="step"><div class="para">
+ Build the pool according to the specified name.
+ </div><pre class="screen">
+# virsh pool-build <em class="replaceable"><code>guest_images_lvm</code></em>
+
+Pool guest_images_lvm built
+</pre></li><li class="step"><div class="para">
+ Initialize the new pool.
+ </div><pre class="screen">
+# virsh pool-start <em class="replaceable"><code>guest_images_lvm</code></em>
+
+Pool guest_images_lvm started
+</pre></li><li class="step"><div class="para">
+ Show the volume group information with the <code class="command">vgs</code> command.
+ </div><pre class="screen">
+# vgs
+VG #PV #LV #SN Attr VSize VFree
+libvirt_lvm 1 0 0 wz--n- 465.76g 465.76g
+</pre></li><li class="step"><div class="para">
+ Set the pool to start automatically.
+ </div><pre class="screen">
+# virsh pool-autostart <em class="replaceable"><code>guest_images_lvm</code></em>
+Pool guest_images_lvm marked as autostarted
+</pre></li><li class="step"><div class="para">
+ List the available pools with the <code class="command">virsh</code> command.
+ </div><pre class="screen">
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_lvm active yes
+</pre></li><li class="step"><div class="para">
+ The following commands demonstrate the creation of three volumes (<span class="emphasis"><em>volume1</em></span>, <span class="emphasis"><em>volume2</em></span> and <span class="emphasis"><em>volume3</em></span>) within this pool.
+ </div><pre class="screen">
+# virsh vol-create-as <em class="replaceable"><code>guest_images_lvm</code></em> <em class="replaceable"><code>volume1</code></em> <em class="replaceable"><code>8G</code></em>
+Vol volume1 created
+
+# virsh vol-create-as <em class="replaceable"><code>guest_images_lvm</code></em> <em class="replaceable"><code>volume2</code></em> <em class="replaceable"><code>8G</code></em>
+Vol volume2 created
+
+# virsh vol-create-as <em class="replaceable"><code>guest_images_lvm</code></em> <em class="replaceable"><code>volume3</code></em> <em class="replaceable"><code>8G</code></em>
+Vol volume3 created
+</pre></li><li class="step"><div class="para">
+ List the available volumes in this pool with the <code class="command">virsh</code> command.
+ </div><pre class="screen">
+# virsh vol-list <em class="replaceable"><code>guest_images_lvm</code></em>
+Name Path
+-----------------------------------------
+volume1 /dev/libvirt_lvm/volume1
+volume2 /dev/libvirt_lvm/volume2
+volume3 /dev/libvirt_lvm/volume3
+</pre></li><li class="step"><div class="para">
+ The following two commands (<code class="command">lvscan</code> and <code class="command">lvs</code>) display further information about the newly created volumes.
+ </div><pre class="screen">
+# lvscan
+ACTIVE '/dev/libvirt_lvm/volume1' [8.00 GiB] inherit
+ACTIVE '/dev/libvirt_lvm/volume2' [8.00 GiB] inherit
+ACTIVE '/dev/libvirt_lvm/volume3' [8.00 GiB] inherit
+
+# lvs
+LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
+volume1 libvirt_lvm -wi-a- 8.00g
+volume2 libvirt_lvm -wi-a- 8.00g
+volume3 libvirt_lvm -wi-a- 8.00g
+</pre></li></ol></div></div><div class="section" id="delete-lvm-storage-pool-virsh"><div class="titlepage"><div><div><h4 class="title">27.1.4.4. Deleting a storage pool using virsh</h4></div></div></div><div class="para">
+ The following demonstrates how to delete a storage pool using virsh:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it.
+ </div><pre class="screen"># virsh pool-destroy <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Optionally, if you want to remove the directory where the storage pool resides use the following command:
+ </div><pre class="screen"># virsh pool-delete <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Remove the storage pool's definition
+ </div><pre class="screen"># virsh pool-undefine <em class="replaceable"><code>guest_images_disk</code></em></pre></li></ol></div></div></div><div xml:lang="en-US" class="section" id="sect-Virtualization-Storage_Pools-Creating-iSCSI" lang="en-US"><div class="titlepage"><div><div><h3 class="title">27.1.5. iSCSI-based storage pools</h3></div></div></div><div class="para">
+ This section covers using iSCSI-based devices to store guests.
+ </div><div class="para">
+ iSCSI (Internet Small Computer System Interface) is a network protocol for sharing storage devices. iSCSI connects initiators (storage clients) to targets (storage servers) using SCSI instructions over the IP layer.
+ </div><div class="section" id="idm88020464"><div class="titlepage"><div><div><h4 class="title" id="idm88020464">27.1.5.1. Configuring a software iSCSI target</h4></div></div></div><div class="para">
+ The <span class="package">scsi-target-utils</span> package provides a tool for creating software-backed iSCSI targets.
+ </div><div class="procedure"><h6>Procedure 27.4. Creating an iSCSI target</h6><ol class="1"><li class="step"><p class="title"><strong>Install the required packages</strong></p><div class="para">
+ Install the <span class="package">scsi-target-utils</span> package and all dependencies
+ </div><pre class="screen"># yum install scsi-target-utils</pre></li><li class="step"><p class="title"><strong>Start the tgtd service</strong></p><div class="para">
+ The <code class="command">tgtd</code> service hosts SCSI targets and uses the iSCSI protocol to host targets. Start the <code class="command">tgtd</code> service and make the service persistent after restarting with the <code class="command">chkconfig</code> command.
+ </div><pre class="screen"># service tgtd start
+# chkconfig tgtd on</pre></li><li class="step"><p class="title"><strong>Optional: Create LVM volumes</strong></p><div class="para">
+ LVM volumes are useful for iSCSI backing images. LVM snapshots and resizing can be beneficial for guests. This example creates an LVM image named <em class="replaceable"><code>virtimage1</code></em> on a new volume group named <em class="replaceable"><code>virtstore</code></em> on a RAID5 array for hosting guests with iSCSI.
+ </div><ol class="a"><li class="step"><p class="title"><strong>Create the RAID array</strong></p><div class="para">
+ Creating software RAID5 arrays is covered by the <em class="citetitle">Fedora Deployment Guide</em>.
+ </div></li><li class="step"><p class="title"><strong>Create the LVM volume group</strong></p><div class="para">
+ Create a volume group named <em class="replaceable"><code>virtstore</code></em> with the <code class="command">vgcreate</code> command.
+ </div><pre class="screen"># vgcreate <em class="replaceable"><code>virtstore</code></em> /dev/md1</pre></li><li class="step"><p class="title"><strong>Create a LVM logical volume</strong></p><div class="para">
+ Create a logical volume group named <em class="replaceable"><code>virtimage1</code></em> on the <em class="replaceable"><code>virtstore</code></em> volume group with a size of 20GB using the <code class="command">lvcreate</code> command.
+ </div><pre class="screen"># lvcreate --size 20G -n <em class="replaceable"><code>virtimage1 virtstore</code></em></pre><div class="para">
+ The new logical volume, <em class="replaceable"><code>virtimage1</code></em>, is ready to use for iSCSI.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Optional: Create file-based images</strong></p><div class="para">
+ File-based storage is sufficient for testing but is not recommended for production environments or any significant I/O activity. This optional procedure creates a file based imaged named <em class="replaceable"><code>virtimage2.img</code></em> for an iSCSI target.
+ </div><ol class="a"><li class="step"><p class="title"><strong>Create a new directory for the image</strong></p><div class="para">
+ Create a new directory to store the image. The directory must have the correct SELinux contexts.
+ </div><pre class="screen"># mkdir -p /var/lib/tgtd/<em class="replaceable"><code>virtualization</code></em>
+</pre></li><li class="step"><p class="title"><strong>Create the image file</strong></p><div class="para">
+ Create an image named <em class="replaceable"><code>virtimage2.img</code></em> with a size of 10GB.
+ </div><pre class="screen"># dd if=/dev/zero of=/var/lib/tgtd/<em class="replaceable"><code>virtualization</code></em>/<em class="replaceable"><code>virtimage2.img</code></em> bs=1M seek=10000 count=0</pre></li><li class="step"><p class="title"><strong>Configure SELinux file contexts</strong></p><div class="para">
+ Configure the correct SELinux context for the new image and directory.
+ </div><pre class="screen"># restorecon -R /var/lib/tgtd</pre><div class="para">
+ The new file-based image, <em class="replaceable"><code>virtimage2.img</code></em>, is ready to use for iSCSI.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Create targets</strong></p><div class="para">
+ Targets can be created by adding a XML entry to the <code class="filename">/etc/tgt/targets.conf</code> file. The <code class="computeroutput">target</code> attribute requires an iSCSI Qualified Name (IQN). The IQN is in the format:
+ </div><pre class="screen">iqn.<em class="replaceable"><code>yyyy</code></em>-<em class="replaceable"><code>mm</code></em>.<em class="replaceable"><code>reversed domain name</code></em>:<em class="replaceable"><code>optional identifier text</code></em>
+</pre><div class="para">
+ Where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="replaceable"><code>yyyy</code></em>-<em class="replaceable"><code>mm</code></em> represents the year and month the device was started (for example: <em class="replaceable"><code>2010-05</code></em>);
+ </div></li><li class="listitem"><div class="para">
+ <em class="replaceable"><code>reversed domain name</code></em> is the hosts domain name in reverse (for example <em class="replaceable"><code>server1.example.com</code></em> in an IQN would be <em class="replaceable"><code>com.example.server1</code></em>); and
+ </div></li><li class="listitem"><div class="para">
+ <em class="replaceable"><code>optional identifier text</code></em> is any text string, without spaces, that assists the administrator in identifying devices or hardware.
+ </div></li></ul></div><div class="para">
+ This example creates iSCSI targets for the two types of images created in the optional steps on <em class="replaceable"><code>server1.example.com</code></em> with an optional identifier <em class="replaceable"><code>trial</code></em>. Add the following to the <code class="filename">/etc/tgt/targets.conf</code> file.
+ </div><pre class="screen">
+<target iqn.2010-05.com.example.<em class="replaceable"><code>server1</code></em>:<em class="replaceable"><code>trial</code></em>>
+ backing-store /dev/<em class="replaceable"><code>virtstore</code></em>/<em class="replaceable"><code>virtimage1</code></em> #LUN 1
+ backing-store /var/lib/tgtd/<em class="replaceable"><code>virtualization</code></em>/<em class="replaceable"><code>virtimage2.img</code></em> #LUN 2
+ write-cache off
+</target>
+</pre><div class="para">
+ Ensure that the <code class="filename">/etc/tgt/targets.conf</code> file contains the <code class="computeroutput">default-driver iscsi</code> line to set the driver type as iSCSI. The driver uses iSCSI by default.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ This example creates a globally accessible target without access control. Refer to the scsi-target-utils for information on implementing secure access.
+ </div></div></div></li><li class="step"><p class="title"><strong>Restart the tgtd service</strong></p><div class="para">
+ Restart the <code class="systemitem">tgtd</code> service to reload the configuration changes.
+ </div><pre class="screen"># service tgtd restart</pre></li><li class="step"><p class="title"><strong>iptables configuration</strong></p><div class="para">
+ Open port 3260 for iSCSI access with <code class="command">iptables</code>.
+ </div><pre class="screen"># iptables -I INPUT -p tcp -m tcp --dport 3260 -j ACCEPT
+# service iptables save
+# service iptables restart</pre></li><li class="step"><p class="title"><strong>Verify the new targets</strong></p><div class="para">
+ View the new targets to ensure the setup was successful with the <code class="command">tgt-admin --show</code> command.
+ </div><pre class="screen">
+# tgt-admin --show
+Target 1: iqn.2010-05.com.example.server1:trial
+System information:
+Driver: iscsi
+State: ready
+I_T nexus information:
+LUN information:
+LUN: 0
+ Type: controller
+ SCSI ID: IET 00010000
+ SCSI SN: beaf10
+ Size: 0 MB
+ Online: Yes
+ Removable media: No
+ Backing store type: rdwr
+ Backing store path: None
+LUN: 1
+ Type: disk
+ SCSI ID: IET 00010001
+ SCSI SN: beaf11
+ Size: 20000 MB
+ Online: Yes
+ Removable media: No
+ Backing store type: rdwr
+ Backing store path: /dev/<em class="replaceable"><code>virtstore</code></em>/<em class="replaceable"><code>virtimage1</code></em>
+LUN: 2
+ Type: disk
+ SCSI ID: IET 00010002
+ SCSI SN: beaf12
+ Size: 10000 MB
+ Online: Yes
+ Removable media: No
+ Backing store type: rdwr
+ Backing store path: /var/lib/tgtd/<em class="replaceable"><code>virtualization</code></em>/<em class="replaceable"><code>virtimage2.img</code></em>
+Account information:
+ACL information:
+ALL
+</pre><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ The ACL list is set to all. This allows all systems on the local network to access this device. It is recommended to set host access ACLs for production environments.
+ </div></div></div></li><li class="step"><p class="title"><strong>Optional: Test discovery</strong></p><div class="para">
+ Test whether the new iSCSI device is discoverable.
+ </div><pre class="screen"># iscsiadm --mode discovery --type sendtargets --portal server1.example.com
+127.0.0.1:3260,1 iqn.2010-05.com.example.server1:iscsirhel6guest</pre></li><li class="step"><p class="title"><strong>Optional: Test attaching the device</strong></p><div class="para">
+ Attach the new device (<em class="replaceable"><code>iqn.2010-05.com.example.server1:iscsirhel6guest</code></em>) to determine whether the device can be attached.
+ </div><pre class="screen"># iscsiadm -d2 -m node --login
+scsiadm: Max file limits 1024 1024
+
+Logging in to [iface: default, target: iqn.2010-05.com.example.server1:iscsirhel6guest, portal: 10.0.0.1,3260]
+Login to [iface: default, target: iqn.2010-05.com.example.server1:iscsirhel6guest, portal: 10.0.0.1,3260] successful.</pre><div class="para">
+ Detach the device.
+ </div><pre class="screen"># iscsiadm -d2 -m node --logout
+scsiadm: Max file limits 1024 1024
+
+Logging out of session [sid: 2, target: iqn.2010-05.com.example.server1:iscsirhel6guest, portal: 10.0.0.1,3260
+Logout of [sid: 2, target: iqn.2010-05.com.example.server1:iscsirhel6guest, portal: 10.0.0.1,3260] successful.</pre></li></ol></div><div class="para">
+ An iSCSI device is now ready to use for virtualization.
+ </div></div><div class="section" id="idm116307568"><div class="titlepage"><div><div><h4 class="title" id="idm116307568">27.1.5.2. Adding an iSCSI target to virt-manager</h4></div></div></div><div class="para">
+ This procedure covers creating a storage pool with an iSCSI target in <code class="command">virt-manager</code>.
+ </div><div class="procedure"><h6>Procedure 27.5. Adding an iSCSI device to virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Open the host storage tab</strong></p><div class="para">
+ Open the <span class="guilabel"><strong>Storage</strong></span> tab in the <span class="guilabel"><strong>Host Details</strong></span> window.
+ </div><ol class="a"><li class="step"><div class="para">
+ Open <code class="command">virt-manager</code>.
+ </div></li><li class="step"><div class="para">
+ Select a host from the main <code class="command">virt-manager</code> window. Click <span class="guilabel"><strong>Edit menu</strong></span> and select <span class="guilabel"><strong>Connection Details</strong></span>.
+ </div><div class="figure" id="scsi-connection-details"><div class="figure-contents"><div class="mediaobject"><img src="images/Connection_Details.png" width="444" alt="Connection details" /></div></div><h6>Figure 27.19. Connection details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Click on the <span class="guilabel"><strong>Storage</strong></span> tab.
+ </div><div class="figure" id="scsi-storage-tab"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Storage menu" /></div></div><h6>Figure 27.20. Storage menu</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Add a new pool (part 1)</strong></p><div class="para">
+ Press the <span class="guilabel"><strong>+</strong></span> button (the add pool button). The <span class="guilabel"><strong>Add a New Storage Pool</strong></span> wizard appears.
+ </div><div class="figure" id="iscsi-storage-pool"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_add_storage_pool1.png" width="444" alt="Add an iscsi storage pool name and type" /></div></div><h6>Figure 27.21. Add an iscsi storage pool name and type</h6></div><br class="figure-break" /><div class="para">
+ Choose a name for the storage pool, change the Type to iscsi, and press <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Add a new pool (part 2)</strong></p><div class="para">
+ Enter the target path for the device, the host name of the target and the source path (the IQN). The <span class="guilabel"><strong>Format</strong></span> option is not available as formatting is handled by the guests. It is not advised to edit the <span class="guilabel"><strong>Target Path</strong></span>. The default target path value, <code class="filename">/dev/disk/by-path/</code>, adds the drive path to that directory. The target path should be the same on all hosts for migration.
+ </div><div class="para">
+ Enter the hostname or IP address of the iSCSI target. This example uses <code class="computeroutput">server1.example.com</code>.
+ </div><div class="para">
+ Enter the source path, for the iSCSI target. This example uses <code class="computeroutput">demo-target</code>.
+ </div><div class="para">
+ Check the <span class="guilabel"><strong>IQN</strong></span> checkbox to enter the IQN. This example uses <code class="computeroutput">iqn.2010-05.com.example.server1:iscsirhel6guest</code>.
+ </div><div class="figure" id="storage-pool-iscsi-add"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_add_storage_pool2.png" width="444" alt="Create an iscsi storage pool" /></div></div><h6>Figure 27.22. Create an iscsi storage pool</h6></div><br class="figure-break" /><div class="para">
+ Press <span class="guibutton"><strong>Finish</strong></span> to create the new storage pool.
+ </div></li></ol></div></div><div class="section" id="del-stor-pool-iscsi"><div class="titlepage"><div><div><h4 class="title">27.1.5.3. Deleting a storage pool using virt-manager</h4></div></div></div><div class="para">
+ This procedure demonstrates how to delete a storage pool.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it. To do this, select the storage pool you want to stop and click the red X icon at the bottom of the Storage window.
+ </div><div class="figure" id="stop-icon4"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Stop Icon" /></div></div><h6>Figure 27.23. Stop Icon</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Delete the storage pool by clicking the Trash can icon. This icon is only enabled if you stop the storage pool first.
+ </div></li></ol></div></div><div class="section" id="idm113889808"><div class="titlepage"><div><div><h4 class="title" id="idm113889808">27.1.5.4. Creating an iSCSI-based storage pool with virsh</h4></div></div></div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Use pool-define-as to define the pool from the command line</strong></p><div class="para">
+ Storage pool definitions can be created with the <code class="command">virsh</code> command line tool. Creating storage pools with <code class="command">virsh</code> is useful for systems administrators using scripts to create multiple storage pools.
+ </div><div class="para">
+ The <code class="command">virsh pool-define-as</code> command has several parameters which are accepted in the following format:
+ </div><pre class="screen">virsh pool-define-as <em class="parameter"><code>name type source-host source-path source-dev source-name</code></em> <em class="replaceable"><code>target</code></em>
+</pre><div class="para">
+ The parameters are explained as follows:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">type</span></dt><dd><div class="para">
+ defines this pool as a particular type, iscsi for example
+ </div></dd><dt class="varlistentry"><span class="term">name</span></dt><dd><div class="para">
+ must be unique and sets the name for the storage pool
+ </div></dd><dt class="varlistentry"><span class="term">source-host and source-path</span></dt><dd><div class="para">
+ the hostname and iSCSI IQN respectively
+ </div></dd><dt class="varlistentry"><span class="term">source-dev and source-name</span></dt><dd><div class="para">
+ these parameters are not required for iSCSI-based pools, use a <span class="keycap"><strong>-</strong></span> character to leave the field blank.
+ </div></dd><dt class="varlistentry"><span class="term">target</span></dt><dd><div class="para">
+ defines the location for mounting the iSCSI device on the host
+ </div></dd></dl></div><div class="para">
+ The example below creates the same iSCSI-based storage pool as the previous step.
+ </div><pre class="screen"># virsh pool-define-as --name scsirhel6guest --type iscsi \
+ --source-host server1.example.com \
+ --source-dev iqn.2010-05.com.example.server1:iscsirhel6guest
+ --target /dev/disk/by-path
+Pool iscsirhel6guest defined</pre></li><li class="step"><p class="title"><strong>Verify the storage pool is listed</strong></p><div class="para">
+ Verify the storage pool object is created correctly and the state reports as <code class="computeroutput">inactive</code>.
+ </div><pre class="screen"># virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+<em class="replaceable"><code>iscsirhel6guest</code></em> inactive no</pre></li><li class="step"><p class="title"><strong>Start the storage pool</strong></p><div class="para">
+ Use the virsh command <code class="command">pool-start</code> for this. <code class="command">pool-start</code> enables a directory storage pool, allowing it to be used for volumes and guests.
+ </div><pre class="screen"># virsh pool-start <em class="replaceable"><code>guest_images_disk</code></em>
+Pool guest_images_disk started
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+<em class="replaceable"><code>iscsirhel6guest</code></em> active no
+</pre></li><li class="step"><p class="title"><strong>Turn on autostart</strong></p><div class="para">
+ Turn on <em class="parameter"><code>autostart</code></em> for the storage pool. Autostart configures the <code class="systemitem">libvirtd</code> service to start the storage pool when the service starts.
+ </div><pre class="screen"># virsh pool-autostart <em class="replaceable"><code>iscsirhel6guest</code></em>
+Pool iscsirhel6guest marked as autostarted</pre><div class="para">
+ Verify that the <em class="replaceable"><code>iscsirhel6guest</code></em> pool has autostart set:
+ </div><pre class="screen"># virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+<em class="replaceable"><code>iscsirhel6guest</code></em> active yes
+</pre></li><li class="step"><p class="title"><strong>Verify the storage pool configuration</strong></p><div class="para">
+ Verify the storage pool was created correctly, the sizes reported correctly, and the state reports as <code class="computeroutput">running</code>.
+ </div><pre class="screen"># virsh pool-info <em class="replaceable"><code>iscsirhel6guest</code></em>
+Name: <em class="replaceable"><code>iscsirhel6guest</code></em>
+UUID: afcc5367-6770-e151-bcb3-847bc36c5e28
+State: running
+Persistent: unknown
+Autostart: yes
+Capacity: 100.31 GB
+Allocation: 0.00
+Available: 100.31 GB
+</pre></li></ol></div><div class="para">
+ An iSCSI-based storage pool is now available.
+ </div></div><div class="section" id="delete-iscsi-storage-pool-virsh"><div class="titlepage"><div><div><h4 class="title">27.1.5.5. Deleting a storage pool using virsh</h4></div></div></div><div class="para">
+ The following demonstrates how to delete a storage pool using virsh:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it.
+ </div><pre class="screen"># virsh pool-destroy <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Remove the storage pool's definition
+ </div><pre class="screen"># virsh pool-undefine <em class="replaceable"><code>guest_images_disk</code></em></pre></li></ol></div></div></div><div xml:lang="en-US" class="section" id="sect-Virtualization-Storage_Pools-Creating-NFS" lang="en-US"><div class="titlepage"><div><div><h3 class="title">27.1.6. NFS-based storage pools</h3></div></div></div><div class="para">
+ This procedure covers creating a storage pool with a NFS mount point in <code class="command">virt-manager</code>.
+ </div><div class="section" id="idm19705216"><div class="titlepage"><div><div><h4 class="title" id="idm19705216">27.1.6.1. Creating a NFS-based storage pool with virt-manager</h4></div></div></div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Open the host storage tab</strong></p><div class="para">
+ Open the <span class="guilabel"><strong>Storage</strong></span> tab in the <span class="guilabel"><strong>Host Details</strong></span> window.
+ </div><ol class="a"><li class="step"><div class="para">
+ Open <code class="command">virt-manager</code>.
+ </div></li><li class="step"><div class="para">
+ Select a host from the main <code class="command">virt-manager</code> window. Click <span class="guilabel"><strong>Edit menu</strong></span> and select <span class="guilabel"><strong>Connection Details</strong></span>.
+ </div><div class="figure" id="nfs-connection-details"><div class="figure-contents"><div class="mediaobject"><img src="images/Connection_Details.png" width="444" alt="Connection details" /></div></div><h6>Figure 27.24. Connection details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Click on the Storage tab.
+ </div><div class="figure" id="nfs-storage-tab"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Storage tab" /></div></div><h6>Figure 27.25. Storage tab</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Create a new pool (part 1)</strong></p><div class="para">
+ Press the <span class="guilabel"><strong>+</strong></span> button (the add pool button). The <span class="guilabel"><strong>Add a New Storage Pool</strong></span> wizard appears.
+ </div><div class="figure" id="add-nfs-pool-1"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_add_nfs_step1.png" width="444" alt="Add an NFS name and type" /></div></div><h6>Figure 27.26. Add an NFS name and type</h6></div><br class="figure-break" /><div class="para">
+ Choose a name for the storage pool and press <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Create a new pool (part 2)</strong></p><div class="para">
+ Enter the target path for the device, the hostname and the NFS share path. Set the <span class="guilabel"><strong>Format</strong></span> option to <span class="guilabel"><strong>NFS</strong></span> or <span class="guilabel"><strong>auto</strong></span> (to detect the type). The target path must be identical on all hosts for migration.
+ </div><div class="para">
+ Enter the hostname or IP address of the NFS server. This example uses <code class="computeroutput">server1.example.com</code>.
+ </div><div class="para">
+ Enter the NFS path. This example uses <code class="computeroutput">/nfstrial</code>.
+ </div><div class="figure" id="nfs-add-pool-2"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_add_nfs_step2.png" width="444" alt="Create an NFS storage pool" /></div></div><h6>Figure 27.27. Create an NFS storage pool</h6></div><br class="figure-break" /><div class="para">
+ Press <span class="guibutton"><strong>Finish</strong></span> to create the new storage pool.
+ </div></li></ol></div></div><div class="section" id="del-stor-pool-nfs"><div class="titlepage"><div><div><h4 class="title">27.1.6.2. Deleting a storage pool using virt-manager</h4></div></div></div><div class="para">
+ This procedure demonstrates how to delete a storage pool.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it. To do this, select the storage pool you want to stop and click the red X icon at the bottom of the Storage window.
+ </div><div class="figure" id="stop-icon5"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Stop Icon" /></div></div><h6>Figure 27.28. Stop Icon</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Delete the storage pool by clicking the Trash can icon. This icon is only enabled if you stop the storage pool first.
+ </div></li></ol></div></div></div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_Guide-Storage_Volumes" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 28. Volumes </h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Virtualization-Storage_Volumes-Creating_volumes">28.1. Creating volumes</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Volumes-Cloning_volumes">28.2. Cloning volumes</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests">28.3. Adding storage devices to guests</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Adding_storage_devices_to_guests-Adding_file_based_storage_to_a_guest">28.3.1. Adding file based storage to a guest</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Adding_storage_devices_to_guests-
Adding_hard_drives_and_other_block_devices_to_a_guest">28.3.2. Adding hard drives and other block devices to a guest</a></span></dt><dt><span class="section"><a href="#sect-Managing_storage_controllers_in_a_guest">28.3.3. Managing storage controllers in a guest</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Virtualization-Storage_Volumes-Deleting_volumes">28.4. Deleting and removing volumes</a></span></dt></dl></div><div class="section" id="sect-Virtualization-Storage_Volumes-Creating_volumes"><div class="titlepage"><div><div><h2 class="title">28.1. Creating volumes</h2></div></div></div><div class="para">
+ This section shows how to create disk volumes inside a block based storage pool. In the example below, the <code class="command">virsh vol-create-as</code> command will create a storage volume with a specific size in GB within the <em class="replaceable"><code>guest_images_disk</code></em> storage pool. As this command is repeated per volume needed, three volumes are created as shown in the example.
+ </div><pre class="screen"># virsh vol-create-as <em class="replaceable"><code>guest_images_disk</code></em> <em class="replaceable"><code>volume1</code></em> <em class="replaceable"><code>8</code></em>G
+Vol volume1 created
+
+# virsh vol-create-as <em class="replaceable"><code>guest_images_disk</code></em> <em class="replaceable"><code>volume2</code></em> <em class="replaceable"><code>8</code></em>G
+Vol volume2 created
+
+# virsh vol-create-as <em class="replaceable"><code>guest_images_disk</code></em> <em class="replaceable"><code>volume3</code></em> <em class="replaceable"><code>8</code></em>G
+Vol volume3 created
+
+# virsh vol-list <em class="replaceable"><code>guest_images_disk</code></em>
+Name Path
+-----------------------------------------
+volume1 /dev/sdb1
+volume2 /dev/sdb2
+volume3 /dev/sdb3
+
+# <code class="command">parted -s <em class="replaceable"><code>/dev/sdb</code></em> print</code>
+Model: ATA ST3500418AS (scsi)
+Disk /dev/sdb: 500GB
+Sector size (logical/physical): 512B/512B
+Partition Table: gpt
+
+Number Start End Size File system Name Flags
+2 17.4kB 8590MB 8590MB primary
+3 8590MB 17.2GB 8590MB primary
+1 21.5GB 30.1GB 8590MB primary
+
+</pre></div><div class="section" id="sect-Virtualization-Storage_Volumes-Cloning_volumes"><div class="titlepage"><div><div><h2 class="title">28.2. Cloning volumes</h2></div></div></div><div class="para">
+ The new volume will be allocated from storage in the same storage pool as the volume being cloned. The <code class="command"> virsh vol-clone</code> must have the <code class="literal">--pool</code> argument which dictates the name of the storage pool that contains the volume to be cloned. The rest of the command names the volume to be cloned (volume3) and the name of the new volume that was cloned (clone1). The <code class="command">virsh vol-list</code> command lists the volumes that are present in the storage pool (guest_images_disk).
+ </div><pre class="screen"># virsh vol-clone --pool <em class="replaceable"><code>guest_images_disk</code></em> <em class="replaceable"><code>volume3</code></em> <em class="replaceable"><code>clone1</code></em>
+Vol clone1 cloned from volume3
+
+# <code class="command">virsh vol-list <em class="replaceable"><code>guest_images_disk</code></em></code>
+Name Path
+-----------------------------------------
+volume1 /dev/sdb1
+volume2 /dev/sdb2
+volume3 /dev/sdb3
+clone1 /dev/sdb4
+
+
+# <code class="command">parted -s <em class="replaceable"><code>/dev/sdb</code></em> print</code>
+Model: ATA ST3500418AS (scsi)
+Disk /dev/sdb: 500GB
+Sector size (logical/physical): 512B/512B
+Partition Table: msdos
+
+Number Start End Size File system Name Flags
+1 4211MB 12.8GB 8595MB primary
+2 12.8GB 21.4GB 8595MB primary
+3 21.4GB 30.0GB 8595MB primary
+4 30.0GB 38.6GB 8595MB primary
+
+</pre></div><div class="section" id="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests"><div class="titlepage"><div><div><h2 class="title">28.3. Adding storage devices to guests</h2></div></div></div><div class="para">
+ This section covers adding storage devices to a guest. Additional storage can only be added as needed.
+ </div><div class="section" id="sect-Virtualization-Adding_storage_devices_to_guests-Adding_file_based_storage_to_a_guest"><div class="titlepage"><div><div><h3 class="title">28.3.1. Adding file based storage to a guest</h3></div></div></div><div class="para">
+ File-based storage is a collection of files that are stored on the hosts file system that act as virtualized hard drives for guests. To add file-based storage, perform the following steps:
+ </div><div class="procedure" id="proc-Virtualization-Adding_storage_devices"><h6>Procedure 28.1. Adding file-based storage</h6><ol class="1"><li class="step"><div class="para">
+ Create a storage file or use an existing file (such as an ISO file). Note that both of the following commands create a 4GB file which can be used as additional storage for a guest:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Pre-allocated files are recommended for file-based storage images. Create a pre-allocated file using the following <code class="command">dd</code> command as shown:
+ </div><pre class="screen"># dd if=/dev/zero of=/var/lib/libvirt/images/FileName.iso bs=1M count=4096</pre></li><li class="listitem"><div class="para">
+ Alternatively, create a sparse file instead of a pre-allocated file. Sparse files are created much faster and can be used for testing, but are not recommended for production environments due to data integrity and performance issues.
+ </div><pre class="screen"># dd if=/dev/zero of=/var/lib/libvirt/images/FileName.iso bs=1M seek=4096 count=0</pre></li></ul></div></li><li class="step"><div class="para">
+ Create the additional storage by writing a <em class="replaceable"><code><disk></code></em> element in a new file. In this example, this file will be known as <code class="filename">NewStorage.xml</code>.
+ </div><div class="para">
+ A <code class="literal"><disk></code> element describes the source of the disk, and a device name for the virtual block device. The device name should be unique across all devices in the guest, and identifies the bus on which the guest will find the virtual block device. The following example defines a virtio block device whose source is a file-based storage container named <code class="filename">FileName.img</code>:
+ </div><pre class="screen">
+<disk type='file' device='disk'>
+ <driver name='qemu' type='raw' cache='none'/>
+ <source file='/var/lib/libvirt/images/FileName.img'/>
+ <target dev='vdb'/>
+</disk>
+</pre><div class="para">
+ Device names can also start with "hd" or "sd", identifying respectively an IDE and a SCSI disk. The configuration file can also contain an <code class="literal"><address></code> sub-element that specifies the position on the bus for the new device. In the case of virtio block devices, this should be a PCI address. Omitting the <code class="literal"><address></code> sub-element lets libvirt locate and assign the next available PCI slot.
+ </div></li><li class="step"><div class="para">
+ Attach the CD-ROM as follows:
+ </div><pre class="screen">
+<disk type='file' device='cdrom'>
+ <driver name='qemu' type='raw' cache='none'/>
+ <source file='/var/lib/libvirt/images/FileName.iso'/>
+ <readonly/>
+ <target dev='hdc'/>
+</disk >
+</pre></li><li class="step"><div class="para">
+ Add the device defined in <code class="filename">NewStorage.xml</code> with your guest (<code class="literal">Guest1</code>):
+ </div><pre class="screen"># virsh attach-device --config Guest1 ~/NewStorage.xml</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ This change will only apply after the guest has been destroyed and restarted. In addition, persistent devices can only be added to a persistent domain, that is a domain whose configuration has been saved with <code class="command"> virsh define </code> command.
+ </div></div></div><div class="para">
+ If the guest is running, and you want the new device to be added temporarily until the guest is destroyed, omit the <code class="literal">--config</code> option:
+ </div><pre class="screen"># virsh attach-device Guest1 ~/NewStorage.xml</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The <code class="command">virsh</code> command allows for an <code class="command">attach-disk</code> command that can set a limited number of parameters with a simpler syntax and without the need to create an XML file. The <code class="command">attach-disk</code> command is used in a similar manner to the <code class="command">attach-device</code> command mentioned previously, as shown:
+ </div><pre class="screen">
+# virsh attach-disk Guest1 /var/lib/libvirt/images/FileName.iso vdb --cache none
+</pre><div class="para">
+ Note that the <code class="command">virsh attach-disk</code> command also accepts the <code class="literal">--config</code> option.
+ </div></div></div></li><li class="step"><div class="para">
+ Start the guest machine (if it is currently not running):
+ </div><pre class="screen"># virsh start Guest1</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The following steps are Linux guest specific. Other operating systems handle new storage devices in different ways. For other systems, refer to that operating system's documentation.
+ </div></div></div></li><li class="step" id="step-partition_disk"><p class="title"><strong>Partitioning the disk drive</strong></p><div class="para">
+ The guest now has a hard disk device called <code class="filename">/dev/vdb</code>. If required, partition this disk drive and format the partitions. If you do not see the device that you added, then it indicates that there is an issue with the disk hotplug in your guest's operating system.
+ </div><ol class="a"><li class="step"><div class="para">
+ Start <code class="command">fdisk</code> for the new device:
+ </div><pre class="screen">
+# fdisk /dev/vdb
+Command (m for help):
+</pre></li><li class="step"><div class="para">
+ Type <em class="parameter"><code>n</code></em> for a new partition.
+ </div></li><li class="step"><div class="para">
+ The following appears:
+ </div><pre class="screen">
+Command action
+e extended
+p primary partition (1-4)
+</pre><div class="para">
+ Type <em class="parameter"><code>p</code></em> for a primary partition.
+ </div></li><li class="step"><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): 1</pre></li><li class="step"><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 class="step"><div class="para">
+ Select the size of the partition. In this example the entire disk is allocated by pressing <code class="command">Enter</code>.
+ </div><pre class="screen">Last cylinder or +size or +sizeM or +sizeK (2-400, default 400):</pre></li><li class="step"><div class="para">
+ Enter <code class="command">t</code> to configure the partition type.
+ </div><pre class="screen">Command (m for help): t</pre></li><li class="step"><div class="para">
+ Select the partition you created in the previous steps. In this example, the partition number is <code class="command">1</code> as there was only one partition created and fdisk automatically selected partition 1.
+ </div><pre class="screen">Partition number (1-4): 1</pre></li><li class="step"><div class="para">
+ Enter <code class="command">83</code> for a Linux partition.
+ </div><pre class="screen">Hex code (type L to list codes): 83</pre></li><li class="step"><div class="para">
+ Enter <code class="command">w</code> to write changes and quit.
+ </div><pre class="screen">
+Command (m for help): w
+</pre></li><li class="step"><div class="para">
+ Format the new partition with the <code class="systemitem">ext3</code> file system.
+ </div><pre class="screen"># mke2fs -j /dev/vdb1</pre></li></ol></li><li class="step"><div class="para">
+ Create a mount directory, and mount the disk on the guest. In this example, the directory is located in <em class="replaceable"><code>myfiles</code></em>.
+ </div><pre class="screen">
+# mkdir /myfiles
+# mount /dev/vdb1 /myfiles
+</pre><div class="para">
+ The guest now has an additional virtualized file-based storage device. Note however, that this storage will not mount persistently across reboot unless defined in the guest's <code class="filename">/etc/fstab</code> file:
+ </div><pre class="screen">/dev/vdb1 <em class="replaceable"><code>/myfiles</code></em> ext3 defaults 0 0</pre></li></ol></div></div><div class="section" id="sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest"><div class="titlepage"><div><div><h3 class="title">28.3.2. Adding hard drives and other block devices to a guest</h3></div></div></div><div class="para">
+ System administrators use additional hard drives to provide increased storage space for a guest, or to separate system data from user data.
+ </div><div class="procedure" id="proc-Virtualization-Adding_storage_devices_to_guests-Adding_physical_block_devices_to_virtualized_guests"><h6>Procedure 28.2. Adding physical block devices to guests</h6><ol class="1"><li class="step"><div class="para">
+ This procedure describes how to add a hard drive on the host to a guest. It applies to all physical block devices, including CD-ROM, DVD and floppy devices.
+ </div><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 class="step"><div class="para">
+ Do one of the following:
+ </div><ol class="a"><li class="step"><div class="para">
+ Create the additional storage by writing a <code class="command">disk</code> element in a new file. In this example, this file will be known as <code class="filename">NewStorage.xml</code>. The following example is a configuration file section which contains an additional device-based storage container for the host partition <code class="filename">/dev/sr0:</code>
+ </div><pre class="screen">
+<disk type='block' device='disk'>
+ <driver name='qemu' type='raw' cache='none'/>
+ <source dev='/dev/sr0'/>
+ <target dev='vdc' bus='virtio'/>
+</disk>
+</pre></li><li class="step"><div class="para">
+ Follow the instruction in the previous section to attach the device to the guest. Alternatively, you can use the <em class="parameter"><code>virsh attach-disk</code></em> command, as shown:
+ </div><pre class="screen">
+# virsh attach-disk Guest1 /dev/sr0 vdc
+</pre><div class="para">
+ Note that the following options are available:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The<code class="command">virsh attach-disk</code> command also accepts the <em class="parameter"><code>--config</code></em>, <em class="parameter"><code>--type</code></em>, and <em class="parameter"><code>--mode</code></em> options, as shown:
+ </div><pre class="screen">
+# <code class="command">virsh attach-disk Guest1 /dev/sr0 vdc --config --type cdrom --mode readonly</code></pre></li><li class="listitem"><div class="para">
+ Additionally, <em class="parameter"><code> --type</code></em> also accepts <em class="parameter"><code>--type disk</code></em> in cases where the device is a hard drive.
+ </div></li></ul></div></li></ol></li><li class="step"><div class="para">
+ The guest now has a new hard disk device called <code class="filename">/dev/vdc</code> on Linux (or something similar, depending on what the guest OS chooses) or <code class="filename">D: drive</code> (for example) on Windows. You can now initialize the disk from the guest, following the standard procedures for the guest's operating system. Refer to <a class="xref" href="#proc-Virtualization-Adding_storage_devices">Procedure 28.1, “Adding file-based storage”</a> and <a class="xref" href="#step-partition_disk">Step 6</a> for an example.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ The host should not use filesystem labels to identify file systems in the <code class="filename">fstab</code> file, the <code class="filename">initrd</code> file or on the kernel command line. Doing so presents a security risk if less privileged users, such as guests, have write access to whole partitions or LVM volumes, because a guest could potentially write a filesystem label belonging to the host, to its own block device storage. Upon reboot of the host, the host could then mistakenly use the guest's disk as a system disk, which would compromise the host system.
+ </div><div class="para">
+ It is preferable to use the UUID of a device to identify it in the <code class="filename">fstab</code> file, the <code class="filename">initrd</code> file or on the kernel command line. While using UUIDs is still not completely secure on certain file systems, a similar compromise with UUID is significantly less feasible.
+ </div></div></div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Guests should not be given write access to whole disks or block devices (for example, <code class="filename">/dev/sdb</code>). Guests with access to whole block devices may be able to modify volume labels, which can be used to compromise the host system. Use partitions (for example, <code class="filename">/dev/sdb1</code>) or LVM volumes to prevent this issue.
+ </div></div></div></li></ol></div></div><div class="section" id="sect-Managing_storage_controllers_in_a_guest"><div class="titlepage"><div><div><h3 class="title">28.3.3. Managing storage controllers in a guest</h3></div></div></div><div class="para">
+ Starting from Red Hat Enterprise Linux 6.3, SCSI devices are also supported inside guests.
+ </div><div class="para">
+ Unlike virtio disks, SCSI devices require the presence of a controller in the guest.
+ </div><div class="para">
+ This section details the necessary steps to create a virtual SCSI controller (also known as "Host Bus Adapter", or HBA), and to add SCSI storage to the guest.
+ </div><div class="procedure" id="proc-Creating_a_virtual_SCSI_controller"><h6>Procedure 28.3. Creating a virtual SCSI controller</h6><ol class="1"><li class="step"><div class="para">
+ Display the configuration of the guest (<code class="literal">Guest1</code>) and look for a pre-existing SCSI controller:
+ </div><pre class="screen">
+# virsh dumpxml Guest1 | grep controller.*scsi
+</pre><div class="para">
+ If a controller is present, the command will output one or more lines similar to the following:
+ </div><pre class="screen">
+<controller type='scsi' model='virtio-scsi' index='0'/>
+</pre></li><li class="step"><div class="para">
+ If the previous step did not show a controller, create the description for one in a new file and add it to the virtual machine, using the following steps:
+ </div><ol class="a"><li class="step"><div class="para">
+ Create the controller by writing a <code class="literal"><controller></code> element in a new file and save this file with an XML extension. <code class="filename">NewHBA.xml</code>, for example.
+ </div><pre class="screen">
+<controller type='scsi' model='virtio-scsi'/>
+</pre></li><li class="step"><div class="para">
+ Associate the device in the <code class="filename">NewHBA.xml</code> you just created with your guest:
+ </div><pre class="screen">
+# virsh attach-device --config Guest1 ~/NewHBA.xml
+</pre><div class="para">
+ In this example the <code class="literal">--config</code> option behaves the same as it does for disks. Refer to <a class="xref" href="#proc-Virtualization-Adding_storage_devices_to_guests-Adding_physical_block_devices_to_virtualized_guests">Procedure 28.2, “Adding physical block devices to guests”</a> for more information.
+ </div></li></ol></li><li class="step"><div class="para">
+ Add a new SCSI disk or CD-ROM. The new disk can be added using the methods in sections <a class="xref" href="#sect-Virtualization-Adding_storage_devices_to_guests-Adding_file_based_storage_to_a_guest">Section 28.3.1, “Adding file based storage to a guest”</a> and <a class="xref" href="#sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest">Section 28.3.2, “Adding hard drives and other block devices to a guest”</a>. In order to create a SCSI disk, specify a target device name that starts with <em class="replaceable"><code>sd</code></em>.
+ </div><pre class="screen">
+# virsh attach-disk Guest1 /var/lib/libvirt/images/FileName.iso sdb --cache none
+</pre><div class="para">
+ Depending on the version of the driver in the guest, the new disk may not be detected immediately by a running guest. Follow the steps in the <em class="citetitle">Red Hat Enterprise Linux Storage Administration Guide</em>.
+ </div></li></ol></div></div></div><div class="section" id="sect-Virtualization-Storage_Volumes-Deleting_volumes"><div class="titlepage"><div><div><h2 class="title">28.4. Deleting and removing volumes</h2></div></div></div><div class="para">
+ This section shows how to delete a disk volume from a block based storage pool using the <code class="command">virsh vol-delete</code> command. In this example, the volume is <em class="replaceable"><code>volume 1</code></em> and the storage pool is <em class="replaceable"><code>guest_images</code></em>.
+ </div><pre class="screen">
+# virsh vol-delete --pool guest_images volume1
+Vol volume1 deleted
+</pre></div></div><div xml:lang="en-US" class="chapter" id="vhostmd" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 29. The Virtual Host Metrics Daemon (vhostmd)</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#idm110570048">29.1. Installing vhostmd on the host</a></span></dt><dt><span class="section"><a href="#idm80150944">29.2. Configuration of vhostmd</a></span></dt><dt><span class="section"><a href="#idm12488144">29.3. Starting and stopping the daemon</a></span></dt><dt><span class="section"><a href="#idm106196464">29.4. Verifying that vhostmd is working from the host</a></span></dt><dt><span class="section"><a href="#idm86879104">29.5. Configuring guests to see the metrics</a></span></dt><dt><span class="section"><a href="#idm91330288">29.6. Using vm-dump-metrics in Fedora guests to verify operation</a></span></dt></dl></div><div class="para">
+ <span class="application"><strong>vhostmd</strong></span> (the Virtual Host Metrics Daemon) allows virtual machines to see limited information about the host they are running on.
+ </div><div class="para">
+ In the host, a daemon (<span class="application"><strong>vhostmd</strong></span>) runs which writes metrics periodically into a disk image. This disk image is exported read-only to guests. Guests can read the disk image to see metrics. Simple synchronization stops guests from seeing out of date or corrupt metrics.
+ </div><div class="para">
+ The system administrator chooses which metrics the guests can see, and also which guests get to see the metrics at all.
+ </div><div class="section" id="idm110570048"><div class="titlepage"><div><div><h2 class="title" id="idm110570048">29.1. Installing vhostmd on the host</h2></div></div></div><div class="para">
+ The <span class="application"><strong>vhostmd</strong></span> package is available from RHN and is located in the Downloads area. It must be installed on each host where guests are required to get host metrics.
+ </div></div><div class="section" id="idm80150944"><div class="titlepage"><div><div><h2 class="title" id="idm80150944">29.2. Configuration of vhostmd</h2></div></div></div><div class="para">
+ After installing the package, but before starting the daemon, it is a good idea to understand exactly what metrics <span class="application"><strong>vhostmd</strong></span> will expose to guests, and how this happens.
+ </div><div class="para">
+ The metrics are controlled by the file <code class="filename">/etc/vhostmd/vhostmd.conf</code>.
+ </div><div class="para">
+ There are two parts of particular importance in this XML file. Firstly <em class="parameter"><code><update_period>60</update_period></code></em> controls how often the metrics are updated (in seconds). Since updating metrics can be an expensive operation, you can reduce the load on the host by increasing this period. Secondly, each <em class="parameter"><code><metric>...</metric></code></em> section controls what information is exposed by <span class="application"><strong>vhostmd</strong></span>. For example:
+ </div><pre class="screen"><metric type="string" context="host">
+ <name>HostName</name>
+ <action>hostname</action>
+</metric></pre><div class="para">
+ means that the hostname of the host is exposed to selected guests. To disable particular metrics, you can comment out <em class="parameter"><code><metric></code></em> sections by putting <code class="literal"><!-- ... --></code> around them. Note that disabling metrics may cause problems for guest software such as SAP that may rely on these metrics being available.
+ </div><div class="para">
+ When the daemon (also called <span class="application"><strong>vhostmd</strong></span>) is running, it writes the metrics into a temporary file called <code class="filename">/dev/shm/vhostmd0</code>. This file contains a small binary header followed by the selected metrics encoded as XML. In practice you can display this file with a tool like <span class="application"><strong>less</strong></span>. The file is updated every 60 seconds (or however often <em class="parameter"><code><update_period></code></em> was set).
+ </div><div class="para">
+ The vhostmd(8) man page contains a detailed description of the configuration file, as well as examples of the XML output in <code class="filename">/dev/shm/vhostmd0</code>. To read this, do:
+ </div><pre class="screen"># man vhostmd</pre><div class="para">
+ In addition, there is a README file which covers some of the same information:
+ </div><pre class="screen">less /usr/share/doc/vhostmd-*/README</pre></div><div class="section" id="idm12488144"><div class="titlepage"><div><div><h2 class="title" id="idm12488144">29.3. Starting and stopping the daemon</h2></div></div></div><div class="para">
+ The daemon (<span class="application"><strong>vhostmd</strong></span>) will not be started automatically. To enable it to be started at boot, run:
+ </div><pre class="screen"># /sbin/chkconfig vhostmd on</pre><div class="para">
+ To start the daemon running, do:
+ </div><pre class="screen"># /sbin/service vhostmd start</pre><div class="para">
+ To stop the daemon running, do:
+ </div><pre class="screen"># /sbin/service vhostmd stop</pre><div class="para">
+ To disable the daemon from being started at boot, do:
+ </div><pre class="screen"># /sbin/chkconfig vhostmd off</pre></div><div class="section" id="idm106196464"><div class="titlepage"><div><div><h2 class="title" id="idm106196464">29.4. Verifying that vhostmd is working from the host</h2></div></div></div><div class="para">
+ A short time after the daemon has started, you should see a metrics disk appearing. Do:
+ </div><pre class="screen"># ls -l /dev/shm
+# less /dev/shm/vhostmd0</pre><div class="para">
+ This file has a short binary header, followed by XML. The <span class="application"><strong>less</strong></span> program identifies it as binary and asks:
+ </div><pre class="screen">"/dev/shm/vhostmd0" may be a binary file. See it anyway?</pre><div class="para">
+ Press the <span class="keycap"><strong>y</strong></span> key to indicate that you wish to view it.
+ </div><div class="para">
+ You should see the binary header appearing as garbled characters, followed by the <em class="parameter"><code><metrics></code></em> XML, and after that, many zero bytes (displayed as <code class="literal">^@^@^@</code>...).
+ </div></div><div class="section" id="idm86879104"><div class="titlepage"><div><div><h2 class="title" id="idm86879104">29.5. Configuring guests to see the metrics</h2></div></div></div><div class="para">
+ Although metrics are written to <code class="filename">/dev/shm/vhostmd0</code>, they are not made available to guests by default. The administrator must choose which guests get to see metrics, and must manually change the configuration of selected guests to see metrics.
+ </div><div class="para">
+ The guest must be shut down before the disk is attached. (Hot attaching the metrics disk is also possible, but only for a limited number of guest configurations. In particular it is NOT possible to hot-add the metrics disk to guests that do not have virtio / PV drivers installed. See the vhostmd README file for more information).
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ It is extremely important that the metrics disk is added in readonly mode to all guests. If this is not done, then it would be possible for a guest to modify the metrics and possibly subvert other guests that are reading it.
+ </div></div></div><div class="procedure"><h6>Procedure 29.1. Configuring KVM guests</h6><ol class="1"><li class="step"><div class="para">
+ Shut down the guest.
+ </div></li><li class="step"><div class="para">
+ Do:
+ </div><pre class="screen"># virsh edit GuestName</pre><div class="para">
+ and add the following section into <em class="parameter"><code><devices></code></em>:
+ </div><pre class="screen"><disk type='file' device='disk'>
+ <driver name='qemu' type='raw'/>
+ <source file='/dev/shm/vhostmd0'/>
+ <target dev='vdd' bus='virtio'/>
+ <readonly/>
+ </disk></pre></li><li class="step"><div class="para">
+ Reboot the guest.
+ </div></li></ol></div><div class="procedure"><h6>Procedure 29.2. Configuring Xen guests</h6><ol class="1"><li class="step"><div class="para">
+ Shut down the guest.
+ </div></li><li class="step"><div class="para">
+ Do:
+ </div><pre class="screen"># virsh edit GuestName</pre><div class="para">
+ and add the following section into <em class="parameter"><code><devices></code></em>:
+ </div><pre class="screen"><disk type='file' device='disk'>
+ <source dev='/dev/shm/vhostmd0'/>
+ <target dev='hdd' bus='ide'/>
+ <readonly/>
+ </disk></pre></li><li class="step"><div class="para">
+ Reboot the guest.
+ </div></li></ol></div></div><div class="section" id="idm91330288"><div class="titlepage"><div><div><h2 class="title" id="idm91330288">29.6. Using vm-dump-metrics in Fedora guests to verify operation</h2></div></div></div><div class="para">
+ Optionally, the <span class="package">vm-dump-metrics</span> package from the RHN Downloads area may be installed in Fedora guests. This package provides a simple command line tool (also called <span class="application"><strong>vm-dump-metrics</strong></span>) which allows host metrics to be displayed in the guest.
+ </div><div class="para">
+ This is useful for verifying correct operation of <span class="application"><strong>vhostmd</strong></span> from a guest.
+ </div><div class="para">
+ In the guest, run the following command as root:
+ </div><pre class="screen"># vm-dump-metrics</pre><div class="para">
+ If everything is working, this should print out a long XML document starting with <code class="literal"><metrics></code>.
+ </div><div class="para">
+ If this does not work, then verify that the metrics disk has appeared in the guest. It should appear as <code class="filename">/dev/vd*</code> (for example, <code class="filename">/dev/vdb</code>, <code class="filename">/dev/vdd</code>).
+ </div><div class="para">
+ On the host, verify that the libvirt configuration changes have been made by using the command:
+ </div><pre class="screen"># virsh dumpxml GuestName</pre><div class="para">
+ Verify that vhostmd is running on the host and the /dev/shm/vhostmd0 file exists.
+ </div></div></div></div><div class="part" id="idm95247120"><div class="titlepage"><div><div><h1 class="title">Part III. Appendicies</h1></div></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl><dt><span class="appendix"><a href="#chap-Virtualization_Administration_Guide-Troubleshooting">A. Troubleshooting</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Troubleshooting_-Debugging_and_troubleshooting_">A.1. Debugging and troubleshooting tools</a></span></dt><dt><span class="section"><a href="#idm79846544">A.2. kvm_stat</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles">A.3. Troubleshooting with serial consoles</a></span></dt><dt><span class="section"><a href="#idm12647232">A.4. Virtualization log files</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Troubleshooting-Loop_device_errors">A.5. Loop device errors</a></span></dt>
<dt><span class="section"><a href="#live-migration-errors">A.6. Live Migration Errors</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS">A.7. Enabling Intel VT-x and AMD-V virtualization hardware extensions in BIOS</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Troubleshooting-KVM_networking_performance">A.8. KVM networking performance</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard">A.9. Missing characters on guest console with Japanese keyboard</a></span></dt><dt><span class="section"><a href="#sec-known-issues-windows-xp-guests">A.10. Known Windows XP guest issues</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idm105767440">B. Common <span class="application"><strong>libvirt</strong></span> errors and troubleshooting</a></span></dt><dd><dl
><dt><span class="section"><a href="#App_Libvirt_Daemon">B.1. <span class="application"><strong>libvirtd</strong></span> failed to start</a></span></dt><dt><span class="section"><a href="#App_Hypervisor_Connection_Fail">B.2. The URI failed to connect to the hypervisor</a></span></dt><dd><dl><dt><span class="section"><a href="#Sect_Cannot_read_CA_certificate">B.2.1. Cannot read CA certificate</a></span></dt><dt><span class="section"><a href="#Sect_Failed_to_connect_socket">B.2.2. Failed to connect socket ... : Permission denied</a></span></dt><dt><span class="section"><a href="#Sect_Other_Connectivity_Errors">B.2.3. Other connectivity errors</a></span></dt></dl></dd><dt><span class="section"><a href="#App_Domain_Processor">B.3. The guest virtual machine cannot be started: <code class="computeroutput">internal error guest CPU is not compatible with host CPU</code></a></span></dt><dt><span class="section"><a href="#App_Domain_Monitor_Socket">B.4. Guest starting fails with error
: <code class="computeroutput">monitor socket did not show up</code></a></span></dt><dt><span class="section"><a href="#App_Domain_Console">B.5. <code class="computeroutput">Internal error cannot find character device (null)</code></a></span></dt><dt><span class="section"><a href="#App_Domain_Not_Booting">B.6. Guest virtual machine booting stalls with error: <code class="computeroutput">No boot device</code></a></span></dt><dt><span class="section"><a href="#App_Virt_Net_Not_Starting">B.7. Virtual network <em class="replaceable"><code>default</code></em> has not been started</a></span></dt><dt><span class="section"><a href="#App_PXE_Guest_Boot_Fail">B.8. PXE boot (or DHCP) on guest failed</a></span></dt><dt><span class="section"><a href="#App_Macvtap">B.9. Guest can reach outside network, but cannot reach host when using macvtap interface</a></span></dt><dt><span class="section"><a href="#App_DHCP_Response_Checksums">B.10. Could not add rule to fixup DHCP response checksums
on network <em class="replaceable"><code>'default'</code></em></a></span></dt><dt><span class="section"><a href="#App_Bridge_Device">B.11. Unable to add bridge br0 port vnet0: No such device</a></span></dt><dt><span class="section"><a href="#App_Generic_Ethernet">B.12. Guest is unable to start with error: <code class="computeroutput">warning: could not open /dev/net/tun</code></a></span></dt><dt><span class="section"><a href="#App_Migration_Address">B.13. Migration fails with <code class="computeroutput">Error: unable to resolve address</code></a></span></dt><dt><span class="section"><a href="#App_Migration_Disk_Image">B.14. Migration fails with <code class="computeroutput">Unable to allow access for disk path: No such file or directory</code></a></span></dt><dt><span class="section"><a href="#App_No_Guest_Machines">B.15. No guest virtual machines are present when <span class="application"><strong>libvirtd</strong></span> is started</a></span></dt><dt><span class="section"><
a href="#App_TCP_Ports">B.16. Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor</a></span></dt><dt><span class="section"><a href="#App_XML_Errors">B.17. Common XML errors</a></span></dt><dd><dl><dt><span class="section"><a href="#idm115036144">B.17.1. Editing domain definition</a></span></dt><dt><span class="section"><a href="#idm98827392">B.17.2. XML syntax errors</a></span></dt><dt><span class="section"><a href="#idm99205120">B.17.3. Logic and configuration errors</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#netkvm-parameters">C. NetKVM Driver Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idm84429120">C.1. Configurable parameters for NetKVM</a></span></dt></dl></dd><dt><span class="appendix"><a href="#chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist">D. qemu-kvm Whitelist</a></span></dt><dd><dl><dt><span class="section"><a href="#idm115407088">D.1. Int
roduction</a></span></dt><dt><span class="section"><a href="#idm88207680">D.2. Basic options</a></span></dt><dt><span class="section"><a href="#idm19048240">D.3. Disk options</a></span></dt><dt><span class="section"><a href="#idm99806304">D.4. Display options</a></span></dt><dt><span class="section"><a href="#idm97967728">D.5. Network options</a></span></dt><dt><span class="section"><a href="#idm95825168">D.6. Device options</a></span></dt><dt><span class="section"><a href="#idm110926144">D.7. Linux/Multiboot boot </a></span></dt><dt><span class="section"><a href="#idm85902736">D.8. Expert options</a></span></dt><dt><span class="section"><a href="#idm75543056">D.9. Help and information options</a></span></dt><dt><span class="section"><a href="#idm101602032">D.10. Miscellaneous options</a></span></dt></dl></dd><dt><span class="appendix"><a href="#chap-Virtualization_Administration_Guide-Managing_guests_with_virsh">E. Managing guests with virsh</a></span></dt><dd><dl><dt><span
class="section"><a href="#idm76402464">E.1. virsh command quick reference</a></span></dt><dt><span class="section"><a href="#sect-Attaching_and_updating_a_device_with_virsh">E.2. Attaching and updating a device with virsh</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor">E.3. Connecting to the hypervisor</a></span></dt><dt><span class="section"><a href="#form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file">E.4. Creating a virtual machine XML dump (configuration file)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-multifunction-pci-install">E.4.1. Adding multifunction PCI devices to KVM guests</a></span></dt></dl></dd><dt><span class="section"><a href="#idm15093120">E.5. Suspending, resuming, saving and restoring a guest</a></span></dt><dt><span class="section"><a href="#idm111188384">E.6. Shutting down, rebooting and force-shutdown
of a guest</a></span></dt><dt><span class="section"><a href="#idm124247680">E.7. Retrieving guest information</a></span></dt><dt><span class="section"><a href="#idm80557872">E.8. Retrieving node information</a></span></dt><dt><span class="section"><a href="#idm75574976">E.9. Storage pool information</a></span></dt><dt><span class="section"><a href="#idm99238304">E.10. Displaying per-guest information</a></span></dt><dt><span class="section"><a href="#idm115752416">E.11. Managing virtual networks</a></span></dt><dt><span class="section"><a href="#migrating_guests-with-virsh">E.12. Migrating guests with virsh</a></span></dt><dt><span class="section"><a href="#sect-man-disk-image">E.13. Disk image management with live block copy</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-blockcommit">E.13.1. Using blockcommit to shorten a backing chain</a></span></dt><dt><span class="section"><a href="#sub-sect-blockpull">E.13.2. Using blockpull to shorten a backing chain<
/a></span></dt><dt><span class="section"><a href="#sub-sect-blkresize">E.13.3. Using blockresize to change the size of a domain path</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-guest-cpu-model-config">E.14. Guest CPU model configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-guest-cpu-intro">E.14.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-learn-about-host-cpu">E.14.2. Learning about the host CPU model</a></span></dt><dt><span class="section"><a href="#idm118920304">E.14.3. Determining a compatible CPU model to suit a pool of hosts</a></span></dt><dt><span class="section"><a href="#idm122440672">E.14.4. Configuring the guest CPU model</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager">F. Managing guests with the Virtual Machine Manager (virt-manager)</a></span></dt><dd><dl><dt><
span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Starting_virt_manager">F.1. Starting virt-manager</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window">F.2. The Virtual Machine Manager main window</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_">F.3. The virtual hardware details window</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_">F.4. Virtual Machine graphical console</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window">F.5. Adding a remot
e connection</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details">F.6. Displaying guest details</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring">F.7. Performance monitoring</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage">F.8. Displaying CPU usage for guests</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage">F.9. Displaying CPU usage for hosts</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO">F.10. Displaying Disk I/O</a></span></dt><dt><span class="section"
><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO">F.11. Displaying Network I/O</a></span></dt></dl></dd><dt><span class="appendix"><a href="#chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs">G. Guest disk access with offline tools</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-introduction-Virtualization_Administration_Guide-Guest_Disks_libguestfs">G.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-Terminology-Guest_Disks_libguestfs">G.2. Terminology</a></span></dt><dt><span class="section"><a href="#sect-Guide-Guest_Disks_libguestfs-installation">G.3. Installation</a></span></dt><dt><span class="section"><a href="#sect-the_guestfish_shell">G.4. The guestfish shell</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Viewing_file_systems_with_guestfish">G.4.1. Viewing file systems with guestfish</a></span></dt><dt><span class="section"><a href="
#sect-Modifying-files-with-guestfish">G.4.2. Modifying files with guestfish</a></span></dt><dt><span class="section"><a href="#sect-Other-actions-with-guestfish">G.4.3. Other actions with guestfish</a></span></dt><dt><span class="section"><a href="#sect-Shell-scripting-with-guestfish">G.4.4. Shell scripting with guestfish</a></span></dt><dt><span class="section"><a href="#sect-Augeas-and-libguestfs-scripting">G.4.5. Augeas and libguestfs scripting</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-other-commands">G.5. Other commands</a></span></dt><dt><span class="section"><a href="#sect-virt-rescue">G.6. virt-rescue: The rescue shell</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-virt-rescue-intro">G.6.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-run-virt-rescue">G.6.2. Running virt-rescue</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-virt-df">G.7. virt-df: Monitoring disk usage</a></span></dt><d
d><dl><dt><span class="section"><a href="#sect-virt-df-intro">G.7.1. Introduction</a></span></dt><dt><span class="section"><a href="#run-virt-df">G.7.2. Running virt-df</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-virt-resize">G.8. virt-resize: resizing guests offline</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-virt-resize-intro">G.8.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-expand-disk-image">G.8.2. Expanding a disk image</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-virt-inspector">G.9. virt-inspector: inspecting guests</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-virt-inspector-intro">G.9.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-virt-inspector-install">G.9.2. Installation</a></span></dt><dt><span class="section"><a href="#sect-virt-inspector-run">G.9.3. Running virt-inspector</a></span></dt></dl></dd><dt><span class="section"><a href
="#sect-virt-win-reg">G.10. virt-win-reg: Reading and editing the Windows Registry</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-virt-win-reg-intro">G.10.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-virt-win-reg-install">G.10.2. Installation</a></span></dt><dt><span class="section"><a href="#sect-virt-win-reg-use">G.10.3. Using virt-win-reg</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Using-API-Programming-Languages">G.11. Using the API from Programming Languages</a></span></dt><dd><dl><dt><span class="section"><a href="#API-and-C">G.11.1. Interaction with the API via a C program</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-libguestfs-troubleshoot">G.12. Troubleshooting</a></span></dt><dt><span class="section"><a href="#sect-libguestfs-more-docs">G.13. Where to find further documentation</a></span></dt></dl></dd><dt><span class="appendix"><a href="#chap-Virtualization_Administration_Guide-
Virtual_Networking">H. Virtual Networking</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-virtual_network-switches-livbvirt">H.1. Virtual network switches</a></span></dt><dt><span class="section"><a href="#sect-Network_Address_Translation-libvirt">H.2. Network Address Translation</a></span></dt><dt><span class="section"><a href="#sect-network-protocols">H.3. Networking protocols</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-DNS_and_DHCP-protocols-libvirt">H.3.1. DNS and DHCP</a></span></dt><dt><span class="section"><a href="#sub-sect-routed-mode-libvirt">H.3.2. Routed mode</a></span></dt><dt><span class="section"><a href="#sub-sect-iso-mode">H.3.3. Isolated mode</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-the-Default_Configuration-libvirt">H.4. The default configuration</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Virtual_Networking-Example_scenarios">H.5. Examples of common scenarios</a></span
></dt><dd><dl><dt><span class="section"><a href="#sub-sect-routed-mode">H.5.1. Routed mode</a></span></dt><dt><span class="section"><a href="#sub-sect-nat-mode">H.5.2. NAT mode</a></span></dt><dt><span class="section"><a href="#sub-sect-isolated-mode">H.5.3. Isolated mode</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Virtualization-Virtual_Networking-Managing_a_virtual_network">H.6. Managing a virtual network</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Virtual_Networking-Creating_a_virtual_network">H.7. Creating a virtual network</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest">H.8. Attaching a virtual network to a guest</a></span></dt><dt><span class="section"><a href="#sect-attch-nic-physdev">H.9. Directly attaching to physical interface</a></span></dt><dt><span class="section"><a href="#sect-applying-network-filtering">H.10. Applying network filterin
g</a></span></dt><dd><dl><dt><span class="section"><a href="#intro-sub-sect-applying-network-filtering">H.10.1. Introduction</a></span></dt><dt><span class="section"><a href="#sub-sect-filt-chain">H.10.2. Filtering chains</a></span></dt><dt><span class="section"><a href="#sub-sect-filt-chain-props">H.10.3. Filtering chain priorities</a></span></dt><dt><span class="section"><a href="#sub-sect-vars-in-filters">H.10.4. Usage of variables in filters</a></span></dt><dt><span class="section"><a href="#sub-sect-auto-IP-add-detect-dhcp-snoop">H.10.5. Automatic IP address detection and DHCP snooping</a></span></dt><dt><span class="section"><a href="#sub-sect-vars-reserved">H.10.6. Reserved Variables</a></span></dt><dt><span class="section"><a href="#sub-sect-element-oview">H.10.7. Element and attribute overview</a></span></dt><dt><span class="section"><a href="#sub-sect-ref-filter">H.10.8. References to other filters</a></span></dt><dt><span class="section"><a href="#sub-sect-filter-
rules">H.10.9. Filter rules</a></span></dt><dt><span class="section"><a href="#sub-sect-supp-pros">H.10.10. Supported protocols</a></span></dt><dt><span class="section"><a href="#sub-sect-adv-filt-topics">H.10.11. Advanced Filter Configuration Topics</a></span></dt><dt><span class="section"><a href="#sub-sect-limitations-filters-network-subsystem">H.10.12. Limitations</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#appe-Virtualization-Additional_resources">I. Additional resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Additional_resources-Online_resources">I.1. Online resources</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Additional_resources-Installed_documentation">I.2. Installed documentation</a></span></dt></dl></dd><dt><span class="appendix"><a href="#ch-lib-dom-xml">J. Manipulating the domain xml</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-gen-metadata">J.1. Ge
neral information and metadata</a></span></dt><dt><span class="section"><a href="#sect-dom-xml-op-sys-boot">J.2. Operating system booting</a></span></dt><dd><dl><dt><span class="section"><a href="#sub-sect-op-sys-boot-bios-boot">J.2.1. BIOS bootloader</a></span></dt><dt><span class="section"><a href="#sub-sect-op-sys-host-boot">J.2.2. Host bootloader</a></span></dt><dt><span class="section"><a href="#sub-sect-op-sys-dir-kern-boot">J.2.3. Direct kernel boot</a></span></dt><dt><span class="section"><a href="#sub-sect-op-sys-cont-boot">J.2.4. Container boot</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-smbios-sys-info">J.3. SMBIOS system information</a></span></dt><dt><span class="section"><a href="#sect-cpu-allocation">J.4. CPU allocation</a></span></dt><dt><span class="section"><a href="#sect-cpu-tuning">J.5. CPU tuning</a></span></dt><dt><span class="section"><a href="#sect-mem-back">J.6. Memory backing</a></span></dt><dt><span class="section"><a href="#s
ect-libvirt-dom-xml-mem-tuning">J.7. Memory tuning</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-numa-node-tuning">J.8. NUMA node tuning</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-blk-io-tuning">J.9. Block I/O tuning</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-res-part">J.10. Resource partitioning</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-cpu-model-top">J.11. CPU model and topology</a></span></dt><dd><dl><dt><span class="section"><a href="#sub-sect-libvirt-dom-xml-res-part-guest-numa">J.11.1. Guest NUMA topology</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-libvirt-dom-xml-event-config">J.12. Events configuration</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-pwr-man">J.13. Power Management</a></span></dt><dt><span class="section"><a href="#idm83056320">J.14. Hypervisor features</a></span></dt><dt><span class="section">
<a href="#sect-libvirt-dom-xml-time-keep">J.15. Time keeping</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-devices">J.16. Devices</a></span></dt><dd><dl><dt><span class="section"><a href="#sub-sect-libvirt-dom-xml-devices">J.16.1. Hard drives, floppy disks, CDROMs</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-filesystems">J.16.2. Filesystems</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-device-addresses">J.16.3. Device addresses</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-controllers">J.16.4. Controllers</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-device-leases">J.16.5. Device leases</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-host-device-assignment">J.16.6. Host device assignment</a></span></dt><dt><span class="section"><a href="#sub-section
-libvirt-dom-xml-devices-redirected-devices">J.16.7. Redirected devices</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-smartcard">J.16.8. Smartcard devices</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-Network-interfaces">J.16.9. Network interfaces</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-input-devices">J.16.10. Input devices</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-hub-devices">J.16.11. Hub devices</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-graphical-framebuffers">J.16.12. Graphical framebuffers</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-video">J.16.13. Video devices</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-consoles">J.16.14. Consoles, serial, parallel, and channel devices
</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-guest-interface">J.16.15. Guest interfaces</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-channel">J.16.16. Channel</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-host-interface">J.16.17. Host interface</a></span></dt></dl></dd><dt><span class="section"><a href="#section-libvirt-dom-xml-sound-devices">J.17. Sound devices</a></span></dt><dt><span class="section"><a href="#section-libvirt-dom-xml-watchdog">J.18. Watchdog device</a></span></dt><dt><span class="section"><a href="#section-libvirt-dom-xml-memory-baloon-device">J.19. Memory balloon device</a></span></dt><dt><span class="section"><a href="#section-libvirt-dom-xml-random-number-gen">J.20. Random number generator device</a></span></dt><dt><span class="section"><a href="#section-libvirt-dom-xml-tpm-device">J.21. TPM devices</a></span></dt><dt><span class
="section"><a href="#section-libvirt-dom-xml-security-label">J.22. Security label</a></span></dt><dt><span class="section"><a href="#section-libvirt-dom-xml-example">J.23. Example domain XML configuration</a></span></dt></dl></dd></dl></div><div xml:lang="en-US" class="appendix" id="chap-Virtualization_Administration_Guide-Troubleshooting" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Troubleshooting</h1></div></div></div><div class="para">
+ This chapter covers common problems and solutions for Fedora virtualization issues.
+ </div><div class="para">
+ Read this chapter to develop an understanding of some of the common problems associated with virtualization technologies. Troubleshooting takes practice and experience which are difficult to learn from a book. It is recommended that you experiment and test virtualization on Fedora 19 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="#sect-Virtualization-Additional_resources-Online_resources">Section I.1, “Online resources”</a> for a list of Linux virtualization websites.
+ </div><div class="section" id="sect-Virtualization-Troubleshooting_-Debugging_and_troubleshooting_"><div class="titlepage"><div><div><h2 class="title">A.1. Debugging and troubleshooting tools</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="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">kvm_stat</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">trace-cmd</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">vmstat</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">iostat</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">lsof</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">systemtap</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">crash</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">sysrq</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">sysrq t</code>
+ </div></li><li class="listitem"><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 class="listitem"><div class="para">
+ <code class="command">ifconfig</code>
+ </div></li><li class="listitem"><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 class="listitem"><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 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
+-----------------------------------------------------------------------------
+virtbr0 8000.feffffff yes eth0
+
+# brctl showmacs virtbr0
+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 virtbr0
+virtbr0
+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.
+ </div><div class="itemizedlist"><ul><li class="listitem"><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 class="listitem"><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 class="listitem"><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 class="section" id="idm79846544"><div class="titlepage"><div><div><h2 class="title" id="idm79846544">A.2. kvm_stat</h2></div></div></div><div class="para">
+ The <code class="command">kvm_stat</code> command is a python script which retrieves runtime statistics from the <code class="systemitem">kvm</code> kernel module. The <code class="command">kvm_stat</code> command can be used to diagnose guest behavior visible to <code class="systemitem">kvm</code>. In particular, performance related issues with guests. Currently, the reported statistics are for the entire system; the behavior of all running guests is reported.
+ </div><div class="para">
+ The <code class="command">kvm_stat</code> command requires that the <code class="systemitem">kvm</code> kernel module is loaded and <code class="command">debugfs</code> is mounted. If either of these features are not enabled, the command will output the required steps to enable <code class="command">debugfs</code> or the <code class="systemitem">kvm</code> module. For example:
+ </div><pre class="screen"># kvm_stat
+Please mount debugfs ('mount -t debugfs debugfs /sys/kernel/debug')
+and ensure the kvm modules are loaded</pre><div class="para">
+ Mount <code class="command">debugfs</code> if required:
+ </div><pre class="screen"># mount -t debugfs debugfs /sys/kernel/debug</pre><div class="formalpara"><h5 class="formalpara" id="idm95392032">kvm_stat output</h5>
+ The <code class="command">kvm_stat</code> command outputs statistics for all guests and the host. The output is updated until the command is terminated (using <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>c</strong></span> or the <span class="keycap"><strong>q</strong></span> key).
+ </div><pre class="screen"># kvm_stat
+
+kvm statistics
+
+efer_reload 94 0
+exits 4003074 31272
+fpu_reload 1313881 10796
+halt_exits 14050 259
+halt_wakeup 4496 203
+host_state_reload 1638354 24893
+hypercalls 0 0
+insn_emulation 1093850 1909
+insn_emulation_fail 0 0
+invlpg 75569 0
+io_exits 1596984 24509
+irq_exits 21013 363
+irq_injections 48039 1222
+irq_window 24656 870
+largepages 0 0
+mmio_exits 11873 0
+mmu_cache_miss 42565 8
+mmu_flooded 14752 0
+mmu_pde_zapped 58730 0
+mmu_pte_updated 6 0
+mmu_pte_write 138795 0
+mmu_recycled 0 0
+mmu_shadow_zapped 40358 0
+mmu_unsync 793 0
+nmi_injections 0 0
+nmi_window 0 0
+pf_fixed 697731 3150
+pf_guest 279349 0
+remote_tlb_flush 5 0
+request_irq 0 0
+signal_exits 1 0
+tlb_flush 200190 0
+</pre><div class="variablelist"><h6>Explanation of variables:</h6><dl class="variablelist"><dt class="varlistentry"><span class="term">efer_reload</span></dt><dd><div class="para">
+ The number of Extended Feature Enable Register (EFER) reloads.
+ </div></dd><dt class="varlistentry"><span class="term">exits</span></dt><dd><div class="para">
+ The count of all <code class="computeroutput">VMEXIT</code> calls.
+ </div></dd><dt class="varlistentry"><span class="term">fpu_reload</span></dt><dd><div class="para">
+ The number of times a <code class="computeroutput">VMENTRY</code> reloaded the FPU state. The <code class="command">fpu_reload</code> is incremented when a guest is using the Floating Point Unit (FPU).
+ </div></dd><dt class="varlistentry"><span class="term">halt_exits</span></dt><dd><div class="para">
+ Number of guest exits due to <code class="computeroutput">halt</code> calls. This type of exit is usually seen when a guest is idle.
+ </div></dd><dt class="varlistentry"><span class="term">halt_wakeup</span></dt><dd><div class="para">
+ Number of wakeups from a <code class="computeroutput">halt</code>.
+ </div></dd><dt class="varlistentry"><span class="term">host_state_reload</span></dt><dd><div class="para">
+ Count of full reloads of the host state (currently tallies MSR setup and guest MSR reads).
+ </div></dd><dt class="varlistentry"><span class="term">hypercalls</span></dt><dd><div class="para">
+ Number of guest hypervisor service calls.
+ </div></dd><dt class="varlistentry"><span class="term">insn_emulation</span></dt><dd><div class="para">
+ Number of guest instructions emulated by the host.
+ </div></dd><dt class="varlistentry"><span class="term">insn_emulation_fail</span></dt><dd><div class="para">
+ Number of failed <code class="computeroutput">insn_emulation</code> attempts.
+ </div></dd><dt class="varlistentry"><span class="term">io_exits</span></dt><dd><div class="para">
+ Number of guest exits from I/O port accesses.
+ </div></dd><dt class="varlistentry"><span class="term">irq_exits</span></dt><dd><div class="para">
+ Number of guest exits due to external interrupts.
+ </div></dd><dt class="varlistentry"><span class="term">irq_injections</span></dt><dd><div class="para">
+ Number of interrupts sent to guests.
+ </div></dd><dt class="varlistentry"><span class="term">irq_window</span></dt><dd><div class="para">
+ Number of guest exits from an outstanding interrupt window.
+ </div></dd><dt class="varlistentry"><span class="term">largepages</span></dt><dd><div class="para">
+ Number of large pages currently in use.
+ </div></dd><dt class="varlistentry"><span class="term">mmio_exits</span></dt><dd><div class="para">
+ Number of guest exits due to memory mapped I/O (MMIO) accesses.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_cache_miss</span></dt><dd><div class="para">
+ Number of KVM MMU shadow pages created.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_flooded</span></dt><dd><div class="para">
+ Detection count of excessive write operations to an MMU page. This counts detected write operations not of individual write operations.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_pde_zapped</span></dt><dd><div class="para">
+ Number of page directory entry (PDE) destruction operations.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_pte_updated</span></dt><dd><div class="para">
+ Number of page table entry (PTE) destruction operations.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_pte_write</span></dt><dd><div class="para">
+ Number of guest page table entry (PTE) write operations.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_recycled</span></dt><dd><div class="para">
+ Number of shadow pages that can be reclaimed.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_shadow_zapped</span></dt><dd><div class="para">
+ Number of invalidated shadow pages.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_unsync</span></dt><dd><div class="para">
+ Number of non-synchronized pages which are not yet unlinked.
+ </div></dd><dt class="varlistentry"><span class="term">nmi_injections</span></dt><dd><div class="para">
+ Number of Non-maskable Interrupt (NMI) injections to the guest.
+ </div></dd><dt class="varlistentry"><span class="term">nmi_window</span></dt><dd><div class="para">
+ Number of guest exits from (outstanding) Non-maskable Interrupt (NMI) windows.
+ </div></dd><dt class="varlistentry"><span class="term">pf_fixed</span></dt><dd><div class="para">
+ Number of fixed (non-paging) page table entry (PTE) maps.
+ </div></dd><dt class="varlistentry"><span class="term">pf_guest</span></dt><dd><div class="para">
+ Number of page faults injected into guests.
+ </div></dd><dt class="varlistentry"><span class="term">remote_tlb_flush</span></dt><dd><div class="para">
+ Number of remote (sibling CPU) Translation Lookaside Buffer (TLB) flush requests.
+ </div></dd><dt class="varlistentry"><span class="term">request_irq</span></dt><dd><div class="para">
+ Number of guest interrupt window request exits.
+ </div></dd><dt class="varlistentry"><span class="term">signal_exits</span></dt><dd><div class="para">
+ Number of guest exits due to pending signals from the host.
+ </div></dd><dt class="varlistentry"><span class="term">tlb_flush</span></dt><dd><div class="para">
+ Number of <code class="computeroutput">tlb_flush</code> operations performed by the hypervisor.
+ </div></dd></dl></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The output information from the <code class="command">kvm_stat</code> command is exported by the KVM hypervisor as pseudo files located in the <code class="filename">/sys/kernel/debug/kvm/</code> directory.
+ </div></div></div></div><div class="section" id="sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles"><div class="titlepage"><div><div><h2 class="title">A.3. 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 Fedora virtualization kernels and their guests.
+ </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 class="listitem"><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. Append the following to the <em class="parameter"><code>kernel</code></em> line: <em class="parameter"><code>console=tty0 console=ttyS0,115200</code></em>.
+ </div><pre class="screen">title Fedora Server (2.6.32-36.x86-64)
+ root (hd0,0)
+ kernel /vmlinuz-2.6.32-36.x86-64 ro root=/dev/volgroup00/logvol00 \
+ <em class="parameter"><code>console=tty0 console=ttyS0,115200</code></em>
+ initrd /initrd-2.6.32-36.x86-64.img
+</pre><div class="para">
+ Reboot the guest.
+ </div><div class="para">
+ On the host, 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 guest console window, select <span class="guilabel"><strong>Serial 1</strong></span> in <span class="guilabel"><strong>Text Consoles</strong></span> from the <span class="guilabel"><strong>View</strong></span> menu.
+ </div></div><div class="section" id="idm12647232"><div class="titlepage"><div><div><h2 class="title" id="idm12647232">A.4. Virtualization log files</h2></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Each fully virtualized guest log is in the <code class="filename">/var/log/libvirt/qemu/</code> directory. Each guest log is named as <em class="replaceable"><code>GuestName</code></em>.log and will be periodically compressed once a size limit is reached.
+ </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">$HOME/.virt-manager</code> directory.
+ </div></div><div class="section" id="sect-Virtualization-Troubleshooting-Loop_device_errors"><div class="titlepage"><div><div><h2 class="title">A.5. 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 eight active loop devices. If more than eight file-based guests or loop devices are needed the number of loop devices configured can be adjusted in the <code class="filename">/etc/modprobe.d/</code>directory. Add the following line:
+ </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 use a 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><div class="section" id="live-migration-errors"><div class="titlepage"><div><div><h2 class="title">A.6. Live Migration Errors</h2></div></div></div><div class="para">
+ There may be cases where a live migration causes the memory contents to be re-transfered over and over again This process causes the guest to be in a state where it is constantly writing to memory and therefore will slow down migration. If this should occur, and the guest is writing more than several tens of MBs per second, then live migration may fail to finish (converge). This issue is scheduled to be fixed in Fedora 19 or 20.
+ </div><div class="para">
+ The current live-migration implementation has a default migration time configured to 30ms. This value determines the guest pause time at the end of the migration in order to transfer the leftovers. Higher values increase the odds that live migration will converge
+ </div></div><div class="section" id="sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS"><div class="titlepage"><div><div><h2 class="title">A.7. Enabling Intel VT-x 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-x extensions can be disabled in the BIOS. Certain laptop vendors have disabled the Intel VT-x extensions by default in their CPUs.
+ </div><div class="para">
+ The virtualization extensions cannot be disabled in the BIOS for AMD-V.
+ </div><div class="para">
+ Refer to the following section for instructions on enabling disabled virtualization extensions.
+ </div><div class="para">
+ Verify the virtualization extensions are enabled in BIOS. The BIOS settings for Intel 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-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS-Enabling_virtualization_extensions_in_BIOS"><h6>Procedure A.1. Enabling virtualization extensions in BIOS</h6><ol class="1"><li class="step"><div class="para">
+ Reboot the computer and open the system's BIOS menu. This can usually be done by pressing the <span class="guibutton"><strong>delete</strong></span> key, the <span class="keycap"><strong>F1</strong></span> key or <span class="keycap"><strong>Alt</strong></span> and <span class="keycap"><strong>F4</strong></span> keys depending on the system.
+ </div></li><li class="step"><p class="title"><strong>Enabling the virtualization extensions in BIOS</strong></p><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Many of the steps below may vary depending on your motherboard, processor type, chipset and OEM. Refer to your system's accompanying documentation for the correct information on configuring your system.
+ </div></div></div><ol class="a"><li class="step"><div class="para">
+ Open the <span class="guilabel"><strong>Processor</strong></span> submenu The processor settings menu may be hidden in the <span class="guilabel"><strong>Chipset</strong></span>, <span class="guilabel"><strong>Advanced CPU Configuration</strong></span> or <span class="guilabel"><strong>Northbridge</strong></span>.
+ </div></li><li class="step"><div class="para">
+ Enable <span class="guilabel"><strong>Intel Virtualization Technology</strong></span> (also known as Intel VT-x). <span class="guilabel"><strong>AMD-V</strong></span> extensions cannot be disabled in the BIOS and should already be enabled. The virtualization extensions may be labeled <span class="guilabel"><strong>Virtualization Extensions</strong></span>, <span class="guilabel"><strong>Vanderpool</strong></span> or various other names depending on the OEM and system BIOS.
+ </div></li><li class="step"><div class="para">
+ Enable Intel VT-d or AMD IOMMU, if the options are available. Intel VT-d and AMD IOMMU are used for PCI device assignment.
+ </div></li><li class="step"><div class="para">
+ Select <span class="guilabel"><strong>Save & Exit</strong></span>.
+ </div></li></ol></li><li class="step"><div class="para">
+ Reboot the machine.
+ </div></li><li class="step"><div class="para">
+ When the machine has booted, run <code class="command">cat /proc/cpuinfo |grep -E "vmx|svm"</code>. Specifying <em class="parameter"><code>--color</code></em> is optional, but useful if you want the search term highlighted. 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><div class="section" id="sect-Virtualization-Troubleshooting-KVM_networking_performance"><div class="titlepage"><div><div><h2 class="title">A.8. KVM networking performance</h2></div></div></div><div class="para">
+ By default, KVM virtual machines are assigned a virtual Realtek 8139 (rtl8139) NIC (network interface controller) if they are Windows guests or the guest type is not specified. Fedora guests are assigned a virtio NIC by default.
+ </div><div class="para">
+ The rtl8139 virtualized NIC works fine in most environments. However, this device can suffer from performance degradation problems on some networks, for example, a 10 Gigabit Ethernet network.
+ </div><div class="para">
+ To improve performance switch to the para-virtualized network driver.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Note that the virtualized Intel PRO/1000 (<code class="systemitem">e1000</code>) driver is also supported as an emulated driver choice. To use the <code class="computeroutput">e1000</code> driver, replace <code class="computeroutput">virtio</code> in the procedure below with <code class="computeroutput">e1000</code>. For the best performance it is recommended to use the <code class="computeroutput">virtio</code> driver.
+ </div></div></div><div class="procedure"><h6>Procedure A.2. Switching to the virtio driver</h6><ol class="1"><li class="step"><div class="para">
+ Shutdown the guest operating system.
+ </div></li><li class="step"><div class="para">
+ Edit the guest's configuration file with the <code class="command">virsh</code> command (where <em class="parameter"><code>GUEST</code></em> is the guest's name):
+ </div><pre class="screen"># virsh edit <em class="parameter"><code>GUEST</code></em>
+</pre><div class="para">
+ The <code class="command">virsh edit</code> command uses the <code class="command">$EDITOR</code> shell variable to determine which editor to use.
+ </div></li><li class="step"><div class="para">
+ Find the network interface section of the configuration. This section resembles the snippet below:
+ </div><pre class="screen"><interface type='network'>
+ <span class="emphasis"><em>[output truncated]</em></span>
+ <model type='rtl8139' />
+</interface>
+</pre></li><li class="step"><div class="para">
+ Change the type attribute of the model element from <em class="parameter"><code>'rtl8139'</code></em> to <em class="parameter"><code>'virtio'</code></em>. This will change the driver from the rtl8139 driver to the e1000 driver.
+ </div><pre class="screen"><interface type='network'>
+ <span class="emphasis"><em>[output truncated]</em></span>
+ <model type=<em class="parameter"><code>'virtio'</code></em> />
+</interface>
+</pre></li><li class="step"><div class="para">
+ Save the changes and exit the text editor
+ </div></li><li class="step"><div class="para">
+ Restart the guest operating system.
+ </div></li></ol></div><div class="formalpara"><h5 class="formalpara" id="idm114861216">Creating new guests using other network drivers</h5>
+ Alternatively, new guests can be created with a different network driver. This may be required if you are having difficulty installing guests over a network connection. This method requires you to have at least one guest already created (possibly installed from CD or DVD) to use as a template.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Create an XML template from an existing guest (in this example, named <em class="replaceable"><code>Guest1</code></em>):
+ </div><pre class="screen"># virsh dumpxml <em class="replaceable"><code>Guest1</code></em> > /tmp/<em class="replaceable"><code>guest-template</code></em>.xml
+</pre></li><li class="step"><div class="para">
+ Copy and edit the XML file and update the unique fields: virtual machine name, UUID, disk image, MAC address, and any other unique parameters. Note that you can delete the UUID and MAC address lines and virsh will generate a UUID and MAC address.
+ </div><pre class="screen"># cp /tmp/<em class="replaceable"><code>guest-template</code></em>.xml /tmp/<em class="replaceable"><code>new-guest</code></em>.xml
+# vi /tmp/<em class="replaceable"><code>new-guest</code></em>.xml
+</pre><div class="para">
+ Add the model line in the network interface section:
+ </div><pre class="screen"> <interface type='network'>
+ <span class="emphasis"><em>[output truncated]</em></span>
+ <model type='virtio' />
+</interface>
+</pre></li><li class="step"><div class="para">
+ Create the new virtual machine:
+ </div><pre class="screen"># virsh define /tmp/new-guest.xml
+# virsh start new-guest
+</pre></li></ol></div></div><div class="section" id="sect-Virtualization-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard"><div class="titlepage"><div><div><h2 class="title">A.9. Missing characters on guest console with Japanese keyboard</h2></div></div></div><div class="para">
+ On a Fedora host, connecting a Japanese keyboard locally to a machine may result in typed characters such as the underscore (the <span class="bold bold"><strong>_</strong></span> character) not being displayed correctly in guest consoles. This occurs because the required keymap is not set correctly by default.
+ </div><div class="para">
+ When Using Fedora with Red Hat Enterprise Linux 6 guests, there is usually no error message produced when pressing the associated key. However, Red Hat Enterprise Linux 4 and Red Hat Enterprise Linux 5 guests may display an error similar to the following:
+ </div><pre class="screen">
+atkdb.c: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0).
+atkbd.c: Use 'setkeycodes 00 <keycode>' to make it known.
+</pre><div class="para">
+ To fix this issue in <code class="command">virt-manager</code>, perform the following steps:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Open the affected guest in <code class="command">virt-manager</code>.
+ </div></li><li class="listitem"><div class="para">
+ Click <span class="guimenu"><strong>View</strong></span> → <span class="guisubmenu"><strong>Details</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ Select <span class="guilabel"><strong>Display VNC</strong></span> in the list.
+ </div></li><li class="listitem"><div class="para">
+ Change <span class="bold bold"><strong>Auto</strong></span> to <span class="bold bold"><strong>ja</strong></span> in the <span class="guilabel"><strong>Keymap</strong></span> pull-down menu.
+ </div></li><li class="listitem"><div class="para">
+ Click the <span class="guilabel"><strong>Apply</strong></span> button.
+ </div></li></ul></div><div class="para">
+ Alternatively, to fix this issue using the <code class="command">virsh edit</code> command on the target guest:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Run <code class="command">virsh edit <target guest></code>
+ </div></li><li class="listitem"><div class="para">
+ Add the following attribute to the <graphics> tag: <span class="bold bold"><strong>keymap='ja'</strong></span>. For example:
+<pre class="screen">
+ <graphics type='vnc' port='-1' autoport='yes' <span class="bold bold"><strong>keymap='ja'</strong></span>/>
+</pre>
+ </div></li></ul></div></div><div class="section" id="sec-known-issues-windows-xp-guests"><div class="titlepage"><div><div><h2 class="title">A.10. Known Windows XP guest issues</h2></div></div></div><div class="para">
+ If you perform device-add quickly followed by device-del using a Windows XP guest, the guest does not eject the device and instead it displays the following error: "The device (device name) cannot be stopped because of an unknown error. Since the device is still being used, do not remove it". It should be noted that newer Windows OS version guests as well as all known Linux guests do not experience this problem. To prevent this issue from happening, wait to delete a device that you just added.
+ </div></div></div><div xml:lang="en-US" class="appendix" id="idm105767440" lang="en-US"><div class="titlepage"><div><div><h1 id="idm105767440" class="title">Common <span class="application"><strong>libvirt</strong></span> errors and troubleshooting</h1></div></div></div><div class="para">
+ This appendix documents common <span class="application"><strong>libvirt</strong></span>-related problems and errors along with instructions for dealing with them.
+ </div><div class="para">
+ Locate the error on the table below and follow the corresponding link under <code class="literal">Solution</code> for detailed troubleshooting information.
+ </div><div class="table"><h6>Table B.1. Common <span class="application">libvirt</span> errors</h6><div class="table-contents"><table summary="Common libvirt errors" border="1"><colgroup><col align="left" class="c1" width="33%" /><col align="left" class="c2" width="33%" /><col align="left" class="c3" width="33%" /></colgroup><thead><tr><th class="" align="left">
+ Error
+ </th><th class="" align="left">
+ Description of problem
+ </th><th class="" align="left">
+ Solution
+ </th></tr></thead><tbody><tr><td class="" align="left">
+ <code class="computeroutput"><span class="application"><strong>libvirtd</strong></span> failed to start</code>
+ </td><td class="" align="left">
+ The <span class="application"><strong>libvirt</strong></span> daemon failed to start. However, there is no information about this error in <code class="filename">/var/log/messages</code>.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Libvirt_Daemon">Section B.1, “<span class="application"><strong>libvirtd</strong></span> failed to start”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Cannot read CA certificate</code>
+ </td><td class="" align="left">
+ This is one of several errors that occur when the URI fails to connect to the hypervisor.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Hypervisor_Connection_Fail">Section B.2, “The URI failed to connect to the hypervisor”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Failed to connect socket ... : Permission denied</code>
+ </td><td class="" align="left">
+ This is one of several errors that occur when the URI fails to connect to the hypervisor.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Hypervisor_Connection_Fail">Section B.2, “The URI failed to connect to the hypervisor”</a>
+ </td></tr><tr><td class="" align="left">
+ Other connectivity errors
+ </td><td class="" align="left">
+ These are other errors that occur when the URI fails to connect to the hypervisor.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Hypervisor_Connection_Fail">Section B.2, “The URI failed to connect to the hypervisor”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Internal error guest CPU is not compatible with host CPU</code>
+ </td><td class="" align="left">
+ The guest virtual machine cannot be started because the host and guest processors are different.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Domain_Processor">Section B.3, “The guest virtual machine cannot be started: <code class="computeroutput">internal error guest CPU is not compatible with host CPU</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Failed to create domain from vm.xml error: monitor socket did not show up.: Connection refused</code>
+ </td><td class="" align="left">
+ The guest virtual machine (or domain) starting fails and returns this error or similar.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Domain_Monitor_Socket">Section B.4, “Guest starting fails with error: <code class="computeroutput">monitor socket did not show up</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Internal error cannot find character device (null)</code>
+ </td><td class="" align="left">
+ This error can occur when attempting to connect a guest's console. It reports that there is no serial console configured for the guest virtual machine.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Domain_Console">Section B.5, “<code class="computeroutput">Internal error cannot find character device (null)</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">No boot device</code>
+ </td><td class="" align="left">
+ After building a guest virtual machine from an existing disk image, the guest booting stalls. However, the guest can start successfully using the <code class="command">QEMU</code> command directly.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Domain_Not_Booting">Section B.6, “Guest virtual machine booting stalls with error: <code class="computeroutput">No boot device</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">The virtual network <em class="replaceable"><code>"default"</code></em> has not been started</code>
+ </td><td class="" align="left">
+ <div class="para">
+ If the <em class="replaceable"><code>default</code></em> network (or other locally-created network) is unable to start, any virtual machine configured to use that network for its connectivity will also fail to start.
+ </div>
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Virt_Net_Not_Starting">Section B.7, “Virtual network <em class="replaceable"><code>default</code></em> has not been started”</a>
+ </td></tr><tr><td class="" align="left">
+ PXE boot (or DHCP) on guest failed
+ </td><td class="" align="left">
+ A guest virtual machine starts successfully, but is unable to acquire an IP address from DHCP, boot using the PXE protocol, or both. This is often a result of a long forward delay time set for the bridge, or when the <span class="package">iptables</span> package and kernel do not support checksum mangling rules.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_PXE_Guest_Boot_Fail">Section B.8, “PXE boot (or DHCP) on guest failed”</a>
+ </td></tr><tr><td class="" align="left">
+ Guest can reach outside network, but cannot reach host when using macvtap interface
+ </td><td class="" align="left">
+ <div class="para">
+ A guest can communicate with other guests, but cannot connect to the host machine after being configured to use a macvtap (or <em class="parameter"><code>type='direct'</code></em>) network interface.
+ </div>
+ <div class="para">
+ This is actually not an error — it is the defined behavior of macvtap.
+ </div>
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Macvtap">Section B.9, “Guest can reach outside network, but cannot reach host when using macvtap interface”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Could not add rule to fixup DHCP response checksums on network <em class="replaceable"><code>'default'</code></em></code>
+ </td><td class="" align="left">
+ This warning message is almost always harmless, but is often mistakenly seen as evidence of a problem.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_DHCP_Response_Checksums">Section B.10, “Could not add rule to fixup DHCP response checksums on network <em class="replaceable"><code>'default'</code></em>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Unable to add bridge br0 port vnet0: No such device</code>
+ </td><td class="" align="left">
+ This error message or the similar <code class="computeroutput">Failed to add tap interface to bridge <em class="replaceable"><code>'br0'</code></em>: No such device</code> reveal that the bridge device specified in the guest's (or domain's) <code class="code"><interface></code> definition does not exist.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Bridge_Device">Section B.11, “Unable to add bridge br0 port vnet0: No such device”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Warning: could not open /dev/net/tun: no virtual network emulation qemu-kvm: -netdev tap,script=/etc/my-qemu-ifup,id=hostnet0: Device 'tap' could not be initialized</code>
+ </td><td class="" align="left">
+ The guest virtual machine does not start after configuring a <code class="code">type='ethernet'</code> (or 'generic ethernet') interface in the host system. This error or similar appears either in <code class="filename">libvirtd.log</code>, <code class="filename">/var/log/libvirt/qemu/<em class="replaceable"><code>name_of_guest</code></em>.log</code>, or in both.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Generic_Ethernet">Section B.12, “Guest is unable to start with error: <code class="computeroutput">warning: could not open /dev/net/tun</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Unable to resolve address <em class="replaceable"><code>name_of_host</code></em> service '49155': Name or service not known</code>
+ </td><td class="" align="left">
+ <span class="application"><strong>QEMU</strong></span> guest migration fails and this error message appears with an unfamiliar hostname.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Migration_Address">Section B.13, “Migration fails with <code class="computeroutput">Error: unable to resolve address</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Unable to allow access for disk path /var/lib/libvirt/images/qemu.img: No such file or directory</code>
+ </td><td class="" align="left">
+ A guest virtual machine cannot be migrated because <span class="application"><strong>libvirt</strong></span> cannot access the disk image(s).
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Migration_Disk_Image">Section B.14, “Migration fails with <code class="computeroutput">Unable to allow access for disk path: No such file or directory</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ No guest virtual machines are present when <span class="application"><strong>libvirtd</strong></span> is started
+ </td><td class="" align="left">
+ The <span class="application"><strong>libvirt</strong></span> daemon is successfully started, but no guest virtual machines appear to be present when running <code class="command">virsh list --all</code>.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_No_Guest_Machines">Section B.15, “No guest virtual machines are present when <span class="application"><strong>libvirtd</strong></span> is started”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor</code>
+ </td><td class="" align="left">
+ While <span class="application"><strong>libvirtd</strong></span> should listen on TCP ports for connections, the connection to the hypervisor fails.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_TCP_Ports">Section B.16, “Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor”</a>
+ </td></tr><tr><td class="" align="left">
+ Common XML errors
+ </td><td class="" align="left">
+ <span class="application"><strong>libvirt</strong></span> uses XML documents to store structured data. Several common errors occur with XML documents when they are passed to <span class="application"><strong>libvirt</strong></span> through the API. This entry provides instructions for editing guest XML definitions, and details common errors in XML syntax and configuration.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_XML_Errors">Section B.17, “Common XML errors”</a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div xml:lang="en-US" class="section" id="App_Libvirt_Daemon" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.1. <span class="application"><strong>libvirtd</strong></span> failed to start</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The <span class="application"><strong>libvirt</strong></span> daemon does not start automatically. Starting the <span class="application"><strong>libvirt</strong></span> daemon manually fails as well:
+ </div><pre class="screen"># /etc/init.d/libvirtd start
+* Caching service dependencies ... [ ok ]
+* Starting libvirtd ...
+/usr/sbin/libvirtd: error: Unable to initialize network sockets. Check /var/log/messages or run without --daemon for more info.
+* start-stop-daemon: failed to start `/usr/sbin/libvirtd' [ !! ]
+* ERROR: libvirtd failed to start</pre><div class="para">
+ Moreover, there is not <code class="literal">'more info'</code> about this error in <code class="filename">/var/log/messages</code>.
+ </div></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ Change <span class="application"><strong>libvirt's</strong></span> logging in <code class="filename">/etc/libvirt/libvirtd.conf</code> by uncommenting the line below. To uncomment the line, open the <code class="filename">/etc/libvirt/libvirtd.conf</code> file in a text editor, remove the hash (or <code class="literal">#</code>) symbol from the beginning of the following line, and save the change:
+ </div><pre class="screen">log_outputs="3:syslog:libvirtd"</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ This line is commented out by default to prevent <span class="application"><strong>libvirt</strong></span> from producing excessive log messages. After diagnosing the problem, it is recommended to comment this line again in the <code class="filename">/etc/libvirt/libvirtd.conf</code> file.
+ </div></div></div><div class="para">
+ Restart <span class="application"><strong>libvirt</strong></span> to determine if this has solved the problem.
+ </div><div class="para">
+ If <code class="filename">libvirtd</code> still does not start successfully, an error similar to the following will be shown in the <code class="filename">/var/log/messages</code> file:
+ </div><pre class="programlisting">Feb 6 17:22:09 bart libvirtd: 17576: info : libvirt version: 0.9.9
+Feb 6 17:22:09 bart libvirtd: 17576: error : virNetTLSContextCheckCertFile:92: Cannot read CA certificate '/etc/pki/CA/cacert.pem': No such file or directory
+Feb 6 17:22:09 bart /etc/init.d/libvirtd[17573]: start-stop-daemon: failed to start `/usr/sbin/libvirtd'
+Feb 6 17:22:09 bart /etc/init.d/libvirtd[17565]: ERROR: libvirtd failed to start</pre><div class="para">
+ The <span class="application"><strong>libvirtd</strong></span> man page shows that the missing <code class="filename">cacert.pem</code> file is used as TLS authority when <span class="application"><strong>libvirt</strong></span> is run in <code class="literal">Listen for TCP/IP connections</code> mode. This means the <em class="parameter"><code>--listen</code></em> parameter is being passed.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Configure the <span class="application"><strong>libvirt</strong></span> daemon's settings with one of the following methods:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Install a CA certificate.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ For more information on CA certificates and configuring system authentication, refer to the Configuring Authentication chapter in the <em class="citetitle">Fedora Deployment Guide</em>.
+ </div></div></div></li><li class="listitem"><div class="para">
+ Do not use TLS; use bare TCP instead. In <code class="filename">/etc/libvirt/libvirtd.conf</code> set <code class="option">listen_tls = 0</code> and <code class="option">listen_tcp = 1</code>. The default values are <code class="option">listen_tls = 1</code> and <code class="option">listen_tcp = 0</code>.
+ </div></li><li class="listitem"><div class="para">
+ Do not pass the <em class="parameter"><code>--listen</code></em> parameter. In <code class="filename">/etc/sysconfig/libvirtd.conf</code> change the <em class="parameter"><code>LIBVIRTD_ARGS</code></em> variable.
+ </div></li></ul></div></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_Hypervisor_Connection_Fail" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.2. The URI failed to connect to the hypervisor</h2></div></div></div><div class="para">
+ Several different errors can occur when connecting to the server (for example, when running <code class="command">virsh</code>).
+ </div><div class="section" id="Sect_Cannot_read_CA_certificate"><div class="titlepage"><div><div><h3 class="title">B.2.1. Cannot read CA certificate</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ When running a command, the following error (or similar) appears:
+ </div><pre class="screen">$ virsh -c <em class="replaceable"><code>name_of_uri</code></em> list
+error: Cannot read CA certificate '/etc/pki/CA/cacert.pem': No such file or directory
+error: failed to connect to the hypervisor</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ The error message is misleading about the actual cause. This error can be caused by a variety of factors, such as an incorrectly specified URI, or a connection that is not configured.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Incorrectly specified URI</span></dt><dd><div class="para">
+ When specifying <em class="parameter"><code>qemu://system</code></em> or <em class="parameter"><code>qemu://session</code></em> as a connection URI, <code class="command">virsh</code> attempts to connect to hostnames <em class="parameter"><code>system</code></em> or <em class="parameter"><code>session</code></em> respectively. This is because <code class="command">virsh</code> recognizes the text after the second forward slash as the host.
+ </div><div class="para">
+ Use three forward slashes to connect to the local host. For example, specifying <em class="parameter"><code>qemu:///system</code></em> instructs <code class="command">virsh</code> connect to the <em class="parameter"><code>system</code></em> instance of <span class="application"><strong>libvirtd</strong></span> on the local host.
+ </div><div class="para">
+ When a hostname is specified, the <span class="application"><strong>QEMU</strong></span> transport defaults to <code class="systemitem">TLS</code>. This results in certificates.
+ </div></dd><dt class="varlistentry"><span class="term">Connection is not configured</span></dt><dd><div class="para">
+ The URI is correct (for example, <em class="parameter"><code>qemu[+tls]://server/system</code></em>) but the certificates are not set up properly on your machine. For information on configuring TLS, see <a href="http://wiki.libvirt.org/page/TLSSetup">Setting up <span class="application"><strong>libvirt</strong></span> for TLS</a> available from the <span class="application"><strong>libvirt</strong></span> website.
+ </div></dd></dl></div></dd></dl></div></div><div class="section" id="Sect_Failed_to_connect_socket"><div class="titlepage"><div><div><h3 class="title">B.2.2. Failed to connect socket ... : Permission denied</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ When running a <code class="command">virsh</code> command, the following error (or similar) appears:
+ </div><pre class="screen">$ virsh -c qemu:///system list
+error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Permission denied
+error: failed to connect to the hypervisor</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ Without any hostname specified, the connection to <span class="application"><strong>QEMU</strong></span> uses UNIX sockets by default. If there is no error running this command as root, the UNIX socket options in <code class="filename">/etc/libvirt/libvirtd.conf</code> are likely misconfigured.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ To connect as a non-root user using UNIX sockets, configure the following options in <code class="filename">/etc/libvirt/libvirtd.conf</code>:
+ </div><pre class="programlisting">unix_sock_group = <code class="literal"><group></code>
+unix_sock_ro_perms = <perms>
+unix_sock_rw_perms = <perms></pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The user running <code class="command">virsh</code> must be a member of the <code class="literal">group</code> specified in the <code class="option">unix_sock_group</code> option.
+ </div></div></div></dd></dl></div></div><div class="section" id="Sect_Other_Connectivity_Errors"><div class="titlepage"><div><div><h3 class="title">B.2.3. Other connectivity errors</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Unable to connect to server at <code class="literal">server:port</code>: Connection refused</span></dt><dd><div class="para">
+ The daemon is not running on the server or is configured not to listen, using configuration option <code class="option">listen_tcp</code> or <code class="option">listen_tls</code>.
+ </div></dd><dt class="varlistentry"><span class="term">End of file while reading data: nc: using stream socket: Input/output error</span></dt><dd><div class="para">
+ If you specified <code class="systemitem">ssh</code> transport, the daemon is likely not running on the server. Solve this error by verifying that the daemon is running on the server.
+ </div></dd></dl></div></div></div><div xml:lang="en-US" class="section" id="App_Domain_Processor" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.3. The guest virtual machine cannot be started: <code class="computeroutput">internal error guest CPU is not compatible with host CPU</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ Running on an Intel Core i7 processor (which <span class="application"><strong>virt-manager</strong></span> refers to as <code class="literal">Nehalem</code>, or the older Core 2 Duo, referred to as <code class="literal">Penryn</code>), a KVM guest (or domain) is created using <span class="application"><strong>virt-manager</strong></span>. After installation, the guest's processor is changed to match the host's CPU. The guest is then unable to start and reports this error:
+ </div><pre class="screen">2012-02-06 17:49:15.985+0000: 20757: error : qemuBuildCpuArgStr:3565 : internal error guest CPU is not compatible with host CPU</pre><div class="para">
+ Additionally, clicking <code class="literal">Copy host CPU configuration</code> in <span class="application"><strong>virt-manager</strong></span> shows Pentium III instead of <code class="literal">Nehalem</code> or <code class="literal">Penryn</code>.
+ </div></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ The <code class="filename">/usr/share/libvirt/cpu_map.xml</code> file lists the flags that define each CPU model. The <code class="literal">Nehalem</code> and <code class="literal">Penryn</code> definitions contain this:
+ </div><pre class="programlisting"><feature name='nx'/></pre><div class="para">
+ As a result, the <code class="literal">NX</code> (or <code class="literal">No eXecute</code>) flag needs to be presented to identify the CPU as <code class="literal">Nehalem</code> or <code class="literal">Penryn</code>. However, in <code class="filename">/proc/cpuinfo</code>, this flag is missing.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Nearly all new BIOSes allow enabling or disabling of the <code class="literal">No eXecute</code> bit. However, if disabled, some CPUs do not report this flag and thus <span class="application"><strong>libvirt</strong></span> detects a different CPU. Enabling this functionality instructs <span class="application"><strong>libvirt</strong></span> to report the correct CPU. Refer to your hardware documentation for further instructions on this subject.
+ </div></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_Domain_Monitor_Socket" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.4. Guest starting fails with error: <code class="computeroutput">monitor socket did not show up</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The guest virtual machine (or domain) starting fails with this error (or similar):
+ </div><pre class="screen"># virsh -c qemu:///system create <em class="replaceable"><code>name_of_guest</code></em>.xml error: Failed to create domain from <em class="replaceable"><code>name_of_guest</code></em>.xml error: monitor socket did not show up.: Connection refused</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This error message shows:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <span class="application"><strong>libvirt</strong></span> is working;
+ </div></li><li class="listitem"><div class="para">
+ The <span class="application"><strong>QEMU</strong></span> process failed to start up; and
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>libvirt</strong></span> quits when trying to connect <span class="application"><strong>QEMU</strong></span> or the QEMU agent monitor socket.
+ </div></li></ol></div><div class="para">
+ To understand the error details, examine the guest log:
+ </div><pre class="screen"># cat /var/log/libvirt/qemu/<em class="replaceable"><code>name_of_guest</code></em>.log
+LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-kvm -S -M pc -enable-kvm -m 768 -smp 1,sockets=1,cores=1,threads=1 -name <em class="replaceable"><code>name_of_guest</code></em> -uuid ebfaadbe-e908-ba92-fdb8-3fa2db557a42 -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/<em class="replaceable"><code>name_of_guest</code></em>.monitor,server,nowait -mon chardev=monitor,mode=readline -no-reboot -boot c -kernel /var/lib/libvirt/boot/vmlinuz -initrd /var/lib/libvirt/boot/initrd.img -append method=http://www.example.com/pub/product/release/version/x86_64/os/ -drive file=/var/lib/libvirt/images/<em class="replaceable"><code>name_of_guest</code></em>.img,if=none,id=drive-ide0-0-0,boot=on -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -device virtio-net-pci,vlan=0,id=net0,mac=52:40:00:f4:f1:0a,bus=pci.0,addr=0x4 -net tap,fd=42,vlan=0,name=hostnet0 -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -vnc 127
.0.0.1:0 -k en-gb -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,
+addr=0x3
+char device redirected to /dev/pts/1
+qemu: could not load kernel '/var/lib/libvirt/boot/vmlinuz':
+Permission denied</pre></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ The guest log contains the details needed to fix the error.
+ </div><div class="para">
+ If a host is shut down while the guest is still running a <span class="application"><strong>libvirt</strong></span> version prior to 0.9.5, the libvirt-guest's init script attempts to perform a managed save of the guest. If the managed save was incomplete (for example, due to loss of power before the managed save image was flushed to disk), the save image is corrupted and will not be loaded by <span class="application"><strong>QEMU</strong></span>. The older version of <span class="application"><strong>libvirt</strong></span> does not recognize the corruption, making the problem perpetual. In this case, the guest log will show an attempt to use <code class="command">-incoming</code> as one of its arguments, meaning that <span class="application"><strong>libvirt</strong></span> is trying to start <span class="application"><strong>QEMU</strong></span> by migrating in the saved state file.
+ </div><div class="para">
+ This problem can be fixed by running <code class="command">virsh managedsave-remove <em class="replaceable"><code>name_of_guest</code></em></code> to remove the corrupted managed save image. Newer versions of <span class="application"><strong>libvirt</strong></span> take steps to avoid the corruption in the first place, as well as adding <code class="command">virsh start --force-boot <em class="replaceable"><code>name_of_guest</code></em></code> to bypass any managed save image.
+ </div></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_Domain_Console" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.5. <code class="computeroutput">Internal error cannot find character device (null)</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ This error message appears when attempting to connect to a guest virtual machine's console:
+ </div><pre class="screen"># virsh console test2 Connected to domain test2 Escape character is ^] error: internal error cannot find character device (null)</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This error message shows that there is no serial console configured for the guest virtual machine.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Set up a serial console in the guest's XML file.
+ </div><div class="procedure"><h6>Procedure B.1. Setting up a serial console in the guest's XML</h6><ol class="1"><li class="step"><div class="para">
+ Add the following XML to the guest virtual machine's XML using <span class="application"><strong>virsh edit</strong></span>:
+ </div><pre class="programlisting"><serial type='pty'>
+ <target port='0'/>
+</serial>
+<console type='pty'>
+ <target type='serial' port='0'/>
+</console></pre></li><li class="step"><div class="para">
+ Set up the console in the guest kernel command line.
+ </div><div class="para">
+ To do this, either log in to the guest virtual machine to edit the <code class="filename">/boot/grub/grub.conf</code> file directly, or use the <span class="application"><strong>virt-edit</strong></span> command line tool. Add the following to the guest kernel command line:
+ </div><pre class="screen">console=ttyS0,115200</pre></li><li class="step"><div class="para">
+ Run the followings command:
+ </div><pre class="screen"># virsh start vm && virsh console vm</pre></li></ol></div></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_Domain_Not_Booting" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.6. Guest virtual machine booting stalls with error: <code class="computeroutput">No boot device</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ After building a guest virtual machine from an existing disk image, the guest booting stalls with the error message <code class="computeroutput">No boot device</code>. However, the guest virtual machine can start successfully using the <code class="command">QEMU</code> command directly.
+ </div></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ The disk's bus type is not specified in the command for importing the existing disk image:
+ </div><pre class="screen"># virt-install \
+--connect qemu:///system \
+--ram 2048 -n rhel_64 \
+--os-type=linux --os-variant=rhel5 \
+--disk path=/root/RHEL-Server-5.8-64-virtio.qcow2,device=disk,format=qcow2 \
+--vcpus=2 --graphics spice --noautoconsole --import
+</pre><div class="para">
+ However, the command line used to boot up the guest virtual machine using <span class="application"><strong>QEMU</strong></span> directly shows that it uses <code class="literal">virtio</code> for its bus type:
+ </div><pre class="screen"># ps -ef | grep qemu
+/usr/libexec/qemu-kvm -monitor stdio -drive file=/root/RHEL-Server-5.8-32-virtio.qcow2,index=0,<span class="bold bold"><strong>if=virtio</strong></span>,media=disk,cache=none,format=qcow2 -net nic,vlan=0,model=rtl8139,macaddr=00:30:91:aa:04:74 -net tap,vlan=0,script=/etc/qemu-ifup,downscript=no -m 2048 -smp 2,cores=1,threads=1,sockets=2 -cpu qemu64,+sse2 -soundhw ac97 -rtc-td-hack -M rhel5.6.0 -usbdevice tablet -vnc :10 -boot c -no-kvm-pit-reinjection</pre><div class="para">
+ Note the <em class="parameter"><code>bus=</code></em> in the guest's XML generated by <span class="application"><strong>libvirt</strong></span> for the imported guest:
+ </div><pre class="programlisting">
+<domain type='qemu'>
+ <name>rhel_64</name>
+ <uuid>6cd34d52-59e3-5a42-29e4-1d173759f3e7</uuid>
+ <memory>2097152</memory>
+ <currentMemory>2097152</currentMemory>
+ <vcpu>2</vcpu>
+ <os>
+ <type arch='x86_64' machine='rhel5.4.0'>hvm</type>
+ <boot dev='hd'/>
+ </os>
+ <features>
+ <acpi/>
+ <apic/>
+ <pae/>
+ </features>
+ <clock offset='utc'>
+ <timer name='pit' tickpolicy='delay'/>
+ </clock>
+ <on_poweroff>destroy</on_poweroff>
+ <on_reboot>restart</on_reboot>
+ <on_crash>restart</on_crash>
+ <devices>
+ <emulator>/usr/libexec/qemu-kvm</emulator>
+ <disk type='file' device='disk'>
+ <driver name='qemu' type='qcow2' cache='none'/>
+ <source file='/root/RHEL-Server-5.8-64-virtio.qcow2'/>
+ <emphasis role="bold"><target dev='hda' bus='ide'/></emphasis>
+ <address type='drive' controller='0' bus='0' unit='0'/>
+ </disk>
+ <controller type='ide' index='0'/>
+ <interface type='bridge'>
+ <mac address='54:52:00:08:3e:8c'/>
+ <source bridge='br0'/>
+ </interface>
+ <serial type='pty'>
+ <target port='0'/>
+ </serial>
+ <console type='pty'>
+ <target port='0'/>
+ </console>
+ <input type='mouse' bus='ps2'/>
+ <graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
+ <video>
+ <model type='cirrus' vram='9216' heads='1'/>
+ </video>
+ </devices>
+ </domain>
+</pre><div class="para">
+ The bus type for the disk is set as <em class="parameter"><code>ide</code></em>, which is the default value set by <span class="application"><strong>libvirt</strong></span>. This is the incorrect bus type, and has caused the unsuccessful boot for the imported guest.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="procedure"><h6>Procedure B.2. Correcting the disk bus type</h6><ol class="1"><li class="step"><div class="para">
+ Undefine the imported guest, then re-import it with <em class="parameter"><code>bus=virtio</code></em> and the following:
+ </div><pre class="screen"># virsh destroy rhel_64
+# virsh undefine rhel_64
+# virt-install \
+--connect qemu:///system \
+--ram 1024 -n rhel_64 -r 2048 \
+--os-type=linux --os-variant=rhel5 \
+--disk path=/root/RHEL-Server-5.8-64-virtio.qcow2,device=disk,<span class="bold bold"><strong>bus=virtio</strong></span>,format=qcow2 \
+--vcpus=2 --graphics spice --noautoconsole --import</pre></li><li class="step"><div class="para">
+ Edit the imported guest's XML using <code class="command">virsh edit</code> and correct the disk bus type.
+ </div></li></ol></div></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_Virt_Net_Not_Starting" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.7. Virtual network <em class="replaceable"><code>default</code></em> has not been started</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ Normally, the configuration for a virtual network named <em class="replaceable"><code>default</code></em> is installed as part of the <span class="package">libvirt</span> package, and is configured to autostart when <span class="application"><strong>libvirtd</strong></span> is started.
+ </div><div class="para">
+ If the <em class="replaceable"><code>default</code></em> network (or any other locally-created network) is unable to start, any virtual machine configured to use that network for its connectivity will also fail to start, resulting in this error message:
+ </div><pre class="screen">Virtual network <em class="replaceable"><code>default</code></em> has not been started</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ One of the most common reasons for a <span class="application"><strong>libvirt</strong></span> virtual network's failure to start is that the dnsmasq instance required to serve DHCP and DNS requests from clients on that network has failed to start.
+ </div><div class="para">
+ To determine if this is the cause, run <code class="command">virsh net-start default</code> from a root shell to start the <em class="replaceable"><code>default</code></em> virtual network.
+ </div><div class="para">
+ If this action does not successfully start the virtual network, open <code class="filename">/var/log/libvirt/libvirtd.log</code> to view the complete error log message.
+ </div><div class="para">
+ If a message similar to the following appears, the problem is likely a systemwide dnsmasq instance that is already listening on <span class="application"><strong>libvirt</strong></span>'s bridge, and is preventing <span class="application"><strong>libvirt</strong></span>'s own dnsmasq instance from doing so. The most important parts to note in the error message are <code class="literal">dnsmasq</code> and <code class="literal">exit status 2</code>:
+ </div><pre class="screen">Could not start virtual network <em class="replaceable"><code>default</code></em>: internal error
+Child process (/usr/sbin/dnsmasq --strict-order --bind-interfaces
+--pid-file=/var/run/libvirt/network/<em class="replaceable"><code>default</code></em>.pid --conf-file=
+--except-interface lo --listen-address 192.168.122.1
+--dhcp-range 192.168.122.2,192.168.122.254
+--dhcp-leasefile=/var/lib/libvirt/dnsmasq/<em class="replaceable"><code>default</code></em>.leases
+--dhcp-lease-max=253 --dhcp-no-override) status unexpected: exit status 2</pre></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ If the machine is not using dnsmasq to serve DHCP for the physical network, disable dnsmasq completely.
+ </div><div class="para">
+ If it is necessary to run dnsmasq to serve DHCP for the physical network, edit the <code class="filename">/etc/dnsmasq.conf</code> file. Add or uncomment the first line, as well as one of the two lines following that line. Do not add or uncomment all three lines:
+ </div><pre class="programlisting">bind-interfaces
+interface=<em class="replaceable"><code>name_of_physical_interface</code></em>
+listen-address=<em class="replaceable"><code>chosen_IP_address</code></em></pre><div class="para">
+ After making this change and saving the file, restart the systemwide dnsmasq service.
+ </div><div class="para">
+ Next, start the <em class="replaceable"><code>default</code></em> network with the <code class="command">virsh net-start default</code> command.
+ </div><div class="para">
+ Start the virtual machines.
+ </div></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_PXE_Guest_Boot_Fail" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.8. PXE boot (or DHCP) on guest failed</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ A guest virtual machine starts successfully, but is then either unable to acquire an IP address from DHCP or boot using the PXE protocol, or both. There are two common causes of this error: having a long forward delay time set for the bridge, and when the <span class="package">iptables</span> package and kernel do not support checksum mangling rules.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Long forward delay time on bridge</span></dt><dd><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This is the most common cause of this error. If the guest network interface is connecting to a bridge device that has STP (Spanning Tree Protocol) enabled, as well as a long forward delay set, the bridge will not forward network packets from the guest virtual machine onto the bridge until at least that number of forward delay seconds have elapsed since the guest connected to the bridge. This delay allows the bridge time to watch traffic from the interface and determine the MAC addresses behind it, and prevent forwarding loops in the network topology.
+ </div><div class="para">
+ If the forward delay is longer than the timeout of the guest's PXE or DHCP client, then the client's operation will fail, and the guest will either fail to boot (in the case of PXE) or fail to acquire an IP address (in the case of DHCP).
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ If this is the case, change the forward delay on the bridge to 0, disable STP on the bridge, or both.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ This solution applies only if the bridge is not used to connect multiple networks, but just to connect multiple endpoints to a single network (the most common use case for bridges used by <span class="application"><strong>libvirt</strong></span>).
+ </div></div></div><div class="para">
+ If the guest has interfaces connecting to a <span class="application"><strong>libvirt</strong></span>-managed virtual network, edit the definition for the network, and restart it. For example, edit the default network with the following command:
+ </div><pre class="screen"># virsh net-edit default</pre><div class="para">
+ Add the following attributes to the <code class="code"><bridge></code> element:
+ </div><pre class="programlisting"><<em class="replaceable"><code>name_of_bridge</code></em>='virbr0' <code class="code">delay='0' stp='on'</code>/></pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ <code class="code">delay='0'</code> and <code class="code">stp='on'</code> are the default settings for virtual networks, so this step is only necessary if the configuration has been modified from the default.
+ </div></div></div><div class="para">
+ If the guest interface is connected to a host bridge that was configured outside of <span class="application"><strong>libvirt</strong></span>, change the delay setting.
+ </div><div class="para">
+ Add or edit the following lines in the <code class="filename">/etc/sysconfig/network-scripts/ifcfg-<em class="replaceable"><code>name_of_bridge</code></em></code> file to turn STP on with a 0 second delay:
+ </div><pre class="programlisting">STP=on
+DELAY=0</pre><div class="para">
+ After changing the configuration file, restart the bridge device:
+ </div><pre class="programlisting">/sbin/ifdown <em class="replaceable"><code>name_of_bridge</code></em>
+/sbin/ifup <em class="replaceable"><code>name_of_bridge</code></em></pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If <em class="replaceable"><code>name_of_bridge</code></em> is not the root bridge in the network, that bridge's delay will eventually reset to the delay time configured for the root bridge. In this case, the only solution is to disable STP completely on <em class="replaceable"><code>name_of_bridge</code></em>.
+ </div></div></div></dd></dl></div></dd></dl></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">The <span class="package">iptables</span> package and kernel do not support checksum mangling rules</span></dt><dd><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This message is only a problem if all four of the following conditions are true:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The guest is using <span class="application"><strong>virtio</strong></span> network devices.
+ </div><div class="para">
+ If so, the configuration file will contain <code class="code">model type='virtio'</code>
+ </div></li><li class="listitem"><div class="para">
+ The host has the <code class="literal">vhost-net</code> module loaded.
+ </div><div class="para">
+ This is true if <code class="computeroutput"><code class="command">ls</code> <code class="filename">/dev/vhost-net</code></code> does not return an empty result.
+ </div></li><li class="listitem"><div class="para">
+ The guest is attempting to get an IP address from a DHCP server that is running directly on the host.
+ </div></li><li class="listitem"><div class="para">
+ The <span class="package">iptables</span> version on the host is older than 1.4.10.
+ </div><div class="para">
+ <span class="package">iptables</span> 1.4.10 was the first version to add the <code class="literal">libxt_CHECKSUM</code> extension. This is the case if the following message appears in the <span class="application"><strong>libvirtd</strong></span> logs:
+ </div><pre class="screen">warning: Could not add rule to fixup DHCP response checksums on network <em class="replaceable"><code>default</code></em>
+warning: May need to update iptables package and kernel to support CHECKSUM rule.</pre><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Unless all of the other three conditions in this list are also true, the above warning message can be disregarded, and is not an indicator of any other problems.
+ </div></div></div></li></ul></div><div class="para">
+ When these conditions occur, UDP packets sent from the host to the guest have uncomputed checksums. This makes the host's UDP packets seem invalid to the guest's network stack.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ To solve this problem, invalidate any of the four points above. The best solution is to update the host <span class="package">iptables</span> and kernel to <span class="package">iptables-1.4.10</span> or newer where possible. Otherwise, the most specific fix is to disable the <code class="literal">vhost-net</code> driver for this particular guest. To do this, edit the guest configuration with this command:
+ </div><pre class="screen">virsh edit <em class="replaceable"><code>name_of_guest</code></em></pre><div class="para">
+ Change or add a <code class="code"><driver></code> line to the <code class="code"><interface></code> section:
+ </div><pre class="programlisting"><interface type='network'>
+ <model type='virtio'/>
+ <driver name='qemu'/>
+ ...
+</interface></pre><div class="para">
+ Save the changes, shut down the guest, and then restart it.
+ </div><div class="para">
+ If this problem is still not resolved, the issue may be due to a conflict between <span class="application"><strong>firewalld</strong></span> and the default <span class="application"><strong>libvirt</strong></span> network.
+ </div><div class="para">
+ To fix this, stop <span class="application"><strong>firewalld</strong></span> with the <code class="command">service firewalld stop</code> command, then restart <span class="application"><strong>libvirt</strong></span> with the <code class="command">service libvirtd restart</code> command.
+ </div></dd></dl></div></dd></dl></div></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_Macvtap" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.9. Guest can reach outside network, but cannot reach host when using macvtap interface</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ A guest virtual machine can communicate with other guests, but cannot connect to the host machine after being configured to use a macvtap (also known as <em class="parameter"><code>type='direct'</code></em>) network interface.
+ </div></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ Even when not connecting to a Virtual Ethernet Port Aggregator (VEPA) or VN-Link capable switch, macvtap interfaces can be useful. Setting the mode of such an interface to <code class="option">bridge</code> allows the guest to be directly connected to the physical network in a very simple manner without the setup issues (or <span class="package">NetworkManager</span> incompatibility) that can accompany the use of a traditional host bridge device.
+ </div><div class="para">
+ However, when a guest virtual machine is configured to use a <em class="parameter"><code>type='direct'</code></em> network interface such as macvtap, despite having the ability to communicate with other guests and other external hosts on the network, the guest cannot communicate with its own host.
+ </div><div class="para">
+ This situation is actually not an error — it is the defined behavior of macvtap. Due to the way in which the host's physical Ethernet is attached to the macvtap bridge, traffic into that bridge from the guests that is forwarded to the physical interface cannot be bounced back up to the host's IP stack. Additionally, traffic from the host's IP stack that is sent to the physical interface cannot be bounced back up to the macvtap bridge for forwarding to the guests.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Use <span class="application"><strong>libvirt</strong></span> to create an isolated network, and create a second interface for each guest virtual machine that is connected to this network. The host and guests can then directly communicate over this isolated network, while also maintaining compatibility with <span class="package">NetworkManager</span>.
+ </div><div class="procedure"><h6>Procedure B.3. Creating an isolated network with <span class="application"><strong>libvirt</strong></span></h6><ol class="1"><li class="step"><div class="para">
+ Add and save the following XML in the <code class="filename">/tmp/isolated.xml</code> file. If the 192.168.254.0/24 network is already in use elsewhere on your network, you can choose a different network.
+ </div><pre class="programlisting"><network>
+ <name>isolated</name>
+ <ip address='192.168.254.1' netmask='255.255.255.0'>
+ <dhcp>
+ <range start='192.168.254.2' end='192.168.254.254' />
+ </dhcp>
+ </ip>
+</network></pre></li><li class="step"><div class="para">
+ Create the network with this command: <code class="command">virsh net-define /tmp/isolated.xml</code>
+ </div></li><li class="step"><div class="para">
+ Set the network to autostart with the <code class="command">virsh net-autostart isolated</code> command.
+ </div></li><li class="step"><div class="para">
+ Start the network with the <code class="command">virsh net-start isolated</code> command.
+ </div></li><li class="step"><div class="para">
+ Using <code class="command">virsh edit <em class="replaceable"><code>name_of_guest</code></em></code>, edit the configuration of each guest that uses macvtap for its network connection and add a new <em class="parameter"><code><interface></code></em> in the <em class="parameter"><code><devices></code></em> section similar to the following (note the <em class="parameter"><code><model type='virtio'/></code></em> line is optional to include):
+ </div><pre class="programlisting"><interface type='network'>
+ <source network='isolated'/>
+ <model type='virtio'/>
+</interface></pre></li><li class="step"><div class="para">
+ Shut down, then restart each of these guests.
+ </div></li></ol></div><div class="para">
+ The guests are now able to reach the host at the address 192.168.254.1, and the host will be able to reach the guests at the IP address they acquired from DHCP (alternatively, you can manually configure the IP addresses for the guests). Since this new network is isolated to only the host and guests, all other communication from the guests will use the macvtap interface.
+ </div></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_DHCP_Response_Checksums" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.10. Could not add rule to fixup DHCP response checksums on network <em class="replaceable"><code>'default'</code></em></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ This message appears:
+ </div><pre class="screen">Could not add rule to fixup DHCP response checksums on network <em class="replaceable"><code>'default'</code></em></pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ Although this message appears to be evidence of an error, it is almost always harmless.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Unless the problem you are experiencing is that the guest virtual machines are unable to acquire IP addresses through DHCP, this message can be ignored.
+ </div><div class="para">
+ If this is the case, refer to <a class="xref" href="#App_PXE_Guest_Boot_Fail">Section B.8, “PXE boot (or DHCP) on guest failed”</a> for further details on this situation.
+ </div></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_Bridge_Device" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.11. Unable to add bridge br0 port vnet0: No such device</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The following error message appears:
+ </div><pre class="screen">Unable to add bridge <em class="replaceable"><code>name_of_bridge</code></em> port vnet0: No such device</pre><div class="para">
+ For example, if the bridge name is <em class="replaceable"><code>br0</code></em>, the error message will appear as:
+ </div><pre class="screen">Unable to add bridge br0 port vnet0: No such device</pre><div class="para">
+ In <span class="application"><strong>libvirt</strong></span> versions 0.9.6 and earlier, the same error appears as:
+ </div><pre class="screen">Failed to add tap interface to bridge <em class="replaceable"><code>name_of_bridge</code></em>: No such device</pre><div class="para">
+ Or for example, if the bridge is named <em class="replaceable"><code>br0</code></em>:
+ </div><pre class="screen">Failed to add tap interface to bridge <em class="replaceable"><code>'br0'</code></em>: No such device</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ Both error messages reveal that the bridge device specified in the guest's (or domain's) <code class="code"><interface></code> definition does not exist.
+ </div><div class="para">
+ To verify the bridge device listed in the error message does not exist, use the shell command <code class="command">ifconfig <em class="replaceable"><code>br0</code></em></code>.
+ </div><div class="para">
+ A message similar to this confirms the host has no bridge by that name:
+ </div><pre class="screen"><em class="replaceable"><code>br0</code></em>: error fetching interface information: Device not found</pre><div class="para">
+ If this is the case, continue to the solution.
+ </div><div class="para">
+ However, if the resulting message is similar to the following, the issue exists elsewhere:
+ </div><pre class="screen"><em class="replaceable"><code>br0</code></em> Link encap:Ethernet HWaddr 00:00:5A:11:70:48
+ inet addr:10.22.1.5 Bcast:10.255.255.255 Mask:255.0.0.0
+ UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
+ RX packets:249841 errors:0 dropped:0 overruns:0 frame:0
+ TX packets:281948 errors:0 dropped:0 overruns:0 carrier:0
+ collisions:0 txqueuelen:0
+ RX bytes:106327234 (101.4 MiB) TX bytes:21182634 (20.2 MiB)</pre></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Edit the existing bridge or create a new bridge with <code class="command">virsh</code></span></dt><dd><div class="para">
+ Use <code class="command">virsh</code> to either edit the settings of an existing bridge or network, or to add the bridge device to the host system configuration.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Edit the existing bridge settings using <code class="command">virsh</code></span></dt><dd><div class="para">
+ Use <code class="command">virsh edit <em class="replaceable"><code>name_of_guest</code></em></code> to change the <code class="code"><interface></code> definition to use a bridge or network that already exists.
+ </div><div class="para">
+ For example, change <code class="code">type='bridge'</code> to <code class="code">type='network'</code>, and <code class="code"><source bridge='br0'/></code> to <code class="code"><source network='default'/></code>.
+ </div></dd><dt class="varlistentry"><span class="term">Create a host bridge using <code class="command">virsh</code></span></dt><dd><div class="para">
+ For <span class="application"><strong>libvirt</strong></span> version 0.9.8 and later, a bridge device can be created with the <code class="command">virsh iface-bridge</code> command. This will create a bridge device <em class="replaceable"><code>br0</code></em> with <code class="filename">eth0</code>, the physical network interface which is set as part of a bridge, attached:
+ </div><pre class="screen">virsh iface-bridge eth0 <em class="replaceable"><code>br0</code></em></pre><div class="para">
+ Optional: If desired, remove this bridge and restore the original <code class="filename">eth0</code> configuration with this command:
+ </div><pre class="screen">virsh iface-unbridge <em class="replaceable"><code>br0</code></em></pre></dd></dl></div></dd><dt class="varlistentry"><span class="term">Create a host bridge manually</span></dt><dd><div class="para">
+ For older versions of <span class="application"><strong>libvirt</strong></span>, it is possible to manually create a bridge device on the host. Refer to <a class="xref" href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt">Section 11.3, “Bridged networking with libvirt”</a> for instructions.
+ </div></dd></dl></div></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_Generic_Ethernet" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.12. Guest is unable to start with error: <code class="computeroutput">warning: could not open /dev/net/tun</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The guest virtual machine does not start after configuring a <code class="code">type='ethernet'</code> (also known as 'generic ethernet') interface in the host system. An error appears either in <code class="filename">libvirtd.log</code>, <code class="filename">/var/log/libvirt/qemu/<em class="replaceable"><code>name_of_guest</code></em>.log</code>, or in both, similar to the below message:
+ </div><pre class="screen">warning: could not open /dev/net/tun: no virtual network emulation qemu-kvm: -netdev tap,script=/etc/my-qemu-ifup,id=hostnet0: Device 'tap' could not be initialized</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ Use of the generic ethernet interface type (<code class="code"><interface type='ethernet'></code>) is discouraged, because using it requires lowering the level of host protection against potential security flaws in <span class="application"><strong>QEMU</strong></span> and its guests. However, it is sometimes necessary to use this type of interface to take advantage of some other facility that is not yet supported directly in <span class="application"><strong>libvirt</strong></span>. For example, <span class="application"><strong>openvswitch</strong></span> was not supported in <span class="application"><strong>libvirt</strong></span> until <span class="package">libvirt-0.9.11</span>, so in older versions of <span class="application"><strong>libvirt</strong></span>, <code class="code"><interface type='ethernet'></code> was the only way to connect a guest to an <span class="application"><strong>openvswitch</strong></span> bridge.
+ </div><div class="para">
+ However, if you configure a <code class="code"><interface type='ethernet'></code> interface without making any other changes to the host system, the guest virtual machine will not start successfully.
+ </div><div class="para">
+ The reason for this failure is that for this type of interface, a script called by <span class="application"><strong>QEMU</strong></span> needs to manipulate the tap device. However, with <code class="code">type='ethernet'</code> configured, in an attempt to lock down <span class="application"><strong>QEMU</strong></span>, <span class="application"><strong>libvirt</strong></span> and SELinux have put in place several checks to prevent this. (Normally, <span class="application"><strong>libvirt</strong></span> performs all of the tap device creation and manipulation, and passes an open file descriptor for the tap device to <span class="application"><strong>QEMU</strong></span>.)
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Reconfigure the host system to be compatible with the generic ethernet interface.
+ </div><div class="procedure"><h6>Procedure B.4. Reconfiguring the host system to use the generic ethernet interface</h6><ol class="1"><li class="step"><div class="para">
+ Set SELinux to permissive by configuring <code class="code">SELINUX=permissive</code> in <code class="filename">/etc/selinux/config</code>:
+ </div><pre class="screen"># This file controls the state of SELinux on the system.
+# SELINUX= can take one of these three values:
+# enforcing - SELinux security policy is enforced.
+# permissive - SELinux prints warnings instead of enforcing.
+# disabled - No SELinux policy is loaded.
+SELINUX=permissive
+# SELINUXTYPE= can take one of these two values:
+# targeted - Targeted processes are protected,
+# mls - Multi Level Security protection.
+SELINUXTYPE=targeted</pre></li><li class="step"><div class="para">
+ From a root shell, run the command <code class="command">setenforce permissive</code>.
+ </div></li><li class="step"><div class="para">
+ In <code class="filename">/etc/libvirt/qemu.conf</code> add or edit the following lines:
+ </div><pre class="screen">clear_emulator_capabilities = 0</pre><pre class="screen">user = "root"</pre><pre class="screen">group = "root"</pre><pre class="screen">cgroup_device_acl = [
+ "/dev/null", "/dev/full", "/dev/zero",
+ "/dev/random", "/dev/urandom",
+ "/dev/ptmx", "/dev/kvm", "/dev/kqemu",
+ "/dev/rtc", "/dev/hpet", "/dev/net/tun",</pre></li><li class="step"><div class="para">
+ Restart <code class="filename">libvirtd</code>.
+ </div></li></ol></div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Since each of these steps significantly decreases the host's security protections against <span class="application"><strong>QEMU</strong></span> guest domains, this configuration should only be used if there is no alternative to using <code class="code"><interface type='ethernet'></code>.
+ </div></div></div></dd></dl></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ For more information on SELinux, refer to the <em class="citetitle">Fedora Security Guide</em>.
+ </div></div></div></div><div xml:lang="en-US" class="section" id="App_Migration_Address" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.13. Migration fails with <code class="computeroutput">Error: unable to resolve address</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ <span class="application"><strong>QEMU</strong></span> guest migration fails and this error message appears:
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://192.168.122.12/system
+ error: Unable to resolve address <em class="replaceable"><code>name_of_host</code></em> service '49155': Name or service not known</pre><div class="para">
+ For example, if the destination hostname is "newyork", the error message will appear as:
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://192.168.122.12/system
+error: Unable to resolve address <em class="replaceable"><code>'newyork'</code></em> service '49155': Name or service not known</pre><div class="para">
+ However, this error looks strange as we did not use "newyork" hostname anywhere.
+ </div></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ During migration, <span class="application"><strong>libvirtd</strong></span> running on the destination host creates a URI from an address and port where it expects to receive migration data and sends it back to <span class="application"><strong>libvirtd</strong></span> running on the source host.
+ </div><div class="para">
+ In this case, the destination host (<code class="literal">192.168.122.12</code>) has its name set to <em class="replaceable"><code>'newyork'</code></em>. For some reason, <span class="application"><strong>libvirtd</strong></span> running on that host is unable to resolve the name to an IP address that could be sent back and still be useful. For this reason, it returned the <em class="replaceable"><code>'newyork'</code></em> hostname hoping the source <span class="application"><strong>libvirtd</strong></span> would be more successful with resolving the name. This can happen if DNS is not properly configured or <code class="filename">/etc/hosts</code> has the hostname associated with local loopback address (<code class="filename">127.0.0.1</code>).
+ </div><div class="para">
+ Note that the address used for migration data cannot be automatically determined from the address used for connecting to destination <span class="application"><strong>libvirtd</strong></span> (for example, from <code class="filename">qemu+tcp://192.168.122.12/system</code>). This is because to communicate with the destination <span class="application"><strong>libvirtd</strong></span>, the source <span class="application"><strong>libvirtd</strong></span> may need to use network infrastructure different from that which <span class="application"><strong>virsh</strong></span> (possibly running on a separate machine) requires.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ The best solution is to configure DNS correctly so that all hosts involved in migration are able to resolve all host names.
+ </div><div class="para">
+ If DNS cannot be configured to do this, a list of every host used for migration can be added manually to the <code class="filename">/etc/hosts</code> file on each of the hosts. However, it is difficult to keep such lists consistent in a dynamic environment.
+ </div><div class="para">
+ If the host names cannot be made resolvable by any means, <code class="command">virsh migrate</code> supports specifying the migration host:
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://192.168.122.12/system tcp://192.168.122.12</pre><div class="para">
+ Destination <span class="application"><strong>libvirtd</strong></span> will take the <code class="literal">tcp://192.168.122.12</code> URI and append an automatically generated port number. If this is not desirable (because of firewall configuration, for example), the port number can be specified in this command:
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://192.168.122.12/system tcp://192.168.122.12:12345</pre><div class="para">
+ Another option is to use tunnelled migration. Tunnelled migration does not create a separate connection for migration data, but instead tunnels the data through the connection used for communication with destination <span class="application"><strong>libvirtd</strong></span> (for example, <code class="filename">qemu+tcp://192.168.122.12/system</code>):
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://192.168.122.12/system --p2p --tunnelled</pre></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_Migration_Disk_Image" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.14. Migration fails with <code class="computeroutput">Unable to allow access for disk path: No such file or directory</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ A guest virtual machine (or domain) cannot be migrated because <span class="application"><strong>libvirt</strong></span> cannot access the disk image(s):
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://<em class="replaceable"><code>name_of_host</code></em>/system
+error: Unable to allow access for disk path /var/lib/libvirt/images/qemu.img: No such file or directory</pre><div class="para">
+ For example, if the destination hostname is "newyork", the error message will appear as:
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://<em class="replaceable"><code>newyork</code></em>/system
+error: Unable to allow access for disk path /var/lib/libvirt/images/qemu.img: No such file or directory</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ By default, migration only transfers the in-memory state of a running guest (such as memory or CPU state). Although disk images are not transferred during migration, they need to remain accessible at the same path by both hosts.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Set up and mount shared storage at the same location on both hosts. The simplest way to do this is to use NFS:
+ </div><div class="procedure"><h6>Procedure B.5. Setting up shared storage</h6><ol class="1"><li class="step"><div class="para">
+ Set up an NFS server on a host serving as shared storage. The NFS server can be one of the hosts involved in the migration, as long as all hosts involved are accessing the shared storage through NFS.
+ </div><pre class="screen"># mkdir -p /exports/images
+# cat >>/etc/exports <<EOF
+/exports/images 192.168.122.0/24(rw,no_root_squash)
+EOF</pre></li><li class="step"><div class="para">
+ Mount the exported directory at a common location on all hosts running <span class="application"><strong>libvirt</strong></span>. For example, if the IP address of the NFS server is 192.168.122.1, mount the directory with the following commands:
+ </div><pre class="screen"># cat >>/etc/fstab <<EOF
+192.168.122.1:/exports/images /var/lib/libvirt/images nfs auto 0 0
+EOF
+# mount /var/lib/libvirt/images</pre></li></ol></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ It is not possible to export a local directory from one host using NFS and mount it at the same path on another host — the directory used for storing disk images must be mounted from shared storage on both hosts. If this is not configured correctly, the guest virtual machine may lose access to its disk images during migration, because the source host's <span class="application"><strong>libvirt</strong></span> daemon may change the owner, permissions, and SELinux labels on the disk images after it successfully migrates the guest to its destination.
+ </div><div class="para">
+ If <span class="application"><strong>libvirt</strong></span> detects that the disk images are mounted from a shared storage location, it will not make these changes.
+ </div></div></div></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_No_Guest_Machines" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.15. No guest virtual machines are present when <span class="application"><strong>libvirtd</strong></span> is started</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The <span class="application"><strong>libvirt</strong></span> daemon is successfully started, but no guest virtual machines appear to be present.
+ </div><pre class="screen"># virsh list --all
+ Id Name State
+----------------------------------------------------
+#
+</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ There are various possible causes of this problem. Performing these tests will help to determine the cause of this situation:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Verify KVM kernel modules</span></dt><dd><div class="para">
+ Verify that KVM kernel modules are inserted in the kernel:
+ </div><pre class="screen"># lsmod | grep kvm
+kvm_intel 121346 0
+kvm 328927 1 kvm_intel</pre><div class="para">
+ If you are using an AMD machine, verify the <code class="systemitem">kvm_amd</code> kernel modules are inserted in the kernel instead, using the similar command <code class="command">lsmod | grep kvm_amd</code> in the root shell.
+ </div><div class="para">
+ If the modules are not present, insert them using the <code class="command">modprobe <em class="replaceable"><code><modulename></code></em></code> command.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Although it is uncommon, KVM virtualization support may be compiled into the kernel. In this case, modules are not needed.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">Verify virtualization extensions</span></dt><dd><div class="para">
+ Verify that virtualization extensions are supported and enabled on the host:
+ </div><pre class="screen"># egrep "(vmx|svm)" /proc/cpuinfo
+flags : fpu vme de pse tsc ... svm ... skinit wdt npt lbrv svm_lock nrip_save
+flags : fpu vme de pse tsc ... svm ... skinit wdt npt lbrv svm_lock nrip_save</pre><div class="para">
+ Enable virtualization extensions in your hardware's firmware configuration within the BIOS setup. Refer to your hardware documentation for further details on this.
+ </div></dd><dt class="varlistentry"><span class="term">Verify client URI configuration</span></dt><dd><div class="para">
+ Verify that the URI of the client is configured as desired:
+ </div><pre class="screen"># virsh uri
+vbox:///system</pre><div class="para">
+ For example, this message shows the URI is connected to the <span class="application"><strong>VirtualBox</strong></span> hypervisor, not <span class="application"><strong>QEMU</strong></span>, and reveals a configuration error for a URI that is otherwise set to connect to a <span class="application"><strong>QEMU</strong></span> hypervisor. If the URI was correctly connecting to <span class="application"><strong>QEMU</strong></span>, the same message would appear instead as:
+ </div><pre class="screen"># virsh uri
+qemu:///system</pre><div class="para">
+ This situation occurs when there are other hypervisors present, which <span class="application"><strong>libvirt</strong></span> may speak to by default.
+ </div></dd></dl></div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ After performing these tests, use the following command to view a list of guest virtual machines:
+ </div><pre class="screen"># virsh list --all</pre></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_TCP_Ports" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.16. Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ While <span class="application"><strong>libvirtd</strong></span> should listen on TCP ports for connections, the connections fail:
+ </div><pre class="screen"># virsh -c qemu+tcp://host/system
+error: unable to connect to server at 'host:16509': Connection refused
+error: failed to connect to the hypervisor</pre><div class="para">
+ The <span class="application"><strong>libvirt</strong></span> daemon is not listening on TCP ports even after changing configuration in <code class="filename">/etc/libvirt/libvirtd.conf</code>:
+ </div><pre class="screen"># grep listen_ /etc/libvirt/libvirtd.conf
+listen_tls = 1
+listen_tcp = 1
+listen_addr = "0.0.0.0"</pre><div class="para">
+ However, the TCP ports for <span class="application"><strong>libvirt</strong></span> are still not open after changing configuration:
+ </div><pre class="screen"># netstat -lntp | grep libvirtd
+#</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ The <span class="application"><strong>libvirt</strong></span> daemon was started without the <code class="option">--listen</code> option. Verify this by running this command:
+ </div><pre class="screen"># ps aux | grep libvirtd
+root 27314 0.0 0.0 1000920 18304 ? Sl Feb16 1:19 libvirtd --daemon</pre><div class="para">
+ The output does not contain the <code class="option">--listen</code> option.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Start the daemon with the <code class="option">--listen</code> option.
+ </div><div class="para">
+ To do this, modify the <code class="filename">/etc/sysconfig/libvirtd</code> file and uncomment the following line:
+ </div><pre class="screen">#LIBVIRTD_ARGS="--listen"</pre><div class="para">
+ Then restart the <span class="application"><strong>libvirtd</strong></span> service with this command:
+ </div><pre class="screen"># /etc/init.d/libvirtd restart</pre></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_XML_Errors" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.17. Common XML errors</h2></div></div></div><div class="para">
+ The <span class="application"><strong>libvirt</strong></span> tool uses XML documents to store structured data. A variety of common errors occur with XML documents when they are passed to <span class="application"><strong>libvirt</strong></span> through the API. Several common XML errors — including misformatted XML, inappropriate values, and missing elements — are detailed below.
+ </div><div class="section" id="idm115036144"><div class="titlepage"><div><div><h3 class="title" id="idm115036144">B.17.1. Editing domain definition</h3></div></div></div><div class="para">
+ Although it is not recommended, it is sometimes necessary to edit a guest virtual machine's (or a domain's) XML file manually. To access the guest's XML for editing, use the following command:
+ </div><pre class="screen"># virsh edit <em class="replaceable"><code>name_of_guest.xml</code></em></pre><div class="para">
+ This command opens the file in a text editor with the current definition of the guest virtual machine. After finishing the edits and saving the changes, the XML is reloaded and parsed by <span class="application"><strong>libvirt</strong></span>. If the XML is correct, the following message is displayed:
+ </div><pre class="screen"># virsh edit <em class="replaceable"><code>name_of_guest.xml</code></em>
+
+Domain <em class="replaceable"><code>name_of_guest.xml</code></em> XML configuration edited.</pre><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ When using the <code class="command">edit</code> command in <span class="application"><strong>virsh</strong></span> to edit an XML document, save all changes before exiting the editor.
+ </div></div></div><div class="para">
+ After saving the XML file, use the <code class="command">xmllint</code> command to validate that the XML is well-formed, or the <code class="command">virt-xml-validate</code> command to check for usage problems:
+ </div><pre class="screen"># xmllint --noout config.xml</pre><pre class="screen"># virt-xml-validate config.xml</pre><div class="para">
+ If no errors are returned, the XML description is well-formed and matches the <span class="application"><strong>libvirt</strong></span> schema. While the schema does not catch all constraints, fixing any reported errors will further troubleshooting.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">XML documents stored by <span class="application"><strong>libvirt</strong></span></span></dt><dd><div class="para">
+ These documents contain definitions of states and configurations for the guests. These documents are automatically generated and should not be edited manually. Errors in these documents contain the file name of the broken document. The file name is valid only on the host machine defined by the URI, which may refer to the machine the command was run on.
+ </div><div class="para">
+ Errors in files created by <span class="application"><strong>libvirt</strong></span> are rare. However, one possible source of these errors is a downgrade of <span class="application"><strong>libvirt</strong></span> — while newer versions of <span class="application"><strong>libvirt</strong></span> can always read XML generated by older versions, older versions of <span class="application"><strong>libvirt</strong></span> may be confused by XML elements added in a newer version.
+ </div></dd></dl></div></div><div class="section" id="idm98827392"><div class="titlepage"><div><div><h3 class="title" id="idm98827392">B.17.2. XML syntax errors</h3></div></div></div><div class="para">
+ Syntax errors are caught by the XML parser. The error message contains information for identifying the problem.
+ </div><div class="para">
+ This example error message from the XML parser consists of three lines — the first line denotes the error message, and the two following lines contain the context and location of the XML code containing the error. The third line contains an indicator showing approximately where the error lies on the line above it:
+ </div><pre class="screen">error: (<em class="replaceable"><code>name_of_guest.xml</code></em>):6: StartTag: invalid element name
+<vcpu>2</vcpu><
+-----------------^</pre><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Information contained in this message:</span></dt><dd><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">(<em class="replaceable"><code>name_of_guest.xml</code></em>)</span></dt><dd><div class="para">
+ This is the file name of the document that contains the error. File names in parentheses are symbolic names to describe XML documents parsed from memory, and do not directly correspond to files on disk. File names that are not contained in parentheses are local files that reside on the target of the connection.
+ </div></dd><dt class="varlistentry"><span class="term">6</span></dt><dd><div class="para">
+ This is the line number in the XML file that contains the error.
+ </div></dd><dt class="varlistentry"><span class="term">StartTag: invalid element name </span></dt><dd><div class="para">
+ This is the error message from the <span class="application"><strong>libxml2</strong></span> parser, which describes the specific XML error.
+ </div></dd></dl></div></dd></dl></div><div class="section" id="idm74208464"><div class="titlepage"><div><div><h4 class="title" id="idm74208464">B.17.2.1. Stray <code class="literal"><</code> in the document</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The following error occurs:
+ </div><pre class="screen">error: (<em class="replaceable"><code>name_of_guest.xml</code></em>):6: StartTag: invalid element name
+<vcpu>2</vcpu><
+-----------------^</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This error message shows that the parser expects a new element name after the <code class="literal"><</code> symbol on line 6 of a guest's XML file.
+ </div><div class="para">
+ Ensure line number display is enabled in your text editor. Open the XML file, and locate the text on line 6:
+ </div><pre class="screen"><domain type='kvm'>
+ <name><em class="replaceable"><code>name_of_guest</code></em></name>
+<memory>524288</memory>
+<vcpu>2</vcpu><
+</pre><div class="para">
+ This snippet of a guest's XML file contains an extra <code class="literal"><</code> in the document:
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Remove the extra <code class="literal"><</code> or finish the new element.
+ </div></dd></dl></div></div><div class="section" id="idm85906768"><div class="titlepage"><div><div><h4 class="title" id="idm85906768">B.17.2.2. Unterminated attribute</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The following error occurs:
+ </div><pre class="screen">error: (<em class="replaceable"><code>name_of_guest.xml</code></em>):2: Unescaped '<' not allowed in attributes values
+<name><em class="replaceable"><code>name_of_guest</code></em></name>
+--^</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This snippet of a guest's XML file contains an unterminated element attribute value:
+ </div><pre class="screen"><domain type='kvm>
+<name><em class="replaceable"><code>name_of_guest</code></em></name></pre><div class="para">
+ In this case, <code class="literal">'kvm'</code> is missing a second quotation mark. Strings of attribute values, such as quotation marks and apostrophes, must be opened and closed, similar to XML start and end tags.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Correctly open and close all attribute value strings.
+ </div></dd></dl></div></div><div class="section" id="idm98732288"><div class="titlepage"><div><div><h4 class="title" id="idm98732288">B.17.2.3. Opening and ending tag mismatch</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The following error occurs:
+ </div><pre class="screen">error: (<em class="replaceable"><code>name_of_guest.xml</code></em>):61: Opening and ending tag mismatch: clock line 16 and domain
+</domain>
+---------^</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ The error message above contains three clues to identify the offending tag:
+ </div><div class="para">
+ The message following the last colon, <code class="literal">clock line 16 and domain</code>, reveals that <code class="literal"><clock></code> contains a mismatched tag on line 16 of the document. The last hint is the pointer in the context part of the message, which identifies the second offending tag.
+ </div><div class="para">
+ Unpaired tags must be closed with <code class="literal">/></code>. The following snippet does not follow this rule and has produced the error message shown above:
+ </div><pre class="screen"><domain type='kvm'>
+ ...
+ <clock offset='utc'></pre><div class="para">
+ This error is caused by mismatched XML tags in the file. Every XML tag must have a matching start and end tag.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Other examples of mismatched XML tags</span></dt><dd><div class="para">
+ The following examples produce similar error messages and show variations of mismatched XML tags.
+ </div><div class="para">
+ This snippet contains an unended pair tag for <code class="literal"><features></code>:
+ </div><pre class="screen"><domain type='kvm'>
+ ...
+ <features>
+ <acpi/>
+ <pae/>
+ ...
+ </domain></pre><div class="para">
+ This snippet contains an end tag (<code class="literal"></name></code>) without a corresponding start tag:
+ </div><pre class="screen"><domain type='kvm'>
+ </name>
+ ...
+</domain></pre></dd></dl></div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Ensure all XML tags start and end correctly.
+ </div></dd></dl></div></div><div class="section" id="idm14753296"><div class="titlepage"><div><div><h4 class="title" id="idm14753296">B.17.2.4. Typographical errors in tags</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The following error message appears:
+ </div><pre class="screen">error: (name_of_guest.xml):1: Specification mandate value for attribute ty
+<domain ty pe='kvm'>
+-----------^</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ XML errors are easily caused by a simple typographical error. This error message highlights the XML error — in this case, an extra white space within the word <code class="literal">type</code> — with a pointer.
+ </div><pre class="screen"><domain ty pe='kvm'></pre><div class="para">
+ These XML examples will not parse correctly because of typographical errors such as a missing special character, or an additional character:
+ </div><pre class="screen"><domain type 'kvm'></pre><pre class="screen"><dom#ain type='kvm'></pre></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ To identify the problematic tag, read the error message for the context of the file, and locate the error with the pointer. Correct the XML and save the changes.
+ </div></dd></dl></div></div></div><div class="section" id="idm99205120"><div class="titlepage"><div><div><h3 class="title" id="idm99205120">B.17.3. Logic and configuration errors</h3></div></div></div><div class="para">
+ A well-formatted XML document can contain errors that are correct in syntax but <span class="application"><strong>libvirt</strong></span> cannot parse. Many of these errors exist, with two of the most common cases outlined below.
+ </div><div class="section" id="idm93916544"><div class="titlepage"><div><div><h4 class="title" id="idm93916544">B.17.3.1. Vanishing parts</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ Parts of the change you have made do not show up and have no effect after editing or defining the domain. The <code class="command">define</code> or <code class="command">edit</code> command works, but when dumping the XML once again, the change disappears.
+ </div></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This error likely results from a broken construct or syntax that libvirt does not parse. The <span class="application"><strong>libvirt</strong></span> tool will generally only look for constructs it knows but ignore everything else, resulting in some of the XML changes vanishing after <span class="application"><strong>libvirt</strong></span> parses the input.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Validate the XML input before passing it to the <code class="command">edit</code> or <code class="command">define</code> commands. The <span class="application"><strong>libvirt</strong></span> developers maintain a set of XML schemas bundled with <span class="application"><strong>libvirt</strong></span> which define the majority of the constructs allowed in XML documents used by <span class="application"><strong>libvirt</strong></span>.
+ </div><div class="para">
+ Validate <span class="application"><strong>libvirt</strong></span> XML files using the following command:
+ </div><pre class="screen"># virt-xml-validate libvirt.xml</pre><div class="para">
+ If this command passes, <span class="application"><strong>libvirt</strong></span> will likely understand all constructs from your XML, except if the schemas cannot detect options which are valid only for a given hypervisor. Any XML generated by <span class="application"><strong>libvirt</strong></span> as a result of a <code class="command">virsh dump</code> command, for example, should validate without error.
+ </div></dd></dl></div></div><div class="section" id="idm101738592"><div class="titlepage"><div><div><h4 class="title" id="idm101738592">B.17.3.2. Incorrect drive device type</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The definition of the source image for the CD-ROM virtual drive is not present, despite being added:
+ </div><pre class="screen"># virsh dumpxml domain
+<domain type='kvm'>
+ ...
+ <disk type='block' device='cdrom'>
+ <driver name='qemu' type='raw'/>
+ <target dev='hdc' bus='ide'/>
+ <readonly/>
+ </disk>
+ ...
+</domain></pre></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Correct the XML by adding the missing <code class="code"><source></code> parameter as follows:
+ </div><pre class="screen"><disk type='block' device='cdrom'>
+ <driver name='qemu' type='raw'/>
+ <source file='/path/to/image.iso'/>
+ <target dev='hdc' bus='ide'/>
+ <readonly/>
+</disk></pre><div class="para">
+ A <code class="code">type='block'</code> disk device expects that the source is a physical device. To use the disk with an image file, use <code class="code">type='file'</code> instead.
+ </div></dd></dl></div></div></div></div></div><div xml:lang="en-US" class="appendix" id="netkvm-parameters" lang="en-US"><div class="titlepage"><div><div><h1 class="title">NetKVM Driver Parameters</h1></div></div></div><div class="para">
+ After the NetKVM driver is installed, you can configure it to better suit your environment. The parameters listed in this section can be configured in the Windows <span class="guilabel"><strong>Device Manager</strong></span> (<code class="filename">devmgmt.msc</code>).
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Modifying the driver's parameters causes Windows to re-load that driver. This interrupts existing network activity.
+ </div></div></div><div class="procedure"><h6>Procedure C.1. Configuring NetKVM Parameters</h6><ol class="1"><li class="step"><p class="title"><strong>Open <span class="guilabel"><strong>Device Manager</strong></span></strong></p><div class="para">
+ Click on the <span class="guibutton"><strong>Start</strong></span> button. In the right-hand pane, right-click on <span class="guilabel"><strong>Computer</strong></span>, and click <span class="guilabel"><strong>Manage</strong></span>. If prompted, click <span class="guibutton"><strong>Continue</strong></span> on the <span class="guilabel"><strong>User Account Control</strong></span> window. This opens the <span class="guilabel"><strong>Computer Management</strong></span> window.
+ </div><div class="para">
+ In the left-hand pane of the <span class="guilabel"><strong>Computer Management</strong></span> window, click <span class="guilabel"><strong>Device Manager</strong></span>.
+ </div></li><li class="step"><p class="title"><strong>Locate the correct device</strong></p><div class="para">
+ In the central pane of the <span class="guilabel"><strong>Computer Management</strong></span> window, click on the <span class="guilabel"><strong>+</strong></span> symbol beside <span class="guilabel"><strong>Network adapters</strong></span>.
+ </div><div class="para">
+ Under the list of <span class="guilabel"><strong>Fedora VirtIO Ethernet Adapter</strong></span> devices, double-click on <span class="guilabel"><strong>NetKVM</strong></span>. This opens the <span class="guilabel"><strong>Properties</strong></span> window for that device.
+ </div></li><li class="step"><p class="title"><strong>View device parameters</strong></p><div class="para">
+ In the <span class="guilabel"><strong>Properties</strong></span> window, click on the <span class="guilabel"><strong>Advanced</strong></span> tab.
+ </div></li><li class="step"><p class="title"><strong>Modify device parameters</strong></p><div class="para">
+ Click on the parameter you wish to modify to display the options for that parameter.
+ </div><div class="para">
+ Modify the options as appropriate, then click on <span class="guibutton"><strong>OK</strong></span> to save your changes.
+ </div></li></ol></div><div class="section" id="idm84429120"><div class="titlepage"><div><div><h2 class="title" id="idm84429120">C.1. Configurable parameters for NetKVM</h2></div></div></div><div class="variablelist"><h6>Logging parameters</h6><dl class="variablelist"><dt class="varlistentry"><span class="term">Logging.Enable</span></dt><dd><div class="para">
+ A Boolean value that determines whether logging is enabled. The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">Logging.Level</span></dt><dd><div class="para">
+ An integer that defines the logging level. As the integer increases, so does the verbosity of the log. The default value is <code class="literal">0</code> (errors only). <code class="literal">1-2</code> adds configuration messages. <code class="literal">3-4</code> adds packet flow information. <code class="literal">5-6</code> adds interrupt and DPC level trace information.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ High logging levels will slow down your guest virtual machine.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">Logging.Statistics(sec)</span></dt><dd><div class="para">
+ An integer that defines whether log statistics are printed, and the time in seconds between each periodical statistics printout. The default value is <code class="literal">0</code> (no logging statistics).
+ </div></dd></dl></div><div class="variablelist"><h6>Initial parameters</h6><dl class="variablelist"><dt class="varlistentry"><span class="term">Assign MAC</span></dt><dd><div class="para">
+ A string that defines the locally-administered MAC address for the para-virtualized NIC. This is not set by default.
+ </div></dd><dt class="varlistentry"><span class="term">Init.ConnectionRate(Mb)</span></dt><dd><div class="para">
+ An integer that represents the connection rate in megabytes. The default value for Windows 2008 and later is <code class="literal">10000</code>.
+ </div></dd><dt class="varlistentry"><span class="term">Init.Do802.1PQ</span></dt><dd><div class="para">
+ A Boolean value that enables Priority/VLAN tag population and removal support. The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">Init.UseMergedBuffers</span></dt><dd><div class="para">
+ A Boolean value that enables merge-able RX buffers. The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">Init.UsePublishEvents</span></dt><dd><div class="para">
+ A Boolean value that enables published event use. The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">Init.MTUSize</span></dt><dd><div class="para">
+ An integer that defines the maximum transmission unit (MTU). The default value is <code class="literal">1500</code>. Any value from 500 to 65500 is acceptable.
+ </div></dd><dt class="varlistentry"><span class="term">Init.IndirectTx</span></dt><dd><div class="para">
+ Controls whether indirect ring descriptors are in use. The default value is <code class="literal">Disable</code>, which disables use of indirect ring descriptors. Other valid values are <code class="literal">Enable</code>, which enables indirect ring descriptor usage; and <code class="literal">Enable*</code>, which enables conditional use of indirect ring descriptors.
+ </div></dd><dt class="varlistentry"><span class="term">Init.MaxTxBuffers</span></dt><dd><div class="para">
+ An integer that represents the amount of TX ring descriptors that will be allocated. The default value is <code class="literal">1024</code>. Valid values are: 16, 32, 64, 128, 256, 512, or 1024.
+ </div></dd><dt class="varlistentry"><span class="term">Init.MaxRxBuffers</span></dt><dd><div class="para">
+ An integer that represents the amount of RX ring descriptors that will be allocated. The default value is <code class="literal">256</code>. Valid values are: 16, 32, 64, 128, 256, 512, or 1024.
+ </div></dd><dt class="varlistentry"><span class="term">Offload.Tx.Checksum</span></dt><dd><div class="para">
+ Specifies the TX checksum offloading mode.
+ </div><div class="para">
+ In Fedora 18 and onward, the valid values for this parameter are <code class="literal">All</code> (the default), which enables IP, TCP and UDP checksum offloading for both IPv4 and IPv6; <code class="literal">TCP/UDP(v4,v6)</code>, which enables TCP and UDP checksum offloading for both IPv4 and IPv6; <code class="literal">TCP/UDP(v4)</code>, which enables TCP and UDP checksum offloading for IPv4 only; and <code class="literal">TCP(v4)</code>, which enables only TCP checksum offloading for IPv4 only.
+ </div><div class="para">
+ In Fedora 17 and earlier, the valid values for this parameter are <code class="literal">TCP/UDP</code> (the default value), which enables TCP and UDP checksum offload; <code class="literal">TCP</code>, which enables only TCP checksum offload; or <code class="literal">Disable</code>, which disables TX checksum offload.
+ </div></dd><dt class="varlistentry"><span class="term">Offload.Tx.LSO</span></dt><dd><div class="para">
+ A Boolean value that enables TX TCP Large Segment Offload (LSO). The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">Offload.Rx.Checksum</span></dt><dd><div class="para">
+ Specifies the RX checksum offloading mode.
+ </div><div class="para">
+ In Fedora 18 and onward, the valid values for this parameter are <code class="literal">All</code> (the default), which enables IP, TCP and UDP checksum offloading for both IPv4 and IPv6; <code class="literal">TCP/UDP(v4,v6)</code>, which enables TCP and UDP checksum offloading for both IPv4 and IPv6; <code class="literal">TCP/UDP(v4)</code>, which enables TCP and UDP checksum offloading for IPv4 only; and <code class="literal">TCP(v4)</code>, which enables only TCP checksum offloading for IPv4 only.
+ </div><div class="para">
+ In Fedora 17 and earlier, the valid values are <code class="literal">Disable</code> (the default), which disables RX checksum offloading; <code class="literal">All</code>, which enables TCP, UDP, and IP checksum offloading; <code class="literal">TCP/UDP</code>, which enables TCP and UDP checksum offloading; and <code class="literal">TCP</code>, which enables only TCP checksum offloading.
+ </div></dd></dl></div><div class="variablelist"><h6>Test and debug parameters</h6><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Test and debug parameters should only be used for testing or debugging; they should not be used in production.
+ </div></div></div><dl class="variablelist"><dt class="varlistentry"><span class="term">TestOnly.DelayConnect(ms)</span></dt><dd><div class="para">
+ The period for which to delay connection upon startup, in milliseconds. The default value is <code class="literal">0</code>.
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.DPCChecking</span></dt><dd><div class="para">
+ Sets the DPC checking mode. <code class="literal">0</code> (the default) disables DPC checking. <code class="literal">1</code> enables DPC checking; each hang test verifies DPC activity and acts as if the DPC was spawned. <code class="literal">2</code> clears the device interrupt status and is otherwise identical to <code class="literal">1</code>.
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.Scatter-Gather</span></dt><dd><div class="para">
+ A Boolean value that determines whether scatter-gather functionality is enabled. The default value is <code class="literal">1</code> (enabled). Setting this value to <code class="literal">0</code> disables scatter-gather functionality and all dependent capabilities.
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.InterruptRecovery</span></dt><dd><div class="para">
+ A Boolean value that determines whether interrupt recovery is enabled. The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.PacketFilter</span></dt><dd><div class="para">
+ A Boolean value that determines whether packet filtering is enabled. The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.BatchReceive</span></dt><dd><div class="para">
+ A Boolean value that determines whether packets are received in batches, or singularly. The default value is <code class="literal">1</code>, which enables batched packet receipt.
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.Promiscuous</span></dt><dd><div class="para">
+ A Boolean value that determines whether promiscuous mode is enabled. The default value is <code class="literal">0</code> (disabled).
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.AnalyzeIPPackets</span></dt><dd><div class="para">
+ A Boolean value that determines whether the checksum fields of outgoing IP packets are tested and verified for debugging purposes. The default value is <code class="literal">0</code> (no checking).
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.RXThrottle</span></dt><dd><div class="para">
+ An integer that determines the number of receive packets handled in a single DPC. The default value is <code class="literal">1000</code>.
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.UseSwTxChecksum</span></dt><dd><div class="para">
+ A Boolean value that determines whether hardware checksumming is enabled. The default value is <code class="literal">0</code> (disabled).
+ </div></dd></dl></div></div></div><div xml:lang="en-US" class="appendix" id="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist" lang="en-US"><div class="titlepage"><div><div><h1 class="title">qemu-kvm Whitelist</h1></div></div></div><div class="section" id="idm115407088"><div class="titlepage"><div><div><h2 class="title" id="idm115407088">D.1. Introduction</h2></div></div></div><h4 id="idm35456224">Product identification</h4><div class="para">
+ Fedora
+ </div><h4 id="idm84631872">Objectives</h4><div class="para">
+ The primary objective of this whitelist is to provide a complete list of the supported options of the <code class="command">qemu-kvm</code> utility used as an emulator and a virtualizer in Fedora. This is a comprehensive summary of the supported options.
+ </div><h4 id="idm95689392">Background</h4><div class="para">
+ Fedora uses KVM as an underlying virtualization technology. The machine emulator and virtualizer used is a modified version of QEMU called qemu-kvm. This version does not support all configuration options of the original QEMU and it adds some additional options.
+ </div><h4 id="idm110066464">Scope of the chapter</h4><h4 id="idm92231216">Used format</h4><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong><name></strong></span> - When used in a syntax description, this string shoud be replaced by user-defined value.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>[a|b|c]</strong></span> - When used in a syntax description, only one of the strings separated by | is used.
+ </div></li><li class="listitem"><div class="para">
+ When no comment is present, an option is supported with all possible values.
+ </div></li></ul></div></div><div class="section" id="idm88207680"><div class="titlepage"><div><div><h2 class="title" id="idm88207680">D.2. Basic options</h2></div></div></div><h4 id="idm95289936">Emulated machine</h4><div class="para">
+ <span class="application"><strong>-M</strong></span> <machine-type>
+ </div><h4 id="idm8162864">Processor type</h4><div class="para">
+ <span class="application"><strong>-cpu</strong></span> <model>[,<FEATURE>][...]
+ </div><div class="para">
+ We support exposing additional features and placing restrictions. Supported models are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>Opteron_G5</strong></span> - AMD Opteron 63xx class CPU
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Opteron_G4</strong></span> - AMD Opteron 62xx class CPU
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Opteron_G3</strong></span> - AMD Opteron 23xx (AMD Opteron Gen 3)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Opteron_G2</strong></span> - AMD Opteron 22xx (AMD Opteron Gen 2)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Opteron_G1</strong></span> - AMD Opteron 240 (AMD Opteron Gen 1)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Westmere</strong></span> - Westmere E56xx/L56xx/X56xx (Nehalem-C)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Haswell</strong></span> - Intel Core Processor (Haswell)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>SandyBridge</strong></span> - Intel Xeon E312xx (Sandy Bridge)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Nehalem</strong></span> - Intel Core i7 9xx (Nehalem Class Core i7)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Penryn</strong></span> - Intel Core 2 Duo P9xxx (Penryn Class Core 2)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Conroe</strong></span> - Intel Celeron_4x0 (Conroe/Merom Class Core 2)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>cpu64-rhel5</strong></span> - Red Hat Enterprise Linux 5 supported QEMU Virtual CPU version
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>cpu64-rhel6</strong></span> - Red Hat Enterprise Linux 6 supported QEMU Virtual CPU version
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>default</strong></span> - special option use default option from above.
+ </div></li></ul></div><h4 id="idm92986368">Processor Topology</h4><div class="para">
+ <span class="application"><strong>-smp</strong></span> <n>[,cores=<ncores>][,threads=<nthreads>][,sockets=<nsocks>][,maxcpus=<maxcpus>]
+ </div><div class="para">
+ Hypervisor and guest operating system limits on processor topology apply.
+ </div><h4 id="idm118503248">NUMA system</h4><div class="para">
+ <span class="application"><strong>-numa</strong></span> <nodes>[,mem=<size>][,cpus=<cpu[-cpu>]][,nodeid=<node>]
+ </div><div class="para">
+ Hypervisor and guest operating system limits on processor topology apply.
+ </div><h4 id="idm20346816">Memory size</h4><div class="para">
+ <span class="application"><strong>-m</strong></span> <megs>
+ </div><div class="para">
+ Supported values are limited by guest minimal and maximal values and hypervisor limits.
+ </div><h4 id="idm115323952">Keyboard layout</h4><div class="para">
+ <span class="application"><strong>-k</strong></span> <language>
+ </div><h4 id="idm115322320">Guest name</h4><div class="para">
+ <span class="application"><strong>-name</strong></span> <name>
+ </div><h4 id="idm99136880">Guest UUID</h4><div class="para">
+ <span class="application"><strong>-uuid</strong></span> <uuid>
+ </div></div><div class="section" id="idm19048240"><div class="titlepage"><div><div><h2 class="title" id="idm19048240">D.3. Disk options</h2></div></div></div><h4 id="idm19047440">Generic drive</h4><div class="para">
+ <span class="application"><strong>-drive</strong></span> <option>[,<option>[,<option>[,...]]]
+ </div><div class="para">
+ Supported with the following options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>readonly</strong></span>[on|off]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>werror</strong></span>[enospc|report|stop|ignore]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>rerror</strong></span>[report|stop|ignore]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>id</strong></span>=<id>
+ </div><div class="para">
+ Id of the drive has the following limitaton for if=none:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ IDE disk has to have <id> in following format: drive-ide0-<BUS>-<UNIT>
+ </div><div class="para">
+ Example of correct format:
+ </div><div class="para">
+ -drive if=none,id=drive-ide0-<BUS>-<UNIT>,... -device ide-drive,drive=drive-ide0-<BUS>-<UNIT>,bus=ide.<BUS>,unit=<UNIT>
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>file</strong></span>=<file>
+ </div><div class="para">
+ Value of <file> is parsed with the following rules:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Passing floppy device as <file> is not supported.
+ </div></li><li class="listitem"><div class="para">
+ Passing cd-rom device as <file> is supported only with cdrom media type (media=cdrom) and only as IDE drive (either if=ide or if=none + -device ide-drive).
+ </div></li><li class="listitem"><div class="para">
+ If <file> is neither block nor character device, it must not contain ':'.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>if</strong></span>=<interface>
+ </div><div class="para">
+ The following interfaces are supported: none, ide, virtio, floppy.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>index</strong></span>=<index>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>media</strong></span>=<media>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>cache</strong></span>=<cache>
+ </div><div class="para">
+ Supported values: none, writeback or writethrough.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>copy-on-read</strong></span>=[on|off]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>snapshot</strong></span>=[yes|no]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>serial</strong></span>=<serial>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>aio</strong></span>=<aio>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>format</strong></span>=<format>
+ </div><div class="para">
+ This option is not required and can be omitted. However, this is not recommended for raw images because it represents security risk. Supported formats are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>qcow2</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>raw</strong></span>
+ </div></li></ul></div></li></ul></div><h4 id="idm75353648">Boot option</h4><div class="para">
+ <span class="application"><strong>-boot</strong></span> [order=<drives>][,menu=[on|off]]
+ </div><h4 id="idm75352048">Snapshot mode</h4><div class="para">
+ <span class="application"><strong>-snapshot</strong></span>
+ </div></div><div class="section" id="idm99806304"><div class="titlepage"><div><div><h2 class="title" id="idm99806304">D.4. Display options</h2></div></div></div><h4 id="idm99805504">Disable graphics</h4><div class="para">
+ <span class="application"><strong>-nographic</strong></span>
+ </div><h4 id="idm89763712">VGA card emulation</h4><div class="para">
+ <span class="application"><strong>-vga</strong></span> <type>
+ </div><div class="para">
+ Supported types:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>cirrus</strong></span> - Cirrus Logic GD5446 Video card.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>std</strong></span> - Standard VGA card with Bochs VBE extensions.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>qxl</strong></span> - Spice paravirtual card.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>none</strong></span> - Disable VGA card.
+ </div></li></ul></div><h4 id="idm92695296">VNC display</h4><div class="para">
+ <span class="application"><strong>-vnc</strong></span> <display>[,<option>[,<option>[,...]]]
+ </div><div class="para">
+ Supported display value:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ [<host>]:<port>
+ </div></li><li class="listitem"><div class="para">
+ unix:<path>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>share</strong></span>[allow-exclusive|force-shared|ignore]
+ </div></li><li class="listitem"><div class="para">
+ none - Supported with no other options specified.
+ </div></li></ul></div><div class="para">
+ Supported options are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>to</strong></span>=<port>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>reverse</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>password</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>tls</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>x509</strong></span>=</path/to/certificate/dir> - Supported when <span class="application"><strong>tls</strong></span> specified.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>x509verify</strong></span>=</path/to/certificate/dir> - Supported when <span class="application"><strong>tls</strong></span> specified.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>sasl</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>acl</strong></span>
+ </div></li></ul></div><h4 id="idm12830288">Spice desktop</h4><div class="para">
+ <span class="application"><strong>-spice</strong></span> option[,option[,...]]
+ </div><div class="para">
+ Supported options are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>port</strong></span>=<number>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>addr</strong></span>=<addr>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>ipv4</strong></span>
+ </div><div class="para">
+ <span class="application"><strong>ipv6</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>password</strong></span>=<secret>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>disable-ticketing</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>disable-copy-paste</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>tls-port</strong></span>=<number>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>x509-dir</strong></span>=</path/to/certificate/dir>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>x509-key-file</strong></span>=<file>
+ </div><div class="para">
+ <span class="application"><strong>x509-key-password</strong></span>=<file>
+ </div><div class="para">
+ <span class="application"><strong>x509-cert-file</strong></span>=<file>
+ </div><div class="para">
+ <span class="application"><strong>x509-cacert-file</strong></span>=<file>
+ </div><div class="para">
+ <span class="application"><strong>x509-dh-key-file</strong></span>=<file>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>tls-cipher</strong></span>=<list>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>tls-channel</strong></span>[main|display|cursor|inputs|record|playback]
+ </div><div class="para">
+ <span class="application"><strong>plaintext-channel</strong></span>[main|display|cursor|inputs|record|playback]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>image-compression</strong></span>=<compress>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>jpeg-wan-compression</strong></span>=<value>
+ </div><div class="para">
+ <span class="application"><strong>zlib-glz-wan-compression</strong></span>=<value>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>streaming-video</strong></span>=[off|all|filter]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>agent-mouse</strong></span>=[on|off]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>playback-compression</strong></span>=[on|off]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>seamless-migratio</strong></span>=[on|off]
+ </div></li></ul></div></div><div class="section" id="idm97967728"><div class="titlepage"><div><div><h2 class="title" id="idm97967728">D.5. Network options</h2></div></div></div><h4 id="idm7186624">TAP network</h4><div class="para">
+ <span class="application"><strong>-netdev tap</strong></span>,id=<id>][,<options>...]
+ </div><div class="para">
+ The following options are supported (all use name=value format):
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ ifname
+ </div></li><li class="listitem"><div class="para">
+ fd
+ </div></li><li class="listitem"><div class="para">
+ script
+ </div></li><li class="listitem"><div class="para">
+ downscript
+ </div></li><li class="listitem"><div class="para">
+ sndbuf
+ </div></li><li class="listitem"><div class="para">
+ vnet_hdr
+ </div></li><li class="listitem"><div class="para">
+ vhost
+ </div></li><li class="listitem"><div class="para">
+ vhostfd
+ </div></li><li class="listitem"><div class="para">
+ vhostforce
+ </div></li></ul></div></div><div class="section" id="idm95825168"><div class="titlepage"><div><div><h2 class="title" id="idm95825168">D.6. Device options</h2></div></div></div><h4 id="idm95824368">General device</h4><div class="para">
+ <span class="application"><strong>-device</strong></span> <driver>[,<prop>[=<value>][,...]]
+ </div><div class="para">
+ All drivers support following properties
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ id
+ </div></li><li class="listitem"><div class="para">
+ bus
+ </div></li></ul></div><div class="para">
+ Following drivers are supported (with available properties):
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>pci-assign</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ host
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ configfd
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li><li class="listitem"><div class="para">
+ rombar
+ </div></li><li class="listitem"><div class="para">
+ romfile
+ </div></li><li class="listitem"><div class="para">
+ multifunction
+ </div></li></ul></div><div class="para">
+ If the device has multiple functions, all of them need to be assigned to the same guest.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>rtl8139</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ mac
+ </div></li><li class="listitem"><div class="para">
+ netdev
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>e1000</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ mac
+ </div></li><li class="listitem"><div class="para">
+ netdev
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>virtio-net-pci</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ ioeventfd
+ </div></li><li class="listitem"><div class="para">
+ vectors
+ </div></li><li class="listitem"><div class="para">
+ indirect
+ </div></li><li class="listitem"><div class="para">
+ event_idx
+ </div></li><li class="listitem"><div class="para">
+ csum
+ </div></li><li class="listitem"><div class="para">
+ guest_csum
+ </div></li><li class="listitem"><div class="para">
+ gso
+ </div></li><li class="listitem"><div class="para">
+ guest_tso4
+ </div></li><li class="listitem"><div class="para">
+ guest_tso6
+ </div></li><li class="listitem"><div class="para">
+ guest_ecn
+ </div></li><li class="listitem"><div class="para">
+ guest_ufo
+ </div></li><li class="listitem"><div class="para">
+ host_tso4
+ </div></li><li class="listitem"><div class="para">
+ host_tso6
+ </div></li><li class="listitem"><div class="para">
+ host_ecn
+ </div></li><li class="listitem"><div class="para">
+ host_ufo
+ </div></li><li class="listitem"><div class="para">
+ mrg_rxbuf
+ </div></li><li class="listitem"><div class="para">
+ status
+ </div></li><li class="listitem"><div class="para">
+ ctrl_vq
+ </div></li><li class="listitem"><div class="para">
+ ctrl_rx
+ </div></li><li class="listitem"><div class="para">
+ ctrl_vlan
+ </div></li><li class="listitem"><div class="para">
+ ctrl_rx_extra
+ </div></li><li class="listitem"><div class="para">
+ mac
+ </div></li><li class="listitem"><div class="para">
+ netdev
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ x-txtimer
+ </div></li><li class="listitem"><div class="para">
+ x-txburst
+ </div></li><li class="listitem"><div class="para">
+ tx
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>qxl</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ ram_size
+ </div></li><li class="listitem"><div class="para">
+ vram_size
+ </div></li><li class="listitem"><div class="para">
+ revision
+ </div></li><li class="listitem"><div class="para">
+ cmdlog
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>ide-drive</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ unit
+ </div></li><li class="listitem"><div class="para">
+ drive
+ </div></li><li class="listitem"><div class="para">
+ physical_block_size
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ ver
+ </div></li><li class="listitem"><div class="para">
+ wwn
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>virtio-blk-pci</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ class
+ </div></li><li class="listitem"><div class="para">
+ drive
+ </div></li><li class="listitem"><div class="para">
+ logical_block_size
+ </div></li><li class="listitem"><div class="para">
+ physical_block_size
+ </div></li><li class="listitem"><div class="para">
+ min_io_size
+ </div></li><li class="listitem"><div class="para">
+ opt_io_size
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ ioeventfd
+ </div></li><li class="listitem"><div class="para">
+ vectors
+ </div></li><li class="listitem"><div class="para">
+ indirect_desc
+ </div></li><li class="listitem"><div class="para">
+ event_idx
+ </div></li><li class="listitem"><div class="para">
+ scsi
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>isa-debugcon</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>isa-serial</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ index
+ </div></li><li class="listitem"><div class="para">
+ iobase
+ </div></li><li class="listitem"><div class="para">
+ irq
+ </div></li><li class="listitem"><div class="para">
+ chardev
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>virtserialport</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ nr
+ </div></li><li class="listitem"><div class="para">
+ chardev
+ </div></li><li class="listitem"><div class="para">
+ name
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>virtconsole</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ nr
+ </div></li><li class="listitem"><div class="para">
+ chardev
+ </div></li><li class="listitem"><div class="para">
+ name
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>virtio-serial-pci</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ vectors
+ </div></li><li class="listitem"><div class="para">
+ class
+ </div></li><li class="listitem"><div class="para">
+ indirect_desc
+ </div></li><li class="listitem"><div class="para">
+ event_idx
+ </div></li><li class="listitem"><div class="para">
+ max_ports
+ </div></li><li class="listitem"><div class="para">
+ flow_control
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>ES1370</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>AC97</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>intel-hda</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>hda-duplex</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ cad
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>hda-micro</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ cad
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>hda-output</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ cad
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>i6300esb</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>ib700</strong></span> - no properties
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>sga</strong></span> - no properties
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>virtio-balloon-pci</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ indirect_desc
+ </div></li><li class="listitem"><div class="para">
+ event_idx
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-tablet</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ migrate
+ </div></li><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-kbd</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ migrate
+ </div></li><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-mouse</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ migrate
+ </div></li><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-ccid</strong></span> - supported since 6.2
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ port
+ </div></li><li class="listitem"><div class="para">
+ slot
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-host</strong></span> - tech preview since 6.2
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ hostbus
+ </div></li><li class="listitem"><div class="para">
+ hostaddr
+ </div></li><li class="listitem"><div class="para">
+ hostport
+ </div></li><li class="listitem"><div class="para">
+ vendorid
+ </div></li><li class="listitem"><div class="para">
+ productid
+ </div></li><li class="listitem"><div class="para">
+ isobufs
+ </div></li><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-hub</strong></span> - supported since 6.2
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-ehci</strong></span> - tech preview since 6.2
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ freq
+ </div></li><li class="listitem"><div class="para">
+ maxframes
+ </div></li><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-storage</strong></span> - tech preview since 6.2
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ drive
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ serial
+ </div></li><li class="listitem"><div class="para">
+ removable
+ </div></li><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-redir</strong></span> - tech preview since 6.3
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ chardev
+ </div></li><li class="listitem"><div class="para">
+ filter
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>scsi-cd</strong></span> - tech preview for 6.3
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ drive
+ </div></li><li class="listitem"><div class="para">
+ logical_block_size
+ </div></li><li class="listitem"><div class="para">
+ physical_block_size
+ </div></li><li class="listitem"><div class="para">
+ min_io_size
+ </div></li><li class="listitem"><div class="para">
+ opt_io_size
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ ver
+ </div></li><li class="listitem"><div class="para">
+ serial
+ </div></li><li class="listitem"><div class="para">
+ scsi-id
+ </div></li><li class="listitem"><div class="para">
+ lun
+ </div></li><li class="listitem"><div class="para">
+ channel-scsi
+ </div></li><li class="listitem"><div class="para">
+ wwn
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>scsi-hd</strong></span> -tech preview for 6.3
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ drive
+ </div></li><li class="listitem"><div class="para">
+ logical_block_size
+ </div></li><li class="listitem"><div class="para">
+ physical_block_size
+ </div></li><li class="listitem"><div class="para">
+ min_io_size
+ </div></li><li class="listitem"><div class="para">
+ opt_io_size
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ ver
+ </div></li><li class="listitem"><div class="para">
+ serial
+ </div></li><li class="listitem"><div class="para">
+ scsi-id
+ </div></li><li class="listitem"><div class="para">
+ lun
+ </div></li><li class="listitem"><div class="para">
+ channel-scsi
+ </div></li><li class="listitem"><div class="para">
+ wwn
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>scsi-block</strong></span> -tech preview for 6.3
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ drive
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>scsi-disk</strong></span> -tech preview for 6.3
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ drive=drive
+ </div></li><li class="listitem"><div class="para">
+ logical_block_size
+ </div></li><li class="listitem"><div class="para">
+ physical_block_size
+ </div></li><li class="listitem"><div class="para">
+ min_io_size
+ </div></li><li class="listitem"><div class="para">
+ opt_io_size
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ ver
+ </div></li><li class="listitem"><div class="para">
+ serial
+ </div></li><li class="listitem"><div class="para">
+ scsi-id
+ </div></li><li class="listitem"><div class="para">
+ lun
+ </div></li><li class="listitem"><div class="para">
+ channel-scsi
+ </div></li><li class="listitem"><div class="para">
+ wwn
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>piix3-usb-uhci</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>piix4-usb-uhci</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>ccid-card-passthru</strong></span>
+ </div></li></ul></div><h4 id="idm79486928">Global device setting</h4><div class="para">
+ <span class="application"><strong>-global</strong></span> <device>.<property>=<value>
+ </div><div class="para">
+ Supported devices and properties as in "General device" section with these additional devices:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>isa-fdc</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ driveA
+ </div></li><li class="listitem"><div class="para">
+ driveB
+ </div></li><li class="listitem"><div class="para">
+ bootindexA
+ </div></li><li class="listitem"><div class="para">
+ bootindexB
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>qxl-vga</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ ram_size
+ </div></li><li class="listitem"><div class="para">
+ vram_size
+ </div></li><li class="listitem"><div class="para">
+ revision
+ </div></li><li class="listitem"><div class="para">
+ cmdlog
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li></ul></div><h4 id="idm6332864">Character device</h4><div class="para">
+ <span class="application"><strong>-chardev</strong></span> backend,id=<id>[,<options>]
+ </div><div class="para">
+ Supported backends are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>null</strong></span>,id=<id> - null device
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>socket</strong></span>,id=<id>,port=<port>[,host=<host>][,to=<to>][,ipv4][,ipv6][,nodelay][,server][,nowait][,telnet] - tcp socket
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>socket</strong></span>,id=<id>,path=<path>[,server][,nowait][,telnet] - unix socket
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>file</strong></span>,id=<id>,path=<path> - trafit to file.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>stdio</strong></span>,id=<id> - standard i/o
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>spicevmc</strong></span>,id=<id>,name=<name> - spice channel
+ </div></li></ul></div><h4 id="idm110927936">Enable USB</h4><div class="para">
+ <span class="application"><strong>-usb</strong></span>
+ </div></div><div class="section" id="idm110926144"><div class="titlepage"><div><div><h2 class="title" id="idm110926144">D.7. Linux/Multiboot boot </h2></div></div></div><h4 id="idm86547104">Kernel file</h4><div class="para">
+ <span class="application"><strong>-kernel</strong></span> <bzImage>
+ </div><div class="para">
+ Note: multiboot images are not supported
+ </div><h4 id="idm80080192">Ram disk</h4><div class="para">
+ <span class="application"><strong>-initrd</strong></span> <file>
+ </div><h4 id="idm80078128">Command line parameter</h4><div class="para">
+ <span class="application"><strong>-append</strong></span> <cmdline>
+ </div></div><div class="section" id="idm85902736"><div class="titlepage"><div><div><h2 class="title" id="idm85902736">D.8. Expert options</h2></div></div></div><h4 id="idm87601056">KVM virtualization</h4><div class="para">
+ <span class="application"><strong>-enable-kvm</strong></span>
+ </div><div class="para">
+ Qemu-kvm supports only KVM virtualization and it is used by default if available. If -enable-kvm is used and KVM is not available, qemu-kvm fails. However, if -enable-kvm is not used and KVM is not available, qemu-kvm runs in TCG mode, which is not supported.
+ </div><h4 id="idm87598688">Disable kernel mode PIT reinjection</h4><div class="para">
+ <span class="application"><strong>-no-kvm-pit-reinjection</strong></span>
+ </div><h4 id="idm114310144">No shutdown</h4><div class="para">
+ <span class="application"><strong>-no-shutdown</strong></span>
+ </div><h4 id="idm91091136">No reboot</h4><div class="para">
+ <span class="application"><strong>-no-reboot</strong></span>
+ </div><h4 id="idm91089504">Serial port, monitor, QMP</h4><div class="para">
+ <span class="application"><strong>-serial</strong></span> <dev>
+ </div><div class="para">
+ <span class="application"><strong>-monitor</strong></span> <dev>
+ </div><div class="para">
+ <span class="application"><strong>-qmp</strong></span> <dev>
+ </div><div class="para">
+ Supported devices are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>stdio</strong></span> - standard input/output
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>null</strong></span> - null device
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>file</strong></span>:<filename> - output to file.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>tcp</strong></span>:[<host>]:<port>[,server][,nowait][,nodelay] - TCP Net console.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>unix</strong></span>:<path>[,server][,nowait] - Unix domain socket.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>mon</strong></span>:<dev_string> - Any device above, used to multiplex monitor too.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>none</strong></span> - disable, valid only for -serial.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>chardev</strong></span>:<id> - character device created with -chardev.
+ </div></li></ul></div><h4 id="idm90680864">Monitor redirect</h4><div class="para">
+ <span class="application"><strong>-mon</strong></span> <chardev_id>[,mode=[readline|control]][,default=[on|off]]
+ </div><h4 id="idm90679264">Manual CPU start</h4><div class="para">
+ <span class="application"><strong>-S</strong></span>
+ </div><h4 id="idm97509616">RTC</h4><div class="para">
+ <span class="application"><strong>-rtc</strong></span> [base=utc|localtime|date][,clock=host|vm][,driftfix=none|slew]
+ </div><h4 id="idm104496544">Watchdog</h4><div class="para">
+ <span class="application"><strong>-watchdog</strong></span> model
+ </div><h4 id="idm104494912">Watchdog reaction</h4><div class="para">
+ <span class="application"><strong>-watchdog-action</strong></span> <action>
+ </div><h4 id="idm120250048">Guest memory backing</h4><div class="para">
+ <span class="application"><strong>-mem-prealloc</strong></span> <span class="application"><strong>-mem-path</strong></span> /dev/hugepages
+ </div><h4 id="idm114616704">SMBIOS entry</h4><div class="para">
+ <span class="application"><strong>-smbios</strong></span> type=0[,vendor=<str>][,<version=str>][,date=<str>][,release=%d.%d]
+ </div><div class="para">
+ <span class="application"><strong>-smbios</strong></span> type=1[,manufacturer=<str>][,product=<str>][,version=<str>][,serial=<str>][,uuid=<uuid>][,sku=<str>][,family=<str>]
+ </div></div><div class="section" id="idm75543056"><div class="titlepage"><div><div><h2 class="title" id="idm75543056">D.9. Help and information options</h2></div></div></div><h4 id="idm75542288">Help</h4><div class="para">
+ <span class="application"><strong>-h</strong></span>
+ </div><div class="para">
+ <span class="application"><strong>-help</strong></span>
+ </div><h4 id="idm99174640">Version</h4><div class="para">
+ <span class="application"><strong>-version</strong></span>
+ </div><h4 id="idm111157712">Audio help</h4><div class="para">
+ <span class="application"><strong>-audio-help</strong></span>
+ </div></div><div class="section" id="idm101602032"><div class="titlepage"><div><div><h2 class="title" id="idm101602032">D.10. Miscellaneous options</h2></div></div></div><h4 id="idm101601232">Migration</h4><div class="para">
+ <span class="application"><strong>-incoming</strong></span>
+ </div><h4 id="idm86703120">No default configuration</h4><div class="para">
+ <span class="application"><strong>-nodefconfig</strong></span>
+ </div><div class="para">
+ <span class="application"><strong>-nodefaults</strong></span>
+ </div><div class="para">
+ Running without -nodefaults is not supported
+ </div><h4 id="idm109837536">Device configuration file</h4><div class="para">
+ <span class="application"><strong>-readconfig</strong></span> <file>
+ </div><div class="para">
+ <span class="application"><strong>-writeconfig</strong></span> <file>
+ </div><h4 id="idm102863520">Loaded saved state</h4><div class="para">
+ <span class="application"><strong>-loadvm</strong></span> <file>
+ </div></div></div><div xml:lang="en-US" class="appendix" id="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Managing guests with virsh</h1></div></div></div><div class="para">
+ <code class="command">virsh</code> is a command line interface tool for managing guests and the hypervisor. The <code class="command">virsh</code> command-line tool is built on the <code class="command">libvirt</code> management API and operates as an alternative to the <code class="command">qemu-kvm</code> command and the graphical <code class="command">virt-manager</code> application. The <code class="command">virsh</code> command can be used in read-only mode by unprivileged users or, with root access, full administration functionality. The <code class="command">virsh</code> command is ideal for scripting virtualization administration.
+ </div><div class="section" id="idm76402464"><div class="titlepage"><div><div><h2 class="title" id="idm76402464">E.1. virsh command quick reference</h2></div></div></div><div class="para">
+ The following tables provide a quick reference for all virsh command line options.
+ </div><div class="table" id="tabl-Virtualization-Managing_guests_with_virsh-Guest_management_commands"><h6>Table E.1. Guest management commands</h6><div class="table-contents"><table summary="Guest management commands" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">help</code>
+ </td><td class="">
+ Prints basic help information.
+ </td></tr><tr><td class="">
+ <code class="command">list</code>
+ </td><td class="">
+ Lists all guests.
+ </td></tr><tr><td class="">
+ <code class="command">dumpxml</code>
+ </td><td class="">
+ Outputs the XML configuration file for the guest.
+ </td></tr><tr><td class="">
+ <code class="command">create</code>
+ </td><td class="">
+ Creates a guest from an XML configuration file and starts the new guest.
+ </td></tr><tr><td class="">
+ <code class="command">start</code>
+ </td><td class="">
+ Starts an inactive guest.
+ </td></tr><tr><td class="">
+ <code class="command">destroy</code>
+ </td><td class="">
+ Forces a guest to stop.
+ </td></tr><tr><td class="">
+ <code class="command">define</code>
+ </td><td class="">
+ Creates a guest from an XML configuration file without starting the new guest.
+ </td></tr><tr><td class="">
+ <code class="command">domid</code>
+ </td><td class="">
+ Displays the guest's ID.
+ </td></tr><tr><td class="">
+ <code class="command">domuuid</code>
+ </td><td class="">
+ Displays the guest's UUID.
+ </td></tr><tr><td class="">
+ <code class="command">dominfo</code>
+ </td><td class="">
+ Displays guest information.
+ </td></tr><tr><td class="">
+ <code class="command">domname</code>
+ </td><td class="">
+ Displays the guest's name.
+ </td></tr><tr><td class="">
+ <code class="command">domstate</code>
+ </td><td class="">
+ Displays the state of a guest.
+ </td></tr><tr><td class="">
+ <code class="command">quit</code>
+ </td><td class="">
+ Quits the interactive terminal.
+ </td></tr><tr><td class="">
+ <code class="command">reboot</code>
+ </td><td class="">
+ Reboots a guest.
+ </td></tr><tr><td class="">
+ <code class="command">restore</code>
+ </td><td class="">
+ Restores a previously saved guest stored in a file.
+ </td></tr><tr><td class="">
+ <code class="command">resume</code>
+ </td><td class="">
+ Resumes a paused guest.
+ </td></tr><tr><td class="">
+ <code class="command">save</code>
+ </td><td class="">
+ Saves the present state of a guest to a file.
+ </td></tr><tr><td class="">
+ <code class="command">shutdown</code>
+ </td><td class="">
+ Gracefully shuts down a guest.
+ </td></tr><tr><td class="">
+ <code class="command">suspend</code>
+ </td><td class="">
+ Pauses a guest.
+ </td></tr><tr><td class="">
+ <code class="command">undefine</code>
+ </td><td class="">
+ Deletes all files associated with a guest.
+ </td></tr><tr><td class="">
+ <code class="command">migrate</code>
+ </td><td class="">
+ Migrates a guest to another host.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The following <code class="command">virsh</code> command options manage guest and hypervisor resources:
+ </div><div class="table" id="tabl-Virtualization-Managing_guests_with_virsh-Resource_management_options"><h6>Table E.2. Resource management options</h6><div class="table-contents"><table summary="Resource management options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">setmem</code>
+ </td><td class="">
+ Sets the allocated memory for a guest. Refer to the <code class="command">virsh</code> manpage for more details.
+ </td></tr><tr><td class="">
+ <code class="command">setmaxmem</code>
+ </td><td class="">
+ Sets maximum memory limit for the hypervisor. Refer to the <code class="command">virsh</code> manpage for more details.
+ </td></tr><tr><td class="">
+ <code class="command">setvcpus</code>
+ </td><td class="">
+ Changes number of virtual CPUs assigned to a guest. Refer to the <code class="command">virsh</code> manpage for more details.
+ </td></tr><tr><td class="">
+ <code class="command">vcpuinfo</code>
+ </td><td class="">
+ Displays virtual CPU information about a guest.
+ </td></tr><tr><td class="">
+ <code class="command">vcpupin</code>
+ </td><td class="">
+ Controls the virtual CPU affinity of a guest.
+ </td></tr><tr><td class="">
+ <code class="command">domblkstat</code>
+ </td><td class="">
+ Displays block device statistics for a running guest.
+ </td></tr><tr><td class="">
+ <code class="command">domifstat</code>
+ </td><td class="">
+ Displays network interface statistics for a running guest.
+ </td></tr><tr><td class="">
+ <code class="command">attach-device</code>
+ </td><td class="">
+ Attach a device to a guest, using a device definition in an XML file.
+ </td></tr><tr><td class="">
+ <code class="command">attach-disk</code>
+ </td><td class="">
+ Attaches a new disk device to a guest.
+ </td></tr><tr><td class="">
+ <code class="command">attach-interface</code>
+ </td><td class="">
+ Attaches a new network interface to a guest.
+ </td></tr><tr><td class="">
+ <code class="command">update-device</code>
+ </td><td class="">
+ Detaches a disk image from a guest's CD-ROM drive. See <a class="xref" href="#sect-Attaching_and_updating_a_device_with_virsh">Section E.2, “Attaching and updating a device with virsh”</a> for more details.
+ </td></tr><tr><td class="">
+ <code class="command">detach-device</code>
+ </td><td class="">
+ Detaches a device from a guest, takes the same kind of XML descriptions as command <code class="command">attach-device</code>.
+ </td></tr><tr><td class="">
+ <code class="command">detach-disk</code>
+ </td><td class="">
+ Detaches a disk device from a guest.
+ </td></tr><tr><td class="">
+ <code class="command">detach-interface</code>
+ </td><td class="">
+ Detach a network interface from a guest.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The <code class="command">virsh</code> commands for managing and creating storage pools and volumes.
+ </div><div class="para">
+ For more information on using storage pools with virsh, refer to <a href="http://libvirt.org/formatstorage.html">http://libvirt.org/formatstorage.html</a>
+ </div><div class="table" id="tabl-Virtualization-Managing_gunagement_options"><h6>Table E.3. Storage Pool options</h6><div class="table-contents"><table summary="Storage Pool options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">find-storage-pool-sources</code>
+ </td><td class="">
+ Returns the XML definition for all storage pools of a given type that could be found.
+ </td></tr><tr><td class="">
+ <code class="command">find-storage-pool-sources</code> <em class="parameter"><code>host port</code></em>
+ </td><td class="">
+ Returns data on all storage pools of a given type that could be found as XML. If the host and port are provided, this command can be run remotely.
+ </td></tr><tr><td class="">
+ <code class="command">pool-autostart </code>
+ </td><td class="">
+ Sets the storage pool to start at boot time.
+ </td></tr><tr><td class="">
+ <code class="command">pool-build</code>
+ </td><td class="">
+ The <code class="command">pool-build</code> command builds a defined pool. This command can format disks and create partitions.
+ </td></tr><tr><td class="">
+ <code class="command">pool-create</code>
+ </td><td class="">
+ <code class="command">pool-create</code> creates and starts a storage pool from the provided XML storage pool definition file.
+ </td></tr><tr><td class="">
+ <code class="command">pool-create-as name</code>
+ </td><td class="">
+ Creates and starts a storage pool from the provided parameters. If the <em class="parameter"><code>--print-xml</code></em> parameter is specified, the command prints the XML definition for the storage pool without creating the storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-define</code>
+ </td><td class="">
+ Creates a storage bool from an XML definition file but does not start the new storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-define-as name</code>
+ </td><td class="">
+ Creates but does not start, a storage pool from the provided parameters. If the <em class="parameter"><code>--print-xml</code></em> parameter is specified, the command prints the XML definition for the storage pool without creating the storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-destroy</code>
+ </td><td class="">
+ Permanently destroys a storage pool in <code class="command">libvirt</code>. The raw data contained in the storage pool is not changed and can be recovered with the <code class="command">pool-create</code> command.
+ </td></tr><tr><td class="">
+ <code class="command">pool-delete</code>
+ </td><td class="">
+ Destroys the storage resources used by a storage pool. This operation cannot be recovered. The storage pool still exists after this command but all data is deleted.
+ </td></tr><tr><td class="">
+ <code class="command">pool-dumpxml</code>
+ </td><td class="">
+ Prints the XML definition for a storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-edit</code>
+ </td><td class="">
+ Opens the XML definition file for a storage pool in the users default text editor.
+ </td></tr><tr><td class="">
+ <code class="command">pool-info</code>
+ </td><td class="">
+ Returns information about a storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-list</code>
+ </td><td class="">
+ Lists storage pools known to libvirt. By default, <code class="command">pool-list</code> lists pools in use by active guests. The <em class="parameter"><code>--inactive</code></em> parameter lists inactive pools and the <em class="parameter"><code>--all</code></em> parameter lists all pools.
+ </td></tr><tr><td class="">
+ <code class="command">pool-undefine</code>
+ </td><td class="">
+ Deletes the definition for an inactive storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-uuid</code>
+ </td><td class="">
+ Returns the UUID of the named pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-name </code>
+ </td><td class="">
+ Prints a storage pool's name when provided the UUID of a storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-refresh</code>
+ </td><td class="">
+ Refreshes the list of volumes contained in a storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-start</code>
+ </td><td class="">
+ Starts a storage pool that is defined but inactive.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><h6>Table E.4. Volume options</h6><div class="table-contents"><table summary="Volume options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">vol-create</code>
+ </td><td class="">
+ Create a volume from an XML file.
+ </td></tr><tr><td class="">
+ <code class="command">vol-create-from</code>
+ </td><td class="">
+ Create a volume using another volume as input.
+ </td></tr><tr><td class="">
+ <code class="command">vol-create-as</code>
+ </td><td class="">
+ Create a volume from a set of arguments.
+ </td></tr><tr><td class="">
+ <code class="command">vol-clone</code>
+ </td><td class="">
+ Clone a volume.
+ </td></tr><tr><td class="">
+ <code class="command">vol-delete</code>
+ </td><td class="">
+ Delete a volume.
+ </td></tr><tr><td class="">
+ <code class="command">vol-wipe</code>
+ </td><td class="">
+ Wipe a volume.
+ </td></tr><tr><td class="">
+ <code class="command">vol-dumpxml</code>
+ </td><td class="">
+ Show volume information in XML.
+ </td></tr><tr><td class="">
+ <code class="command">vol-info</code>
+ </td><td class="">
+ Show storage volume information.
+ </td></tr><tr><td class="">
+ <code class="command">vol-list</code>
+ </td><td class="">
+ List volumes.
+ </td></tr><tr><td class="">
+ <code class="command">vol-pool</code>
+ </td><td class="">
+ Returns the storage pool for a given volume key or path.
+ </td></tr><tr><td class="">
+ <code class="command">vol-path</code>
+ </td><td class="">
+ Returns the volume path for a given volume name or key.
+ </td></tr><tr><td class="">
+ <code class="command">vol-name</code>
+ </td><td class="">
+ Returns the volume name for a given volume key or path.
+ </td></tr><tr><td class="">
+ <code class="command">vol-key</code>
+ </td><td class="">
+ Returns the volume key for a given volume name or path.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><h6>Table E.5. Secret options</h6><div class="table-contents"><table summary="Secret options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">secret-define</code>
+ </td><td class="">
+ Define or modify a secret from an XML file.
+ </td></tr><tr><td class="">
+ <code class="command">secret-dumpxml</code>
+ </td><td class="">
+ Show secret attributes in XML.
+ </td></tr><tr><td class="">
+ <code class="command">secret-set-value</code>
+ </td><td class="">
+ Set a secret value.
+ </td></tr><tr><td class="">
+ <code class="command">secret-get-value</code>
+ </td><td class="">
+ Output a secret value.
+ </td></tr><tr><td class="">
+ <code class="command">secret-undefine</code>
+ </td><td class="">
+ Undefine a secret.
+ </td></tr><tr><td class="">
+ <code class="command">secret-list</code>
+ </td><td class="">
+ List secrets.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><h6>Table E.6. Network filter options</h6><div class="table-contents"><table summary="Network filter options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">nwfilter-define</code>
+ </td><td class="">
+ Define or update a network filter from an XML file.
+ </td></tr><tr><td class="">
+ <code class="command">nwfilter-undefine</code>
+ </td><td class="">
+ Undefine a network filter.
+ </td></tr><tr><td class="">
+ <code class="command">nwfilter-dumpxml</code>
+ </td><td class="">
+ Show network filter information in XML.
+ </td></tr><tr><td class="">
+ <code class="command">nwfilter-list</code>
+ </td><td class="">
+ List network filters.
+ </td></tr><tr><td class="">
+ <code class="command">nwfilter-edit</code>
+ </td><td class="">
+ Edit XML configuration for a network filter.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ This table contains <code class="command">virsh</code> command options for snapshots:
+ </div><div class="table"><h6>Table E.7. Snapshot options</h6><div class="table-contents"><table summary="Snapshot options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">snapshot-create</code>
+ </td><td class="">
+ Create a snapshot.
+ </td></tr><tr><td class="">
+ <code class="command">snapshot-current</code>
+ </td><td class="">
+ Get the current snapshot.
+ </td></tr><tr><td class="">
+ <code class="command">snapshot-delete</code>
+ </td><td class="">
+ Delete a domain snapshot.
+ </td></tr><tr><td class="">
+ <code class="command">snapshot-dumpxml</code>
+ </td><td class="">
+ Dump XML for a domain snapshot.
+ </td></tr><tr><td class="">
+ <code class="command">snapshot-list</code>
+ </td><td class="">
+ List snapshots for a domain.
+ </td></tr><tr><td class="">
+ <code class="command">snapshot-revert</code>
+ </td><td class="">
+ Revert a domain to a snapshot.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ This table contains miscellaneous <code class="command">virsh</code> commands:
+ </div><div class="table" id="tabl-Virtualization-Managing_guests_with_virsh-Miscellaneous_options"><h6>Table E.8. Miscellaneous options</h6><div class="table-contents"><table summary="Miscellaneous options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">version</code>
+ </td><td class="">
+ Displays the version of <code class="command">virsh</code>.
+ </td></tr><tr><td class="">
+ <code class="command">nodeinfo</code>
+ </td><td class="">
+ Outputs information about the hypervisor.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sect-Attaching_and_updating_a_device_with_virsh"><div class="titlepage"><div><div><h2 class="title">E.2. Attaching and updating a device with virsh</h2></div></div></div><div class="para">
+ For information on this procedure refer to <a class="xref" href="#sect-Virtualization-Adding_storage_devices_to_guests-Adding_file_based_storage_to_a_guest">Section 28.3.1, “Adding file based storage to a guest”</a>
+ </div></div><div class="section" id="sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor"><div class="titlepage"><div><div><h2 class="title">E.3. Connecting to the hypervisor</h2></div></div></div><div class="para">
+ Connect to a hypervisor session with <code class="command">virsh</code>:
+ </div><pre class="screen"># virsh connect <em class="parameter"><code>{name}</code></em></pre><div class="para">
+ Where <em class="parameter"><code>{name}</code></em> is the machine name (hostname) or URL (the output of the <code class="command">virsh uri</code> command) of the hypervisor. To initiate a read-only connection, append the above command with <code class="command">--readonly</code>.
+ </div></div><div class="section" id="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file"><div class="titlepage"><div><div><h2 class="title">E.4. Creating a virtual machine XML dump (configuration file)</h2></div></div></div><div class="para">
+ Output a guest's XML configuration file with <code class="command">virsh</code>:
+ </div><pre class="screen"># virsh dumpxml <em class="parameter"><code>{guest-id, guestname or 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>:
+ </div><pre class="screen"># virsh dumpxml <em class="replaceable"><code>GuestID</code></em> > <em class="replaceable"><code>guest.xml</code></em></pre><div class="para">
+ This file <code class="filename">guest.xml</code> can recreate the guest (refer to <a class="xref" href="#form-Virtualization-Managing_guests_with_virsh-Editing_a_guests_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.
+ </div><div class="para">
+ An example of <code class="command">virsh dumpxml</code> output:
+ </div><pre class="screen"># virsh dumpxml guest1-rhel6-64
+<domain type='kvm'>
+ <name>guest1-rhel6-64</name>
+ <uuid>b8d7388a-bbf2-db3a-e962-b97ca6e514bd</uuid>
+ <memory>2097152</memory>
+ <currentMemory>2097152</currentMemory>
+ <vcpu>2</vcpu>
+ <os>
+ <type arch='x86_64' machine='rhel6.2.0'>hvm</type>
+ <boot dev='hd'/>
+ </os>
+ <features>
+ <acpi/>
+ <apic/>
+ <pae/>
+ </features>
+ <clock offset='utc'/>
+ <on_poweroff>destroy</on_poweroff>
+ <on_reboot>restart</on_reboot>
+ <on_crash>restart</on_crash>
+ <devices>
+ <emulator>/usr/libexec/qemu-kvm</emulator>
+ <disk type='file' device='disk'>
+ <driver name='qemu' type='raw' cache='none' io='threads'/>
+ <source file='/home/guest-images/guest1-rhel6-64.img'/>
+ <target dev='vda' bus='virtio'/>
+ <shareable/<
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
+ </disk>
+ <interface type='bridge'>
+ <mac address='52:54:00:b9:35:a9'/>
+ <source bridge='br0'/>
+ <model type='virtio'/>
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
+ </interface>
+ <serial type='pty'>
+ <target port='0'/>
+ </serial>
+ <console type='pty'>
+ <target type='serial' port='0'/>
+ </console>
+ <input type='tablet' bus='usb'/>
+ <input type='mouse' bus='ps2'/>
+ <graphics type='vnc' port='-1' autoport='yes'/>
+ <sound model='ich6'>
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
+ </sound>
+ <video>
+ <model type='cirrus' vram='9216' heads='1'/>
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
+ </video>
+ <memballoon model='virtio'>
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
+ </memballoon>
+ </devices>
+</domain>
+
+
+</pre><div class="para">
+ Note that the <shareable/> flag is set. This indicates the device is expected to be shared between domains (assuming the hypervisor and OS support this), which means that caching should be deactivated for that device.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Creating_a_guest_from_a_configuration_file"><h5 class="formalpara">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="#form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file">Section E.4, “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" id="form-Virtualization-Managing_guests_with_virsh-Editing_a_guests_configuration_file"><h5 class="formalpara">Editing a guest's configuration file</h5>
+ Instead of using the <code class="command">dumpxml</code> option (refer to <a class="xref" href="#form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file">Section E.4, “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="section" id="sect-multifunction-pci-install"><div class="titlepage"><div><div><h3 class="title">E.4.1. Adding multifunction PCI devices to KVM guests</h3></div></div></div><div class="para">
+ This section will demonstrate how to add multi-function PCI devices to KVM guests.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Run the <code class="command">virsh edit <em class="replaceable"><code>[guestname]</code></em></code> command to edit the XML configuration file for the guest.
+ </div></li><li class="step"><div class="para">
+ In the address type tag, add a <code class="command">multifunction='on'</code> entry for <code class="command">function='0x0'</code>.
+ </div><div class="para">
+ This enables the guest to use the multifunction PCI devices.
+ </div><pre class="screen">
+<disk type='file' device='disk'>
+<driver name='qemu' type='raw' cache='none'/>
+<source file='/var/lib/libvirt/images/rhel62-1.img'/>
+<target dev='vda' bus='virtio'/>
+<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0' multifunction='on'/
+</disk>
+</pre><div class="para">
+ For a PCI device with two functions, amend the XML configuration file to include a second device with the same slot number as the first device and a different function number, such as <code class="command">function='0x1'</code>.
+ </div><div class="para">
+ For Example:
+ </div><pre class="screen">
+<disk type='file' device='disk'>
+<driver name='qemu' type='raw' cache='none'/>
+<source file='/var/lib/libvirt/images/rhel62-1.img'/>
+<target dev='vda' bus='virtio'/>
+<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0' multifunction='on'/>
+</disk>
+<disk type='file' device='disk'>
+<driver name='qemu' type='raw' cache='none'/>
+<source file='/var/lib/libvirt/images/rhel62-2.img'/>
+<target dev='vdb' bus='virtio'/>
+<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x1'/>
+</disk>
+</pre></li><li class="step"><div class="para">
+ <code class="command">lspci</code> output from the KVM guest shows:
+ </div><pre class="screen">
+$ lspci
+
+00:05.0 SCSI storage controller: Fedora, Inc Virtio block device
+00:05.1 SCSI storage controller: Fedora, Inc Virtio block device
+</pre></li></ol></div></div></div><div class="section" id="idm15093120"><div class="titlepage"><div><div><h2 class="title" id="idm15093120">E.5. Suspending, resuming, saving and restoring a guest</h2></div></div></div><div class="formalpara"><h5 class="formalpara" id="idm15092352">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="#form-Virtualization-Managing_guests_with_virsh-Resuming_a_guest">Resuming a guest</a>) option.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Resuming_a_guest"><h5 class="formalpara">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" id="form-Virtualization-Managing_guests_with_virsh-Save_a_guest"><h5 class="formalpara">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="#form-Virtualization-Managing_guests_with_virsh-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" id="form-Virtualization-Managing_guests_with_virsh-Restore_a_guest"><h5 class="formalpara">Restore a guest</h5>
+ Restore a guest previously saved with the <code class="command">virsh save</code> command (<a class="xref" href="#form-Virtualization-Managing_guests_with_virsh-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><div class="section" id="idm111188384"><div class="titlepage"><div><div><h2 class="title" id="idm111188384">E.6. Shutting down, rebooting and force-shutdown of a guest</h2></div></div></div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Shut_down_a_guest"><h5 class="formalpara">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.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Rebooting_a_guest"><h5 class="formalpara">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> element in the guest's configuration file.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Forcing_a_guest_to_stop"><h5 class="formalpara">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.
+ </div></div><div class="section" id="idm124247680"><div class="titlepage"><div><div><h2 class="title" id="idm124247680">E.7. Retrieving guest information</h2></div></div></div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Getting_the_domain_ID_of_a_guest"><h5 class="formalpara">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" id="form-Virtualization-Managing_guests_with_virsh-Getting_the_domain_name_of_a_guest"><h5 class="formalpara">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" id="form-Virtualization-Managing_guests_with_virsh-Getting_the_UUID_of_a_guest"><h5 class="formalpara">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" id="form-Virtualization-Managing_guests_with_virsh-Displaying_guest_Information_"><h5 class="formalpara">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 vr-rhel6u1-x86_64-kvm
+Id: 9
+Name: vr-rhel6u1-x86_64-kvm
+UUID: a03093a1-5da6-a2a2-3baf-a845db2f10b9
+OS Type: hvm
+State: running
+CPU(s): 1
+CPU time: 21.6s
+Max memory: 2097152 kB
+Used memory: 1025000 kB
+Persistent: yes
+Autostart: disable
+Security model: selinux
+Security DOI: 0
+Security label: system_u:system_r:svirt_t:s0:c612,c921 (permissive)
+</pre></div><div class="section" id="idm80557872"><div class="titlepage"><div><div><h2 class="title" id="idm80557872">E.8. Retrieving node information</h2></div></div></div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Displaying_node_information"><h5 class="formalpara">Displaying node information</h5>
+ To display information about the node:
+ </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">
+ Returns basic information about the node, including the model number, number of CPUs, type of CPU, and size of the physical memory. The output corresponds to virNodeInfo structure. Specifically, the "CPU socket(s)" field indicates the number of CPU sockets per NUMA cell.
+ </div></div><div class="section" id="idm75574976"><div class="titlepage"><div><div><h2 class="title" id="idm75574976">E.9. Storage pool information</h2></div></div></div><div class="formalpara" id="asfdqsdgasdfsadgwr"><h5 class="formalpara">Editing a storage pool definition</h5>
+ The <code class="command">virsh pool-edit</code> command takes the name or UUID for a storage pool and opens the XML definition file for a storage pool in the users default text editor.
+ </div><div class="para">
+ The <code class="command">virsh pool-edit</code> command is equivalent to running the following commands:
+ </div><pre class="screen"># virsh pool-dumpxml <em class="parameter"><code>pool</code></em> > <em class="parameter"><code>pool</code></em>.xml
+# vim <em class="parameter"><code>pool</code></em>.xml
+# virsh pool-define <em class="parameter"><code>pool</code></em>.xml
+</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The default editor is defined by the <code class="command">$VISUAL</code> or <code class="command">$EDITOR</code> environment variables, and default is <code class="command">vi</code>.
+ </div></div></div></div><div class="section" id="idm99238304"><div class="titlepage"><div><div><h2 class="title" id="idm99238304">E.10. Displaying per-guest information</h2></div></div></div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Displaying_the_guests"><h5 class="formalpara">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">
+ There are seven states that can be visible using this command:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Running - The <code class="computeroutput">running</code> state refers to guests which are currently active on a CPU.
+ </div></li><li class="listitem"><div class="para">
+ Idle - The <code class="computeroutput">idle</code> state indicates that the domain is idle, and may not be running or able to run. This can be caused because the domain is waiting on IO (a traditional wait state) or has gone to sleep because there was nothing else for it to do.
+ </div></li><li class="listitem"><div class="para">
+ Paused - 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 class="listitem"><div class="para">
+ Shutdown - 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 class="listitem"><div class="para">
+ Shut off - The <code class="computeroutput">shut off</code> state indicates that the domain is not running. This can be caused when a domain completly shuts down or has not been started.
+ </div></li><li class="listitem"><div class="para">
+ Crashed - The <code class="computeroutput">crashed</code> state indicates that the domain has crashed and can only occur if the guest has been configured not to restart on crash.
+ </div></li><li class="listitem"><div class="para">
+ Dying - 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></ul></div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Displaying_virtual_CPU_information"><h5 class="formalpara">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" id="form-Virtualization-Managing_guests_with_virsh-Configuring_virtual_CPU_affinity"><h5 class="formalpara">Configuring virtual CPU affinity</h5>
+ To configure the affinity of virtual CPUs with physical CPUs:
+ </div><pre class="screen"># virsh vcpupin <em class="parameter"><code>domain-id vcpu cpulist</code></em></pre><div class="para">
+ The <code class="command">domain-id</code> parameter is the guest's ID number or name.
+ </div><div class="para">
+ The <code class="command">vcpu</code> parameter denotes the number of virtualized CPUs allocated to the guest.The <code class="command">vcpu</code> parameter must be provided.
+ </div><div class="para">
+ The <code class="command">cpulist</code> parameter is a list of physical CPU identifier numbers separated by commas. The <code class="command">cpulist</code> parameter determines which physical CPUs the VCPUs can run on.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Configuring_virtual_CPU_count"><h5 class="formalpara">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">
+ This <em class="parameter"><code>count</code></em> value cannot exceed the number of CPUs that were assigned to the guest when it was created.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Configuring_memory_allocation"><h5 class="formalpara">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><pre class="screen"># <code class="command">virsh setmem</code> <em class="replaceable"><code>vr-rhel6u1-x86_64-kvm</code></em> <em class="replaceable"><code>--kilobytes 1025000</code></em></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 does not affect active guests. If the new value is lower than the available memory, it will shrink possibly causing the guest to crash.
+ </div><div class="para">
+ This command has the following options
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ [--domain] <string> domain name, id or uuid
+ </div></li><li class="listitem"><div class="para">
+ [--size] <number> new memory size, as scaled integer (default KiB)
+ </div></li><li class="listitem"><div class="para">
+ --config takes affect next boot
+ </div></li><li class="listitem"><div class="para">
+ --live controls the memory of the running domain
+ </div></li><li class="listitem"><div class="para">
+ --current controls the memory on the current domain
+ </div></li></ul></div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Configuring_memory_tuning"><h5 class="formalpara">Configuring memory Tuning</h5>
+ The element memtune provides details regarding the memory tunable parameters for the domain. If this is omitted, it defaults to the OS provided defaults. For QEMU/KVM, the parameters are applied to the QEMU process as a whole. Thus, when counting them, one needs to add up guest RAM, guest video RAM, and some memory overhead of QEMU itself. The last piece is hard to determine so one needs guess and try. For each tunable, it is possible to designate which unit the number is in on input, using the same values as for <memory>. For backwards compatibility, output is always in KiB. units.
+ </div><div class="para">
+ Here is an example XML with the memtune options used:
+ </div><pre class="screen">
+<domain>
+
+ <memtune>
+ <hard_limit unit='G'>1</hard_limit>
+ <soft_limit unit='M'>128</soft_limit>
+ <swap_hard_limit unit='G'>2</swap_hard_limit>
+ <min_guarantee unit='bytes'>67108864</min_guarantee>
+ </memtune>
+ ...
+</domain>
+</pre><div class="para">
+ memtune has the following options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ hard_limit - The optional hard_limit element is the maximum memory the guest can use. The units for this value are kibibytes (i.e. blocks of 1024 bytes)
+ </div></li><li class="listitem"><div class="para">
+ soft_limit - The optional soft_limit element is the memory limit to enforce during memory contention. The units for this value are kibibytes (i.e. blocks of 1024 bytes)
+ </div></li><li class="listitem"><div class="para">
+ swap_hard_limit - The optional swap_hard_limit element is the maximum memory plus swap the guest can use. The units for this value are kibibytes (i.e. blocks of 1024 bytes). This has to be more than hard_limit value provided
+ </div></li><li class="listitem"><div class="para">
+ min_guarantee - The optional min_guarantee element is the guaranteed minimum memory allocation for the guest. The units for this value are kibibytes (i.e. blocks of 1024 bytes)
+ </div></li></ul></div><pre class="screen">
+# virsh memtune vr-rhel6u1-x86_64-kvm --hard-limit 512000
+
+# virsh memtune vr-rhel6u1-x86_64-kvm
+hard_limit : 512000 kB
+soft_limit : unlimited
+swap_hard_limit: unlimited
+</pre><div class="para">
+ hard_limit is 512000 kB, it is maximum memory the guest domain can use.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Displaying_guest_block_device_information"><h5 class="formalpara">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" id="form-Virtualization-Managing_guests_with_virsh-Displaying_guest_network_device_information"><h5 class="formalpara">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><div class="section" id="idm115752416"><div class="titlepage"><div><div><h2 class="title" id="idm115752416">E.11. Managing virtual networks</h2></div></div></div><div class="para">
+ 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 class="listitem"><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 class="listitem"><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 class="listitem"><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 class="listitem"><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 class="listitem"><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 class="listitem"><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 class="listitem"><div class="para">
+ <code class="command">virsh net-start <em class="replaceable"><code>nameOfInactiveNetwork</code></em> </code> — starts an inactive network.
+ </div></li><li class="listitem"><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><div class="section" id="migrating_guests-with-virsh"><div class="titlepage"><div><div><h2 class="title">E.12. Migrating guests with virsh</h2></div></div></div><div class="para">
+ Information on migration using virsh is located in the section entitled Live KVM Migration with virsh Refer to <a class="xref" href="#sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh">Section 20.4, “Live KVM migration with virsh”</a>
+ </div></div><div class="section" id="sect-man-disk-image"><div class="titlepage"><div><div><h2 class="title">E.13. Disk image management with live block copy</h2></div></div></div><div class="para">
+ Live block copy allows you to copy an in use guest disk image to a destination image and switches the guest disk image to the destination guest image while the guest is running. Whilst live migration moves the memory and registry state of the host, the guest is kept in shared storage. Live block copy allows you to move the entire guest contents to another host on the fly while the guest is running. Live block copy may also be used for live migration without requiring permanent share storage. In this method the disk image is copied to the destination host after migration, but while the guest is running.
+ </div><div class="para">
+ Live block copy is especially useful for the following applications:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ moving the guest image from local storage to a central location
+ </div></li><li class="listitem"><div class="para">
+ when maintenance is required, guests can be transferred to another location, with no loss of performance
+ </div></li><li class="listitem"><div class="para">
+ allows for management of guest images for speed and efficiency
+ </div></li><li class="listitem"><div class="para">
+ image format conversions can be done without having to shut down the guest
+ </div></li></ul></div><div class="example" id="live-blk-cpy-example"><h6>Example E.1. Example (live block copy)</h6><div class="example-contents"><div class="para">
+ This example shows what happens when live block copy is performed. The example has a backing file (base) that is shared between a source and destination. It also has two overlays (sn1 and sn2) that are only present on the source and must be copied.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ The backing file chain at the beginning looks like this:
+ </div><div class="para">
+ <code class="command"> base ← sn1 ← sn2</code>
+ </div><div class="para">
+ The components are as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ base - the original disk image
+ </div></li><li class="listitem"><div class="para">
+ sn1 - the first snapshot that was taken of the base disk image
+ </div></li><li class="listitem"><div class="para">
+ sn2 - the most current snapshot
+ </div></li><li class="listitem"><div class="para">
+ active - the copy of the disk
+ </div></li></ul></div></li><li class="step"><div class="para">
+ When a copy of the image is created as a new image on top of sn2 the result is this:
+ </div><div class="para">
+ <code class="command">base ← sn1 ← sn2 ← active </code>
+ </div></li><li class="step"><div class="para">
+ At this point the read permissions are all in the correct order and are set automatically. To make sure write permissions are set properly, a mirror mechanism redirects all writes to both sn2 and active, so that sn2 and active read the same at any time (and this mirror mechanism is the essential difference between live block copy and image streaming).
+ </div></li><li class="step"><div class="para">
+ A background task that loops over all disk clusters is executed. For each cluster, there are the following possible cases and actions:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The cluster is already allocated in active and there is nothing to do.
+ </div></li><li class="listitem"><div class="para">
+ Use <code class="command">bdrv_is_allocated()</code> to follow the backing file chain. If the cluster is read from base (which is shared) there is nothing to do.
+ </div></li><li class="listitem"><div class="para">
+ If <code class="command">bdrv_is_allocated()</code> variant is not feasible, rebase the image and compare the read data with write data in base in order to decide if a copy is needed.
+ </div></li><li class="listitem"><div class="para">
+ In all other cases, copy the cluster into <code class="filename">active</code>
+ </div></li></ul></div></li><li class="step"><div class="para">
+ When the copy has completed, the backing file of active is switched to base (similar to rebase)
+ </div></li></ol></div></div></div><br class="example-break" /><div class="para">
+ To reduce the length of a backing chain after a series of snapshots, the following commands are helpful: <code class="command">blockcommit</code> and <code class="command">blockpull</code>. See <a class="xref" href="#sect-blockcommit">Section E.13.1, “Using blockcommit to shorten a backing chain”</a> for more information.
+ </div><div class="section" id="sect-blockcommit"><div class="titlepage"><div><div><h3 class="title">E.13.1. Using blockcommit to shorten a backing chain</h3></div></div></div><div class="para">
+ This section demonstrates how to use <code class="command">blockcommit</code> to shorten a backing chain. For more background on backing chains, see <a class="xref" href="#sect-man-disk-image">Section E.13, “Disk image management with live block copy”</a>.
+ </div><div class="para">
+ <code class="command">blockcommit</code> copies data from one part of the chain down into a backing file, allowing you to pivot the rest of the chain in order to bypass the committed portions. For example, suppose this is the current state:
+ </div><pre class="screen">
+ <code class="command">base ← snap1 ← snap2 ← active</code>.
+</pre><div class="para">
+ Using <code class="command">blockcommit</code> moves the contents of snap2 into snap1, allowing you to delete snap2 from the chain, making backups much quicker.
+ </div><div class="procedure" id="pro-blockcommit"><h6>Procedure E.1. virsh blockcommit</h6><ul><li class="step"><div class="para">
+ Run the following command:
+ </div><pre class="screen">#<code class="command"> virsh blockcommit $dom $disk --base snap1 --top snap2 --wait --verbose</code></pre><div class="para">
+ The contents of snap2 are moved into snap1, resulting in:
+ </div><div class="para">
+ <code class="command">base ← snap1 ← active</code>. Snap2 is no longer valid and can be deleted
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ <code class="command">blockcommit</code> will corrupt any file that depends on the <em class="parameter"><code>--base</code></em> argument (other than files that depended on the <em class="parameter"><code>--top</code></em> argument, as those files now point to the base). To prevent this, do not commit changes into files shared by more than one guest. The <em class="parameter"><code>--verbose</code></em> option will allow the progress to be printed on the screen.
+ </div></div></div></li></ul></div></div><div class="section" id="sub-sect-blockpull"><div class="titlepage"><div><div><h3 class="title">E.13.2. Using blockpull to shorten a backing chain</h3></div></div></div><div class="para">
+ <code class="command">blockpull</code> can be used in in the following applications:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Flattens an image by populating it with data from its backing image chain. This makes the image file self-contained so that it no longer depends on backing images and looks like this:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Before: base.img ← Active
+ </div></li><li class="listitem"><div class="para">
+ After: base.img is no longer used by the guest and Active contains all of the data.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Flattens part of the backing image chain. This can be used to flatten snapshots into the top-level image and looks like this:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Before: base ← sn1 ←sn2 ← active
+ </div></li><li class="listitem"><div class="para">
+ After: base.img ← active. Note that active now contains all data from sn1 and sn2 and neither sn1 nor sn2 are used by the guest.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Moves the disk image to a new file system on the host. This is allows image files to be moved while the guest is running and looks like this:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Before (The original image file): <code class="filename">/fs1/base.vm.img</code>
+ </div></li><li class="listitem"><div class="para">
+ After: <code class="filename">/fs2/active.vm.qcow2</code> is now the new file system and <code class="filename">/fs1/base.vm.img</code> is no longer used.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Useful in live migration with post-copy storage migration. The disk image is copied from the source host to the destination host after live migration completes.
+ </div><div class="para">
+ In short this is what happens: Before:<code class="filename">/source-host/base.vm.img</code> After:<code class="filename">/destination-host/active.vm.qcow2</code>.<code class="filename">/source-host/base.vm.img</code> is no longer used.
+ </div></li></ul></div><div class="procedure" id="virsh-blk-pull-pro"><h6>Procedure E.2. Using blockpull to shorten a backing chain</h6><ol class="1"><li class="step"><div class="para">
+ It may be helpful to run this command prior to running <code class="command">blockpull</code>:
+ </div><pre class="screen">#<code class="command"> virsh snapshot-create-as $dom $name -- disk-only</code></pre></li><li class="step"><div class="para">
+ If the chain looks like this: <code class="command">base ← snap1 ← snap2 ← active</code> run the following:
+ </div><pre class="screen">#<code class="command"> virsh blockpull $dom $disk snap1</code></pre><div class="para">
+ This command makes 'snap1' the backing file of active, by pulling data from snap2 into active resulting in: base ← snap1 ← active.
+ </div></li><li class="step"><div class="para">
+ Once the <code class="command">blockpull</code> is complete, the <span class="application"><strong>libvirt</strong></span> tracking of the snapshot that created the extra image in the chain is no longer useful. Delete the tracking on the outdated snapshot with this command:
+ </div><pre class="screen">#<code class="command"> virsh snapshot-delete $dom $name -- metadata</code></pre></li></ol></div><div class="para">
+ Additional applications of <code class="command">blockpull</code> can be done as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ To flatten a single image and populate it with data from its backing image chain:<code class="command"># virsh blockpull example-domain vda -- wait</code>
+ </div></li><li class="listitem"><div class="para">
+ To flatten part of the backing image chain:<code class="command"># virsh blockpull example-domain vda -- base /path/to/base.img -- wait</code>
+ </div></li><li class="listitem"><div class="para">
+ To move the disk image to a new file system on the host:<code class="command"># virsh snapshot-create example-domain -- xmlfile /path/to/new.xml -- disk-only</code> followed by <code class="command"># virsh blockpull example-domain vda -- wait</code>
+ </div></li><li class="listitem"><div class="para">
+ To use live migration with post-copy storage migration:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ On the destination run:
+ </div><pre class="screen"><code class="command"> # qemu-img create -f qcow2 -o backing_file=/source-host/vm.img /destination-host/vm.qcow2</code></pre></li><li class="listitem"><div class="para">
+ On the source run:
+ </div><pre class="screen"><code class="command"># virsh migrate example-domain</code></pre></li><li class="listitem"><div class="para">
+ On the destination run:
+ </div><pre class="screen"><code class="command"># virsh blockpull example-domain vda -- wait</code></pre></li></ul></div></li></ul></div></div><div class="section" id="sub-sect-blkresize"><div class="titlepage"><div><div><h3 class="title">E.13.3. Using blockresize to change the size of a domain path</h3></div></div></div><div class="para">
+ <code class="command">blockresize</code> can be used to re-size a block device of a domain while the domain is running, using the absolute path of the block device which also corresponds to a unique target name (<code class="command"><target dev="name"/></code>) or source file (<code class="command"><source file="name"/></code>). This can be applied to one of the disk devices attached to domain (you can use the command <code class="command">domblklist</code> to print a table showing the brief information of all block devices associated with a given domain).
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Live image re-sizing will always resize the image, but may not immediately be picked up by guests. With recent guest kernels, the size of virtio-blk devices is automatically updated (older kernels require a guest reboot). With SCSI devices, it is required to manually trigger a re-scan in the guest with the command, <code class="command">echo > /sys/class/scsi_device/0:0:0:0/device/rescan</code>. In addition, with IDE it is required to reboot the guest before it picks up the new size.
+ </div></div></div><div class="procedure"><ul><li class="step"><div class="para">
+ Run the following command: <code class="command">blockresize [domain] [path size]</code> where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Domain is the unique target name or source file of the domain whose size you want to change
+ </div></li><li class="listitem"><div class="para">
+ Path size is a scaled integer which defaults to KiB (blocks of 1024 bytes) if there is no suffix. You must use a suffix of "B" to for bytes.
+ </div></li></ul></div></li></ul></div></div></div><div class="section" id="sect-guest-cpu-model-config"><div class="titlepage"><div><div><h2 class="title">E.14. Guest CPU model configuration</h2></div></div></div><div class="section" id="sect-guest-cpu-intro"><div class="titlepage"><div><div><h3 class="title">E.14.1. Introduction</h3></div></div></div><div class="para">
+ Every hypervisor has its own policy for what a guest will see for its CPUs by default. Whereas some hypervisors decide which CPU host features will be available for the guest, QEMU/KVM presents the guest with a generic model named <span class="bold bold"><strong>qemu32</strong></span> or <span class="bold bold"><strong>qemu64</strong></span>. These hypervisors perform more advanced filtering, classifying all physical CPUs into a handful of groups and have one baseline CPU model for each group that is presented to the guest. Such behavior enables the safe migration of guests between hosts, provided they all have physical CPUs that classify into the same group. libvirt does not typically enforce policy itself, rather it provides the mechanism on which the higher layers define their own desired policy. Understanding how to obtain CPU model information and define a suitable guest CPU model is critical to ensure guest migration is successful between hosts. Note that a hypervi
sor can only emulate features that it is aware of and features that were created after the hypervisor was released may not be emulated.
+ </div></div><div class="section" id="sect-learn-about-host-cpu"><div class="titlepage"><div><div><h3 class="title">E.14.2. Learning about the host CPU model</h3></div></div></div><div class="para">
+ The <code class="command">virsh capabilities</code> command displays an XML document describing the capabilities of the hypervisor connection and host. The XML schema displayed has been extended to provide information about the host CPU model. One of the big challenges in describing a CPU model is that every architecture has a different approach to exposing their capabilities. On x86, the capabilities of a modern CPU are exposed via the CPUID instruction. Essentially this comes down to a set of 32-bit integers with each bit given a specific meaning. Fortunately AMD and Intel agree on common semantics for these bits. Other hypervisors expose the notion of CPUID masks directly in their guest configuration format. However, QEMU/KVM supports far more than just the x86 architecture, so CPUID is clearly not suitable as the canonical configuration format. QEMU ended up using a scheme which combines a CPU model name string, with a set of named flags. On x86, the CPU model maps t
o a baseline CPUID mask, and the flags can be used to then toggle bits in the mask on or off. libvirt decided to follow this lead and uses a combination of a model name and flags. Here is an example of what libvirt reports as the capabilities on a development workstation:
+ </div><pre class="screen">
+# virsh capabilities
+<capabilities>
+
+ <host>
+ <uuid>c4a68e53-3f41-6d9e-baaf-d33a181ccfa0</uuid>
+ <cpu>
+ <arch>x86_64</arch>
+ <model>core2duo</model>
+ <topology sockets='1' cores='4' threads='1'/>
+ <feature name='lahf_lm'/>
+ <feature name='sse4.1'/>
+ <feature name='xtpr'/>
+ <feature name='cx16'/>
+ <feature name='tm2'/>
+ <feature name='est'/>
+ <feature name='vmx'/>
+ <feature name='ds_cpl'/>
+ <feature name='pbe'/>
+ <feature name='tm'/>
+ <feature name='ht'/>
+ <feature name='ss'/>
+ <feature name='acpi'/>
+ <feature name='ds'/>
+ </cpu>
+
+ ... snip ...
+ </host>
+
+</capabilities>
+</pre><div class="para">
+ It is not practical to have a database listing all known CPU models, so libvirt has a small list of baseline CPU model names. It chooses the one that shares the greatest number of CPUID bits with the actual host CPU and then lists the remaining bits as named features. Notice that libvirt does not display which features the baseline CPU contains. This might seem like a flaw at first, but as will be explained in this section, it is not actually necessary to know this information.
+ </div></div><div class="section" id="idm118920304"><div class="titlepage"><div><div><h3 class="title" id="idm118920304">E.14.3. Determining a compatible CPU model to suit a pool of hosts</h3></div></div></div><div class="para">
+ Now that it is possible to find out what CPU capabilities a single host has, the next step is to determine what CPU capabilities are best to expose to the guest. If it is known that the guest will never need to be migrated to another host, the host CPU model can be passed straight through unmodified. A virtualized data center may have a set of configurations that can guarantee all servers will have 100% identical CPUs. Again the host CPU model can be passed straight through unmodified. The more common case, though, is where there is variation in CPUs between hosts. In this mixed CPU environment, the lowest common denominator CPU must be determined. This is not entirely straightforward, so libvirt provides an API for exactly this task. If libvirt is provided a list of XML documents, each describing a CPU model for a host, libvirt will internally convert these to CPUID masks, calculate their intersection, and convert the CPUID mask result back into an XML CPU description.
Taking the CPU description from a server:
+ </div><pre class="screen">
+# virsh capabilities
+<capabilities>
+
+ <host>
+ <uuid>8e8e4e67-9df4-9117-bf29-ffc31f6b6abb</uuid>
+ <cpu>
+ <arch>x86_64</arch>
+ <model>Westmere</model>
+ <vendor>Intel</vendor>
+ <topology sockets='2' cores='4' threads='2'/>
+ <feature name='rdtscp'/>
+ <feature name='pdpe1gb'/>
+ <feature name='dca'/>
+ <feature name='xtpr'/>
+ <feature name='tm2'/>
+ <feature name='est'/>
+ <feature name='vmx'/>
+ <feature name='ds_cpl'/>
+ <feature name='monitor'/>
+ <feature name='pbe'/>
+ <feature name='tm'/>
+ <feature name='ht'/>
+ <feature name='ss'/>
+ <feature name='acpi'/>
+ <feature name='ds'/>
+ <feature name='vme'/>
+ </cpu>
+
+ ... snip ...
+
+</capabilities>
+</pre><div class="para">
+ A quick check can be made to see whether this CPU description is compatible with the previous workstation CPU description, using the <code class="command">virsh cpu-compare</code> command. To do so, the <code class="command">virsh capabilities > virsh-caps-workstation-full.xml</code> command was executed on the workstation. The file <code class="filename">virsh-caps-workstation-full.xml</code> was edited and reduced to just the following content:
+ </div><pre class="screen">
+<cpu>
+ <arch>x86_64</arch>
+ <model>core2duo</model>
+ <topology sockets='1' cores='4' threads='1'/>
+ <feature name='lahf_lm'/>
+ <feature name='sse4.1'/>
+ <feature name='xtpr'/>
+ <feature name='cx16'/>
+ <feature name='tm2'/>
+ <feature name='est'/>
+ <feature name='vmx'/>
+ <feature name='ds_cpl'/>
+ <feature name='pbe'/>
+ <feature name='tm'/>
+ <feature name='ht'/>
+ <feature name='ss'/>
+ <feature name='acpi'/>
+ <feature name='ds'/>
+ </cpu>
+</pre><div class="para">
+ The reduced content was stored in a file named <code class="filename">virsh-caps-workstation-cpu-only.xml</code> and the <code class="command">virsh cpu-compare</code> command can be executed using this file:
+ </div><pre class="screen">
+virsh cpu-compare virsh-caps-workstation-cpu-only.xml
+Host CPU is a superset of CPU described in virsh-caps-workstation-cpu-only.xml
+</pre><div class="para">
+ As seen in this output, libvirt is correctly reporting the CPUs are not strictly compatible, because there are several features in the server CPU that are missing in the workstation CPU. To be able to migrate between the workstation and the server, it will be necessary to mask out some features, but to determine which ones, libvirt provides an API for this, shown via the <code class="command">virsh cpu-baseline</code> command:
+ </div><pre class="screen">
+# virsh cpu-baseline virsh-cap-weybridge-strictly-cpu-only.xml
+<cpu match='exact'>
+ <model>Penryn</model>
+ <feature policy='require' name='xtpr'/>
+ <feature policy='require' name='tm2'/>
+ <feature policy='require' name='est'/>
+ <feature policy='require' name='vmx'/>
+ <feature policy='require' name='ds_cpl'/>
+ <feature policy='require' name='monitor'/>
+ <feature policy='require' name='pbe'/>
+ <feature policy='require' name='tm'/>
+ <feature policy='require' name='ht'/>
+ <feature policy='require' name='ss'/>
+ <feature policy='require' name='acpi'/>
+ <feature policy='require' name='ds'/>
+ <feature policy='require' name='vme'/>
+</cpu>
+</pre><div class="para">
+ Similarly, if the two <cpu>...</cpu> elements are put into a single file named <code class="filename">both-cpus.xml</code>, the following command would generate the same result:
+ </div><pre class="screen"> # virsh cpu-baseline both-cpus.xml</pre><div class="para">
+ In this case, libvirt has determined that in order to safely migrate a guest between the workstation and the server, it is necessary to mask out 3 features from the XML description for the server, and 3 features from the XML description for the workstation.
+ </div></div><div class="section" id="idm122440672"><div class="titlepage"><div><div><h3 class="title" id="idm122440672">E.14.4. Configuring the guest CPU model</h3></div></div></div><div class="para">
+ For simple defaults, the guest CPU configuration accepts the same basic XML representation as the host capabilities XML exposes. In other words, the XML from the <code class="command">cpu-baseline</code> virsh command can now be copied directly into the guest XML at the top level under the <domain> element. As the observant reader will have noticed from the previous XML snippet, there are a few extra attributes available when describing a CPU in the guest XML. These can mostly be ignored, but for the curious here is a quick description of what they do. The top level <cpu> element has an attribute called <span class="emphasis"><em>match</em></span> with possible values of:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ match='minimum' - the host CPU must have at least the CPU features described in the guest XML. If the host has additional features beyond the guest configuration, these will also be exposed to the guest.
+ </div></li><li class="listitem"><div class="para">
+ match='exact' - the host CPU must have at least the CPU features described in the guest XML. If the host has additional features beyond the guest configuration, these will be masked out from the guest.
+ </div></li><li class="listitem"><div class="para">
+ match='strict' - the host CPU must have exactly the same CPU features described in the guest XML.
+ </div></li></ul></div><div class="para">
+ The next enhancement is that the <feature> elements can each have an extra 'policy' attribute with possible values of:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ policy='force' - expose the feature to the guest even if the host does not have it. This is usually only useful in the case of software emulation.
+ </div></li><li class="listitem"><div class="para">
+ policy='require' - expose the feature to the guest and fail if the host does not have it. This is the sensible default.
+ </div></li><li class="listitem"><div class="para">
+ policy='optional' - expose the feature to the guest if it happens to support it.
+ </div></li><li class="listitem"><div class="para">
+ policy='disable' - if the host has this feature, then hide it from the guest.
+ </div></li><li class="listitem"><div class="para">
+ policy='forbid' - if the host has this feature, then fail and refuse to start the guest.
+ </div></li></ul></div><div class="para">
+ The 'forbid' policy is for a niche scenario where an incorrectly functioning application will try to use a feature even if it is not in the CPUID mask, and you wish to prevent accidentally running the guest on a host with that feature. The 'optional' policy has special behavior with respect to migration. When the guest is initially started the flag is optional, but when the guest is live migrated, this policy turns into 'require', since you cannot have features disappearing across migration.
+ </div></div></div></div><div xml:lang="en-US" class="appendix" id="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Managing guests with the Virtual Machine Manager (virt-manager)</h1></div></div></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 guests on your host system and on remote host systems. <code class="command">virt-manager</code> can perform virtualization management tasks, including:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ defining and creating guests,
+ </div></li><li class="listitem"><div class="para">
+ assigning memory,
+ </div></li><li class="listitem"><div class="para">
+ assigning virtual CPUs,
+ </div></li><li class="listitem"><div class="para">
+ monitoring operational performance,
+ </div></li><li class="listitem"><div class="para">
+ saving and restoring, pausing and resuming, and shutting down and starting guests,
+ </div></li><li class="listitem"><div class="para">
+ links to the textual and graphical consoles, and
+ </div></li><li class="listitem"><div class="para">
+ live and offline migrations.
+ </div></li></ul></div><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Starting_virt_manager"><div class="titlepage"><div><div><h2 class="title">F.1. 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_Administration_Guide-Starting_virt_manager-Starting_virt_manager"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt1.png" width="444" alt="Starting virt-manager" /></div></div><h6>Figure F.1. 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:
+ </div><pre class="screen">ssh -X <em class="replaceable"><code>host's address</code></em>
+[remotehost]# virt-manager
+</pre><div class="para">
+ Using <code class="command">ssh</code> to manage virtual machines and hosts is discussed further in <a class="xref" href="#sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_with_SSH">Section 21.1, “Remote management with SSH”</a>.
+ </div></div><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window"><div class="titlepage"><div><div><h2 class="title">F.2. The Virtual Machine Manager main window</h2></div></div></div><div class="para">
+ This main window displays all the running guests and resources used by guests. Select a guest by double clicking the guest's name.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-The_Virtual_Machine_Manager_main_window-Virtual_Machine_Manager_main_window"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt2.png" width="444" alt="Virtual Machine Manager main window" /></div></div><h6>Figure F.2. Virtual Machine Manager main window</h6></div><br class="figure-break" /></div><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_"><div class="titlepage"><div><div><h2 class="title">F.3. The virtual hardware details window</h2></div></div></div><div class="para">
+ The virtual hardware details window displays information about the virtual hardware configured for the guest. Virtual hardware resources can be added, removed and modified in this window. To access the virtual hardware details window, click on the icon in the toolbar.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-The_Virtual_Machine_Manager_details_window_-virt_manager_details_button"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt3.png" width="444" alt="The virtual hardware details icon" /></div></div><h6>Figure F.3. The virtual hardware details icon</h6></div><br class="figure-break" /><div class="para">
+ Clicking the icon displays the virtual hardware details window.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-The_Virtual_Machine_Manager_details_window_-virt_manager_details_window"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt4.png" width="444" alt="The virtual hardware details window" /></div></div><h6>Figure F.4. The virtual hardware details window</h6></div><br class="figure-break" /></div><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_"><div class="titlepage"><div><div><h2 class="title">F.4. Virtual Machine graphical console</h2></div></div></div><div class="para">
+ This window displays a guest's graphical console. Guests can use several different protocols to export their graphical framebuffers: <code class="command">virt-manager</code> supports <span class="application"><strong>VNC</strong></span> and <span class="application"><strong>SPICE</strong></span>. 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_Administration_Guide-Virtual_Machine_graphical_console_-Graphical_console_window"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt5.png" width="444" alt="Graphical console window" /></div></div><h6>Figure F.5. Graphical console window</h6></div><br class="figure-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><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'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. Although virt-manager is configured to listen to other public network interfaces and alternative methods can be configured, it is not recommended.
+ </div><div class="para">
+ Remote administration can be performed by tunneling over SSH which encrypts the traffic. Although VNC can be configured to access remotely without tunneling over SSH, for security reasons, it is not recommended. To remotely administer the guest follow the instructions in: <a class="xref" href="#chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests">Chapter 21, <em>Remote management of guests</em></a>. TLS can provide enterprise level security for managing guest and host systems.
+ </div></div></div><div class="para">
+ Your local desktop can intercept key combinations (for example, Ctrl+Alt+F1) to prevent them from being sent to the guest machine. You can use the <span class="guimenuitem"><strong>Send key</strong></span> menu option to send these sequences. From the guest machine window, click the <span class="guimenuitem"><strong>Send key</strong></span> menu and select the key sequence to send. In addition, from this menu you can also capture the screen output.
+ </div><div class="para">
+ SPICE is an alternative to VNC available for Fedora.
+ </div></div><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window"><div class="titlepage"><div><div><h2 class="title">F.5. Adding a remote connection</h2></div></div></div><div class="para">
+ This procedure covers how to set up a connection to a remote system using <code class="command">virt-manager</code>.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To create a new connection open the <span class="guilabel"><strong>File</strong></span> menu and select the <span class="guilabel"><strong>Add Connection...</strong></span> menu item.
+ </div></li><li class="step"><div class="para">
+ The <span class="guilabel"><strong>Add Connection</strong></span> wizard appears. Select the hypervisor. For Fedora systems select <span class="guilabel"><strong>QEMU/KVM</strong></span>. Select Local for the local system or one of the remote connection options and click <span class="guilabel"><strong>Connect</strong></span>. This example uses Remote tunnel over SSH which works on default installations. For more information on configuring remote connections refer to <a class="xref" href="#chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests">Chapter 21, <em>Remote management of guests</em></a>
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Remote_management-Add_connection"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt6.png" alt="Add Connection" /></div></div><h6>Figure F.6. Add Connection</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Enter the root password for the selected host when prompted.
+ </div></li></ol></div><div class="para">
+ A remote host is now connected and appears in the main <code class="command">virt-manager</code> window.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Remote_management-Remove_host_in_the_main_virt-manager_window"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt7.png" width="444" alt="Remote host in the main virt-manager window" /></div></div><h6>Figure F.7. Remote host in the main virt-manager window</h6></div><br class="figure-break" /></div><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details"><div class="titlepage"><div><div><h2 class="title">F.6. Displaying guest details</h2></div></div></div><div class="para">
+ You can use the Virtual Machine Monitor to view activity 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 class="step"><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_Administration_Guide-Displaying_guest_details-Selecting_a_virtual_machine_to_display_"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt1.png" width="444" alt="Selecting a virtual machine to display" /></div></div><h6>Figure F.8. Selecting a virtual machine to display </h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ From the Virtual Machine Manager <span class="guilabel"><strong>Edit</strong></span> menu, select <span class="guilabel"><strong>Virtual Machine Details</strong></span>.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Displaying_virtual_machine_details_menu"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt11.png" width="444" alt="Displaying the virtual machine details" /></div></div><h6>Figure F.9. Displaying the virtual machine details</h6></div><br class="figure-break" /><div class="para">
+ When the Virtual Machine details window opens, there may be a console displayed. Should this happen, clikc <span class="guilabel"><strong>View</strong></span> and then select <span class="guilabel"><strong>Details</strong></span>. The Overview window opens first by default. To go back to this window, select <span class="guilabel"><strong>Overview</strong></span> from the navigation pane on the left hand side.
+ </div><div class="para">
+ The <span class="guilabel"><strong>Overview</strong></span> view shows a summary of configuration details for the guest.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Displaying_guest_details_overview"><div class="figure-contents"><div class="mediaobject"><img src="images/virtual_machine_overview.png" width="444" alt="Displaying guest details overview" /></div></div><h6>Figure F.10. Displaying guest details overview</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Select <span class="guilabel"><strong>Performance</strong></span> from the navigation pane on the left hand side.
+ </div><div class="para">
+ The <span class="guilabel"><strong>Performance</strong></span> view shows a summary of guest performance, including CPU and Memory usage.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Displaying_guest_performance"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt13.png" width="444" alt="Displaying guest performance details" /></div></div><h6>Figure F.11. Displaying guest performance details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Select <span class="guilabel"><strong>Processor</strong></span> from the navigation pane on the left hand side. The <span class="guilabel"><strong>Processor</strong></span> view allows you to view or change the current processor allocation.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Processor_allocation_panel"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt14.png" width="444" alt="Processor allocation panel" /></div></div><h6>Figure F.12. Processor allocation panel</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Select <span class="guilabel"><strong>Memory</strong></span> from the navigation pane on the left hand side. The <span class="guilabel"><strong>Memory</strong></span> view allows you to view or change the current memory allocation.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Displaying_memory_allocation"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt15.png" width="444" alt="Displaying memory allocation" /></div></div><h6>Figure F.13. Displaying memory allocation</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Each virtual disk attached to the virtual machine is displayed in the navigation pane. Click on a virtual disk to modify or remove it.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Displaying_disk_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt16.png" width="444" alt="Displaying disk configuration" /></div></div><h6>Figure F.14. Displaying disk configuration</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Each virtual network interface attached to the virtual machine is displayed in the navigation pane. Click on a virtual network interface to modify or remove it.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Displaying_network_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt17.png" width="444" alt="Displaying network configuration" /></div></div><h6>Figure F.15. Displaying network configuration</h6></div><br class="figure-break" /></li></ol></div></div><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring"><div class="titlepage"><div><div><h2 class="title">F.7. Performance monitoring</h2></div></div></div><div class="para">
+ Performance monitoring preferences can be modified with <code class="command">virt-manager</code>'s preferences window.
+ </div><div class="para">
+ To configure performance monitoring:
+ </div><div class="procedure"><ol class="1"><li class="step"><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_Administration_Guide-Status_monitoring-Modifying_guest_preferences"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-VIrt-Manager-fig31pt18.png" width="444" alt="Modifying guest preferences" /></div></div><h6>Figure F.16. Modifying guest preferences</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guilabel"><strong>Preferences</strong></span> window appears.
+ </div></li><li class="step"><div class="para">
+ From the <span class="guilabel"><strong>Stats</strong></span> tab specify the time in seconds or stats polling options.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Status_monitoring-Configuring_status_monitoring"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt19.png" alt="Configuring performance monitoring" /></div></div><h6>Figure F.17. Configuring performance monitoring</h6></div><br class="figure-break" /></li></ol></div></div><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage"><div class="titlepage"><div><div><h2 class="title">F.8. Displaying CPU usage for guests</h2></div></div></div><div class="para">
+ To view the CPU usage for all guests on your system:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ From the <span class="guilabel"><strong>View</strong></span> menu, select <span class="guilabel"><strong>Graph</strong></span>, then the <span class="guilabel"><strong>Guest CPU Usage</strong></span> check box.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_CPU_usage-Selecting_guest-CPU_usage"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt24.png" width="444" alt="Enabling guest CPU usage statistics graphing" /></div></div><h6>Figure F.18. Enabling guest CPU usage statistics graphing</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ The Virtual Machine Manager shows a graph of CPU usage for all virtual machines on your system.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_CPU_usage-Displaying_CPU_usage"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager_fig31pt25.png" width="444" alt="Guest CPU usage graph" /></div></div><h6>Figure F.19. Guest CPU usage graph</h6></div><br class="figure-break" /></li></ol></div></div><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage"><div class="titlepage"><div><div><h2 class="title">F.9. Displaying CPU usage for hosts</h2></div></div></div><div class="para">
+ To view the CPU usage for all hosts on your system:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ From the <span class="guilabel"><strong>View</strong></span> menu, select <span class="guilabel"><strong>Graph</strong></span>, then the <span class="guilabel"><strong>Host CPU Usage</strong></span> check box.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_Host-CPU_usage-Selecting_CPU_usage"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt24a.png" width="444" alt="Enabling host CPU usage statistics graphing" /></div></div><h6>Figure F.20. Enabling host CPU usage statistics graphing</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ The Virtual Machine Manager shows a graph of host CPU usage on your system.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_host-CPU_usage-Displaying_CPU_usage"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager_fig31pt25a.png" width="444" alt="Host CPU usage graph" /></div></div><h6>Figure F.21. Host CPU usage graph</h6></div><br class="figure-break" /></li></ol></div></div><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO"><div class="titlepage"><div><div><h2 class="title">F.10. Displaying Disk I/O</h2></div></div></div><div class="para">
+ To view the disk I/O for all virtual machines on your system:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Make sure that the Disk I/O statisctics collection is enabled. To do this, from the <span class="guilabel"><strong>Edit</strong></span> menu, select <span class="guilabel"><strong>Preferences</strong></span> and click the <span class="guilabel"><strong>Stats</strong></span>tab.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Disk I/O </strong></span>checkbox.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-enabling_Disk_IO-stats"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager-enable-disk-io.png" alt="Enabling Disk I/O" /></div></div><h6>Figure F.22. Enabling Disk I/O</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ To enable the Disk I.O display, from the <span class="guilabel"><strong>View</strong></span> menu, select <span class="guilabel"><strong>Graph</strong></span>, then the <span class="guilabel"><strong>Disk I/O</strong></span> check box.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_Disk_IO-Selecting_Disk_IO"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager_fig31pt26.png" width="444" alt="Selecting Disk I/O" /></div></div><h6>Figure F.23. Selecting Disk I/O</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ The Virtual Machine Manager shows a graph of Disk I/O for all virtual machines on your system.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_Disk_IO-Displaying_Disk_IO"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt27.png" width="444" alt="Displaying Disk I/O" /></div></div><h6>Figure F.24. Displaying Disk I/O</h6></div><br class="figure-break" /></li></ol></div></div><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO"><div class="titlepage"><div><div><h2 class="title">F.11. Displaying Network I/O</h2></div></div></div><div class="para">
+ To view the network I/O for all virtual machines on your system:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Make sure that the Network I/O statisctics collection is enabled. To do this, from the <span class="guilabel"><strong>Edit</strong></span> menu, select <span class="guilabel"><strong>Preferences</strong></span> and click the <span class="guilabel"><strong>Stats</strong></span>tab.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Network I/O </strong></span>checkbox.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-enabling_network_IO-stats"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager-enable-networkio.png" alt="Enabling Network I/O" /></div></div><h6>Figure F.25. Enabling Network I/O</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ To display the Network I/O statistics, from the <span class="guilabel"><strong>View</strong></span> menu, select <span class="guilabel"><strong>Graph</strong></span>, then the <span class="guilabel"><strong>Network I/O</strong></span> check box.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_Network_IO-Selecting_Network_IO"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt28.png" width="444" alt="Selecting Network I/O" /></div></div><h6>Figure F.26. Selecting Network I/O</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ The Virtual Machine Manager shows a graph of Network I/O for all virtual machines on your system.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_Network_IO-Displaying_Network_IO"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt29.png" width="444" alt="Displaying Network I/O" /></div></div><h6>Figure F.27. Displaying Network I/O</h6></div><br class="figure-break" /></li></ol></div></div></div><div xml:lang="en-US" class="appendix" id="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Guest disk access with offline tools</h1></div></div></div><div class="section" id="sect-introduction-Virtualization_Administration_Guide-Guest_Disks_libguestfs"><div class="titlepage"><div><div><h2 class="title">G.1. Introduction</h2></div></div></div><div class="para">
+ Fedora comes with tools to access, edit and create guest disks or other disk images. There are several uses for these tools, including:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Viewing or downloading files located on a guest disk.
+ </div></li><li class="listitem"><div class="para">
+ Editing or uploading files onto a guest disk.
+ </div></li><li class="listitem"><div class="para">
+ Reading or writing guest configuration.
+ </div></li><li class="listitem"><div class="para">
+ Reading or writing the Windows Registry in Windows guests.
+ </div></li><li class="listitem"><div class="para">
+ Preparing new disk images containing files, directories, file systems, partitions, logical volumes and other options.
+ </div></li><li class="listitem"><div class="para">
+ Rescuing and repairing guests that fail to boot or those that need boot configuration changes.
+ </div></li><li class="listitem"><div class="para">
+ Monitoring disk usage of guests.
+ </div></li><li class="listitem"><div class="para">
+ Auditing compliance of guests, for example to organizational security standards.
+ </div></li><li class="listitem"><div class="para">
+ Deploying guests by cloning and modifying templates.
+ </div></li><li class="listitem"><div class="para">
+ Reading CD and DVD ISO and floppy disk images.
+ </div></li></ul></div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ You must <span class="bold bold"><strong>never</strong></span> use these tools to write to a guest or disk image which is attached to a running virtual machine, not even to open such a disk image in write mode. Doing so will result in disk corruption of the guest. The tools try to prevent you from doing this, however do not catch all cases. If there is any suspicion that a guest might be running, it is strongly recommended that the tools not be used, or at least <span class="bold bold"><strong>always</strong></span> use the tools in read-only mode.
+ </div></div></div></div><div class="section" id="sect-Terminology-Guest_Disks_libguestfs"><div class="titlepage"><div><div><h2 class="title">G.2. Terminology</h2></div></div></div><div class="para">
+ This section explains the terms used throughout this chapter.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>libguestfs (GUEST FileSystem LIBrary)</strong></span> - the underlying C library that provides the basic functionality for opening disk images, reading and writing files and so on. You can write C programs directly to this API, but it is quite low level.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>guestfish (GUEST Filesystem Interactive SHell)</strong></span> is an interactive shell that you can use from the command line or from shell scripts. It exposes all of the functionality of the libguestfs API.
+ </div></li><li class="listitem"><div class="para">
+ Various virt tools are built on top of libguestfs, and these provide a way to perform specific single tasks from the command line. Tools include <span class="bold bold"><strong>virt-df</strong></span>, <span class="bold bold"><strong>virt-rescue</strong></span>, <span class="bold bold"><strong>virt-resize</strong></span> and <span class="bold bold"><strong>virt-edit</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>hivex</strong></span> and <span class="bold bold"><strong>Augeas</strong></span> are libraries for editing the Windows Registry and Linux configuration files respectively. Although these are separate from libguestfs, much of the value of libguestfs comes from the combination of these tools.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>guestmount</strong></span> is an interface between libguestfs and FUSE. It is primarily used to mount file systems from disk images on your host. This functionality is not necessary, but can be useful.
+ </div></li></ul></div></div><div class="section" id="sect-Guide-Guest_Disks_libguestfs-installation"><div class="titlepage"><div><div><h2 class="title">G.3. Installation</h2></div></div></div><div class="para">
+ To install libguestfs, guestfish, the libguestfs tools, guestmount and support for Windows guests, subscribe to the RHEL V2WIN channel, go to the <a href="https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=631818">Fedora Website</a> and run the following command:
+ </div><pre class="screen">
+# yum install libguestfs guestfish libguestfs-tools libguestfs-mount libguestfs-winsupport
+</pre><div class="para">
+ To install every libguestfs-related package including the language bindings, run the following command:
+ </div><pre class="screen">
+# yum install '*guestf*'
+</pre></div><div class="section" id="sect-the_guestfish_shell"><div class="titlepage"><div><div><h2 class="title">G.4. The guestfish shell</h2></div></div></div><div class="para">
+ <span class="bold bold"><strong>guestfish</strong></span> is an interactive shell that you can use from the command line or from shell scripts to access guest file systems. All of the functionality of the libguestfs API is available from the shell.
+ </div><div class="para">
+ To begin viewing or editing a virtual machine disk image, run the following command, substituting the path to your desired disk image:
+ </div><pre class="screen">
+guestfish --ro -a /path/to/disk/image
+</pre><div class="para">
+ <span class="bold bold"><strong>--ro</strong></span> means that the disk image is opened read-only. This mode is always safe but does not allow write access. Only omit this option when you are <span class="bold bold"><strong>certain</strong></span> that the guest is not running, or the disk image is not attached to a live guest. It is not possible to use libguestfs to edit a live guest, and attempting to will assuredly result in irreversible disk corruption.
+ </div><div class="para">
+ <span class="bold bold"><strong>/path/to/disk/image</strong></span> is the path to the disk. This can be a file, a host logical volume (such as /dev/VG/LV), a host device (/dev/cdrom) or a SAN LUN (/dev/sdf3).
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ libguestfs and guestfish do not require root privileges. You only need to run them as root if the disk image being accessed needs root to read and/or write.
+ </div></div></div><div class="para">
+ When you start guestfish interactively, it will display this prompt:
+ </div><pre class="screen">
+ guestfish --ro -a /path/to/disk/image
+
+Welcome to guestfish, the libguestfs filesystem interactive shell for editing virtual machine filesystems.
+
+ Type: 'help' for help on commands
+ 'man' to read the manual
+ 'quit' to quit the shell
+
+><fs>
+</pre><div class="para">
+ At the prompt, type <span class="bold bold"><strong>run</strong></span> to initiate the library and attach the disk image. This can take up to 30 seconds the first time it is done. Subsequent starts will complete much faster.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ libguestfs will use hardware virtualization acceleration such as KVM (if available) to speed up this process.
+ </div></div></div><div class="para">
+ Once the <span class="bold bold"><strong>run</strong></span> command has been entered, other commands can be used, as the following section demonstrates.
+ </div><div class="section" id="sect-Viewing_file_systems_with_guestfish"><div class="titlepage"><div><div><h3 class="title">G.4.1. Viewing file systems with guestfish</h3></div></div></div><div class="section" id="sect-Manual-listing-and-viewing"><div class="titlepage"><div><div><h4 class="title">G.4.1.1. Manual listing and viewing</h4></div></div></div><div class="para">
+ The <code class="command">list-filesystems</code> command will list file systems found by libguestfs. This output shows a Red Hat Enterprise Linux 4 disk image:
+ </div><pre class="screen">
+><fs> run
+><fs> list-filesystems
+/dev/vda1: ext3
+/dev/VolGroup00/LogVol00: ext3
+/dev/VolGroup00/LogVol01: swap
+</pre><div class="para">
+ This output shows a Windows disk image:
+ </div><pre class="screen">
+><fs> run
+><fs> list-filesystems
+/dev/vda1: ntfs
+/dev/vda2: ntfs
+</pre><div class="para">
+ Other useful commands are <code class="command">list-devices</code>, <code class="command">list-partitions</code>, <code class="command">lvs</code>, <code class="command">pvs</code>, <code class="command">vfs-type</code> and <code class="command">file</code>. You can get more information and help on any command by typing <code class="command">help</code> <span class="emphasis"><em>command</em></span>, as shown in the following output:
+ </div><pre class="screen">
+><fs> help vfs-type
+ NAME
+ vfs-type - get the Linux VFS type corresponding to a mounted device
+
+ SYNOPSIS
+ vfs-type device
+
+ DESCRIPTION
+ This command gets the filesystem type corresponding to the filesystem on
+ "device".
+
+ For most filesystems, the result is the name of the Linux VFS module
+ which would be used to mount this filesystem if you mounted it without
+ specifying the filesystem type. For example a string such as "ext3" or
+ "ntfs".
+</pre><div class="para">
+ To view the actual contents of a file system, it must first be mounted. This example uses one of the Windows partitions shown in the previous output (<code class="filename">/dev/vda2</code>), which in this case is known to correspond to the <span class="bold bold"><strong>C:\</strong></span> drive:
+ </div><pre class="screen">
+><fs> mount-ro /dev/vda2 /
+><fs> ll /
+total 1834753
+ drwxrwxrwx 1 root root 4096 Nov 1 11:40 .
+ drwxr-xr-x 21 root root 4096 Nov 16 21:45 ..
+ lrwxrwxrwx 2 root root 60 Jul 14 2009 Documents and Settings
+ drwxrwxrwx 1 root root 4096 Nov 15 18:00 Program Files
+ drwxrwxrwx 1 root root 4096 Sep 19 10:34 Users
+ drwxrwxrwx 1 root root 16384 Sep 19 10:34 Windows
+</pre><div class="para">
+ You can use guestfish commands such as <code class="command">ls</code>, <code class="command">ll</code>, <code class="command">cat</code>, <code class="command">more</code>, <code class="command">download</code> and <code class="command">tar-out</code> to view and download files and directories.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ There is no concept of a current working directory in this shell. Unlike ordinary shells, you cannot for example use the <code class="command">cd</code> command to change directories. All paths must be fully qualified starting at the top with a forward slash (<span class="bold bold"><strong>/</strong></span>) character. Use the <span class="emphasis"><em>Tab</em></span> key to complete paths.
+ </div></div></div><div class="para">
+ To exit from the guestfish shell, type <code class="command">exit</code> or enter <code class="command">Ctrl+d</code>.
+ </div></div><div class="section" id="sect-Via_guestfish_inspection"><div class="titlepage"><div><div><h4 class="title">G.4.1.2. Via guestfish inspection</h4></div></div></div><div class="para">
+ Instead of listing and mounting file systems by hand, it is possible to let guestfish itself inspect the image and mount the file systems as they would be in the guest. To do this, add the <span class="bold bold"><strong>-i</strong></span> option on the command line:
+ </div><pre class="screen">
+guestfish --ro -a /path/to/disk/image -i
+
+Welcome to guestfish, the libguestfs filesystem interactive shell for
+ editing virtual machine filesystems.
+
+ Type: 'help' for help on commands
+ 'man' to read the manual
+ 'quit' to quit the shell
+
+ Operating system: Red Hat Enterprise Linux AS release 4 (Nahant Update 8)
+ /dev/VolGroup00/LogVol00 mounted on /
+ /dev/vda1 mounted on /boot
+
+ ><fs> ll /
+ total 210
+ drwxr-xr-x. 24 root root 4096 Oct 28 09:09 .
+ drwxr-xr-x 21 root root 4096 Nov 17 15:10 ..
+ drwxr-xr-x. 2 root root 4096 Oct 27 22:37 bin
+ drwxr-xr-x. 4 root root 1024 Oct 27 21:52 boot
+ drwxr-xr-x. 4 root root 4096 Oct 27 21:21 dev
+ drwxr-xr-x. 86 root root 12288 Oct 28 09:09 etc
+ [etc]
+</pre><div class="para">
+ Because guestfish needs to start up the libguestfs back end in order to perform the inspection and mounting, the <code class="command">run</code> command is not necessary when using the <code class="command">-i</code> option. The <code class="command">-i</code> option works for many common Linux and Windows guests.
+ </div></div><div class="section" id="sect-Accessing-aguesT-by-name"><div class="titlepage"><div><div><h4 class="title">G.4.1.3. Accessing a guest by name</h4></div></div></div><div class="para">
+ A guest can be accessed from the command line when you specify its name as known to libvirt (in other words, as it appears in <code class="command">virsh list --all</code>). Use the <code class="command">-d</code> option to access a guest by its name, with or without the <code class="command">-i</code> option:
+ </div><pre class="screen">
+guestfish --ro -d GuestName -i
+</pre></div></div><div class="section" id="sect-Modifying-files-with-guestfish"><div class="titlepage"><div><div><h3 class="title">G.4.2. Modifying files with guestfish</h3></div></div></div><div class="para">
+ To modify files, create directories or make other changes to a guest, first heed the warning at the beginning of this section: <span class="bol bol">your guest must be shut down</span>. Editing or changing a running disk with guestfish <span class="bold bold"><strong>will</strong></span> result in disk corruption. This section gives an example of editing the <code class="filename">/boot/grub/grub.conf</code> file. When you are sure the guest is shut down you can omit the <code class="command">--ro</code> flag in order to get write access via a command such as:
+ </div><pre class="screen">
+guestfish -d RHEL3 -i
+
+Welcome to guestfish, the libguestfs filesystem interactive shell for
+ editing virtual machine filesystems.
+
+ Type: 'help' for help on commands
+ 'man' to read the manual
+ 'quit' to quit the shell
+
+ Operating system: Red Hat Enterprise Linux AS release 3 (Taroon Update 9)
+ /dev/vda2 mounted on /
+ /dev/vda1 mounted on /boot
+
+><fs> edit /boot/grub/grub.conf
+</pre><div class="para">
+ Commands to edit files include <code class="command">edit</code>, <code class="command">vi</code> and <code class="command">emacs</code>. Many commands also exist for creating files and directories, such as <code class="command">write</code>, <code class="command">mkdir</code>, <code class="command">upload</code> and <code class="command">tar-in</code>.
+ </div></div><div class="section" id="sect-Other-actions-with-guestfish"><div class="titlepage"><div><div><h3 class="title">G.4.3. Other actions with guestfish</h3></div></div></div><div class="para">
+ You can also format file systems, create partitions, create and resize LVM logical volumes and much more, with commands such as <code class="command">mkfs</code>, <code class="command">part-add</code>, <code class="command">lvresize</code>, <code class="command">lvcreate</code>, <code class="command">vgcreate</code> and <code class="command">pvcreate</code>.
+ </div></div><div class="section" id="sect-Shell-scripting-with-guestfish"><div class="titlepage"><div><div><h3 class="title">G.4.4. Shell scripting with guestfish</h3></div></div></div><div class="para">
+ Once you are familiar with using guestfish interactively, according to your needs, writing shell scripts with it may be useful. The following is a simple shell script to add a new MOTD (message of the day) to a guest:
+ </div><pre class="screen">
+#!/bin/bash -
+ set -e
+ guestname="$1"
+
+ guestfish -d "$guestname" -i <<'EOF'
+ write /etc/motd "Welcome to Acme Incorporated."
+ chmod 0644 /etc/motd
+ EOF
+</pre></div><div class="section" id="sect-Augeas-and-libguestfs-scripting"><div class="titlepage"><div><div><h3 class="title">G.4.5. Augeas and libguestfs scripting</h3></div></div></div><div class="para">
+ Combining libguestfs with Augeas can help when writing scripts to manipulate Linux guest configuration. For example, the following script uses Augeas to parse the keyboard configuration of a guest, and to print out the layout. Note that this example only works with guests running Red Hat Enterprise Linux:
+ </div><pre class="screen">
+#!/bin/bash -
+ set -e
+ guestname="$1"
+
+ guestfish -d "$1" -i --ro <<'EOF'
+ aug-init / 0
+ aug-get /files/etc/sysconfig/keyboard/LAYOUT
+ EOF
+</pre><div class="para">
+ Augeas can also be used to modify configuration files. You can modify the above script to <span class="bold bold"><strong>change</strong></span> the keyboard layout:
+ </div><pre class="screen">
+#!/bin/bash -
+ set -e
+ guestname="$1"
+
+ guestfish -d "$1" -i <<'EOF'
+ aug-init / 0
+ aug-set /files/etc/sysconfig/keyboard/LAYOUT '"gb"'
+ aug-save
+ EOF
+</pre><div class="para">
+ Note the three changes between the two scripts:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ The <code class="command">--ro</code> option has been removed in the second example, giving the ability to write to the guest.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="command">aug-get</code> command has been changed to <code class="command">aug-set</code> to modify the value instead of fetching it. The new value will be <code class="command">"gb"</code> (including the quotes).
+ </div></li><li class="listitem"><div class="para">
+ The <code class="command">aug-save</code> command is used here so Augeas will write the changes out to disk.
+ </div></li></ol></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ More information about Augeas can be found on the website <a href="http://augeas.net">http://augeas.net</a>.
+ </div></div></div><div class="para">
+ guestfish can do much more than we can cover in this introductory document. For example, creating disk images from scratch:
+ </div><pre class="screen">
+guestfish -N fs
+</pre><div class="para">
+ Or copying out whole directories from a disk image:
+ </div><pre class="screen">
+><fs> copy-out /home /tmp/home
+</pre><div class="para">
+ For more information see the man page guestfish(1).
+ </div></div></div><div class="section" id="sect-other-commands"><div class="titlepage"><div><div><h2 class="title">G.5. Other commands</h2></div></div></div><div class="para">
+ This section describes tools that are simpler equivalents to using guestfish to view and edit guest disk images.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">virt-cat</code> is similar to the guestfish <code class="command">download</code> command. It downloads and displays a single file to the guest. For example:
+ </div><pre class="screen">
+# virt-cat RHEL3 /etc/ntp.conf | grep ^server
+ server 127.127.1.0 # local clock
+</pre></li><li class="listitem"><div class="para">
+ <code class="command">virt-edit</code> is similar to the guestfish <code class="command">edit</code> command. It can be used to interactively edit a single file within a guest. For example, you may need to edit the <code class="filename">grub.conf</code> file in a Linux-based guest that will not boot:
+ </div><pre class="screen">
+# virt-edit LinuxGuest /boot/grub/grub.conf
+</pre><div class="para">
+ <code class="command">virt-edit</code> has another mode where it can be used to make simple non-interactive changes to a single file. For this, the <span class="bold bold"><strong>-e</strong></span> option is used. This command, for example, changes the root password in a Linux guest to having no password:
+ </div><pre class="screen">
+# virt-edit LinuxGuest /etc/passwd -e 's/^root:.*?:/root::/'
+</pre></li><li class="listitem"><div class="para">
+ <code class="command">virt-ls</code> is similar to the guestfish <code class="command">ls</code>, <code class="command">ll</code> and <code class="command">find</code> commands. It is used to list a directory or directories (recursively). For example, the following command would recursively list files and directories under /home in a Linux guest:
+ </div><pre class="screen">
+# virt-ls -R LinuxGuest /home/ | less
+</pre></li></ul></div></div><div class="section" id="sect-virt-rescue"><div class="titlepage"><div><div><h2 class="title">G.6. virt-rescue: The rescue shell</h2></div></div></div><div class="section" id="sect-virt-rescue-intro"><div class="titlepage"><div><div><h3 class="title">G.6.1. Introduction</h3></div></div></div><div class="para">
+ This section describes <code class="command">virt-rescue</code>, which can be considered analogous to a rescue CD for virtual machines. It boots a guest into a rescue shell so that maintenance can be performed to correct errors and the guest can be repaired.
+ </div><div class="para">
+ There is some overlap between virt-rescue and guestfish. It is important to distinguish their differing uses. virt-rescue is for making interactive, ad-hoc changes using ordinary Linux file system tools. It is particularly suited to rescuing a guest that has gone wrong. virt-rescue cannot be scripted.
+ </div><div class="para">
+ In contrast, guestfish is particularly useful for making scripted, structured changes through a formal set of commands (the libguestfs API), although it can also be used interactively.
+ </div></div><div class="section" id="sect-run-virt-rescue"><div class="titlepage"><div><div><h3 class="title">G.6.2. Running virt-rescue</h3></div></div></div><div class="para">
+ Before you use <code class="command">virt-rescue</code> on a guest, make sure the guest is not running, otherwise disk corruption will occur. When you are sure the guest is not live, enter:
+ </div><pre class="screen">
+virt-rescue GuestName
+</pre><div class="para">
+ (where GuestName is the guest name as known to libvirt), or:
+ </div><pre class="screen">
+virt-rescue /path/to/disk/image
+</pre><div class="para">
+ (where the path can be any file, any logical volume, LUN, or so on) containing a guest disk.
+ </div><div class="para">
+ You will first see output scroll past, as virt-rescue boots the rescue VM. In the end you will see:
+ </div><pre class="screen">
+Welcome to virt-rescue, the libguestfs rescue shell.
+
+ Note: The contents of / are the rescue appliance.
+ You have to mount the guest's partitions under /sysroot
+ before you can examine them.
+
+ bash: cannot set terminal process group (-1): Inappropriate ioctl for device
+ bash: no job control in this shell
+ ><rescue>
+</pre><div class="para">
+ The shell prompt here is an ordinary bash shell, and a reduced set of ordinary Fedora commands is available. For example, you can enter:
+ </div><pre class="screen">
+><rescue> fdisk -l /dev/vda
+</pre><div class="para">
+ The previous command will list disk partitions. To mount a file system, it is suggested that you mount it under <code class="filename">/sysroot</code>, which is an empty directory in the rescue machine for the user to mount anything you like. Note that the files under <code class="filename">/</code> are files from the rescue VM itself:
+ </div><pre class="screen">
+><rescue> mount /dev/vda1 /sysroot/
+EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
+><rescue> ls -l /sysroot/grub/
+ total 324
+ -rw-r--r--. 1 root root 63 Sep 16 18:14 device.map
+ -rw-r--r--. 1 root root 13200 Sep 16 18:14 e2fs_stage1_5
+ -rw-r--r--. 1 root root 12512 Sep 16 18:14 fat_stage1_5
+ -rw-r--r--. 1 root root 11744 Sep 16 18:14 ffs_stage1_5
+ -rw-------. 1 root root 1503 Oct 15 11:19 grub.conf
+ [...]
+</pre><div class="para">
+ When you are finished rescuing the guest, exit the shell by entering <code class="command">exit</code> or <code class="command">Ctrl+d</code>.
+ </div><div class="para">
+ <code class="command">virt-rescue</code> has many command line options. The options most often used are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>--ro</strong></span>: Operate in read-only mode on the guest. No changes will be saved. You can use this to experiment with the guest. As soon as you exit from the shell, all of your changes are discarded.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>--network</strong></span>: Enable network access from the rescue shell. Use this if you need to, for example, download RPM or other files into the guest.
+ </div></li></ul></div></div></div><div class="section" id="sect-virt-df"><div class="titlepage"><div><div><h2 class="title">G.7. virt-df: Monitoring disk usage</h2></div></div></div><div class="section" id="sect-virt-df-intro"><div class="titlepage"><div><div><h3 class="title">G.7.1. Introduction</h3></div></div></div><div class="para">
+ This section describes <code class="command">virt-df</code>, which displays file system usage from a disk image or a guest. It is similar to the Linux <code class="command">df</code> command, but for virtual machines.
+ </div></div><div class="section" id="run-virt-df"><div class="titlepage"><div><div><h3 class="title">G.7.2. Running virt-df</h3></div></div></div><div class="para">
+ To display file system usage for all file systems found in a disk image, enter the following:
+ </div><pre class="screen">
+# virt-df /dev/vg_guests/RHEL6
+ Filesystem 1K-blocks Used Available Use%
+ RHEL6:/dev/sda1 101086 10233 85634 11%
+ RHEL6:/dev/VolGroup00/LogVol00 7127864 2272744 4493036 32%
+</pre><div class="para">
+ (Where <code class="filename">/dev/vg_guests/RHEL6</code> is a Red Hat Enterprise Linux 4 guest disk image. The path in this case is the host logical volume where this disk image is located.)
+ </div><div class="para">
+ You can also use <code class="command">virt-df</code> on its own to list information about all of your guests (ie. those known to libvirt). The <code class="command">virt-df</code> command recognizes some of the same options as the standard <code class="command">df</code> such as <code class="command">-h</code> (human-readable) and <code class="command">-i</code> (show inodes instead of blocks).
+ </div><div class="para">
+ <code class="command">virt-df</code> also works on Windows guests:
+ </div><pre class="screen">
+# virt-df -h
+ Filesystem Size Used Available Use%
+ F14x64:/dev/sda1 484.2M 66.3M 392.9M 14%
+ F14x64:/dev/vg_f14x64/lv_root 7.4G 3.0G 4.4G 41%
+ RHEL6brewx64:/dev/sda1 484.2M 52.6M 406.6M 11%
+ RHEL6brewx64:/dev/vg_rhel6brewx64/lv_root
+ 13.3G 3.4G 9.2G 26%
+ Win7x32:/dev/sda1 100.0M 24.1M 75.9M 25%
+ Win7x32:/dev/sda2 19.9G 7.4G 12.5G 38%
+</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ You can use <code class="command">virt-df</code> safely on live guests, since it only needs read-only access. However, you should not expect the numbers to be precisely the same as those from a <code class="command">df</code> command running inside the guest. This is because what is on disk will be slightly out of synch with the state of the live guest. Nevertheless it should be a good enough approximation for analysis and monitoring purposes.
+ </div></div></div><div class="para">
+ virt-df is designed to allow you to integrate the statistics into monitoring tools, databases and so on. This allows system administrators to generate reports on trends in disk usage, and alerts if a guest is about to run out of disk space. To do this you should use the <code class="command">--csv</code> option to generate machine-readable Comma-Separated-Values (CSV) output. CSV output is readable by most databases, spreadsheet software and a variety of other tools and programming languages. The raw CSV looks like the following:
+ </div><pre class="screen">
+# virt-df --csv WindowsGuest
+ Virtual Machine,Filesystem,1K-blocks,Used,Available,Use%
+ Win7x32,/dev/sda1,102396,24712,77684,24.1%
+ Win7x32,/dev/sda2,20866940,7786652,13080288,37.3%
+</pre><div class="para">
+ For resources and ideas on how to process this output to produce trends and alerts, refer to the following URL: <a href=" http://virt-tools.org/learning/advanced-virt-df/"> http://virt-tools.org/learning/advanced-virt-df/</a>.
+ </div></div></div><div class="section" id="sect-virt-resize"><div class="titlepage"><div><div><h2 class="title">G.8. virt-resize: resizing guests offline</h2></div></div></div><div class="section" id="sect-virt-resize-intro"><div class="titlepage"><div><div><h3 class="title">G.8.1. Introduction</h3></div></div></div><div class="para">
+ This section describes <code class="command">virt-resize</code>, a tool for expanding or shrinking guests. It only works for guests which are offline (shut down). It works by copying the guest image and leaving the original disk image untouched. This is ideal because you can use the original image as a backup, however there is a trade-off as you need twice the amount of disk space.
+ </div></div><div class="section" id="sect-expand-disk-image"><div class="titlepage"><div><div><h3 class="title">G.8.2. Expanding a disk image</h3></div></div></div><div class="para">
+ This section demonstrates a simple case of expanding a disk image:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Locate the disk image to be resized. You can use the command <code class="command">virsh dumpxml GuestName</code> for a libvirt guest.
+ </div></li><li class="listitem"><div class="para">
+ Decide on how you wish to expand the guest. Run <code class="command">virt-df -h</code> and <code class="command">virt-list-partitions -lh</code> on the guest disk, as shown in the following output:
+ </div><pre class="screen">
+# virt-df -h /dev/vg_guests/RHEL6
+Filesystem Size Used Available Use%
+RHEL6:/dev/sda1 98.7M 10.0M 83.6M 11%
+RHEL6:/dev/VolGroup00/LogVol00 6.8G 2.2G 4.3G 32%
+
+# virt-list-partitions -lh /dev/vg_guests/RHEL6
+/dev/sda1 ext3 101.9M
+/dev/sda2 pv 7.9G
+</pre></li></ol></div><div class="para">
+ This example will demonstrate how to:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Increase the size of the first (boot) partition, from approximately 100MB to 500MB.
+ </div></li><li class="listitem"><div class="para">
+ Increase the total disk size from 8GB to 16GB.
+ </div></li><li class="listitem"><div class="para">
+ Expand the second partition to fill the remaining space.
+ </div></li><li class="listitem"><div class="para">
+ Expand <code class="filename">/dev/VolGroup00/LogVol00</code> to fill the new space in the second partition.
+ </div></li></ul></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Make sure the guest is shut down.
+ </div></li><li class="listitem"><div class="para">
+ Rename the original disk as the backup. How you do this depends on the host storage environment for the original disk. If it is stored as a file, use the <code class="command">mv</code> command. For logical volumes (as demonstrated in this example), use <code class="command">lvrename</code>:
+ </div><pre class="screen">
+# lvrename /dev/vg_guests/RHEL6 /dev/vg_guests/RHEL6.backup
+</pre></li><li class="listitem"><div class="para">
+ Create the new disk. The requirements in this example are to expand the total disk size up to 16GB. Since logical volumes are used here, the following command is used:
+ </div><pre class="screen">
+# lvcreate -L 16G -n RHEL6 /dev/vg_guests
+Logical volume "RHEL6" created
+</pre></li><li class="listitem"><div class="para">
+ The requirements from step 2 are expressed by this command:
+ </div><pre class="screen">
+# virt-resize \
+ /dev/vg_guests/RHEL6.backup /dev/vg_guests/RHEL6 \
+ --resize /dev/sda1=500M \
+ --expand /dev/sda2 \
+ --LV-expand /dev/VolGroup00/LogVol00
+</pre><div class="para">
+ The first two arguments are the input disk and output disk. <code class="command">--resize /dev/sda1=500M</code> resizes the first partition up to 500MB. <code class="command">--expand /dev/sda2</code> expands the second partition to fill all remaining space. <code class="command">--LV-expand /dev/VolGroup00/LogVol00</code> expands the guest logical volume to fill the extra space in the second partition.
+ </div><div class="para">
+ <code class="command">virt-resize</code> describes what it is doing in the output:
+ </div><pre class="screen">
+Summary of changes:
+ /dev/sda1: partition will be resized from 101.9M to 500.0M
+ /dev/sda1: content will be expanded using the 'resize2fs' method
+ /dev/sda2: partition will be resized from 7.9G to 15.5G
+ /dev/sda2: content will be expanded using the 'pvresize' method
+ /dev/VolGroup00/LogVol00: LV will be expanded to maximum size
+ /dev/VolGroup00/LogVol00: content will be expanded using the 'resize2fs' method
+ Copying /dev/sda1 ...
+ [#####################################################]
+ Copying /dev/sda2 ...
+ [#####################################################]
+ Expanding /dev/sda1 using the 'resize2fs' method
+ Expanding /dev/sda2 using the 'pvresize' method
+ Expanding /dev/VolGroup00/LogVol00 using the 'resize2fs' method
+</pre></li><li class="listitem"><div class="para">
+ Try to boot the virtual machine. If it works (and after testing it thoroughly) you can delete the backup disk. If it fails, shut down the virtual machine, delete the new disk, and rename the backup disk back to its original name.
+ </div></li><li class="listitem"><div class="para">
+ Use <code class="command">virt-df</code> and/or <code class="command">virt-list-partitions</code> to show the new size:
+ </div><pre class="screen">
+# virt-df -h /dev/vg_pin/RHEL6
+ Filesystem Size Used Available Use%
+ RHEL6:/dev/sda1 484.4M 10.8M 448.6M 3%
+ RHEL6:/dev/VolGroup00/LogVol00 14.3G 2.2G 11.4G 16%
+</pre></li></ol></div><div class="para">
+ Resizing guests is not an exact science. If <code class="command">virt-resize</code> fails, there are a number of tips that you can review and attempt in the virt-resize(1) man page. For some older Red Hat Enterprise Linux guests, you may need to pay particular attention to the tip regarding GRUB.
+ </div></div></div><div class="section" id="sect-virt-inspector"><div class="titlepage"><div><div><h2 class="title">G.9. virt-inspector: inspecting guests</h2></div></div></div><div class="section" id="sect-virt-inspector-intro"><div class="titlepage"><div><div><h3 class="title">G.9.1. Introduction</h3></div></div></div><div class="para">
+ <code class="command">virt-inspector</code> is a tool for inspecting a disk image to find out what operating system it contains.
+ </div></div><div class="section" id="sect-virt-inspector-install"><div class="titlepage"><div><div><h3 class="title">G.9.2. Installation</h3></div></div></div><div class="para">
+ To install virt-inspector and the documentation, enter the following command:
+ </div><pre class="screen">
+# yum install libguestfs-tools libguestfs-devel
+</pre><div class="para">
+ To process Windows guests you must also install <span class="package">libguestfs-winsupport</span>. Refer to <a class="xref" href="#sect-virt-win-reg-install">Section G.10.2, “Installation”</a> for details. The documentation, including example XML output and a Relax-NG schema for the output, will be installed in <code class="filename">/usr/share/doc/libguestfs-devel-*/</code> where "*" is replaced by the version number of libguestfs.
+ </div></div><div class="section" id="sect-virt-inspector-run"><div class="titlepage"><div><div><h3 class="title">G.9.3. Running virt-inspector</h3></div></div></div><div class="para">
+ You can run <code class="command">virt-inspector</code> against any disk image or libvirt guest as shown in the following example:
+ </div><pre class="screen">
+virt-inspector --xml disk.img > report.xml
+</pre><div class="para">
+ Or as shown here:
+ </div><pre class="screen">
+virt-inspector --xml GuestName > report.xml
+</pre><div class="para">
+ The result will be an XML report (<code class="filename">report.xml</code>). The main components of the XML file are a top-level <operatingsytems> element containing usually a single <operatingsystem> element, similar to the following:
+ </div><pre class="screen">
+ <operatingsystems>
+ <operatingsystem>
+
+ <!-- the type of operating system and Linux distribution -->
+ <name>linux</name>
+ <distro>rhel</distro>
+ <!-- the name, version and architecture -->
+ <product_name>Red Hat Enterprise Linux Server release 6.4 </product_name>
+ <major_version>6</major_version>
+ <minor_version>4</minor_version>
+ <package_format>rpm</package_format>
+ <package_management>yum</package_management>
+ <root>/dev/VolGroup/lv_root</root>
+ <!-- how the filesystems would be mounted when live -->
+ <mountpoints>
+ <mountpoint dev="/dev/VolGroup/lv_root">/</mountpoint>
+ <mountpoint dev="/dev/sda1">/boot</mountpoint>
+ <mountpoint dev="/dev/VolGroup/lv_swap">swap</mountpoint>
+ </mountpoints>
+
+ < !-- filesystems-->
+ <filesystem dev="/dev/VolGroup/lv_root">
+ <label></label>
+ <uuid>b24d9161-5613-4ab8-8649-f27a8a8068d3</uuid>
+ <type>ext4</type>
+ <content>linux-root</content>
+ <spec>/dev/mapper/VolGroup-lv_root</spec>
+ </filesystem>
+ <filesystem dev="/dev/VolGroup/lv_swap">
+ <type>swap</type>
+ <spec>/dev/mapper/VolGroup-lv_swap</spec>
+ </filesystem>
+ <!-- packages installed -->
+ <applications>
+ <application>
+ <name>firefox</name>
+ <version>3.5.5</version>
+ <release>1.fc12</release>
+ </application>
+ </applications>
+
+ </operatingsystem>
+ </operatingsystems>
+</pre><div class="para">
+ Processing these reports is best done using W3C standard XPath queries. Fedora comes with a command line program (<code class="command">xpath</code>) which can be used for simple instances; however, for long-term and advanced usage, you should consider using an XPath library along with your favorite programming language.
+ </div><div class="para">
+ As an example, you can list out all file system devices using the following XPath query:
+ </div><pre class="screen">
+virt-inspector --xml GuestName | xpath //filesystem/@dev
+ Found 3 nodes:
+ -- NODE --
+ dev="/dev/sda1"
+ -- NODE --
+ dev="/dev/vg_f12x64/lv_root"
+ -- NODE --
+ dev="/dev/vg_f12x64/lv_swap"
+</pre><div class="para">
+ Or list the names of all applications installed by entering:
+ </div><pre class="screen">
+ virt-inspector --xml GuestName | xpath //application/name
+ [...long list...]
+</pre></div></div><div class="section" id="sect-virt-win-reg"><div class="titlepage"><div><div><h2 class="title">G.10. virt-win-reg: Reading and editing the Windows Registry</h2></div></div></div><div class="section" id="sect-virt-win-reg-intro"><div class="titlepage"><div><div><h3 class="title">G.10.1. Introduction</h3></div></div></div><div class="para">
+ <code class="command">virt-win-reg</code> is a tool that manipulates the Registry in Windows guests. It can be used to read out registry keys. You can also use it to make changes to the Registry, but you must <span class="bold bold"><strong>never</strong></span> try to do this for live/running guests, as it will result in disk corruption.
+ </div></div><div class="section" id="sect-virt-win-reg-install"><div class="titlepage"><div><div><h3 class="title">G.10.2. Installation</h3></div></div></div><div class="para">
+ To use <code class="command">virt-win-reg</code> you must run the following:
+ </div><pre class="screen">
+# yum install libguestfs-tools libguestfs-winsupport
+</pre></div><div class="section" id="sect-virt-win-reg-use"><div class="titlepage"><div><div><h3 class="title">G.10.3. Using virt-win-reg</h3></div></div></div><div class="para">
+ To read out Registry keys, specify the name of the guest (or its disk image) and the name of the Registry key. You must use single quotes to surround the name of the desired key:
+ </div><pre class="screen">
+# virt-win-reg WindowsGuest \
+ 'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall' \
+ | less
+</pre><div class="para">
+ The output is in the standard text-based format used by <code class="filename">.REG</code> files on Windows.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Hex-quoting is used for strings because the format does not properly define a portable encoding method for strings. This is the only way to ensure fidelity when transporting <code class="filename">.REG</code> files from one machine to another.
+ </div><div class="para">
+ You can make hex-quoted strings printable by piping the output of <code class="command">virt-win-reg</code> through this simple Perl script:
+ </div><pre class="screen">perl -MEncode -pe's?hex\((\d+)\):(\S+)?$t=$1;$_=$2;s,\,,,g;"str($t):\"".decode(utf16le=>pack("H*",$_))."\""?eg'
+</pre></div></div><div class="para">
+ To merge changes into the Windows Registry of an offline guest, you must first prepare a <code class="filename">.REG</code> file. There is a great deal of documentation about doing this available from MSDN, and there is a good summary in the following Wikipedia page: <a href="https://secure.wikimedia.org/wikipedia/en/wiki/Windows_Registry#.REG_files">https://secure.wikimedia.org/wikipedia/en/wiki/Windows_Registry#.REG_files</a>. When you have prepared a <code class="filename">.REG</code> file, enter the following:
+ </div><pre class="screen">
+# virt-win-reg --merge WindowsGuest input.reg
+</pre><div class="para">
+ This will update the registry in the guest.
+ </div></div></div><div class="section" id="sect-Using-API-Programming-Languages"><div class="titlepage"><div><div><h2 class="title">G.11. Using the API from Programming Languages</h2></div></div></div><div class="para">
+ The libguestfs API can be used directly from the following languages in Fedora 19: C, C++, Perl, Python, Java, Ruby and OCaml.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ To install C and C++ bindings, enter the following command:
+ </div><pre class="screen">
+# yum install libguestfs-devel
+</pre></li><li class="listitem"><div class="para">
+ To install Perl bindings:
+ </div><pre class="screen">
+# yum install 'perl(Sys::Guestfs)'
+</pre></li><li class="listitem"><div class="para">
+ To install Python bindings:
+ </div><pre class="screen">
+# yum install python-libguestfs
+</pre></li><li class="listitem"><div class="para">
+ To install Java bindings:
+ </div><pre class="screen">
+# yum install libguestfs-java libguestfs-java-devel libguestfs-javadoc
+</pre></li><li class="listitem"><div class="para">
+ To install Ruby bindings:
+ </div><pre class="screen">
+# yum install ruby-libguestfs
+</pre></li><li class="listitem"><div class="para">
+ To install OCaml bindings:
+ </div><pre class="screen">
+# yum install ocaml-libguestfs ocaml-libguestfs-devel
+</pre></li></ul></div><div class="para">
+ The binding for each language is essentially the same, but with minor syntactic changes. A C statement:
+ </div><pre class="screen">
+guestfs_launch (g);
+</pre><div class="para">
+ Would appear like the following in Perl:
+ </div><pre class="screen">
+$g->launch ()
+</pre><div class="para">
+ Or like the following in OCaml:
+ </div><pre class="screen">
+g#launch ()
+</pre><div class="para">
+ Only the API from C is detailed in this section.
+ </div><div class="para">
+ In the C and C++ bindings, you must manually check for errors. In the other bindings, errors are converted into exceptions; the additional error checks shown in the examples below are not necessary for other languages, but conversely you may wish to add code to catch exceptions. Refer to the following list for some points of interest regarding the architecture of the libguestfs API:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The libguestfs API is synchronous. Each call blocks until it has completed. If you want to make calls asynchronously, you have to create a thread.
+ </div></li><li class="listitem"><div class="para">
+ The libguestfs API is not thread safe: each handle should be used only from a single thread, or if you want to share a handle between threads you should implement your own mutex to ensure that two threads cannot execute commands on one handle at the same time.
+ </div></li><li class="listitem"><div class="para">
+ You should not open multiple handles on the same disk image. It is permissible if all the handles are read-only, but still not recommended.
+ </div></li><li class="listitem"><div class="para">
+ You should not add a disk image for writing if anything else could be using that disk image (eg. a live VM). Doing this will cause disk corruption.
+ </div></li><li class="listitem"><div class="para">
+ Opening a read-only handle on a disk image which is currently in use (eg. by a live VM) is possible; however, the results may be unpredictable or inconsistent particularly if the disk image is being heavily written to at the time you are reading it.
+ </div></li></ul></div><div class="section" id="API-and-C"><div class="titlepage"><div><div><h3 class="title">G.11.1. Interaction with the API via a C program</h3></div></div></div><div class="para">
+ Your C program should start by including the <guestfs.h> header file, and creating a handle:
+ </div><pre class="screen">
+#include <stdio.h>
+#include <stdlib.h>
+#include <guestfs.h>
+
+int
+main (int argc, char *argv[])
+{
+ guestfs_h *g;
+
+ g = guestfs_create ();
+ if (g == NULL) {
+ perror ("failed to create libguestfs handle");
+ exit (EXIT_FAILURE);
+ }
+
+ /* ... */
+
+ guestfs_close (g);
+
+ exit (EXIT_SUCCESS);
+ }
+</pre><div class="para">
+ Save this program to a file (<code class="filename">test.c</code>). Compile this program and run it with the following two commands:
+ </div><pre class="screen">
+gcc -Wall test.c -o test -lguestfs
+./test
+</pre><div class="para">
+ At this stage it should print no output. The rest of this section demonstrates an example showing how to extend this program to create a new disk image, partition it, format it with an ext4 file system, and create some files in the file system. The disk image will be called <code class="filename">disk.img</code> and be created in the current directory.
+ </div><div class="para">
+ The outline of the program is:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Create the handle.
+ </div></li><li class="listitem"><div class="para">
+ Add disk(s) to the handle.
+ </div></li><li class="listitem"><div class="para">
+ Launch the libguestfs back end.
+ </div></li><li class="listitem"><div class="para">
+ Create the partition, file system and files.
+ </div></li><li class="listitem"><div class="para">
+ Close the handle and exit.
+ </div></li></ul></div><div class="para">
+ Here is the modified program:
+ </div><pre class="screen">
+#include <stdio.h>
+#include <stdlib.h>
+#include <string.h>
+#include <fcntl.h>
+#include <unistd.h>
+#include <guestfs.h>
+
+ int
+ main (int argc, char *argv[])
+ {
+ guestfs_h *g;
+ size_t i;
+
+ g = guestfs_create ();
+ if (g == NULL) {
+ perror ("failed to create libguestfs handle");
+ exit (EXIT_FAILURE);
+ }
+
+ /* Create a raw-format sparse disk image, 512 MB in size. */
+ int fd = open ("disk.img", O_CREAT|O_WRONLY|O_TRUNC|O_NOCTTY, 0666);
+ if (fd == -1) {
+ perror ("disk.img");
+ exit (EXIT_FAILURE);
+ }
+ if (ftruncate (fd, 512 * 1024 * 1024) == -1) {
+ perror ("disk.img: truncate");
+ exit (EXIT_FAILURE);
+ }
+ if (close (fd) == -1) {
+ perror ("disk.img: close");
+ exit (EXIT_FAILURE);
+ }
+
+ /* Set the trace flag so that we can see each libguestfs call. */
+ guestfs_set_trace (g, 1);
+
+ /* Set the autosync flag so that the disk will be synchronized
+ * automatically when the libguestfs handle is closed.
+ */
+ guestfs_set_autosync (g, 1);
+
+ /* Add the disk image to libguestfs. */
+ if (guestfs_add_drive_opts (g, "disk.img",
+ GUESTFS_ADD_DRIVE_OPTS_FORMAT, "raw", /* raw format */
+ GUESTFS_ADD_DRIVE_OPTS_READONLY, 0, /* for write */
+ -1 /* this marks end of optional arguments */ )
+ == -1)
+ exit (EXIT_FAILURE);
+
+ /* Run the libguestfs back-end. */
+ if (guestfs_launch (g) == -1)
+ exit (EXIT_FAILURE);
+
+ /* Get the list of devices. Because we only added one drive
+ * above, we expect that this list should contain a single
+ * element.
+ */
+ char **devices = guestfs_list_devices (g);
+ if (devices == NULL)
+ exit (EXIT_FAILURE);
+ if (devices[0] == NULL || devices[1] != NULL) {
+ fprintf (stderr,
+ "error: expected a single device from list-devices\n");
+ exit (EXIT_FAILURE);
+ }
+
+ /* Partition the disk as one single MBR partition. */
+ if (guestfs_part_disk (g, devices[0], "mbr") == -1)
+ exit (EXIT_FAILURE);
+
+ /* Get the list of partitions. We expect a single element, which
+ * is the partition we have just created.
+ */
+ char **partitions = guestfs_list_partitions (g);
+ if (partitions == NULL)
+ exit (EXIT_FAILURE);
+ if (partitions[0] == NULL || partitions[1] != NULL) {
+ fprintf (stderr,
+ "error: expected a single partition from list-partitions\n");
+ exit (EXIT_FAILURE);
+ }
+
+ /* Create an ext4 filesystem on the partition. */
+ if (guestfs_mkfs (g, "ext4", partitions[0]) == -1)
+ exit (EXIT_FAILURE);
+
+ /* Now mount the filesystem so that we can add files. */
+ if (guestfs_mount_options (g, "", partitions[0], "/") == -1)
+ exit (EXIT_FAILURE);
+
+ /* Create some files and directories. */
+ if (guestfs_touch (g, "/empty") == -1)
+ exit (EXIT_FAILURE);
+
+ const char *message = "Hello, world\n";
+ if (guestfs_write (g, "/hello", message, strlen (message)) == -1)
+ exit (EXIT_FAILURE);
+
+ if (guestfs_mkdir (g, "/foo") == -1)
+ exit (EXIT_FAILURE);
+
+ /* This uploads the local file /etc/resolv.conf into the disk image. */
+ if (guestfs_upload (g, "/etc/resolv.conf", "/foo/resolv.conf") == -1)
+ exit (EXIT_FAILURE);
+
+ /* Because 'autosync' was set (above) we can just close the handle
+ * and the disk contents will be synchronized. You can also do
+ * this manually by calling guestfs_umount_all and guestfs_sync.
+ */
+ guestfs_close (g);
+
+ /* Free up the lists. */
+ for (i = 0; devices[i] != NULL; ++i)
+ free (devices[i]);
+ free (devices);
+ for (i = 0; partitions[i] != NULL; ++i)
+ free (partitions[i]);
+ free (partitions);
+
+ exit (EXIT_SUCCESS);
+ }
+</pre><div class="para">
+ Compile and run this program with the following two commands:
+ </div><pre class="screen">
+gcc -Wall test.c -o test -lguestfs
+./test
+</pre><div class="para">
+ If the program runs to completion successfully then you should be left with a disk image called <code class="filename">disk.img</code>, which you can examine with guestfish:
+ </div><pre class="screen">
+guestfish --ro -a disk.img -m /dev/sda1
+><fs> ll /
+><fs> cat /foo/resolv.conf
+</pre><div class="para">
+ By default (for C and C++ bindings only), libguestfs prints errors to stderr. You can change this behavior by setting an error handler. The guestfs(3) man page discusses this in detail.
+ </div></div></div><div class="section" id="sect-libguestfs-troubleshoot"><div class="titlepage"><div><div><h2 class="title">G.12. Troubleshooting</h2></div></div></div><div class="para">
+ A test tool is available to check that libguestfs is working. Run the following command after installing libguestfs (root access not required) to test for normal operation:
+ </div><pre class="screen">
+$ libguestfs-test-tool
+</pre><div class="para">
+ This tool prints a large amount of text to test the operation of libguestfs. If the test is successful, the following text will appear near the end of the output:
+ </div><pre class="screen">===== TEST FINISHED OK =====</pre></div><div class="section" id="sect-libguestfs-more-docs"><div class="titlepage"><div><div><h2 class="title">G.13. Where to find further documentation</h2></div></div></div><div class="para">
+ The primary source for documentation for libguestfs and the tools are the Unix man pages. The API is documented in guestfs(3). guestfish is documented in guestfish(1). The virt tools are documented in their own man pages (eg. virt-df(1)).
+ </div></div></div><div xml:lang="en-US" class="appendix" id="chap-Virtualization_Administration_Guide-Virtual_Networking" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Virtual Networking</h1></div></div></div><div class="para">
+ This chapter introduces the concepts needed to create, start, stop, remove, and modify virtual networks with libvirt.
+ </div><div class="para">
+ Additional information can be found in the libvirt reference chapter
+ </div><div class="section" id="sect-virtual_network-switches-livbvirt"><div class="titlepage"><div><div><h2 class="title">H.1. Virtual network switches</h2></div></div></div><div class="para">
+ Libvirt virtual networking uses the concept of a <span class="emphasis"><em>virtual network switch</em></span>. A virtual network switch is a software construct that operates on a host server, to which virtual machines (guests) connect. The network traffic for a guest is directed through this switch:
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-Switch_with_two_guests"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-02-switchandtwoguests.png" alt="Virtual network switch with two guests" /></div></div><h6>Figure H.1. Virtual network switch with two guests</h6></div><br class="figure-break" /><div class="para">
+ Linux host servers represent a virtual network switch as a network interface. When the libvirtd daemon (<code class="command">libvirtd</code>) is first installed and started, the default network interface representing the virtual network switch is <code class="command">virbr0</code>.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-Linux_host_with_switch"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-03-hostwithswitch.png" alt="Linux host with an interface to a virtual network switch" /></div></div><h6>Figure H.2. Linux host with an interface to a virtual network switch</h6></div><br class="figure-break" /><div class="para">
+ This <code class="command">virbr0</code> interface can be viewed with the <code class="command">ifconfig</code> and <code class="command">ip</code> commands like any other interface:
+ </div><pre class="screen">
+$ ifconfig virbr0
+ virbr0 Link encap:Ethernet HWaddr 1B:C4:94:CF:FD:17
+ inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
+ UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
+ RX packets:0 errors:0 dropped:0 overruns:0 frame:0
+ TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
+ collisions:0 txqueuelen:0
+ RX bytes:0 (0.0 b) TX bytes:3097 (3.0 KiB)
+</pre><pre class="screen">
+ $ ip addr show virbr0
+ 3: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
+ link/ether 1b:c4:94:cf:fd:17 brd ff:ff:ff:ff:ff:ff
+ inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
+</pre></div><div class="section" id="sect-Network_Address_Translation-libvirt"><div class="titlepage"><div><div><h2 class="title">H.2. Network Address Translation</h2></div></div></div><div class="para">
+ By default, virtual network switches operate in NAT mode. They use IP masquerading rather than SNAT (Source-NAT) or DNAT (Destination-NAT). IP masquerading enables connected guests to use the host IP address for communication to any external network. By default, computers that are placed externally to the host cannot communicate to the guests inside when the virtual network switch is operating in NAT mode, as shown in the following diagram:
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-Network_Address_Translation-Switch_in_NAT_mode_with_two_guests"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-04-hostwithnatswitch.png" width="444" alt="Virtual network switch using NAT with two guests" /></div></div><h6>Figure H.3. Virtual network switch using NAT with two guests</h6></div><br class="figure-break" /><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Virtual network switches use NAT configured by iptables rules. Editing these rules while the switch is running is not recommended, as incorrect rules may result in the switch being unable to communicate.
+ </div></div></div></div><div class="section" id="sect-network-protocols"><div class="titlepage"><div><div><h2 class="title">H.3. Networking protocols</h2></div></div></div><div class="para">
+ The following sections describe individual networking protocols and how they are used in libvirt
+ </div><div class="section" id="sect-DNS_and_DHCP-protocols-libvirt"><div class="titlepage"><div><div><h3 class="title">H.3.1. DNS and DHCP</h3></div></div></div><div class="para">
+ IP information can be assigned to guests via DHCP. A pool of addresses can be assigned to a virtual network switch for this purpose. Libvirt uses the <code class="command">dnsmasq</code> program for this. An instance of dnsmasq is automatically configured and started by libvirt for each virtual network switch that needs it.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-Network_Address_Translation-Switch_with_DNSDHCP"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-05-switchwithdnsmasq.jpg" width="444" alt="Virtual network switch running dnsmasq" /></div></div><h6>Figure H.4. Virtual network switch running dnsmasq</h6></div><br class="figure-break" /></div><div class="section" id="sub-sect-routed-mode-libvirt"><div class="titlepage"><div><div><h3 class="title">H.3.2. Routed mode</h3></div></div></div><div class="para">
+ When using <span class="emphasis"><em>routed mode</em></span>, the virtual switch connects to the physical LAN connected to the host, passing traffic back and forth without the use of NAT. The virtual switch can examine all traffic and use the information contained within the network packets to make routing decisions. When using this mode, all of the virtual machines are in their own subnet, routed through a virtual switch. This situation is not always ideal as no other hosts on the physical network are aware of the virtual machines without manual physical router configuration, and cannot access the virtual machines. Routed mode operates at Layer 3 of the OSI networking model.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-Other_routing_types-Routed_mode"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-06-routed-switch.png" width="444" alt="Virtual network switch in routed mode" /></div></div><h6>Figure H.5. Virtual network switch in routed mode</h6></div><br class="figure-break" /></div><div class="section" id="sub-sect-iso-mode"><div class="titlepage"><div><div><h3 class="title">H.3.3. Isolated mode</h3></div></div></div><div class="para">
+ When using <span class="emphasis"><em>Isolated mode</em></span>, guests connected to the virtual switch can communicate with each other, and with the host, but their traffic will not pass outside of the host, nor can they receive traffic from outside the host. Using dnsmasq in this mode is required for basic functionality such as DHCP. However, even if this network is isolated from any physical network, DNS names are still resolved. Therefore a situation can arise when DNS names resolve but ICMP echo request (ping) commands fail.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-Other_routing_types-Isolated_mode"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-07-isolated-switch.png" width="444" alt="Virtual network switch in isolated mode" /></div></div><h6>Figure H.6. Virtual network switch in isolated mode</h6></div><br class="figure-break" /></div></div><div class="section" id="sect-the-Default_Configuration-libvirt"><div class="titlepage"><div><div><h2 class="title">H.4. The default configuration</h2></div></div></div><div class="para">
+ When the libvirtd daemon (<code class="command">libvirtd</code>) is first installed, it contains an initial virtual network switch configuration in NAT mode. This configuration is used so that installed guests can communicate to the external network, through the host. The following image demonstrates this default configuration for <code class="systemitem">libvirtd</code>:
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-the_default_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-08-network-overview.png" width="444" alt="Default libvirt network configuration" /></div></div><h6>Figure H.7. Default libvirt network configuration</h6></div><br class="figure-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ A virtual network can be restricted to a specific physical interface. This may be useful on a physical system that has several interfaces (for example, <code class="filename">eth0</code>, <code class="filename">eth1</code> and <code class="filename">eth2</code>). This is only useful in routed and NAT modes, and can be defined in the <code class="command">dev=<interface></code> option, or in <code class="command">virt-manager</code> when creating a new virtual network.
+ </div></div></div></div><div class="section" id="sect-Virtualization-Virtual_Networking-Example_scenarios"><div class="titlepage"><div><div><h2 class="title">H.5. Examples of common scenarios</h2></div></div></div><div class="para">
+ This section demonstrates different virtual networking modes and provides some example scenarios.
+ </div><div class="section" id="sub-sect-routed-mode"><div class="titlepage"><div><div><h3 class="title">H.5.1. Routed mode</h3></div></div></div><div class="formalpara"><h5 class="formalpara" id="idm105295504">DMZ</h5>
+ Consider a network where one or more nodes are placed in a controlled subnetwork for security reasons. The deployment of a special subnetwork such as this is a common practice, and the subnetwork is known as a DMZ. Refer to the following diagram for more details on this layout:
+ </div><div class="figure" id="dmz-example-diagram"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-09-routed-mode-DMZ.png" width="444" alt="Sample DMZ configuration" /></div></div><h6>Figure H.8. Sample DMZ configuration</h6></div><br class="figure-break" /><div class="para">
+ Hosts in a DMZ typically provide services to WAN (external) hosts as well as LAN (internal) hosts. As this requires them to be accessible from multiple locations, and considering that these locations are controlled and operated in different ways based on their security and trust level, routed mode is the best configuration for this environment.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm89641040">Virtual Server hosting</h5>
+ Consider a virtual server hosting company that has several hosts, each with two physical network connections. One interface is used for management and accounting, the other is for the virtual machines to connect through. Each guest has its own public IP address, but the hosts use private IP address as management of the guests can only be performed by internal administrators. Refer to the following diagram to understand this scenario:
+ </div><div class="figure" id="virt-serv-host-diagram"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-10-routed-mode-datacenter.png" width="444" alt="Virtual server hosting sample configuration" /></div></div><h6>Figure H.9. Virtual server hosting sample configuration</h6></div><br class="figure-break" /><div class="para">
+ When the host has a public IP address and the virtual machines have static public IP addresses, bridged networking cannot be used, as the provider only accepts packets from the MAC address of the public host. The following diagram demonstrates this:
+ </div><div class="figure" id="static-ip-diagram"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-11-router-mode-mac-restricted.png" width="444" alt="Virtual server using static IP addresses" /></div></div><h6>Figure H.10. Virtual server using static IP addresses</h6></div><br class="figure-break" /></div><div class="section" id="sub-sect-nat-mode"><div class="titlepage"><div><div><h3 class="title">H.5.2. NAT mode</h3></div></div></div><div class="para">
+ NAT (Network Address Translation) mode is the default mode. It can be used for testing when there is no need for direct network visibility.
+ </div></div><div class="section" id="sub-sect-isolated-mode"><div class="titlepage"><div><div><h3 class="title">H.5.3. Isolated mode</h3></div></div></div><div class="para">
+ Isolated mode allows virtual machines to communicate with each other only. They are unable to interact with the physical network.
+ </div></div></div><div class="section" id="sect-Virtualization-Virtual_Networking-Managing_a_virtual_network"><div class="titlepage"><div><div><h2 class="title">H.6. 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 class="step"><div class="para">
+ From the <span class="guilabel"><strong>Edit</strong></span> menu, select <span class="guilabel"><strong>Connection Details</strong></span>.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Selecting_a_hosts_details"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_vnet_menuselect.png" width="444" alt="Selecting a host's details" /></div></div><h6>Figure H.11. Selecting a host's details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ This will open the <span class="guimenu"><strong>Connection Details</strong></span> menu. Click the <span class="guilabel"><strong>Virtual Networks</strong></span> tab.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic1.png" width="444" alt="Virtual network configuration" /></div></div><h6>Figure H.12. Virtual network configuration</h6></div><br class="figure-break" /></li><li class="step"><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><div class="section" id="sect-Virtualization-Virtual_Networking-Creating_a_virtual_network"><div class="titlepage"><div><div><h2 class="title">H.7. 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 class="step"><div class="para">
+ Open the <span class="guilabel"><strong>Virtual Networks</strong></span> tab from within the <span class="guilabel"><strong>Connection Details</strong></span> menu. Click the <span class="guibutton"><strong>Add Network</strong></span> button, identified by a plus sign (+) icon. For more information, refer to <a class="xref" href="#sect-Virtualization-Virtual_Networking-Managing_a_virtual_network">Section H.6, “Managing a virtual network”</a>.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Virtual_network_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic1.png" width="444" alt="Virtual network configuration" /></div></div><h6>Figure H.13. 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> window. Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Creating_a_new_virtual_network"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic2.png" width="444" alt="Creating a new virtual network" /></div></div><h6>Figure H.14. Creating a new virtual network</h6></div><br class="figure-break" /></li><li class="step"><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_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Naming_your_virtual_network"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic3.png" width="444" alt="Naming your virtual network" /></div></div><h6>Figure H.15. Naming your virtual network</h6></div><br class="figure-break" /></li><li class="step"><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_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Choosing_an_IPv4_address_space"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic4.png" width="444" alt="Choosing an IPv4 address space" /></div></div><h6>Figure H.16. Choosing an IPv4 address space</h6></div><br class="figure-break" /></li><li class="step"><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_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Selecting_the_DHCP_range"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic5.png" width="444" alt="Selecting the DHCP range" /></div></div><h6>Figure H.17. Selecting the DHCP range</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Select how the virtual network should connect to the physical network.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Connecting_to_physical_network"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic6.png" width="444" alt="Connecting to physical network" /></div></div><h6>Figure H.18. 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>Any physical device</strong></span> or a specific physical device. Also select whether the <span class="guilabel"><strong>Mode</strong></span> should be <span class="guilabel"><strong>NAT</strong></span> or <span class="guilabel"><strong>Routed</strong></span>.
+ </div><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><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_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Ready_to_create_network"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic7.png" width="444" alt="Ready to create network" /></div></div><h6>Figure H.19. Ready to create network</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ The new virtual network is now available in the <span class="guilabel"><strong>Virtual Networks</strong></span> tab of the <span class="guilabel"><strong>Connection Details</strong></span> window.
+ </div></li></ol></div></div><div class="section" id="sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest"><div class="titlepage"><div><div><h2 class="title">H.8. Attaching a virtual network to a guest</h2></div></div></div><div class="para">
+ To attach a virtual network to a guest:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ In the <span class="guilabel"><strong>Virtual Machine Manager</strong></span> window, highlight the guest that will have the network assigned.
+ </div><div class="figure" id="guest4network"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt1.png" width="444" alt="Selecting a virtual machine to display" /></div></div><h6>Figure H.20. Selecting a virtual machine to display</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ From the Virtual Machine Manager <span class="guilabel"><strong>Edit</strong></span> menu, select <span class="guilabel"><strong>Virtual Machine Details</strong></span>.
+ </div><div class="figure" id="showdetails"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt11.png" width="444" alt="Displaying the virtual machine details" /></div></div><h6>Figure H.21. Displaying the virtual machine details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Click the <span class="guilabel"><strong>Add Hardware</strong></span> button on the Virtual Machine Details window.
+ </div><div class="figure" id="vmdetailswindow"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt4.png" width="444" alt="The Virtual Machine Details window" /></div></div><h6>Figure H.22. The Virtual Machine Details window</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ In the <span class="guilabel"><strong>Add new virtual hardware</strong></span> window, select <span class="guilabel"><strong>Network</strong></span> from the left pane, and select your network name (<span class="emphasis"><em>network1</em></span> in this example) from the <span class="guilabel"><strong>Host device</strong></span> menu and click <span class="guibutton"><strong>Finish</strong></span>.
+ </div><div class="figure" id="select_network"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic10.png" width="444" alt="Select your network from the Add new virtual hardware window" /></div></div><h6>Figure H.23. Select your network from the Add new virtual hardware window</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ The new network is now displayed as a virtual network interface that will be presented to the guest upon launch.
+ </div><div class="figure" id="newnetworkishown"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic11.png" width="444" alt="New network shown in guest hardware list" /></div></div><h6>Figure H.24. New network shown in guest hardware list</h6></div><br class="figure-break" /></li></ol></div></div><div class="section" id="sect-attch-nic-physdev"><div class="titlepage"><div><div><h2 class="title">H.9. Directly attaching to physical interface</h2></div></div></div><div class="para">
+ The instructions provided in this chapter will assist in the direct attachment of the virtual machine's NIC to the given physical interface of the host. This setup requires the Linux macvtap driver to be available. There are four modes that you can choose for the operation mode of the macvtap device, with 'vepa' being the default mode. Their behavior is as follows:
+ </div><div class="variablelist"><h6>Physical interface delivery modes</h6><dl class="variablelist"><dt class="varlistentry"><span class="term">vepa</span></dt><dd><div class="para">
+ All VMs' packets are sent to the external bridge. Packets whose destination is a VM on the same host as where the packet originates from are sent back to the host by the VEPA capable bridge (today's bridges are typically not VEPA capable).
+ </div></dd><dt class="varlistentry"><span class="term">bridge</span></dt><dd><div class="para">
+ Packets whose destination is on the same host as where they originate from are directly delivered to the target macvtap device. Both origin and destination devices need to be in bridge mode for direct delivery. If either one of them is in vepa mode, a VEPA capable bridge is required.
+ </div></dd><dt class="varlistentry"><span class="term">private</span></dt><dd><div class="para">
+ All packets are sent to the external bridge and will only be delivered to a target VM on the same host if they are sent through an external router or gateway and that device sends them back to the host. This procedure is followed if either the source or destination device is in private mode.
+ </div></dd><dt class="varlistentry"><span class="term">passthrough</span></dt><dd><div class="para">
+ This feature attaches a virtual function of a SRIOV capable NIC directly to a VM without losing the migration capability. All packets are sent to the VF/IF of the configured network device. Depending on the capabilities of the device additional prerequisites or limitations may apply; for example, on Linux this requires kernel 2.6.38 or newer.
+ </div></dd></dl></div><div class="para">
+ Each of the four modes is configured by changing the domain xml file. Once this file is opened, change the mode setting as shown:
+ </div><pre class="screen">
+ <devices>
+ ...
+ <interface type='direct'>
+ <source dev='eth0' mode='vepa'/>
+ </interface>
+ </devices>
+</pre><div class="para">
+ The network access of direct attached guest virtual machines can be managed by the hardware switch to which the physical interface of the host machine is connected to.
+ </div><div class="para">
+ The interface can have additional parameters as shown below, if the switch is conforming to the IEEE 802.1Qbg standard. The parameters of the virtualport element are documented in more detail in the IEEE 802.1Qbg standard. The values are network specific and should be provided by the network administrator. In 802.1Qbg terms, the Virtual Station Interface (VSI) represents the virtual interface of a virtual machine.
+ </div><div class="para">
+ Note that IEEE 802.1Qbg requires a non-zero value for the VLAN ID. Also if the switch is conforming to the IEEE 802.1Qbh standard, the values are network specific and should be provided by the network administrator.
+ </div><div class="variablelist"><h6>Virtual Station Interface types</h6><dl class="variablelist"><dt class="varlistentry"><span class="term">managerid</span></dt><dd><div class="para">
+ The VSI Manager ID identifies the database containing the VSI type and instance definitions. This is an integer value and the value 0 is reserved.
+ </div></dd><dt class="varlistentry"><span class="term">typeid</span></dt><dd><div class="para">
+ The VSI Type ID identifies a VSI type characterizing the network access. VSI types are typically managed by network administrator. This is an integer value.
+ </div></dd><dt class="varlistentry"><span class="term">typeidversion</span></dt><dd><div class="para">
+ The VSI Type Version allows multiple versions of a VSI Type. This is an integer value.
+ </div></dd><dt class="varlistentry"><span class="term">instanceid</span></dt><dd><div class="para">
+ The VSI Instance ID Identifier is generated when a VSI instance (i.e. a virtual interface of a virtual machine) is created. This is a globally unique identifier.
+ </div></dd><dt class="varlistentry"><span class="term">profileid</span></dt><dd><div class="para">
+ The profile ID contains the name of the port profile that is to be applied onto this interface. This name is resolved by the port profile database into the network parameters from the port profile, and those network parameters will be applied to this interface.
+ </div></dd></dl></div><div class="para">
+ Each of the four types is configured by changing the domain xml file. Once this file is opened, change the mode setting as shown:
+ </div><pre class="screen">
+ <devices>
+ ...
+ <interface type='direct'>
+ <source dev='eth0.2' mode='vepa'/>
+ <virtualport type="802.1Qbg">
+ <parameters managerid="11" typeid="1193047" typeidversion="2" instanceid="09b11c53-8b5c-4eeb-8f00-d84eaa0aaa4f"/>
+ </virtualport>
+ </interface>
+ </devices>
+</pre><div class="para">
+ The profile ID is shown here:
+ </div><pre class="screen">
+ <devices>
+ ...
+ <interface type='direct'>
+ <source dev='eth0' mode='private'/>
+ <virtualport type='802.1Qbh'>
+ <parameters profileid='finance'/>
+ </virtualport>
+ </interface>
+ </devices>
+ ...
+</pre></div><div class="section" id="sect-applying-network-filtering"><div class="titlepage"><div><div><h2 class="title">H.10. Applying network filtering</h2></div></div></div><div class="para">
+ This section provides an introduction to libvirt's network filters, their goals, concepts and XML format.
+ </div><div class="section" id="intro-sub-sect-applying-network-filtering"><div class="titlepage"><div><div><h3 class="title">H.10.1. Introduction</h3></div></div></div><div class="para">
+ The goal of the network filtering, is to enable administrators of a virtualized system to configure and enforce network traffic filtering rules on virtual machines and manage the parameters of network traffic that virtual machines are allowed to send or receive. The network traffic filtering rules are applied on the host when a virtual machine is started. Since the filtering rules cannot be circumvented from within the virtual machine, it makes them mandatory from the point of view of a virtual machine user.
+ </div><div class="para">
+ From the point of view of the guest, the network filtering system allows each virtual machine's network traffic filtering rules to be configured individually on a per interface basis. These rules are applied on the host when the virtual machine is started and can be modified while the virtual machine is running. The latter can be achieved by modifying the XML description of a network filter.
+ </div><div class="para">
+ Multiple virtual machines can make use of the same generic network filter. When such a filter is modified, the network traffic filtering rules of all running virtual machines that reference this filter are updated. The machines that are not running will update on start.
+ </div><div class="para">
+ As previously mentioned, applying network traffic filtering rules can be done on individual network interfaces that are configured for certain types of network configurations. Supported network types include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ network
+ </div></li><li class="listitem"><div class="para">
+ ethernet -- must be used in bridging mode
+ </div></li><li class="listitem"><div class="para">
+ bridge
+ </div></li></ul></div><div class="example" id="ex-net-filtering"><h6>Example H.1. An example of network filtering</h6><div class="example-contents"><div class="para">
+ The interface XML is used to reference a top-level filter. In the following example, the interface description references the filter clean-traffic.
+ </div><pre class="screen">
+ <devices>
+ <interface type='bridge'>
+ <mac address='00:16:3e:5d:c7:9e'/>
+ <filterref filter='clean-traffic'/>
+ </interface>
+ </devices>
+</pre><div class="para">
+ Network filters are written in XML and may either contain: references to other filters, rules for traffic filtering, or hold a combination of both. The above referenced filter clean-traffic is a filter that only contains references to other filters and no actual filtering rules. Since references to other filters can be used, a tree of filters can be built. The clean-traffic filter can be viewed using the command: <code class="command"># virsh nwfilter-dumpxml clean-traffic</code>.
+ </div><div class="para">
+ As previously mentioned, a single network filter can be referenced by multiple virtual machines. Since interfaces will typically have individual parameters associated with their respective traffic filtering rules, the rules described in a filter's XML can be generalized using variables. In this case, the variable name is used in the filter XML and the name and value are provided at the place where the filter is referenced.
+ </div></div></div><br class="example-break" /><div class="example"><h6>Example H.2. Description extended</h6><div class="example-contents"><div class="para">
+ In the following example, the interface description has been extended with the parameter IP and a dotted IP address as a value.
+ </div><pre class="screen">
+ <devices>
+ <interface type='bridge'>
+ <mac address='00:16:3e:5d:c7:9e'/>
+ <filterref filter='clean-traffic'>
+ <parameter name='IP' value='10.0.0.1'/>
+ </filterref>
+ </interface>
+ </devices>
+</pre><div class="para">
+ In this particular example, the clean-traffic network traffic filter will be represented with the IP address parameter 10.0.0.1 and as per the rule dictates that all traffic from this interface will always be using 10.0.0.1 as the source IP address, which is one of the purpose of this particular filter.
+ </div></div></div><br class="example-break" /></div><div class="section" id="sub-sect-filt-chain"><div class="titlepage"><div><div><h3 class="title">H.10.2. Filtering chains</h3></div></div></div><div class="para">
+ Filtering rules are organized in filter chains. These chains can be thought of as having a tree structure with packet filtering rules as entries in individual chains (branches).
+ </div><div class="para">
+ Packets start their filter evaluation in the root chain and can then continue their evaluation in other chains, return from those chains back into the root chain or be dropped or accepted by a filtering rule in one of the traversed chains.
+ </div><div class="para">
+ Libvirt's network filtering system automatically creates individual root chains for every virtual machine's network interface on which the user chooses to activate traffic filtering. The user may write filtering rules that are either directly instantiated in the root chain or may create protocol-specific filtering chains for efficient evaluation of protocol-specific rules.
+ </div><div class="para">
+ The following chains exist:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ root
+ </div></li><li class="listitem"><div class="para">
+ mac
+ </div></li><li class="listitem"><div class="para">
+ stp (spanning tree protocol)
+ </div></li><li class="listitem"><div class="para">
+ vlan
+ </div></li><li class="listitem"><div class="para">
+ arp and rarp
+ </div></li><li class="listitem"><div class="para">
+ ipv4
+ </div></li><li class="listitem"><div class="para">
+ ipv6
+ </div></li></ul></div><div class="para">
+ Multiple chains evaluating the mac, stp, vlan, arp, rarp, ipv4, or ipv6 protocol can be created using the protocol name only as a prefix in the chain's name.
+ </div><div class="example" id="arp-pro-example"><h6>Example H.3. ARP traffic filtering</h6><div class="example-contents"><div class="para">
+ This example allows chains with names arp-xyz or arp-test to be specified and have their ARP protocol packets evaluated in those chains.
+ </div><div class="para">
+ The following filter XML shows an example of filtering ARP traffic in the arp chain.
+ </div><pre class="screen">
+<filter name='no-arp-spoofing' chain='arp' priority='-500'>
+ <uuid>f88f1932-debf-4aa1-9fbe-f10d3aa4bc95</uuid>
+ <rule action='drop' direction='out' priority='300'>
+ <mac match='no' srcmacaddr='$MAC'/>
+ </rule>
+ <rule action='drop' direction='out' priority='350'>
+ <arp match='no' arpsrcmacaddr='$MAC'/>
+ </rule>
+ <rule action='drop' direction='out' priority='400'>
+ <arp match='no' arpsrcipaddr='$IP'/>
+ </rule>
+ <rule action='drop' direction='in' priority='450'>
+ <arp opcode='Reply'/>
+ <arp match='no' arpdstmacaddr='$MAC'/>
+ </rule>
+ <rule action='drop' direction='in' priority='500'>
+ <arp match='no' arpdstipaddr='$IP'/>
+ </rule>
+ <rule action='accept' direction='inout' priority='600'>
+ <arp opcode='Request'/>
+ </rule>
+ <rule action='accept' direction='inout' priority='650'>
+ <arp opcode='Reply'/>
+ </rule>
+ <rule action='drop' direction='inout' priority='1000'/>
+</filter>
+</pre><div class="para">
+ The consequence of putting ARP-specific rules in the arp chain, rather than for example in the root chain, is that packets protocols other than ARP do not need to be evaluated by ARP protocol-specific rules. This improves the efficiency of the traffic filtering. However, one must then pay attention to only putting filtering rules for the given protocol into the chain since other rules will not be evaluated. For example, an IPv4 rule will not be evaluated in the ARP chain since IPv4 protocol packets will not traverse the ARP chain.
+ </div></div></div><br class="example-break" /></div><div class="section" id="sub-sect-filt-chain-props"><div class="titlepage"><div><div><h3 class="title">H.10.3. Filtering chain priorities</h3></div></div></div><div class="para">
+ As previously mentioned, when creating a filtering rule, all chains are connected to the root chain. The order in which those chains are accessed is influenced by the priority of the chain. The following table shows the chains that can be assigned a priority and their default priorities.
+ </div><div class="table" id="tab-filtering-chain-priorities"><h6>Table H.1. Filtering chain default priorities values</h6><div class="table-contents"><table summary="Filtering chain default priorities values" border="1"><colgroup><col class="1" width="50%" /><col class="2" width="50%" /></colgroup><thead><tr><th class="">
+ Chain (prefix)
+ </th><th class="">
+ Default priority
+ </th></tr></thead><tbody><tr><td class="">
+ stp
+ </td><td class="">
+ -810
+ </td></tr><tr><td class="">
+ mac
+ </td><td class="">
+ -800
+ </td></tr><tr><td class="">
+ vlan
+ </td><td class="">
+ -750
+ </td></tr><tr><td class="">
+ ipv4
+ </td><td class="">
+ -700
+ </td></tr><tr><td class="">
+ ipv6
+ </td><td class="">
+ -600
+ </td></tr><tr><td class="">
+ arp
+ </td><td class="">
+ -500
+ </td></tr><tr><td class="">
+ rarp
+ </td><td class="">
+ -400
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ A chain with a lower priority value is accessed before one with a higher value.
+ </div><div class="para">
+ The chains listed in <a class="xref" href="#tab-filtering-chain-priorities">Table H.1, “Filtering chain default priorities values”</a> can be also be assigned custom priorities by writing a value in the range [-1000 to 1000] into the priority (XML) attribute in the filter node. <a class="xref" href="#sub-sect-filt-chain">Section H.10.2, “Filtering chains”</a>filter shows the default priority of -500 for arp chains, for example.
+ </div></div></div></div><div class="section" id="sub-sect-vars-in-filters"><div class="titlepage"><div><div><h3 class="title">H.10.4. Usage of variables in filters</h3></div></div></div><div class="para">
+ There are two variables that have been reserved for usage by the network traffic filtering subsystem: MAC and IP.
+ </div><div class="para">
+ <em class="parameter"><code>MAC</code></em> is designated for the MAC address of the network interface. A filtering rule that references this variable will automatically be replaced with the MAC address of the interface. This works without the user having to explicitly provide the MAC parameter. Even though it is possible to specify the MAC parameter similar to the IP parameter above, it is discouraged since libvirt knows what MAC address an interface will be using.
+ </div><div class="para">
+ The parameter <em class="parameter"><code>IP</code></em> represents the IP address that the operating system inside the virtual machine is expected to use on the given interface. The IP parameter is special in so far as the libvirt daemon will try to determine the IP address (and thus the IP parameter's value) that is being used on an interface if the parameter is not explicitly provided but referenced. For current limitations on IP address detection, consult the section on limitations <a class="xref" href="#sub-sect-limitations-filters-network-subsystem">Section H.10.12, “Limitations”</a> on how to use this feature and what to expect when using it. The XML file shown in <a class="xref" href="#sub-sect-filt-chain">Section H.10.2, “Filtering chains”</a> contains the filter <em class="parameter"><code>no-arp-spoofing</code></em>, which is an example of using a network filter XML to reference the MAC and IP variables.
+ </div><div class="para">
+ Note that referenced variables are always prefixed with the character <em class="parameter"><code>$</code></em>. The format of the value of a variable must be of the type expected by the filter attribute identified in the XML. In the above example, the <em class="parameter"><code>IP</code></em> parameter must hold a legal IP address in standard format. Failure to provide the correct structure will result in the filter variable not being replaced with a value and will prevent a virtual machine from starting or will prevent an interface from attaching when hotplugging is being used. Some of the types that are expected for each XML attribute are shown in the example <a class="xref" href="#example-vars-xml-iptraffic-filter">Example H.4, “Sample variable types”</a>.
+ </div><div class="example" id="example-vars-xml-iptraffic-filter"><h6>Example H.4. Sample variable types</h6><div class="example-contents"><div class="para">
+ As variables can contain lists of elements, (the variable IP can contain multiple IP addresses that are valid on a particular interface, for example), the notation for providing multiple elements for the IP variable is:
+ </div><pre class="screen">
+ <devices>
+ <interface type='bridge'>
+ <mac address='00:16:3e:5d:c7:9e'/>
+ <filterref filter='clean-traffic'>
+ <parameter name='IP' value='10.0.0.1'/>
+ <parameter name='IP' value='10.0.0.2'/>
+ <parameter name='IP' value='10.0.0.3'/>
+ </filterref>
+ </interface>
+ </devices>
+</pre><div class="para">
+ This XML file creates filters to enable multiple IP addresses per interface. Each of the IP addresses will result in a seperate filtering rule. Therefore using the XML above and the the following rule, three individual filtering rules (one for each IP address) will be created:
+ </div><pre class="screen">
+ <rule action='accept' direction='in' priority='500'>
+ <tcp srpipaddr='$IP'/>
+ </rule>
+</pre><div class="para">
+ As it is possible to access individual elements of a variable holding a list of elements, a filtering rule like the following accesses the 2nd element of the variable <em class="replaceable"><code>DSTPORTS</code></em>.
+ </div><pre class="screen">
+ <rule action='accept' direction='in' priority='500'>
+ <udp dstportstart='$DSTPORTS[1]'/>
+ </rule>
+</pre></div></div><br class="example-break" /><div class="example" id="exam-fil-rules-combo"><h6>Example H.5. Using a variety of variables</h6><div class="example-contents"><div class="para">
+ As it is possible to create filtering rules that represent all possible combinations of rules from different lists using the notation <code class="command">$VARIABLE[@<iterator id="x">]</code>. The following rule allows a virtual machine to receive traffic on a set of ports, which are specified in <em class="replaceable"><code>DSTPORTS</code></em>, from the set of source IP address specified in <em class="replaceable"><code>SRCIPADDRESSES</code></em>. The rule generates all combinations of elements of the variable <em class="replaceable"><code>DSTPORTS</code></em> with those of <em class="replaceable"><code>SRCIPADDRESSES</code></em> by using two independent iterators to access their elements.
+ </div><pre class="screen">
+ <rule action='accept' direction='in' priority='500'>
+ <ip srcipaddr='$SRCIPADDRESSES[@1]' dstportstart='$DSTPORTS[@2]'/>
+ </rule>
+</pre><div class="para">
+ Assign concrete values to <em class="replaceable"><code>SRCIPADDRESSES</code></em> and <em class="replaceable"><code>DSTPORTS</code></em> as shown:
+ </div><pre class="screen">
+ SRCIPADDRESSES = [ 10.0.0.1, 11.1.2.3 ]
+ DSTPORTS = [ 80, 8080 ]
+</pre><div class="para">
+ Assigning values to the variables using <code class="command">$SRCIPADDRESSES[@1]</code> and <code class="command">$DSTPORTS[@2]</code> would then result in all combinations of addresses and ports being created as shown:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ 10.0.0.1, 80
+ </div></li><li class="listitem"><div class="para">
+ 10.0.0.1, 8080
+ </div></li><li class="listitem"><div class="para">
+ 11.1.2.3, 80
+ </div></li><li class="listitem"><div class="para">
+ 11.1.2.3, 8080
+ </div></li></ul></div><div class="para">
+ Accessing the same variables using a single iterator, for example by using the notation <code class="command">$SRCIPADDRESSES[@1]</code> and <code class="command">$DSTPORTS[@1]</code>, would result in parallel access to both lists and result in the following combinations:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ 10.0.0.1, 80
+ </div></li><li class="listitem"><div class="para">
+ 11.1.2.3, 8080
+ </div></li></ul></div></div></div><br class="example-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ <code class="command">$VARIABLE</code> is short-hand for <code class="command">$VARIABLE[@0]</code>. The former notation always assumes the role of iterator with <code class="command">iterator id="0"</code> added as shown in the opening paragraph at the top of this section.
+ </div></div></div></div><div class="section" id="sub-sect-auto-IP-add-detect-dhcp-snoop"><div class="titlepage"><div><div><h3 class="title">H.10.5. Automatic IP address detection and DHCP snooping</h3></div></div></div><div class="section" id="sub-sub-sect-intro-dhcp-snoop"><div class="titlepage"><div><div><h4 class="title">H.10.5.1. Introduction</h4></div></div></div><div class="para">
+ The detection of IP addresses used on a virtual machine's interface is automatically activated if the variable IP is referenced but no value has been assigned to it. The variable <em class="parameter"><code>CTRL_IP_LEARNING</code></em> can be used to specify the IP address learning method to use. Valid values include: <em class="replaceable"><code>any</code></em>, <em class="replaceable"><code>dhcp</code></em>, or <em class="replaceable"><code>none</code></em>.
+ </div><div class="para">
+ The value <em class="replaceable"><code>any</code></em> instructs libvirt to use any packet to determine the address in use by a virtual machine, which is the default setting if the variable <em class="parameter"><code>TRL_IP_LEARNING</code></em> is not set. This method will only detect a single IP address per interface. Once a guest's IP address has been detected, its IP network traffic will be locked to that address, if for example, IP address spoofing is prevented by one of its filters. In that case, the user of the VM will not be able to change the IP address on the interface inside the guest, which would be considered IP address spoofing. When a guest is migrated to another host or resumed after a suspend operation, the first packet sent by the guest will again determine the IP address that the guest can use on a particular interface.
+ </div><div class="para">
+ The value of <em class="replaceable"><code>dhcp</code></em> instucts libvirt to only honor DHCP server-assigned addresses with valid leases. This method supports the detection and usage of multiple IP address per interface. When a guest resumes after a suspend operation, any valid IP address leases are applied to its filters. Otherwise the guest is expected to use DHCP to obtain a new IP addresses. When a guest migrates to another physical host, the guest is required to re-run the DHCP protocol.
+ </div><div class="para">
+ If CTRL_IP_LEARNING is set to <em class="replaceable"><code>none</code></em>, libvirt does not do IP address learning and referencing IP without assigning it an explicit value is an error.
+ </div></div><div class="section" id="sub-sub-sect-DHCP-snooping"><div class="titlepage"><div><div><h4 class="title">H.10.5.2. DHCP snooping</h4></div></div></div><div class="para">
+ <code class="command">CTRL_IP_LEARNING=<em class="replaceable"><code>dhcp</code></em></code> (DHCP snooping) provides additional anti-spoofing security, especially when combined with a filter allowing only trusted DHCP servers to assign IP addresses. To enable this, set the variable <em class="parameter"><code>DHCPSERVER</code></em> to the IP address of a valid DHCP server and provide filters that use this variable to filter incoming DHCP responses.
+ </div><div class="para">
+ When DHCP snooping is enabled and the DHCP lease expires, the guest will no longer be able to use the IP address until it acquires a new, valid lease from a DHCP server. If the guest is migrated, it must get a new valid DHCP lease to use an IP address (e.g., by bringing the VM interface down and up again).
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Automatic DHCP detection listens to the DHCP traffic the guest exchanges with the DHCP server of the infrastructure. To avoid denial-of-service attacks on libvirt, the evaluation of those packets is rate-limited, meaning that a guest sending an excessive number of DHCP packets per second on an interface will not have all of those packets evaluated and thus filters may not get adapted. Normal DHCP client behavior is assumed to send a low number of DHCP packets per second. Further, it is important to setup appropriate filters on all guests in the infrastructure to avoid them being able to send DHCP packets. Therefore guests must either be prevented from sending UDP and TCP traffic from port 67 to port 68 or the DHCPSERVER variable should be used on all guests to restrict DHCP server messages to only be allowed to originate from trusted DHCP servers. At the same time anti-spoofing prevention must be enabled on all guests in the subnet.
+ </div></div></div><div class="example" id="exam-dhcp-snoop"><h6>Example H.6. Activating IPs for DHCP snooping</h6><div class="example-contents"><div class="para">
+ The following XML provides an example for the activation of IP address learning using the DHCP snooping method:
+ </div><pre class="screen">
+ <interface type='bridge'>
+ <source bridge='virbr0'/>
+ <filterref filter='clean-traffic'>
+ <parameter name='CTRL_IP_LEARNING' value='dhcp'/>
+ </filterref>
+ </interface>
+</pre></div></div><br class="example-break" /></div></div><div class="section" id="sub-sect-vars-reserved"><div class="titlepage"><div><div><h3 class="title">H.10.6. Reserved Variables</h3></div></div></div><div class="para">
+ <a class="xref" href="#table-res-vars">Table H.2, “Reserved variables”</a> shows the variables that are considered reserved and are used by libvirt:
+ </div><div class="table" id="table-res-vars"><h6>Table H.2. Reserved variables</h6><div class="table-contents"><table summary="Reserved variables" border="1"><colgroup><col class="1" width="50%" /><col class="2" width="50%" /></colgroup><thead><tr><th class="">
+ Variable Name
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ MAC
+ </td><td class="">
+ The MAC address of the interface
+ </td></tr><tr><td class="">
+ IP
+ </td><td class="">
+ The list of IP addresses in use by an interface
+ </td></tr><tr><td class="">
+ IPV6
+ </td><td class="">
+ Not currently implemented: the list of IPV6 addresses in use by an interface
+ </td></tr><tr><td class="">
+ DHCPSERVER
+ </td><td class="">
+ The list of IP addresses of trusted DHCP servers
+ </td></tr><tr><td class="">
+ DHCPSERVERV6
+ </td><td class="">
+ Not currently implemented: The list of IPv6 addresses of trusted DHCP servers
+ </td></tr><tr><td class="">
+ CTRL_IP_LEARNING
+ </td><td class="">
+ The choice of the IP address detection mode
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sect-element-oview"><div class="titlepage"><div><div><h3 class="title">H.10.7. Element and attribute overview</h3></div></div></div><div class="para">
+ The root element required for all network filters is named filter with two possible attributes. The name attribute provides a unique name of the given filter. The chain attribute is optional but allows certain filters to be better organized for more efficient processing by the firewall subsystem of the underlying host. Currently the system only supports the chains root, ipv4, ipv6, arp and rarp.
+ </div></div><div class="section" id="sub-sect-ref-filter"><div class="titlepage"><div><div><h3 class="title">H.10.8. References to other filters</h3></div></div></div><div class="para">
+ Any filter may hold references to other filters. Individual filters may be referenced multiple times in a filter tree but references between filters must not introduce loops.
+ </div><div class="example" id="exam-clean-traffic"><h6>Example H.7. An Example of a clean traffic filter</h6><div class="example-contents"><div class="para">
+ The following shows the XML of the clean-traffic network filter referencing several other filters.
+ </div><pre class="screen">
+<filter name='clean-traffic'>
+ <uuid>6ef53069-ba34-94a0-d33d-17751b9b8cb1</uuid>
+ <filterref filter='no-mac-spoofing'/>
+ <filterref filter='no-ip-spoofing'/>
+ <filterref filter='allow-incoming-ipv4'/>
+ <filterref filter='no-arp-spoofing'/>
+ <filterref filter='no-other-l2-traffic'/>
+ <filterref filter='qemu-announce-self'/>
+</filter>
+</pre><div class="para">
+ To reference another filter, the XML node filterref needs to be provided inside a filter node. This node must have the attribute filter whose value contains the name of the filter to be referenced.
+ </div></div></div><br class="example-break" /><div class="para">
+ New network filters can be defined at any time and may contain references to network filters that are not known to libvirt, yet. However, once a virtual machine is started or a network interface referencing a filter is to be hotplugged, all network filters in the filter tree must be available. Otherwise the virtual machine will not start or the network interface cannot be attached.
+ </div></div><div class="section" id="sub-sect-filter-rules"><div class="titlepage"><div><div><h3 class="title">H.10.9. Filter rules</h3></div></div></div><div class="para">
+ The following XML shows a simple example of a network traffic filter implementing a rule to drop traffic if the IP address (provided through the value of the variable IP) in an outgoing IP packet is not the expected one, thus preventing IP address spoofing by the VM.
+ </div><div class="example" id="filter-rules-example"><h6>Example H.8. Example of network traffic filtering</h6><div class="example-contents"><pre class="screen">
+<filter name='no-ip-spoofing' chain='ipv4'>
+ <uuid>fce8ae33-e69e-83bf-262e-30786c1f8072</uuid>
+ <rule action='drop' direction='out' priority='500'>
+ <ip match='no' srcipaddr='$IP'/>
+ </rule>
+</filter>
+</pre></div></div><br class="example-break" /><div class="para">
+ The traffic filtering rule starts with the rule node. This node may contain up to three of the following attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ action is mandatory can have the following values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ drop (matching the rule silently discards the packet with no further analysis)
+ </div></li><li class="listitem"><div class="para">
+ reject (matching the rule generates an ICMP reject message with no further analysis)
+ </div></li><li class="listitem"><div class="para">
+ accept (matching the rule accepts the packet with no further analysis)
+ </div></li><li class="listitem"><div class="para">
+ return (matching the rule passes this filter, but returns control to the calling filter for further analysis)
+ </div></li><li class="listitem"><div class="para">
+ continue (matching the rule goes on to the next rule for further analysis)
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ direction is mandatory can have the following values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ in for incomming traffic
+ </div></li><li class="listitem"><div class="para">
+ out for outgoing traffic
+ </div></li><li class="listitem"><div class="para">
+ inout for incoming and outgoing traffic
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ priority is optional. The priority of the rule controls the order in which the rule will be instantiated relative to other rules. Rules with lower values will be instantiated before rules with higher values. Valid values are in the range of -1000 to 1000. If this attribute is not provided, priority 500 will be assigned by default. Note that filtering rules in the root chain are sorted with filters connected to the root chain following their priorities. This allows to interleave filtering rules with access to filter chains. Refer to <a class="xref" href="#sub-sect-filt-chain-props">Section H.10.3, “Filtering chain priorities”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ statematch is optional. Possible values are '0' or 'false' to turn the underlying connection state matching off. The default setting is 'true' or 1
+ </div></li></ul></div><div class="para">
+ For more information see <a class="xref" href="#sub-sect-adv-filt-topics">Section H.10.11, “Advanced Filter Configuration Topics”</a>.
+ </div><div class="para">
+ The above example <a class="xref" href="#exam-clean-traffic">Example H.7, “An Example of a clean traffic filter”</a> indicates that the traffic of <em class="replaceable"><code>type ip</code></em> will be associated with the chain <em class="replaceable"><code>ipv4</code></em> and the rule will have <code class="command">priority=<em class="replaceable"><code>500</code></em></code>. If for example another filter is referenced whose traffic of <em class="replaceable"><code>type ip</code></em> is also associated with the chain <em class="replaceable"><code>ipv4</code></em> then that filter's rules will be ordered relative to the <code class="command">priority=<em class="replaceable"><code>500</code></em></code> of the shown rule.
+ </div><div class="para">
+ A rule may contain a single rule for filtering of traffic. The above example shows that traffic of type ip is to be filtered.
+ </div></div><div class="section" id="sub-sect-supp-pros"><div class="titlepage"><div><div><h3 class="title">H.10.10. Supported protocols</h3></div></div></div><div class="para">
+ The following sections list and give some details about the protocols that are supported by the network filtering subsystem. This type of traffic rule is provided in the rule node as a nested node. Depending on the traffic type a rule is filtering, the attributes are different. The above example showed the single attribute <em class="parameter"><code>srcipaddr</code></em> that is valid inside the ip traffic filtering node. The following sections show what attributes are valid and what type of data they are expecting. The following datatypes are available:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ UINT8 : 8 bit integer; range 0-255
+ </div></li><li class="listitem"><div class="para">
+ UINT16: 16 bit integer; range 0-65535
+ </div></li><li class="listitem"><div class="para">
+ MAC_ADDR: MAC address in dotted decimal format, i.e., 00:11:22:33:44:55
+ </div></li><li class="listitem"><div class="para">
+ MAC_MASK: MAC address mask in MAC address format, i.e., FF:FF:FF:FC:00:00
+ </div></li><li class="listitem"><div class="para">
+ IP_ADDR: IP address in dotted decimal format, i.e., 10.1.2.3
+ </div></li><li class="listitem"><div class="para">
+ IP_MASK: IP address mask in either dotted decimal format (255.255.248.0) or CIDR mask (0-32)
+ </div></li><li class="listitem"><div class="para">
+ IPV6_ADDR: IPv6 address in numbers format, i.e., FFFF::1
+ </div></li><li class="listitem"><div class="para">
+ IPV6_MASK: IPv6 mask in numbers format (FFFF:FFFF:FC00::) or CIDR mask (0-128)
+ </div></li><li class="listitem"><div class="para">
+ STRING: A string
+ </div></li><li class="listitem"><div class="para">
+ BOOLEAN: 'true', 'yes', '1' or 'false', 'no', '0'
+ </div></li><li class="listitem"><div class="para">
+ IPSETFLAGS: The source and destination flags of the ipset described by up to 6 'src' or 'dst' elements selecting features from either the source or destination part of the packet header; example: src,src,dst. The number of 'selectors' to provide here depends on the type of ipset that is referenced
+ </div></li></ul></div><div class="para">
+ Every attribute except for those of type <em class="parameter"><code>IP_MASK</code></em> or <em class="parameter"><code>IPV6_MASK</code></em> can be negated using the match attribute with value <em class="replaceable"><code>no</code></em>. Multiple negated attributes may be grouped together. The following XML fragment shows such an example using abstract attributes.
+ </div><pre class="screen">
+[...]
+ <rule action='drop' direction='in'>
+ <protocol match='no' attribute1='value1' attribute2='value2'/>
+ <protocol attribute3='value3'/>
+ </rule>
+[...]
+</pre><div class="para">
+ Rules behave evaluate the rule as well as look at it logically within the boundaries of the given protocol attributes. Thus, if a single attribute's value does not match the one given in the rule, the whole rule will be skipped during the evaluation process. Therefore, in the above example incoming traffic will only be dropped if: the protocol property <em class="parameter"><code>attribute1</code></em> does not match both <em class="parameter"><code>value1</code></em> and the protocol property <em class="parameter"><code>attribute2</code></em> does not match <em class="parameter"><code>value2</code></em> and the protocol property <em class="parameter"><code>attribute3</code></em> matches <em class="parameter"><code>value3</code></em>.
+ </div><div class="section" id="sub-sub-sect-mac-filter-rules"><div class="titlepage"><div><div><h4 class="title">H.10.10.1. MAC (Ethernet)</h4></div></div></div><div class="para">
+ Protocol ID: mac
+ </div><div class="para">
+ Rules of this type should go into the root chain.
+ </div><div class="table" id="table-mac-vars"><h6>Table H.3. MAC protocol types</h6><div class="table-contents"><table summary="MAC protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of destination
+ </td></tr><tr><td class="">
+ protocolid
+ </td><td class="">
+ UINT16 (0x600-0xffff), STRING
+ </td><td class="">
+ Layer 3 protocol ID. Valid strings include [arp, rarp, ipv4, ipv6]
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The filter can be written as such:
+ </div><pre class="screen">
+[...]
+<mac match='no' srcmacaddr='$MAC'/>
+[...]
+</pre></div><div class="section" id="sub-sub-sect-vlan"><div class="titlepage"><div><div><h4 class="title">H.10.10.2. VLAN (802.1Q)</h4></div></div></div><div class="para">
+ Protocol ID: vlan
+ </div><div class="para">
+ Rules of this type should go either into the root or vlan chain.
+ </div><div class="table" id="table-vlan-vars"><h6>Table H.4. VLAN protocol types</h6><div class="table-contents"><table summary="VLAN protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of destination
+ </td></tr><tr><td class="">
+ vlan-id
+ </td><td class="">
+ UINT16 (0x0-0xfff, 0 - 4095)
+ </td><td class="">
+ VLAN ID
+ </td></tr><tr><td class="">
+ encap-protocol
+ </td><td class="">
+ UINT16 (0x03c-0xfff), String
+ </td><td class="">
+ Encapsulated layer 3 protocol ID, valid strings are arp, ipv4, ipv6
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sub-sect-prot-STP-explained"><div class="titlepage"><div><div><h4 class="title">H.10.10.3. STP (Spanning Tree Protocol) </h4></div></div></div><div class="para">
+ Protocol ID: stp
+ </div><div class="para">
+ Rules of this type should go either into the root or stp chain.
+ </div><div class="table" id="table-stp-vars"><h6>Table H.5. STP protocol types</h6><div class="table-contents"><table summary="STP protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of sender
+ </td></tr><tr><td class="">
+ type
+ </td><td class="">
+ UINT8
+ </td><td class="">
+ Bridge Protocol Data Unit (BPDU) type
+ </td></tr><tr><td class="">
+ flags
+ </td><td class="">
+ UINT8
+ </td><td class="">
+ BPDU flagdstmacmask
+ </td></tr><tr><td class="">
+ root-priority
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Root priority range start
+ </td></tr><tr><td class="">
+ root-priority-hi
+ </td><td class="">
+ UINT16 (0x0-0xfff, 0 - 4095)
+ </td><td class="">
+ Root priority range end
+ </td></tr><tr><td class="">
+ root-address
+ </td><td class="">
+ MAC _ADDRESS
+ </td><td class="">
+ root MAC Address
+ </td></tr><tr><td class="">
+ root-address-mask
+ </td><td class="">
+ MAC _MASK
+ </td><td class="">
+ root MAC Address mask
+ </td></tr><tr><td class="">
+ roor-cost
+ </td><td class="">
+ UINT32
+ </td><td class="">
+ Root path cost (range start)
+ </td></tr><tr><td class="">
+ root-cost-hi
+ </td><td class="">
+ UINT32
+ </td><td class="">
+ Root path cost range end
+ </td></tr><tr><td class="">
+ sender-priority-hi
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Sender prioriry range end
+ </td></tr><tr><td class="">
+ sender-address
+ </td><td class="">
+ MAC_ADDRESS
+ </td><td class="">
+ BPDU sender MAC address
+ </td></tr><tr><td class="">
+ sender-address-mask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ BPDU sender MAC address mask
+ </td></tr><tr><td class="">
+ port
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Port identifier (range start)
+ </td></tr><tr><td class="">
+ port_hi
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Port identifier range end
+ </td></tr><tr><td class="">
+ msg-age
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Message age timer (range start)
+ </td></tr><tr><td class="">
+ msg-age-hi
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Message age timer range end
+ </td></tr><tr><td class="">
+ max-age-hi
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Maximum age time range end
+ </td></tr><tr><td class="">
+ hello-time
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Hello time timer (range start)
+ </td></tr><tr><td class="">
+ hello-time-hi
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Hello time timer range end
+ </td></tr><tr><td class="">
+ forward-delay
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Forward delay (range start)
+ </td></tr><tr><td class="">
+ forward-delay-hi
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Forward delay range end
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sub-sect-prot-ARP-RARP-explained"><div class="titlepage"><div><div><h4 class="title">H.10.10.4. ARP/RARP</h4></div></div></div><div class="para">
+ Protocol ID: arp or rarp
+ </div><div class="para">
+ Rules of this type should either go into the root or arp/rarp chain.
+ </div><div class="table" id="table-arp-vars"><h6>Table H.6. ARP and RARP protocol types</h6><div class="table-contents"><table summary="ARP and RARP protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of destination
+ </td></tr><tr><td class="">
+ hwtype
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Hardware type
+ </td></tr><tr><td class="">
+ protocoltype
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Protocol type
+ </td></tr><tr><td class="">
+ opcode
+ </td><td class="">
+ UINT16, STRING
+ </td><td class="">
+ Opcode valid strings are: Request, Reply, Request_Reverse, Reply_Reverse, DRARP_Request, DRARP_Reply, DRARP_Error, InARP_Request, ARP_NAK
+ </td></tr><tr><td class="">
+ arpsrcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ Source MAC address in ARP/RARP packet
+ </td></tr><tr><td class="">
+ arpdstmacaddr
+ </td><td class="">
+ MAC _ADDR
+ </td><td class="">
+ Destination MAC address in ARP/RARP packet
+ </td></tr><tr><td class="">
+ arpsrcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address in ARP/RARP packet
+ </td></tr><tr><td class="">
+ arpdstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address in ARP/RARP packet
+ </td></tr><tr><td class="">
+ gratututous
+ </td><td class="">
+ BOOLEAN
+ </td><td class="">
+ Boolean indiating whether to check for a gratuitous ARP packet
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sub-sect-prot-Ipv4-explained"><div class="titlepage"><div><div><h4 class="title">H.10.10.5. IPv4</h4></div></div></div><div class="para">
+ Protocol ID: ip
+ </div><div class="para">
+ Rules of this type should either go into the root or ipv4 chain.
+ </div><div class="table" id="table-ipv4-vars"><h6>Table H.7. IPv4 protocol types</h6><div class="table-contents"><table summary="IPv4 protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of destination
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ protocol
+ </td><td class="">
+ UINT8, STRING
+ </td><td class="">
+ Layer 4 protocol identifier. Valid strings for protocol are: tcp, udp, udplite, esp, ah, icmp, igmp, sctp
+ </td></tr><tr><td class="">
+ srcportstart
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Start of range of valid source ports; requires protocol
+ </td></tr><tr><td class="">
+ srcportend
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ End of range of valid source ports; requires protocol
+ </td></tr><tr><td class="">
+ dstportstart
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ Start of range of valid destination ports; requires protocol
+ </td></tr><tr><td class="">
+ dstportend
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ End of range of valid destination ports; requires protocol
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sub-sect-chars-IPv6"><div class="titlepage"><div><div><h4 class="title">H.10.10.6. IPv6</h4></div></div></div><div class="para">
+ Protocol ID: ipv6
+ </div><div class="para">
+ Rules of this type should either go into the root or ipv6 chain.
+ </div><div class="table" id="table-ipv6-vars"><h6>Table H.8. IPv6 protocol types</h6><div class="table-contents"><table summary="IPv6 protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of destination
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ protocol
+ </td><td class="">
+ UINT8, STRING
+ </td><td class="">
+ Layer 4 protocol identifier. Valid strings for protocol are: tcp, udp, udplite, esp, ah, icmpv6, sctp
+ </td></tr><tr><td class="">
+ scrportstart
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ Start of range of valid source ports; requires protocol
+ </td></tr><tr><td class="">
+ srcportend
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ End of range of valid source ports; requires protocol
+ </td></tr><tr><td class="">
+ dstportstart
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ Start of range of valid destination ports; requires protocol
+ </td></tr><tr><td class="">
+ dstportend
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ End of range of valid destination ports; requires protocol
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sub-sect-chars-tcp-udp"><div class="titlepage"><div><div><h4 class="title">H.10.10.7. TCP/UDP/SCTP</h4></div></div></div><div class="para">
+ Protocol ID: tcp, udp, sctp
+ </div><div class="para">
+ The chain parameter is ignored for this type of traffic and should either be omitted or set to root. .
+ </div><div class="table" id="table-tcp-udp-vars"><h6>Table H.9. TCP/UDP/SCTP protocol types</h6><div class="table-contents"><table summary="TCP/UDP/SCTP protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ scripto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of source IP address
+ </td></tr><tr><td class="">
+ srcipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of source IP address
+ </td></tr><tr><td class="">
+ dstipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of destination IP address
+ </td></tr><tr><td class="">
+ dstipto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of destination IP address
+ </td></tr><tr><td class="">
+ scrportstart
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ Start of range of valid source ports; requires protocol
+ </td></tr><tr><td class="">
+ srcportend
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ End of range of valid source ports; requires protocol
+ </td></tr><tr><td class="">
+ dstportstart
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ Start of range of valid destination ports; requires protocol
+ </td></tr><tr><td class="">
+ dstportend
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ End of range of valid destination ports; requires protocol
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr><tr><td class="">
+ state
+ </td><td class="">
+ STRING
+ </td><td class="">
+ comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE
+ </td></tr><tr><td class="">
+ flags
+ </td><td class="">
+ STRING
+ </td><td class="">
+ TCP-only: format of mask/flags with mask and flags each being a comma separated list of SYN,ACK,URG,PSH,FIN,RST or NONE or ALL
+ </td></tr><tr><td class="">
+ ipset
+ </td><td class="">
+ STRING
+ </td><td class="">
+ The name of an IPSet managed outside of libvirt
+ </td></tr><tr><td class="">
+ ipsetflags
+ </td><td class="">
+ IPSETFLAGS
+ </td><td class="">
+ flags for the IPSet; requires ipset attribute
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sub-sect-icmp"><div class="titlepage"><div><div><h4 class="title">H.10.10.8. ICMP</h4></div></div></div><div class="para">
+ Protocol ID: icmp
+ </div><div class="para">
+ Note: The chain parameter is ignored for this type of traffic and should either be omitted or set to root.
+ </div><div class="table" id="table-icmp-vars"><h6>Table H.10. ICMP protocol types</h6><div class="table-contents"><table summary="ICMP protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to the MAC address of the sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAD_ADDR
+ </td><td class="">
+ MAC address of the destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to the MAC address of the destination
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ srcipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ start of range of source IP address
+ </td></tr><tr><td class="">
+ scripto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ end of range of source IP address
+ </td></tr><tr><td class="">
+ dstipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of destination IP address
+ </td></tr><tr><td class="">
+ dstipto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of destination IP address
+ </td></tr><tr><td class="">
+ type
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ ICMP type
+ </td></tr><tr><td class="">
+ code
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ ICMP code
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr><tr><td class="">
+ state
+ </td><td class="">
+ STRING
+ </td><td class="">
+ comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE
+ </td></tr><tr><td class="">
+ ipset
+ </td><td class="">
+ STRING
+ </td><td class="">
+ The name of an IPSet managed outside of libvirt
+ </td></tr><tr><td class="">
+ ipsetflags
+ </td><td class="">
+ IPSETFLAGS
+ </td><td class="">
+ flags for the IPSet; requires ipset attribute
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sub-sect-igmp-esp-ah-etc"><div class="titlepage"><div><div><h4 class="title">H.10.10.9. IGMP, ESP, AH, UDPLITE, 'ALL'</h4></div></div></div><div class="para">
+ Protocol ID: igmp, esp, ah, udplite, all
+ </div><div class="para">
+ The chain parameter is ignored for this type of traffic and should either be omitted or set to root.
+ </div><div class="table" id="table-igmp-esp-ah-vars"><h6>Table H.11. IGMP, ESP, AH, UDPLITE, 'ALL'</h6><div class="table-contents"><table summary="IGMP, ESP, AH, UDPLITE, 'ALL'" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to the MAC address of the sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAD_ADDR
+ </td><td class="">
+ MAC address of the destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to the MAC address of the destination
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ srcipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ start of range of source IP address
+ </td></tr><tr><td class="">
+ scripto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ end of range of source IP address
+ </td></tr><tr><td class="">
+ dstipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of destination IP address
+ </td></tr><tr><td class="">
+ dstipto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of destination IP address
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr><tr><td class="">
+ state
+ </td><td class="">
+ STRING
+ </td><td class="">
+ comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE
+ </td></tr><tr><td class="">
+ ipset
+ </td><td class="">
+ STRING
+ </td><td class="">
+ The name of an IPSet managed outside of libvirt
+ </td></tr><tr><td class="">
+ ipsetflags
+ </td><td class="">
+ IPSETFLAGS
+ </td><td class="">
+ flags for the IPSet; requires ipset attribute
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sub-sect-tcp-utp-sctp-over-ipv6"><div class="titlepage"><div><div><h4 class="title">H.10.10.10. TCP/UDP/SCTP over IPV6</h4></div></div></div><div class="para">
+ Protocol ID: tcp-ipv6, udp-ipv6, sctp-ipv6
+ </div><div class="para">
+ The chain parameter is ignored for this type of traffic and should either be omitted or set to root.
+ </div><div class="table" id="table-tcp-udp-over-IPv6-vars"><h6>Table H.12. TCP, UDP, SCTP over IPv6 protocol types</h6><div class="table-contents"><table summary="TCP, UDP, SCTP over IPv6 protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ srcipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ start of range of source IP address
+ </td></tr><tr><td class="">
+ scripto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ end of range of source IP address
+ </td></tr><tr><td class="">
+ dstipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of destination IP address
+ </td></tr><tr><td class="">
+ dstipto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of destination IP address
+ </td></tr><tr><td class="">
+ srcportstart
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Start of range of valid source ports
+ </td></tr><tr><td class="">
+ srcportend
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ End of range of valid source ports
+ </td></tr><tr><td class="">
+ dstportstart
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Start of range of valid destination ports
+ </td></tr><tr><td class="">
+ dstportend
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ End of range of valid destination ports
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr><tr><td class="">
+ state
+ </td><td class="">
+ STRING
+ </td><td class="">
+ comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE
+ </td></tr><tr><td class="">
+ ipset
+ </td><td class="">
+ STRING
+ </td><td class="">
+ The name of an IPSet managed outside of libvirt
+ </td></tr><tr><td class="">
+ ipsetflags
+ </td><td class="">
+ IPSETFLAGS
+ </td><td class="">
+ flags for the IPSet; requires ipset attribute
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sub-sect-icmpv6"><div class="titlepage"><div><div><h4 class="title">H.10.10.11. ICMPv6</h4></div></div></div><div class="para">
+ Protocol ID: icmpv6
+ </div><div class="para">
+ The chain parameter is ignored for this type of traffic and should either be omitted or set to root.
+ </div><div class="table" id="table-icmpv6-protcol-types"><h6>Table H.13. ICMPv6 protocol types</h6><div class="table-contents"><table summary="ICMPv6 protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ srcipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ start of range of source IP address
+ </td></tr><tr><td class="">
+ scripto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ end of range of source IP address
+ </td></tr><tr><td class="">
+ dstipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of destination IP address
+ </td></tr><tr><td class="">
+ dstipto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of destination IP address
+ </td></tr><tr><td class="">
+ type
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ ICMPv6 type
+ </td></tr><tr><td class="">
+ code
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ ICMPv6 code
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr><tr><td class="">
+ state
+ </td><td class="">
+ STRING
+ </td><td class="">
+ comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE
+ </td></tr><tr><td class="">
+ ipset
+ </td><td class="">
+ STRING
+ </td><td class="">
+ The name of an IPSet managed outside of libvirt
+ </td></tr><tr><td class="">
+ ipsetflags
+ </td><td class="">
+ IPSETFLAGS
+ </td><td class="">
+ flags for the IPSet; requires ipset attribute
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sub-sect-igmp-esp-ah-udplite-over-ipv6"><div class="titlepage"><div><div><h4 class="title">H.10.10.12. IGMP, ESP, AH, UDPLITE, 'ALL' over IPv6</h4></div></div></div><div class="para">
+ Protocol ID: igmp-ipv6, esp-ipv6, ah-ipv6, udplite-ipv6, all-ipv6
+ </div><div class="para">
+ The chain parameter is ignored for this type of traffic and should either be omitted or set to root.
+ </div><div class="table" id="table-igmp-esp-ah-udplite-over-ipv6-vars"><h6>Table H.14. IGMP, ESP, AH, UDPLITE, 'ALL' over IPv protocol types</h6><div class="table-contents"><table summary="IGMP, ESP, AH, UDPLITE, 'ALL' over IPv protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ srcipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ start of range of source IP address
+ </td></tr><tr><td class="">
+ scripto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ end of range of source IP address
+ </td></tr><tr><td class="">
+ dstipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of destination IP address
+ </td></tr><tr><td class="">
+ dstipto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of destination IP address
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr><tr><td class="">
+ state
+ </td><td class="">
+ STRING
+ </td><td class="">
+ comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE
+ </td></tr><tr><td class="">
+ ipset
+ </td><td class="">
+ STRING
+ </td><td class="">
+ The name of an IPSet managed outside of libvirt
+ </td></tr><tr><td class="">
+ ipsetflags
+ </td><td class="">
+ IPSETFLAGS
+ </td><td class="">
+ flags for the IPSet; requires ipset attribute
+ </td></tr></tbody></table></div></div><br class="table-break" /></div></div><div class="section" id="sub-sect-adv-filt-topics"><div class="titlepage"><div><div><h3 class="title">H.10.11. Advanced Filter Configuration Topics</h3></div></div></div><div class="para">
+ The following sections discuss advanced filter configuration topics.
+ </div><div class="section" id="sub-sub-sect-conn-track"><div class="titlepage"><div><div><h4 class="title">H.10.11.1. Connection tracking</h4></div></div></div><div class="para">
+ The network filtering subsystem (on Linux) makes use of the connection tracking support of IP tables. This helps in enforcing the directionality of network traffic (state match) as well as counting and limiting the number of simultaneous connections towards a guest. As an example, if a guest has TCP port 8080 open as a server, clients may connect to the guest on port 8080. Connection tracking and enforcement of directionality then prevents the guest from initiating a connection from (TCP client) port 8080 to the host back to a remote host. More importantly, tracking helps to prevent remote attackers from establishing a connection back to a guest. For example, if the user inside the guest established a connection to port 80 on an attacker site, then the attacker will not be able to initiate a connection from TCP port 80 back towards the guest. By default the connection state match that enables connection tracking and then enforcement of directionality of traffic is turne
d on.
+ </div><div class="example"><h6>Example H.9. XML example for turning off connections to the TCP port</h6><div class="example-contents"><div class="para">
+ The following shows an example XML fragement where this feature has been turned off for incoming connections to TCP port 12345.
+ </div><pre class="screen">
+ [...]
+ <rule direction='in' action='accept' statematch='false'>
+ <cp dstportstart='12345'/>
+ </rule>
+ [...]
+</pre><div class="para">
+ This now allows incoming traffic to TCP port 12345, but would also enable the initiation from (client) TCP port 12345 within the VM, which may or may not be desirable.
+ </div></div></div><br class="example-break" /></div><div class="section" id="sub-sub-sect-lim-numb-conns"><div class="titlepage"><div><div><h4 class="title">H.10.11.2. Limiting Number of Connections</h4></div></div></div><div class="para">
+ To limit the number of connections a guest may establish, a rule must be provided that sets a limit of connections for a given type of traffic. If for example a VM is supposed to be allowed to only ping one other IP address at a time and is supposed to have only one active incoming ssh connection at a time.
+ </div><div class="example" id="ex-xml-frag-limits"><h6>Example H.10. XML sample file that sets limits to connections</h6><div class="example-contents"><div class="para">
+ The following XML fragment can be used to limit connections
+ </div><pre class="screen">
+ [...]
+ <rule action='drop' direction='in' priority='400'>
+ <tcp connlimit-above='1'/>
+ </rule>
+ <rule action='accept' direction='in' priority='500'>
+ <tcp dstportstart='22'/>
+ </rule>
+ <rule action='drop' direction='out' priority='400'>
+ <icmp connlimit-above='1'/>
+ </rule>
+ <rule action='accept' direction='out' priority='500'>
+ <icmp/>
+ </rule>
+ <rule action='accept' direction='out' priority='500'>
+ <udp dstportstart='53'/>
+ </rule>
+ <rule action='drop' direction='inout' priority='1000'>
+ <all/>
+ </rule>
+ [...]
+</pre></div></div><br class="example-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Limitation rules must be listed in the XML prior to the rules for accepting traffic. According to the XML file in <a class="xref" href="#ex-xml-frag-limits">Example H.10, “XML sample file that sets limits to connections”</a>, an additional rule for allowing DNS traffic sent to port 22 go out the guest, has been added to avoid ssh sessions not getting established for reasons related to DNS lookup failures by the ssh daemon. Leaving this rule out may result in the ssh client hanging unexpectedly as it tries to connect. Additional caution should be used in regards to handling timeouts related to tracking of traffic. An ICMP ping that the user may have terminated inside the guest may have a long timeout in the host's connection tracking system and will therefore not allow another ICMP ping to go through.
+ </div><div class="para">
+ The best solution is to tune the timeout in the host's <code class="filename">sysfs</code> with the following command:# <code class="command">echo 3 > /proc/sys/net/netfilter/nf_conntrack_icmp_timeout</code>. This command sets the ICMP connection tracking timeout to 3 seconds. The effect of this is that once one ping is terminated, another one can start after 3 seconds.
+ </div><div class="para">
+ If for any reason the guest has not properly closed its TCP connection, the connection to be held open for a longer period of time, especially if the TCP timeout value was set for a large amount of time on the host. In addition, any idle connection may result in a time out in the connection tracking system which can be re-activated once packets are exchanged.
+ </div><div class="para">
+ However, if the limit is set too low, newly initiated connections may force an idle connection into TCP backoff. Therefore, the limit of connections should be set rather high so that fluctuations in new TCP connections don't cause odd traffic behavior in relation to idle connections.
+ </div></div></div></div><div class="section" id="sub-sub-subsect-command-line-tools"><div class="titlepage"><div><div><h4 class="title">H.10.11.3. Command line tools</h4></div></div></div><div class="para">
+ virsh has been extended with life-cycle support for network filters. All commands related to the network filtering subsystem start with the prefix <em class="parameter"><code>nwfilter</code></em>. The following commands are available:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">nwfilter-list</code> : lists UUIDs and names of all network filters
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">nwfilter-define</code> : defines a new network filter or updates an existing one (must supply a name)
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">nwfilter-undefine</code> : deletes a specified network filter (must supply a name). In addition, it cannot currently be in use
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">nwfilter-dumpxml</code> : displays a specified network filter (must supply a name)
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">nwfilter-edit</code> : edits a specified network filter (must supply a name)
+ </div></li></ul></div></div><div class="section" id="sub-sub-sect-pre-exist-net-filter"><div class="titlepage"><div><div><h4 class="title">H.10.11.4. Pre-existing network filters</h4></div></div></div><div class="para">
+ The following is a list of example network filters that are automatically installed with libvirt:
+ </div><div class="table" id="table-icmpv6-vars"><h6>Table H.15. ICMPv6 protocol types</h6><div class="table-contents"><table summary="ICMPv6 protocol types" border="1"><colgroup><col class="1" width="50%" /><col class="2" width="50%" /></colgroup><thead><tr><th class="">
+ Command Name
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ no-arp-spoofing
+ </td><td class="">
+ Prevents a guest from spoofing ARP traffic; this filter only allows ARP request and reply messages and enforces that those packets contain the MAC and IP addresses of the guest.
+ </td></tr><tr><td class="">
+ allow-dhcp
+ </td><td class="">
+ Allows a guest to request an IP address via DHCP (from any DHCP server)
+ </td></tr><tr><td class="">
+ allow-dhcp-server
+ </td><td class="">
+ Allows a guest to request an IP address from a specified DHCP server. The dotted decimal IP address of the DHCP server must be provided in a reference to this filter. The name of the variable must be <em class="replaceable"><code>DHCPSERVER</code></em>.
+ </td></tr><tr><td class="">
+ no-ip-spoofing
+ </td><td class="">
+ Prevents a guest from sending IP packets with a source IP address different from the one inside the packet.
+ </td></tr><tr><td class="">
+ no-ip-multicast
+ </td><td class="">
+ Prevents a guest from sending IP multicast packets.
+ </td></tr><tr><td class="">
+ clean-traffic
+ </td><td class="">
+ Prevents MAC, IP and ARP spoofing. This filter references several other filters as building blocks.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ These filters are only building blocks and require a combination with other filters to provide useful network traffic filtering. The most used one in the above list is the <em class="replaceable"><code>clean-traffic</code></em> filter. This filter itself can for example be combined with the <em class="replaceable"><code>no-ip-multicast</code></em> filter to prevent virtual machines from sending IP multicast traffic on top of the prevention of packet spoofing.
+ </div></div><div class="section" id="sub-sub-sect-write-own-filters"><div class="titlepage"><div><div><h4 class="title">H.10.11.5. Writing your own filters</h4></div></div></div><div class="para">
+ Since libvirt only provides a couple of example networking filters, you may consider writing your own. When planning on doing so there are a couple of things you may need to know regarding the network filtering subsystem and how it works internally. Certainly you also have to know and understand the protocols very well that you want to be filtering on so that no further traffic than what you want can pass and that in fact the traffic you want to allow does pass.
+ </div><div class="para">
+ The network filtering subsystem is currently only available on Linux hosts and only works for Qemu and KVM type of virtual machines. On Linux, it builds upon the support for ebtables, iptables and ip6tables and makes use of their features. Considering the list found in <a class="xref" href="#sub-sect-supp-pros">Section H.10.10, “Supported protocols”</a> the following protolcols can be implemented using ebtables:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ mac
+ </div></li><li class="listitem"><div class="para">
+ stp (spanning tree protocol)
+ </div></li><li class="listitem"><div class="para">
+ vlan (802.1Q)
+ </div></li><li class="listitem"><div class="para">
+ arp, rarp
+ </div></li><li class="listitem"><div class="para">
+ ipv4
+ </div></li><li class="listitem"><div class="para">
+ ipv6
+ </div></li></ul></div><div class="para">
+ Any protocol that runs over IPv4 is supported using iptables, those over IPv6 are implemented using ip6tables.
+ </div><div class="para">
+ Using a Linux host, all traffic filtering rules created by libvirt's network filtering subsystem first passes through the filtering support implemented by ebtables and only afterwards through iptables or ip6tables filters. If a filter tree has rules with the protocols including: mac, stp, vlan arp, rarp, ipv4, or ipv6; the ebtable rules and values listed will automatically be used first.
+ </div><div class="para">
+ Multiple chains for the same protocol can be created. The name of the chain must have a prefix of one of the previously enumerated protocols. To create an additional chain for handling of ARP traffic, a chain with name arp-test, can for example be specified.
+ </div><div class="para">
+ As an example, it is possible to filter on UDP traffic by source and destination ports using the ip protocol filter and specifying attributes for the protocol, source and destination IP addresses and ports of UDP packets that are to be accepted. This allows early filtering of UDP traffic with ebtables. However, once an IP or IPv6 packet, such as a UDP packet, has passed the ebtables layer and there is at least one rule in a filter tree that instantiates iptables or ip6tables rules, a rule to let the UDP packet pass will also be necessary to be provided for those filtering layers. This can be achieved with a rule containing an appropriate udp or udp-ipv6 traffic filtering node.
+ </div><div class="example"><h6>Example H.11. Creating a custom filter</h6><div class="example-contents"><div class="para">
+ Suppose a filter is needed to fulfill the following list of requirements:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ prevents a VM's interface from MAC, IP and ARP spoofing
+ </div></li><li class="listitem"><div class="para">
+ opens only TCP ports 22 and 80 of a VM's interface
+ </div></li><li class="listitem"><div class="para">
+ allows the VM to send ping traffic from an interface but not let the VM be pinged on the interface
+ </div></li><li class="listitem"><div class="para">
+ allows the VM to do DNS lookups (UDP towards port 53)
+ </div></li></ul></div><div class="para">
+ The requirement to prevent spoofing is fulfilled by the existing <em class="parameter"><code>clean-traffic</code></em> network filter, thus the way to do this is to reference it from a custom filter.
+ </div><div class="para">
+ To enable traffic for TCP ports 22 and 80, two rules are added to enable this type of traffic. To allow the guest to send ping traffic a rule is added for ICMP traffic. For simplicity reasons, general ICMP traffic will be allowed to be initated from the guest, and will not be specified to ICMP echo request and response messages. All other traffic will be prevented to reach or be initated by the guest. To do this a rule will be added that drops all other traffic. Assuming the guest is called <code class="filename">test</code> and the interface to associate our filter with is called <code class="filename">eth0</code>, a filter is created named <code class="filename">test-eth0</code>.
+ </div><div class="para">
+ The result of these considerations is the following network filter XML:
+ </div><pre class="screen">
+<filter name='test-eth0'>
+ <!- - This rule references the clean traffic filter to prevent MAC, IP and ARP spoofing. By not providing an IP address parameter, libvirt will detect the IP address the guest is using. - ->
+ <filterref filter='clean-traffic'/>
+
+ <!- - This rule enables TCP ports 22 (ssh) and 80 (http) to be reachable - ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='22'/>
+ </rule>
+
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='80'/>
+ </rule>
+
+ <!- - This rule enables general ICMP traffic to be initiated by the guest including ping traffic - ->
+ <rule action='accept' direction='out'>
+ <icmp/>
+ </rule>>
+
+ <!- - This rule enables outgoing DNS lookups using UDP - ->
+ <rule action='accept' direction='out'>
+ <udp dstportstart='53'/>
+ </rule>
+
+ <!- - This rule drops all other traffic - ->
+ <rule action='drop' direction='inout'>
+ <all/>
+ </rule>
+
+</filter>
+</pre></div></div><br class="example-break" /></div><div class="section" id="sub-sub-sect-samp-filter"><div class="titlepage"><div><div><h4 class="title">H.10.11.6. Sample custom filter</h4></div></div></div><div class="para">
+ Although one of the rules in the above XML contains the IP address of the guest as either a source or a destination address, the filtering of the traffic works correctly. The reason is that whereas the rule's evaluation occurrs internally on a per-interface basis, the rules are additionaly evaluated based on which (tap) interface has sent or will receive the packet, rather than what their source or destination IP address may be.
+ </div><div class="example"><h6>Example H.12. Sample XML for network interface descriptions</h6><div class="example-contents"><div class="para">
+ An XML fragment for a possible network interface description inside the domain XML of the test guest could then look like this:
+ </div><pre class="screen">
+ [...]
+ <interface type='bridge'>
+ <source bridge='mybridge'/>
+ <filterref filter='test-eth0'/>
+ </interface>
+ [...]
+</pre><div class="para">
+ To more strictly control the ICMP traffic and enforce that only ICMP echo requests can be sent from the guest and only ICMP echo responses be received by the guest, the above ICMP rule can be replaced with the following two rules:
+ </div><pre class="screen">
+ <!- - enable outgoing ICMP echo requests- ->
+ <rule action='accept' direction='out'>
+ <icmp type='8'/>
+ </rule>
+</pre><pre class="screen">
+ <!- - enable incoming ICMP echo replies- ->
+ <rule action='accept' direction='in'>
+ <icmp type='0'/>
+ </rule>
+</pre></div></div><br class="example-break" /><div class="example"><h6>Example H.13. Second example custom filter</h6><div class="example-contents"><div class="para">
+ This example demonstrates how to build a similar filter as in the example above, but extends the list of requirements with an ftp server located inside the guest. The requirements for this filter are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ prevents a guest's interface from MAC, IP, and ARP spoofing
+ </div></li><li class="listitem"><div class="para">
+ opens only TCP ports 22 and 80 in a guest's interface
+ </div></li><li class="listitem"><div class="para">
+ allows the guest to send ping traffic from an interface but does not allow the guest to be pinged on the interface
+ </div></li><li class="listitem"><div class="para">
+ allows the guest to do DNS lookups (UDP towards port 53)
+ </div></li><li class="listitem"><div class="para">
+ enables the ftp server (in active mode) so it can run inside the guest
+ </div></li></ul></div><div class="para">
+ The additional requirement of allowing an FTP server to be run inside the guest maps into the requirement of allowing port 21 to be reachable for FTP control traffic as well as enabling the guest to establish an outgoing TCP connection originating from the guest's TCP port 20 back to the FTP client (FTP active mode). There are several ways of how this filter can be written and two possible solutions are included in this example.
+ </div><div class="para">
+ The first solution makes use of the state attribute of the TCP protocol that provides a hook into the connection tracking framework of the Linux host. For the guest-initiated FTP data connection (FTP active mode) the RELATED state is used to enable detection that the guest-initiated FTP data connection is a consequence of ( or 'has a relationship with' ) an existing FTP control connection, thereby allowing it to pass packets through the firewall. The RELATED state, however, is only valid for the very first packet of the outgoing TCP connection for the FTP data path. Afterwards, the state is ESTABLISHED, which then applies equally to the incoming and outgoing direction. All this is related to the FTP data traffic originating from TCP port 20 of the guest. This then leads to the following solution:
+ </div><pre class="screen">
+<filter name='test-eth0'>
+ <!- - This filter (eth0) references the <code class="filename">clean traffic</code> filter to prevent MAC, IP, and ARP spoofing. By not providing an IP address parameter, libvirt will detect the IP address the guest is using. - ->
+ <filterref filter='clean-traffic'/>
+
+ <!- - This rule enables TCP port 21 (FTP-control) to be reachable - ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='21'/>
+ </rule>
+
+ <!- - This rule enables TCP port 20 for guest-initiated FTP data connection related to an existing FTP control connection - ->
+ <rule action='accept' direction='out'>
+ <tcp srcportstart='20' state='RELATED,ESTABLISHED'/>
+ </rule>
+
+ <!- - This rule accepts all packets from a client on the FTP data connection - ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='20' state='ESTABLISHED'/>
+ </rule>
+
+ <!- - This rule enables TCP port 22 (SSH) to be reachable - ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='22'/>
+ </rule>
+
+ <!- -This rule enables TCP port 80 (HTTP) to be reachable - ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='80'/>
+ </rule>
+
+ <!- - This rule enables general ICMP traffic to be initiated by the guest, including ping traffic - ->
+ <rule action='accept' direction='out'>
+ <icmp/>
+ </rule>
+
+ <!- - This rule enables outgoing DNS lookups using UDP - ->
+ <rule action='accept' direction='out'>
+ <udp dstportstart='53'/>
+ </rule>
+
+ <!- - This rule drops all other traffic - ->
+ <rule action='drop' direction='inout'>
+ <all/>
+ </rule>
+
+</filter>
+</pre><div class="para">
+ Before trying out a filter using the RELATED state, you have to make sure that the appropriate connection tracking module has been loaded into the host's kernel. Depending on the version of the kernel, you must run either one of the following two commands before the FTP connection with the guest is established:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ #<code class="command">modprobe nf_conntrack_ftp</code> - where available OR
+ </div></li><li class="listitem"><div class="para">
+ #<code class="command">modprobe ip_conntrack_ftp</code> if above is not available
+ </div></li></ul></div><div class="para">
+ If protocols other than FTP are used in conjunction with the RELATED state, their corresponding module must be loaded. Modules are available for the protocols: ftp, tftp, irc, sip, sctp, and amanda.
+ </div><div class="para">
+ The second solution makes use of the state flags of connections more than the previous solution did. This solution takes advantage of the fact that the NEW state of a connection is valid when the very first packet of a traffic flow is detected. Subsequently, if the very first packet of a flow is accepted, the flow becomes a connection and thus enters into the ESTABLISHED state. Therefore a general rule can be written for allowing packets of ESTABLISHED connections to reach the guest or be sent by the guest. This is done writing specific rules for the very first packets identified by the NEW state and dictates the ports that the data is acceptable. All packets meant for ports that are not explicitly accepted are dropped, thus not reaching an ESTABLISHED state. Any subsequent packets sent from that port are dropped as well.
+ </div><pre class="screen">
+<filter name='test-eth0'>
+ <!- - This filter references the <code class="filename">clean traffic</code> filter to prevent MAC, IP and ARP spoofing. By not providing and IP address parameter, libvirt will detect the IP address the VM is using. - ->
+ <filterref filter='clean-traffic'/>
+
+ <!- - This rule allows the packets of all previously accepted connections to reach the guest - ->
+ <rule action='accept' direction='in'>
+ <all state='ESTABLISHED'/>
+ </rule>
+
+ <!- - This rule allows the packets of all previously accepted and related connections be sent from the guest - ->
+ <rule action='accept' direction='out'>
+ <all state='ESTABLISHED,RELATED'/>
+ </rule>
+
+ <!- - This rule enables traffic towards port 21 (FTP) and port 22 (SSH)- ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='21' dstportend='22' state='NEW'/>
+ </rule>
+
+ <!- - This rule enables traffic towards port 80 (HTTP) - ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='80' state='NEW'/>
+ </rule>
+
+ <!- - This rule enables general ICMP traffic to be initiated by the guest, including ping traffic - ->
+ <rule action='accept' direction='out'>
+ <icmp state='NEW'/>
+ </rule>
+
+ <!- - This rule enables outgoing DNS lookups using UDP - ->
+ <rule action='accept' direction='out'>
+ <udp dstportstart='53' state='NEW'/>
+ </rule>
+
+ <!- - This rule drops all other traffic - ->
+ <rule action='drop' direction='inout'>
+ <all/>
+ </rule>
+
+</filter>
+</pre></div></div><br class="example-break" /></div></div><div class="section" id="sub-sect-limitations-filters-network-subsystem"><div class="titlepage"><div><div><h3 class="title">H.10.12. Limitations</h3></div></div></div><div class="para">
+ The following is a list of the currently known limitations of the network filtering subsystem.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ VM migration is only supported if the whole filter tree that is referenced by a guest's top level filter is also available on the target host. The network filter <code class="filename">clean-traffic</code> for example should be available on all libvirt installations and thus enable migration of guests that reference this filter. To assure version compatibility is not a problem make sure you are using the most current version of libvirt by updating the package regurally.
+ </div></li><li class="listitem"><div class="para">
+ Migration must occur between libvirt insallations of version 0.8.1 or later in order not to lose the network traffic filters associated with an interface.
+ </div></li><li class="listitem"><div class="para">
+ VLAN (802.1Q) packets, if sent by a guest, cannot be filtered with rules for protocol IDs arp, rarp, ipv4 and ipv6. They can only be filtered with protocol IDs, MAC and VLAN. Therefore, the example filter clean-traffic <a class="xref" href="#ex-net-filtering">Example H.1, “An example of network filtering”</a> will not work as expected.
+ </div></li></ul></div></div></div></div><div xml:lang="en-US" class="appendix" id="appe-Virtualization-Additional_resources" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Additional resources</h1></div></div></div><div class="para">
+ To learn more about virtualization and Fedora, refer to the following resources.
+ </div><div class="section" id="sect-Virtualization-Additional_resources-Online_resources"><div class="titlepage"><div><div><h2 class="title">I.1. Online resources</h2></div></div></div><a id="idm105109248" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><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 class="listitem"><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 class="listitem"><div class="para">
+ Open Virtualization Center
+ </div><div class="para">
+ <a href="http://www.openvirtualization.com/">http://www.openvirtualization.com</a>
+ </div></li><li class="listitem"><div class="para">
+ Fedora Documentation
+ </div><div class="para">
+ <a href="http://docs.fedoraproject.org">http://docs.fedoraproject.org</a>
+ </div></li><li class="listitem"><div class="para">
+ Virtualization technologies overview
+ </div><div class="para">
+ <a href="http://virt.kernelnewbies.org/">http://virt.kernelnewbies.org</a>
+ </div></li><li class="listitem"><div class="para">
+ Fedora Community
+ </div><div class="para">
+ <a href="https://fedoraproject.org/en/join-fedora">https://fedoraproject.org/en/join-fedora</a>
+ </div></li></ul></div></div><div class="section" id="sect-Virtualization-Additional_resources-Installed_documentation"><div class="titlepage"><div><div><h2 class="title">I.2. Installed documentation</h2></div></div></div><a id="idm95835504" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><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 class="listitem"><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 class="listitem"><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 class="listitem"><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 distributions inside of virtual machines.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/virt-manager-<em class="replaceable"><code><version-number></code></em></code> — Provides documentation on the Virtual Machine Manager, which provides a graphical tool for administering virtual machines.
+ </div></li></ul></div></div></div><div xml:lang="en-US" class="appendix" id="ch-lib-dom-xml" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Manipulating the domain xml</h1></div></div></div><div class="para">
+ This section describes the XML format used to represent one or more libvirt domains. Whereas a libvirt domain refers to a specified guest virtual machine, here the term <em class="firstterm">domain</em> refers to the root <code class="sgmltag-starttag"><domain></code> element required for defining the parameters of all guest virtual machines. The <code class="sgmltag-starttag"><domain></code> element has two attributes: <code class="sgmltag-attribute">type</code> specifies the hypervisor used for running the domain. The allowed values are driver specific, but include <code class="sgmltag-attvalue"> KVM</code> and others. <code class="sgmltag-attribute">id</code> is a unique integer identifier for the running guest machine. Inactive machines have no id value. The sections in this chapter will address the components of the domain XML. Additional chapters in this manual may refer to this chapter when manipulation of the domain XML is required.
+ </div><div class="section" id="sect-gen-metadata"><div class="titlepage"><div><div><h2 class="title">J.1. General information and metadata</h2></div></div></div><div class="para">
+ This information is in this part of the domain XML:
+ </div><div class="figure" id="ch-lib-dom-xml-example"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain</span><span class="perl_Others"> type=</span><span class="perl_String">'xen'</span><span class="perl_Others"> id=</span><span class="perl_String">'3'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><name></span>fv0<span class="perl_Keyword"></name></span>
+ <span class="perl_Keyword"><uuid></span>4dea22b31d52d8f32516782e98ab3fa0<span class="perl_Keyword"></uuid></span>
+ <span class="perl_Keyword"><title></span>A short description - title - of the domain<span class="perl_Keyword"></title></span>
+ <span class="perl_Keyword"><description></span>Some human readable description<span class="perl_Keyword"></description></span>
+ <span class="perl_Keyword"><metadata></span>
+ <span class="perl_Keyword"><app1:foo</span><span class="perl_Others"> xmlns:app1=</span><span class="perl_String">"http://app1.org/app1/"</span><span class="perl_Keyword">></span>..<span class="perl_Keyword"></app1:foo></span>
+ <span class="perl_Keyword"><app2:bar</span><span class="perl_Others"> xmlns:app2=</span><span class="perl_String">"http://app1.org/app2/"</span><span class="perl_Keyword">></span>..<span class="perl_Keyword"></app2:bar></span>
+ <span class="perl_Keyword"></metadata></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.1. Domain XML metadata</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-gen-metadata"><h6>Table J.1. General metadata elements</h6><div class="table-contents"><table summary="General metadata elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><name></code>
+ </td><td class="">
+ Assigns a name for the virtual machine. This name should consist only of alpha-numeric characters and is required to be unique within the scope of a single host. It is often used to form the filename for storing the persistent configuration files.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><uuid></code>
+ </td><td class="">
+ assigns a globally unique identifier for the virtual machine. The format must be RFC 4122 compliant, eg <code class="sgmltag-attvalue">3e3fce45-4f53-4fa7-bb32-11f34168b82b</code>. If omitted when defining/creating a new machine, a random UUID is generated. It is also possible to provide the UUID via a sysinfo specification.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><title></code>
+ </td><td class="">
+ <code class="sgmltag-element">title</code> Creates space for a short description of the domain. The title should not contain any newlines.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><description></code>
+ </td><td class="">
+ Different from the title, This data is not used by libvirt in any way, it can contain any information the user wants to display.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><metadata></code>
+ </td><td class="">
+ Can be used by applications to store custom metadata in the form of XML nodes/trees. Applications must use custom namespaces on their XML nodes/trees, with only one top-level element per namespace (if the application needs structure, they should have sub-elements to their namespace element)
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sect-dom-xml-op-sys-boot"><div class="titlepage"><div><div><h2 class="title">J.2. Operating system booting</h2></div></div></div><div class="para">
+ There are a number of different ways to boot virtual machines each with their own pros and cons. Each one is described in the sub-sections that follow and include: BIOS bootloader, Host bootloader, direct kerel boot, and container boot.
+ </div><div class="section" id="sub-sect-op-sys-boot-bios-boot"><div class="titlepage"><div><div><h3 class="title">J.2.1. BIOS bootloader</h3></div></div></div><div class="para">
+ Booting via the BIOS is available for hypervisors supporting full virtualization. In this case the BIOS has a boot order priority (floppy, harddisk, cdrom, network) determining where to obtain/find the boot image. The OS section of the domain XML contatins the information as follows:
+ </div><div class="figure" id="fig-op-sys-boot-bios-boot"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><os></span>
+ <span class="perl_Keyword"><type></span>hvm<span class="perl_Keyword"></type></span>
+ <span class="perl_Keyword"><loader></span>/usr/lib/xen/boot/hvmloader<span class="perl_Keyword"></loader></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> dev=</span><span class="perl_String">'hd'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> dev=</span><span class="perl_String">'cdrom'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><bootmenu</span><span class="perl_Others"> enable=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><smbios</span><span class="perl_Others"> mode=</span><span class="perl_String">'sysinfo'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><bios</span><span class="perl_Others"> useserial=</span><span class="perl_String">'yes'</span><span class="perl_Others"> rebootTimeout=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></os></span>
+ ...
+</pre></div><h6>Figure J.2. BOIS bootloader domain XML</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-biosbootloader-os"><h6>Table J.2. BIOS bootloader elements</h6><div class="table-contents"><table summary="BIOS bootloader elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><type></code>
+ </td><td class="">
+ Specifies the type of operating system to be booted on the guest virtual machine. <code class="sgmltag-attvalue">hvm</code> indicates that the OS is one designed to run on bare metal, so requires full virtualization. <code class="sgmltag-attvalue">linux</code> refers to an OS that supports the Xen 3 hypervisor guest ABI. There are also two optional attributes, <code class="sgmltag-attribute">arch</code> specifying the CPU architecture to virtualization, and <code class="sgmltag-attribute">machine</code> referring to the machine type. Refer to <a href="http://libvirt.org/formatcaps.html"><em class="citetitle">Driver Capabilities</em></a> for more information.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><loader></code>
+ </td><td class="">
+ refers to a piece of firmware that is used to assist the domain creation process. It is only needed for using Xen fully virtualized domains.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><boot></code>
+ </td><td class="">
+ takes one of the values:<code class="sgmltag-attvalue">fd</code>, <code class="sgmltag-attvalue">hd</code>, <code class="sgmltag-attvalue">cdrom</code> or <code class="sgmltag-attvalue">network</code> and is used to specify the next boot device to consider. The boot element can be repeated multiple times to setup a priority list of boot devices to try in turn. Multiple devices of the same type are sorted according to their targets while preserving the order of buses. After defining the domain, its XML configuration returned by libvirt (through virDomainGetXMLDesc) lists devices in the sorted order. Once sorted, the first device is marked as bootable. For more information see <a href="http://libvirt.org/formatdomain.html#elements"><em class="citetitle">BIOS bootloader</em></a>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><bootmenu></code>
+ </td><td class="">
+ determines whether or not to enable an interactive boot menu prompt on guest startup. The <code class="sgmltag-attribute">enable</code> attribute can be either <code class="sgmltag-attvalue">yes</code> or <code class="sgmltag-attvalue">no</code>. If not specified, the hypervisor default is used
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><smbios></code>
+ </td><td class="">
+ determines how SMBIOS information is made visible in the guest. The <code class="sgmltag-attribute">mode</code> attribute must be specified, as either <code class="sgmltag-attvalue">emulate</code> (lets the hypervisor generate all values), <code class="sgmltag-attvalue">host</code>(copies all of Block 0 and Block 1, except for the UUID, from the host's SMBIOS values; the virConnectGetSysinfo call can be used to see what values are copied), or <code class="sgmltag-attvalue">sysinfo</code> (uses the values in the sysinfo element). If not specified, the hypervisor default setting is used.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><bios></code>
+ </td><td class="">
+ This element has attribute <code class="sgmltag-attribute">useserial</code> with possible values <code class="sgmltag-attvalue">yes</code> or <code class="sgmltag-attvalue">no</code>. The attribute enables or disables Serial Graphics Adapter which allows users to see BIOS messages on a serial port. Therefore, one needs to have serial port defined. Note there is another attribute, <code class="sgmltag-attribute">rebootTimeout</code> that controls whether and after how long the guest should start booting again in case the boot fails (according to BIOS). The value is in milliseconds with maximum of <code class="sgmltag-attvalue">65535</code> and special value <code class="sgmltag-attvalue">-1</code> disables the reboot.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sect-op-sys-host-boot"><div class="titlepage"><div><div><h3 class="title">J.2.2. Host bootloader</h3></div></div></div><div class="para">
+ Hypervisors employing paravirtualization do not usually emulate a BIOS, but instead the host is responsible for the operating system boot. This may use a pseudo-bootloader in the host to provide an interface to choose a kernel for the guest. An example is pygrub with Xen.
+ </div><div class="figure" id="fig-op-sys-host-boot"><div class="figure-contents"><pre class="programlisting">
+ ...
+ <span class="perl_Keyword"><bootloader></span>/usr/bin/pygrub<span class="perl_Keyword"></bootloader></span>
+ <span class="perl_Keyword"><bootloader_args></span>--append single<span class="perl_Keyword"></bootloader_args></span>
+ ...
+</pre></div><h6>Figure J.3. Host bootloader domain XML</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-hostbootloader-os"><h6>Table J.3. BIOS bootloader elements</h6><div class="table-contents"><table summary="BIOS bootloader elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><bootloader></code>
+ </td><td class="">
+ provides a fully qualified path to the bootloader executable in the host OS. This bootloader will choose which kernel to boot. The required output of the bootloader is dependent on the hypervisor in use.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><bootloader_args></code>
+ </td><td class="">
+ allows command line arguments to be passed to the bootloader (optional command)
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sect-op-sys-dir-kern-boot"><div class="titlepage"><div><div><h3 class="title">J.2.3. Direct kernel boot</h3></div></div></div><div class="para">
+ When installing a new guest OS, it is often useful to boot directly from a kernel and initrd stored in the host OS, allowing command line arguments to be passed directly to the installer. This capability is usually available for both para and full virtualized guests.
+ </div><div class="figure" id="fig-op-sys-dir-kern-boot"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><os></span>
+ <span class="perl_Keyword"><type></span>hvm<span class="perl_Keyword"></type></span>
+ <span class="perl_Keyword"><loader></span>/usr/lib/xen/boot/hvmloader<span class="perl_Keyword"></loader></span>
+ <span class="perl_Keyword"><kernel></span>/root/f8-i386-vmlinuz<span class="perl_Keyword"></kernel></span>
+ <span class="perl_Keyword"><initrd></span>/root/f8-i386-initrd<span class="perl_Keyword"></initrd></span>
+ <span class="perl_Keyword"><cmdline></span>console=ttyS0 ks=http://example.com/f8-i386/os/<span class="perl_Keyword"></cmdline></span>
+ <span class="perl_Keyword"><dtb></span>/root/ppc.dtb<span class="perl_Keyword"></dtb></span>
+ <span class="perl_Keyword"></os></span>
+ ...
+
+</pre></div><h6>Figure J.4. Direct kernel boot</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-dir-kernelboot-os"><h6>Table J.4. Direct kernel boot elements</h6><div class="table-contents"><table summary="Direct kernel boot elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><type></code>
+ </td><td class="">
+ same as described in the BIOS boot section
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><loader></code>
+ </td><td class="">
+ same as described in the BIOS boot section
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><kernel></code>
+ </td><td class="">
+ secifies the fully-qualified path to the kernel image in the host OS
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><initrd></code>
+ </td><td class="">
+ specifies the fully-qualified path to the (optional) ramdisk image in the host OS.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><cmdline></code>
+ </td><td class="">
+ specifies arguments to be passed to the kernel (or installer) at boot time. This is often used to specify an alternate primary console (eg serial port), or the installation media source / kickstart file
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sect-op-sys-cont-boot"><div class="titlepage"><div><div><h3 class="title">J.2.4. Container boot</h3></div></div></div><div class="para">
+ When booting a domain using container based virtualization, instead of a kernel or boot image, a path to the init binary is required, using the init element. By default this will be launched with no arguments. To specify the initial argv, use the <code class="sgmltag-element">initarg</code> element, repeated as many times as required. The <code class="sgmltag-element">cmdline</code> element, provides an equivalent to <code class="filename">/proc/cmdline</code> but will not effect <code class="sgmltag-starttag"><initarg></code>.
+ </div><div class="figure" id="fig-op-sys-cont-boot"><div class="figure-contents"><pre class="programlisting">
+>
+ ...
+ <span class="perl_Keyword"><os></span>
+ <span class="perl_Keyword"><type></span>hvm<span class="perl_Keyword"></type></span>
+ <span class="perl_Keyword"><loader></span>/usr/lib/xen/boot/hvmloader<span class="perl_Keyword"></loader></span>
+ <span class="perl_Keyword"><kernel></span>/root/f8-i386-vmlinuz<span class="perl_Keyword"></kernel></span>
+ <span class="perl_Keyword"><initrd></span>/root/f8-i386-initrd<span class="perl_Keyword"></initrd></span>
+ <span class="perl_Keyword"><cmdline></span>console=ttyS0 ks=http://example.com/f8-i386/os/<span class="perl_Keyword"></cmdline></span>
+ <span class="perl_Keyword"><dtb></span>/root/ppc.dtb<span class="perl_Keyword"></dtb></span>
+ <span class="perl_Keyword"></os></span>
+ ...
+
+</pre></div><h6>Figure J.5. Container boot</h6></div><br class="figure-break" /></div></div><div class="section" id="sect-smbios-sys-info"><div class="titlepage"><div><div><h2 class="title">J.3. SMBIOS system information</h2></div></div></div><div class="para">
+ Some hypervisors allow control over what system information is presented to the guest (for example, SMBIOS fields can be populated by a hypervisor and inspected via the dmidecode command in the guest). The optional sysinfo element covers all such categories of information.
+ </div><div class="figure"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><os></span>
+ <span class="perl_Keyword"><smbios</span><span class="perl_Others"> mode=</span><span class="perl_String">'sysinfo'</span><span class="perl_Keyword">/></span>
+ ...
+ <span class="perl_Keyword"></os></span>
+ <span class="perl_Keyword"><sysinfo</span><span class="perl_Others"> type=</span><span class="perl_String">'smbios'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><bios></span>
+ <span class="perl_Keyword"><entry</span><span class="perl_Others"> name=</span><span class="perl_String">'vendor'</span><span class="perl_Keyword">></span>LENOVO<span class="perl_Keyword"></entry></span>
+ <span class="perl_Keyword"></bios></span>
+ <span class="perl_Keyword"><system></span>
+ <span class="perl_Keyword"><entry</span><span class="perl_Others"> name=</span><span class="perl_String">'manufacturer'</span><span class="perl_Keyword">></span>Fedora<span class="perl_Keyword"></entry></span>
+ <span class="perl_Keyword"><entry</span><span class="perl_Others"> name=</span><span class="perl_String">'vendor'</span><span class="perl_Keyword">></span>Virt-Manager<span class="perl_Keyword"></entry></span>
+ <span class="perl_Keyword"></system></span>
+ <span class="perl_Keyword"></sysinfo></span>
+ ...
+
+</pre></div><h6>Figure J.6. SMBIOS system information</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-starttag"><sysinfo></code> element has a mandatory attribute <code class="sgmltag-attribute">type</code> that determines the layout of sub-elements, and may be defined as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">smbios</code> - Sub-elements call out specific SMBIOS values, which will affect the guest if used in conjunction with the smbios sub-element of the os element. Each sub-element of sysinfo names a SMBIOS block, and within those elements can be a list of entry elements that describe a field within the block. The following blocks and entries are recognized:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">bios</code> - This is block 0 of SMBIOS, with entry names drawn from <code class="sgmltag-attribute">vendor</code>, <code class="sgmltag-attribute">version</code>, <code class="sgmltag-attribute">date</code>, and <code class="sgmltag-attribute">release</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><system></code> - This is block 1 of SMBIOS, with entry names drawn from <code class="sgmltag-attribute">manufacturer</code>, <code class="sgmltag-attribute">product</code>, <code class="sgmltag-attribute">version</code>, <code class="sgmltag-attribute">serial</code>, <code class="sgmltag-attribute">uuid</code>, <code class="sgmltag-attribute">sku</code>, and <code class="sgmltag-attribute">family</code>. If a <code class="sgmltag-attribute">uuid</code> entry is provided alongside a top-level uuid element, the two values must match.
+ </div></li></ul></div></li></ul></div></div><div class="section" id="sect-cpu-allocation"><div class="titlepage"><div><div><h2 class="title">J.4. CPU allocation</h2></div></div></div><div class="figure"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain></span>
+ ...
+ <span class="perl_Keyword"><vcpu</span><span class="perl_Others"> placement=</span><span class="perl_String">'static'</span><span class="perl_Others"> cpuset=</span><span class="perl_String">"1-4,^3,6"</span><span class="perl_Others"> current=</span><span class="perl_String">"1"</span><span class="perl_Keyword">></span>2<span class="perl_Keyword"></vcpu></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.7. CPU allocation</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-starttag"><cpu></code> element defines the maximum number of virtual CPUs allocated for the guest OS, which must be between 1 and the maximum supported by the hypervisor. This element can contain an optional <code class="sgmltag-attribute">cpuset</code> attribute, which is a comma-separated list of physical CPU numbers that domain process and virtual CPUs can be pinned to by default.
+ </div><div class="para">
+ Note that the pinning policy of domain process and virtual CPUs can be specified separately by using the <code class="sgmltag-attribute">cputune</code> attribute. If attribute <code class="sgmltag-attribute">emulatorpin</code> of <code class="sgmltag-starttag"><cputune></code> is specified, <code class="sgmltag-attribute">cpuset</code> specified by <code class="sgmltag-starttag"><vcpu></code> will be ingored.
+ </div><div class="para">
+ Similarly, virtual CPUs that have set a value for <code class="sgmltag-attribute">vcpupin</code> cause <code class="sgmltag-attribute">cpuset</code> settings to be ignored. For virtual CPUs where <code class="sgmltag-attribute">vcpupin</code> is not specified, it will be pinned to the physical CPUs specified by <code class="sgmltag-attribute">cpuset</code>. Each element in the <code class="sgmltag-attribute">cpuset</code> list is either a single CPU number, a range of CPU numbers, or a caret (^) followed by a CPU number to be excluded from a previous range. The sgmltagal attribute <code class="sgmltag-attribute">current</code> can be used to specify whether fewer than the maximum number of virtual CPUs should be enabled.
+ </div><div class="para">
+ The optional attribute <code class="sgmltag-attribute">placement</code> can be used to indicate the CPU placement mode for domain process, its value can be either <code class="sgmltag-attvalue">static</code> or <code class="sgmltag-attvalue">auto</code>, which defaults to <code class="sgmltag-attvalue">placement</code>, or <code class="sgmltag-attvalue">numatune</code>, or <code class="sgmltag-attvalue">static</code> if <code class="sgmltag-element">cpuset</code> is specified. <code class="sgmltag-attvalue">auto</code> indicates the domain process will be pinned to the advisory nodeset from querying numad, and the value of attribute <code class="sgmltag-attribute">cpuset</code> will be ignored if it's specified. If both <code class="sgmltag-attribute">cpuset</code> and <code class="sgmltag-attribute">placement</code> are not specified, or if placement is <code class="sgmltag-attvalue">static</code>, but no <code class="sgmltag-attribute">cpuset</code> is specified, the do
main process will be pinned to all the available physical CPUs.
+ </div></div><div class="section" id="sect-cpu-tuning"><div class="titlepage"><div><div><h2 class="title">J.5. CPU tuning</h2></div></div></div><div class="figure" id="fig-cpu-tuning"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain></span>
+ ...
+ <span class="perl_Keyword"><cputune></span>
+ <span class="perl_Keyword"><vcpupin</span><span class="perl_Others"> vcpu=</span><span class="perl_String">"0"</span><span class="perl_Others"> cpuset=</span><span class="perl_String">"1-4,^2"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><vcpupin</span><span class="perl_Others"> vcpu=</span><span class="perl_String">"1"</span><span class="perl_Others"> cpuset=</span><span class="perl_String">"0,1"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><vcpupin</span><span class="perl_Others"> vcpu=</span><span class="perl_String">"2"</span><span class="perl_Others"> cpuset=</span><span class="perl_String">"2,3"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><vcpupin</span><span class="perl_Others"> vcpu=</span><span class="perl_String">"3"</span><span class="perl_Others"> cpuset=</span><span class="perl_String">"0,4"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><emulatorpin</span><span class="perl_Others"> cpuset=</span><span class="perl_String">"1-3"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><shares></span>2048<span class="perl_Keyword"></shares></span>
+ <span class="perl_Keyword"><period></span>1000000<span class="perl_Keyword"></period></span>
+ <span class="perl_Keyword"><quota></span>-1<span class="perl_Keyword"></quota></span>
+ <span class="perl_Keyword"><emulator_period></span>1000000<span class="perl_Keyword"></emulator_period></span>
+ <span class="perl_Keyword"><emulator_quota></span>-1<span class="perl_Keyword"></emulator_quota></span>
+ <span class="perl_Keyword"></cputune></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.8. CPU tuning</h6></div><br class="figure-break" /><div class="para">
+ Although all are optional, the components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-cpu-turn-elem"><h6>Table J.5. CPU tuning elements</h6><div class="table-contents"><table summary="CPU tuning elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><cputune></code>
+ </td><td class="">
+ Provides details regarding the CPU tunable parameters for the domain. This is optional.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><vcpupin></code>
+ </td><td class="">
+ Specifies which of host's physical CPUs the domain VCPU will be pinned to. If this is omitted, and attribute <code class="sgmltag-attribute">cpuset</code> of element <code class="sgmltag-starttag"><vcpu></code> is not specified, the vCPU is pinned to all the physical CPUs by default. It contains two required attributes, the attribute <code class="sgmltag-element">vcpu</code> specifies <code class="sgmltag-attribute">id</code>, and the attribute <code class="sgmltag-attribute">cpuset</code> is same as attribute <code class="sgmltag-attribute">cpuset</code> of element <code class="sgmltag-starttag"><vCPU></code>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><emulatorpin></code>
+ </td><td class="">
+ Specifies which of the host physical CPUs, the "emulator", a subset of a domains not including vcpu, will be pinned to. If this is omitted, and attribute <code class="sgmltag-attribute">cpuset</code> of element <code class="sgmltag-starttag"><vcpu></code> is not specified, the "emulator" is pinned to all the physical CPUs by default. It contains one required attribute <code class="sgmltag-attribute">cpuset</code> specifying which physical CPUs to pin to. <code class="sgmltag-element">emulatorpin</code> is not allowed if attribute <code class="sgmltag-attribute">placement</code> of element <code class="sgmltag-starttag"><vcpu></code> is <code class="sgmltag-attvalue">auto</code>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><shares></code>
+ </td><td class="">
+ Specifies the proportional weighted share for the domain. If this is omitted, it defaults to the OS provided defaults. If there is no unit for the value, itn is calculated relative to the setting of other guest virtual machines. For example, if a guest virtual machine is configured with value 2048 will get twice as much CPU time as a guest virtual machine configured with value 1024.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><period></code>
+ </td><td class="">
+ Specifies the enforcement intervalin microseconds. By using <code class="sgmltag-attribute">period</code>, each of the domain's vcpu will not be allowed to consume more than its alloted quota worth of runtime. This value should be within the following range: <code class="literal">1000-1000000</code>. A <code class="sgmltag-attribute">period></code> with a value of <code class="sgmltag-attvalue">0</code> means no value.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><quota></code>
+ </td><td class="">
+ Specifies the maximum allowed bandwidth in microseconds. A domain with <code class="sgmltag-element">quota</code> as any negative value indicates that the domain has infinite bandwidth, which means that it is not bandwidth controlled. The value should be within the following range:<code class="sgmltag-attvalue">1000 - 18446744073709551</code> or less than <code class="sgmltag-attvalue">0</code>. A <code class="sgmltag-attribute">quota</code> with value of <code class="sgmltag-attvalue">0</code> means no value. You can use this feature to ensure that all vcpus run at the same speed.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><emulator_period></code>
+ </td><td class="">
+ Specifies the enforcement interval in microseconds. Within an <code class="sgmltag-starttag"><emulator_period></code>, emulator threads (those excluding vcpus) of the domain will not be allowed to consume more than the <code class="sgmltag-starttag"><emulator_quota></code> worth of runtime. The <code class="sgmltag-starttag"><emulator_period></code> value should be in the following range: <code class="sgmltag-attvalue">1000 - 1000000</code>. An <code class="sgmltag-starttag"><emulator_period></code> with value of <code class="sgmltag-attvalue">0</code>, means no value.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><emulator_quota></code>
+ </td><td class="">
+ Specifies the maximum allowed bandwidth in microseconds for the domain's emulator threads (those excluding vcpus). A domain with an <code class="sgmltag-starttag"><emulator_quota></code> as a negative value indicates that the domain has infinite bandwidth for emulator threads (those excluding vcpus), which means that it is not bandwidth controlled. The value should be in the following range: <code class="sgmltag-attvalue">1000 - 18446744073709551</code>, or less than <code class="sgmltag-attvalue">0</code>. An <code class="sgmltag-starttag"><emulator_quota></code> with value <code class="sgmltag-attvalue">0</code> means no value.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sect-mem-back"><div class="titlepage"><div><div><h2 class="title">J.6. Memory backing</h2></div></div></div><div class="para">
+ Memory backing allows the hypervisor to properly manage large pages within the guest. Once confured the following domain XML is effected:
+ </div><div class="figure" id="fig-mem-back"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain></span>
+ ...
+ <span class="perl_Keyword"><memoryBacking></span>
+ <span class="perl_Keyword"><hugepages/></span>
+ <span class="perl_Keyword"></memoryBacking></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.9. Memory backing</h6></div><br class="figure-break" /><div class="para">
+ The optional <code class="sgmltag-starttag"><memoryBacking></code> element, may have an <code class="sgmltag-starttag"><hugepages></code> element set within it. This tells the hypervisor that the guest should have its memory allocated using hugepages instead of the normal native page size.
+ </div></div><div class="section" id="sect-libvirt-dom-xml-mem-tuning"><div class="titlepage"><div><div><h2 class="title">J.7. Memory tuning</h2></div></div></div><div class="figure" id="fig-dom-xml-mem-tuning"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain></span>
+ ...
+ <span class="perl_Keyword"><memtune></span>
+ <span class="perl_Keyword"><hard_limit</span><span class="perl_Others"> unit=</span><span class="perl_String">'G'</span><span class="perl_Keyword">></span>1<span class="perl_Keyword"></hard_limit></span>
+ <span class="perl_Keyword"><soft_limit</span><span class="perl_Others"> unit=</span><span class="perl_String">'M'</span><span class="perl_Keyword">></span>128<span class="perl_Keyword"></soft_limit></span>
+ <span class="perl_Keyword"><swap_hard_limit</span><span class="perl_Others"> unit=</span><span class="perl_String">'G'</span><span class="perl_Keyword">></span>2<span class="perl_Keyword"></swap_hard_limit></span>
+ <span class="perl_Keyword"><min_guarantee</span><span class="perl_Others"> unit=</span><span class="perl_String">'bytes'</span><span class="perl_Keyword">></span>67108864<span class="perl_Keyword"></min_guarantee></span>
+ <span class="perl_Keyword"></memtune></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.10. Memory tuning</h6></div><br class="figure-break" /><div class="para">
+ Although all are optional, the components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-mem-tun-elem"><h6>Table J.6. Memory tuning elements</h6><div class="table-contents"><table summary="Memory tuning elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><memtune></code>
+ </td><td class="">
+ Provides details regarding the memory tunable parameters for the domain. If this is omitted, it defaults to the OS provided defaults. The parameters are applied to the process as a whole therefore when setting limits, one needs to add up guest RAM, guest video RAM, and allow for some memory overhead. The last piece is hard to determine so one use trial and error. For each tunable, it is possible to designate which unit the number is in on input, using the same values as for <code class="sgmltag-starttag"><memory></code>. For backwards compatibility, output is always in KiB.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><hard_limit></code>
+ </td><td class="">
+ This is the maximum memory the guest can use. The <code class="sgmltag-attribute">unit</code> for this value is expressed in <code class="literal">kibibytes</code> (i.e. blocks of 1024 bytes)
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><soft_limit></code>
+ </td><td class="">
+ This is the memory limit to enforce during memory contention. The <code class="sgmltag-attribute">unit</code> for this value is expressed in kibibytes (i.e. blocks of 1024 bytes)
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><swap_hard_limit></code>
+ </td><td class="">
+ This is the maximum memory plus swap the guest can use. The <code class="sgmltag-attribute">unit</code> for this value is expressed in kibibytes (i.e. blocks of 1024 bytes). This has to be more than <code class="sgmltag-starttag"><hard_limit></code> value provided
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><min_guarantee></code>
+ </td><td class="">
+ This is the guaranteed minimum memory allocation for the guest. The units for this value is expressed in kibibytes (i.e. blocks of 1024 bytes)
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sect-libvirt-dom-xml-numa-node-tuning"><div class="titlepage"><div><div><h2 class="title">J.8. NUMA node tuning</h2></div></div></div><div class="para">
+ Once NUMA node tuning is done using conventional managment tools the following domain XML parameters are effected:
+ </div><div class="figure" id="fig-dom-xml-numa-node-tuning"><div class="figure-contents"><pre class="programlisting">
+>
+<span class="perl_Keyword"><domain></span>
+ ...
+ <span class="perl_Keyword"><numatune></span>
+ <span class="perl_Keyword"><memory</span><span class="perl_Others"> mode=</span><span class="perl_String">"strict"</span><span class="perl_Others"> nodeset=</span><span class="perl_String">"1-4,^3"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></numatune></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.11. NUMA node tuning</h6></div><br class="figure-break" /><div class="para">
+ Although all are optional, the components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-numa-tun-elem"><h6>Table J.7. NUMA node tuning elements</h6><div class="table-contents"><table summary="NUMA node tuning elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><numatune></code>
+ </td><td class="">
+ Provides details of how to tune the performance of a NUMA host via controlling NUMA policy for domain process.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><memory></code>
+ </td><td class="">
+ Specifies how to allocate memory for the domain process on a NUMA host. It contains several optional attributes. Attribute <code class="sgmltag-attribute">mode</code> is either <code class="sgmltag-attvalue">interleave</code>, <code class="sgmltag-attvalue">strict</code>, or <code class="sgmltag-attvalue">preferred</code>. If no value is given it defaults to <code class="sgmltag-attvalue">strict</code>. Attribute <code class="sgmltag-attribute">nodeset</code> specifies the NUMA nodes, using the same syntax as attribute <code class="sgmltag-attribute">cpuset</code> of element <code class="sgmltag-starttag"><vcpu></code>. Attribute <code class="sgmltag-attribute">placement</code> can be used to indicate the memory placement mode for the domain process. Its value can be either <code class="sgmltag-attvalue">static</code> or <code class="sgmltag-attvalue">auto</code>. If attribute <code class="sgmltag-starttag"><nodeset></code> is specified it defaults to the
<code class="sgmltag-starttag"><placement></code> of <code class="sgmltag-starttag"><vcpu></code>, or <code class="sgmltag-attvalue">static</code>. <code class="sgmltag-attvalue">auto</code> indicates the domain process will only allocate memory from the advisory nodeset returned from querying numad and the value of attribute nodeset will be ignored if it's specified. If attribute <code class="sgmltag-attribute">placement</code> of <code class="sgmltag-element">vcpu</code> is <code class="sgmltag-attvalue">auto</code>, and attribute <code class="sgmltag-starttag"><numatune></code> is not specified, a default numatune with <code class="sgmltag-starttag"><placement></code> <code class="sgmltag-attvalue">auto</code> and mode <code class="sgmltag-attvalue">strict</code> will be added implicitly.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sect-libvirt-dom-xml-blk-io-tuning"><div class="titlepage"><div><div><h2 class="title">J.9. Block I/O tuning</h2></div></div></div><div class="figure" id="fig-blk-io-tuning"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain></span>
+ ...
+ <span class="perl_Keyword"><blkiotune></span>
+ <span class="perl_Keyword"><weight></span>800<span class="perl_Keyword"></weight></span>
+ <span class="perl_Keyword"><device></span>
+ <span class="perl_Keyword"><path></span>/dev/sda<span class="perl_Keyword"></path></span>
+ <span class="perl_Keyword"><weight></span>1000<span class="perl_Keyword"></weight></span>
+ <span class="perl_Keyword"></device></span>
+ <span class="perl_Keyword"><device></span>
+ <span class="perl_Keyword"><path></span>/dev/sdb<span class="perl_Keyword"></path></span>
+ <span class="perl_Keyword"><weight></span>500<span class="perl_Keyword"></weight></span>
+ <span class="perl_Keyword"></device></span>
+ <span class="perl_Keyword"></blkiotune></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.12. Block I/O tuning</h6></div><br class="figure-break" /><div class="para">
+ Although all are optional, the components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-blk-io-elem"><h6>Table J.8. Block I/O tuning elements</h6><div class="table-contents"><table summary="Block I/O tuning elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><blkiotune></code>
+ </td><td class="">
+ This optional element provides the ability to tune Blkio cgroup tunable parameters for the domain. If this is omitted, it defaults to the OS provided defaults.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><weight></code>
+ </td><td class="">
+ This optional weight element is the overall I/O weight of the guest. The value should be within the range 100 - 1000.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><device></code>
+ </td><td class="">
+ The domain may have multiple <code class="sgmltag-starttag"><device></code> elements that further tune the weights for each host block device in use by the domain. Note that multiple guest disks can share a single host block device. In addition, as they are backed by files within the same host file system, this tuning parameter is at the global domain level, rather than being associated with each guest disk device (contrast this to the <code class="sgmltag-starttag"><iotune></code> element which can be applied to a single <code class="sgmltag-starttag"><disk></code>). Each device element has two mandatory sub-elements, <code class="sgmltag-starttag"><path></code> describing the absolute path of the device, and <code class="sgmltag-starttag"><weight></code> giving the relative weight of that device, which has an acceptable range of 100 - 1000.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sect-libvirt-dom-xml-res-part"><div class="titlepage"><div><div><h2 class="title">J.10. Resource partitioning</h2></div></div></div><div class="para">
+ Hypervisors may allow for virtual machines to be placed into resource partitions, potentially with nesting of said partitions. The <code class="sgmltag-starttag"><resource></code> element groups together configuration related to resource partitioning. It currently supports a child element partition whose content defines the path of the resource partition in which to place the domain. If no partition is listed, then the domain will be placed in a default partition. It is the responsibility of the app/admin to ensure that the partition exists prior to starting the guest. Only the (hypervisor specific) default partition can be assumed to exist by default.
+ </div><div class="figure" id="fig-res-part"><div class="figure-contents"><pre class="programlisting">
+
+
+ ...
+ <span class="perl_Keyword"><resource></span>
+ <span class="perl_Keyword"><partition></span>/virtualmachines/production<span class="perl_Keyword"></partition></span>
+ <span class="perl_Keyword"></resource></span>
+ ...
+
+</pre></div><h6>Figure J.13. Resource partitioning</h6></div><br class="figure-break" /><div class="para">
+ Resource partitions are currently supported by the QEMU and LXC drivers, which map partition paths to cgroups directories in all mounted controllers.
+ </div></div><div class="section" id="sect-libvirt-dom-xml-cpu-model-top"><div class="titlepage"><div><div><h2 class="title">J.11. CPU model and topology</h2></div></div></div><div class="para">
+ This section covers the requirements for CPU model. Its features and topology is specified using the following elements from the domain XML:
+ </div><div class="figure" id="fig-xml-cpu-model-top"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><cpu</span><span class="perl_Others"> match=</span><span class="perl_String">'exact'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><model</span><span class="perl_Others"> fallback=</span><span class="perl_String">'allow'</span><span class="perl_Keyword">></span>core2duo<span class="perl_Keyword"></model></span>
+ <span class="perl_Keyword"><vendor></span>Intel<span class="perl_Keyword"></vendor></span>
+ <span class="perl_Keyword"><topology</span><span class="perl_Others"> sockets=</span><span class="perl_String">'1'</span><span class="perl_Others"> cores=</span><span class="perl_String">'2'</span><span class="perl_Others"> threads=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><feature</span><span class="perl_Others"> policy=</span><span class="perl_String">'disable'</span><span class="perl_Others"> name=</span><span class="perl_String">'lahf_lm'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></cpu></span>
+ ...
+
+</pre></div><h6>Figure J.14. CPU model and topology example 1</h6></div><br class="figure-break" /><div class="figure" id="fig-xml-cpu-model-top2"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><cpu</span><span class="perl_Others"> mode=</span><span class="perl_String">'host-model'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><model</span><span class="perl_Others"> fallback=</span><span class="perl_String">'forbid'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><topology</span><span class="perl_Others"> sockets=</span><span class="perl_String">'1'</span><span class="perl_Others"> cores=</span><span class="perl_String">'2'</span><span class="perl_Others"> threads=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+<span class="perl_Keyword"></cpu></span>
+ ...
+</pre></div><h6>Figure J.15. CPU model and topology example 2</h6></div><br class="figure-break" /><div class="figure" id="fig-xml-cpu-model-top3"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><cpu</span><span class="perl_Others"> mode=</span><span class="perl_String">'host-passthrough'</span><span class="perl_Keyword">/></span>
+
+</pre></div><h6>Figure J.16. CPU model and topology example 3</h6></div><br class="figure-break" /><div class="para">
+ In cases where no restrictions are to be put on either the CPU model nor its features, a simpler cpu element such as the following may be used.
+ </div><div class="figure" id="fig-xml-cpu-model-top4"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><cpu></span>
+ <span class="perl_Keyword"><topology</span><span class="perl_Others"> sockets=</span><span class="perl_String">'1'</span><span class="perl_Others"> cores=</span><span class="perl_String">'2'</span><span class="perl_Others"> threads=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></cpu></span>
+ ...
+
+</pre></div><h6>Figure J.17. CPU model and topology example 4</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-cpu-model-elem"><h6>Table J.9. CPU model and topology elements</h6><div class="table-contents"><table summary="CPU model and topology elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><cpu></code>
+ </td><td class="">
+ This is the main container for describing guest CPU requirements.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><match></code>
+ </td><td class="">
+ Specifies how the virtual CPU is provided to the guest match for these requirements. The <code class="sgmltag-attribute">match</code> attribute can be omitted if topology is the only element within <code class="sgmltag-starttag"><cpu></code>. Possible values for the <code class="sgmltag-attribute">match</code> attribute are:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">minimum</code> - the specified CPU model and features describes the minimum requested CPU.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">exact</code> - the virtual CPU provided to the guest will exactly match the specification
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">strict</code> - the guest will not be created unless the host CPU exactly matches the specification.
+ </div></li></ul></div>
+ Note that the <code class="sgmltag-attribute">match</code> attribute can be omitted and will default to <code class="sgmltag-attvalue">exact</code>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><mode></code>
+ </td><td class="">
+ This optional attribute may be used to make it easier to configure a guest CPU to be as close to the host CPU as possible. Possible values for the mode attribute are:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">custom</code> - describes how the CPU is presented to the guest. This is the default setting when the <code class="sgmltag-attribute">mode</code> attribute is not specified. This mode makes it so that a persistent guest will see the same hardware no matter what host the guest is booted on.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">host-model</code> - this is essentially a shortcut to copying host CPU definition from the capabilities XML into the domain XML. As the CPU definition is copied just before starting a domain, the same XML can be used on different hosts while still providing the best guest CPU each host supports. Neither the <code class="sgmltag-attribute">match</code> attribute nor any feature elements can be used in this mode. For more information see <a href="http://libvirt.org/formatdomain.html">libvirt domain XML CPU models</a>
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">host-passthrough</code> With this mode, the CPU visible to the guest is exactly the same as the host CPU including elements that cause errors within libvirt. The obvious the downside of this mode is that the guest environment cannot be reproduced on different hardware and therefore this mode is recommended with great caution. Neither <code class="sgmltag-element">model</code> nor <code class="sgmltag-element">feature</code> elements are allowed in this mode.
+ </div></li><li class="listitem"><div class="para">
+ Note that in both <code class="sgmltag-element">host-model</code> and <code class="sgmltag-element">host-passthrough</code> mode, the real (approximate in host-passthrough mode) CPU definition which would be used on current host can be determined by specifying VIR_DOMAIN_XML_UPDATE_CPU flag when calling virDomainGetXMLDesc API. When running a guest that might be prone to operating system reactivation when presented with different hardware, and which will be migrated between hosts with different capabilities, you can use this output to rewrite XML to the custom mode for more robust migration.
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><model></code>
+ </td><td class="">
+ Specifies CPU model requested by the guest. The list of available CPU models and their definition can be found in <code class="filename">cpu_map.xml</code> file installed in libvirt's data directory. If a hypervisor is not able to use the exact CPU model, libvirt automatically falls back to a closest model supported by the hypervisor while maintaining the list of CPU features. An optional <code class="sgmltag-attribute">fallback</code> attribute can be used to forbid this behavior, in which case an attempt to start a domain requesting an unsupported CPU model will fail. Supported values for fallback attribute are: <code class="sgmltag-attvalue">allow</code> (this is the default), and <code class="sgmltag-attvalue">forbid</code>. The optional <code class="sgmltag-attribute">vendor_id</code> attribute can be used to set the vendor id seen by the guest. It must be exactly 12 characters long. If not set, the vendor id of the host is used. Typical possible values are <code
class="sgmltag-attvalue">AuthenticAMD</code> and <code class="sgmltag-attvalue">GenuineIntel</code>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><vendor></code>
+ </td><td class="">
+ Specifies CPU vendor requested by the guest. If this element is missing, the guest runs on a CPU matching given features regardless of its vendor. The list of supported vendors can be found in <code class="filename">cpu_map.xml</code>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><topology></code>
+ </td><td class="">
+ Specifies requested topology of virtual CPU provided to the guest. Three non-zero values have to be given for sockets, cores, and threads: total number of CPU sockets, number of cores per socket, and number of threads per core, respectively.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><feature></code>
+ </td><td class="">
+ Can contain zero or more elements used to fine-tune features provided by the selected CPU model. The list of known feature names can be found in the same file as CPU models. The meaning of each feature element depends on its policy attribute, which has to be set to one of the following values:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">force</code> - forces the virtual to be supported regardless of whether it is actually supported by host CPU.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">require</code> - dictates that guest creation will fail unless the feature is supported by host CPU. This is the default setting
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">optional</code> - this feature is supported by virtual CPU but and only if it is supported by host CPU.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">disable</code> - this is not supported by virtual CPU.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">forbid</code> - guest creation will fail if the feature is supported by host CPU.
+ </div></li></ul></div>
+
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="section" id="sub-sect-libvirt-dom-xml-res-part-guest-numa"><div class="titlepage"><div><div><h3 class="title">J.11.1. Guest NUMA topology</h3></div></div></div><div class="para">
+ Guest NUMA topology can be specifed using the numa element and the following from the domain XML:
+ </div><div class="figure" id="fig-xml-cpu-model-top-numa"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><cpu></span>
+ ...
+ <span class="perl_Keyword"><numa></span>
+ <span class="perl_Keyword"><cell</span><span class="perl_Others"> cpus=</span><span class="perl_String">'0-3'</span><span class="perl_Others"> memory=</span><span class="perl_String">'512000'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><cell</span><span class="perl_Others"> cpus=</span><span class="perl_String">'4-7'</span><span class="perl_Others"> memory=</span><span class="perl_String">'512000'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></numa></span>
+ ...
+ <span class="perl_Keyword"></cpu></span>
+ ...
+</pre></div><h6>Figure J.18. Guest NUMA topology</h6></div><br class="figure-break" /><div class="para">
+ Each cell element specifies a NUMA cell or a NUMA node. <code class="sgmltag-attribute">cpus</code> specifies the CPU or range of CPUs that are part of the node. <code class="sgmltag-attribute">memory</code> specifies the node memory in kibibytes (i.e. blocks of 1024 bytes). Each cell or node is assigned <code class="sgmltag-attribute">cellid</code> or <code class="sgmltag-attribute">nodeid</code> in increasing order starting from 0.
+ </div></div></div><div class="section" id="sect-libvirt-dom-xml-event-config"><div class="titlepage"><div><div><h2 class="title">J.12. Events configuration</h2></div></div></div><div class="para">
+ Using the following sections of domain XML it is possible to override the default actions taken on various events.
+ </div><div class="figure" id="fig-xml-cpu-model-events-config"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><on_poweroff></span>destroy<span class="perl_Keyword"></on_poweroff></span>
+ <span class="perl_Keyword"><on_reboot></span>restart<span class="perl_Keyword"></on_reboot></span>
+ <span class="perl_Keyword"><on_crash></span>restart<span class="perl_Keyword"></on_crash></span>
+ <span class="perl_Keyword"><on_lockfailure></span>poweroff<span class="perl_Keyword"></on_lockfailure></span>
+ ..
+
+</pre></div><h6>Figure J.19. Events Configuration</h6></div><br class="figure-break" /><div class="para">
+ The following collections of elements allow the actions to be specified when a guest OS triggers a lifecycle operation. A common use case is to force a reboot to be treated as a poweroff when doing the initial OS installation. This allows the VM to be re-configured for the first post-install bootup.
+ </div><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-event-config-elem"><h6>Table J.10. Event configurtation elements</h6><div class="table-contents"><table summary="Event configurtation elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ State
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><on_poweroff></code>
+ </td><td class="">
+ Specifies the action that is to be executed when the guest requests a poweroff. Four possible arguements are possible:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">destroy</code> - this action terminates the domain completely and releases all resources
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">restart</code> - this action terminates the domain completely and restarts it with the same configuration
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">preserve</code> - this action terminates the domain completely but and its resources are preserved to allow for future analysis.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">rename-restart</code> - this action terminates the domain completely and then restarts it with a new name
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><on_reboot></code>
+ </td><td class="">
+ Specifies the action that is to be executed when the guest requests a reboot.Four possible arguements are possible:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">destroy</code> - this action terminates the domain completely and releases all resources
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">restart</code> - this action terminates the domain completely and restarts it with the same configuration
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">preserve</code> - this action terminates the domain completely but and its resources are preserved to allow for future analysis.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">rename-restart</code> - this action terminates the domain completely and then restarts it with a new name
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><on_crash></code>
+ </td><td class="">
+ Specifies the action that is to be executed when the guest crashes. In addition, it supports these additional actions:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">coredump-destroy</code> - the crashed domain's core is dumped, domain is terminated completely, and all resources are released.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">coredump-restart</code> - the crashed domain's core is dumped, and the domain is restarted with the same configuration settings
+ </div></li></ul></div>
+ Four possible arguements are possible:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">destroy</code> - this action terminates the domain completely and releases all resources
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">restart</code> - this action terminates the domain completely and restarts it with the same configuration
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">preserve</code> - this action terminates the domain completely but and its resources are preserved to allow for future analysis.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">rename-restart</code> - this action terminates the domain completely and then restarts it with a new name
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><on_lockfailure></code>
+ </td><td class="">
+ Specifies what action should be taken when a lock manager loses resource locks. The following actions are recognized by libvirt, although not all of them need to be supported by individual lock managers. When no action is specified, each lock manager will take its default action. The following arguements are possible:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">poweroff</code> - forcefully powers off the domain
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">restart</code> - restarts the domain to reacquire its locks.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">pause</code> - pauses the domain so that it can be manually resumed when lock issues are solved.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">ignore</code> - keeps the domain running as if nothing happened.
+ </div></li></ul></div>
+
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sect-libvirt-dom-xml-pwr-man"><div class="titlepage"><div><div><h2 class="title">J.13. Power Management</h2></div></div></div><div class="para">
+ It is possible to forcibly enable or disable BIOS advertisements to the guest OS using conventional management tools which effects the following section of the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-pwr-man"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><pm></span>
+ <span class="perl_Keyword"><suspend-to-disk</span><span class="perl_Others"> enabled=</span><span class="perl_String">'no'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><suspend-to-mem</span><span class="perl_Others"> enabled=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></pm></span>
+ ...
+
+</pre></div><h6>Figure J.20. Power Management</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-starttag"><pm></code> element can be enabled using the arguement <code class="sgmltag-attvalue">yes</code> or disabled using the arguement <code class="sgmltag-attvalue">no</code>. BIOS support can be implemented for S3 using the arguement <code class="sgmltag-attribute">suspend-to-disk</code> and S4 using the arguement <code class="sgmltag-attribute">suspend-to-mem</code> ACPI sleep states. If nothing is specified, the hypervisor will be left with its default value.
+ </div></div><div class="section" id="idm83056320"><div class="titlepage"><div><div><h2 class="title" id="idm83056320">J.14. Hypervisor features</h2></div></div></div><div class="para">
+ Hypervisors may allow certain CPU / machine features to be enabled (<code class="sgmltag-attvalue">state='on')</code> or disabled (<code class="sgmltag-attvalue">state='off'</code>).
+ </div><div class="figure" id="fig-libvirt-dom-xml-hypr-feat"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><features></span>
+ <span class="perl_Keyword"><pae/></span>
+ <span class="perl_Keyword"><acpi/></span>
+ <span class="perl_Keyword"><apic/></span>
+ <span class="perl_Keyword"><hap/></span>
+ <span class="perl_Keyword"><privnet/></span>
+ <span class="perl_Keyword"><hyperv></span>
+ <span class="perl_Keyword"><relaxed</span><span class="perl_Others"> state=</span><span class="perl_String">'on'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></hyperv></span>
+ <span class="perl_Keyword"></features></span>
+ ...
+
+</pre></div><h6>Figure J.21. Hypervisor features</h6></div><br class="figure-break" /><div class="para">
+ All features are listed within the <code class="sgmltag-starttag"><features></code> element, if a <code class="sgmltag-starttag"><state></code> is not specified it is disabled. The available features can be found by calling the <code class="filename">capabilities</code> XML, but a common set for fully virtualized domains are:
+ </div><div class="table" id="table-libvirt-dom-xml-hyp-feat-elem"><h6>Table J.11. Hypervisor features elements</h6><div class="table-contents"><table summary="Hypervisor features elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ State
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><pae></code>
+ </td><td class="">
+ Physical address extension mode allows 32-bit guests to address more than 4 GB of memory.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><acpi></code>
+ </td><td class="">
+ Useful for power management, for example, with KVM guests it is required for graceful shutdown to work.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><apic></code>
+ </td><td class="">
+ Allows the use of programmable IRQ management. For this element, there is an optional attribute <code class="sgmltag-attribute">eoi</code> with values <code class="sgmltag-attvalue">on</code> and <code class="sgmltag-attvalue">off</code> which sets the availability of EOI (End of Interrupt) for the guest.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><hap></code>
+ </td><td class="">
+ Enables the use of Hardware Assisted Paging if it is available in the hardware.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">hyperv</code>
+ </td><td class="">
+ Enables various features to improve the behavior of guests running Microsoft Windows. Using the optional attribute <code class="sgmltag-attribute">relaxed</code> with values <code class="sgmltag-attvalue">on</code> or <code class="sgmltag-attvalue">off</code> enables or disables the relax constraints on timers
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sect-libvirt-dom-xml-time-keep"><div class="titlepage"><div><div><h2 class="title">J.15. Time keeping</h2></div></div></div><div class="para">
+ The guest clock is typically initialized from the host clock. Most operating systems expect the hardware clock to be kept in UTC, which is the default setting. Note that for Windows guests the guest must be set in <code class="sgmltag-attvalue">localtime</code>.
+ </div><div class="figure" id="fig-libvirt-dom-xml-time-keep"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><clock</span><span class="perl_Others"> offset=</span><span class="perl_String">'localtime'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><timer</span><span class="perl_Others"> name=</span><span class="perl_String">'rtc'</span><span class="perl_Others"> tickpolicy=</span><span class="perl_String">'catchup'</span><span class="perl_Others"> track=</span><span class="perl_String">'guest'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><catchup</span><span class="perl_Others"> threshold=</span><span class="perl_String">'123'</span><span class="perl_Others"> slew=</span><span class="perl_String">'120'</span><span class="perl_Others"> limit=</span><span class="perl_String">'10000'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></timer></span>
+ <span class="perl_Keyword"><timer</span><span class="perl_Others"> name=</span><span class="perl_String">'pit'</span><span class="perl_Others"> tickpolicy=</span><span class="perl_String">'delay'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></clock></span>
+ ...
+
+</pre></div><h6>Figure J.22. Time keeping</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-time-keep-elem"><h6>Table J.12. Time keeping elements</h6><div class="table-contents"><table summary="Time keeping elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ State
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><clock></code>
+ </td><td class="">
+ The <code class="sgmltag-attribute">offset</code> attribute takes four possible values, allowing for fine grained control over how the guest clock is synchronized to the host. Note that hypervisors are not required to support all policies across all time sources <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">utc</code> - Synchronizes the clock to UTC when booted. <code class="sgmltag-attvalue">utc</code> mode can be converted to <code class="sgmltag-attvalue">variable</code> mode, which can be controlled by using the adjustment attribute. If the value is <code class="sgmltag-attvalue">reset</code>, the conversion is not done. A numeric value forces the conversion to <code class="sgmltag-attvalue">variable</code> mode using the value as the initial adjustment. The default adjustment is hypervisor specific.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">localtime</code> - Synchronizes the guest clock with the host's configured timezone when booted. The adjustment attribute behaves the same as in 'utc' mode.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">timezone</code> - Synchronizes the guest clock to the requested timezone using the timezone attribute.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">variable</code> - Gives the guest clock an arbitrary offset applied relative to UTC or localtime, depending on the basis attribute. The delta relative to UTC (or localtime) is specified in seconds, using the <code class="sgmltag-attribute">adjustment</code> attribute. The guest is free to adjust the RTC over time and expect that it will be honored at next reboot. This is in contrast to <code class="sgmltag-attvalue">utc</code> and <code class="sgmltag-attvalue">localtime</code> mode (with the optional attribute <code class="sgmltag-attvalue">adjustment='reset'</code>), where the RTC adjustments are lost at each reboot. In addition the <code class="sgmltag-attribute">basis</code> attribute can be either <code class="sgmltag-attvalue">utc</code> (default) or <code class="sgmltag-attvalue">localtime</code>. The <code class="sgmltag-element">clock</code> element may have zero or more <code class="sgmltag-starttag"><timer></code> ele
ments.
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><timer></code>
+ </td><td class="">
+ See Note
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><frequency></code>
+ </td><td class="">
+ This is an unsigned integer specifying the frequency at which <code class="sgmltag-attribute">name</code>=<code class="sgmltag-attvalue">"tsc"</code> runs.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><mode></code>
+ </td><td class="">
+ The <code class="sgmltag-attribute">mode</code> attribute controls how the <code class="sgmltag-attvalue">name="tsc"</code> <code class="sgmltag-starttag"><timer></code> is managed, and can be set to: <code class="sgmltag-attvalue">auto</code>, <code class="sgmltag-attvalue">native</code>, <code class="sgmltag-attvalue">emulate</code>, <code class="sgmltag-attvalue">paravirt</code>, or <code class="sgmltag-attvalue">smpsafe</code>. Other timers are always emulated.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><present></code>
+ </td><td class="">
+ Specifies whether a particular timer is available to the guest. Can be set to <code class="sgmltag-attvalue">yes</code> or <code class="sgmltag-attvalue">no</code>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="note"><div class="admonition_header"><h2>Additional information about the <code class="sgmltag-starttag"><timer></code> element</h2></div><div class="admonition"><div class="para">
+ Each <code class="sgmltag-starttag"><timer></code> element must contain a <code class="sgmltag-attribute">name</code> attribute, and may have the following attributes depending on the name specified.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><name></code> - selects which <code class="sgmltag-element">timer</code> is being modified. The following values are acceptable:<code class="sgmltag-attvalue">platform</code>, <code class="sgmltag-attvalue">hpet</code>, <code class="sgmltag-attvalue">kvmclock</code>, <code class="sgmltag-attvalue">pit</code>, <code class="sgmltag-attvalue">rtc</code>, or <code class="sgmltag-attvalue">tsc</code>.
+ </div></li><li class="listitem"><div class="para">
+ track - specifies the timer track. The following values are acceptable: <code class="sgmltag-attvalue">boot</code>, <code class="sgmltag-attvalue">guest</code>, or <code class="sgmltag-attvalue">wall</code>. <code class="sgmltag-element">track</code> is only valid for <code class="sgmltag-attvalue">name="rtc"</code> or <code class="sgmltag-attvalue">name="platform"</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-element">tickpolicy</code> - determines what happens whens the deadline for injecting a tick to the guest is missed. The following values can be assigned:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">delay</code> -will continue to deliver ticks at the normal rate. The guest time will be delayed due to the late tick
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">catchup</code> - delivers ticks at a higher rate in order to catch up with the missed tick. The guest time is not displayed once catchup is complete. In addition, there can be three optional attributes, each a positive integer, as follows: threshold, slew, and limit.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">merge</code> - merges the missed tick(s) into one tick and injects them. The guest time may be delayed, depending on how the merge is done.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">discard</code> - throws away the missed tick(s) and continues with future injection at its default interval setting. The guest time may be delayed, unless the there is an explicit statement for handling lost ticks
+ </div></li></ul></div></li></ul></div></div></div></div><div class="section" id="sect-libvirt-dom-xml-devices"><div class="titlepage"><div><div><h2 class="title">J.16. Devices</h2></div></div></div><div class="para">
+ This set of XML elements are all used to describe devices provided to the guest domain. All of the devices below are indicated as children of the main devices element.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><emulator></span>/usr/lib/xen/bin/qemu-dm<span class="perl_Keyword"></emulator></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.23. Devices - child elements</h6></div><br class="figure-break" /><div class="para">
+ The contents of the <code class="sgmltag-starttag"><emulator></code> element specify the fully qualified path to the device model emulator binary. The capabilities XML specifies the recommended default emulator to use for each particular domain type or architecture combination.
+ </div><div class="section" id="sub-sect-libvirt-dom-xml-devices"><div class="titlepage"><div><div><h3 class="title">J.16.1. Hard drives, floppy disks, CDROMs</h3></div></div></div><div class="para">
+ This section of the domain XML specifies any device that looks like a disk, be it a floppy, harddisk, cdrom, or paravirtualized driver is specified via the disk element.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-cds"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'file'</span><span class="perl_Others"> snapshot=</span><span class="perl_String">'external'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">"tap"</span><span class="perl_Others"> type=</span><span class="perl_String">"aio"</span><span class="perl_Others"> cache=</span><span class="perl_String">"default"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> file=</span><span class="perl_String">'/var/lib/xen/images/fv0'</span><span class="perl_Others"> startupPolicy=</span><span class="perl_String">'optional'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><seclabel</span><span class="perl_Others"> relabel=</span><span class="perl_String">'no'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></source></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hda'</span><span class="perl_Others"> bus=</span><span class="perl_String">'ide'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><iotune></span>
+ <span class="perl_Keyword"><total_bytes_sec></span>10000000<span class="perl_Keyword"></total_bytes_sec></span>
+ <span class="perl_Keyword"><read_iops_sec></span>400000<span class="perl_Keyword"></read_iops_sec></span>
+ <span class="perl_Keyword"><write_iops_sec></span>100000<span class="perl_Keyword"></write_iops_sec></span>
+ <span class="perl_Keyword"></iotune></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'2'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><encryption</span><span class="perl_Others"> type=</span><span class="perl_String">'...'</span><span class="perl_Keyword">></span>
+ ...
+ <span class="perl_Keyword"></encryption></span>
+ <span class="perl_Keyword"><shareable/></span>
+ <span class="perl_Keyword"><serial></span>
+ ...
+ <span class="perl_Keyword"></serial></span>
+ <span class="perl_Keyword"></disk></span>
+ ...
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">"qemu"</span><span class="perl_Others"> type=</span><span class="perl_String">"raw"</span><span class="perl_Others"> io=</span><span class="perl_String">"threads"</span><span class="perl_Others"> ioeventfd=</span><span class="perl_String">"on"</span><span class="perl_Others"> event_idx=</span><span class="perl_String">"off"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> protocol=</span><span class="perl_String">"sheepdog"</span><span class="perl_Others"> name=</span><span class="perl_String">"image_name"</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><host</span><span class="perl_Others"> name=</span><span class="perl_String">"hostname"</span><span class="perl_Others"> port=</span><span class="perl_String">"7000"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></source></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">"hdb"</span><span class="perl_Others"> bus=</span><span class="perl_String">"ide"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><transient/></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'drive'</span><span class="perl_Others"> controller=</span><span class="perl_String">'0'</span><span class="perl_Others"> bus=</span><span class="perl_String">'1'</span><span class="perl_Others"> unit=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">"qemu"</span><span class="perl_Others"> type=</span><span class="perl_String">"raw"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> protocol=</span><span class="perl_String">"rbd"</span><span class="perl_Others"> name=</span><span class="perl_String">"image_name2"</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><host</span><span class="perl_Others"> name=</span><span class="perl_String">"hostname"</span><span class="perl_Others"> port=</span><span class="perl_String">"7000"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></source></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">"hdd"</span><span class="perl_Others"> bus=</span><span class="perl_String">"ide"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><auth</span><span class="perl_Others"> username=</span><span class="perl_String">'myuser'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><secret</span><span class="perl_Others"> type=</span><span class="perl_String">'ceph'</span><span class="perl_Others"> usage=</span><span class="perl_String">'mypassid'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></auth></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'block'</span><span class="perl_Others"> device=</span><span class="perl_String">'cdrom'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">'qemu'</span><span class="perl_Others"> type=</span><span class="perl_String">'raw'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hdc'</span><span class="perl_Others"> bus=</span><span class="perl_String">'ide'</span><span class="perl_Others"> tray=</span><span class="perl_String">'open'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><readonly/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'block'</span><span class="perl_Others"> device=</span><span class="perl_String">'lun'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">'qemu'</span><span class="perl_Others"> type=</span><span class="perl_String">'raw'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> dev=</span><span class="perl_String">'/dev/sda'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'sda'</span><span class="perl_Others"> bus=</span><span class="perl_String">'scsi'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'drive'</span><span class="perl_Others"> controller=</span><span class="perl_String">'0'</span><span class="perl_Others"> bus=</span><span class="perl_String">'0'</span><span class="perl_Others"> target=</span><span class="perl_String">'3'</span><span class="perl_Others"> unit=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'block'</span><span class="perl_Others"> device=</span><span class="perl_String">'disk'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">'qemu'</span><span class="perl_Others"> type=</span><span class="perl_String">'raw'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> dev=</span><span class="perl_String">'/dev/sda'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><geometry</span><span class="perl_Others"> cyls=</span><span class="perl_String">'16383'</span><span class="perl_Others"> heads=</span><span class="perl_String">'16'</span><span class="perl_Others"> secs=</span><span class="perl_String">'63'</span><span class="perl_Others"> trans=</span><span class="perl_String">'lba'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><blockio</span><span class="perl_Others"> logical_block_size=</span><span class="perl_String">'512'</span><span class="perl_Others"> physical_block_size=</span><span class="perl_String">'4096'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hda'</span><span class="perl_Others"> bus=</span><span class="perl_String">'ide'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'volume'</span><span class="perl_Others"> device=</span><span class="perl_String">'disk'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">'qemu'</span><span class="perl_Others"> type=</span><span class="perl_String">'raw'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> pool=</span><span class="perl_String">'blk-pool0'</span><span class="perl_Others"> volume=</span><span class="perl_String">'blk-pool0-vol0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hda'</span><span class="perl_Others"> bus=</span><span class="perl_String">'ide'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.24. Devices - Hard drives, floppy disks, CDROMs</h6></div><br class="figure-break" /><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-disk"><div class="titlepage"><div><div><h4 class="title">J.16.1.1. Disk element</h4></div></div></div><div class="para">
+ The <code class="sgmltag-starttag"><disk></code> element is the main container for describing disks. The attribute <code class="sgmltag-attribute">type</code> can be used with the <code class="sgmltag-starttag"><disk></code> element. The following types are allowed:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">file</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">block</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">dir</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">network</code>
+ </div></li></ul></div><div class="para">
+ For more information, see <a href="http://libvirt.org/formatdomain.html">Disk Elements</a>
+ </div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-source"><div class="titlepage"><div><div><h4 class="title">J.16.1.2. Source element</h4></div></div></div><div class="para">
+ If the <code class="sgmltag-starttag"><disk type='file''></code>, then the <code class="sgmltag-attribute">file</code> attribute specifies the fully-qualified path to the file holding the disk. If the <code class="sgmltag-starttag"><disk type='block'></code>, then the <code class="sgmltag-attribute">dev</code> attribute specifies the path to the host device to serve as the disk. With both <code class="sgmltag-attvalue">file</code> and <code class="sgmltag-attvalue">block</code>, one or more optional sub-elements <code class="sgmltag-element">seclabel</code>, described below, can be used to override the domain security labeling policy for just that source file. If the disk type is <code class="sgmltag-attvalue">dir</code>, then the <code class="sgmltag-attribute">dir</code> attribute specifies the fully-qualified path to the directory to use as the disk. If the disk type is <code class="sgmltag-attvalue">network</code>, then the protocol attribute specifies t
he protocol to access to the requested image; possible values are <code class="sgmltag-attvalue">nbd</code>, <code class="sgmltag-attvalue">rbd</code>, <code class="sgmltag-attvalue">sheepdog</code> or <code class="sgmltag-attvalue">gluster</code>.
+ </div><div class="para">
+ If the protocol attribute is <code class="sgmltag-attvalue">rbd</code>, <code class="sgmltag-attvalue">sheepdog</code> or <code class="sgmltag-attvalue">gluster</code>, an additional attribute <code class="sgmltag-attvalue">name</code> is mandatory to specify which volume and or image will be used. When the disk type is <code class="sgmltag-attvalue">network</code>, the <code class="sgmltag-attvalue">source</code> may have zero or more <code class="sgmltag-element">host</code> sub-elements used to specify the hosts to connect, including: <code class="sgmltag-attvalue">type='dir'</code> and <code class="sgmltag-attvalue">type='network'</code>. For a <code class="sgmltag-attvalue">file</code> disk type which represents a cdrom or floppy (the device attribute), it is possible to define policy what to do with the disk if the source file is not accessible. This is done by manipulating the <code class="sgmltag-attribute">startupPolicy</code> attribute, with the following valu
es:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">mandatory</code> causes a failure if missing for any reason. This is the default setting.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">requisite</code> causes a failure if missing on boot up, drops if missing on migrate/restore/revert
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">optional</code> drops if missing at any start attempt
+ </div></li></ul></div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-mirror"><div class="titlepage"><div><div><h4 class="title">J.16.1.3. Mirror element</h4></div></div></div><div class="para">
+ This element is present if the hypervisor has started a <code class="command">BlockCopy</code> operation, where the <code class="sgmltag-starttag"><mirror></code> location in the attribute file will eventually have the same contents as the source, and with the file format in attribute format (which might differ from the format of the source). If an attribute ready is present, then it is known the disk is ready to pivot; otherwise, the disk is probably still copying. For now, this element only valid in output; it is ignored on input.
+ </div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-target"><div class="titlepage"><div><div><h4 class="title">J.16.1.4. Target element</h4></div></div></div><div class="para">
+ The <code class="sgmltag-starttag"><target></code> element controls the bus / device under which the disk is exposed to the guest OS. The dev attribute indicates the logical device name. The actual device name specified is not guaranteed to map to the device name in the guest OS. The optional bus attribute specifies the type of disk device to emulate; possible values are driver specific, with typical values being <code class="sgmltag-attvalue">ide</code>, <code class="sgmltag-attvalue">scsi</code>, <code class="sgmltag-attvalue">virtio</code>, <code class="sgmltag-attvalue">xen</code>, <code class="sgmltag-attvalue">usb</code> or <code class="sgmltag-attvalue">sata</code>. If omitted, the bus type is inferred from the style of the device name. eg, a device named <code class="filename">'sda'</code> will typically be exported using a SCSI bus. The optional attribute <code class="sgmltag-attribute">tray</code> indicates the tray status of the removable disks (i.e. CD
ROM or Floppy disk), the value can be either <code class="sgmltag-attvalue">open</code> or <code class="sgmltag-attvalue">closed</code>. The default setting is <code class="sgmltag-attvalue">closed</code>. For more information, see <a href="http://libvirt.org/formatdomain.html">target Elements</a>
+ </div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-iotune"><div class="titlepage"><div><div><h4 class="title">J.16.1.5. iotune</h4></div></div></div><div class="para">
+ The optional <code class="sgmltag-starttag"><iotune></code> element provides the ability to provide additional per-device I/O tuning, with values that can vary for each device (contrast this to the <code class="sgmltag-attvalue">blkiotune</code> element, which applies globally to the domain). This element has the following optional sub-elements. Note that any sub-element not specified or at all or specified with a value of <code class="sgmltag-attvalue">0</code> implies no limit.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><total_bytes_sec></code> - the total throughput limit in bytes per second. This element cannot be used with <code class="sgmltag-starttag"><read_bytes_sec></code> or <code class="sgmltag-starttag"><write_bytes_sec></code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><read_bytes_sec></code> - the read throughput limit in bytes per second.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><write_bytes_sec></code> - the write throughput limit in bytes per second.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><total_iops_sec></code> - the total I/O operations per second. This element cannot be used with <code class="sgmltag-starttag"><read_iops_sec></code> or <code class="sgmltag-starttag"><write_iops_sec></code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><read_iops_sec></code> - the read I/O operations per second.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><write_iops_sec></code> - the write I/O operations per second.
+ </div></li></ul></div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-driver"><div class="titlepage"><div><div><h4 class="title">J.16.1.6. driver</h4></div></div></div><div class="para">
+ The optional <code class="sgmltag-starttag"><driver></code> element allows specifying further details related to the hypervisor driver that is used to provide the disk. The following options may be used:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If the hypervisor supports multiple backend drivers, then the <code class="sgmltag-attribute">name</code> attribute selects the primary backend driver name, while the optional type attribute provides the sub-type. For a list of possible types refer to <a href="http://libvirt.org/formatdomain.html">Driver Elements</a>
+ </div></li><li class="listitem"><div class="para">
+ The optional <code class="sgmltag-attribute">cache</code> attribute controls the cache mechanism, possible values are: <code class="sgmltag-attvalue">default</code>, <code class="sgmltag-attvalue">none</code>, <code class="sgmltag-attvalue">writethrough</code>, <code class="sgmltag-attvalue">writeback</code>, <code class="sgmltag-attvalue">directsync</code> (similar to <code class="sgmltag-element">writethrough</code>, but it bypasses the host page cache) and <code class="sgmltag-attvalue">unsafe</code> (host may cache all disk io, and sync requests from guest are ignored).
+ </div></li><li class="listitem"><div class="para">
+ The optional <code class="sgmltag-attribute">error_policy</code> attribute controls how the hypervisor behaves on a disk read or write error, possible values are <code class="sgmltag-attvalue">stop</code>, <code class="sgmltag-attvalue">report</code>, <code class="sgmltag-attvalue">ignore</code>, and <code class="sgmltag-attvalue">enospace</code>. The default setting of <code class="sgmltag-attribute">error_policy</code> is <code class="sgmltag-attvalue">report</code>. There is also an optional <code class="sgmltag-attribute">rerror_policy</code> that controls behavior for read errors only. If no <code class="sgmltag-attribute">rerror_policy</code> is given, <code class="sgmltag-attribute">error_policy</code> is used for both read and write errors. If <code class="sgmltag-attribute">rerror_policy</code> is given, it overrides the <code class="sgmltag-attribute">error_policy</code> for read errors. Also note that <code class="sgmltag-attvalue">enospace</code> is not a
valid policy for read errors, so if <code class="sgmltag-attribute">error_policy</code> is set to <code class="sgmltag-attvalue">enospace</code> and <code class="sgmltag-attribute">no rerror_policy</code> is given, the read error the default setting, <code class="sgmltag-attvalue">report</code> will be used.
+ </div></li><li class="listitem"><div class="para">
+ The optional <code class="sgmltag-attribute">io</code> attribute controls specific policies on I/O; <code class="sgmltag-attribute">qemu</code> guests support <code class="sgmltag-attvalue">threads</code> and <code class="sgmltag-attvalue">native</code>. The optional <code class="sgmltag-attribute">ioeventfd</code> attribute allows users to set domain I/O asynchronous handling for disk device. The default is left to the discretion of the hypervisor. Accepted values are <code class="sgmltag-attvalue">on</code> and <code class="sgmltag-attvalue">off</code>. Enabling this allows the guest virtual machine to be executed while a separate thread handles I/O. Typically guests experiencing high system CPU utilization during I/O will benefit from this. On the other hand, an overloaded host can increase guest I/O latency. Unless you are absolutely certian that the <code class="sgmltag-attribute">io</code> needs to be manipulated, it is highly recommended that you not change the
default setting and allow the hypervisor to dictate the setting.
+ </div></li><li class="listitem"><div class="para">
+ The optional <code class="sgmltag-attribute">event_idx</code> attribute controls some aspects of device event processing and can be set to either <code class="sgmltag-attvalue">on</code> or <code class="sgmltag-attvalue">off</code> - if it is on, it will reduce the number of interrupts and exits for the guest. The default is determined by the hypervisor and the default setting is <code class="sgmltag-attvalue">on</code>. In cases that there is a situation where this behavior is suboptimal, this attribute provides a way to force the feature <code class="sgmltag-attvalue">off</code>. Unless you are absolutely certian that the <code class="sgmltag-attribute">event_idx</code> needs to be manipulated, it is highly recommended that you not change the default setting and allow the hypervisor to dictate the setting.
+ </div></li><li class="listitem"><div class="para">
+ The optional <code class="sgmltag-attribute">copy_on_read</code> attribute controls whether to copy the read backing file into the image file. The accepted values can be either <code class="sgmltag-attvalue">on</code> or <code class="sgmltag-starttag"><off></code>. <code class="sgmltag-attribute">copy-on-read</code> avoids accessing the same backing file sectors repeatedly and is useful when the backing file is over a slow network. By default <code class="sgmltag-attribute">copy-on-read</code> is <code class="sgmltag-attvalue">off</code>.
+ </div></li></ul></div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-misc"><div class="titlepage"><div><div><h4 class="title">J.16.1.7. Additional Device Elements</h4></div></div></div><div class="para">
+ The following attributes may be used within the <code class="sgmltag-element">device</code> element:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><boot></code> - Specifies that the disk is bootable.
+ </div><div class="itemizedlist"><h6>Additional boot values</h6><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><order></code> - Determines the order in which devices will be tried during boot sequence.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><per-device></code> boot elements cannot be used together with general boot elements in BIOS bootloader section
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><encryption></code> - Specifies how the volume is encrypted. See the Storage Encryption page for more information.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><readonly></code> - Indicates the device cannot be modified by the guest. This setting is the default for disks with <code class="sgmltag-attribute">attribute</code> <code class="sgmltag-attvalue">device='cdrom'</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">shareable</code> Indicates the device is expected to be shared between domains (as long as hypervisor and OS support this). If <code class="sgmltag-element">shareable</code> is used, <code class="sgmltag-attvalue">cache='no'</code> should be used for that device.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><transient></code>- Indicates that changes to the device contents should be reverted automatically when the guest exits. With some hypervisors, marking a disk <code class="sgmltag-attvalue">transient</code> prevents the domain from participating in migration or snapshots.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><serial></code>- Specifies the serial number of guest virtual machine's hard drive. For example, <code class="sgmltag-starttag"><serial></code>WD-WMAP9A966149<code class="sgmltag-endtag"></serial></code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><wwn></code> - Specifies the WWN (World Wide Name) of a virtual hard disk or CD-ROM drive. It must be composed of 16 hexadecimal digits.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><vendor></code> - Specifies the vendor of a virtual hard disk or CD-ROM device. It must not be longer than 8 printable characters.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><product></code> - Specifies the product of a virtual hard disk or CD-ROM device. It must not be longer than 16 printable characters
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><host></code> - Supports 4 attributes: <code class="sgmltag-element">viz</code>, <code class="sgmltag-element">name</code>, <code class="sgmltag-element">port</code>, <code class="sgmltag-element">transport</code> and <code class="sgmltag-element">socket</code>, which specify the hostname, the port number, transport type and path to socket, respectively. The meaning of this element and the number of the elements depend on the <code class="sgmltag-element">protocol</code> attribute as shown here:
+ </div><div class="itemizedlist"><h6>additional host attributes</h6><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">nbd</code> - Specifies a server running nbd-server and may only be used for only one host
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">rbd</code> - Monitors servers of RBD type and may be used for one or more hosts
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">sheepdog</code> - Specifies one of the sheepdog servers (default is localhost:7000) and can be used one or none of the hosts
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">gluster</code> - Specifies a server running a glusterd daemon and may be used for only only one host. The valid values for transport attribute are <code class="sgmltag-attvalue">tcp</code>, <code class="sgmltag-attvalue">rdma</code> or <code class="sgmltag-attvalue">unix</code>. If nothing is specified, <code class="sgmltag-attvalue">tcp</code> is assumed. If transport is <code class="sgmltag-attvalue">unix</code>, the <code class="sgmltag-attvalue">socket</code> attribute specifies path to unix socket.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><address></code> - Ties the disk to a given slot of a controller. The actual <code class="sgmltag-starttag"><controller></code> device can often be inferred by but it can also be explicitly specified. The <code class="sgmltag-attribute">type</code> attribute is mandatory, and is typically <code class="sgmltag-attvalue">pci</code> or <code class="sgmltag-attvalue">drive</code>. For a <code class="sgmltag-attribute">pci</code> controller, additional attributes for <code class="sgmltag-element">bus</code>, <code class="sgmltag-element">slot</code>, and <code class="sgmltag-element">function</code> must be present, as well as optional <code class="sgmltag-element">domain</code> and <code class="sgmltag-attvalue">multifunction</code>. <code class="sgmltag-attvalue">multifunction</code> defaults to <code class="sgmltag-attvalue">off</code>. For a <code class="sgmltag-attribute">drive</code> controller, additional attributes <code c
lass="sgmltag-attvalue">controller</code>, <code class="sgmltag-attvalue">bus</code>, <code class="sgmltag-attvalue">target</code>, and <code class="sgmltag-attvalue">unit</code> are available, each with a default setting of <code class="sgmltag-attvalue">0</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">auth</code> - Provides the authentication credentials needed to access the source. It includes a mandatory attribute username, which identifies the username to use during authentication, as well as a sub-element <code class="sgmltag-attvalue">secret</code> with mandatory attribute <code class="sgmltag-attribute">type</code>. More information can be found here at <a href="http://libvirt.org/formatdomain.html">Device Elements</a>
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">geometry</code> - Provides the ability to override geometry settings. This mostly useful for S390 DASD-disks or older DOS-disks.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">cyls</code> - Specifies the number of cylinders.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">heads</code> - Specifies the number of heads.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">secs</code> - Specifies the number of sectors per track.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">trans</code> - Specifies the BIOS-Translation-Modus and can have the following values:<code class="sgmltag-element">none</code>, <code class="sgmltag-element">lba</code> or <code class="sgmltag-element">auto</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">blockio</code> - Allows the block device to be overridden with any of the block device properties listed below:
+ </div><div class="itemizedlist"><h6>blockio options</h6><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">logical_block_size</code>- reports to the guest OS and describes the smallest units for disk I/O.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">physical_block_size</code> - reports to the guest OS and describes the disk's hardware sector size which can be relevant for the alignment of disk data.
+ </div></li></ul></div></li></ul></div></div></div><div class="section" id="sub-section-libvirt-dom-xml-devices-filesystems"><div class="titlepage"><div><div><h3 class="title">J.16.2. Filesystems</h3></div></div></div><div class="para">
+ A filesystems directory on the host that can be accessed directly from the guest
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-filesystems"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><filesystem</span><span class="perl_Others"> type=</span><span class="perl_String">'template'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> name=</span><span class="perl_String">'my-vm-template'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dir=</span><span class="perl_String">'/'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></filesystem></span>
+ <span class="perl_Keyword"><filesystem</span><span class="perl_Others"> type=</span><span class="perl_String">'mount'</span><span class="perl_Others"> accessmode=</span><span class="perl_String">'passthrough'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> type=</span><span class="perl_String">'path'</span><span class="perl_Others"> wrpolicy=</span><span class="perl_String">'immediate'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> dir=</span><span class="perl_String">'/export/to/guest'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dir=</span><span class="perl_String">'/import/from/host'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><readonly/></span>
+ <span class="perl_Keyword"></filesystem></span>
+ ...
+ <span class="perl_Keyword"></devices></span>
+ ...
+
+</pre></div><h6>Figure J.25. Devices - filesystems</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-attribute">filesystem</code> attribute has the following possible values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='mount'</code> - Specifies the host directory to mount in the guest. This is the default type if one is not specified. This mode also has an optional sub-element <code class="sgmltag-element">driver</code>, with an attribute <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='path'</code> or <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='handle'</code>. The driver block has an optional attribute <code class="sgmltag-attribute">wrpolicy</code> that further controls interaction with the host page cache; omitting the attribute reverts to the default setting, while specifying a value immediate means that a host writeback is immediately triggered for all pages touched during a guest file write operation
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='template'</code> - Specifies the OpenVZ filesystem template and is only used by OpenVZ driver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='file'</code> - Specifies that a host file will be treated as an image and mounted in the guest. This filesystem format will be autodetected and is only used by LXC driver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='block'</code> - Specifies the host block device to mount in the guest. The filesystem format will be autodetected and is only used by LXC driver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='ram'</code> - Specifies that an in-memory filesystem, using memory from the host OS will be used. The source element has a single attribute <code class="sgmltag-attribute">usage</code> which gives the memory usage limit in kibibytes and is only used by LXC driver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='bind'</code> - Specifies a directory inside the guest which will be bound to another directory inside the guest. This element is only used by LXC driver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">accessmode</code> which specifies the security mode for accessing the source. Currently this only works with type='mount' for the QEMU/KVM driver. The possible values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">passthrough</code> - Specifies that the source is accessed with the User's permission settings that are set from inside the virtual guest machine. This is the default accessmode if one is not specified.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">mapped</code> - Specifies that the source is accessed with the permission settings of the hypervisor.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">squash</code> - Similar to <code class="sgmltag-attvalue">'passthrough'</code>, the exception is that failure of privileged operations like <code class="sgmltag-attvalue">chown</code> are ignored. This makes a passthrough-like mode usable for people who run the hypervisor as non-root.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><source></code> - Specifies that the resource on the host that is being accessed in the guest virtual machine. The <code class="sgmltag-attribute">name</code> attribute must be used with <code class="sgmltag-starttag"><type='template'></code>, and the <code class="sgmltag-attribute">dir</code> attribute must be used with <code class="sgmltag-starttag"><type='mount'></code>. The <code class="sgmltag-attribute">usage</code> attribute is used with <code class="sgmltag-starttag"><type='ram'></code> to set the memory limit in KB.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-element">target</code> - Dictates where the source drivers can be accessed in the guest virtual machine. For most drivers this is an automatic mount point, but for QEMU-KVM this is merely an arbitrary string tag that is exported to the guest as a hint for where to mount.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">readonly</code> - Enables exporting the filesytem as a readonly mount for guest virtual machine, by default <code class="sgmltag-element">read-write</code> access is given.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">space_hard_limit</code> - Specifies the maximum space available to this guest's filesystem
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">space_soft_limit</code> - Specifies the maximum space available to this guest's filesystem. The container is permitted to exceed its soft limits for a grace period of time. Afterwards the hard limit is enforced.
+ </div></li></ul></div></div><div class="section" id="sub-section-libvirt-dom-xml-devices-device-addresses"><div class="titlepage"><div><div><h3 class="title">J.16.3. Device addresses</h3></div></div></div><div class="para">
+ Many devices have an optional <code class="sgmltag-starttag"><address></code> sub-element to describe where the device placed on the virtual bus is presented to the guest. If an address (or any optional attribute within an address) is omitted on input, libvirt will generate an appropriate address; but an explicit address is required if more control over layout is required. See below for device examples including an address element.
+ </div><div class="para">
+ Every address has a mandatory attribute <em class="parameter"><code>type</code></em> that describes which bus the device is on. The choice of which address to use for a given device is constrained in part by the device and the architecture of the guest. For example, a disk device uses <code class="sgmltag-attribute">type='disk'</code>, while a console device would use <code class="sgmltag-attribute">type='pci'</code> on i686 or x86_64 guests, or <code class="sgmltag-attribute">type='spapr-vio'</code> on PowerPC64 pseries guests. Each address <code class="sgmltag-starttag"><type></code> has additional optional attributes that control where on the bus the device will be placed. The additional attributes are as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type='pci'</code> - PCI addresses have the following additional attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">domain</code> (a 2-byte hex integer, not currently used by qemu)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">bus</code> (a hex value between 0 and 0xff, inclusive)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">slot</code> (a hex value between 0x0 and 0x1f, inclusive)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">function</code> (a value between 0 and 7, inclusive)
+ </div></li><li class="listitem"><div class="para">
+ Also available is the <code class="sgmltag-attribute">multifunction</code> attribute, which controls turning on the multifunction bit for a particular slot/function in the PCI control register. This multifunction attribute defaults to <code class="sgmltag-attvalue">'off'</code>, but should be set to <code class="sgmltag-attvalue">'on'</code> for function 0 of a slot that will have multiple functions used.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type='drive</code> - drive addresses have the following additional attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">controller</code>- (a 2-digit controller number)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">bus</code> - (a 2-digit bus number)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">target</code> - (a 2-digit bus number)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">unit</code> - (a 2-digit unit number on the bus)
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type='virtio-serial'</code> - Each virtio-serial address has the following additional attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">controller</code> - (a 2-digit controller number)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">bus</code> - (a 2-digit bus number)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">slot</code> - (a 2-digit slot within the bus)
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type='ccid'</code> - A CCID address, used for smart-cards, has the following additional attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">bus</code> - (a 2-digit bus number)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">slot</code> attribute - (a 2-digit slot within the bus)
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type='usb'</code> - USB addresses have the following additional attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">bus</code> - (a hex value between 0 and 0xfff, inclusive)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">port</code> - (a dotted notation of up to four octets, such as 1.2 or 2.1.3.1)
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type='spapr-vio</code> - On PowerPC pseries guests, devices can be assigned to the SPAPR-VIO bus. It has a flat 64-bit address space; by convention, devices are generally assigned at a non-zero multiple of 0x1000, but other addresses are valid and permitted by libvirt. The additional attribute: reg (the hex value address of the starting register) can be assigned to this attribute.
+ </div></li></ul></div></div><div class="section" id="sub-section-libvirt-dom-xml-devices-controllers"><div class="titlepage"><div><div><h3 class="title">J.16.4. Controllers</h3></div></div></div><div class="para">
+ Depending on the guest architecture, some device busses can appear more than once, with a group of virtual devices tied to a virtual controller. Normally, libvirt can automatically infer such controllers without requiring explicit XML markup, but sometimes it is necessary to provide an explicit controller element.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-controllers"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><controller</span><span class="perl_Others"> type=</span><span class="perl_String">'ide'</span><span class="perl_Others"> index=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><controller</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio-serial'</span><span class="perl_Others"> index=</span><span class="perl_String">'0'</span><span class="perl_Others"> ports=</span><span class="perl_String">'16'</span><span class="perl_Others"> vectors=</span><span class="perl_String">'4'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><controller</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio-serial'</span><span class="perl_Others"> index=</span><span class="perl_String">'1'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'pci'</span><span class="perl_Others"> domain=</span><span class="perl_String">'0x0000'</span><span class="perl_Others"> bus=</span><span class="perl_String">'0x00'</span><span class="perl_Others"> slot=</span><span class="perl_String">'0x0a'</span><span class="perl_Others"> function=</span><span class="perl_String">'0x0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></controller></span>
+ ...
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.26. Devices - controllers</h6></div><br class="figure-break" /><div class="para">
+ Each controller has a mandatory attribute<code class="sgmltag-attribute">type</code>, which must be one of <code class="sgmltag-element">"ide", "fdc", "scsi", "sata", "usb", "ccid", or "virtio-serial"</code>, and a mandatory attribute <code class="sgmltag-attribute">index</code> which is the decimal integer describing in which order the bus controller is encountered (for use in controller attributes of <code class="sgmltag-element">address</code>elements). The "virtio-serial" controller has two additional optional attributes ports and vectors, which control how many devices can be connected through the controller. A "scsi" controller has an optional attribute <code class="sgmltag-element">model</code>, which is one of <code class="sgmltag-element">"auto", "buslogic", "ibmvscsi", "lsilogic", "lsias1068", "virtio-scsi" or "vmpvscsi"</code>. A "usb" controller has an optional attribute <code class="sgmltag-attribute">model</code>, which is one of <code class="sgmltag-elemen
t">"piix3-uhci", "piix4-uhci", "ehci", "ich9-ehci1", "ich9-uhci1", "ich9-uhci2", "ich9-uhci3", "vt82c686b-uhci", "pci-ohci" or "nec-xhci"</code>. Additionally, if the USB bus needs to be explicitly disabled for the guest, <code class="sgmltag-attribute">model='none'</code> may be used. The PowerPC64 "spapr-vio" addresses do not have an associated controller.
+ </div><div class="para">
+ For controllers that are themselves devices on a PCI or USB bus, an optional sub-element <code class="sgmltag-element">address</code> can specify the exact relationship of the controller to its master bus, with semantics given above.
+ </div><div class="para">
+ USB companion controllers have an optional sub-element <code class="sgmltag-element">master</code> to specify the exact relationship of the companion to its master controller. A companion controller is on the same bus as its master, so the companion index value should be equal.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-controllers2"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><controller</span><span class="perl_Others"> type=</span><span class="perl_String">'usb'</span><span class="perl_Others"> index=</span><span class="perl_String">'0'</span><span class="perl_Others"> model=</span><span class="perl_String">'ich9-ehci1'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'pci'</span><span class="perl_Others"> domain=</span><span class="perl_String">'0'</span><span class="perl_Others"> bus=</span><span class="perl_String">'0'</span><span class="perl_Others"> slot=</span><span class="perl_String">'4'</span><span class="perl_Others"> function=</span><span class="perl_String">'7'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></controller></span>
+ <span class="perl_Keyword"><controller</span><span class="perl_Others"> type=</span><span class="perl_String">'usb'</span><span class="perl_Others"> index=</span><span class="perl_String">'0'</span><span class="perl_Others"> model=</span><span class="perl_String">'ich9-uhci1'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><master</span><span class="perl_Others"> startport=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'pci'</span><span class="perl_Others"> domain=</span><span class="perl_String">'0'</span><span class="perl_Others"> bus=</span><span class="perl_String">'0'</span><span class="perl_Others"> slot=</span><span class="perl_String">'4'</span><span class="perl_Others"> function=</span><span class="perl_String">'0'</span><span class="perl_Others"> multifunction=</span><span class="perl_String">'on'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></controller></span>
+ ...
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.27. Devices - controllers - USB</h6></div><br class="figure-break" /></div><div class="section" id="sub-section-libvirt-dom-xml-devices-device-leases"><div class="titlepage"><div><div><h3 class="title">J.16.5. Device leases</h3></div></div></div><div class="para">
+ When using a lock manager, you have the option to record device leases against a guest virtual machine. The lock manager will ensure that the guest virtual machine doesn't start unless the leases can be acquired. When configured using conventional management tools, the following section of the domain xml is effected:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-device-leases"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ ...
+ <span class="perl_Keyword"><lease></span>
+ <span class="perl_Keyword"><lockspace></span>somearea<span class="perl_Keyword"></lockspace></span>
+ <span class="perl_Keyword"><key></span>somekey<span class="perl_Keyword"></key></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> path=</span><span class="perl_String">'/some/lease/path'</span><span class="perl_Others"> offset=</span><span class="perl_String">'1024'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></lease></span>
+ ...
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.28. Devices - device leases</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-element">lease</code> section can have the following arguements:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-element">lockspace</code> - an arbitrary string that identifies lockspace within which the key is held. Lock managers may impose extra restrictions on the format, or length of the lockspace name.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-element">key</code> - an arbitrary string, that uniquely identies the lease to be acquired. Lock managers may impose extra restrictions on the format, or length of the key.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-element">target</code> - the fully qualified path of the file associated with the lockspace. The offset specifies where the lease is stored within the file. If the lock manager does not require a offset, set this value to <code class="sgmltag-element">0</code>.
+ </div></li></ul></div></div><div class="section" id="sub-section-libvirt-dom-xml-devices-host-device-assignment"><div class="titlepage"><div><div><h3 class="title">J.16.6. Host device assignment</h3></div></div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-host-device-assignment-usb-pci-devices"><div class="titlepage"><div><div><h4 class="title">J.16.6.1. USB / PCI devices</h4></div></div></div><div class="para">
+ The host's USB and PCI devices can be passed through to the guest using the <code class="sgmltag-element">hostdev</code> element, by modifying the host using a management tool the following section of the domain xml file is configured:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-host-device-assignment"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><hostdev</span><span class="perl_Others"> mode=</span><span class="perl_String">'subsystem'</span><span class="perl_Others"> type=</span><span class="perl_String">'usb'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> startupPolicy=</span><span class="perl_String">'optional'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><vendor</span><span class="perl_Others"> id=</span><span class="perl_String">'0x1234'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><product</span><span class="perl_Others"> id=</span><span class="perl_String">'0xbeef'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></source></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'2'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></hostdev></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.29. Devices - host device assignment</h6></div><br class="figure-break" /><div class="para">
+ Alternatively the following can also be done:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-host-device-assignment2"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><hostdev</span><span class="perl_Others"> mode=</span><span class="perl_String">'subsystem'</span><span class="perl_Others"> type=</span><span class="perl_String">'pci'</span><span class="perl_Others"> managed=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> bus=</span><span class="perl_String">'0x06'</span><span class="perl_Others"> slot=</span><span class="perl_String">'0x02'</span><span class="perl_Others"> function=</span><span class="perl_String">'0x0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></source></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><rom</span><span class="perl_Others"> bar=</span><span class="perl_String">'on'</span><span class="perl_Others"> file=</span><span class="perl_String">'/etc/fake/boot.bin'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></hostdev></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.30. Devices - host device assignment alternative</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-pci-managed-devices"><h6>Table J.13. Host device assignment elements</h6><div class="table-contents"><table summary="Host device assignment elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-element">hostdev</code>
+ </td><td class="">
+ This is the main container for describing host devices. For USB device passthrough <code class="sgmltag-element">mode</code> is always <code class="sgmltag-element">subsystem</code> and <code class="sgmltag-element">type</code> is <code class="sgmltag-element">usb</code> for a USB device and <code class="sgmltag-element">pci</code> for a PCI device. When <code class="sgmltag-element">managed</code> is <code class="sgmltag-element">yes</code> for a PCI device, it is detached from the host before being passed on to the guest, and reattached to the host after the guest exits. If <code class="sgmltag-element">managed</code> is omitted or <code class="sgmltag-element">no</code> for PCI and for USB devices, the user is responsible to use the arguement <code class="sgmltag-element">virNodeDeviceDettach</code> (or <code class="command">virsh nodedev-dettach</code>) before starting the guest or hot-plugging the device, and <code class="sgmltag-element">virNodeDeviceReAttach<
/code> (or <code class="command">virsh nodedev-reattach</code>) after hot-unplug or stopping the guest.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">source</code>
+ </td><td class="">
+ Describes the device as seen from the host. The USB device can either be addressed by vendor / product id using the <code class="sgmltag-element">vendor</code> and <code class="sgmltag-element">product</code> elements or by the device's address on the hosts using the <code class="sgmltag-element">address</code> element. PCI devices on the other hand can only be described by their address. Note that the source element of USB devices may contain a <code class="sgmltag-attribute">startupPolicy</code> attribute which can be used to define a rule for what to do if the specified host USB device is not found. The attribute accepts the following values:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-element">mandatory</code> - fails if missing for any reason (the default)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-element">requisite</code> - fails if missing on boot up, drops if missing on migrate/restore/revert
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-element">optional</code> - drops if missing at any start attempt
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">vendor, product</code>
+ </td><td class="">
+ These elements each have an <code class="sgmltag-attribute">id</code> attribute that specifies the USB vendor and product id. The IDs can be given in decimal, hexadecimal (starting with 0x) or octal (starting with 0) form.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">boot</code>
+ </td><td class="">
+ Specifies that the device is bootable. The attribute's order determines the order in which devices will be tried during boot sequence. The per-device boot elements cannot be used together with general boot elements in BIOS bootloader section.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">rom</code>
+ </td><td class="">
+ Used to change how a PCI device's ROM is presented to the guest. The optional <code class="sgmltag-attribute">bar</code> attribute can be set to <code class="sgmltag-element">on</code> or <code class="sgmltag-element">off</code>, and determines whether or not the device's ROM will be visible in the guest's memory map. (In PCI documentation, the <code class="sgmltag-element">rombar</code> setting controls the presence of the Base Address Register for the ROM). If no rom bar is specified, the default setting will be used. The optional <code class="sgmltag-attribute">file</code> attribute is used to point to a binary file to be presented to the guest as the device's ROM BIOS. This can be useful, for example, to provide a PXE boot ROM for a virtual function of an sr-iov capable ethernet device (which has no boot ROMs for the VFs).
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">address</code>
+ </td><td class="">
+ Also has a <code class="sgmltag-attribute">bus</code> and <code class="sgmltag-attribute">device</code> attribute to specify the USB bus and device number the device appears at on the host. The values of these attributes can be given in decimal, hexadecimal (starting with 0x) or octal (starting with 0) form. For PCI devices the element carries 3 attributes allowing to designate the device as can be found with <code class="command">lspci</code> or with <code class="command">virsh nodedev-list</code>
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-host-device-assignment-block-character-devices"><div class="titlepage"><div><div><h4 class="title">J.16.6.2. Block / character devices </h4></div></div></div><div class="para">
+ The host's block / character devices can be passed through to the guest by using managment tools to modify the domain xml <code class="sgmltag-element">hostdev</code> element. Note that this is only possible with container based virtualization.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-host-device-assignment-blk"><div class="figure-contents"><pre class="programlisting">
+
+...
+<span class="perl_Keyword"><hostdev</span><span class="perl_Others"> mode=</span><span class="perl_String">'capabilities'</span><span class="perl_Others"> type=</span><span class="perl_String">'storage'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source></span>
+ <span class="perl_Keyword"><block></span>/dev/sdf1<span class="perl_Keyword"></block></span>
+ <span class="perl_Keyword"></source></span>
+<span class="perl_Keyword"></hostdev></span>
+...
+
+</pre></div><h6>Figure J.31. Devices - host device assignment block character devices</h6></div><br class="figure-break" /><div class="para">
+ An alternative approach is this:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-host-device-assignment-blk2"><div class="figure-contents"><pre class="programlisting">
+
+...
+<span class="perl_Keyword"><hostdev</span><span class="perl_Others"> mode=</span><span class="perl_String">'capabilities'</span><span class="perl_Others"> type=</span><span class="perl_String">'misc'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source></span>
+ <span class="perl_Keyword"><char></span>/dev/input/event3<span class="perl_Keyword"></char></span>
+ <span class="perl_Keyword"></source></span>
+<span class="perl_Keyword"></hostdev></span>
+...
+
+</pre></div><h6>Figure J.32. Devices - host device assignment block character devices alternative 1</h6></div><br class="figure-break" /><div class="para">
+ Another alternative approach is this:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-host-device-assignment-blk3"><div class="figure-contents"><pre class="programlisting">
+
+...
+<span class="perl_Keyword"><hostdev</span><span class="perl_Others"> mode=</span><span class="perl_String">'capabilities'</span><span class="perl_Others"> type=</span><span class="perl_String">'net'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source></span>
+ <span class="perl_Keyword"><interface></span>eth0<span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></source></span>
+<span class="perl_Keyword"></hostdev></span>
+...
+
+
+</pre></div><h6>Figure J.33. Devices - host device assignment block character devices alternative 2</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-host-device-assignement-block-character-devices"><h6>Table J.14. Block / character device elements</h6><div class="table-contents"><table summary="Block / character device elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-element">hostdev</code>
+ </td><td class="">
+ This is the main container for describing host devices. For block/character devices passthrough <code class="sgmltag-attribute">mode</code> is always <code class="sgmltag-element">capabilities</code> and <code class="sgmltag-attribute">type</code> is <code class="sgmltag-element">block</code> for a block device and <code class="sgmltag-element">char</code> for a character device.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">source</code>
+ </td><td class="">
+ This describes the device as seen from the host. For block devices, the path to the block device in the host OS is provided in the nested <code class="sgmltag-element">block</code> element, while for character devices the <code class="sgmltag-element">char</code> element is used
+ </td></tr></tbody></table></div></div><br class="table-break" /></div></div><div class="section" id="sub-section-libvirt-dom-xml-devices-redirected-devices"><div class="titlepage"><div><div><h3 class="title">J.16.7. Redirected devices</h3></div></div></div><div class="para">
+ USB device redirection through a character device is supported by configuring it with managment tools that modify the following section of the domain xml:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-redirected-devices"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><redirdev</span><span class="perl_Others"> bus=</span><span class="perl_String">'usb'</span><span class="perl_Others"> type=</span><span class="perl_String">'tcp'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'connect'</span><span class="perl_Others"> host=</span><span class="perl_String">'localhost'</span><span class="perl_Others"> service=</span><span class="perl_String">'4000'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></redirdev></span>
+ <span class="perl_Keyword"><redirfilter></span>
+ <span class="perl_Keyword"><usbdev</span><span class="perl_Others"> class=</span><span class="perl_String">'0x08'</span><span class="perl_Others"> vendor=</span><span class="perl_String">'0x1234'</span><span class="perl_Others"> product=</span><span class="perl_String">'0xbeef'</span><span class="perl_Others"> version=</span><span class="perl_String">'2.00'</span><span class="perl_Others"> allow=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><usbdev</span><span class="perl_Others"> allow=</span><span class="perl_String">'no'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></redirfilter></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.34. Devices - redirected devices</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-host-device-assignement-redirected-devices"><h6>Table J.15. Redirected device elements</h6><div class="table-contents"><table summary="Redirected device elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-element">redirdev</code>
+ </td><td class="">
+ This is the main container for describing redirected devices. <code class="sgmltag-attribute">bus</code> must be <code class="sgmltag-element">usb</code> for a USB device. An additional attribute type is required, matching one of the supported serial device types, to describe the host side of the tunnel; <code class="sgmltag-attribute">type='tcp'</code> or <code class="sgmltag-attribute">type='spicevmc'</code> (which uses the usbredir channel of a SPICE graphics device) are typical. The redirdev element has an optional sub-element <code class="sgmltag-element">address</code> which can tie the device to a particular controller. Further sub-elements, such as <code class="sgmltag-element">source</code>, may be required according to the given <code class="sgmltag-attribute">type</code>, although a<code class="sgmltag-element">target</code> sub-element is not required (since the consumer of the character device is the hypervisor itself, rather than a device visible in the
guest).
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">boot</code>
+ </td><td class="">
+ Specifies that the device is bootable. The order attribute determines the order in which devices will be tried during boot sequence. The per-device boot elements cannot be used together with general boot elements in BIOS bootloader section.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">redirfilter</code>
+ </td><td class="">
+ This is used for creating the filter rule to filter out certain devices from redirection. It uses sub-element <code class="sgmltag-element">usbdev</code> to define each filter rule. The <code class="sgmltag-attribute">class</code> attribute is the USB Class code.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-section-libvirt-dom-xml-devices-smartcard"><div class="titlepage"><div><div><h3 class="title">J.16.8. Smartcard devices</h3></div></div></div><div class="para">
+ A virtual smartcard device can be supplied to the guest via the <code class="sgmltag-element">smartcard</code> element. A USB smartcard reader device on the host cannot be used on a guest with simple device passthrough, as it cannot be made available to both the host and guest and can possibly lock the host computer when it is removed from the guest. Therefore, some hypervisors provide a specialized virtual device that can present a smartcard interface to the guest, with several modes for describing how the credentials are obtained from the host or even a from a channel created to a third-party smartcard provider. To set these parameters use a managment tool that will edit the following section of the domain XML:
+ </div><div class="para">
+ USB device redirection through a character device is supported by configuring it with managment tools that modify the following section of the domain xml:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-smartcard"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><smartcard</span><span class="perl_Others"> mode=</span><span class="perl_String">'host'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><smartcard</span><span class="perl_Others"> mode=</span><span class="perl_String">'host-certificates'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><certificate></span>cert1<span class="perl_Keyword"></certificate></span>
+ <span class="perl_Keyword"><certificate></span>cert2<span class="perl_Keyword"></certificate></span>
+ <span class="perl_Keyword"><certificate></span>cert3<span class="perl_Keyword"></certificate></span>
+ <span class="perl_Keyword"><database></span>/etc/pki/nssdb/<span class="perl_Keyword"></database></span>
+ <span class="perl_Keyword"></smartcard></span>
+ <span class="perl_Keyword"><smartcard</span><span class="perl_Others"> mode=</span><span class="perl_String">'passthrough'</span><span class="perl_Others"> type=</span><span class="perl_String">'tcp'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'bind'</span><span class="perl_Others"> host=</span><span class="perl_String">'127.0.0.1'</span><span class="perl_Others"> service=</span><span class="perl_String">'2001'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><protocol</span><span class="perl_Others"> type=</span><span class="perl_String">'raw'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'ccid'</span><span class="perl_Others"> controller=</span><span class="perl_String">'0'</span><span class="perl_Others"> slot=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></smartcard></span>
+ <span class="perl_Keyword"><smartcard</span><span class="perl_Others"> mode=</span><span class="perl_String">'passthrough'</span><span class="perl_Others"> type=</span><span class="perl_String">'spicevmc'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.35. Devices - smartcard devices</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-element">smartcard</code> element has a mandatory attribute <code class="sgmltag-attribute">mode</code>. The following modes are supported; in each mode, the guest sees a device on its USB bus that behaves like a physical USB CCID (Chip/Smart Card Interface Device) card.
+ </div><div class="para">
+ The mode attributes are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-host-device-assignement-smartcard-modes"><h6>Table J.16. Smartcard mode elements</h6><div class="table-contents"><table summary="Smartcard mode elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-attribute">mode='host'</code>
+ </td><td class="">
+ In this mode, the hypervisor relays all requests from the guest into direct access to the host's smartcard via NSS. No other attributes or sub-elements are required. See below about the use of an optional <code class="sgmltag-element">address</code> sub-element.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">mode='host-certificates'</code>
+ </td><td class="">
+ This mode allows you to provide three NSS certificate names residing in a database on the host, rather than requiring a smartcard to be plugged into the host. These certificates can be generated via the command <code class="sgmltag-element">certutil -d /etc/pki/nssdb -x -t CT,CT,CT -S -s CN=cert1 -n cert1,</code> and the resulting three certificate names must be supplied as the content of each of three <code class="sgmltag-element">certificate</code> sub-elements. An additional sub-element <code class="sgmltag-element">database</code> can specify the absolute path to an alternate directory (matching the <code class="sgmltag-element">-d</code> flag of the <code class="command">certutil</code> command when creating the certificates); if not present, it defaults to <code class="filename">/etc/pki/nssdb</code>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">mode='passthrough'</code>
+ </td><td class="">
+ Using this mode allows you to tunnel all requests through a secondary character device to a third-party provider (which may in turn be talking to a smartcard or using three certificate files, rather than having the hypervisor directly communicate with the host. In this mode of operation, an additional attribute <code class="sgmltag-attribute">type</code> is required, matching one of the supported serial device types, to describe the host side of the tunnel; <code class="sgmltag-attribute">type='tcp'</code> or <code class="sgmltag-attribute">type='spicevmc'</code> (which uses the smartcard channel of a SPICE graphics device) are typical. Further sub-elements, such as <code class="sgmltag-element">source</code>, may be required according to the given type, although a <code class="sgmltag-element">target</code> sub-element is not required (since the consumer of the character device is the hypervisor itself, rather than a device visible in the guest).
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Each mode supports an optional sub-element <code class="sgmltag-element">address</code>, which fine-tunes the correlation between the smartcard and a ccid bus controller (Refer to <a class="xref" href="#sub-section-libvirt-dom-xml-devices-device-addresses">Section J.16.3, “Device addresses”</a>).
+ </div></div><div class="section" id="sub-section-libvirt-dom-xml-devices-Network-interfaces"><div class="titlepage"><div><div><h3 class="title">J.16.9. Network interfaces</h3></div></div></div><div class="para">
+ The network interface devices are modified using managment tools that will configure the following part of the Domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'bridge'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> bridge=</span><span class="perl_String">'xenbr0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">'00:16:3e:5d:c7:9e'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><script</span><span class="perl_Others"> path=</span><span class="perl_String">'vif-bridge'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><rom</span><span class="perl_Others"> bar=</span><span class="perl_String">'off'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.36. Devices - network interfaces</h6></div><br class="figure-break" /><div class="para">
+ There are several possibilities for specifying a network interface visible to the guest. Each subsection below provides more details about common setup options. Additionally, each <code class="sgmltag-starttag"><interface></code> element has an optional <code class="sgmltag-starttag"><address></code> sub-element that can tie the interface to a particular pci slot, with attribute <code class="sgmltag-attribute">type='pci'</code> (Refer to <a class="xref" href="#sub-section-libvirt-dom-xml-devices-device-addresses">Section J.16.3, “Device addresses”</a>).
+ </div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-virtual-network"><div class="titlepage"><div><div><h4 class="title">J.16.9.1. Virtual networks</h4></div></div></div><div class="para">
+ This is the recommended configuration for general guest connectivity on hosts with dynamic / wireless networking configurations (or multi-host environments where the host hardware details are described separately in a <code class="sgmltag-starttag"><network></code> definition). In addition, it provides a connection whose details are described by the named network definition. Depending on the virtual network's <code class="sgmltag-attribute">forward mode</code> configuration, the network may be totally isolated (no <code class="sgmltag-starttag"><forward></code> element given), NAT'ing to an explicit network device or to the default route (<code class="sgmltag-attribute">forward mode='nat'</code>), routed with no NAT (<code class="sgmltag-attribute">forward mode='route'/</code>), or connected directly to one of the host's network interfaces (via macvtap) or bridge devices (<code class="sgmltag-attribute">forward mode='bridge|private|vepa|passthrough'/</code>)
+ </div><div class="para">
+ For networks with a forward mode of bridge, private, vepa, and passthrough, it is assumed that the host has any necessary DNS and DHCP services already setup outside the scope of libvirt. In the case of isolated, nat, and routed networks, DHCP and DNS are provided on the virtual network by libvirt, and the IP range can be determined by examining the virtual network config with <code class="command">virsh net-dumpxml [networkname]</code>. There is one virtual network called 'default' setup out of the box which does NAT'ing to the default route and has an IP range of 192.168.122.0/255.255.255.0. Each guest will have an associated tun device created with a name of vnetN, which can also be overridden with the <code class="sgmltag-starttag"><target></code> element (refer to <a class="xref" href="#sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element">Section J.16.9.10, “Overriding the target element”</a>).
+ </div><div class="para">
+ When the source of an interface is a network, a portgroup can be specified along with the name of the network; one network may have multiple portgroups defined, with each portgroup containing slightly different configuration information for different classes of network connections. Also, similar to <code class="sgmltag-starttag"><direct></code> network connections (described below), a connection of type <code class="sgmltag-attribute">network</code> may specify a <code class="sgmltag-starttag"><virtualport></code> element, with configuration data to be forwarded to a vepa (802.1Qbg) or 802.1Qbh compliant switch, or to an Open vSwitch virtual switch.
+ </div><div class="para">
+ Since the actual type of switch may vary depending on the configuration in the <code class="sgmltag-starttag"><network></code> on the host, it is acceptable to omit the virtualport type attribute, and specify attributes from multiple different virtualport types (and also to leave out certain attributes); at domain startup time, a complete <code class="sgmltag-starttag"><virtualport></code> element will be constructed by merging together the type and attributes defined in the network and the portgroup referenced by the interface. The newly-constructed virtualport is a combination of both. The attributes from lower virtualport can't make changes on the ones defined in higher virtualport. Interfaces take the highest priority, portgroup is lowest priority.
+ </div><div class="para">
+ For example, in order to work properly with both an 802.1Qbh switch and an Open vSwitch switch, you may choose to specify no type, but both an <code class="sgmltag-attribute">profileid</code> (in case the switch is 802.1Qbh) and an <code class="sgmltag-attribute">interfaceid</code> (in case the switch is Open vSwitch) (you may also omit the other attributes, such as <code class="sgmltag-attribute">managerid</code>, <code class="sgmltag-attribute">typeid</code>, or <code class="sgmltag-attribute">profileid</code>, to be filled in from the network's <code class="sgmltag-attribute">virtualport</code>). If you want to limit a guest to connecting only to certain types of switches, you can specify the virtualport type, but still omit some/all of the parameters - in this case if the host's network has a different type of virtualport, connection of the interface will fail. The virtual network parameters are defined using management tools that modify the following part of the do
main XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-virt-net"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Others"> portgroup=</span><span class="perl_String">'engineering'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet7'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">"00:11:22:33:44:55"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><virtualport></span>
+ <span class="perl_Keyword"><parameters</span><span class="perl_Others"> instanceid=</span><span class="perl_String">'09b11c53-8b5c-4eeb-8f00-d84eaa0aaa4f'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></virtualport></span>
+
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.37. Devices - network interfaces- virtual networks</h6></div><br class="figure-break" /></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-bridge-to-lan"><div class="titlepage"><div><div><h4 class="title">J.16.9.2. Bridge to LAN</h4></div></div></div><div class="para">
+ Note that this is the recommended configuration setting for general guest connectivity on hosts with static wired networking configurations.
+ </div><div class="para">
+ Bridge to LAN provides a bridge from the guest virtual machine directly onto the LAN. This assumes there is a bridge device on the host which has one or more of the hosts physical NICs enslaved. The guest virtual machine will have an associated <code class="sgmltag-attribute">tun</code> device created with a name of <code class="sgmltag-starttag"><vnetN></code>, which can also be overridden with the <code class="sgmltag-starttag"><target></code> element (refer to <a class="xref" href="#sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element">Section J.16.9.10, “Overriding the target element”</a>). The <code class="sgmltag-starttag"><tun></code> device will be enslaved to the bridge. The IP range / network configuration is whatever is used on the LAN. This provides the guest virtual machine full incoming and outgoing net access just like a physical machine.
+ </div><div class="para">
+ On Linux systems, the bridge device is normally a standard Linux host bridge. On hosts that support Open vSwitch, it is also possible to connect to an open vSwitch bridge device by adding a <code class="sgmltag-attribute">virtualport type='openvswitch'/</code> to the interface definition. The Open vSwitch type virtualport accepts two parameters in its <code class="sgmltag-element">parameters</code> element - an <code class="sgmltag-element">interfaceid</code> which is a standard uuid used to uniquely identify this particular interface to Open vSwitch (if you do no specify one, a random <code class="sgmltag-attribute">interfaceid</code> will be generated for you when you first define the interface), and an optional <code class="sgmltag-element">profileid</code> which is sent to Open vSwitch as the interfaces <code class="sgmltag-starttag"><port-profile></code>. To set the bridge to LAN settings, use a managment tool that will configure the following part of the dom
ain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-br2lan"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'bridge'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> bridge=</span><span class="perl_String">'br0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'bridge'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> bridge=</span><span class="perl_String">'br1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet7'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">"00:11:22:33:44:55"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'bridge'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> bridge=</span><span class="perl_String">'ovsbr'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><virtualport</span><span class="perl_Others"> type=</span><span class="perl_String">'openvswitch'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><parameters</span><span class="perl_Others"> profileid=</span><span class="perl_String">'menial'</span><span class="perl_Others"> interfaceid=</span><span class="perl_String">'09b11c53-8b5c-4eeb-8f00-d84eaa0aaa4f'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></virtualport></span>
+ <span class="perl_Keyword"></interface></span>
+ ...
+ <span class="perl_Keyword"></devices></span>
+</pre></div><h6>Figure J.38. Devices - network interfaces- bridge to LAN</h6></div><br class="figure-break" /></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-userspace-slirp-stack"><div class="titlepage"><div><div><h4 class="title">J.16.9.3. Userspace SLIRP stack</h4></div></div></div><div class="para">
+ Setting the userspace SLIRP stack parameters provides a virtual LAN with NAT to the outside world. The virtual network has DHCP and DNS services and will give the guest virtual machine an IP addresses starting from 10.0.2.15. The default router will be 10.0.2.2 and the DNS server will be 10.0.2.3. This networking is the only option for unprivileged users who need their guest virtual machines to have outgoing access.
+ </div><div class="para">
+ The userspace SLIP stack parameters are defined in the following part of the domain XML::
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-usr-spc-slip"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'user'</span><span class="perl_Keyword">/></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'user'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">"00:11:22:33:44:55"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.39. Devices - network interfaces- Userspace SLIRP stack</h6></div><br class="figure-break" /></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-generic-ethernet-connection"><div class="titlepage"><div><div><h4 class="title">J.16.9.4. Generic Ethernet connection</h4></div></div></div><div class="para">
+ Provides a means for the administrator to execute an arbitrary script to connect the guest's network to the LAN. The guest will have a <code class="sgmltag-element">tun</code> device created with a name of <code class="sgmltag-element">vnetN</code>, which can also be overridden with the <code class="sgmltag-element">target</code> element. After creating the <code class="sgmltag-element">tun</code> device a shell script will be run which is expected to do whatever host network integration is required. By default this script is called <code class="filename">/etc/qemu-ifup</code> but can be overridden (refer to <a class="xref" href="#sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element">Section J.16.9.10, “Overriding the target element”</a>).
+ </div><div class="para">
+ The generic Ethernet connection parameters are defined in the following part of the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-gen-eth-con"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'ethernet'</span><span class="perl_Keyword">/></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'ethernet'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet7'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><script</span><span class="perl_Others"> path=</span><span class="perl_String">'/etc/qemu-ifup-mynet'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.40. Devices - network interfaces- generic Ethernet connection</h6></div><br class="figure-break" /></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-direct-attachment-to-physical-device"><div class="titlepage"><div><div><h4 class="title">J.16.9.5. Direct attachment to physical interfaces</h4></div></div></div><div class="para">
+ Manipulating the direct attachment to physical interfaces provides direct attachment of the guest virtual machine's NIC to the given taht the physial interface of the host is specified.
+ </div><div class="para">
+ This setup requires the Linux macvtap driver to be available. One of the modes <code class="sgmltag-element">vepa</code> ( 'Virtual Ethernet Port Aggregator'), <code class="sgmltag-element">bridge</code> or <code class="sgmltag-element">private</code> can be chosen for the operation mode of the macvtap device, <code class="sgmltag-element">vepa</code> being the default mode.
+ </div><div class="para">
+ Manipulating direct attachment to physical interfaces involves setting the following parameters in the following part of the domain XML.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-dir-att-2phys"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'direct'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> dev=</span><span class="perl_String">'eth0'</span><span class="perl_Others"> mode=</span><span class="perl_String">'vepa'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.41. Devices - network interfaces- direct attachment to physical interfaces</h6></div><br class="figure-break" /><div class="para">
+ The individual modes cause the delivery of packets to behave as shown in <a class="xref" href="#table-libvirt-dom-xml-gen-direct-attachment-physical-interface">Table J.17, “Direct attachment to physical interface elements”</a>:
+ </div><div class="table" id="table-libvirt-dom-xml-gen-direct-attachment-physical-interface"><h6>Table J.17. Direct attachment to physical interface elements</h6><div class="table-contents"><table summary="Direct attachment to physical interface elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-attribute">vepa</code>
+ </td><td class="">
+ All of the guest virtual machines' packets are sent to the external bridge. Packets whose destination is a guest virtual machine on the same host as where the packet originates from are sent back to the host by the VEPA capable bridge (today's bridges are typically not VEPA capable).
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">bridge</code>
+ </td><td class="">
+ Packets whose destination is on the same host as where they originate from are directly delivered to the target macvtap device. Both origin and destination devices need to be in bridge mode for direct delivery. If either one of them is in <code class="sgmltag-attribute">vepa</code> mode, a VEPA capable bridge is required.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">private</code>
+ </td><td class="">
+ All packets are sent to the external bridge and will only be delivered to a target VM on the same host if they are sent through an external router or gateway and that device sends them back to the host. This procedure is followed if either the source or destination device is in private mode.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">passthrough</code>
+ </td><td class="">
+ This feature attaches a virtual function of a SRIOV capable NIC directly to a guest virtual machine without losing the migration capability. All packets are sent to the VF/IF of the configured network device. Depending on the capabilities of the device additional prerequisites or limitations may apply; for example, this requires kernel 2.6.38 or newer.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The network access of direct attached virtual machines can be managed by the hardware switch to which the physical interface of the host machine is connected to.
+ </div><div class="para">
+ The interface can have additional parameters as shown below, if the switch is conforming to the IEEE 802.1Qbg standard. The parameters of the virtualport element are documented in more detail in the IEEE 802.1Qbg standard. The values are network specific and should be provided by the network administrator. In 802.1Qbg terms, the Virtual Station Interface (VSI) represents the virtual interface of a virtual machine.
+ </div><div class="para">
+ Note that IEEE 802.1Qbg requires a non-zero value for the VLAN ID.
+ </div><div class="para">
+ Additional elements that can be manipulated are described in <a class="xref" href="#table-libvirt-dom-xml-gen-direct-attachment-physical-interface2">Table J.18, “Direct attachment to physical interface additional elements”</a>:
+ </div><div class="table" id="table-libvirt-dom-xml-gen-direct-attachment-physical-interface2"><h6>Table J.18. Direct attachment to physical interface additional elements</h6><div class="table-contents"><table summary="Direct attachment to physical interface additional elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-attribute">managerid</code>
+ </td><td class="">
+ The VSI Manager ID identifies the database containing the VSI type and instance definitions. This is an integer value and the value <code class="sgmltag-element">0</code> is reserved.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">typeid</code>
+ </td><td class="">
+ The VSI Type ID identifies a VSI type characterizing the network access. VSI types are typically managed by network administrator. This is an integer value.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">typeidversion</code>
+ </td><td class="">
+ The VSI Type Version allows multiple versions of a VSI Type. This is an integer value.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">instanceid</code>
+ </td><td class="">
+ The VSI Instance ID Identifier is generated when a VSI instance (i.e. a virtual interface of a virtual machine) is created. This is a globally unique identifier.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">profileid</code>
+ </td><td class="">
+ The profile ID contains the name of the port profile that is to be applied onto this interface. This name is resolved by the port profile database into the network parameters from the port profile, and those network parameters will be applied to this interface.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Additional parameters in the domain XML include:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-dir-att-2phys2"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'direct'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> dev=</span><span class="perl_String">'eth0.2'</span><span class="perl_Others"> mode=</span><span class="perl_String">'vepa'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><virtualport</span><span class="perl_Others"> type=</span><span class="perl_String">"802.1Qbg"</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><parameters</span><span class="perl_Others"> managerid=</span><span class="perl_String">"11"</span><span class="perl_Others"> typeid=</span><span class="perl_String">"1193047"</span><span class="perl_Others"> typeidversion=</span><span class="perl_String">"2"</span><span class="perl_Others"> instanceid=</span><span class="perl_String">"09b11c53-8b5c-4eeb-8f00-d84eaa0aaa4f"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></virtualport></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.42. Devices - network interfaces- direct attachment to physical interfaces additional parameters</h6></div><br class="figure-break" /><div class="para">
+ The interface can have additional parameters as shown below if the switch is conforming to the IEEE 802.1Qbh standard. The values are network specific and should be provided by the network administrator.
+ </div><div class="para">
+ Additional parameters in the domain XML include:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-dir-att-2phys3"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'direct'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> dev=</span><span class="perl_String">'eth0'</span><span class="perl_Others"> mode=</span><span class="perl_String">'private'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><virtualport</span><span class="perl_Others"> type=</span><span class="perl_String">'802.1Qbh'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><parameters</span><span class="perl_Others"> profileid=</span><span class="perl_String">'finance'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></virtualport></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.43. Devices - network interfaces- direct attachment to physical interfaces more additional parameters</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-attribute">profileid</code> attribute, contains the name of the port profile that is to be applied to this interface. This name is resolved by the port profile database into the network parameters from the port profile, and those network parameters will be applied to this interface.
+ </div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-pci-passthrough"><div class="titlepage"><div><div><h4 class="title">J.16.9.6. PCI passthrough</h4></div></div></div><div class="para">
+ A PCI network device (specified by the <code class="sgmltag-element">source</code> element) is directly assigned to the guest using generic device passthrough, after first optionally setting the device's MAC address to the configured value, and associating the device with an 802.1Qbh capable switch using an optionally specified <code class="sgmltag-element">virtualport</code> element (see the examples of virtualport given above for type='direct' network devices). Note that - due to limitations in standard single-port PCI ethernet card driver design - only SR-IOV (Single Root I/O Virtualization) virtual function (VF) devices can be assigned in this manner; to assign a standard single-port PCI or PCIe ethernet card to a guest, use the traditional <code class="sgmltag-element">hostdev</code> device definition
+ </div><div class="para">
+ Note that this "intelligent passthrough" of network devices is very similar to the functionality of a standard <code class="sgmltag-element">hostdev</code> device, the difference being that this method allows specifying a MAC address and <code class="sgmltag-attribute">virtualport</code> for the passed-through device. If these capabilities are not required, if you have a standard single-port PCI, PCIe, or USB network card that doesn't support SR-IOV (and hence would anyway lose the configured MAC address during reset after being assigned to the guest domain), or if you are using a version of libvirt older than 0.9.11, you should use standard <code class="sgmltag-attribute">hostdev</code> to assign the device to the guest instead of <code class="sgmltag-attribute">interface type='hostdev'/</code>.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-pci-pass"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'hostdev'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">'vfio'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'pci'</span><span class="perl_Others"> domain=</span><span class="perl_String">'0x0000'</span><span class="perl_Others"> bus=</span><span class="perl_String">'0x00'</span><span class="perl_Others"> slot=</span><span class="perl_String">'0x07'</span><span class="perl_Others"> function=</span><span class="perl_String">'0x0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></source></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">'52:54:00:6d:90:02'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><virtualport</span><span class="perl_Others"> type=</span><span class="perl_String">'802.1Qbh'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><parameters</span><span class="perl_Others"> profileid=</span><span class="perl_String">'finance'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></virtualport></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.44. Devices - network interfaces- PCI passthrough</h6></div><br class="figure-break" /></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-multicast-tunnel"><div class="titlepage"><div><div><h4 class="title">J.16.9.7. Multicast tunnel</h4></div></div></div><div class="para">
+ A multicast group may be used to represent a virtual network. Any guest virtual machine whose network devices are within the same multicast group will talk to each other, even if they reside across miltiple physical hosts. This mode may be used as an unprivileged user. There is no default DNS or DHCP support and no outgoing network access. To provide outgoing network access, one of the guest virtual machines should have a second NIC which is connected to one of the first 4 network types in order to provide appropriate routing. The multicast protocol is compatible with protocols used by <code class="command">user mode</code> linux guests as well. Note that the source address used must be from the multicast address block. A multicast tunnel is created by manipulating the <code class="command">interface type</code> using a management tool and setting/changing it to <code class="sgmltag-element">mcast</code>, and providing a mac and source address. The result is shown in ch
anges made to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-multi-cast-tun"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'mcast'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">'52:54:00:6d:90:01'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> address=</span><span class="perl_String">'230.0.0.1'</span><span class="perl_Others"> port=</span><span class="perl_String">'5558'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.45. Devices - network interfaces- multicast tunnel</h6></div><br class="figure-break" /></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-tcp-tunnel"><div class="titlepage"><div><div><h4 class="title">J.16.9.8. TCP tunnel</h4></div></div></div><div class="para">
+ Creating a TCP client/server architecture is another way to provide a virtual network wher one guest virtual machine provides the server end of the network and all other guest virtual machines are configured as clients. All network traffic between the guest virtual machines is routed via the guest virtual machine that is configrured as the server. This model is also available for use to unprivileged users. There is no default DNS or DHCP support and no outgoing network access. To provide outgoing network access, one of the guest virtual machines should have a second NIC which is connected to one of the first 4 network types thereby providing the appropriate routing. A TCP tunnel is created by manipulating the <code class="sgmltag-element">interface type</code> using a management tool and setting/changing it to <code class="sgmltag-element">server</code> or <code class="sgmltag-element">client</code>, and providing a mac and source address. The result is shown in changes
made to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-tcp-tun"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'server'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">'52:54:00:22:c9:42'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> address=</span><span class="perl_String">'192.168.0.1'</span><span class="perl_Others"> port=</span><span class="perl_String">'5558'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'client'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">'52:54:00:8b:c9:51'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> address=</span><span class="perl_String">'192.168.0.1'</span><span class="perl_Others"> port=</span><span class="perl_String">'5558'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.46. Devices - network interfaces- TCP tunnel</h6></div><br class="figure-break" /></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-setting-nic-driver-specific-options"><div class="titlepage"><div><div><h4 class="title">J.16.9.9. Setting NIC driver-specific options</h4></div></div></div><div class="para">
+ Some NICs may have tunable driver-specific options. These options are set as attributes of the <code class="sgmltag-element">driver</code> sub-element of the interface definition. These options are set by using management toools to configuring the following sections of the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-nic-driver-options"><div class="figure-contents"><pre class="programlisting">
+
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><model</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">'vhost'</span><span class="perl_Others"> txmode=</span><span class="perl_String">'iothread'</span><span class="perl_Others"> ioeventfd=</span><span class="perl_String">'on'</span><span class="perl_Others"> event_idx=</span><span class="perl_String">'off'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.47. Devices - network interfaces- setting NIC driver-specific options</h6></div><br class="figure-break" /><div class="para">
+ Currently the following attributes are available for the "virtio" NIC driver:
+ </div><div class="table" id="table--libvirt-dom-xml-devices-Network-interfaces-setting-nic-driver-specific-options"><h6>Table J.19. virtio NIC driver elements</h6><div class="table-contents"><table summary="virtio NIC driver elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-attribute">name</code>
+ </td><td class="">
+ The optional <code class="sgmltag-attribute">name</code> attribute forces which type of backend driver to use. The value can be either <code class="sgmltag-attribute">qemu</code> (a user-space backend) or <code class="sgmltag-attribute">vhost</code> (a kernel backend, which requires the vhost module to be provided by the kernel); an attempt to require the vhost driver without kernel support will be rejected. The default setting is <code class="sgmltag-attribute">vhost</code> if the vhost driver present, but will silently fall back to <code class="sgmltag-attribute">qemu</code> if not.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">txmode</code>
+ </td><td class="">
+ Specifies how to handle transmission of packets when the transmit buffer is full. The value can be either <code class="sgmltag-attribute">iothread</code> or <code class="sgmltag-attribute">timer</code>. If set to <code class="sgmltag-attribute">iothread</code>, packet tx is all done in an iothread in the bottom half of the driver (this option translates into adding <code class="sgmltag-attvalue">"tx=bh"</code> to the <code class="sgmltag-attribute">qemu</code> commandline -device virtio-net-pci option). If set to <code class="sgmltag-attvalue">timer</code>, tx work is done in qemu, and if there is more tx data than can be sent at the present time, a timer is set before qemu moves on to do other things; when the timer fires, another attempt is made to send more data. In general you should leave this option alone, unless you are very certain you that changing it is an absolute necessity.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">ioeventfd</code>
+ </td><td class="">
+ Allows users to set domain I/O asynchronous handling for interface device. The default is left to the discretion of the hypervisor. Accepted values are <code class="sgmltag-attvalue">on</code> and <code class="sgmltag-attvalue">off </code>. Enabling this option allows qemu to execute a guest virtual machine while a separate thread handles I/O. Typically guest virtual machines experiencing high system CPU utilization during I/O will benefit from this. On the other hand, overloading the physical host may also increase guest I/O latency. Therefore, you should leave this option alone, unless you are very certain you that changing it is an absolute necessity.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">event_idx</code>
+ </td><td class="">
+ The event_idx attribute controls some aspects of device event processing. The value can be either <code class="sgmltag-attvalue">on</code> or <code class="sgmltag-attvalue">off</code>. Choosing <code class="sgmltag-attvalue">on</code>, reduces the number of interrupts and exits for the guest virtual machine. The default is <code class="sgmltag-attvalue">on</code>. In case there is a situation where this behavior is suboptimal, this attribute provides a way to force the feature off. You should leave this option alone, unless you are very certain you that changing it is an absolute necessity.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element"><div class="titlepage"><div><div><h4 class="title">J.16.9.10. Overriding the target element</h4></div></div></div><div class="para">
+ To override the target element, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-overriding-the-target-element"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.48. Devices - network interfaces- overriding the target element</h6></div><br class="figure-break" /><div class="para">
+ If no target is specified, certain hypervisors will automatically generate a name for the created tun device. This name can be manually specifed, however the name must not start with either 'vnet' or 'vif', which are prefixes reserved by libvirt and certain hypervisors. Manually specified targets using these prefixes will be ignored.
+ </div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-boot-order"><div class="titlepage"><div><div><h4 class="title">J.16.9.11. Specifying boot order</h4></div></div></div><div class="para">
+ To specify the boot order, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig--libvirt-dom-xml-devices-Network-interfaces-boot-order"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.49. Specifying boot order</h6></div><br class="figure-break" /><div class="para">
+ For hypervisors which support it, you can set a specific NIC to be used for the network boot. The order of attributes determine the order in which devices will be tried during boot sequence. Note that the per-device boot elements cannot be used together with general boot elements in BIOS bootloader section.
+ </div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-interface-ROM-BIOS-configuration"><div class="titlepage"><div><div><h4 class="title">J.16.9.12. Interface ROM BIOS configuration</h4></div></div></div><div class="para">
+ To specify the ROM BIOS configuration settings, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-interface-ROM-BIOS-configuration"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><rom</span><span class="perl_Others"> bar=</span><span class="perl_String">'on'</span><span class="perl_Others"> file=</span><span class="perl_String">'/etc/fake/boot.bin'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.50. Interface ROM BIOS configuration</h6></div><br class="figure-break" /><div class="para">
+ For hypervisors which support it, you can change how a PCI Network device's ROM is presented to the guest virtual machine. The <code class="sgmltag-attribute">bar</code> attribute can be set to <code class="sgmltag-element">on</code> or <code class="sgmltag-element">off</code>, and determines whether or not the device's ROM will be visible in the guest's memory map. (In PCI documentation, the "rombar" setting controls the presence of the Base Address Register for the ROM). If no rom bar is specified, the qemu default will be used (older versions of qemu used a default of <code class="sgmltag-element">off</code>, while newer qemus have a default of <code class="sgmltag-element">on</code>). The optional <code class="sgmltag-element">file</code> attribute is used to point to a binary file to be presented to the guest as the device's ROM BIOS. This can be useful to provide an alternative boot ROM for a network device.
+ </div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-qos"><div class="titlepage"><div><div><h4 class="title">J.16.9.13. Quality of service</h4></div></div></div><div class="para">
+ This section of the domain XML provides setting quality of service. Incoming and outgoing traffic can be shaped independently. The <code class="sgmltag-element">bandwidth</code> element can have at most one inbound and at most one outbound child elements. Leaving any of these children element out results in no QoS being applied on that traffic direction. Therefore, when you want to shape only domain's incoming traffic, use inbound only, and vice versa.
+ </div><div class="para">
+ Each of these elements has one mandatory attribute <code class="sgmltag-attribute">average</code> (or <code class="sgmltag-attribute">floor</code> as described below). <code class="sgmltag-attribute">average</code> specifies average bit rate on the interface being shaped. Then there are two optional attributes: <code class="sgmltag-attribute">peak</code>, which specifies maximum rate at which interface can send data, and <code class="sgmltag-attribute">burst</code>, which specifies the amount of bytes that can be burst at peak speed. Accepted values for attributes are integer numbers.
+ </div><div class="para">
+ The units for <code class="sgmltag-attribute">average</code> and <code class="sgmltag-attribute">peak</code> attributes are kilobytes per second, whereas <code class="sgmltag-attribute">burst</code> is only set in kilobytes. In addtion, inbound traffic can optionally have a <code class="sgmltag-attribute">floor</code> attribute. This guarantees minimal throughput for shaped interfaces. Using the <code class="sgmltag-attribute">floor</code> requires that all traffic goes through one point where QoS decisions can take place. As such it may only be used in cases where the <code class="sgmltag-element">interface type='network'/</code> with a <code class="sgmltag-element">forward</code> type of <code class="sgmltag-element">route</code>, <code class="sgmltag-element">nat</code>, or no forward at all). It should be noted that within a virtual network, all connected interfaces are required to have at least the inbound QoS set (<code class="sgmltag-element">average</code> at le
ast) but the floor attribute doesn't require specifying <code class="sgmltag-element">average</code>. However, <code class="sgmltag-element">peak</code> and <code class="sgmltag-element">burst</code> attributes still require <code class="sgmltag-element">average</code>. At the present time, ingress qdiscs may not have any classes, and therefore <code class="sgmltag-attribute">floor</code> may only be applied only on inbound and not outbound traffic.
+ </div><div class="para">
+ To specify the QoS configuration settings, use a managment tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-qos"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><bandwidth></span>
+ <span class="perl_Keyword"><inbound</span><span class="perl_Others"> average=</span><span class="perl_String">'1000'</span><span class="perl_Others"> peak=</span><span class="perl_String">'5000'</span><span class="perl_Others"> floor=</span><span class="perl_String">'200'</span><span class="perl_Others"> burst=</span><span class="perl_String">'1024'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><outbound</span><span class="perl_Others"> average=</span><span class="perl_String">'128'</span><span class="perl_Others"> peak=</span><span class="perl_String">'256'</span><span class="perl_Others"> burst=</span><span class="perl_String">'256'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></bandwidth></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><devices></span>
+ ...
+</pre></div><h6>Figure J.51. Quality of service</h6></div><br class="figure-break" /></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-setting-vlan-tag"><div class="titlepage"><div><div><h4 class="title">J.16.9.14. Setting VLAN tag (on supported network types only)</h4></div></div></div><div class="para">
+ To specify the VLAN tag configuration settings, use a mangement tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-setting-vlan-tag"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'bridge'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><vlan></span>
+ <span class="perl_Keyword"><tag</span><span class="perl_Others"> id=</span><span class="perl_String">'42'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></vlan></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> bridge=</span><span class="perl_String">'ovsbr0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><virtualport</span><span class="perl_Others"> type=</span><span class="perl_String">'openvswitch'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><parameters</span><span class="perl_Others"> interfaceid=</span><span class="perl_String">'09b11c53-8b5c-4eeb-8f00-d84eaa0aaa4f'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></virtualport></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><devices></span>
+ ...
+
+</pre></div><h6>Figure J.52. Setting VLAN tag (on supported network types only)</h6></div><br class="figure-break" /><div class="para">
+ If (and only if) the network connection used by the guest supports vlan tagging transparent to the guest, an optional <code class="sgmltag-element">vlan</code> element can specify one or more vlan tags to apply to the guest's network traffic (openvswitch and <code class="sgmltag-element">type='hostdev'</code> SR-IOV interfaces do support transparent vlan tagging of guest traffic; everything else, including standard linux bridges and libvirt's own virtual networks, do not support it. 802.1Qbh (vn-link) and 802.1Qbg (VEPA) switches provide their own way (outside of libvirt) to tag guest traffic onto specific vlans.) To allow for specification of multiple tags (in the case of vlan trunking), a subelement, <code class="sgmltag-element">tag</code>, specifies which vlan tag to use (for example: <code class="sgmltag-attribute">tag id='42'/</code>. If an interface has more than one <code class="sgmltag-element">vlan</code> element defined, it is assumed that the user wants to d
o VLAN trunking using all the specified tags. In the case that vlan trunking with a single tag is desired, the optional attribute <code class="sgmltag-attribute">trunk='yes'</code> can be added to the toplevel vlan element.
+ </div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-modifying-virtual-link-state"><div class="titlepage"><div><div><h4 class="title">J.16.9.15. Modifying virtual link state</h4></div></div></div><div class="para">
+ This element provides means of setting state of the virtual network link. Possible values for attribute <code class="sgmltag-attribute">state</code> are <code class="sgmltag-attvalue">up</code> and <code class="sgmltag-attvalue">down</code>. If <code class="sgmltag-attvalue">down</code> is specified as the value, the interface behaves as if it had the network cable disconnected. Default behavior if this element is unspecified is to have the link state <code class="sgmltag-attvalue">up</code>.
+ </div><div class="para">
+ To specify the virtual link state configuration settings, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-dom-xml-devices-modifying-virtual-link-state"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><link</span><span class="perl_Others"> state=</span><span class="perl_String">'down'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><devices></span>
+ ...
+</pre></div><h6>Figure J.53. Modifying virtual link state</h6></div><br class="figure-break" /></div></div><div class="section" id="sub-section-libvirt-dom-xml-devices-input-devices"><div class="titlepage"><div><div><h3 class="title">J.16.10. Input devices</h3></div></div></div><div class="para">
+ Input devices allow interaction with the graphical framebuffer in the guest virtual machine. When enabling the framebuffer, an input device is automatically provided. It may be possible to add additional devices explicitly, for example, to provide a graphics tablet for absolute cursor movement.
+ </div><div class="para">
+ To specify the input devices configuration settings, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-input-devices"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><input</span><span class="perl_Others"> type=</span><span class="perl_String">'mouse'</span><span class="perl_Others"> bus=</span><span class="perl_String">'usb'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+
+</pre></div><h6>Figure J.54. Input devices</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-starttag"><input></code> element has one mandatory attribute: <code class="sgmltag-attribute">type</code> which can be set to: <code class="sgmltag-attvalue">mouse</code> or <code class="sgmltag-attvalue">tablet</code>. The latter provides absolute cursor movement, while the former uses relative movement. The optional <code class="sgmltag-attribute">bus</code> attribute can be used to refine the exact device type and can be set to: <code class="sgmltag-attvalue">xen</code> (paravirtualized), <code class="sgmltag-attvalue">ps2</code>, and <code class="sgmltag-attvalue">usb</code>.
+ </div><div class="para">
+ The input element has an optional sub-element <code class="sgmltag-starttag"><address></code>, which can tie the device to a particular PCI slot, as documented above.
+ </div></div><div class="section" id="sub-section-libvirt-dom-xml-devices-hub-devices"><div class="titlepage"><div><div><h3 class="title">J.16.11. Hub devices</h3></div></div></div><div class="para">
+ A hub is a device that expands a single port into several so that there are more ports available to connect devices to a host system.
+ </div><div class="para">
+ To specify the hub devices configuration settings, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-xml-devices-hub-devices"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><hub</span><span class="perl_Others"> type=</span><span class="perl_String">'usb'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.55. Hub devices</h6></div><br class="figure-break" /><div class="para">
+ The hub element has one mandatory attribute, the type whose value can only be <code class="sgmltag-element">usb</code>. The hub element has an optional sub-element <code class="sgmltag-element">address</code> with <code class="sgmltag-attribute">type='usb'</code>which can tie the device to a particular controller.
+ </div></div><div class="section" id="sub-section-libvirt-dom-xml-devices-graphical-framebuffers"><div class="titlepage"><div><div><h3 class="title">J.16.12. Graphical framebuffers</h3></div></div></div><div class="para">
+ A graphics device allows for graphical interaction with the guest OS. A guest will typically have either a framebuffer or a text console configured to allow interaction with the admin.
+ </div><div class="para">
+ To specify the graphical framebuffer devices configuration settings, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig--xml-devices-graphical-framebuffers"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'sdl'</span><span class="perl_Others"> display=</span><span class="perl_String">':0.0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'vnc'</span><span class="perl_Others"> port=</span><span class="perl_String">'5904'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><listen</span><span class="perl_Others"> type=</span><span class="perl_String">'address'</span><span class="perl_Others"> address=</span><span class="perl_String">'1.2.3.4'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></graphics></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'rdp'</span><span class="perl_Others"> autoport=</span><span class="perl_String">'yes'</span><span class="perl_Others"> multiUser=</span><span class="perl_String">'yes'</span> <span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'desktop'</span><span class="perl_Others"> fullscreen=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'spice'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><listen</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Others"> network=</span><span class="perl_String">'rednet'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></graphics></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.56. Graphical framebuffers</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-element">graphics</code> element has a mandatory <code class="sgmltag-attribute">type</code> attribute which takes the value <code class="sgmltag-element">sdl</code>, <code class="sgmltag-element">vnc</code>, <code class="sgmltag-element">rdp</code> or <code class="sgmltag-element">desktop</code> as explained below:
+ </div><div class="table" id="table--libvirt-dom-xml-devices-Network-interfaces-setting-graphical-framebuffer-sgmltags"><h6>Table J.20. Graphical framebuffer elements</h6><div class="table-contents"><table summary="Graphical framebuffer elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-element">sdl</code>
+ </td><td class="">
+ This displays a window on the host desktop, it can take 3 optional arguments: a <code class="sgmltag-attribute">display</code> attribute for the display to use, an <code class="sgmltag-attribute">xauth</code> attribute for the authentication identifier, and an optional <code class="sgmltag-attribute">fullscreen</code> attribute accepting values <code class="sgmltag-element">yes</code> or <code class="sgmltag-element">no</code>
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">vnc</code>
+ </td><td class="">
+ Starts a VNC server. The <code class="sgmltag-attribute">port</code> attribute specifies the TCP port number (with <code class="sgmltag-element">-1</code> as legacy syntax indicating that it should be auto-allocated). The <code class="sgmltag-attribute">autoport</code> attribute is the new preferred syntax for indicating autoallocation of the TCP port to use. The <code class="sgmltag-attribute">listen</code> attribute is an IP address for the server to listen on. The <code class="sgmltag-attribute">passwd</code> attribute provides a VNC password in clear text. The <code class="sgmltag-attribute">keymap</code> attribute specifies the keymap to use. It is possible to set a limit on the validity of the password be giving an <code class="sgmltag-element">timestamp passwdValidTo='2010-04-09T15:51:00'</code> assumed to be in UTC. The <code class="sgmltag-attribute">connected</code> attribute allows control of connected client during password changes. VNC accepts <code clas
s="sgmltag-element">keep</code> value only and note that it may not be supported by all hypervisors. Rather than using listen/port, QEMU supports a socket attribute for listening on a unix domain socket path.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">spice</code>
+ </td><td class="">
+ Starts a SPICE server. The <code class="sgmltag-attribute">port</code> attribute specifies the TCP port number (with -1 as legacy syntax indicating that it should be auto-allocated), while <code class="sgmltag-element">tlsPort</code> gives an alternative secure port number. The <code class="sgmltag-attribute">autoport</code> attribute is the new preferred syntax for indicating autoallocation of both port numbers. The <code class="sgmltag-attribute">listen</code> attribute is an IP address for the server to listen on. The <code class="sgmltag-attribute">passwd</code> attribute provides a SPICE password in clear text. The <code class="sgmltag-attribute">keymap</code> attribute specifies the keymap to use. It is possible to set a limit on the validity of the password be giving an <code class="sgmltag-attribute">timestamp passwdValidTo='2010-04-09T15:51:00'</code> assumed to be in UTC. The <code class="sgmltag-attribute">connected</code> attribute allows control of conne
cted client during password changes. SPICE accepts keep to keep client connected, disconnect to disconnect client and fail to fail changing password. Note it is not be supported by all hypervisors. The <code class="sgmltag-attribute">defaultMode</code> attribute sets the default channel security policy, valid values are <code class="sgmltag-element">secure</code>, <code class="sgmltag-element">insecure</code> and the default <code class="sgmltag-element">any</code> (which is <code class="sgmltag-element">secure</code> if possible, but falls back to <code class="sgmltag-element">insecure</code> rather than erroring out if no secure path is available).
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ When SPICE has both a normal and TLS secured TCP port configured, it may be desirable to restrict what channels can be run on each port. This is achieved by adding one or more <code class="sgmltag-element">channel</code> elements inside the main <code class="sgmltag-element">graphics</code> element. Valid channel names include <code class="sgmltag-element">main</code>, <code class="sgmltag-element">display</code>, <code class="sgmltag-element">inputs</code>, <code class="sgmltag-element">cursor</code>, <code class="sgmltag-element">playback</code>, <code class="sgmltag-element">record</code>; <code class="sgmltag-element">smartcard</code>; and <code class="sgmltag-element">usbredir</code>.
+ </div><div class="para">
+ To specify the SPICE configuration settings, use a mangement tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-:devices-Network-interfaces-setting-graphical-framebuffer-sgmltags-spice-cfg"><div class="figure-contents"><pre class="programlisting">
+
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'spice'</span><span class="perl_Others"> port=</span><span class="perl_String">'-1'</span><span class="perl_Others"> tlsPort=</span><span class="perl_String">'-1'</span><span class="perl_Others"> autoport=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> name=</span><span class="perl_String">'main'</span><span class="perl_Others"> mode=</span><span class="perl_String">'secure'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> name=</span><span class="perl_String">'record'</span><span class="perl_Others"> mode=</span><span class="perl_String">'insecure'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><image</span><span class="perl_Others"> compression=</span><span class="perl_String">'auto_glz'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><streaming</span><span class="perl_Others"> mode=</span><span class="perl_String">'filter'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><clipboard</span><span class="perl_Others"> copypaste=</span><span class="perl_String">'no'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><mouse</span><span class="perl_Others"> mode=</span><span class="perl_String">'client'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></graphics></span>
+</pre></div><h6>Figure J.57. SPICE configuration</h6></div><br class="figure-break" /><div class="para">
+ SPICE supports variable compression settings for audio, images and streaming. These settings are accessible via the compression attribute in all following elements: <code class="sgmltag-element">image</code> to set image compression (accepts auto_glz, auto_lz, quic, glz, lz, off), <code class="sgmltag-element">jpeg</code> for JPEG compression for images over wan (accepts auto, never, always), <code class="sgmltag-element">zlib</code> for configuring wan image compression (accepts auto, never, always) and <code class="sgmltag-element">playback</code> for enabling audio stream compression (accepts on or off).
+ </div><div class="para">
+ Streaming mode is set by the <code class="sgmltag-element">streaming</code> element, settings its <code class="sgmltag-attribute">mode</code> attribute to one of <code class="sgmltag-element">filter</code>, <code class="sgmltag-element">all</code> or <code class="sgmltag-element">off</code>.
+ </div><div class="para">
+ In addition, Copy and paste functionality (via the SPICE agent) is set by the <code class="sgmltag-element">clipboard</code> element. It is enabled by default, and can be disabled by setting the <code class="sgmltag-attribute">copypaste</code> property to <code class="sgmltag-element">no</code>.
+ </div><div class="para">
+ Mouse mode is set by the <code class="sgmltag-element">mouse</code> element, setting its <code class="sgmltag-attribute">mode</code> attribute to one of <code class="sgmltag-element">server</code> or <code class="sgmltag-element">client</code>. If no mode is specified, the qemu default will be used (<code class="sgmltag-element">client</code> mode).
+ </div><div class="para">
+ Additional elements include:
+ </div><div class="table" id="table-libvirt-dom-xml-devices-Network-interfaces-setting-graphical-framebuffer-options2"><h6>Table J.21. Additional graphical framebuffer elements</h6><div class="table-contents"><table summary="Additional graphical framebuffer elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-element">rdp</code>
+ </td><td class="">
+ Starts a RDP server. The port attribute specifies the TCP port number (with -1 as legacy syntax indicating that it should be auto-allocated). The autoport attribute is the new preferred syntax for indicating autoallocation of the TCP port to use. The replaceUser attribute is a boolean deciding whether multiple simultaneous connections to the VM are permitted. The multiUser whether the existing connection must be dropped and a new connection must be established by the VRDP server, when a new client connects in single connection mode.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">desktop</code>
+ </td><td class="">
+ This value is reserved for VirtualBox domains for the moment. It displays a window on the host desktop, similarly to "sdl", but uses the VirtualBox viewer. Just like "sdl", it accepts the optional attributes display and fullscreen.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">listen</code>
+ </td><td class="">
+ Rather than putting the address information used to set up the listening socket for graphics types vnc and spice in the <code class="sgmltag-element">graphics</code>, the <code class="sgmltag-element">listen</code> attribute, a separate subelement of <code class="sgmltag-element">graphics</code>, called <code class="sgmltag-element">listen</code> can be specified (see the examples above). <code class="sgmltag-element">listen</code> accepts the following attributes:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code> - Set to either address or network. This tells whether this listen element is specifying the address to be used directly, or by naming a network (which will then be used to determine an appropriate address for listening).
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">address</code> - this attribute will contain either an IP address or hostname (which will be resolved to an IP address via a DNS query) to listen on. In the "live" XML of a running domain, this attribute will be set to the IP address used for listening, even if <code class="sgmltag-attribute">type='network'</code>.
+ </div></li><li class="listitem"><div class="para">
+ network - if <code class="sgmltag-attribute">type='network'</code>, the network attribute will contain the name of a network in libvirt's list of configured networks. The named network configuration will be examined to determine an appropriate listen address. For example, if the network has an IPv4 address in its configuration (e.g. if it has a forward type of route, nat, or no forward type (isolated)), the first IPv4 address listed in the network's configuration will be used. If the network is describing a host bridge, the first IPv4 address associated with that bridge device will be used, and if the network is describing one of the 'direct' (macvtap) modes, the first IPv4 address of the first forward dev will be used.
+ </div></li></ul></div>
+
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-section-libvirt-dom-xml-devices-video"><div class="titlepage"><div><div><h3 class="title">J.16.13. Video devices</h3></div></div></div><div class="para">
+ A video device.
+ </div><div class="para">
+ To specify the video devices configuration settings, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-devices-video"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><video></span>
+ <span class="perl_Keyword"><model</span><span class="perl_Others"> type=</span><span class="perl_String">'vga'</span><span class="perl_Others"> vram=</span><span class="perl_String">'8192'</span><span class="perl_Others"> heads=</span><span class="perl_String">'1'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><acceleration</span><span class="perl_Others"> accel3d=</span><span class="perl_String">'yes'</span><span class="perl_Others"> accel2d=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></model></span>
+ <span class="perl_Keyword"></video></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.58. Video devices</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-element">graphics</code> element has a mandatory <code class="sgmltag-attribute">type</code> attribute which takes the value "sdl", "vnc", "rdp" or "desktop" as explained below:
+ </div><div class="table" id="table-libvirt-dom-xml-devices-Network-interfaces-setting-graphical-framebuffer-options"><h6>Table J.22. Graphical framebuffer elements</h6><div class="table-contents"><table summary="Graphical framebuffer elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-element">video</code>
+ </td><td class="">
+ The <code class="sgmltag-element">video</code> element is the container for describing video devices. For backwards compatibility, if no video is set but there is a <code class="sgmltag-element">graphics</code> element in domain xml, then libvirt will add a default <code class="sgmltag-element">video</code> according to the guest type. If "ram" or "vram" are not supplied a default value is used.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">model</code>
+ </td><td class="">
+ This has a mandatory <code class="sgmltag-attribute">type</code> attribute which takes the value <code class="sgmltag-element">vga</code>, <code class="sgmltag-element">cirrus</code>, <code class="sgmltag-element">vmvga</code>, <code class="sgmltag-element">xen</code>, <code class="sgmltag-element">vbox</code>, or <code class="sgmltag-element">qxl</code> depending on the hypervisor features available. You can also provide the amount of video memory in kibibytes (blocks of 1024 bytes) using vram and the number of figure with heads.
+ </td></tr><tr><td class="">
+ acceleration
+ </td><td class="">
+ If acceleration is supported it should be enabled using the <code class="sgmltag-attribute">accel3d</code> and <code class="sgmltag-attribute">accel2d</code> attributes in the <code class="sgmltag-element">acceleration</code> element.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">address</code>
+ </td><td class="">
+ The optional address sub-element can be used to tie the video device to a particular PCI slot.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-section-libvirt-dom-xml-devices-consoles"><div class="titlepage"><div><div><h3 class="title">J.16.14. Consoles, serial, parallel, and channel devices</h3></div></div></div><div class="para">
+ A character device provides a way to interact with the virtual machine. Paravirtualized consoles, serial ports, parallel ports and channels are all classed as character devices and so represented using the same syntax.
+ </div><div class="para">
+ To specify the consols, channel and other devices configuration settings, use a mangement tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-dom-xml-devices-consoles"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><parallel</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/2'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></parallel></span>
+ <span class="perl_Keyword"><serial</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/3'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></serial></span>
+ <span class="perl_Keyword"><console</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/4'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></console></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> type=</span><span class="perl_String">'unix'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'bind'</span><span class="perl_Others"> path=</span><span class="perl_String">'/tmp/guestfwd'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'guestfwd'</span><span class="perl_Others"> address=</span><span class="perl_String">'10.0.2.1'</span><span class="perl_Others"> port=</span><span class="perl_String">'4600'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></channel></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.59. Consoles, serial, parallel, and channel devices</h6></div><br class="figure-break" /><div class="para">
+ In each of these directives, the top-level element name (parallel, serial, console, channel) describes how the device is presented to the guest. The guest interface is configured by the target element. The interface presented to the host is given in the type attribute of the top-level element. The host interface is configured by the source element. The source element may contain an optional seclabel to override the way that labelling is done on the socket path. If this element is not present, the security label is inherited from the per-domain setting. Each character device element has an optional sub-element <code class="sgmltag-element">address</code> which can tie the device to a particular controller or PCI slot.
+ </div></div><div class="section" id="sub-section-libvirt-dom-xml-devices-guest-interface"><div class="titlepage"><div><div><h3 class="title">J.16.15. Guest interfaces</h3></div></div></div><div class="para">
+ A character device presents itself to the guest as one of the following types.
+ </div><div class="para">
+ To set the parallel port, use a management tool to make the following change to the domain XML
+ </div><div class="figure" id="fig--devices-guest-interface"><div class="figure-contents"><pre class="programlisting">
+
+...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><parallel</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/2'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></parallel></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.60. Guest interface Parallel Port</h6></div><br class="figure-break" /><div class="para">
+ <code class="sgmltag-starttag"><target></code> can have a <code class="sgmltag-attribute">port</code> attribute, which specifies the port number. Ports are numbered starting from 0. There are usually 0, 1 or 2 parallel ports.
+ </div><div class="para">
+ To set the serial port use a management tool to make the following change to the domain XML:
+ </div><div class="figure" id="fig-devices-guest-interface-serial-port"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><serial</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/3'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></serial></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.61. Guest Interface Serial port</h6></div><br class="figure-break" /><div class="para">
+ <code class="sgmltag-starttag"><target></code> can have a <code class="sgmltag-attribute">port</code> attribute, which specifies the port number. Ports are numbered starting from 0. There are usually 0, 1 or 2 serial ports. There is also an optional <code class="sgmltag-attribute">type</code> attribute, which has two choices for its value, one is <code class="sgmltag-attvalue">isa-serial</code>, the other is <code class="sgmltag-attvalue">usb-serial</code>. If <code class="sgmltag-attribute">type</code> is missing, <code class="sgmltag-attvalue">isa-serial</code> will be used by default. For usb-serial an optional sub-element <code class="sgmltag-starttag"><address></code> with <code class="sgmltag-attribute">type='usb'</code> can tie the device to a particular controller, documented above.
+ </div><div class="para">
+ The <code class="sgmltag-starttag"><console></code> element is used to represent interactive consoles. Depending on the type of guest in use, the consoles might be paravirtualized devices, or they might be a clone of a serial device, according to the following rules:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If no <code class="sgmltag-attribute">targetType</code> attribute is set, then the default device <code class="sgmltag-attribute">type</code> is according to the hypervisor's rules. The default <code class="sgmltag-attribute">type</code> will be added when re-querying the XML fed into libvirt. For fully virtualized guests, the default device type will usually be a serial port.
+ </div></li><li class="listitem"><div class="para">
+ If the <code class="sgmltag-attribute">targetType</code> attribute is <code class="sgmltag-element">serial</code>, and if no <code class="sgmltag-starttag"><serial></code> element exists, the console element will be copied to the <code class="sgmltag-starttag"><serial></code> element. If a <code class="sgmltag-starttag"><serial></code> element does already exist, the console element will be ignored.
+ </div></li><li class="listitem"><div class="para">
+ If the <code class="sgmltag-attribute">targetType</code> attribute is not <code class="sgmltag-element">serial</code>, it will be treated normally.
+ </div></li><li class="listitem"><div class="para">
+ Only the first <code class="sgmltag-starttag"><console></code> element may use a <code class="sgmltag-attribute">targetType</code> of <code class="sgmltag-attvalue">serial</code>. Secondary consoles must all be paravirtualized.
+ </div></li><li class="listitem"><div class="para">
+ On s390, the console element may use a targetType of sclp or sclplm (line mode). SCLP is the native console type for s390. There's no controller associated to SCLP consoles.
+ </div></li></ul></div><div class="para">
+ In the example below, a virtio console device is exposed in the guest as /dev/hvc[0-7] (for more information, see http://fedoraproject.org/wiki/Features/VirtioSerial):
+ </div><div class="figure" id="fig-devices-guest-interface-serial-port-virtio-console-device"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><console</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/4'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></console></span>
+
+ <span class="perl_Comment"><!-- KVM virtio console --></span>
+ <span class="perl_Keyword"><console</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/5'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio'</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></console></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Comment"><!-- KVM s390 sclp console --></span>
+ <span class="perl_Keyword"><console</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'sclp'</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></console></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.62. Guest Interface - virtio console device</h6></div><br class="figure-break" /><div class="para">
+ If the console is presented as a serial port, the <code class="sgmltag-starttag"><target></code> element has the same attributes as for a serial port. There is usually only one console.
+ </div></div><div class="section" id="sub-section-libvirt-dom-xml-devices-channel"><div class="titlepage"><div><div><h3 class="title">J.16.16. Channel</h3></div></div></div><div class="para">
+ This represents a private communication channel between the host and the guest and is manipulated by making changes to your guest virtual machine using a management tool that results in changes made to the following section of the domain xml
+ </div><div class="figure" id="fig-dom-xml-devices-channel"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> type=</span><span class="perl_String">'unix'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'bind'</span><span class="perl_Others"> path=</span><span class="perl_String">'/tmp/guestfwd'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'guestfwd'</span><span class="perl_Others"> address=</span><span class="perl_String">'10.0.2.1'</span><span class="perl_Others"> port=</span><span class="perl_String">'4600'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></channel></span>
+
+ <span class="perl_Comment"><!-- KVM virtio channel --></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio'</span><span class="perl_Others"> name=</span><span class="perl_String">'arbitrary.virtio.serial.port.name'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></channel></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> type=</span><span class="perl_String">'unix'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'bind'</span><span class="perl_Others"> path=</span><span class="perl_String">'/var/lib/libvirt/qemu/f16x86_64.agent'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio'</span><span class="perl_Others"> name=</span><span class="perl_String">'org.qemu.guest_agent.0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></channel></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> type=</span><span class="perl_String">'spicevmc'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio'</span><span class="perl_Others"> name=</span><span class="perl_String">'com.redhat.spice.0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></channel></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.63. Channel</h6></div><br class="figure-break" /><div class="para">
+ This can be implemented in a variety of ways. The specific type of <code class="sgmltag-starttag"><channel></code> is given in the <code class="sgmltag-attribute">type</code> attribute of the <code class="sgmltag-starttag"><target></code> element. Different channel types have different target attributes as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">guestfwd</code> - Dictates that TCP traffic sent by the guest to a given IP address and port is forwarded to the channel device on the host. The <code class="sgmltag-element">target</code> element must have address and port attributes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">virtio</code> - Paravirtualized virtio channel. <code class="sgmltag-starttag"><channel></code> is exposed in the guest under <code class="filename">/dev/vport*</code>, and if the optional element <code class="sgmltag-attribute">name</code>is specified, <code class="filename">/dev/virtio-ports/$name</code> (for more info, please see http://fedoraproject.org/wiki/Features/VirtioSerial). The optional element <code class="sgmltag-attribute">address</code> can tie the channel to a particular <code class="sgmltag-attribute">type='virtio-serial'</code> controller, documented above. With QEMU, if name is "org.qemu.guest_agent.0", then libvirt can interact with a guest agent installed in the guest, for actions such as guest shutdown or file system quiescing.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">spicevmc</code> - Paravirtualized SPICE channel. The domain must also have a SPICE server as a graphics device, at which point the host piggy-backs messages across the main channel. The <code class="sgmltag-element">target</code> element must be present, with attribute <code class="sgmltag-attribute">type='virtio';</code> an optional attribute <code class="sgmltag-attribute">name</code> controls how the guest will have access to the channel, and defaults to <code class="sgmltag-attribute">name='com.redhat.spice.0'</code>. The optional <code class="sgmltag-starttag"><address></code> element can tie the channel to a particular <code class="sgmltag-attribute">type='virtio-serial'</code> controller.
+ </div></li></ul></div></div><div class="section" id="sub-section-libvirt-dom-xml-devices-host-interface"><div class="titlepage"><div><div><h3 class="title">J.16.17. Host interface</h3></div></div></div><div class="para">
+ A character device presents itself to the host as one of the following types:
+ </div><div class="table" id="table--libvirt-dom-xml-devices-host-interfaces-character-device-options"><h6>Table J.23. Character device elements</h6><div class="table-contents"><table summary="Character device elements" border="1"><colgroup><col width="33%" /><col width="33%" /><col width="33%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th><th class="">
+ XML snippet
+ </th></tr></thead><tbody><tr><td class="">
+ Domain logfile
+ </td><td class="">
+ Disables all input on the character device, and sends output into the virtual machine's logfile
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><console type='stdio'></code>
+ <code class="sgmltag-starttag"><target port='1'/></code>
+ <code class="sgmltag-endtag"></console></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ Device logfile
+ </td><td class="">
+ A file is opened and all data sent to the character device is written to the file.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="file"></code>
+ <code class="sgmltag-starttag"><source path="/var/log/vm/vm-serial.log"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ Virtual console
+ </td><td class="">
+ Connects the character device to the graphical framebuffer in a virtual console. This is typically accessed via a special hotkey sequence such as "ctrl+alt+3"
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type='vc'></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ Null device
+ </td><td class="">
+ Connects the character device to the void. No data is ever provided to the input. All data written is discarded.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type='null'></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ Pseudo TTY
+ </td><td class="">
+ A Pseudo TTY is allocated using <code class="filename">/dev/ptmx</code>. A suitable client such as <code class="command">virsh console</code> can connect to interact with the serial port locally.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="pty"></code>
+ <code class="sgmltag-starttag"><source path="/dev/pts/3"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ NB Special case
+ </td><td class="">
+ NB special case if <code class="sgmltag-starttag"><console type='pty'></code>, then the TTY path is also duplicated as an attribute <code class="sgmltag-attribute">tty='/dev/pts/3'</code> on the top level <code class="sgmltag-starttag"><console></code> tag. This provides compat with existing syntax for <code class="sgmltag-starttag"><console></code> tags.
+ </td><td class="auto-generated"> </td></tr><tr><td class="">
+ Host device proxy
+ </td><td class="">
+ The character device is passed through to the underlying physical character device. The device types must match, eg the emulated serial port should only be connected to a host serial port - don't connect a serial port to a parallel port.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="dev"></code>
+ <code class="sgmltag-starttag"><source path="/dev/ttyS0"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ Named pipe
+ </td><td class="">
+ The character device writes output to a named pipe. See pipe(7) MAN page for more info.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="pipe"></code>
+ <code class="sgmltag-starttag"><source path="/tmp/mypipe"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ TCP client/server
+ </td><td class="">
+ The character device acts as a TCP client connecting to a remote server.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="tcp"></code>
+ <code class="sgmltag-starttag"><source mode="connect" host="0.0.0.0" service="2445"/></code>
+ <code class="sgmltag-starttag"><protocol type="raw"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ <div class="para">
+ Or as a TCP server waiting for a client connection.
+ </div>
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="tcp"></code>
+ <code class="sgmltag-starttag"><source mode="bind" host="127.0.0.1" service="2445"/></code>
+ <code class="sgmltag-starttag"><protocol type="raw"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ <div class="para">
+ Alternatively you can use telnet instead of raw TCP. In addition, you can also use telnets (secure telnet) and tls.
+ </div>
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="tcp"></code>
+ <code class="sgmltag-starttag"><source mode="connect" host="0.0.0.0" service="2445"/></code>
+ <code class="sgmltag-starttag"><protocol type="telnet"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-starttag"><serial type="tcp"></code>
+ <code class="sgmltag-starttag"><source mode="bind" host="127.0.0.1" service="2445"/></code>
+ <code class="sgmltag-starttag"><protocol type="telnet"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+
+ </td></tr><tr><td class="">
+ UDP network console
+ </td><td class="">
+ The character device acts as a UDP netconsole service, sending and receiving packets. This is a lossy service.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="udp"></code>
+ <code class="sgmltag-starttag"><source mode="bind" host="0.0.0.0" service="2445"/></code>
+ <code class="sgmltag-starttag"><source mode="connect" host="0.0.0.0" service="2445"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ UNIX domain socket client/server
+ </td><td class="">
+ The character device acts as a UNIX domain socket server, accepting connections from local clients.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="unix"></code>
+ <code class="sgmltag-starttag"><source mode="bind" path="/tmp/foo"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr></tbody></table></div></div><br class="table-break" /></div></div><div class="section" id="section-libvirt-dom-xml-sound-devices"><div class="titlepage"><div><div><h2 class="title">J.17. Sound devices</h2></div></div></div><div class="para">
+ A virtual sound card can be attached to the host via the sound element.
+ </div><div class="figure" id="fig-dom-xml-sound-devices"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><sound</span><span class="perl_Others"> model=</span><span class="perl_String">'es1370'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.64. Virtual sound card</h6></div><br class="figure-break" /><div class="para">
+ The sound element has one mandatory attribute, <code class="sgmltag-attribute">model</code>, which specifies what real sound device is emulated. Valid values are specific to the underlying hypervisor, though typical choices are <code class="sgmltag-attvalue">'es1370'</code>, <code class="sgmltag-attvalue">'sb16'</code>, <code class="sgmltag-attvalue">'ac97'</code>, and <code class="sgmltag-attvalue">'ich6'</code>. In addition, a sound element with ich6 model can have optional sub-elements <code class="sgmltag-element">codec</code> to attach various audio codecs to the audio device. If not specified, a default codec will be attached to allow playback and recording. Valid values are <code class="sgmltag-attvalue">'duplex'</code> (advertises a line-in and a line-out) and <code class="sgmltag-attvalue">'micro'</code> (advertises a speaker and a microphone).
+ </div><div class="figure" id="fig-dom-xml-sound-devices2"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><sound</span><span class="perl_Others"> model=</span><span class="perl_String">'ich6'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><codec</span><span class="perl_Others"> type=</span><span class="perl_String">'micro'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><sound/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.65. Sound devices</h6></div><br class="figure-break" /><div class="para">
+ Each sound element has an optional sub-element <code class="sgmltag-starttag"><address></code> which can tie the device to a particular PCI slot, documented above.
+ </div></div><div class="section" id="section-libvirt-dom-xml-watchdog"><div class="titlepage"><div><div><h2 class="title">J.18. Watchdog device</h2></div></div></div><div class="para">
+ A virtual hardware watchdog device can be added to the guest via the <code class="sgmltag-starttag"><watchdog></code> element. The watchdog device requires an additional driver and management daemon in the guest. As merely enabling the watchdog in the libvirt configuration does not do anything useful on its own. Currently there is no support notification when the watchdog fires.
+ </div><div class="figure" id="fig--dom-xml-watchdog"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><watchdog</span><span class="perl_Others"> model=</span><span class="perl_String">'i6300esb'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><watchdog</span><span class="perl_Others"> model=</span><span class="perl_String">'i6300esb'</span><span class="perl_Others"> action=</span><span class="perl_String">'poweroff'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+<span class="perl_Error"><</span>/domain>
+</pre></div><h6>Figure J.66. Watchdog device</h6></div><br class="figure-break" /><div class="para">
+ The following attributes are declared in this XML:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">model</code> - The required <code class="sgmltag-attribute">model</code> attribute specifies what real watchdog device is emulated. Valid values are specific to the underlying hypervisor.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="sgmltag-attribute">model</code> attribute may take the following values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">i6300esb</code> — the recommended device, emulating a PCI Intel 6300ESB
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">ib700</code> — emulates an ISA iBase IB700
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">action</code> - The optional <code class="sgmltag-attribute">action</code> attribute describes what action to take when the watchdog expires. Valid values are specific to the underlying hypervisor. The <code class="sgmltag-attribute">action</code> attribute can have the following values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">reset</code> — default setting, forcefully resets the guest
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">shutdown</code> — gracefully shuts down the guest (not recommended)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">poweroff</code> — forcefully powers off the guest
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">pause</code> — pauses the guest
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">none</code> — does nothing
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">dump</code> — automatically dumps the guest.
+ </div></li></ul></div></li></ul></div><div class="para">
+ Note that the 'shutdown' action requires that the guest is responsive to ACPI signals. In the sort of situations where the watchdog has expired, guests are usually unable to respond to ACPI signals. Therefore using 'shutdown' is not recommended. In addition, the directory to save dump files can be configured by auto_dump_path in file /etc/libvirt/qemu.conf.
+ </div></div><div class="section" id="section-libvirt-dom-xml-memory-baloon-device"><div class="titlepage"><div><div><h2 class="title">J.19. Memory balloon device</h2></div></div></div><div class="para">
+ A virtual memory balloon device is added to all Xen and KVM/QEMU guests. It will be seen as <code class="sgmltag-starttag"><memballoon></code> element. It will be automatically added when appropriate, so there is no need to explicitly add this element in the guest XML unless a specific PCI slot needs to be assigned. Note that if the memballoon device needs to be explicitly disabled, <code class="sgmltag-attribute">model='none'</code> may be used.
+ </div><div class="para">
+ The following example automatically added device with KVM
+ </div><div class="figure" id="fig-dom-xml-memory-baloon-device"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><memballoon</span><span class="perl_Others"> model=</span><span class="perl_String">'virtio'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.67. Memory balloon device</h6></div><br class="figure-break" /><div class="para">
+ Here is an example where the device is added manually with static PCI slot 2 requested
+ </div><div class="figure" id="fig-dom-xml-memory-baloon-device2"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><memballoon</span><span class="perl_Others"> model=</span><span class="perl_String">'virtio'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'pci'</span><span class="perl_Others"> domain=</span><span class="perl_String">'0x0000'</span><span class="perl_Others"> bus=</span><span class="perl_String">'0x00'</span><span class="perl_Others"> slot=</span><span class="perl_String">'0x02'</span><span class="perl_Others"> function=</span><span class="perl_String">'0x0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></memballoon></span>
+ <span class="perl_Keyword"></devices></span>
+<span class="perl_Error"><</span>/domain>
+</pre></div><h6>Figure J.68. Memory balloon device added manually</h6></div><br class="figure-break" /><div class="para">
+ The required <code class="sgmltag-element">model</code> attribute specifies what type of balloon device is provided. Valid values are specific to the virtualization platform are: <code class="sgmltag-element">'virtio'</code> which is the default setting with the KVM hypervisor or <code class="sgmltag-element">'xen'</code> which is the default setting with the Xen hypervisor.
+ </div></div><div class="section" id="section-libvirt-dom-xml-random-number-gen"><div class="titlepage"><div><div><h2 class="title">J.20. Random number generator device</h2></div></div></div><div class="para">
+ The virtual random number generator device allows the host to pass through entropy to guest operating systems.
+ </div><div class="figure" id="fig--dom-xml-random-number-gen"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><rng</span><span class="perl_Others"> model=</span><span class="perl_String">'virtio'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><rate</span><span class="perl_Others"> period=</span><span class="perl_String">"2000"</span><span class="perl_Others"> bytes=</span><span class="perl_String">"1234"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><backend</span><span class="perl_Others"> model=</span><span class="perl_String">'random'</span><span class="perl_Keyword">></span>/dev/random<span class="perl_Keyword"></backend></span>
+ <span class="perl_Comment"><!-- OR --></span>
+ <span class="perl_Keyword"><backend</span><span class="perl_Others"> model=</span><span class="perl_String">'egd'</span><span class="perl_Others"> type=</span><span class="perl_String">'udp'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'bind'</span><span class="perl_Others"> service=</span><span class="perl_String">'1234'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'connect'</span><span class="perl_Others"> host=</span><span class="perl_String">'1.2.3.4'</span><span class="perl_Others"> service=</span><span class="perl_String">'1234'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"></backend></span>
+ <span class="perl_Keyword"></rng></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.69. Random number generator device</h6></div><br class="figure-break" /><div class="para">
+ The random number generator device allows the following attributes/elements:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">model</code> - The required <code class="sgmltag-attribute">model</code> attribute specifies what type of RNG device is provided. <code class="sgmltag-attvalue">'virtio'</code> — supported by qemu and virtio-rng kernel module
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><backend></code> - The <code class="sgmltag-starttag"><backend></code> element specifies the source of entropy to be used for the domain. The source model is configured using the <code class="sgmltag-attribute">model</code> attribute. Supported source models include <code class="sgmltag-attvalue">'random'</code> — <code class="filename">/dev/random</code> (default setting) or similar device as source and <code class="sgmltag-attvalue">'egd'</code> which sets a EGD protocol backend.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">backend type='random'</code> - This <code class="sgmltag-starttag"><backend></code> type expects a non-blocking character device as input. Examples of such devices are <code class="filename">/dev/random</code> and <code class="filename">/dev/urandom</code>. The file name is specified as contents of the <code class="sgmltag-starttag"><backend></code> element. When no file name is specified the hypervisor default is used.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><backend type='egd'></code> - This backend connects to a source using the EGD protocol. The source is specified as a character device. Refer to character device host interface for more information.
+ </div></li></ul></div></div><div class="section" id="section-libvirt-dom-xml-tpm-device"><div class="titlepage"><div><div><h2 class="title">J.21. TPM devices</h2></div></div></div><div class="para">
+ The TPM device enables a QEMU guest to have access to TPM functionality. The TPM passthrough device type provides access to the host's TPM for one QEMU guest. No other software may be is using the TPM device, typically <code class="filename">/dev/tpm0</code>, at the time the QEMU guest is started. The following domain XML example shows the usage of the TPM passthrough device
+ </div><div class="figure" id="fig-libvirt-dom-xml-tpm-device"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><tpm</span><span class="perl_Others"> model=</span><span class="perl_String">'tpm-tis'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><backend</span><span class="perl_Others"> type=</span><span class="perl_String">'passthrough'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><backend</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/tpm0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></backend></span>
+ <span class="perl_Keyword"></tpm></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+
+</pre></div><h6>Figure J.70. TPM devices</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-attribute">model</code> attribute specifies what device model QEMU provides to the guest. If no model name is provided, tpm-tis will automatically be chosen. The <code class="sgmltag-starttag"><backend></code> element specifies the type of TPM device. The following types are supported: <code class="sgmltag-attvalue">'passthrough'</code> — uses the host's TPM device and <code class="sgmltag-attvalue">'passthrough'</code>. This backend type requires exclusive access to a TPM device on the host. An example for such a device is <code class="filename">/dev/tpm0</code>. The filename is specified as path attribute of the source element. If no file name is specified then <code class="filename">/dev/tpm0</code> is automatically used.
+ </div></div><div class="section" id="section-libvirt-dom-xml-security-label"><div class="titlepage"><div><div><h2 class="title">J.22. Security label</h2></div></div></div><div class="para">
+ The <code class="sgmltag-starttag"><seclabel></code> element allows control over the operation of the security drivers. There are three basic modes of operation, <code class="sgmltag-attvalue">'dynamic'</code> where libvirt automatically generates a unique security label, <code class="sgmltag-attvalue">'static'</code> where the application/administrator chooses the labels, or <code class="sgmltag-element">'none'</code> where confinement is disabled. With dynamic label generation, libvirt will always automatically relabel any resources associated with the virtual machine. With static label assignment, by default, the administrator or application must ensure labels are set correctly on any resources, however, automatic relabeling can be enabled if desired.
+ </div><div class="para">
+ If more than one security driver is used by libvirt, multiple seclabel tags can be used, one for each driver and the security driver referenced by each tag can be defined using the attribute <code class="sgmltag-attribute">model</code> Valid input XML configurations for the top-level security label are:
+ </div><div class="figure" id="fig-libvirt-dom-xml-security-label"><div class="figure-contents"><pre class="programlisting">
+
+ <span class="perl_Keyword"><seclabel</span><span class="perl_Others"> type=</span><span class="perl_String">'dynamic'</span><span class="perl_Others"> model=</span><span class="perl_String">'selinux'</span><span class="perl_Keyword">/></span>
+
+ <span class="perl_Keyword"><seclabel</span><span class="perl_Others"> type=</span><span class="perl_String">'dynamic'</span><span class="perl_Others"> model=</span><span class="perl_String">'selinux'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><baselabel></span>system_u:system_r:my_svirt_t:s0<span class="perl_Keyword"></baselabel></span>
+ <span class="perl_Keyword"></seclabel></span>
+
+ <span class="perl_Keyword"><seclabel</span><span class="perl_Others"> type=</span><span class="perl_String">'static'</span><span class="perl_Others"> model=</span><span class="perl_String">'selinux'</span><span class="perl_Others"> relabel=</span><span class="perl_String">'no'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><label></span>system_u:system_r:svirt_t:s0:c392,c662<span class="perl_Keyword"></label></span>
+ <span class="perl_Keyword"></seclabel></span>
+
+ <span class="perl_Keyword"><seclabel</span><span class="perl_Others"> type=</span><span class="perl_String">'static'</span><span class="perl_Others"> model=</span><span class="perl_String">'selinux'</span><span class="perl_Others"> relabel=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><label></span>system_u:system_r:svirt_t:s0:c392,c662<span class="perl_Keyword"></label></span>
+ <span class="perl_Keyword"></seclabel></span>
+
+ <span class="perl_Keyword"><seclabel</span><span class="perl_Others"> type=</span><span class="perl_String">'none'</span><span class="perl_Keyword">/></span>
+</pre></div><h6>Figure J.71. Security label</h6></div><br class="figure-break" /><div class="para">
+ If no <code class="sgmltag-attribute">'type'</code> attribute is provided in the input XML, then the security driver default setting will be used, which may be either <code class="sgmltag-attvalue">'none'</code> or <code class="sgmltag-attvalue">'dynamic'</code>. If a <code class="sgmltag-starttag"><baselabel></code> is set but no <code class="sgmltag-attribute">'type'</code> is set, then the type is presumed to be <code class="sgmltag-attribute">'dynamic'</code>. When viewing the XML for a running guest with automatic resource relabeling active, an additional XML element, <code class="sgmltag-attribute">imagelabel</code>, will be included. This is an output-only element, so will be ignored in user supplied XML documents.
+ </div><div class="para">
+ The following elements can be manipulated with the following values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">type</code> - Either <code class="sgmltag-element">static</code>, <code class="sgmltag-element">dynamic</code> or <code class="sgmltag-element">none</code> to determine whether libvirt automatically generates a unique security label or not.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">model</code> - A valid security model name, matching the currently activated security model
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">relabel</code> - Either <code class="sgmltag-attvalue">yes</code> or <code class="sgmltag-attvalue">no</code>. This must always be <code class="sgmltag-attvalue">yes</code> if dynamic label assignment is used. With static label assignment it will default to <code class="sgmltag-attvalue">no</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><label></code> - If static labelling is used, this must specify the full security label to assign to the virtual domain. The format of the content depends on the security driver in use:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">SELinux</code>: a SELinux context.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">AppArmor</code>: an AppArmor profile.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">DAC</code>: owner and group separated by colon. They can be defined both as user/group names or uid/gid. The driver will first try to parse these values as names, but a leading plus sign can used to force the driver to parse them as uid or gid.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><baselabel></code> - If dynamic labelling is used, this can optionally be used to specify the base security label. The format of the content depends on the security driver in use.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><imagelabel></code> - This is an output only element, which shows the security label used on resources associated with the virtual domain. The format of the content depends on the security driver in use When relabeling is in effect, it is also possible to fine-tune the labeling done for specific source file names, by either disabling the labeling (useful if the file lives on NFS or other file system that lacks security labeling) or requesting an alternate label (useful when a management application creates a special label to allow sharing of some, but not all, resources between domains). When a seclabel element is attached to a specific path rather than the top-level domain assignment, only the attribute relabel or the sub-element label are supported.
+ </div></li></ul></div></div><div class="section" id="section-libvirt-dom-xml-example"><div class="titlepage"><div><div><h2 class="title">J.23. Example domain XML configuration</h2></div></div></div><div class="para">
+ QEMU emulated guest on x86_64
+ </div><div class="figure" id="fig-dom-xml-example-qemu"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain</span><span class="perl_Others"> type=</span><span class="perl_String">'qemu'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><name></span>QEmu-fedora-i686<span class="perl_Keyword"></name></span>
+ <span class="perl_Keyword"><uuid></span>c7a5fdbd-cdaf-9455-926a-d65c16db1809<span class="perl_Keyword"></uuid></span>
+ <span class="perl_Keyword"><memory></span>219200<span class="perl_Keyword"></memory></span>
+ <span class="perl_Keyword"><currentMemory></span>219200<span class="perl_Keyword"></currentMemory></span>
+ <span class="perl_Keyword"><vcpu></span>2<span class="perl_Keyword"></vcpu></span>
+ <span class="perl_Keyword"><os></span>
+ <span class="perl_Keyword"><type</span><span class="perl_Others"> arch=</span><span class="perl_String">'i686'</span><span class="perl_Others"> machine=</span><span class="perl_String">'pc'</span><span class="perl_Keyword">></span>hvm<span class="perl_Keyword"></type></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> dev=</span><span class="perl_String">'cdrom'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></os></span>
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><emulator></span>/usr/bin/qemu-system-x86_64<span class="perl_Keyword"></emulator></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'file'</span><span class="perl_Others"> device=</span><span class="perl_String">'cdrom'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> file=</span><span class="perl_String">'/home/user/boot.iso'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hdc'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><readonly/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'file'</span><span class="perl_Others"> device=</span><span class="perl_String">'disk'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> file=</span><span class="perl_String">'/home/user/fedora.img'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hda'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'vnc'</span><span class="perl_Others"> port=</span><span class="perl_String">'-1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.72. Example domain XML config</h6></div><br class="figure-break" /><div class="para">
+ KVM hardware accelerated guest on i686
+ </div><div class="figure" id="fig-dom-xml-example-kvm"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain</span><span class="perl_Others"> type=</span><span class="perl_String">'kvm'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><name></span>demo2<span class="perl_Keyword"></name></span>
+ <span class="perl_Keyword"><uuid></span>4dea24b3-1d52-d8f3-2516-782e98a23fa0<span class="perl_Keyword"></uuid></span>
+ <span class="perl_Keyword"><memory></span>131072<span class="perl_Keyword"></memory></span>
+ <span class="perl_Keyword"><vcpu></span>1<span class="perl_Keyword"></vcpu></span>
+ <span class="perl_Keyword"><os></span>
+ <span class="perl_Keyword"><type</span><span class="perl_Others"> arch=</span><span class="perl_String">"i686"</span><span class="perl_Keyword">></span>hvm<span class="perl_Keyword"></type></span>
+ <span class="perl_Keyword"></os></span>
+ <span class="perl_Keyword"><clock</span><span class="perl_Others"> sync=</span><span class="perl_String">"localtime"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><emulator></span>/usr/bin/qemu-kvm<span class="perl_Keyword"></emulator></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'file'</span><span class="perl_Others"> device=</span><span class="perl_String">'disk'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> file=</span><span class="perl_String">'/var/lib/libvirt/images/demo2.img'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hda'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">'24:42:53:21:52:45'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'vnc'</span><span class="perl_Others"> port=</span><span class="perl_String">'-1'</span><span class="perl_Others"> keymap=</span><span class="perl_String">'de'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.73. Example domain XML config</h6></div><br class="figure-break" /></div></div></div><div xml:lang="en-US" class="appendix" id="appe-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Revision_History" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Revision History</h1></div></div></div><div class="para">
+ <div class="revhistory"><table summary="Revision History"><tr><th align="left" valign="top" colspan="3"><strong>Revision History</strong></th></tr><tr><td align="left">Revision 0.2-0</td><td align="left">Tue May 28 2013</td><td align="left"><span class="author"><span class="firstname">Laura</span> <span class="surname">Novich</span></span></td></tr><tr><td align="left" colspan="3">
+ <table border="0" summary="Simple list" class="simplelist"><tr><td>Completed merger of guides and prepared for final publishing.</td></tr></table>
+
+ </td></tr><tr><td align="left">Revision 0.1-0</td><td align="left">Tue Jan 15 2013</td><td align="left"><span class="author"><span class="firstname">Laura</span> <span class="surname">Bailey</span></span></td></tr><tr><td align="left" colspan="3">
+ <table border="0" summary="Simple list" class="simplelist"><tr><td>Combined F18 Virtualization Administration Guide and Virtualization Host Configuration and Guest Installation Guide for use in Fedora 19.</td></tr></table>
+
+ </td></tr></table></div>
+
+ </div></div></div></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Bridge_Device.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Bridge_Device.html
new file mode 100644
index 0000000..7f3e9a3
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Bridge_Device.html
@@ -0,0 +1,46 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.11. Unable to add bridge br0 port vnet0: No such device</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_DHCP_Response_Checksums.html" title="B.10. Could not add rule to fixup DHCP response checksums on network 'default'" /><link rel="next" href="App_Generic_Ethernet.html" title="B.12. Guest is unable to start with error: warning: could not open /dev/net/tun" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><
ul class="docnav"><li class="previous"><a accesskey="p" href="App_DHCP_Response_Checksums.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_Generic_Ethernet.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_Bridge_Device" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.11. Unable to add bridge br0 port vnet0: No such device</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The following error message appears:
+ </div><pre class="screen">Unable to add bridge <em class="replaceable"><code>name_of_bridge</code></em> port vnet0: No such device</pre><div class="para">
+ For example, if the bridge name is <em class="replaceable"><code>br0</code></em>, the error message will appear as:
+ </div><pre class="screen">Unable to add bridge br0 port vnet0: No such device</pre><div class="para">
+ In <span class="application"><strong>libvirt</strong></span> versions 0.9.6 and earlier, the same error appears as:
+ </div><pre class="screen">Failed to add tap interface to bridge <em class="replaceable"><code>name_of_bridge</code></em>: No such device</pre><div class="para">
+ Or for example, if the bridge is named <em class="replaceable"><code>br0</code></em>:
+ </div><pre class="screen">Failed to add tap interface to bridge <em class="replaceable"><code>'br0'</code></em>: No such device</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ Both error messages reveal that the bridge device specified in the guest's (or domain's) <code class="code"><interface></code> definition does not exist.
+ </div><div class="para">
+ To verify the bridge device listed in the error message does not exist, use the shell command <code class="command">ifconfig <em class="replaceable"><code>br0</code></em></code>.
+ </div><div class="para">
+ A message similar to this confirms the host has no bridge by that name:
+ </div><pre class="screen"><em class="replaceable"><code>br0</code></em>: error fetching interface information: Device not found</pre><div class="para">
+ If this is the case, continue to the solution.
+ </div><div class="para">
+ However, if the resulting message is similar to the following, the issue exists elsewhere:
+ </div><pre class="screen"><em class="replaceable"><code>br0</code></em> Link encap:Ethernet HWaddr 00:00:5A:11:70:48
+ inet addr:10.22.1.5 Bcast:10.255.255.255 Mask:255.0.0.0
+ UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
+ RX packets:249841 errors:0 dropped:0 overruns:0 frame:0
+ TX packets:281948 errors:0 dropped:0 overruns:0 carrier:0
+ collisions:0 txqueuelen:0
+ RX bytes:106327234 (101.4 MiB) TX bytes:21182634 (20.2 MiB)</pre></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Edit the existing bridge or create a new bridge with <code class="command">virsh</code></span></dt><dd><div class="para">
+ Use <code class="command">virsh</code> to either edit the settings of an existing bridge or network, or to add the bridge device to the host system configuration.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Edit the existing bridge settings using <code class="command">virsh</code></span></dt><dd><div class="para">
+ Use <code class="command">virsh edit <em class="replaceable"><code>name_of_guest</code></em></code> to change the <code class="code"><interface></code> definition to use a bridge or network that already exists.
+ </div><div class="para">
+ For example, change <code class="code">type='bridge'</code> to <code class="code">type='network'</code>, and <code class="code"><source bridge='br0'/></code> to <code class="code"><source network='default'/></code>.
+ </div></dd><dt class="varlistentry"><span class="term">Create a host bridge using <code class="command">virsh</code></span></dt><dd><div class="para">
+ For <span class="application"><strong>libvirt</strong></span> version 0.9.8 and later, a bridge device can be created with the <code class="command">virsh iface-bridge</code> command. This will create a bridge device <em class="replaceable"><code>br0</code></em> with <code class="filename">eth0</code>, the physical network interface which is set as part of a bridge, attached:
+ </div><pre class="screen">virsh iface-bridge eth0 <em class="replaceable"><code>br0</code></em></pre><div class="para">
+ Optional: If desired, remove this bridge and restore the original <code class="filename">eth0</code> configuration with this command:
+ </div><pre class="screen">virsh iface-unbridge <em class="replaceable"><code>br0</code></em></pre></dd></dl></div></dd><dt class="varlistentry"><span class="term">Create a host bridge manually</span></dt><dd><div class="para">
+ For older versions of <span class="application"><strong>libvirt</strong></span>, it is possible to manually create a bridge device on the host. Refer to <a class="xref" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html">Section 11.3, “Bridged networking with libvirt”</a> for instructions.
+ </div></dd></dl></div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_DHCP_Response_Checksums.html"><strong>Prev</strong>B.10. Could not add rule to fixup DHCP response c...</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="App_Generic_Ethernet.html"><strong>Next</strong>B.12. Guest is unable to start with error: warnin...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_DHCP_Response_Checksums.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_DHCP_Response_Checksums.html
new file mode 100644
index 0000000..852ef24
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_DHCP_Response_Checksums.html
@@ -0,0 +1,18 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.10. Could not add rule to fixup DHCP response checksums on network 'default'</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_Macvtap.html" title="B.9. Guest can reach outside network, but cannot reach host when using macvtap interface" /><link rel="next" href="App_Bridge_Device.html" title="B.11. Unable to add bridge br0 port vnet0: No such device" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="pr
evious"><a accesskey="p" href="App_Macvtap.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_Bridge_Device.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_DHCP_Response_Checksums" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.10. Could not add rule to fixup DHCP response checksums on network <em class="replaceable"><code>'default'</code></em></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ This message appears:
+ </div><pre class="screen">Could not add rule to fixup DHCP response checksums on network <em class="replaceable"><code>'default'</code></em></pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ Although this message appears to be evidence of an error, it is almost always harmless.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Unless the problem you are experiencing is that the guest virtual machines are unable to acquire IP addresses through DHCP, this message can be ignored.
+ </div><div class="para">
+ If this is the case, refer to <a class="xref" href="App_PXE_Guest_Boot_Fail.html">Section B.8, “PXE boot (or DHCP) on guest failed”</a> for further details on this situation.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_Macvtap.html"><strong>Prev</strong>B.9. Guest can reach outside network, but cannot ...</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="App_Bridge_Device.html"><strong>Next</strong>B.11. Unable to add bridge br0 port vnet0: No suc...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Domain_Console.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Domain_Console.html
new file mode 100644
index 0000000..a5a9e85
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Domain_Console.html
@@ -0,0 +1,29 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.5. Internal error cannot find character device (null)</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_Domain_Monitor_Socket.html" title="B.4. Guest starting fails with error: monitor socket did not show up" /><link rel="next" href="App_Domain_Not_Booting.html" title="B.6. Guest virtual machine booting stalls with error: No boot device" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="App_Domain_Monitor_Socket.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_Domain_Not_Booting.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_Domain_Console" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.5. <code class="computeroutput">Internal error cannot find character device (null)</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ This error message appears when attempting to connect to a guest virtual machine's console:
+ </div><pre class="screen"># virsh console test2 Connected to domain test2 Escape character is ^] error: internal error cannot find character device (null)</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This error message shows that there is no serial console configured for the guest virtual machine.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Set up a serial console in the guest's XML file.
+ </div><div class="procedure"><h6>Procedure B.1. Setting up a serial console in the guest's XML</h6><ol class="1"><li class="step"><div class="para">
+ Add the following XML to the guest virtual machine's XML using <span class="application"><strong>virsh edit</strong></span>:
+ </div><pre class="programlisting"><serial type='pty'>
+ <target port='0'/>
+</serial>
+<console type='pty'>
+ <target type='serial' port='0'/>
+</console></pre></li><li class="step"><div class="para">
+ Set up the console in the guest kernel command line.
+ </div><div class="para">
+ To do this, either log in to the guest virtual machine to edit the <code class="filename">/boot/grub/grub.conf</code> file directly, or use the <span class="application"><strong>virt-edit</strong></span> command line tool. Add the following to the guest kernel command line:
+ </div><pre class="screen">console=ttyS0,115200</pre></li><li class="step"><div class="para">
+ Run the followings command:
+ </div><pre class="screen"># virsh start vm && virsh console vm</pre></li></ol></div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_Domain_Monitor_Socket.html"><strong>Prev</strong>B.4. Guest starting fails with error: monitor soc...</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="App_Domain_Not_Booting.html"><strong>Next</strong>B.6. Guest virtual machine booting stalls with er...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Domain_Monitor_Socket.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Domain_Monitor_Socket.html
new file mode 100644
index 0000000..f6b84e6
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Domain_Monitor_Socket.html
@@ -0,0 +1,33 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.4. Guest starting fails with error: monitor socket did not show up</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_Domain_Processor.html" title="B.3. The guest virtual machine cannot be started: internal error guest CPU is not compatible with host CPU" /><link rel="next" href="App_Domain_Console.html" title="B.5. Internal error cannot find character device (null)" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul cl
ass="docnav"><li class="previous"><a accesskey="p" href="App_Domain_Processor.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_Domain_Console.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_Domain_Monitor_Socket" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.4. Guest starting fails with error: <code class="computeroutput">monitor socket did not show up</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The guest virtual machine (or domain) starting fails with this error (or similar):
+ </div><pre class="screen"># virsh -c qemu:///system create <em class="replaceable"><code>name_of_guest</code></em>.xml error: Failed to create domain from <em class="replaceable"><code>name_of_guest</code></em>.xml error: monitor socket did not show up.: Connection refused</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This error message shows:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <span class="application"><strong>libvirt</strong></span> is working;
+ </div></li><li class="listitem"><div class="para">
+ The <span class="application"><strong>QEMU</strong></span> process failed to start up; and
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>libvirt</strong></span> quits when trying to connect <span class="application"><strong>QEMU</strong></span> or the QEMU agent monitor socket.
+ </div></li></ol></div><div class="para">
+ To understand the error details, examine the guest log:
+ </div><pre class="screen"># cat /var/log/libvirt/qemu/<em class="replaceable"><code>name_of_guest</code></em>.log
+LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-kvm -S -M pc -enable-kvm -m 768 -smp 1,sockets=1,cores=1,threads=1 -name <em class="replaceable"><code>name_of_guest</code></em> -uuid ebfaadbe-e908-ba92-fdb8-3fa2db557a42 -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/<em class="replaceable"><code>name_of_guest</code></em>.monitor,server,nowait -mon chardev=monitor,mode=readline -no-reboot -boot c -kernel /var/lib/libvirt/boot/vmlinuz -initrd /var/lib/libvirt/boot/initrd.img -append method=http://www.example.com/pub/product/release/version/x86_64/os/ -drive file=/var/lib/libvirt/images/<em class="replaceable"><code>name_of_guest</code></em>.img,if=none,id=drive-ide0-0-0,boot=on -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -device virtio-net-pci,vlan=0,id=net0,mac=52:40:00:f4:f1:0a,bus=pci.0,addr=0x4 -net tap,fd=42,vlan=0,name=hostnet0 -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -vnc 127
.0.0.1:0 -k en-gb -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,
+addr=0x3
+char device redirected to /dev/pts/1
+qemu: could not load kernel '/var/lib/libvirt/boot/vmlinuz':
+Permission denied</pre></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ The guest log contains the details needed to fix the error.
+ </div><div class="para">
+ If a host is shut down while the guest is still running a <span class="application"><strong>libvirt</strong></span> version prior to 0.9.5, the libvirt-guest's init script attempts to perform a managed save of the guest. If the managed save was incomplete (for example, due to loss of power before the managed save image was flushed to disk), the save image is corrupted and will not be loaded by <span class="application"><strong>QEMU</strong></span>. The older version of <span class="application"><strong>libvirt</strong></span> does not recognize the corruption, making the problem perpetual. In this case, the guest log will show an attempt to use <code class="command">-incoming</code> as one of its arguments, meaning that <span class="application"><strong>libvirt</strong></span> is trying to start <span class="application"><strong>QEMU</strong></span> by migrating in the saved state file.
+ </div><div class="para">
+ This problem can be fixed by running <code class="command">virsh managedsave-remove <em class="replaceable"><code>name_of_guest</code></em></code> to remove the corrupted managed save image. Newer versions of <span class="application"><strong>libvirt</strong></span> take steps to avoid the corruption in the first place, as well as adding <code class="command">virsh start --force-boot <em class="replaceable"><code>name_of_guest</code></em></code> to bypass any managed save image.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_Domain_Processor.html"><strong>Prev</strong>B.3. The guest virtual machine cannot be started:...</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="App_Domain_Console.html"><strong>Next</strong>B.5. Internal error cannot find character device ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Domain_Not_Booting.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Domain_Not_Booting.html
new file mode 100644
index 0000000..9061042
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Domain_Not_Booting.html
@@ -0,0 +1,86 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.6. Guest virtual machine booting stalls with error: No boot device</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_Domain_Console.html" title="B.5. Internal error cannot find character device (null)" /><link rel="next" href="App_Virt_Net_Not_Starting.html" title="B.7. Virtual network default has not been started" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" h
ref="App_Domain_Console.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_Virt_Net_Not_Starting.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_Domain_Not_Booting" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.6. Guest virtual machine booting stalls with error: <code class="computeroutput">No boot device</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ After building a guest virtual machine from an existing disk image, the guest booting stalls with the error message <code class="computeroutput">No boot device</code>. However, the guest virtual machine can start successfully using the <code class="command">QEMU</code> command directly.
+ </div></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ The disk's bus type is not specified in the command for importing the existing disk image:
+ </div><pre class="screen"># virt-install \
+--connect qemu:///system \
+--ram 2048 -n rhel_64 \
+--os-type=linux --os-variant=rhel5 \
+--disk path=/root/RHEL-Server-5.8-64-virtio.qcow2,device=disk,format=qcow2 \
+--vcpus=2 --graphics spice --noautoconsole --import
+</pre><div class="para">
+ However, the command line used to boot up the guest virtual machine using <span class="application"><strong>QEMU</strong></span> directly shows that it uses <code class="literal">virtio</code> for its bus type:
+ </div><pre class="screen"># ps -ef | grep qemu
+/usr/libexec/qemu-kvm -monitor stdio -drive file=/root/RHEL-Server-5.8-32-virtio.qcow2,index=0,<span class="bold bold"><strong>if=virtio</strong></span>,media=disk,cache=none,format=qcow2 -net nic,vlan=0,model=rtl8139,macaddr=00:30:91:aa:04:74 -net tap,vlan=0,script=/etc/qemu-ifup,downscript=no -m 2048 -smp 2,cores=1,threads=1,sockets=2 -cpu qemu64,+sse2 -soundhw ac97 -rtc-td-hack -M rhel5.6.0 -usbdevice tablet -vnc :10 -boot c -no-kvm-pit-reinjection</pre><div class="para">
+ Note the <em class="parameter"><code>bus=</code></em> in the guest's XML generated by <span class="application"><strong>libvirt</strong></span> for the imported guest:
+ </div><pre class="programlisting">
+<domain type='qemu'>
+ <name>rhel_64</name>
+ <uuid>6cd34d52-59e3-5a42-29e4-1d173759f3e7</uuid>
+ <memory>2097152</memory>
+ <currentMemory>2097152</currentMemory>
+ <vcpu>2</vcpu>
+ <os>
+ <type arch='x86_64' machine='rhel5.4.0'>hvm</type>
+ <boot dev='hd'/>
+ </os>
+ <features>
+ <acpi/>
+ <apic/>
+ <pae/>
+ </features>
+ <clock offset='utc'>
+ <timer name='pit' tickpolicy='delay'/>
+ </clock>
+ <on_poweroff>destroy</on_poweroff>
+ <on_reboot>restart</on_reboot>
+ <on_crash>restart</on_crash>
+ <devices>
+ <emulator>/usr/libexec/qemu-kvm</emulator>
+ <disk type='file' device='disk'>
+ <driver name='qemu' type='qcow2' cache='none'/>
+ <source file='/root/RHEL-Server-5.8-64-virtio.qcow2'/>
+ <emphasis role="bold"><target dev='hda' bus='ide'/></emphasis>
+ <address type='drive' controller='0' bus='0' unit='0'/>
+ </disk>
+ <controller type='ide' index='0'/>
+ <interface type='bridge'>
+ <mac address='54:52:00:08:3e:8c'/>
+ <source bridge='br0'/>
+ </interface>
+ <serial type='pty'>
+ <target port='0'/>
+ </serial>
+ <console type='pty'>
+ <target port='0'/>
+ </console>
+ <input type='mouse' bus='ps2'/>
+ <graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
+ <video>
+ <model type='cirrus' vram='9216' heads='1'/>
+ </video>
+ </devices>
+ </domain>
+</pre><div class="para">
+ The bus type for the disk is set as <em class="parameter"><code>ide</code></em>, which is the default value set by <span class="application"><strong>libvirt</strong></span>. This is the incorrect bus type, and has caused the unsuccessful boot for the imported guest.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="procedure"><h6>Procedure B.2. Correcting the disk bus type</h6><ol class="1"><li class="step"><div class="para">
+ Undefine the imported guest, then re-import it with <em class="parameter"><code>bus=virtio</code></em> and the following:
+ </div><pre class="screen"># virsh destroy rhel_64
+# virsh undefine rhel_64
+# virt-install \
+--connect qemu:///system \
+--ram 1024 -n rhel_64 -r 2048 \
+--os-type=linux --os-variant=rhel5 \
+--disk path=/root/RHEL-Server-5.8-64-virtio.qcow2,device=disk,<span class="bold bold"><strong>bus=virtio</strong></span>,format=qcow2 \
+--vcpus=2 --graphics spice --noautoconsole --import</pre></li><li class="step"><div class="para">
+ Edit the imported guest's XML using <code class="command">virsh edit</code> and correct the disk bus type.
+ </div></li></ol></div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_Domain_Console.html"><strong>Prev</strong>B.5. Internal error cannot find character device ...</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="App_Virt_Net_Not_Starting.html"><strong>Next</strong>B.7. Virtual network default has not been started</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Domain_Processor.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Domain_Processor.html
new file mode 100644
index 0000000..4af4da7
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Domain_Processor.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.3. The guest virtual machine cannot be started: internal error guest CPU is not compatible with host CPU</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="Sect_Other_Connectivity_Errors.html" title="B.2.3. Other connectivity errors" /><link rel="next" href="App_Domain_Monitor_Socket.html" title="B.4. Guest starting fails with error: monitor socket did not show up" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accessk
ey="p" href="Sect_Other_Connectivity_Errors.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_Domain_Monitor_Socket.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_Domain_Processor" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.3. The guest virtual machine cannot be started: <code class="computeroutput">internal error guest CPU is not compatible with host CPU</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ Running on an Intel Core i7 processor (which <span class="application"><strong>virt-manager</strong></span> refers to as <code class="literal">Nehalem</code>, or the older Core 2 Duo, referred to as <code class="literal">Penryn</code>), a KVM guest (or domain) is created using <span class="application"><strong>virt-manager</strong></span>. After installation, the guest's processor is changed to match the host's CPU. The guest is then unable to start and reports this error:
+ </div><pre class="screen">2012-02-06 17:49:15.985+0000: 20757: error : qemuBuildCpuArgStr:3565 : internal error guest CPU is not compatible with host CPU</pre><div class="para">
+ Additionally, clicking <code class="literal">Copy host CPU configuration</code> in <span class="application"><strong>virt-manager</strong></span> shows Pentium III instead of <code class="literal">Nehalem</code> or <code class="literal">Penryn</code>.
+ </div></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ The <code class="filename">/usr/share/libvirt/cpu_map.xml</code> file lists the flags that define each CPU model. The <code class="literal">Nehalem</code> and <code class="literal">Penryn</code> definitions contain this:
+ </div><pre class="programlisting"><feature name='nx'/></pre><div class="para">
+ As a result, the <code class="literal">NX</code> (or <code class="literal">No eXecute</code>) flag needs to be presented to identify the CPU as <code class="literal">Nehalem</code> or <code class="literal">Penryn</code>. However, in <code class="filename">/proc/cpuinfo</code>, this flag is missing.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Nearly all new BIOSes allow enabling or disabling of the <code class="literal">No eXecute</code> bit. However, if disabled, some CPUs do not report this flag and thus <span class="application"><strong>libvirt</strong></span> detects a different CPU. Enabling this functionality instructs <span class="application"><strong>libvirt</strong></span> to report the correct CPU. Refer to your hardware documentation for further instructions on this subject.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="Sect_Other_Connectivity_Errors.html"><strong>Prev</strong>B.2.3. Other connectivity 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="App_Domain_Monitor_Socket.html"><strong>Next</strong>B.4. Guest starting fails with error: monitor soc...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Generic_Ethernet.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Generic_Ethernet.html
new file mode 100644
index 0000000..50e7a24
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Generic_Ethernet.html
@@ -0,0 +1,45 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.12. Guest is unable to start with error: warning: could not open /dev/net/tun</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_Bridge_Device.html" title="B.11. Unable to add bridge br0 port vnet0: No such device" /><link rel="next" href="App_Migration_Address.html" title="B.13. Migration fails with Error: unable to resolve address" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesske
y="p" href="App_Bridge_Device.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_Migration_Address.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_Generic_Ethernet" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.12. Guest is unable to start with error: <code class="computeroutput">warning: could not open /dev/net/tun</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The guest virtual machine does not start after configuring a <code class="code">type='ethernet'</code> (also known as 'generic ethernet') interface in the host system. An error appears either in <code class="filename">libvirtd.log</code>, <code class="filename">/var/log/libvirt/qemu/<em class="replaceable"><code>name_of_guest</code></em>.log</code>, or in both, similar to the below message:
+ </div><pre class="screen">warning: could not open /dev/net/tun: no virtual network emulation qemu-kvm: -netdev tap,script=/etc/my-qemu-ifup,id=hostnet0: Device 'tap' could not be initialized</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ Use of the generic ethernet interface type (<code class="code"><interface type='ethernet'></code>) is discouraged, because using it requires lowering the level of host protection against potential security flaws in <span class="application"><strong>QEMU</strong></span> and its guests. However, it is sometimes necessary to use this type of interface to take advantage of some other facility that is not yet supported directly in <span class="application"><strong>libvirt</strong></span>. For example, <span class="application"><strong>openvswitch</strong></span> was not supported in <span class="application"><strong>libvirt</strong></span> until <span class="package">libvirt-0.9.11</span>, so in older versions of <span class="application"><strong>libvirt</strong></span>, <code class="code"><interface type='ethernet'></code> was the only way to connect a guest to an <span class="application"><strong>openvswitch</strong></span> bridge.
+ </div><div class="para">
+ However, if you configure a <code class="code"><interface type='ethernet'></code> interface without making any other changes to the host system, the guest virtual machine will not start successfully.
+ </div><div class="para">
+ The reason for this failure is that for this type of interface, a script called by <span class="application"><strong>QEMU</strong></span> needs to manipulate the tap device. However, with <code class="code">type='ethernet'</code> configured, in an attempt to lock down <span class="application"><strong>QEMU</strong></span>, <span class="application"><strong>libvirt</strong></span> and SELinux have put in place several checks to prevent this. (Normally, <span class="application"><strong>libvirt</strong></span> performs all of the tap device creation and manipulation, and passes an open file descriptor for the tap device to <span class="application"><strong>QEMU</strong></span>.)
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Reconfigure the host system to be compatible with the generic ethernet interface.
+ </div><div class="procedure"><h6>Procedure B.4. Reconfiguring the host system to use the generic ethernet interface</h6><ol class="1"><li class="step"><div class="para">
+ Set SELinux to permissive by configuring <code class="code">SELINUX=permissive</code> in <code class="filename">/etc/selinux/config</code>:
+ </div><pre class="screen"># This file controls the state of SELinux on the system.
+# SELINUX= can take one of these three values:
+# enforcing - SELinux security policy is enforced.
+# permissive - SELinux prints warnings instead of enforcing.
+# disabled - No SELinux policy is loaded.
+SELINUX=permissive
+# SELINUXTYPE= can take one of these two values:
+# targeted - Targeted processes are protected,
+# mls - Multi Level Security protection.
+SELINUXTYPE=targeted</pre></li><li class="step"><div class="para">
+ From a root shell, run the command <code class="command">setenforce permissive</code>.
+ </div></li><li class="step"><div class="para">
+ In <code class="filename">/etc/libvirt/qemu.conf</code> add or edit the following lines:
+ </div><pre class="screen">clear_emulator_capabilities = 0</pre><pre class="screen">user = "root"</pre><pre class="screen">group = "root"</pre><pre class="screen">cgroup_device_acl = [
+ "/dev/null", "/dev/full", "/dev/zero",
+ "/dev/random", "/dev/urandom",
+ "/dev/ptmx", "/dev/kvm", "/dev/kqemu",
+ "/dev/rtc", "/dev/hpet", "/dev/net/tun",</pre></li><li class="step"><div class="para">
+ Restart <code class="filename">libvirtd</code>.
+ </div></li></ol></div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Since each of these steps significantly decreases the host's security protections against <span class="application"><strong>QEMU</strong></span> guest domains, this configuration should only be used if there is no alternative to using <code class="code"><interface type='ethernet'></code>.
+ </div></div></div></dd></dl></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ For more information on SELinux, refer to the <em class="citetitle">Fedora Security Guide</em>.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_Bridge_Device.html"><strong>Prev</strong>B.11. Unable to add bridge br0 port vnet0: No suc...</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="App_Migration_Address.html"><strong>Next</strong>B.13. Migration fails with Error: unable to resol...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Hypervisor_Connection_Fail.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Hypervisor_Connection_Fail.html
new file mode 100644
index 0000000..7e1cb81
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Hypervisor_Connection_Fail.html
@@ -0,0 +1,26 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.2. The URI failed to connect to the hypervisor</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="next" href="Sect_Failed_to_connect_socket.html" title="B.2.2. Failed to connect socket ... : Permission denied" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="a
pb.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="Sect_Failed_to_connect_socket.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_Hypervisor_Connection_Fail" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.2. The URI failed to connect to the hypervisor</h2></div></div></div><div class="para">
+ Several different errors can occur when connecting to the server (for example, when running <code class="command">virsh</code>).
+ </div><div class="section" id="Sect_Cannot_read_CA_certificate"><div class="titlepage"><div><div><h3 class="title">B.2.1. Cannot read CA certificate</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ When running a command, the following error (or similar) appears:
+ </div><pre class="screen">$ virsh -c <em class="replaceable"><code>name_of_uri</code></em> list
+error: Cannot read CA certificate '/etc/pki/CA/cacert.pem': No such file or directory
+error: failed to connect to the hypervisor</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ The error message is misleading about the actual cause. This error can be caused by a variety of factors, such as an incorrectly specified URI, or a connection that is not configured.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Incorrectly specified URI</span></dt><dd><div class="para">
+ When specifying <em class="parameter"><code>qemu://system</code></em> or <em class="parameter"><code>qemu://session</code></em> as a connection URI, <code class="command">virsh</code> attempts to connect to hostnames <em class="parameter"><code>system</code></em> or <em class="parameter"><code>session</code></em> respectively. This is because <code class="command">virsh</code> recognizes the text after the second forward slash as the host.
+ </div><div class="para">
+ Use three forward slashes to connect to the local host. For example, specifying <em class="parameter"><code>qemu:///system</code></em> instructs <code class="command">virsh</code> connect to the <em class="parameter"><code>system</code></em> instance of <span class="application"><strong>libvirtd</strong></span> on the local host.
+ </div><div class="para">
+ When a hostname is specified, the <span class="application"><strong>QEMU</strong></span> transport defaults to <code class="systemitem">TLS</code>. This results in certificates.
+ </div></dd><dt class="varlistentry"><span class="term">Connection is not configured</span></dt><dd><div class="para">
+ The URI is correct (for example, <em class="parameter"><code>qemu[+tls]://server/system</code></em>) but the certificates are not set up properly on your machine. For information on configuring TLS, see <a href="http://wiki.libvirt.org/page/TLSSetup">Setting up <span class="application"><strong>libvirt</strong></span> for TLS</a> available from the <span class="application"><strong>libvirt</strong></span> website.
+ </div></dd></dl></div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apb.html"><strong>Prev</strong>Appendix B. Common libvirt errors and troubleshoo...</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_Failed_to_connect_socket.html"><strong>Next</strong>B.2.2. Failed to connect socket ... : Permission ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Macvtap.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Macvtap.html
new file mode 100644
index 0000000..c1fea20
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Macvtap.html
@@ -0,0 +1,44 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.9. Guest can reach outside network, but cannot reach host when using macvtap interface</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_PXE_Guest_Boot_Fail.html" title="B.8. PXE boot (or DHCP) on guest failed" /><link rel="next" href="App_DHCP_Response_Checksums.html" title="B.10. Could not add rule to fixup DHCP response checksums on network 'default'" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous
"><a accesskey="p" href="App_PXE_Guest_Boot_Fail.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_DHCP_Response_Checksums.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_Macvtap" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.9. Guest can reach outside network, but cannot reach host when using macvtap interface</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ A guest virtual machine can communicate with other guests, but cannot connect to the host machine after being configured to use a macvtap (also known as <em class="parameter"><code>type='direct'</code></em>) network interface.
+ </div></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ Even when not connecting to a Virtual Ethernet Port Aggregator (VEPA) or VN-Link capable switch, macvtap interfaces can be useful. Setting the mode of such an interface to <code class="option">bridge</code> allows the guest to be directly connected to the physical network in a very simple manner without the setup issues (or <span class="package">NetworkManager</span> incompatibility) that can accompany the use of a traditional host bridge device.
+ </div><div class="para">
+ However, when a guest virtual machine is configured to use a <em class="parameter"><code>type='direct'</code></em> network interface such as macvtap, despite having the ability to communicate with other guests and other external hosts on the network, the guest cannot communicate with its own host.
+ </div><div class="para">
+ This situation is actually not an error — it is the defined behavior of macvtap. Due to the way in which the host's physical Ethernet is attached to the macvtap bridge, traffic into that bridge from the guests that is forwarded to the physical interface cannot be bounced back up to the host's IP stack. Additionally, traffic from the host's IP stack that is sent to the physical interface cannot be bounced back up to the macvtap bridge for forwarding to the guests.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Use <span class="application"><strong>libvirt</strong></span> to create an isolated network, and create a second interface for each guest virtual machine that is connected to this network. The host and guests can then directly communicate over this isolated network, while also maintaining compatibility with <span class="package">NetworkManager</span>.
+ </div><div class="procedure"><h6>Procedure B.3. Creating an isolated network with <span class="application"><strong>libvirt</strong></span></h6><ol class="1"><li class="step"><div class="para">
+ Add and save the following XML in the <code class="filename">/tmp/isolated.xml</code> file. If the 192.168.254.0/24 network is already in use elsewhere on your network, you can choose a different network.
+ </div><pre class="programlisting"><network>
+ <name>isolated</name>
+ <ip address='192.168.254.1' netmask='255.255.255.0'>
+ <dhcp>
+ <range start='192.168.254.2' end='192.168.254.254' />
+ </dhcp>
+ </ip>
+</network></pre></li><li class="step"><div class="para">
+ Create the network with this command: <code class="command">virsh net-define /tmp/isolated.xml</code>
+ </div></li><li class="step"><div class="para">
+ Set the network to autostart with the <code class="command">virsh net-autostart isolated</code> command.
+ </div></li><li class="step"><div class="para">
+ Start the network with the <code class="command">virsh net-start isolated</code> command.
+ </div></li><li class="step"><div class="para">
+ Using <code class="command">virsh edit <em class="replaceable"><code>name_of_guest</code></em></code>, edit the configuration of each guest that uses macvtap for its network connection and add a new <em class="parameter"><code><interface></code></em> in the <em class="parameter"><code><devices></code></em> section similar to the following (note the <em class="parameter"><code><model type='virtio'/></code></em> line is optional to include):
+ </div><pre class="programlisting"><interface type='network'>
+ <source network='isolated'/>
+ <model type='virtio'/>
+</interface></pre></li><li class="step"><div class="para">
+ Shut down, then restart each of these guests.
+ </div></li></ol></div><div class="para">
+ The guests are now able to reach the host at the address 192.168.254.1, and the host will be able to reach the guests at the IP address they acquired from DHCP (alternatively, you can manually configure the IP addresses for the guests). Since this new network is isolated to only the host and guests, all other communication from the guests will use the macvtap interface.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_PXE_Guest_Boot_Fail.html"><strong>Prev</strong>B.8. PXE boot (or DHCP) on guest failed</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="App_DHCP_Response_Checksums.html"><strong>Next</strong>B.10. Could not add rule to fixup DHCP response c...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Migration_Address.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Migration_Address.html
new file mode 100644
index 0000000..7552473
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Migration_Address.html
@@ -0,0 +1,34 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.13. Migration fails with Error: unable to resolve address</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_Generic_Ethernet.html" title="B.12. Guest is unable to start with error: warning: could not open /dev/net/tun" /><link rel="next" href="App_Migration_Disk_Image.html" title="B.14. Migration fails with Unable to allow access for disk path: No such file or directory" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" />
</a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="App_Generic_Ethernet.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_Migration_Disk_Image.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_Migration_Address" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.13. Migration fails with <code class="computeroutput">Error: unable to resolve address</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ <span class="application"><strong>QEMU</strong></span> guest migration fails and this error message appears:
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://192.168.122.12/system
+ error: Unable to resolve address <em class="replaceable"><code>name_of_host</code></em> service '49155': Name or service not known</pre><div class="para">
+ For example, if the destination hostname is "newyork", the error message will appear as:
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://192.168.122.12/system
+error: Unable to resolve address <em class="replaceable"><code>'newyork'</code></em> service '49155': Name or service not known</pre><div class="para">
+ However, this error looks strange as we did not use "newyork" hostname anywhere.
+ </div></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ During migration, <span class="application"><strong>libvirtd</strong></span> running on the destination host creates a URI from an address and port where it expects to receive migration data and sends it back to <span class="application"><strong>libvirtd</strong></span> running on the source host.
+ </div><div class="para">
+ In this case, the destination host (<code class="literal">192.168.122.12</code>) has its name set to <em class="replaceable"><code>'newyork'</code></em>. For some reason, <span class="application"><strong>libvirtd</strong></span> running on that host is unable to resolve the name to an IP address that could be sent back and still be useful. For this reason, it returned the <em class="replaceable"><code>'newyork'</code></em> hostname hoping the source <span class="application"><strong>libvirtd</strong></span> would be more successful with resolving the name. This can happen if DNS is not properly configured or <code class="filename">/etc/hosts</code> has the hostname associated with local loopback address (<code class="filename">127.0.0.1</code>).
+ </div><div class="para">
+ Note that the address used for migration data cannot be automatically determined from the address used for connecting to destination <span class="application"><strong>libvirtd</strong></span> (for example, from <code class="filename">qemu+tcp://192.168.122.12/system</code>). This is because to communicate with the destination <span class="application"><strong>libvirtd</strong></span>, the source <span class="application"><strong>libvirtd</strong></span> may need to use network infrastructure different from that which <span class="application"><strong>virsh</strong></span> (possibly running on a separate machine) requires.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ The best solution is to configure DNS correctly so that all hosts involved in migration are able to resolve all host names.
+ </div><div class="para">
+ If DNS cannot be configured to do this, a list of every host used for migration can be added manually to the <code class="filename">/etc/hosts</code> file on each of the hosts. However, it is difficult to keep such lists consistent in a dynamic environment.
+ </div><div class="para">
+ If the host names cannot be made resolvable by any means, <code class="command">virsh migrate</code> supports specifying the migration host:
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://192.168.122.12/system tcp://192.168.122.12</pre><div class="para">
+ Destination <span class="application"><strong>libvirtd</strong></span> will take the <code class="literal">tcp://192.168.122.12</code> URI and append an automatically generated port number. If this is not desirable (because of firewall configuration, for example), the port number can be specified in this command:
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://192.168.122.12/system tcp://192.168.122.12:12345</pre><div class="para">
+ Another option is to use tunnelled migration. Tunnelled migration does not create a separate connection for migration data, but instead tunnels the data through the connection used for communication with destination <span class="application"><strong>libvirtd</strong></span> (for example, <code class="filename">qemu+tcp://192.168.122.12/system</code>):
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://192.168.122.12/system --p2p --tunnelled</pre></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_Generic_Ethernet.html"><strong>Prev</strong>B.12. Guest is unable to start with error: warnin...</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="App_Migration_Disk_Image.html"><strong>Next</strong>B.14. Migration fails with Unable to allow access...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Migration_Disk_Image.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Migration_Disk_Image.html
new file mode 100644
index 0000000..5eac7a8
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Migration_Disk_Image.html
@@ -0,0 +1,34 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.14. Migration fails with Unable to allow access for disk path: No such file or directory</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_Migration_Address.html" title="B.13. Migration fails with Error: unable to resolve address" /><link rel="next" href="App_No_Guest_Machines.html" title="B.15. No guest virtual machines are present when libvirtd is started" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previo
us"><a accesskey="p" href="App_Migration_Address.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_No_Guest_Machines.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_Migration_Disk_Image" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.14. Migration fails with <code class="computeroutput">Unable to allow access for disk path: No such file or directory</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ A guest virtual machine (or domain) cannot be migrated because <span class="application"><strong>libvirt</strong></span> cannot access the disk image(s):
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://<em class="replaceable"><code>name_of_host</code></em>/system
+error: Unable to allow access for disk path /var/lib/libvirt/images/qemu.img: No such file or directory</pre><div class="para">
+ For example, if the destination hostname is "newyork", the error message will appear as:
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://<em class="replaceable"><code>newyork</code></em>/system
+error: Unable to allow access for disk path /var/lib/libvirt/images/qemu.img: No such file or directory</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ By default, migration only transfers the in-memory state of a running guest (such as memory or CPU state). Although disk images are not transferred during migration, they need to remain accessible at the same path by both hosts.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Set up and mount shared storage at the same location on both hosts. The simplest way to do this is to use NFS:
+ </div><div class="procedure"><h6>Procedure B.5. Setting up shared storage</h6><ol class="1"><li class="step"><div class="para">
+ Set up an NFS server on a host serving as shared storage. The NFS server can be one of the hosts involved in the migration, as long as all hosts involved are accessing the shared storage through NFS.
+ </div><pre class="screen"># mkdir -p /exports/images
+# cat >>/etc/exports <<EOF
+/exports/images 192.168.122.0/24(rw,no_root_squash)
+EOF</pre></li><li class="step"><div class="para">
+ Mount the exported directory at a common location on all hosts running <span class="application"><strong>libvirt</strong></span>. For example, if the IP address of the NFS server is 192.168.122.1, mount the directory with the following commands:
+ </div><pre class="screen"># cat >>/etc/fstab <<EOF
+192.168.122.1:/exports/images /var/lib/libvirt/images nfs auto 0 0
+EOF
+# mount /var/lib/libvirt/images</pre></li></ol></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ It is not possible to export a local directory from one host using NFS and mount it at the same path on another host — the directory used for storing disk images must be mounted from shared storage on both hosts. If this is not configured correctly, the guest virtual machine may lose access to its disk images during migration, because the source host's <span class="application"><strong>libvirt</strong></span> daemon may change the owner, permissions, and SELinux labels on the disk images after it successfully migrates the guest to its destination.
+ </div><div class="para">
+ If <span class="application"><strong>libvirt</strong></span> detects that the disk images are mounted from a shared storage location, it will not make these changes.
+ </div></div></div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_Migration_Address.html"><strong>Prev</strong>B.13. Migration fails with Error: unable to resol...</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="App_No_Guest_Machines.html"><strong>Next</strong>B.15. No guest virtual machines are present when ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_No_Guest_Machines.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_No_Guest_Machines.html
new file mode 100644
index 0000000..4115713
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_No_Guest_Machines.html
@@ -0,0 +1,44 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.15. No guest virtual machines are present when libvirtd is started</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_Migration_Disk_Image.html" title="B.14. Migration fails with Unable to allow access for disk path: No such file or directory" /><link rel="next" href="App_TCP_Ports.html" title="B.16. Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.pn
g" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="App_Migration_Disk_Image.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_TCP_Ports.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_No_Guest_Machines" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.15. No guest virtual machines are present when <span class="application"><strong>libvirtd</strong></span> is started</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The <span class="application"><strong>libvirt</strong></span> daemon is successfully started, but no guest virtual machines appear to be present.
+ </div><pre class="screen"># virsh list --all
+ Id Name State
+----------------------------------------------------
+#
+</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ There are various possible causes of this problem. Performing these tests will help to determine the cause of this situation:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Verify KVM kernel modules</span></dt><dd><div class="para">
+ Verify that KVM kernel modules are inserted in the kernel:
+ </div><pre class="screen"># lsmod | grep kvm
+kvm_intel 121346 0
+kvm 328927 1 kvm_intel</pre><div class="para">
+ If you are using an AMD machine, verify the <code class="systemitem">kvm_amd</code> kernel modules are inserted in the kernel instead, using the similar command <code class="command">lsmod | grep kvm_amd</code> in the root shell.
+ </div><div class="para">
+ If the modules are not present, insert them using the <code class="command">modprobe <em class="replaceable"><code><modulename></code></em></code> command.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Although it is uncommon, KVM virtualization support may be compiled into the kernel. In this case, modules are not needed.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">Verify virtualization extensions</span></dt><dd><div class="para">
+ Verify that virtualization extensions are supported and enabled on the host:
+ </div><pre class="screen"># egrep "(vmx|svm)" /proc/cpuinfo
+flags : fpu vme de pse tsc ... svm ... skinit wdt npt lbrv svm_lock nrip_save
+flags : fpu vme de pse tsc ... svm ... skinit wdt npt lbrv svm_lock nrip_save</pre><div class="para">
+ Enable virtualization extensions in your hardware's firmware configuration within the BIOS setup. Refer to your hardware documentation for further details on this.
+ </div></dd><dt class="varlistentry"><span class="term">Verify client URI configuration</span></dt><dd><div class="para">
+ Verify that the URI of the client is configured as desired:
+ </div><pre class="screen"># virsh uri
+vbox:///system</pre><div class="para">
+ For example, this message shows the URI is connected to the <span class="application"><strong>VirtualBox</strong></span> hypervisor, not <span class="application"><strong>QEMU</strong></span>, and reveals a configuration error for a URI that is otherwise set to connect to a <span class="application"><strong>QEMU</strong></span> hypervisor. If the URI was correctly connecting to <span class="application"><strong>QEMU</strong></span>, the same message would appear instead as:
+ </div><pre class="screen"># virsh uri
+qemu:///system</pre><div class="para">
+ This situation occurs when there are other hypervisors present, which <span class="application"><strong>libvirt</strong></span> may speak to by default.
+ </div></dd></dl></div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ After performing these tests, use the following command to view a list of guest virtual machines:
+ </div><pre class="screen"># virsh list --all</pre></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_Migration_Disk_Image.html"><strong>Prev</strong>B.14. Migration fails with Unable to allow 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="App_TCP_Ports.html"><strong>Next</strong>B.16. Unable to connect to server at 'host:16509'...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_PXE_Guest_Boot_Fail.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_PXE_Guest_Boot_Fail.html
new file mode 100644
index 0000000..48076f7
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_PXE_Guest_Boot_Fail.html
@@ -0,0 +1,71 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.8. PXE boot (or DHCP) on guest failed</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_Virt_Net_Not_Starting.html" title="B.7. Virtual network default has not been started" /><link rel="next" href="App_Macvtap.html" title="B.9. Guest can reach outside network, but cannot reach host when using macvtap interface" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="pr
evious"><a accesskey="p" href="App_Virt_Net_Not_Starting.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_Macvtap.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_PXE_Guest_Boot_Fail" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.8. PXE boot (or DHCP) on guest failed</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ A guest virtual machine starts successfully, but is then either unable to acquire an IP address from DHCP or boot using the PXE protocol, or both. There are two common causes of this error: having a long forward delay time set for the bridge, and when the <span class="package">iptables</span> package and kernel do not support checksum mangling rules.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Long forward delay time on bridge</span></dt><dd><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This is the most common cause of this error. If the guest network interface is connecting to a bridge device that has STP (Spanning Tree Protocol) enabled, as well as a long forward delay set, the bridge will not forward network packets from the guest virtual machine onto the bridge until at least that number of forward delay seconds have elapsed since the guest connected to the bridge. This delay allows the bridge time to watch traffic from the interface and determine the MAC addresses behind it, and prevent forwarding loops in the network topology.
+ </div><div class="para">
+ If the forward delay is longer than the timeout of the guest's PXE or DHCP client, then the client's operation will fail, and the guest will either fail to boot (in the case of PXE) or fail to acquire an IP address (in the case of DHCP).
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ If this is the case, change the forward delay on the bridge to 0, disable STP on the bridge, or both.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ This solution applies only if the bridge is not used to connect multiple networks, but just to connect multiple endpoints to a single network (the most common use case for bridges used by <span class="application"><strong>libvirt</strong></span>).
+ </div></div></div><div class="para">
+ If the guest has interfaces connecting to a <span class="application"><strong>libvirt</strong></span>-managed virtual network, edit the definition for the network, and restart it. For example, edit the default network with the following command:
+ </div><pre class="screen"># virsh net-edit default</pre><div class="para">
+ Add the following attributes to the <code class="code"><bridge></code> element:
+ </div><pre class="programlisting"><<em class="replaceable"><code>name_of_bridge</code></em>='virbr0' <code class="code">delay='0' stp='on'</code>/></pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ <code class="code">delay='0'</code> and <code class="code">stp='on'</code> are the default settings for virtual networks, so this step is only necessary if the configuration has been modified from the default.
+ </div></div></div><div class="para">
+ If the guest interface is connected to a host bridge that was configured outside of <span class="application"><strong>libvirt</strong></span>, change the delay setting.
+ </div><div class="para">
+ Add or edit the following lines in the <code class="filename">/etc/sysconfig/network-scripts/ifcfg-<em class="replaceable"><code>name_of_bridge</code></em></code> file to turn STP on with a 0 second delay:
+ </div><pre class="programlisting">STP=on
+DELAY=0</pre><div class="para">
+ After changing the configuration file, restart the bridge device:
+ </div><pre class="programlisting">/sbin/ifdown <em class="replaceable"><code>name_of_bridge</code></em>
+/sbin/ifup <em class="replaceable"><code>name_of_bridge</code></em></pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If <em class="replaceable"><code>name_of_bridge</code></em> is not the root bridge in the network, that bridge's delay will eventually reset to the delay time configured for the root bridge. In this case, the only solution is to disable STP completely on <em class="replaceable"><code>name_of_bridge</code></em>.
+ </div></div></div></dd></dl></div></dd></dl></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">The <span class="package">iptables</span> package and kernel do not support checksum mangling rules</span></dt><dd><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This message is only a problem if all four of the following conditions are true:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The guest is using <span class="application"><strong>virtio</strong></span> network devices.
+ </div><div class="para">
+ If so, the configuration file will contain <code class="code">model type='virtio'</code>
+ </div></li><li class="listitem"><div class="para">
+ The host has the <code class="literal">vhost-net</code> module loaded.
+ </div><div class="para">
+ This is true if <code class="computeroutput"><code class="command">ls</code> <code class="filename">/dev/vhost-net</code></code> does not return an empty result.
+ </div></li><li class="listitem"><div class="para">
+ The guest is attempting to get an IP address from a DHCP server that is running directly on the host.
+ </div></li><li class="listitem"><div class="para">
+ The <span class="package">iptables</span> version on the host is older than 1.4.10.
+ </div><div class="para">
+ <span class="package">iptables</span> 1.4.10 was the first version to add the <code class="literal">libxt_CHECKSUM</code> extension. This is the case if the following message appears in the <span class="application"><strong>libvirtd</strong></span> logs:
+ </div><pre class="screen">warning: Could not add rule to fixup DHCP response checksums on network <em class="replaceable"><code>default</code></em>
+warning: May need to update iptables package and kernel to support CHECKSUM rule.</pre><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Unless all of the other three conditions in this list are also true, the above warning message can be disregarded, and is not an indicator of any other problems.
+ </div></div></div></li></ul></div><div class="para">
+ When these conditions occur, UDP packets sent from the host to the guest have uncomputed checksums. This makes the host's UDP packets seem invalid to the guest's network stack.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ To solve this problem, invalidate any of the four points above. The best solution is to update the host <span class="package">iptables</span> and kernel to <span class="package">iptables-1.4.10</span> or newer where possible. Otherwise, the most specific fix is to disable the <code class="literal">vhost-net</code> driver for this particular guest. To do this, edit the guest configuration with this command:
+ </div><pre class="screen">virsh edit <em class="replaceable"><code>name_of_guest</code></em></pre><div class="para">
+ Change or add a <code class="code"><driver></code> line to the <code class="code"><interface></code> section:
+ </div><pre class="programlisting"><interface type='network'>
+ <model type='virtio'/>
+ <driver name='qemu'/>
+ ...
+</interface></pre><div class="para">
+ Save the changes, shut down the guest, and then restart it.
+ </div><div class="para">
+ If this problem is still not resolved, the issue may be due to a conflict between <span class="application"><strong>firewalld</strong></span> and the default <span class="application"><strong>libvirt</strong></span> network.
+ </div><div class="para">
+ To fix this, stop <span class="application"><strong>firewalld</strong></span> with the <code class="command">service firewalld stop</code> command, then restart <span class="application"><strong>libvirt</strong></span> with the <code class="command">service libvirtd restart</code> command.
+ </div></dd></dl></div></dd></dl></div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_Virt_Net_Not_Starting.html"><strong>Prev</strong>B.7. Virtual network default has not been started</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="App_Macvtap.html"><strong>Next</strong>B.9. Guest can reach outside network, but cannot ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_TCP_Ports.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_TCP_Ports.html
new file mode 100644
index 0000000..b91e9c4
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_TCP_Ports.html
@@ -0,0 +1,33 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.16. Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_No_Guest_Machines.html" title="B.15. No guest virtual machines are present when libvirtd is started" /><link rel="next" href="App_XML_Errors.html" title="B.17. Common XML errors" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="App_No_Guest_Mac
hines.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_XML_Errors.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_TCP_Ports" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.16. Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ While <span class="application"><strong>libvirtd</strong></span> should listen on TCP ports for connections, the connections fail:
+ </div><pre class="screen"># virsh -c qemu+tcp://host/system
+error: unable to connect to server at 'host:16509': Connection refused
+error: failed to connect to the hypervisor</pre><div class="para">
+ The <span class="application"><strong>libvirt</strong></span> daemon is not listening on TCP ports even after changing configuration in <code class="filename">/etc/libvirt/libvirtd.conf</code>:
+ </div><pre class="screen"># grep listen_ /etc/libvirt/libvirtd.conf
+listen_tls = 1
+listen_tcp = 1
+listen_addr = "0.0.0.0"</pre><div class="para">
+ However, the TCP ports for <span class="application"><strong>libvirt</strong></span> are still not open after changing configuration:
+ </div><pre class="screen"># netstat -lntp | grep libvirtd
+#</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ The <span class="application"><strong>libvirt</strong></span> daemon was started without the <code class="option">--listen</code> option. Verify this by running this command:
+ </div><pre class="screen"># ps aux | grep libvirtd
+root 27314 0.0 0.0 1000920 18304 ? Sl Feb16 1:19 libvirtd --daemon</pre><div class="para">
+ The output does not contain the <code class="option">--listen</code> option.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Start the daemon with the <code class="option">--listen</code> option.
+ </div><div class="para">
+ To do this, modify the <code class="filename">/etc/sysconfig/libvirtd</code> file and uncomment the following line:
+ </div><pre class="screen">#LIBVIRTD_ARGS="--listen"</pre><div class="para">
+ Then restart the <span class="application"><strong>libvirtd</strong></span> service with this command:
+ </div><pre class="screen"># /etc/init.d/libvirtd restart</pre></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_No_Guest_Machines.html"><strong>Prev</strong>B.15. No guest virtual machines are present 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="App_XML_Errors.html"><strong>Next</strong>B.17. Common XML errors</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Virt_Net_Not_Starting.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Virt_Net_Not_Starting.html
new file mode 100644
index 0000000..b8524cf
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_Virt_Net_Not_Starting.html
@@ -0,0 +1,40 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.7. Virtual network default has not been started</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_Domain_Not_Booting.html" title="B.6. Guest virtual machine booting stalls with error: No boot device" /><link rel="next" href="App_PXE_Guest_Boot_Fail.html" title="B.8. PXE boot (or DHCP) on guest failed" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey=
"p" href="App_Domain_Not_Booting.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_PXE_Guest_Boot_Fail.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_Virt_Net_Not_Starting" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.7. Virtual network <em class="replaceable"><code>default</code></em> has not been started</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ Normally, the configuration for a virtual network named <em class="replaceable"><code>default</code></em> is installed as part of the <span class="package">libvirt</span> package, and is configured to autostart when <span class="application"><strong>libvirtd</strong></span> is started.
+ </div><div class="para">
+ If the <em class="replaceable"><code>default</code></em> network (or any other locally-created network) is unable to start, any virtual machine configured to use that network for its connectivity will also fail to start, resulting in this error message:
+ </div><pre class="screen">Virtual network <em class="replaceable"><code>default</code></em> has not been started</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ One of the most common reasons for a <span class="application"><strong>libvirt</strong></span> virtual network's failure to start is that the dnsmasq instance required to serve DHCP and DNS requests from clients on that network has failed to start.
+ </div><div class="para">
+ To determine if this is the cause, run <code class="command">virsh net-start default</code> from a root shell to start the <em class="replaceable"><code>default</code></em> virtual network.
+ </div><div class="para">
+ If this action does not successfully start the virtual network, open <code class="filename">/var/log/libvirt/libvirtd.log</code> to view the complete error log message.
+ </div><div class="para">
+ If a message similar to the following appears, the problem is likely a systemwide dnsmasq instance that is already listening on <span class="application"><strong>libvirt</strong></span>'s bridge, and is preventing <span class="application"><strong>libvirt</strong></span>'s own dnsmasq instance from doing so. The most important parts to note in the error message are <code class="literal">dnsmasq</code> and <code class="literal">exit status 2</code>:
+ </div><pre class="screen">Could not start virtual network <em class="replaceable"><code>default</code></em>: internal error
+Child process (/usr/sbin/dnsmasq --strict-order --bind-interfaces
+--pid-file=/var/run/libvirt/network/<em class="replaceable"><code>default</code></em>.pid --conf-file=
+--except-interface lo --listen-address 192.168.122.1
+--dhcp-range 192.168.122.2,192.168.122.254
+--dhcp-leasefile=/var/lib/libvirt/dnsmasq/<em class="replaceable"><code>default</code></em>.leases
+--dhcp-lease-max=253 --dhcp-no-override) status unexpected: exit status 2</pre></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ If the machine is not using dnsmasq to serve DHCP for the physical network, disable dnsmasq completely.
+ </div><div class="para">
+ If it is necessary to run dnsmasq to serve DHCP for the physical network, edit the <code class="filename">/etc/dnsmasq.conf</code> file. Add or uncomment the first line, as well as one of the two lines following that line. Do not add or uncomment all three lines:
+ </div><pre class="programlisting">bind-interfaces
+interface=<em class="replaceable"><code>name_of_physical_interface</code></em>
+listen-address=<em class="replaceable"><code>chosen_IP_address</code></em></pre><div class="para">
+ After making this change and saving the file, restart the systemwide dnsmasq service.
+ </div><div class="para">
+ Next, start the <em class="replaceable"><code>default</code></em> network with the <code class="command">virsh net-start default</code> command.
+ </div><div class="para">
+ Start the virtual machines.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_Domain_Not_Booting.html"><strong>Prev</strong>B.6. Guest virtual machine booting stalls with er...</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="App_PXE_Guest_Boot_Fail.html"><strong>Next</strong>B.8. PXE boot (or DHCP) on guest failed</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_XML_Errors.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_XML_Errors.html
new file mode 100644
index 0000000..2755c30
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/App_XML_Errors.html
@@ -0,0 +1,28 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.17. Common XML errors</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_TCP_Ports.html" title="B.16. Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor" /><link rel="next" href="apbs17s02.html" title="B.17.2. XML syntax errors" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a
accesskey="p" href="App_TCP_Ports.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apbs17s02.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_XML_Errors" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.17. Common XML errors</h2></div></div></div><div class="para">
+ The <span class="application"><strong>libvirt</strong></span> tool uses XML documents to store structured data. A variety of common errors occur with XML documents when they are passed to <span class="application"><strong>libvirt</strong></span> through the API. Several common XML errors — including misformatted XML, inappropriate values, and missing elements — are detailed below.
+ </div><div class="section" id="idp28425648"><div class="titlepage"><div><div><h3 class="title" id="idp28425648">B.17.1. Editing domain definition</h3></div></div></div><div class="para">
+ Although it is not recommended, it is sometimes necessary to edit a guest virtual machine's (or a domain's) XML file manually. To access the guest's XML for editing, use the following command:
+ </div><pre class="screen"># virsh edit <em class="replaceable"><code>name_of_guest.xml</code></em></pre><div class="para">
+ This command opens the file in a text editor with the current definition of the guest virtual machine. After finishing the edits and saving the changes, the XML is reloaded and parsed by <span class="application"><strong>libvirt</strong></span>. If the XML is correct, the following message is displayed:
+ </div><pre class="screen"># virsh edit <em class="replaceable"><code>name_of_guest.xml</code></em>
+
+Domain <em class="replaceable"><code>name_of_guest.xml</code></em> XML configuration edited.</pre><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ When using the <code class="command">edit</code> command in <span class="application"><strong>virsh</strong></span> to edit an XML document, save all changes before exiting the editor.
+ </div></div></div><div class="para">
+ After saving the XML file, use the <code class="command">xmllint</code> command to validate that the XML is well-formed, or the <code class="command">virt-xml-validate</code> command to check for usage problems:
+ </div><pre class="screen"># xmllint --noout config.xml</pre><pre class="screen"># virt-xml-validate config.xml</pre><div class="para">
+ If no errors are returned, the XML description is well-formed and matches the <span class="application"><strong>libvirt</strong></span> schema. While the schema does not catch all constraints, fixing any reported errors will further troubleshooting.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">XML documents stored by <span class="application"><strong>libvirt</strong></span></span></dt><dd><div class="para">
+ These documents contain definitions of states and configurations for the guests. These documents are automatically generated and should not be edited manually. Errors in these documents contain the file name of the broken document. The file name is valid only on the host machine defined by the URI, which may refer to the machine the command was run on.
+ </div><div class="para">
+ Errors in files created by <span class="application"><strong>libvirt</strong></span> are rare. However, one possible source of these errors is a downgrade of <span class="application"><strong>libvirt</strong></span> — while newer versions of <span class="application"><strong>libvirt</strong></span> can always read XML generated by older versions, older versions of <span class="application"><strong>libvirt</strong></span> may be confused by XML elements added in a newer version.
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_TCP_Ports.html"><strong>Prev</strong>B.16. Unable to connect to server at 'host:16509'...</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="apbs17s02.html"><strong>Next</strong>B.17.2. XML syntax errors</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/common.css b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/common.css
new file mode 100644
index 0000000..d7dc3f2
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/common.css
@@ -0,0 +1,1528 @@
+* {
+ widows: 2 !important;
+ orphans: 2 !important;
+}
+
+body, h1, h2, h3, h4, h5, h6, pre, li, div {
+ line-height: 1.29em;
+}
+
+body {
+ background-color: white;
+ margin:0 auto;
+ font-family: "liberation sans", "Myriad ", "Bitstream Vera Sans", "Lucida Grande", "Luxi Sans", "Trebuchet MS", helvetica, verdana, arial, sans-serif;
+ font-size:12px;
+ max-width:55em;
+ color:black;
+}
+
+body.toc_embeded {
+ /*for web hosting system only*/
+ margin-left: 300px;
+}
+
+object.toc, iframe.toc {
+ /*for web hosting system only*/
+ border-style:none;
+ position:fixed;
+ width:290px;
+ height:99.99%;
+ top:0;
+ left:0;
+ z-index: 100;
+ border-style:none;
+ border-right:1px solid #999;
+}
+
+/* Hide web menu */
+
+body.notoc {
+ margin-left: 3em;
+}
+
+iframe.notoc {
+ border-style:none;
+ border: none;
+ padding: 0em;
+ position:fixed;
+ width: 21px;
+ height: 29px;
+ top: 0px;
+ left:0;
+ overflow: hidden;
+ margin: 0em;
+ margin-left: -3px;
+}
+/* End hide web menu */
+
+/* desktop styles */
+body.desktop {
+ margin-left: 26em;
+}
+
+body.desktop .book > .toc {
+ display:block;
+ width:24em;
+ height:99%;
+ position:fixed;
+ overflow:auto;
+ top:0px;
+ left:0px;
+ padding-left:1em;
+ background-color:#EEEEEE;
+}
+
+.toc {
+ line-height:1.35em;
+}
+
+.toc .glossary,
+.toc .chapter, .toc .appendix {
+ margin-top:1em;
+}
+
+.toc .part {
+ margin-top:1em;
+ display:block;
+}
+
+span.glossary,
+span.appendix {
+ display:block;
+ margin-top:0.5em;
+}
+
+div {
+ padding-top:0px;
+}
+
+div.section {
+ padding-top:1em;
+}
+
+p, div.para, div.formalpara {
+ padding-top:0px;
+ margin-top:0.3em;
+ padding-bottom:0px;
+ margin-bottom:1em;
+}
+
+/*Links*/
+a {
+ outline: none;
+}
+
+a:link {
+ text-decoration:none;
+ border-bottom: 1px dotted ;
+ color:#3366cc;
+}
+
+a:visited {
+ text-decoration:none;
+ border-bottom: 1px dotted ;
+ color:#003366;
+}
+
+div.longdesc-link {
+ float:right;
+ color:#999;
+}
+
+.toc a, .qandaset a {
+ font-weight:normal;
+ border:none;
+}
+
+.toc a:hover, .qandaset a:hover
+{
+ border-bottom: 1px dotted;
+}
+
+/*headings*/
+h1, h2, h3, h4, h5, h6 {
+ color: #336699;
+ margin-top: 0em;
+ margin-bottom: 0em;
+ background-color: transparent;
+ page-break-inside: avoid;
+ page-break-after: avoid;
+}
+
+h1 {
+ font-size:2.0em;
+}
+
+.titlepage h1.title {
+ font-size: 3.0em;
+ padding-top: 1em;
+ text-align:left;
+}
+
+.book > .titlepage h1.title {
+ text-align:center;
+}
+
+.article > .titlepage h1.title {
+ text-align:center;
+}
+
+.set .titlepage > div > div > h1.title {
+ text-align:center;
+}
+
+.producttitle {
+ margin-top: 0em;
+ margin-bottom: 0em;
+ font-size: 3.0em;
+ font-weight: bold;
+ background: #003d6e url(../images/h1-bg.png) top left repeat-x;
+ color: white;
+ text-align: center;
+ padding: 0.7em;
+}
+
+.titlepage .corpauthor {
+ margin-top: 1em;
+ text-align: center;
+}
+
+.section h1.title {
+ font-size: 1.6em;
+ padding: 0em;
+ color: #336699;
+ text-align: left;
+ background: white;
+}
+
+h2 {
+ font-size:1.6em;
+}
+
+
+h2.subtitle, h3.subtitle {
+ margin-top: 1em;
+ margin-bottom: 1em;
+ font-size: 1.4em;
+ text-align: center;
+}
+
+.preface > div > div > div > h2.title {
+ margin-top: 1em;
+ font-size: 2.0em;
+}
+
+.appendix h2 {
+ margin-top: 1em;
+ font-size: 2.0em;
+}
+
+
+
+h3 {
+ font-size:1.3em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+h4 {
+ font-size:1.1em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+
+h5 {
+ font-size:1em;
+}
+
+h6 {
+ font-size:1em;
+}
+
+h5.formalpara {
+ font-size:1em;
+ margin-top:2em;
+ margin-bottom:.8em;
+}
+
+.abstract h6 {
+ margin-top:1em;
+ margin-bottom:.5em;
+ font-size:2em;
+}
+
+/*element rules*/
+hr {
+ border-collapse: collapse;
+ border-style:none;
+ border-top: 1px dotted #ccc;
+ width:100%;
+ margin-top: 3em;
+}
+
+/* web site rules */
+ul.languages, .languages li {
+ display:inline;
+ padding:0em;
+}
+
+.languages li a {
+ padding:0em .5em;
+ text-decoration: none;
+}
+
+.languages li p, .languages li div.para {
+ display:inline;
+}
+
+.languages li a:link, .languages li a:visited {
+ color:#444;
+}
+
+.languages li a:hover, .languages li a:focus, .languages li a:active {
+ color:black;
+}
+
+ul.languages {
+ display:block;
+ background-color:#eee;
+ padding:.5em;
+}
+
+/*supporting stylesheets*/
+
+/*unique to the webpage only*/
+.books {
+ position:relative;
+}
+
+.versions li {
+ width:100%;
+ clear:both;
+ display:block;
+}
+
+a.version {
+ font-size:2em;
+ text-decoration:none;
+ width:100%;
+ display:block;
+ padding:1em 0em .2em 0em;
+ clear:both;
+}
+
+a.version:before {
+ content:"Version";
+ font-size:smaller;
+}
+
+a.version:visited, a.version:link {
+ color:#666;
+}
+
+a.version:focus, a.version:hover {
+ color:black;
+}
+
+.books {
+ display:block;
+ position:relative;
+ clear:both;
+ width:100%;
+}
+
+.books li {
+ display:block;
+ width:200px;
+ float:left;
+ position:relative;
+ clear: none ;
+}
+
+.books .html {
+ width:170px;
+ display:block;
+}
+
+.books .pdf {
+ position:absolute;
+ left:170px;
+ top:0px;
+ font-size:smaller;
+}
+
+.books .pdf:link, .books .pdf:visited {
+ color:#555;
+}
+
+.books .pdf:hover, .books .pdf:focus {
+ color:#000;
+}
+
+.books li a {
+ text-decoration:none;
+}
+
+.books li a:hover {
+ color:black;
+}
+
+/*products*/
+.products li {
+ display: block;
+ width:300px;
+ float:left;
+}
+
+.products li a {
+ width:300px;
+ padding:.5em 0em;
+}
+
+.products ul {
+ clear:both;
+}
+
+/*revision history*/
+.revhistory {
+ display:block;
+}
+
+.revhistory table {
+ background-color:transparent;
+ border-color:#fff;
+ padding:0em;
+ margin: 0;
+ border-collapse:collapse;
+ border-style:none;
+}
+
+.revhistory td {
+ text-align :left;
+ padding:0em;
+ border: none;
+ border-top: 1px solid #fff;
+ font-weight: bold;
+}
+
+.revhistory .simplelist td {
+ font-weight: normal;
+}
+
+.revhistory .simplelist {
+ margin-bottom: 1.5em;
+ margin-left: 1em;
+}
+
+.revhistory table th {
+ display: none;
+}
+
+
+/*credits*/
+.authorgroup div {
+ clear:both;
+ text-align: center;
+}
+
+h3.author {
+ margin: 0em;
+ padding: 0em;
+ padding-top: 1em;
+}
+
+.authorgroup h4 {
+ padding: 0em;
+ margin: 0em;
+ padding-top: 1em;
+ margin-top: 1em;
+}
+
+.author,
+.editor,
+.translator,
+.othercredit,
+.contrib {
+ display: block;
+}
+
+.revhistory .author {
+ display: inline;
+}
+
+.othercredit h3 {
+ padding-top: 1em;
+}
+
+
+.othercredit {
+ margin:0em;
+ padding:0em;
+}
+
+.releaseinfo {
+ clear: both;
+}
+
+.copyright {
+ margin-top: 1em;
+}
+
+/* qanda sets */
+.answer {
+ margin-bottom:1em;
+ border-bottom:1px dotted #ccc;
+}
+
+.qandaset .toc {
+ border-bottom:1px dotted #ccc;
+}
+
+.question {
+ font-weight:bold;
+}
+
+.answer .data, .question .data {
+ padding-left: 2.6em;
+}
+
+.answer label, .question label {
+ float:left;
+ font-weight:bold;
+}
+
+/* inline syntax highlighting */
+.perl_Alert {
+ color: #0000ff;
+}
+
+.perl_BaseN {
+ color: #007f00;
+}
+
+.perl_BString {
+ color: #5C3566;
+}
+
+.perl_Char {
+ color: #ff00ff;
+}
+
+.perl_Comment {
+ color: #FF00FF;
+}
+
+
+.perl_DataType {
+ color: #0000ff;
+}
+
+
+.perl_DecVal {
+ color: #00007f;
+}
+
+
+.perl_Error {
+ color: #ff0000;
+}
+
+
+.perl_Float {
+ color: #00007f;
+}
+
+
+.perl_Function {
+ color: #007f00;
+}
+
+
+.perl_IString {
+ color: #5C3566;
+}
+
+
+.perl_Keyword {
+ color: #002F5D;
+}
+
+
+.perl_Operator {
+ color: #ffa500;
+}
+
+
+.perl_Others {
+ color: #b03060;
+}
+
+
+.perl_RegionMarker {
+ color: #96b9ff;
+}
+
+
+.perl_Reserved {
+ color: #9b30ff;
+}
+
+
+.perl_String {
+ color: #5C3566;
+}
+
+
+.perl_Variable {
+ color: #0000ff;
+}
+
+
+.perl_Warning {
+ color: #0000ff;
+}
+
+/*Lists*/
+ul {
+ padding-left:1.6em;
+ list-style-image:url(../images/dot.png);
+ list-style-type: circle;
+}
+
+ul ul {
+ list-style-image:url(../images/dot2.png);
+ list-style-type: circle;
+}
+
+ol {
+ list-style-image:none;
+ list-style-type: decimal;
+}
+
+ol ol {
+ list-style-type: lower-alpha;
+}
+
+ol.arabic {
+ list-style-type: decimal;
+}
+
+ol.loweralpha {
+ list-style-type: lower-alpha;
+}
+
+ol.lowerroman {
+ list-style-type: lower-roman;
+}
+
+ol.upperalpha {
+ list-style-type: upper-alpha;
+}
+
+ol.upperroman {
+ list-style-type: upper-roman;
+}
+
+dt {
+ font-weight:bold;
+ margin-bottom:0em;
+ padding-bottom:0em;
+}
+
+dd {
+ margin:0em;
+ margin-left:2em;
+ padding-top:0em;
+ padding-bottom: 1em;
+}
+
+li {
+ padding-top:0px;
+ margin-top:0em;
+ padding-bottom:0px;
+ margin-bottom:0.4em;
+}
+
+li p, li div.para {
+ padding-top:0px;
+ margin-top:0em;
+ padding-bottom:0px;
+ margin-bottom:0.3em;
+}
+
+/*images*/
+img {
+ display:block;
+ margin: 2em 0;
+}
+
+.inlinemediaobject, .inlinemediaobject img {
+ display:inline;
+ margin:0em;
+}
+
+.figure img {
+ display:block;
+ margin:0;
+ page-break-inside: avoid;
+}
+
+.figure .title {
+ margin:0em;
+ margin-bottom:2em;
+ padding:0px;
+}
+
+/*document modes*/
+.confidential {
+ background-color:#900;
+ color:White;
+ padding:.5em .5em;
+ text-transform:uppercase;
+ text-align:center;
+}
+
+.longdesc-link {
+ display:none;
+}
+
+.longdesc {
+ display:none;
+}
+
+.prompt {
+ padding:0em .3em;
+}
+
+/*user interface styles*/
+.screen .replaceable {
+}
+
+.guibutton, .guilabel {
+ font-family: "liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight: bold;
+ white-space: nowrap;
+}
+
+.example {
+ background-color: #ffffff;
+ border-left: 3px solid #aaaaaa;
+ padding-top: 1em;
+ padding-bottom: 0.1em;
+}
+
+.example h6 {
+ padding-left: 10px;
+}
+
+.example-contents {
+ padding-left: 10px;
+ background-color: #ffffff;
+}
+
+.example-contents .para {
+/* padding: 10px;*/
+}
+
+/*terminal/console text*/
+.computeroutput,
+.option {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight:bold;
+}
+
+.replaceable {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-style: italic;
+}
+
+.command, .filename, .keycap, .classname, .literal {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight:bold;
+}
+
+/* no bold in toc */
+.toc * {
+ font-weight: inherit;
+}
+
+pre {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ display:block;
+ background-color: #f5f5f5;
+ color: #000000;
+ border: 1px solid #aaaaaa;
+ margin-bottom: 0.3em;
+ padding:.5em 1em;
+ white-space: pre-wrap; /* css-3 */
+ white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
+ white-space: -pre-wrap; /* Opera 4-6 */
+ white-space: -o-pre-wrap; /* Opera 7 */
+ word-wrap: break-word; /* Internet Explorer 5.5+ */
+ font-size: 0.9em;
+}
+
+pre .replaceable,
+pre .keycap {
+}
+
+code {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+/* white-space: nowrap;*/
+ white-space: pre-wrap;
+ word-wrap: break-word;
+ font-weight:bold;
+}
+
+.parameter code {
+ display: inline;
+ white-space: pre-wrap; /* css-3 */
+ white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
+ white-space: -pre-wrap; /* Opera 4-6 */
+ white-space: -o-pre-wrap; /* Opera 7 */
+ word-wrap: break-word; /* Internet Explorer 5.5+ */
+}
+
+/*Notifications*/
+div.warning:before {
+ content:url(../images/warning.png);
+ padding-left: 5px;
+}
+
+div.note:before {
+ content:url(../images/note.png);
+ padding-left: 5px;
+}
+
+div.important:before {
+ content:url(../images/important.png);
+ padding-left: 5px;
+}
+
+div.warning, div.note, div.important {
+ color: black;
+ margin: 0em;
+ padding: 0em;
+ background: none;
+ background-color: white;
+ margin-bottom: 1em;
+ border-bottom: 1px solid #aaaaaa;
+ page-break-inside: avoid;
+}
+
+div.warning h2, div.note h2,div.important h2 {
+ margin: 0em;
+ padding: 0em;
+ color: #eeeeec;
+ padding-top: 0px;
+ padding-bottom: 0px;
+ height: 1.4em;
+ line-height: 1.4em;
+ font-size: 1.4em;
+ display:inline;
+}
+
+div.admonition_header {
+ clear: both;
+ margin: 0em;
+ padding: 0em;
+ margin-top: -3.3em;
+ padding-left: 58px;
+ line-height: 1.0em;
+ font-size: 1.0em;
+}
+
+div.warning div.admonition_header {
+ background: url(../images/red.png) top left repeat-x;
+ background-color: #590000;
+}
+
+div.note div.admonition_header {
+ background: url(../images/green.png) top right repeat-x;
+ background-color: #597800;
+}
+
+div.important div.admonition_header {
+ background: url(../images/yellow.png) top right repeat-x;
+ background-color: #a6710f;
+}
+
+div.warning p, div.warning div.para,
+div.note p, div.note div.para,
+div.important p, div.important div.para {
+ padding: 0em;
+ margin: 0em;
+}
+
+div.admonition {
+ border: none;
+ border-left: 1px solid #aaaaaa;
+ border-right: 1px solid #aaaaaa;
+ padding:0em;
+ margin:0em;
+ padding-top: 1.5em;
+ padding-bottom: 1em;
+ padding-left: 2em;
+ padding-right: 1em;
+ background-color: #eeeeec;
+ -moz-border-radius: 0px;
+ -webkit-border-radius: 0px;
+ border-radius: 0px;
+}
+
+/*Page Title*/
+#title {
+ display:block;
+ height:45px;
+ padding-bottom:1em;
+ margin:0em;
+}
+
+#title a.left{
+ display:inline;
+ border:none;
+}
+
+#title a.left img{
+ border:none;
+ float:left;
+ margin:0em;
+ margin-top:.7em;
+}
+
+#title a.right {
+ padding-bottom:1em;
+}
+
+#title a.right img {
+ border:none;
+ float:right;
+ margin:0em;
+ margin-top:.7em;
+}
+
+/*Table*/
+div.table {
+ page-break-inside: avoid;
+}
+
+table {
+ border:1px solid #6c614b;
+ width:100%;
+ border-collapse:collapse;
+}
+
+table.simplelist, .calloutlist table {
+ border-style: none;
+}
+
+table th {
+ text-align:left;
+ background-color:#6699cc;
+ padding:.3em .5em;
+ color:white;
+}
+
+table td {
+ padding:.15em .5em;
+}
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+table th p:first-child, table td p:first-child, table li p:first-child,
+table th div.para:first-child, table td div.para:first-child, table li div.para:first-child {
+ margin-top:0em;
+ padding-top:0em;
+ display:inline;
+}
+
+th, td {
+ border-style:none;
+ vertical-align: top;
+ border: 1px solid #000;
+}
+
+.simplelist th, .simplelist td {
+ border: none;
+}
+
+table table td {
+ border-bottom:1px dotted #aaa;
+ background-color:white;
+ padding:.6em 0em;
+}
+
+table table {
+ border:1px solid white;
+}
+
+td.remarkval {
+ color:#444;
+}
+
+td.fieldval {
+ font-weight:bold;
+}
+
+.lbname, .lbtype, .lbdescr, .lbdriver, .lbhost {
+ color:white;
+ font-weight:bold;
+ background-color:#999;
+ width:120px;
+}
+
+td.remarkval {
+ width:230px;
+}
+
+td.tname {
+ font-weight:bold;
+}
+
+th.dbfield {
+ width:120px;
+}
+
+th.dbtype {
+ width:70px;
+}
+
+th.dbdefault {
+ width:70px;
+}
+
+th.dbnul {
+ width:70px;
+}
+
+th.dbkey {
+ width:70px;
+}
+
+span.book {
+ margin-top:4em;
+ display:block;
+ font-size:11pt;
+}
+
+span.book a{
+ font-weight:bold;
+}
+span.chapter {
+ display:block;
+ margin-top:0.5em;
+}
+
+table.simplelist td, .calloutlist table td {
+ border-style: none;
+}
+
+/*Breadcrumbs*/
+#breadcrumbs ul li.first:before {
+ content:" ";
+}
+
+#breadcrumbs {
+ color:#900;
+ padding:3px;
+ margin-bottom:25px;
+}
+
+#breadcrumbs ul {
+ margin-left:0;
+ padding-left:0;
+ display:inline;
+ border:none;
+}
+
+#breadcrumbs ul li {
+ margin-left:0;
+ padding-left:2px;
+ border:none;
+ list-style:none;
+ display:inline;
+}
+
+#breadcrumbs ul li:before {
+ content:"\0020 \0020 \0020 \00BB \0020";
+ color:#333;
+}
+
+/*index*/
+.glossary h3,
+.index h3 {
+ font-size: 2em;
+ color:#aaa;
+ margin:0em;
+}
+
+.indexdiv {
+ margin-bottom:1em;
+}
+
+.glossary dt,
+.index dt {
+ color:#444;
+ padding-top:.5em;
+}
+
+.glossary dl dl dt,
+.index dl dl dt {
+ color:#777;
+ font-weight:normal;
+ padding-top:0em;
+}
+
+.index dl dl dt:before {
+ content:"- ";
+ color:#ccc;
+}
+
+/*changes*/
+.footnote {
+ font-size: .7em;
+ margin:0em;
+ color:#222;
+}
+
+table .footnote {
+}
+
+sup {
+ color:#999;
+ margin:0em;
+ padding:0em;
+ line-height: .4em;
+ font-size: 1em;
+ padding-left:0em;
+}
+
+.footnote {
+ position:relative;
+}
+
+.footnote sup {
+ color:#e3dcc0;
+ position:absolute;
+ left: .4em;
+}
+
+.footnote sup a:link,
+.footnote sup a:visited {
+ color:#92917d;
+ text-decoration:none;
+}
+
+.footnote:hover sup a {
+ text-decoration:none;
+}
+
+.footnote p,.footnote div.para {
+ padding-left:2em;
+}
+
+.footnote a:link,
+.footnote a:visited {
+ color:#00537c;
+}
+
+.footnote a:hover {
+}
+
+/**/
+div.chapter {
+ margin-top:3em;
+ page-break-inside: avoid;
+}
+
+div.preface {
+ page-break-inside: avoid;
+}
+
+div.section {
+ margin-top:1em;
+ page-break-inside: auto;
+}
+
+div.note .replaceable,
+div.important .replaceable,
+div.warning .replaceable,
+div.note .keycap,
+div.important .keycap,
+div.warning .keycap
+{
+}
+
+ul li p:last-child, ul li div.para:last-child {
+ margin-bottom:0em;
+ padding-bottom:0em;
+}
+
+/*document navigation*/
+.docnav a, .docnav strong {
+ border:none;
+ text-decoration:none;
+ font-weight:normal;
+}
+
+.docnav {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+ position:relative;
+ width:100%;
+ padding-bottom:2em;
+ padding-top:1em;
+ border-top:1px dotted #ccc;
+}
+
+.docnav li {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+ display:inline;
+ font-size:.8em;
+}
+
+.docnav li:before {
+ content:" ";
+}
+
+.docnav li.previous, .docnav li.next {
+ position:absolute;
+ top:1em;
+}
+
+.docnav li.up, .docnav li.home {
+ margin:0em 1.5em;
+}
+
+.docnav li.previous {
+ left:0px;
+ text-align:left;
+}
+
+.docnav li.next {
+ right:0px;
+ text-align:right;
+}
+
+.docnav li.previous strong, .docnav li.next strong {
+ height:22px;
+ display:block;
+}
+
+.docnav {
+ margin:0 auto;
+ text-align:center;
+}
+
+.docnav li.next a strong {
+ background: url(../images/stock-go-forward.png) top right no-repeat;
+ padding-top:3px;
+ padding-bottom:4px;
+ padding-right:28px;
+ font-size:1.2em;
+}
+
+.docnav li.previous a strong {
+ background: url(../images/stock-go-back.png) top left no-repeat;
+ padding-top:3px;
+ padding-bottom:4px;
+ padding-left:28px;
+ padding-right:0.5em;
+ font-size:1.2em;
+}
+
+.docnav li.home a strong {
+ background: url(../images/stock-home.png) top left no-repeat;
+ padding:5px;
+ padding-left:28px;
+ font-size:1.2em;
+}
+
+.docnav li.up a strong {
+ background: url(../images/stock-go-up.png) top left no-repeat;
+ padding:5px;
+ padding-left:28px;
+ font-size:1.2em;
+}
+
+.docnav a:link, .docnav a:visited {
+ color:#666;
+}
+
+.docnav a:hover, .docnav a:focus, .docnav a:active {
+ color:black;
+}
+
+.docnav a {
+ max-width: 10em;
+ overflow:hidden;
+}
+
+.docnav a:link strong {
+ text-decoration:none;
+}
+
+.docnav {
+ margin:0 auto;
+ text-align:center;
+}
+
+ul.docnav {
+ margin-bottom: 1em;
+}
+/* Reports */
+.reports ul {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+}
+
+.reports li{
+ margin:0em;
+ padding:0em;
+}
+
+.reports li.odd {
+ background-color: #eeeeee;
+ margin:0em;
+ padding:0em;
+}
+
+.reports dl {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ float:right;
+ margin-right: 17em;
+ margin-top:-1.3em;
+}
+
+.reports dt {
+ display:inline;
+ margin:0em;
+ padding:0em;
+}
+
+.reports dd {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ padding-right:.5em;
+}
+
+.reports h2, .reports h3{
+ display:inline;
+ padding-right:.5em;
+ font-size:10pt;
+ font-weight:normal;
+}
+
+.reports div.progress {
+ display:inline;
+ float:right;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ margin:0em;
+ margin-top:-1.3em;
+ padding:0em;
+ border:none;
+}
+
+/*uniform*/
+body.results, body.reports {
+ max-width:57em ;
+ padding:0em;
+}
+
+/*Progress Bar*/
+div.progress {
+ display:block;
+ float:left;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ height:1em;
+}
+
+div.progress span {
+ height:1em;
+ float:left;
+}
+
+div.progress span.translated {
+ background:#6c3 url(../images/shine.png) top left repeat-x;
+}
+
+div.progress span.fuzzy {
+ background:#ff9f00 url(../images/shine.png) top left repeat-x;
+}
+
+
+/*Results*/
+
+.results ul {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+}
+
+.results li{
+ margin:0em;
+ padding:0em;
+}
+
+.results li.odd {
+ background-color: #eeeeee;
+ margin:0em;
+ padding:0em;
+}
+
+.results dl {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ float:right;
+ margin-right: 17em;
+ margin-top:-1.3em;
+}
+
+.results dt {
+ display:inline;
+ margin:0em;
+ padding:0em;
+}
+
+.results dd {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ padding-right:.5em;
+}
+
+.results h2, .results h3 {
+ display:inline;
+ padding-right:.5em;
+ font-size:10pt;
+ font-weight:normal;
+}
+
+.results div.progress {
+ display:inline;
+ float:right;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ margin:0em;
+ margin-top:-1.3em;
+ padding:0em;
+ border:none;
+}
+
+/* Dirty EVIL Mozilla hack for round corners */
+pre {
+ -moz-border-radius:11px;
+ -webkit-border-radius:11px;
+ border-radius: 11px;
+ page-break-inside: avoid;
+}
+
+.example {
+ -moz-border-radius:0px;
+ -webkit-border-radius:0px;
+ border-radius: 0px;
+ page-break-inside: avoid;
+}
+
+.package, .citetitle {
+ font-style: italic;
+}
+
+.titlepage .edition {
+ color: #336699;
+ background-color: transparent;
+ margin-top: 1em;
+ margin-bottom: 1em;
+ font-size: 1.4em;
+ font-weight: bold;
+ text-align: center;
+}
+
+span.remark {
+ background-color: #ff00ff;
+}
+
+.draft {
+ background-image: url(../images/watermark-draft.png);
+ background-repeat: repeat-y;
+ background-position: center;
+}
+
+.foreignphrase {
+ font-style: inherit;
+}
+
+dt {
+ clear:both;
+}
+
+dt img {
+ border-style: none;
+ max-width: 112px;
+}
+
+dt object {
+ max-width: 112px;
+}
+
+dt .inlinemediaobject, dt object {
+ display: inline;
+ float: left;
+ margin-bottom: 1em;
+ padding-right: 1em;
+ width: 112px;
+}
+
+dl:after {
+ display: block;
+ clear: both;
+ content: "";
+}
+
+.toc dd {
+ padding-bottom: 0em;
+ margin-bottom: 1em;
+ padding-left: 1.3em;
+ margin-left: 0em;
+}
+
+div.toc > dl > dt {
+ padding-bottom: 0em;
+ margin-bottom: 0em;
+ margin-top: 1em;
+}
+
+
+.strikethrough {
+ text-decoration: line-through;
+}
+
+.underline {
+ text-decoration: underline;
+}
+
+.calloutlist img, .callout {
+ padding: 0em;
+ margin: 0em;
+ width: 12pt;
+ display: inline;
+ vertical-align: middle;
+}
+
+.stepalternatives {
+ list-style-image: none;
+ list-style-type: none;
+}
+
+
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/default.css b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/default.css
new file mode 100644
index 0000000..bf38ebb
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/default.css
@@ -0,0 +1,3 @@
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/lang.css b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/lang.css
new file mode 100644
index 0000000..81c3115
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/lang.css
@@ -0,0 +1,2 @@
+/* place holder */
+
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/menu.css b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/menu.css
new file mode 100644
index 0000000..f574cc5
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/menu.css
@@ -0,0 +1,48 @@
+a:link {
+ color:#0066cc;
+}
+
+a:visited {
+ color:#6699cc;
+}
+
+h1,h2,h3,h4,h5,h6 {
+ color:#a70000;
+}
+
+div.producttitle {
+ color:#a70000;
+}
+
+.section h1.title {
+ color:#a70000;
+}
+
+table {
+ border:1px solid #aaa;
+}
+
+table th {
+ background-color:#900;
+}
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+.revhistory table th {
+ color:#a70000;
+}
+
+.titlepage .edition {
+ color: #a70000;
+}
+
+span.remark{
+ background-color: #ffff00;
+}
+
+.home{
+ color: #a70000;
+}
+
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/overrides.css b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/overrides.css
new file mode 100644
index 0000000..0498ded
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/overrides.css
@@ -0,0 +1,46 @@
+a:link {
+ color:#0066cc;
+}
+
+a:visited {
+ color:#6699cc;
+}
+
+h1,h2,h3,h4,h5,h6 {
+ color:#a70000;
+}
+
+div.producttitle {
+/* background: #a70000 url(../images/h1-bg.png) top left repeat; */
+ color:#a70000;
+}
+
+.section h1.title {
+ color:#a70000;
+}
+
+
+
+table {
+ border:1px solid #aaa;
+}
+
+table th {
+ background-color:#900;
+}
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+.revhistory table th {
+ color:#a70000;
+}
+
+.titlepage .edition {
+ color: #a70000;
+}
+
+span.remark{
+ background-color: #ffff00;
+}
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/pdf.css b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/pdf.css
new file mode 100644
index 0000000..cbeab47
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/pdf.css
@@ -0,0 +1,138 @@
+
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
+
+/* Cover Page styles */
+
+html {
+ height: 260mm;
+}
+
+body.cover {
+ height: 100%;
+ background-color: white;
+/* margin-left: 10em;
+ margin-right: 10em;
+*/ padding: 0px;
+ font-family: "overpass", sans-serif;
+ font-weight:300;
+}
+
+body.cover > div {
+ height: 100%;
+}
+
+body.cover * {
+ text-align: left;
+ box-sizing: border-box;
+ -moz-box-sizing: border-box;
+ -webkit-box-sizing: border-box;
+}
+
+body.cover div.logo {
+ height: 30%;
+ background-position: 50% 0%;
+ margin-top: 15mm;
+ background-image: url(../images/title_logo.svg);
+ background-repeat: no-repeat;
+}
+
+
+body.cover div.leader {
+ display: inline-block;
+ font-size: 40px;
+ font-weight: 600;
+ margin-top: 2em;
+}
+
+body.cover div.product {
+ display: inline;
+}
+
+
+body.cover div.edition {
+ display: inline;
+}
+
+body.cover div.docname {
+ font-size: 40px;
+ font-weight: 600;
+ height: 10%;
+}
+
+body.cover div.subtitle {
+ height: 20%;
+ font-weight:300;
+ font-size: 20px;
+ color: black;
+ border-top: .1em solid black;
+ padding-top: 40px;
+}
+body.cover div.authors {
+}
+
+body.cover div.author {
+ float: left;
+ min-width: 33%;
+ font-weight: 300;
+ font-size: 20px;
+}
+
+div.draft {
+ background-image: url(../images/watermark-draft.png);
+ background-repeat: repeat-y;
+ background-position: center;
+}
+
+body.titlepages {
+ text-align: left;
+}
+
+body.titlepages > div {
+ height: 100%;
+}
+body.titlepages .legalnotice {
+ page-break-before: always;
+}
+
+body.titlepages .title {
+ font-size: 20px;
+ color: black;
+ font-weight: normal;
+ margin-bottom: 0.1em;
+}
+
+body.titlepages .subtitle {
+ color: black;
+ font-weight: normal;
+ text-align: left;
+ font-size: 12px;
+ margin-top: 0.1em;
+ margin-bottom: 2em;
+}
+
+body.titlepages .contributor {
+ margin-bottom: 1em;
+ font-size: 12px;
+}
+
+body.titlepages .abstract {
+ page-break-before: avoid !important;
+ font-size: 14px;
+}
+
+body.titlepages h1 {
+ color: black;
+ font-size: 14px;
+ font-weight: normal;
+}
+
+body.titlepages .editors h1,
+body.titlepages .othercredit h1,
+body.titlepages .legalnotice h1,
+body.titlepages .keywords h1,
+body.titlepages .abstract h1 {
+ font-weight: bold;
+}
+
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/print.css b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/print.css
new file mode 100644
index 0000000..773d8ae
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/print.css
@@ -0,0 +1,16 @@
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
+
+#tocframe {
+ display: none;
+}
+
+body.toc_embeded {
+ margin-left: 30px;
+}
+
+.producttitle {
+ color: #336699;
+}
+
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/1.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/1.png
new file mode 100644
index 0000000..270707b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/1.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/1.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/1.svg
new file mode 100644
index 0000000..0a7036e
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/1.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;fill:#000000;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 17.853468,22.008438 -2.564941,0 0,-7.022461 c -5e-6,-0.143873 -5e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224122,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08854,0.08302 -0.17432,0.157723 -0.257324,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/10.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/10.png
new file mode 100644
index 0000000..ec548f3
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/10.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/10.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/10.svg
new file mode 100644
index 0000000..d1c32c7
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/10.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/11.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/11.png
new file mode 100644
index 0000000..f59d84b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/11.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/11.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/11.svg
new file mode 100644
index 0000000..872d14a
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/11.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/12.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/12.png
new file mode 100644
index 0000000..c8a3906
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/12.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/12.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/12.svg
new file mode 100644
index 0000000..6bc95d2
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/12.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c 0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141 0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801 0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648 -0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083 -1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l -1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/13.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/13.png
new file mode 100644
index 0000000..2db6743
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/13.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/13.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/13.svg
new file mode 100644
index 0000000..cf105bc
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/13.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883 -0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579 2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273 -0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534 -1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l 0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961 0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414 0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289 -0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032 -0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269 0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026 -0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l -1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868 0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393 1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/14.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/14.png
new file mode 100644
index 0000000..1a12fb3
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/14.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/14.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/14.svg
new file mode 100644
index 0000000..1009bce
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/14.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/15.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/15.png
new file mode 100644
index 0000000..2532d13
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/15.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/15.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/15.svg
new file mode 100644
index 0000000..52daf8d
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/15.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2839"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2841"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/16.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/16.png
new file mode 100644
index 0000000..3b3f17f
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/16.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/16.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/16.svg
new file mode 100644
index 0000000..95dedc2
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/16.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/17.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/17.png
new file mode 100644
index 0000000..d0f12f7
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/17.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/17.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/17.svg
new file mode 100644
index 0000000..7b3e327
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/17.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/18.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/18.png
new file mode 100644
index 0000000..ed2f1fe
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/18.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/18.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/18.svg
new file mode 100644
index 0000000..fc744d5
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/18.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/19.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/19.png
new file mode 100644
index 0000000..a145b4a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/19.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/19.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/19.svg
new file mode 100644
index 0000000..69c6f5f
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/19.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/2.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/2.png
new file mode 100644
index 0000000..126f8fd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/2.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/2.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/2.svg
new file mode 100644
index 0000000..15424b2
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/2.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.89546,22.008438 -8.143066,0 0,-1.784668 2.855468,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979493,-1.0708 0.293289,-0.326492 0.545079,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.373529,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.17431,-0.666821 0.174316,-1.037598 -6e-6,-0.409496 -0.124517,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827313,0.522958 -1.270019,0.921386 l -1.394531,-1.651855 c 0.249022,-0.226877 0.509113,-0.442698 0.780273,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079102,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319824,-0.1494141 0.58105,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187012,0.6889648 0.326489,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.893727 0.265625,1.41
9433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/20.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/20.png
new file mode 100644
index 0000000..b23618f
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/20.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/20.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/20.svg
new file mode 100644
index 0000000..7abd11e
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/20.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/21.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/21.png
new file mode 100644
index 0000000..91b602b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/21.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/21.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/21.svg
new file mode 100644
index 0000000..8d33472
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/21.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/22.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/22.png
new file mode 100644
index 0000000..33e0374
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/22.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/22.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/22.svg
new file mode 100644
index 0000000..0224965
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/22.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c 0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141 0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801 0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648 -0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083 -1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l -1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/23.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/23.png
new file mode 100644
index 0000000..cc961c1
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/23.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/23.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/23.svg
new file mode 100644
index 0000000..72609f4
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/23.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883 -0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579 2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273 -0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534 -1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l 0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961 0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414 0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289 -0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032 -0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269 0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026 -0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l -1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868 0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393 1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/24.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/24.png
new file mode 100644
index 0000000..17b1531
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/24.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/24.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/24.svg
new file mode 100644
index 0000000..5b34c33
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/24.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/25.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/25.png
new file mode 100644
index 0000000..193686c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/25.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/25.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/25.svg
new file mode 100644
index 0000000..4f57373
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/25.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/26.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/26.png
new file mode 100644
index 0000000..e8bf82a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/26.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/26.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/26.svg
new file mode 100644
index 0000000..aff5a90
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/26.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/27.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/27.png
new file mode 100644
index 0000000..06dfc67
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/27.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/27.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/27.svg
new file mode 100644
index 0000000..0769006
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/27.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/28.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/28.png
new file mode 100644
index 0000000..065ce1a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/28.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/28.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/28.svg
new file mode 100644
index 0000000..60cf157
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/28.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/29.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/29.png
new file mode 100644
index 0000000..8f28d5b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/29.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/29.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/29.svg
new file mode 100644
index 0000000..6dc6635
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/29.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/3.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/3.png
new file mode 100644
index 0000000..9e3ae40
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/3.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/3.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/3.svg
new file mode 100644
index 0000000..2e88abd
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/3.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.422316,12.587051 c -9e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.23243,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315437,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.392911,0.332031 -0.890957,0.592122 -1.494141,0.780273 -0.597661,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267255,-0.05534 -1.842773,-0.166016 -0.575523,-0.105143 -1.112306,-0.268392 -1.610352,-0.489746 l 0,-2.183105 c 0.249023,0.132815 0.511881,0.249025 0.788574,0.348632 0.276692,0.09961 0.553384,0.185387 0.830079,0.257325 0.27669,0.06641 0.547848,0.116212 0.813476,0.149414 0.271156,0.0332 0.525713,0.04981 0.763672,0.0498 0.475907,2e-6 0.871577,-0.04427 1.187012,-0.132812 0.315424,-
0.08854 0.567214,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320957,-0.351397 0.398437,-0.572754 0.083,-0.226885 0.124506,-0.473141 0.124512,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.265631,-0.376297 -0.498047,-0.514648 -0.226893,-0.143876 -0.525721,-0.254553 -0.896484,-0.332032 -0.370773,-0.07747 -0.827315,-0.116205 -1.369629,-0.116211 l -0.863281,0 0,-1.801269 0.846679,0 c 0.509111,7e-6 0.932451,-0.04426 1.27002,-0.132813 0.33756,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.43164,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.68897,-0.365224 -1.27002,-0.365234 -0.265629,10e-6 -0.514652,0.02768 -0.74707,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193688,0.07748 -0.373538,0.166026 -0.539551,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439941,0.282227 l -1.294922,-1.70
9961 c 0.232421,-0.171538 0.484211,-0.329253 0.755371,-0.473145 0.276691,-0.143868 0.575519,-0.26838 0.896484,-0.373535 0.320961,-0.1106647 0.666827,-0.1964393 1.037598,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492506,0.1272911 0.913079,0.3154421 1.261718,0.5644531 0.348626,0.243501 0.617017,0.545096 0.805176,0.904786 0.193677,0.354177 0.290519,0.760914 0.290528,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/30.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/30.png
new file mode 100644
index 0000000..d583185
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/30.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/30.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/30.svg
new file mode 100644
index 0000000..717ae1c
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/30.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/31.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/31.png
new file mode 100644
index 0000000..9146925
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/31.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/31.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/31.svg
new file mode 100644
index 0000000..25c7b52
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/31.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/32.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/32.png
new file mode 100644
index 0000000..cbc972e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/32.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/32.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/32.svg
new file mode 100644
index 0000000..79866e8
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/32.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c 0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141 0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801 0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648 -0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083 -1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l -1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/33.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/33.png
new file mode 100644
index 0000000..7c1ab6a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/33.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/33.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/33.svg
new file mode 100644
index 0000000..01c3222
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/33.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883 -0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579 2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273 -0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534 -1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l 0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961 0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414 0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289 -0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032 -0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269 0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026 -0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l -1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868 0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393 1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/34.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/34.png
new file mode 100644
index 0000000..2585ddc
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/34.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/34.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/34.svg
new file mode 100644
index 0000000..cf9cf7c
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/34.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/35.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/35.png
new file mode 100644
index 0000000..86ff09c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/35.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/35.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/35.svg
new file mode 100644
index 0000000..948ed84
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/35.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/36.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/36.png
new file mode 100644
index 0000000..c4a7f79
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/36.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/36.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/36.svg
new file mode 100644
index 0000000..cff32b5
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/36.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/37.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/37.png
new file mode 100644
index 0000000..91cf6ae
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/37.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/37.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/37.svg
new file mode 100644
index 0000000..6694ee4
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/37.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/38.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/38.png
new file mode 100644
index 0000000..882f8cd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/38.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/38.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/38.svg
new file mode 100644
index 0000000..26ded93
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/38.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/39.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/39.png
new file mode 100644
index 0000000..cc0726d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/39.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/39.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/39.svg
new file mode 100644
index 0000000..082c1b1
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/39.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/4.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/4.png
new file mode 100644
index 0000000..266e714
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/4.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/4.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/4.svg
new file mode 100644
index 0000000..25888e4
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/4.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 20.078077,19.493301 -1.460937,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460937,0 0,1.992187 m -3.959472,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09962,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.12175,0.2601 -0.262863,0.520191 -0.42334,0.780274 l -2.025391,3.071289 2.75586,0"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/40.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/40.png
new file mode 100644
index 0000000..b92fd2f
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/40.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/40.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/40.svg
new file mode 100644
index 0000000..33ef96a
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/40.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.440535,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.0136719,0 0,-1.784668 5.1547849,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262863,0.520191 -0.42334,0.780274 l -2.0253904,3.071289 2.7558594,0"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/5.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/5.png
new file mode 100644
index 0000000..94153bd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/5.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/5.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/5.svg
new file mode 100644
index 0000000..7d1dabd
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/5.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 16.035597,14.255508 c 0.520177,8e-6 1.004388,0.08025 1.452637,0.240723 0.448235,0.160489 0.838371,0.395678 1.17041,0.705566 0.332023,0.309903 0.592114,0.697272 0.780273,1.16211 0.188143,0.459315 0.282218,0.987797 0.282227,1.585449 -9e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.204761,0.520184 -0.506356,0.962892 -0.904785,1.328125 -0.398445,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261724,0.290528 -2.025391,0.290528 -0.304365,0 -0.60596,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863281,-0.124512 -0.271161,-0.04981 -0.531252,-0.116211 -0.780274,-0.199219 -0.24349,-0.08301 -0.464844,-0.17985 -0.664062,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672363,0.31543 0.254556,0.09408 0.517414,0.177086 0.788574,0.249024 0.276691,0.06641 0.553383,0.121746 0.830078,0.166015 0.27669,0.03874 0.539548,0.05811 0.788575,0.05811 0.741532,2e-6 1.305984,-0.152179 1.693359,-0.456543 0.387364,-0.309893 0.5810
49,-0.799639 0.581055,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751465,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320966,0.03874 -0.481445,0.06641 -0.154951,0.02768 -0.304365,0.05811 -0.448242,0.09131 -0.143883,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456542,-6.1840821 6.408204,0 0,2.1748051 -4.183594,0 -0.199219,2.382324 c 0.17708,-0.03873 0.381832,-0.07747 0.614258,-0.116211 0.237951,-0.03873 0.542313,-0.0581 0.913086,-0.05811"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/6.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/6.png
new file mode 100644
index 0000000..792940e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/6.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/6.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/6.svg
new file mode 100644
index 0000000..3ab7c39
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/6.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 11.702589,16.853653 c -10e-7,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.0664,-0.575514 0.179849,-1.126132 0.340332,-1.651856 0.166014,-0.531241 0.387368,-1.023753 0.664062,-1.477539 0.282225,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431638,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603186,-0.1936727 1.305984,-0.2905151 2.108399,-0.2905274 0.116204,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.138339,0.00555 0.276685,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251782,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210295,-0.04979 -0.434416,-0.08853 -0.672364,-0.116211 -0.232429,-0.03319 -0.467617,-0.04979 -0.705566,-0.0498 -0.747076,1e-5 -1.361334,0.09408 -1.842774,0.282226 -0.481449,0.182627 -0.863285,0.439951 -1.145507,0.771973 -0.28223,0.33204 -0.484216,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.215821,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243486,-0.384596 0.39843
7,-0.556153 0.160478,-0.177076 0.345862,-0.32649 0.556153,-0.448242 0.210282,-0.127271 0.44547,-0.22688 0.705566,-0.298828 0.26562,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419433,0.257324 0.420566,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.15494,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282226,1.768066 -0.182626,0.520184 -0.445484,0.962892 -0.788575,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643554,0.282227 -0.597661,0 -1.15658,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.973961,-0.542317 -1.361328,-0.979492 -0.381838,-0.437173 -0.683433,-0.987791 -0.904785,-1.651856 -0.215822,-0.669593 -0.323732,-1.460933 -0.323731,-2.374023 m 4.216797,3.270508 c 0.226883,2e-6 0.431635,-0.0415 0.614258,-0.124512 0.188145,-0.08854 0.348627,-0.218585 0.481445,-0.390137 0.13834,-0.17708 0.243483,-0.3
98434 0.31543,-0.664062 0.07747,-0.265622 0.116204,-0.581051 0.116211,-0.946289 -7e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243496,-0.343094 -0.617031,-0.514643 -1.120606,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.39014,0.229661 -0.53955,0.390137 -0.149418,0.160487 -0.265629,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.31543,0.755371 0.143876,0.221357 0.318193,0.401207 0.522949,0.539551 0.210282,0.138349 0.453772,0.207522 0.730469,0.20752"
+ id="path2846"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/7.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/7.png
new file mode 100644
index 0000000..59eaefd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/7.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/7.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/7.svg
new file mode 100644
index 0000000..ab9cb5d
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/7.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 12.789991,22.008438 4.316407,-9.960937 -5.578125,0 0,-2.1582035 8.367187,0 0,1.6103515 -4.424316,10.508789 -2.681153,0"
+ id="path2832"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/8.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/8.png
new file mode 100644
index 0000000..6aad94b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/8.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/8.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/8.svg
new file mode 100644
index 0000000..23b1e20
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/8.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.761671,9.7149811 c 0.503576,1.23e-5 0.979487,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337558,0.243501 0.60595,0.547862 0.805176,0.913086 0.199211,0.365244 0.29882,0.794118 0.298828,1.286621 -8e-6,0.365243 -0.05535,0.697274 -0.166015,0.996094 -0.110686,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193693,0.237963 -0.423348,0.451017 -0.688965,0.639161 -0.265632,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.633619,0.362473 0.937988,0.572754 0.309888,0.210292 0.583814,0.448247 0.821777,0.713867 0.237948,0.260096 0.428866,0.55339 0.572754,0.879883 0.143872,0.326501 0.215812,0.691735 0.21582,1.095703 -8e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478686,0.758139 -0.838379,1.045898 -0.359707,0.287761 -0.791348,0.509115 -1.294921,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651856,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.9379
9,-0.362467 -1.286621,-0.639161 -0.348634,-0.276691 -0.614259,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265626,-0.857744 -0.265625,-1.361328 -10e-7,-0.415035 0.06087,-0.78857 0.182617,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498047,-0.896485 0.210285,-0.265619 0.456541,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271162,-0.171543 -0.525719,-0.356927 -0.763672,-0.556152 -0.237958,-0.204746 -0.445477,-0.428866 -0.622559,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -10e-7,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478677,-0.669585 0.821778,-0.913086 0.343096,-0.249012 0.738766,-0.434396 1.187011,-0.5561527 0.448239,-0.1217326 0.918616,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.107911,0.614258 0.07194,0.18262 0.17708,0.340334 0.315429,0.473145 0.143877,0.132814 0.32
096,0.237957 0.53125,0.315429 0.210283,0.07194 0.453772,0.107912 0.730469,0.10791 0.581049,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.43164,-1.087402 -6e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218593,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.320969,-0.307125 -0.514648,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 15.662062,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664063,0.398438 -0.199222,0.138351 -0.370772,0.293299 -0.514648,0.464844 -0.13835,0.16602 -0.24626,0.348637 -0.323731,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.701661,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514649,0.08301 -0.154952,0.05535 -0.290531,0.13559 -0.406738,0.240723 -0.110681,0.105153 -0.199223,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.31543
8 0.282226,0.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160478,0.09962 0.32926,0.199226 0.506348,0.298828 0.171545,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154943,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.12174,-0.138338 0.218582,-0.293286 0.290528,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.157721,-0.284984 -0.273926,-0.390137 -0.116217,-0.105133 -0.254563,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/9.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/9.png
new file mode 100644
index 0000000..2478355
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/9.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/9.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/9.svg
new file mode 100644
index 0000000..80db11b
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/9.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.829054,15.052383 c -9e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340333,1.651856 -0.160489,0.525719 -0.381843,1.018232 -0.664062,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426113,0.332032 -0.940761,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.30046,0.282227 -2.108399,0.282227 -0.116214,0 -0.243492,-0.0028 -0.381836,-0.0083 -0.138348,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273927,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237954,0.02767 0.478676,0.04151 0.722168,0.0415 0.747067,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.481441,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.282221,-0.337562 0.481439,-0.738766 0.597657,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.107911,0 c -0.110683,0.199225 -0.243495,0.384609 -0.398437,0.556153 -0.
154954,0.171554 -0.337571,0.320968 -0.547852,0.448242 -0.210291,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.265629,0.07194 -0.56169,0.107914 -0.888183,0.10791 -0.52572,4e-6 -0.998864,-0.08577 -1.419434,-0.257324 -0.420575,-0.171545 -0.777508,-0.420568 -1.070801,-0.74707 -0.287761,-0.326492 -0.509115,-0.727696 -0.664062,-1.203614 -0.154949,-0.475904 -0.232423,-1.020988 -0.232422,-1.635253 -10e-7,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453774,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758135,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043127,-0.2905151 1.651855,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520176,0.210298 0.971184,0.534028 1.353027,0.971192 0.381829,0.437185 0.683423,0.990569 0.904786,1.660156 0.221345,0.669605 0.332022,1.458178 0.332031,2.365722 m -4.216797,-3.262207 c -0.226892,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188154,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132815,0.17155
9 -0.237959,0.392913 -0.315429,0.664062 -0.07194,0.265634 -0.107914,0.581063 -0.107911,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373536,1.394532 0.249019,0.343105 0.625321,0.514654 1.128906,0.514648 0.254552,6e-6 0.486974,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.53955,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124506,-0.401197 0.124512,-0.605958 -6e-6,-0.282218 -0.03598,-0.561677 -0.10791,-0.838378 -0.06641,-0.282218 -0.171556,-0.534008 -0.31543,-0.755372 -0.138352,-0.226878 -0.312668,-0.409495 -0.522949,-0.547851 -0.204758,-0.138336 -0.44548,-0.207509 -0.722168,-0.20752"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/bkgrnd_greydots.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/bkgrnd_greydots.png
new file mode 100644
index 0000000..2333a6d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/bkgrnd_greydots.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/bullet_arrowblue.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/bullet_arrowblue.png
new file mode 100644
index 0000000..c235534
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/bullet_arrowblue.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/documentation.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/documentation.png
new file mode 100644
index 0000000..7ae45bd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/documentation.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/dot.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/dot.png
new file mode 100644
index 0000000..36a6859
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/dot.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/dot2.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/dot2.png
new file mode 100644
index 0000000..40aff92
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/dot2.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/green.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/green.png
new file mode 100644
index 0000000..ebb3c24
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/green.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/h1-bg.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/h1-bg.png
new file mode 100644
index 0000000..31397b5
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/h1-bg.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/image_left.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/image_left.png
new file mode 100644
index 0000000..ecd4856
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/image_left.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/image_right.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/image_right.png
new file mode 100644
index 0000000..7ae45bd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/image_right.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/important.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/important.png
new file mode 100644
index 0000000..eb42966
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/important.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/important.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/important.svg
new file mode 100644
index 0000000..064c783
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/important.svg
@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg2">
+ <defs
+ id="defs5" />
+ <path
+ d="M 255.25,-411.29002 L 261.86798,-400.85887 L 273.83367,-397.7882 L 265.95811,-388.27072 L 266.73534,-375.94179 L 255.25,-380.49082 L 243.76466,-375.94179 L 244.54189,-388.27072 L 236.66633,-397.7882 L 248.63202,-400.85887 L 255.25,-411.29002 z "
+ transform="matrix(1.1071323,0,0,1.1071323,-258.4137,459.98052)"
+ style="fill:#2e3436;fill-opacity:1;stroke:#2e3436;stroke-width:4.25880718;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1"
+ id="path4450" />
+ <path
+ d="M 255.25,-411.29002 L 261.86798,-400.85887 L 273.83367,-397.7882 L 265.95811,-388.27072 L 266.73534,-375.94179 L 255.25,-380.49082 L 243.76466,-375.94179 L 244.54189,-388.27072 L 236.66633,-397.7882 L 248.63202,-400.85887 L 255.25,-411.29002 z "
+ transform="matrix(1.1071323,0,0,1.1071323,-258.4137,459.98052)"
+ style="fill:#fac521;fill-opacity:1;stroke-width:3.4070456;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1"
+ id="path4452" />
+ <path
+ d="M 24.175987,4.476098 L 16.980534,16.087712 L 3.9317841,19.443104 L 16.980534,20.076901 L 24.175987,10.383543 L 31.408721,20.076901 L 44.457471,19.443104 L 31.468862,16.027571 L 24.175987,4.476098 z "
+ style="fill:#feeaab;fill-opacity:1;stroke-width:3.4070456;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1"
+ id="path4531" />
+ <path
+ d="M 12.456856,24.055852 C 11.65845,24.299685 14.436112,29.177769 14.436112,32.041127 C 14.436112,37.343117 13.010825,39.831516 15.971742,37.364645 C 18.711008,35.08244 21.184735,34.873512 24.195894,34.873512 C 27.207053,34.873512 29.646656,35.08244 32.38592,37.364645 C 35.346837,39.831516 33.921551,37.343117 33.92155,32.041127 C 33.92155,28.223316 38.868232,20.827013 33.682674,25.591482 C 31.458295,27.635233 27.413886,29.481744 24.195894,29.481744 C 20.977903,29.481744 16.933493,27.635233 14.709113,25.591482 C 13.412724,24.400365 12.722992,23.974574 12.456856,24.055852 z "
+ style="fill:#fcd867;fill-opacity:1;stroke-width:3.4070456;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1"
+ id="path2185" />
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/note.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/note.png
new file mode 100644
index 0000000..2b421d2
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/note.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/note.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/note.svg
new file mode 100644
index 0000000..abe5a60
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/note.svg
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg2">
+ <defs
+ id="defs5" />
+ <path
+ d="M 30.27396,4.1232594 L 18.765811,4.1232594 C 11.476786,4.1232594 5.5574109,10.546411 5.5574109,19.960741 C 5.5574109,24.746615 7.0844878,29.075948 9.5403943,32.177328 C 9.4616811,32.681104 9.414455,33.200619 9.414455,33.720144 C 9.414455,39.308917 13.554865,43.591015 18.891751,44.267966 C 17.506371,42.693663 16.656245,40.914707 16.656245,38.616218 C 16.656245,38.01799 16.719219,37.419752 16.82942,36.837262 C 17.459135,36.963202 18.104599,37.026176 18.750063,37.026176 L 30.258211,37.026176 C 37.547237,37.026176 43.466612,29.39081 43.466612,19.960741 C 43.466612,10.530672 37.578724,4.1232594 30.27396,4.1232594 z "
+ style="fill:#2e3436;fill-opacity:1;stroke:#2e3436;stroke-width:4.7150631;stroke-miterlimit:4;stroke-dasharray:none"
+ id="path4317" />
+ <path
+ d="M 30.27396,4.1232594 L 18.765811,4.1232594 C 11.476786,4.1232594 5.5574109,10.546411 5.5574109,19.960741 C 5.5574109,24.746615 7.0844878,29.075948 9.5403943,32.177328 C 9.4616811,32.681104 9.414455,33.200619 9.414455,33.720144 C 9.414455,39.308917 13.554865,43.591015 18.891751,44.267966 C 17.506371,42.693663 16.656245,40.914707 16.656245,38.616218 C 16.656245,38.01799 16.719219,37.419752 16.82942,36.837262 C 17.459135,36.963202 18.104599,37.026176 18.750063,37.026176 L 30.258211,37.026176 C 37.547237,37.026176 43.466612,29.39081 43.466612,19.960741 C 43.466612,10.530672 37.578724,4.1232594 30.27396,4.1232594 z "
+ style="fill:#bfdce8;fill-opacity:1"
+ id="path142" />
+ <path
+ d="M 19.200879,5.5648899 C 12.490241,5.5648899 7.0622987,11.295775 7.0622987,19.690323 C 7.0622987,22.890926 7.8418023,25.879852 9.1910836,28.332288 C 8.6113289,26.599889 8.2852163,24.667826 8.2852163,22.673336 C 8.2852163,14.629768 13.495502,9.1620492 19.925575,9.1620492 L 30.071259,9.1620492 C 36.515213,9.1620492 41.711609,14.616311 41.711609,22.673336 C 41.864688,21.709218 41.983366,20.710908 41.983366,19.690323 C 41.983366,11.281743 36.524624,5.5648899 29.799492,5.5648899 L 19.200879,5.5648899 z "
+ style="fill:#ffffff"
+ id="path2358" />
+ <path
+ d="M 28.241965,33.725087 L 20.792252,33.725087 C 16.073756,33.725087 12.241894,32.944782 12.241894,26.850486 C 12.241894,25.10387 12.368512,23.572125 15.515722,23.567487 L 33.508301,23.540969 C 36.182481,23.537028 36.782127,24.950794 36.782127,26.850486 C 36.782127,32.95497 32.970649,33.725087 28.241965,33.725087 z "
+ style="fill:#d0ecf9;fill-opacity:1"
+ id="path2173" />
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/red.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/red.png
new file mode 100644
index 0000000..d32d5e2
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/red.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/redhat-logo.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/redhat-logo.svg
new file mode 100644
index 0000000..1001776
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/redhat-logo.svg
@@ -0,0 +1,94 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://web.resource.org/cc/"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:xlink="http://www.w3.org/1999/xlink"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ width="300"
+ height="140"
+ id="svg2812"
+ sodipodi:version="0.32"
+ inkscape:version="0.45+devel"
+ version="1.0"
+ sodipodi:docname="redhat-logo.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape">
+ <defs
+ id="defs3" />
+ <sodipodi:namedview
+ inkscape:document-units="mm"
+ id="base"
+ pagecolor="#ffffff"
+ bordercolor="#666666"
+ borderopacity="1.0"
+ inkscape:pageopacity="0.0"
+ inkscape:pageshadow="2"
+ inkscape:zoom="1"
+ inkscape:cx="174.26394"
+ inkscape:cy="40.358463"
+ inkscape:current-layer="layer1"
+ inkscape:window-width="722"
+ inkscape:window-height="523"
+ inkscape:window-x="71"
+ inkscape:window-y="636"
+ width="300px"
+ height="140px" />
+ <metadata
+ id="metadata4">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <g
+ inkscape:label="Layer 1"
+ inkscape:groupmode="layer"
+ id="layer1"
+ transform="translate(-13.714282,-252.57246)">
+ <g
+ transform="matrix(2.1166666,0,0,2.1166666,-32.193429,187.76029)"
+ id="shadowman">
+ <path
+ d="M 55.68466,68.503937 C 55.68466,79.688581 46.617715,88.755526 35.433071,88.755526 C 24.248427,88.755526 15.181482,79.688581 15.181482,68.503937 C 15.181482,57.319293 24.248427,48.252348 35.433071,48.252348 C 46.617715,48.252348 55.68466,57.319293 55.68466,68.503937 z"
+ transform="matrix(1.10693,0,0,1.10693,5.005761,-12.00975)"
+ style="fill:#ffffff"
+ id="path4548" />
+ <path
+ d="M 147.81332,72.126073 C 147.81332,73.329962 147.86057,74.57586 148.03519,75.740362 L 146.64882,75.740362 L 146.42826,73.559712 L 146.35605,73.559712 C 145.61822,74.733404 143.92333,76.086957 141.50635,76.086957 C 138.4461,76.086957 137.02164,73.933874 137.02164,71.904202 C 137.02164,68.394942 140.11998,66.27862 146.30878,66.34295 L 146.30878,65.937278 C 146.30878,64.432747 146.01471,61.431561 142.41879,61.45388 C 141.08756,61.45388 139.70118,61.810976 138.5997,62.588186 L 138.1205,61.494579 C 139.51083,60.551948 141.20703,60.180411 142.58291,60.180411 C 146.97178,60.180411 147.81201,63.475677 147.81201,66.194597 L 147.81201,72.126073 L 147.81332,72.126073 z M 146.30878,67.609855 C 142.99645,67.514016 138.62333,68.015527 138.62333,71.667888 C 138.62333,73.853791 140.06616,74.835806 141.65077,74.835806 C 144.1859,74.835806 145.62742,73.266945 146.15124,71.786044 C 146.26152,71.460456 146.3101,71.134869 146.3101,70.874924 L 146.3101,67.609855 L 146.30878,67.609855 z
M 153.80387,57.175286 L 153.80387,60.527004 L 158.13891,60.527004 L 158.13891,61.747959 L 153.80387,61.747959 L 153.80387,71.635066 C 153.80387,73.568902 154.40385,74.780665 156.03835,74.780665 C 156.82343,74.780665 157.37877,74.676951 157.76606,74.541727 L 157.94856,75.707542 C 157.45754,75.912347 156.76567,76.072514 155.84798,76.072514 C 154.73862,76.072514 153.81831,75.723296 153.22358,74.994662 C 152.53566,74.195133 152.29934,72.917726 152.29934,71.365932 L 152.29934,61.746646 L 149.7314,61.746646 L 149.7314,60.525692 L 152.29934,60.525692 L 152.29934,57.729312 L 153.80387,57.175286 z M 129.02767,60.179099 C 127.87105,60.179099 126.8339,60.512563 125.96348,61.052146 C 125.05891,61.581226 124.3224,62.399135 123.88522,63.247239 L 123.8222,63.247239 L 123.8222,55.719331 L 122.31767,55.309721 L 122.31767,75.740362 L 123.8222,75.740362 L 123.8222,66.437475 C 123.8222,65.819121 123.86947,65.39113 124.02832,64.938196 C 124.67818,63.046372 126.45974,61.493265 128.61545,61.49326
5 C 131.72953,61.493265 132.80739,63.990315 132.80739,66.730242 L 132.80739,75.73905 L 134.31191,75.73905 L 134.31191,66.564822 C 134.31191,60.899855 130.4692,60.179099 129.02767,60.179099 z"
+ id="path620" />
+ <path
+ d="M 78.208384,65.270348 C 78.208384,63.205228 78.16506,61.686255 78.08235,60.311696 L 81.460325,60.311696 L 81.604739,63.240675 L 81.713705,63.240675 C 82.473849,61.069213 84.273772,59.961164 85.938472,59.961164 C 86.319199,59.961164 86.541071,59.976918 86.853532,60.045187 L 86.853532,63.719867 C 86.488557,63.648972 86.147215,63.609587 85.677213,63.609587 C 83.819525,63.609587 82.528988,64.792469 82.181081,66.560884 C 82.115438,66.904852 82.079992,67.318401 82.079992,67.738514 L 82.079992,75.73905 L 78.176875,75.73905 L 78.208384,65.270348 z M 91.56274,69.076313 C 91.666455,71.871381 93.83004,73.093647 96.328402,73.093647 C 98.123074,73.093647 99.405732,72.814009 100.58599,72.379455 L 101.16365,75.064243 C 99.842914,75.623519 98.010169,76.042319 95.771752,76.042319 C 90.763211,76.042319 87.82767,72.949234 87.82767,68.220332 C 87.82767,63.961432 90.411366,59.933594 95.372644,59.933594 C 100.38906,59.933594 102.02225,64.059896 102.02225,67.436558 C 102.02225,68.16256
6 101.95792,68.744161 101.88309,69.103883 L 91.56274,69.076313 z M 98.348885,66.358704 C 98.365952,64.929006 97.743659,62.59869 95.129766,62.59869 C 92.728556,62.59869 91.730785,64.778027 91.554863,66.358704 L 98.348885,66.358704 z M 118.82942,54.363153 L 114.93024,53.307617 L 114.93024,61.97377 L 114.8659,61.97377 C 114.17665,60.834212 112.65375,59.962477 110.54268,59.962477 C 106.83386,59.962477 103.60162,63.033244 103.62656,68.201952 C 103.62656,72.945296 106.54372,76.086957 110.22759,76.086957 C 112.45288,76.086957 114.31582,75.024857 115.23745,73.297141 L 115.30703,73.297141 L 115.48164,75.73905 L 118.95675,75.73905 C 118.88586,74.690078 118.82809,72.991246 118.82809,71.411881 L 118.82809,54.363153 L 118.82942,54.363153 z M 114.92893,69.050056 C 114.92893,69.459667 114.90136,69.840395 114.81077,70.189614 C 114.41823,71.877945 113.0371,72.966301 111.44198,72.966301 C 108.98563,72.966301 107.57957,70.894617 107.57957,68.060164 C 107.57957,65.198141 108.97382,62.983355 111
.48662,62.983355 C 113.2406,62.983355 114.49568,64.220064 114.84228,65.72197 C 114.90922,66.038368 114.92893,66.428286 114.92893,66.738119 L 114.92893,69.050056 L 114.92893,69.050056 z"
+ id="path616" />
+ <path
+ d="M 161.80517,73.528501 C 160.90479,73.528501 160.18937,74.243893 160.18939,75.144292 C 160.18939,76.044668 160.90478,76.760094 161.80517,76.760081 C 162.70554,76.760081 163.42095,76.041202 163.42097,75.144292 C 163.42097,74.24046 162.70554,73.528501 161.80517,73.528501 z M 161.80517,73.803529 C 162.54687,73.803529 163.14594,74.402585 163.14593,75.144292 C 163.14593,75.882533 162.54342,76.485053 161.80517,76.485053 C 161.06348,76.485053 160.46441,75.882523 160.46441,75.144292 C 160.46441,74.402596 161.06346,73.80354 161.80517,73.803529 z M 161.25512,74.319207 L 161.25512,75.969376 L 161.49577,75.969376 L 161.49577,75.247426 L 161.80517,75.247426 L 162.2521,75.969376 L 162.52712,75.969376 L 162.04582,75.247426 C 162.29078,75.216382 162.49274,75.06625 162.49274,74.766128 C 162.49273,74.438393 162.30159,74.319207 161.90832,74.319207 L 161.25512,74.319207 z M 161.49577,74.525479 L 161.83955,74.525479 C 162.0155,74.525467 162.21771,74.562596 162.21771,74.766128 C 162.21
773,75.02142 162.01906,75.041156 161.80517,75.041156 L 161.49577,75.041156 L 161.49577,74.525479 z"
+ id="path650" />
+ <path
+ d="M 63.115808,76.090895 C 60.810796,75.504093 58.522203,75.797079 56.285026,76.486064 C 56.010655,76.526189 56.159301,76.830359 56.114355,76.953441 C 56.240389,77.319727 56.032958,77.717522 54.998429,77.944646 C 53.465014,78.282048 52.496128,79.864039 51.942103,80.389181 C 51.290927,81.007536 49.45293,81.388262 49.729943,81.01935 C 49.946565,80.730522 50.773662,79.83253 51.276485,78.861018 C 51.726795,77.99322 52.127215,77.746405 52.678614,76.919305 C 52.841408,76.676428 53.46764,75.824385 53.650127,75.149578 C 53.854932,74.490525 53.786663,73.663427 53.865435,73.323398 C 53.97834,72.83239 54.440465,71.767665 54.477226,71.166377 C 54.496918,70.825035 53.056716,71.650821 52.372719,71.650821 C 51.688722,71.650821 51.024417,71.242523 50.412627,71.21364 C 49.657736,71.17688 49.17198,71.795235 48.489295,71.68758 C 48.098065,71.625877 47.769852,71.281909 47.087167,71.255652 C 46.115654,71.220205 44.928834,71.795235 42.698294,71.724341 C 40.507139,71.653447 38.480092,68.9
52905 38.204394,68.523601 C 37.880118,68.019465 37.484949,68.019465 37.054333,68.414634 C 36.622404,68.809804 36.090697,68.498657 35.939718,68.234773 C 35.652203,67.73195 34.882871,66.258927 33.692111,65.951719 C 32.044479,65.523729 31.210817,66.864153 31.31847,67.928878 C 31.427438,69.010669 32.127189,69.31394 32.451465,69.887656 C 32.77574,70.462687 32.94116,70.834225 33.54901,71.088919 C 33.980939,71.267467 34.142421,71.53529 34.013762,71.888448 C 33.900856,72.198281 33.451859,72.269175 33.156467,72.282304 C 31.933813,72.291845 31.468231,71.67907 30.76576,70.807968 C 30.388969,70.188301 29.79556,69.919166 29.103685,69.919166 C 28.774159,69.919166 28.465638,70.005814 28.191252,70.147603 C 27.106833,70.710817 25.817611,71.045595 24.429922,71.045595 L 22.863688,71.045595 C 22.102232,68.784859 21.688683,66.365268 21.688683,63.847213 C 21.688683,51.409229 31.770093,41.32782 44.208077,41.32782 C 56.646061,41.32782 66.72747,51.410542 66.72747,63.847213 C 66.730097,68.36212 65.40
1488,72.565881 63.115808,76.090895 z M 49.170707,74.025807 C 49.286239,74.138712 49.485793,74.518127 49.241602,75.001258 C 49.105065,75.257265 48.956712,75.437126 48.694141,75.647183 C 48.37643,75.900564 47.758075,76.194643 46.908658,75.65506 C 46.451785,75.364919 46.424215,75.267768 45.794044,75.349165 C 45.343735,75.408243 45.163874,74.953995 45.326668,74.575893 C 45.488149,74.199104 46.152454,73.893208 46.980865,74.378965 C 47.353716,74.598211 47.932685,75.059024 48.44076,74.649413 C 48.65213,74.481367 48.778164,74.368462 49.069618,74.031058 C 49.082746,74.015304 49.101126,74.007427 49.122132,74.007427 C 49.140512,74.007427 49.157579,74.013991 49.170707,74.025807 z"
+ id="path632" />
+ <path
+ d="M 63.115853,76.089615 C 65.401534,72.564599 66.72883,68.36215 66.72883,63.849868 C 66.72883,51.411879 56.647417,41.330466 44.209428,41.330466 C 31.77144,41.330466 21.690027,51.413192 21.690027,63.849868 C 21.690027,66.367923 22.103576,68.787515 22.865032,71.046939 C 25.868844,79.95466 34.290809,86.367957 44.209428,86.367957 C 52.133821,86.367957 59.101143,82.275788 63.115853,76.089615 z"
+ style="fill:none"
+ id="path646" />
+ <path
+ d="M 56.917822,57.857972 C 56.694636,58.606299 56.378238,59.562056 54.970858,60.285439 C 54.766053,60.390468 54.687282,60.218483 54.781807,60.057003 C 55.313513,59.151133 55.409352,58.925322 55.562956,58.568226 C 55.779577,58.047022 55.892482,57.303946 55.463179,55.754779 C 54.615075,52.707643 52.849285,48.633855 51.564001,47.31181 C 50.32598,46.037029 48.079686,45.677306 46.050011,46.19851 C 45.302998,46.390186 43.839164,47.151642 41.126807,46.539852 C 36.433353,45.483004 35.738853,47.833013 35.468405,48.857041 C 35.197956,49.881066 34.552032,52.791666 34.552032,52.791666 C 34.33541,53.977174 34.05446,56.038354 41.342116,57.426043 C 44.737158,58.071966 44.910455,58.950266 45.060119,59.58175 C 45.329254,60.712117 45.761183,61.360667 46.245627,61.682316 C 46.731383,62.006591 46.245627,62.274414 45.707356,62.329554 C 44.260592,62.480532 38.917273,60.947118 35.754607,59.151133 C 33.168283,57.570457 33.124958,56.147322 33.717056,54.939495 C 29.808689,54.516756 26.877084
,55.304469 26.345378,57.155594 C 25.431631,60.330077 33.324513,65.752165 42.311003,68.473712 C 51.741236,71.329172 61.440606,69.336258 62.519772,63.40872 C 63.012093,60.71343 60.74348,58.721829 56.917822,57.857972 z M 42.458041,52.053841 C 39.857276,52.241579 39.586829,52.52253 39.099759,53.041108 C 38.411824,53.772368 37.507268,52.090601 37.507268,52.090601 C 36.965059,51.976382 36.306006,51.100708 36.661789,50.2828 C 37.012321,49.474082 37.658246,49.71696 37.860425,49.969029 C 38.107242,50.274923 38.633697,50.777747 39.315068,50.759366 C 39.997753,50.7423 40.785465,50.597886 41.884324,50.597886 C 42.998938,50.597886 43.745953,51.014061 43.789276,51.371156 C 43.823411,51.675739 43.698689,51.964567 42.458041,52.053841 z M 45.191406,47.754243 C 45.187466,47.754243 45.183528,47.755556 45.179589,47.755556 C 45.138891,47.755556 45.107383,47.72536 45.107383,47.687287 C 45.107383,47.659717 45.123137,47.636085 45.14808,47.625583 C 45.652218,47.359073 46.404482,47.147704 47.265715,4
7.059743 C 47.524347,47.032172 47.776416,47.019045 48.019294,47.016418 C 48.062617,47.016418 48.103316,47.016418 48.147954,47.017731 C 49.592094,47.04924 50.746092,47.622957 50.729025,48.299078 C 50.711958,48.973884 49.527763,49.495088 48.084936,49.46358 C 47.617561,49.453076 47.179067,49.384807 46.800965,49.275842 C 46.756328,49.264025 46.723506,49.225952 46.723506,49.181315 C 46.723506,49.135365 46.756328,49.097292 46.802278,49.08679 C 47.702895,48.878046 48.310747,48.538016 48.268737,48.215055 C 48.212283,47.788376 47.03334,47.557315 45.637776,47.696476 C 45.484171,47.713544 45.334507,47.733237 45.191406,47.754243 z"
+ style="fill:#cc0000"
+ id="path648" />
+ <use
+ transform="translate(-94.61853,1.913321)"
+ id="use4312"
+ x="0"
+ y="0"
+ width="744.09448"
+ height="1052.3622"
+ xlink:href="#path650" />
+ </g>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/rhlogo.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/rhlogo.png
new file mode 100644
index 0000000..ecd4856
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/rhlogo.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/shade.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/shade.png
new file mode 100644
index 0000000..a73afdf
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/shade.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/shine.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/shine.png
new file mode 100644
index 0000000..a18f7c4
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/shine.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-back.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-back.png
new file mode 100644
index 0000000..8160290
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-back.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-forward.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-forward.png
new file mode 100644
index 0000000..be86474
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-forward.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-up.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-up.png
new file mode 100644
index 0000000..52a31ed
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-up.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-home.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-home.png
new file mode 100644
index 0000000..b9ce2b8
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-home.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/title_logo.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/title_logo.png
new file mode 100644
index 0000000..ecd4856
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/title_logo.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/title_logo.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/title_logo.svg
new file mode 100644
index 0000000..1001776
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/title_logo.svg
@@ -0,0 +1,94 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://web.resource.org/cc/"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:xlink="http://www.w3.org/1999/xlink"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ width="300"
+ height="140"
+ id="svg2812"
+ sodipodi:version="0.32"
+ inkscape:version="0.45+devel"
+ version="1.0"
+ sodipodi:docname="redhat-logo.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape">
+ <defs
+ id="defs3" />
+ <sodipodi:namedview
+ inkscape:document-units="mm"
+ id="base"
+ pagecolor="#ffffff"
+ bordercolor="#666666"
+ borderopacity="1.0"
+ inkscape:pageopacity="0.0"
+ inkscape:pageshadow="2"
+ inkscape:zoom="1"
+ inkscape:cx="174.26394"
+ inkscape:cy="40.358463"
+ inkscape:current-layer="layer1"
+ inkscape:window-width="722"
+ inkscape:window-height="523"
+ inkscape:window-x="71"
+ inkscape:window-y="636"
+ width="300px"
+ height="140px" />
+ <metadata
+ id="metadata4">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <g
+ inkscape:label="Layer 1"
+ inkscape:groupmode="layer"
+ id="layer1"
+ transform="translate(-13.714282,-252.57246)">
+ <g
+ transform="matrix(2.1166666,0,0,2.1166666,-32.193429,187.76029)"
+ id="shadowman">
+ <path
+ d="M 55.68466,68.503937 C 55.68466,79.688581 46.617715,88.755526 35.433071,88.755526 C 24.248427,88.755526 15.181482,79.688581 15.181482,68.503937 C 15.181482,57.319293 24.248427,48.252348 35.433071,48.252348 C 46.617715,48.252348 55.68466,57.319293 55.68466,68.503937 z"
+ transform="matrix(1.10693,0,0,1.10693,5.005761,-12.00975)"
+ style="fill:#ffffff"
+ id="path4548" />
+ <path
+ d="M 147.81332,72.126073 C 147.81332,73.329962 147.86057,74.57586 148.03519,75.740362 L 146.64882,75.740362 L 146.42826,73.559712 L 146.35605,73.559712 C 145.61822,74.733404 143.92333,76.086957 141.50635,76.086957 C 138.4461,76.086957 137.02164,73.933874 137.02164,71.904202 C 137.02164,68.394942 140.11998,66.27862 146.30878,66.34295 L 146.30878,65.937278 C 146.30878,64.432747 146.01471,61.431561 142.41879,61.45388 C 141.08756,61.45388 139.70118,61.810976 138.5997,62.588186 L 138.1205,61.494579 C 139.51083,60.551948 141.20703,60.180411 142.58291,60.180411 C 146.97178,60.180411 147.81201,63.475677 147.81201,66.194597 L 147.81201,72.126073 L 147.81332,72.126073 z M 146.30878,67.609855 C 142.99645,67.514016 138.62333,68.015527 138.62333,71.667888 C 138.62333,73.853791 140.06616,74.835806 141.65077,74.835806 C 144.1859,74.835806 145.62742,73.266945 146.15124,71.786044 C 146.26152,71.460456 146.3101,71.134869 146.3101,70.874924 L 146.3101,67.609855 L 146.30878,67.609855 z
M 153.80387,57.175286 L 153.80387,60.527004 L 158.13891,60.527004 L 158.13891,61.747959 L 153.80387,61.747959 L 153.80387,71.635066 C 153.80387,73.568902 154.40385,74.780665 156.03835,74.780665 C 156.82343,74.780665 157.37877,74.676951 157.76606,74.541727 L 157.94856,75.707542 C 157.45754,75.912347 156.76567,76.072514 155.84798,76.072514 C 154.73862,76.072514 153.81831,75.723296 153.22358,74.994662 C 152.53566,74.195133 152.29934,72.917726 152.29934,71.365932 L 152.29934,61.746646 L 149.7314,61.746646 L 149.7314,60.525692 L 152.29934,60.525692 L 152.29934,57.729312 L 153.80387,57.175286 z M 129.02767,60.179099 C 127.87105,60.179099 126.8339,60.512563 125.96348,61.052146 C 125.05891,61.581226 124.3224,62.399135 123.88522,63.247239 L 123.8222,63.247239 L 123.8222,55.719331 L 122.31767,55.309721 L 122.31767,75.740362 L 123.8222,75.740362 L 123.8222,66.437475 C 123.8222,65.819121 123.86947,65.39113 124.02832,64.938196 C 124.67818,63.046372 126.45974,61.493265 128.61545,61.49326
5 C 131.72953,61.493265 132.80739,63.990315 132.80739,66.730242 L 132.80739,75.73905 L 134.31191,75.73905 L 134.31191,66.564822 C 134.31191,60.899855 130.4692,60.179099 129.02767,60.179099 z"
+ id="path620" />
+ <path
+ d="M 78.208384,65.270348 C 78.208384,63.205228 78.16506,61.686255 78.08235,60.311696 L 81.460325,60.311696 L 81.604739,63.240675 L 81.713705,63.240675 C 82.473849,61.069213 84.273772,59.961164 85.938472,59.961164 C 86.319199,59.961164 86.541071,59.976918 86.853532,60.045187 L 86.853532,63.719867 C 86.488557,63.648972 86.147215,63.609587 85.677213,63.609587 C 83.819525,63.609587 82.528988,64.792469 82.181081,66.560884 C 82.115438,66.904852 82.079992,67.318401 82.079992,67.738514 L 82.079992,75.73905 L 78.176875,75.73905 L 78.208384,65.270348 z M 91.56274,69.076313 C 91.666455,71.871381 93.83004,73.093647 96.328402,73.093647 C 98.123074,73.093647 99.405732,72.814009 100.58599,72.379455 L 101.16365,75.064243 C 99.842914,75.623519 98.010169,76.042319 95.771752,76.042319 C 90.763211,76.042319 87.82767,72.949234 87.82767,68.220332 C 87.82767,63.961432 90.411366,59.933594 95.372644,59.933594 C 100.38906,59.933594 102.02225,64.059896 102.02225,67.436558 C 102.02225,68.16256
6 101.95792,68.744161 101.88309,69.103883 L 91.56274,69.076313 z M 98.348885,66.358704 C 98.365952,64.929006 97.743659,62.59869 95.129766,62.59869 C 92.728556,62.59869 91.730785,64.778027 91.554863,66.358704 L 98.348885,66.358704 z M 118.82942,54.363153 L 114.93024,53.307617 L 114.93024,61.97377 L 114.8659,61.97377 C 114.17665,60.834212 112.65375,59.962477 110.54268,59.962477 C 106.83386,59.962477 103.60162,63.033244 103.62656,68.201952 C 103.62656,72.945296 106.54372,76.086957 110.22759,76.086957 C 112.45288,76.086957 114.31582,75.024857 115.23745,73.297141 L 115.30703,73.297141 L 115.48164,75.73905 L 118.95675,75.73905 C 118.88586,74.690078 118.82809,72.991246 118.82809,71.411881 L 118.82809,54.363153 L 118.82942,54.363153 z M 114.92893,69.050056 C 114.92893,69.459667 114.90136,69.840395 114.81077,70.189614 C 114.41823,71.877945 113.0371,72.966301 111.44198,72.966301 C 108.98563,72.966301 107.57957,70.894617 107.57957,68.060164 C 107.57957,65.198141 108.97382,62.983355 111
.48662,62.983355 C 113.2406,62.983355 114.49568,64.220064 114.84228,65.72197 C 114.90922,66.038368 114.92893,66.428286 114.92893,66.738119 L 114.92893,69.050056 L 114.92893,69.050056 z"
+ id="path616" />
+ <path
+ d="M 161.80517,73.528501 C 160.90479,73.528501 160.18937,74.243893 160.18939,75.144292 C 160.18939,76.044668 160.90478,76.760094 161.80517,76.760081 C 162.70554,76.760081 163.42095,76.041202 163.42097,75.144292 C 163.42097,74.24046 162.70554,73.528501 161.80517,73.528501 z M 161.80517,73.803529 C 162.54687,73.803529 163.14594,74.402585 163.14593,75.144292 C 163.14593,75.882533 162.54342,76.485053 161.80517,76.485053 C 161.06348,76.485053 160.46441,75.882523 160.46441,75.144292 C 160.46441,74.402596 161.06346,73.80354 161.80517,73.803529 z M 161.25512,74.319207 L 161.25512,75.969376 L 161.49577,75.969376 L 161.49577,75.247426 L 161.80517,75.247426 L 162.2521,75.969376 L 162.52712,75.969376 L 162.04582,75.247426 C 162.29078,75.216382 162.49274,75.06625 162.49274,74.766128 C 162.49273,74.438393 162.30159,74.319207 161.90832,74.319207 L 161.25512,74.319207 z M 161.49577,74.525479 L 161.83955,74.525479 C 162.0155,74.525467 162.21771,74.562596 162.21771,74.766128 C 162.21
773,75.02142 162.01906,75.041156 161.80517,75.041156 L 161.49577,75.041156 L 161.49577,74.525479 z"
+ id="path650" />
+ <path
+ d="M 63.115808,76.090895 C 60.810796,75.504093 58.522203,75.797079 56.285026,76.486064 C 56.010655,76.526189 56.159301,76.830359 56.114355,76.953441 C 56.240389,77.319727 56.032958,77.717522 54.998429,77.944646 C 53.465014,78.282048 52.496128,79.864039 51.942103,80.389181 C 51.290927,81.007536 49.45293,81.388262 49.729943,81.01935 C 49.946565,80.730522 50.773662,79.83253 51.276485,78.861018 C 51.726795,77.99322 52.127215,77.746405 52.678614,76.919305 C 52.841408,76.676428 53.46764,75.824385 53.650127,75.149578 C 53.854932,74.490525 53.786663,73.663427 53.865435,73.323398 C 53.97834,72.83239 54.440465,71.767665 54.477226,71.166377 C 54.496918,70.825035 53.056716,71.650821 52.372719,71.650821 C 51.688722,71.650821 51.024417,71.242523 50.412627,71.21364 C 49.657736,71.17688 49.17198,71.795235 48.489295,71.68758 C 48.098065,71.625877 47.769852,71.281909 47.087167,71.255652 C 46.115654,71.220205 44.928834,71.795235 42.698294,71.724341 C 40.507139,71.653447 38.480092,68.9
52905 38.204394,68.523601 C 37.880118,68.019465 37.484949,68.019465 37.054333,68.414634 C 36.622404,68.809804 36.090697,68.498657 35.939718,68.234773 C 35.652203,67.73195 34.882871,66.258927 33.692111,65.951719 C 32.044479,65.523729 31.210817,66.864153 31.31847,67.928878 C 31.427438,69.010669 32.127189,69.31394 32.451465,69.887656 C 32.77574,70.462687 32.94116,70.834225 33.54901,71.088919 C 33.980939,71.267467 34.142421,71.53529 34.013762,71.888448 C 33.900856,72.198281 33.451859,72.269175 33.156467,72.282304 C 31.933813,72.291845 31.468231,71.67907 30.76576,70.807968 C 30.388969,70.188301 29.79556,69.919166 29.103685,69.919166 C 28.774159,69.919166 28.465638,70.005814 28.191252,70.147603 C 27.106833,70.710817 25.817611,71.045595 24.429922,71.045595 L 22.863688,71.045595 C 22.102232,68.784859 21.688683,66.365268 21.688683,63.847213 C 21.688683,51.409229 31.770093,41.32782 44.208077,41.32782 C 56.646061,41.32782 66.72747,51.410542 66.72747,63.847213 C 66.730097,68.36212 65.40
1488,72.565881 63.115808,76.090895 z M 49.170707,74.025807 C 49.286239,74.138712 49.485793,74.518127 49.241602,75.001258 C 49.105065,75.257265 48.956712,75.437126 48.694141,75.647183 C 48.37643,75.900564 47.758075,76.194643 46.908658,75.65506 C 46.451785,75.364919 46.424215,75.267768 45.794044,75.349165 C 45.343735,75.408243 45.163874,74.953995 45.326668,74.575893 C 45.488149,74.199104 46.152454,73.893208 46.980865,74.378965 C 47.353716,74.598211 47.932685,75.059024 48.44076,74.649413 C 48.65213,74.481367 48.778164,74.368462 49.069618,74.031058 C 49.082746,74.015304 49.101126,74.007427 49.122132,74.007427 C 49.140512,74.007427 49.157579,74.013991 49.170707,74.025807 z"
+ id="path632" />
+ <path
+ d="M 63.115853,76.089615 C 65.401534,72.564599 66.72883,68.36215 66.72883,63.849868 C 66.72883,51.411879 56.647417,41.330466 44.209428,41.330466 C 31.77144,41.330466 21.690027,51.413192 21.690027,63.849868 C 21.690027,66.367923 22.103576,68.787515 22.865032,71.046939 C 25.868844,79.95466 34.290809,86.367957 44.209428,86.367957 C 52.133821,86.367957 59.101143,82.275788 63.115853,76.089615 z"
+ style="fill:none"
+ id="path646" />
+ <path
+ d="M 56.917822,57.857972 C 56.694636,58.606299 56.378238,59.562056 54.970858,60.285439 C 54.766053,60.390468 54.687282,60.218483 54.781807,60.057003 C 55.313513,59.151133 55.409352,58.925322 55.562956,58.568226 C 55.779577,58.047022 55.892482,57.303946 55.463179,55.754779 C 54.615075,52.707643 52.849285,48.633855 51.564001,47.31181 C 50.32598,46.037029 48.079686,45.677306 46.050011,46.19851 C 45.302998,46.390186 43.839164,47.151642 41.126807,46.539852 C 36.433353,45.483004 35.738853,47.833013 35.468405,48.857041 C 35.197956,49.881066 34.552032,52.791666 34.552032,52.791666 C 34.33541,53.977174 34.05446,56.038354 41.342116,57.426043 C 44.737158,58.071966 44.910455,58.950266 45.060119,59.58175 C 45.329254,60.712117 45.761183,61.360667 46.245627,61.682316 C 46.731383,62.006591 46.245627,62.274414 45.707356,62.329554 C 44.260592,62.480532 38.917273,60.947118 35.754607,59.151133 C 33.168283,57.570457 33.124958,56.147322 33.717056,54.939495 C 29.808689,54.516756 26.877084
,55.304469 26.345378,57.155594 C 25.431631,60.330077 33.324513,65.752165 42.311003,68.473712 C 51.741236,71.329172 61.440606,69.336258 62.519772,63.40872 C 63.012093,60.71343 60.74348,58.721829 56.917822,57.857972 z M 42.458041,52.053841 C 39.857276,52.241579 39.586829,52.52253 39.099759,53.041108 C 38.411824,53.772368 37.507268,52.090601 37.507268,52.090601 C 36.965059,51.976382 36.306006,51.100708 36.661789,50.2828 C 37.012321,49.474082 37.658246,49.71696 37.860425,49.969029 C 38.107242,50.274923 38.633697,50.777747 39.315068,50.759366 C 39.997753,50.7423 40.785465,50.597886 41.884324,50.597886 C 42.998938,50.597886 43.745953,51.014061 43.789276,51.371156 C 43.823411,51.675739 43.698689,51.964567 42.458041,52.053841 z M 45.191406,47.754243 C 45.187466,47.754243 45.183528,47.755556 45.179589,47.755556 C 45.138891,47.755556 45.107383,47.72536 45.107383,47.687287 C 45.107383,47.659717 45.123137,47.636085 45.14808,47.625583 C 45.652218,47.359073 46.404482,47.147704 47.265715,4
7.059743 C 47.524347,47.032172 47.776416,47.019045 48.019294,47.016418 C 48.062617,47.016418 48.103316,47.016418 48.147954,47.017731 C 49.592094,47.04924 50.746092,47.622957 50.729025,48.299078 C 50.711958,48.973884 49.527763,49.495088 48.084936,49.46358 C 47.617561,49.453076 47.179067,49.384807 46.800965,49.275842 C 46.756328,49.264025 46.723506,49.225952 46.723506,49.181315 C 46.723506,49.135365 46.756328,49.097292 46.802278,49.08679 C 47.702895,48.878046 48.310747,48.538016 48.268737,48.215055 C 48.212283,47.788376 47.03334,47.557315 45.637776,47.696476 C 45.484171,47.713544 45.334507,47.733237 45.191406,47.754243 z"
+ style="fill:#cc0000"
+ id="path648" />
+ <use
+ transform="translate(-94.61853,1.913321)"
+ id="use4312"
+ x="0"
+ y="0"
+ width="744.09448"
+ height="1052.3622"
+ xlink:href="#path650" />
+ </g>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/warning.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/warning.png
new file mode 100644
index 0000000..3745cf6
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/warning.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/warning.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/warning.svg
new file mode 100644
index 0000000..484138d
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/warning.svg
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg2">
+ <defs
+ id="defs5" />
+ <path
+ d="M 26.553837,7.3026447 C 25.283816,5.0882437 23.199663,5.0882437 21.945919,7.3026447 L 3.9376032,38.711367 C 2.6675727,40.925778 3.7259346,42.749404 6.2822626,42.749404 L 42.217493,42.749404 C 44.77383,42.749404 45.832183,40.925778 44.545876,38.711367 L 26.553837,7.3026447 z "
+ style="fill:#2e3436;fill-opacity:1;stroke:#2e3436;stroke-width:4.7150631;stroke-miterlimit:4;stroke-dasharray:none"
+ id="use2812" />
+ <path
+ d="M 26.553837,7.3026447 C 25.283816,5.0882437 23.199663,5.0882437 21.945919,7.3026447 L 3.9376032,38.711367 C 2.6675727,40.925778 3.7259346,42.749404 6.2822626,42.749404 L 42.217493,42.749404 C 44.77383,42.749404 45.832183,40.925778 44.545876,38.711367 L 26.553837,7.3026447 z "
+ style="fill:#fde8a6;fill-opacity:1;stroke-width:4;stroke-miterlimit:4;stroke-dasharray:none"
+ id="path4309" />
+ <path
+ d="M 26.220057,12.491166 C 25.133792,10.597163 23.351196,10.597163 22.278859,12.491166 L 6.8761436,39.355379 C 5.789878,41.249382 6.6951041,42.809153 8.8815542,42.809153 L 39.617353,42.809153 C 41.803812,42.809153 42.709038,41.249382 41.608844,39.355379 L 26.220057,12.491166 z "
+ style="fill:#fac521;fill-opacity:1"
+ id="path2991" />
+ <path
+ d="M 28.470282,37.445157 C 28.470282,38.878008 27.2491,39.952646 25.392902,39.952646 L 25.36034,39.952646 C 23.520438,39.952646 22.282969,38.878008 22.282969,37.445157 C 22.282969,35.947181 23.553,34.921391 25.392902,34.921391 C 27.216538,34.921391 28.437711,35.947181 28.470282,37.445157 z M 28.144632,33.146613 L 29.21927,19.990446 L 21.517696,19.990446 L 22.592334,33.146613 L 28.144632,33.146613 z "
+ style="fill:#fef2cb;fill-opacity:1;stroke:#fef2cb;stroke-width:0.9430126;stroke-linecap:round;stroke-linejoin:round;stroke-opacity:1"
+ id="path4468" />
+ <path
+ d="M 27.089325,36.371084 C 27.089325,37.803935 25.868143,38.878574 24.011955,38.878574 L 23.979392,38.878574 C 22.139481,38.878574 20.902022,37.803935 20.902022,36.371084 C 20.902022,34.873109 22.172043,33.847319 24.011955,33.847319 C 25.835581,33.847319 27.056763,34.873109 27.089325,36.371084 z M 26.763675,32.072531 L 27.838313,18.916364 L 20.136748,18.916364 L 21.211386,32.072531 L 26.763675,32.072531 z "
+ style="fill:#2e3436"
+ id="path4470" />
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/watermark-draft.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/watermark-draft.png
new file mode 100644
index 0000000..0ead5af
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/watermark-draft.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/yellow.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/yellow.png
new file mode 100644
index 0000000..223865d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/yellow.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Live_migration_and_RHEL_compatibility.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Live_migration_and_RHEL_compatibility.html
new file mode 100644
index 0000000..6582a3c
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Live_migration_and_RHEL_compatibility.html
@@ -0,0 +1,18 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.2. Live migration and Fedora version compatibility</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-KVM_live_migration.html" title="Chapter 20. KVM live migration" /><link rel="prev" href="chap-Virtualization_Administration_Guide-KVM_live_migration.html" title="Chapter 20. KVM live migration" /><link rel="next" href="shared-storage-nfs-migration.html" title="20.3. Shared storage example: NFS for a simple migration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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_Administration_Guide-KVM_live_migration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="shared-storage-nfs-migration.html"><strong>Next</strong></a></li></ul><div class="section" id="Live_migration_and_RHEL_compatibility"><div class="titlepage"><div><div><h2 class="title">20.2. Live migration and Fedora version compatibility </h2></div></div></div><div class="para">
+ Live Migration should only be performed in cases where the guest virtual machine and the host physical machine are running the same version of Fedora. Should you perform a live migration using different versions be forwarned that the migration may fail.
+ </div><div class="para">
+ <span class="bold bold"><strong>Issues with the migration protocol</strong></span> — If backward migration ends with "unknown section error", repeating the migration process can repair the issue as it may be a transient error. If not, please report the problem.
+ </div><div class="formalpara" id="form-Virtualization-Live_migration_requirements-Configuring_network_storage"><h5 class="formalpara">Configuring network storage</h5>
+ Configure shared storage and install a guest on the shared storage.
+ </div><div class="para">
+ Alternatively, use the NFS example in <a class="xref" href="shared-storage-nfs-migration.html">Section 20.3, “Shared storage example: NFS for a simple migration”</a>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-KVM_live_migration.html"><strong>Prev</strong>Chapter 20. 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="shared-storage-nfs-migration.html"><strong>Next</strong>20.3. Shared storage example: NFS for a simple mi...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Sect_Failed_to_connect_socket.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Sect_Failed_to_connect_socket.html
new file mode 100644
index 0000000..7edce1f
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Sect_Failed_to_connect_socket.html
@@ -0,0 +1,22 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.2.2. Failed to connect socket ... : Permission denied</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="App_Hypervisor_Connection_Fail.html" title="B.2. The URI failed to connect to the hypervisor" /><link rel="prev" href="App_Hypervisor_Connection_Fail.html" title="B.2. The URI failed to connect to the hypervisor" /><link rel="next" href="Sect_Other_Connectivity_Errors.html" title="B.2.3. Other connectivity errors" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a a
ccesskey="p" href="App_Hypervisor_Connection_Fail.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="Sect_Other_Connectivity_Errors.html"><strong>Next</strong></a></li></ul><div class="section" id="Sect_Failed_to_connect_socket"><div class="titlepage"><div><div><h3 class="title">B.2.2. Failed to connect socket ... : Permission denied</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ When running a <code class="command">virsh</code> command, the following error (or similar) appears:
+ </div><pre class="screen">$ virsh -c qemu:///system list
+error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Permission denied
+error: failed to connect to the hypervisor</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ Without any hostname specified, the connection to <span class="application"><strong>QEMU</strong></span> uses UNIX sockets by default. If there is no error running this command as root, the UNIX socket options in <code class="filename">/etc/libvirt/libvirtd.conf</code> are likely misconfigured.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ To connect as a non-root user using UNIX sockets, configure the following options in <code class="filename">/etc/libvirt/libvirtd.conf</code>:
+ </div><pre class="programlisting">unix_sock_group = <code class="literal"><group></code>
+unix_sock_ro_perms = <perms>
+unix_sock_rw_perms = <perms></pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The user running <code class="command">virsh</code> must be a member of the <code class="literal">group</code> specified in the <code class="option">unix_sock_group</code> option.
+ </div></div></div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_Hypervisor_Connection_Fail.html"><strong>Prev</strong>B.2. The URI failed to connect to the 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_Other_Connectivity_Errors.html"><strong>Next</strong>B.2.3. Other connectivity errors</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Sect_Other_Connectivity_Errors.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Sect_Other_Connectivity_Errors.html
new file mode 100644
index 0000000..6e45436
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/Sect_Other_Connectivity_Errors.html
@@ -0,0 +1,14 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.2.3. Other connectivity errors</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="App_Hypervisor_Connection_Fail.html" title="B.2. The URI failed to connect to the hypervisor" /><link rel="prev" href="Sect_Failed_to_connect_socket.html" title="B.2.2. Failed to connect socket ... : Permission denied" /><link rel="next" href="App_Domain_Processor.html" title="B.3. The guest virtual machine cannot be started: internal error guest CPU is not compatible with host CPU" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Docu
mentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="Sect_Failed_to_connect_socket.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_Domain_Processor.html"><strong>Next</strong></a></li></ul><div class="section" id="Sect_Other_Connectivity_Errors"><div class="titlepage"><div><div><h3 class="title">B.2.3. Other connectivity errors</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Unable to connect to server at <code class="literal">server:port</code>: Connection refused</span></dt><dd><div class="para">
+ The daemon is not running on the server or is configured not to listen, using configuration option <code class="option">listen_tcp</code> or <code class="option">listen_tls</code>.
+ </div></dd><dt class="varlistentry"><span class="term">End of file while reading data: nc: using stream socket: Input/output error</span></dt><dd><div class="para">
+ If you specified <code class="systemitem">ssh</code> transport, the daemon is likely not running on the server. Solve this error by verifying that the daemon is running on the server.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="Sect_Failed_to_connect_socket.html"><strong>Prev</strong>B.2.2. Failed to connect socket ... : Permission ...</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="App_Domain_Processor.html"><strong>Next</strong>B.3. The guest virtual machine cannot be started:...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apas02.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apas02.html
new file mode 100644
index 0000000..9cc51c1
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apas02.html
@@ -0,0 +1,120 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.2. kvm_stat</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Troubleshooting.html" title="Appendix A. Troubleshooting" /><link rel="prev" href="chap-Virtualization_Administration_Guide-Troubleshooting.html" title="Appendix A. Troubleshooting" /><link rel="next" href="sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles.html" title="A.3. Troubleshooting with serial consoles" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentat
ion Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Troubleshooting.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles.html"><strong>Next</strong></a></li></ul><div class="section" id="idm18934480"><div class="titlepage"><div><div><h2 class="title" id="idm18934480">A.2. kvm_stat</h2></div></div></div><div class="para">
+ The <code class="command">kvm_stat</code> command is a python script which retrieves runtime statistics from the <code class="systemitem">kvm</code> kernel module. The <code class="command">kvm_stat</code> command can be used to diagnose guest behavior visible to <code class="systemitem">kvm</code>. In particular, performance related issues with guests. Currently, the reported statistics are for the entire system; the behavior of all running guests is reported.
+ </div><div class="para">
+ The <code class="command">kvm_stat</code> command requires that the <code class="systemitem">kvm</code> kernel module is loaded and <code class="command">debugfs</code> is mounted. If either of these features are not enabled, the command will output the required steps to enable <code class="command">debugfs</code> or the <code class="systemitem">kvm</code> module. For example:
+ </div><pre class="screen"># kvm_stat
+Please mount debugfs ('mount -t debugfs debugfs /sys/kernel/debug')
+and ensure the kvm modules are loaded</pre><div class="para">
+ Mount <code class="command">debugfs</code> if required:
+ </div><pre class="screen"># mount -t debugfs debugfs /sys/kernel/debug</pre><div class="formalpara"><h5 class="formalpara" id="idp4168624">kvm_stat output</h5>
+ The <code class="command">kvm_stat</code> command outputs statistics for all guests and the host. The output is updated until the command is terminated (using <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>c</strong></span> or the <span class="keycap"><strong>q</strong></span> key).
+ </div><pre class="screen"># kvm_stat
+
+kvm statistics
+
+efer_reload 94 0
+exits 4003074 31272
+fpu_reload 1313881 10796
+halt_exits 14050 259
+halt_wakeup 4496 203
+host_state_reload 1638354 24893
+hypercalls 0 0
+insn_emulation 1093850 1909
+insn_emulation_fail 0 0
+invlpg 75569 0
+io_exits 1596984 24509
+irq_exits 21013 363
+irq_injections 48039 1222
+irq_window 24656 870
+largepages 0 0
+mmio_exits 11873 0
+mmu_cache_miss 42565 8
+mmu_flooded 14752 0
+mmu_pde_zapped 58730 0
+mmu_pte_updated 6 0
+mmu_pte_write 138795 0
+mmu_recycled 0 0
+mmu_shadow_zapped 40358 0
+mmu_unsync 793 0
+nmi_injections 0 0
+nmi_window 0 0
+pf_fixed 697731 3150
+pf_guest 279349 0
+remote_tlb_flush 5 0
+request_irq 0 0
+signal_exits 1 0
+tlb_flush 200190 0
+</pre><div class="variablelist"><h6>Explanation of variables:</h6><dl class="variablelist"><dt class="varlistentry"><span class="term">efer_reload</span></dt><dd><div class="para">
+ The number of Extended Feature Enable Register (EFER) reloads.
+ </div></dd><dt class="varlistentry"><span class="term">exits</span></dt><dd><div class="para">
+ The count of all <code class="computeroutput">VMEXIT</code> calls.
+ </div></dd><dt class="varlistentry"><span class="term">fpu_reload</span></dt><dd><div class="para">
+ The number of times a <code class="computeroutput">VMENTRY</code> reloaded the FPU state. The <code class="command">fpu_reload</code> is incremented when a guest is using the Floating Point Unit (FPU).
+ </div></dd><dt class="varlistentry"><span class="term">halt_exits</span></dt><dd><div class="para">
+ Number of guest exits due to <code class="computeroutput">halt</code> calls. This type of exit is usually seen when a guest is idle.
+ </div></dd><dt class="varlistentry"><span class="term">halt_wakeup</span></dt><dd><div class="para">
+ Number of wakeups from a <code class="computeroutput">halt</code>.
+ </div></dd><dt class="varlistentry"><span class="term">host_state_reload</span></dt><dd><div class="para">
+ Count of full reloads of the host state (currently tallies MSR setup and guest MSR reads).
+ </div></dd><dt class="varlistentry"><span class="term">hypercalls</span></dt><dd><div class="para">
+ Number of guest hypervisor service calls.
+ </div></dd><dt class="varlistentry"><span class="term">insn_emulation</span></dt><dd><div class="para">
+ Number of guest instructions emulated by the host.
+ </div></dd><dt class="varlistentry"><span class="term">insn_emulation_fail</span></dt><dd><div class="para">
+ Number of failed <code class="computeroutput">insn_emulation</code> attempts.
+ </div></dd><dt class="varlistentry"><span class="term">io_exits</span></dt><dd><div class="para">
+ Number of guest exits from I/O port accesses.
+ </div></dd><dt class="varlistentry"><span class="term">irq_exits</span></dt><dd><div class="para">
+ Number of guest exits due to external interrupts.
+ </div></dd><dt class="varlistentry"><span class="term">irq_injections</span></dt><dd><div class="para">
+ Number of interrupts sent to guests.
+ </div></dd><dt class="varlistentry"><span class="term">irq_window</span></dt><dd><div class="para">
+ Number of guest exits from an outstanding interrupt window.
+ </div></dd><dt class="varlistentry"><span class="term">largepages</span></dt><dd><div class="para">
+ Number of large pages currently in use.
+ </div></dd><dt class="varlistentry"><span class="term">mmio_exits</span></dt><dd><div class="para">
+ Number of guest exits due to memory mapped I/O (MMIO) accesses.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_cache_miss</span></dt><dd><div class="para">
+ Number of KVM MMU shadow pages created.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_flooded</span></dt><dd><div class="para">
+ Detection count of excessive write operations to an MMU page. This counts detected write operations not of individual write operations.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_pde_zapped</span></dt><dd><div class="para">
+ Number of page directory entry (PDE) destruction operations.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_pte_updated</span></dt><dd><div class="para">
+ Number of page table entry (PTE) destruction operations.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_pte_write</span></dt><dd><div class="para">
+ Number of guest page table entry (PTE) write operations.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_recycled</span></dt><dd><div class="para">
+ Number of shadow pages that can be reclaimed.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_shadow_zapped</span></dt><dd><div class="para">
+ Number of invalidated shadow pages.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_unsync</span></dt><dd><div class="para">
+ Number of non-synchronized pages which are not yet unlinked.
+ </div></dd><dt class="varlistentry"><span class="term">nmi_injections</span></dt><dd><div class="para">
+ Number of Non-maskable Interrupt (NMI) injections to the guest.
+ </div></dd><dt class="varlistentry"><span class="term">nmi_window</span></dt><dd><div class="para">
+ Number of guest exits from (outstanding) Non-maskable Interrupt (NMI) windows.
+ </div></dd><dt class="varlistentry"><span class="term">pf_fixed</span></dt><dd><div class="para">
+ Number of fixed (non-paging) page table entry (PTE) maps.
+ </div></dd><dt class="varlistentry"><span class="term">pf_guest</span></dt><dd><div class="para">
+ Number of page faults injected into guests.
+ </div></dd><dt class="varlistentry"><span class="term">remote_tlb_flush</span></dt><dd><div class="para">
+ Number of remote (sibling CPU) Translation Lookaside Buffer (TLB) flush requests.
+ </div></dd><dt class="varlistentry"><span class="term">request_irq</span></dt><dd><div class="para">
+ Number of guest interrupt window request exits.
+ </div></dd><dt class="varlistentry"><span class="term">signal_exits</span></dt><dd><div class="para">
+ Number of guest exits due to pending signals from the host.
+ </div></dd><dt class="varlistentry"><span class="term">tlb_flush</span></dt><dd><div class="para">
+ Number of <code class="computeroutput">tlb_flush</code> operations performed by the hypervisor.
+ </div></dd></dl></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The output information from the <code class="command">kvm_stat</code> command is exported by the KVM hypervisor as pseudo files located in the <code class="filename">/sys/kernel/debug/kvm/</code> directory.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Troubleshooting.html"><strong>Prev</strong>Appendix A. 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-Troubleshooting_-Troubleshooting_with_serial_consoles.html"><strong>Next</strong>A.3. Troubleshooting with serial consoles</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apas04.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apas04.html
new file mode 100644
index 0000000..ff27d3b
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apas04.html
@@ -0,0 +1,14 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.4. Virtualization log files</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Troubleshooting.html" title="Appendix A. Troubleshooting" /><link rel="prev" href="sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles.html" title="A.3. Troubleshooting with serial consoles" /><link rel="next" href="sect-Virtualization-Troubleshooting-Loop_device_errors.html" title="A.5. Loop device errors" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Sit
e" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Troubleshooting-Loop_device_errors.html"><strong>Next</strong></a></li></ul><div class="section" id="idp1265392"><div class="titlepage"><div><div><h2 class="title" id="idp1265392">A.4. Virtualization log files</h2></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Each fully virtualized guest log is in the <code class="filename">/var/log/libvirt/qemu/</code> directory. Each guest log is named as <em class="replaceable"><code>GuestName</code></em>.log and will be periodically compressed once a size limit is reached.
+ </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">$HOME/.virt-manager</code> directory.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles.html"><strong>Prev</strong>A.3. 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-Troubleshooting-Loop_device_errors.html"><strong>Next</strong>A.5. Loop device errors</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apb.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apb.html
new file mode 100644
index 0000000..c06ba23
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apb.html
@@ -0,0 +1,173 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix B. Common libvirt errors and troubleshooting</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt03.html" title="Part III. Appendicies" /><link rel="prev" href="sec-known-issues-windows-xp-guests.html" title="A.10. Known Windows XP guest issues" /><link rel="next" href="App_Hypervisor_Connection_Fail.html" title="B.2. The URI failed to connect to the hypervisor" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-known-issues-windows-x
p-guests.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_Hypervisor_Connection_Fail.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="appendix" id="idm8725712" lang="en-US"><div class="titlepage"><div><div><h1 id="idm8725712" class="title">Common <span class="application"><strong>libvirt</strong></span> errors and troubleshooting</h1></div></div></div><div class="para">
+ This appendix documents common <span class="application"><strong>libvirt</strong></span>-related problems and errors along with instructions for dealing with them.
+ </div><div class="para">
+ Locate the error on the table below and follow the corresponding link under <code class="literal">Solution</code> for detailed troubleshooting information.
+ </div><div class="table"><h6>Table B.1. Common <span class="application">libvirt</span> errors</h6><div class="table-contents"><table summary="Common libvirt errors" border="1"><colgroup><col align="left" class="c1" width="33%" /><col align="left" class="c2" width="33%" /><col align="left" class="c3" width="33%" /></colgroup><thead><tr><th class="" align="left">
+ Error
+ </th><th class="" align="left">
+ Description of problem
+ </th><th class="" align="left">
+ Solution
+ </th></tr></thead><tbody><tr><td class="" align="left">
+ <code class="computeroutput"><span class="application"><strong>libvirtd</strong></span> failed to start</code>
+ </td><td class="" align="left">
+ The <span class="application"><strong>libvirt</strong></span> daemon failed to start. However, there is no information about this error in <code class="filename">/var/log/messages</code>.
+ </td><td class="" align="left">
+ <a class="xref" href="apb.html#App_Libvirt_Daemon">Section B.1, “<span class="application"><strong>libvirtd</strong></span> failed to start”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Cannot read CA certificate</code>
+ </td><td class="" align="left">
+ This is one of several errors that occur when the URI fails to connect to the hypervisor.
+ </td><td class="" align="left">
+ <a class="xref" href="App_Hypervisor_Connection_Fail.html">Section B.2, “The URI failed to connect to the hypervisor”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Failed to connect socket ... : Permission denied</code>
+ </td><td class="" align="left">
+ This is one of several errors that occur when the URI fails to connect to the hypervisor.
+ </td><td class="" align="left">
+ <a class="xref" href="App_Hypervisor_Connection_Fail.html">Section B.2, “The URI failed to connect to the hypervisor”</a>
+ </td></tr><tr><td class="" align="left">
+ Other connectivity errors
+ </td><td class="" align="left">
+ These are other errors that occur when the URI fails to connect to the hypervisor.
+ </td><td class="" align="left">
+ <a class="xref" href="App_Hypervisor_Connection_Fail.html">Section B.2, “The URI failed to connect to the hypervisor”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Internal error guest CPU is not compatible with host CPU</code>
+ </td><td class="" align="left">
+ The guest virtual machine cannot be started because the host and guest processors are different.
+ </td><td class="" align="left">
+ <a class="xref" href="App_Domain_Processor.html">Section B.3, “The guest virtual machine cannot be started: <code class="computeroutput">internal error guest CPU is not compatible with host CPU</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Failed to create domain from vm.xml error: monitor socket did not show up.: Connection refused</code>
+ </td><td class="" align="left">
+ The guest virtual machine (or domain) starting fails and returns this error or similar.
+ </td><td class="" align="left">
+ <a class="xref" href="App_Domain_Monitor_Socket.html">Section B.4, “Guest starting fails with error: <code class="computeroutput">monitor socket did not show up</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Internal error cannot find character device (null)</code>
+ </td><td class="" align="left">
+ This error can occur when attempting to connect a guest's console. It reports that there is no serial console configured for the guest virtual machine.
+ </td><td class="" align="left">
+ <a class="xref" href="App_Domain_Console.html">Section B.5, “<code class="computeroutput">Internal error cannot find character device (null)</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">No boot device</code>
+ </td><td class="" align="left">
+ After building a guest virtual machine from an existing disk image, the guest booting stalls. However, the guest can start successfully using the <code class="command">QEMU</code> command directly.
+ </td><td class="" align="left">
+ <a class="xref" href="App_Domain_Not_Booting.html">Section B.6, “Guest virtual machine booting stalls with error: <code class="computeroutput">No boot device</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">The virtual network <em class="replaceable"><code>"default"</code></em> has not been started</code>
+ </td><td class="" align="left">
+ <div class="para">
+ If the <em class="replaceable"><code>default</code></em> network (or other locally-created network) is unable to start, any virtual machine configured to use that network for its connectivity will also fail to start.
+ </div>
+ </td><td class="" align="left">
+ <a class="xref" href="App_Virt_Net_Not_Starting.html">Section B.7, “Virtual network <em class="replaceable"><code>default</code></em> has not been started”</a>
+ </td></tr><tr><td class="" align="left">
+ PXE boot (or DHCP) on guest failed
+ </td><td class="" align="left">
+ A guest virtual machine starts successfully, but is unable to acquire an IP address from DHCP, boot using the PXE protocol, or both. This is often a result of a long forward delay time set for the bridge, or when the <span class="package">iptables</span> package and kernel do not support checksum mangling rules.
+ </td><td class="" align="left">
+ <a class="xref" href="App_PXE_Guest_Boot_Fail.html">Section B.8, “PXE boot (or DHCP) on guest failed”</a>
+ </td></tr><tr><td class="" align="left">
+ Guest can reach outside network, but cannot reach host when using macvtap interface
+ </td><td class="" align="left">
+ <div class="para">
+ A guest can communicate with other guests, but cannot connect to the host machine after being configured to use a macvtap (or <em class="parameter"><code>type='direct'</code></em>) network interface.
+ </div>
+ <div class="para">
+ This is actually not an error — it is the defined behavior of macvtap.
+ </div>
+ </td><td class="" align="left">
+ <a class="xref" href="App_Macvtap.html">Section B.9, “Guest can reach outside network, but cannot reach host when using macvtap interface”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Could not add rule to fixup DHCP response checksums on network <em class="replaceable"><code>'default'</code></em></code>
+ </td><td class="" align="left">
+ This warning message is almost always harmless, but is often mistakenly seen as evidence of a problem.
+ </td><td class="" align="left">
+ <a class="xref" href="App_DHCP_Response_Checksums.html">Section B.10, “Could not add rule to fixup DHCP response checksums on network <em class="replaceable"><code>'default'</code></em>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Unable to add bridge br0 port vnet0: No such device</code>
+ </td><td class="" align="left">
+ This error message or the similar <code class="computeroutput">Failed to add tap interface to bridge <em class="replaceable"><code>'br0'</code></em>: No such device</code> reveal that the bridge device specified in the guest's (or domain's) <code class="code"><interface></code> definition does not exist.
+ </td><td class="" align="left">
+ <a class="xref" href="App_Bridge_Device.html">Section B.11, “Unable to add bridge br0 port vnet0: No such device”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Warning: could not open /dev/net/tun: no virtual network emulation qemu-kvm: -netdev tap,script=/etc/my-qemu-ifup,id=hostnet0: Device 'tap' could not be initialized</code>
+ </td><td class="" align="left">
+ The guest virtual machine does not start after configuring a <code class="code">type='ethernet'</code> (or 'generic ethernet') interface in the host system. This error or similar appears either in <code class="filename">libvirtd.log</code>, <code class="filename">/var/log/libvirt/qemu/<em class="replaceable"><code>name_of_guest</code></em>.log</code>, or in both.
+ </td><td class="" align="left">
+ <a class="xref" href="App_Generic_Ethernet.html">Section B.12, “Guest is unable to start with error: <code class="computeroutput">warning: could not open /dev/net/tun</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Unable to resolve address <em class="replaceable"><code>name_of_host</code></em> service '49155': Name or service not known</code>
+ </td><td class="" align="left">
+ <span class="application"><strong>QEMU</strong></span> guest migration fails and this error message appears with an unfamiliar hostname.
+ </td><td class="" align="left">
+ <a class="xref" href="App_Migration_Address.html">Section B.13, “Migration fails with <code class="computeroutput">Error: unable to resolve address</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Unable to allow access for disk path /var/lib/libvirt/images/qemu.img: No such file or directory</code>
+ </td><td class="" align="left">
+ A guest virtual machine cannot be migrated because <span class="application"><strong>libvirt</strong></span> cannot access the disk image(s).
+ </td><td class="" align="left">
+ <a class="xref" href="App_Migration_Disk_Image.html">Section B.14, “Migration fails with <code class="computeroutput">Unable to allow access for disk path: No such file or directory</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ No guest virtual machines are present when <span class="application"><strong>libvirtd</strong></span> is started
+ </td><td class="" align="left">
+ The <span class="application"><strong>libvirt</strong></span> daemon is successfully started, but no guest virtual machines appear to be present when running <code class="command">virsh list --all</code>.
+ </td><td class="" align="left">
+ <a class="xref" href="App_No_Guest_Machines.html">Section B.15, “No guest virtual machines are present when <span class="application"><strong>libvirtd</strong></span> is started”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor</code>
+ </td><td class="" align="left">
+ While <span class="application"><strong>libvirtd</strong></span> should listen on TCP ports for connections, the connection to the hypervisor fails.
+ </td><td class="" align="left">
+ <a class="xref" href="App_TCP_Ports.html">Section B.16, “Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor”</a>
+ </td></tr><tr><td class="" align="left">
+ Common XML errors
+ </td><td class="" align="left">
+ <span class="application"><strong>libvirt</strong></span> uses XML documents to store structured data. Several common errors occur with XML documents when they are passed to <span class="application"><strong>libvirt</strong></span> through the API. This entry provides instructions for editing guest XML definitions, and details common errors in XML syntax and configuration.
+ </td><td class="" align="left">
+ <a class="xref" href="App_XML_Errors.html">Section B.17, “Common XML errors”</a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div xml:lang="en-US" class="section" id="App_Libvirt_Daemon" lang="en-US"><div class="titlepage"><div><div><h2 class="title">B.1. <span class="application"><strong>libvirtd</strong></span> failed to start</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The <span class="application"><strong>libvirt</strong></span> daemon does not start automatically. Starting the <span class="application"><strong>libvirt</strong></span> daemon manually fails as well:
+ </div><pre class="screen"># /etc/init.d/libvirtd start
+* Caching service dependencies ... [ ok ]
+* Starting libvirtd ...
+/usr/sbin/libvirtd: error: Unable to initialize network sockets. Check /var/log/messages or run without --daemon for more info.
+* start-stop-daemon: failed to start `/usr/sbin/libvirtd' [ !! ]
+* ERROR: libvirtd failed to start</pre><div class="para">
+ Moreover, there is not <code class="literal">'more info'</code> about this error in <code class="filename">/var/log/messages</code>.
+ </div></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ Change <span class="application"><strong>libvirt's</strong></span> logging in <code class="filename">/etc/libvirt/libvirtd.conf</code> by uncommenting the line below. To uncomment the line, open the <code class="filename">/etc/libvirt/libvirtd.conf</code> file in a text editor, remove the hash (or <code class="literal">#</code>) symbol from the beginning of the following line, and save the change:
+ </div><pre class="screen">log_outputs="3:syslog:libvirtd"</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ This line is commented out by default to prevent <span class="application"><strong>libvirt</strong></span> from producing excessive log messages. After diagnosing the problem, it is recommended to comment this line again in the <code class="filename">/etc/libvirt/libvirtd.conf</code> file.
+ </div></div></div><div class="para">
+ Restart <span class="application"><strong>libvirt</strong></span> to determine if this has solved the problem.
+ </div><div class="para">
+ If <code class="filename">libvirtd</code> still does not start successfully, an error similar to the following will be shown in the <code class="filename">/var/log/messages</code> file:
+ </div><pre class="programlisting">Feb 6 17:22:09 bart libvirtd: 17576: info : libvirt version: 0.9.9
+Feb 6 17:22:09 bart libvirtd: 17576: error : virNetTLSContextCheckCertFile:92: Cannot read CA certificate '/etc/pki/CA/cacert.pem': No such file or directory
+Feb 6 17:22:09 bart /etc/init.d/libvirtd[17573]: start-stop-daemon: failed to start `/usr/sbin/libvirtd'
+Feb 6 17:22:09 bart /etc/init.d/libvirtd[17565]: ERROR: libvirtd failed to start</pre><div class="para">
+ The <span class="application"><strong>libvirtd</strong></span> man page shows that the missing <code class="filename">cacert.pem</code> file is used as TLS authority when <span class="application"><strong>libvirt</strong></span> is run in <code class="literal">Listen for TCP/IP connections</code> mode. This means the <em class="parameter"><code>--listen</code></em> parameter is being passed.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Configure the <span class="application"><strong>libvirt</strong></span> daemon's settings with one of the following methods:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Install a CA certificate.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ For more information on CA certificates and configuring system authentication, refer to the Configuring Authentication chapter in the <em class="citetitle">Fedora Deployment Guide</em>.
+ </div></div></div></li><li class="listitem"><div class="para">
+ Do not use TLS; use bare TCP instead. In <code class="filename">/etc/libvirt/libvirtd.conf</code> set <code class="option">listen_tls = 0</code> and <code class="option">listen_tcp = 1</code>. The default values are <code class="option">listen_tls = 1</code> and <code class="option">listen_tcp = 0</code>.
+ </div></li><li class="listitem"><div class="para">
+ Do not pass the <em class="parameter"><code>--listen</code></em> parameter. In <code class="filename">/etc/sysconfig/libvirtd.conf</code> change the <em class="parameter"><code>LIBVIRTD_ARGS</code></em> variable.
+ </div></li></ul></div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-known-issues-windows-xp-guests.html"><strong>Prev</strong>A.10. Known Windows XP guest issues</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="App_Hypervisor_Connection_Fail.html"><strong>Next</strong>B.2. The URI failed to connect to the hypervisor</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apbs17s02.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apbs17s02.html
new file mode 100644
index 0000000..cfbfc1d
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apbs17s02.html
@@ -0,0 +1,38 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.17.2. XML syntax errors</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="App_XML_Errors.html" title="B.17. Common XML errors" /><link rel="prev" href="App_XML_Errors.html" title="B.17. Common XML errors" /><link rel="next" href="apbs17s02s02.html" title="B.17.2.2. Unterminated attribute" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="App_XML_Errors.html"><strong>Prev</strong></a></li><li class="next"><a accesskey=
"n" href="apbs17s02s02.html"><strong>Next</strong></a></li></ul><div class="section" id="idp869504"><div class="titlepage"><div><div><h3 class="title" id="idp869504">B.17.2. XML syntax errors</h3></div></div></div><div class="para">
+ Syntax errors are caught by the XML parser. The error message contains information for identifying the problem.
+ </div><div class="para">
+ This example error message from the XML parser consists of three lines — the first line denotes the error message, and the two following lines contain the context and location of the XML code containing the error. The third line contains an indicator showing approximately where the error lies on the line above it:
+ </div><pre class="screen">error: (<em class="replaceable"><code>name_of_guest.xml</code></em>):6: StartTag: invalid element name
+<vcpu>2</vcpu><
+-----------------^</pre><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Information contained in this message:</span></dt><dd><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">(<em class="replaceable"><code>name_of_guest.xml</code></em>)</span></dt><dd><div class="para">
+ This is the file name of the document that contains the error. File names in parentheses are symbolic names to describe XML documents parsed from memory, and do not directly correspond to files on disk. File names that are not contained in parentheses are local files that reside on the target of the connection.
+ </div></dd><dt class="varlistentry"><span class="term">6</span></dt><dd><div class="para">
+ This is the line number in the XML file that contains the error.
+ </div></dd><dt class="varlistentry"><span class="term">StartTag: invalid element name </span></dt><dd><div class="para">
+ This is the error message from the <span class="application"><strong>libxml2</strong></span> parser, which describes the specific XML error.
+ </div></dd></dl></div></dd></dl></div><div class="section" id="idp13148832"><div class="titlepage"><div><div><h4 class="title" id="idp13148832">B.17.2.1. Stray <code class="literal"><</code> in the document</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The following error occurs:
+ </div><pre class="screen">error: (<em class="replaceable"><code>name_of_guest.xml</code></em>):6: StartTag: invalid element name
+<vcpu>2</vcpu><
+-----------------^</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This error message shows that the parser expects a new element name after the <code class="literal"><</code> symbol on line 6 of a guest's XML file.
+ </div><div class="para">
+ Ensure line number display is enabled in your text editor. Open the XML file, and locate the text on line 6:
+ </div><pre class="screen"><domain type='kvm'>
+ <name><em class="replaceable"><code>name_of_guest</code></em></name>
+<memory>524288</memory>
+<vcpu>2</vcpu><
+</pre><div class="para">
+ This snippet of a guest's XML file contains an extra <code class="literal"><</code> in the document:
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Remove the extra <code class="literal"><</code> or finish the new element.
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_XML_Errors.html"><strong>Prev</strong>B.17. Common XML 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="apbs17s02s02.html"><strong>Next</strong>B.17.2.2. Unterminated attribute</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apbs17s02s02.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apbs17s02s02.html
new file mode 100644
index 0000000..5352dcd
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apbs17s02s02.html
@@ -0,0 +1,21 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.17.2.2. Unterminated attribute</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apbs17s02.html" title="B.17.2. XML syntax errors" /><link rel="prev" href="apbs17s02.html" title="B.17.2. XML syntax errors" /><link rel="next" href="apbs17s02s03.html" title="B.17.2.3. Opening and ending tag mismatch" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apbs17s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n
" href="apbs17s02s03.html"><strong>Next</strong></a></li></ul><div class="section" id="idm12921872"><div class="titlepage"><div><div><h4 class="title" id="idm12921872">B.17.2.2. Unterminated attribute</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The following error occurs:
+ </div><pre class="screen">error: (<em class="replaceable"><code>name_of_guest.xml</code></em>):2: Unescaped '<' not allowed in attributes values
+<name><em class="replaceable"><code>name_of_guest</code></em></name>
+--^</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This snippet of a guest's XML file contains an unterminated element attribute value:
+ </div><pre class="screen"><domain type='kvm>
+<name><em class="replaceable"><code>name_of_guest</code></em></name></pre><div class="para">
+ In this case, <code class="literal">'kvm'</code> is missing a second quotation mark. Strings of attribute values, such as quotation marks and apostrophes, must be opened and closed, similar to XML start and end tags.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Correctly open and close all attribute value strings.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apbs17s02.html"><strong>Prev</strong>B.17.2. XML syntax 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="apbs17s02s03.html"><strong>Next</strong>B.17.2.3. Opening and ending tag mismatch</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apbs17s02s03.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apbs17s02s03.html
new file mode 100644
index 0000000..1e010a4
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apbs17s02s03.html
@@ -0,0 +1,41 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.17.2.3. Opening and ending tag mismatch</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apbs17s02.html" title="B.17.2. XML syntax errors" /><link rel="prev" href="apbs17s02s02.html" title="B.17.2.2. Unterminated attribute" /><link rel="next" href="apbs17s02s04.html" title="B.17.2.4. Typographical errors in tags" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apbs17s02s02.html"><strong>Prev</strong></a></li><li class="next"><a ac
cesskey="n" href="apbs17s02s04.html"><strong>Next</strong></a></li></ul><div class="section" id="idm15094272"><div class="titlepage"><div><div><h4 class="title" id="idm15094272">B.17.2.3. Opening and ending tag mismatch</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The following error occurs:
+ </div><pre class="screen">error: (<em class="replaceable"><code>name_of_guest.xml</code></em>):61: Opening and ending tag mismatch: clock line 16 and domain
+</domain>
+---------^</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ The error message above contains three clues to identify the offending tag:
+ </div><div class="para">
+ The message following the last colon, <code class="literal">clock line 16 and domain</code>, reveals that <code class="literal"><clock></code> contains a mismatched tag on line 16 of the document. The last hint is the pointer in the context part of the message, which identifies the second offending tag.
+ </div><div class="para">
+ Unpaired tags must be closed with <code class="literal">/></code>. The following snippet does not follow this rule and has produced the error message shown above:
+ </div><pre class="screen"><domain type='kvm'>
+ ...
+ <clock offset='utc'></pre><div class="para">
+ This error is caused by mismatched XML tags in the file. Every XML tag must have a matching start and end tag.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Other examples of mismatched XML tags</span></dt><dd><div class="para">
+ The following examples produce similar error messages and show variations of mismatched XML tags.
+ </div><div class="para">
+ This snippet contains an unended pair tag for <code class="literal"><features></code>:
+ </div><pre class="screen"><domain type='kvm'>
+ ...
+ <features>
+ <acpi/>
+ <pae/>
+ ...
+ </domain></pre><div class="para">
+ This snippet contains an end tag (<code class="literal"></name></code>) without a corresponding start tag:
+ </div><pre class="screen"><domain type='kvm'>
+ </name>
+ ...
+</domain></pre></dd></dl></div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Ensure all XML tags start and end correctly.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apbs17s02s02.html"><strong>Prev</strong>B.17.2.2. Unterminated attribute</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="apbs17s02s04.html"><strong>Next</strong>B.17.2.4. Typographical errors in tags</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apbs17s02s04.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apbs17s02s04.html
new file mode 100644
index 0000000..a9ff2f1
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apbs17s02s04.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.17.2.4. Typographical errors in tags</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apbs17s02.html" title="B.17.2. XML syntax errors" /><link rel="prev" href="apbs17s02s03.html" title="B.17.2.3. Opening and ending tag mismatch" /><link rel="next" href="apbs17s03.html" title="B.17.3. Logic and configuration errors" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apbs17s02s03.html"><strong>Prev</strong></a></li><li class="next"
><a accesskey="n" href="apbs17s03.html"><strong>Next</strong></a></li></ul><div class="section" id="idp4381024"><div class="titlepage"><div><div><h4 class="title" id="idp4381024">B.17.2.4. Typographical errors in tags</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The following error message appears:
+ </div><pre class="screen">error: (name_of_guest.xml):1: Specification mandate value for attribute ty
+<domain ty pe='kvm'>
+-----------^</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ XML errors are easily caused by a simple typographical error. This error message highlights the XML error — in this case, an extra white space within the word <code class="literal">type</code> — with a pointer.
+ </div><pre class="screen"><domain ty pe='kvm'></pre><div class="para">
+ These XML examples will not parse correctly because of typographical errors such as a missing special character, or an additional character:
+ </div><pre class="screen"><domain type 'kvm'></pre><pre class="screen"><dom#ain type='kvm'></pre></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ To identify the problematic tag, read the error message for the context of the file, and locate the error with the pointer. Correct the XML and save the changes.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apbs17s02s03.html"><strong>Prev</strong>B.17.2.3. Opening and ending tag mismatch</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="apbs17s03.html"><strong>Next</strong>B.17.3. Logic and configuration errors</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apbs17s03.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apbs17s03.html
new file mode 100644
index 0000000..faf50c6
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apbs17s03.html
@@ -0,0 +1,22 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.17.3. Logic and configuration errors</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="App_XML_Errors.html" title="B.17. Common XML errors" /><link rel="prev" href="apbs17s02s04.html" title="B.17.2.4. Typographical errors in tags" /><link rel="next" href="apbs17s03s02.html" title="B.17.3.2. Incorrect drive device type" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apbs17s02s04.html"><strong>Prev</strong></a></li><li class="nex
t"><a accesskey="n" href="apbs17s03s02.html"><strong>Next</strong></a></li></ul><div class="section" id="idm19313648"><div class="titlepage"><div><div><h3 class="title" id="idm19313648">B.17.3. Logic and configuration errors</h3></div></div></div><div class="para">
+ A well-formatted XML document can contain errors that are correct in syntax but <span class="application"><strong>libvirt</strong></span> cannot parse. Many of these errors exist, with two of the most common cases outlined below.
+ </div><div class="section" id="idp26082592"><div class="titlepage"><div><div><h4 class="title" id="idp26082592">B.17.3.1. Vanishing parts</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ Parts of the change you have made do not show up and have no effect after editing or defining the domain. The <code class="command">define</code> or <code class="command">edit</code> command works, but when dumping the XML once again, the change disappears.
+ </div></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This error likely results from a broken construct or syntax that libvirt does not parse. The <span class="application"><strong>libvirt</strong></span> tool will generally only look for constructs it knows but ignore everything else, resulting in some of the XML changes vanishing after <span class="application"><strong>libvirt</strong></span> parses the input.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Validate the XML input before passing it to the <code class="command">edit</code> or <code class="command">define</code> commands. The <span class="application"><strong>libvirt</strong></span> developers maintain a set of XML schemas bundled with <span class="application"><strong>libvirt</strong></span> which define the majority of the constructs allowed in XML documents used by <span class="application"><strong>libvirt</strong></span>.
+ </div><div class="para">
+ Validate <span class="application"><strong>libvirt</strong></span> XML files using the following command:
+ </div><pre class="screen"># virt-xml-validate libvirt.xml</pre><div class="para">
+ If this command passes, <span class="application"><strong>libvirt</strong></span> will likely understand all constructs from your XML, except if the schemas cannot detect options which are valid only for a given hypervisor. Any XML generated by <span class="application"><strong>libvirt</strong></span> as a result of a <code class="command">virsh dump</code> command, for example, should validate without error.
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apbs17s02s04.html"><strong>Prev</strong>B.17.2.4. Typographical errors in tags</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="apbs17s03s02.html"><strong>Next</strong>B.17.3.2. Incorrect drive device type</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apbs17s03s02.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apbs17s03s02.html
new file mode 100644
index 0000000..f54d7cb
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apbs17s03s02.html
@@ -0,0 +1,30 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.17.3.2. Incorrect drive device type</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apbs17s03.html" title="B.17.3. Logic and configuration errors" /><link rel="prev" href="apbs17s03.html" title="B.17.3. Logic and configuration errors" /><link rel="next" href="netkvm-parameters.html" title="Appendix C. NetKVM Driver Parameters" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apbs17s03.html"><strong>Prev</strong></a></li><li c
lass="next"><a accesskey="n" href="netkvm-parameters.html"><strong>Next</strong></a></li></ul><div class="section" id="idm1773440"><div class="titlepage"><div><div><h4 class="title" id="idm1773440">B.17.3.2. Incorrect drive device type</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The definition of the source image for the CD-ROM virtual drive is not present, despite being added:
+ </div><pre class="screen"># virsh dumpxml domain
+<domain type='kvm'>
+ ...
+ <disk type='block' device='cdrom'>
+ <driver name='qemu' type='raw'/>
+ <target dev='hdc' bus='ide'/>
+ <readonly/>
+ </disk>
+ ...
+</domain></pre></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Correct the XML by adding the missing <code class="code"><source></code> parameter as follows:
+ </div><pre class="screen"><disk type='block' device='cdrom'>
+ <driver name='qemu' type='raw'/>
+ <source file='/path/to/image.iso'/>
+ <target dev='hdc' bus='ide'/>
+ <readonly/>
+</disk></pre><div class="para">
+ A <code class="code">type='block'</code> disk device expects that the source is a physical device. To use the disk with an image file, use <code class="code">type='file'</code> instead.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apbs17s03.html"><strong>Prev</strong>B.17.3. Logic and configuration 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="netkvm-parameters.html"><strong>Next</strong>Appendix C. NetKVM Driver Parameters</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds02.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds02.html
new file mode 100644
index 0000000..79564de
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds02.html
@@ -0,0 +1,62 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>D.2. Basic options</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html" title="Appendix D. qemu-kvm Whitelist" /><link rel="prev" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html" title="Appendix D. qemu-kvm Whitelist" /><link rel="next" href="apds03.html" title="D.3. Disk options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" hr
ef="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apds03.html"><strong>Next</strong></a></li></ul><div class="section" id="idp844448"><div class="titlepage"><div><div><h2 class="title" id="idp844448">D.2. Basic options</h2></div></div></div><h4 id="idp26060928">Emulated machine</h4><div class="para">
+ <span class="application"><strong>-M</strong></span> <machine-type>
+ </div><h4 id="idm20942144">Processor type</h4><div class="para">
+ <span class="application"><strong>-cpu</strong></span> <model>[,<FEATURE>][...]
+ </div><div class="para">
+ We support exposing additional features and placing restrictions. Supported models are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>Opteron_G5</strong></span> - AMD Opteron 63xx class CPU
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Opteron_G4</strong></span> - AMD Opteron 62xx class CPU
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Opteron_G3</strong></span> - AMD Opteron 23xx (AMD Opteron Gen 3)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Opteron_G2</strong></span> - AMD Opteron 22xx (AMD Opteron Gen 2)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Opteron_G1</strong></span> - AMD Opteron 240 (AMD Opteron Gen 1)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Westmere</strong></span> - Westmere E56xx/L56xx/X56xx (Nehalem-C)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Haswell</strong></span> - Intel Core Processor (Haswell)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>SandyBridge</strong></span> - Intel Xeon E312xx (Sandy Bridge)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Nehalem</strong></span> - Intel Core i7 9xx (Nehalem Class Core i7)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Penryn</strong></span> - Intel Core 2 Duo P9xxx (Penryn Class Core 2)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Conroe</strong></span> - Intel Celeron_4x0 (Conroe/Merom Class Core 2)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>cpu64-rhel5</strong></span> - Red Hat Enterprise Linux 5 supported QEMU Virtual CPU version
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>cpu64-rhel6</strong></span> - Red Hat Enterprise Linux 6 supported QEMU Virtual CPU version
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>default</strong></span> - special option use default option from above.
+ </div></li></ul></div><h4 id="idm8765808">Processor Topology</h4><div class="para">
+ <span class="application"><strong>-smp</strong></span> <n>[,cores=<ncores>][,threads=<nthreads>][,sockets=<nsocks>][,maxcpus=<maxcpus>]
+ </div><div class="para">
+ Hypervisor and guest operating system limits on processor topology apply.
+ </div><h4 id="idp22581312">NUMA system</h4><div class="para">
+ <span class="application"><strong>-numa</strong></span> <nodes>[,mem=<size>][,cpus=<cpu[-cpu>]][,nodeid=<node>]
+ </div><div class="para">
+ Hypervisor and guest operating system limits on processor topology apply.
+ </div><h4 id="idp22583360">Memory size</h4><div class="para">
+ <span class="application"><strong>-m</strong></span> <megs>
+ </div><div class="para">
+ Supported values are limited by guest minimal and maximal values and hypervisor limits.
+ </div><h4 id="idp26825040">Keyboard layout</h4><div class="para">
+ <span class="application"><strong>-k</strong></span> <language>
+ </div><h4 id="idp26826672">Guest name</h4><div class="para">
+ <span class="application"><strong>-name</strong></span> <name>
+ </div><h4 id="idm15195840">Guest UUID</h4><div class="para">
+ <span class="application"><strong>-uuid</strong></span> <uuid>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html"><strong>Prev</strong>Appendix D. qemu-kvm Whitelist</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="apds03.html"><strong>Next</strong>D.3. Disk options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds03.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds03.html
new file mode 100644
index 0000000..2dca16d
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds03.html
@@ -0,0 +1,72 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>D.3. Disk options</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html" title="Appendix D. qemu-kvm Whitelist" /><link rel="prev" href="apds02.html" title="D.2. Basic options" /><link rel="next" href="apds04.html" title="D.4. Display options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apds02.html"><strong>Prev</strong></a></li><li class="next"
><a accesskey="n" href="apds04.html"><strong>Next</strong></a></li></ul><div class="section" id="idm15194048"><div class="titlepage"><div><div><h2 class="title" id="idm15194048">D.3. Disk options</h2></div></div></div><h4 id="idm15193248">Generic drive</h4><div class="para">
+ <span class="application"><strong>-drive</strong></span> <option>[,<option>[,<option>[,...]]]
+ </div><div class="para">
+ Supported with the following options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>readonly</strong></span>[on|off]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>werror</strong></span>[enospc|report|stop|ignore]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>rerror</strong></span>[report|stop|ignore]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>id</strong></span>=<id>
+ </div><div class="para">
+ Id of the drive has the following limitaton for if=none:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ IDE disk has to have <id> in following format: drive-ide0-<BUS>-<UNIT>
+ </div><div class="para">
+ Example of correct format:
+ </div><div class="para">
+ -drive if=none,id=drive-ide0-<BUS>-<UNIT>,... -device ide-drive,drive=drive-ide0-<BUS>-<UNIT>,bus=ide.<BUS>,unit=<UNIT>
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>file</strong></span>=<file>
+ </div><div class="para">
+ Value of <file> is parsed with the following rules:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Passing floppy device as <file> is not supported.
+ </div></li><li class="listitem"><div class="para">
+ Passing cd-rom device as <file> is supported only with cdrom media type (media=cdrom) and only as IDE drive (either if=ide or if=none + -device ide-drive).
+ </div></li><li class="listitem"><div class="para">
+ If <file> is neither block nor character device, it must not contain ':'.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>if</strong></span>=<interface>
+ </div><div class="para">
+ The following interfaces are supported: none, ide, virtio, floppy.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>index</strong></span>=<index>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>media</strong></span>=<media>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>cache</strong></span>=<cache>
+ </div><div class="para">
+ Supported values: none, writeback or writethrough.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>copy-on-read</strong></span>=[on|off]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>snapshot</strong></span>=[yes|no]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>serial</strong></span>=<serial>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>aio</strong></span>=<aio>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>format</strong></span>=<format>
+ </div><div class="para">
+ This option is not required and can be omitted. However, this is not recommended for raw images because it represents security risk. Supported formats are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>qcow2</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>raw</strong></span>
+ </div></li></ul></div></li></ul></div><h4 id="idp13369968">Boot option</h4><div class="para">
+ <span class="application"><strong>-boot</strong></span> [order=<drives>][,menu=[on|off]]
+ </div><h4 id="idp6713680">Snapshot mode</h4><div class="para">
+ <span class="application"><strong>-snapshot</strong></span>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apds02.html"><strong>Prev</strong>D.2. Basic options</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="apds04.html"><strong>Next</strong>D.4. Display options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds04.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds04.html
new file mode 100644
index 0000000..9294c34
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds04.html
@@ -0,0 +1,106 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>D.4. Display options</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html" title="Appendix D. qemu-kvm Whitelist" /><link rel="prev" href="apds03.html" title="D.3. Disk options" /><link rel="next" href="apds05.html" title="D.5. Network options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apds03.html"><strong>Prev</strong></a></li><li class="next">
<a accesskey="n" href="apds05.html"><strong>Next</strong></a></li></ul><div class="section" id="idp6715472"><div class="titlepage"><div><div><h2 class="title" id="idp6715472">D.4. Display options</h2></div></div></div><h4 id="idp6716272">Disable graphics</h4><div class="para">
+ <span class="application"><strong>-nographic</strong></span>
+ </div><h4 id="idm9342112">VGA card emulation</h4><div class="para">
+ <span class="application"><strong>-vga</strong></span> <type>
+ </div><div class="para">
+ Supported types:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>cirrus</strong></span> - Cirrus Logic GD5446 Video card.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>std</strong></span> - Standard VGA card with Bochs VBE extensions.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>qxl</strong></span> - Spice paravirtual card.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>none</strong></span> - Disable VGA card.
+ </div></li></ul></div><h4 id="idp15744400">VNC display</h4><div class="para">
+ <span class="application"><strong>-vnc</strong></span> <display>[,<option>[,<option>[,...]]]
+ </div><div class="para">
+ Supported display value:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ [<host>]:<port>
+ </div></li><li class="listitem"><div class="para">
+ unix:<path>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>share</strong></span>[allow-exclusive|force-shared|ignore]
+ </div></li><li class="listitem"><div class="para">
+ none - Supported with no other options specified.
+ </div></li></ul></div><div class="para">
+ Supported options are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>to</strong></span>=<port>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>reverse</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>password</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>tls</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>x509</strong></span>=</path/to/certificate/dir> - Supported when <span class="application"><strong>tls</strong></span> specified.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>x509verify</strong></span>=</path/to/certificate/dir> - Supported when <span class="application"><strong>tls</strong></span> specified.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>sasl</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>acl</strong></span>
+ </div></li></ul></div><h4 id="idm19986800">Spice desktop</h4><div class="para">
+ <span class="application"><strong>-spice</strong></span> option[,option[,...]]
+ </div><div class="para">
+ Supported options are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>port</strong></span>=<number>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>addr</strong></span>=<addr>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>ipv4</strong></span>
+ </div><div class="para">
+ <span class="application"><strong>ipv6</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>password</strong></span>=<secret>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>disable-ticketing</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>disable-copy-paste</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>tls-port</strong></span>=<number>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>x509-dir</strong></span>=</path/to/certificate/dir>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>x509-key-file</strong></span>=<file>
+ </div><div class="para">
+ <span class="application"><strong>x509-key-password</strong></span>=<file>
+ </div><div class="para">
+ <span class="application"><strong>x509-cert-file</strong></span>=<file>
+ </div><div class="para">
+ <span class="application"><strong>x509-cacert-file</strong></span>=<file>
+ </div><div class="para">
+ <span class="application"><strong>x509-dh-key-file</strong></span>=<file>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>tls-cipher</strong></span>=<list>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>tls-channel</strong></span>[main|display|cursor|inputs|record|playback]
+ </div><div class="para">
+ <span class="application"><strong>plaintext-channel</strong></span>[main|display|cursor|inputs|record|playback]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>image-compression</strong></span>=<compress>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>jpeg-wan-compression</strong></span>=<value>
+ </div><div class="para">
+ <span class="application"><strong>zlib-glz-wan-compression</strong></span>=<value>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>streaming-video</strong></span>=[off|all|filter]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>agent-mouse</strong></span>=[on|off]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>playback-compression</strong></span>=[on|off]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>seamless-migratio</strong></span>=[on|off]
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apds03.html"><strong>Prev</strong>D.3. Disk options</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="apds05.html"><strong>Next</strong>D.5. Network options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds05.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds05.html
new file mode 100644
index 0000000..7615a3d
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds05.html
@@ -0,0 +1,32 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>D.5. Network options</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html" title="Appendix D. qemu-kvm Whitelist" /><link rel="prev" href="apds04.html" title="D.4. Display options" /><link rel="next" href="apds06.html" title="D.6. Device options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apds04.html"><strong>Prev</strong></a></li><li class="next
"><a accesskey="n" href="apds06.html"><strong>Next</strong></a></li></ul><div class="section" id="idp5361136"><div class="titlepage"><div><div><h2 class="title" id="idp5361136">D.5. Network options</h2></div></div></div><h4 id="idp5361936">TAP network</h4><div class="para">
+ <span class="application"><strong>-netdev tap</strong></span>,id=<id>][,<options>...]
+ </div><div class="para">
+ The following options are supported (all use name=value format):
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ ifname
+ </div></li><li class="listitem"><div class="para">
+ fd
+ </div></li><li class="listitem"><div class="para">
+ script
+ </div></li><li class="listitem"><div class="para">
+ downscript
+ </div></li><li class="listitem"><div class="para">
+ sndbuf
+ </div></li><li class="listitem"><div class="para">
+ vnet_hdr
+ </div></li><li class="listitem"><div class="para">
+ vhost
+ </div></li><li class="listitem"><div class="para">
+ vhostfd
+ </div></li><li class="listitem"><div class="para">
+ vhostforce
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apds04.html"><strong>Prev</strong>D.4. Display options</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="apds06.html"><strong>Next</strong>D.6. Device options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds06.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds06.html
new file mode 100644
index 0000000..8905ec8
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds06.html
@@ -0,0 +1,458 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>D.6. Device options</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html" title="Appendix D. qemu-kvm Whitelist" /><link rel="prev" href="apds05.html" title="D.5. Network options" /><link rel="next" href="apds07.html" title="D.7. Linux/Multiboot boot" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apds05.html"><strong>Prev</strong></a></li><li class
="next"><a accesskey="n" href="apds07.html"><strong>Next</strong></a></li></ul><div class="section" id="idm8833744"><div class="titlepage"><div><div><h2 class="title" id="idm8833744">D.6. Device options</h2></div></div></div><h4 id="idp564752">General device</h4><div class="para">
+ <span class="application"><strong>-device</strong></span> <driver>[,<prop>[=<value>][,...]]
+ </div><div class="para">
+ All drivers support following properties
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ id
+ </div></li><li class="listitem"><div class="para">
+ bus
+ </div></li></ul></div><div class="para">
+ Following drivers are supported (with available properties):
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>pci-assign</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ host
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ configfd
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li><li class="listitem"><div class="para">
+ rombar
+ </div></li><li class="listitem"><div class="para">
+ romfile
+ </div></li><li class="listitem"><div class="para">
+ multifunction
+ </div></li></ul></div><div class="para">
+ If the device has multiple functions, all of them need to be assigned to the same guest.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>rtl8139</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ mac
+ </div></li><li class="listitem"><div class="para">
+ netdev
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>e1000</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ mac
+ </div></li><li class="listitem"><div class="para">
+ netdev
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>virtio-net-pci</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ ioeventfd
+ </div></li><li class="listitem"><div class="para">
+ vectors
+ </div></li><li class="listitem"><div class="para">
+ indirect
+ </div></li><li class="listitem"><div class="para">
+ event_idx
+ </div></li><li class="listitem"><div class="para">
+ csum
+ </div></li><li class="listitem"><div class="para">
+ guest_csum
+ </div></li><li class="listitem"><div class="para">
+ gso
+ </div></li><li class="listitem"><div class="para">
+ guest_tso4
+ </div></li><li class="listitem"><div class="para">
+ guest_tso6
+ </div></li><li class="listitem"><div class="para">
+ guest_ecn
+ </div></li><li class="listitem"><div class="para">
+ guest_ufo
+ </div></li><li class="listitem"><div class="para">
+ host_tso4
+ </div></li><li class="listitem"><div class="para">
+ host_tso6
+ </div></li><li class="listitem"><div class="para">
+ host_ecn
+ </div></li><li class="listitem"><div class="para">
+ host_ufo
+ </div></li><li class="listitem"><div class="para">
+ mrg_rxbuf
+ </div></li><li class="listitem"><div class="para">
+ status
+ </div></li><li class="listitem"><div class="para">
+ ctrl_vq
+ </div></li><li class="listitem"><div class="para">
+ ctrl_rx
+ </div></li><li class="listitem"><div class="para">
+ ctrl_vlan
+ </div></li><li class="listitem"><div class="para">
+ ctrl_rx_extra
+ </div></li><li class="listitem"><div class="para">
+ mac
+ </div></li><li class="listitem"><div class="para">
+ netdev
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ x-txtimer
+ </div></li><li class="listitem"><div class="para">
+ x-txburst
+ </div></li><li class="listitem"><div class="para">
+ tx
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>qxl</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ ram_size
+ </div></li><li class="listitem"><div class="para">
+ vram_size
+ </div></li><li class="listitem"><div class="para">
+ revision
+ </div></li><li class="listitem"><div class="para">
+ cmdlog
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>ide-drive</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ unit
+ </div></li><li class="listitem"><div class="para">
+ drive
+ </div></li><li class="listitem"><div class="para">
+ physical_block_size
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ ver
+ </div></li><li class="listitem"><div class="para">
+ wwn
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>virtio-blk-pci</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ class
+ </div></li><li class="listitem"><div class="para">
+ drive
+ </div></li><li class="listitem"><div class="para">
+ logical_block_size
+ </div></li><li class="listitem"><div class="para">
+ physical_block_size
+ </div></li><li class="listitem"><div class="para">
+ min_io_size
+ </div></li><li class="listitem"><div class="para">
+ opt_io_size
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ ioeventfd
+ </div></li><li class="listitem"><div class="para">
+ vectors
+ </div></li><li class="listitem"><div class="para">
+ indirect_desc
+ </div></li><li class="listitem"><div class="para">
+ event_idx
+ </div></li><li class="listitem"><div class="para">
+ scsi
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>isa-debugcon</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>isa-serial</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ index
+ </div></li><li class="listitem"><div class="para">
+ iobase
+ </div></li><li class="listitem"><div class="para">
+ irq
+ </div></li><li class="listitem"><div class="para">
+ chardev
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>virtserialport</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ nr
+ </div></li><li class="listitem"><div class="para">
+ chardev
+ </div></li><li class="listitem"><div class="para">
+ name
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>virtconsole</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ nr
+ </div></li><li class="listitem"><div class="para">
+ chardev
+ </div></li><li class="listitem"><div class="para">
+ name
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>virtio-serial-pci</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ vectors
+ </div></li><li class="listitem"><div class="para">
+ class
+ </div></li><li class="listitem"><div class="para">
+ indirect_desc
+ </div></li><li class="listitem"><div class="para">
+ event_idx
+ </div></li><li class="listitem"><div class="para">
+ max_ports
+ </div></li><li class="listitem"><div class="para">
+ flow_control
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>ES1370</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>AC97</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>intel-hda</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>hda-duplex</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ cad
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>hda-micro</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ cad
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>hda-output</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ cad
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>i6300esb</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>ib700</strong></span> - no properties
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>sga</strong></span> - no properties
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>virtio-balloon-pci</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ indirect_desc
+ </div></li><li class="listitem"><div class="para">
+ event_idx
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-tablet</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ migrate
+ </div></li><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-kbd</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ migrate
+ </div></li><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-mouse</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ migrate
+ </div></li><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-ccid</strong></span> - supported since 6.2
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ port
+ </div></li><li class="listitem"><div class="para">
+ slot
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-host</strong></span> - tech preview since 6.2
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ hostbus
+ </div></li><li class="listitem"><div class="para">
+ hostaddr
+ </div></li><li class="listitem"><div class="para">
+ hostport
+ </div></li><li class="listitem"><div class="para">
+ vendorid
+ </div></li><li class="listitem"><div class="para">
+ productid
+ </div></li><li class="listitem"><div class="para">
+ isobufs
+ </div></li><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-hub</strong></span> - supported since 6.2
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-ehci</strong></span> - tech preview since 6.2
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ freq
+ </div></li><li class="listitem"><div class="para">
+ maxframes
+ </div></li><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-storage</strong></span> - tech preview since 6.2
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ drive
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ serial
+ </div></li><li class="listitem"><div class="para">
+ removable
+ </div></li><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-redir</strong></span> - tech preview since 6.3
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ chardev
+ </div></li><li class="listitem"><div class="para">
+ filter
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>scsi-cd</strong></span> - tech preview for 6.3
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ drive
+ </div></li><li class="listitem"><div class="para">
+ logical_block_size
+ </div></li><li class="listitem"><div class="para">
+ physical_block_size
+ </div></li><li class="listitem"><div class="para">
+ min_io_size
+ </div></li><li class="listitem"><div class="para">
+ opt_io_size
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ ver
+ </div></li><li class="listitem"><div class="para">
+ serial
+ </div></li><li class="listitem"><div class="para">
+ scsi-id
+ </div></li><li class="listitem"><div class="para">
+ lun
+ </div></li><li class="listitem"><div class="para">
+ channel-scsi
+ </div></li><li class="listitem"><div class="para">
+ wwn
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>scsi-hd</strong></span> -tech preview for 6.3
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ drive
+ </div></li><li class="listitem"><div class="para">
+ logical_block_size
+ </div></li><li class="listitem"><div class="para">
+ physical_block_size
+ </div></li><li class="listitem"><div class="para">
+ min_io_size
+ </div></li><li class="listitem"><div class="para">
+ opt_io_size
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ ver
+ </div></li><li class="listitem"><div class="para">
+ serial
+ </div></li><li class="listitem"><div class="para">
+ scsi-id
+ </div></li><li class="listitem"><div class="para">
+ lun
+ </div></li><li class="listitem"><div class="para">
+ channel-scsi
+ </div></li><li class="listitem"><div class="para">
+ wwn
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>scsi-block</strong></span> -tech preview for 6.3
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ drive
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>scsi-disk</strong></span> -tech preview for 6.3
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ drive=drive
+ </div></li><li class="listitem"><div class="para">
+ logical_block_size
+ </div></li><li class="listitem"><div class="para">
+ physical_block_size
+ </div></li><li class="listitem"><div class="para">
+ min_io_size
+ </div></li><li class="listitem"><div class="para">
+ opt_io_size
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ ver
+ </div></li><li class="listitem"><div class="para">
+ serial
+ </div></li><li class="listitem"><div class="para">
+ scsi-id
+ </div></li><li class="listitem"><div class="para">
+ lun
+ </div></li><li class="listitem"><div class="para">
+ channel-scsi
+ </div></li><li class="listitem"><div class="para">
+ wwn
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>piix3-usb-uhci</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>piix4-usb-uhci</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>ccid-card-passthru</strong></span>
+ </div></li></ul></div><h4 id="idp18101184">Global device setting</h4><div class="para">
+ <span class="application"><strong>-global</strong></span> <device>.<property>=<value>
+ </div><div class="para">
+ Supported devices and properties as in "General device" section with these additional devices:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>isa-fdc</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ driveA
+ </div></li><li class="listitem"><div class="para">
+ driveB
+ </div></li><li class="listitem"><div class="para">
+ bootindexA
+ </div></li><li class="listitem"><div class="para">
+ bootindexB
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>qxl-vga</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ ram_size
+ </div></li><li class="listitem"><div class="para">
+ vram_size
+ </div></li><li class="listitem"><div class="para">
+ revision
+ </div></li><li class="listitem"><div class="para">
+ cmdlog
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li></ul></div><h4 id="idp2458880">Character device</h4><div class="para">
+ <span class="application"><strong>-chardev</strong></span> backend,id=<id>[,<options>]
+ </div><div class="para">
+ Supported backends are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>null</strong></span>,id=<id> - null device
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>socket</strong></span>,id=<id>,port=<port>[,host=<host>][,to=<to>][,ipv4][,ipv6][,nodelay][,server][,nowait][,telnet] - tcp socket
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>socket</strong></span>,id=<id>,path=<path>[,server][,nowait][,telnet] - unix socket
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>file</strong></span>,id=<id>,path=<path> - trafit to file.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>stdio</strong></span>,id=<id> - standard i/o
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>spicevmc</strong></span>,id=<id>,name=<name> - spice channel
+ </div></li></ul></div><h4 id="idp8881600">Enable USB</h4><div class="para">
+ <span class="application"><strong>-usb</strong></span>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apds05.html"><strong>Prev</strong>D.5. Network options</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="apds07.html"><strong>Next</strong>D.7. Linux/Multiboot boot </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds07.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds07.html
new file mode 100644
index 0000000..0a42297
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds07.html
@@ -0,0 +1,18 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>D.7. Linux/Multiboot boot</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html" title="Appendix D. qemu-kvm Whitelist" /><link rel="prev" href="apds06.html" title="D.6. Device options" /><link rel="next" href="apds08.html" title="D.8. Expert options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apds06.html"><strong>Prev</strong></a></li><li class="next"
><a accesskey="n" href="apds08.html"><strong>Next</strong></a></li></ul><div class="section" id="idp8883392"><div class="titlepage"><div><div><h2 class="title" id="idp8883392">D.7. Linux/Multiboot boot </h2></div></div></div><h4 id="idp8884192">Kernel file</h4><div class="para">
+ <span class="application"><strong>-kernel</strong></span> <bzImage>
+ </div><div class="para">
+ Note: multiboot images are not supported
+ </div><h4 id="idm3017136">Ram disk</h4><div class="para">
+ <span class="application"><strong>-initrd</strong></span> <file>
+ </div><h4 id="idm3015072">Command line parameter</h4><div class="para">
+ <span class="application"><strong>-append</strong></span> <cmdline>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apds06.html"><strong>Prev</strong>D.6. Device options</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="apds08.html"><strong>Next</strong>D.8. Expert options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds08.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds08.html
new file mode 100644
index 0000000..f3e5a10
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds08.html
@@ -0,0 +1,60 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>D.8. Expert options</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html" title="Appendix D. qemu-kvm Whitelist" /><link rel="prev" href="apds07.html" title="D.7. Linux/Multiboot boot" /><link rel="next" href="apds09.html" title="D.9. Help and information options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apds07.html"><strong>Prev</strong></a><
/li><li class="next"><a accesskey="n" href="apds09.html"><strong>Next</strong></a></li></ul><div class="section" id="idp16712896"><div class="titlepage"><div><div><h2 class="title" id="idp16712896">D.8. Expert options</h2></div></div></div><h4 id="idp16713696">KVM virtualization</h4><div class="para">
+ <span class="application"><strong>-enable-kvm</strong></span>
+ </div><div class="para">
+ Qemu-kvm supports only KVM virtualization and it is used by default if available. If -enable-kvm is used and KVM is not available, qemu-kvm fails. However, if -enable-kvm is not used and KVM is not available, qemu-kvm runs in TCG mode, which is not supported.
+ </div><h4 id="idp16716064">Disable kernel mode PIT reinjection</h4><div class="para">
+ <span class="application"><strong>-no-kvm-pit-reinjection</strong></span>
+ </div><h4 id="idp16717664">No shutdown</h4><div class="para">
+ <span class="application"><strong>-no-shutdown</strong></span>
+ </div><h4 id="idp11086672">No reboot</h4><div class="para">
+ <span class="application"><strong>-no-reboot</strong></span>
+ </div><h4 id="idp11088304">Serial port, monitor, QMP</h4><div class="para">
+ <span class="application"><strong>-serial</strong></span> <dev>
+ </div><div class="para">
+ <span class="application"><strong>-monitor</strong></span> <dev>
+ </div><div class="para">
+ <span class="application"><strong>-qmp</strong></span> <dev>
+ </div><div class="para">
+ Supported devices are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>stdio</strong></span> - standard input/output
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>null</strong></span> - null device
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>file</strong></span>:<filename> - output to file.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>tcp</strong></span>:[<host>]:<port>[,server][,nowait][,nodelay] - TCP Net console.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>unix</strong></span>:<path>[,server][,nowait] - Unix domain socket.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>mon</strong></span>:<dev_string> - Any device above, used to multiplex monitor too.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>none</strong></span> - disable, valid only for -serial.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>chardev</strong></span>:<id> - character device created with -chardev.
+ </div></li></ul></div><h4 id="idp3095040">Monitor redirect</h4><div class="para">
+ <span class="application"><strong>-mon</strong></span> <chardev_id>[,mode=[readline|control]][,default=[on|off]]
+ </div><h4 id="idp3096640">Manual CPU start</h4><div class="para">
+ <span class="application"><strong>-S</strong></span>
+ </div><h4 id="idp4947504">RTC</h4><div class="para">
+ <span class="application"><strong>-rtc</strong></span> [base=utc|localtime|date][,clock=host|vm][,driftfix=none|slew]
+ </div><h4 id="idp4949104">Watchdog</h4><div class="para">
+ <span class="application"><strong>-watchdog</strong></span> model
+ </div><h4 id="idp4950736">Watchdog reaction</h4><div class="para">
+ <span class="application"><strong>-watchdog-action</strong></span> <action>
+ </div><h4 id="idm1778880">Guest memory backing</h4><div class="para">
+ <span class="application"><strong>-mem-prealloc</strong></span> <span class="application"><strong>-mem-path</strong></span> /dev/hugepages
+ </div><h4 id="idm1776768">SMBIOS entry</h4><div class="para">
+ <span class="application"><strong>-smbios</strong></span> type=0[,vendor=<str>][,<version=str>][,date=<str>][,release=%d.%d]
+ </div><div class="para">
+ <span class="application"><strong>-smbios</strong></span> type=1[,manufacturer=<str>][,product=<str>][,version=<str>][,serial=<str>][,uuid=<uuid>][,sku=<str>][,family=<str>]
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apds07.html"><strong>Prev</strong>D.7. Linux/Multiboot 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="apds09.html"><strong>Next</strong>D.9. Help and information options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds09.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds09.html
new file mode 100644
index 0000000..64fa4af
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds09.html
@@ -0,0 +1,18 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>D.9. Help and information options</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html" title="Appendix D. qemu-kvm Whitelist" /><link rel="prev" href="apds08.html" title="D.8. Expert options" /><link rel="next" href="apds10.html" title="D.10. Miscellaneous options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apds08.html"><strong>Prev</strong></a></li><li clas
s="next"><a accesskey="n" href="apds10.html"><strong>Next</strong></a></li></ul><div class="section" id="idm20874544"><div class="titlepage"><div><div><h2 class="title" id="idm20874544">D.9. Help and information options</h2></div></div></div><h4 id="idm20873776">Help</h4><div class="para">
+ <span class="application"><strong>-h</strong></span>
+ </div><div class="para">
+ <span class="application"><strong>-help</strong></span>
+ </div><h4 id="idm20871184">Version</h4><div class="para">
+ <span class="application"><strong>-version</strong></span>
+ </div><h4 id="idm5474192">Audio help</h4><div class="para">
+ <span class="application"><strong>-audio-help</strong></span>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apds08.html"><strong>Prev</strong>D.8. Expert options</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="apds10.html"><strong>Next</strong>D.10. Miscellaneous options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds10.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds10.html
new file mode 100644
index 0000000..3d017e6
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apds10.html
@@ -0,0 +1,24 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>D.10. Miscellaneous options</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html" title="Appendix D. qemu-kvm Whitelist" /><link rel="prev" href="apds09.html" title="D.9. Help and information options" /><link rel="next" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li clas
s="previous"><a accesskey="p" href="apds09.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html"><strong>Next</strong></a></li></ul><div class="section" id="idm5472400"><div class="titlepage"><div><div><h2 class="title" id="idm5472400">D.10. Miscellaneous options</h2></div></div></div><h4 id="idm5471600">Migration</h4><div class="para">
+ <span class="application"><strong>-incoming</strong></span>
+ </div><h4 id="idm5469968">No default configuration</h4><div class="para">
+ <span class="application"><strong>-nodefconfig</strong></span>
+ </div><div class="para">
+ <span class="application"><strong>-nodefaults</strong></span>
+ </div><div class="para">
+ Running without -nodefaults is not supported
+ </div><h4 id="idm12682096">Device configuration file</h4><div class="para">
+ <span class="application"><strong>-readconfig</strong></span> <file>
+ </div><div class="para">
+ <span class="application"><strong>-writeconfig</strong></span> <file>
+ </div><h4 id="idm12679536">Loaded saved state</h4><div class="para">
+ <span class="application"><strong>-loadvm</strong></span> <file>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apds09.html"><strong>Prev</strong>D.9. Help and information options</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_Administration_Guide-Managing_guests_with_virsh.html"><strong>Next</strong>Appendix E. Managing guests with virsh</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes05.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes05.html
new file mode 100644
index 0000000..3b77e4b
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes05.html
@@ -0,0 +1,26 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.5. Suspending, resuming, saving and restoring a guest</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="prev" href="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html" title="E.4. Creating a virtual machine XML dump (configuration file)" /><link rel="next" href="apes06.html" title="E.6. Shutting down, rebooting and force-shutdown of a guest" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Com
mon_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apes06.html"><strong>Next</strong></a></li></ul><div class="section" id="idp19001168"><div class="titlepage"><div><div><h2 class="title" id="idp19001168">E.5. Suspending, resuming, saving and restoring a guest</h2></div></div></div><div class="formalpara"><h5 class="formalpara" id="idp19001936">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="apes05.html#form-Virtualization-Managing_guests_with_virsh-Resuming_a_guest">Resuming a guest</a>) option.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Resuming_a_guest"><h5 class="formalpara">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" id="form-Virtualization-Managing_guests_with_virsh-Save_a_guest"><h5 class="formalpara">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="apes05.html#form-Virtualization-Managing_guests_with_virsh-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" id="form-Virtualization-Managing_guests_with_virsh-Restore_a_guest"><h5 class="formalpara">Restore a guest</h5>
+ Restore a guest previously saved with the <code class="command">virsh save</code> command (<a class="xref" href="apes05.html#form-Virtualization-Managing_guests_with_virsh-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><ul class="docnav"><li class="previous"><a accesskey="p" href="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html"><strong>Prev</strong>E.4. Creating a virtual machine XML dump (configu...</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="apes06.html"><strong>Next</strong>E.6. Shutting down, rebooting and force-shutdown ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes06.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes06.html
new file mode 100644
index 0000000..5f4b02b
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes06.html
@@ -0,0 +1,22 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.6. Shutting down, rebooting and force-shutdown of a guest</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="prev" href="apes05.html" title="E.5. Suspending, resuming, saving and restoring a guest" /><link rel="next" href="apes07.html" title="E.7. Retrieving guest information" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p"
href="apes05.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apes07.html"><strong>Next</strong></a></li></ul><div class="section" id="idp6492608"><div class="titlepage"><div><div><h2 class="title" id="idp6492608">E.6. Shutting down, rebooting and force-shutdown of a guest</h2></div></div></div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Shut_down_a_guest"><h5 class="formalpara">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.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Rebooting_a_guest"><h5 class="formalpara">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> element in the guest's configuration file.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Forcing_a_guest_to_stop"><h5 class="formalpara">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.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apes05.html"><strong>Prev</strong>E.5. Suspending, resuming, saving and restoring 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="apes07.html"><strong>Next</strong>E.7. Retrieving guest information</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes07.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes07.html
new file mode 100644
index 0000000..2414c01
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes07.html
@@ -0,0 +1,40 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.7. Retrieving guest information</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="prev" href="apes06.html" title="E.6. Shutting down, rebooting and force-shutdown of a guest" /><link rel="next" href="apes08.html" title="E.8. Retrieving node information" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey=
"p" href="apes06.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apes08.html"><strong>Next</strong></a></li></ul><div class="section" id="idm12088016"><div class="titlepage"><div><div><h2 class="title" id="idm12088016">E.7. Retrieving guest information</h2></div></div></div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Getting_the_domain_ID_of_a_guest"><h5 class="formalpara">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" id="form-Virtualization-Managing_guests_with_virsh-Getting_the_domain_name_of_a_guest"><h5 class="formalpara">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" id="form-Virtualization-Managing_guests_with_virsh-Getting_the_UUID_of_a_guest"><h5 class="formalpara">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" id="form-Virtualization-Managing_guests_with_virsh-Displaying_guest_Information_"><h5 class="formalpara">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 vr-rhel6u1-x86_64-kvm
+Id: 9
+Name: vr-rhel6u1-x86_64-kvm
+UUID: a03093a1-5da6-a2a2-3baf-a845db2f10b9
+OS Type: hvm
+State: running
+CPU(s): 1
+CPU time: 21.6s
+Max memory: 2097152 kB
+Used memory: 1025000 kB
+Persistent: yes
+Autostart: disable
+Security model: selinux
+Security DOI: 0
+Security label: system_u:system_r:svirt_t:s0:c612,c921 (permissive)
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apes06.html"><strong>Prev</strong>E.6. Shutting down, rebooting and force-shutdown ...</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="apes08.html"><strong>Next</strong>E.8. Retrieving node information</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes08.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes08.html
new file mode 100644
index 0000000..0b3320c
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes08.html
@@ -0,0 +1,26 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.8. Retrieving node information</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="prev" href="apes07.html" title="E.7. Retrieving guest information" /><link rel="next" href="apes09.html" title="E.9. Storage pool information" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apes07.html"><stron
g>Prev</strong></a></li><li class="next"><a accesskey="n" href="apes09.html"><strong>Next</strong></a></li></ul><div class="section" id="idm4306448"><div class="titlepage"><div><div><h2 class="title" id="idm4306448">E.8. Retrieving node information</h2></div></div></div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Displaying_node_information"><h5 class="formalpara">Displaying node information</h5>
+ To display information about the node:
+ </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">
+ Returns basic information about the node, including the model number, number of CPUs, type of CPU, and size of the physical memory. The output corresponds to virNodeInfo structure. Specifically, the "CPU socket(s)" field indicates the number of CPU sockets per NUMA cell.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apes07.html"><strong>Prev</strong>E.7. Retrieving guest information</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="apes09.html"><strong>Next</strong>E.9. Storage pool information</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes09.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes09.html
new file mode 100644
index 0000000..272f6c1
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes09.html
@@ -0,0 +1,19 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.9. Storage pool information</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="prev" href="apes08.html" title="E.8. Retrieving node information" /><link rel="next" href="apes10.html" title="E.10. Displaying per-guest information" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apes08.html
"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apes10.html"><strong>Next</strong></a></li></ul><div class="section" id="idm15735360"><div class="titlepage"><div><div><h2 class="title" id="idm15735360">E.9. Storage pool information</h2></div></div></div><div class="formalpara" id="asfdqsdgasdfsadgwr"><h5 class="formalpara">Editing a storage pool definition</h5>
+ The <code class="command">virsh pool-edit</code> command takes the name or UUID for a storage pool and opens the XML definition file for a storage pool in the users default text editor.
+ </div><div class="para">
+ The <code class="command">virsh pool-edit</code> command is equivalent to running the following commands:
+ </div><pre class="screen"># virsh pool-dumpxml <em class="parameter"><code>pool</code></em> > <em class="parameter"><code>pool</code></em>.xml
+# vim <em class="parameter"><code>pool</code></em>.xml
+# virsh pool-define <em class="parameter"><code>pool</code></em>.xml
+</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The default editor is defined by the <code class="command">$VISUAL</code> or <code class="command">$EDITOR</code> environment variables, and default is <code class="command">vi</code>.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apes08.html"><strong>Prev</strong>E.8. Retrieving node information</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="apes10.html"><strong>Next</strong>E.10. Displaying per-guest information</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes10.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes10.html
new file mode 100644
index 0000000..58b5748
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes10.html
@@ -0,0 +1,119 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.10. Displaying per-guest information</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="prev" href="apes09.html" title="E.9. Storage pool information" /><link rel="next" href="apes11.html" title="E.11. Managing virtual networks" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apes09.html"><strong>
Prev</strong></a></li><li class="next"><a accesskey="n" href="apes11.html"><strong>Next</strong></a></li></ul><div class="section" id="idp6366192"><div class="titlepage"><div><div><h2 class="title" id="idp6366192">E.10. Displaying per-guest information</h2></div></div></div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Displaying_the_guests"><h5 class="formalpara">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">
+ There are seven states that can be visible using this command:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Running - The <code class="computeroutput">running</code> state refers to guests which are currently active on a CPU.
+ </div></li><li class="listitem"><div class="para">
+ Idle - The <code class="computeroutput">idle</code> state indicates that the domain is idle, and may not be running or able to run. This can be caused because the domain is waiting on IO (a traditional wait state) or has gone to sleep because there was nothing else for it to do.
+ </div></li><li class="listitem"><div class="para">
+ Paused - 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 class="listitem"><div class="para">
+ Shutdown - 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 class="listitem"><div class="para">
+ Shut off - The <code class="computeroutput">shut off</code> state indicates that the domain is not running. This can be caused when a domain completly shuts down or has not been started.
+ </div></li><li class="listitem"><div class="para">
+ Crashed - The <code class="computeroutput">crashed</code> state indicates that the domain has crashed and can only occur if the guest has been configured not to restart on crash.
+ </div></li><li class="listitem"><div class="para">
+ Dying - 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></ul></div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Displaying_virtual_CPU_information"><h5 class="formalpara">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" id="form-Virtualization-Managing_guests_with_virsh-Configuring_virtual_CPU_affinity"><h5 class="formalpara">Configuring virtual CPU affinity</h5>
+ To configure the affinity of virtual CPUs with physical CPUs:
+ </div><pre class="screen"># virsh vcpupin <em class="parameter"><code>domain-id vcpu cpulist</code></em></pre><div class="para">
+ The <code class="command">domain-id</code> parameter is the guest's ID number or name.
+ </div><div class="para">
+ The <code class="command">vcpu</code> parameter denotes the number of virtualized CPUs allocated to the guest.The <code class="command">vcpu</code> parameter must be provided.
+ </div><div class="para">
+ The <code class="command">cpulist</code> parameter is a list of physical CPU identifier numbers separated by commas. The <code class="command">cpulist</code> parameter determines which physical CPUs the VCPUs can run on.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Configuring_virtual_CPU_count"><h5 class="formalpara">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">
+ This <em class="parameter"><code>count</code></em> value cannot exceed the number of CPUs that were assigned to the guest when it was created.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Configuring_memory_allocation"><h5 class="formalpara">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><pre class="screen"># <code class="command">virsh setmem</code> <em class="replaceable"><code>vr-rhel6u1-x86_64-kvm</code></em> <em class="replaceable"><code>--kilobytes 1025000</code></em></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 does not affect active guests. If the new value is lower than the available memory, it will shrink possibly causing the guest to crash.
+ </div><div class="para">
+ This command has the following options
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ [--domain] <string> domain name, id or uuid
+ </div></li><li class="listitem"><div class="para">
+ [--size] <number> new memory size, as scaled integer (default KiB)
+ </div></li><li class="listitem"><div class="para">
+ --config takes affect next boot
+ </div></li><li class="listitem"><div class="para">
+ --live controls the memory of the running domain
+ </div></li><li class="listitem"><div class="para">
+ --current controls the memory on the current domain
+ </div></li></ul></div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Configuring_memory_tuning"><h5 class="formalpara">Configuring memory Tuning</h5>
+ The element memtune provides details regarding the memory tunable parameters for the domain. If this is omitted, it defaults to the OS provided defaults. For QEMU/KVM, the parameters are applied to the QEMU process as a whole. Thus, when counting them, one needs to add up guest RAM, guest video RAM, and some memory overhead of QEMU itself. The last piece is hard to determine so one needs guess and try. For each tunable, it is possible to designate which unit the number is in on input, using the same values as for <memory>. For backwards compatibility, output is always in KiB. units.
+ </div><div class="para">
+ Here is an example XML with the memtune options used:
+ </div><pre class="screen">
+<domain>
+
+ <memtune>
+ <hard_limit unit='G'>1</hard_limit>
+ <soft_limit unit='M'>128</soft_limit>
+ <swap_hard_limit unit='G'>2</swap_hard_limit>
+ <min_guarantee unit='bytes'>67108864</min_guarantee>
+ </memtune>
+ ...
+</domain>
+</pre><div class="para">
+ memtune has the following options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ hard_limit - The optional hard_limit element is the maximum memory the guest can use. The units for this value are kibibytes (i.e. blocks of 1024 bytes)
+ </div></li><li class="listitem"><div class="para">
+ soft_limit - The optional soft_limit element is the memory limit to enforce during memory contention. The units for this value are kibibytes (i.e. blocks of 1024 bytes)
+ </div></li><li class="listitem"><div class="para">
+ swap_hard_limit - The optional swap_hard_limit element is the maximum memory plus swap the guest can use. The units for this value are kibibytes (i.e. blocks of 1024 bytes). This has to be more than hard_limit value provided
+ </div></li><li class="listitem"><div class="para">
+ min_guarantee - The optional min_guarantee element is the guaranteed minimum memory allocation for the guest. The units for this value are kibibytes (i.e. blocks of 1024 bytes)
+ </div></li></ul></div><pre class="screen">
+# virsh memtune vr-rhel6u1-x86_64-kvm --hard-limit 512000
+
+# virsh memtune vr-rhel6u1-x86_64-kvm
+hard_limit : 512000 kB
+soft_limit : unlimited
+swap_hard_limit: unlimited
+</pre><div class="para">
+ hard_limit is 512000 kB, it is maximum memory the guest domain can use.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Displaying_guest_block_device_information"><h5 class="formalpara">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" id="form-Virtualization-Managing_guests_with_virsh-Displaying_guest_network_device_information"><h5 class="formalpara">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><ul class="docnav"><li class="previous"><a accesskey="p" href="apes09.html"><strong>Prev</strong>E.9. Storage pool information</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="apes11.html"><strong>Next</strong>E.11. Managing virtual networks</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes11.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes11.html
new file mode 100644
index 0000000..0f7ce5d
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes11.html
@@ -0,0 +1,55 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.11. Managing virtual networks</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="prev" href="apes10.html" title="E.10. Displaying per-guest information" /><link rel="next" href="migrating_guests-with-virsh.html" title="E.12. Migrating guests with virsh" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey
="p" href="apes10.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="migrating_guests-with-virsh.html"><strong>Next</strong></a></li></ul><div class="section" id="idm15826000"><div class="titlepage"><div><div><h2 class="title" id="idm15826000">E.11. Managing virtual networks</h2></div></div></div><div class="para">
+ 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 class="listitem"><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 class="listitem"><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 class="listitem"><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 class="listitem"><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 class="listitem"><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 class="listitem"><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 class="listitem"><div class="para">
+ <code class="command">virsh net-start <em class="replaceable"><code>nameOfInactiveNetwork</code></em> </code> — starts an inactive network.
+ </div></li><li class="listitem"><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="apes10.html"><strong>Prev</strong>E.10. Displaying per-guest information</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="migrating_guests-with-virsh.html"><strong>Next</strong>E.12. Migrating guests with virsh</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes14s03.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes14s03.html
new file mode 100644
index 0000000..dcc87b0
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes14s03.html
@@ -0,0 +1,95 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.14.3. Determining a compatible CPU model to suit a pool of hosts</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-guest-cpu-model-config.html" title="E.14. Guest CPU model configuration" /><link rel="prev" href="sect-learn-about-host-cpu.html" title="E.14.2. Learning about the host CPU model" /><link rel="next" href="apes14s04.html" title="E.14.4. Configuring the guest CPU model" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-learn-about-host-c
pu.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apes14s04.html"><strong>Next</strong></a></li></ul><div class="section" id="idp19394992"><div class="titlepage"><div><div><h3 class="title" id="idp19394992">E.14.3. Determining a compatible CPU model to suit a pool of hosts</h3></div></div></div><div class="para">
+ Now that it is possible to find out what CPU capabilities a single host has, the next step is to determine what CPU capabilities are best to expose to the guest. If it is known that the guest will never need to be migrated to another host, the host CPU model can be passed straight through unmodified. A virtualized data center may have a set of configurations that can guarantee all servers will have 100% identical CPUs. Again the host CPU model can be passed straight through unmodified. The more common case, though, is where there is variation in CPUs between hosts. In this mixed CPU environment, the lowest common denominator CPU must be determined. This is not entirely straightforward, so libvirt provides an API for exactly this task. If libvirt is provided a list of XML documents, each describing a CPU model for a host, libvirt will internally convert these to CPUID masks, calculate their intersection, and convert the CPUID mask result back into an XML CPU description.
Taking the CPU description from a server:
+ </div><pre class="screen">
+# virsh capabilities
+<capabilities>
+
+ <host>
+ <uuid>8e8e4e67-9df4-9117-bf29-ffc31f6b6abb</uuid>
+ <cpu>
+ <arch>x86_64</arch>
+ <model>Westmere</model>
+ <vendor>Intel</vendor>
+ <topology sockets='2' cores='4' threads='2'/>
+ <feature name='rdtscp'/>
+ <feature name='pdpe1gb'/>
+ <feature name='dca'/>
+ <feature name='xtpr'/>
+ <feature name='tm2'/>
+ <feature name='est'/>
+ <feature name='vmx'/>
+ <feature name='ds_cpl'/>
+ <feature name='monitor'/>
+ <feature name='pbe'/>
+ <feature name='tm'/>
+ <feature name='ht'/>
+ <feature name='ss'/>
+ <feature name='acpi'/>
+ <feature name='ds'/>
+ <feature name='vme'/>
+ </cpu>
+
+ ... snip ...
+
+</capabilities>
+</pre><div class="para">
+ A quick check can be made to see whether this CPU description is compatible with the previous workstation CPU description, using the <code class="command">virsh cpu-compare</code> command. To do so, the <code class="command">virsh capabilities > virsh-caps-workstation-full.xml</code> command was executed on the workstation. The file <code class="filename">virsh-caps-workstation-full.xml</code> was edited and reduced to just the following content:
+ </div><pre class="screen">
+<cpu>
+ <arch>x86_64</arch>
+ <model>core2duo</model>
+ <topology sockets='1' cores='4' threads='1'/>
+ <feature name='lahf_lm'/>
+ <feature name='sse4.1'/>
+ <feature name='xtpr'/>
+ <feature name='cx16'/>
+ <feature name='tm2'/>
+ <feature name='est'/>
+ <feature name='vmx'/>
+ <feature name='ds_cpl'/>
+ <feature name='pbe'/>
+ <feature name='tm'/>
+ <feature name='ht'/>
+ <feature name='ss'/>
+ <feature name='acpi'/>
+ <feature name='ds'/>
+ </cpu>
+</pre><div class="para">
+ The reduced content was stored in a file named <code class="filename">virsh-caps-workstation-cpu-only.xml</code> and the <code class="command">virsh cpu-compare</code> command can be executed using this file:
+ </div><pre class="screen">
+virsh cpu-compare virsh-caps-workstation-cpu-only.xml
+Host CPU is a superset of CPU described in virsh-caps-workstation-cpu-only.xml
+</pre><div class="para">
+ As seen in this output, libvirt is correctly reporting the CPUs are not strictly compatible, because there are several features in the server CPU that are missing in the workstation CPU. To be able to migrate between the workstation and the server, it will be necessary to mask out some features, but to determine which ones, libvirt provides an API for this, shown via the <code class="command">virsh cpu-baseline</code> command:
+ </div><pre class="screen">
+# virsh cpu-baseline virsh-cap-weybridge-strictly-cpu-only.xml
+<cpu match='exact'>
+ <model>Penryn</model>
+ <feature policy='require' name='xtpr'/>
+ <feature policy='require' name='tm2'/>
+ <feature policy='require' name='est'/>
+ <feature policy='require' name='vmx'/>
+ <feature policy='require' name='ds_cpl'/>
+ <feature policy='require' name='monitor'/>
+ <feature policy='require' name='pbe'/>
+ <feature policy='require' name='tm'/>
+ <feature policy='require' name='ht'/>
+ <feature policy='require' name='ss'/>
+ <feature policy='require' name='acpi'/>
+ <feature policy='require' name='ds'/>
+ <feature policy='require' name='vme'/>
+</cpu>
+</pre><div class="para">
+ Similarly, if the two <cpu>...</cpu> elements are put into a single file named <code class="filename">both-cpus.xml</code>, the following command would generate the same result:
+ </div><pre class="screen"> # virsh cpu-baseline both-cpus.xml</pre><div class="para">
+ In this case, libvirt has determined that in order to safely migrate a guest between the workstation and the server, it is necessary to mask out 3 features from the XML description for the server, and 3 features from the XML description for the workstation.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-learn-about-host-cpu.html"><strong>Prev</strong>E.14.2. Learning about the host CPU model</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="apes14s04.html"><strong>Next</strong>E.14.4. Configuring the guest CPU model</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes14s04.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes14s04.html
new file mode 100644
index 0000000..c942c0d
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apes14s04.html
@@ -0,0 +1,32 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.14.4. Configuring the guest CPU model</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-guest-cpu-model-config.html" title="E.14. Guest CPU model configuration" /><link rel="prev" href="apes14s03.html" title="E.14.3. Determining a compatible CPU model to suit a pool of hosts" /><link rel="next" href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="Appendix F. Managing guests with the Virtual Machine Manager (virt-manager)" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images
/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apes14s03.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html"><strong>Next</strong></a></li></ul><div class="section" id="idp11306912"><div class="titlepage"><div><div><h3 class="title" id="idp11306912">E.14.4. Configuring the guest CPU model</h3></div></div></div><div class="para">
+ For simple defaults, the guest CPU configuration accepts the same basic XML representation as the host capabilities XML exposes. In other words, the XML from the <code class="command">cpu-baseline</code> virsh command can now be copied directly into the guest XML at the top level under the <domain> element. As the observant reader will have noticed from the previous XML snippet, there are a few extra attributes available when describing a CPU in the guest XML. These can mostly be ignored, but for the curious here is a quick description of what they do. The top level <cpu> element has an attribute called <span class="emphasis"><em>match</em></span> with possible values of:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ match='minimum' - the host CPU must have at least the CPU features described in the guest XML. If the host has additional features beyond the guest configuration, these will also be exposed to the guest.
+ </div></li><li class="listitem"><div class="para">
+ match='exact' - the host CPU must have at least the CPU features described in the guest XML. If the host has additional features beyond the guest configuration, these will be masked out from the guest.
+ </div></li><li class="listitem"><div class="para">
+ match='strict' - the host CPU must have exactly the same CPU features described in the guest XML.
+ </div></li></ul></div><div class="para">
+ The next enhancement is that the <feature> elements can each have an extra 'policy' attribute with possible values of:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ policy='force' - expose the feature to the guest even if the host does not have it. This is usually only useful in the case of software emulation.
+ </div></li><li class="listitem"><div class="para">
+ policy='require' - expose the feature to the guest and fail if the host does not have it. This is the sensible default.
+ </div></li><li class="listitem"><div class="para">
+ policy='optional' - expose the feature to the guest if it happens to support it.
+ </div></li><li class="listitem"><div class="para">
+ policy='disable' - if the host has this feature, then hide it from the guest.
+ </div></li><li class="listitem"><div class="para">
+ policy='forbid' - if the host has this feature, then fail and refuse to start the guest.
+ </div></li></ul></div><div class="para">
+ The 'forbid' policy is for a niche scenario where an incorrectly functioning application will try to use a feature even if it is not in the CPUID mask, and you wish to prevent accidentally running the guest on a host with that feature. The 'optional' policy has special behavior with respect to migration. When the guest is initially started the flag is optional, but when the guest is live migrated, this policy turns into 'require', since you cannot have features disappearing across migration.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apes14s03.html"><strong>Prev</strong>E.14.3. Determining a compatible CPU model to sui...</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_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html"><strong>Next</strong>Appendix F. Managing guests with the Virtual Mach...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apjs14.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apjs14.html
new file mode 100644
index 0000000..34884fe
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/apjs14.html
@@ -0,0 +1,53 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.14. Hypervisor features</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sect-libvirt-dom-xml-pwr-man.html" title="J.13. Power Management" /><link rel="next" href="sect-libvirt-dom-xml-time-keep.html" title="J.15. Time keeping" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-pwr-man.html"><strong>Prev
</strong></a></li><li class="next"><a accesskey="n" href="sect-libvirt-dom-xml-time-keep.html"><strong>Next</strong></a></li></ul><div class="section" id="idm10999840"><div class="titlepage"><div><div><h2 class="title" id="idm10999840">J.14. Hypervisor features</h2></div></div></div><div class="para">
+ Hypervisors may allow certain CPU / machine features to be enabled (<code class="sgmltag-attvalue">state='on')</code> or disabled (<code class="sgmltag-attvalue">state='off'</code>).
+ </div><div class="figure" id="fig-libvirt-dom-xml-hypr-feat"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><features></span>
+ <span class="perl_Keyword"><pae/></span>
+ <span class="perl_Keyword"><acpi/></span>
+ <span class="perl_Keyword"><apic/></span>
+ <span class="perl_Keyword"><hap/></span>
+ <span class="perl_Keyword"><privnet/></span>
+ <span class="perl_Keyword"><hyperv></span>
+ <span class="perl_Keyword"><relaxed</span><span class="perl_Others"> state=</span><span class="perl_String">'on'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></hyperv></span>
+ <span class="perl_Keyword"></features></span>
+ ...
+
+</pre></div><h6>Figure J.21. Hypervisor features</h6></div><br class="figure-break" /><div class="para">
+ All features are listed within the <code class="sgmltag-starttag"><features></code> element, if a <code class="sgmltag-starttag"><state></code> is not specified it is disabled. The available features can be found by calling the <code class="filename">capabilities</code> XML, but a common set for fully virtualized domains are:
+ </div><div class="table" id="table-libvirt-dom-xml-hyp-feat-elem"><h6>Table J.11. Hypervisor features elements</h6><div class="table-contents"><table summary="Hypervisor features elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ State
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><pae></code>
+ </td><td class="">
+ Physical address extension mode allows 32-bit guests to address more than 4 GB of memory.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><acpi></code>
+ </td><td class="">
+ Useful for power management, for example, with KVM guests it is required for graceful shutdown to work.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><apic></code>
+ </td><td class="">
+ Allows the use of programmable IRQ management. For this element, there is an optional attribute <code class="sgmltag-attribute">eoi</code> with values <code class="sgmltag-attvalue">on</code> and <code class="sgmltag-attvalue">off</code> which sets the availability of EOI (End of Interrupt) for the guest.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><hap></code>
+ </td><td class="">
+ Enables the use of Hardware Assisted Paging if it is available in the hardware.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">hyperv</code>
+ </td><td class="">
+ Enables various features to improve the behavior of guests running Microsoft Windows. Using the optional attribute <code class="sgmltag-attribute">relaxed</code> with values <code class="sgmltag-attvalue">on</code> or <code class="sgmltag-attvalue">off</code> enables or disables the relax constraints on timers
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-pwr-man.html"><strong>Prev</strong>J.13. Power 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-libvirt-dom-xml-time-keep.html"><strong>Next</strong>J.15. Time keeping</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/appe-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Revision_History.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/appe-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Revision_History.html
new file mode 100644
index 0000000..516fff7
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/appe-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Revision_History.html
@@ -0,0 +1,19 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix K. Revision History</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="prev" href="section-libvirt-dom-xml-example.html" title="J.23. Example domain XML configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="section-libvirt-dom-xml-example.html"><strong>Prev</strong></a></li><li class="next"></li></ul><div xml:lang="en-US" c
lass="appendix" id="appe-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Revision_History" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Revision History</h1></div></div></div><div class="para">
+ <div class="revhistory"><table summary="Revision History"><tr><th align="left" valign="top" colspan="3"><strong>Revision History</strong></th></tr><tr><td align="left">Revision 0.2-0</td><td align="left">Tue May 28 2013</td><td align="left"><span class="author"><span class="firstname">Laura</span> <span class="surname">Novich</span></span></td></tr><tr><td align="left" colspan="3">
+ <table border="0" summary="Simple list" class="simplelist"><tr><td>Completed merger of guides and prepared for final publishing.</td></tr></table>
+
+ </td></tr><tr><td align="left">Revision 0.1-0</td><td align="left">Tue Jan 15 2013</td><td align="left"><span class="author"><span class="firstname">Laura</span> <span class="surname">Bailey</span></span></td></tr><tr><td align="left" colspan="3">
+ <table border="0" summary="Simple list" class="simplelist"><tr><td>Combined F18 Virtualization Administration Guide and Virtualization Host Configuration and Guest Installation Guide for use in Fedora 19.</td></tr></table>
+
+ </td></tr></table></div>
+
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="section-libvirt-dom-xml-example.html"><strong>Prev</strong>J.23. Example domain XML 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></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/appe-Virtualization-Additional_resources.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/appe-Virtualization-Additional_resources.html
new file mode 100644
index 0000000..2d31ae4
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/appe-Virtualization-Additional_resources.html
@@ -0,0 +1,32 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix I. Additional resources</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt03.html" title="Part III. Appendicies" /><link rel="prev" href="sub-sect-limitations-filters-network-subsystem.html" title="H.10.12. Limitations" /><link rel="next" href="sect-Virtualization-Additional_resources-Installed_documentation.html" title="I.2. Installed documentation" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-limita
tions-filters-network-subsystem.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Additional_resources-Installed_documentation.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="appendix" id="appe-Virtualization-Additional_resources" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Additional resources</h1></div></div></div><div class="para">
+ To learn more about virtualization and Fedora, refer to the following resources.
+ </div><div class="section" id="sect-Virtualization-Additional_resources-Online_resources"><div class="titlepage"><div><div><h2 class="title">I.1. Online resources</h2></div></div></div><a id="idp16033760" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><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 class="listitem"><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 class="listitem"><div class="para">
+ Open Virtualization Center
+ </div><div class="para">
+ <a href="http://www.openvirtualization.com/">http://www.openvirtualization.com</a>
+ </div></li><li class="listitem"><div class="para">
+ Fedora Documentation
+ </div><div class="para">
+ <a href="http://docs.fedoraproject.org">http://docs.fedoraproject.org</a>
+ </div></li><li class="listitem"><div class="para">
+ Virtualization technologies overview
+ </div><div class="para">
+ <a href="http://virt.kernelnewbies.org/">http://virt.kernelnewbies.org</a>
+ </div></li><li class="listitem"><div class="para">
+ Fedora Community
+ </div><div class="para">
+ <a href="https://fedoraproject.org/en/join-fedora">https://fedoraproject.org/en/join-fedora</a>
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-limitations-filters-network-subsystem.html"><strong>Prev</strong>H.10.12. Limitations</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-Additional_resources-Installed_documentation.html"><strong>Next</strong>I.2. Installed documentation</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch-lib-dom-xml.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch-lib-dom-xml.html
new file mode 100644
index 0000000..bdabcf2
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch-lib-dom-xml.html
@@ -0,0 +1,54 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix J. Manipulating the domain xml</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt03.html" title="Part III. Appendicies" /><link rel="prev" href="sect-Virtualization-Additional_resources-Installed_documentation.html" title="I.2. Installed documentation" /><link rel="next" href="sect-dom-xml-op-sys-boot.html" title="J.2. Operating system booting" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-Addition
al_resources-Installed_documentation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-dom-xml-op-sys-boot.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="appendix" id="ch-lib-dom-xml" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Manipulating the domain xml</h1></div></div></div><div class="para">
+ This section describes the XML format used to represent one or more libvirt domains. Whereas a libvirt domain refers to a specified guest virtual machine, here the term <em class="firstterm">domain</em> refers to the root <code class="sgmltag-starttag"><domain></code> element required for defining the parameters of all guest virtual machines. The <code class="sgmltag-starttag"><domain></code> element has two attributes: <code class="sgmltag-attribute">type</code> specifies the hypervisor used for running the domain. The allowed values are driver specific, but include <code class="sgmltag-attvalue"> KVM</code> and others. <code class="sgmltag-attribute">id</code> is a unique integer identifier for the running guest machine. Inactive machines have no id value. The sections in this chapter will address the components of the domain XML. Additional chapters in this manual may refer to this chapter when manipulation of the domain XML is required.
+ </div><div class="section" id="sect-gen-metadata"><div class="titlepage"><div><div><h2 class="title">J.1. General information and metadata</h2></div></div></div><div class="para">
+ This information is in this part of the domain XML:
+ </div><div class="figure" id="ch-lib-dom-xml-example"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain</span><span class="perl_Others"> type=</span><span class="perl_String">'xen'</span><span class="perl_Others"> id=</span><span class="perl_String">'3'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><name></span>fv0<span class="perl_Keyword"></name></span>
+ <span class="perl_Keyword"><uuid></span>4dea22b31d52d8f32516782e98ab3fa0<span class="perl_Keyword"></uuid></span>
+ <span class="perl_Keyword"><title></span>A short description - title - of the domain<span class="perl_Keyword"></title></span>
+ <span class="perl_Keyword"><description></span>Some human readable description<span class="perl_Keyword"></description></span>
+ <span class="perl_Keyword"><metadata></span>
+ <span class="perl_Keyword"><app1:foo</span><span class="perl_Others"> xmlns:app1=</span><span class="perl_String">"http://app1.org/app1/"</span><span class="perl_Keyword">></span>..<span class="perl_Keyword"></app1:foo></span>
+ <span class="perl_Keyword"><app2:bar</span><span class="perl_Others"> xmlns:app2=</span><span class="perl_String">"http://app1.org/app2/"</span><span class="perl_Keyword">></span>..<span class="perl_Keyword"></app2:bar></span>
+ <span class="perl_Keyword"></metadata></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.1. Domain XML metadata</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-gen-metadata"><h6>Table J.1. General metadata elements</h6><div class="table-contents"><table summary="General metadata elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><name></code>
+ </td><td class="">
+ Assigns a name for the virtual machine. This name should consist only of alpha-numeric characters and is required to be unique within the scope of a single host. It is often used to form the filename for storing the persistent configuration files.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><uuid></code>
+ </td><td class="">
+ assigns a globally unique identifier for the virtual machine. The format must be RFC 4122 compliant, eg <code class="sgmltag-attvalue">3e3fce45-4f53-4fa7-bb32-11f34168b82b</code>. If omitted when defining/creating a new machine, a random UUID is generated. It is also possible to provide the UUID via a sysinfo specification.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><title></code>
+ </td><td class="">
+ <code class="sgmltag-element">title</code> Creates space for a short description of the domain. The title should not contain any newlines.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><description></code>
+ </td><td class="">
+ Different from the title, This data is not used by libvirt in any way, it can contain any information the user wants to display.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><metadata></code>
+ </td><td class="">
+ Can be used by applications to store custom metadata in the form of XML nodes/trees. Applications must use custom namespaces on their XML nodes/trees, with only one top-level element per namespace (if the application needs structure, they should have sub-elements to their namespace element)
+ </td></tr></tbody></table></div></div><br class="table-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Additional_resources-Installed_documentation.html"><strong>Prev</strong>I.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="sect-dom-xml-op-sys-boot.html"><strong>Next</strong>J.2. Operating system booting</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch01s02.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch01s02.html
new file mode 100644
index 0000000..af24931
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch01s02.html
@@ -0,0 +1,46 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2. Virtualization Documentation Suite</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html" title="Chapter 1. Introduction" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html" title="Chapter 1. Introduction" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_Requirements.html" title="Chapter 2. System requirements" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Con
tent/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_Requirements.html"><strong>Next</strong></a></li></ul><div class="section" id="idm9825280"><div class="titlepage"><div><div><h2 class="title" id="idm9825280">1.2. Virtualization Documentation Suite</h2></div></div></div><div class="para">
+ Fedora offers a wealth of documentation solutions across its various virtualization products. Coverage of Fedora and its inbuilt virtualization products include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="citetitle">Fedora — Virtualization Getting Started Guide</em>: This guide provides an introduction to virtualization concepts, advantages, and tools, and an overview of Red Hat virtualization documentation and products.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Fedora — Virtualization Deployment and Administration Guide</em> covers the installation, configuration, and maintenance of virtualization hosts and virtual machines.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Fedora — Virtualization Security Guide</em>: This guide provides an overview of virtualization security technologies provided by Red Hat. Also included are recommendations for securing hosts, guests, and shared infrastructure and resources in virtualized environments.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Fedora — Virtualization Tuning and Optimization Guide</em>: This guide provides tips, tricks and suggestions for making full use of virtualization performance features and options for your systems and guest virtual machines.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Fedora — V2V Guide</em> describes importing virtual machines from KVM, Xen and VMware ESX/ESX(i) hypervisors to Red Hat Enterprise Virtualization and KVM managed by libvirt.
+ </div></li></ul></div><div class="para">
+ The oVirt documentation suite provides information on installation, development of applications, configuration and usage of the Red Hat Enterprise Virtualization platform and its related products.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Administration Guide</em> describes how to set up, configure and manage Red Hat Enterprise Virtualization. It assumes that you have successfully installed the Red Hat Enterprise Virtualization Manager and hosts.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Command Line Shell Guide</em> contains information for installing and using the Red Hat Enterprise Virtualization Manager command line shell.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Developer Guide</em> explains how to use the REST API. It covers the fundamentals of the REST architectural concepts in the context of a virtualization environment and provides examples of the API in operation. It also documents the installation and use of the Python Software Development Kit.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Evaluation Guide</em> enables prospective customers to evaluate the features of Red Hat Enterprise Virtualization. Use this guide if you have an evaluation license.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Installation Guide</em> describes the installation prerequisites and procedures. Read this if you need to install Red Hat Enterprise Virtualization. The installation of hosts, Manager and storage are covered in this guide. You will need to refer to the <em class="citetitle">Red Hat Enterprise Virtualization Administration Guide</em> to configure the system before you can start using the platform.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Manager Release Notes</em> contain release specific information for Red Hat Enterprise Virtualization Managers.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Power User Portal Guide</em> describes how power users can create and manage virtual machines from the Red Hat Enterprise Virtualization User Portal.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Quick Start Guide</em> provides quick and simple instructions for first time users to set up a basic Red Hat Enterprise Virtualization environment.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Technical Notes</em> describe the changes made between the current release and the previous one.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Red Hat Enterprise Virtualization — Technical Reference Guide</em> describes the technical architecture of Red Hat Enterprise Virtualization and its interactions with existing infrastructure.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Red Hat Enterprise Virtualization — User Portal Guide</em> describes how users of the Red Hat Enterprise Virtualization system can access and use virtual desktops from the User Portal.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html"><strong>Prev</strong>Chapter 1. Introduction</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_Host_Configuration_and_Guest_Installation_Guide-System_Requirements.html"><strong>Next</strong>Chapter 2. System requirements</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch03s02.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch03s02.html
new file mode 100644
index 0000000..6b63d15
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch03s02.html
@@ -0,0 +1,75 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2. Supported CPU Models</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html" title="Chapter 3. KVM guest virtual machine compatibility" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html" title="Chapter 3. KVM guest virtual machine compatibility" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html" title="Chapter 4. Virtualization restrictions" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product
Site" /></a><a class="right" href="http://docs.redhat.com"><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_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html"><strong>Next</strong></a></li></ul><div class="section" id="idp26449632"><div class="titlepage"><div><div><h2 class="title" id="idp26449632">3.2. Supported CPU Models</h2></div></div></div><div class="para">
+ Fedora 19 supports the use of the following QEMU CPU model definitions:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><em class="parameter"><code>Opteron_G4</code></em></span></dt><dd><div class="para">
+ AMD Opteron 62xx (Gen 4 Class Opteron)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Opteron_G3</code></em></span></dt><dd><div class="para">
+ AMD Opteron 23xx (Gen 3 Class Opteron)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Opteron_G2</code></em></span></dt><dd><div class="para">
+ AMD Opteron 22xx (Gen 2 Class Opteron)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Opteron_G1</code></em></span></dt><dd><div class="para">
+ AMD Opteron 240 (Gen 1 Class Opteron)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>SandyBridge</code></em></span></dt><dd><div class="para">
+ Intel Xeon E312xx (Sandy Bridge)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Nehalem</code></em></span></dt><dd><div class="para">
+ Intel Core i7 9xx (Nehalem Class Core i7)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Penryn</code></em></span></dt><dd><div class="para">
+ Intel Core 2 Duo P9xxx (Penryn Class Core 2)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Conroe</code></em></span></dt><dd><div class="para">
+ Intel Celeron_4x0 (Conroe/Merom Class Core 2)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Westmere</code></em></span></dt><dd><div class="para">
+ Westmere E56xx/L56xx/X56xx (Nehalem-C)
+ </div></dd></dl></div><div class="section" id="para-CPU_Models"><div class="titlepage"><div><div><h3 class="title">3.2.1. Guest CPU models</h3></div></div></div><div class="para">
+ Historically, CPU model definitions were hard-coded in <span class="application"><strong>qemu</strong></span>. This method of defining CPU models was inflexible, and made it difficult to create virtual CPUs with feature sets that matched existing physical CPUs. Typically, users modified a basic CPU model definition with feature flags in order to provide the CPU characteristics required by a virtual machine. Unless these feature sets were carefully controlled, safe migration — which requires feature sets between current and prospective hosts to match — was difficult to support.
+ </div><div class="para">
+ <span class="application"><strong>qemu-kvm</strong></span> has now replaced most hard-wired definitions with configuration file based CPU model definitions. Definitions for a number of current processor models are now included by default, allowing users to specify features more accurately and migrate more safely.
+ </div><div class="para">
+ A list of supported guest CPU models can be viewed with the <code class="command">/usr/libexec/qemu-kvm -cpu ?model</code> command. This command outputs the <em class="parameter"><code>name</code></em> used to select the CPU model at the command line, and a model identifier that corresponds to a commercial instance of that processor class.
+ </div><div class="para">
+ Configuration details for all of these CPU models can be viewed with the <code class="command">/usr/libexec/qemu-kvm -cpu ?dump</code> command, but they are also stored in the <code class="filename">/usr/share/qemu-kvm/cpu-model/cpu-x86_64.conf</code> file by default. Each CPU model definition begins with <code class="literal">[cpudef]</code>, as shown:
+ </div><pre class="screen">[cpudef]
+ name = "Nehalem"
+ level = "2"
+ vendor = "GenuineIntel"
+ family = "6"
+ model = "26"
+ stepping = "3"
+ feature_edx = "sse2 sse fxsr mmx clflush pse36 pat cmov mca \
+ pge mtrr sep apic cx8 mce pae msr tsc pse de fpu"
+ feature_ecx = "popcnt x2apic sse4.2 sse4.1 cx16 ssse3 sse3"
+ extfeature_edx = "i64 syscall xd"
+ extfeature_ecx = "lahf_lm"
+ xlevel = "0x8000000A"
+ model_id = "Intel Core i7 9xx (Nehalem Class Core i7)"</pre><div class="para">
+ The four CPUID fields, <code class="literal">feature_edx</code>, <code class="literal">feature_ecx</code>, <code class="literal">extfeature_edx</code> and <code class="literal">extfeature_ecx</code>, accept named flag values from the corresponding feature sets listed by the <code class="command">/usr/libexec/qemu-kvm -cpu ?cpuid</code> command, as shown:
+ </div><pre class="screen"># /usr/libexec/qemu-kvm -cpu ?cpuid
+Recognized CPUID flags:
+ f_edx: pbe ia64 tm ht ss sse2 sse fxsr mmx acpi ds clflush pn \
+ pse36 pat cmov mca pge mtrr sep apic cx8 mce pae msr tsc \
+ pse de vme fpu
+ f_ecx: hypervisor avx osxsave xsave aes popcnt movbe x2apic \
+ sse4.2|sse4_2 sse4.1|sse4_1 dca pdcm xtpr cx16 fma cid \
+ ssse3 tm2 est smx vmx ds_cpl monitor dtes64 pclmuldq \
+ pni|sse3
+ extf_edx: 3dnow 3dnowext lm rdtscp pdpe1gb fxsr_opt fxsr mmx \
+ mmxext nx pse36 pat cmov mca pge mtrr syscall apic cx8 \
+ mce pae msr tsc pse de vme fpu
+ extf_ecx: nodeid_msr cvt16 fma4 wdt skinit xop ibs osvw \
+ 3dnowprefetch misalignsse sse4a abm cr8legacy extapic svm \
+ cmp_legacy lahf_lm</pre><div class="para">
+ These feature sets are described in greater detail in the appropriate Intel and AMD specifications.
+ </div><div class="para">
+ It is important to use the <code class="code">check</code> flag to verify that all configured features are available.
+ </div><pre class="screen"># /usr/libexec/qemu-kvm -cpu Nehalem,check
+warning: host cpuid 0000_0001 lacks requested flag 'sse4.2|sse4_2' [0x00100000]
+warning: host cpuid 0000_0001 lacks requested flag 'popcnt' [0x00800000]</pre><div class="para">
+ If a defined feature is not available, those features will fail silently by default.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html"><strong>Prev</strong>Chapter 3. KVM guest virtual machine compatibility</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_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html"><strong>Next</strong>Chapter 4. Virtualization restrictions</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch07s02.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch07s02.html
new file mode 100644
index 0000000..6663b36
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch07s02.html
@@ -0,0 +1,34 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.2. Creating a Red Hat Enterprise Linux 6 guest with a network installation tree</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html" title="Chapter 7. Installing a Red Hat Enterprise Linux 6 guest virtual machine on a Red Hat Enterprise Linux 6 host" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html" title="Chapter 7. Installing a Red Hat Enterprise Linux 6 guest virtual machine on a Red Hat Enterprise Linux 6 host" /><link rel="next" href="ch07s03.html" title="7.3. Creating a Red Hat Enterprise Linux 6 guest with PXE" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Con
tent/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch07s03.html"><strong>Next</strong></a></li></ul><div class="section" id="idp17417664"><div class="titlepage"><div><div><h2 class="title" id="idp17417664">7.2. Creating a Red Hat Enterprise Linux 6 guest with a network installation tree</h2></div></div></div><div class="procedure"><h6>Procedure 7.2. Creating a Red Hat Enterprise Linux 6 guest with virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Optional: Preparation</strong></p><div class="para">
+ Prepare the storage environment for the guest virtual machine. For more information on preparing storage, refer to the <em class="citetitle">Red Hat Enterprise Linux 6 Virtualization Administration Guide</em>.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ >Various storage types may be used for storing guest virtual machines. However, for a virtual machine to be able to use migration features the virtual machine must be created on networked storage.
+ </div></div></div><div class="para">
+ Red Hat Enterprise Linux 6 requires at least 1GB of storage space. However, Red Hat recommends at least 5GB of storage space for a Red Hat Enterprise Linux 6 installation and for the procedures in this guide.
+ </div></li><li class="step"><p class="title"><strong>Open virt-manager and start the wizard</strong></p><div class="para">
+ Open virt-manager by executing the <code class="command">virt-manager</code> command as root or opening <span class="guilabel"><strong>Applications</strong></span> → <span class="guilabel"><strong>System Tools</strong></span> → <span class="guilabel"><strong>Virtual Machine Manager</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt1-pic1.png" alt="The main virt-manager window" /></div></div><h6>Figure 7.11. The main virt-manager window</h6></div><br class="figure-break" /><div class="para">
+ Click on the <span class="guibutton"><strong>Create a new virtual machine</strong></span> button to start the new virtual machine wizard.
+ </div><div class="figure" id="gofigurego2"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_newicon.png" alt="The Create a new virtual machine button" /></div></div><h6>Figure 7.12. The Create a new virtual machine button</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guilabel"><strong>Create a new virtual machine</strong></span> window opens.
+ </div></li><li class="step"><p class="title"><strong>Name the virtual machine</strong></p><div class="para">
+ Virtual machine names can contain letters, numbers and the following characters: '<span class="keycap"><strong>_</strong></span>', '<span class="keycap"><strong>.</strong></span>' and '<span class="keycap"><strong>-</strong></span>'. Virtual machine names must be unique for migration and cannot consist only of numbers.
+ </div><div class="para">
+ Choose the installation method from the list of radio buttons.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/rhel6_Screenshot-step1.png" width="444" alt="The New VM window - Step 1" /></div></div><h6>Figure 7.13. The New VM window - Step 1</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><div class="para">
+ Provide the installation URL, and the Kickstart URL and Kernel options if required.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt2-pic3.png" alt="The New VM window - Step 2" /></div></div><h6>Figure 7.14. The New VM window - Step 2</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><div class="para">
+ The remaining steps are the same as the ISO installation procedure. Continue from <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html#RAM-and-VCPUs">Step 5</a> of the ISO installation procedure.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html"><strong>Prev</strong>Chapter 7. Installing a Red Hat Enterprise Linux ...</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="ch07s03.html"><strong>Next</strong>7.3. Creating a Red Hat Enterprise Linux 6 guest ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch07s03.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch07s03.html
new file mode 100644
index 0000000..68235c1
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch07s03.html
@@ -0,0 +1,30 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3. Creating a Red Hat Enterprise Linux 6 guest with PXE</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html" title="Chapter 7. Installing a Red Hat Enterprise Linux 6 guest virtual machine on a Red Hat Enterprise Linux 6 host" /><link rel="prev" href="ch07s02.html" title="7.2. Creating a Red Hat Enterprise Linux 6 guest with a network installation tree" /><link rel="next" href="ch08.html" title="Chapter 8. Virtualizing Fedora on Other Platforms" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Com
mon_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch08.html"><strong>Next</strong></a></li></ul><div class="section" id="idm11250304"><div class="titlepage"><div><div><h2 class="title" id="idm11250304">7.3. Creating a Red Hat Enterprise Linux 6 guest with PXE</h2></div></div></div><div class="procedure"><h6>Procedure 7.3. Creating a Red Hat Enterprise Linux 6 guest with virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Optional: Preparation</strong></p><div class="para">
+ Prepare the storage environment for the virtual machine. For more information on preparing storage, refer to the <em class="citetitle">Red Hat Enterprise Linux 6 Virtualization Administration Guide</em>.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Various storage types may be used for storing guest virtual machines. However, for a virtual machine to be able to use migration features the virtual machine must be created on networked storage.
+ </div></div></div><div class="para">
+ Red Hat Enterprise Linux 6 requires at least 1GB of storage space. However, Red Hat recommends at least 5GB of storage space for a Red Hat Enterprise Linux 6 installation and for the procedures in this guide.
+ </div></li><li class="step"><p class="title"><strong>Open virt-manager and start the wizard</strong></p><div class="para">
+ Open virt-manager by executing the <code class="command">virt-manager</code> command as root or opening <span class="guilabel"><strong>Applications</strong></span> → <span class="guilabel"><strong>System Tools</strong></span> → <span class="guilabel"><strong>Virtual Machine Manager</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt1-pic1.png" alt="The main virt-manager window" /></div></div><h6>Figure 7.15. The main virt-manager window</h6></div><br class="figure-break" /><div class="para">
+ Click on the <span class="guibutton"><strong>Create new virtualized guest</strong></span> button to start the new virtualized guest wizard.
+ </div><div class="figure" id="gofigurego3"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_newicon.png" alt="The create new virtualized guest button" /></div></div><h6>Figure 7.16. The create new virtualized guest button</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guilabel"><strong>New VM</strong></span> window opens.
+ </div></li><li class="step"><p class="title"><strong>Name the virtual machine</strong></p><div class="para">
+ Virtual machine names can contain letters, numbers and the following characters: '<span class="keycap"><strong>_</strong></span>', '<span class="keycap"><strong>.</strong></span>' and '<span class="keycap"><strong>-</strong></span>'. Virtual machine names must be unique for migration and cannot consist only of numbers.
+ </div><div class="para">
+ Choose the installation method from the list of radio buttons.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt3-pic2.png" alt="The New VM window - Step 1" /></div></div><h6>Figure 7.17. The New VM window - Step 1</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><div class="para">
+ The remaining steps are the same as the ISO installation procedure. Continue from <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html#RAM-and-VCPUs">Step 5</a> of the ISO installation procedure. From this point, the only difference in this PXE procedure is on the final <span class="guilabel"><strong>New VM</strong></span> screen, which shows the <span class="guilabel"><strong>Install: PXE Install</strong></span> field.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt3-pic6.png" alt="The New VM window - Step 5 - PXE Install" /></div></div><h6>Figure 7.18. The New VM window - Step 5 - PXE Install</h6></div><br class="figure-break" /></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s02.html"><strong>Prev</strong>7.2. Creating a Red Hat Enterprise Linux 6 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="ch08.html"><strong>Next</strong>Chapter 8. Virtualizing Fedora on Other Platforms</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch08.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch08.html
new file mode 100644
index 0000000..6e2a1b3
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch08.html
@@ -0,0 +1,16 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 8. Virtualizing Fedora on Other Platforms</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="ch07s03.html" title="7.3. Creating a Red Hat Enterprise Linux 6 guest with PXE" /><link rel="next" href="ch08s02.html" title="8.2. On Hyper-V" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s03.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch08s0
2.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="idm3707456" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="idm3707456">Chapter 8. Virtualizing Fedora on Other Platforms</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch08.html#idm18230720">8.1. On VMWare</a></span></dt><dt><span class="section"><a href="ch08s02.html">8.2. On Hyper-V</a></span></dt></dl></div><div class="para">
+ This chapter contains useful reference material for customers running Fedora as a virtualized operating system on other virtualization hosts.
+ </div><div class="section" id="idm18230720"><div class="titlepage"><div><div><h2 class="title" id="idm18230720">8.1. On VMWare</h2></div></div></div><div class="para">
+ Fedora 17 and onwards provide the <code class="systemitem">vmxnet3</code> driver, a para-virtualized network adapter used when running Red Hat Enterprise Linux on VMWare hosts. For further information about this driver, refer to <a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001805">http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001805</a>.
+ </div><div class="para">
+ Fedora 18 and onwards provide the <code class="systemitem">vmw_pvscsi</code> driver, a para-virtualized SCSI adapter used when running Red Hat Enterprise Linux on VMWare hosts. For further information about this driver, refer to <a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010398">http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010398</a>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s03.html"><strong>Prev</strong>7.3. Creating a Red Hat Enterprise Linux 6 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="ch08s02.html"><strong>Next</strong>8.2. On Hyper-V</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch08s02.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch08s02.html
new file mode 100644
index 0000000..a36bfd0
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch08s02.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.2. On Hyper-V</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch08.html" title="Chapter 8. Virtualizing Fedora on Other Platforms" /><link rel="prev" href="ch08.html" title="Chapter 8. Virtualizing Fedora on Other Platforms" /><link rel="next" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html" title="Chapter 9. Installing a fully-virtualized Windows guest" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_righ
t.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html"><strong>Next</strong></a></li></ul><div class="section" id="idp13861216"><div class="titlepage"><div><div><h2 class="title" id="idp13861216">8.2. On Hyper-V</h2></div></div></div><div class="para">
+ Fedora 18 and onwards provide Microsoft's Linux Integration Services, a set of drivers that enable synthetic device support in supported virtualized operating systems. Fedora is a supported virtualized operating system under Linux Integration Services version 3.4. Further details about the drivers provided are available from <a href="http://www.microsoft.com/en-us/download/details.aspx?id=34603">http://www.microsoft.com/en-us/download/details.aspx?id=34603</a>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08.html"><strong>Prev</strong>Chapter 8. Virtualizing Fedora on Other Platforms</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_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html"><strong>Next</strong>Chapter 9. Installing a fully-virtualized Windows...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch10s04.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch10s04.html
new file mode 100644
index 0000000..e73e088
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch10s04.html
@@ -0,0 +1,69 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.4. Using the para-virtualized drivers with Red Hat Enterprise Linux 3.9 guests</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html" title="Chapter 10. KVM Para-virtualized Drivers" /><link rel="prev" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html" title="10.3. Installing drivers during the Windows installation" /><link rel="next" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices.html" title="10.5. Using KVM para-virtualized drivers for existing devices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe
></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices.html"><strong>Next</strong></a></li></ul><div class="section" id="idp6947696"><div class="titlepage"><div><div><h2 class="title" id="idp6947696">10.4. Using the para-virtualized drivers with Red Hat Enterprise Linux 3.9 guests</h2></div></div></div><div class="para">
+ Para-virtualized drivers for Red Hat Enterprise Linux 3.9 consist of five kernel modules: <code class="command">virtio</code>, <code class="command">virtio_blk</code>, <code class="command">virtio_net</code>, <code class="command">virtio_pci</code> and <code class="command">virtio_ring</code>. All five modules must be loaded to use both the para-virtualized block and network devices drivers.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ For Red Hat Enterprise Linux 3.9 guests, the <span class="package">kmod-virtio</span> package is a requirement for the <code class="command">virtio</code> module.
+ </div></div></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ To use the network device driver only, load the <code class="command">virtio</code>, <code class="command">virtio_net</code> and <code class="command">virtio_pci</code> modules. To use the block device driver only, load the <code class="command">virtio</code>, <code class="command">virtio_ring</code>, <code class="command">virtio_blk</code> and <code class="command">virtio_pci</code> modules.
+ </div></div></div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The <span class="package">virtio</span> package modifies the initrd RAM disk file in the <code class="filename">/boot</code> directory. The original initrd file is saved to <code class="filename">/boot/initrd-<em class="replaceable"><code>kernel-version</code></em>.img.virtio.orig</code>. The original initrd file is replaced with a new initrd RAM disk containing the <code class="command">virtio</code> driver modules. The initrd RAM disk is modified to allow the virtual machine to boot from a storage device using the para-virtualized drivers. To use a different initrd file, you must ensure that drivers are loaded with the <code class="filename">sysinit</code> script (<a class="xref" href="ch10s04.html#proc1">Loading the para-virtualized drivers with the sysinit script</a>) or when creating new initrd RAM disk (<a class="xref" href="ch10s04.html#proc2">Adding the para-virtualized drivers to the initrd RAM disk</a>).
+ </div></div></div><div class="formalpara" id="proc1"><h5 class="formalpara">Loading the para-virtualized drivers with the sysinit script</h5>
+ This procedure covers loading the para-virtualized driver modules during the boot sequence on a Red Hat Enterprise Linux 3.9 or newer guest with the <code class="filename">sysinit</code> script. Note that the guest virtual machine cannot use the para-virtualized drivers for the default boot disk if the modules are loaded with the <code class="filename">sysinit</code> script.
+ </div><div class="para">
+ The drivers must be loaded in the following order:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <code class="command">virtio</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">virtio_ring</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">virtio_pci</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">virtio_blk</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">virtio_net</code>
+ </div></li></ol></div><div class="para">
+ <code class="command">virtio_net</code> and <code class="command">virtio_blk</code> are the only drivers whose order can be changed. If other drivers are loaded in a different order, they will not work.
+ </div><div class="para">
+ Next, configure the modules. Locate the following section of the <code class="filename">/etc/rc.d/rc.sysinit</code> file.
+ </div><pre class="screen">if [ -f /etc/rc.modules ]; then
+ /etc/rc.modules
+fi</pre><div class="para">
+ Append the following lines after that section:
+ </div><pre class="screen">if [ -f /etc/rc.modules ]; then
+ /etc/rc.modules
+fi
+
+modprobe virtio
+modprobe virtio_ring # Comment this out if you do not need block driver
+modprobe virtio_blk # Comment this out if you do not need block driver
+modprobe virtio_net # Comment this out if you do not need net driver
+modprobe virtio_pci</pre><div class="para">
+ Reboot the guest virtual machine to load the kernel modules.
+ </div><div class="formalpara" id="proc2"><h5 class="formalpara">Adding the para-virtualized drivers to the initrd RAM disk</h5>
+ This procedure covers loading the para-virtualized driver modules with the kernel on a Red Hat Enterprise Linux 3.9 or newer guest by including the modules in the initrd RAM disk. The mkinitrd tool configures the initrd RAM disk to load the modules. Specify the additional modules with the <em class="parameter"><code>--with</code></em> parameter for the <code class="command">mkinitrd</code> command. Append following set of parameters, in the exact order, when using the <code class="command">mkinitrd</code> command to create a custom initrd RAM disk:
+ </div><pre class="screen">--with virtio --with virtio_ring --with virtio_blk --with virtio_net --with virtio_pci</pre><div class="formalpara"><h5 class="formalpara" id="idp16553888">AMD64 and Intel 64 issues</h5>
+ Use the <code class="filename">x86_64</code> version of the <span class="package">virtio</span> package for AMD64 systems.
+ </div><div class="para">
+ Use the <code class="filename">ia32e</code> version of the <span class="package">virtio</span> package for Intel 64 systems. Using the <code class="filename">x86_64</code> version of the <span class="package">virtio</span> may cause a '<code class="computeroutput">Unresolved symbol</code>' error during the boot sequence on Intel 64 systems.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm1328480">Network performance issues</h5>
+ If you experience low performance with the para-virtualized network drivers, verify the setting for the GSO and TSO features on the host system. The para-virtualized network drivers require that the GSO and TSO options are disabled for optimal performance.
+ </div><div class="para">
+ Verify the status of the GSO and TSO settings, use the command on the host (replacing <em class="replaceable"><code>interface</code></em> with the network interface used by the guest):
+ </div><pre class="screen"># ethtool -k <em class="replaceable"><code>interface</code></em></pre><div class="para">
+ Disable the GSO and TSO options with the following commands on the host:
+ </div><pre class="screen"># ethtool -K <em class="replaceable"><code>interface</code></em> gso off
+# ethtool -K <em class="replaceable"><code>interface</code></em> tso off</pre><div class="formalpara"><h5 class="formalpara" id="idm1323120">Para-virtualized driver swap partition issue</h5>
+ After activating the para-virtualized block device driver the swap partition may not be available. This issue is may be caused by a change in disk device name. To fix this issue, open the <code class="filename">/etc/fstab</code> file and locate the lines containing swap partitions, for example:
+ </div><pre class="screen">/dev/hda3 swap swap defaults 0 0</pre><div class="para">
+ The para-virtualized drivers use the <code class="command">/dev/vd*</code> naming convention, not the <code class="command">/dev/hd*</code> naming convention. To resolve this issue modify the incorrect swap entries in the <code class="filename">/etc/fstab</code> file to use the <code class="command">/dev/vd*</code> convention, for the example above:
+ </div><pre class="screen">/dev/vda3 swap swap defaults 0 0</pre><div class="para">
+ Save the changes and reboot the guest virtual machine. The virtual machine should now have swap partitions.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html"><strong>Prev</strong>10.3. Installing drivers during the Windows insta...</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="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices.html"><strong>Next</strong>10.5. Using KVM para-virtualized drivers for exis...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch11s02.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch11s02.html
new file mode 100644
index 0000000..5186894
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch11s02.html
@@ -0,0 +1,23 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.2. Disabling vhost-net</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html" title="Chapter 11. Network configuration" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html" title="Chapter 11. Network configuration" /><link rel="next" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html" title="11.3. Bridged networking with libvirt" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_le
ft.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html"><strong>Next</strong></a></li></ul><div class="section" id="idm3770256"><div class="titlepage"><div><div><h2 class="title" id="idm3770256">11.2. Disabling vhost-net</h2></div></div></div><div class="para">
+ The <code class="command">vhost-net</code> module is a kernel-level backend for virtio networking that reduces virtualization overhead by moving virtio packet processing tasks out of user space (the qemu process) and into the kernel (the <code class="systemitem">vhost-net</code> driver). vhost-net is only available for virtio network interfaces. If the vhost-net kernel module is loaded, it is enabled by default for all virtio interfaces, but can be disabled in the interface configuration in the case that a particular workload experiences a degradation in performance when vhost-net is in use.
+ </div><div class="para">
+ Specifically, when UDP traffic is sent from a host machine to a guest virtual machine on that host, performance degradation can occur if the guest virtual machine processes incoming data at a rate slower than the host machine sends it. In this situation, enabling <code class="command">vhost-net</code> causes the UDP socket's receive buffer to overflow more quickly, which results in greater packet loss. It is therefore better to disable <code class="command">vhost-net</code> in this situation to slow the traffic, and improve overall performance.
+ </div><div class="para">
+ To disable <code class="command">vhost-net</code>, edit the <code class="code"><interface></code> sub-element in the guest virtual machine's XML configuration file and define the network as follows:
+ </div><pre class="screen"><interface type="network">
+ ...
+ <model type="virtio"/>
+ <driver name="qemu"/>
+ ...
+</interface></pre><div class="para">
+ Setting the driver name to <code class="literal">qemu</code> forces packet processing into qemu user space, effectively disabling vhost-net for that interface.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html"><strong>Prev</strong>Chapter 11. 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_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html"><strong>Next</strong>11.3. Bridged networking with libvirt</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch12s03.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch12s03.html
new file mode 100644
index 0000000..7826f8d
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch12s03.html
@@ -0,0 +1,87 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.3. PCI device assignment with virt-install</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html" title="Chapter 12. PCI device configuration" /><link rel="prev" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host.html" title="12.2. Assigning a PCI device with virt-manager" /><link rel="next" href="ch12s04.html" title="12.4. Detaching an assigned PCI device" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch12s04.html"><strong>Next</strong></a></li></ul><div class="section" id="idm13270864"><div class="titlepage"><div><div><h2 class="title" id="idm13270864">12.3. PCI device assignment with virt-install</h2></div></div></div><div class="para">
+ To use <span class="application"><strong>virt-install</strong></span> to assign a PCI device, use the <em class="parameter"><code>--host-device</code></em> parameter.
+ </div><div class="procedure"><h6>Procedure 12.5. Assigning a PCI device to a virtual machine with virt-install</h6><ol class="1"><li class="step"><p class="title"><strong>Identify the device</strong></p><div class="para">
+ Identify the PCI device designated for device assignment to the guest virtual machine.
+ </div><pre class="screen"># lspci | grep Ethernet
+00:19.0 Ethernet controller: Intel Corporation 82567LM-2 Gigabit Network Connection
+01:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
+01:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)</pre><div class="para">
+ The <code class="command">virsh nodedev-list</code> command lists all devices attached to the system, and identifies each PCI device with a string. To limit output to only PCI devices, run the following command:
+ </div><pre class="screen"># virsh nodedev-list --cap pci
+pci_0000_00_00_0
+pci_0000_00_01_0
+pci_0000_00_03_0
+pci_0000_00_07_0
+pci_0000_00_10_0
+pci_0000_00_10_1
+pci_0000_00_14_0
+pci_0000_00_14_1
+pci_0000_00_14_2
+pci_0000_00_14_3
+pci_0000_00_19_0
+pci_0000_00_1a_0
+pci_0000_00_1a_1
+pci_0000_00_1a_2
+pci_0000_00_1a_7
+pci_0000_00_1b_0
+pci_0000_00_1c_0
+pci_0000_00_1c_1
+pci_0000_00_1c_4
+pci_0000_00_1d_0
+pci_0000_00_1d_1
+pci_0000_00_1d_2
+pci_0000_00_1d_7
+pci_0000_00_1e_0
+pci_0000_00_1f_0
+pci_0000_00_1f_2
+pci_0000_00_1f_3
+pci_0000_01_00_0
+pci_0000_01_00_1
+pci_0000_02_00_0
+pci_0000_02_00_1
+pci_0000_06_00_0
+pci_0000_07_02_0
+pci_0000_07_03_0</pre><div class="para">
+ Record the PCI device number; the number is needed in other steps.
+ </div><div class="para">
+ Information on the domain, bus and function are available from output of the <code class="command">virsh nodedev-dumpxml</code> command:
+ </div><pre class="screen"># virsh nodedev-dumpxml pci_0000_01_00_0
+<device>
+ <name>pci_0000_01_00_0</name>
+ <parent>pci_0000_00_01_0</parent>
+ <driver>
+ <name>igb</name>
+ </driver>
+ <capability type='pci'>
+ <domain>0</domain>
+ <bus>1</bus>
+ <slot>0</slot>
+ <function>0</function>
+ <product id='0x10c9'>82576 Gigabit Network Connection</product>
+ <vendor id='0x8086'>Intel Corporation</vendor>
+ <capability type='virt_functions'>
+ </capability>
+ </capability>
+</device></pre></li><li class="step"><p class="title"><strong>Add the device</strong></p><div class="para">
+ Use the PCI identifier output from the <code class="command">virsh nodedev</code> command as the value for the <em class="parameter"><code>--host-device</code></em> parameter.
+ </div><pre class="screen">virt-install \
+--name=guest1-F19 \
+--disk path=/var/lib/libvirt/images/guest1-F19.img,size=8 \
+--nonsparse --graphics spice \
+--vcpus=2 --ram=2048 \
+--location=http://example1.com/installation_tree/f19-Server-x86_64/os \
+--nonetworks \
+--os-type=linux \
+--os-variant=fedora
+--host-device=<span class="emphasis"><em>pci_0000_01_00_0</em></span></pre></li><li class="step"><p class="title"><strong>Complete the installation</strong></p><div class="para">
+ Complete the guest installation. The PCI device should be attached to the guest.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host.html"><strong>Prev</strong>12.2. Assigning a PCI device 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="ch12s04.html"><strong>Next</strong>12.4. Detaching an assigned PCI device</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch12s04.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch12s04.html
new file mode 100644
index 0000000..7a36c16
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch12s04.html
@@ -0,0 +1,28 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.4. Detaching an assigned PCI device</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html" title="Chapter 12. PCI device configuration" /><link rel="prev" href="ch12s03.html" title="12.3. PCI device assignment with virt-install" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html" title="Chapter 13. SR-IOV" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a
></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch12s03.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html"><strong>Next</strong></a></li></ul><div class="section" id="idp1348656"><div class="titlepage"><div><div><h2 class="title" id="idp1348656">12.4. Detaching an assigned PCI device</h2></div></div></div><div class="para">
+ When a host PCI device has been assigned to a guest machine, the host can no longer use the device. Read this section to learn how to detach the device from the guest with <code class="command">virsh</code> or <span class="application"><strong>virt-manager</strong></span> so it is available for host use.
+ </div><div class="procedure"><h6>Procedure 12.6. Detaching a PCI device from a guest with virsh</h6><ol class="1"><li class="step"><p class="title"><strong>Detach the device</strong></p><div class="para">
+ Use the following command to detach the PCI device from the guest by removing it in the guest's XML file:
+ </div><pre class="screen"># virsh detach-device <em class="replaceable"><code>name_of_guest</code></em> <em class="replaceable"><code>file.xml</code></em></pre></li><li class="step"><p class="title"><strong>Re-attach the device to the host (optional)</strong></p><div class="para">
+ If the device is in <em class="parameter"><code>managed</code></em> mode, skip this step. The device will be returned to the host automatically.
+ </div><div class="para">
+ If the device is not using <em class="parameter"><code>managed</code></em> mode, use the following command to re-attach the PCI device to the host machine:
+ </div><pre class="screen"># virsh nodedev-reattach <em class="replaceable"><code>device</code></em></pre><div class="para">
+ For example, to re-attach the <code class="literal">pci_0000_01_00_0</code> device to the host:
+ </div><pre class="screen">virsh nodedev-reattach pci_0000_01_00_0</pre><div class="para">
+ The device is now available for host use.
+ </div></li></ol></div><div class="procedure"><h6>Procedure 12.7. Detaching a PCI Device from a guest with virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Open the virtual hardware details screen</strong></p><div class="para">
+ In <span class="application"><strong>virt-manager</strong></span>, double-click on the virtual machine that contains the device. Select the <span class="guilabel"><strong>Show virtual hardware details</strong></span> button to display a list of virtual hardware.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/vm_info_button_new.png" alt="The Show virtual hardware details button." /></div></div><h6>Figure 12.4. The virtual hardware details button</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Select and remove the device</strong></p><div class="para">
+ Select the PCI device to be detached from the list of virtual devices in the left panel.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/PCIremoval.png" width="444" alt="The PCI device details and the Remove button." /></div></div><h6>Figure 12.5. Selecting the PCI device to be detached</h6></div><br class="figure-break" /><div class="para">
+ Click the <span class="guibutton"><strong>Remove</strong></span> button to confirm. The device is now available for host use.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch12s03.html"><strong>Prev</strong>12.3. PCI device assignment with virt-install</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_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html"><strong>Next</strong>Chapter 13. SR-IOV</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch13s03.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch13s03.html
new file mode 100644
index 0000000..688fc9d
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch13s03.html
@@ -0,0 +1,29 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>13.3. Troubleshooting SR-IOV</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html" title="Chapter 13. SR-IOV" /><link rel="prev" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html" title="13.2. Using SR-IOV" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management.html" title="Chapter 14. KVM guest timing management" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><
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_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management.html"><strong>Next</strong></a></li></ul><div class="section" id="idm4394640"><div class="titlepage"><div><div><h2 class="title" id="idm4394640">13.3. Troubleshooting SR-IOV</h2></div></div></div><div class="para">
+ This section contains solutions for problems which may affect SR-IOV.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Error starting the guest</span></dt><dd><div class="para">
+ When starting a configured virtual machine, an error occurs as follows:
+ </div><pre class="screen"># virsh start test
+error: Failed to start domain test
+error: internal error unable to start guest: char device redirected to
+/dev/pts/2
+get_real_device: /sys/bus/pci/devices/0000:03:10.0/config: Permission denied
+init_assigned_device: Error: Couldn't get real device (03:10.0)!
+Failed to initialize assigned device host=03:10.0</pre><div class="para">
+ This error is often caused by a device that is already assigned to another guest or to the host itself.
+ </div></dd><dt class="varlistentry"><span class="term">Error migrating, saving, or dumping the guest</span></dt><dd><div class="para">
+ Attempts to migrate and dump the virtual machine cause an error similar to the following:
+ </div><pre class="screen"># virsh dump --crash 5 /tmp/vmcore
+error: Failed to core dump domain 5 to /tmp/vmcore
+error: internal error unable to execute QEMU command 'migrate': An undefined
+error has occurred</pre><div class="para">
+ Because device assignment uses hardware on the specific host where the virtual machine was started, guest migration and save are not supported when device assignment is in use. Currently, the same limitation also applies to core-dumping a guest; this may change in the future.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html"><strong>Prev</strong>13.2. Using SR-IOV</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_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management.html"><strong>Next</strong>Chapter 14. KVM guest timing management</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch15s02.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch15s02.html
new file mode 100644
index 0000000..1f2bb94
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch15s02.html
@@ -0,0 +1,29 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.2. Booting a guest using PXE</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html" title="Chapter 15. Network booting with libvirt" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html" title="Chapter 15. Network booting with libvirt" /><link rel="next" href="ch15s02s02.html" title="15.2.2. Using a private libvirt network" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/i
mage_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch15s02s02.html"><strong>Next</strong></a></li></ul><div class="section" id="idp22497584"><div class="titlepage"><div><div><h2 class="title" id="idp22497584">15.2. Booting a guest using PXE</h2></div></div></div><div class="para">
+ This section demonstrates how to boot a guest virtual machine with PXE.
+ </div><div class="section" id="idp22499056"><div class="titlepage"><div><div><h3 class="title" id="idp22499056">15.2.1. Using bridged networking</h3></div></div></div><div class="procedure"><h6>Procedure 15.2. Booting a guest using PXE and bridged networking</h6><ol class="1"><li class="step"><div class="para">
+ Ensure bridging is enabled such that the PXE boot server is available on the network.
+ </div></li><li class="step"><div class="para">
+ Boot a guest virtual machine with PXE booting enabled. You can use the <code class="command">virt-install</code> command to create a new virtual machine with PXE booting enabled, as shown in the following example command:
+ </div><pre class="screen">virt-install --pxe --network bridge=breth0 --prompt</pre><div class="para">
+ Alternatively, ensure that the guest network is configured to use your bridged network, and that the XML guest configuration file has a <code class="code"><boot dev='network'/></code> element inside the <code class="code"><os></code> element, as shown in the following example:
+ </div><pre class="screen"><os>
+ <type arch='x86_64' machine='rhel6.2.0'>hvm</type>
+ <boot dev='network'/>
+ <boot dev='hd'/>
+</os>
+<interface type='bridge'>
+ <mac address='52:54:00:5a:ad:cb'/>
+ <source bridge='breth0'/>
+ <target dev='vnet0'/>
+ <alias name='net0'/>
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
+</interface></pre></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html"><strong>Prev</strong>Chapter 15. Network booting 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="ch15s02s02.html"><strong>Next</strong>15.2.2. Using a private libvirt network</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch15s02s02.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch15s02s02.html
new file mode 100644
index 0000000..27d66cb
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch15s02s02.html
@@ -0,0 +1,28 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.2.2. Using a private libvirt network</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch15s02.html" title="15.2. Booting a guest using PXE" /><link rel="prev" href="ch15s02.html" title="15.2. Booting a guest using PXE" /><link rel="next" href="qemu-ga.html" title="Chapter 16. QEMU Guest Agent" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="qem
u-ga.html"><strong>Next</strong></a></li></ul><div class="section" id="idp10845872"><div class="titlepage"><div><div><h3 class="title" id="idp10845872">15.2.2. Using a private libvirt network</h3></div></div></div><div class="procedure"><h6>Procedure 15.3. Using a private libvirt network</h6><ol class="1"><li class="step"><div class="para">
+ Configure PXE booting on libvirt as shown in <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html#setting-up-server-private">Section 15.1.1, “Setting up a PXE boot server on a private libvirt network”</a>.
+ </div></li><li class="step"><div class="para">
+ Boot a guest virtual machine using libvirt with PXE booting enabled. You can use the <code class="command">virt-install</code> command to create/install a new virtual machine using PXE:
+ </div><pre class="screen">virt-install --pxe --network network=default --prompt</pre></li></ol></div><div class="para">
+ Alternatively, ensure that the guest network is configured to use your bridged network, and that the XML guest configuration file has a <code class="code"><boot dev='network'/></code> element inside the <code class="code"><os></code> element, as shown in the following example:
+ </div><pre class="screen"><os>
+ <type arch='x86_64' machine='rhel6.2.0'>hvm</type>
+ <boot dev='network'/>
+ <boot dev='hd'/>
+</os></pre><div class="para">
+ Also ensure that the guest virtual machine is connected to the private network:
+ </div><pre class="screen"><interface type='network'>
+ <mac address='52:54:00:66:79:14'/>
+ <source network='default'/>
+ <target dev='vnet0'/>
+ <alias name='net0'/>
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
+</interface></pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s02.html"><strong>Prev</strong>15.2. Booting a guest using 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="qemu-ga.html"><strong>Next</strong>Chapter 16. QEMU Guest Agent</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch18s04.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch18s04.html
new file mode 100644
index 0000000..c250240
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch18s04.html
@@ -0,0 +1,28 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>18.4. Virtualization firewall information</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization-Security_for_virtualization.html" title="Chapter 18. Security for virtualization" /><link rel="prev" href="sect-Virtualization-Security_for_virtualization-SELinux_considerations.html" title="18.3. SELinux" /><link rel="next" href="chap-sVirt.html" title="Chapter 19. sVirt" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s
ect-Virtualization-Security_for_virtualization-SELinux_considerations.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-sVirt.html"><strong>Next</strong></a></li></ul><div class="section" id="idp983088"><div class="titlepage"><div><div><h2 class="title" id="idp983088">18.4. Virtualization firewall information</h2></div></div></div><div class="para">
+ Various ports are used for communication between virtualized guests and management utilities.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Any network service on a virtualized guest must have the applicable ports open on the guest to allow external access. If a network service on a guest is firewalled it will be inaccessible. Always verify the guests network configuration first.
+ </div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ ICMP requests must be accepted. ICMP packets are used for network testing. You cannot ping guests if ICMP packets are blocked.
+ </div></li><li class="listitem"><div class="para">
+ Port 22 should be open for SSH access and the initial installation.
+ </div></li><li class="listitem"><div class="para">
+ Ports 80 or 443 (depending on the security settings on the RHEV Manager) are used by the vdsm-reg service to communicate information about the host.
+ </div></li><li class="listitem"><div class="para">
+ Ports 5634 to 6166 are used for guest console access with the SPICE protocol.
+ </div></li><li class="listitem"><div class="para">
+ Ports 49152 to 49216 are used for migrations with KVM. Migration may use any port in this range depending on the number of concurrent migrations occurring.
+ </div></li><li class="listitem"><div class="para">
+ Enabling IP forwarding (<code class="computeroutput">net.ipv4.ip_forward = 1</code>) is also required for shared bridges and the default bridge. Note that installing libvirt enables this variable so it will be enabled when the virtualization packages are installed unless it was manually disabled.
+ </div></li></ul></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Note that enabling IP forwarding is <span class="bold bold"><strong>not</strong></span> required for physical bridge devices. When a guest is connected through a physical bridge, traffic only operates at a level that does not require IP configuration such as IP forwarding.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Security_for_virtualization-SELinux_considerations.html"><strong>Prev</strong>18.3. SELinux</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-sVirt.html"><strong>Next</strong>Chapter 19. sVirt</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch19s02.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch19s02.html
new file mode 100644
index 0000000..408bdb1
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch19s02.html
@@ -0,0 +1,52 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2. sVirt labeling</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-sVirt.html" title="Chapter 19. sVirt" /><link rel="prev" href="chap-sVirt.html" title="Chapter 19. sVirt" /><link rel="next" href="chap-Virtualization_Administration_Guide-KVM_live_migration.html" title="Chapter 20. KVM live migration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-sVirt.html"><strong>Prev</strong></a></li><li cl
ass="next"><a accesskey="n" href="chap-Virtualization_Administration_Guide-KVM_live_migration.html"><strong>Next</strong></a></li></ul><div class="section" id="idm2880032"><div class="titlepage"><div><div><h2 class="title" id="idm2880032">19.2. sVirt labeling</h2></div></div></div><div class="para">
+ Like other services under the protection of SELinux, sVirt uses process-based mechanisms and restrictions to provide an extra layer of security over guest instances. Under typical use, you should not even notice that sVirt is working in the background. This section describes the labeling features of sVirt.
+ </div><div class="para">
+ As shown in the following output, when using sVirt, each virtualized guest process is labeled and runs with a dynamically generated level. Each process is isolated from other VMs with different levels:
+ </div><pre class="screen">
+# ps -eZ | grep qemu
+
+system_u:system_r:svirt_t:s0:c87,c520 27950 ? 00:00:17 qemu-kvm
+</pre><div class="para">
+ The actual disk images are automatically labeled to match the processes, as shown in the following output:
+ </div><pre class="screen">
+# ls -lZ /var/lib/libvirt/images/*
+
+ system_u:object_r:svirt_image_t:s0:c87,c520 image1
+</pre><div class="para">
+ The following table outlines the different labels that can be assigned when using sVirt:
+ </div><div class="table"><h6>Table 19.1. sVirt labels</h6><div class="table-contents"><table summary="sVirt labels" border="1"><colgroup><col align="left" class="c1" width="50%" /><col align="left" class="c2" width="50%" /></colgroup><thead><tr><th class="" align="left">
+ Type/Description
+ </th><th class="" align="left">
+ SELinux Context
+ </th></tr></thead><tbody><tr><td class="" align="left">
+ Virtualized guest processes. MCS1 is a random MCS field. Approximately 500,000 labels are supported.
+ </td><td class="" align="left">
+ system_u:system_r:svirt_t:MCS1
+ </td></tr><tr><td class="" align="left">
+ Virtualized guest images. Only <span class="emphasis"><em>svirt_t</em></span> processes with the same MCS fields can read/write these images.
+ </td><td class="" align="left">
+ system_u:object_r:svirt_image_t:MCS1
+ </td></tr><tr><td class="" align="left">
+ Virtualized guest shared read/write content. All <span class="emphasis"><em>svirt_t</em></span> processes can write to the svirt_image_t:s0 files.
+ </td><td class="" align="left">
+ system_u:object_r:svirt_image_t:s0
+ </td></tr><tr><td class="" align="left">
+ Virtualized guest shared read only content. All svirt_t processes can read these files/devices.
+ </td><td class="" align="left">
+ system_u:object_r:svirt_content_t:s0
+ </td></tr><tr><td class="" align="left">
+ Virtualized guest images. Default label for when an image exits. No <span class="emphasis"><em>svirt_t</em></span> virtual processes can read files/devices with this label.
+ </td><td class="" align="left">
+ system_u:object_r:virt_content_t:s0
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ It is also possible to perform static labeling when using sVirt. Static labels allow the administrator to select a specific label, including the MCS/MLS field, for a virtualized guest. Administrators who run statically-labeled virtualized guests are responsible for setting the correct label on the image files. The virtualized guest will always be started with that label, and the sVirt system will never modify the label of a statically-labeled virtual machine's content. This allows the sVirt component to run in an MLS environment. You can also run multiple virtualized guests with different sensitivity levels on a system, depending on your requirements.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-sVirt.html"><strong>Prev</strong>Chapter 19. sVirt</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_Administration_Guide-KVM_live_migration.html"><strong>Next</strong>Chapter 20. KVM live migration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch24s02.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch24s02.html
new file mode 100644
index 0000000..6a54189
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch24s02.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>24.2. Hugepage support</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_GuideAdvanced.html" title="Chapter 24. Advanced virtualization administration" /><link rel="prev" href="chap-Virtualization_Administration_GuideAdvanced.html" title="Chapter 24. Advanced virtualization administration" /><link rel="next" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.p
ng" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_GuideAdvanced.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html"><strong>Next</strong></a></li></ul><div class="section" id="idm9393504"><div class="titlepage"><div><div><h2 class="title" id="idm9393504">24.2. Hugepage support</h2></div></div></div><div class="formalpara"><h5 class="formalpara" id="idp23024192">Introduction</h5>
+ x86 CPUs usually address memory in 4kB pages, but they are capable of using larger pages known as <span class="bold bold"><strong>huge pages</strong></span>. KVM guests can be deployed with huge page memory support in order to reduce memory consumption and improve performance by reducing CPU cache usage.
+ </div><div class="para">
+ By using huge pages for a KVM guest, less memory is used for page tables and TLB (Translation Lookaside Buffer) misses are reduced, thereby significantly increasing performance, especially for memory-intensive situations.
+ </div><div class="para">
+ <span class="bold bold"><strong>Transparent Hugepage Support</strong></span> is a kernel feature that reduces TLB entries needed for an application. By also allowing all free memory to be used as cache, performance is increased.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm3462912">Using Transparent Hugepage Support</h5>
+ To use Transparent Hugepage Support, no special configuration in the <code class="filename">qemu.conf</code> file is required. Hugepages are used by default if <code class="filename">/sys/kernel/mm/redhat_transparent_hugepage/enabled</code> is set to <span class="bold bold"><strong>always</strong></span>.
+ </div><div class="para">
+ Transparent Hugepage Support does not prevent the use of hugetlbfs. However, when hugetlbfs is not used, KVM will use transparent hugepages instead of the regular 4kB page size.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_GuideAdvanced.html"><strong>Prev</strong>Chapter 24. Advanced virtualization 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_Administration_Guide-Tips_and_tricks.html"><strong>Next</strong>Chapter 25. Miscellaneous administration tasks</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch25s05.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch25s05.html
new file mode 100644
index 0000000..68354b4
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch25s05.html
@@ -0,0 +1,179 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.5. Setting KVM processor affinities</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions.html" title="25.4. Verifying virtualization extensions" /><link rel="next" href="sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address.html" title="25.6. Generating a new unique MAC address" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Co
ntent/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="idp6363040" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="idp6363040">25.5. Setting KVM processor affinities</h2></div></div></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ <span class="application"><strong>libvirt</strong></span> refers to a NUMA node as a <span class="emphasis"><em>cell</em></span>.
+ </div></div></div><div class="para">
+ This section covers setting processor and processing core affinities with <span class="application"><strong>libvirt</strong></span> and KVM guests.
+ </div><div class="para">
+ By default, libvirt provisions guests using the hypervisor's default policy. For most hypervisors, the policy is to run guests on any available processing core or CPU. There are times when an explicit policy may be better, particularly for systems with a NUMA (Non-Uniform Memory Access) architecture. A guest on a NUMA system can be pinned to a processing core so that its memory allocations are always local to the node it is running on. This avoids cross-node memory transports which have less bandwidth and can significantly degrade performance.
+ </div><div class="para">
+ On non-NUMA systems some form of explicit placement across the hosts’ sockets, cores and hyperthreads may be more efficient.
+ </div><div class="formalpara"><h5 class="formalpara" id="idp1925568">Identifying CPU and NUMA topology</h5>
+ The first step in deciding which policy to apply is to determine the host’s memory and CPU topology. The <code class="command">virsh nodeinfo</code> command provides information about how many sockets, cores and hyperthreads are attached to a host.
+ </div><pre class="screen"># virsh nodeinfo
+CPU model: x86_64
+CPU(s): 8
+CPU frequency: 1000 MHz
+CPU socket(s): 2
+Core(s) per socket: 4
+Thread(s) per core: 1
+NUMA cell(s): 2
+Memory size: 8179176 kB</pre><div class="para">
+ This output shows that the system has eight CPU cores and two sockets. Each CPU socket has four cores. This splitting of CPU cores across multiple sockets suggests that the system has Non-Uniform Memory Access (NUMA) architecture.
+ </div><div class="para">
+ NUMA architecture can be more complex than other architectures. Use the <code class="command">virsh capabilities</code> command to get additional output data about the CPU configuration.
+ </div><pre class="programlisting"># virsh capabilities
+<capabilities>
+ <host>
+ <cpu>
+ <arch>x86_64</arch>
+ </cpu>
+ <migration_features>
+ <live/>
+ <uri_transports>
+ <uri_transport>tcp</uri_transport>
+ </uri_transports>
+ </migration_features>
+ <topology>
+ <cells num='2'>
+ <cell id='0'>
+ <cpus num='4'>
+ <cpu id='0'/>
+ <cpu id='1'/>
+ <cpu id='2'/>
+ <cpu id='3'/>
+ </cpus>
+ </cell>
+ <cell id='1'>
+ <cpus num='4'>
+ <cpu id='4'/>
+ <cpu id='5'/>
+ <cpu id='6'/>
+ <cpu id='7'/>
+ </cpus>
+ </cell>
+ </cells>
+ </topology>
+ <secmodel>
+ <model>selinux</model>
+ <doi>0</doi>
+ </secmodel>
+ </host>
+
+ <span class="emphasis"><em>[ Additional XML removed ]</em></span>
+
+</capabilities></pre><div class="para">
+ This output shows two NUMA nodes (also know as NUMA cells), each containing four logical CPUs (four processing cores). This system has two sockets, therefore it can be inferred that each socket is a separate NUMA node. For a guest with four virtual CPUs, it is optimal to lock the guest to physical CPUs 0 to 3, or 4 to 7, to avoid accessing non-local memory, which is significantly slower than accessing local memory.
+ </div><div class="para">
+ If a guest requires eight virtual CPUs, you could run two sets of four virtual CPU guests and split the work between them, since each NUMA node only has four physical CPUs. Running across multiple NUMA nodes significantly degrades performance for physical and virtualized tasks.
+ </div><div class="formalpara"><h5 class="formalpara" id="idp14906944">Decide which NUMA node can run the guest</h5>
+ Locking a guest to a particular NUMA node offers no benefit if that node does not have sufficient free memory for that guest. libvirt stores information on the free memory available on each node. Use the <code class="command">virsh freecell --all</code> command to display the free memory on all NUMA nodes.
+ </div><pre class="screen"># virsh freecell --all
+0: 2203620 kB
+1: 3354784 kB</pre><div class="para">
+ If a guest requires 3 GB of RAM allocated, then the guest should be run on NUMA node (cell) 1. Node 0 only has 2.2GB free which may not be sufficient for certain guests.
+ </div><div class="formalpara"><h5 class="formalpara" id="idp4063904">Lock a guest to a NUMA node or physical CPU set</h5>
+ Once you have determined which node to run the guest on, refer to the capabilities data (the output of the <code class="command">virsh capabilities</code> command) about NUMA topology.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Extract from the <code class="command">virsh capabilities</code> output.
+ </div><pre class="screen"><topology>
+ <cells num='2'>
+ <cell id='0'>
+ <cpus num='4'>
+ <cpu id='0'/>
+ <cpu id='1'/>
+ <cpu id='2'/>
+ <cpu id='3'/>
+ </cpus>
+ </cell>
+ <cell id='1'>
+ <cpus num='4'>
+ <cpu id='4'/>
+ <cpu id='5'/>
+ <cpu id='6'/>
+ <cpu id='7'/>
+ </cpus>
+ </cell>
+ </cells>
+</topology></pre></li><li class="step"><div class="para">
+ Observe that the node 1, <code class="computeroutput"><cell id='1'></code>, uses physical CPUs 4 to 7.
+ </div></li><li class="step"><div class="para">
+ The guest can be locked to a set of CPUs by appending the <code class="computeroutput">cpuset</code> attribute to the configuration file.
+ </div><ol class="a"><li class="step"><div class="para">
+ While the guest is offline, open the configuration file with <code class="command">virsh edit</code>.
+ </div></li><li class="step"><div class="para">
+ Locate the guest's virtual CPU count, defined in the <code class="computeroutput">vcpus</code> element.
+ </div><pre class="screen"><vcpus>4</vcpus></pre><div class="para">
+ The guest in this example has four CPUs.
+ </div></li><li class="step"><div class="para">
+ Add a <code class="computeroutput">cpuset</code> attribute with the CPU numbers for the relevant NUMA cell.
+ </div><pre class="screen"><vcpus cpuset='4-7'>4</vcpus></pre></li></ol></li><li class="step"><div class="para">
+ Save the configuration file and restart the guest.
+ </div></li></ol></div><div class="para">
+ The guest has been locked to CPUs 4 to 7.
+ </div><div class="formalpara"><h5 class="formalpara" id="idp6583856">Automatically locking guests to CPUs with virt-install</h5>
+ The <code class="command">virt-install</code> provisioning tool provides a simple way to automatically apply a 'best fit' NUMA policy when guests are created.
+ </div><div class="para">
+ The <em class="parameter"><code>cpuset</code></em> option for <code class="command">virt-install</code> can use a CPU set of processors or the parameter <em class="parameter"><code>auto</code></em>. The <em class="parameter"><code>auto</code></em> parameter automatically determines the optimal CPU locking using the available NUMA data.
+ </div><div class="para">
+ For a NUMA system, use the <em class="parameter"><code>--cpuset=auto</code></em> with the <code class="command">virt-install</code> command when creating new guests.
+ </div><div class="formalpara"><h5 class="formalpara" id="idp16027600">Tuning CPU affinity on running guests</h5>
+ There may be times where modifying CPU affinities on running guests is preferable to rebooting the guest. The <code class="command">virsh vcpuinfo</code> and <code class="command">virsh vcpupin</code> commands can perform CPU affinity changes on running guests.
+ </div><div class="para">
+ The <code class="command">virsh vcpuinfo</code> command gives up to date information about where each virtual CPU is running.
+ </div><div class="para">
+ In this example, <em class="replaceable"><code>guest1</code></em> is a guest with four virtual CPUs is running on a KVM host.
+ </div><pre class="screen"># virsh vcpuinfo <em class="replaceable"><code>guest1</code></em>
+VCPU: 0
+CPU: 3
+State: running
+CPU time: 0.5s
+CPU Affinity: yyyyyyyy
+VCPU: 1
+CPU: 1
+State: running
+CPU Affinity: yyyyyyyy
+VCPU: 2
+CPU: 1
+State: running
+CPU Affinity: yyyyyyyy
+VCPU: 3
+CPU: 2
+State: running
+CPU Affinity: yyyyyyyy</pre><div class="para">
+ The <code class="command">virsh vcpuinfo</code> output (the <code class="computeroutput">yyyyyyyy</code> value of <code class="computeroutput">CPU Affinity</code>) shows that the guest can presently run on any CPU.
+ </div><div class="para">
+ To lock the virtual CPUs to the second NUMA node (CPUs four to seven), run the following commands.
+ </div><pre class="screen"># virsh vcpupin <em class="replaceable"><code>guest1</code></em> 0 4
+# virsh vcpupin <em class="replaceable"><code>guest1</code></em> 1 5
+# virsh vcpupin <em class="replaceable"><code>guest1</code></em> 2 6
+# virsh vcpupin <em class="replaceable"><code>guest1</code></em> 3 7</pre><div class="para">
+ The <code class="command">virsh vcpuinfo</code> command confirms the change in affinity.
+ </div><pre class="screen"># virsh vcpuinfo <em class="replaceable"><code>guest1</code></em>
+VCPU: 0
+CPU: 4
+State: running
+CPU time: 32.2s
+CPU Affinity: ----y---
+VCPU: 1
+CPU: 5
+State: running
+CPU time: 16.9s
+CPU Affinity: -----y--
+VCPU: 2
+CPU: 6
+State: running
+CPU time: 11.9s
+CPU Affinity: ------y-
+VCPU: 3
+CPU: 7
+State: running
+CPU time: 14.6s
+CPU Affinity: -------y</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions.html"><strong>Prev</strong>25.4. 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-Tips_and_tricks-Generating_a_new_unique_MAC_address.html"><strong>Next</strong>25.6. Generating a new unique MAC address</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch25s07.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch25s07.html
new file mode 100644
index 0000000..796936f
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch25s07.html
@@ -0,0 +1,42 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.7. Improving guest response time</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address.html" title="25.6. Generating a new unique MAC address" /><link rel="next" href="sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html" title="25.8. Disable SMART disk monitoring for guests" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-Tips_and_tricks-Generating_a_new_unique_MAC_address.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html"><strong>Next</strong></a></li></ul><div class="section" id="idp14241440"><div class="titlepage"><div><div><h2 class="title" id="idp14241440">25.7. Improving guest response time</h2></div></div></div><div class="para">
+ Guests can sometimes be slow to respond with certain workloads and usage patterns. Examples of situations which may cause slow or unresponsive guests:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Severely overcommitted memory.
+ </div></li><li class="listitem"><div class="para">
+ Overcommitted memory with high processor usage
+ </div></li><li class="listitem"><div class="para">
+ Other (not <code class="command">qemu-kvm</code> processes) busy or stalled processes on the host.
+ </div></li></ul></div><div class="para">
+ These types of workload may cause guests to appear slow or unresponsive. Usually, the guest's memory is eventually fully loaded into the host's main memory from swap. Once the guest is loaded in main memory, the guest will perform normally. Note, the process of loading a guest from swap to main memory may take several seconds per gigabyte of RAM assigned to the guest, depending on the type of storage used for swap and the performance of the components.
+ </div><div class="para">
+ KVM guests function as Linux processes. Linux processes are not permanently kept in main memory (physical RAM). The kernel scheduler swaps process memory into virtual memory (swap). Swap, with conventional hard disk drives, is thousands of times slower than main memory in modern computers. If a guest is inactive for long periods of time, the guest may be placed into swap by the kernel.
+ </div><div class="para">
+ KVM guests processes may be moved to swap regardless of whether memory is overcommitted or overall memory usage.
+ </div><div class="para">
+ Using unsafe overcommit levels or overcommitting with swap turned off guest processes or other critical processesis not recommended. Always ensure the host has sufficient swap space when overcommitting memory.
+ </div><div class="para">
+ For more information on overcommitting with KVM, refer to <a class="xref" href="sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM.html">Chapter 22, <em>Overcommitting with KVM</em></a>.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Virtual memory allows a Linux system to use more memory than there is physical RAM on the system. Underused processes are swapped out which allows active processes to use memory, improving memory utilization. Disabling swap reduces memory utilization as all processes are stored in physical RAM.
+ </div><div class="para">
+ If swap is turned off, do not overcommit guests. Overcommitting guests without any swap can cause guests or the host system to crash.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="idm14951168">Turning off swap</h5>
+ Swap usage can be completely turned off to prevent guests from being unresponsive while they are moved back to main memory. Swap may also not be desired for guests as it can be resource-intensive on some systems.
+ </div><div class="para">
+ The <code class="command">swapoff</code> command can disable all swap partitions and swap files on a system.
+ </div><pre class="screen"># swapoff -a</pre><div class="para">
+ To make this change permanent, remove <em class="parameter"><code>swap</code></em> lines from the <code class="filename">/etc/fstab</code> file and restart the host system.
+ </div><div class="formalpara"><h5 class="formalpara" id="idp3941488">Using SSDs for swap</h5>
+ Using Solid State Drives (SSDs) for swap storage may improve the performance of guests.
+ </div><div class="para">
+ Using RAID arrays, faster disks or separate drives dedicated to swap may also improve performance.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address.html"><strong>Prev</strong>25.6. 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-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html"><strong>Next</strong>25.8. Disable SMART disk monitoring for guests</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch29s02.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch29s02.html
new file mode 100644
index 0000000..49e70d3
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch29s02.html
@@ -0,0 +1,27 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>29.2. Configuration of vhostmd</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="vhostmd.html" title="Chapter 29. The Virtual Host Metrics Daemon (vhostmd)" /><link rel="prev" href="vhostmd.html" title="Chapter 29. The Virtual Host Metrics Daemon (vhostmd)" /><link rel="next" href="ch29s03.html" title="29.3. Starting and stopping the daemon" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="vhostmd.html"><strong>Prev</stro
ng></a></li><li class="next"><a accesskey="n" href="ch29s03.html"><strong>Next</strong></a></li></ul><div class="section" id="idp11335408"><div class="titlepage"><div><div><h2 class="title" id="idp11335408">29.2. Configuration of vhostmd</h2></div></div></div><div class="para">
+ After installing the package, but before starting the daemon, it is a good idea to understand exactly what metrics <span class="application"><strong>vhostmd</strong></span> will expose to guests, and how this happens.
+ </div><div class="para">
+ The metrics are controlled by the file <code class="filename">/etc/vhostmd/vhostmd.conf</code>.
+ </div><div class="para">
+ There are two parts of particular importance in this XML file. Firstly <em class="parameter"><code><update_period>60</update_period></code></em> controls how often the metrics are updated (in seconds). Since updating metrics can be an expensive operation, you can reduce the load on the host by increasing this period. Secondly, each <em class="parameter"><code><metric>...</metric></code></em> section controls what information is exposed by <span class="application"><strong>vhostmd</strong></span>. For example:
+ </div><pre class="screen"><metric type="string" context="host">
+ <name>HostName</name>
+ <action>hostname</action>
+</metric></pre><div class="para">
+ means that the hostname of the host is exposed to selected guests. To disable particular metrics, you can comment out <em class="parameter"><code><metric></code></em> sections by putting <code class="literal"><!-- ... --></code> around them. Note that disabling metrics may cause problems for guest software such as SAP that may rely on these metrics being available.
+ </div><div class="para">
+ When the daemon (also called <span class="application"><strong>vhostmd</strong></span>) is running, it writes the metrics into a temporary file called <code class="filename">/dev/shm/vhostmd0</code>. This file contains a small binary header followed by the selected metrics encoded as XML. In practice you can display this file with a tool like <span class="application"><strong>less</strong></span>. The file is updated every 60 seconds (or however often <em class="parameter"><code><update_period></code></em> was set).
+ </div><div class="para">
+ The vhostmd(8) man page contains a detailed description of the configuration file, as well as examples of the XML output in <code class="filename">/dev/shm/vhostmd0</code>. To read this, do:
+ </div><pre class="screen"># man vhostmd</pre><div class="para">
+ In addition, there is a README file which covers some of the same information:
+ </div><pre class="screen">less /usr/share/doc/vhostmd-*/README</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="vhostmd.html"><strong>Prev</strong>Chapter 29. The Virtual Host Metrics Daemon (vhos...</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="ch29s03.html"><strong>Next</strong>29.3. Starting and stopping the daemon</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch29s03.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch29s03.html
new file mode 100644
index 0000000..6091255
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch29s03.html
@@ -0,0 +1,18 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>29.3. Starting and stopping the daemon</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="vhostmd.html" title="Chapter 29. The Virtual Host Metrics Daemon (vhostmd)" /><link rel="prev" href="ch29s02.html" title="29.2. Configuration of vhostmd" /><link rel="next" href="ch29s04.html" title="29.4. Verifying that vhostmd is working from the host" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch29s02.html"><strong>Prev</strong></a></
li><li class="next"><a accesskey="n" href="ch29s04.html"><strong>Next</strong></a></li></ul><div class="section" id="idm8806976"><div class="titlepage"><div><div><h2 class="title" id="idm8806976">29.3. Starting and stopping the daemon</h2></div></div></div><div class="para">
+ The daemon (<span class="application"><strong>vhostmd</strong></span>) will not be started automatically. To enable it to be started at boot, run:
+ </div><pre class="screen"># /sbin/chkconfig vhostmd on</pre><div class="para">
+ To start the daemon running, do:
+ </div><pre class="screen"># /sbin/service vhostmd start</pre><div class="para">
+ To stop the daemon running, do:
+ </div><pre class="screen"># /sbin/service vhostmd stop</pre><div class="para">
+ To disable the daemon from being started at boot, do:
+ </div><pre class="screen"># /sbin/chkconfig vhostmd off</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch29s02.html"><strong>Prev</strong>29.2. Configuration of vhostmd</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="ch29s04.html"><strong>Next</strong>29.4. Verifying that vhostmd is working from the ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch29s04.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch29s04.html
new file mode 100644
index 0000000..288fecc
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch29s04.html
@@ -0,0 +1,19 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>29.4. Verifying that vhostmd is working from the host</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="vhostmd.html" title="Chapter 29. The Virtual Host Metrics Daemon (vhostmd)" /><link rel="prev" href="ch29s03.html" title="29.3. Starting and stopping the daemon" /><link rel="next" href="ch29s05.html" title="29.5. Configuring guests to see the metrics" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch29s03.html"><strong>Prev</strong></a></li
><li class="next"><a accesskey="n" href="ch29s05.html"><strong>Next</strong></a></li></ul><div class="section" id="idm3409840"><div class="titlepage"><div><div><h2 class="title" id="idm3409840">29.4. Verifying that vhostmd is working from the host</h2></div></div></div><div class="para">
+ A short time after the daemon has started, you should see a metrics disk appearing. Do:
+ </div><pre class="screen"># ls -l /dev/shm
+# less /dev/shm/vhostmd0</pre><div class="para">
+ This file has a short binary header, followed by XML. The <span class="application"><strong>less</strong></span> program identifies it as binary and asks:
+ </div><pre class="screen">"/dev/shm/vhostmd0" may be a binary file. See it anyway?</pre><div class="para">
+ Press the <span class="keycap"><strong>y</strong></span> key to indicate that you wish to view it.
+ </div><div class="para">
+ You should see the binary header appearing as garbled characters, followed by the <em class="parameter"><code><metrics></code></em> XML, and after that, many zero bytes (displayed as <code class="literal">^@^@^@</code>...).
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch29s03.html"><strong>Prev</strong>29.3. Starting and stopping the daemon</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="ch29s05.html"><strong>Next</strong>29.5. Configuring guests to see the metrics</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch29s05.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch29s05.html
new file mode 100644
index 0000000..ffde094
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch29s05.html
@@ -0,0 +1,41 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>29.5. Configuring guests to see the metrics</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="vhostmd.html" title="Chapter 29. The Virtual Host Metrics Daemon (vhostmd)" /><link rel="prev" href="ch29s04.html" title="29.4. Verifying that vhostmd is working from the host" /><link rel="next" href="ch29s06.html" title="29.6. Using vm-dump-metrics in Fedora guests to verify operation" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch29s04
.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch29s06.html"><strong>Next</strong></a></li></ul><div class="section" id="idp10914352"><div class="titlepage"><div><div><h2 class="title" id="idp10914352">29.5. Configuring guests to see the metrics</h2></div></div></div><div class="para">
+ Although metrics are written to <code class="filename">/dev/shm/vhostmd0</code>, they are not made available to guests by default. The administrator must choose which guests get to see metrics, and must manually change the configuration of selected guests to see metrics.
+ </div><div class="para">
+ The guest must be shut down before the disk is attached. (Hot attaching the metrics disk is also possible, but only for a limited number of guest configurations. In particular it is NOT possible to hot-add the metrics disk to guests that do not have virtio / PV drivers installed. See the vhostmd README file for more information).
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ It is extremely important that the metrics disk is added in readonly mode to all guests. If this is not done, then it would be possible for a guest to modify the metrics and possibly subvert other guests that are reading it.
+ </div></div></div><div class="procedure"><h6>Procedure 29.1. Configuring KVM guests</h6><ol class="1"><li class="step"><div class="para">
+ Shut down the guest.
+ </div></li><li class="step"><div class="para">
+ Do:
+ </div><pre class="screen"># virsh edit GuestName</pre><div class="para">
+ and add the following section into <em class="parameter"><code><devices></code></em>:
+ </div><pre class="screen"><disk type='file' device='disk'>
+ <driver name='qemu' type='raw'/>
+ <source file='/dev/shm/vhostmd0'/>
+ <target dev='vdd' bus='virtio'/>
+ <readonly/>
+ </disk></pre></li><li class="step"><div class="para">
+ Reboot the guest.
+ </div></li></ol></div><div class="procedure"><h6>Procedure 29.2. Configuring Xen guests</h6><ol class="1"><li class="step"><div class="para">
+ Shut down the guest.
+ </div></li><li class="step"><div class="para">
+ Do:
+ </div><pre class="screen"># virsh edit GuestName</pre><div class="para">
+ and add the following section into <em class="parameter"><code><devices></code></em>:
+ </div><pre class="screen"><disk type='file' device='disk'>
+ <source dev='/dev/shm/vhostmd0'/>
+ <target dev='hdd' bus='ide'/>
+ <readonly/>
+ </disk></pre></li><li class="step"><div class="para">
+ Reboot the guest.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch29s04.html"><strong>Prev</strong>29.4. Verifying that vhostmd is working from the ...</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="ch29s06.html"><strong>Next</strong>29.6. Using vm-dump-metrics in Fedora guests to v...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch29s06.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch29s06.html
new file mode 100644
index 0000000..d8fc23d
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/ch29s06.html
@@ -0,0 +1,24 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>29.6. Using vm-dump-metrics in Fedora guests to verify operation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="vhostmd.html" title="Chapter 29. The Virtual Host Metrics Daemon (vhostmd)" /><link rel="prev" href="ch29s05.html" title="29.5. Configuring guests to see the metrics" /><link rel="next" href="pt03.html" title="Part III. Appendicies" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch29s05.html"><strong>Prev</strong></a></li><li class="next"><
a accesskey="n" href="pt03.html"><strong>Next</strong></a></li></ul><div class="section" id="idp28420096"><div class="titlepage"><div><div><h2 class="title" id="idp28420096">29.6. Using vm-dump-metrics in Fedora guests to verify operation</h2></div></div></div><div class="para">
+ Optionally, the <span class="package">vm-dump-metrics</span> package from the RHN Downloads area may be installed in Fedora guests. This package provides a simple command line tool (also called <span class="application"><strong>vm-dump-metrics</strong></span>) which allows host metrics to be displayed in the guest.
+ </div><div class="para">
+ This is useful for verifying correct operation of <span class="application"><strong>vhostmd</strong></span> from a guest.
+ </div><div class="para">
+ In the guest, run the following command as root:
+ </div><pre class="screen"># vm-dump-metrics</pre><div class="para">
+ If everything is working, this should print out a long XML document starting with <code class="literal"><metrics></code>.
+ </div><div class="para">
+ If this does not work, then verify that the metrics disk has appeared in the guest. It should appear as <code class="filename">/dev/vd*</code> (for example, <code class="filename">/dev/vdb</code>, <code class="filename">/dev/vdd</code>).
+ </div><div class="para">
+ On the host, verify that the libvirt configuration changes have been made by using the command:
+ </div><pre class="screen"># virsh dumpxml GuestName</pre><div class="para">
+ Verify that vhostmd is running on the host and the /dev/shm/vhostmd0 file exists.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch29s05.html"><strong>Prev</strong>29.5. Configuring guests to see the metrics</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="pt03.html"><strong>Next</strong>Part III. Appendicies</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-KSM.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-KSM.html
new file mode 100644
index 0000000..fe85a06
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-KSM.html
@@ -0,0 +1,101 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 23. KSM</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt02.html" title="Part II. Administration" /><link rel="prev" href="sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM.html" title="Chapter 22. Overcommitting with KVM" /><link rel="next" href="chap-Virtualization_Administration_GuideAdvanced.html" title="Chapter 24. Advanced virtualization administration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-Tips_and_tricks-Overcommitting_with_KVM.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_GuideAdvanced.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-KSM" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 23. KSM</h2></div></div></div><div class="para">
+ The concept of shared memory is common in modern operating systems. For example, when a program is first started it shares all of its memory with the parent program. When either the child or parent program tries to modify this memory, the kernel allocates a new memory region, copies the original contents and allows the program to modify this new region. This is known as copy on write.
+ </div><div class="para">
+ KSM is a new Linux feature which uses this concept in reverse. KSM enables the kernel to examine two or more already running programs and compare their memory. If any memory regions or pages are identical, KSM reduces multiple identical memory pages to a single page. This page is then marked copy on write. If the contents of the page is modified by a guest, a new page is created for that guest.
+ </div><div class="para">
+ This is useful for virtualization with KVM. When a guest is started, it only inherits the memory from the parent <code class="systemitem">qemu-kvm</code> process. Once the guest is running the contents of the guest operating system image can be shared when guests are running the same operating system or applications. KSM only identifies and merges identical pages which does not interfere with the guest or impact the security of the host or the guests. KSM allows KVM to request that these identical guest memory regions be shared.
+ </div><div class="para">
+ KSM provides enhanced memory speed and utilization. With KSM, common process data is stored in cache or in main memory. This reduces cache misses for the KVM guests which can improve performance for some applications and operating systems. Secondly, sharing memory reduces the overall memory usage of guests which allows for higher densities and greater utilization of resources.
+ </div><div class="para">
+ Starting in Fedora 18, KSM is NUMA aware
+ </div><div class="para">
+ Fedora uses two separate methods for controlling KSM:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <code class="systemitem">ksm</code> service starts and stops the KSM kernel thread.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="systemitem">ksmtuned</code> service controls and tunes the <code class="systemitem">ksm</code>, dynamically managing same-page merging. The <code class="systemitem">ksmtuned</code> service starts <code class="systemitem">ksm</code> and stops the <code class="systemitem">ksm</code> service if memory sharing is not necessary. The <code class="systemitem">ksmtuned</code> service must be told with the <em class="parameter"><code>retune</code></em> parameter to run when new guests are created or destroyed.
+ </div></li></ul></div><div class="para">
+ Both of these services are controlled with the standard service management tools.
+ </div><div class="formalpara"><h5 class="formalpara" id="idp26726816">The KSM service</h5>
+ The <code class="systemitem">ksm</code> service is included in the <span class="package">qemu-kvm</span> package. KSM is off by default on Fedora. When using Fedora as a KVM host, however, it is likely turned on by the <code class="systemitem">ksm/ksmtuned</code> services.
+ </div><div class="para">
+ When the <code class="systemitem">ksm</code> service is not started, KSM shares only 2000 pages. This default is low and provides limited memory saving benefits.
+ </div><div class="para">
+ When the <code class="systemitem">ksm</code> service is started, KSM will share up to half of the host system's main memory. Start the <code class="systemitem">ksm</code> service to enable KSM to share more memory.
+ </div><pre class="screen"># service ksm start
+Starting ksm: [ OK ]</pre><div class="para">
+ The <code class="systemitem">ksm</code> service can be added to the default startup sequence. Make the <code class="systemitem">ksm</code> service persistent with the chkconfig command.
+ </div><pre class="screen"># chkconfig ksm on</pre><div class="formalpara"><h5 class="formalpara" id="idm18385648">The KSM tuning service</h5>
+ The <code class="systemitem">ksmtuned</code> service does not have any options. The <code class="systemitem">ksmtuned</code> service loops and adjusts <code class="systemitem">ksm</code>. The <code class="systemitem">ksmtuned</code> service is notified by libvirt when a guest is created or destroyed.
+ </div><pre class="screen"># service ksmtuned start
+Starting ksmtuned: [ OK ]</pre><div class="para">
+ The <code class="systemitem">ksmtuned</code> service can be tuned with the <em class="parameter"><code>retune</code></em> parameter. The <em class="parameter"><code>retune</code></em> parameter instructs <code class="systemitem">ksmtuned</code> to run tuning functions manually.
+ </div><div class="para">
+ The <code class="filename">/etc/ksmtuned.conf</code> file is the configuration file for the <code class="systemitem">ksmtuned</code> service. The file output below is the default <code class="filename">ksmtuned.conf</code> file.
+ </div><pre class="screen"># Configuration file for ksmtuned.
+
+# How long ksmtuned should sleep between tuning adjustments
+# KSM_MONITOR_INTERVAL=60
+
+# Millisecond sleep between ksm scans for 16Gb server.
+# Smaller servers sleep more, bigger sleep less.
+# KSM_SLEEP_MSEC=10
+
+# KSM_NPAGES_BOOST=300
+# KSM_NPAGES_DECAY=-50
+# KSM_NPAGES_MIN=64
+# KSM_NPAGES_MAX=1250
+
+# KSM_THRES_COEF=20
+# KSM_THRES_CONST=2048
+
+# uncomment the following to enable ksmtuned debug information
+# LOGFILE=/var/log/ksmtuned
+# DEBUG=1
+</pre><div class="formalpara"><h5 class="formalpara" id="idp4047872">KSM variables and monitoring</h5>
+ KSM stores monitoring data in the <code class="filename">/sys/kernel/mm/ksm/</code> directory. Files in this directory are updated by the kernel and are an accurate record of KSM usage and statistics.
+ </div><div class="para">
+ The variables in the list below are also configurable variables in the <code class="filename">/etc/ksmtuned.conf</code> file as noted below.
+ </div><div class="variablelist"><h6>The <code class="filename">/sys/kernel/mm/ksm/</code> files</h6><dl class="variablelist"><dt class="varlistentry"><span class="term">full_scans</span></dt><dd><div class="para">
+ Full scans run.
+ </div></dd><dt class="varlistentry"><span class="term">pages_shared</span></dt><dd><div class="para">
+ Total pages shared.
+ </div></dd><dt class="varlistentry"><span class="term">pages_sharing</span></dt><dd><div class="para">
+ Pages presently shared.
+ </div></dd><dt class="varlistentry"><span class="term">pages_to_scan</span></dt><dd><div class="para">
+ Pages not scanned.
+ </div></dd><dt class="varlistentry"><span class="term">pages_unshared</span></dt><dd><div class="para">
+ Pages no longer shared.
+ </div></dd><dt class="varlistentry"><span class="term">pages_volatile</span></dt><dd><div class="para">
+ Number of volatile pages.
+ </div></dd><dt class="varlistentry"><span class="term">run</span></dt><dd><div class="para">
+ Whether the KSM process is running.
+ </div></dd><dt class="varlistentry"><span class="term">sleep_millisecs</span></dt><dd><div class="para">
+ Sleep milliseconds.
+ </div></dd></dl></div><div class="para">
+ KSM tuning activity is stored in the <code class="filename">/var/log/ksmtuned</code> log file if the <em class="parameter"><code>DEBUG=1</code></em> line is added to the <code class="filename">/etc/ksmtuned.conf</code> file. The log file location can be changed with the <em class="parameter"><code>LOGFILE</code></em> parameter. Changing the log file location is not advised and may require special configuration of SELinux settings.
+ </div><div class="formalpara"><h5 class="formalpara" id="idp14236112">Deactivating KSM</h5>
+ KSM has a performance overhead which may be too large for certain environments or host systems.
+ </div><div class="para">
+ KSM can be deactivated by stopping the <code class="systemitem">ksmtuned</code> and the <code class="systemitem">ksm</code> service. Stopping the services deactivates KSM but does not persist after restarting.
+ </div><pre class="screen">
+# service ksmtuned stop
+Stopping ksmtuned: [ OK ]
+# service ksm stop
+Stopping ksm: [ OK ]
+
+</pre><div class="para">
+ Persistently deactivate KSM with the <code class="command">chkconfig</code> command. To turn off the services, run the following commands:
+ </div><pre class="screen"># chkconfig ksm off
+# chkconfig ksmtuned off</pre><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Ensure the swap size is sufficient for the committed RAM even with KSM. KSM reduces the RAM usage of identical or similar guests. Overcommitting guests with KSM without sufficient swap space may be possible but is not recommended because guest memory use can result in pages becoming unshared.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM.html"><strong>Prev</strong>Chapter 22. 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="chap-Virtualization_Administration_GuideAdvanced.html"><strong>Next</strong>Chapter 24. Advanced virtualization administration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization-Security_for_virtualization.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization-Security_for_virtualization.html
new file mode 100644
index 0000000..e996188
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization-Security_for_virtualization.html
@@ -0,0 +1,26 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 18. Security for virtualization</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt02.html" title="Part II. Administration" /><link rel="prev" href="chap-Virtualization_Administration_Guide-Server_best_practices.html" title="Chapter 17. Server best practices" /><link rel="next" href="sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization.html" title="18.2. SELinux and virtualization" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="pr
evious"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Server_best_practices.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization-Security_for_virtualization" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 18. Security for virtualization</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization-Security_for_virtualization.html#sect-Virtualization-Security_for_virtualization-Storage_security_issues">18.1. Storage security issues</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization.html">18.2. SELinux and virtualization</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Security_for_virtualization-SELinux_co
nsiderations.html">18.3. SELinux</a></span></dt><dt><span class="section"><a href="ch18s04.html">18.4. Virtualization firewall information</a></span></dt></dl></div><div class="para">
+ When deploying virtualization technologies, you must ensure that the host cannot be compromised. The host is a Fedora system that manages the system, devices, memory and networks as well as all virtualized guests. If the host is insecure, all guests 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 class="listitem"><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 class="listitem"><div class="para">
+ Enable SELinux on the hypervisor. Read <a class="xref" href="sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization.html">Section 18.2, “SELinux and virtualization”</a> for more information on using SELinux and virtualization.
+ </div></li><li class="listitem"><div class="para">
+ Use a firewall to restrict traffic to the host. You can setup a firewall with default-reject rules that will help secure the host from attacks. It is also important to limit network-facing services.
+ </div></li><li class="listitem"><div class="para">
+ Do not allow normal users to access the host. The host is privileged, and granting access to unprivileged accounts may compromise the level of security.
+ </div></li></ul></div><div class="section" id="sect-Virtualization-Security_for_virtualization-Storage_security_issues"><div class="titlepage"><div><div><h2 class="title">18.1. Storage security issues</h2></div></div></div><div class="para">
+ Administrators of virtualized guests can change the partitions the host boots in certain circumstances. To prevent this administrators should follow these recommendations:
+ </div><div class="para">
+ The host should not use disk labels to identify file systems in the <code class="filename">fstab</code> file, the <code class="filename">initrd</code> file or used by the kernel command line. If less privileged users, especially virtualized guests, have write access to whole partitions or LVM volumes.
+ </div><div class="para">
+ Guests should not be given write access to whole disks or block devices (for example, <code class="filename">/dev/sdb</code>). Use partitions (for example, <code class="filename">/dev/sdb1</code>) or LVM volumes.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Server_best_practices.html"><strong>Prev</strong>Chapter 17. 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-Security_for_virtualization-SELinux_and_virtualization.html"><strong>Next</strong>18.2. SELinux and virtualization</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html
new file mode 100644
index 0000000..7415030
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html
@@ -0,0 +1,34 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix G. Guest disk access with offline tools</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt03.html" title="Part III. Appendicies" /><link rel="prev" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO.html" title="F.11. Displaying Network I/O" /><link rel="next" href="sect-Terminology-Guest_Disks_libguestfs.html" title="G.2. Terminology" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accessk
ey="p" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Terminology-Guest_Disks_libguestfs.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="appendix" id="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Guest disk access with offline tools</h1></div></div></div><div class="section" id="sect-introduction-Virtualization_Administration_Guide-Guest_Disks_libguestfs"><div class="titlepage"><div><div><h2 class="title">G.1. Introduction</h2></div></div></div><div class="para">
+ Fedora comes with tools to access, edit and create guest disks or other disk images. There are several uses for these tools, including:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Viewing or downloading files located on a guest disk.
+ </div></li><li class="listitem"><div class="para">
+ Editing or uploading files onto a guest disk.
+ </div></li><li class="listitem"><div class="para">
+ Reading or writing guest configuration.
+ </div></li><li class="listitem"><div class="para">
+ Reading or writing the Windows Registry in Windows guests.
+ </div></li><li class="listitem"><div class="para">
+ Preparing new disk images containing files, directories, file systems, partitions, logical volumes and other options.
+ </div></li><li class="listitem"><div class="para">
+ Rescuing and repairing guests that fail to boot or those that need boot configuration changes.
+ </div></li><li class="listitem"><div class="para">
+ Monitoring disk usage of guests.
+ </div></li><li class="listitem"><div class="para">
+ Auditing compliance of guests, for example to organizational security standards.
+ </div></li><li class="listitem"><div class="para">
+ Deploying guests by cloning and modifying templates.
+ </div></li><li class="listitem"><div class="para">
+ Reading CD and DVD ISO and floppy disk images.
+ </div></li></ul></div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ You must <span class="bold bold"><strong>never</strong></span> use these tools to write to a guest or disk image which is attached to a running virtual machine, not even to open such a disk image in write mode. Doing so will result in disk corruption of the guest. The tools try to prevent you from doing this, however do not catch all cases. If there is any suspicion that a guest might be running, it is strongly recommended that the tools not be used, or at least <span class="bold bold"><strong>always</strong></span> use the tools in read-only mode.
+ </div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO.html"><strong>Prev</strong>F.11. Displaying Network I/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-Terminology-Guest_Disks_libguestfs.html"><strong>Next</strong>G.2. Terminology</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-KVM_live_migration.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-KVM_live_migration.html
new file mode 100644
index 0000000..9b485e0
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-KVM_live_migration.html
@@ -0,0 +1,64 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 20. KVM live migration</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt02.html" title="Part II. Administration" /><link rel="prev" href="ch19s02.html" title="19.2. sVirt labeling" /><link rel="next" href="Live_migration_and_RHEL_compatibility.html" title="20.2. Live migration and Fedora version compatibility" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s02.html"><strong>Prev</strong></a></li><li class=
"next"><a accesskey="n" href="Live_migration_and_RHEL_compatibility.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_Guide-KVM_live_migration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 20. KVM live migration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-KVM_live_migration.html#Live_migration_requirements">20.1. Live migration requirements</a></span></dt><dt><span class="section"><a href="Live_migration_and_RHEL_compatibility.html">20.2. Live migration and Fedora version compatibility </a></span></dt><dt><span class="section"><a href="shared-storage-nfs-migration.html">20.3. Shared storage example: NFS for a simple migration</a></span></dt><dt><span class="section"><a href="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html">20.4. Live KVM migration with virsh</a></span></dt><dd><dl
><dt><span class="section"><a href="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html#add-notes">20.4.1. Additonal tips for migration with virsh </a></span></dt><dt><span class="section"><a href="virsh-migration-arguements.html">20.4.2. Additional options for the virsh migrate command</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager.html">20.5. 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 describes the process of moving a guest from one host to another. This is possible because guests are running in a virtualized environment instead of directly on the hardware. Migration is useful for:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Load balancing - guests can be moved to hosts with lower usage when their host becomes overloaded, or another host is under-utilized.
+ </div></li><li class="listitem"><div class="para">
+ Hardware independence - when we need to upgrade, add, or remove hardware devices on the host, we can safely relocate guests to other hosts. This means that guests do not experience any downtime for hardware improvements.
+ </div></li><li class="listitem"><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 class="listitem"><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">
+ Migration works by sending the state of the guest's memory and any virtualized devices to a destination host. It is recommended to use shared, networked storage to store guest images to be migrated. It is also recommended to libvirt-managed storage pools for shared storage when migrating virtual machines.
+ </div><div class="para">
+ Migrations can be performed live or not.
+ </div><div class="para">
+ In a live migration, the guest continues to run on the source host while its memory pages are transferred, in order, to the destination host. During migration, KVM monitors the source for any changes in pages it has already transferred, and begins to transfer these changes when all of the initial pages have been transferred. KVM also estimates transfer speed during migration, so when the remaining amount of data to transfer will take a certain configurable period of time (10ms by default), KVM suspends the original guest, transfers the remaining data, and resumes the guest on the destination host.
+ </div><div class="para">
+ A migration that is not performed live, suspends the guest, then moves an image of the guest's memory to the destination host. The guest is then resumed on the destination host and the memory the guest used on the source host is freed. The time it takes to complete such a migration depends on network bandwidth and latency. If the network is experiencing heavy use or low bandwidth, the migration will take much longer.
+ </div><div class="para">
+ If the original guest modifies pages faster than KVM can transfer them to the destination host, offline migration must be used, as live migration would never complete.
+ </div><div class="section" id="Live_migration_requirements"><div class="titlepage"><div><div><h2 class="title">20.1. Live migration requirements</h2></div></div></div><div class="para">
+ Migrating guests requires the following:
+ </div><div class="itemizedlist" id="item-Virtualization-Live_migration_requirements-Migration_requirements"><h6>Migration requirements</h6><ul><li class="listitem"><div class="para">
+ A guest installed on shared storage using one of the following protocols:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Fibre Channel-based LUNs
+ </div></li><li class="listitem"><div class="para">
+ iSCSI
+ </div></li><li class="listitem"><div class="para">
+ FCoE
+ </div></li><li class="listitem"><div class="para">
+ NFS
+ </div></li><li class="listitem"><div class="para">
+ GFS2
+ </div></li><li class="listitem"><div class="para">
+ SCSI RDMA protocols (SCSI RCP): the block export protocol used in Infiniband and 10GbE iWARP adapters
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Both systems must have the appropriate TCP/IP ports open.
+ </div></li><li class="listitem"><div class="para">
+ A separate system exporting the shared storage medium. Storage should not reside on either of the two hosts being used for migration.
+ </div></li><li class="listitem"><div class="para">
+ Shared storage must mount at the same location on source and destination systems. The mounted directory names must be identical. Although it is possible to keep the images using different paths, it is not recommended. Note that, if you are intending to use virt-manager to perform the migration, the path names must be identical. If however you intend to use virsh to perform the migration, different network configurations and mount directories can be used with the help of --xml option or pre-hooks when doing migrations. Even with out shared storage, migration can still succeed with the command <code class="command">--copy-storage-all</code>. For more information on <code class="command">prehooks</code>, refer to <a href="http://www.libvirt.org/hooks.html"> libvirt.org</a>, and for more information on the XML option, see the virsh manual.
+ </div></li><li class="listitem"><div class="para">
+ When migration is attempted on an existing guest in a public bridge+tap network, the source and destination hosts must be located in the same network. Otherwise, the guest network will not operate after migration.
+ </div></li></ul></div><div class="para">
+ Make sure that the <code class="filename">libvirtd</code> service is enabled (<code class="command"># chkconfig libvirtd on</code>) and running (<code class="command"># service libvirtd start</code>). It is also important to note that the ability to migrate effectively is dependent on the parameter settings in the <code class="filename">/etc/libvirt/libvirtd.conf</code> configuration file.
+ </div><div class="procedure" id="change-libvirt-config"><h6>Procedure 20.1. Configuring libvirtd.conf</h6><ol class="1"><li class="step"><div class="para">
+ Opening the <code class="filename">libvirtd.conf</code> requires running the command as root:
+ </div><pre class="screen"># vim /etc/libvirt/libvirtd.conf</pre></li><li class="step"><div class="para">
+ Change the parameters as needed and save the file.
+ </div></li><li class="step"><div class="para">
+ Restart the <code class="filename">libvirtd</code> service:
+ </div><pre class="screen"># service libvirtd restart</pre></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s02.html"><strong>Prev</strong>19.2. sVirt labeling</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="Live_migration_and_RHEL_compatibility.html"><strong>Next</strong>20.2. Live migration and Fedora version compatibi...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html
new file mode 100644
index 0000000..5d08d3b
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html
@@ -0,0 +1,38 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix F. Managing guests with the Virtual Machine Manager (virt-manager)</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt03.html" title="Part III. Appendicies" /><link rel="prev" href="apes14s04.html" title="E.14.4. Configuring the guest CPU model" /><link rel="next" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html" title="F.2. The Virtual Machine Manager main window" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li
class="previous"><a accesskey="p" href="apes14s04.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="appendix" id="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Managing guests with the Virtual Machine Manager (virt-manager)</h1></div></div></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 guests on your host system and on remote host systems. <code class="command">virt-manager</code> can perform virtualization management tasks, including:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ defining and creating guests,
+ </div></li><li class="listitem"><div class="para">
+ assigning memory,
+ </div></li><li class="listitem"><div class="para">
+ assigning virtual CPUs,
+ </div></li><li class="listitem"><div class="para">
+ monitoring operational performance,
+ </div></li><li class="listitem"><div class="para">
+ saving and restoring, pausing and resuming, and shutting down and starting guests,
+ </div></li><li class="listitem"><div class="para">
+ links to the textual and graphical consoles, and
+ </div></li><li class="listitem"><div class="para">
+ live and offline migrations.
+ </div></li></ul></div><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Starting_virt_manager"><div class="titlepage"><div><div><h2 class="title">F.1. 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_Administration_Guide-Starting_virt_manager-Starting_virt_manager"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt1.png" width="444" alt="Starting virt-manager" /></div></div><h6>Figure F.1. 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:
+ </div><pre class="screen">ssh -X <em class="replaceable"><code>host's address</code></em>
+[remotehost]# virt-manager
+</pre><div class="para">
+ Using <code class="command">ssh</code> to manage virtual machines and hosts is discussed further in <a class="xref" href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html#sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_with_SSH">Section 21.1, “Remote management with SSH”</a>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apes14s04.html"><strong>Prev</strong>E.14.4. Configuring the guest CPU model</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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html"><strong>Next</strong>F.2. The Virtual Machine Manager main window</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html
new file mode 100644
index 0000000..4ee470a
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html
@@ -0,0 +1,400 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix E. Managing guests with virsh</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt03.html" title="Part III. Appendicies" /><link rel="prev" href="apds10.html" title="D.10. Miscellaneous options" /><link rel="next" href="sect-Attaching_and_updating_a_device_with_virsh.html" title="E.2. Attaching and updating a device with virsh" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apds10.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="sect-Attaching_and_updating_a_device_with_virsh.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="appendix" id="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Managing guests with virsh</h1></div></div></div><div class="para">
+ <code class="command">virsh</code> is a command line interface tool for managing guests and the hypervisor. The <code class="command">virsh</code> command-line tool is built on the <code class="command">libvirt</code> management API and operates as an alternative to the <code class="command">qemu-kvm</code> command and the graphical <code class="command">virt-manager</code> application. The <code class="command">virsh</code> command can be used in read-only mode by unprivileged users or, with root access, full administration functionality. The <code class="command">virsh</code> command is ideal for scripting virtualization administration.
+ </div><div class="section" id="idm20931200"><div class="titlepage"><div><div><h2 class="title" id="idm20931200">E.1. virsh command quick reference</h2></div></div></div><div class="para">
+ The following tables provide a quick reference for all virsh command line options.
+ </div><div class="table" id="tabl-Virtualization-Managing_guests_with_virsh-Guest_management_commands"><h6>Table E.1. Guest management commands</h6><div class="table-contents"><table summary="Guest management commands" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">help</code>
+ </td><td class="">
+ Prints basic help information.
+ </td></tr><tr><td class="">
+ <code class="command">list</code>
+ </td><td class="">
+ Lists all guests.
+ </td></tr><tr><td class="">
+ <code class="command">dumpxml</code>
+ </td><td class="">
+ Outputs the XML configuration file for the guest.
+ </td></tr><tr><td class="">
+ <code class="command">create</code>
+ </td><td class="">
+ Creates a guest from an XML configuration file and starts the new guest.
+ </td></tr><tr><td class="">
+ <code class="command">start</code>
+ </td><td class="">
+ Starts an inactive guest.
+ </td></tr><tr><td class="">
+ <code class="command">destroy</code>
+ </td><td class="">
+ Forces a guest to stop.
+ </td></tr><tr><td class="">
+ <code class="command">define</code>
+ </td><td class="">
+ Creates a guest from an XML configuration file without starting the new guest.
+ </td></tr><tr><td class="">
+ <code class="command">domid</code>
+ </td><td class="">
+ Displays the guest's ID.
+ </td></tr><tr><td class="">
+ <code class="command">domuuid</code>
+ </td><td class="">
+ Displays the guest's UUID.
+ </td></tr><tr><td class="">
+ <code class="command">dominfo</code>
+ </td><td class="">
+ Displays guest information.
+ </td></tr><tr><td class="">
+ <code class="command">domname</code>
+ </td><td class="">
+ Displays the guest's name.
+ </td></tr><tr><td class="">
+ <code class="command">domstate</code>
+ </td><td class="">
+ Displays the state of a guest.
+ </td></tr><tr><td class="">
+ <code class="command">quit</code>
+ </td><td class="">
+ Quits the interactive terminal.
+ </td></tr><tr><td class="">
+ <code class="command">reboot</code>
+ </td><td class="">
+ Reboots a guest.
+ </td></tr><tr><td class="">
+ <code class="command">restore</code>
+ </td><td class="">
+ Restores a previously saved guest stored in a file.
+ </td></tr><tr><td class="">
+ <code class="command">resume</code>
+ </td><td class="">
+ Resumes a paused guest.
+ </td></tr><tr><td class="">
+ <code class="command">save</code>
+ </td><td class="">
+ Saves the present state of a guest to a file.
+ </td></tr><tr><td class="">
+ <code class="command">shutdown</code>
+ </td><td class="">
+ Gracefully shuts down a guest.
+ </td></tr><tr><td class="">
+ <code class="command">suspend</code>
+ </td><td class="">
+ Pauses a guest.
+ </td></tr><tr><td class="">
+ <code class="command">undefine</code>
+ </td><td class="">
+ Deletes all files associated with a guest.
+ </td></tr><tr><td class="">
+ <code class="command">migrate</code>
+ </td><td class="">
+ Migrates a guest to another host.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The following <code class="command">virsh</code> command options manage guest and hypervisor resources:
+ </div><div class="table" id="tabl-Virtualization-Managing_guests_with_virsh-Resource_management_options"><h6>Table E.2. Resource management options</h6><div class="table-contents"><table summary="Resource management options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">setmem</code>
+ </td><td class="">
+ Sets the allocated memory for a guest. Refer to the <code class="command">virsh</code> manpage for more details.
+ </td></tr><tr><td class="">
+ <code class="command">setmaxmem</code>
+ </td><td class="">
+ Sets maximum memory limit for the hypervisor. Refer to the <code class="command">virsh</code> manpage for more details.
+ </td></tr><tr><td class="">
+ <code class="command">setvcpus</code>
+ </td><td class="">
+ Changes number of virtual CPUs assigned to a guest. Refer to the <code class="command">virsh</code> manpage for more details.
+ </td></tr><tr><td class="">
+ <code class="command">vcpuinfo</code>
+ </td><td class="">
+ Displays virtual CPU information about a guest.
+ </td></tr><tr><td class="">
+ <code class="command">vcpupin</code>
+ </td><td class="">
+ Controls the virtual CPU affinity of a guest.
+ </td></tr><tr><td class="">
+ <code class="command">domblkstat</code>
+ </td><td class="">
+ Displays block device statistics for a running guest.
+ </td></tr><tr><td class="">
+ <code class="command">domifstat</code>
+ </td><td class="">
+ Displays network interface statistics for a running guest.
+ </td></tr><tr><td class="">
+ <code class="command">attach-device</code>
+ </td><td class="">
+ Attach a device to a guest, using a device definition in an XML file.
+ </td></tr><tr><td class="">
+ <code class="command">attach-disk</code>
+ </td><td class="">
+ Attaches a new disk device to a guest.
+ </td></tr><tr><td class="">
+ <code class="command">attach-interface</code>
+ </td><td class="">
+ Attaches a new network interface to a guest.
+ </td></tr><tr><td class="">
+ <code class="command">update-device</code>
+ </td><td class="">
+ Detaches a disk image from a guest's CD-ROM drive. See <a class="xref" href="sect-Attaching_and_updating_a_device_with_virsh.html">Section E.2, “Attaching and updating a device with virsh”</a> for more details.
+ </td></tr><tr><td class="">
+ <code class="command">detach-device</code>
+ </td><td class="">
+ Detaches a device from a guest, takes the same kind of XML descriptions as command <code class="command">attach-device</code>.
+ </td></tr><tr><td class="">
+ <code class="command">detach-disk</code>
+ </td><td class="">
+ Detaches a disk device from a guest.
+ </td></tr><tr><td class="">
+ <code class="command">detach-interface</code>
+ </td><td class="">
+ Detach a network interface from a guest.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The <code class="command">virsh</code> commands for managing and creating storage pools and volumes.
+ </div><div class="para">
+ For more information on using storage pools with virsh, refer to <a href="http://libvirt.org/formatstorage.html">http://libvirt.org/formatstorage.html</a>
+ </div><div class="table" id="tabl-Virtualization-Managing_gunagement_options"><h6>Table E.3. Storage Pool options</h6><div class="table-contents"><table summary="Storage Pool options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">find-storage-pool-sources</code>
+ </td><td class="">
+ Returns the XML definition for all storage pools of a given type that could be found.
+ </td></tr><tr><td class="">
+ <code class="command">find-storage-pool-sources</code> <em class="parameter"><code>host port</code></em>
+ </td><td class="">
+ Returns data on all storage pools of a given type that could be found as XML. If the host and port are provided, this command can be run remotely.
+ </td></tr><tr><td class="">
+ <code class="command">pool-autostart </code>
+ </td><td class="">
+ Sets the storage pool to start at boot time.
+ </td></tr><tr><td class="">
+ <code class="command">pool-build</code>
+ </td><td class="">
+ The <code class="command">pool-build</code> command builds a defined pool. This command can format disks and create partitions.
+ </td></tr><tr><td class="">
+ <code class="command">pool-create</code>
+ </td><td class="">
+ <code class="command">pool-create</code> creates and starts a storage pool from the provided XML storage pool definition file.
+ </td></tr><tr><td class="">
+ <code class="command">pool-create-as name</code>
+ </td><td class="">
+ Creates and starts a storage pool from the provided parameters. If the <em class="parameter"><code>--print-xml</code></em> parameter is specified, the command prints the XML definition for the storage pool without creating the storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-define</code>
+ </td><td class="">
+ Creates a storage bool from an XML definition file but does not start the new storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-define-as name</code>
+ </td><td class="">
+ Creates but does not start, a storage pool from the provided parameters. If the <em class="parameter"><code>--print-xml</code></em> parameter is specified, the command prints the XML definition for the storage pool without creating the storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-destroy</code>
+ </td><td class="">
+ Permanently destroys a storage pool in <code class="command">libvirt</code>. The raw data contained in the storage pool is not changed and can be recovered with the <code class="command">pool-create</code> command.
+ </td></tr><tr><td class="">
+ <code class="command">pool-delete</code>
+ </td><td class="">
+ Destroys the storage resources used by a storage pool. This operation cannot be recovered. The storage pool still exists after this command but all data is deleted.
+ </td></tr><tr><td class="">
+ <code class="command">pool-dumpxml</code>
+ </td><td class="">
+ Prints the XML definition for a storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-edit</code>
+ </td><td class="">
+ Opens the XML definition file for a storage pool in the users default text editor.
+ </td></tr><tr><td class="">
+ <code class="command">pool-info</code>
+ </td><td class="">
+ Returns information about a storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-list</code>
+ </td><td class="">
+ Lists storage pools known to libvirt. By default, <code class="command">pool-list</code> lists pools in use by active guests. The <em class="parameter"><code>--inactive</code></em> parameter lists inactive pools and the <em class="parameter"><code>--all</code></em> parameter lists all pools.
+ </td></tr><tr><td class="">
+ <code class="command">pool-undefine</code>
+ </td><td class="">
+ Deletes the definition for an inactive storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-uuid</code>
+ </td><td class="">
+ Returns the UUID of the named pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-name </code>
+ </td><td class="">
+ Prints a storage pool's name when provided the UUID of a storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-refresh</code>
+ </td><td class="">
+ Refreshes the list of volumes contained in a storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-start</code>
+ </td><td class="">
+ Starts a storage pool that is defined but inactive.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><h6>Table E.4. Volume options</h6><div class="table-contents"><table summary="Volume options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">vol-create</code>
+ </td><td class="">
+ Create a volume from an XML file.
+ </td></tr><tr><td class="">
+ <code class="command">vol-create-from</code>
+ </td><td class="">
+ Create a volume using another volume as input.
+ </td></tr><tr><td class="">
+ <code class="command">vol-create-as</code>
+ </td><td class="">
+ Create a volume from a set of arguments.
+ </td></tr><tr><td class="">
+ <code class="command">vol-clone</code>
+ </td><td class="">
+ Clone a volume.
+ </td></tr><tr><td class="">
+ <code class="command">vol-delete</code>
+ </td><td class="">
+ Delete a volume.
+ </td></tr><tr><td class="">
+ <code class="command">vol-wipe</code>
+ </td><td class="">
+ Wipe a volume.
+ </td></tr><tr><td class="">
+ <code class="command">vol-dumpxml</code>
+ </td><td class="">
+ Show volume information in XML.
+ </td></tr><tr><td class="">
+ <code class="command">vol-info</code>
+ </td><td class="">
+ Show storage volume information.
+ </td></tr><tr><td class="">
+ <code class="command">vol-list</code>
+ </td><td class="">
+ List volumes.
+ </td></tr><tr><td class="">
+ <code class="command">vol-pool</code>
+ </td><td class="">
+ Returns the storage pool for a given volume key or path.
+ </td></tr><tr><td class="">
+ <code class="command">vol-path</code>
+ </td><td class="">
+ Returns the volume path for a given volume name or key.
+ </td></tr><tr><td class="">
+ <code class="command">vol-name</code>
+ </td><td class="">
+ Returns the volume name for a given volume key or path.
+ </td></tr><tr><td class="">
+ <code class="command">vol-key</code>
+ </td><td class="">
+ Returns the volume key for a given volume name or path.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><h6>Table E.5. Secret options</h6><div class="table-contents"><table summary="Secret options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">secret-define</code>
+ </td><td class="">
+ Define or modify a secret from an XML file.
+ </td></tr><tr><td class="">
+ <code class="command">secret-dumpxml</code>
+ </td><td class="">
+ Show secret attributes in XML.
+ </td></tr><tr><td class="">
+ <code class="command">secret-set-value</code>
+ </td><td class="">
+ Set a secret value.
+ </td></tr><tr><td class="">
+ <code class="command">secret-get-value</code>
+ </td><td class="">
+ Output a secret value.
+ </td></tr><tr><td class="">
+ <code class="command">secret-undefine</code>
+ </td><td class="">
+ Undefine a secret.
+ </td></tr><tr><td class="">
+ <code class="command">secret-list</code>
+ </td><td class="">
+ List secrets.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><h6>Table E.6. Network filter options</h6><div class="table-contents"><table summary="Network filter options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">nwfilter-define</code>
+ </td><td class="">
+ Define or update a network filter from an XML file.
+ </td></tr><tr><td class="">
+ <code class="command">nwfilter-undefine</code>
+ </td><td class="">
+ Undefine a network filter.
+ </td></tr><tr><td class="">
+ <code class="command">nwfilter-dumpxml</code>
+ </td><td class="">
+ Show network filter information in XML.
+ </td></tr><tr><td class="">
+ <code class="command">nwfilter-list</code>
+ </td><td class="">
+ List network filters.
+ </td></tr><tr><td class="">
+ <code class="command">nwfilter-edit</code>
+ </td><td class="">
+ Edit XML configuration for a network filter.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ This table contains <code class="command">virsh</code> command options for snapshots:
+ </div><div class="table"><h6>Table E.7. Snapshot options</h6><div class="table-contents"><table summary="Snapshot options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">snapshot-create</code>
+ </td><td class="">
+ Create a snapshot.
+ </td></tr><tr><td class="">
+ <code class="command">snapshot-current</code>
+ </td><td class="">
+ Get the current snapshot.
+ </td></tr><tr><td class="">
+ <code class="command">snapshot-delete</code>
+ </td><td class="">
+ Delete a domain snapshot.
+ </td></tr><tr><td class="">
+ <code class="command">snapshot-dumpxml</code>
+ </td><td class="">
+ Dump XML for a domain snapshot.
+ </td></tr><tr><td class="">
+ <code class="command">snapshot-list</code>
+ </td><td class="">
+ List snapshots for a domain.
+ </td></tr><tr><td class="">
+ <code class="command">snapshot-revert</code>
+ </td><td class="">
+ Revert a domain to a snapshot.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ This table contains miscellaneous <code class="command">virsh</code> commands:
+ </div><div class="table" id="tabl-Virtualization-Managing_guests_with_virsh-Miscellaneous_options"><h6>Table E.8. Miscellaneous options</h6><div class="table-contents"><table summary="Miscellaneous options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">version</code>
+ </td><td class="">
+ Displays the version of <code class="command">virsh</code>.
+ </td></tr><tr><td class="">
+ <code class="command">nodeinfo</code>
+ </td><td class="">
+ Outputs information about the hypervisor.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apds10.html"><strong>Prev</strong>D.10. Miscellaneous options</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-Attaching_and_updating_a_device_with_virsh.html"><strong>Next</strong>E.2. Attaching and updating a device with virsh</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html
new file mode 100644
index 0000000..392d176
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html
@@ -0,0 +1,22 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix D. qemu-kvm Whitelist</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt03.html" title="Part III. Appendicies" /><link rel="prev" href="netkvm-parameters.html" title="Appendix C. NetKVM Driver Parameters" /><link rel="next" href="apds02.html" title="D.2. Basic options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="netkvm-parameters.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="a
pds02.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="appendix" id="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist" lang="en-US"><div class="titlepage"><div><div><h1 class="title">qemu-kvm Whitelist</h1></div></div></div><div class="section" id="idp5322656"><div class="titlepage"><div><div><h2 class="title" id="idp5322656">D.1. Introduction</h2></div></div></div><h4 id="idm11282912">Product identification</h4><div class="para">
+ Fedora
+ </div><h4 id="idm11213536">Objectives</h4><div class="para">
+ The primary objective of this whitelist is to provide a complete list of the supported options of the <code class="command">qemu-kvm</code> utility used as an emulator and a virtualizer in Fedora. This is a comprehensive summary of the supported options.
+ </div><h4 id="idm11673728">Background</h4><div class="para">
+ Fedora uses KVM as an underlying virtualization technology. The machine emulator and virtualizer used is a modified version of QEMU called qemu-kvm. This version does not support all configuration options of the original QEMU and it adds some additional options.
+ </div><h4 id="idp6206624">Scope of the chapter</h4><h4 id="idm7580416">Used format</h4><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong><name></strong></span> - When used in a syntax description, this string shoud be replaced by user-defined value.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>[a|b|c]</strong></span> - When used in a syntax description, only one of the strings separated by | is used.
+ </div></li><li class="listitem"><div class="para">
+ When no comment is present, an option is supported with all possible values.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="netkvm-parameters.html"><strong>Prev</strong>Appendix C. NetKVM Driver Parameters</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="apds02.html"><strong>Next</strong>D.2. Basic options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html
new file mode 100644
index 0000000..2801087
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html
@@ -0,0 +1,76 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 21. Remote management of guests</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt02.html" title="Part II. Administration" /><link rel="prev" href="sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager.html" title="20.5. Migrating with virt-manager" /><link rel="next" href="sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html" title="21.2. Remote management over TLS and SSL" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-KVM_live_migration-Migrating_with_virt_manager.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 21. Remote management of guests</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html#sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_with_SSH">21.1. Remote management with SSH</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_
TLS_and_SSL.html">21.2. Remote management over TLS and SSL</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes.html">21.3. Transport modes</a></span></dt></dl></div><div class="para">
+ This section explains how to remotely manage your guests using <code class="command">ssh</code> or TLS and SSL. More information on SSH can be found in the <em class="citetitle">Fedora Deployment Guide</em>
+ </div><div class="section" id="sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_with_SSH"><div class="titlepage"><div><div><h2 class="title">21.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 is tunneled over <span class="application"><strong>SSH</strong></span>.
+ </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><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ you require root log in access to the remote machine for managing virtual machines,
+ </div></li><li class="listitem"><div class="para">
+ the initial connection setup process may be slow,
+ </div></li><li class="listitem"><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 class="listitem"><div class="para">
+ ssh does not scale well with larger numbers of remote machines.
+ </div></li></ul></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Fedora enables remote management of large numbers of virtual machines. Refer to the oVirt documentation for further details.
+ </div></div></div><div class="para">
+ The following packages are required for ssh access:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="package">openssh</span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">openssh-askpass</span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">openssh-clients</span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">openssh-server</span>
+ </div></li></ul></div><div class="formalpara" id="form-Virtualization-Remote_management_with_SSH-Configuring_SSH_access_for_virt_manager"><h5 class="formalpara">Configuring password less or password managed <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. If you have SSH keys set up and copied to the other systems you can skip this procedure.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ SSH keys are user dependent and may only be used by their owners. A key's owner is the one who generated it. Keys may not be shared.
+ </div><div class="para">
+ <code class="command">virt-manager</code> must be run by the user who owns the keys to connect to the remote host. That means, if the remote systems are managed by a non-root user <code class="command">virt-manager</code> must be run in unprivileged mode. If the remote systems are managed by the local root user then the SSH keys must be owned and created by root.
+ </div><div class="para">
+ You cannot manage the local host as an unprivileged user with <code class="command">virt-manager</code>.
+ </div></div></div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Optional: Changing user</strong></p><div class="para">
+ Change user, if required. This example uses the local root user for remotely managing the other hosts and the local host.
+ </div><pre class="screen">$<code class="command"> su -</code></pre></li><li class="step"><p class="title"><strong>Generating the SSH key pair</strong></p><div class="para">
+ Generate a public key pair on the machine <code class="command">virt-manager</code> is used. This example uses the default key location, in the <code class="filename">~/.ssh/</code> directory.
+ </div><pre class="screen"># <code class="command">ssh-keygen -t rsa</code></pre></li><li class="step"><p class="title"><strong>Copying the keys to the remote hosts</strong></p><div class="para">
+ Remote login without a password, or with a passphrase, requires an SSH key to be distributed to the systems being managed. Use the <code class="command">ssh-copy-id</code> command to copy the key to root user at the system address provided (in the example, <em class="parameter"><code>root at host2.example.com</code></em>).
+ </div><pre class="screen"># <code class="command">ssh-copy-id -i ~/.ssh/id_rsa.pub root at host2.example.com</code>
+root at host2.example.com's password:
+</pre><div class="para">
+ Now try logging into the machine, with the <code class="command">ssh root at host2.example.com</code> command and check in the <code class="filename">.ssh/authorized_keys</code> file to make sure unexpected keys have not been added.
+ </div><div class="para">
+ Repeat for other systems, as required.
+ </div></li><li class="step"><p class="title"><strong>Optional: Add the passphrase to the ssh-agent</strong></p><div class="para">
+ The instructions below describe how to add a passphrase to an existing ssh-agent. It will fail to run if the ssh-agent is not running. To avoid errors or conflicts make sure that your SSH parameters are set correctly. Refer to the <em class="citetitle">Fedora Deployment Guide</em> for more information.
+ </div><div class="para">
+ Add the passphrase for the SSH key to the <code class="command">ssh-agent</code>, if required. On the local host, use the following command to add the passphrase (if there was one) to enable password-less login.
+ </div><pre class="screen"># <code class="command">ssh-add ~/.ssh/id_rsa.pub</code></pre><div class="para">
+ The SSH key is added to the remote system.
+ </div></li></ol></div><div class="formalpara" id="form-Virtualization-Remote_management_with_SSH-The_libvirt_daemon_libvirtd"><h5 class="formalpara">The <code class="command">libvirt</code> daemon (<code class="systemitem">libvirtd</code>)</h5>
+ The <code class="systemitem">libvirt</code> daemon provides an interface for managing virtual machines. You must have the <code class="systemitem">libvirtd</code> daemon installed and running on every remote host that needs managing.
+ </div><pre class="screen">$ <code class="command">ssh root@<em class="replaceable"><code>somehost</code></em></code>
+<code class="command"># chkconfig libvirtd on</code>
+<code class="command"># service libvirtd start</code></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 class="formalpara" id="form-Virtualization-Remote_management_with_SSH-Accessing_remote_hosts_with_virt_manager"><h5 class="formalpara">Accessing remote hosts with virt-manager</h5>
+ Remote hosts can be managed with the virt-manager GUI tool. SSH keys must belong to the user executing virt-manager for password-less login to work.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Start virt-manager.
+ </div></li><li class="step"><div class="para">
+ Open the <span class="guimenuitem"><strong>File</strong></span>-><span class="guimenuitem"><strong>Add Connection</strong></span> menu.
+ </div><div class="figure" id="add-connection"><div class="figure-contents"><div class="mediaobject"><img src="images/Virt-Manager-Add-Connection.png" alt="Add connection menu" /></div></div><h6>Figure 21.1. Add connection menu</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Use the drop down menu to select hypervisor type, and click the <span class="guimenuitem"><strong>Connect to remote host</strong></span> check box to open the Connection <span class="guimenuitem"><strong>Method</strong></span> (in this case Remote tunnel over SSH), and enter the desired <span class="guimenuitem"><strong>User name</strong></span> and <span class="guimenuitem"><strong>Hostname</strong></span>, then click <span class="guimenuitem"><strong>Connect</strong></span>.
+ </div></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager.html"><strong>Prev</strong>20.5. 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-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html"><strong>Next</strong>21.2. Remote management over TLS and SSL</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Server_best_practices.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Server_best_practices.html
new file mode 100644
index 0000000..0886f40
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Server_best_practices.html
@@ -0,0 +1,23 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 17. Server best practices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt02.html" title="Part II. Administration" /><link rel="prev" href="pt02.html" title="Part II. Administration" /><link rel="next" href="chap-Virtualization-Security_for_virtualization.html" title="Chapter 18. Security for virtualization" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pt02.html"><strong>Prev</strong></a></li><li class="next
"><a accesskey="n" href="chap-Virtualization-Security_for_virtualization.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_Guide-Server_best_practices" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 17. 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 host.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Run SELinux in enforcing mode. Set SELinux to run in enforcing mode with the <code class="command">setenforce</code> command.
+ </div><pre class="screen"># setenforce 1
+</pre></li><li class="listitem"><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 class="listitem"><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 class="listitem"><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 class="listitem"><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. Use of shareable, network storage in a central location is highly recommended.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pt02.html"><strong>Prev</strong>Part II. 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-Security_for_virtualization.html"><strong>Next</strong>Chapter 18. Security for virtualization</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Storage_Concepts.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Storage_Concepts.html
new file mode 100644
index 0000000..ab2be50
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Storage_Concepts.html
@@ -0,0 +1,30 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 26. Storage concepts</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt02.html" title="Part II. Administration" /><link rel="prev" href="sect-dynamic-vNIC.html" title="25.16. Dynamically changing a host or a network bridge that is attached to a virtual NIC" /><link rel="next" href="sect-Virtualization-Storage_Concepts-Volumes.html" title="26.2. Volumes" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-dyn
amic-vNIC.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Storage_Concepts-Volumes.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_Guide-Storage_Concepts" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 26. Storage concepts</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Concepts.html#sect-Virtualization-Storage_Concepts-Storage_Pools">26.1. Storage pools</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Storage_Concepts-Volumes.html">26.2. Volumes </a></span></dt></dl></div><div class="para">
+ This chapter introduces the concepts used for describing and managing storage devices. Terms such as Storage Pools and Volumes are explained in the sections that follow.
+ </div><div class="section" id="sect-Virtualization-Storage_Concepts-Storage_Pools"><div class="titlepage"><div><div><h2 class="title">26.1. Storage pools</h2></div></div></div><div class="para">
+ A <em class="firstterm">storage pool</em> is a file, directory, or storage device managed by libvirt for the purpose of providing storage to guests. The storage pool can be local or it can be shared over a network.
+ </div><div class="para">
+ libvirt uses a directory-based storage pool, the <code class="filename">/var/lib/libvirt/images/</code> directory, as the default storage pool. The default storage pool can be changed to another storage pool.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Local storage pools</strong></span> - Local storage pools are directly attached to the host server. Local storage pools include: local directories, directly attached disks, physical partitions, and LVM volume groups. These storage volumes store guest images or are attached to guests as additional storage. As local storage pools are directly attached to the host server, they are useful for development, testing and small deployments that do not require migration or large numbers of guests. Local storage pools are not suitable for many production environments as local storage pools do not support live migration.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Networked (shared) storage pools</strong></span> - Networked storage pools include storage devices shared over a network using standard protocols. Networked storage is required when migrating virtual machines between hosts with virt-manager, but is optional when migrating with virsh. Networked storage pools are managed by libvirt. Supported protocols for networked storage pools include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Fibre Channel-based LUNs
+ </div></li><li class="listitem"><div class="para">
+ iSCSI
+ </div></li><li class="listitem"><div class="para">
+ NFS
+ </div></li><li class="listitem"><div class="para">
+ GFS2
+ </div></li><li class="listitem"><div class="para">
+ SCSI RDMA protocols (SCSI RCP), the block export protocol used in InfiniBand and 10GbE iWARP adapters.
+ </div></li></ul></div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-dynamic-vNIC.html"><strong>Prev</strong>25.16. Dynamically changing a host or a network b...</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-Storage_Concepts-Volumes.html"><strong>Next</strong>26.2. Volumes </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html
new file mode 100644
index 0000000..faa4f65
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html
@@ -0,0 +1,793 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 27. Storage pools</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt02.html" title="Part II. Administration" /><link rel="prev" href="sect-Virtualization-Storage_Concepts-Volumes.html" title="26.2. Volumes" /><link rel="next" href="chap-Virtualization_Administration_Guide-Storage_Volumes.html" title="Chapter 28. Volumes" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-Storage_Concepts
-Volumes.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_Guide-Storage_Volumes.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 27. Storage pools</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating_Storage_Pools">27.1. Creating storage pools </a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-Dedicated_Disk_Devices">27.1.1. Disk-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-
Virtualization-Storage_Pools-Creating-File_Systems">27.1.2. Partition-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-Local_Directories">27.1.3. Directory-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-LVM">27.1.4. LVM-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-iSCSI">27.1.5. iSCSI-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-NFS">27.1.6. NFS-based storage pools</a></span></dt></dl></dd></dl></div><div class="para">
+ This chapter includes instructions on creating storage pools of assorted types. A <em class="firstterm">storage pool</em> is a quantity of storage set aside by an administrator, often a dedicated storage administrator, for use by virtual machines. Storage pools are often divided into storage volumes either by the storage administrator or the system administrator, and the volumes are assigned to guest virtual machines as block devices.
+ </div><div class="example"><h6>Example 27.1. NFS storage pool</h6><div class="example-contents"><div class="para">
+ Suppose a storage administrator responsible for an NFS server creates a share to store guest virtual machines' data. The system administrator defines a pool on the host with the details of the share (nfs.example.com:<code class="filename">/path/to/share</code> should be mounted on <code class="filename">/vm_data</code>). When the pool is started, libvirt mounts the share on the specified directory, just as if the system administrator logged in and executed <code class="command">mount nfs.example.com:/path/to/share /vmdata</code>. If the pool is configured to autostart, libvirt ensures that the NFS share is mounted on the directory specified when libvirt is started.
+ </div><div class="para">
+ Once the pool starts, the files that the NFS share, are reported as volumes, and the storage volumes' paths are then queried using the libvirt APIs. The volumes' paths can then be copied into the section of a guest virtual machine's XML definition file describing the source storage for the guest virtual machine's block devices. With NFS, applications using the libvirt APIs can create and delete volumes in the pool (files within the NFS share) up to the limit of the size of the pool (the maximum storage capacity of the share). Not all pool types support creating and deleting volumes. Stopping the pool negates the start operation, in this case, unmounts the NFS share. The data on the share is not modified by the destroy operation, despite the name. See man virsh for more details.
+ </div></div></div><br class="example-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Storage pools and volumes are not required for the proper operation of guest virtual machines. Pools and volumes provide a way for libvirt to ensure that a particular piece of storage will be available for a guest virtual machine, but some administrators will prefer to manage their own storage and guest virtual machines will operate properly without any pools or volumes defined. On systems that do not use pools, system administrators must ensure the availability of the guest virtual machines' storage using whatever tools they prefer, for example, adding the NFS share to the host's fstab so that the share is mounted at boot time.
+ </div></div></div><div class="section" id="sect-Virtualization-Storage_Pools-Creating_Storage_Pools"><div class="titlepage"><div><div><h2 class="title">27.1. Creating storage pools </h2></div></div></div><div xml:lang="en-US" class="section" id="sect-Virtualization-Storage_Pools-Creating-Dedicated_Disk_Devices" lang="en-US"><div class="titlepage"><div><div><h3 class="title">27.1.1. Disk-based storage pools</h3></div></div></div><div class="para">
+ This section covers creating disk based storage devices for guest virtual machines.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Guests should not be given write access to whole disks or block devices (for example, <code class="filename">/dev/sdb</code>). Use partitions (for example, <code class="filename">/dev/sdb1</code>) or LVM volumes.
+ </div><div class="para">
+ If you pass an entire block device to the guest, the guest will likely partition it or create its own LVM groups on it. This can cause the host to detect these partitions or LVM groups and cause errors.
+ </div></div></div><div class="section" id="idp6530752"><div class="titlepage"><div><div><h4 class="title" id="idp6530752">27.1.1.1. Creating a disk based storage pool using virsh</h4></div></div></div><div class="para">
+ This procedure creates a new storage pool using a disk device with the <code class="command">virsh</code> command.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Dedicating a disk to a storage pool will reformat and erase all data presently stored on the disk device! It is strongly recommended to back up the storage device before commencing with the following procedure:
+ </div></div></div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong> Create a GPT disk label on the disk </strong></p><div class="para">
+ The disk must be relabeled with a <em class="firstterm">GUID Partition Table</em> (GPT) disk label. GPT disk labels allow for creating a large numbers of partitions, up to 128 partitions, on each device. GPT partition tables can store partition data for far more partitions than the MS-DOS partition table.
+ </div><pre class="screen"># parted /dev/sdb
+GNU Parted 2.1
+Using /dev/sdb
+Welcome to GNU Parted! Type 'help' to view a list of commands.
+(parted) mklabel
+New disk label type? gpt
+(parted) quit
+Information: You may need to update /etc/fstab.
+#
+</pre></li><li class="step"><p class="title"><strong>Create the storage pool configuration file</strong></p><div class="para">
+ Create a temporary XML text file containing the storage pool information required for the new device.
+ </div><div class="para">
+ The file must be in the format shown below, and contain the following fields:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><name>guest_images_disk</name></span></dt><dd><div class="para">
+ The <em class="parameter"><code>name</code></em> parameter determines the name of the storage pool. This example uses the name <em class="replaceable"><code>guest_images_disk</code></em> in the example below.
+ </div></dd><dt class="varlistentry"><span class="term"> <device path='<em class="replaceable"><code>/dev/sdb</code></em>'/></span></dt><dd><div class="para">
+ The <em class="parameter"><code>device</code></em> parameter with the <em class="parameter"><code>path</code></em> attribute specifies the device path of the storage device. This example uses the device <em class="replaceable"><code>/dev/sdb</code></em>.
+ </div></dd><dt class="varlistentry"><span class="term"><target> <path><em class="replaceable"><code>/dev</code></em></path></target></span></dt><dd><div class="para">
+ The file system <em class="parameter"><code>target</code></em> parameter with the <em class="parameter"><code>path</code></em> sub-parameter determines the location on the host file system to attach volumes created with this storage pool.
+ </div><div class="para">
+ For example, sdb1, sdb2, sdb3. Using <em class="replaceable"><code>/dev/</code></em>, as in the example below, means volumes created from this storage pool can be accessed as <em class="replaceable"><code>/dev</code></em>/sdb1, <em class="replaceable"><code>/dev</code></em>/sdb2, <em class="replaceable"><code>/dev</code></em>/sdb3.
+ </div></dd><dt class="varlistentry"><span class="term"><format type='<em class="replaceable"><code>gpt</code></em>'/></span></dt><dd><div class="para">
+ The <em class="parameter"><code>format</code></em> parameter specifies the partition table type. This example uses the <em class="replaceable"><code>gpt</code></em> in the example below, to match the GPT disk label type created in the previous step.
+ </div></dd></dl></div><div class="para">
+ Create the XML file for the storage pool device with a text editor.
+ </div><div class="example"><h6>Example 27.2. Disk based storage device storage pool</h6><div class="example-contents"><pre class="screen">
+<pool type='disk'>
+ <name><em class="replaceable"><code>guest_images_disk</code></em></name>
+ <source>
+ <device path='<em class="replaceable"><code>/dev/sdb</code></em>'/>
+ <format type='<em class="replaceable"><code>gpt</code></em>'/>
+ </source>
+ <target>
+ <path><em class="replaceable"><code>/dev</code></em></path>
+ </target>
+</pool>
+</pre></div></div><br class="example-break" /></li><li class="step"><p class="title"><strong>Attach the device</strong></p><div class="para">
+ Add the storage pool definition using the <code class="command">virsh pool-define</code> command with the XML configuration file created in the previous step.
+ </div><pre class="screen"># virsh pool-define ~/guest_images_disk.xml
+Pool guest_images_disk defined from /root/guest_images_disk.xml
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_disk inactive no
+</pre></li><li class="step"><p class="title"><strong>Start the storage pool</strong></p><div class="para">
+ Start the storage pool with the <code class="command">virsh pool-start</code> command. Verify the pool is started with the <code class="command">virsh pool-list --all</code> command.
+ </div><pre class="screen"># virsh pool-start <em class="replaceable"><code>guest_images_disk</code></em>
+Pool guest_images_disk started
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_disk active no
+</pre></li><li class="step"><p class="title"><strong>Turn on autostart</strong></p><div class="para">
+ Turn on <em class="parameter"><code>autostart</code></em> for the storage pool. Autostart configures the <code class="systemitem">libvirtd</code> service to start the storage pool when the service starts.
+ </div><pre class="screen"># virsh pool-autostart <em class="replaceable"><code>guest_images_disk</code></em>
+Pool guest_images_disk marked as autostarted
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_disk active yes
+</pre></li><li class="step"><p class="title"><strong>Verify the storage pool configuration</strong></p><div class="para">
+ Verify the storage pool was created correctly, the sizes reported correctly, and the state reports as <code class="computeroutput">running</code>.
+ </div><pre class="screen"># virsh pool-info <em class="replaceable"><code>guest_images_disk</code></em>
+Name: guest_images_disk
+UUID: 551a67c8-5f2a-012c-3844-df29b167431c
+State: running
+Capacity: 465.76 GB
+Allocation: 0.00
+Available: 465.76 GB
+# ls -la /dev/sdb
+brw-rw----. 1 root disk 8, 16 May 30 14:08 /dev/sdb
+# virsh vol-list guest_images_disk
+Name Path
+-----------------------------------------
+</pre></li><li class="step"><p class="title"><strong>Optional: Remove the temporary configuration file</strong></p><div class="para">
+ Remove the temporary storage pool XML configuration file if it is not needed.
+ </div><pre class="screen"># rm ~/<em class="replaceable"><code>guest_images_disk</code></em>.xml</pre></li></ol></div><div class="para">
+ A disk based storage pool is now available.
+ </div></div><div class="section" id="delete-ded-disk-storage-pool"><div class="titlepage"><div><div><h4 class="title">27.1.1.2. Deleting a storage pool using virsh</h4></div></div></div><div class="para">
+ The following demonstrates how to delete a storage pool using virsh:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it.
+ </div><pre class="screen"># virsh pool-destroy <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Remove the storage pool's definition
+ </div><pre class="screen"># virsh pool-undefine <em class="replaceable"><code>guest_images_disk</code></em></pre></li></ol></div></div></div><div xml:lang="en-US" class="section" id="sect-Virtualization-Storage_Pools-Creating-File_Systems" lang="en-US"><div class="titlepage"><div><div><h3 class="title">27.1.2. Partition-based storage pools</h3></div></div></div><div class="para">
+ This section covers using a pre-formatted block device, a partition, as a storage pool.
+ </div><div class="para">
+ For the following examples, a host has a 500GB hard drive (<code class="systemitem">/dev/sdc</code>) partitioned into one 500GB, ext4 formatted partition (<code class="systemitem">/dev/sdc1</code>). We set up a storage pool for it using the procedure below.
+ </div><div class="section" id="create-part-stor-pool"><div class="titlepage"><div><div><h4 class="title">27.1.2.1. Creating a partition-based storage pool using virt-manager</h4></div></div></div><div class="para">
+ This procedure creates a new storage pool using a partition of a storage device.
+ </div><div class="procedure"><h6>Procedure 27.1. Creating a partition-based storage pool with virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Open the storage pool settings</strong></p><ol class="a"><li class="step"><div class="para">
+ In the <code class="command">virt-manager</code> graphical interface, select the host from the main window.
+ </div><div class="para">
+ Open the <span class="guilabel"><strong>Edit</strong></span> menu and select <span class="guilabel"><strong>Connection Details</strong></span>
+ </div><div class="figure" id="connection_details"><div class="figure-contents"><div class="mediaobject"><img src="images/Connection_Details.png" width="444" alt="Connection Details" /></div></div><h6>Figure 27.1. Connection Details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Click on the <span class="guilabel"><strong>Storage</strong></span> tab of the <span class="guilabel"><strong>Connection Details</strong></span> window.
+ </div><div class="figure" id="storage-tab"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Storage tab" /></div></div><h6>Figure 27.2. Storage tab</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Create the new storage pool</strong></p><ol class="a"><li class="step"><p class="title"><strong>Add a new pool (part 1)</strong></p><div class="para">
+ Press the <span class="guilabel"><strong>+</strong></span> button (the add pool button). The <span class="guilabel"><strong>Add a New Storage Pool</strong></span> wizard appears.
+ </div><div class="para">
+ Choose a <span class="guibutton"><strong>Name</strong></span> for the storage pool. This example uses the name <em class="replaceable"><code>guest_images_fs</code></em>. Change the <span class="guibutton"><strong>Type</strong></span> to <code class="command">fs: Pre-Formatted Block Device</code>.
+ </div><div class="figure" id="name-and-type"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_fs_step_1_name_and_type.png" width="444" alt="Storage pool name and type" /></div></div><h6>Figure 27.3. Storage pool name and type</h6></div><br class="figure-break" /><div class="para">
+ Press the <span class="guibutton"><strong>Forward</strong></span> button to continue.
+ </div></li><li class="step"><p class="title"><strong>Add a new pool (part 2)</strong></p><div class="para">
+ Change the <span class="guibutton"><strong>Target Path</strong></span>, <span class="guibutton"><strong>Format</strong></span>, and <span class="guibutton"><strong>Source Path</strong></span> fields.
+ </div><div class="figure" id="path-and-format"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_fs_step_2_paths_and_format.png" width="444" alt="Storage pool path and format" /></div></div><h6>Figure 27.4. Storage pool path and format</h6></div><br class="figure-break" /><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Target Path</span></dt><dd><div class="para">
+ Enter the location to mount the source device for the storage pool in the <span class="guibutton"><strong>Target Path</strong></span> field. If the location does not already exist, <code class="command">virt-manager</code> will create the directory.
+ </div></dd><dt class="varlistentry"><span class="term">Format</span></dt><dd><div class="para">
+ Select a format from the <span class="guibutton"><strong>Format</strong></span> list. The device is formatted with the selected format.
+ </div><div class="para">
+ This example uses the <em class="replaceable"><code>ext4</code></em> file system, the default Fedora file system.
+ </div></dd><dt class="varlistentry"><span class="term">Source Path</span></dt><dd><div class="para">
+ Enter the device in the <code class="command">Source Path</code> field.
+ </div><div class="para">
+ This example uses the <em class="replaceable"><code>/dev/sdc1</code></em> device.
+ </div></dd></dl></div><div class="para">
+ Verify the details and press the <span class="guibutton"><strong>Finish</strong></span> button to create the storage pool.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Verify the new storage pool</strong></p><div class="para">
+ The new storage pool appears in the storage list on the left after a few seconds. Verify the size is reported as expected, <em class="replaceable"><code>458.20 GB Free</code></em> in this example. Verify the <span class="guibutton"><strong>State</strong></span> field reports the new storage pool as <em class="replaceable"><code>Active</code></em>.
+ </div><div class="para">
+ Select the storage pool. In the <span class="guibutton"><strong>Autostart</strong></span> field, click the <span class="guibutton"><strong>On Boot</strong></span> checkbox. This will make sure the storage device starts whenever the <code class="systemitem">libvirtd</code> service starts.
+ </div><div class="figure" id="confirmation"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_fs_step_3_result.png" width="444" alt="Storage list confirmation" /></div></div><h6>Figure 27.5. Storage list confirmation</h6></div><br class="figure-break" /><div class="para">
+ The storage pool is now created, close the <span class="guilabel"><strong>Connection Details</strong></span> window.
+ </div></li></ol></div></div><div class="section" id="del-stor-pool-vmana-part"><div class="titlepage"><div><div><h4 class="title">27.1.2.2. Deleting a storage pool using virt-manager</h4></div></div></div><div class="para">
+ This procedure demonstrates how to delete a storage pool.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it. To do this, select the storage pool you want to stop and click the red X icon at the bottom of the Storage window.
+ </div><div class="figure" id="stop-icon"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Stop Icon" /></div></div><h6>Figure 27.6. Stop Icon</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Delete the storage pool by clicking the Trash can icon. This icon is only enabled if you stop the storage pool first.
+ </div></li></ol></div></div><div class="section" id="idp7336928"><div class="titlepage"><div><div><h4 class="title" id="idp7336928">27.1.2.3. Creating a partition-based storage pool using virsh</h4></div></div></div><div class="para">
+ This section covers creating a partition-based storage pool with the <code class="command">virsh</code> command.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Do not use this procedure to assign an entire disk as a storage pool (for example, <code class="filename">/dev/sdb</code>). Guests should not be given write access to whole disks or block devices. Only use this method to assign partitions (for example, <code class="filename">/dev/sdb1</code>) to storage pools.
+ </div></div></div><div class="procedure"><h6>Procedure 27.2. Creating pre-formatted block device storage pools using virsh</h6><ol class="1"><li class="step"><p class="title"><strong> Create the storage pool definition </strong></p><div class="para">
+ Use the virsh <code class="command">pool-define-as</code> command to create a new storage pool definition. There are three options that must be provided to define a pre-formatted disk as a storage pool:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Partition name</span></dt><dd><div class="para">
+ The <em class="parameter"><code>name</code></em> parameter determines the name of the storage pool. This example uses the name <em class="replaceable"><code>guest_images_fs</code></em> in the example below.
+ </div></dd><dt class="varlistentry"><span class="term">device</span></dt><dd><div class="para">
+ The <em class="parameter"><code>device</code></em> parameter with the <em class="parameter"><code>path</code></em> attribute specifies the device path of the storage device. This example uses the partition <em class="replaceable"><code>/dev/sdc1</code></em>.
+ </div></dd><dt class="varlistentry"><span class="term">mountpoint</span></dt><dd><div class="para">
+ The <em class="parameter"><code>mountpoint</code></em> on the local file system where the formatted device will be mounted. If the mount point directory does not exist, the <code class="command">virsh</code> command can create the directory.
+ </div><div class="para">
+ The directory <em class="replaceable"><code>/guest_images</code></em> is used in this example.
+ </div></dd></dl></div><pre class="screen"># virsh pool-define-as <em class="replaceable"><code>guest_images_fs</code></em> fs - - <em class="replaceable"><code>/dev/sdc1</code></em> - "<em class="replaceable"><code>/guest_images</code></em>"
+Pool guest_images_fs defined
+</pre><div class="para">
+ The new pool and mount points are now created.
+ </div></li><li class="step"><p class="title"><strong>Verify the new pool</strong></p><div class="para">
+ List the present storage pools.
+ </div><pre class="screen">
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+<em class="replaceable"><code>guest_images_fs</code></em> inactive no
+</pre></li><li class="step"><p class="title"><strong> Create the mount point </strong></p><div class="para">
+ Use the <code class="command">virsh pool-build</code> command to create a mount point for a pre-formatted file system storage pool.
+ </div><pre class="screen">
+# virsh pool-build <em class="replaceable"><code>guest_images_fs</code></em>
+Pool guest_images_fs built
+# ls -la /<em class="replaceable"><code>guest_images</code></em>
+total 8
+drwx------. 2 root root 4096 May 31 19:38 .
+dr-xr-xr-x. 25 root root 4096 May 31 19:38 ..
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_fs inactive no
+</pre></li><li class="step"><p class="title"><strong> Start the storage pool </strong></p><div class="para">
+ Use the <code class="command">virsh pool-start</code> command to mount the file system onto the mount point and make the pool available for use.
+ </div><pre class="screen">
+# virsh pool-start <em class="replaceable"><code>guest_images_fs</code></em>
+Pool guest_images_fs started
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_fs active no
+</pre></li><li class="step"><p class="title"><strong> Turn on autostart </strong></p><div class="para">
+ By default, a storage pool is defined with <code class="command">virsh</code> is not set to automatically start each time <code class="systemitem">libvirtd</code> starts. Turn on automatic start with the <code class="command">virsh pool-autostart</code> command. The storage pool is now automatically started each time <code class="systemitem">libvirtd</code> starts.
+ </div><pre class="screen">
+# virsh pool-autostart <em class="replaceable"><code>guest_images_fs</code></em>
+Pool guest_images_fs marked as autostarted
+
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_fs active yes
+</pre></li><li class="step"><p class="title"><strong> Verify the storage pool </strong></p><div class="para">
+ Verify the storage pool was created correctly, the sizes reported are as expected, and the state is reported as <code class="command">running</code>. Verify there is a "lost+found" directory in the mount point on the file system, indicating the device is mounted.
+ </div><pre class="screen">
+# virsh pool-info <em class="replaceable"><code>guest_images_fs</code></em>
+Name: guest_images_fs
+UUID: c7466869-e82a-a66c-2187-dc9d6f0877d0
+State: running
+Persistent: yes
+Autostart: yes
+Capacity: 458.39 GB
+Allocation: 197.91 MB
+Available: 458.20 GB
+# mount | grep /guest_images
+/dev/sdc1 on /guest_images type ext4 (rw)
+# ls -la /guest_images
+total 24
+drwxr-xr-x. 3 root root 4096 May 31 19:47 .
+dr-xr-xr-x. 25 root root 4096 May 31 19:38 ..
+drwx------. 2 root root 16384 May 31 14:18 lost+found
+</pre></li></ol></div></div><div class="section" id="delete-ded-part-storage-pool-virsh"><div class="titlepage"><div><div><h4 class="title">27.1.2.4. Deleting a storage pool using virsh</h4></div></div></div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it.
+ </div><pre class="screen"># virsh pool-destroy <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Optionally, if you want to remove the directory where the storage pool resides use the following command:
+ </div><pre class="screen"># virsh pool-delete <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Remove the storage pool's definition
+ </div><pre class="screen"># virsh pool-undefine <em class="replaceable"><code>guest_images_disk</code></em></pre></li></ol></div></div></div><div xml:lang="en-US" class="section" id="sect-Virtualization-Storage_Pools-Creating-Local_Directories" lang="en-US"><div class="titlepage"><div><div><h3 class="title">27.1.3. Directory-based storage pools</h3></div></div></div><div class="para">
+ This section covers storing guests in a directory on the host.
+ </div><div class="para">
+ Directory-based storage pools can be created with <code class="command">virt-manager</code> or the <code class="command">virsh</code> command line tools.
+ </div><div class="section" id="idp13336784"><div class="titlepage"><div><div><h4 class="title" id="idp13336784">27.1.3.1. Creating a directory-based storage pool with virt-manager</h4></div></div></div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Create the local directory</strong></p><ol class="a"><li class="step"><p class="title"><strong>Optional: Create a new directory for the storage pool</strong></p><div class="para">
+ Create the directory on the host for the storage pool. This example uses a directory named <em class="replaceable"><code>/guest_images</code></em>.
+ </div><pre class="screen"># mkdir <em class="replaceable"><code>/guest_images</code></em></pre></li><li class="step"><p class="title"><strong>Set directory ownership</strong></p><div class="para">
+ Change the user and group ownership of the directory. The directory must be owned by the root user.
+ </div><pre class="screen"># chown root:root <em class="replaceable"><code>/guest_images</code></em></pre></li><li class="step"><p class="title"><strong>Set directory permissions</strong></p><div class="para">
+ Change the file permissions of the directory.
+ </div><pre class="screen"># chmod 700 <em class="replaceable"><code>/guest_images</code></em></pre></li><li class="step"><p class="title"><strong>Verify the changes</strong></p><div class="para">
+ Verify the permissions were modified. The output shows a correctly configured empty directory.
+ </div><pre class="screen"># ls -la <em class="replaceable"><code>/guest_images</code></em>
+total 8
+drwx------. 2 root root 4096 May 28 13:57 .
+dr-xr-xr-x. 26 root root 4096 May 28 13:57 ..
+</pre></li></ol></li><li class="step"><p class="title"><strong>Configure SELinux file contexts</strong></p><div class="para">
+ Configure the correct SELinux context for the new directory. Note that the name of the pool and the directory do not have to match. However, when you shutdown the guest virtual machine, libvirt has to set the context back to a default value. The context of the directory determines what this default value is. It is worth explicitly labelling the directory virt_image_t, so that when the guest virtual machine is shutdown, the images get labeled 'virt_image_t' and are thus isolated from other processes running on the host.
+ </div><pre class="screen">
+# semanage fcontext -a -t virt_image_t '/guest_images(/.*)?'
+# restorecon -R /guest_images
+</pre></li><li class="step"><p class="title"><strong>Open the storage pool settings</strong></p><ol class="a"><li class="step"><div class="para">
+ In the <code class="command">virt-manager</code> graphical interface, select the host from the main window.
+ </div><div class="para">
+ Open the <span class="guilabel"><strong>Edit</strong></span> menu and select <span class="guilabel"><strong>Connection Details</strong></span>
+ </div><div class="figure" id="conn-details-screenshot"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_select_host.png" width="444" alt="Connection details window" /></div></div><h6>Figure 27.7. Connection details window</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Click on the <span class="guilabel"><strong>Storage</strong></span> tab of the <span class="guilabel"><strong>Connection Details</strong></span> window.
+ </div><div class="figure" id="host-details-screenshot-storagepools-dir"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Storage tab" /></div></div><h6>Figure 27.8. Storage tab</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Create the new storage pool</strong></p><ol class="a"><li class="step"><p class="title"><strong>Add a new pool (part 1)</strong></p><div class="para">
+ Press the <span class="guilabel"><strong>+</strong></span> button (the add pool button). The <span class="guilabel"><strong>Add a New Storage Pool</strong></span> wizard appears.
+ </div><div class="para">
+ Choose a <span class="guibutton"><strong>Name</strong></span> for the storage pool. This example uses the name <em class="replaceable"><code>guest_images</code></em>. Change the <span class="guibutton"><strong>Type</strong></span> to <code class="command">dir: Filesystem Directory</code>.
+ </div><div class="figure" id="screenshot-pick-pool-name"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_dir_step_1_name_and_type.png" width="444" alt="Name the storage pool" /></div></div><h6>Figure 27.9. Name the storage pool</h6></div><br class="figure-break" /><div class="para">
+ Press the <span class="guibutton"><strong>Forward</strong></span> button to continue.
+ </div></li><li class="step"><p class="title"><strong>Add a new pool (part 2)</strong></p><div class="para">
+ Change the <span class="guibutton"><strong>Target Path</strong></span> field. For example, <em class="replaceable"><code>/guest_images</code></em>.
+ </div><div class="para">
+ Verify the details and press the <span class="guibutton"><strong>Finish</strong></span> button to create the storage pool.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Verify the new storage pool</strong></p><div class="para">
+ The new storage pool appears in the storage list on the left after a few seconds. Verify the size is reported as expected, <em class="replaceable"><code>36.41 GB Free</code></em> in this example. Verify the <span class="guibutton"><strong>State</strong></span> field reports the new storage pool as <em class="replaceable"><code>Active</code></em>.
+ </div><div class="para">
+ Select the storage pool. In the <span class="guibutton"><strong>Autostart</strong></span> field, confirm that the <span class="guibutton"><strong>On Boot</strong></span> checkbox is checked. This will make sure the storage pool starts whenever the <code class="systemitem">libvirtd</code> service starts.
+ </div><div class="figure" id="verify-pool-screenshot"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_dir_step_3_result.png" width="444" alt="Verify the storage pool information" /></div></div><h6>Figure 27.10. Verify the storage pool information</h6></div><br class="figure-break" /><div class="para">
+ The storage pool is now created, close the <span class="guilabel"><strong>Connection Details</strong></span> window.
+ </div></li></ol></div></div><div class="section" id="del-stor-pool-dir"><div class="titlepage"><div><div><h4 class="title">27.1.3.2. Deleting a storage pool using virt-manager</h4></div></div></div><div class="para">
+ This procedure demonstrates how to delete a storage pool.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it. To do this, select the storage pool you want to stop and click the red X icon at the bottom of the Storage window.
+ </div><div class="figure" id="stop-icon2"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Stop Icon" /></div></div><h6>Figure 27.11. Stop Icon</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Delete the storage pool by clicking the Trash can icon. This icon is only enabled if you stop the storage pool first.
+ </div></li></ol></div></div><div class="section" id="idp1887664"><div class="titlepage"><div><div><h4 class="title" id="idp1887664">27.1.3.3. Creating a directory-based storage pool with virsh</h4></div></div></div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong> Create the storage pool definition </strong></p><div class="para">
+ Use the <code class="command">virsh pool-define-as</code> command to define a new storage pool. There are two options required for creating directory-based storage pools:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <code class="command">name</code> of the storage pool.
+ </div><div class="para">
+ This example uses the name <em class="replaceable"><code>guest_images</code></em>. All further <code class="command">virsh</code> commands used in this example use this name.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="command">path</code> to a file system directory for storing guest image files. If this directory does not exist, <code class="command">virsh</code> will create it.
+ </div><div class="para">
+ This example uses the <em class="replaceable"><code>/guest_images</code></em> directory.
+ </div></li></ul></div><pre class="screen"> # virsh pool-define-as <em class="replaceable"><code>guest_images</code></em> dir - - - - "<em class="replaceable"><code>/guest_images</code></em>"
+Pool guest_images defined</pre></li><li class="step"><p class="title"><strong>Verify the storage pool is listed</strong></p><div class="para">
+ Verify the storage pool object is created correctly and the state reports it as <code class="computeroutput">inactive</code>.
+ </div><pre class="screen"># virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images inactive no</pre></li><li class="step"><p class="title"><strong> Create the local directory </strong></p><div class="para">
+ Use the <code class="command">virsh pool-build</code> command to build the directory-based storage pool for the directory <em class="replaceable"><code>guest_images</code></em> (for example), as shown:
+ </div><pre class="screen"># virsh pool-build <em class="replaceable"><code>guest_images</code></em>
+Pool guest_images built
+# ls -la /<em class="replaceable"><code>guest_images</code></em>
+total 8
+drwx------. 2 root root 4096 May 30 02:44 .
+dr-xr-xr-x. 26 root root 4096 May 30 02:44 ..
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images inactive no</pre></li><li class="step"><p class="title"><strong>Start the storage pool</strong></p><div class="para">
+ Use the virsh command <code class="command">pool-start</code> to enable a directory storage pool, thereby allowing allowing volumes of the pool to be used as guest disk images.
+ </div><pre class="screen"># virsh pool-start <em class="replaceable"><code>guest_images</code></em>
+Pool guest_images started
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images active no
+</pre></li><li class="step"><p class="title"><strong>Turn on autostart</strong></p><div class="para">
+ Turn on <em class="parameter"><code>autostart</code></em> for the storage pool. Autostart configures the <code class="systemitem">libvirtd</code> service to start the storage pool when the service starts.
+ </div><pre class="screen"># virsh pool-autostart <em class="replaceable"><code>guest_images</code></em>
+Pool guest_images marked as autostarted
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images active yes
+</pre></li><li class="step"><p class="title"><strong>Verify the storage pool configuration</strong></p><div class="para">
+ Verify the storage pool was created correctly, the size is reported correctly, and the state is reported as <code class="computeroutput">running</code>. If you want the pool to be accessible even if the guest is not running, make sure that <code class="computeroutput">Persistent</code> is reported as <code class="computeroutput">yes</code>. If you want the pool to start automatically when the service starts, make sure that <code class="computeroutput">Autostart</code> is reported as <code class="computeroutput">yes</code>.
+ </div><pre class="screen"># virsh pool-info <em class="replaceable"><code>guest_images</code></em>
+Name: guest_images
+UUID: 779081bf-7a82-107b-2874-a19a9c51d24c
+State: running
+Persistent: yes
+Autostart: yes
+Capacity: 49.22 GB
+Allocation: 12.80 GB
+Available: 36.41 GB
+
+# ls -la /guest_images
+total 8
+drwx------. 2 root root 4096 May 30 02:44 .
+dr-xr-xr-x. 26 root root 4096 May 30 02:44 ..
+#
+</pre></li></ol></div><div class="para">
+ A directory-based storage pool is now available.
+ </div></div><div class="section" id="delete-dir-storage-pool-virsh"><div class="titlepage"><div><div><h4 class="title">27.1.3.4. Deleting a storage pool using virsh</h4></div></div></div><div class="para">
+ The following demonstrates how to delete a storage pool using virsh:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it.
+ </div><pre class="screen"># virsh pool-destroy <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Optionally, if you want to remove the directory where the storage pool resides use the following command:
+ </div><pre class="screen"># virsh pool-delete <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Remove the storage pool's definition
+ </div><pre class="screen"># virsh pool-undefine <em class="replaceable"><code>guest_images_disk</code></em></pre></li></ol></div></div></div><div xml:lang="en-US" class="section" id="sect-Virtualization-Storage_Pools-Creating-LVM" lang="en-US"><div class="titlepage"><div><div><h3 class="title">27.1.4. LVM-based storage pools</h3></div></div></div><div class="para">
+ This chapter covers using LVM volume groups as storage pools.
+ </div><div class="para">
+ LVM-based storage groups provide the full flexibility of LVM.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Please refer to the <em class="citetitle">Fedora Storage Administration Guide</em> for more details on LVM.
+ </div></div></div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ LVM-based storage pools require a full disk partition. If activating a new partition/device with these procedures, the partition will be formatted and all data will be erased. If using the host's existing Volume Group (VG) nothing will be erased. It is recommended to back up the storage device before commencing the following procedure.
+ </div></div></div><div class="section" id="idm3043648"><div class="titlepage"><div><div><h4 class="title" id="idm3043648">27.1.4.1. Creating an LVM-based storage pool with virt-manager</h4></div></div></div><div class="para">
+ LVM-based storage pools can use existing LVM volume groups or create new LVM volume groups on a blank partition.
+ </div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Optional: Create new partition for LVM volumes</strong></p><div class="para">
+ These steps describe how to create a new partition and LVM volume group on a new hard disk drive.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ This procedure will remove all data from the selected storage device.
+ </div></div></div><ol class="a"><li class="step"><p class="title"><strong>Create a new partition</strong></p><div class="para">
+ Use the <code class="command">fdisk</code> command to create a new disk partition from the command line. The following example creates a new partition that uses the entire disk on the storage device <code class="computeroutput">/dev/sdb</code>.
+ </div><pre class="screen"># fdisk /dev/sdb
+Command (m for help):
+</pre><div class="para">
+ Press <em class="parameter"><code>n</code></em> for a new partition.
+ </div></li><li class="step"><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 class="step"><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 class="step"><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 class="step"><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 class="step"><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 class="step"><div class="para">
+ Choose the partition you created in the previous steps. In this example, the partition number is <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 class="step"><div class="para">
+ Enter <em class="parameter"><code>8e</code></em> for a Linux LVM partition.
+ </div><pre class="screen">Hex code (type L to list codes): <em class="parameter"><code>8e</code></em>
+</pre></li><li class="step"><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 class="step"><p class="title"><strong>Create a new LVM volume group</strong></p><div class="para">
+ Create a new LVM volume group with the <code class="command">vgcreate</code> command. This example creates a volume group named <em class="replaceable"><code>guest_images_lvm</code></em>.
+ </div><pre class="screen"># vgcreate <em class="replaceable"><code>guest_images_lvm</code></em> /dev/sdb1
+ Physical volume "/dev/vdb1" successfully created
+ Volume group "<em class="replaceable"><code>guest_images_lvm</code></em>" successfully created
+</pre></li></ol><div class="para">
+ The new LVM volume group, <em class="replaceable"><code>guest_images_lvm</code></em>, can now be used for an LVM-based storage pool.
+ </div></li><li class="step"><p class="title"><strong>Open the storage pool settings</strong></p><ol class="a"><li class="step"><div class="para">
+ In the <code class="command">virt-manager</code> graphical interface, select the host from the main window.
+ </div><div class="para">
+ Open the <span class="guilabel"><strong>Edit</strong></span> menu and select <span class="guilabel"><strong>Connection Details</strong></span>
+ </div><div class="figure" id="connection-details"><div class="figure-contents"><div class="mediaobject"><img src="images/Connection_Details.png" width="444" alt="Connection details" /></div></div><h6>Figure 27.12. Connection details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Click on the <span class="guilabel"><strong>Storage</strong></span> tab.
+ </div><div class="figure" id="lvm-storage-tab"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Storage tab" /></div></div><h6>Figure 27.13. Storage tab</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Create the new storage pool</strong></p><ol class="a"><li class="step"><p class="title"><strong>Start the Wizard</strong></p><div class="para">
+ Press the <span class="guilabel"><strong>+</strong></span> button (the add pool button). The <span class="guilabel"><strong>Add a New Storage Pool</strong></span> wizard appears.
+ </div><div class="para">
+ Choose a <span class="guibutton"><strong>Name</strong></span> for the storage pool. We use <em class="replaceable"><code>guest_images_lvm</code></em> for this example. Then change the <span class="guibutton"><strong>Type</strong></span> to <code class="command">logical: LVM Volume Group</code>, and
+ </div><div class="figure" id="lvm-add"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_lvm_step_1_name_and_type.png" width="444" alt="Add LVM storage pool" /></div></div><h6>Figure 27.14. Add LVM storage pool</h6></div><br class="figure-break" /><div class="para">
+ Press the <span class="guibutton"><strong>Forward</strong></span> button to continue.
+ </div></li><li class="step"><p class="title"><strong>Add a new pool (part 2)</strong></p><div class="para">
+ Change the <span class="guibutton"><strong>Target Path</strong></span> field. This example uses <em class="replaceable"><code>/guest_images</code></em>.
+ </div><div class="para">
+ Now fill in the <span class="guibutton"><strong>Target Path</strong></span> and <span class="guibutton"><strong>Source Path</strong></span> fields, then tick the <span class="guibutton"><strong>Build Pool</strong></span> check box.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Use the <span class="guibutton"><strong>Target Path</strong></span> field to <span class="emphasis"><em>either</em></span> select an existing LVM volume group or as the name for a new volume group. The default format is <code class="computeroutput">/dev/</code><em class="replaceable"><code>storage_pool_name</code></em>.
+ </div><div class="para">
+ This example uses a new volume group named <em class="replaceable"><code>/dev/guest_images_lvm</code></em>.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="command">Source Path</code> field is optional if an existing LVM volume group is used in the <span class="guibutton"><strong>Target Path</strong></span>.
+ </div><div class="para">
+ For new LVM volume groups, input the location of a storage device in the <code class="command">Source Path</code> field. This example uses a blank partition <em class="replaceable"><code>/dev/sdc</code></em>.
+ </div></li><li class="listitem"><div class="para">
+ The <span class="guibutton"><strong>Build Pool</strong></span> checkbox instructs <code class="command">virt-manager</code> to create a new LVM volume group. If you are using an existing volume group you should not select the <span class="guibutton"><strong>Build Pool</strong></span> checkbox.
+ </div><div class="para">
+ This example is using a blank partition to create a new volume group so the <span class="guibutton"><strong>Build Pool</strong></span> checkbox must be selected.
+ </div></li></ul></div><div class="figure" id="lvm-pool-step2"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_lvm_step_2a_paths_and_pool.png" width="444" alt="Add target and source" /></div></div><h6>Figure 27.15. Add target and source</h6></div><br class="figure-break" /><div class="para">
+ Verify the details and press the <span class="guibutton"><strong>Finish</strong></span> button format the LVM volume group and create the storage pool.
+ </div></li><li class="step"><p class="title"><strong>Confirm the device to be formatted</strong></p><div class="para">
+ A warning message appears.
+ </div><div class="figure" id="lvm-warning-message"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_lvm_step_2b_format_warning.png" alt="Warning message" /></div></div><h6>Figure 27.16. Warning message</h6></div><br class="figure-break" /><div class="para">
+ Press the <span class="guilabel"><strong>Yes</strong></span> button to proceed to erase all data on the storage device and create the storage pool.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Verify the new storage pool</strong></p><div class="para">
+ The new storage pool will appear in the list on the left after a few seconds. Verify the details are what you expect, <em class="replaceable"><code>465.76 GB Free</code></em> in our example. Also verify the <span class="guibutton"><strong>State</strong></span> field reports the new storage pool as <em class="replaceable"><code>Active</code></em>.
+ </div><div class="para">
+ It is generally a good idea to have the <span class="guibutton"><strong>Autostart</strong></span> check box enabled, to ensure the storage pool starts automatically with libvirtd.
+ </div><div class="figure" id="confirm-lvm-pool"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_lvm_step_3_result.png" width="444" alt="Confirm LVM storage pool details" /></div></div><h6>Figure 27.17. Confirm LVM storage pool details</h6></div><br class="figure-break" /><div class="para">
+ Close the Host Details dialog, as the task is now complete.
+ </div></li></ol></div></div><div class="section" id="del-stor-pool-lvm"><div class="titlepage"><div><div><h4 class="title">27.1.4.2. Deleting a storage pool using virt-manager</h4></div></div></div><div class="para">
+ This procedure demonstrates how to delete a storage pool.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it. To do this, select the storage pool you want to stop and click the red X icon at the bottom of the Storage window.
+ </div><div class="figure" id="stop-icon3"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Stop Icon" /></div></div><h6>Figure 27.18. Stop Icon</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Delete the storage pool by clicking the Trash can icon. This icon is only enabled if you stop the storage pool first.
+ </div></li></ol></div></div><div class="section" id="idp671312"><div class="titlepage"><div><div><h4 class="title" id="idp671312">27.1.4.3. Creating an LVM-based storage pool with virsh</h4></div></div></div><div class="para">
+ This section outlines the steps required to create an LVM-based storage pool with the <code class="command">virsh</code> command. It uses the example of a pool named <span class="bold bold"><strong>guest_images_lvm</strong></span> from a single drive (<code class="filename">/dev/sdc</code>). This is only an example and your settings should be substituted as appropriate.
+ </div><div class="procedure"><h6>Procedure 27.3. Creating an LVM-based storage pool with virsh</h6><ol class="1"><li class="step"><div class="para">
+ Define the pool name <span class="bold bold"><strong>guest_images_lvm</strong></span>.
+ </div><pre class="screen"># virsh pool-define-as <em class="replaceable"><code>guest_images_lvm</code></em> logical - - <em class="replaceable"><code>/dev/sdc</code></em> <em class="replaceable"><code>libvirt_lvm</code></em> \ /dev/<em class="replaceable"><code>libvirt_lvm</code></em>
+Pool guest_images_lvm defined
+</pre></li><li class="step"><div class="para">
+ Build the pool according to the specified name.
+ </div><pre class="screen">
+# virsh pool-build <em class="replaceable"><code>guest_images_lvm</code></em>
+
+Pool guest_images_lvm built
+</pre></li><li class="step"><div class="para">
+ Initialize the new pool.
+ </div><pre class="screen">
+# virsh pool-start <em class="replaceable"><code>guest_images_lvm</code></em>
+
+Pool guest_images_lvm started
+</pre></li><li class="step"><div class="para">
+ Show the volume group information with the <code class="command">vgs</code> command.
+ </div><pre class="screen">
+# vgs
+VG #PV #LV #SN Attr VSize VFree
+libvirt_lvm 1 0 0 wz--n- 465.76g 465.76g
+</pre></li><li class="step"><div class="para">
+ Set the pool to start automatically.
+ </div><pre class="screen">
+# virsh pool-autostart <em class="replaceable"><code>guest_images_lvm</code></em>
+Pool guest_images_lvm marked as autostarted
+</pre></li><li class="step"><div class="para">
+ List the available pools with the <code class="command">virsh</code> command.
+ </div><pre class="screen">
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_lvm active yes
+</pre></li><li class="step"><div class="para">
+ The following commands demonstrate the creation of three volumes (<span class="emphasis"><em>volume1</em></span>, <span class="emphasis"><em>volume2</em></span> and <span class="emphasis"><em>volume3</em></span>) within this pool.
+ </div><pre class="screen">
+# virsh vol-create-as <em class="replaceable"><code>guest_images_lvm</code></em> <em class="replaceable"><code>volume1</code></em> <em class="replaceable"><code>8G</code></em>
+Vol volume1 created
+
+# virsh vol-create-as <em class="replaceable"><code>guest_images_lvm</code></em> <em class="replaceable"><code>volume2</code></em> <em class="replaceable"><code>8G</code></em>
+Vol volume2 created
+
+# virsh vol-create-as <em class="replaceable"><code>guest_images_lvm</code></em> <em class="replaceable"><code>volume3</code></em> <em class="replaceable"><code>8G</code></em>
+Vol volume3 created
+</pre></li><li class="step"><div class="para">
+ List the available volumes in this pool with the <code class="command">virsh</code> command.
+ </div><pre class="screen">
+# virsh vol-list <em class="replaceable"><code>guest_images_lvm</code></em>
+Name Path
+-----------------------------------------
+volume1 /dev/libvirt_lvm/volume1
+volume2 /dev/libvirt_lvm/volume2
+volume3 /dev/libvirt_lvm/volume3
+</pre></li><li class="step"><div class="para">
+ The following two commands (<code class="command">lvscan</code> and <code class="command">lvs</code>) display further information about the newly created volumes.
+ </div><pre class="screen">
+# lvscan
+ACTIVE '/dev/libvirt_lvm/volume1' [8.00 GiB] inherit
+ACTIVE '/dev/libvirt_lvm/volume2' [8.00 GiB] inherit
+ACTIVE '/dev/libvirt_lvm/volume3' [8.00 GiB] inherit
+
+# lvs
+LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
+volume1 libvirt_lvm -wi-a- 8.00g
+volume2 libvirt_lvm -wi-a- 8.00g
+volume3 libvirt_lvm -wi-a- 8.00g
+</pre></li></ol></div></div><div class="section" id="delete-lvm-storage-pool-virsh"><div class="titlepage"><div><div><h4 class="title">27.1.4.4. Deleting a storage pool using virsh</h4></div></div></div><div class="para">
+ The following demonstrates how to delete a storage pool using virsh:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it.
+ </div><pre class="screen"># virsh pool-destroy <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Optionally, if you want to remove the directory where the storage pool resides use the following command:
+ </div><pre class="screen"># virsh pool-delete <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Remove the storage pool's definition
+ </div><pre class="screen"># virsh pool-undefine <em class="replaceable"><code>guest_images_disk</code></em></pre></li></ol></div></div></div><div xml:lang="en-US" class="section" id="sect-Virtualization-Storage_Pools-Creating-iSCSI" lang="en-US"><div class="titlepage"><div><div><h3 class="title">27.1.5. iSCSI-based storage pools</h3></div></div></div><div class="para">
+ This section covers using iSCSI-based devices to store guests.
+ </div><div class="para">
+ iSCSI (Internet Small Computer System Interface) is a network protocol for sharing storage devices. iSCSI connects initiators (storage clients) to targets (storage servers) using SCSI instructions over the IP layer.
+ </div><div class="section" id="idm15693984"><div class="titlepage"><div><div><h4 class="title" id="idm15693984">27.1.5.1. Configuring a software iSCSI target</h4></div></div></div><div class="para">
+ The <span class="package">scsi-target-utils</span> package provides a tool for creating software-backed iSCSI targets.
+ </div><div class="procedure"><h6>Procedure 27.4. Creating an iSCSI target</h6><ol class="1"><li class="step"><p class="title"><strong>Install the required packages</strong></p><div class="para">
+ Install the <span class="package">scsi-target-utils</span> package and all dependencies
+ </div><pre class="screen"># yum install scsi-target-utils</pre></li><li class="step"><p class="title"><strong>Start the tgtd service</strong></p><div class="para">
+ The <code class="command">tgtd</code> service hosts SCSI targets and uses the iSCSI protocol to host targets. Start the <code class="command">tgtd</code> service and make the service persistent after restarting with the <code class="command">chkconfig</code> command.
+ </div><pre class="screen"># service tgtd start
+# chkconfig tgtd on</pre></li><li class="step"><p class="title"><strong>Optional: Create LVM volumes</strong></p><div class="para">
+ LVM volumes are useful for iSCSI backing images. LVM snapshots and resizing can be beneficial for guests. This example creates an LVM image named <em class="replaceable"><code>virtimage1</code></em> on a new volume group named <em class="replaceable"><code>virtstore</code></em> on a RAID5 array for hosting guests with iSCSI.
+ </div><ol class="a"><li class="step"><p class="title"><strong>Create the RAID array</strong></p><div class="para">
+ Creating software RAID5 arrays is covered by the <em class="citetitle">Fedora Deployment Guide</em>.
+ </div></li><li class="step"><p class="title"><strong>Create the LVM volume group</strong></p><div class="para">
+ Create a volume group named <em class="replaceable"><code>virtstore</code></em> with the <code class="command">vgcreate</code> command.
+ </div><pre class="screen"># vgcreate <em class="replaceable"><code>virtstore</code></em> /dev/md1</pre></li><li class="step"><p class="title"><strong>Create a LVM logical volume</strong></p><div class="para">
+ Create a logical volume group named <em class="replaceable"><code>virtimage1</code></em> on the <em class="replaceable"><code>virtstore</code></em> volume group with a size of 20GB using the <code class="command">lvcreate</code> command.
+ </div><pre class="screen"># lvcreate --size 20G -n <em class="replaceable"><code>virtimage1 virtstore</code></em></pre><div class="para">
+ The new logical volume, <em class="replaceable"><code>virtimage1</code></em>, is ready to use for iSCSI.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Optional: Create file-based images</strong></p><div class="para">
+ File-based storage is sufficient for testing but is not recommended for production environments or any significant I/O activity. This optional procedure creates a file based imaged named <em class="replaceable"><code>virtimage2.img</code></em> for an iSCSI target.
+ </div><ol class="a"><li class="step"><p class="title"><strong>Create a new directory for the image</strong></p><div class="para">
+ Create a new directory to store the image. The directory must have the correct SELinux contexts.
+ </div><pre class="screen"># mkdir -p /var/lib/tgtd/<em class="replaceable"><code>virtualization</code></em>
+</pre></li><li class="step"><p class="title"><strong>Create the image file</strong></p><div class="para">
+ Create an image named <em class="replaceable"><code>virtimage2.img</code></em> with a size of 10GB.
+ </div><pre class="screen"># dd if=/dev/zero of=/var/lib/tgtd/<em class="replaceable"><code>virtualization</code></em>/<em class="replaceable"><code>virtimage2.img</code></em> bs=1M seek=10000 count=0</pre></li><li class="step"><p class="title"><strong>Configure SELinux file contexts</strong></p><div class="para">
+ Configure the correct SELinux context for the new image and directory.
+ </div><pre class="screen"># restorecon -R /var/lib/tgtd</pre><div class="para">
+ The new file-based image, <em class="replaceable"><code>virtimage2.img</code></em>, is ready to use for iSCSI.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Create targets</strong></p><div class="para">
+ Targets can be created by adding a XML entry to the <code class="filename">/etc/tgt/targets.conf</code> file. The <code class="computeroutput">target</code> attribute requires an iSCSI Qualified Name (IQN). The IQN is in the format:
+ </div><pre class="screen">iqn.<em class="replaceable"><code>yyyy</code></em>-<em class="replaceable"><code>mm</code></em>.<em class="replaceable"><code>reversed domain name</code></em>:<em class="replaceable"><code>optional identifier text</code></em>
+</pre><div class="para">
+ Where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="replaceable"><code>yyyy</code></em>-<em class="replaceable"><code>mm</code></em> represents the year and month the device was started (for example: <em class="replaceable"><code>2010-05</code></em>);
+ </div></li><li class="listitem"><div class="para">
+ <em class="replaceable"><code>reversed domain name</code></em> is the hosts domain name in reverse (for example <em class="replaceable"><code>server1.example.com</code></em> in an IQN would be <em class="replaceable"><code>com.example.server1</code></em>); and
+ </div></li><li class="listitem"><div class="para">
+ <em class="replaceable"><code>optional identifier text</code></em> is any text string, without spaces, that assists the administrator in identifying devices or hardware.
+ </div></li></ul></div><div class="para">
+ This example creates iSCSI targets for the two types of images created in the optional steps on <em class="replaceable"><code>server1.example.com</code></em> with an optional identifier <em class="replaceable"><code>trial</code></em>. Add the following to the <code class="filename">/etc/tgt/targets.conf</code> file.
+ </div><pre class="screen">
+<target iqn.2010-05.com.example.<em class="replaceable"><code>server1</code></em>:<em class="replaceable"><code>trial</code></em>>
+ backing-store /dev/<em class="replaceable"><code>virtstore</code></em>/<em class="replaceable"><code>virtimage1</code></em> #LUN 1
+ backing-store /var/lib/tgtd/<em class="replaceable"><code>virtualization</code></em>/<em class="replaceable"><code>virtimage2.img</code></em> #LUN 2
+ write-cache off
+</target>
+</pre><div class="para">
+ Ensure that the <code class="filename">/etc/tgt/targets.conf</code> file contains the <code class="computeroutput">default-driver iscsi</code> line to set the driver type as iSCSI. The driver uses iSCSI by default.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ This example creates a globally accessible target without access control. Refer to the scsi-target-utils for information on implementing secure access.
+ </div></div></div></li><li class="step"><p class="title"><strong>Restart the tgtd service</strong></p><div class="para">
+ Restart the <code class="systemitem">tgtd</code> service to reload the configuration changes.
+ </div><pre class="screen"># service tgtd restart</pre></li><li class="step"><p class="title"><strong>iptables configuration</strong></p><div class="para">
+ Open port 3260 for iSCSI access with <code class="command">iptables</code>.
+ </div><pre class="screen"># iptables -I INPUT -p tcp -m tcp --dport 3260 -j ACCEPT
+# service iptables save
+# service iptables restart</pre></li><li class="step"><p class="title"><strong>Verify the new targets</strong></p><div class="para">
+ View the new targets to ensure the setup was successful with the <code class="command">tgt-admin --show</code> command.
+ </div><pre class="screen">
+# tgt-admin --show
+Target 1: iqn.2010-05.com.example.server1:trial
+System information:
+Driver: iscsi
+State: ready
+I_T nexus information:
+LUN information:
+LUN: 0
+ Type: controller
+ SCSI ID: IET 00010000
+ SCSI SN: beaf10
+ Size: 0 MB
+ Online: Yes
+ Removable media: No
+ Backing store type: rdwr
+ Backing store path: None
+LUN: 1
+ Type: disk
+ SCSI ID: IET 00010001
+ SCSI SN: beaf11
+ Size: 20000 MB
+ Online: Yes
+ Removable media: No
+ Backing store type: rdwr
+ Backing store path: /dev/<em class="replaceable"><code>virtstore</code></em>/<em class="replaceable"><code>virtimage1</code></em>
+LUN: 2
+ Type: disk
+ SCSI ID: IET 00010002
+ SCSI SN: beaf12
+ Size: 10000 MB
+ Online: Yes
+ Removable media: No
+ Backing store type: rdwr
+ Backing store path: /var/lib/tgtd/<em class="replaceable"><code>virtualization</code></em>/<em class="replaceable"><code>virtimage2.img</code></em>
+Account information:
+ACL information:
+ALL
+</pre><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ The ACL list is set to all. This allows all systems on the local network to access this device. It is recommended to set host access ACLs for production environments.
+ </div></div></div></li><li class="step"><p class="title"><strong>Optional: Test discovery</strong></p><div class="para">
+ Test whether the new iSCSI device is discoverable.
+ </div><pre class="screen"># iscsiadm --mode discovery --type sendtargets --portal server1.example.com
+127.0.0.1:3260,1 iqn.2010-05.com.example.server1:iscsirhel6guest</pre></li><li class="step"><p class="title"><strong>Optional: Test attaching the device</strong></p><div class="para">
+ Attach the new device (<em class="replaceable"><code>iqn.2010-05.com.example.server1:iscsirhel6guest</code></em>) to determine whether the device can be attached.
+ </div><pre class="screen"># iscsiadm -d2 -m node --login
+scsiadm: Max file limits 1024 1024
+
+Logging in to [iface: default, target: iqn.2010-05.com.example.server1:iscsirhel6guest, portal: 10.0.0.1,3260]
+Login to [iface: default, target: iqn.2010-05.com.example.server1:iscsirhel6guest, portal: 10.0.0.1,3260] successful.</pre><div class="para">
+ Detach the device.
+ </div><pre class="screen"># iscsiadm -d2 -m node --logout
+scsiadm: Max file limits 1024 1024
+
+Logging out of session [sid: 2, target: iqn.2010-05.com.example.server1:iscsirhel6guest, portal: 10.0.0.1,3260
+Logout of [sid: 2, target: iqn.2010-05.com.example.server1:iscsirhel6guest, portal: 10.0.0.1,3260] successful.</pre></li></ol></div><div class="para">
+ An iSCSI device is now ready to use for virtualization.
+ </div></div><div class="section" id="idm11426064"><div class="titlepage"><div><div><h4 class="title" id="idm11426064">27.1.5.2. Adding an iSCSI target to virt-manager</h4></div></div></div><div class="para">
+ This procedure covers creating a storage pool with an iSCSI target in <code class="command">virt-manager</code>.
+ </div><div class="procedure"><h6>Procedure 27.5. Adding an iSCSI device to virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Open the host storage tab</strong></p><div class="para">
+ Open the <span class="guilabel"><strong>Storage</strong></span> tab in the <span class="guilabel"><strong>Host Details</strong></span> window.
+ </div><ol class="a"><li class="step"><div class="para">
+ Open <code class="command">virt-manager</code>.
+ </div></li><li class="step"><div class="para">
+ Select a host from the main <code class="command">virt-manager</code> window. Click <span class="guilabel"><strong>Edit menu</strong></span> and select <span class="guilabel"><strong>Connection Details</strong></span>.
+ </div><div class="figure" id="scsi-connection-details"><div class="figure-contents"><div class="mediaobject"><img src="images/Connection_Details.png" width="444" alt="Connection details" /></div></div><h6>Figure 27.19. Connection details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Click on the <span class="guilabel"><strong>Storage</strong></span> tab.
+ </div><div class="figure" id="scsi-storage-tab"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Storage menu" /></div></div><h6>Figure 27.20. Storage menu</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Add a new pool (part 1)</strong></p><div class="para">
+ Press the <span class="guilabel"><strong>+</strong></span> button (the add pool button). The <span class="guilabel"><strong>Add a New Storage Pool</strong></span> wizard appears.
+ </div><div class="figure" id="iscsi-storage-pool"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_add_storage_pool1.png" width="444" alt="Add an iscsi storage pool name and type" /></div></div><h6>Figure 27.21. Add an iscsi storage pool name and type</h6></div><br class="figure-break" /><div class="para">
+ Choose a name for the storage pool, change the Type to iscsi, and press <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Add a new pool (part 2)</strong></p><div class="para">
+ Enter the target path for the device, the host name of the target and the source path (the IQN). The <span class="guilabel"><strong>Format</strong></span> option is not available as formatting is handled by the guests. It is not advised to edit the <span class="guilabel"><strong>Target Path</strong></span>. The default target path value, <code class="filename">/dev/disk/by-path/</code>, adds the drive path to that directory. The target path should be the same on all hosts for migration.
+ </div><div class="para">
+ Enter the hostname or IP address of the iSCSI target. This example uses <code class="computeroutput">server1.example.com</code>.
+ </div><div class="para">
+ Enter the source path, for the iSCSI target. This example uses <code class="computeroutput">demo-target</code>.
+ </div><div class="para">
+ Check the <span class="guilabel"><strong>IQN</strong></span> checkbox to enter the IQN. This example uses <code class="computeroutput">iqn.2010-05.com.example.server1:iscsirhel6guest</code>.
+ </div><div class="figure" id="storage-pool-iscsi-add"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_add_storage_pool2.png" width="444" alt="Create an iscsi storage pool" /></div></div><h6>Figure 27.22. Create an iscsi storage pool</h6></div><br class="figure-break" /><div class="para">
+ Press <span class="guibutton"><strong>Finish</strong></span> to create the new storage pool.
+ </div></li></ol></div></div><div class="section" id="del-stor-pool-iscsi"><div class="titlepage"><div><div><h4 class="title">27.1.5.3. Deleting a storage pool using virt-manager</h4></div></div></div><div class="para">
+ This procedure demonstrates how to delete a storage pool.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it. To do this, select the storage pool you want to stop and click the red X icon at the bottom of the Storage window.
+ </div><div class="figure" id="stop-icon4"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Stop Icon" /></div></div><h6>Figure 27.23. Stop Icon</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Delete the storage pool by clicking the Trash can icon. This icon is only enabled if you stop the storage pool first.
+ </div></li></ol></div></div><div class="section" id="idp7385632"><div class="titlepage"><div><div><h4 class="title" id="idp7385632">27.1.5.4. Creating an iSCSI-based storage pool with virsh</h4></div></div></div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Use pool-define-as to define the pool from the command line</strong></p><div class="para">
+ Storage pool definitions can be created with the <code class="command">virsh</code> command line tool. Creating storage pools with <code class="command">virsh</code> is useful for systems administrators using scripts to create multiple storage pools.
+ </div><div class="para">
+ The <code class="command">virsh pool-define-as</code> command has several parameters which are accepted in the following format:
+ </div><pre class="screen">virsh pool-define-as <em class="parameter"><code>name type source-host source-path source-dev source-name</code></em> <em class="replaceable"><code>target</code></em>
+</pre><div class="para">
+ The parameters are explained as follows:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">type</span></dt><dd><div class="para">
+ defines this pool as a particular type, iscsi for example
+ </div></dd><dt class="varlistentry"><span class="term">name</span></dt><dd><div class="para">
+ must be unique and sets the name for the storage pool
+ </div></dd><dt class="varlistentry"><span class="term">source-host and source-path</span></dt><dd><div class="para">
+ the hostname and iSCSI IQN respectively
+ </div></dd><dt class="varlistentry"><span class="term">source-dev and source-name</span></dt><dd><div class="para">
+ these parameters are not required for iSCSI-based pools, use a <span class="keycap"><strong>-</strong></span> character to leave the field blank.
+ </div></dd><dt class="varlistentry"><span class="term">target</span></dt><dd><div class="para">
+ defines the location for mounting the iSCSI device on the host
+ </div></dd></dl></div><div class="para">
+ The example below creates the same iSCSI-based storage pool as the previous step.
+ </div><pre class="screen"># virsh pool-define-as --name scsirhel6guest --type iscsi \
+ --source-host server1.example.com \
+ --source-dev iqn.2010-05.com.example.server1:iscsirhel6guest
+ --target /dev/disk/by-path
+Pool iscsirhel6guest defined</pre></li><li class="step"><p class="title"><strong>Verify the storage pool is listed</strong></p><div class="para">
+ Verify the storage pool object is created correctly and the state reports as <code class="computeroutput">inactive</code>.
+ </div><pre class="screen"># virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+<em class="replaceable"><code>iscsirhel6guest</code></em> inactive no</pre></li><li class="step"><p class="title"><strong>Start the storage pool</strong></p><div class="para">
+ Use the virsh command <code class="command">pool-start</code> for this. <code class="command">pool-start</code> enables a directory storage pool, allowing it to be used for volumes and guests.
+ </div><pre class="screen"># virsh pool-start <em class="replaceable"><code>guest_images_disk</code></em>
+Pool guest_images_disk started
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+<em class="replaceable"><code>iscsirhel6guest</code></em> active no
+</pre></li><li class="step"><p class="title"><strong>Turn on autostart</strong></p><div class="para">
+ Turn on <em class="parameter"><code>autostart</code></em> for the storage pool. Autostart configures the <code class="systemitem">libvirtd</code> service to start the storage pool when the service starts.
+ </div><pre class="screen"># virsh pool-autostart <em class="replaceable"><code>iscsirhel6guest</code></em>
+Pool iscsirhel6guest marked as autostarted</pre><div class="para">
+ Verify that the <em class="replaceable"><code>iscsirhel6guest</code></em> pool has autostart set:
+ </div><pre class="screen"># virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+<em class="replaceable"><code>iscsirhel6guest</code></em> active yes
+</pre></li><li class="step"><p class="title"><strong>Verify the storage pool configuration</strong></p><div class="para">
+ Verify the storage pool was created correctly, the sizes reported correctly, and the state reports as <code class="computeroutput">running</code>.
+ </div><pre class="screen"># virsh pool-info <em class="replaceable"><code>iscsirhel6guest</code></em>
+Name: <em class="replaceable"><code>iscsirhel6guest</code></em>
+UUID: afcc5367-6770-e151-bcb3-847bc36c5e28
+State: running
+Persistent: unknown
+Autostart: yes
+Capacity: 100.31 GB
+Allocation: 0.00
+Available: 100.31 GB
+</pre></li></ol></div><div class="para">
+ An iSCSI-based storage pool is now available.
+ </div></div><div class="section" id="delete-iscsi-storage-pool-virsh"><div class="titlepage"><div><div><h4 class="title">27.1.5.5. Deleting a storage pool using virsh</h4></div></div></div><div class="para">
+ The following demonstrates how to delete a storage pool using virsh:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it.
+ </div><pre class="screen"># virsh pool-destroy <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Remove the storage pool's definition
+ </div><pre class="screen"># virsh pool-undefine <em class="replaceable"><code>guest_images_disk</code></em></pre></li></ol></div></div></div><div xml:lang="en-US" class="section" id="sect-Virtualization-Storage_Pools-Creating-NFS" lang="en-US"><div class="titlepage"><div><div><h3 class="title">27.1.6. NFS-based storage pools</h3></div></div></div><div class="para">
+ This procedure covers creating a storage pool with a NFS mount point in <code class="command">virt-manager</code>.
+ </div><div class="section" id="idp3299216"><div class="titlepage"><div><div><h4 class="title" id="idp3299216">27.1.6.1. Creating a NFS-based storage pool with virt-manager</h4></div></div></div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Open the host storage tab</strong></p><div class="para">
+ Open the <span class="guilabel"><strong>Storage</strong></span> tab in the <span class="guilabel"><strong>Host Details</strong></span> window.
+ </div><ol class="a"><li class="step"><div class="para">
+ Open <code class="command">virt-manager</code>.
+ </div></li><li class="step"><div class="para">
+ Select a host from the main <code class="command">virt-manager</code> window. Click <span class="guilabel"><strong>Edit menu</strong></span> and select <span class="guilabel"><strong>Connection Details</strong></span>.
+ </div><div class="figure" id="nfs-connection-details"><div class="figure-contents"><div class="mediaobject"><img src="images/Connection_Details.png" width="444" alt="Connection details" /></div></div><h6>Figure 27.24. Connection details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Click on the Storage tab.
+ </div><div class="figure" id="nfs-storage-tab"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Storage tab" /></div></div><h6>Figure 27.25. Storage tab</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Create a new pool (part 1)</strong></p><div class="para">
+ Press the <span class="guilabel"><strong>+</strong></span> button (the add pool button). The <span class="guilabel"><strong>Add a New Storage Pool</strong></span> wizard appears.
+ </div><div class="figure" id="add-nfs-pool-1"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_add_nfs_step1.png" width="444" alt="Add an NFS name and type" /></div></div><h6>Figure 27.26. Add an NFS name and type</h6></div><br class="figure-break" /><div class="para">
+ Choose a name for the storage pool and press <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Create a new pool (part 2)</strong></p><div class="para">
+ Enter the target path for the device, the hostname and the NFS share path. Set the <span class="guilabel"><strong>Format</strong></span> option to <span class="guilabel"><strong>NFS</strong></span> or <span class="guilabel"><strong>auto</strong></span> (to detect the type). The target path must be identical on all hosts for migration.
+ </div><div class="para">
+ Enter the hostname or IP address of the NFS server. This example uses <code class="computeroutput">server1.example.com</code>.
+ </div><div class="para">
+ Enter the NFS path. This example uses <code class="computeroutput">/nfstrial</code>.
+ </div><div class="figure" id="nfs-add-pool-2"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_add_nfs_step2.png" width="444" alt="Create an NFS storage pool" /></div></div><h6>Figure 27.27. Create an NFS storage pool</h6></div><br class="figure-break" /><div class="para">
+ Press <span class="guibutton"><strong>Finish</strong></span> to create the new storage pool.
+ </div></li></ol></div></div><div class="section" id="del-stor-pool-nfs"><div class="titlepage"><div><div><h4 class="title">27.1.6.2. Deleting a storage pool using virt-manager</h4></div></div></div><div class="para">
+ This procedure demonstrates how to delete a storage pool.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it. To do this, select the storage pool you want to stop and click the red X icon at the bottom of the Storage window.
+ </div><div class="figure" id="stop-icon5"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Stop Icon" /></div></div><h6>Figure 27.28. Stop Icon</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Delete the storage pool by clicking the Trash can icon. This icon is only enabled if you stop the storage pool first.
+ </div></li></ol></div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Storage_Concepts-Volumes.html"><strong>Prev</strong>26.2. Volumes </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_Administration_Guide-Storage_Volumes.html"><strong>Next</strong>Chapter 28. Volumes </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Storage_Volumes.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Storage_Volumes.html
new file mode 100644
index 0000000..a3f1796
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Storage_Volumes.html
@@ -0,0 +1,39 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 28. Volumes</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt02.html" title="Part II. Administration" /><link rel="prev" href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html" title="Chapter 27. Storage pools" /><link rel="next" href="sect-Virtualization-Storage_Volumes-Cloning_volumes.html" title="28.2. Cloning volumes" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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_Administration_Guide-Storage_Pools-Storage_Pools.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Storage_Volumes-Cloning_volumes.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_Guide-Storage_Volumes" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 28. Volumes </h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Volumes.html#sect-Virtualization-Storage_Volumes-Creating_volumes">28.1. Creating volumes</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Storage_Volumes-Cloning_volumes.html">28.2. Cloning volumes</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html">28.3. Adding storage devices to guests</a></span></dt><dd><dl><dt><span class="section
"><a href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html#sect-Virtualization-Adding_storage_devices_to_guests-Adding_file_based_storage_to_a_guest">28.3.1. Adding file based storage to a guest</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html">28.3.2. Adding hard drives and other block devices to a guest</a></span></dt><dt><span class="section"><a href="sect-Managing_storage_controllers_in_a_guest.html">28.3.3. Managing storage controllers in a guest</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Virtualization-Storage_Volumes-Deleting_volumes.html">28.4. Deleting and removing volumes</a></span></dt></dl></div><div class="section" id="sect-Virtualization-Storage_Volumes-Creating_volumes"><div class="titlepage"><div><div><h2 class="title">28.1. Creating volumes</h2></div></div></div><div class="para">
+ This section shows how to create disk volumes inside a block based storage pool. In the example below, the <code class="command">virsh vol-create-as</code> command will create a storage volume with a specific size in GB within the <em class="replaceable"><code>guest_images_disk</code></em> storage pool. As this command is repeated per volume needed, three volumes are created as shown in the example.
+ </div><pre class="screen"># virsh vol-create-as <em class="replaceable"><code>guest_images_disk</code></em> <em class="replaceable"><code>volume1</code></em> <em class="replaceable"><code>8</code></em>G
+Vol volume1 created
+
+# virsh vol-create-as <em class="replaceable"><code>guest_images_disk</code></em> <em class="replaceable"><code>volume2</code></em> <em class="replaceable"><code>8</code></em>G
+Vol volume2 created
+
+# virsh vol-create-as <em class="replaceable"><code>guest_images_disk</code></em> <em class="replaceable"><code>volume3</code></em> <em class="replaceable"><code>8</code></em>G
+Vol volume3 created
+
+# virsh vol-list <em class="replaceable"><code>guest_images_disk</code></em>
+Name Path
+-----------------------------------------
+volume1 /dev/sdb1
+volume2 /dev/sdb2
+volume3 /dev/sdb3
+
+# <code class="command">parted -s <em class="replaceable"><code>/dev/sdb</code></em> print</code>
+Model: ATA ST3500418AS (scsi)
+Disk /dev/sdb: 500GB
+Sector size (logical/physical): 512B/512B
+Partition Table: gpt
+
+Number Start End Size File system Name Flags
+2 17.4kB 8590MB 8590MB primary
+3 8590MB 17.2GB 8590MB primary
+1 21.5GB 30.1GB 8590MB primary
+
+</pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html"><strong>Prev</strong>Chapter 27. Storage pools</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-Storage_Volumes-Cloning_volumes.html"><strong>Next</strong>28.2. Cloning volumes</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Tips_and_tricks.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Tips_and_tricks.html
new file mode 100644
index 0000000..df4c4d2
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Tips_and_tricks.html
@@ -0,0 +1,26 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 25. Miscellaneous administration tasks</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt02.html" title="Part II. Administration" /><link rel="prev" href="ch24s02.html" title="24.2. Hugepage support" /><link rel="next" href="sect-mem-dump-off.html" title="25.2. Guest memory allocation" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch24s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-mem-dum
p-off.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_Guide-Tips_and_tricks" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 25. Miscellaneous administration tasks</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html#sect-Virtualization-Tips_and_tricks-Automatically_starting_guests">25.1. Automatically starting guests</a></span></dt><dt><span class="section"><a href="sect-mem-dump-off.html">25.2. Guest memory allocation</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Using_qemu_img.html">25.3. Using qemu-img</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions.html">25.4. Verifying virtualization extensions</a></span></dt><dt><span class="section"><a href="ch25s05.html">25.5. Setting KVM pr
ocessor affinities</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address.html">25.6. Generating a new unique MAC address</a></span></dt><dt><span class="section"><a href="ch25s07.html">25.7. Improving guest response time</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html">25.8. Disable SMART disk monitoring for guests</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server.html">25.9. Configuring a VNC Server</a></span></dt><dt><span class="section"><a href="sect-gracefully-shut-down-guests.html">25.10. Gracefully shutting down guests</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers.html">25.11. Virtual machine timer management with libvirt</a></span></dt><dt><span class="section"><a href="sect-perf-mon.html">25.12.
Using PMU to monitor guest performance</a></span></dt><dt><span class="section"><a href="sect-s3-s4.html">25.13. Guest virtual machine power management</a></span></dt><dt><span class="section"><a href="sect-qemu-ga.html">25.14. QEMU Guest Agent Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="sect-qemu-ga.html#sect-guest-synch">25.14.1. guest-sync</a></span></dt><dt><span class="section"><a href="subsect-guest-synch-delimited.html">25.14.2. guest-sync-delimited</a></span></dt></dl></dd><dt><span class="section"><a href="sect-limit-redirection.html">25.15. Setting a limit on device redirection</a></span></dt><dt><span class="section"><a href="sect-dynamic-vNIC.html">25.16. Dynamically changing a host or a network bridge that is attached to a virtual NIC</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" id="sect-Virtualization-Tips_and_tricks-Automatically_starting_guests"><div class="titlepage"><div><div><h2 class="title">25.1. Automatically starting guests</h2></div></div></div><div class="para">
+ This section covers how to make 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="ch24s02.html"><strong>Prev</strong>24.2. Hugepage support</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-mem-dump-off.html"><strong>Next</strong>25.2. Guest memory allocation</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Troubleshooting.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Troubleshooting.html
new file mode 100644
index 0000000..4e5835e
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Troubleshooting.html
@@ -0,0 +1,78 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix A. Troubleshooting</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt03.html" title="Part III. Appendicies" /><link rel="prev" href="pt03.html" title="Part III. Appendicies" /><link rel="next" href="apas02.html" title="A.2. kvm_stat" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pt03.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apas02.html"><strong>Next</strong></a></li></ul
><div xml:lang="en-US" class="appendix" id="chap-Virtualization_Administration_Guide-Troubleshooting" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Troubleshooting</h1></div></div></div><div class="para">
+ This chapter covers common problems and solutions for Fedora virtualization issues.
+ </div><div class="para">
+ Read this chapter to develop an understanding of some of the common problems associated with virtualization technologies. Troubleshooting takes practice and experience which are difficult to learn from a book. It is recommended that you experiment and test virtualization on Fedora 19 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-Additional_resources.html#sect-Virtualization-Additional_resources-Online_resources">Section I.1, “Online resources”</a> for a list of Linux virtualization websites.
+ </div><div class="section" id="sect-Virtualization-Troubleshooting_-Debugging_and_troubleshooting_"><div class="titlepage"><div><div><h2 class="title">A.1. Debugging and troubleshooting tools</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="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">kvm_stat</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">trace-cmd</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">vmstat</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">iostat</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">lsof</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">systemtap</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">crash</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">sysrq</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">sysrq t</code>
+ </div></li><li class="listitem"><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 class="listitem"><div class="para">
+ <code class="command">ifconfig</code>
+ </div></li><li class="listitem"><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 class="listitem"><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 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
+-----------------------------------------------------------------------------
+virtbr0 8000.feffffff yes eth0
+
+# brctl showmacs virtbr0
+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 virtbr0
+virtbr0
+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.
+ </div><div class="itemizedlist"><ul><li class="listitem"><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 class="listitem"><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 class="listitem"><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="pt03.html"><strong>Prev</strong>Part III. Appendicies</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="apas02.html"><strong>Next</strong>A.2. kvm_stat</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Virtual_Networking.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Virtual_Networking.html
new file mode 100644
index 0000000..d8c0e54
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Virtual_Networking.html
@@ -0,0 +1,34 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix H. Virtual Networking</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt03.html" title="Part III. Appendicies" /><link rel="prev" href="sect-libguestfs-more-docs.html" title="G.13. Where to find further documentation" /><link rel="next" href="sect-Network_Address_Translation-libvirt.html" title="H.2. Network Address Translation" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libguestfs-more-docs.html"><st
rong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Network_Address_Translation-libvirt.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="appendix" id="chap-Virtualization_Administration_Guide-Virtual_Networking" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Virtual Networking</h1></div></div></div><div class="para">
+ This chapter introduces the concepts needed to create, start, stop, remove, and modify virtual networks with libvirt.
+ </div><div class="para">
+ Additional information can be found in the libvirt reference chapter
+ </div><div class="section" id="sect-virtual_network-switches-livbvirt"><div class="titlepage"><div><div><h2 class="title">H.1. Virtual network switches</h2></div></div></div><div class="para">
+ Libvirt virtual networking uses the concept of a <span class="emphasis"><em>virtual network switch</em></span>. A virtual network switch is a software construct that operates on a host server, to which virtual machines (guests) connect. The network traffic for a guest is directed through this switch:
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-Switch_with_two_guests"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-02-switchandtwoguests.png" alt="Virtual network switch with two guests" /></div></div><h6>Figure H.1. Virtual network switch with two guests</h6></div><br class="figure-break" /><div class="para">
+ Linux host servers represent a virtual network switch as a network interface. When the libvirtd daemon (<code class="command">libvirtd</code>) is first installed and started, the default network interface representing the virtual network switch is <code class="command">virbr0</code>.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-Linux_host_with_switch"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-03-hostwithswitch.png" alt="Linux host with an interface to a virtual network switch" /></div></div><h6>Figure H.2. Linux host with an interface to a virtual network switch</h6></div><br class="figure-break" /><div class="para">
+ This <code class="command">virbr0</code> interface can be viewed with the <code class="command">ifconfig</code> and <code class="command">ip</code> commands like any other interface:
+ </div><pre class="screen">
+$ ifconfig virbr0
+ virbr0 Link encap:Ethernet HWaddr 1B:C4:94:CF:FD:17
+ inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
+ UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
+ RX packets:0 errors:0 dropped:0 overruns:0 frame:0
+ TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
+ collisions:0 txqueuelen:0
+ RX bytes:0 (0.0 b) TX bytes:3097 (3.0 KiB)
+</pre><pre class="screen">
+ $ ip addr show virbr0
+ 3: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
+ link/ether 1b:c4:94:cf:fd:17 brd ff:ff:ff:ff:ff:ff
+ inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
+</pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libguestfs-more-docs.html"><strong>Prev</strong>G.13. Where to find further 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="sect-Network_Address_Translation-libvirt.html"><strong>Next</strong>H.2. Network Address Translation</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_GuideAdvanced.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_GuideAdvanced.html
new file mode 100644
index 0000000..c1d0424
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_GuideAdvanced.html
@@ -0,0 +1,18 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 24. Advanced virtualization administration</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt02.html" title="Part II. Administration" /><link rel="prev" href="chap-KSM.html" title="Chapter 23. KSM" /><link rel="next" href="ch24s02.html" title="24.2. Hugepage support" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-KSM.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch24s02.html"><strong>Next</stron
g></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_GuideAdvanced" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 24. Advanced virtualization administration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Administration_GuideAdvanced.html#idm7175824">24.1. Control Groups (cgroups)</a></span></dt><dt><span class="section"><a href="ch24s02.html">24.2. Hugepage support</a></span></dt></dl></div><div class="para">
+ This chapter covers advanced administration tools for fine tuning and controlling guests and host system resources.
+ </div><div class="section" id="idm7175824"><div class="titlepage"><div><div><h2 class="title" id="idm7175824">24.1. Control Groups (cgroups)</h2></div></div></div><div class="para">
+ Fedora 19 provides a new kernel feature: <em class="firstterm">control groups</em>, which are often referred to as <em class="firstterm">cgroups</em>. Cgroups allow you to allocate resources such as CPU time, system memory, network bandwidth, or combinations of these resources among user-defined groups of tasks (processes) running on a system. You can monitor the cgroups you configure, deny cgroups access to certain resources, and even reconfigure your cgroups dynamically on a running system.
+ </div><div class="para">
+ The cgroup functionality is fully supported by libvirt. By default, libvirt puts each guest into a separate control group for various controllers (such as memory, cpu, blkio, device).
+ </div><div class="para">
+ When a guest is started, it is already in a cgroup. The only configuration that may be required is the setting of policies on the cgroups. Refer to the <em class="citetitle">Fedora Resource Management Guide</em> for more information on cgroups.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-KSM.html"><strong>Prev</strong>Chapter 23. KSM</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="ch24s02.html"><strong>Next</strong>24.2. Hugepage support</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html
new file mode 100644
index 0000000..26e2b8f
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html
@@ -0,0 +1,28 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 6. Guest virtual machine installation overview</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html" title="5.2. Installing virtualization packages on an existing Fedora system" /><link rel="next" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install.html" title="6.2. Creating guests with virt-install" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product
Site" /></a><a class="right" href="http://docs.redhat.com"><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_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 6. Guest virtual machine installation overview</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installati
on_Guide-Guest_Installation.html#idp26095728">6.1. Guest virtual machine prerequisites and considerations</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install.html">6.2. Creating guests with virt-install</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html">6.3. Creating guests with virt-manager</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE.html">6.4. Installing guest virtual machines 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 guest virtual machines 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 in the following chapters for specific versions of Fedora and Microsoft Windows.
+ </div><div class="section" id="idp26095728"><div class="titlepage"><div><div><h2 class="title" id="idp26095728">6.1. Guest virtual machine prerequisites and considerations</h2></div></div></div><div class="para">
+ Various factors should be considered before creating any guest virtual machines. Not only should the role of a virtual machine be considered before deployment, but regular ongoing monitoring and assessment based on variable factors (load, amount of clients) should be performed. Some factors include:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Performance</span></dt><dd><div class="para">
+ Guest virtual machines should be deployed and configured based on their intended tasks. Some guest systems (for instance, guests running a database server) may require special performance considerations. Guests may require more assigned CPUs or memory based on their role and projected system load.
+ </div></dd><dt class="varlistentry"><span class="term">Input/Output requirements and types of Input/Output</span></dt><dd><div class="para">
+ Some guest virtual machines may have a particularly high I/O requirement or may require further considerations or projections based on the type of I/O (for instance, typical disk block size access, or the amount of clients).
+ </div></dd><dt class="varlistentry"><span class="term">Storage</span></dt><dd><div class="para">
+ Some guest virtual machines may require higher priority access to storage or faster disk types, or may require exclusive access to areas of storage. The amount of storage used by guests should also be regularly monitored and taken into account when deploying and maintaining storage.
+ </div></dd><dt class="varlistentry"><span class="term">Networking and network infrastructure</span></dt><dd><div class="para">
+ Depending upon your environment, some guest virtual machines could require faster network links than other guests. Bandwidth or latency are often factors when deploying and maintaining guests, especially as requirements or load changes.
+ </div></dd><dt class="varlistentry"><span class="term">Request requirements</span></dt><dd><div class="para">
+ SCSI requests can only be issued to guest virtual machines on virtio drives if the virtio drives are backed by whole disks, and the disk device parameter is set to <code class="literal">lun</code>, as shown in the following example:
+ </div><pre class="screen"><devices>
+ <emulator>/usr/libexec/qemu-kvm</emulator>
+ <disk type='block' device='lun'></pre></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html"><strong>Prev</strong>5.2. Installing virtualization packages on an exi...</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_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install.html"><strong>Next</strong>6.2. Creating guests with virt-install</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html
new file mode 100644
index 0000000..ffa323e
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html
@@ -0,0 +1,62 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.3. Creating guests with virt-manager</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html" title="Chapter 6. Guest virtual machine installation overview" /><link rel="prev" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install.html" title="6.2. Creating guests with virt-install" /><link rel="next" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE.html" title="6.4. Installing guest virtual machines with PXE" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img sr
c="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager" lang="en-US"><div class="titlepage"><div><div><h2 class="title">6.3. 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 guest virtual machines.
+ </div><div class="procedure" id="proc-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_a_virtualized_guest_with_virt_manager"><h6>Procedure 6.1. Creating a guest virtual machine with <span class="application"><strong>virt-manager</strong></span></h6><ol class="1"><li class="step"><p class="title"><strong>Open virt-manager</strong></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 class="step"><p class="title"><strong>Optional: Open a remote hypervisor</strong></p><div class="para">
+ Select the hypervisor and press the <span class="guibutton"><strong>Connect</strong></span> button to connect to the remote hypervisor.
+ </div></li><li class="step"><p class="title"><strong>Create a new virtual machine</strong></p><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>Create a new virtual machine</strong></span> button (<a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html#virt-manager_main-png">Figure 6.1, “Virtual Machine Manager window”</a>) to open the <span class="guimenu"><strong>New VM</strong></span> wizard.
+ </div><div class="figure" id="virt-manager_main-png"><div class="figure-contents"><div class="mediaobject"><img src="images/rhel6_virt_manager.png" alt="Virtual Machine Manager window" /></div></div><h6>Figure 6.1. Virtual Machine Manager window</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guimenu"><strong>New VM</strong></span> wizard breaks down the virtual machine creation process into five steps:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Naming the guest virtual machine and choosing the installation type
+ </div></li><li class="listitem"><div class="para">
+ Locating and configuring the installation media
+ </div></li><li class="listitem"><div class="para">
+ Configuring memory and CPU options
+ </div></li><li class="listitem"><div class="para">
+ Configuring the virtual machine's storage
+ </div></li><li class="listitem"><div class="para">
+ Configuring networking, architecture, and other hardware settings
+ </div></li></ol></div><div class="para">
+ Ensure that <code class="command">virt-manager</code> can access the installation media (whether locally or over the network) before you continue.
+ </div></li><li class="step"><p class="title"><strong>Specify name and installation type</strong></p><div class="para">
+ The guest virtual machine creation process starts with the selection of a name and installation type. Virtual machine names can have underscores (<code class="computeroutput">_</code>), periods (<code class="computeroutput">.</code>), and hyphens (<code class="computeroutput">-</code>).
+ </div><div class="figure" id="Virtual_Machine_Name-guest-install-png"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt2-pic2.png" alt="Name virtual machine and select installation method" /></div></div><h6>Figure 6.2. Name virtual machine and select installation method</h6></div><br class="figure-break" /><div class="para">
+ Type in a virtual machine name and choose an installation type:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Local install media (ISO image or CDROM)</span></dt><dd><div class="para">
+ This method uses a CD-ROM, DVD, or image of an installation disk (for example, <code class="filename">.iso</code>).
+ </div></dd><dt class="varlistentry"><span class="term">Network Install (HTTP, FTP, or NFS)</span></dt><dd><div class="para">
+ Network installing involves the use of a mirrored Fedora installation tree to install a guest. The installation tree must be accessible through either HTTP, FTP, or NFS.
+ </div></dd><dt class="varlistentry"><span class="term">Network Boot (PXE)</span></dt><dd><div class="para">
+ This method uses a Preboot eXecution Environment (PXE) server to install the guest virtual machine. Setting up a PXE server is covered in the <em class="citetitle">Deployment Guide</em>. To install via network boot, the guest must have a routable IP address or shared network device. For information on the required networking configuration for PXE installation, refer to <a class="xref" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE.html">Section 6.4, “Installing guest virtual machines with PXE”</a>.
+ </div></dd><dt class="varlistentry"><span class="term">Import existing disk image</span></dt><dd><div class="para">
+ This method allows you to create a new guest virtual machine and import a disk image (containing a pre-installed, bootable operating system) to it.
+ </div></dd></dl></div><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Configure installation</strong></p><div class="para">
+ Next, configure the <span class="guimenuitem"><strong>OS type</strong></span> and <span class="guimenuitem"><strong>Version</strong></span> of the installation. Ensure that you select the appropriate OS type for your virtual machine. Depending on the method of installation, provide the install URL or existing storage path.
+ </div><div class="figure" id="Virtual_Machine_Name-guest-install_STEP2-local-png"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt2-pic3.png" alt="Remote installation URL" /></div></div><h6>Figure 6.3. Remote installation URL</h6></div><br class="figure-break" /><div class="figure" id="Virtual_Machine_Name-guest-install_STEP2-import-png"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt1-pic5.png" alt="Local ISO image installation" /></div></div><h6>Figure 6.4. Local ISO image installation</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Configure CPU and memory</strong></p><div class="para">
+ The next step involves configuring the number of CPUs and amount of memory to allocate to the virtual machine. The wizard shows the number of CPUs and amount of memory you can allocate; configure these settings and click <span class="guibutton"><strong>Forward</strong></span>.
+ </div><div class="figure" id="Virtual_Machine_Name-guest-install_STEP2-cpumem-png"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt1-pic6.png" alt="Configuring CPU and Memory" /></div></div><h6>Figure 6.5. Configuring CPU and Memory</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Configure storage</strong></p><div class="para">
+ Assign storage to the guest virtual machine.
+ </div><div class="figure" id="Virtual_Machine_Name-guest-install_STEP4-png"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt1-pic7.png" alt="Configuring virtual storage" /></div></div><h6>Figure 6.6. Configuring virtual storage</h6></div><br class="figure-break" /><div class="para">
+ If you chose to import an existing disk image during the first step, <code class="command">virt-manager</code> will skip this step.
+ </div><div class="para">
+ Assign sufficient space for your virtual machine and any applications it requires, then click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Final configuration</strong></p><div class="para">
+ Verify the settings of the virtual machine and click <span class="guibutton"><strong>Finish</strong></span> when you are satisfied; doing so will create the virtual machine with default networking settings, virtualization type, and architecture.
+ </div><div class="figure" id="Virtual_Machine_Name-guest-install_STEP5-finish-png"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt1-pic9-local-storage.png" alt="Verifying the configuration" /></div></div><h6>Figure 6.7. Verifying the configuration</h6></div><br class="figure-break" /><div class="para">
+ If you prefer to further configure the virtual machine's hardware first, check the <span class="guimenuitem"><strong>Customize configuration before install</strong></span> box first before clicking <span class="guibutton"><strong>Finish</strong></span>. Doing so will open another wizard that will allow you to add, remove, and configure the virtual machine's hardware settings.
+ </div><div class="para">
+ After configuring the virtual machine's hardware, click <span class="guibutton"><strong>Apply</strong></span>. <code class="command">virt-manager</code> will then create the virtual machine with your specified hardware settings.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install.html"><strong>Prev</strong>6.2. Creating guests with virt-install</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_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE.html"><strong>Next</strong>6.4. Installing guest virtual machines with PXE</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html
new file mode 100644
index 0000000..c14ec00
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html
@@ -0,0 +1,43 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 5. Installing the virtualization packages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions.html" title="4.3. Other restrictions" /><link rel="next" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html" title="5.2. Installing virtualization packages on an existing Fedora system" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class=
"right" href="http://docs.redhat.com"><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_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 5. Installing the virtualization packages</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html#s
ect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_with_a_new_Red_Hat_Enterprise_Linux_installation">5.1. Configuring a Virtualization Host installation</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html">5.2. Installing virtualization 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 your computer. Virtualization packages can be installed either during the host installation sequence or after host installation using the <code class="command">yum</code> command and the Fedora Project download page.
+ </div><div class="para">
+ The KVM hypervisor uses the default Fedora kernel with the <span class="package">kvm</span> kernel module.
+ </div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_with_a_new_Red_Hat_Enterprise_Linux_installation"><div class="titlepage"><div><div><h2 class="title">5.1. Configuring a Virtualization Host installation</h2></div></div></div><div class="para">
+ This section covers installing virtualization tools and virtualization packages as part of a fresh Fedora installation.
+ </div><div class="procedure"><h6>Procedure 5.1. Installing the virtualization package group</h6><ol class="1"><li class="step"><p class="title"><strong>Launch the Fedora installation program</strong></p><div class="para">
+ Start an interactive Fedora installation from the Fedora Installation CD-ROM, DVD or PXE.
+ </div></li><li class="step"><p class="title"><strong>Continue installation up to package selection</strong></p><div class="para">
+ Complete the other steps up to the package selection step.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/RHELcustomize15.png" width="444" alt="The Fedora package selection screen showing options to select a different set of software from regular installation. Virtualization Host is selected in the upper menu, and Fedora is selected from the list of additional repositories. Customize now is selected at the bottom of the window, with Back and Next buttons shown at the bottom right corner of the window." /></div></div><h6>Figure 5.1. The Fedora package selection screen</h6></div><br class="figure-break" /><div class="para">
+ Select the <span class="guilabel"><strong>Virtualization Host</strong></span> server role to install a platform for guest virtual machines. Alternatively, ensure that the <span class="guilabel"><strong>Customize Now</strong></span> radio button is selected before proceeding, to specify individual packages.
+ </div></li><li class="step"><p class="title"><strong>Select the <span class="guilabel"><strong>Virtualization</strong></span> package group.</strong></p><div class="para">
+ This selects the qemu-kvm emulator, <code class="command">virt-manager</code>, <code class="command">libvirt</code> and <code class="command">virt-viewer</code> for installation.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/RHELkvmSelect.png" width="444" alt="The Fedora package selection screen with Virtualization selected in the left menu." /></div></div><h6>Figure 5.2. The Fedora package selection screen</h6></div><br class="figure-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If you wish to create virtual machines in a graphical user interface (<span class="application"><strong>virt-manager</strong></span>) later, you should also select the <code class="systemitem">General Purpose Desktop</code> package group.
+ </div></div></div></li><li class="step" id="step-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Customize_the_packages_if_required"><p class="title"><strong>Customize the packages (if required)</strong></p><div class="para">
+ Customize the <span class="guilabel"><strong>Virtualization</strong></span> group if you require other virtualization packages.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/RHELKVMpackages-2.png" width="444" alt="The Fedora package selection screen with a pop-up Packages in Virtualization window showing the packages available to be installed." /></div></div><h6>Figure 5.3. The Fedora package selection screen</h6></div><br class="figure-break" /><div class="para">
+ Click on the <span class="guilabel"><strong>Close</strong></span> button, then the <span class="guilabel"><strong>Next</strong></span> button to continue the installation.
+ </div></li></ol></div><div class="para">
+ When the installation is complete, reboot the system.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ You require a valid RHN virtualization entitlement to receive updates for the virtualization packages.
+ </div></div></div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_with_Kickstart_files"><h5 class="formalpara">Installing KVM packages with Kickstart files</h5>
+ Kickstart files allow for large, automated installations without a user manually installing each individual host system. This section describes how to create and use 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 groups:
+ </div><pre class="screen">@virtualization
+ at virtualization-client
+ at virtualization-platform
+ at virtualization-tools</pre><div class="para">
+ For more information about Kickstart files, refer to the Fedora <em class="citetitle">Installation Guide</em>, available from <a href="https://access.redhat.com/knowledge/docs/Red_Hat_Enterprise_Linux/">https://access.redhat.com/knowledge/docs/Red_Hat_Enterprise_Linux/</a>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions.html"><strong>Prev</strong>4.3. Other restrictions</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_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html"><strong>Next</strong>5.2. Installing virtualization packages on an exi...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html
new file mode 100644
index 0000000..8d4bbe3
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html
@@ -0,0 +1,18 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 1. Introduction</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="pt01.html" title="Part I. Deployment" /><link rel="next" href="ch01s02.html" title="1.2. Virtualization Documentation Suite" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pt01.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch01s02.html"><strong>Next
</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 1. Introduction</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html#idp12674320">1.1. What is in this guide?</a></span></dt><dt><span class="section"><a href="ch01s02.html">1.2. Virtualization Documentation Suite</a></span></dt></dl></div><div class="section" id="idp12674320"><div class="titlepage"><div><div><h2 class="title" id="idp12674320">1.1. What is in this guide?</h2></div></div></div><div class="para">
+ The <em class="citetitle">Virtualization Deployment and Administration Guide</em>, introduced in Fedora 19, resulted from the merger of the <em class="citetitle">Virtualization Host Installation and Guest Configuration Guide</em> and the <em class="citetitle">Virtualization Administration Guide</em>. This new guide provides complete information on both deploying a virtual setup on a Fedora virtualization host as well as how to administer and maintain the system. As such, this guide has 2 main parts:Deployment and Adminsitration. The appendix sections contain references and troubleshooting.
+ </div><div class="para">
+ The initial chapters in this guide outline the prerequisites to enable a Fedora host machine to deploy virtualization. System requirements, compatible hardware, support and product restrictions are covered in detail. The first part of this guide (Deployment) covers basic host configuration, including mandatory and optional virtualization packages, which are covered in <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html">Chapter 5, <em>Installing the virtualization packages</em></a>. Later chapters in this part include guest virtual machine installation, which is covered in detail starting from <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html">Chapter 6, <em>Guest virtual machine installation overview</em></a>, with procedures for installing fully virtualized Fedora guests and Windows para-virtualized guests using virt-manager and virsh. The part
concludes with More detailed information on networking, PCI device configuration, SR-IOV, KVM guest timing management, and troubleshooting help for libvirt and SR-IOV is included later in the guide.
+ </div><div class="para">
+ The second part of this guide (Administration) covers more advanced configuration tactics, creating various storage pools and volumes, manipulating and finetuning memory and other resources, as well as administration tasks that can be performed using virsh and virt-manager to administer both hosts and guests.
+ </div><div class="para">
+ The last part of this guide (Appendix) contains troubleshooting information with steps that should be done before getting technical support (if possible), detailed reference guides for using QEMU-KVM flags, describing the Domain XML, and a complete CLI description of the commands used in Virsh and the screens used in Virt-manager. Additional tools that may be useful are also described in this part as well.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pt01.html"><strong>Prev</strong>Part I. Deployment</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="ch01s02.html"><strong>Next</strong>1.2. Virtualization Documentation Suite</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html
new file mode 100644
index 0000000..4f2b99d
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html
@@ -0,0 +1,24 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 3. KVM guest virtual machine compatibility</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_Requirements.html" title="Chapter 2. System requirements" /><link rel="next" href="ch03s02.html" title="3.2. Supported CPU Models" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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_Host_C
onfiguration_and_Guest_Installation_Guide-System_Requirements.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch03s02.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 3. KVM guest virtual machine compatibility</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html#idp4241536">3.1. Fedora 6 support limits</a></span></dt><dt><span class="section"><a href="ch03s02.html">3.2. Supported CPU Models</a></span></dt><dd><dl><dt><span class="section"><a href="ch03s02.html#para-CPU_Models">3.2.1. Guest CPU models</a></span></dt></dl></dd></dl></div><div class="para">
+ To verify whether your processor supports the virtualization extensions and for information on enabling the virtualization extensions if they are disabled, refer to the <em class="citetitle">Fedora Virtualization Administration Guide</em>.
+ </div><div class="section" id="idp4241536"><div class="titlepage"><div><div><h2 class="title" id="idp4241536">3.1. Fedora 6 support limits</h2></div></div></div><div class="para">
+ Fedora 19 servers have certain support limits.
+ </div><div class="para">
+ The following URLs explain the processor and memory amount limitations for Fedora 19:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ For host systems: <a href="http://www.redhat.com/resourcelibrary/articles/articles-red-hat-enterprise-linux-6-technology-capabilities-and-limits">http://www.redhat.com/resourcelibrary/articles/articles-red-hat-enterprise-linux-6-technology-capabilities-and-limits</a>
+ </div></li><li class="listitem"><div class="para">
+ For hypervisors: <a href="http://www.redhat.com/resourcelibrary/articles/virtualization-limits-rhel-hypervisors">http://www.redhat.com/resourcelibrary/articles/virtualization-limits-rhel-hypervisors</a>
+ </div></li></ul></div><div class="para">
+ The following URL is a complete reference showing supported operating systems and host and guest combinations:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.redhat.com/resourcelibrary/articles/enterprise-linux-virtualization-support">http://www.redhat.com/resourcelibrary/articles/enterprise-linux-virtualization-support</a>
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_Requirements.html"><strong>Prev</strong>Chapter 2. System requirements</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="ch03s02.html"><strong>Next</strong>3.2. Supported CPU Models</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management.html
new file mode 100644
index 0000000..bd26a7b
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management.html
@@ -0,0 +1,79 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 14. KVM guest timing management</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="ch13s03.html" title="13.3. Troubleshooting SR-IOV" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html" title="Chapter 15. Network booting with libvirt" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch13s03.h
tml"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 14. KVM guest timing management</h2></div></div></div><div class="para">
+ Virtualization involves several intrinsic challenges for time keeping in guest virtual machines. Interrupts cannot always be delivered simultaneously and instantaneously to all guest virtual machines, because interrupts in virtual machines are not true interrupts; they are injected into the guest virtual machine by the host machine. The host may be running another guest virtual machine, or a different process, meaning that the precise timing typically required by interrupts may not always be possible.
+ </div><div class="para">
+ Guest virtual machines without accurate time keeping may experience issues with network applications and processes, as session validity, migration, and other network activities rely on timestamps to remain correct.
+ </div><div class="para">
+ KVM avoids these issues by providing guest virtual machines with a para-virtualized clock (<span class="application"><strong>kvm-clock</strong></span>). However, it is still vital to test timing before attempting activities that may be affected by time keeping inaccuracies.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Fedora 17 and newer, uses <span class="application"><strong>kvm-clock</strong></span> as their default clock source. Running without <span class="application"><strong>kvm-clock</strong></span> requires special configuration, and is not recommended.
+ </div></div></div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The Network Time Protocol (NTP) daemon should be running on the host and the guest virtual machines. 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">
+ The <code class="systemitem">ntpd</code> service will correct the effects of clock skew as long as the clock runs no more than 0.05% faster or slower than the reference time source. The <code class="systemitem">ntp</code> startup script adjusts the clock offset from the reference time by adjusting the system clock at startup time, if required.
+ </div></div></div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management-Determining_if_your_CPU_has_the_constant_Time_Stamp_Counter"><h5 class="formalpara">Constant Time Stamp Counter (TSC)</h5>
+ Modern Intel and AMD CPUs provide a constant Time Stamp Counter (TSC). The count frequency of the constant TSC does not vary when the CPU core itself changes frequency, for example, to comply with a power saving policy. A CPU with a constant TSC frequency is necessary in order to use the TSC as a clock source for KVM guests.
+ </div><div class="para">
+ 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" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management-Configuring_hosts_without_a_constant_Time_Stamp_Counter"><h5 class="formalpara">Configuring hosts without a constant Time Stamp Counter</h5>
+ Systems without a constant TSC frequency cannot use the TSC as a clock source for virtual machines, and require additional configuration. Power management features interfere with accurate time keeping and must be disabled for guest virtual machines to accurately keep time with KVM.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ These instructions are for AMD revision F CPUs only.
+ </div></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. Deep C sleep states can stop the TSC. To prevent the kernel using deep C states append <code class="command">processor.max_cstate=1</code> to the kernel boot options in the <code class="filename">grub.conf</code> file on the host:
+ </div><pre class="screen">title Fedora (2.6.32-330.x86_64)
+ root (hd0,0)
+ kernel /vmlinuz-2.6.32-330.x86_64 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" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management-Required_parameters_for_RHEL_guests"><h5 class="formalpara">Required parameters for Fedora Linux guests</h5>
+ For certain Fedroa guest virtual machines, additional kernel parameters are required. These parameters can be set by appending them to the end of the <code class="literal">/kernel</code> line in the <code class="filename">/boot/grub/grub.conf</code> file of the guest virtual machine.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The <em class="parameter"><code>lpj</code></em> parameter requires a numeric value equal to the <span class="emphasis"><em>loops per jiffy</em></span> value of the specific CPU on which the guest virtual machine runs. If you do not know this value, do not set the <em class="parameter"><code>lpj</code></em> parameter.
+ </div></div></div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ The <em class="parameter"><code>divider</code></em> kernel parameter was previously recommended for Fedora guest virtual machines that did not have high responsiveness requirements, or exist on systems with high guest density. It is no longer recommended for use with guests running Fedora versions prior to version 16.
+ </div></div></div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management-KVM_guest_timing_management-Using_the_Real_Time_Clock_with_Windows_guests"><h5 class="formalpara">Using the Real-Time Clock with Windows Server 2003 and Windows XP guests</h5>
+ Windows uses the both the Real-Time Clock (RTC) and the Time Stamp Counter (TSC). For Windows guest virtual machines the Real-Time Clock can be used instead of the TSC for all time sources which resolves guest timing issues.
+ </div><div class="para">
+ To enable the Real-Time Clock for the <code class="computeroutput">PMTIMER</code> clock source (the <code class="computeroutput">PMTIMER</code> usually uses the TSC), add the following option to the Windows boot settings. Windows boot settings are stored in the boot.ini file. Add the following option to the end of the Windows boot line in the <code class="filename">boot.ini</code> file:
+ </div><pre class="screen">/usepmtimer
+</pre><div class="para">
+ For more information on Windows boot settings and the usepmtimer 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 class="formalpara"><h5 class="formalpara" id="idp7308464">Using the Real-Time Clock with Windows Server 2008, Windows Server 2008 R2, and Windows 7 guests</h5>
+ Windows uses the both the Real-Time Clock (RTC) and the Time Stamp Counter (TSC). For Windows guest virtual machines the Real-Time Clock can be used instead of the TSC for all time sources, which resolves guest timing issues.
+ </div><div class="para">
+ The <code class="filename">boot.ini</code> file is no longer used as of Windows Server 2008 and newer. Windows Server 2008, Windows Server 2008 R2, and Windows 7 do not use the TSC as a time source if the <code class="literal">hypervisor-present</code> bit is set. The Fedora KVM hypervisor enables this CPUID bit by default, so it is no longer necessary to use the <span class="application"><strong>Boot Configuration Data Editor</strong></span> (<code class="command">bcdedit.exe</code>) to modify the Windows boot parameters.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Open the Windows guest virtual machine.
+ </div></li><li class="step"><div class="para">
+ Open the <span class="guimenuitem"><strong>Accessories</strong></span> menu of the <span class="guimenuitem"><strong>start</strong></span> menu. Right click on the <span class="application"><strong>Command Prompt</strong></span> application, select <span class="guilabel"><strong>Run as Administrator</strong></span>.
+ </div></li><li class="step"><div class="para">
+ Confirm the security exception, if prompted.
+ </div></li><li class="step"><div class="para">
+ Set the boot manager to use the platform clock. This should instruct Windows to use the PM timer for the primary clock source. The system UUID (<em class="parameter"><code>{default}</code></em> in the example below) should be changed if the system UUID is different than the default boot device.
+ </div><pre class="screen">C:\Windows\system32>bcdedit /set {default} USEPLATFORMCLOCK on
+The operation completed successfully</pre></li></ol></div><div class="para">
+ This fix should improve time keeping for Windows Server 2008 and Windows 7 guests.
+ </div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management-Steal_Time_Accounting"><h5 class="formalpara">Steal time accounting</h5>
+ Steal time is the amount of CPU time desired by a guest virtual machine that is not provided by the host. Steal time occurs when the host allocates these resources elsewhere: for example, to another guest.
+ </div><div class="para">
+ Steal time is reported in the CPU time fields in <code class="filename">/proc/stat</code> as <em class="parameter"><code>st</code></em>. It is automatically reported by utilities such as <code class="command">top</code> and <code class="command">vmstat</code>, and cannot be switched off.
+ </div><div class="para">
+ Large amounts of steal time indicate CPU contention, which can reduce guest performance. To relieve CPU contention, increase the guest's CPU priority or CPU quota, or run fewer guests on the host.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch13s03.html"><strong>Prev</strong>13.3. Troubleshooting SR-IOV</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_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html"><strong>Next</strong>Chapter 15. Network booting with libvirt</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html
new file mode 100644
index 0000000..4125b76
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html
@@ -0,0 +1,39 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 15. Network booting with libvirt</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management.html" title="Chapter 14. KVM guest timing management" /><link rel="next" href="ch15s02.html" title="15.2. Booting a guest using PXE" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="cha
p-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch15s02.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 15. Network booting with libvirt</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html#idp1296992">15.1. Preparing the boot server</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html#idm8060224">15.1.1. Setting up a PXE boot server on a private libvirt network</a></span></dt></dl></dd><dt><span class="section"><a href="ch15s02.html">15.
2. Booting a guest using PXE</a></span></dt><dd><dl><dt><span class="section"><a href="ch15s02.html#idp22499056">15.2.1. Using bridged networking</a></span></dt><dt><span class="section"><a href="ch15s02s02.html">15.2.2. Using a private libvirt network</a></span></dt></dl></dd></dl></div><div class="para">
+ Guest virtual machines can be booted with PXE enabled. PXE allows guest virtual machines to boot and load their configuration off the network itself. This section demonstrates some basic configuration steps to configure PXE guests with libvirt.
+ </div><div class="para">
+ This section does not cover the creation of boot images or PXE servers. It is used to explain how to configure libvirt, in a private or bridged network, to boot a guest virtual machine with PXE booting enabled.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ These procedures are provided only as an example. Ensure that you have sufficient backups before proceeding.
+ </div></div></div><div class="section" id="idp1296992"><div class="titlepage"><div><div><h2 class="title" id="idp1296992">15.1. Preparing the boot server</h2></div></div></div><div class="para">
+ To perform the steps in this chapter you will need:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ A PXE Server (DHCP and TFTP) - This can be a libvirt internal server, manually-configured dhcpd and tftpd, dnsmasq, a server configured by Cobbler, or some other server.
+ </div></li><li class="listitem"><div class="para">
+ Boot images - for example, PXELINUX configured manually or by Cobbler.
+ </div></li></ul></div><div class="section" id="idm8060224"><div class="titlepage"><div><div><h3 class="title" id="idm8060224">15.1.1. Setting up a PXE boot server on a private libvirt network</h3></div></div></div><div class="para">
+ This example uses the <span class="emphasis"><em>default</em></span> network. Perform the following steps:
+ </div><div class="procedure"><h6>Procedure 15.1. Configuring the PXE boot server</h6><ol class="1"><li class="step"><div class="para">
+ Place the PXE boot images and configuration in <code class="filename">/var/lib/tftp</code>.
+ </div></li><li class="step"><div class="para">
+ Run the following commands:
+ </div><pre class="screen"># virsh net-destroy default
+# virsh net-edit default</pre></li><li class="step"><div class="para">
+ Edit the <code class="code"><ip></code> element in the configuration file for the <span class="emphasis"><em>default</em></span> network to include the appropriate address, network mask, DHCP address range, and boot file, where <em class="replaceable"><code>BOOT_FILENAME</code></em> represents the file name you are using to boot the guest virtual machine.
+ </div><pre class="screen"><ip address='192.168.122.1' netmask='255.255.255.0'>
+ <tftp root='/var/lib/tftp' />
+ <dhcp>
+ <range start='192.168.122.2' end='192.168.122.254' />
+ <bootp file='<em class="replaceable"><code>BOOT_FILENAME</code></em>' />
+ </dhcp>
+</ip></pre></li><li class="step"><div class="para">
+ Boot the guest using PXE (refer to <a class="xref" href="ch15s02.html#booting-guest-with-pxe">Section 15.2, “Booting a guest using PXE”</a>).
+ </div></li></ol></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management.html"><strong>Prev</strong>Chapter 14. 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="ch15s02.html"><strong>Next</strong>15.2. Booting a guest using PXE</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html
new file mode 100644
index 0000000..caafaad
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html
@@ -0,0 +1,57 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 11. Network configuration</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html" title="10.6. Using KVM para-virtualized drivers for new devices" /><link rel="next" href="ch11s02.html" title="11.2. Disabling vhost-net" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_ri
ght.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch11s02.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 11. Network configuration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_address_translation_NAT_with_libvirt">11.1. Network Addre
ss Translation (NAT) with libvirt</a></span></dt><dt><span class="section"><a href="ch11s02.html">11.2. Disabling vhost-net</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html">11.3. Bridged networking with libvirt</a></span></dt></dl></div><div class="para">
+ This chapter provides an introduction to the common networking configurations used by libvirt based guest virtual machines. For additional information, consult the libvirt network architecture documentation: <a href="http://libvirt.org/intro.html">http://libvirt.org/intro.html</a>.
+ </div><div class="para">
+ Fedora supports the following networking setups for virtualization:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ virtual networks using Network Address Translation (<em class="firstterm">NAT</em>)
+ </div></li><li class="listitem"><div class="para">
+ directly allocated physical devices using PCI device assignment
+ </div></li><li class="listitem"><div class="para">
+ directly allocated virtual functions using PCIe SR-IOV
+ </div></li><li class="listitem"><div class="para">
+ bridged networks
+ </div></li></ul></div><div class="para">
+ You must enable NAT, network bridging or directly assign a PCI device to allow external hosts access to network services on guest virtual machines.
+ </div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_address_translation_NAT_with_libvirt"><div class="titlepage"><div><div><h2 class="title">11.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 known as virtual networks).
+ </div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_address_translation_NAT_with_libvirt-Host_configuration"><h5 class="formalpara">Host configuration</h5>
+ Every standard <code class="systemitem">libvirt</code> installation provides NAT-based connectivity to virtual machines as the 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. The new device uses NAT and IP forwarding to connect to the physical network. 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 guest virtual machines 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" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_address_translation_NAT_with_libvirt-Guest_configuration"><h5 class="formalpara">Guest virtual machine configuration</h5>
+ Once the host configuration is complete, a guest virtual machine can be connected to the virtual network based on its name. To connect a guest to the 'default' virtual network, the following could be used in the XML configuration file (such as <code class="filename">/etc/libvirtd/qemu/myguest.xml</code>) for the guest:
+ </div><pre class="screen"><interface type='network'>
+ <source network='default'/>
+</interface></pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Defining a MAC address is optional. If you do not define one, a MAC address is automatically generated and used as the MAC address of the bridge device used by the network. Manually setting the MAC address may be useful to maintain consistency or easy reference throughout your environment, or to avoid the very small chance of a conflict.
+ </div><pre class="screen"><interface type='network'>
+ <source network='default'/>
+ <mac address='00:16:3e:1a:b3:4a'/>
+</interface></pre></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html"><strong>Prev</strong>10.6. Using KVM para-virtualized drivers for new ...</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="ch11s02.html"><strong>Next</strong>11.2. Disabling vhost-net</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html
new file mode 100644
index 0000000..6f8a21a
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html
@@ -0,0 +1,161 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 12. PCI device configuration</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html" title="11.3. Bridged networking with libvirt" /><link rel="next" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host.html" title="12.2. Assigning a PCI device with virt-manager" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://do
cs.redhat.com"><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_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 12. PCI device configuration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html#sect-Virtualization_Host_Configuration_and_Guest_Ins
tallation_Guide-PCI_Assignment-AI_device_to_a_host">12.1. Assigning a PCI device with virsh</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host.html">12.2. Assigning a PCI device with virt-manager</a></span></dt><dt><span class="section"><a href="ch12s03.html">12.3. PCI device assignment with virt-install</a></span></dt><dt><span class="section"><a href="ch12s04.html">12.4. Detaching an assigned PCI device</a></span></dt></dl></div><div class="para">
+ Red Hat Enterprise Linux 6 exposes three classes of device to its virtual machines:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="firstterm">Emulated devices</em> are purely virtual devices that mimic real hardware, allowing unmodified guest operating systems to work with them using their standard in-box drivers.
+ </div></li><li class="listitem"><div class="para">
+ <em class="firstterm">Virtio devices</em> are purely virtual devices designed to work optimally in a virtual machine. Virtio devices are similar to emulated devices, however, non-Linux virtual machines do not include the drivers they require by default. Virtualization management software like the Virtual Machine Manager (<span class="application"><strong>virt-manager</strong></span>) and the Red Hat Enterprise Virtualization Hypervisor install these drivers automatically for supported non-Linux guest operating systems.
+ </div></li><li class="listitem"><div class="para">
+ <em class="firstterm">Assigned devices</em> are physical devices that are exposed to the virtual machine. This method is also known as 'passthrough'. Device assignment allows virtual machines exclusive access to PCI devices for a range of tasks, and allows PCI devices to appear and behave as if they were physically attached to the guest operating system.
+ </div><div class="para">
+ Device assignment is supported on PCI Express devices, except graphics cards. Parallel PCI devices may be supported as assigned devices, but they have severe limitations due to security and system configuration conflicts.
+ </div></li></ul></div><div class="para">
+ Red Hat Enterprise Linux 6 supports 32 PCI device slots per virtual machine, and 8 PCI functions per device slot. This gives a theoretical maximum of 256 configurable PCI functions per guest.
+ </div><div class="para">
+ However, this theoretical maximum is subject to the following limitations:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Each virtual machine supports a maximum of 8 assigned device functions.
+ </div></li><li class="listitem"><div class="para">
+ 4 PCI device slots are configured with emulated devices by default. However, users can explicitly remove 2 of the emulated devices that are configured by default (the video adapter device in slot 2, and the memory balloon driver device in slot 3). This gives users a supported functional maximum of 30 PCI device slots per virtual machine.
+ </div></li></ul></div><div class="para">
+ Red Hat Enterprise Linux 6.0 and newer supports hot plugging assigned PCI devices into virtual machines. However, PCI device hot plugging operates at the slot level and therefore does not support multi-function PCI devices. Multi-function PCI devices are recommended for static device configuration only.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Red Hat Enterprise Linux 6.0 limited guest operating system driver access to a device's standard and extended configuration space. Limitations that were present in Red Hat Enterprise Linux 6.0 are significantly reduced in Red Hat Enterprise Linux 6.1, and enable a much larger set of PCI Express devices to be successfully assigned to KVM guests.
+ </div></div></div><div class="para">
+ Secure device assignment also requires interrupt remapping support. If a platform does not support interrupt remapping, device assignment will fail. To use device assignment without interrupt remapping support in a development environment, set the <em class="parameter"><code>allow_unsafe_assigned_interrupts</code></em> KVM module parameter to <code class="literal">1</code>.
+ </div><div class="para">
+ PCI device assignment is only available on hardware platforms supporting either Intel VT-d or AMD IOMMU. These Intel VT-d or AMD IOMMU specifications must be enabled in BIOS for PCI device assignment to function.
+ </div><div class="procedure" id="intel-prep"><h6>Procedure 12.1. Preparing an Intel system for PCI device assignment</h6><ol class="1"><li class="step"><p class="title"><strong>Enable the Intel VT-d specifications</strong></p><div class="para">
+ The Intel VT-d specifications provide hardware support for directly assigning a physical device to a virtual machine. These specifications are required to use PCI device assignment with Red Hat Enterprise Linux.
+ </div><div class="para">
+ The Intel VT-d specifications must be enabled in the BIOS. Some system manufacturers disable these specifications by default. The terms used to refer to these specifications can differ between manufacturers; consult your system manufacturer's documentation for the appropriate terms.
+ </div></li><li class="step"><p class="title"><strong>Activate Intel VT-d in the kernel</strong></p><div class="para">
+ Activate Intel VT-d in the kernel by adding the <em class="parameter"><code>intel_iommu=on</code></em> parameter to the kernel line in the <code class="filename">/boot/grub/grub.conf</code> file.
+ </div><div class="para">
+ The example below is a modified <code class="filename">grub.conf</code> file with Intel VT-d activated.
+ </div><pre class="screen">default=0
+timeout=5
+splashimage=(hd0,0)/grub/splash.xpm.gz
+hiddenmenu
+title Red Hat Enterprise Linux Server (2.6.32-330.x86_645)
+ root (hd0,0)
+ kernel /vmlinuz-2.6.32-330.x86_64 ro root=/dev/VolGroup00/LogVol00 rhgb quiet <span class="bold bold"><strong>intel_iommu=on</strong></span>
+ initrd /initrd-2.6.32-330.x86_64.img</pre></li><li class="step"><p class="title"><strong>Ready to use</strong></p><div class="para">
+ Reboot the system to enable the changes. Your system is now capable of PCI device assignment.
+ </div></li></ol></div><div class="procedure" id="amd-prep"><h6>Procedure 12.2. Preparing an AMD system for PCI device assignment</h6><ol class="1"><li class="step"><p class="title"><strong>Enable the AMD IOMMU specifications</strong></p><div class="para">
+ The AMD IOMMU specifications are required to use PCI device assignment in Red Hat Enterprise Linux. These specifications must be enabled in the BIOS. Some system manufacturers disable these specifications by default.
+ </div></li><li class="step"><p class="title"><strong>Enable IOMMU kernel support</strong></p><div class="para">
+ Append <em class="parameter"><code>amd_iommu=on</code></em> to the kernel command line in <code class="filename">/boot/grub/grub.conf</code> so that AMD IOMMU specifications are enabled at boot.
+ </div></li></ol></div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-AI_device_to_a_host"><div class="titlepage"><div><div><h2 class="title">12.1. Assigning a PCI device with virsh</h2></div></div></div><div class="para">
+ These steps cover assigning a PCI device to a virtual machine on a KVM hypervisor.
+ </div><div class="para">
+ This example uses a PCIe network controller with the PCI identifier code, <code class="computeroutput">pci_0000_01_00_0</code>, and a fully virtualized guest machine named <em class="replaceable"><code>guest1-F19</code></em>.
+ </div><div class="procedure"><h6>Procedure 12.3. Assigning a PCI device to a guest virtual machine with virsh</h6><ol class="1"><li class="step"><p class="title"><strong>Identify the device</strong></p><div class="para">
+ First, identify the PCI device designated for device assignment to the virtual machine. Use the <code class="command">lspci</code> command to list the available PCI devices. You can refine the output of <code class="command">lspci</code> with <code class="command">grep</code>.
+ </div><div class="para">
+ This example uses the Ethernet controller highlighted in the following output:
+ </div><pre class="screen"># lspci | grep Ethernet
+<span class="bold bold"><strong>00:19.0 Ethernet controller: Intel Corporation 82567LM-2 Gigabit Network Connection</strong></span>
+01:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
+01:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)</pre><div class="para">
+ This Ethernet controller is shown with the short identifier <code class="literal">00:19.0</code>. We need to find out the full identifier used by <code class="command">virsh</code> in order to assign this PCI device to a virtual machine.
+ </div><div class="para">
+ To do so, combine the <code class="command">virsh nodedev-list</code> command with the <code class="command">grep</code> command to list all devices of a particular type (<code class="literal">pci</code>) that are attached to the host machine. Then look at the output for the string that maps to the short identifier of the device you wish to use.
+ </div><div class="para">
+ This example highlights the string that maps to the Ethernet controller with the short identifier <code class="literal">00:19.0</code>. Note that the <code class="literal">:</code> and <code class="literal">.</code> characters are replaced with underscores in the full identifier.
+ </div><pre class="screen"># virsh nodedev-list --cap pci
+pci_0000_00_00_0
+pci_0000_00_01_0
+pci_0000_00_03_0
+pci_0000_00_07_0
+pci_0000_00_10_0
+pci_0000_00_10_1
+pci_0000_00_14_0
+pci_0000_00_14_1
+pci_0000_00_14_2
+pci_0000_00_14_3
+pci_0000_<span class="bold bold"><strong>00_19_0</strong></span>
+pci_0000_00_1a_0
+pci_0000_00_1a_1
+pci_0000_00_1a_2
+pci_0000_00_1a_7
+pci_0000_00_1b_0
+pci_0000_00_1c_0
+pci_0000_00_1c_1
+pci_0000_00_1c_4
+pci_0000_00_1d_0
+pci_0000_00_1d_1
+pci_0000_00_1d_2
+pci_0000_00_1d_7
+pci_0000_00_1e_0
+pci_0000_00_1f_0
+pci_0000_00_1f_2
+pci_0000_00_1f_3
+pci_0000_01_00_0
+pci_0000_01_00_1
+pci_0000_02_00_0
+pci_0000_02_00_1
+pci_0000_06_00_0
+pci_0000_07_02_0
+pci_0000_07_03_0</pre><div class="para">
+ Record the PCI device number that maps to the device you want to use; this is required in other steps.
+ </div></li><li class="step"><p class="title"><strong>Review device information</strong></p><div class="para">
+ Information on the domain, bus, and function are available from output of the <code class="command">virsh nodedev-dumpxml</code> command:
+ </div><pre class="screen">virsh nodedev-dumpxml pci_0000_00_19_0
+<device>
+ <name>pci_0000_00_19_0</name>
+ <parent>computer</parent>
+ <driver>
+ <name>e1000e</name>
+ </driver>
+ <capability type='pci'>
+ <domain>0</domain>
+ <bus>0</bus>
+ <slot>25</slot>
+ <function>0</function>
+ <product id='0x1502'>82579LM Gigabit Network Connection</product>
+ <vendor id='0x8086'>Intel Corporation</vendor>
+ <capability type='virt_functions'>
+ </capability>
+ </capability>
+</device></pre></li><li class="step"><p class="title"><strong>Determine required configuration details</strong></p><div class="para">
+ Refer to the output from the <code class="command">virsh nodedev-dumpxml pci_0000_00_19_0</code> command for the values required for the configuration file.
+ </div><div class="para">
+ Optionally, convert slot and function values to hexadecimal values (from decimal) to get the PCI bus addresses. Append "0x" to the beginning of the output to tell the computer that the value is a hexadecimal number.
+ </div><div class="para">
+ The example device has the following values: bus = 0, slot = 25 and function = 0. The decimal configuration uses those three values:
+ </div><pre class="screen">bus='0'
+slot='25'
+function='0'</pre><div class="para">
+ If you want to convert to hexadecimal values, you can use the <code class="command">printf</code> utility to convert from decimal values, as shown in the following example:
+ </div><pre class="screen">$ printf %x 0
+0
+$ printf %x 25
+19
+$ printf %x 0
+0</pre><div class="para">
+ The example device would use the following hexadecimal values in the configuration file:
+ </div><pre class="screen">bus='0x0'
+slot='0x19'
+function='0x0'</pre></li><li class="step"><p class="title"><strong>Add configuration details</strong></p><div class="para">
+ Run <code class="command">virsh edit</code>, specifying the virtual machine name, and add a device entry in the <code class="computeroutput"><source></code> section to assign the PCI device to the guest virtual machine.
+ </div><pre class="screen"># virsh edit <em class="replaceable"><code>guest1-F19</code></em>
+<hostdev mode='subsystem' type='pci' managed='yes'>
+ <source>
+ <address domain='0x0' bus='0x0' slot='0x19' function='0x0'/>
+ </source>
+</hostdev></pre><div class="para">
+ Alternately, run <code class="command">virsh attach-device</code>, specifying the virtual machine name and the guest's XML file:
+ </div><pre class="screen">virsh attach-device <em class="replaceable"><code>guest1-F19</code></em> <code class="filename">file.xml</code></pre></li><li class="step"><p class="title"><strong>Allow device management</strong></p><div class="para">
+ Set an SELinux boolean to allow the management of the PCI device from the virtual machine:
+ </div><pre class="screen"># setsebool -P virt_use_sysfs 1</pre></li><li class="step"><p class="title"><strong>Start the virtual machine</strong></p><pre class="screen"># virsh start <em class="replaceable"><code>guest1-F19</code></em></pre></li></ol></div><div class="para">
+ The PCI device should now be successfully assigned to the virtual machine, and accessible to the guest operating system.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html"><strong>Prev</strong>11.3. 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_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host.html"><strong>Next</strong>12.2. Assigning a PCI device with virt-manager</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html
new file mode 100644
index 0000000..d3b9b99
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html
@@ -0,0 +1,76 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 10. KVM Para-virtualized Drivers</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html" title="Chapter 9. Installing a fully-virtualized Windows guest" /><link rel="next" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html" title="10.2. Installing the drivers on an installed Windows guest virtual machine" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.p
ng" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 10. KVM Para-virtualized Drivers</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installa
tion_Guide-Para_virtualized_drivers.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers">10.1. Installing the KVM Windows para-virtualized drivers</a></span></dt><dt><span class="section"><a href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html">10.2. Installing the drivers on an installed Windows guest virtual machine</a></span></dt><dt><span class="section"><a href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html">10.3. Installing drivers during the Windows installation</a></span></dt><dt><span class="section"><a href="ch10s04.html">10.4. Using the para-virtualized drivers with Red Hat Enterprise Linux 3.9 guests</a></span></dt><dt><span class="section"><a href="form-Virtualization_Host_Configuration_
and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices.html">10.5. Using KVM para-virtualized drivers for existing devices</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html">10.6. Using KVM para-virtualized drivers for new devices</a></span></dt></dl></div><div class="para">
+ Para-virtualized drivers are available for Windows guest virtual machines 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 the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Red Hat Enterprise Linux 4.8 and newer
+ </div></li><li class="listitem"><div class="para">
+ Red Hat Enterprise Linux 5.3 and newer
+ </div></li><li class="listitem"><div class="para">
+ Red Hat Enterprise Linux 6 and newer
+ </div></li><li class="listitem"><div class="para">
+ Some versions of Linux based on the 2.6.27 kernel or newer kernel versions.
+ </div></li></ul></div><div class="para">
+ Versions of Red Hat Enterprise Linux in the list above detect and install the drivers, additional installation steps are not required.
+ </div><div class="para">
+ In Red Hat Enterprise Linux 3 (3.9 and above), manual installation is required.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ PCI devices are limited by the virtualized system architecture. Refer to <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html">Chapter 12, <em>PCI device configuration</em></a> for additional limitations when using assigned devices.
+ </div></div></div><div class="para">
+ Using KVM para-virtualized drivers, the following Microsoft Windows versions are expected to run similarly to bare-metal-based systems.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Windows XP Service Pack 3 and newer (32-bit only)
+ </div></li><li class="listitem"><div class="para">
+ Windows Server 2003 (32-bit and 64-bit versions)
+ </div></li><li class="listitem"><div class="para">
+ Windows Server 2008 (32-bit and 64-bit versions)
+ </div></li><li class="listitem"><div class="para">
+ Windows Server 2008 R2 (64-bit only)
+ </div></li><li class="listitem"><div class="para">
+ Windows 7 (32-bit and 64-bit versions)
+ </div></li></ul></div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers"><div class="titlepage"><div><div><h2 class="title">10.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 a guest virtual machine using one of the following methods:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ hosting the installation files on a network accessible to the virtual machine,
+ </div></li><li class="listitem"><div class="para">
+ using a virtualized CD-ROM device of the driver installation disk .iso file, or
+ </div></li><li class="listitem"><div class="para">
+ using a virtualized floppy device to install the drivers during boot time.
+ </div></li></ul></div><div class="para">
+ This guide describes installation from the para-virtualized installer disk as a virtualized CD-ROM device.
+ </div><div class="procedure"><ol class="1"><li class="step" id="step-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Download_the_drivers"><p class="title"><strong>Download the drivers</strong></p><div class="para">
+ The <span class="package">virtio-win</span> package contains the para-virtualized block and network drivers for all supported Windows guest virtual machines.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The <span class="package">virtio-win</span> package can be found here in RHN: <a href="https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=602010">https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=602010</a>. It requires access to one of the following channels:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ RHEL Client Supplementary (v. 6)
+ </div></li><li class="listitem"><div class="para">
+ RHEL Server Supplementary (v. 6)
+ </div></li><li class="listitem"><div class="para">
+ RHEL Workstation Supplementary (v. 6)
+ </div></li></ul></div></div></div><div class="para">
+ Download and install the <span class="package">virtio-win</span> package on the host with the <code class="command">yum</code> command.
+ </div><pre class="screen"> # yum install virtio-win</pre><div class="para">
+ The list of virtio-win packages that are supported on Windows operating systems, and the current certified package version, can be found at the following URL: <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">
+ Note that the Red Hat Enterprise Virtualization Hypervisor and Red Hat Enterprise Linux are created on the same code base so the drivers for the same version (for example, Red Hat Enterprise Virtualization Hypervisor 3.0 and Red Hat Enterprise Linux 6) are supported for both environments.
+ </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 class="step" id="step-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Install_the_para_virtualized_drivers"><p class="title"><strong>Install the para-virtualized drivers</strong></p><div class="para">
+ It is recommended to install the drivers on the virtual machine 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 virtual machine, the drivers must be installed before the device is modified. If the drivers are not installed on the virtual machine and the driver is set to the virtio driver the virtual machine will not boot.
+ </div></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html"><strong>Prev</strong>Chapter 9. Installing a fully-virtualized Windows...</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="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html"><strong>Next</strong>10.2. Installing the drivers on an installed Wind...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html
new file mode 100644
index 0000000..18d05dc
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html
@@ -0,0 +1,94 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 7. Installing a Red Hat Enterprise Linux 6 guest virtual machine on a Red Hat Enterprise Linux 6 host</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE.html" title="6.4. Installing guest virtual machines with PXE" /><link rel="next" href="ch07s02.html" title="7.2. Creating a Red Hat Enterprise Linux 6 guest with a network installation tree" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch07s02.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 7. Installing a Red Hat Enterprise Linux 6 guest virtual machine on a Red Hat Enterprise Linux 6 host</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html#idm7256240">7.1. Creating a Red Hat Enterprise Linux 6 guest with local installation media</a></span></dt><dt><span class="section"><a href="ch07s02.html">7.2. Creating a Red Hat Enterprise Linux 6 guest with a n
etwork installation tree</a></span></dt><dt><span class="section"><a href="ch07s03.html">7.3. Creating a Red Hat Enterprise Linux 6 guest with PXE</a></span></dt></dl></div><div class="para">
+ This chapter covers how to install a Red Hat Enterprise Linux 6 guest virtual machine on a Red Hat Enterprise Linux 6 host.
+ </div><div class="para">
+ These procedures assume that the KVM hypervisor and all other required packages are installed and the host is configured for virtualization.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ For more information on installing the virtualization packages, refer to <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html">Chapter 5, <em>Installing the virtualization packages</em></a>.
+ </div></div></div><div class="section" id="idm7256240"><div class="titlepage"><div><div><h2 class="title" id="idm7256240">7.1. Creating a Red Hat Enterprise Linux 6 guest with local installation media</h2></div></div></div><div class="para">
+ This procedure covers creating a Red Hat Enterprise Linux 6 guest virtual machine with a locally stored installation DVD or DVD image. DVD images are available from <a href="http://access.redhat.com">http://access.redhat.com</a> for Red Hat Enterprise Linux 6.
+ </div><div class="procedure"><h6>Procedure 7.1. Creating a Red Hat Enterprise Linux 6 guest virtual machine with virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Optional: Preparation</strong></p><div class="para">
+ Prepare the storage environment for the virtual machine. For more information on preparing storage, refer to the <em class="citetitle">Red Hat Enterprise Linux 6 Virtualization Administration Guide</em>.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Various storage types may be used for storing guest virtual machines. However, for a virtual machine to be able to use migration features the virtual machine must be created on networked storage.
+ </div></div></div><div class="para">
+ Red Hat Enterprise Linux 6 requires at least 1GB of storage space. However, Red Hat recommends at least 5GB of storage space for a Red Hat Enterprise Linux 6 installation and for the procedures in this guide.
+ </div></li><li class="step"><p class="title"><strong>Open virt-manager and start the wizard</strong></p><div class="para">
+ Open virt-manager by executing the <code class="command">virt-manager</code> command as root or opening <span class="guilabel"><strong>Applications</strong></span> → <span class="guilabel"><strong>System Tools</strong></span> → <span class="guilabel"><strong>Virtual Machine Manager</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/1-7RHEL_local_install.png" width="444" alt="The Virtual Machine Manager window" /></div></div><h6>Figure 7.1. The Virtual Machine Manager window</h6></div><br class="figure-break" /><div class="para">
+ Click on the <span class="guibutton"><strong>Create a new virtual machine</strong></span> button to start the new virtualized guest wizard.
+ </div><div class="figure" id="gofigurego"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_newicon.png" alt="The Create a new virtual machine button" /></div></div><h6>Figure 7.2. The Create a new virtual machine button</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guilabel"><strong>New VM</strong></span> window opens.
+ </div></li><li class="step"><p class="title"><strong>Name the virtual machine</strong></p><div class="para">
+ Virtual machine names can contain letters, numbers and the following characters: '<span class="keycap"><strong>_</strong></span>', '<span class="keycap"><strong>.</strong></span>' and '<span class="keycap"><strong>-</strong></span>'. Virtual machine names must be unique for migration and cannot consist only of numbers.
+ </div><div class="para">
+ Choose the <span class="guilabel"><strong>Local install media (ISO image or CDROM)</strong></span> radio button.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/2-7RHEL_local_install.png" width="444" alt="The New VM window - Step 1" /></div></div><h6>Figure 7.3. The New VM window - Step 1</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Select the installation media</strong></p><div class="para">
+ Select the appropriate radio button for your installation media.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/3-7RHEL_local_install.png" width="444" alt="Locate your install media" /></div></div><h6>Figure 7.4. Locate your install media</h6></div><br class="figure-break" /><ul class="stepalternatives">
+ <li class="step"><div class="para">
+ If you wish to install from a CD-ROM or DVD, select the <span class="guilabel"><strong>Use CDROM or DVD</strong></span> radio button, and select the appropriate disk drive from the drop-down list of drives available.
+ </div></li>
+ <li class="step"><div class="para">
+ If you wish to install from an ISO image, select <span class="guilabel"><strong>Use ISO image</strong></span>, and then click the <span class="guibutton"><strong>Browse...</strong></span> button to open the <span class="guilabel"><strong>Locate media volume</strong></span> window.
+ </div><div class="para">
+ Select the installation image you wish to use, and click <span class="guibutton"><strong>Choose Volume</strong></span>.
+ </div><div class="para">
+ If no images are displayed in the <span class="guilabel"><strong>Locate media volume</strong></span> window, click on the <span class="guibutton"><strong>Browse Local</strong></span> button to browse the host machine for the installation image or DVD drive containing the installation disk. Select the installation image or DVD drive containing the installation disk and click <span class="guibutton"><strong>Open</strong></span>; the volume is selected for use and you are returned to the <span class="guilabel"><strong>Create a new virtual machine</strong></span> wizard.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ For ISO image files and guest storage images, the recommended location to use is <code class="filename">/var/lib/libvirt/images/</code>. Any other location may require additional configuration by SELinux. Refer to the Red Hat Enterprise Linux 6 <em class="citetitle">Virtualization Administration Guide</em> for more details on configuring SELinux.
+ </div></div></div></li>
+
+ </ul><div class="para">
+ Select the operating system type and version which match the installation media you have selected.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/5-7RHEL_local_install.png" width="444" alt="The New VM window - Step 2" /></div></div><h6>Figure 7.5. The New VM window - Step 2</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title" id="RAM-and-VCPUs"><strong>Set RAM and virtual CPUs</strong></p><div class="para">
+ Choose appropriate values for the virtual CPUs and RAM allocation. These values affect the host's and guest's performance. Memory and virtual CPUs can be overcommitted. For more information on overcommitting, refer to the <em class="citetitle">Red Hat Enterprise Linux 6 Virtualization Administration Guide</em>.
+ </div><div class="para">
+ Virtual machines require sufficient physical memory (RAM) to run efficiently and effectively. Red Hat supports a minimum of 512MB of RAM for a virtual machine. Red Hat recommends at least 1024MB of RAM for each logical core.
+ </div><div class="para">
+ Assign sufficient virtual CPUs for the virtual machine. If the virtual machine runs a multithreaded application, assign the number of virtual CPUs the guest virtual machine will require to run efficiently.
+ </div><div class="para">
+ You cannot assign more virtual CPUs than there are physical processors (or hyper-threads) available on the host system. The number of virtual CPUs available is noted in the <span class="guilabel"><strong>Up to <em class="replaceable"><code>X</code></em> available</strong></span> field.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/6-7RHEL_local_install.png" width="444" alt="The new VM window - Step 3" /></div></div><h6>Figure 7.6. The new VM window - Step 3</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Storage</strong></p><div class="para">
+ Enable and assign storage for the Red Hat Enterprise Linux 6 guest virtual machine. Assign at least 5GB for a desktop installation or at least 1GB for a minimal installation.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Live and offline migrations require virtual machines to be installed on shared network storage. For information on setting up shared storage for virtual machines, refer to the <em class="citetitle">Red Hat Enterprise Linux Virtualization Administration Guide</em>.
+ </div></div></div><ol class="a"><li class="step"><p class="title"><strong>With the default local storage</strong></p><div class="para">
+ Select the <span class="guilabel"><strong>Create a disk image on the computer's hard drive</strong></span> radio button to create a file-based image in the default storage pool, the <code class="filename">/var/lib/libvirt/images/</code> directory. Enter the size of the disk image to be created. If the <span class="guilabel"><strong>Allocate entire disk now</strong></span> check box is selected, a disk image of the size specified will be created immediately. If not, the disk image will grow as it becomes filled.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/7-7RHEL_local_install.png" width="444" alt="The New VM window - Step 4" /></div></div><h6>Figure 7.7. The New VM window - Step 4</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to create a disk image on the local hard drive. Alternatively, select <span class="guilabel"><strong>Select managed or other existing storage</strong></span>, then select <span class="guilabel"><strong>Browse</strong></span> to configure managed storage.
+ </div></li><li class="step"><p class="title"><strong>With a storage pool</strong></p><div class="para">
+ If you selected <span class="guilabel"><strong>Select managed or other existing storage</strong></span> in the previous step to use a storage pool and clicked <span class="guilabel"><strong>Browse</strong></span>, the <span class="guilabel"><strong>Locate or create storage volume</strong></span> window will appear.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/8-7RHEL_local_install.png" width="444" alt="The Locate or create storage volume window" /></div></div><h6>Figure 7.8. The Locate or create storage volume window</h6></div><br class="figure-break" /><ol class="i"><li class="step"><div class="para">
+ Select a storage pool from the <span class="guilabel"><strong>Storage Pools</strong></span> list.
+ </div></li><li class="step"><div class="para">
+ Optional: Click on the <span class="guilabel"><strong>New Volume</strong></span> button to create a new storage volume. The <span class="guilabel"><strong>Add a Storage Volume</strong></span> screen will appear. Enter the name of the new storage volume.
+ </div><div class="para">
+ Choose a format option from the <span class="guilabel"><strong>Format</strong></span> dropdown menu. Format options include raw, cow, qcow, qcow2, qed, vmdk, and vpc. Adjust other fields as desired.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/9-7RHEL_local_install.png" width="444" alt="The Add a Storage Volume window" /></div></div><h6>Figure 7.9. The Add a Storage Volume window</h6></div><br class="figure-break" /></li></ol></li></ol><div class="para">
+ Click <span class="guibutton"><strong>Finish</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Verify and finish</strong></p><div class="para">
+ Verify there were no errors made during the wizard and everything appears as expected.
+ </div><div class="para">
+ Select the <span class="guilabel"><strong>Customize configuration before install</strong></span> check box to change the guest's storage or network devices, to use the para-virtualized drivers or to add additional devices.
+ </div><div class="para">
+ Click on the <code class="systemitem">Advanced options</code> down arrow to inspect and modify advanced options. For a standard Red Hat Enterprise Linux 6 installation, none of these options require modification.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/11-7RHEL_local_install.png" width="444" alt="The New VM window - local storage" /></div></div><h6>Figure 7.10. The New VM window - local storage</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Finish</strong></span> to continue into the Red Hat Enterprise Linux installation sequence. For more information on installing Red Hat Enterprise Linux 6 refer to the Red Hat Enterprise Linux 6 <em class="citetitle">Installation Guide</em>.
+ </div></li></ol></div><div class="para">
+ A Red Hat Enterprise Linux 6 guest virtual machine is now created from an ISO installation disc image.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE.html"><strong>Prev</strong>6.4. Installing guest virtual machines 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="ch07s02.html"><strong>Next</strong>7.2. Creating a Red Hat Enterprise Linux 6 guest ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html
new file mode 100644
index 0000000..8261300
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html
@@ -0,0 +1,34 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 13. SR-IOV</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="ch12s04.html" title="12.4. Detaching an assigned PCI device" /><link rel="next" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html" title="13.2. Using SR-IOV" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch12s04.html">
<strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 13. SR-IOV</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html#idm108480">13.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html">13.2. Using SR-IOV</a></span></dt><dt><span class="section"><a href="ch13s03.html">13.3. Troubleshooting SR-IOV</a></span></dt></dl></div><div class="section" id="idm108480"><div class="titlepage"><div><div><h2 class="title" id="id
m108480">13.1. Introduction</h2></div></div></div><div class="para">
+ Developed by the PCI-SIG (PCI Special Interest Group), the Single Root I/O Virtualization (SR-IOV) specification is a standard for a type of PCI device assignment that can share a single device to multiple virtual machines. SR-IOV improves device performance for virtual machines.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/SR-IOV_implementation_2.png" width="444" alt="How SR-IOV works" /></div></div><h6>Figure 13.1. How SR-IOV works</h6></div><br class="figure-break" /><div class="para">
+ SR-IOV enables a Single Root Function (for example, a single Ethernet port), to appear as multiple, separate, physical devices. A physical device with SR-IOV capabilities can be configured to appear in the PCI configuration space as multiple functions. Each device has its own configuration space complete with Base Address Registers (BARs).
+ </div><div class="para">
+ SR-IOV uses two PCI functions:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Physical Functions (PFs) are full PCIe devices that include the SR-IOV capabilities. Physical Functions are discovered, managed, and configured as normal PCI devices. Physical Functions configure and manage the SR-IOV functionality by assigning Virtual Functions.
+ </div></li><li class="listitem"><div class="para">
+ Virtual Functions (VFs) are simple PCIe functions that only process I/O. Each Virtual Function is derived from a Physical Function. The number of Virtual Functions a device may have is limited by the device hardware. A single Ethernet port, the Physical Device, may map to many Virtual Functions that can be shared to virtual machines.
+ </div></li></ul></div><div class="para">
+ The hypervisor can map one or more Virtual Functions to a virtual machine. The Virtual Function's configuration space is then mapped to the configuration space presented to the guest.
+ </div><div class="para">
+ Each Virtual Function can only be mapped to a single guest at a time, as Virtual Functions require real hardware resources. A virtual machine can have multiple Virtual Functions. A Virtual Function appears as a network card in the same way as a normal network card would appear to an operating system.
+ </div><div class="para">
+ The SR-IOV drivers are implemented in the kernel. The core implementation is contained in the PCI subsystem, but there must also be driver support for both the Physical Function (PF) and Virtual Function (VF) devices. An SR-IOV capable device can allocate VFs from a PF. The VFs appear as PCI devices which are backed on the physical PCI device by resources such as queues and register sets.
+ </div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-Libvirt_Strengths"><h5 class="formalpara">Advantages of SR-IOV</h5>
+ SR-IOV devices can share a single physical port with multiple virtual machines.
+ </div><div class="para">
+ Virtual Functions have near-native performance and provide better performance than para-virtualized drivers and emulated access. Virtual Functions provide data protection between virtual machines on the same physical server as the data is managed and controlled by the hardware.
+ </div><div class="para">
+ These features allow for increased virtual machine density on hosts within a data center.
+ </div><div class="para">
+ SR-IOV is better able to utilize the bandwidth of devices with multiple guests.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch12s04.html"><strong>Prev</strong>12.4. Detaching an assigned PCI device</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_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html"><strong>Next</strong>13.2. Using SR-IOV</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_Requirements.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_Requirements.html
new file mode 100644
index 0000000..4668afb
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_Requirements.html
@@ -0,0 +1,62 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 2. System requirements</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="ch01s02.html" title="1.2. Virtualization Documentation Suite" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html" title="Chapter 3. KVM guest virtual machine compatibility" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p"
href="ch01s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_Requirements" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 2. System requirements</h2></div></div></div><div class="para">
+ This chapter lists system requirements for successfully running virtual machines, referred to as VMs on Fedora. Virtualization is available for Fedora on the Intel 64 and AMD64 architecture.
+ </div><div class="para">
+ The KVM hypervisor is provided with Fedora 16.
+ </div><div class="para">
+ For information on installing the virtualization packages, see <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html">Chapter 5, <em>Installing the virtualization packages</em></a>.
+ </div><div class="itemizedlist" id="item-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_requirements-Minimum_system_requirements"><h6>Minimum system requirements</h6><ul><li class="listitem"><div class="para">
+ 6 GB free disk space.
+ </div></li><li class="listitem"><div class="para">
+ 2 GB of RAM.
+ </div></li></ul></div><div class="itemizedlist" id="item-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_requirements-Recommended_system_requirements"><h6>Recommended system requirements</h6><ul><li class="listitem"><div class="para">
+ One processor core or hyper-thread for the maximum number of virtualized CPUs in a guest virtual machine and one for the host.
+ </div></li><li class="listitem"><div class="para">
+ 2 GB of RAM plus additional RAM for virtual machines.
+ </div></li><li class="listitem"><div class="para">
+ 6 GB disk space for the host, plus the required disk space for each virtual machine.
+ </div><div class="para">
+ Most guest operating systems will require at least 6GB of disk space, but the additional storage space required for each guest depends on its image format.
+ </div><div class="para">
+ For guest virtual machines using raw images, the guest's total required space <code class="literal">(total for raw format)</code> is equal to or greater than the sum of the space required by the guest's raw image files <code class="literal">(images)</code>, the 6GB space required by the host operating system <code class="literal">(host)</code>, and the swap space that guest will require <code class="literal">(swap)</code>.
+ </div><div class="equation"><h6>Equation 2.1. Calculating required space for guest virtual machines using raw images</h6><div class="equation-contents"><span class="mathphrase">total for raw format = images + host + swap</span></div></div><br class="equation-break" /><div class="para">
+ For qcow images, you must also calculate the expected maximum storage requirements of the guest <code class="literal">(total for qcow format)</code>, as qcow and qcow2 images grow as required. To allow for this expansion, first multiply the expected maximum storage requirements of the guest <code class="literal">(expected maximum guest storage)</code> by 1.01, and add to this the space required by the host <code class="literal">(host)</code>, and the necessary swap space <code class="literal">(swap)</code>.
+ </div><div class="equation"><h6>Equation 2.2. Calculating required space for guest virtual machines using qcow images</h6><div class="equation-contents"><span class="mathphrase">total for qcow format = (expected maximum guest storage * 1.01) + host + swap</span></div></div><br class="equation-break" /></li></ul></div><div class="para">
+ For more information on Guest virtual machine requirements refer to <a class="xref" href="sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM.html">Chapter 22, <em>Overcommitting with KVM</em></a>.
+ </div><div class="formalpara"><h5 class="formalpara" id="idp2434560">Calculating swap space</h5>
+ Using swap space can provide additional memory beyond the available physical memory. 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 the physical RAM of the host.
+ </div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_requirements-KVM_requirements"><h5 class="formalpara">KVM requirements</h5>
+ The KVM hypervisor requires:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ an Intel processor with the Intel VT-x and Intel 64 extensions for x86-based systems, or
+ </div></li><li class="listitem"><div class="para">
+ an AMD processor with the AMD-V and the AMD64 extensions.
+ </div></li></ul></div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_requirements-Storage_support"><h5 class="formalpara">Storage support</h5>
+ The guest virtual machine storage methods are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ files on local storage,
+ </div></li><li class="listitem"><div class="para">
+ physical disk partitions,
+ </div></li><li class="listitem"><div class="para">
+ locally connected physical LUNs,
+ </div></li><li class="listitem"><div class="para">
+ LVM partitions,
+ </div></li><li class="listitem"><div class="para">
+ NFS shared file systems,
+ </div></li><li class="listitem"><div class="para">
+ iSCSI,
+ </div></li><li class="listitem"><div class="para">
+ GFS2 clustered file systems,
+ </div></li><li class="listitem"><div class="para">
+ Fibre Channel-based LUNs, and
+ </div></li><li class="listitem"><div class="para">
+ Fibre Channel over Ethernet (FCoE).
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch01s02.html"><strong>Prev</strong>1.2. Virtualization Documentation Suite</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_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html"><strong>Next</strong>Chapter 3. KVM guest virtual machine compatibility</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions.html
new file mode 100644
index 0000000..49bfd9d
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions.html
@@ -0,0 +1,24 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2. Application restrictions</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html" title="Chapter 4. Virtualization restrictions" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html" title="Chapter 4. Virtualization restrictions" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions.html" title="4.3. Other restrictions" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product
Site" /></a><a class="right" href="http://docs.redhat.com"><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_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions.html"><strong>Next</strong></a></li></ul><div class="section" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions"><div class="titlepage"><div><div><h2 class="title">4.2. Application restrictions</h2></div></div></div><div class="para">
+ There are aspects of virtualization which make it unsuitable for certain types of applications.
+ </div><div class="para">
+ Applications with high I/O throughput requirements should use the para-virtualized drivers for fully-virtualized guests. Without the para-virtualized drivers certain applications may be unpredictable under heavy I/O loads.
+ </div><div class="para">
+ The following applications should be avoided due to high I/O requirements:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>kdump</strong></span> server
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>netdump</strong></span> server
+ </div></li></ul></div><div class="para">
+ You should carefully evaluate applications and tools that heavily utilize I/O or those that require real-time performance. Consider the para-virtualized drivers or PCI device assignment for increased I/O performance. Refer to <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html">Chapter 10, <em>KVM Para-virtualized Drivers</em></a> for more information on the para-virtualized drivers for fully virtualized guests. Refer to <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html">Chapter 12, <em>PCI device configuration</em></a> for more information on PCI device assignment.
+ </div><div class="para">
+ Applications suffer a small performance loss from running in virtualized environments. The performance benefits of virtualization through consolidating to newer and faster hardware should be evaluated against the potential application performance issues associated with using virtualization.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html"><strong>Prev</strong>Chapter 4. Virtualization restrictions</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_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions.html"><strong>Next</strong>4.3. Other restrictions</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions.html
new file mode 100644
index 0000000..e1eeba3
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.3. Other restrictions</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html" title="Chapter 4. Virtualization restrictions" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions.html" title="4.2. Application restrictions" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html" title="Chapter 5. Installing the virtualization packages" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png"
alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html"><strong>Next</strong></a></li></ul><div class="section" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions"><div class="titlepage"><div><div><h2 class="title">4.3. Other restrictions</h2></div></div></div><div class="para">
+ For the list of all other restrictions and issues affecting virtualization read the <em class="citetitle">Fedora 19 Release Notes</em>. The <em class="citetitle">Fedora 19 Release Notes</em> cover the present new features, known issues and restrictions as they are updated or discovered.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions.html"><strong>Prev</strong>4.2. Application restrictions</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_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html"><strong>Next</strong>Chapter 5. Installing the virtualization packages</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html
new file mode 100644
index 0000000..acc61b5
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html
@@ -0,0 +1,78 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 4. Virtualization restrictions</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="ch03s02.html" title="3.2. Supported CPU Models" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions.html" title="4.2. Application restrictions" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" h
ref="ch03s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 4. Virtualization restrictions</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html#sect-chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-KVM_Restrictions">4.1. KVM restrictions</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions.htm
l">4.2. Application restrictions</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions.html">4.3. Other restrictions</a></span></dt></dl></div><div class="para">
+ This chapter covers additional support and product restrictions of the virtualization packages in Fedora 19.
+ </div><div class="section" id="sect-chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-KVM_Restrictions"><div class="titlepage"><div><div><h2 class="title">4.1. KVM restrictions</h2></div></div></div><div class="para">
+ The following restrictions apply to the KVM hypervisor:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Maximum vCPUs per guest</span></dt><dd><div class="para">
+ Guest virtual machines support up to a maximum of 160 virtual CPUs in Fedora 19.
+ </div></dd><dt class="varlistentry"><span class="term">Constant TSC bit</span></dt><dd><div class="para">
+ Systems without a Constant Time Stamp Counter require additional configuration. Refer to <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management.html">Chapter 14, <em>KVM guest timing management</em></a> for details on determining whether you have a Constant Time Stamp Counter and configuration steps for fixing any related issues.
+ </div></dd><dt class="varlistentry"><span class="term">Memory overcommit</span></dt><dd><div class="para">
+ KVM supports memory overcommit and can store the memory of guest virtual machines in swap. A virtual machine will run slower if it is swapped frequently. Fedora Knowledgebase has an article on safely and efficiently determining the size of the swap partition, available here: <a href="https://access.redhat.com/knowledge/solutions/15244">https://access.redhat.com/knowledge/solutions/15244</a>. When KSM is used for memory overcommitting, make sure that the swap size follows the recommendations described in this article.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ When device assignment is in use, all virtual machine memory must be statically pre-allocated to enable DMA with the assigned device. Memory overcommit is therefore not supported with device assignment.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">CPU overcommit</span></dt><dd><div class="para">
+ It is not recommended to have more than 10 virtual CPUs per physical processor core. Customers are encouraged to use a capacity planning tool in order to determine the CPU overcommit ratio. Estimating an ideal ratio is difficult as it is highly dependent on each workload. For instance, a guest virtual machine may consume 100% CPU on one use case, and multiple guests may be completely idle on another.
+ </div><div class="para">
+ Fedora does not support running more vCPUs to a single guest than the amount of overall physical cores that exist on the system. While Hyperthreads can be considered as cores, their performance can also vary from one scenario to the next, and they should not be expected to perform as well as regular cores.
+ </div><div class="para">
+ Refer to the <em class="citetitle">Fedora Virtualization Administration Guide</em> for tips and recommendations on overcommitting CPUs.
+ </div></dd><dt class="varlistentry"><span class="term">Virtualized SCSI devices</span></dt><dd><div class="para">
+ SCSI emulation is not supported with KVM in Fedora.
+ </div></dd><dt class="varlistentry"><span class="term">Virtualized IDE devices</span></dt><dd><div class="para">
+ KVM is limited to a maximum of four virtualized (emulated) IDE devices per guest virtual machine.
+ </div></dd><dt class="varlistentry"><span class="term">Para-virtualized devices</span></dt><dd><div class="para">
+ Para-virtualized devices are also known as Virtio devices. They are purely virtual devices designed to work optimally in a virtual machine.
+ </div><div class="para">
+ Fedora 19 supports 32 PCI device slots per virtual machine, and 8 PCI functions per device slot. This gives a theoretical maximum of 256 PCI functions per guest when multi-function capabilities are enabled.
+ </div><div class="para">
+ However, this theoretical maximum is subject to the following limitations:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Each virtual machine supports a maximum of 8 assigned device functions.
+ </div></li><li class="listitem"><div class="para">
+ 4 PCI device slots are configured with emulated devices by default. However, users can explicitly remove 2 of the emulated devices that are configured by default (the video adapter device in slot 2, and the memory balloon driver device in slot 3). This gives users a supported functional maximum of 30 PCI device slots per virtual machine.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term">Migration restrictions</span></dt><dd><div class="para">
+ Device assignment refers to physical devices that have been exposed to a virtual machine, for the exclusive use of that virtual machine. Because device assignment uses hardware on the specific host where the virtual machine runs, migration and save/restore are not supported when device assignment is in use. If the guest operating system supports hot-plugging, assigned devices can be removed prior to the migration or save/restore operation to enable this feature.
+ </div><div class="para">
+ Live migration is only possible between hosts with the same CPU type (that is, Intel to Intel or AMD to AMD only).
+ </div><div class="para">
+ For live migration, both hosts must have the same value set for the No eXecution (NX) bit, either <code class="literal">on</code> or <code class="literal">off</code>.
+ </div><div class="para">
+ For migration to work, <code class="code">cache=none</code> must be specified for all block devices opened in write mode.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Failing to include the <code class="code">cache=none</code> option can result in disk corruption.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">Storage restrictions</span></dt><dd><div class="para">
+ There are risks associated with giving guest virtual machines write access to entire disks or block devices (such as <code class="filename">/dev/sdb</code>). If a guest virtual machine has access to an entire block device, it can share any volume label or partition table with the host machine. If bugs exist in the host system's partition recognition code, this can create a security risk. Avoid this risk by configuring the host machine to ignore devices assigned to a guest virtual machine.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Failing to adhere to storage restrictions can result in risks to security.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">SR-IOV restrictions</span></dt><dd><div class="para">
+ SR-IOV is only thoroughly tested with the following devices (other SR-IOV devices may work but have not been tested at the time of release):
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Intel® 82576NS Gigabit Ethernet Controller (<code class="command">igb</code> driver)
+ </div></li><li class="listitem"><div class="para">
+ Intel® 82576EB Gigabit Ethernet Controller (<code class="command">igb</code> driver)
+ </div></li><li class="listitem"><div class="para">
+ Intel® 82599ES 10 Gigabit Ethernet Controller (<code class="command">ixgbe</code> driver)
+ </div></li><li class="listitem"><div class="para">
+ Intel® 82599EB 10 Gigabit Ethernet Controller (<code class="command">ixgbe</code> driver)
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term">Core dumping restrictions</span></dt><dd><div class="para">
+ Because core dumping is currently implemented on top of migration, it is not supported when device assignment is in use.
+ </div></dd><dt class="varlistentry"><span class="term">PCI device assignment restrictions</span></dt><dd><div class="para">
+ PCI device assignment (attaching PCI devices to virtual machines) requires host systems to have AMD IOMMU or Intel VT-d support to enable device assignment of PCI-e devices.
+ </div><div class="para">
+ For parallel/legacy PCI, only single devices behind a PCI bridge are supported.
+ </div><div class="para">
+ Multiple PCIe endpoints connected through a non-root PCIe switch require ACS support in the PCIe bridges of the PCIe switch. To disable this restriction, edit the <code class="filename">/etc/libvirt/qemu.conf</code> file and insert the line:
+ </div><pre class="programlisting">relaxed_acs_check=1</pre><div class="para">
+ Fedora 19 has limited PCI configuration space access by guest device drivers. This limitation could cause drivers that are dependent on PCI configuration space to fail configuration.
+ </div><div class="para">
+ Fedora 17 introduced interrupt remapping as a requirement for PCI device assignment. If your platform does not provide support for interrupt remapping, circumvent the KVM check for this support with the following command as the root user at the command line prompt:
+ </div><pre class="screen"># echo 1 > /sys/module/kvm/parameters/allow_unsafe_assigned_interrupts</pre></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s02.html"><strong>Prev</strong>3.2. Supported CPU Models</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_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions.html"><strong>Next</strong>4.2. Application restrictions</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-sVirt.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-sVirt.html
new file mode 100644
index 0000000..34c6551
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/chap-sVirt.html
@@ -0,0 +1,24 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 19. sVirt</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt02.html" title="Part II. Administration" /><link rel="prev" href="ch18s04.html" title="18.4. Virtualization firewall information" /><link rel="next" href="ch19s02.html" title="19.2. sVirt labeling" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s04.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch19s02.html
"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-sVirt" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 19. sVirt</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-sVirt.html#idm12596528">19.1. Security and Virtualization</a></span></dt><dt><span class="section"><a href="ch19s02.html">19.2. sVirt labeling</a></span></dt></dl></div><div class="para">
+ sVirt is a technology included in Fedora that integrates SELinux and virtualization. sVirt applies Mandatory Access Control (MAC) to improve security when using virtualized guests. The main reasons for integrating these technologies are to improve security and harden the system against bugs in the hypervisor that might be used as an attack vector aimed toward the host or to another virtualized guest.
+ </div><div class="para">
+ This chapter describes how sVirt integrates with virtualization technologies in Fedora.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm17804128">Non-virtualized environments</h5>
+ In a non-virtualized environment, hosts are separated from each other physically and each host has a self-contained environment, consisting of services such as a web server, or a DNS server. These services communicate directly to their own user space, host kernel and physical host, offering their services directly to the network. The following image represents a non-virtualized environment:
+ </div><div class="mediaobject"><img src="./images/before_virtualization.png" /></div><div class="formalpara"><h5 class="formalpara" id="idp28354096">Virtualized environments</h5>
+ In a virtualized environment, several operating systems can run on a single host kernel and physical host. The following image represents a virtualized environment:
+ </div><div class="mediaobject"><img src="./images/after_virtualization.png" /></div><div class="section" id="idm12596528"><div class="titlepage"><div><div><h2 class="title" id="idm12596528">19.1. Security and Virtualization</h2></div></div></div><div class="para">
+ When services are not virtualized, machines are physically separated. Any exploit is usually contained to the affected machine, with the obvious exception of network attacks. When services are grouped together in a virtualized environment, extra vulnerabilities emerge in the system. If there is a security flaw in the hypervisor that can be exploited by a guest instance, this guest may be able to not only attack the host, but also other guests running on that host. These attacks can extend beyond the guest instance and could expose other guests to attack.
+ </div><div class="para">
+ sVirt is an effort to isolate guests and limit their ability to launch further attacks if exploited. This is demonstrated in the following image, where an attack can not break out of the virtualized guest and extend to another guest instance:
+ </div><div class="mediaobject"><img src="./images/selinux_uuid_block.png" /></div><div class="para">
+ SELinux introduces a pluggable security framework for virtualized instances in its implementation of Mandatory Access Control (MAC). The sVirt framework allows guests and their resources to be uniquely labeled. Once labeled, rules can be applied which can reject access between different guests.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s04.html"><strong>Prev</strong>18.4. Virtualization firewall information</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="ch19s02.html"><strong>Next</strong>19.2. sVirt labeling</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html
new file mode 100644
index 0000000..60a0e94
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html
@@ -0,0 +1,123 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.4. Creating a virtual machine XML dump (configuration file)</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="prev" href="sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor.html" title="E.3. Connecting to the hypervisor" /><link rel="next" href="apes05.html" title="E.5. Suspending, resuming, saving and restoring a guest" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Sit
e" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apes05.html"><strong>Next</strong></a></li></ul><div class="section" id="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file"><div class="titlepage"><div><div><h2 class="title">E.4. Creating a virtual machine XML dump (configuration file)</h2></div></div></div><div class="para">
+ Output a guest's XML configuration file with <code class="command">virsh</code>:
+ </div><pre class="screen"># virsh dumpxml <em class="parameter"><code>{guest-id, guestname or 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>:
+ </div><pre class="screen"># virsh dumpxml <em class="replaceable"><code>GuestID</code></em> > <em class="replaceable"><code>guest.xml</code></em></pre><div class="para">
+ This file <code class="filename">guest.xml</code> can recreate the guest (refer to <a class="xref" href="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html#form-Virtualization-Managing_guests_with_virsh-Editing_a_guests_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.
+ </div><div class="para">
+ An example of <code class="command">virsh dumpxml</code> output:
+ </div><pre class="screen"># virsh dumpxml guest1-rhel6-64
+<domain type='kvm'>
+ <name>guest1-rhel6-64</name>
+ <uuid>b8d7388a-bbf2-db3a-e962-b97ca6e514bd</uuid>
+ <memory>2097152</memory>
+ <currentMemory>2097152</currentMemory>
+ <vcpu>2</vcpu>
+ <os>
+ <type arch='x86_64' machine='rhel6.2.0'>hvm</type>
+ <boot dev='hd'/>
+ </os>
+ <features>
+ <acpi/>
+ <apic/>
+ <pae/>
+ </features>
+ <clock offset='utc'/>
+ <on_poweroff>destroy</on_poweroff>
+ <on_reboot>restart</on_reboot>
+ <on_crash>restart</on_crash>
+ <devices>
+ <emulator>/usr/libexec/qemu-kvm</emulator>
+ <disk type='file' device='disk'>
+ <driver name='qemu' type='raw' cache='none' io='threads'/>
+ <source file='/home/guest-images/guest1-rhel6-64.img'/>
+ <target dev='vda' bus='virtio'/>
+ <shareable/<
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
+ </disk>
+ <interface type='bridge'>
+ <mac address='52:54:00:b9:35:a9'/>
+ <source bridge='br0'/>
+ <model type='virtio'/>
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
+ </interface>
+ <serial type='pty'>
+ <target port='0'/>
+ </serial>
+ <console type='pty'>
+ <target type='serial' port='0'/>
+ </console>
+ <input type='tablet' bus='usb'/>
+ <input type='mouse' bus='ps2'/>
+ <graphics type='vnc' port='-1' autoport='yes'/>
+ <sound model='ich6'>
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
+ </sound>
+ <video>
+ <model type='cirrus' vram='9216' heads='1'/>
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
+ </video>
+ <memballoon model='virtio'>
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
+ </memballoon>
+ </devices>
+</domain>
+
+
+</pre><div class="para">
+ Note that the <shareable/> flag is set. This indicates the device is expected to be shared between domains (assuming the hypervisor and OS support this), which means that caching should be deactivated for that device.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Creating_a_guest_from_a_configuration_file"><h5 class="formalpara">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="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html">Section E.4, “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" id="form-Virtualization-Managing_guests_with_virsh-Editing_a_guests_configuration_file"><h5 class="formalpara">Editing a guest's configuration file</h5>
+ Instead of using the <code class="command">dumpxml</code> option (refer to <a class="xref" href="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html">Section E.4, “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="section" id="sect-multifunction-pci-install"><div class="titlepage"><div><div><h3 class="title">E.4.1. Adding multifunction PCI devices to KVM guests</h3></div></div></div><div class="para">
+ This section will demonstrate how to add multi-function PCI devices to KVM guests.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Run the <code class="command">virsh edit <em class="replaceable"><code>[guestname]</code></em></code> command to edit the XML configuration file for the guest.
+ </div></li><li class="step"><div class="para">
+ In the address type tag, add a <code class="command">multifunction='on'</code> entry for <code class="command">function='0x0'</code>.
+ </div><div class="para">
+ This enables the guest to use the multifunction PCI devices.
+ </div><pre class="screen">
+<disk type='file' device='disk'>
+<driver name='qemu' type='raw' cache='none'/>
+<source file='/var/lib/libvirt/images/rhel62-1.img'/>
+<target dev='vda' bus='virtio'/>
+<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0' multifunction='on'/
+</disk>
+</pre><div class="para">
+ For a PCI device with two functions, amend the XML configuration file to include a second device with the same slot number as the first device and a different function number, such as <code class="command">function='0x1'</code>.
+ </div><div class="para">
+ For Example:
+ </div><pre class="screen">
+<disk type='file' device='disk'>
+<driver name='qemu' type='raw' cache='none'/>
+<source file='/var/lib/libvirt/images/rhel62-1.img'/>
+<target dev='vda' bus='virtio'/>
+<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0' multifunction='on'/>
+</disk>
+<disk type='file' device='disk'>
+<driver name='qemu' type='raw' cache='none'/>
+<source file='/var/lib/libvirt/images/rhel62-2.img'/>
+<target dev='vdb' bus='virtio'/>
+<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x1'/>
+</disk>
+</pre></li><li class="step"><div class="para">
+ <code class="command">lspci</code> output from the KVM guest shows:
+ </div><pre class="screen">
+$ lspci
+
+00:05.0 SCSI storage controller: Fedora, Inc Virtio block device
+00:05.1 SCSI storage controller: Fedora, Inc Virtio block device
+</pre></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor.html"><strong>Prev</strong>E.3. Connecting to the 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="apes05.html"><strong>Next</strong>E.5. Suspending, resuming, saving and restoring a...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html
new file mode 100644
index 0000000..47d6819
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html
@@ -0,0 +1,84 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.3. Installing drivers during the Windows installation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html" title="Chapter 10. KVM Para-virtualized Drivers" /><link rel="prev" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html" title="10.2. Installing the drivers on an installed Windows guest virtual machine" /><link rel="next" href="ch10s04.html" title="10.4. Using the para-virtualized drivers with Red Hat Enterprise Linux 3.9 guests" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left
.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch10s04.html"><strong>Next</strong></a></li></ul><div class="section" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk"><div class="titlepage"><div><div><h2 class="title">10.3. Installing drivers during the Windows installation</h2></div></div></div><div class="para">
+ This procedure covers installing the para-virtualized drivers during a Windows installation.
+ </div><div class="para">
+ This method allows a Windows guest virtual machine to use the para-virtualized (<code class="command">virtio</code>) drivers for the default storage device.
+ </div><div class="procedure"><h6>Procedure 10.3. Installing para-virtualized drivers during the Windows installation</h6><ol class="1"><li class="step"><div class="para">
+ Install the virtio-win package:
+ </div><pre class="screen"># yum install virtio-win</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The <span class="package">virtio-win</span> package can be found here in RHN: <a href="https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=602010">https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=602010</a>. It requires access to one of the following channels:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ RHEL Client Supplementary (v. 6)
+ </div></li><li class="listitem"><div class="para">
+ RHEL Server Supplementary (v. 6)
+ </div></li><li class="listitem"><div class="para">
+ RHEL Workstation Supplementary (v. 6)
+ </div></li></ul></div></div></div></li><li class="step"><p class="title"><strong>Creating the guest virtual machine</strong></p><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Create the virtual machine, as normal, without starting the virtual machine. Follow one of the procedures below.
+ </div></div></div><div class="para">
+ Select <span class="emphasis"><em>one</em></span> of the following guest-creation methods, and follow the instructions.
+ </div><ol class="a"><li class="step"><p class="title"><strong>Creating the guest virtual machine with virsh</strong></p><div class="para">
+ This method attaches the para-virtualized driver floppy disk to a Windows guest <span class="emphasis"><em>before</em></span> the installation.
+ </div><div class="para">
+ If the virtual machine is created from an XML definition file with <code class="command">virsh</code>, use the <code class="command">virsh define</code> command not the <code class="command">virsh create</code> command.
+ </div><ol class="i"><li class="step"><div class="para">
+ Create, but do not start, the virtual machine. Refer to the <em class="citetitle">Red Hat Enterprise Linux Virtualization Administration Guide</em> for details on creating virtual machines with the <code class="command">virsh</code> command.
+ </div></li><li class="step"><div class="para">
+ Add the driver disk as a virtualized floppy disk with the <code class="command">virsh</code> command. This example can be copied and used if there are no other virtualized floppy devices attached to the guest virtual machine. Note that <em class="replaceable"><code>vm_name</code></em> should be replaced with the name of the virtual machine.
+ </div><pre class="screen"># virsh attach-disk <em class="replaceable"><code>vm_name</code></em> /usr/share/virtio-win/virtio-win.vfd fda --type floppy</pre><div class="para">
+ You can now continue with <a class="xref" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html#aftercreation">Step 3</a>.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Creating the guest virtual machine with virt-manager and changing the disk type</strong></p><ol class="i"><li class="step"><div class="para">
+ At the final step of the virt-manager guest creation wizard, check the <span class="guilabel"><strong>Customize configuration before install</strong></span> checkbox.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-0-click-configure-before-install.png" alt="Step 5 of 5 of creating a new virtual machine with virt-manager, with a checkbox selected under Storage to customize configuration before install." /></div></div><h6>Figure 10.17. The virt-manager guest creation wizard</h6></div><br class="figure-break" /><div class="para">
+ Click on the <span class="guibutton"><strong>Finish</strong></span> button to continue.
+ </div></li><li class="step"><p class="title"><strong>Open the Add Hardware wizard</strong></p><div class="para">
+ Click the <span class="guilabel"><strong>Add Hardware</strong></span> button in the bottom left of the new panel.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-1-click-add-hardware.png" alt="The Add Hardware button." /></div></div><h6>Figure 10.18. The Add Hardware button</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Select storage device</strong></p><div class="para">
+ <span class="guilabel"><strong>Storage</strong></span> is the default selection in the <span class="guilabel"><strong>Hardware type</strong></span> list.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-2z-select-storage.png" width="444" alt="The Add new virtual hardware wizard with Storage selected in the Hardware type field." /></div></div><h6>Figure 10.19. The Add new virtual hardware wizard</h6></div><br class="figure-break" /><div class="para">
+ Ensure the <span class="guilabel"><strong>Select managed or other existing storage</strong></span> radio button is selected. Click <span class="guibutton"><strong>Browse...</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-2a-select-existing-storage.png" alt="The Add new virtual hardware wizard with Storage selected in the Hardware type field, and the Select managed or other existing storage radio button selected." /></div></div><h6>Figure 10.20. Select managed or existing storage</h6></div><br class="figure-break" /><div class="para">
+ In the new window that opens, click <span class="guilabel"><strong>Browse Local</strong></span>. Navigate to <code class="filename">/usr/share/virtio-win/virtio-win.vfd</code>, and click <span class="guibutton"><strong>Select</strong></span> to confirm.
+ </div><div class="para">
+ Change <span class="guilabel"><strong>Device type</strong></span> to <span class="guilabel"><strong>Floppy disk</strong></span>, and click <span class="guibutton"><strong>Finish</strong></span> to continue.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-select-device-type-floppy.png" alt="The Device type field, set to Floppy Disk." /></div></div><h6>Figure 10.21. Change the Device type</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Confirm settings</strong></p><div class="para">
+ Review the device settings.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-confirm-floppy-settings.png" width="444" alt="The virtual machine hardware information window with the target device (Floppy 1) selected." /></div></div><h6>Figure 10.22. The virtual machine hardware information window</h6></div><br class="figure-break" /><div class="para">
+ You have now created a removable device accessible by your virtual machine.
+ </div></li><li class="step"><p class="title"><strong>Change the hard disk type</strong></p><div class="para">
+ To change the hard disk type from <em class="replaceable"><code>IDE Disk</code></em> to <em class="replaceable"><code>Virtio Disk</code></em>, we must first remove the existing hard disk, Disk 1. Select the disk and click on the <span class="guibutton"><strong>Remove</strong></span> button.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-remove-disk1.png" width="444" alt="The virtual machine hardware information window with virtual disk Disk 1 selected, with the Remove button available at the bottom right corner of the window." /></div></div><h6>Figure 10.23. The virtual machine hardware information window</h6></div><br class="figure-break" /><div class="para">
+ Add a new virtual storage device by clicking <span class="guilabel"><strong>Add Hardware</strong></span>. Then, change the <span class="guilabel"><strong>Device type</strong></span> from <em class="replaceable"><code>IDE disk</code></em> to <em class="replaceable"><code>Virtio Disk</code></em>. Click <span class="guibutton"><strong>Finish</strong></span> to confirm the operation.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-device-type-virtio-finish.png" width="444" alt="The virtual machine hardware information window with the Floppy 1 target device selected, and the Add Hardware on the left bottom corner of the window." /></div></div><h6>Figure 10.24. The virtual machine hardware information window</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Ensure settings are correct</strong></p><div class="para">
+ Review the settings for <em class="replaceable"><code>VirtIO Disk 1</code></em>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-review-virtio-settings.png" width="444" alt="The virtual machine hardware information window with the Overview option selected, showing Basic Details, Hypervisor Details, plus expandable headings Machine Setting and Security, in the right part of the window." /></div></div><h6>Figure 10.25. The virtual machine hardware information window</h6></div><br class="figure-break" /><div class="para">
+ When you are satisfied with the configuration details, click the <span class="guilabel"><strong>Begin Installation</strong></span> button.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-5-begin-installation.png" alt="The Begin Installation button." /></div></div><h6>Figure 10.26. The Begin Installation button</h6></div><br class="figure-break" /><div class="para">
+ You can now continue with <a class="xref" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html#aftercreation">Step 3</a>.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Creating the guest virtual machine with virt-install</strong></p><div class="para">
+ Append the following parameter exactly as listed below to add the driver disk to the installation with the <code class="command">virt-install</code> command:
+ </div><pre class="screen">--disk path=/usr/share/virtio-win/virtio-win.vfd,device=floppy</pre><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ If the device you wish to add is a <code class="literal">disk</code> (that is, not a <code class="literal">floppy</code> or a <code class="literal">cdrom</code>), you will also need to add the <code class="code">bus=virtio</code> option to the end of the <em class="parameter"><code>--disk</code></em> parameter, like so:
+ </div><pre class="screen">--disk path=/usr/share/virtio-win/virtio-win.vfd,device=disk,bus=virtio</pre></div></div><div class="para">
+ According to the version of Windows you are installing, append one of the following options to the <code class="command">virt-install</code> command:
+ </div><pre class="screen">--os-variant winxp</pre><pre class="screen">--os-variant win2k3</pre><pre class="screen">--os-variant win7</pre><div class="para">
+ You can now continue with <a class="xref" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html#aftercreation">Step 3</a>.
+ </div></li></ol></li><li class="step" id="aftercreation"><p class="title"><strong>Additional steps for driver installation</strong></p><div class="para">
+ During the installation, additional steps are required to install drivers, depending on the type of Windows guest.
+ </div><ol class="a"><li class="step" id="step-Virtualization-Installing_the_KVM_Windows_para_virtualized_drivers-Windows_Server_2003"><p class="title"><strong>Windows Server 2003 and Windows XP</strong></p><div class="para">
+ Before the installation blue screen repeatedly press <span class="keycap"><strong>F6</strong></span> for third party drivers.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/XP-driver-capture.png" width="444" alt="The Windows pre-installation blue screen reads Window Setup at the top in plain text, and "Press F6 if you need to install a third party SCSI or RAID driver..." at the bottom." /></div></div><h6>Figure 10.27. The Windows Setup screen</h6></div><br class="figure-break" /><div class="para">
+ Press <span class="keycap"><strong>S</strong></span> to install additional device drivers.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/XP-driver-select2.png" width="444" alt="The next Windows pre-installation blue screen reads Window Setup at the top in plain text and details the option to install an additional device. Options at the bottom of the screen include S to "Specify Additional Device", ENTER to continue, or F3 to exit." /></div></div><h6>Figure 10.28. The Windows Setup screen</h6></div><br class="figure-break" /><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/XP-driver-select-driver.png" width="444" alt="The next Windows blue screen reads Window Setup at the top in plain text and provides options to select the SCSI Adapter to be installed. Options at the bottom of the screen include ENTER to select, or F3 to exit." /></div></div><h6>Figure 10.29. The Windows Setup screen</h6></div><br class="figure-break" /><div class="para">
+ Press <span class="keycap"><strong>Enter</strong></span> to continue the installation.
+ </div></li><li class="step" id="step-Virtualization-Installing_the_KVM_Windows_para_virtualized_drivers-Windows_Server_2008"><p class="title"><strong>Windows Server 2008</strong></p><div class="para">
+ Follow the same procedure for Windows Server 2003, but when the installer prompts you for the driver, click on <span class="guilabel"><strong>Load Driver</strong></span>, point the installer to <code class="systemitem">Drive A:</code> and pick the driver that suits your guest operating system and architecture.
+ </div></li></ol></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html"><strong>Prev</strong>10.2. Installing the drivers on an installed Wind...</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="ch10s04.html"><strong>Next</strong>10.4. Using the para-virtualized drivers with Red...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html
new file mode 100644
index 0000000..418cd20
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html
@@ -0,0 +1,82 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.2. Installing the drivers on an installed Windows guest virtual machine</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html" title="Chapter 10. KVM Para-virtualized Drivers" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html" title="Chapter 10. KVM Para-virtualized Drivers" /><link rel="next" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html" title="10.3. Installing drivers during the Windows installation" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="
Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html"><strong>Next</strong></a></li></ul><div class="section" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager"><div class="titlepage"><div><div><h2 class="title">10.2. Installing the drivers on an installed Windows guest virtual machine</h2></div></div></div><div class="para">
+ This procedure covers installing the para-virtualized drivers with a virtualized CD-ROM after Windows is installed.
+ </div><div class="para">
+ Follow <a class="xref" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html#proc-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_virt_manager_to_mount_a_CD_ROM_image_for_a_Windows_guest">Procedure 10.1, “Installing from the driver CD-ROM image with virt-manager”</a> to add a CD-ROM image with <code class="command">virt-manager</code> and then install the drivers.
+ </div><div class="procedure" id="proc-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_virt_manager_to_mount_a_CD_ROM_image_for_a_Windows_guest"><h6>Procedure 10.1. Installing from the driver CD-ROM image with virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Open virt-manager and the guest virtual machine</strong></p><div class="para">
+ Open <code class="command">virt-manager</code>, then open the guest virtual machine from the list by double-clicking the guest name.
+ </div></li><li class="step"><p class="title"><strong>Open the hardware window</strong></p><div class="para">
+ Click the lightbulb icon on the toolbar at the top of the window to view virtual hardware details.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/vm_info_button_new.png" alt="The Show virtual hardware details button." /></div></div><h6>Figure 10.1. The virtual hardware details button</h6></div><br class="figure-break" /><div class="para">
+ Then click the <span class="guibutton"><strong>Add Hardware</strong></span> button at the bottom of the new view that appears.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/vm_add_hardware_new.png" alt="The Add Hardware button." /></div></div><h6>Figure 10.2. The virtual machine hardware information window</h6></div><br class="figure-break" /><div class="para">
+ This opens a wizard for adding the new device.
+ </div></li><li class="step"><p class="title"><strong>Select the device type — for Red Hat Enterprise Linux 6 versions prior to 6.2</strong></p><div class="para">
+ Skip this step if you are using Red Hat Enterprise Linux 6.2 or later.
+ </div><div class="para">
+ On Red Hat Enterprise Linux 6 versions prior to version 6.2, you must select the type of device you wish to add. In this case, select <span class="guilabel"><strong>Storage</strong></span> from the dropdown menu.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_hardware_wizard1.png" alt="The Add new virtual hardware wizard window in Red Hat Enterprise Linux 6.1 with Storage selected as the hardware type." /></div></div><h6>Figure 10.3. The Add new virtual hardware wizard in Red Hat Enterprise Linux 6.1</h6></div><br class="figure-break" /><div class="para">
+ Click the <span class="guibutton"><strong>Finish</strong></span> button to proceed.
+ </div></li><li class="step"><p class="title"><strong>Select the ISO file</strong></p><div class="para">
+ Ensure that the <span class="guilabel"><strong>Select managed or other existing storage</strong></span> radio button is selected, and browse to the para-virtualized driver's <code class="filename">.iso</code> image file. The default location for the latest version of the drivers is <code class="filename">/usr/share/virtio-win/virtio-win.iso</code>.
+ </div><div class="para">
+ Change the <span class="guilabel"><strong>Device type</strong></span> to <span class="guilabel"><strong>IDE cdrom</strong></span> and click the <span class="guibutton"><strong>Forward</strong></span> button to proceed.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/type_assigned-KVM_PV_new.png" width="444" alt="Selecting the ISO file in the Add new virtual hardware wizard window." /></div></div><h6>Figure 10.4. The Add new virtual hardware wizard</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Finish adding virtual hardware — for Red Hat Enterprise Linux 6 versions prior to 6.2</strong></p><div class="para">
+ If you are using Red Hat Enterprise Linux 6.2 or later, skip this step.
+ </div><div class="para">
+ On Red Hat Enterprise Linux 6 versions prior to version 6.2, click on the <span class="guibutton"><strong>Finish</strong></span> button to finish adding the virtual hardware and close the wizard.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/done-KVM_PV.png" alt="The final screen of the Add new virtual hardware wizard in Red Hat Enterprise Linux 6.1." /></div></div><h6>Figure 10.5. The Add new virtual hardware wizard in Red Hat Enterprise Linux 6.1</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Reboot</strong></p><div class="para">
+ Reboot or start the virtual machine to begin using the driver disc. Virtualized IDE devices require a restart to for the virtual machine to recognize the new device.
+ </div></li></ol></div><div class="para">
+ Once the CD-ROM with the drivers is attached and the virtual machine has started, proceed with <a class="xref" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html#wooras">Procedure 10.2, “Windows installation on a Windows 7 virtual machine”</a>.
+ </div><div class="procedure" id="wooras"><h6>Procedure 10.2. Windows installation on a Windows 7 virtual machine</h6><div class="para">
+ This procedure installs the drivers on a Windows 7 virtual machine as an example. Adapt the Windows installation instructions to your guest's version of Windows.
+ </div><ol class="1"><li class="step"><p class="title"><strong>Open the Computer Management window</strong></p><div class="para">
+ On the desktop of the Windows virtual machine, click the <span class="guibutton"><strong>Windows</strong></span> icon at the bottom corner of the screen to open the Start menu.
+ </div><div class="para">
+ Right-click on <span class="guilabel"><strong>Computer</strong></span> and select <span class="guilabel"><strong>Manage</strong></span> from the pop-up menu.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/StartDevManagerInVM_win7.png" width="444" alt="A menu window opens on the Computer Management window when right-clicking D the My Computer icon on the desktop." /></div></div><h6>Figure 10.6. The Computer Management window</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Open the Device Manager</strong></p><div class="para">
+ Select the <span class="guilabel"><strong>Device Manager</strong></span> from the left-most pane. This can be found under <span class="guilabel"><strong>Computer Management</strong></span> > <span class="guilabel"><strong>System Tools</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/DevManagerStart_win7.png" width="444" alt="Opening the Device Manager on the right hand side of the Computer Management window." /></div></div><h6>Figure 10.7. The Computer Management window</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Start the driver update wizard</strong></p><ol class="a"><li class="step"><p class="title"><strong>View available system devices</strong></p><div class="para">
+ Expand <span class="guilabel"><strong>System devices</strong></span> by clicking on the arrow to its left.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/DriverInstall-Expand.png" width="444" alt="Detail of viewing available system devices from the Computer Management window." /></div></div><h6>Figure 10.8. Viewing available system devices in the Computer Management window</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Locate the appropriate device</strong></p><div class="para">
+ There are up to four drivers available: the balloon driver, the serial driver, the network driver, and the block driver.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">Balloon</code>, the balloon driver, affects the <span class="guilabel"><strong>PCI standard RAM Controller</strong></span> in the <span class="guilabel"><strong>System devices</strong></span> group.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">vioserial</code>, the serial driver, affects the <span class="guilabel"><strong>PCI Simple Communication Controller</strong></span> in the <span class="guilabel"><strong>System devices</strong></span> group.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">NetKVM</code>, the network driver, affects the <span class="guilabel"><strong>Network adapters</strong></span> group. This driver is only available if a virtio NIC is configured. Configurable parameters for this driver are documented in <a class="xref" href="netkvm-parameters.html">Appendix C, <em>NetKVM Driver Parameters</em></a>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">viostor</code>, the block driver, affects the <span class="guilabel"><strong>Disk drives</strong></span> group. This driver is only available if a virtio disk is configured.
+ </div></li></ul></div><div class="para">
+ Right-click on the device whose driver you wish to update, and select <span class="guilabel"><strong>Update Driver...</strong></span> from the pop-up menu.
+ </div><div class="para">
+ This example installs the balloon driver, so right-click on <span class="guilabel"><strong>PCI standard RAM Controller</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/StartInstallingBalloon-1_win7.png" width="444" alt="Locate the appropriate device under the expanded System Devices entry in the Computer Management window." /></div></div><h6>Figure 10.9. The Computer Management window</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Open the driver update wizard</strong></p><div class="para">
+ From the drop-down menu, select <span class="guilabel"><strong>Update Driver Software...</strong></span> to access the driver update wizard.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/DriverInstall-OpenWizard_win7.png" alt="Open the driver update wizard by right-clicking the device to be updated and selecting the first menu option, Update Driver Software, in the Computer Management window." /></div></div><h6>Figure 10.10. Opening the driver update wizard</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Specify how to find the driver</strong></p><div class="para">
+ The first page of the driver update wizard asks how you want to search for driver software. Click on the second option, <span class="guilabel"><strong>Browse my computer for driver software</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/8-BrowseForDriver_win7.png" width="444" alt="The driver update wizard provides two options for searching for driver software." /></div></div><h6>Figure 10.11. The driver update wizard</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Select the driver to install</strong></p><ol class="a"><li class="step"><p class="title"><strong>Open a file browser</strong></p><div class="para">
+ Click on <span class="guilabel"><strong>Browse...</strong></span>
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/10-w7x86driverstart_win7.png" width="444" alt="The driver update wizard." /></div></div><h6>Figure 10.12. The driver update wizard</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Browse to the location of the driver</strong></p><div class="para">
+ A separate driver is provided for each of the various combinations of operating system and architecture. The drivers are arranged hierarchically according to their driver type, the operating system, and the architecture on which they will be installed: <code class="filename"><em class="replaceable"><code>driver_type</code></em>/<em class="replaceable"><code>os</code></em>/<em class="replaceable"><code>arch</code></em>/</code>. For example, the Balloon driver for a Windows 7 operating system with an x86 (32-bit) architecture, resides in the <code class="filename">Balloon/w7/x86</code> directory.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/9-BrowseToDirectory_win7.png" alt="The Browse For Folder window, which pops up after choosing "Browse" to search for driver software on your computer. Select the folder that contains drivers for your hardware from this window." /></div></div><h6>Figure 10.13. The Browse for driver software pop-up window</h6></div><br class="figure-break" /><div class="para">
+ Once you have navigated to the correct location, click <span class="guilabel"><strong>OK</strong></span>.
+ </div></li><li class="step"><p class="title"><strong>Click <span class="guilabel"><strong>Next</strong></span> to continue</strong></p><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/10-w7x86driverchosen_win7.png" width="444" alt="The Update Driver Software wizard, with the specified location to search for driver software selected, with the Browse button on the right, and the Next and Cancel buttons at the bottom right of the window." /></div></div><h6>Figure 10.14. The Update Driver Software wizard</h6></div><br class="figure-break" /><div class="para">
+ The following screen is displayed while the driver installs:
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/DuringInstallation.png" width="444" alt="As the driver software installs, a flashing bar in the Update Driver Software wizard window shows the system is busy." /></div></div><h6>Figure 10.15. The Update Driver Software wizard</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Close the installer</strong></p><div class="para">
+ The following screen is displayed when installation is complete:
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/12-DriverInstalled.png" width="444" alt="After the driver software installs, the Update Driver Software wizard window read "Windows has successfully updated your driver software"." /></div></div><h6>Figure 10.16. The Update Driver Software wizard</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guilabel"><strong>Close</strong></span> to close the installer.
+ </div></li><li class="step"><p class="title"><strong>Reboot</strong></p><div class="para">
+ Reboot the virtual machine to complete the driver installation.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html"><strong>Prev</strong>Chapter 10. 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="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html"><strong>Next</strong>10.3. Installing drivers during the Windows insta...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices.html
new file mode 100644
index 0000000..d000d16
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices.html
@@ -0,0 +1,32 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.5. Using KVM para-virtualized drivers for existing devices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html" title="Chapter 10. KVM Para-virtualized Drivers" /><link rel="prev" href="ch10s04.html" title="10.4. Using the para-virtualized drivers with Red Hat Enterprise Linux 3.9 guests" /><link rel="next" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html" title="10.6. Using KVM para-virtualized drivers for new devices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat
.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s04.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html"><strong>Next</strong></a></li></ul><div class="section" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices"><div class="titlepage"><div><div><h2 class="title">10.5. Using KVM para-virtualized drivers for existing devices</h2></div></div></div><div class="para">
+ You can modify an existing hard disk device attached to the guest to use the <code class="command">virtio</code> driver instead of the virtualized IDE driver. The example shown in this section edits libvirt configuration files. Note that the guest virtual machine does not need to be shut down to perform these steps, however the change will not be applied until the guest is completely shut down and rebooted.
+ </div><div class="procedure"><h6>Procedure 10.4. Using KVM para-virtualized drivers for existing devices</h6><ol class="1"><li class="step"><div class="para">
+ Ensure that you have installed the appropriate driver (<code class="classname">viostor</code>), as described in <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers">Section 10.1, “Installing the KVM Windows para-virtualized drivers”</a>, before continuing with this procedure.
+ </div></li><li class="step"><div class="para">
+ Run the <code class="command">virsh edit <guestname></code> command as root to edit the XML configuration file for your device. For example, <code class="command">virsh edit guest1</code>. The configuration files are located in <code class="filename">/etc/libvirt/qemu</code>.
+ </div></li><li class="step"><div class="para">
+ Below is a file-based block device using the virtualized IDE driver. This is a typical entry for a virtual machine 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 class="step"><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>. Note that if the disk was previously IDE it will have a target similar to hda, hdb, or hdc and so on. When changing to <span class="bold bold"><strong>bus=virtio</strong></span> the target needs to be changed to vda, vdb, or vdc accordingly.
+ </div><pre class="screen"><disk type='file' device='disk'>
+ <source file='/var/lib/libvirt/images/disk1.img'/>
+ <target <span class="bold bold"><strong>dev='vda'</strong></span> <span class="bold bold"><strong>bus='virtio'/></strong></span>
+</disk></pre></li><li class="step"><div class="para">
+ Remove the <span class="bold bold"><strong>address</strong></span> tag inside the <span class="bold bold"><strong>disk</strong></span> tags. This must be done for this procedure to work. Libvirt will regenerate the <span class="bold bold"><strong>address</strong></span> tag appropriately the next time the virtual machine is started.
+ </div></li></ol></div><div class="para">
+ 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.
+ </div><div class="para">
+ Refer to the libvirt website for more details on using Virtio: <a href="http://www.linux-kvm.org/page/Virtio">http://www.linux-kvm.org/page/Virtio</a>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s04.html"><strong>Prev</strong>10.4. Using the para-virtualized drivers with Red...</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_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html"><strong>Next</strong>10.6. Using KVM para-virtualized drivers for new ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/1-7RHEL_local_install.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/1-7RHEL_local_install.png
new file mode 100644
index 0000000..68ad5bb
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/1-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/1-Iso_general.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/1-Iso_general.png
new file mode 100644
index 0000000..564c85d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/1-Iso_general.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/1-files_PV-win.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/1-files_PV-win.png
new file mode 100644
index 0000000..bfb31dc
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/1-files_PV-win.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/10-7RHEL_local_install.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/10-7RHEL_local_install.png
new file mode 100644
index 0000000..309f788
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/10-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverchosen.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverchosen.png
new file mode 100644
index 0000000..92e56a0
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverchosen.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverchosen_win7.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverchosen_win7.png
new file mode 100644
index 0000000..abd28c8
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverchosen_win7.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverstart.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverstart.png
new file mode 100644
index 0000000..83b8d25
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverstart.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverstart_win7.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverstart_win7.png
new file mode 100644
index 0000000..e02377c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverstart_win7.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/11-7RHEL_local_install.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/11-7RHEL_local_install.png
new file mode 100644
index 0000000..c11a72a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/11-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/12-DriverInstalled.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/12-DriverInstalled.png
new file mode 100644
index 0000000..cb71880
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/12-DriverInstalled.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/14-StartInstallSerial.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/14-StartInstallSerial.png
new file mode 100644
index 0000000..ad1a744
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/14-StartInstallSerial.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/2-7RHEL_local_install.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/2-7RHEL_local_install.png
new file mode 100644
index 0000000..5cc3eef
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/2-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/2-Iso_Balloon_Os.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/2-Iso_Balloon_Os.png
new file mode 100644
index 0000000..7280b22
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/2-Iso_Balloon_Os.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/3-7RHEL_local_install.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/3-7RHEL_local_install.png
new file mode 100644
index 0000000..ec3adc0
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/3-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/3-Iso_Balloon_Os_arch.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/3-Iso_Balloon_Os_arch.png
new file mode 100644
index 0000000..72ed471
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/3-Iso_Balloon_Os_arch.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/3_PCI_Device.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/3_PCI_Device.png
new file mode 100644
index 0000000..6d45920
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/3_PCI_Device.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/4-7RHEL_local_install.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/4-7RHEL_local_install.png
new file mode 100644
index 0000000..ba41670
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/4-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/4-Iso_balloon_files.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/4-Iso_balloon_files.png
new file mode 100644
index 0000000..bc73a65
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/4-Iso_balloon_files.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/4_finish.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/4_finish.png
new file mode 100644
index 0000000..92a37ea
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/4_finish.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/5-7RHEL_local_install.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/5-7RHEL_local_install.png
new file mode 100644
index 0000000..05c4e27
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/5-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/6-7RHEL_local_install.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/6-7RHEL_local_install.png
new file mode 100644
index 0000000..211498b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/6-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/6.4-2.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/6.4-2.png
new file mode 100644
index 0000000..88f6dd9
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/6.4-2.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/6.4-3.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/6.4-3.png
new file mode 100644
index 0000000..985c268
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/6.4-3.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/6.4-4.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/6.4-4.png
new file mode 100644
index 0000000..ee00ec2
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/6.4-4.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/7-7RHEL_local_install.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/7-7RHEL_local_install.png
new file mode 100644
index 0000000..9bca57c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/7-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/8-7RHEL_local_install.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/8-7RHEL_local_install.png
new file mode 100644
index 0000000..accbc04
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/8-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/8-BrowseForDriver.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/8-BrowseForDriver.png
new file mode 100644
index 0000000..9adc468
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/8-BrowseForDriver.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/8-BrowseForDriver_win7.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/8-BrowseForDriver_win7.png
new file mode 100644
index 0000000..cdc6ad1
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/8-BrowseForDriver_win7.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/9-7RHEL_local_install.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/9-7RHEL_local_install.png
new file mode 100644
index 0000000..0b5c0eb
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/9-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/9-BrowseToDirectory.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/9-BrowseToDirectory.png
new file mode 100644
index 0000000..fa98b9c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/9-BrowseToDirectory.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/9-BrowseToDirectory_win7.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/9-BrowseToDirectory_win7.png
new file mode 100644
index 0000000..a41edd6
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/9-BrowseToDirectory_win7.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/COPYME.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/COPYME.png
new file mode 100644
index 0000000..f99eaad
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/COPYME.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ChangeType.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ChangeType.png
new file mode 100644
index 0000000..5b78310
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ChangeType.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Connection_Details.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Connection_Details.png
new file mode 100644
index 0000000..27f542b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Connection_Details.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Create-1.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Create-1.png
new file mode 100644
index 0000000..4e3e649
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Create-1.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/DevManagerStart.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/DevManagerStart.png
new file mode 100644
index 0000000..930a787
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/DevManagerStart.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/DevManagerStart_win7.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/DevManagerStart_win7.png
new file mode 100644
index 0000000..2fba9a8
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/DevManagerStart_win7.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-Expand.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-Expand.png
new file mode 100644
index 0000000..3b49f18
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-Expand.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-OpenWizard.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-OpenWizard.png
new file mode 100644
index 0000000..74918fc
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-OpenWizard.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-OpenWizard_win7.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-OpenWizard_win7.png
new file mode 100644
index 0000000..aeaa604
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-OpenWizard_win7.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/DriverInstallExpand_win7.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/DriverInstallExpand_win7.png
new file mode 100644
index 0000000..d906057
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/DriverInstallExpand_win7.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/DuringInstallation.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/DuringInstallation.png
new file mode 100644
index 0000000..389ed9a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/DuringInstallation.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Iso_Balloon_files.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Iso_Balloon_files.png
new file mode 100644
index 0000000..e024530
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Iso_Balloon_files.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Iso_general.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Iso_general.png
new file mode 100644
index 0000000..f99eaad
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Iso_general.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ManageStart.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ManageStart.png
new file mode 100644
index 0000000..3ab0161
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ManageStart.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Network_hardware.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Network_hardware.png
new file mode 100644
index 0000000..a4d305b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Network_hardware.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Network_hardware_virtio.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Network_hardware_virtio.png
new file mode 100644
index 0000000..4c18960
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Network_hardware_virtio.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/PCIremoval.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/PCIremoval.png
new file mode 100644
index 0000000..5817e55
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/PCIremoval.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/PXEguest_5of5.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/PXEguest_5of5.png
new file mode 100644
index 0000000..1348bf3
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/PXEguest_5of5.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_cpu+ram.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_cpu+ram.png
new file mode 100644
index 0000000..ad33769
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_cpu+ram.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_finish_advanced.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_finish_advanced.png
new file mode 100644
index 0000000..057d47d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_finish_advanced.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_storage.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_storage.png
new file mode 100644
index 0000000..fcd4b8a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_storage.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_storage_local.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_storage_local.png
new file mode 100644
index 0000000..613e684
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_storage_local.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_virt-manager_new_1.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_virt-manager_new_1.png
new file mode 100644
index 0000000..73bf11f
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_virt-manager_new_1.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6local_choose.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6local_choose.png
new file mode 100644
index 0000000..0178c2c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6local_choose.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6local_selectedISO.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6local_selectedISO.png
new file mode 100644
index 0000000..de74827
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6local_selectedISO.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHELKVMpackages-2.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHELKVMpackages-2.png
new file mode 100644
index 0000000..65aa27a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHELKVMpackages-2.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHELKVMpackages.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHELKVMpackages.png
new file mode 100644
index 0000000..ef73b85
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHELKVMpackages.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHELcustomize14.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHELcustomize14.png
new file mode 100644
index 0000000..83050fc
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHELcustomize14.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHELcustomize15.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHELcustomize15.png
new file mode 100644
index 0000000..597f744
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHELcustomize15.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHELkvmSelect.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHELkvmSelect.png
new file mode 100644
index 0000000..6b897c6
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/RHELkvmSelect.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/SR-IOV_implementation.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/SR-IOV_implementation.png
new file mode 100644
index 0000000..7327f39
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/SR-IOV_implementation.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-VIrt-Manager-fig31pt18.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-VIrt-Manager-fig31pt18.png
new file mode 100644
index 0000000..1299ffa
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-VIrt-Manager-fig31pt18.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt1.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt1.png
new file mode 100644
index 0000000..2319393
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt1.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt11.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt11.png
new file mode 100644
index 0000000..8cad81e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt11.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt13.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt13.png
new file mode 100644
index 0000000..caf6608
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt13.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt14.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt14.png
new file mode 100644
index 0000000..3254d26
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt14.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt15.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt15.png
new file mode 100644
index 0000000..362e28b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt15.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt16.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt16.png
new file mode 100644
index 0000000..841484e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt16.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt17.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt17.png
new file mode 100644
index 0000000..cd88714
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt17.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt19.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt19.png
new file mode 100644
index 0000000..e0d075d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt19.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt2.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt2.png
new file mode 100644
index 0000000..95665bc
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt2.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt24.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt24.png
new file mode 100644
index 0000000..c1c6edf
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt24.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt24a.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt24a.png
new file mode 100644
index 0000000..48c1808
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt24a.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt27.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt27.png
new file mode 100644
index 0000000..541d6d9
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt27.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt28.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt28.png
new file mode 100644
index 0000000..fb670c0
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt28.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt29.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt29.png
new file mode 100644
index 0000000..4b1904b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt29.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt3.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt3.png
new file mode 100644
index 0000000..d19603a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt3.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt4.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt4.png
new file mode 100644
index 0000000..c4439e4
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt4.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt5.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt5.png
new file mode 100644
index 0000000..9801530
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt5.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt6.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt6.png
new file mode 100644
index 0000000..baf2a69
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt6.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt7.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt7.png
new file mode 100644
index 0000000..955b48b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt7.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt25.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt25.png
new file mode 100644
index 0000000..6cc2283
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt25.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt25a.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt25a.png
new file mode 100644
index 0000000..bd59c7e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt25a.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt26.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt26.png
new file mode 100644
index 0000000..08eca7b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt26.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic1.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic1.png
new file mode 100644
index 0000000..7c133fa
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic1.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic10.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic10.png
new file mode 100644
index 0000000..2967923
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic10.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic11.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic11.png
new file mode 100644
index 0000000..ddd69b4
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic11.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic2.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic2.png
new file mode 100644
index 0000000..52a4bec
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic2.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic3.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic3.png
new file mode 100644
index 0000000..7be870b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic3.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic4.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic4.png
new file mode 100644
index 0000000..79d74a5
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic4.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic5.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic5.png
new file mode 100644
index 0000000..67e8ac5
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic5.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic6.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic6.png
new file mode 100644
index 0000000..5a53e96
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic6.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic7.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic7.png
new file mode 100644
index 0000000..4e17f51
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic7.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic8.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic8.png
new file mode 100644
index 0000000..ceee7d9
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic8.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic9.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic9.png
new file mode 100644
index 0000000..97d8476
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic9.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic1-virt-mgr-guests.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic1-virt-mgr-guests.png
new file mode 100644
index 0000000..ea86b26
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic1-virt-mgr-guests.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic2-add-connection-pull-down.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic2-add-connection-pull-down.png
new file mode 100644
index 0000000..82c0542
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic2-add-connection-pull-down.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic3-Add Connection.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic3-Add Connection.png
new file mode 100644
index 0000000..ffff21f
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic3-Add Connection.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic3-Add-Connection.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic3-Add-Connection.png
new file mode 100644
index 0000000..bc5028e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic3-Add-Connection.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic4-OpenSSH.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic4-OpenSSH.png
new file mode 100644
index 0000000..314c36a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic4-OpenSSH.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic5-guest-select-migrate.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic5-guest-select-migrate.png
new file mode 100644
index 0000000..70018bf
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic5-guest-select-migrate.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic6-final-before-migrate.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic6-final-before-migrate.png
new file mode 100644
index 0000000..f244ff7
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic6-final-before-migrate.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic7-Migrating-guest1-rhel6-64.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic7-Migrating-guest1-rhel6-64.png
new file mode 100644
index 0000000..12202b4
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic7-Migrating-guest1-rhel6-64.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic8-migrated.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic8-migrated.png
new file mode 100644
index 0000000..3cce087
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic8-migrated.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-rhel6pv-virt-method.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-rhel6pv-virt-method.png
new file mode 100644
index 0000000..5f6957a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-rhel6pv-virt-method.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic1.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic1.png
new file mode 100644
index 0000000..604e0d8
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic1.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic2.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic2.png
new file mode 100644
index 0000000..7807aa3
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic2.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic4.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic4.png
new file mode 100644
index 0000000..09e2781
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic4.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic5.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic5.png
new file mode 100644
index 0000000..6950418
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic5.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic6.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic6.png
new file mode 100644
index 0000000..c267406
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic6.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic7-managed.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic7-managed.png
new file mode 100644
index 0000000..a635499
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic7-managed.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic7.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic7.png
new file mode 100644
index 0000000..c642653
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic7.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic8-create-lvm.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic8-create-lvm.png
new file mode 100644
index 0000000..010c7d0
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic8-create-lvm.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic8-new-storage-volume.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic8-new-storage-volume.png
new file mode 100644
index 0000000..542c15d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic8-new-storage-volume.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic9-local-storage.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic9-local-storage.png
new file mode 100644
index 0000000..8875f30
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic9-local-storage.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic9-storage-volume.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic9-storage-volume.png
new file mode 100644
index 0000000..9d58e09
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic9-storage-volume.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt2-pic2.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt2-pic2.png
new file mode 100644
index 0000000..b6e48c8
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt2-pic2.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt2-pic3.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt2-pic3.png
new file mode 100644
index 0000000..135ac84
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt2-pic3.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic2.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic2.png
new file mode 100644
index 0000000..b1b8667
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic2.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic3.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic3.png
new file mode 100644
index 0000000..17becd5
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic3.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic4.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic4.png
new file mode 100644
index 0000000..4d42817
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic4.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic5.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic5.png
new file mode 100644
index 0000000..c642653
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic5.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic6.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic6.png
new file mode 100644
index 0000000..2135749
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic6.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-virtlab22-Host-Details.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-virtlab22-Host-Details.png
new file mode 100644
index 0000000..d5a3eb3
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-virtlab22-Host-Details.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Section_11_pt_2_pt_2_step3_substep_c.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Section_11_pt_2_pt_2_step3_substep_c.png
new file mode 100644
index 0000000..1cb3707
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Section_11_pt_2_pt_2_step3_substep_c.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Section_11_pt_2_pt_2_step3_substep_d.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Section_11_pt_2_pt_2_step3_substep_d.png
new file mode 100644
index 0000000..650b0bb
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Section_11_pt_2_pt_2_step3_substep_d.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Select_storage_pools.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Select_storage_pools.png
new file mode 100644
index 0000000..7e4c07d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Select_storage_pools.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/StartDevManagerInVM.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/StartDevManagerInVM.png
new file mode 100644
index 0000000..438e32b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/StartDevManagerInVM.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/StartDevManagerInVM_win7.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/StartDevManagerInVM_win7.png
new file mode 100644
index 0000000..4b59a25
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/StartDevManagerInVM_win7.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/StartInstallingBalloon-1.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/StartInstallingBalloon-1.png
new file mode 100644
index 0000000..e496e60
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/StartInstallingBalloon-1.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/StartInstallingBalloon-1_win7.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/StartInstallingBalloon-1_win7.png
new file mode 100644
index 0000000..c03a94a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/StartInstallingBalloon-1_win7.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Virt-Manager-Add-Connection.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Virt-Manager-Add-Connection.png
new file mode 100644
index 0000000..44d5e61
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Virt-Manager-Add-Connection.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install.png
new file mode 100644
index 0000000..a7ef6cc
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-cpumem.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-cpumem.png
new file mode 100644
index 0000000..20afcae
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-cpumem.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-import.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-import.png
new file mode 100644
index 0000000..1b8a5c1
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-import.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-local.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-local.png
new file mode 100644
index 0000000..5cb5c11
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-local.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP4.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP4.png
new file mode 100644
index 0000000..304089a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP4.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP5-finish.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP5-finish.png
new file mode 100644
index 0000000..55f87df
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP5-finish.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_final-hardware.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_final-hardware.png
new file mode 100644
index 0000000..def864d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_final-hardware.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-capture.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-capture.png
new file mode 100644
index 0000000..aaf7cdb
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-capture.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-select-driver.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-select-driver.png
new file mode 100644
index 0000000..bc2449f
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-select-driver.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-select2.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-select2.png
new file mode 100644
index 0000000..22f75f7
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-select2.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/after_virtualization.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/after_virtualization.png
new file mode 100644
index 0000000..96bd1ee
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/after_virtualization.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/before_virtualization.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/before_virtualization.png
new file mode 100644
index 0000000..e47e9e0
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/before_virtualization.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/block_finish-virtio-win.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/block_finish-virtio-win.png
new file mode 100644
index 0000000..61fb164
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/block_finish-virtio-win.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/block_start-virtio-win.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/block_start-virtio-win.png
new file mode 100644
index 0000000..35abf5e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/block_start-virtio-win.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/bridgePXE.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/bridgePXE.png
new file mode 100644
index 0000000..4c5945f
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/bridgePXE.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/bridgefinish.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/bridgefinish.png
new file mode 100644
index 0000000..7ecb971
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/bridgefinish.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/bz734652-step3.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/bz734652-step3.png
new file mode 100644
index 0000000..5f9cd87
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/bz734652-step3.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/done-KVM_PV.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/done-KVM_PV.png
new file mode 100644
index 0000000..5176b1c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/done-KVM_PV.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/exception-virtio-win.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/exception-virtio-win.png
new file mode 100644
index 0000000..f7df9dd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/exception-virtio-win.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/icon.svg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/icon.svg
new file mode 100644
index 0000000..b2f16d0
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/icon.svg
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<svg xmlns:svg="http://www.w3.org/2000/svg" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.0" width="32" height="32" id="svg3017">
+ <defs id="defs3019">
+ <linearGradient id="linearGradient2381">
+ <stop id="stop2383" style="stop-color:#ffffff;stop-opacity:1" offset="0"/>
+ <stop id="stop2385" style="stop-color:#ffffff;stop-opacity:0" offset="1"/>
+ </linearGradient>
+ <linearGradient x1="296.4996" y1="188.81061" x2="317.32471" y2="209.69398" id="linearGradient2371" xlink:href="#linearGradient2381" gradientUnits="userSpaceOnUse" gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)"/>
+ </defs>
+ <g transform="matrix(0.437808,-0.437808,0.437808,0.437808,-220.8237,43.55311)" id="g5089">
+ <path d="m 8.4382985,-6.28125 c -0.6073916,0 -4.3132985,5.94886271 -4.3132985,8.25 l 0,26.71875 c 0,0.846384 0.5818159,1.125 1.15625,1.125 l 25.5625,0 c 0.632342,0 1.125001,-0.492658 1.125,-1.125 l 0,-5.21875 0.28125,0 c 0.49684,0 0.906249,-0.409411 0.90625,-0.90625 l 0,-27.9375 c 0,-0.4968398 -0.40941,-0.90625 -0.90625,-0.90625 l -23.8117015,0 z" transform="translate(282.8327,227.1903)" id="path5091" style="fill:#5c5c4f;stroke:#000000;stroke-width:3.23021388;stroke-miterlimit:4;stroke-dasharray:none"/>
+ <rect width="27.85074" height="29.369793" rx="1.1414107" ry="1.1414107" x="286.96509" y="227.63805" id="rect5093" style="fill:#032c87"/>
+ <path d="m 288.43262,225.43675 25.2418,0 0,29.3698 -26.37615,0.0241 1.13435,-29.39394 z" id="rect5095" style="fill:#ffffff"/>
+ <path d="m 302.44536,251.73726 c 1.38691,7.85917 -0.69311,11.28365 -0.69311,11.28365 2.24384,-1.60762 3.96426,-3.47694 4.90522,-5.736 0.96708,2.19264 1.83294,4.42866 4.27443,5.98941 0,0 -1.59504,-7.2004 -1.71143,-11.53706 l -6.77511,0 z" id="path5097" style="fill:#a70000;fill-opacity:1;stroke-width:2"/>
+ <rect width="25.241802" height="29.736675" rx="0.89682275" ry="0.89682275" x="290.73544" y="220.92249" id="rect5099" style="fill:#809cc9"/>
+ <path d="m 576.47347,725.93939 6.37084,0.41502 0.4069,29.51809 c -1.89202,-1.31785 -6.85427,-3.7608 -8.26232,-1.68101 l 0,-26.76752 c 0,-0.82246 0.66212,-1.48458 1.48458,-1.48458 z" transform="matrix(0.499065,-0.866565,0,1,0,0)" id="rect5101" style="fill:#4573b3;fill-opacity:1"/>
+ <path d="m 293.2599,221.89363 20.73918,0 c 0.45101,0 0.8141,0.3631 0.8141,0.81411 0.21547,6.32836 -19.36824,21.7635 -22.36739,17.59717 l 0,-17.59717 c 0,-0.45101 0.3631,-0.81411 0.81411,-0.81411 z" id="path5103" style="opacity:0.65536726;fill:url(#linearGradient2371);fill-opacity:1"/>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio-add-hardware.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio-add-hardware.png
new file mode 100644
index 0000000..16c8abd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio-add-hardware.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio-remove-dev.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio-remove-dev.png
new file mode 100644
index 0000000..d21be2c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio-remove-dev.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio1.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio1.png
new file mode 100755
index 0000000..4fe8553
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio1.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio1replacement.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio1replacement.png
new file mode 100644
index 0000000..e7f1805
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio1replacement.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio2.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio2.png
new file mode 100755
index 0000000..b31e7c7
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio2.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio3.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio3.png
new file mode 100755
index 0000000..3fbefbe
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio3.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio4.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio4.png
new file mode 100755
index 0000000..bbefebc
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio4.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio5.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio5.png
new file mode 100755
index 0000000..d3888d7
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio5.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio5replacement.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio5replacement.png
new file mode 100644
index 0000000..8941fd0
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio5replacement.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio6.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio6.png
new file mode 100755
index 0000000..a843646
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio6.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio6replacement.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio6replacement.png
new file mode 100644
index 0000000..530f0aa
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio6replacement.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio7.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio7.png
new file mode 100755
index 0000000..35fbb90
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio7.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio7replacement.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio7replacement.png
new file mode 100644
index 0000000..9fe1ad5
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio7replacement.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/infotabbutton.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/infotabbutton.png
new file mode 100644
index 0000000..31082a3
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/infotabbutton.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/installmedia-blank.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/installmedia-blank.png
new file mode 100644
index 0000000..365f435
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/installmedia-blank.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/installmedia-select-os1.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/installmedia-select-os1.png
new file mode 100644
index 0000000..19b7495
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/installmedia-select-os1.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/installmedia-select-volume.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/installmedia-select-volume.png
new file mode 100644
index 0000000..e6344cd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/installmedia-select-volume.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/network_finish-virtio-win.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/network_finish-virtio-win.png
new file mode 100644
index 0000000..b387250
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/network_finish-virtio-win.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/network_performance-virtio-win.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/network_performance-virtio-win.png
new file mode 100644
index 0000000..130bd7e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/network_performance-virtio-win.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/network_start-virtio-win.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/network_start-virtio-win.png
new file mode 100644
index 0000000..0db3f0e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/network_start-virtio-win.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-0-click-configure-before-install.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-0-click-configure-before-install.png
new file mode 100644
index 0000000..71783ad
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-0-click-configure-before-install.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-0-click-configure-before-install_win7.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-0-click-configure-before-install_win7.png
new file mode 100644
index 0000000..0a9ce10
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-0-click-configure-before-install_win7.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-1-click-add-hardware.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-1-click-add-hardware.png
new file mode 100644
index 0000000..e8b7783
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-1-click-add-hardware.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-10-select-custom-installation.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-10-select-custom-installation.png
new file mode 100644
index 0000000..3b12745
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-10-select-custom-installation.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-11-load-driver.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-11-load-driver.png
new file mode 100644
index 0000000..94bb9a0
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-11-load-driver.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-12-insert-disk.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-12-insert-disk.png
new file mode 100644
index 0000000..8fe079e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-12-insert-disk.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-13-select-driver-arch.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-13-select-driver-arch.png
new file mode 100644
index 0000000..21e58f3
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-13-select-driver-arch.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-14-view-drivers-loaded.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-14-view-drivers-loaded.png
new file mode 100644
index 0000000..b6be79f
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-14-view-drivers-loaded.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2-disk-type.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2-disk-type.png
new file mode 100644
index 0000000..940a1ec
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2-disk-type.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2a-select-existing-storage.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2a-select-existing-storage.png
new file mode 100644
index 0000000..eae4416
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2a-select-existing-storage.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2b-select-browse-local.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2b-select-browse-local.png
new file mode 100644
index 0000000..0068c9c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2b-select-browse-local.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2c-virtio-win-vfd.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2c-virtio-win-vfd.png
new file mode 100644
index 0000000..76529b4
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2c-virtio-win-vfd.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2z-select-storage.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2z-select-storage.png
new file mode 100644
index 0000000..bf7cc17
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2z-select-storage.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-3-floppy-advanced-options.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-3-floppy-advanced-options.png
new file mode 100644
index 0000000..2448048
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-3-floppy-advanced-options.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-4-after-adding-virtio-disk.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-4-after-adding-virtio-disk.png
new file mode 100644
index 0000000..3350be3
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-4-after-adding-virtio-disk.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-5-begin-installation.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-5-begin-installation.png
new file mode 100644
index 0000000..54eb223
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-5-begin-installation.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-6-windows-install.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-6-windows-install.png
new file mode 100644
index 0000000..8df17e7
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-6-windows-install.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-6a-select-installation-type.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-6a-select-installation-type.png
new file mode 100644
index 0000000..01196df
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-6a-select-installation-type.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-8-agree-to-license-terms.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-8-agree-to-license-terms.png
new file mode 100644
index 0000000..63a83f8
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-8-agree-to-license-terms.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-adding-virtio-disk.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-adding-virtio-disk.png
new file mode 100644
index 0000000..e87cc64
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-adding-virtio-disk.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-click-begin-installation.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-click-begin-installation.png
new file mode 100644
index 0000000..b5da7ee
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-click-begin-installation.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-floppy-settings.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-floppy-settings.png
new file mode 100644
index 0000000..f3a29de
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-floppy-settings.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-settings.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-settings.png
new file mode 100644
index 0000000..3a2ea73
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-settings.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-virtio-disk-in-use.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-virtio-disk-in-use.png
new file mode 100644
index 0000000..78d5e93
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-virtio-disk-in-use.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-device-type-virtio-finish.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-device-type-virtio-finish.png
new file mode 100644
index 0000000..2219703
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-device-type-virtio-finish.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-device-type-virtiodisk.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-device-type-virtiodisk.png
new file mode 100644
index 0000000..44ffd8e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-device-type-virtiodisk.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-remove-disk1-2.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-remove-disk1-2.png
new file mode 100644
index 0000000..4f4f38d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-remove-disk1-2.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-remove-disk1.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-remove-disk1.png
new file mode 100644
index 0000000..634439d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-remove-disk1.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-review-virtio-settings.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-review-virtio-settings.png
new file mode 100644
index 0000000..5c5f00c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-review-virtio-settings.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-select-device-type-floppy.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-select-device-type-floppy.png
new file mode 100644
index 0000000..c62349c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-select-device-type-floppy.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-storage-win7.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-storage-win7.png
new file mode 100644
index 0000000..1236b8d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-storage-win7.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/pci_host_device.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/pci_host_device.png
new file mode 100644
index 0000000..a4a3ea2
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/pci_host_device.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_create_vm.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_create_vm.png
new file mode 100644
index 0000000..211647e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_create_vm.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_finish.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_finish.png
new file mode 100644
index 0000000..d76cba1
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_finish.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_finish_3.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_finish_3.png
new file mode 100644
index 0000000..7fce9df
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_finish_3.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_install_method.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_install_method.png
new file mode 100644
index 0000000..2f9d04f
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_install_method.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_install_source_2.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_install_source_2.png
new file mode 100644
index 0000000..2293268
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_install_source_2.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_mem_n_cpu_alloc.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_mem_n_cpu_alloc.png
new file mode 100644
index 0000000..93dccd9
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_mem_n_cpu_alloc.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_network.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_network.png
new file mode 100644
index 0000000..56f4ec9
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_network.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_storage.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_storage.png
new file mode 100644
index 0000000..e71f549
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_storage.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_virt_install.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_virt_install.png
new file mode 100644
index 0000000..c9c3557
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_virt_install.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6-Screenshot-step2-existing-disk-image.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6-Screenshot-step2-existing-disk-image.png
new file mode 100644
index 0000000..3805b84
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6-Screenshot-step2-existing-disk-image.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-guest1-rhel5-64-final.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-guest1-rhel5-64-final.png
new file mode 100644
index 0000000..a0685cd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-guest1-rhel5-64-final.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step1.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step1.png
new file mode 100644
index 0000000..a2d0836
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step1.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step2.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step2.png
new file mode 100644
index 0000000..e55c49a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step2.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step3.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step3.png
new file mode 100644
index 0000000..f5bc777
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step3.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step4.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step4.png
new file mode 100644
index 0000000..4791de4
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step4.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step5.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step5.png
new file mode 100644
index 0000000..5aa1fa0
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step5.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_virt_manager.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_virt_manager.png
new file mode 100644
index 0000000..d2538a7
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_virt_manager.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/selinux_uuid_block.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/selinux_uuid_block.png
new file mode 100644
index 0000000..d1a69a9
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/selinux_uuid_block.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-1.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-1.png
new file mode 100644
index 0000000..eddb949
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-1.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-2.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-2.png
new file mode 100644
index 0000000..3738c87
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-2.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-3.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-3.png
new file mode 100644
index 0000000..5f3de0f
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-3.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-4.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-4.png
new file mode 100644
index 0000000..b17a6fb
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-4.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step-1-1.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step-1-1.png
new file mode 100644
index 0000000..ed6dc3b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step-1-1.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step1-1.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step1-1.png
new file mode 100644
index 0000000..87a0e0b
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step1-1.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step1-2.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step1-2.png
new file mode 100644
index 0000000..871e7bb
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step1-2.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step2-1.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step2-1.png
new file mode 100644
index 0000000..b7f01ae
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step2-1.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step2-2.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step2-2.png
new file mode 100644
index 0000000..25f3edd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step2-2.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step2-3.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step2-3.png
new file mode 100644
index 0000000..99b51fc
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step2-3.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step2-4.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step2-4.png
new file mode 100644
index 0000000..8910ab3
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step2-4.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step3-1.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step3-1.png
new file mode 100644
index 0000000..689a2a7
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step3-1.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step4-1.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step4-1.png
new file mode 100644
index 0000000..f12e5fd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step4-1.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step4-2.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step4-2.png
new file mode 100644
index 0000000..de53e6c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step4-2.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step5-1.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step5-1.png
new file mode 100644
index 0000000..d636dcd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step5-1.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step5-2.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step5-2.png
new file mode 100644
index 0000000..b76a181
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step5-2.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step5-3.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step5-3.png
new file mode 100644
index 0000000..bd1e219
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/step5-3.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/type_assigned-KVM_PV.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/type_assigned-KVM_PV.png
new file mode 100644
index 0000000..cdc7c6d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/type_assigned-KVM_PV.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/type_assigned-KVM_PV_new.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/type_assigned-KVM_PV_new.png
new file mode 100644
index 0000000..adb335f
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/type_assigned-KVM_PV_new.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/v2v-add_storagepool.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/v2v-add_storagepool.png
new file mode 100644
index 0000000..82710ae
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/v2v-add_storagepool.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/v2v-select_host.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/v2v-select_host.png
new file mode 100644
index 0000000..b9b1c99
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/v2v-select_host.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/v2v-storage_tab.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/v2v-storage_tab.png
new file mode 100644
index 0000000..fea967c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/v2v-storage_tab.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager-enable-disk-io.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager-enable-disk-io.png
new file mode 100644
index 0000000..9840461
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager-enable-disk-io.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager-enable-networkio.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager-enable-networkio.png
new file mode 100644
index 0000000..6260da0
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager-enable-networkio.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_nfs_step1.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_nfs_step1.png
new file mode 100644
index 0000000..43d4e7e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_nfs_step1.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_nfs_step2.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_nfs_step2.png
new file mode 100644
index 0000000..7e5d6c8
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_nfs_step2.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_storage_pool1.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_storage_pool1.png
new file mode 100644
index 0000000..3896a18
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_storage_pool1.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_storage_pool2.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_storage_pool2.png
new file mode 100644
index 0000000..1a29807
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_storage_pool2.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_hardware.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_hardware.png
new file mode 100644
index 0000000..08568e6
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_hardware.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_hardware_wizard1.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_hardware_wizard1.png
new file mode 100644
index 0000000..b45e590
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_hardware_wizard1.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_home.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_home.png
new file mode 100644
index 0000000..62dbd94
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_home.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_host_details_storage.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_host_details_storage.png
new file mode 100644
index 0000000..e4c7c00
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_host_details_storage.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_main.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_main.png
new file mode 100644
index 0000000..e6b7b0d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_main.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_newicon.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_newicon.png
new file mode 100644
index 0000000..9c0a829
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_newicon.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_select_host.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_select_host.png
new file mode 100644
index 0000000..cf2fc41
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_select_host.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_1_name_and_type.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_1_name_and_type.png
new file mode 100644
index 0000000..4c1aa23
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_1_name_and_type.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_2_target_path.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_2_target_path.png
new file mode 100644
index 0000000..67d9310
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_2_target_path.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_3_result.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_3_result.png
new file mode 100644
index 0000000..c2dc6ba
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_3_result.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_1_name_and_type.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_1_name_and_type.png
new file mode 100644
index 0000000..516a12c
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_1_name_and_type.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_2_paths_and_format.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_2_paths_and_format.png
new file mode 100644
index 0000000..86a2e05
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_2_paths_and_format.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_3_result.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_3_result.png
new file mode 100644
index 0000000..20ee4b6
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_3_result.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_1_name_and_type.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_1_name_and_type.png
new file mode 100644
index 0000000..7879370
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_1_name_and_type.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_2a_paths_and_pool.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_2a_paths_and_pool.png
new file mode 100644
index 0000000..1547ee7
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_2a_paths_and_pool.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_2b_format_warning.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_2b_format_warning.png
new file mode 100644
index 0000000..0b88899
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_2b_format_warning.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_3_result.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_3_result.png
new file mode 100644
index 0000000..9510682
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_3_result.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_virtualization_method.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_virtualization_method.png
new file mode 100644
index 0000000..6dab167
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_virtualization_method.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-disk2.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-disk2.png
new file mode 100644
index 0000000..cebc522
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-disk2.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-finish3.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-finish3.png
new file mode 100644
index 0000000..afaed72
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-finish3.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-step1.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-step1.png
new file mode 100644
index 0000000..1f8e7c4
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-step1.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-step2.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-step2.png
new file mode 100644
index 0000000..bdef1fd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-step2.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-finish3.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-finish3.png
new file mode 100644
index 0000000..700e4bc
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-finish3.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step1-new.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step1-new.png
new file mode 100644
index 0000000..3c24dd8
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step1-new.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step1.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step1.png
new file mode 100644
index 0000000..3235be4
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step1.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step2-new.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step2-new.png
new file mode 100644
index 0000000..293c735
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step2-new.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step2.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step2.png
new file mode 100644
index 0000000..f61cc79
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step2.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio0-customize.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio0-customize.png
new file mode 100644
index 0000000..49e56bb
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio0-customize.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio3-finished.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio3-finished.png
new file mode 100644
index 0000000..603725e
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtio3-finished.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtual_machine_overview.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtual_machine_overview.png
new file mode 100644
index 0000000..8a60772
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/virtual_machine_overview.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vm-add_hardware1.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vm-add_hardware1.png
new file mode 100644
index 0000000..e4e761d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vm-add_hardware1.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vm_add_hardware.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vm_add_hardware.png
new file mode 100644
index 0000000..ca4b140
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vm_add_hardware.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vm_add_hardware_new.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vm_add_hardware_new.png
new file mode 100644
index 0000000..406dc05
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vm_add_hardware_new.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vm_info_button.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vm_info_button.png
new file mode 100644
index 0000000..7c080f7
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vm_info_button.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vm_info_button_new.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vm_info_button_new.png
new file mode 100644
index 0000000..4156307
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vm_info_button_new.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create1.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create1.png
new file mode 100644
index 0000000..1768ae8
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create1.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create2.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create2.png
new file mode 100644
index 0000000..6adb9fe
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create2.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create3_ipv4addspace.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create3_ipv4addspace.png
new file mode 100644
index 0000000..6b884c5
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create3_ipv4addspace.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create4_dhcprange.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create4_dhcprange.png
new file mode 100644
index 0000000..f72639a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create4_dhcprange.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create5_connectphysnet.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create5_connectphysnet.png
new file mode 100644
index 0000000..0219a18
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create5_connectphysnet.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create6_finish.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create6_finish.png
new file mode 100644
index 0000000..632def4
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create6_finish.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create7_maintab.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create7_maintab.png
new file mode 100644
index 0000000..b7df642
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create7_maintab.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_maintab.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_maintab.png
new file mode 100644
index 0000000..d2104e8
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_maintab.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_menuselect.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_menuselect.png
new file mode 100644
index 0000000..7a7623d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_menuselect.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-01-switch.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-01-switch.png
new file mode 100644
index 0000000..9aa78c1
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-01-switch.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-02-switchandtwoguests.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-02-switchandtwoguests.png
new file mode 100644
index 0000000..9256a76
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-02-switchandtwoguests.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-03-hostwithswitch.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-03-hostwithswitch.png
new file mode 100644
index 0000000..d41424a
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-03-hostwithswitch.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-04-hostwithnatswitch.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-04-hostwithnatswitch.png
new file mode 100644
index 0000000..e94c04d
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-04-hostwithnatswitch.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-05-switchwithdnsmasq.jpg b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-05-switchwithdnsmasq.jpg
new file mode 100644
index 0000000..204d854
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-05-switchwithdnsmasq.jpg differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-06-routed-switch.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-06-routed-switch.png
new file mode 100644
index 0000000..5b5af96
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-06-routed-switch.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-07-isolated-switch.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-07-isolated-switch.png
new file mode 100644
index 0000000..1c234cb
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-07-isolated-switch.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-08-network-overview.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-08-network-overview.png
new file mode 100644
index 0000000..61c1342
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-08-network-overview.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-09-routed-mode-DMZ.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-09-routed-mode-DMZ.png
new file mode 100644
index 0000000..f1ea4e9
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-09-routed-mode-DMZ.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-10-routed-mode-datacenter.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-10-routed-mode-datacenter.png
new file mode 100644
index 0000000..35cd345
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-10-routed-mode-datacenter.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-11-router-mode-mac-restricted.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-11-router-mode-mac-restricted.png
new file mode 100644
index 0000000..bbf3882
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-11-router-mode-mac-restricted.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-12-network-tab-default.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-12-network-tab-default.png
new file mode 100644
index 0000000..63d3582
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/vn-12-network-tab-default.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/w7x86driverchosen.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/w7x86driverchosen.png
new file mode 100644
index 0000000..3f1a832
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/w7x86driverchosen.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/win2003_select_hal.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/win2003_select_hal.png
new file mode 100644
index 0000000..c8d4ecd
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/win2003_select_hal.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/win7paravirt-click-configure-before-install.png b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/win7paravirt-click-configure-before-install.png
new file mode 100644
index 0000000..b692e68
Binary files /dev/null and b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/images/win7paravirt-click-configure-before-install.png differ
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/index.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/index.html
new file mode 100644
index 0000000..9aff631
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/index.html
@@ -0,0 +1,44 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Virtualization Deployment and Administration Guide</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><meta name="description" content="This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization." /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="next" href="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html" title="Preface" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"></li><li class="next"><a accesskey="n" href="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="book" id="idp46591
168" lang="en-US"><div class="titlepage"><div><div class="producttitle"><span class="productname">Fedora</span> <span class="productnumber">19</span></div><div><h1 id="idp46591168" class="title">Virtualization Deployment and Administration Guide</h1></div><div><h2 class="subtitle">Virtualization Documentation</h2></div><p class="edition">Edition 1.0</p><div><h3 class="corpauthor">
+ <span class="inlinemediaobject"><object data="Common_Content/images/title_logo.svg" type="image/svg+xml"> </object></span>
+
+ </h3></div><div><div xml:lang="en-US" class="authorgroup" lang="en-US"><div class="author"><h3 class="author"><span class="firstname">Laura</span> <span class="surname">Novich</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div></div><div class="author"><h3 class="author"><span class="firstname">Tahlia</span> <span class="surname">Richardson</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div></div><div class="author"><h3 class="author"><span class="firstname">Laura</span> <span class="surname">Bailey</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div></div><div class="author"><h3 class="author"><span class="firstname">Dayle</span> <span class="surname">Parker</span></h3><div class="affiliation"><span class="orgname">Red Hat</sp
an> <span class="orgdiv">Engineering Content Services</span></div></div></div></div><hr /><div><div id="idp27030992" class="legalnotice"><h1 class="legalnotice">Legal Notice</h1><div class="para">
+ Copyright <span class="trademark"></span>© 2013 Red Hat, Inc.
+ </div><div class="para">
+ The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at <a href="http://creativecommons.org/licenses/by-sa/3.0/">http://creativecommons.org/licenses/by-sa/3.0/</a>. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
+ </div><div class="para">
+ Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
+ </div><div class="para">
+ Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
+ </div><div class="para">
+ <span class="trademark">Linux</span>® is the registered trademark of Linus Torvalds in the United States and other countries.
+ </div><div class="para">
+ <span class="trademark">Java</span>® is a registered trademark of Oracle and/or its affiliates.
+ </div><div class="para">
+ <span class="trademark">XFS</span>® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
+ </div><div class="para">
+ <span class="trademark">MySQL</span>® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
+ </div><div class="para">
+ All other trademarks are the property of their respective owners.
+ </div><div class="para">
+
+<div class="address"><p><br />
+ <span class="street">1801 Varsity Drive</span><br />
+ <span class="city">Raleigh</span>, <span class="state">NC</span> <span class="postcode">27606-2072</span> <span class="country">USA</span><br />
+ <span class="phone">Phone: +1 919 754 3700</span><br />
+ <span class="phone">Phone: 888 733 4281</span><br />
+ <span class="fax">Fax: +1 919 754 3701</span></p></div>
+
+ </div></div></div><div><div class="abstract"><h6>Abstract</h6><div class="para">
+
+ </div><div class="para">
+ This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization.
+ </div></div></div></div><hr /></div><div class="toc"><dl><dt><span class="preface"><a href="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html">Preface</a></span></dt><dd><dl><dt><span class="section"><a href="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html#idm11413824">1. Document Conventions</a></span></dt><dd><dl><dt><span class="section"><a href="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html#idm7938768">1.1. Typographic Conventions</a></span></dt><dt><span class="section"><a href="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html#idp4053568">1.2. Pull-quote Conventions</a></span></dt><dt><span class="section"><a href="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html#idp3280336">1.3. Notes and Warnings</a></span></dt></dl></dd><dt><span class="section"><a href="sect_RedHat-Gett
ing_Help_and_Giving_Feedback.html">2. Getting Help and Giving Feedback</a></span></dt><dd><dl><dt><span class="section"><a href="sect_RedHat-Getting_Help_and_Giving_Feedback.html#sect_RedHat-Do_You_Need_Help">2.1. Do You Need Help?</a></span></dt><dt><span class="section"><a href="sect-RedHat-We_Need_Feedback.html">2.2. We Need Feedback!</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="pt01.html">I. Deployment</a></span></dt><dd><dl><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html">1. Introduction</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html#idp12674320">1.1. What is in this guide?</a></span></dt><dt><span class="section"><a href="ch01s02.html">1.2. Virtualization Documentation Suite</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Gues
t_Installation_Guide-System_Requirements.html">2. System requirements</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html">3. KVM guest virtual machine compatibility</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html#idp4241536">3.1. Fedora 6 support limits</a></span></dt><dt><span class="section"><a href="ch03s02.html">3.2. Supported CPU Models</a></span></dt><dd><dl><dt><span class="section"><a href="ch03s02.html#para-CPU_Models">3.2.1. Guest CPU models</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html">4. Virtualization restrictions</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualizatio
n_Restrictions.html#sect-chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-KVM_Restrictions">4.1. KVM restrictions</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions.html">4.2. Application restrictions</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions.html">4.3. Other restrictions</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html">5. Installing the virtualization packages</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installati
on-Installing_KVM_with_a_new_Red_Hat_Enterprise_Linux_installation">5.1. Configuring a Virtualization Host installation</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html">5.2. Installing virtualization packages on an existing Fedora system</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html">6. Guest virtual machine installation overview</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html#idp26095728">6.1. Guest virtual machine prerequisites and considerations</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_i
nstall.html">6.2. Creating guests with virt-install</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html">6.3. Creating guests with virt-manager</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE.html">6.4. Installing guest virtual machines with PXE</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html">7. Installing a Red Hat Enterprise Linux 6 guest virtual machine on a Red Hat Enterprise Linux 6 host</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html#idm7256240">7.1. Creating a Red Hat Enterprise Linux 6 guest with local installation media</a><
/span></dt><dt><span class="section"><a href="ch07s02.html">7.2. Creating a Red Hat Enterprise Linux 6 guest with a network installation tree</a></span></dt><dt><span class="section"><a href="ch07s03.html">7.3. Creating a Red Hat Enterprise Linux 6 guest with PXE</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch08.html">8. Virtualizing Fedora on Other Platforms</a></span></dt><dd><dl><dt><span class="section"><a href="ch08.html#idm18230720">8.1. On VMWare</a></span></dt><dt><span class="section"><a href="ch08s02.html">8.2. On Hyper-V</a></span></dt></dl></dd><dt><span class="chapter"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html">9. Installing a fully-virtualized Windows guest</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_
virtualized_guest.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_virt-install">9.1. Using virt-install to create a guest</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html">10. KVM Para-virtualized Drivers</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers">10.1. Installing the KVM Windows para-virtualized drivers</a></span></dt><dt><span class="section"><a href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html">10.2. Installing the drivers on an installed Windows guest virt
ual machine</a></span></dt><dt><span class="section"><a href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html">10.3. Installing drivers during the Windows installation</a></span></dt><dt><span class="section"><a href="ch10s04.html">10.4. Using the para-virtualized drivers with Red Hat Enterprise Linux 3.9 guests</a></span></dt><dt><span class="section"><a href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices.html">10.5. Using KVM para-virtualized drivers for existing devices</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html">10.6. Using KVM para-virtualized drivers for new devices</a></sp
an></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html">11. Network configuration</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_address_translation_NAT_with_libvirt">11.1. Network Address Translation (NAT) with libvirt</a></span></dt><dt><span class="section"><a href="ch11s02.html">11.2. Disabling vhost-net</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html">11.3. Bridged networking with libvirt</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Confi
g.html">12. PCI device configuration</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-AI_device_to_a_host">12.1. Assigning a PCI device with virsh</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host.html">12.2. Assigning a PCI device with virt-manager</a></span></dt><dt><span class="section"><a href="ch12s03.html">12.3. PCI device assignment with virt-install</a></span></dt><dt><span class="section"><a href="ch12s04.html">12.4. Detaching an assigned PCI device</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html">13. SR-IOV</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_
Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html#idm108480">13.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html">13.2. Using SR-IOV</a></span></dt><dt><span class="section"><a href="ch13s03.html">13.3. Troubleshooting SR-IOV</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management.html">14. KVM guest timing management</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html">15. Network booting with libvirt</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html#idp1296992">15.1. Preparing the boot server</a></span></dt><dd><dl><dt><span class="section"><a href=
"chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html#idm8060224">15.1.1. Setting up a PXE boot server on a private libvirt network</a></span></dt></dl></dd><dt><span class="section"><a href="ch15s02.html">15.2. Booting a guest using PXE</a></span></dt><dd><dl><dt><span class="section"><a href="ch15s02.html#idp22499056">15.2.1. Using bridged networking</a></span></dt><dt><span class="section"><a href="ch15s02s02.html">15.2.2. Using a private libvirt network</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="qemu-ga.html">16. QEMU Guest Agent</a></span></dt><dd><dl><dt><span class="section"><a href="qemu-ga.html#idp7949600">16.1. Set Up Communication between Guest Agent and Host</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="pt02.html">II. Administration</a></span></dt><dd><dl><dt><span class="chapter"><a href="chap-Virtualization_Administration_Guide-Server_best_practices.html">17. Server best
practices</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization-Security_for_virtualization.html">18. Security for virtualization</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization-Security_for_virtualization.html#sect-Virtualization-Security_for_virtualization-Storage_security_issues">18.1. Storage security issues</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization.html">18.2. SELinux and virtualization</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Security_for_virtualization-SELinux_considerations.html">18.3. SELinux</a></span></dt><dt><span class="section"><a href="ch18s04.html">18.4. Virtualization firewall information</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-sVirt.html">19. sVirt</a></span></dt><dd><dl><dt><span class="section"><a href="chap-sVirt.html#idm12596528">19.1. Security and Virtualization</a></span
></dt><dt><span class="section"><a href="ch19s02.html">19.2. sVirt labeling</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Administration_Guide-KVM_live_migration.html">20. KVM live migration</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-KVM_live_migration.html#Live_migration_requirements">20.1. Live migration requirements</a></span></dt><dt><span class="section"><a href="Live_migration_and_RHEL_compatibility.html">20.2. Live migration and Fedora version compatibility </a></span></dt><dt><span class="section"><a href="shared-storage-nfs-migration.html">20.3. Shared storage example: NFS for a simple migration</a></span></dt><dt><span class="section"><a href="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html">20.4. Live KVM migration with virsh</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh
.html#add-notes">20.4.1. Additonal tips for migration with virsh </a></span></dt><dt><span class="section"><a href="virsh-migration-arguements.html">20.4.2. Additional options for the virsh migrate command</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager.html">20.5. Migrating with virt-manager</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html">21. Remote management of guests</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html#sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_with_SSH">21.1. Remote management with SSH</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html">21.2. Remote manageme
nt over TLS and SSL</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes.html">21.3. Transport modes</a></span></dt></dl></dd><dt><span class="chapter"><a href="sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM.html">22. Overcommitting with KVM</a></span></dt><dt><span class="chapter"><a href="chap-KSM.html">23. KSM</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization_Administration_GuideAdvanced.html">24. Advanced virtualization administration</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_GuideAdvanced.html#idm7175824">24.1. Control Groups (cgroups)</a></span></dt><dt><span class="section"><a href="ch24s02.html">24.2. Hugepage support</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html">25. Miscellaneous administration tasks</a></span></dt><dd><dl><dt><span cla
ss="section"><a href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html#sect-Virtualization-Tips_and_tricks-Automatically_starting_guests">25.1. Automatically starting guests</a></span></dt><dt><span class="section"><a href="sect-mem-dump-off.html">25.2. Guest memory allocation</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Using_qemu_img.html">25.3. Using qemu-img</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions.html">25.4. Verifying virtualization extensions</a></span></dt><dt><span class="section"><a href="ch25s05.html">25.5. Setting KVM processor affinities</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address.html">25.6. Generating a new unique MAC address</a></span></dt><dt><span class="section"><a href="ch25s07.html">25.7. Improving guest response time</a></span></dt><dt><span cl
ass="section"><a href="sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html">25.8. Disable SMART disk monitoring for guests</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server.html">25.9. Configuring a VNC Server</a></span></dt><dt><span class="section"><a href="sect-gracefully-shut-down-guests.html">25.10. Gracefully shutting down guests</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers.html">25.11. Virtual machine timer management with libvirt</a></span></dt><dt><span class="section"><a href="sect-perf-mon.html">25.12. Using PMU to monitor guest performance</a></span></dt><dt><span class="section"><a href="sect-s3-s4.html">25.13. Guest virtual machine power management</a></span></dt><dt><span class="section"><a href="sect-qemu-ga.html">25.14. QEMU Guest Agent Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="sec
t-qemu-ga.html#sect-guest-synch">25.14.1. guest-sync</a></span></dt><dt><span class="section"><a href="subsect-guest-synch-delimited.html">25.14.2. guest-sync-delimited</a></span></dt></dl></dd><dt><span class="section"><a href="sect-limit-redirection.html">25.15. Setting a limit on device redirection</a></span></dt><dt><span class="section"><a href="sect-dynamic-vNIC.html">25.16. Dynamically changing a host or a network bridge that is attached to a virtual NIC</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Administration_Guide-Storage_Concepts.html">26. Storage concepts</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Concepts.html#sect-Virtualization-Storage_Concepts-Storage_Pools">26.1. Storage pools</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Storage_Concepts-Volumes.html">26.2. Volumes </a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Vir
tualization_Administration_Guide-Storage_Pools-Storage_Pools.html">27. Storage pools</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating_Storage_Pools">27.1. Creating storage pools </a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-Dedicated_Disk_Devices">27.1.1. Disk-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-File_Systems">27.1.2. Partition-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-Local_Directories">27.1.3. Directory-based storage pools</a></spa
n></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-LVM">27.1.4. LVM-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-iSCSI">27.1.5. iSCSI-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-NFS">27.1.6. NFS-based storage pools</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Administration_Guide-Storage_Volumes.html">28. Volumes </a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Volumes.html#sect-Virtualization-Storage_Volumes-Creating_volumes">28.1. Creating volumes</a></span></dt><dt><span class="secti
on"><a href="sect-Virtualization-Storage_Volumes-Cloning_volumes.html">28.2. Cloning volumes</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html">28.3. Adding storage devices to guests</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html#sect-Virtualization-Adding_storage_devices_to_guests-Adding_file_based_storage_to_a_guest">28.3.1. Adding file based storage to a guest</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html">28.3.2. Adding hard drives and other block devices to a guest</a></span></dt><dt><span class="section"><a href="sect-Managing_storage_controllers_in_a_guest.html">28.3.3. Managing storage controllers in a guest</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Virtu
alization-Storage_Volumes-Deleting_volumes.html">28.4. Deleting and removing volumes</a></span></dt></dl></dd><dt><span class="chapter"><a href="vhostmd.html">29. The Virtual Host Metrics Daemon (vhostmd)</a></span></dt><dd><dl><dt><span class="section"><a href="vhostmd.html#idm2331248">29.1. Installing vhostmd on the host</a></span></dt><dt><span class="section"><a href="ch29s02.html">29.2. Configuration of vhostmd</a></span></dt><dt><span class="section"><a href="ch29s03.html">29.3. Starting and stopping the daemon</a></span></dt><dt><span class="section"><a href="ch29s04.html">29.4. Verifying that vhostmd is working from the host</a></span></dt><dt><span class="section"><a href="ch29s05.html">29.5. Configuring guests to see the metrics</a></span></dt><dt><span class="section"><a href="ch29s06.html">29.6. Using vm-dump-metrics in Fedora guests to verify operation</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="pt03.html">III. Appendicies</a></span></dt><
dd><dl><dt><span class="appendix"><a href="chap-Virtualization_Administration_Guide-Troubleshooting.html">A. Troubleshooting</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Troubleshooting.html#sect-Virtualization-Troubleshooting_-Debugging_and_troubleshooting_">A.1. Debugging and troubleshooting tools</a></span></dt><dt><span class="section"><a href="apas02.html">A.2. kvm_stat</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles.html">A.3. Troubleshooting with serial consoles</a></span></dt><dt><span class="section"><a href="apas04.html">A.4. Virtualization log files</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Troubleshooting-Loop_device_errors.html">A.5. Loop device errors</a></span></dt><dt><span class="section"><a href="live-migration-errors.html">A.6. Live Migration Errors</a></span></dt><dt><span class="section"><a href="se
ct-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html">A.7. Enabling Intel VT-x and AMD-V virtualization hardware extensions in BIOS</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Troubleshooting-KVM_networking_performance.html">A.8. KVM networking performance</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard.html">A.9. Missing characters on guest console with Japanese keyboard</a></span></dt><dt><span class="section"><a href="sec-known-issues-windows-xp-guests.html">A.10. Known Windows XP guest issues</a></span></dt></dl></dd><dt><span class="appendix"><a href="apb.html">B. Common <span class="application"><strong>libvirt</strong></span> errors and troubleshooting</a></span></dt><dd><dl><dt><span class="section"><a href="apb.html#App_Libvirt_Daemon">B.1. <span class="application"><strong>libvirtd</strong></span
> failed to start</a></span></dt><dt><span class="section"><a href="App_Hypervisor_Connection_Fail.html">B.2. The URI failed to connect to the hypervisor</a></span></dt><dd><dl><dt><span class="section"><a href="App_Hypervisor_Connection_Fail.html#Sect_Cannot_read_CA_certificate">B.2.1. Cannot read CA certificate</a></span></dt><dt><span class="section"><a href="Sect_Failed_to_connect_socket.html">B.2.2. Failed to connect socket ... : Permission denied</a></span></dt><dt><span class="section"><a href="Sect_Other_Connectivity_Errors.html">B.2.3. Other connectivity errors</a></span></dt></dl></dd><dt><span class="section"><a href="App_Domain_Processor.html">B.3. The guest virtual machine cannot be started: <code class="computeroutput">internal error guest CPU is not compatible with host CPU</code></a></span></dt><dt><span class="section"><a href="App_Domain_Monitor_Socket.html">B.4. Guest starting fails with error: <code class="computeroutput">monitor socket did not show up</c
ode></a></span></dt><dt><span class="section"><a href="App_Domain_Console.html">B.5. <code class="computeroutput">Internal error cannot find character device (null)</code></a></span></dt><dt><span class="section"><a href="App_Domain_Not_Booting.html">B.6. Guest virtual machine booting stalls with error: <code class="computeroutput">No boot device</code></a></span></dt><dt><span class="section"><a href="App_Virt_Net_Not_Starting.html">B.7. Virtual network <em class="replaceable"><code>default</code></em> has not been started</a></span></dt><dt><span class="section"><a href="App_PXE_Guest_Boot_Fail.html">B.8. PXE boot (or DHCP) on guest failed</a></span></dt><dt><span class="section"><a href="App_Macvtap.html">B.9. Guest can reach outside network, but cannot reach host when using macvtap interface</a></span></dt><dt><span class="section"><a href="App_DHCP_Response_Checksums.html">B.10. Could not add rule to fixup DHCP response checksums on network <em class="replaceable"><code
>'default'</code></em></a></span></dt><dt><span class="section"><a href="App_Bridge_Device.html">B.11. Unable to add bridge br0 port vnet0: No such device</a></span></dt><dt><span class="section"><a href="App_Generic_Ethernet.html">B.12. Guest is unable to start with error: <code class="computeroutput">warning: could not open /dev/net/tun</code></a></span></dt><dt><span class="section"><a href="App_Migration_Address.html">B.13. Migration fails with <code class="computeroutput">Error: unable to resolve address</code></a></span></dt><dt><span class="section"><a href="App_Migration_Disk_Image.html">B.14. Migration fails with <code class="computeroutput">Unable to allow access for disk path: No such file or directory</code></a></span></dt><dt><span class="section"><a href="App_No_Guest_Machines.html">B.15. No guest virtual machines are present when <span class="application"><strong>libvirtd</strong></span> is started</a></span></dt><dt><span class="section"><a href="App_TCP_Port
s.html">B.16. Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor</a></span></dt><dt><span class="section"><a href="App_XML_Errors.html">B.17. Common XML errors</a></span></dt><dd><dl><dt><span class="section"><a href="App_XML_Errors.html#idp28425648">B.17.1. Editing domain definition</a></span></dt><dt><span class="section"><a href="apbs17s02.html">B.17.2. XML syntax errors</a></span></dt><dt><span class="section"><a href="apbs17s03.html">B.17.3. Logic and configuration errors</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="netkvm-parameters.html">C. NetKVM Driver Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="netkvm-parameters.html#idm4631968">C.1. Configurable parameters for NetKVM</a></span></dt></dl></dd><dt><span class="appendix"><a href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html">D. qemu-kvm Whitelist</a></span></dt><dd><dl><dt><span class="se
ction"><a href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html#idp5322656">D.1. Introduction</a></span></dt><dt><span class="section"><a href="apds02.html">D.2. Basic options</a></span></dt><dt><span class="section"><a href="apds03.html">D.3. Disk options</a></span></dt><dt><span class="section"><a href="apds04.html">D.4. Display options</a></span></dt><dt><span class="section"><a href="apds05.html">D.5. Network options</a></span></dt><dt><span class="section"><a href="apds06.html">D.6. Device options</a></span></dt><dt><span class="section"><a href="apds07.html">D.7. Linux/Multiboot boot </a></span></dt><dt><span class="section"><a href="apds08.html">D.8. Expert options</a></span></dt><dt><span class="section"><a href="apds09.html">D.9. Help and information options</a></span></dt><dt><span class="section"><a href="apds10.html">D.10. Miscellaneous options</a></span></dt></dl></dd><dt><span class="appendix"><a href="chap-Virtualization_Administration_Guide-M
anaging_guests_with_virsh.html">E. Managing guests with virsh</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html#idm20931200">E.1. virsh command quick reference</a></span></dt><dt><span class="section"><a href="sect-Attaching_and_updating_a_device_with_virsh.html">E.2. Attaching and updating a device with virsh</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor.html">E.3. Connecting to the hypervisor</a></span></dt><dt><span class="section"><a href="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html">E.4. Creating a virtual machine XML dump (configuration file)</a></span></dt><dd><dl><dt><span class="section"><a href="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html#sect-multifunction-pci-install">E.4.1. Adding
multifunction PCI devices to KVM guests</a></span></dt></dl></dd><dt><span class="section"><a href="apes05.html">E.5. Suspending, resuming, saving and restoring a guest</a></span></dt><dt><span class="section"><a href="apes06.html">E.6. Shutting down, rebooting and force-shutdown of a guest</a></span></dt><dt><span class="section"><a href="apes07.html">E.7. Retrieving guest information</a></span></dt><dt><span class="section"><a href="apes08.html">E.8. Retrieving node information</a></span></dt><dt><span class="section"><a href="apes09.html">E.9. Storage pool information</a></span></dt><dt><span class="section"><a href="apes10.html">E.10. Displaying per-guest information</a></span></dt><dt><span class="section"><a href="apes11.html">E.11. Managing virtual networks</a></span></dt><dt><span class="section"><a href="migrating_guests-with-virsh.html">E.12. Migrating guests with virsh</a></span></dt><dt><span class="section"><a href="sect-man-disk-image.html">E.13. Disk image ma
nagement with live block copy</a></span></dt><dd><dl><dt><span class="section"><a href="sect-man-disk-image.html#sect-blockcommit">E.13.1. Using blockcommit to shorten a backing chain</a></span></dt><dt><span class="section"><a href="sub-sect-blockpull.html">E.13.2. Using blockpull to shorten a backing chain</a></span></dt><dt><span class="section"><a href="sub-sect-blkresize.html">E.13.3. Using blockresize to change the size of a domain path</a></span></dt></dl></dd><dt><span class="section"><a href="sect-guest-cpu-model-config.html">E.14. Guest CPU model configuration</a></span></dt><dd><dl><dt><span class="section"><a href="sect-guest-cpu-model-config.html#sect-guest-cpu-intro">E.14.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-learn-about-host-cpu.html">E.14.2. Learning about the host CPU model</a></span></dt><dt><span class="section"><a href="apes14s03.html">E.14.3. Determining a compatible CPU model to suit a pool of hosts</a></span></dt><dt><s
pan class="section"><a href="apes14s04.html">E.14.4. Configuring the guest CPU model</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html">F. Managing guests with the Virtual Machine Manager (virt-manager)</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Starting_virt_manager">F.1. Starting virt-manager</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html">F.2. The Virtual Machine Manager main window</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_
Virtual_Machine_Manager_details_window_.html">F.3. The virtual hardware details window</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html">F.4. Virtual Machine graphical console</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window.html">F.5. Adding a remote connection</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html">F.6. Displaying guest details</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html">F.7. Performance monitoring</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manag
er_virt_manager-Displaying_CPU_usage.html">F.8. Displaying CPU usage for guests</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage.html">F.9. Displaying CPU usage for hosts</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO.html">F.10. Displaying Disk I/O</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO.html">F.11. Displaying Network I/O</a></span></dt></dl></dd><dt><span class="appendix"><a href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html">G. Guest disk access with offline tools</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html#sect-introduction-Virtualization_Admini
stration_Guide-Guest_Disks_libguestfs">G.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-Terminology-Guest_Disks_libguestfs.html">G.2. Terminology</a></span></dt><dt><span class="section"><a href="sect-Guide-Guest_Disks_libguestfs-installation.html">G.3. Installation</a></span></dt><dt><span class="section"><a href="sect-the_guestfish_shell.html">G.4. The guestfish shell</a></span></dt><dd><dl><dt><span class="section"><a href="sect-the_guestfish_shell.html#sect-Viewing_file_systems_with_guestfish">G.4.1. Viewing file systems with guestfish</a></span></dt><dt><span class="section"><a href="sect-Modifying-files-with-guestfish.html">G.4.2. Modifying files with guestfish</a></span></dt><dt><span class="section"><a href="sect-Other-actions-with-guestfish.html">G.4.3. Other actions with guestfish</a></span></dt><dt><span class="section"><a href="sect-Shell-scripting-with-guestfish.html">G.4.4. Shell scripting with guestfish</a></span></dt><dt><span class="s
ection"><a href="sect-Augeas-and-libguestfs-scripting.html">G.4.5. Augeas and libguestfs scripting</a></span></dt></dl></dd><dt><span class="section"><a href="sect-other-commands.html">G.5. Other commands</a></span></dt><dt><span class="section"><a href="sect-virt-rescue.html">G.6. virt-rescue: The rescue shell</a></span></dt><dd><dl><dt><span class="section"><a href="sect-virt-rescue.html#sect-virt-rescue-intro">G.6.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-run-virt-rescue.html">G.6.2. Running virt-rescue</a></span></dt></dl></dd><dt><span class="section"><a href="sect-virt-df.html">G.7. virt-df: Monitoring disk usage</a></span></dt><dd><dl><dt><span class="section"><a href="sect-virt-df.html#sect-virt-df-intro">G.7.1. Introduction</a></span></dt><dt><span class="section"><a href="run-virt-df.html">G.7.2. Running virt-df</a></span></dt></dl></dd><dt><span class="section"><a href="sect-virt-resize.html">G.8. virt-resize: resizing guests offline</
a></span></dt><dd><dl><dt><span class="section"><a href="sect-virt-resize.html#sect-virt-resize-intro">G.8.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-expand-disk-image.html">G.8.2. Expanding a disk image</a></span></dt></dl></dd><dt><span class="section"><a href="sect-virt-inspector.html">G.9. virt-inspector: inspecting guests</a></span></dt><dd><dl><dt><span class="section"><a href="sect-virt-inspector.html#sect-virt-inspector-intro">G.9.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-virt-inspector-install.html">G.9.2. Installation</a></span></dt><dt><span class="section"><a href="sect-virt-inspector-run.html">G.9.3. Running virt-inspector</a></span></dt></dl></dd><dt><span class="section"><a href="sect-virt-win-reg.html">G.10. virt-win-reg: Reading and editing the Windows Registry</a></span></dt><dd><dl><dt><span class="section"><a href="sect-virt-win-reg.html#sect-virt-win-reg-intro">G.10.1. Introduction</a></span></dt><
dt><span class="section"><a href="sect-virt-win-reg-install.html">G.10.2. Installation</a></span></dt><dt><span class="section"><a href="sect-virt-win-reg-use.html">G.10.3. Using virt-win-reg</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Using-API-Programming-Languages.html">G.11. Using the API from Programming Languages</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Using-API-Programming-Languages.html#API-and-C">G.11.1. Interaction with the API via a C program</a></span></dt></dl></dd><dt><span class="section"><a href="sect-libguestfs-troubleshoot.html">G.12. Troubleshooting</a></span></dt><dt><span class="section"><a href="sect-libguestfs-more-docs.html">G.13. Where to find further documentation</a></span></dt></dl></dd><dt><span class="appendix"><a href="chap-Virtualization_Administration_Guide-Virtual_Networking.html">H. Virtual Networking</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guid
e-Virtual_Networking.html#sect-virtual_network-switches-livbvirt">H.1. Virtual network switches</a></span></dt><dt><span class="section"><a href="sect-Network_Address_Translation-libvirt.html">H.2. Network Address Translation</a></span></dt><dt><span class="section"><a href="sect-network-protocols.html">H.3. Networking protocols</a></span></dt><dd><dl><dt><span class="section"><a href="sect-network-protocols.html#sect-DNS_and_DHCP-protocols-libvirt">H.3.1. DNS and DHCP</a></span></dt><dt><span class="section"><a href="sub-sect-routed-mode-libvirt.html">H.3.2. Routed mode</a></span></dt><dt><span class="section"><a href="sub-sect-iso-mode.html">H.3.3. Isolated mode</a></span></dt></dl></dd><dt><span class="section"><a href="sect-the-Default_Configuration-libvirt.html">H.4. The default configuration</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Virtual_Networking-Example_scenarios.html">H.5. Examples of common scenarios</a></span></dt><dd><dl><dt><span
class="section"><a href="sect-Virtualization-Virtual_Networking-Example_scenarios.html#sub-sect-routed-mode">H.5.1. Routed mode</a></span></dt><dt><span class="section"><a href="sub-sect-nat-mode.html">H.5.2. NAT mode</a></span></dt><dt><span class="section"><a href="sub-sect-isolated-mode.html">H.5.3. Isolated mode</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Virtualization-Virtual_Networking-Managing_a_virtual_network.html">H.6. Managing a virtual network</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Virtual_Networking-Creating_a_virtual_network.html">H.7. Creating a virtual network</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest.html">H.8. Attaching a virtual network to a guest</a></span></dt><dt><span class="section"><a href="sect-attch-nic-physdev.html">H.9. Directly attaching to physical interface</a></span></dt><dt><span class="section"><a href="sect
-applying-network-filtering.html">H.10. Applying network filtering</a></span></dt><dd><dl><dt><span class="section"><a href="sect-applying-network-filtering.html#intro-sub-sect-applying-network-filtering">H.10.1. Introduction</a></span></dt><dt><span class="section"><a href="sub-sect-filt-chain.html">H.10.2. Filtering chains</a></span></dt><dt><span class="section"><a href="sub-sect-filt-chain-props.html">H.10.3. Filtering chain priorities</a></span></dt><dt><span class="section"><a href="sub-sect-vars-in-filters.html">H.10.4. Usage of variables in filters</a></span></dt><dt><span class="section"><a href="sub-sect-auto-IP-add-detect-dhcp-snoop.html">H.10.5. Automatic IP address detection and DHCP snooping</a></span></dt><dt><span class="section"><a href="sub-sect-vars-reserved.html">H.10.6. Reserved Variables</a></span></dt><dt><span class="section"><a href="sub-sect-element-oview.html">H.10.7. Element and attribute overview</a></span></dt><dt><span class="section"><a href="
sub-sect-ref-filter.html">H.10.8. References to other filters</a></span></dt><dt><span class="section"><a href="sub-sect-filter-rules.html">H.10.9. Filter rules</a></span></dt><dt><span class="section"><a href="sub-sect-supp-pros.html">H.10.10. Supported protocols</a></span></dt><dt><span class="section"><a href="sub-sect-adv-filt-topics.html">H.10.11. Advanced Filter Configuration Topics</a></span></dt><dt><span class="section"><a href="sub-sect-limitations-filters-network-subsystem.html">H.10.12. Limitations</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="appe-Virtualization-Additional_resources.html">I. Additional resources</a></span></dt><dd><dl><dt><span class="section"><a href="appe-Virtualization-Additional_resources.html#sect-Virtualization-Additional_resources-Online_resources">I.1. Online resources</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Additional_resources-Installed_documentation.html">I.2. Installed documentat
ion</a></span></dt></dl></dd><dt><span class="appendix"><a href="ch-lib-dom-xml.html">J. Manipulating the domain xml</a></span></dt><dd><dl><dt><span class="section"><a href="ch-lib-dom-xml.html#sect-gen-metadata">J.1. General information and metadata</a></span></dt><dt><span class="section"><a href="sect-dom-xml-op-sys-boot.html">J.2. Operating system booting</a></span></dt><dd><dl><dt><span class="section"><a href="sect-dom-xml-op-sys-boot.html#sub-sect-op-sys-boot-bios-boot">J.2.1. BIOS bootloader</a></span></dt><dt><span class="section"><a href="sub-sect-op-sys-host-boot.html">J.2.2. Host bootloader</a></span></dt><dt><span class="section"><a href="sub-sect-op-sys-dir-kern-boot.html">J.2.3. Direct kernel boot</a></span></dt><dt><span class="section"><a href="sub-sect-op-sys-cont-boot.html">J.2.4. Container boot</a></span></dt></dl></dd><dt><span class="section"><a href="sect-smbios-sys-info.html">J.3. SMBIOS system information</a></span></dt><dt><span class="section"><a
href="sect-cpu-allocation.html">J.4. CPU allocation</a></span></dt><dt><span class="section"><a href="sect-cpu-tuning.html">J.5. CPU tuning</a></span></dt><dt><span class="section"><a href="sect-mem-back.html">J.6. Memory backing</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-mem-tuning.html">J.7. Memory tuning</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-numa-node-tuning.html">J.8. NUMA node tuning</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-blk-io-tuning.html">J.9. Block I/O tuning</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-res-part.html">J.10. Resource partitioning</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-cpu-model-top.html">J.11. CPU model and topology</a></span></dt><dd><dl><dt><span class="section"><a href="sect-libvirt-dom-xml-cpu-model-top.html#sub-sect-libvirt-dom-xml-res-part-guest-numa">J.11.1. Guest NUMA topology</a></span></dt></
dl></dd><dt><span class="section"><a href="sect-libvirt-dom-xml-event-config.html">J.12. Events configuration</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-pwr-man.html">J.13. Power Management</a></span></dt><dt><span class="section"><a href="apjs14.html">J.14. Hypervisor features</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-time-keep.html">J.15. Time keeping</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-devices.html">J.16. Devices</a></span></dt><dd><dl><dt><span class="section"><a href="sect-libvirt-dom-xml-devices.html#sub-sect-libvirt-dom-xml-devices">J.16.1. Hard drives, floppy disks, CDROMs</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-filesystems.html">J.16.2. Filesystems</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-device-addresses.html">J.16.3. Device addresses</a></span></dt><dt><span class="section"><a href="s
ub-section-libvirt-dom-xml-devices-controllers.html">J.16.4. Controllers</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-device-leases.html">J.16.5. Device leases</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-host-device-assignment.html">J.16.6. Host device assignment</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-redirected-devices.html">J.16.7. Redirected devices</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-smartcard.html">J.16.8. Smartcard devices</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html">J.16.9. Network interfaces</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-input-devices.html">J.16.10. Input devices</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-hub-devices.html">J.16.
11. Hub devices</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-graphical-framebuffers.html">J.16.12. Graphical framebuffers</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-video.html">J.16.13. Video devices</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-consoles.html">J.16.14. Consoles, serial, parallel, and channel devices</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-guest-interface.html">J.16.15. Guest interfaces</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-channel.html">J.16.16. Channel</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-host-interface.html">J.16.17. Host interface</a></span></dt></dl></dd><dt><span class="section"><a href="section-libvirt-dom-xml-sound-devices.html">J.17. Sound devices</a></span></dt><dt><span class="section">
<a href="section-libvirt-dom-xml-watchdog.html">J.18. Watchdog device</a></span></dt><dt><span class="section"><a href="section-libvirt-dom-xml-memory-baloon-device.html">J.19. Memory balloon device</a></span></dt><dt><span class="section"><a href="section-libvirt-dom-xml-random-number-gen.html">J.20. Random number generator device</a></span></dt><dt><span class="section"><a href="section-libvirt-dom-xml-tpm-device.html">J.21. TPM devices</a></span></dt><dt><span class="section"><a href="section-libvirt-dom-xml-security-label.html">J.22. Security label</a></span></dt><dt><span class="section"><a href="section-libvirt-dom-xml-example.html">J.23. Example domain XML configuration</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="appe-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Revision_History.html">K. Revision History</a></span></dt></dl></div></div><ul class="docnav"><li class="previous"></li><li class="next"><a accesskey="n" hre
f="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html"><strong>Next</strong>Preface</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/live-migration-errors.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/live-migration-errors.html
new file mode 100644
index 0000000..103f887
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/live-migration-errors.html
@@ -0,0 +1,14 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.6. Live Migration Errors</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Troubleshooting.html" title="Appendix A. Troubleshooting" /><link rel="prev" href="sect-Virtualization-Troubleshooting-Loop_device_errors.html" title="A.5. Loop device errors" /><link rel="next" href="sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html" title="A.7. Enabling Intel VT-x and AMD-V virtualization hardware extensions in BIOS" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-Troubleshooting-Loop_device_errors.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html"><strong>Next</strong></a></li></ul><div class="section" id="live-migration-errors"><div class="titlepage"><div><div><h2 class="title">A.6. Live Migration Errors</h2></div></div></div><div class="para">
+ There may be cases where a live migration causes the memory contents to be re-transfered over and over again This process causes the guest to be in a state where it is constantly writing to memory and therefore will slow down migration. If this should occur, and the guest is writing more than several tens of MBs per second, then live migration may fail to finish (converge). This issue is scheduled to be fixed in Fedora 19 or 20.
+ </div><div class="para">
+ The current live-migration implementation has a default migration time configured to 30ms. This value determines the guest pause time at the end of the migration in order to transfer the leftovers. Higher values increase the odds that live migration will converge
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Troubleshooting-Loop_device_errors.html"><strong>Prev</strong>A.5. 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-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html"><strong>Next</strong>A.7. Enabling Intel VT-x and AMD-V virtualization...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/migrating_guests-with-virsh.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/migrating_guests-with-virsh.html
new file mode 100644
index 0000000..392d211
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/migrating_guests-with-virsh.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.12. Migrating guests with virsh</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="prev" href="apes11.html" title="E.11. Managing virtual networks" /><link rel="next" href="sect-man-disk-image.html" title="E.13. Disk image management with live block copy" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey
="p" href="apes11.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-man-disk-image.html"><strong>Next</strong></a></li></ul><div class="section" id="migrating_guests-with-virsh"><div class="titlepage"><div><div><h2 class="title">E.12. Migrating guests with virsh</h2></div></div></div><div class="para">
+ Information on migration using virsh is located in the section entitled Live KVM Migration with virsh Refer to <a class="xref" href="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html">Section 20.4, “Live KVM migration with virsh”</a>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apes11.html"><strong>Prev</strong>E.11. Managing virtual networks</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-man-disk-image.html"><strong>Next</strong>E.13. Disk image management with live block copy</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/netkvm-parameters.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/netkvm-parameters.html
new file mode 100644
index 0000000..70e472f
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/netkvm-parameters.html
@@ -0,0 +1,90 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix C. NetKVM Driver Parameters</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt03.html" title="Part III. Appendicies" /><link rel="prev" href="apbs17s03s02.html" title="B.17.3.2. Incorrect drive device type" /><link rel="next" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html" title="Appendix D. qemu-kvm Whitelist" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apbs17s03s02.html"><strong>Prev</s
trong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="appendix" id="netkvm-parameters" lang="en-US"><div class="titlepage"><div><div><h1 class="title">NetKVM Driver Parameters</h1></div></div></div><div class="para">
+ After the NetKVM driver is installed, you can configure it to better suit your environment. The parameters listed in this section can be configured in the Windows <span class="guilabel"><strong>Device Manager</strong></span> (<code class="filename">devmgmt.msc</code>).
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Modifying the driver's parameters causes Windows to re-load that driver. This interrupts existing network activity.
+ </div></div></div><div class="procedure"><h6>Procedure C.1. Configuring NetKVM Parameters</h6><ol class="1"><li class="step"><p class="title"><strong>Open <span class="guilabel"><strong>Device Manager</strong></span></strong></p><div class="para">
+ Click on the <span class="guibutton"><strong>Start</strong></span> button. In the right-hand pane, right-click on <span class="guilabel"><strong>Computer</strong></span>, and click <span class="guilabel"><strong>Manage</strong></span>. If prompted, click <span class="guibutton"><strong>Continue</strong></span> on the <span class="guilabel"><strong>User Account Control</strong></span> window. This opens the <span class="guilabel"><strong>Computer Management</strong></span> window.
+ </div><div class="para">
+ In the left-hand pane of the <span class="guilabel"><strong>Computer Management</strong></span> window, click <span class="guilabel"><strong>Device Manager</strong></span>.
+ </div></li><li class="step"><p class="title"><strong>Locate the correct device</strong></p><div class="para">
+ In the central pane of the <span class="guilabel"><strong>Computer Management</strong></span> window, click on the <span class="guilabel"><strong>+</strong></span> symbol beside <span class="guilabel"><strong>Network adapters</strong></span>.
+ </div><div class="para">
+ Under the list of <span class="guilabel"><strong>Fedora VirtIO Ethernet Adapter</strong></span> devices, double-click on <span class="guilabel"><strong>NetKVM</strong></span>. This opens the <span class="guilabel"><strong>Properties</strong></span> window for that device.
+ </div></li><li class="step"><p class="title"><strong>View device parameters</strong></p><div class="para">
+ In the <span class="guilabel"><strong>Properties</strong></span> window, click on the <span class="guilabel"><strong>Advanced</strong></span> tab.
+ </div></li><li class="step"><p class="title"><strong>Modify device parameters</strong></p><div class="para">
+ Click on the parameter you wish to modify to display the options for that parameter.
+ </div><div class="para">
+ Modify the options as appropriate, then click on <span class="guibutton"><strong>OK</strong></span> to save your changes.
+ </div></li></ol></div><div class="section" id="idm4631968"><div class="titlepage"><div><div><h2 class="title" id="idm4631968">C.1. Configurable parameters for NetKVM</h2></div></div></div><div class="variablelist"><h6>Logging parameters</h6><dl class="variablelist"><dt class="varlistentry"><span class="term">Logging.Enable</span></dt><dd><div class="para">
+ A Boolean value that determines whether logging is enabled. The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">Logging.Level</span></dt><dd><div class="para">
+ An integer that defines the logging level. As the integer increases, so does the verbosity of the log. The default value is <code class="literal">0</code> (errors only). <code class="literal">1-2</code> adds configuration messages. <code class="literal">3-4</code> adds packet flow information. <code class="literal">5-6</code> adds interrupt and DPC level trace information.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ High logging levels will slow down your guest virtual machine.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">Logging.Statistics(sec)</span></dt><dd><div class="para">
+ An integer that defines whether log statistics are printed, and the time in seconds between each periodical statistics printout. The default value is <code class="literal">0</code> (no logging statistics).
+ </div></dd></dl></div><div class="variablelist"><h6>Initial parameters</h6><dl class="variablelist"><dt class="varlistentry"><span class="term">Assign MAC</span></dt><dd><div class="para">
+ A string that defines the locally-administered MAC address for the para-virtualized NIC. This is not set by default.
+ </div></dd><dt class="varlistentry"><span class="term">Init.ConnectionRate(Mb)</span></dt><dd><div class="para">
+ An integer that represents the connection rate in megabytes. The default value for Windows 2008 and later is <code class="literal">10000</code>.
+ </div></dd><dt class="varlistentry"><span class="term">Init.Do802.1PQ</span></dt><dd><div class="para">
+ A Boolean value that enables Priority/VLAN tag population and removal support. The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">Init.UseMergedBuffers</span></dt><dd><div class="para">
+ A Boolean value that enables merge-able RX buffers. The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">Init.UsePublishEvents</span></dt><dd><div class="para">
+ A Boolean value that enables published event use. The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">Init.MTUSize</span></dt><dd><div class="para">
+ An integer that defines the maximum transmission unit (MTU). The default value is <code class="literal">1500</code>. Any value from 500 to 65500 is acceptable.
+ </div></dd><dt class="varlistentry"><span class="term">Init.IndirectTx</span></dt><dd><div class="para">
+ Controls whether indirect ring descriptors are in use. The default value is <code class="literal">Disable</code>, which disables use of indirect ring descriptors. Other valid values are <code class="literal">Enable</code>, which enables indirect ring descriptor usage; and <code class="literal">Enable*</code>, which enables conditional use of indirect ring descriptors.
+ </div></dd><dt class="varlistentry"><span class="term">Init.MaxTxBuffers</span></dt><dd><div class="para">
+ An integer that represents the amount of TX ring descriptors that will be allocated. The default value is <code class="literal">1024</code>. Valid values are: 16, 32, 64, 128, 256, 512, or 1024.
+ </div></dd><dt class="varlistentry"><span class="term">Init.MaxRxBuffers</span></dt><dd><div class="para">
+ An integer that represents the amount of RX ring descriptors that will be allocated. The default value is <code class="literal">256</code>. Valid values are: 16, 32, 64, 128, 256, 512, or 1024.
+ </div></dd><dt class="varlistentry"><span class="term">Offload.Tx.Checksum</span></dt><dd><div class="para">
+ Specifies the TX checksum offloading mode.
+ </div><div class="para">
+ In Fedora 18 and onward, the valid values for this parameter are <code class="literal">All</code> (the default), which enables IP, TCP and UDP checksum offloading for both IPv4 and IPv6; <code class="literal">TCP/UDP(v4,v6)</code>, which enables TCP and UDP checksum offloading for both IPv4 and IPv6; <code class="literal">TCP/UDP(v4)</code>, which enables TCP and UDP checksum offloading for IPv4 only; and <code class="literal">TCP(v4)</code>, which enables only TCP checksum offloading for IPv4 only.
+ </div><div class="para">
+ In Fedora 17 and earlier, the valid values for this parameter are <code class="literal">TCP/UDP</code> (the default value), which enables TCP and UDP checksum offload; <code class="literal">TCP</code>, which enables only TCP checksum offload; or <code class="literal">Disable</code>, which disables TX checksum offload.
+ </div></dd><dt class="varlistentry"><span class="term">Offload.Tx.LSO</span></dt><dd><div class="para">
+ A Boolean value that enables TX TCP Large Segment Offload (LSO). The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">Offload.Rx.Checksum</span></dt><dd><div class="para">
+ Specifies the RX checksum offloading mode.
+ </div><div class="para">
+ In Fedora 18 and onward, the valid values for this parameter are <code class="literal">All</code> (the default), which enables IP, TCP and UDP checksum offloading for both IPv4 and IPv6; <code class="literal">TCP/UDP(v4,v6)</code>, which enables TCP and UDP checksum offloading for both IPv4 and IPv6; <code class="literal">TCP/UDP(v4)</code>, which enables TCP and UDP checksum offloading for IPv4 only; and <code class="literal">TCP(v4)</code>, which enables only TCP checksum offloading for IPv4 only.
+ </div><div class="para">
+ In Fedora 17 and earlier, the valid values are <code class="literal">Disable</code> (the default), which disables RX checksum offloading; <code class="literal">All</code>, which enables TCP, UDP, and IP checksum offloading; <code class="literal">TCP/UDP</code>, which enables TCP and UDP checksum offloading; and <code class="literal">TCP</code>, which enables only TCP checksum offloading.
+ </div></dd></dl></div><div class="variablelist"><h6>Test and debug parameters</h6><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Test and debug parameters should only be used for testing or debugging; they should not be used in production.
+ </div></div></div><dl class="variablelist"><dt class="varlistentry"><span class="term">TestOnly.DelayConnect(ms)</span></dt><dd><div class="para">
+ The period for which to delay connection upon startup, in milliseconds. The default value is <code class="literal">0</code>.
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.DPCChecking</span></dt><dd><div class="para">
+ Sets the DPC checking mode. <code class="literal">0</code> (the default) disables DPC checking. <code class="literal">1</code> enables DPC checking; each hang test verifies DPC activity and acts as if the DPC was spawned. <code class="literal">2</code> clears the device interrupt status and is otherwise identical to <code class="literal">1</code>.
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.Scatter-Gather</span></dt><dd><div class="para">
+ A Boolean value that determines whether scatter-gather functionality is enabled. The default value is <code class="literal">1</code> (enabled). Setting this value to <code class="literal">0</code> disables scatter-gather functionality and all dependent capabilities.
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.InterruptRecovery</span></dt><dd><div class="para">
+ A Boolean value that determines whether interrupt recovery is enabled. The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.PacketFilter</span></dt><dd><div class="para">
+ A Boolean value that determines whether packet filtering is enabled. The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.BatchReceive</span></dt><dd><div class="para">
+ A Boolean value that determines whether packets are received in batches, or singularly. The default value is <code class="literal">1</code>, which enables batched packet receipt.
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.Promiscuous</span></dt><dd><div class="para">
+ A Boolean value that determines whether promiscuous mode is enabled. The default value is <code class="literal">0</code> (disabled).
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.AnalyzeIPPackets</span></dt><dd><div class="para">
+ A Boolean value that determines whether the checksum fields of outgoing IP packets are tested and verified for debugging purposes. The default value is <code class="literal">0</code> (no checking).
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.RXThrottle</span></dt><dd><div class="para">
+ An integer that determines the number of receive packets handled in a single DPC. The default value is <code class="literal">1000</code>.
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.UseSwTxChecksum</span></dt><dd><div class="para">
+ A Boolean value that determines whether hardware checksumming is enabled. The default value is <code class="literal">0</code> (disabled).
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apbs17s03s02.html"><strong>Prev</strong>B.17.3.2. Incorrect drive device type</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_Administration_Guide-QEMU_KVM_Whitelist.html"><strong>Next</strong>Appendix D. qemu-kvm Whitelist</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html
new file mode 100644
index 0000000..c639476
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html
@@ -0,0 +1,95 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Preface</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="prev" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="next" href="sect_RedHat-Getting_Help_and_Giving_Feedback.html" title="2. Getting Help and Giving Feedback" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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="sect_RedHat-Getting_Help_and_Giving_Feedback.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="preface" id="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Preface</h1></div></div></div><div xml:lang="en-US" class="section" id="idm11413824" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="idm11413824">1. 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" id="idm7938768"><div class="titlepage"><div><div><h3 class="title" id="idm7938768">1.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 keycaps 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 keycap, all presented in mono-spaced bold and all distinguishable thanks to context.
+ </div><div class="para">
+ Key combinations can be distinguished from keycaps 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>F2</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>F1</strong></span> to return to your X-Windows session.
+ </div></blockquote></div><div class="para">
+ The first paragraph highlights the particular keycap to press. The second highlights two key combinations (each a set of three keycaps with 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; dialog box text; labeled 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</strong></span> → <span class="guisubmenu"><strong>Preferences</strong></span> → <span class="guimenuitem"><strong>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</strong></span> → <span class="guisubmenu"><strong>Accessories</strong></span> → <span class="guimenuitem"><strong>Character Map</strong></span> from the main menu bar. Next, choose <span class="guimenu"><strong>Search</strong></span> → <span class="guimenuitem"><strong>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"><stron
g>Copy</strong></span> button. Now switch back to your document and choose <span class="guimenu"><strong>Edit</strong></span> → <span class="guimenuitem"><strong>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">
+ <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">
+ Publican is a <em class="firstterm">DocBook</em> publishing system.
+ </div></blockquote></div></div><div class="section" id="idp4053568"><div class="titlepage"><div><div><h3 class="title" id="idp4053568">1.2. Pull-quote Conventions</h3></div></div></div><div class="para">
+ Terminal output and source code listings 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 add syntax highlighting as follows:
+ </div><pre class="programlisting">package org.<span class="perl_Function">jboss</span>.<span class="perl_Function">book</span>.<span class="perl_Function">jca</span>.<span class="perl_Function">ex1</span>;
+
+<span class="perl_Keyword">import</span> javax.naming.InitialContext;
+
+<span class="perl_Keyword">public</span> <span class="perl_Keyword">class</span> ExClient
+{
+ <span class="perl_Keyword">public</span> <span class="perl_DataType">static</span> <span class="perl_DataType">void</span> <span class="perl_Function">main</span>(String args[])
+ <span class="perl_Keyword">throws</span> Exception
+ {
+ InitialContext iniCtx = <span class="perl_Keyword">new</span> InitialContext();
+ Object ref = iniCtx.<span class="perl_Function">lookup</span>(<span class="perl_String">"EchoBean"</span>);
+ EchoHome home = (EchoHome) ref;
+ Echo echo = home.<span class="perl_Function">create</span>();
+
+ System.<span class="perl_Function">out</span>.<span class="perl_Function">println</span>(<span class="perl_String">"Created Echo"</span>);
+
+ System.<span class="perl_Function">out</span>.<span class="perl_Function">println</span>(<span class="perl_String">"Echo.echo('Hello') = "</span> + echo.<span class="perl_Function">echo</span>(<span class="perl_String">"Hello"</span>));
+ }
+}</pre></div><div class="section" id="idp3280336"><div class="titlepage"><div><div><h3 class="title" id="idp3280336">1.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"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Notes are tips, shortcuts or alternative approaches 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><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><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 a box labeled 'Important' will not cause data loss but may cause irritation and frustration.
+ </div></div></div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Warnings should not be ignored. Ignoring warnings will most likely cause data loss.
+ </div></div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="index.html"><strong>Prev</strong>Virtualization Deployment and Administration 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="sect_RedHat-Getting_Help_and_Giving_Feedback.html"><strong>Next</strong>2. Getting Help and Giving Feedback</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/pt01.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/pt01.html
new file mode 100644
index 0000000..82fcb6d
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/pt01.html
@@ -0,0 +1,10 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Part I. Deployment</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="prev" href="sect-RedHat-We_Need_Feedback.html" title="2.2. We Need Feedback!" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html" title="Chapter 1. Introduction" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="
p" href="sect-RedHat-We_Need_Feedback.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html"><strong>Next</strong></a></li></ul><div class="part" id="idp43279872"><div class="titlepage"><div><div><h1 class="title">Part I. Deployment</h1></div></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html">1. Introduction</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html#idp12674320">1.1. What is in this guide?</a></span></dt><dt><span class="section"><a href="ch01s02.html">1.2. Virtualization Documentation Suite</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_
Requirements.html">2. System requirements</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html">3. KVM guest virtual machine compatibility</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html#idp4241536">3.1. Fedora 6 support limits</a></span></dt><dt><span class="section"><a href="ch03s02.html">3.2. Supported CPU Models</a></span></dt><dd><dl><dt><span class="section"><a href="ch03s02.html#para-CPU_Models">3.2.1. Guest CPU models</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html">4. Virtualization restrictions</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html#sect-cha
p-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-KVM_Restrictions">4.1. KVM restrictions</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions.html">4.2. Application restrictions</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions.html">4.3. Other restrictions</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html">5. Installing the virtualization packages</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_with_a_new
_Red_Hat_Enterprise_Linux_installation">5.1. Configuring a Virtualization Host installation</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html">5.2. Installing virtualization packages on an existing Fedora system</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html">6. Guest virtual machine installation overview</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html#idp26095728">6.1. Guest virtual machine prerequisites and considerations</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install.html">6.2. Creating g
uests with virt-install</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html">6.3. Creating guests with virt-manager</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE.html">6.4. Installing guest virtual machines with PXE</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html">7. Installing a Red Hat Enterprise Linux 6 guest virtual machine on a Red Hat Enterprise Linux 6 host</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html#idm7256240">7.1. Creating a Red Hat Enterprise Linux 6 guest with local installation media</a></span></dt><dt><span class="
section"><a href="ch07s02.html">7.2. Creating a Red Hat Enterprise Linux 6 guest with a network installation tree</a></span></dt><dt><span class="section"><a href="ch07s03.html">7.3. Creating a Red Hat Enterprise Linux 6 guest with PXE</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch08.html">8. Virtualizing Fedora on Other Platforms</a></span></dt><dd><dl><dt><span class="section"><a href="ch08.html#idm18230720">8.1. On VMWare</a></span></dt><dt><span class="section"><a href="ch08s02.html">8.2. On Hyper-V</a></span></dt></dl></dd><dt><span class="chapter"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html">9. Installing a fully-virtualized Windows guest</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html#sect-
Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_virt-install">9.1. Using virt-install to create a guest</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html">10. KVM Para-virtualized Drivers</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers">10.1. Installing the KVM Windows para-virtualized drivers</a></span></dt><dt><span class="section"><a href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html">10.2. Installing the drivers on an installed Windows guest virtual machine</a></span></dt><
dt><span class="section"><a href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html">10.3. Installing drivers during the Windows installation</a></span></dt><dt><span class="section"><a href="ch10s04.html">10.4. Using the para-virtualized drivers with Red Hat Enterprise Linux 3.9 guests</a></span></dt><dt><span class="section"><a href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices.html">10.5. Using KVM para-virtualized drivers for existing devices</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html">10.6. Using KVM para-virtualized drivers for new devices</a></span></dt></dl></dd><dt><span
class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html">11. Network configuration</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_address_translation_NAT_with_libvirt">11.1. Network Address Translation (NAT) with libvirt</a></span></dt><dt><span class="section"><a href="ch11s02.html">11.2. Disabling vhost-net</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html">11.3. Bridged networking with libvirt</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html">12. PCI device confi
guration</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-AI_device_to_a_host">12.1. Assigning a PCI device with virsh</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host.html">12.2. Assigning a PCI device with virt-manager</a></span></dt><dt><span class="section"><a href="ch12s03.html">12.3. PCI device assignment with virt-install</a></span></dt><dt><span class="section"><a href="ch12s04.html">12.4. Detaching an assigned PCI device</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html">13. SR-IOV</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest
_Installation_Guide-SR_IOV.html#idm108480">13.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html">13.2. Using SR-IOV</a></span></dt><dt><span class="section"><a href="ch13s03.html">13.3. Troubleshooting SR-IOV</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management.html">14. KVM guest timing management</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html">15. Network booting with libvirt</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html#idp1296992">15.1. Preparing the boot server</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Co
nfiguration_and_Guest_Installation_Guide-Libvirt_network_booting.html#idm8060224">15.1.1. Setting up a PXE boot server on a private libvirt network</a></span></dt></dl></dd><dt><span class="section"><a href="ch15s02.html">15.2. Booting a guest using PXE</a></span></dt><dd><dl><dt><span class="section"><a href="ch15s02.html#idp22499056">15.2.1. Using bridged networking</a></span></dt><dt><span class="section"><a href="ch15s02s02.html">15.2.2. Using a private libvirt network</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="qemu-ga.html">16. QEMU Guest Agent</a></span></dt><dd><dl><dt><span class="section"><a href="qemu-ga.html#idp7949600">16.1. Set Up Communication between Guest Agent and Host</a></span></dt></dl></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-RedHat-We_Need_Feedback.html"><strong>Prev</strong>2.2. We Need Feedback!</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li c
lass="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html"><strong>Next</strong>Chapter 1. Introduction</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/pt02.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/pt02.html
new file mode 100644
index 0000000..e21aa62
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/pt02.html
@@ -0,0 +1,10 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Part II. Administration</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="prev" href="qemu-ga.html" title="Chapter 16. QEMU Guest Agent" /><link rel="next" href="chap-Virtualization_Administration_Guide-Server_best_practices.html" title="Chapter 17. Server best practices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="qemu-ga.html"
><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_Guide-Server_best_practices.html"><strong>Next</strong></a></li></ul><div class="part" id="idm8016496"><div class="titlepage"><div><div><h1 class="title">Part II. Administration</h1></div></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl><dt><span class="chapter"><a href="chap-Virtualization_Administration_Guide-Server_best_practices.html">17. Server best practices</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization-Security_for_virtualization.html">18. Security for virtualization</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization-Security_for_virtualization.html#sect-Virtualization-Security_for_virtualization-Storage_security_issues">18.1. Storage security issues</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization.html">18.2. SE
Linux and virtualization</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Security_for_virtualization-SELinux_considerations.html">18.3. SELinux</a></span></dt><dt><span class="section"><a href="ch18s04.html">18.4. Virtualization firewall information</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-sVirt.html">19. sVirt</a></span></dt><dd><dl><dt><span class="section"><a href="chap-sVirt.html#idm12596528">19.1. Security and Virtualization</a></span></dt><dt><span class="section"><a href="ch19s02.html">19.2. sVirt labeling</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Administration_Guide-KVM_live_migration.html">20. KVM live migration</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-KVM_live_migration.html#Live_migration_requirements">20.1. Live migration requirements</a></span></dt><dt><span class="section"><a href="Live_migration_and_RHEL_compatibility.h
tml">20.2. Live migration and Fedora version compatibility </a></span></dt><dt><span class="section"><a href="shared-storage-nfs-migration.html">20.3. Shared storage example: NFS for a simple migration</a></span></dt><dt><span class="section"><a href="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html">20.4. Live KVM migration with virsh</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html#add-notes">20.4.1. Additonal tips for migration with virsh </a></span></dt><dt><span class="section"><a href="virsh-migration-arguements.html">20.4.2. Additional options for the virsh migrate command</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager.html">20.5. Migrating with virt-manager</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Administration_Guide-Remote_management_of_virtu
alized_guests.html">21. Remote management of guests</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html#sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_with_SSH">21.1. Remote management with SSH</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html">21.2. Remote management over TLS and SSL</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes.html">21.3. Transport modes</a></span></dt></dl></dd><dt><span class="chapter"><a href="sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM.html">22. Overcommitting with KVM</a></span></dt><dt><span class="chapter"><a href="chap-KSM.html">23. KSM</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization_Administration_GuideAdvanced.
html">24. Advanced virtualization administration</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_GuideAdvanced.html#idm7175824">24.1. Control Groups (cgroups)</a></span></dt><dt><span class="section"><a href="ch24s02.html">24.2. Hugepage support</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html">25. Miscellaneous administration tasks</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html#sect-Virtualization-Tips_and_tricks-Automatically_starting_guests">25.1. Automatically starting guests</a></span></dt><dt><span class="section"><a href="sect-mem-dump-off.html">25.2. Guest memory allocation</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Using_qemu_img.html">25.3. Using qemu-img</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tr
icks-Verifying_virtualization_extensions.html">25.4. Verifying virtualization extensions</a></span></dt><dt><span class="section"><a href="ch25s05.html">25.5. Setting KVM processor affinities</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address.html">25.6. Generating a new unique MAC address</a></span></dt><dt><span class="section"><a href="ch25s07.html">25.7. Improving guest response time</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html">25.8. Disable SMART disk monitoring for guests</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server.html">25.9. Configuring a VNC Server</a></span></dt><dt><span class="section"><a href="sect-gracefully-shut-down-guests.html">25.10. Gracefully shutting down guests</a></span></dt><dt><span class="section"><a href="sect-Virtualization-T
ips_and_tricks-Libvirt_Managed_Timers.html">25.11. Virtual machine timer management with libvirt</a></span></dt><dt><span class="section"><a href="sect-perf-mon.html">25.12. Using PMU to monitor guest performance</a></span></dt><dt><span class="section"><a href="sect-s3-s4.html">25.13. Guest virtual machine power management</a></span></dt><dt><span class="section"><a href="sect-qemu-ga.html">25.14. QEMU Guest Agent Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="sect-qemu-ga.html#sect-guest-synch">25.14.1. guest-sync</a></span></dt><dt><span class="section"><a href="subsect-guest-synch-delimited.html">25.14.2. guest-sync-delimited</a></span></dt></dl></dd><dt><span class="section"><a href="sect-limit-redirection.html">25.15. Setting a limit on device redirection</a></span></dt><dt><span class="section"><a href="sect-dynamic-vNIC.html">25.16. Dynamically changing a host or a network bridge that is attached to a virtual NIC</a></span></dt></dl></dd><dt><span
class="chapter"><a href="chap-Virtualization_Administration_Guide-Storage_Concepts.html">26. Storage concepts</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Concepts.html#sect-Virtualization-Storage_Concepts-Storage_Pools">26.1. Storage pools</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Storage_Concepts-Volumes.html">26.2. Volumes </a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html">27. Storage pools</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating_Storage_Pools">27.1. Creating storage pools </a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-Dedicated_Disk_Devi
ces">27.1.1. Disk-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-File_Systems">27.1.2. Partition-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-Local_Directories">27.1.3. Directory-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-LVM">27.1.4. LVM-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-iSCSI">27.1.5. iSCSI-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Stora
ge_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-NFS">27.1.6. NFS-based storage pools</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Administration_Guide-Storage_Volumes.html">28. Volumes </a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Volumes.html#sect-Virtualization-Storage_Volumes-Creating_volumes">28.1. Creating volumes</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Storage_Volumes-Cloning_volumes.html">28.2. Cloning volumes</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html">28.3. Adding storage devices to guests</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html#sect-Virtualization-Adding_storage_devices_to_guests-Adding_file_based_storage_to_a_guest">
28.3.1. Adding file based storage to a guest</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html">28.3.2. Adding hard drives and other block devices to a guest</a></span></dt><dt><span class="section"><a href="sect-Managing_storage_controllers_in_a_guest.html">28.3.3. Managing storage controllers in a guest</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Virtualization-Storage_Volumes-Deleting_volumes.html">28.4. Deleting and removing volumes</a></span></dt></dl></dd><dt><span class="chapter"><a href="vhostmd.html">29. The Virtual Host Metrics Daemon (vhostmd)</a></span></dt><dd><dl><dt><span class="section"><a href="vhostmd.html#idm2331248">29.1. Installing vhostmd on the host</a></span></dt><dt><span class="section"><a href="ch29s02.html">29.2. Configuration of vhostmd</a></span></dt><dt><span class="section"><a href="ch29s03.html">29.3. Starting a
nd stopping the daemon</a></span></dt><dt><span class="section"><a href="ch29s04.html">29.4. Verifying that vhostmd is working from the host</a></span></dt><dt><span class="section"><a href="ch29s05.html">29.5. Configuring guests to see the metrics</a></span></dt><dt><span class="section"><a href="ch29s06.html">29.6. Using vm-dump-metrics in Fedora guests to verify operation</a></span></dt></dl></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="qemu-ga.html"><strong>Prev</strong>Chapter 16. QEMU Guest Agent</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_Administration_Guide-Server_best_practices.html"><strong>Next</strong>Chapter 17. Server best practices</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/pt03.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/pt03.html
new file mode 100644
index 0000000..8522ec8
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/pt03.html
@@ -0,0 +1,10 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Part III. Appendicies</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="prev" href="ch29s06.html" title="29.6. Using vm-dump-metrics in Fedora guests to verify operation" /><link rel="next" href="chap-Virtualization_Administration_Guide-Troubleshooting.html" title="Appendix A. Troubleshooting" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey=
"p" href="ch29s06.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_Guide-Troubleshooting.html"><strong>Next</strong></a></li></ul><div class="part" id="idp2910672"><div class="titlepage"><div><div><h1 class="title">Part III. Appendicies</h1></div></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl><dt><span class="appendix"><a href="chap-Virtualization_Administration_Guide-Troubleshooting.html">A. Troubleshooting</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Troubleshooting.html#sect-Virtualization-Troubleshooting_-Debugging_and_troubleshooting_">A.1. Debugging and troubleshooting tools</a></span></dt><dt><span class="section"><a href="apas02.html">A.2. kvm_stat</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles.html">A.3. Troubleshooting with serial consoles</a></sp
an></dt><dt><span class="section"><a href="apas04.html">A.4. Virtualization log files</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Troubleshooting-Loop_device_errors.html">A.5. Loop device errors</a></span></dt><dt><span class="section"><a href="live-migration-errors.html">A.6. Live Migration Errors</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html">A.7. Enabling Intel VT-x and AMD-V virtualization hardware extensions in BIOS</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Troubleshooting-KVM_networking_performance.html">A.8. KVM networking performance</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard.html">A.9. Missing characters on guest console with Japanese keyboard</a></span></dt><dt><span class="section"><a href="sec-known-issu
es-windows-xp-guests.html">A.10. Known Windows XP guest issues</a></span></dt></dl></dd><dt><span class="appendix"><a href="apb.html">B. Common <span class="application"><strong>libvirt</strong></span> errors and troubleshooting</a></span></dt><dd><dl><dt><span class="section"><a href="apb.html#App_Libvirt_Daemon">B.1. <span class="application"><strong>libvirtd</strong></span> failed to start</a></span></dt><dt><span class="section"><a href="App_Hypervisor_Connection_Fail.html">B.2. The URI failed to connect to the hypervisor</a></span></dt><dd><dl><dt><span class="section"><a href="App_Hypervisor_Connection_Fail.html#Sect_Cannot_read_CA_certificate">B.2.1. Cannot read CA certificate</a></span></dt><dt><span class="section"><a href="Sect_Failed_to_connect_socket.html">B.2.2. Failed to connect socket ... : Permission denied</a></span></dt><dt><span class="section"><a href="Sect_Other_Connectivity_Errors.html">B.2.3. Other connectivity errors</a></span></dt></dl></dd><dt><span
class="section"><a href="App_Domain_Processor.html">B.3. The guest virtual machine cannot be started: <code class="computeroutput">internal error guest CPU is not compatible with host CPU</code></a></span></dt><dt><span class="section"><a href="App_Domain_Monitor_Socket.html">B.4. Guest starting fails with error: <code class="computeroutput">monitor socket did not show up</code></a></span></dt><dt><span class="section"><a href="App_Domain_Console.html">B.5. <code class="computeroutput">Internal error cannot find character device (null)</code></a></span></dt><dt><span class="section"><a href="App_Domain_Not_Booting.html">B.6. Guest virtual machine booting stalls with error: <code class="computeroutput">No boot device</code></a></span></dt><dt><span class="section"><a href="App_Virt_Net_Not_Starting.html">B.7. Virtual network <em class="replaceable"><code>default</code></em> has not been started</a></span></dt><dt><span class="section"><a href="App_PXE_Guest_Boot_Fail.html">B
.8. PXE boot (or DHCP) on guest failed</a></span></dt><dt><span class="section"><a href="App_Macvtap.html">B.9. Guest can reach outside network, but cannot reach host when using macvtap interface</a></span></dt><dt><span class="section"><a href="App_DHCP_Response_Checksums.html">B.10. Could not add rule to fixup DHCP response checksums on network <em class="replaceable"><code>'default'</code></em></a></span></dt><dt><span class="section"><a href="App_Bridge_Device.html">B.11. Unable to add bridge br0 port vnet0: No such device</a></span></dt><dt><span class="section"><a href="App_Generic_Ethernet.html">B.12. Guest is unable to start with error: <code class="computeroutput">warning: could not open /dev/net/tun</code></a></span></dt><dt><span class="section"><a href="App_Migration_Address.html">B.13. Migration fails with <code class="computeroutput">Error: unable to resolve address</code></a></span></dt><dt><span class="section"><a href="App_Migration_Disk_Image.html">B.14. Mi
gration fails with <code class="computeroutput">Unable to allow access for disk path: No such file or directory</code></a></span></dt><dt><span class="section"><a href="App_No_Guest_Machines.html">B.15. No guest virtual machines are present when <span class="application"><strong>libvirtd</strong></span> is started</a></span></dt><dt><span class="section"><a href="App_TCP_Ports.html">B.16. Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor</a></span></dt><dt><span class="section"><a href="App_XML_Errors.html">B.17. Common XML errors</a></span></dt><dd><dl><dt><span class="section"><a href="App_XML_Errors.html#idp28425648">B.17.1. Editing domain definition</a></span></dt><dt><span class="section"><a href="apbs17s02.html">B.17.2. XML syntax errors</a></span></dt><dt><span class="section"><a href="apbs17s03.html">B.17.3. Logic and configuration errors</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href
="netkvm-parameters.html">C. NetKVM Driver Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="netkvm-parameters.html#idm4631968">C.1. Configurable parameters for NetKVM</a></span></dt></dl></dd><dt><span class="appendix"><a href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html">D. qemu-kvm Whitelist</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html#idp5322656">D.1. Introduction</a></span></dt><dt><span class="section"><a href="apds02.html">D.2. Basic options</a></span></dt><dt><span class="section"><a href="apds03.html">D.3. Disk options</a></span></dt><dt><span class="section"><a href="apds04.html">D.4. Display options</a></span></dt><dt><span class="section"><a href="apds05.html">D.5. Network options</a></span></dt><dt><span class="section"><a href="apds06.html">D.6. Device options</a></span></dt><dt><span class="section"><a href="apds07.html">D.7. Linux/Multiboot bo
ot </a></span></dt><dt><span class="section"><a href="apds08.html">D.8. Expert options</a></span></dt><dt><span class="section"><a href="apds09.html">D.9. Help and information options</a></span></dt><dt><span class="section"><a href="apds10.html">D.10. Miscellaneous options</a></span></dt></dl></dd><dt><span class="appendix"><a href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html">E. Managing guests with virsh</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html#idm20931200">E.1. virsh command quick reference</a></span></dt><dt><span class="section"><a href="sect-Attaching_and_updating_a_device_with_virsh.html">E.2. Attaching and updating a device with virsh</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor.html">E.3. Connecting to the hypervisor</a></span></dt><dt><span class="section"><a href="fo
rm-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html">E.4. Creating a virtual machine XML dump (configuration file)</a></span></dt><dd><dl><dt><span class="section"><a href="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html#sect-multifunction-pci-install">E.4.1. Adding multifunction PCI devices to KVM guests</a></span></dt></dl></dd><dt><span class="section"><a href="apes05.html">E.5. Suspending, resuming, saving and restoring a guest</a></span></dt><dt><span class="section"><a href="apes06.html">E.6. Shutting down, rebooting and force-shutdown of a guest</a></span></dt><dt><span class="section"><a href="apes07.html">E.7. Retrieving guest information</a></span></dt><dt><span class="section"><a href="apes08.html">E.8. Retrieving node information</a></span></dt><dt><span class="section"><a href="apes09.html">E.9. Storage pool information</a></span></dt><dt><span class="
section"><a href="apes10.html">E.10. Displaying per-guest information</a></span></dt><dt><span class="section"><a href="apes11.html">E.11. Managing virtual networks</a></span></dt><dt><span class="section"><a href="migrating_guests-with-virsh.html">E.12. Migrating guests with virsh</a></span></dt><dt><span class="section"><a href="sect-man-disk-image.html">E.13. Disk image management with live block copy</a></span></dt><dd><dl><dt><span class="section"><a href="sect-man-disk-image.html#sect-blockcommit">E.13.1. Using blockcommit to shorten a backing chain</a></span></dt><dt><span class="section"><a href="sub-sect-blockpull.html">E.13.2. Using blockpull to shorten a backing chain</a></span></dt><dt><span class="section"><a href="sub-sect-blkresize.html">E.13.3. Using blockresize to change the size of a domain path</a></span></dt></dl></dd><dt><span class="section"><a href="sect-guest-cpu-model-config.html">E.14. Guest CPU model configuration</a></span></dt><dd><dl><dt><span c
lass="section"><a href="sect-guest-cpu-model-config.html#sect-guest-cpu-intro">E.14.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-learn-about-host-cpu.html">E.14.2. Learning about the host CPU model</a></span></dt><dt><span class="section"><a href="apes14s03.html">E.14.3. Determining a compatible CPU model to suit a pool of hosts</a></span></dt><dt><span class="section"><a href="apes14s04.html">E.14.4. Configuring the guest CPU model</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html">F. Managing guests with the Virtual Machine Manager (virt-manager)</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Starting_virt_manager">F.1. Sta
rting virt-manager</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html">F.2. The Virtual Machine Manager main window</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_.html">F.3. The virtual hardware details window</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html">F.4. Virtual Machine graphical console</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window.html">F.5. Adding a remote connection</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Mana
ger_virt_manager-Displaying_guest_details.html">F.6. Displaying guest details</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html">F.7. Performance monitoring</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html">F.8. Displaying CPU usage for guests</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage.html">F.9. Displaying CPU usage for hosts</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO.html">F.10. Displaying Disk I/O</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Netwo
rk_IO.html">F.11. Displaying Network I/O</a></span></dt></dl></dd><dt><span class="appendix"><a href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html">G. Guest disk access with offline tools</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html#sect-introduction-Virtualization_Administration_Guide-Guest_Disks_libguestfs">G.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-Terminology-Guest_Disks_libguestfs.html">G.2. Terminology</a></span></dt><dt><span class="section"><a href="sect-Guide-Guest_Disks_libguestfs-installation.html">G.3. Installation</a></span></dt><dt><span class="section"><a href="sect-the_guestfish_shell.html">G.4. The guestfish shell</a></span></dt><dd><dl><dt><span class="section"><a href="sect-the_guestfish_shell.html#sect-Viewing_file_systems_with_guestfish">G.4.1. Viewing file systems with guestfish</a></span></dt><dt><span class="section">
<a href="sect-Modifying-files-with-guestfish.html">G.4.2. Modifying files with guestfish</a></span></dt><dt><span class="section"><a href="sect-Other-actions-with-guestfish.html">G.4.3. Other actions with guestfish</a></span></dt><dt><span class="section"><a href="sect-Shell-scripting-with-guestfish.html">G.4.4. Shell scripting with guestfish</a></span></dt><dt><span class="section"><a href="sect-Augeas-and-libguestfs-scripting.html">G.4.5. Augeas and libguestfs scripting</a></span></dt></dl></dd><dt><span class="section"><a href="sect-other-commands.html">G.5. Other commands</a></span></dt><dt><span class="section"><a href="sect-virt-rescue.html">G.6. virt-rescue: The rescue shell</a></span></dt><dd><dl><dt><span class="section"><a href="sect-virt-rescue.html#sect-virt-rescue-intro">G.6.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-run-virt-rescue.html">G.6.2. Running virt-rescue</a></span></dt></dl></dd><dt><span class="section"><a href="sect-virt-
df.html">G.7. virt-df: Monitoring disk usage</a></span></dt><dd><dl><dt><span class="section"><a href="sect-virt-df.html#sect-virt-df-intro">G.7.1. Introduction</a></span></dt><dt><span class="section"><a href="run-virt-df.html">G.7.2. Running virt-df</a></span></dt></dl></dd><dt><span class="section"><a href="sect-virt-resize.html">G.8. virt-resize: resizing guests offline</a></span></dt><dd><dl><dt><span class="section"><a href="sect-virt-resize.html#sect-virt-resize-intro">G.8.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-expand-disk-image.html">G.8.2. Expanding a disk image</a></span></dt></dl></dd><dt><span class="section"><a href="sect-virt-inspector.html">G.9. virt-inspector: inspecting guests</a></span></dt><dd><dl><dt><span class="section"><a href="sect-virt-inspector.html#sect-virt-inspector-intro">G.9.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-virt-inspector-install.html">G.9.2. Installation</a></span></dt><dt><
span class="section"><a href="sect-virt-inspector-run.html">G.9.3. Running virt-inspector</a></span></dt></dl></dd><dt><span class="section"><a href="sect-virt-win-reg.html">G.10. virt-win-reg: Reading and editing the Windows Registry</a></span></dt><dd><dl><dt><span class="section"><a href="sect-virt-win-reg.html#sect-virt-win-reg-intro">G.10.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-virt-win-reg-install.html">G.10.2. Installation</a></span></dt><dt><span class="section"><a href="sect-virt-win-reg-use.html">G.10.3. Using virt-win-reg</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Using-API-Programming-Languages.html">G.11. Using the API from Programming Languages</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Using-API-Programming-Languages.html#API-and-C">G.11.1. Interaction with the API via a C program</a></span></dt></dl></dd><dt><span class="section"><a href="sect-libguestfs-troubleshoot.html">G.12. Troubles
hooting</a></span></dt><dt><span class="section"><a href="sect-libguestfs-more-docs.html">G.13. Where to find further documentation</a></span></dt></dl></dd><dt><span class="appendix"><a href="chap-Virtualization_Administration_Guide-Virtual_Networking.html">H. Virtual Networking</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Virtual_Networking.html#sect-virtual_network-switches-livbvirt">H.1. Virtual network switches</a></span></dt><dt><span class="section"><a href="sect-Network_Address_Translation-libvirt.html">H.2. Network Address Translation</a></span></dt><dt><span class="section"><a href="sect-network-protocols.html">H.3. Networking protocols</a></span></dt><dd><dl><dt><span class="section"><a href="sect-network-protocols.html#sect-DNS_and_DHCP-protocols-libvirt">H.3.1. DNS and DHCP</a></span></dt><dt><span class="section"><a href="sub-sect-routed-mode-libvirt.html">H.3.2. Routed mode</a></span></dt><dt><span class="s
ection"><a href="sub-sect-iso-mode.html">H.3.3. Isolated mode</a></span></dt></dl></dd><dt><span class="section"><a href="sect-the-Default_Configuration-libvirt.html">H.4. The default configuration</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Virtual_Networking-Example_scenarios.html">H.5. Examples of common scenarios</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Virtualization-Virtual_Networking-Example_scenarios.html#sub-sect-routed-mode">H.5.1. Routed mode</a></span></dt><dt><span class="section"><a href="sub-sect-nat-mode.html">H.5.2. NAT mode</a></span></dt><dt><span class="section"><a href="sub-sect-isolated-mode.html">H.5.3. Isolated mode</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Virtualization-Virtual_Networking-Managing_a_virtual_network.html">H.6. Managing a virtual network</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Virtual_Networking-Creating_a_virtual_network.html">H.7. Cr
eating a virtual network</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest.html">H.8. Attaching a virtual network to a guest</a></span></dt><dt><span class="section"><a href="sect-attch-nic-physdev.html">H.9. Directly attaching to physical interface</a></span></dt><dt><span class="section"><a href="sect-applying-network-filtering.html">H.10. Applying network filtering</a></span></dt><dd><dl><dt><span class="section"><a href="sect-applying-network-filtering.html#intro-sub-sect-applying-network-filtering">H.10.1. Introduction</a></span></dt><dt><span class="section"><a href="sub-sect-filt-chain.html">H.10.2. Filtering chains</a></span></dt><dt><span class="section"><a href="sub-sect-filt-chain-props.html">H.10.3. Filtering chain priorities</a></span></dt><dt><span class="section"><a href="sub-sect-vars-in-filters.html">H.10.4. Usage of variables in filters</a></span></dt><dt><span class="section"><a href
="sub-sect-auto-IP-add-detect-dhcp-snoop.html">H.10.5. Automatic IP address detection and DHCP snooping</a></span></dt><dt><span class="section"><a href="sub-sect-vars-reserved.html">H.10.6. Reserved Variables</a></span></dt><dt><span class="section"><a href="sub-sect-element-oview.html">H.10.7. Element and attribute overview</a></span></dt><dt><span class="section"><a href="sub-sect-ref-filter.html">H.10.8. References to other filters</a></span></dt><dt><span class="section"><a href="sub-sect-filter-rules.html">H.10.9. Filter rules</a></span></dt><dt><span class="section"><a href="sub-sect-supp-pros.html">H.10.10. Supported protocols</a></span></dt><dt><span class="section"><a href="sub-sect-adv-filt-topics.html">H.10.11. Advanced Filter Configuration Topics</a></span></dt><dt><span class="section"><a href="sub-sect-limitations-filters-network-subsystem.html">H.10.12. Limitations</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="appe-Virtualization-Addi
tional_resources.html">I. Additional resources</a></span></dt><dd><dl><dt><span class="section"><a href="appe-Virtualization-Additional_resources.html#sect-Virtualization-Additional_resources-Online_resources">I.1. Online resources</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Additional_resources-Installed_documentation.html">I.2. Installed documentation</a></span></dt></dl></dd><dt><span class="appendix"><a href="ch-lib-dom-xml.html">J. Manipulating the domain xml</a></span></dt><dd><dl><dt><span class="section"><a href="ch-lib-dom-xml.html#sect-gen-metadata">J.1. General information and metadata</a></span></dt><dt><span class="section"><a href="sect-dom-xml-op-sys-boot.html">J.2. Operating system booting</a></span></dt><dd><dl><dt><span class="section"><a href="sect-dom-xml-op-sys-boot.html#sub-sect-op-sys-boot-bios-boot">J.2.1. BIOS bootloader</a></span></dt><dt><span class="section"><a href="sub-sect-op-sys-host-boot.html">J.2.2. Host bootloader<
/a></span></dt><dt><span class="section"><a href="sub-sect-op-sys-dir-kern-boot.html">J.2.3. Direct kernel boot</a></span></dt><dt><span class="section"><a href="sub-sect-op-sys-cont-boot.html">J.2.4. Container boot</a></span></dt></dl></dd><dt><span class="section"><a href="sect-smbios-sys-info.html">J.3. SMBIOS system information</a></span></dt><dt><span class="section"><a href="sect-cpu-allocation.html">J.4. CPU allocation</a></span></dt><dt><span class="section"><a href="sect-cpu-tuning.html">J.5. CPU tuning</a></span></dt><dt><span class="section"><a href="sect-mem-back.html">J.6. Memory backing</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-mem-tuning.html">J.7. Memory tuning</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-numa-node-tuning.html">J.8. NUMA node tuning</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-blk-io-tuning.html">J.9. Block I/O tuning</a></span></dt><dt><span class="section"><a h
ref="sect-libvirt-dom-xml-res-part.html">J.10. Resource partitioning</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-cpu-model-top.html">J.11. CPU model and topology</a></span></dt><dd><dl><dt><span class="section"><a href="sect-libvirt-dom-xml-cpu-model-top.html#sub-sect-libvirt-dom-xml-res-part-guest-numa">J.11.1. Guest NUMA topology</a></span></dt></dl></dd><dt><span class="section"><a href="sect-libvirt-dom-xml-event-config.html">J.12. Events configuration</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-pwr-man.html">J.13. Power Management</a></span></dt><dt><span class="section"><a href="apjs14.html">J.14. Hypervisor features</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-time-keep.html">J.15. Time keeping</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-devices.html">J.16. Devices</a></span></dt><dd><dl><dt><span class="section"><a href="sect-libvirt-dom-xml-devices.html#sub-sec
t-libvirt-dom-xml-devices">J.16.1. Hard drives, floppy disks, CDROMs</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-filesystems.html">J.16.2. Filesystems</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-device-addresses.html">J.16.3. Device addresses</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-controllers.html">J.16.4. Controllers</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-device-leases.html">J.16.5. Device leases</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-host-device-assignment.html">J.16.6. Host device assignment</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-redirected-devices.html">J.16.7. Redirected devices</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-smartcard.html">J.16.8. Smartcard device
s</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html">J.16.9. Network interfaces</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-input-devices.html">J.16.10. Input devices</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-hub-devices.html">J.16.11. Hub devices</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-graphical-framebuffers.html">J.16.12. Graphical framebuffers</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-video.html">J.16.13. Video devices</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-consoles.html">J.16.14. Consoles, serial, parallel, and channel devices</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-guest-interface.html">J.16.15. Guest interfaces</a></span></dt><dt><span class="sec
tion"><a href="sub-section-libvirt-dom-xml-devices-channel.html">J.16.16. Channel</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-host-interface.html">J.16.17. Host interface</a></span></dt></dl></dd><dt><span class="section"><a href="section-libvirt-dom-xml-sound-devices.html">J.17. Sound devices</a></span></dt><dt><span class="section"><a href="section-libvirt-dom-xml-watchdog.html">J.18. Watchdog device</a></span></dt><dt><span class="section"><a href="section-libvirt-dom-xml-memory-baloon-device.html">J.19. Memory balloon device</a></span></dt><dt><span class="section"><a href="section-libvirt-dom-xml-random-number-gen.html">J.20. Random number generator device</a></span></dt><dt><span class="section"><a href="section-libvirt-dom-xml-tpm-device.html">J.21. TPM devices</a></span></dt><dt><span class="section"><a href="section-libvirt-dom-xml-security-label.html">J.22. Security label</a></span></dt><dt><span class="section"><a href="se
ction-libvirt-dom-xml-example.html">J.23. Example domain XML configuration</a></span></dt></dl></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch29s06.html"><strong>Prev</strong>29.6. Using vm-dump-metrics in Fedora guests to v...</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_Administration_Guide-Troubleshooting.html"><strong>Next</strong>Appendix A. Troubleshooting</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/qemu-ga.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/qemu-ga.html
new file mode 100644
index 0000000..a9b88c3
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/qemu-ga.html
@@ -0,0 +1,30 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 16. QEMU Guest Agent</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="ch15s02s02.html" title="15.2.2. Using a private libvirt network" /><link rel="next" href="pt02.html" title="Part II. Administration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s02s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="pt02.html"><
strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="qemu-ga" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 16. QEMU Guest Agent</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="qemu-ga.html#idp7949600">16.1. Set Up Communication between Guest Agent and Host</a></span></dt></dl></div><div class="para">
+ The QEMU Guest Agent allows the host machine to issue commands to the guest operating system. The guest operating system then responds to those commands asynchronously.
+ </div><div class="para">
+ This section covers the options and commands available to the guest agent in detail. It also covers how to run the guest agent in the foreground, or as a daemon in the background.
+ </div><div class="section" id="idp7949600"><div class="titlepage"><div><div><h2 class="title" id="idp7949600">16.1. Set Up Communication between Guest Agent and Host</h2></div></div></div><div class="para">
+ The host machine communicates with the guest agent through a VirtIO serial connection between the host and guest machines. A VirtIO serial channel is connected to the host via a character device driver (typically a Unix socket), and the guest listens on this serial channel. The following procedure shows how to set up the host and guest machines for guest agent use.
+ </div><div class="procedure"><h6>Procedure 16.1. Set Up Host-Agent Communication</h6><ol class="1"><li class="step"><p class="title"><strong>Launch QEMU with a character device driver</strong></p><div class="para">
+ Launch QEMU as usual, with additional definitions for the character device driver required to communicate with the guest agent.
+ </div><div class="para">
+ The following example launches QEMU to communicate over the Unix socket <code class="filename">/tmp/qga.sock</code>.
+ </div><pre class="screen">/usr/libexec/qemu-kvm [...] -chardev socket,path=/tmp/qga.sock,server,nowait,id=qga0 \
+ -device virtio-serial \
+ -device virtserialport,chardev=qga0,name=org.qemu.guest_agent.0</pre></li><li class="step"><p class="title"><strong>Start the Guest Agent</strong></p><div class="para">
+ On the guest, run the following command to start the Guest Agent:
+ </div><pre class="screen">qemu-ga --path <em class="replaceable"><code>device_path</code></em> --method <em class="replaceable"><code>method</code></em></pre><div class="para">
+ The guest agent now parses incoming QMP messages for commands, and acts upon them if valid.
+ </div><div class="para">
+ If no other method or path is specified with the <code class="option">--method</code> or <code class="option">--path</code> options respectively, the Guest Agent listens over <code class="literal">virtio-serial</code>, through the <code class="filename">/dev/virtio-ports/org.qemu.guest_agent.0</code> device path.
+ </div></li></ol></div><div class="para">
+ You can now communicate with the guest by sending valid QMP commands over the established character device driver.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s02s02.html"><strong>Prev</strong>15.2.2. Using a private libvirt 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="pt02.html"><strong>Next</strong>Part II. Administration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/run-virt-df.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/run-virt-df.html
new file mode 100644
index 0000000..0f48baf
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/run-virt-df.html
@@ -0,0 +1,44 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.7.2. Running virt-df</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-virt-df.html" title="G.7. virt-df: Monitoring disk usage" /><link rel="prev" href="sect-virt-df.html" title="G.7. virt-df: Monitoring disk usage" /><link rel="next" href="sect-virt-resize.html" title="G.8. virt-resize: resizing guests offline" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-virt-df.html"><strong>Prev</strong></a></li
><li class="next"><a accesskey="n" href="sect-virt-resize.html"><strong>Next</strong></a></li></ul><div class="section" id="run-virt-df"><div class="titlepage"><div><div><h3 class="title">G.7.2. Running virt-df</h3></div></div></div><div class="para">
+ To display file system usage for all file systems found in a disk image, enter the following:
+ </div><pre class="screen">
+# virt-df /dev/vg_guests/RHEL6
+ Filesystem 1K-blocks Used Available Use%
+ RHEL6:/dev/sda1 101086 10233 85634 11%
+ RHEL6:/dev/VolGroup00/LogVol00 7127864 2272744 4493036 32%
+</pre><div class="para">
+ (Where <code class="filename">/dev/vg_guests/RHEL6</code> is a Red Hat Enterprise Linux 4 guest disk image. The path in this case is the host logical volume where this disk image is located.)
+ </div><div class="para">
+ You can also use <code class="command">virt-df</code> on its own to list information about all of your guests (ie. those known to libvirt). The <code class="command">virt-df</code> command recognizes some of the same options as the standard <code class="command">df</code> such as <code class="command">-h</code> (human-readable) and <code class="command">-i</code> (show inodes instead of blocks).
+ </div><div class="para">
+ <code class="command">virt-df</code> also works on Windows guests:
+ </div><pre class="screen">
+# virt-df -h
+ Filesystem Size Used Available Use%
+ F14x64:/dev/sda1 484.2M 66.3M 392.9M 14%
+ F14x64:/dev/vg_f14x64/lv_root 7.4G 3.0G 4.4G 41%
+ RHEL6brewx64:/dev/sda1 484.2M 52.6M 406.6M 11%
+ RHEL6brewx64:/dev/vg_rhel6brewx64/lv_root
+ 13.3G 3.4G 9.2G 26%
+ Win7x32:/dev/sda1 100.0M 24.1M 75.9M 25%
+ Win7x32:/dev/sda2 19.9G 7.4G 12.5G 38%
+</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ You can use <code class="command">virt-df</code> safely on live guests, since it only needs read-only access. However, you should not expect the numbers to be precisely the same as those from a <code class="command">df</code> command running inside the guest. This is because what is on disk will be slightly out of synch with the state of the live guest. Nevertheless it should be a good enough approximation for analysis and monitoring purposes.
+ </div></div></div><div class="para">
+ virt-df is designed to allow you to integrate the statistics into monitoring tools, databases and so on. This allows system administrators to generate reports on trends in disk usage, and alerts if a guest is about to run out of disk space. To do this you should use the <code class="command">--csv</code> option to generate machine-readable Comma-Separated-Values (CSV) output. CSV output is readable by most databases, spreadsheet software and a variety of other tools and programming languages. The raw CSV looks like the following:
+ </div><pre class="screen">
+# virt-df --csv WindowsGuest
+ Virtual Machine,Filesystem,1K-blocks,Used,Available,Use%
+ Win7x32,/dev/sda1,102396,24712,77684,24.1%
+ Win7x32,/dev/sda2,20866940,7786652,13080288,37.3%
+</pre><div class="para">
+ For resources and ideas on how to process this output to produce trends and alerts, refer to the following URL: <a href=" http://virt-tools.org/learning/advanced-virt-df/"> http://virt-tools.org/learning/advanced-virt-df/</a>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-virt-df.html"><strong>Prev</strong>G.7. virt-df: Monitoring disk 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-virt-resize.html"><strong>Next</strong>G.8. virt-resize: resizing guests offline</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sec-known-issues-windows-xp-guests.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sec-known-issues-windows-xp-guests.html
new file mode 100644
index 0000000..1b66c89
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sec-known-issues-windows-xp-guests.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.10. Known Windows XP guest issues</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Troubleshooting.html" title="Appendix A. Troubleshooting" /><link rel="prev" href="sect-Virtualization-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard.html" title="A.9. Missing characters on guest console with Japanese keyboard" /><link rel="next" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Do
cumentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apb.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-known-issues-windows-xp-guests"><div class="titlepage"><div><div><h2 class="title">A.10. Known Windows XP guest issues</h2></div></div></div><div class="para">
+ If you perform device-add quickly followed by device-del using a Windows XP guest, the guest does not eject the device and instead it displays the following error: "The device (device name) cannot be stopped because of an unknown error. Since the device is still being used, do not remove it". It should be noted that newer Windows OS version guests as well as all known Linux guests do not experience this problem. To prevent this issue from happening, wait to delete a device that you just added.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard.html"><strong>Prev</strong>A.9. Missing characters on guest console with Jap...</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="apb.html"><strong>Next</strong>Appendix B. Common libvirt errors and troubleshoo...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Attaching_and_updating_a_device_with_virsh.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Attaching_and_updating_a_device_with_virsh.html
new file mode 100644
index 0000000..423887d
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Attaching_and_updating_a_device_with_virsh.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.2. Attaching and updating a device with virsh</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="prev" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="next" href="sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor.html" title="E.3. Connecting to the hypervisor" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/i
mages/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Attaching_and_updating_a_device_with_virsh"><div class="titlepage"><div><div><h2 class="title">E.2. Attaching and updating a device with virsh</h2></div></div></div><div class="para">
+ For information on this procedure refer to <a class="xref" href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html#sect-Virtualization-Adding_storage_devices_to_guests-Adding_file_based_storage_to_a_guest">Section 28.3.1, “Adding file based storage to a guest”</a>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html"><strong>Prev</strong>Appendix E. 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-Managing_guests_with_virsh-Connecting_to_the_hypervisor.html"><strong>Next</strong>E.3. Connecting to the hypervisor</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Augeas-and-libguestfs-scripting.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Augeas-and-libguestfs-scripting.html
new file mode 100644
index 0000000..634db18
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Augeas-and-libguestfs-scripting.html
@@ -0,0 +1,53 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.4.5. Augeas and libguestfs scripting</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-the_guestfish_shell.html" title="G.4. The guestfish shell" /><link rel="prev" href="sect-Shell-scripting-with-guestfish.html" title="G.4.4. Shell scripting with guestfish" /><link rel="next" href="sect-other-commands.html" title="G.5. Other commands" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Shell-scripting-with-guestfish.html"
><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-other-commands.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Augeas-and-libguestfs-scripting"><div class="titlepage"><div><div><h3 class="title">G.4.5. Augeas and libguestfs scripting</h3></div></div></div><div class="para">
+ Combining libguestfs with Augeas can help when writing scripts to manipulate Linux guest configuration. For example, the following script uses Augeas to parse the keyboard configuration of a guest, and to print out the layout. Note that this example only works with guests running Red Hat Enterprise Linux:
+ </div><pre class="screen">
+#!/bin/bash -
+ set -e
+ guestname="$1"
+
+ guestfish -d "$1" -i --ro <<'EOF'
+ aug-init / 0
+ aug-get /files/etc/sysconfig/keyboard/LAYOUT
+ EOF
+</pre><div class="para">
+ Augeas can also be used to modify configuration files. You can modify the above script to <span class="bold bold"><strong>change</strong></span> the keyboard layout:
+ </div><pre class="screen">
+#!/bin/bash -
+ set -e
+ guestname="$1"
+
+ guestfish -d "$1" -i <<'EOF'
+ aug-init / 0
+ aug-set /files/etc/sysconfig/keyboard/LAYOUT '"gb"'
+ aug-save
+ EOF
+</pre><div class="para">
+ Note the three changes between the two scripts:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ The <code class="command">--ro</code> option has been removed in the second example, giving the ability to write to the guest.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="command">aug-get</code> command has been changed to <code class="command">aug-set</code> to modify the value instead of fetching it. The new value will be <code class="command">"gb"</code> (including the quotes).
+ </div></li><li class="listitem"><div class="para">
+ The <code class="command">aug-save</code> command is used here so Augeas will write the changes out to disk.
+ </div></li></ol></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ More information about Augeas can be found on the website <a href="http://augeas.net">http://augeas.net</a>.
+ </div></div></div><div class="para">
+ guestfish can do much more than we can cover in this introductory document. For example, creating disk images from scratch:
+ </div><pre class="screen">
+guestfish -N fs
+</pre><div class="para">
+ Or copying out whole directories from a disk image:
+ </div><pre class="screen">
+><fs> copy-out /home /tmp/home
+</pre><div class="para">
+ For more information see the man page guestfish(1).
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Shell-scripting-with-guestfish.html"><strong>Prev</strong>G.4.4. Shell scripting with guestfish</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-other-commands.html"><strong>Next</strong>G.5. Other commands</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Guide-Guest_Disks_libguestfs-installation.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Guide-Guest_Disks_libguestfs-installation.html
new file mode 100644
index 0000000..bbb00b3
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Guide-Guest_Disks_libguestfs-installation.html
@@ -0,0 +1,18 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.3. Installation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /><link rel="prev" href="sect-Terminology-Guest_Disks_libguestfs.html" title="G.2. Terminology" /><link rel="next" href="sect-the_guestfish_shell.html" title="G.4. The guestfish shell" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a acce
sskey="p" href="sect-Terminology-Guest_Disks_libguestfs.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-the_guestfish_shell.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Guide-Guest_Disks_libguestfs-installation"><div class="titlepage"><div><div><h2 class="title">G.3. Installation</h2></div></div></div><div class="para">
+ To install libguestfs, guestfish, the libguestfs tools, guestmount and support for Windows guests, subscribe to the RHEL V2WIN channel, go to the <a href="https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=631818">Fedora Website</a> and run the following command:
+ </div><pre class="screen">
+# yum install libguestfs guestfish libguestfs-tools libguestfs-mount libguestfs-winsupport
+</pre><div class="para">
+ To install every libguestfs-related package including the language bindings, run the following command:
+ </div><pre class="screen">
+# yum install '*guestf*'
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Terminology-Guest_Disks_libguestfs.html"><strong>Prev</strong>G.2. Terminology</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-the_guestfish_shell.html"><strong>Next</strong>G.4. The guestfish shell</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Managing_storage_controllers_in_a_guest.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Managing_storage_controllers_in_a_guest.html
new file mode 100644
index 0000000..5c7a983
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Managing_storage_controllers_in_a_guest.html
@@ -0,0 +1,42 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>28.3.3. Managing storage controllers in a guest</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html" title="28.3. Adding storage devices to guests" /><link rel="prev" href="sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html" title="28.3.2. Adding hard drives and other block devices to a guest" /><link rel="next" href="sect-Virtualization-Storage_Volumes-Deleting_volumes.html" title="28.4. Deleting and removing volumes" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="
http://docs.redhat.com"><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-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Storage_Volumes-Deleting_volumes.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Managing_storage_controllers_in_a_guest"><div class="titlepage"><div><div><h3 class="title">28.3.3. Managing storage controllers in a guest</h3></div></div></div><div class="para">
+ Starting from Red Hat Enterprise Linux 6.3, SCSI devices are also supported inside guests.
+ </div><div class="para">
+ Unlike virtio disks, SCSI devices require the presence of a controller in the guest.
+ </div><div class="para">
+ This section details the necessary steps to create a virtual SCSI controller (also known as "Host Bus Adapter", or HBA), and to add SCSI storage to the guest.
+ </div><div class="procedure" id="proc-Creating_a_virtual_SCSI_controller"><h6>Procedure 28.3. Creating a virtual SCSI controller</h6><ol class="1"><li class="step"><div class="para">
+ Display the configuration of the guest (<code class="literal">Guest1</code>) and look for a pre-existing SCSI controller:
+ </div><pre class="screen">
+# virsh dumpxml Guest1 | grep controller.*scsi
+</pre><div class="para">
+ If a controller is present, the command will output one or more lines similar to the following:
+ </div><pre class="screen">
+<controller type='scsi' model='virtio-scsi' index='0'/>
+</pre></li><li class="step"><div class="para">
+ If the previous step did not show a controller, create the description for one in a new file and add it to the virtual machine, using the following steps:
+ </div><ol class="a"><li class="step"><div class="para">
+ Create the controller by writing a <code class="literal"><controller></code> element in a new file and save this file with an XML extension. <code class="filename">NewHBA.xml</code>, for example.
+ </div><pre class="screen">
+<controller type='scsi' model='virtio-scsi'/>
+</pre></li><li class="step"><div class="para">
+ Associate the device in the <code class="filename">NewHBA.xml</code> you just created with your guest:
+ </div><pre class="screen">
+# virsh attach-device --config Guest1 ~/NewHBA.xml
+</pre><div class="para">
+ In this example the <code class="literal">--config</code> option behaves the same as it does for disks. Refer to <a class="xref" href="sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html#proc-Virtualization-Adding_storage_devices_to_guests-Adding_physical_block_devices_to_virtualized_guests">Procedure 28.2, “Adding physical block devices to guests”</a> for more information.
+ </div></li></ol></li><li class="step"><div class="para">
+ Add a new SCSI disk or CD-ROM. The new disk can be added using the methods in sections <a class="xref" href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html#sect-Virtualization-Adding_storage_devices_to_guests-Adding_file_based_storage_to_a_guest">Section 28.3.1, “Adding file based storage to a guest”</a> and <a class="xref" href="sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html">Section 28.3.2, “Adding hard drives and other block devices to a guest”</a>. In order to create a SCSI disk, specify a target device name that starts with <em class="replaceable"><code>sd</code></em>.
+ </div><pre class="screen">
+# virsh attach-disk Guest1 /var/lib/libvirt/images/FileName.iso sdb --cache none
+</pre><div class="para">
+ Depending on the version of the driver in the guest, the new disk may not be detected immediately by a running guest. Follow the steps in the <em class="citetitle">Red Hat Enterprise Linux Storage Administration Guide</em>.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html"><strong>Prev</strong>28.3.2. Adding hard drives and other block device...</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-Storage_Volumes-Deleting_volumes.html"><strong>Next</strong>28.4. Deleting and removing volumes</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Modifying-files-with-guestfish.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Modifying-files-with-guestfish.html
new file mode 100644
index 0000000..87d4ae0
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Modifying-files-with-guestfish.html
@@ -0,0 +1,29 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.4.2. Modifying files with guestfish</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-the_guestfish_shell.html" title="G.4. The guestfish shell" /><link rel="prev" href="sect-the_guestfish_shell.html" title="G.4. The guestfish shell" /><link rel="next" href="sect-Other-actions-with-guestfish.html" title="G.4.3. Other actions with guestfish" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-the_guestfish_shell.html"><str
ong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Other-actions-with-guestfish.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Modifying-files-with-guestfish"><div class="titlepage"><div><div><h3 class="title">G.4.2. Modifying files with guestfish</h3></div></div></div><div class="para">
+ To modify files, create directories or make other changes to a guest, first heed the warning at the beginning of this section: <span class="bol bol">your guest must be shut down</span>. Editing or changing a running disk with guestfish <span class="bold bold"><strong>will</strong></span> result in disk corruption. This section gives an example of editing the <code class="filename">/boot/grub/grub.conf</code> file. When you are sure the guest is shut down you can omit the <code class="command">--ro</code> flag in order to get write access via a command such as:
+ </div><pre class="screen">
+guestfish -d RHEL3 -i
+
+Welcome to guestfish, the libguestfs filesystem interactive shell for
+ editing virtual machine filesystems.
+
+ Type: 'help' for help on commands
+ 'man' to read the manual
+ 'quit' to quit the shell
+
+ Operating system: Red Hat Enterprise Linux AS release 3 (Taroon Update 9)
+ /dev/vda2 mounted on /
+ /dev/vda1 mounted on /boot
+
+><fs> edit /boot/grub/grub.conf
+</pre><div class="para">
+ Commands to edit files include <code class="command">edit</code>, <code class="command">vi</code> and <code class="command">emacs</code>. Many commands also exist for creating files and directories, such as <code class="command">write</code>, <code class="command">mkdir</code>, <code class="command">upload</code> and <code class="command">tar-in</code>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-the_guestfish_shell.html"><strong>Prev</strong>G.4. The guestfish shell</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-Other-actions-with-guestfish.html"><strong>Next</strong>G.4.3. Other actions with guestfish</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Network_Address_Translation-libvirt.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Network_Address_Translation-libvirt.html
new file mode 100644
index 0000000..987b814
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Network_Address_Translation-libvirt.html
@@ -0,0 +1,14 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.2. Network Address Translation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html" title="Appendix H. Virtual Networking" /><link rel="prev" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html" title="Appendix H. Virtual Networking" /><link rel="next" href="sect-network-protocols.html" title="H.3. Networking protocols" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previ
ous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-network-protocols.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Network_Address_Translation-libvirt"><div class="titlepage"><div><div><h2 class="title">H.2. Network Address Translation</h2></div></div></div><div class="para">
+ By default, virtual network switches operate in NAT mode. They use IP masquerading rather than SNAT (Source-NAT) or DNAT (Destination-NAT). IP masquerading enables connected guests to use the host IP address for communication to any external network. By default, computers that are placed externally to the host cannot communicate to the guests inside when the virtual network switch is operating in NAT mode, as shown in the following diagram:
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-Network_Address_Translation-Switch_in_NAT_mode_with_two_guests"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-04-hostwithnatswitch.png" width="444" alt="Virtual network switch using NAT with two guests" /></div></div><h6>Figure H.3. Virtual network switch using NAT with two guests</h6></div><br class="figure-break" /><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Virtual network switches use NAT configured by iptables rules. Editing these rules while the switch is running is not recommended, as incorrect rules may result in the switch being unable to communicate.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html"><strong>Prev</strong>Appendix H. Virtual 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="sect-network-protocols.html"><strong>Next</strong>H.3. Networking protocols</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Other-actions-with-guestfish.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Other-actions-with-guestfish.html
new file mode 100644
index 0000000..99216b6
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Other-actions-with-guestfish.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.4.3. Other actions with guestfish</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-the_guestfish_shell.html" title="G.4. The guestfish shell" /><link rel="prev" href="sect-Modifying-files-with-guestfish.html" title="G.4.2. Modifying files with guestfish" /><link rel="next" href="sect-Shell-scripting-with-guestfish.html" title="G.4.4. Shell scripting with guestfish" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Mo
difying-files-with-guestfish.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Shell-scripting-with-guestfish.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Other-actions-with-guestfish"><div class="titlepage"><div><div><h3 class="title">G.4.3. Other actions with guestfish</h3></div></div></div><div class="para">
+ You can also format file systems, create partitions, create and resize LVM logical volumes and much more, with commands such as <code class="command">mkfs</code>, <code class="command">part-add</code>, <code class="command">lvresize</code>, <code class="command">lvcreate</code>, <code class="command">vgcreate</code> and <code class="command">pvcreate</code>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Modifying-files-with-guestfish.html"><strong>Prev</strong>G.4.2. Modifying files with guestfish</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-Shell-scripting-with-guestfish.html"><strong>Next</strong>G.4.4. Shell scripting with guestfish</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-RedHat-We_Need_Feedback.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-RedHat-We_Need_Feedback.html
new file mode 100644
index 0000000..9d49e18
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-RedHat-We_Need_Feedback.html
@@ -0,0 +1,16 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2. We Need Feedback!</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect_RedHat-Getting_Help_and_Giving_Feedback.html" title="2. Getting Help and Giving Feedback" /><link rel="prev" href="sect_RedHat-Getting_Help_and_Giving_Feedback.html" title="2. Getting Help and Giving Feedback" /><link rel="next" href="pt01.html" title="Part I. Deployment" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect_RedHat-Gettin
g_Help_and_Giving_Feedback.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="pt01.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-RedHat-We_Need_Feedback"><div class="titlepage"><div><div><h3 class="title">2.2. We Need Feedback!</h3></div></div></div><a id="idp19149408" class="indexterm"></a><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/">http://bugzilla.redhat.com/</a> against the product <span class="application"><strong>Documentation.</strong></span>
+ </div><div class="para">
+ When submitting a bug report, be sure to mention the manual's identifier: <em class="citetitle">doc-Virtualization_Deployment_and_Administration_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="sect_RedHat-Getting_Help_and_Giving_Feedback.html"><strong>Prev</strong>2. Getting Help and Giving 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="pt01.html"><strong>Next</strong>Part I. Deployment</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Shell-scripting-with-guestfish.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Shell-scripting-with-guestfish.html
new file mode 100644
index 0000000..5d52436
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Shell-scripting-with-guestfish.html
@@ -0,0 +1,21 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.4.4. Shell scripting with guestfish</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-the_guestfish_shell.html" title="G.4. The guestfish shell" /><link rel="prev" href="sect-Other-actions-with-guestfish.html" title="G.4.3. Other actions with guestfish" /><link rel="next" href="sect-Augeas-and-libguestfs-scripting.html" title="G.4.5. Augeas and libguestfs scripting" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Othe
r-actions-with-guestfish.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Augeas-and-libguestfs-scripting.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Shell-scripting-with-guestfish"><div class="titlepage"><div><div><h3 class="title">G.4.4. Shell scripting with guestfish</h3></div></div></div><div class="para">
+ Once you are familiar with using guestfish interactively, according to your needs, writing shell scripts with it may be useful. The following is a simple shell script to add a new MOTD (message of the day) to a guest:
+ </div><pre class="screen">
+#!/bin/bash -
+ set -e
+ guestname="$1"
+
+ guestfish -d "$guestname" -i <<'EOF'
+ write /etc/motd "Welcome to Acme Incorporated."
+ chmod 0644 /etc/motd
+ EOF
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Other-actions-with-guestfish.html"><strong>Prev</strong>G.4.3. Other actions with guestfish</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-Augeas-and-libguestfs-scripting.html"><strong>Next</strong>G.4.5. Augeas and libguestfs scripting</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Terminology-Guest_Disks_libguestfs.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Terminology-Guest_Disks_libguestfs.html
new file mode 100644
index 0000000..1598722
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Terminology-Guest_Disks_libguestfs.html
@@ -0,0 +1,22 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.2. Terminology</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /><link rel="prev" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /><link rel="next" href="sect-Guide-Guest_Disks_libguestfs-installation.html" title="G.3. Installation" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Docum
entation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Guide-Guest_Disks_libguestfs-installation.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Terminology-Guest_Disks_libguestfs"><div class="titlepage"><div><div><h2 class="title">G.2. Terminology</h2></div></div></div><div class="para">
+ This section explains the terms used throughout this chapter.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>libguestfs (GUEST FileSystem LIBrary)</strong></span> - the underlying C library that provides the basic functionality for opening disk images, reading and writing files and so on. You can write C programs directly to this API, but it is quite low level.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>guestfish (GUEST Filesystem Interactive SHell)</strong></span> is an interactive shell that you can use from the command line or from shell scripts. It exposes all of the functionality of the libguestfs API.
+ </div></li><li class="listitem"><div class="para">
+ Various virt tools are built on top of libguestfs, and these provide a way to perform specific single tasks from the command line. Tools include <span class="bold bold"><strong>virt-df</strong></span>, <span class="bold bold"><strong>virt-rescue</strong></span>, <span class="bold bold"><strong>virt-resize</strong></span> and <span class="bold bold"><strong>virt-edit</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>hivex</strong></span> and <span class="bold bold"><strong>Augeas</strong></span> are libraries for editing the Windows Registry and Linux configuration files respectively. Although these are separate from libguestfs, much of the value of libguestfs comes from the combination of these tools.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>guestmount</strong></span> is an interface between libguestfs and FUSE. It is primarily used to mount file systems from disk images on your host. This functionality is not necessary, but can be useful.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html"><strong>Prev</strong>Appendix G. Guest disk access with offline 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="sect-Guide-Guest_Disks_libguestfs-installation.html"><strong>Next</strong>G.3. Installation</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Using-API-Programming-Languages.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Using-API-Programming-Languages.html
new file mode 100644
index 0000000..efb41c7
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Using-API-Programming-Languages.html
@@ -0,0 +1,243 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.11. Using the API from Programming Languages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /><link rel="prev" href="sect-virt-win-reg-use.html" title="G.10.3. Using virt-win-reg" /><link rel="next" href="sect-libguestfs-troubleshoot.html" title="G.12. Troubleshooting" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="
p" href="sect-virt-win-reg-use.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-libguestfs-troubleshoot.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Using-API-Programming-Languages"><div class="titlepage"><div><div><h2 class="title">G.11. Using the API from Programming Languages</h2></div></div></div><div class="para">
+ The libguestfs API can be used directly from the following languages in Fedora 19: C, C++, Perl, Python, Java, Ruby and OCaml.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ To install C and C++ bindings, enter the following command:
+ </div><pre class="screen">
+# yum install libguestfs-devel
+</pre></li><li class="listitem"><div class="para">
+ To install Perl bindings:
+ </div><pre class="screen">
+# yum install 'perl(Sys::Guestfs)'
+</pre></li><li class="listitem"><div class="para">
+ To install Python bindings:
+ </div><pre class="screen">
+# yum install python-libguestfs
+</pre></li><li class="listitem"><div class="para">
+ To install Java bindings:
+ </div><pre class="screen">
+# yum install libguestfs-java libguestfs-java-devel libguestfs-javadoc
+</pre></li><li class="listitem"><div class="para">
+ To install Ruby bindings:
+ </div><pre class="screen">
+# yum install ruby-libguestfs
+</pre></li><li class="listitem"><div class="para">
+ To install OCaml bindings:
+ </div><pre class="screen">
+# yum install ocaml-libguestfs ocaml-libguestfs-devel
+</pre></li></ul></div><div class="para">
+ The binding for each language is essentially the same, but with minor syntactic changes. A C statement:
+ </div><pre class="screen">
+guestfs_launch (g);
+</pre><div class="para">
+ Would appear like the following in Perl:
+ </div><pre class="screen">
+$g->launch ()
+</pre><div class="para">
+ Or like the following in OCaml:
+ </div><pre class="screen">
+g#launch ()
+</pre><div class="para">
+ Only the API from C is detailed in this section.
+ </div><div class="para">
+ In the C and C++ bindings, you must manually check for errors. In the other bindings, errors are converted into exceptions; the additional error checks shown in the examples below are not necessary for other languages, but conversely you may wish to add code to catch exceptions. Refer to the following list for some points of interest regarding the architecture of the libguestfs API:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The libguestfs API is synchronous. Each call blocks until it has completed. If you want to make calls asynchronously, you have to create a thread.
+ </div></li><li class="listitem"><div class="para">
+ The libguestfs API is not thread safe: each handle should be used only from a single thread, or if you want to share a handle between threads you should implement your own mutex to ensure that two threads cannot execute commands on one handle at the same time.
+ </div></li><li class="listitem"><div class="para">
+ You should not open multiple handles on the same disk image. It is permissible if all the handles are read-only, but still not recommended.
+ </div></li><li class="listitem"><div class="para">
+ You should not add a disk image for writing if anything else could be using that disk image (eg. a live VM). Doing this will cause disk corruption.
+ </div></li><li class="listitem"><div class="para">
+ Opening a read-only handle on a disk image which is currently in use (eg. by a live VM) is possible; however, the results may be unpredictable or inconsistent particularly if the disk image is being heavily written to at the time you are reading it.
+ </div></li></ul></div><div class="section" id="API-and-C"><div class="titlepage"><div><div><h3 class="title">G.11.1. Interaction with the API via a C program</h3></div></div></div><div class="para">
+ Your C program should start by including the <guestfs.h> header file, and creating a handle:
+ </div><pre class="screen">
+#include <stdio.h>
+#include <stdlib.h>
+#include <guestfs.h>
+
+int
+main (int argc, char *argv[])
+{
+ guestfs_h *g;
+
+ g = guestfs_create ();
+ if (g == NULL) {
+ perror ("failed to create libguestfs handle");
+ exit (EXIT_FAILURE);
+ }
+
+ /* ... */
+
+ guestfs_close (g);
+
+ exit (EXIT_SUCCESS);
+ }
+</pre><div class="para">
+ Save this program to a file (<code class="filename">test.c</code>). Compile this program and run it with the following two commands:
+ </div><pre class="screen">
+gcc -Wall test.c -o test -lguestfs
+./test
+</pre><div class="para">
+ At this stage it should print no output. The rest of this section demonstrates an example showing how to extend this program to create a new disk image, partition it, format it with an ext4 file system, and create some files in the file system. The disk image will be called <code class="filename">disk.img</code> and be created in the current directory.
+ </div><div class="para">
+ The outline of the program is:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Create the handle.
+ </div></li><li class="listitem"><div class="para">
+ Add disk(s) to the handle.
+ </div></li><li class="listitem"><div class="para">
+ Launch the libguestfs back end.
+ </div></li><li class="listitem"><div class="para">
+ Create the partition, file system and files.
+ </div></li><li class="listitem"><div class="para">
+ Close the handle and exit.
+ </div></li></ul></div><div class="para">
+ Here is the modified program:
+ </div><pre class="screen">
+#include <stdio.h>
+#include <stdlib.h>
+#include <string.h>
+#include <fcntl.h>
+#include <unistd.h>
+#include <guestfs.h>
+
+ int
+ main (int argc, char *argv[])
+ {
+ guestfs_h *g;
+ size_t i;
+
+ g = guestfs_create ();
+ if (g == NULL) {
+ perror ("failed to create libguestfs handle");
+ exit (EXIT_FAILURE);
+ }
+
+ /* Create a raw-format sparse disk image, 512 MB in size. */
+ int fd = open ("disk.img", O_CREAT|O_WRONLY|O_TRUNC|O_NOCTTY, 0666);
+ if (fd == -1) {
+ perror ("disk.img");
+ exit (EXIT_FAILURE);
+ }
+ if (ftruncate (fd, 512 * 1024 * 1024) == -1) {
+ perror ("disk.img: truncate");
+ exit (EXIT_FAILURE);
+ }
+ if (close (fd) == -1) {
+ perror ("disk.img: close");
+ exit (EXIT_FAILURE);
+ }
+
+ /* Set the trace flag so that we can see each libguestfs call. */
+ guestfs_set_trace (g, 1);
+
+ /* Set the autosync flag so that the disk will be synchronized
+ * automatically when the libguestfs handle is closed.
+ */
+ guestfs_set_autosync (g, 1);
+
+ /* Add the disk image to libguestfs. */
+ if (guestfs_add_drive_opts (g, "disk.img",
+ GUESTFS_ADD_DRIVE_OPTS_FORMAT, "raw", /* raw format */
+ GUESTFS_ADD_DRIVE_OPTS_READONLY, 0, /* for write */
+ -1 /* this marks end of optional arguments */ )
+ == -1)
+ exit (EXIT_FAILURE);
+
+ /* Run the libguestfs back-end. */
+ if (guestfs_launch (g) == -1)
+ exit (EXIT_FAILURE);
+
+ /* Get the list of devices. Because we only added one drive
+ * above, we expect that this list should contain a single
+ * element.
+ */
+ char **devices = guestfs_list_devices (g);
+ if (devices == NULL)
+ exit (EXIT_FAILURE);
+ if (devices[0] == NULL || devices[1] != NULL) {
+ fprintf (stderr,
+ "error: expected a single device from list-devices\n");
+ exit (EXIT_FAILURE);
+ }
+
+ /* Partition the disk as one single MBR partition. */
+ if (guestfs_part_disk (g, devices[0], "mbr") == -1)
+ exit (EXIT_FAILURE);
+
+ /* Get the list of partitions. We expect a single element, which
+ * is the partition we have just created.
+ */
+ char **partitions = guestfs_list_partitions (g);
+ if (partitions == NULL)
+ exit (EXIT_FAILURE);
+ if (partitions[0] == NULL || partitions[1] != NULL) {
+ fprintf (stderr,
+ "error: expected a single partition from list-partitions\n");
+ exit (EXIT_FAILURE);
+ }
+
+ /* Create an ext4 filesystem on the partition. */
+ if (guestfs_mkfs (g, "ext4", partitions[0]) == -1)
+ exit (EXIT_FAILURE);
+
+ /* Now mount the filesystem so that we can add files. */
+ if (guestfs_mount_options (g, "", partitions[0], "/") == -1)
+ exit (EXIT_FAILURE);
+
+ /* Create some files and directories. */
+ if (guestfs_touch (g, "/empty") == -1)
+ exit (EXIT_FAILURE);
+
+ const char *message = "Hello, world\n";
+ if (guestfs_write (g, "/hello", message, strlen (message)) == -1)
+ exit (EXIT_FAILURE);
+
+ if (guestfs_mkdir (g, "/foo") == -1)
+ exit (EXIT_FAILURE);
+
+ /* This uploads the local file /etc/resolv.conf into the disk image. */
+ if (guestfs_upload (g, "/etc/resolv.conf", "/foo/resolv.conf") == -1)
+ exit (EXIT_FAILURE);
+
+ /* Because 'autosync' was set (above) we can just close the handle
+ * and the disk contents will be synchronized. You can also do
+ * this manually by calling guestfs_umount_all and guestfs_sync.
+ */
+ guestfs_close (g);
+
+ /* Free up the lists. */
+ for (i = 0; devices[i] != NULL; ++i)
+ free (devices[i]);
+ free (devices);
+ for (i = 0; partitions[i] != NULL; ++i)
+ free (partitions[i]);
+ free (partitions);
+
+ exit (EXIT_SUCCESS);
+ }
+</pre><div class="para">
+ Compile and run this program with the following two commands:
+ </div><pre class="screen">
+gcc -Wall test.c -o test -lguestfs
+./test
+</pre><div class="para">
+ If the program runs to completion successfully then you should be left with a disk image called <code class="filename">disk.img</code>, which you can examine with guestfish:
+ </div><pre class="screen">
+guestfish --ro -a disk.img -m /dev/sda1
+><fs> ll /
+><fs> cat /foo/resolv.conf
+</pre><div class="para">
+ By default (for C and C++ bindings only), libguestfs prints errors to stderr. You can change this behavior by setting an error handler. The guestfs(3) man page discusses this in detail.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-virt-win-reg-use.html"><strong>Prev</strong>G.10.3. Using virt-win-reg</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-libguestfs-troubleshoot.html"><strong>Next</strong>G.12. Troubleshooting</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html
new file mode 100644
index 0000000..0ce3a57
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html
@@ -0,0 +1,45 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>28.3.2. Adding hard drives and other block devices to a guest</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html" title="28.3. Adding storage devices to guests" /><link rel="prev" href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html" title="28.3. Adding storage devices to guests" /><link rel="next" href="sect-Managing_storage_controllers_in_a_guest.html" title="28.3.3. Managing storage controllers in a guest" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-Virtualized_block_devices-Adding_storage_devices_to_guests.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Managing_storage_controllers_in_a_guest.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest"><div class="titlepage"><div><div><h3 class="title">28.3.2. Adding hard drives and other block devices to a guest</h3></div></div></div><div class="para">
+ System administrators use additional hard drives to provide increased storage space for a guest, or to separate system data from user data.
+ </div><div class="procedure" id="proc-Virtualization-Adding_storage_devices_to_guests-Adding_physical_block_devices_to_virtualized_guests"><h6>Procedure 28.2. Adding physical block devices to guests</h6><ol class="1"><li class="step"><div class="para">
+ This procedure describes how to add a hard drive on the host to a guest. It applies to all physical block devices, including CD-ROM, DVD and floppy devices.
+ </div><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 class="step"><div class="para">
+ Do one of the following:
+ </div><ol class="a"><li class="step"><div class="para">
+ Create the additional storage by writing a <code class="command">disk</code> element in a new file. In this example, this file will be known as <code class="filename">NewStorage.xml</code>. The following example is a configuration file section which contains an additional device-based storage container for the host partition <code class="filename">/dev/sr0:</code>
+ </div><pre class="screen">
+<disk type='block' device='disk'>
+ <driver name='qemu' type='raw' cache='none'/>
+ <source dev='/dev/sr0'/>
+ <target dev='vdc' bus='virtio'/>
+</disk>
+</pre></li><li class="step"><div class="para">
+ Follow the instruction in the previous section to attach the device to the guest. Alternatively, you can use the <em class="parameter"><code>virsh attach-disk</code></em> command, as shown:
+ </div><pre class="screen">
+# virsh attach-disk Guest1 /dev/sr0 vdc
+</pre><div class="para">
+ Note that the following options are available:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The<code class="command">virsh attach-disk</code> command also accepts the <em class="parameter"><code>--config</code></em>, <em class="parameter"><code>--type</code></em>, and <em class="parameter"><code>--mode</code></em> options, as shown:
+ </div><pre class="screen">
+# <code class="command">virsh attach-disk Guest1 /dev/sr0 vdc --config --type cdrom --mode readonly</code></pre></li><li class="listitem"><div class="para">
+ Additionally, <em class="parameter"><code> --type</code></em> also accepts <em class="parameter"><code>--type disk</code></em> in cases where the device is a hard drive.
+ </div></li></ul></div></li></ol></li><li class="step"><div class="para">
+ The guest now has a new hard disk device called <code class="filename">/dev/vdc</code> on Linux (or something similar, depending on what the guest OS chooses) or <code class="filename">D: drive</code> (for example) on Windows. You can now initialize the disk from the guest, following the standard procedures for the guest's operating system. Refer to <a class="xref" href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html#proc-Virtualization-Adding_storage_devices">Procedure 28.1, “Adding file-based storage”</a> and <a class="xref" href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html#step-partition_disk">Step 6</a> for an example.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ The host should not use filesystem labels to identify file systems in the <code class="filename">fstab</code> file, the <code class="filename">initrd</code> file or on the kernel command line. Doing so presents a security risk if less privileged users, such as guests, have write access to whole partitions or LVM volumes, because a guest could potentially write a filesystem label belonging to the host, to its own block device storage. Upon reboot of the host, the host could then mistakenly use the guest's disk as a system disk, which would compromise the host system.
+ </div><div class="para">
+ It is preferable to use the UUID of a device to identify it in the <code class="filename">fstab</code> file, the <code class="filename">initrd</code> file or on the kernel command line. While using UUIDs is still not completely secure on certain file systems, a similar compromise with UUID is significantly less feasible.
+ </div></div></div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Guests should not be given write access to whole disks or block devices (for example, <code class="filename">/dev/sdb</code>). Guests with access to whole block devices may be able to modify volume labels, which can be used to compromise the host system. Use partitions (for example, <code class="filename">/dev/sdb1</code>) or LVM volumes to prevent this issue.
+ </div></div></div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html"><strong>Prev</strong>28.3. 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-Managing_storage_controllers_in_a_guest.html"><strong>Next</strong>28.3.3. Managing storage controllers in a guest</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Additional_resources-Installed_documentation.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Additional_resources-Installed_documentation.html
new file mode 100644
index 0000000..41b318e
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Additional_resources-Installed_documentation.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>I.2. Installed documentation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="appe-Virtualization-Additional_resources.html" title="Appendix I. Additional resources" /><link rel="prev" href="appe-Virtualization-Additional_resources.html" title="Appendix I. Additional resources" /><link rel="next" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-Additional_resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-lib-dom-xml.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Additional_resources-Installed_documentation"><div class="titlepage"><div><div><h2 class="title">I.2. Installed documentation</h2></div></div></div><a id="idm8778736" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><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 class="listitem"><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 class="listitem"><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 class="listitem"><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 distributions inside of virtual machines.
+ </div></li><li class="listitem"><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-Additional_resources.html"><strong>Prev</strong>Appendix I. 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="ch-lib-dom-xml.html"><strong>Next</strong>Appendix J. Manipulating the domain xml</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html
new file mode 100644
index 0000000..aa40a8c
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html
@@ -0,0 +1,120 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.4. Live KVM migration with virsh</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-KVM_live_migration.html" title="Chapter 20. KVM live migration" /><link rel="prev" href="shared-storage-nfs-migration.html" title="20.3. Shared storage example: NFS for a simple migration" /><link rel="next" href="virsh-migration-arguements.html" title="20.4.2. Additional options for the virsh migrate command" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul cl
ass="docnav"><li class="previous"><a accesskey="p" href="shared-storage-nfs-migration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="virsh-migration-arguements.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh"><div class="titlepage"><div><div><h2 class="title">20.4. 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">
+ Note that the <em class="replaceable"><code>--live</code></em> option may be eliminated when live migration is not desired. Additional options are listed in <a class="xref" href="virsh-migration-arguements.html">Section 20.4.2, “Additional options for the virsh migrate command”</a>.
+ </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 connection URL of the destination host. 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="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The <em class="parameter"><code>DestinationURL</code></em> parameter for normal migration and peer2peer migration has different semantics:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ normal migration: the <em class="parameter"><code>DestinationURL</code></em> is the URL of the target host as seen from the source guest.
+ </div></li><li class="listitem"><div class="para">
+ peer2peer migration: <em class="parameter"><code>DestinationURL</code></em> is the URL of the target host as seen from the source host.
+ </div></li></ul></div></div></div><div class="para">
+ Once the command is entered, you will be prompted for the root password of the destination system.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ An entry for the destination host, in the <code class="filename">/etc/hosts</code> file on the source server is required for migration to succeed. Enter the IP address and hostname for the destination host in this file as shown in the following example, substituting your destination host's IP address and hostname:
+<pre class="screen">
+10.0.0.20 host2.example.com
+</pre>
+ </div></div></div><div class="formalpara" id="form-Virtualization-Live_KVM_migration_with_virsh-Example_live_migration_with_virsh"><h5 class="formalpara">Example: live migration with virsh</h5>
+ This example migrates from <code class="systemitem">host1.example.com</code> to <code class="systemitem">host2.example.com</code>. Change the host names for your environment. This example migrates a virtual machine named <code class="filename">guest1-F19</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_Administration_Guide-KVM_live_migration.html#item-Virtualization-Live_migration_requirements-Migration_requirements">Migration requirements</a>).
+ </div><div class="procedure"><ol class="1"><li class="step" id="step-Virtualization_Administration_Guide-Live_KVM_migration_with_virsh-Verify_the_guest_is_running"><p class="title"><strong>Verify the guest is running</strong></p><div class="para">
+ From the source system, <code class="systemitem">host1.example.com</code>, verify <code class="systemitem">guest1-F19</code> is running:
+ </div><pre class="screen">[root at host1 ~]# virsh list
+Id Name State
+----------------------------------
+ 10 guest1-F19 running
+</pre></li><li class="step" id="step-Virtualization_Administration_Guide-Live_KVM_migration_with_virsh-Migrate_the_guest"><p class="title"><strong>Migrate the guest</strong></p><div class="para">
+ Execute the following command to live migrate the guest to the destination, <code class="systemitem">host2.example.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>guest1-F19 qemu+ssh://host2.example.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 class="step" id="step-Virtualization_Administration_Guide-Live_KVM_migration_with_virsh-Wait"><p class="title"><strong>Wait</strong></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 class="step" id="step-Virtualization_Administration_Guide-Live_KVM_migration_with_virsh-Verify_the_guest_has_arrived_at_the_destination_host"><p class="title"><strong>Verify the guest has arrived at the destination host</strong></p><div class="para">
+ From the destination system, <code class="systemitem">host2.example.com</code>, verify <code class="systemitem">guest1-F19</code> is running:
+ </div><pre class="screen">[root at host2 ~]# virsh list
+Id Name State
+----------------------------------
+ 10 guest1-F19 running
+</pre></li></ol></div><div class="para">
+ The live migration is now complete.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ libvirt supports a variety of networking methods including TLS/SSL, UNIX sockets, SSH, and unencrypted TCP. Refer to <a class="xref" href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html">Chapter 21, <em>Remote management of guests</em></a> for more information on using other methods.
+ </div></div></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Non-running guests cannot be migrated with the <code class="command">virsh migrate</code> command. To migrate a non-running guest, the following script should be used:
+<pre class="screen">
+virsh dumpxml Guest1 > Guest1.xml
+virsh -c qemu+ssh://<target-system-FQDN> define Guest1.xml
+virsh undefine Guest1
+</pre>
+ </div></div></div><div class="section" id="add-notes"><div class="titlepage"><div><div><h3 class="title">20.4.1. Additonal tips for migration with virsh </h3></div></div></div><div class="para">
+ It is possible to perform multiple, concurrent live migrations where each migration runs in a separate command shell. However, this should be done with caution and should involve careful calculations as each migration instance uses one MAX_CLIENT from each side (source and target). As the default setting is 20, there is enough to run 10 instances without changing the settings. Should you need to change the settings, refer to the procedure <a class="xref" href="chap-Virtualization_Administration_Guide-KVM_live_migration.html#change-libvirt-config">Procedure 20.1, “Configuring libvirtd.conf”</a>.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Open the libvirtd.conf file as described in <a class="xref" href="chap-Virtualization_Administration_Guide-KVM_live_migration.html#change-libvirt-config">Procedure 20.1, “Configuring libvirtd.conf”</a>.
+ </div></li><li class="step"><div class="para">
+ Look for the Processing controls section.
+ </div><pre class="screen">
+#################################################################
+#
+# Processing controls
+#
+
+# The maximum number of concurrent client connections to allow
+# over all sockets combined.
+#max_clients = 20
+
+
+# The minimum limit sets the number of workers to start up
+# initially. If the number of active clients exceeds this,
+# then more threads are spawned, upto max_workers limit.
+# Typically you'd want max_workers to equal maximum number
+# of clients allowed
+#min_workers = 5
+#max_workers = 20
+
+
+# The number of priority workers. If all workers from above
+# pool will stuck, some calls marked as high priority
+# (notably domainDestroy) can be executed in this pool.
+#prio_workers = 5
+
+# Total global limit on concurrent RPC calls. Should be
+# at least as large as max_workers. Beyond this, RPC requests
+# will be read into memory and queued. This directly impact
+# memory usage, currently each request requires 256 KB of
+# memory. So by default upto 5 MB of memory is used
+#
+# XXX this isn't actually enforced yet, only the per-client
+# limit is used so far
+#max_requests = 20
+
+# Limit on concurrent requests from a single client
+# connection. To avoid one client monopolizing the server
+# this should be a small fraction of the global max_requests
+# and max_workers parameter
+#max_client_requests = 5
+
+#################################################################
+</pre></li><li class="step"><div class="para">
+ Change the <em class="parameter"><code>max_clients</code></em> and <em class="parameter"><code>max_workers</code></em> parameters settings. It is recommended that the number be the same in both parameters. The <em class="parameter"><code>max_clients</code></em> will use 2 clients per migration (one per side) and <em class="parameter"><code>max_workers</code></em> will use 1 worker on the source and 0 workers on the destination during the perform phase and 1 worker on the destination during the finish phase.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The <em class="parameter"><code>max_clients</code></em> and <em class="parameter"><code>max_workers</code></em> parameters settings are effected by all guest connections to the libvirtd service. This means that any user that is using the same guest and is performing a migration at the same time will also beholden to the limits set in the the <em class="parameter"><code>max_clients</code></em> and <em class="parameter"><code>max_workers</code></em> parameters settings. This is why the maximum value needs to be considered carefully before performing a concurrent live migration.
+ </div></div></div></li><li class="step"><div class="para">
+ Save the file and restart the service.
+ </div></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="shared-storage-nfs-migration.html"><strong>Prev</strong>20.3. Shared storage example: NFS for a simple mi...</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="virsh-migration-arguements.html"><strong>Next</strong>20.4.2. Additional options for the virsh migrate ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager.html
new file mode 100644
index 0000000..e5ff8bb
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager.html
@@ -0,0 +1,57 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.5. Migrating with virt-manager</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-KVM_live_migration.html" title="Chapter 20. KVM live migration" /><link rel="prev" href="virsh-migration-arguements.html" title="20.4.2. Additional options for the virsh migrate command" /><link rel="next" href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html" title="Chapter 21. Remote management of guests" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="
Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="virsh-migration-arguements.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager"><div class="titlepage"><div><div><h2 class="title">20.5. Migrating with virt-manager</h2></div></div></div><div class="para">
+ This section covers migrating a KVM guest with <code class="command">virt-manager</code> from one host to another.
+ </div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Open virt-manager</strong></p><div class="para">
+ Open <code class="command">virt-manager</code>. Choose <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>Virtual Machine Manager</strong></span> from the main menu bar to launch <code class="command">virt-manager</code>.
+ </div><div class="figure" id="launch-virt-man-mig-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic1-virt-mgr-guests.png" width="444" alt="Virt-Manager main menu" /></div></div><h6>Figure 20.1. Virt-Manager main menu</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Connect to the target host</strong></p><div class="para">
+ Connect to the target host by clicking on the <span class="guimenu"><strong>File</strong></span> menu, then click <span class="guimenuitem"><strong>Add Connection</strong></span>.
+ <div class="figure" id="add-conn-mig-screen-step1"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic2-add-connection-pull-down.png" width="444" alt="Open Add Connection window" /></div></div><h6>Figure 20.2. Open Add Connection window</h6></div><br class="figure-break" />
+
+ </div></li><li class="step"><p class="title"><strong>Add connection</strong></p><div class="para">
+ The <span class="guilabel"><strong>Add Connection</strong></span> window appears.
+ </div><div class="figure" id="add-conn-mig-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic3-Add-Connection.png" alt="Adding a connection to the target host" /></div></div><h6>Figure 20.3. Adding a connection to the target host</h6></div><br class="figure-break" /><div class="para">
+ Enter the following details:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Hypervisor</strong></span>: Select <span class="guimenuitem"><strong>QEMU/KVM</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Method</strong></span>: Select the connection method.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Username</strong></span>: Enter the username for the remote host.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Hostname</strong></span>: Enter the hostname for the remote host.
+ </div></li></ul></div><div class="para">
+ Click the <span class="guibutton"><strong>Connect</strong></span> button. An SSH connection is used in this example, so the specified user's password must be entered in the next step.
+ </div><div class="figure" id="pass-ssh-mig-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic4-OpenSSH.png" alt="Enter password" /></div></div><h6>Figure 20.4. Enter password</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Migrate guest</strong></p><div class="para">
+ Right-click on the host to be migrated (<span class="bold bold"><strong>guest1-F19</strong></span> in this example) and click <span class="guimenuitem"><strong>Migrate</strong></span>.
+ </div><div class="figure" id="choose-host-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic5-guest-select-migrate.png" width="444" alt="Choosing the host to migrate" /></div></div><h6>Figure 20.5. Choosing the host to migrate</h6></div><br class="figure-break" /><div class="para">
+ Select the host you wish to migrate to and click <span class="guimenuitem"><strong>Migrate</strong></span>.
+ </div><div class="figure" id="mig-last-step-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic6-final-before-migrate.png" alt="Migrating the host" /></div></div><h6>Figure 20.6. Migrating the host</h6></div><br class="figure-break" /><div class="para">
+ A progress window will appear.
+ </div><div class="figure" id="mig-status-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic7-Migrating-guest1-rhel6-64.png" alt="Progress window" /></div></div><h6>Figure 20.7. Progress window</h6></div><br class="figure-break" /><div class="para">
+ <code class="command">virt-manager</code> now displays the newly migrated guest.
+ </div><div class="figure" id="mig-results-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic8-migrated.png" width="444" alt="Migrated guest status" /></div></div><h6>Figure 20.8. Migrated guest status</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>View the storage details for the host</strong></p><div class="para">
+ In the <span class="guimenu"><strong>Edit</strong></span> menu, click <span class="guimenuitem"><strong>Connection Details</strong></span>, the Connection Details window appears.
+ </div><div class="para">
+ Click the <span class="guibutton"><strong>Storage</strong></span> tab. The iSCSI target details for this host is shown.
+ </div><div class="figure" id="host-details-screenshot"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-virtlab22-Host-Details.png" width="444" alt="Storage details" /></div></div><h6>Figure 20.9. Storage details</h6></div><br class="figure-break" /><div class="para">
+ This host was defined by the following XML configuration:
+ </div><pre class="screen">
+<pool type='iscsi'>
+ <name>iscsirhel6guest</name>
+ <source>
+ <host name='virtlab22.example.com.'/>
+ <device path='iqn.2001-05.com.iscsivendor:0-8a0906-fbab74a06-a700000017a4cc89-rhevh'/>
+ </source>
+ <target>
+ <path>/dev/disk/by-path</path>
+ </target>
+</pool>
+</pre></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="virsh-migration-arguements.html"><strong>Prev</strong>20.4.2. Additional options for the virsh migrate ...</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_Administration_Guide-Remote_management_of_virtualized_guests.html"><strong>Next</strong>Chapter 21. Remote management of guests</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html
new file mode 100644
index 0000000..aedb3a0
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html
@@ -0,0 +1,16 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.8. Displaying CPU usage for guests</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="Appendix F. Managing guests with the Virtual Machine Manager (virt-manager)" /><link rel="prev" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html" title="F.7. Performance monitoring" /><link rel="next" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage.html" title="F.9. Displaying CPU usage for hosts" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Con
tent/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage"><div class="titlepage"><div><div><h2 class="title">F.8. Displaying CPU usage for guests</h2></div></div></div><div class="para">
+ To view the CPU usage for all guests on your system:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ From the <span class="guilabel"><strong>View</strong></span> menu, select <span class="guilabel"><strong>Graph</strong></span>, then the <span class="guilabel"><strong>Guest CPU Usage</strong></span> check box.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_CPU_usage-Selecting_guest-CPU_usage"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt24.png" width="444" alt="Enabling guest CPU usage statistics graphing" /></div></div><h6>Figure F.18. Enabling guest CPU usage statistics graphing</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ The Virtual Machine Manager shows a graph of CPU usage for all virtual machines on your system.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_CPU_usage-Displaying_CPU_usage"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager_fig31pt25.png" width="444" alt="Guest CPU usage graph" /></div></div><h6>Figure F.19. Guest CPU usage graph</h6></div><br class="figure-break" /></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html"><strong>Prev</strong>F.7. Performance 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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage.html"><strong>Next</strong>F.9. Displaying CPU usage for hosts</a></li></ul></bo
dy></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO.html
new file mode 100644
index 0000000..e0ed1d3
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.10. Displaying Disk I/O</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="Appendix F. Managing guests with the Virtual Machine Manager (virt-manager)" /><link rel="prev" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage.html" title="F.9. Displaying CPU usage for hosts" /><link rel="next" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO.html" title="F.11. Displaying Network I/O" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Commo
n_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO"><div class="titlepage"><div><div><h2 class="title">F.10. Displaying Disk I/O</h2></div></div></div><div class="para">
+ To view the disk I/O for all virtual machines on your system:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Make sure that the Disk I/O statisctics collection is enabled. To do this, from the <span class="guilabel"><strong>Edit</strong></span> menu, select <span class="guilabel"><strong>Preferences</strong></span> and click the <span class="guilabel"><strong>Stats</strong></span>tab.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Disk I/O </strong></span>checkbox.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-enabling_Disk_IO-stats"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager-enable-disk-io.png" alt="Enabling Disk I/O" /></div></div><h6>Figure F.22. Enabling Disk I/O</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ To enable the Disk I.O display, from the <span class="guilabel"><strong>View</strong></span> menu, select <span class="guilabel"><strong>Graph</strong></span>, then the <span class="guilabel"><strong>Disk I/O</strong></span> check box.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_Disk_IO-Selecting_Disk_IO"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager_fig31pt26.png" width="444" alt="Selecting Disk I/O" /></div></div><h6>Figure F.23. Selecting Disk I/O</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ The Virtual Machine Manager shows a graph of Disk I/O for all virtual machines on your system.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_Disk_IO-Displaying_Disk_IO"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt27.png" width="444" alt="Displaying Disk I/O" /></div></div><h6>Figure F.24. Displaying Disk I/O</h6></div><br class="figure-break" /></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage.html"><strong>Prev</strong>F.9. Displaying CPU usage for hosts</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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO.html"><strong>Next</strong>F.11. Displaying Network I/O</a></li></ul></body>
</html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO.html
new file mode 100644
index 0000000..1483d31
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.11. Displaying Network I/O</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="Appendix F. Managing guests with the Virtual Machine Manager (virt-manager)" /><link rel="prev" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO.html" title="F.10. Displaying Disk I/O" /><link rel="next" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt
="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO"><div class="titlepage"><div><div><h2 class="title">F.11. Displaying Network I/O</h2></div></div></div><div class="para">
+ To view the network I/O for all virtual machines on your system:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Make sure that the Network I/O statisctics collection is enabled. To do this, from the <span class="guilabel"><strong>Edit</strong></span> menu, select <span class="guilabel"><strong>Preferences</strong></span> and click the <span class="guilabel"><strong>Stats</strong></span>tab.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Network I/O </strong></span>checkbox.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-enabling_network_IO-stats"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager-enable-networkio.png" alt="Enabling Network I/O" /></div></div><h6>Figure F.25. Enabling Network I/O</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ To display the Network I/O statistics, from the <span class="guilabel"><strong>View</strong></span> menu, select <span class="guilabel"><strong>Graph</strong></span>, then the <span class="guilabel"><strong>Network I/O</strong></span> check box.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_Network_IO-Selecting_Network_IO"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt28.png" width="444" alt="Selecting Network I/O" /></div></div><h6>Figure F.26. Selecting Network I/O</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ The Virtual Machine Manager shows a graph of Network I/O for all virtual machines on your system.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_Network_IO-Displaying_Network_IO"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt29.png" width="444" alt="Displaying Network I/O" /></div></div><h6>Figure F.27. Displaying Network I/O</h6></div><br class="figure-break" /></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO.html"><strong>Prev</strong>F.10. Displaying Disk I/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="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html"><strong>Next</strong>Appendix G. Guest disk access with offline tools</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html
new file mode 100644
index 0000000..458619d
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html
@@ -0,0 +1,34 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.6. Displaying guest details</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="Appendix F. Managing guests with the Virtual Machine Manager (virt-manager)" /><link rel="prev" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window.html" title="F.5. Adding a remote connection" /><link rel="next" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html" title="F.7. Performance monitoring" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Conten
t/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details"><div class="titlepage"><div><div><h2 class="title">F.6. Displaying guest details</h2></div></div></div><div class="para">
+ You can use the Virtual Machine Monitor to view activity 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 class="step"><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_Administration_Guide-Displaying_guest_details-Selecting_a_virtual_machine_to_display_"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt1.png" width="444" alt="Selecting a virtual machine to display" /></div></div><h6>Figure F.8. Selecting a virtual machine to display </h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ From the Virtual Machine Manager <span class="guilabel"><strong>Edit</strong></span> menu, select <span class="guilabel"><strong>Virtual Machine Details</strong></span>.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Displaying_virtual_machine_details_menu"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt11.png" width="444" alt="Displaying the virtual machine details" /></div></div><h6>Figure F.9. Displaying the virtual machine details</h6></div><br class="figure-break" /><div class="para">
+ When the Virtual Machine details window opens, there may be a console displayed. Should this happen, clikc <span class="guilabel"><strong>View</strong></span> and then select <span class="guilabel"><strong>Details</strong></span>. The Overview window opens first by default. To go back to this window, select <span class="guilabel"><strong>Overview</strong></span> from the navigation pane on the left hand side.
+ </div><div class="para">
+ The <span class="guilabel"><strong>Overview</strong></span> view shows a summary of configuration details for the guest.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Displaying_guest_details_overview"><div class="figure-contents"><div class="mediaobject"><img src="images/virtual_machine_overview.png" width="444" alt="Displaying guest details overview" /></div></div><h6>Figure F.10. Displaying guest details overview</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Select <span class="guilabel"><strong>Performance</strong></span> from the navigation pane on the left hand side.
+ </div><div class="para">
+ The <span class="guilabel"><strong>Performance</strong></span> view shows a summary of guest performance, including CPU and Memory usage.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Displaying_guest_performance"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt13.png" width="444" alt="Displaying guest performance details" /></div></div><h6>Figure F.11. Displaying guest performance details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Select <span class="guilabel"><strong>Processor</strong></span> from the navigation pane on the left hand side. The <span class="guilabel"><strong>Processor</strong></span> view allows you to view or change the current processor allocation.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Processor_allocation_panel"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt14.png" width="444" alt="Processor allocation panel" /></div></div><h6>Figure F.12. Processor allocation panel</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Select <span class="guilabel"><strong>Memory</strong></span> from the navigation pane on the left hand side. The <span class="guilabel"><strong>Memory</strong></span> view allows you to view or change the current memory allocation.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Displaying_memory_allocation"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt15.png" width="444" alt="Displaying memory allocation" /></div></div><h6>Figure F.13. Displaying memory allocation</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Each virtual disk attached to the virtual machine is displayed in the navigation pane. Click on a virtual disk to modify or remove it.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Displaying_disk_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt16.png" width="444" alt="Displaying disk configuration" /></div></div><h6>Figure F.14. Displaying disk configuration</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Each virtual network interface attached to the virtual machine is displayed in the navigation pane. Click on a virtual network interface to modify or remove it.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Displaying_network_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt17.png" width="444" alt="Displaying network configuration" /></div></div><h6>Figure F.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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window.html"><strong>Prev</strong>F.5. Adding a remote connection</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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html"><strong>Next</strong>F.7. Perfo
rmance monitoring</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage.html
new file mode 100644
index 0000000..de58f19
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage.html
@@ -0,0 +1,16 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.9. Displaying CPU usage for hosts</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="Appendix F. Managing guests with the Virtual Machine Manager (virt-manager)" /><link rel="prev" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html" title="F.8. Displaying CPU usage for guests" /><link rel="next" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO.html" title="F.10. Displaying Disk I/O" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/
images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage"><div class="titlepage"><div><div><h2 class="title">F.9. Displaying CPU usage for hosts</h2></div></div></div><div class="para">
+ To view the CPU usage for all hosts on your system:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ From the <span class="guilabel"><strong>View</strong></span> menu, select <span class="guilabel"><strong>Graph</strong></span>, then the <span class="guilabel"><strong>Host CPU Usage</strong></span> check box.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_Host-CPU_usage-Selecting_CPU_usage"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt24a.png" width="444" alt="Enabling host CPU usage statistics graphing" /></div></div><h6>Figure F.20. Enabling host CPU usage statistics graphing</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ The Virtual Machine Manager shows a graph of host CPU usage on your system.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_host-CPU_usage-Displaying_CPU_usage"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager_fig31pt25a.png" width="444" alt="Host CPU usage graph" /></div></div><h6>Figure F.21. Host CPU usage graph</h6></div><br class="figure-break" /></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html"><strong>Prev</strong>F.8. Displaying CPU usage 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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO.html"><strong>Next</strong>F.10. Displaying Disk I/O</a></li></ul></bod
y></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html
new file mode 100644
index 0000000..9403879
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.7. Performance monitoring</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="Appendix F. Managing guests with the Virtual Machine Manager (virt-manager)" /><link rel="prev" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html" title="F.6. Displaying guest details" /><link rel="next" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html" title="F.8. Displaying CPU usage for guests" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Commo
n_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring"><div class="titlepage"><div><div><h2 class="title">F.7. Performance monitoring</h2></div></div></div><div class="para">
+ Performance monitoring preferences can be modified with <code class="command">virt-manager</code>'s preferences window.
+ </div><div class="para">
+ To configure performance monitoring:
+ </div><div class="procedure"><ol class="1"><li class="step"><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_Administration_Guide-Status_monitoring-Modifying_guest_preferences"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-VIrt-Manager-fig31pt18.png" width="444" alt="Modifying guest preferences" /></div></div><h6>Figure F.16. Modifying guest preferences</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guilabel"><strong>Preferences</strong></span> window appears.
+ </div></li><li class="step"><div class="para">
+ From the <span class="guilabel"><strong>Stats</strong></span> tab specify the time in seconds or stats polling options.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Status_monitoring-Configuring_status_monitoring"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt19.png" alt="Configuring performance monitoring" /></div></div><h6>Figure F.17. Configuring performance monitoring</h6></div><br class="figure-break" /></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html"><strong>Prev</strong>F.6. 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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html"><strong>Next</strong>F.8. Displaying CPU usage for
guests</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_.html
new file mode 100644
index 0000000..4a82577
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_.html
@@ -0,0 +1,14 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.3. The virtual hardware details window</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="Appendix F. Managing guests with the Virtual Machine Manager (virt-manager)" /><link rel="prev" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html" title="F.2. The Virtual Machine Manager main window" /><link rel="next" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html" title="F.4. Virtual Machine graphical console" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left
" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_"><div class="titlepage"><div><div><h2 class="title">F.3. The virtual hardware details window</h2></div></div></div><div class="para">
+ The virtual hardware details window displays information about the virtual hardware configured for the guest. Virtual hardware resources can be added, removed and modified in this window. To access the virtual hardware details window, click on the icon in the toolbar.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-The_Virtual_Machine_Manager_details_window_-virt_manager_details_button"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt3.png" width="444" alt="The virtual hardware details icon" /></div></div><h6>Figure F.3. The virtual hardware details icon</h6></div><br class="figure-break" /><div class="para">
+ Clicking the icon displays the virtual hardware details window.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-The_Virtual_Machine_Manager_details_window_-virt_manager_details_window"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt4.png" width="444" alt="The virtual hardware details window" /></div></div><h6>Figure F.4. The virtual hardware details window</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html"><strong>Prev</strong>F.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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_cons
ole_.html"><strong>Next</strong>F.4. Virtual Machine graphical console</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html
new file mode 100644
index 0000000..f5a307c
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.2. The Virtual Machine Manager main window</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="Appendix F. Managing guests with the Virtual Machine Manager (virt-manager)" /><link rel="prev" href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="Appendix F. Managing guests with the Virtual Machine Manager (virt-manager)" /><link rel="next" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_.html" title="F.3. The virtual hardware details window" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p i
d="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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_Administration_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-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" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window"><div class="titlepage"><div><div><h2 class="title">F.2. The Virtual Machine Manager main window</h2></div></div></div><div class="para">
+ This main window displays all the running guests and resources used by guests. Select a guest by double clicking the guest's name.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-The_Virtual_Machine_Manager_main_window-Virtual_Machine_Manager_main_window"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt2.png" width="444" alt="Virtual Machine Manager main window" /></div></div><h6>Figure F.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_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html"><strong>Prev</strong>Appendix F. 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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_
window_.html"><strong>Next</strong>F.3. The virtual hardware details window</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window.html
new file mode 100644
index 0000000..2543124
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.5. Adding a remote connection</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="Appendix F. Managing guests with the Virtual Machine Manager (virt-manager)" /><link rel="prev" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html" title="F.4. Virtual Machine graphical console" /><link rel="next" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html" title="F.6. Displaying guest details" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"
><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window"><div class="titlepage"><div><div><h2 class="title">F.5. Adding a remote connection</h2></div></div></div><div class="para">
+ This procedure covers how to set up a connection to a remote system using <code class="command">virt-manager</code>.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To create a new connection open the <span class="guilabel"><strong>File</strong></span> menu and select the <span class="guilabel"><strong>Add Connection...</strong></span> menu item.
+ </div></li><li class="step"><div class="para">
+ The <span class="guilabel"><strong>Add Connection</strong></span> wizard appears. Select the hypervisor. For Fedora systems select <span class="guilabel"><strong>QEMU/KVM</strong></span>. Select Local for the local system or one of the remote connection options and click <span class="guilabel"><strong>Connect</strong></span>. This example uses Remote tunnel over SSH which works on default installations. For more information on configuring remote connections refer to <a class="xref" href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html">Chapter 21, <em>Remote management of guests</em></a>
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Remote_management-Add_connection"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt6.png" alt="Add Connection" /></div></div><h6>Figure F.6. Add Connection</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Enter the root password for the selected host when prompted.
+ </div></li></ol></div><div class="para">
+ A remote host is now connected and appears in the main <code class="command">virt-manager</code> window.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Remote_management-Remove_host_in_the_main_virt-manager_window"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt7.png" width="444" alt="Remote host in the main virt-manager window" /></div></div><h6>Figure F.7. Remote host in the main virt-manager window</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html"><strong>Prev</strong>F.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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html"><str
ong>Next</strong>F.6. Displaying guest details</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html
new file mode 100644
index 0000000..1ad2724
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.4. Virtual Machine graphical console</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="Appendix F. Managing guests with the Virtual Machine Manager (virt-manager)" /><link rel="prev" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_.html" title="F.3. The virtual hardware details window" /><link rel="next" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window.html" title="F.5. Adding a remote connection" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://
www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_"><div class="titlepage"><div><div><h2 class="title">F.4. Virtual Machine graphical console</h2></div></div></div><div class="para">
+ This window displays a guest's graphical console. Guests can use several different protocols to export their graphical framebuffers: <code class="command">virt-manager</code> supports <span class="application"><strong>VNC</strong></span> and <span class="application"><strong>SPICE</strong></span>. 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_Administration_Guide-Virtual_Machine_graphical_console_-Graphical_console_window"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt5.png" width="444" alt="Graphical console window" /></div></div><h6>Figure F.5. Graphical console window</h6></div><br class="figure-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><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'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. Although virt-manager is configured to listen to other public network interfaces and alternative methods can be configured, it is not recommended.
+ </div><div class="para">
+ Remote administration can be performed by tunneling over SSH which encrypts the traffic. Although VNC can be configured to access remotely without tunneling over SSH, for security reasons, it is not recommended. To remotely administer the guest follow the instructions in: <a class="xref" href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html">Chapter 21, <em>Remote management of guests</em></a>. TLS can provide enterprise level security for managing guest and host systems.
+ </div></div></div><div class="para">
+ Your local desktop can intercept key combinations (for example, Ctrl+Alt+F1) to prevent them from being sent to the guest machine. You can use the <span class="guimenuitem"><strong>Send key</strong></span> menu option to send these sequences. From the guest machine window, click the <span class="guimenuitem"><strong>Send key</strong></span> menu and select the key sequence to send. In addition, from this menu you can also capture the screen output.
+ </div><div class="para">
+ SPICE is an alternative to VNC available for Fedora.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_.html"><strong>Prev</strong>F.3. The virtual hardware 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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window.html"><strong>Next</strong>F.5. Adding a remote connection</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor.html
new file mode 100644
index 0000000..cd0fd13
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor.html
@@ -0,0 +1,14 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.3. Connecting to the hypervisor</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="prev" href="sect-Attaching_and_updating_a_device_with_virsh.html" title="E.2. Attaching and updating a device with virsh" /><link rel="next" href="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html" title="E.4. Creating a virtual machine XML dump (configuration file)" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://d
ocs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Attaching_and_updating_a_device_with_virsh.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor"><div class="titlepage"><div><div><h2 class="title">E.3. Connecting to the hypervisor</h2></div></div></div><div class="para">
+ Connect to a hypervisor session with <code class="command">virsh</code>:
+ </div><pre class="screen"># virsh connect <em class="parameter"><code>{name}</code></em></pre><div class="para">
+ Where <em class="parameter"><code>{name}</code></em> is the machine name (hostname) or URL (the output of the <code class="command">virsh uri</code> command) of the hypervisor. To initiate a read-only connection, append the above command with <code class="command">--readonly</code>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Attaching_and_updating_a_device_with_virsh.html"><strong>Prev</strong>E.2. Attaching and updating a device 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="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html"><strong>Next</strong>E.4. Creating a virtual machine XML dump (configu...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html
new file mode 100644
index 0000000..f8824ec
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html
@@ -0,0 +1,90 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>21.2. Remote management over TLS and SSL</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html" title="Chapter 21. Remote management of guests" /><link rel="prev" href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html" title="Chapter 21. Remote management of guests" /><link rel="next" href="sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes.html" title="21.3. Transport modes" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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_Administration_Guide-Remote_management_of_virtualized_guests.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL"><div class="titlepage"><div><div><h2 class="title">21.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_Administration_Guide-Remote_management_of_virtualized_guests.html#sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_with_SSH">Section 21.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. The procedures that follow provide instructions on creating and deploying authentication certificates for TLS and SSL management.
+ </div><div class="procedure" id="createCA-key"><h6>Procedure 21.1. Creating a certificate authority (CA) key for TLS management</h6><ol class="1"><li class="step"><div class="para">
+ Before you begin, confirm that <code class="command">certtool</code> is installed. If not:
+ </div><pre class="screen">#<code class="command"> yum install certtool</code></pre></li><li class="step"><div class="para">
+ Generate a private key, using the following command:
+ </div><pre class="screen"># <code class="command">certtool --generate-privkey > cakey.pem</code></pre></li><li class="step"><div class="para">
+ Once the key generates, the next step is to create a signature file so the key can be self-signed. To do this, create a file with signature details and name it <code class="filename">ca.info</code>. This file should contain the following:
+ </div><pre class="screen"># <code class="command">vim ca.info</code></pre><pre class="screen">
+cn = Name of your organization
+ca
+cert_signing_key
+</pre></li><li class="step"><div class="para">
+ Generate the self-signed key with the following command:
+ </div><pre class="screen"># <code class="command">certtool --generate-self-signed --load-privkey cakey.perm --template ca.info --outfile cacert.pem</code></pre><div class="para">
+ Once the file generates, the ca.info file may be deleted using the <code class="command">rm</code> command. The file that results from the generation process is named <code class="filename">cacert.pem</code>. This file is the public key (certificate). The loaded file <code class="filename">cakey.pem</code> is the private key. This file should not be kept in a shared space. Keep this key private.
+ </div></li><li class="step"><div class="para">
+ Install the <code class="filename">cacert.pem</code> Certificate Authority Certificate file on all clients and servers in the <code class="filename">/etc/pki/CA/cacert.pem</code> directory to let them know that the certificate issued by your CA can be trusted. To view the contents of this file, run:
+<pre class="screen"># <code class="command">certtool -i --infile cacert.pem</code></pre>
+
+ </div><div class="para">
+ This is all that is required to set up your CA. Keep the CA's private key safe as you will need it in order to issue certificates for your clients and servers.
+ </div></li></ol></div><div class="procedure" id="issue-server-cetificate-ca"><h6>Procedure 21.2. Issuing a server certificate</h6><div class="para">
+ This procedure demonstrates how to issue a certificate with the X.509 CommonName (CN)field set to the hostname of the server. The CN must match the hostname which clients will be using to connect to the server. In this example, clients will be connecting to the server using the URI: <code class="filename">qemu://mycommonname/system</code>, so the CN field should be identical, ie mycommoname.
+ </div><ol class="1"><li class="step"><div class="para">
+ Create a private key for the server.
+ </div><pre class="screen"># <code class="command">certtool --generate-privkey > serverkey.pem</code></pre></li><li class="step"><div class="para">
+ Generate a signature for the CA's private key by first creating a template file called <code class="filename">server.info </code>. Make sure that the CN is set to be the same as the server's hostname:
+ </div><pre class="screen">
+organization = Name of your organization
+cn = mycommonname
+tls_www_server
+encryption_key
+signing_key
+</pre></li><li class="step"><div class="para">
+ Create the certificate with the following command:
+ </div><pre class="screen">
+# <code class="command">certtool --generate-certificate --load-privkey serverkey.pem --load-ca-certificate cacert.pem --load-ca-privkey cakey.pem \ --template server.info --outfile servercert.pem</code></pre></li><li class="step"><div class="para">
+ This results in two files being generated:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ serverkey.pem - The server's private key
+ </div></li><li class="listitem"><div class="para">
+ servercert.pem - The server's public key
+ </div></li></ul></div><div class="para">
+ Make sure to keep the location of the private key secret. To view the contents of the file, perform the following command:
+ </div><pre class="screen">
+# <code class="command">certtool -i -inifile servercert.pem</code></pre><div class="para">
+ When opening this file the <code class="filename">CN=</code> parameter should be the same as the CN that you set earlier. For example, <code class="filename">mycommonname</code>.
+ </div></li><li class="step"><div class="para">
+ Install the two files in the following locations:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">serverkey.pem</code> - the server's private key. Place this file in the following location: <code class="filename">/etc/pki/libvirt/private/serverkey.pem</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">servercert.pem</code> - the server's certificate. Install it in the following location on the server:<code class="filename"> /etc/pki/libvirt/servercert.pem</code>
+ </div></li></ul></div></li></ol></div><div class="procedure" id="pro-issue-client-certs-CA"><h6>Procedure 21.3. Issuing a client certificate</h6><ol class="1"><li class="step"><div class="para">
+ For every client (ie. any program linked with libvirt, such as virt-manager), you need to issue a certificate with the X.509 Distinguished Name (DN) set to a suitable name. This needs to be decided on a corporate level.
+ </div><div class="para">
+ For example purposes the following information will be used:
+ </div><pre class="screen"><em class="replaceable"><code>C=USA,ST=North Carolina,L=Raleigh,O=Fedora,CN=name_of_client</code></em></pre><div class="para">
+ This process is quite similar to <a class="xref" href="sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html#issue-server-cetificate-ca">Procedure 21.2, “Issuing a server certificate”</a>, with the following exceptions noted.
+ </div></li><li class="step"><div class="para">
+ Make a private key with the following command:
+ </div><pre class="screen"># <code class="command">certtool --generate-privkey > clientkey.pem</code></pre></li><li class="step"><div class="para">
+ Generate a signature for the CA's private key by first creating a template file called <code class="filename">client.info </code>. The file should contain the following (fields should be customized to reflect your region/location):
+ </div><pre class="screen">
+country = USA
+state = North Carolina
+locality = Raleigh
+organization = Fedora
+cn = client1
+tls_www_client
+encryption_key
+signing_key
+</pre></li><li class="step"><div class="para">
+ Sign the certificate with the following command:
+ </div><pre class="screen">
+# <code class="command">certtool --generate-certificate --load-privkey clientkey.pem --load-ca-certificate cacert.pem \ --load-ca-privkey cakey.pem --template client.info --outfile clientcert.pem</code></pre></li><li class="step"><div class="para">
+ Install the certificates on the client machine:
+ </div><pre class="screen">
+# <code class="command">cp clientkey.pem /etc/pki/libvirt/private/clientkey.pem</code>
+# <code class="command">cp clientcert.pem /etc/pki/libvirt/clientcert.pem</code></pre></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html"><strong>Prev</strong>Chapter 21. Remote management of 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-Remote_management_of_virtualized_guests-Transport_modes.html"><strong>Next</strong>21.3. Transport modes</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes.html
new file mode 100644
index 0000000..ed54802
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes.html
@@ -0,0 +1,109 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>21.3. Transport modes</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html" title="Chapter 21. Remote management of guests" /><link rel="prev" href="sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html" title="21.2. Remote management over TLS and SSL" /><link rel="next" href="sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM.html" title="Chapter 22. Overcommitting with KVM" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.co
m"><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-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes"><div class="titlepage"><div><div><h2 class="title">21.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" id="form-Virtualization-Transport_modes-Transport_Layer_Security_TLS"><h5 class="formalpara">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" id="form-Virtualization-Transport_modes-UNIX_sockets"><h5 class="formalpara">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" id="form-Virtualization-Transport_modes-SSH"><h5 class="formalpara">SSH</h5>
+ Transported over a 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" id="form-Virtualization-Transport_modes-ext"><h5 class="formalpara">ext</h5>
+ The <em class="parameter"><code>ext</code></em> parameter is used for any external program which can make a connection to the remote machine by means outside the scope of libvirt. This parameter is unsupported.
+ </div><div class="formalpara" id="form-Virtualization-Transport_modes-tcp"><h5 class="formalpara">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" id="form-Virtualization-Transport_modes-Remote_URIs"><h5 class="formalpara">Remote URIs</h5>
+ A Uniform Resource Identifier (URI) is used by <code class="command">virsh</code> and <span class="package">libvirt</span> 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.
+ </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">
+ The transport method or the hostname must be provided to target an external location.
+ </div><div class="itemizedlist" id="item-Virtualization-Transport_modes-Examples_of_remote_management_parameters"><h6>Examples of remote management parameters</h6><ul><li class="listitem"><div class="para">
+ Connect to a remote KVM host named <code class="systemitem">host2</code>, using SSH transport and the SSH username <code class="systemitem">virtuser</code>.
+ </div><pre class="screen"><code class="command">qemu+ssh://virtuser@host2/</code></pre></li><li class="listitem"><div class="para">
+ Connect to a remote KVM hypervisor on the host named <code class="systemitem">host2</code> using TLS.
+ </div><pre class="screen"><code class="command">qemu://host2/</code></pre></li></ul></div><div class="itemizedlist" id="item-Virtualization-Transport_modes-Testing_examples"><h6>Testing examples</h6><ul><li class="listitem"><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"><code class="command">qemu+unix:///system?socket=/opt/libvirt/run/libvirt/libvirt-sock</code></pre></li><li class="listitem"><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"><code class="command">test+tcp://10.1.1.10:5000/default</code></pre></li></ul></div><div class="formalpara" id="form-Virtualization-Transport_modes-Extra_URI_parameters"><h5 class="formalpara">Extra URI parameters</h5>
+ Extra parameters can be appended to remote URIs. The table below <a class="xref" href="sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes.html#tabl-Virtualization-Transport_modes-Extra_URI_parameters">Table 21.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-Transport_modes-Extra_URI_parameters"><h6>Table 21.1. Extra URI parameters</h6><div class="table-contents"><table summary="Extra URI parameters" border="1"><colgroup><col width="25%" /><col width="25%" /><col width="25%" /><col width="25%" /></colgroup><thead><tr><th class="">
+ Name
+ </th><th class="">
+ Transport mode
+ </th><th class="">
+ Description
+ </th><th class="">
+ Example usage
+ </th></tr></thead><tbody><tr><td class="">
+ name
+ </td><td class="">
+ all modes
+ </td><td class="">
+ 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 class="">
+ name=qemu:///system
+ </td></tr><tr><td class="">
+ command
+ </td><td class="">
+ ssh and ext
+ </td><td class="">
+ The external command. For ext transport this is required. For ssh the default is ssh. The PATH is searched for the command.
+ </td><td class="">
+ command=/opt/openssh/bin/ssh
+ </td></tr><tr><td class="">
+ socket
+ </td><td class="">
+ unix and ssh
+ </td><td class="">
+ 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 class="">
+ socket=/opt/libvirt/run/libvirt/libvirt-sock
+ </td></tr><tr><td class="">
+ netcat
+ </td><td class="">
+ ssh
+ </td><td class="">
+ <div class="para">
+ The <code class="command">netcat</code> command can be used to connect to remote systems. The default netcat parameter uses the <code class="command">nc</code> command. For SSH transport, libvirt constructs an SSH command using the form below:
+ </div>
+ <div class="para">
+ <em class="parameter"><code>command</code></em> -p <em class="parameter"><code>port</code></em> [-l <em class="parameter"><code>username</code></em>] <em class="parameter"><code>hostname</code></em>
+ </div>
+ <div class="para">
+ <em class="parameter"><code>netcat</code></em> -U socket
+ </div>
+ <div class="para">
+ The <em class="parameter"><code>port</code></em>, <em class="parameter"><code>username</code></em> and <em class="parameter"><code>hostname</code></em> parameters can be specified as part of the remote URI. The <em class="parameter"><code>command</code></em>, <em class="parameter"><code>netcat</code></em> and <em class="parameter"><code>socket</code></em> come from other extra parameters.
+ </div>
+
+ </td><td class="">
+ netcat=/opt/netcat/bin/nc
+ </td></tr><tr><td class="">
+ no_verify
+ </td><td class="">
+ tls
+ </td><td class="">
+ 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 class="">
+ no_verify=1
+ </td></tr><tr><td class="">
+ no_tty
+ </td><td class="">
+ ssh
+ </td><td class="">
+ 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 class="">
+ no_tty=1
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html"><strong>Prev</strong>21.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="sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM.html"><strong>Next</strong>Chapter 22. Overcommitting with KVM</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization.html
new file mode 100644
index 0000000..d27204d
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization.html
@@ -0,0 +1,43 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>18.2. SELinux and virtualization</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization-Security_for_virtualization.html" title="Chapter 18. Security for virtualization" /><link rel="prev" href="chap-Virtualization-Security_for_virtualization.html" title="Chapter 18. Security for virtualization" /><link rel="next" href="sect-Virtualization-Security_for_virtualization-SELinux_considerations.html" title="18.3. SELinux" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul c
lass="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization-Security_for_virtualization.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Security_for_virtualization-SELinux_considerations.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization"><div class="titlepage"><div><div><h2 class="title">18.2. 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 attacker's abilities and works to prevent many common security exploits such as buffer overflow attacks and privilege escalation. It is because of these benefits that all Fedora systems should run with SELinux enabled and in enforcing mode.
+ </div><div class="formalpara" id="form-Virtualization-SELinux_and_virtualization-Adding_LVM_based_storage_with_SELinux_in_enforcing_mode"><h5 class="formalpara">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-SELinux_and_virtualization-Creating_and_mounting_a_logical_volume_on_a_virtualized_guest_with_SELinux_enabled"><h6>Procedure 18.1. Creating and mounting a logical volume on a virtualized guest with SELinux enabled</h6><ol class="1"><li class="step"><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 class="step"><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 class="step"><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 class="step"><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 class="step"><div class="para">
+ Set the correct SELinux type for the libvirt image location.
+ </div><pre class="screen"># semanage fcontext -a -t virt_image_t "/virtstorage(/.*)?"
+</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:virt_image_t:s0
+</pre></li><li class="step"><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">virt_image_t</code> (the <code class="command">restorecon</code> and <code class="command">setfiles</code> commands read the files in <code class="filename">/etc/selinux/targeted/contexts/files/</code>).
+ </div><pre class="screen"># restorecon -R -v /virtstorage
+</pre></li></ol></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Create a new file (using the <code class="command">touch</code> command) on the file system.
+ </div><pre class="screen"># touch <em class="replaceable"><code>/virtstorage/newfile</code></em></pre><div class="para">
+ Verify the file has been relabeled using the following command:
+ </div><pre class="screen"># sudo ls -Z <em class="replaceable"><code>/virtstorage</code></em>
+-rw-------. root root system_u:object_r:virt_image_t:s0 <em class="replaceable"><code>newfile</code></em></pre><div class="para">
+ The output shows that the new file has the correct attribute, <code class="filename">virt_image_t</code>.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization-Security_for_virtualization.html"><strong>Prev</strong>Chapter 18. 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="sect-Virtualization-Security_for_virtualization-SELinux_considerations.html"><strong>Next</strong>18.3. SELinux</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Security_for_virtualization-SELinux_considerations.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Security_for_virtualization-SELinux_considerations.html
new file mode 100644
index 0000000..d986609
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Security_for_virtualization-SELinux_considerations.html
@@ -0,0 +1,16 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>18.3. SELinux</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization-Security_for_virtualization.html" title="Chapter 18. Security for virtualization" /><link rel="prev" href="sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization.html" title="18.2. SELinux and virtualization" /><link rel="next" href="ch18s04.html" title="18.4. Virtualization firewall information" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><l
i class="previous"><a accesskey="p" href="sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch18s04.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Security_for_virtualization-SELinux_considerations"><div class="titlepage"><div><div><h2 class="title">18.3. SELinux</h2></div></div></div><div class="para">
+ This section contains topics to consider when using SELinux with 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. Make sure that you have installed the <code class="filename">policycoreutilis-python</code> package (<code class="command">yum install policycoreutilis-python</code>) before running the command.
+ </div><pre class="screen"># semanage fcontext -a -t virt_image_t -f -b /dev/sda2
+# restorecon /dev/sda2
+</pre><div class="formalpara"><h5 class="formalpara" id="idp5615568">KVM and SELinux</h5>
+ The following table shows the SELinux Booleans which affect KVM when launched by libvirt.
+ </div><div class="segmentedlist"><div class="title"><strong><span class="title">KVM SELinux Booleans</span></strong></div><table border="0"><thead><tr class="segtitle"><th>SELinux Boolean</th><th>Description</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">virt_use_comm</td><td class="seg">Allow virt to use serial/parallel communication ports.</td></tr><tr class="seglistitem"><td class="seg">virt_use_fusefs</td><td class="seg">Allow virt to read fuse files.</td></tr><tr class="seglistitem"><td class="seg">virt_use_nfs</td><td class="seg">Allow virt to manage NFS files.</td></tr><tr class="seglistitem"><td class="seg">virt_use_samba</td><td class="seg">Allow virt to manage CIFS files.</td></tr><tr class="seglistitem"><td class="seg">virt_use_sanlock</td><td class="seg">Allow sanlock to manage virt lib files.</td></tr><tr class="seglistitem"><td class="seg">virt_use_sysfs</td><td class="seg">Allow virt to manage device configuration (PCI).</td></tr><tr class=
"seglistitem"><td class="seg">virt_use_xserver</td><td class="seg">Allow virtual machine to interact with the xserver.</td></tr><tr class="seglistitem"><td class="seg">virt_use_usb</td><td class="seg">Allow virt to use USB devices.</td></tr></tbody></table></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization.html"><strong>Prev</strong>18.2. SELinux 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="ch18s04.html"><strong>Next</strong>18.4. Virtualization firewall information</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Storage_Concepts-Volumes.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Storage_Concepts-Volumes.html
new file mode 100644
index 0000000..3874514
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Storage_Concepts-Volumes.html
@@ -0,0 +1,63 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>26.2. Volumes</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Storage_Concepts.html" title="Chapter 26. Storage concepts" /><link rel="prev" href="chap-Virtualization_Administration_Guide-Storage_Concepts.html" title="Chapter 26. Storage concepts" /><link rel="next" href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html" title="Chapter 27. Storage pools" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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_Administration_Guide-Storage_Concepts.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Storage_Concepts-Volumes"><div class="titlepage"><div><div><h2 class="title">26.2. Volumes </h2></div></div></div><div class="para">
+ Storage pools are divided into storage volumes. Storage volumes are an abstraction of physical partitions, LVM logical volumes, file-based disk images and other storage types handled by libvirt. Storage volumes are presented to guests as local storage devices regardless of the underlying hardware.
+ </div><div class="formalpara"><h5 class="formalpara" id="idp1075728"> Referencing volumes</h5>
+ To reference a specific volume, three approaches are possible:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">The name of the volume and the storage pool</span></dt><dd><div class="para">
+ A volume may be referred to by name, along with an identifier for the storage pool it belongs in. On the virsh command line, this takes the form <em class="parameter"><code>--pool</code></em> <em class="replaceable"><code>storage_pool</code></em> <em class="replaceable"><code>volume_name</code></em>.
+ </div><div class="para">
+ For example, a volume named <em class="replaceable"><code>firstimage</code></em> in the <em class="replaceable"><code>guest_images</code></em> pool.
+ </div><pre class="screen"># virsh vol-info --pool <em class="replaceable"><code>guest_images</code></em> <em class="replaceable"><code>firstimage</code></em>
+Name: <em class="replaceable"><code>firstimage</code></em>
+Type: block
+Capacity: 20.00 GB
+Allocation: 20.00 GB
+
+virsh #</pre></dd><dt class="varlistentry"><span class="term">The full path to the storage on the host system</span></dt><dd><div class="para">
+ A volume may also be referred to by its full path on the file system. When using this approach, a pool identifier does not need to be included.
+ </div><div class="para">
+ For example, a volume named <em class="replaceable"><code>secondimage.img</code></em>, visible to the host system as <em class="replaceable"><code>/images/secondimage.img</code></em>. The image can be referred to as <em class="replaceable"><code>/images/secondimage.img</code></em>.
+ </div><pre class="screen"># virsh vol-info <em class="replaceable"><code>/images/secondimage.img</code></em>
+Name: <em class="replaceable"><code>secondimage.img</code></em>
+Type: file
+Capacity: 20.00 GB
+Allocation: 136.00 kB
+</pre></dd><dt class="varlistentry"><span class="term">The unique volume key</span></dt><dd><div class="para">
+ When a volume is first created in the virtualization system, a unique identifier is generated and assigned to it. The unique identifier is termed the <em class="firstterm">volume key</em>. The format of this volume key varies upon the storage used.
+ </div><div class="para">
+ When used with block based storage such as LVM, the volume key may follow this format:
+ </div><pre class="screen">c3pKz4-qPVc-Xf7M-7WNM-WJc8-qSiz-mtvpGn</pre><div class="para">
+ When used with file based storage, the volume key may instead be a copy of the full path to the volume storage.
+ </div><pre class="screen">/images/secondimage.img</pre><div class="para">
+ For example, a volume with the volume key of <em class="replaceable"><code>Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr</code></em>:
+ </div><pre class="screen"># virsh vol-info Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr
+Name: <em class="replaceable"><code>firstimage</code></em>
+Type: block
+Capacity: 20.00 GB
+Allocation: 20.00 GB
+</pre></dd></dl></div><div class="para">
+ <code class="command">virsh</code> provides commands for converting between a volume name, volume path, or volume key:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> vol-name </span></dt><dd><div class="para">
+ Returns the volume name when provided with a volume path or volume key.
+ </div><pre class="screen"># virsh vol-name /dev/<em class="replaceable"><code>guest_images</code></em>/<em class="replaceable"><code>firstimage</code></em>
+<em class="replaceable"><code>firstimage</code></em>
+# virsh vol-name <em class="replaceable"><code>Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr</code></em></pre></dd><dt class="varlistentry"><span class="term">vol-path</span></dt><dd><div class="para">
+ Returns the volume path when provided with a volume key, or a storage pool identifier and volume name.
+ </div><pre class="screen"># virsh vol-path Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr
+/dev/<em class="replaceable"><code>guest_images</code></em>/<em class="replaceable"><code>firstimage</code></em>
+# virsh vol-path --pool <em class="replaceable"><code>guest_images</code></em> <em class="replaceable"><code>firstimage</code></em>
+/dev/<em class="replaceable"><code>guest_images</code></em>/<em class="replaceable"><code>firstimage</code></em></pre></dd><dt class="varlistentry"><span class="term">The vol-key command</span></dt><dd><div class="para">
+ Returns the volume key when provided with a volume path, or a storage pool identifier and volume name.
+ </div><pre class="screen"># virsh vol-key /dev/<em class="replaceable"><code>guest_images</code></em>/<em class="replaceable"><code>firstimage</code></em>
+Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr
+# virsh vol-key --pool <em class="replaceable"><code>guest_images</code></em> <em class="replaceable"><code>firstimage</code></em>
+Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr
+</pre></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Storage_Concepts.html"><strong>Prev</strong>Chapter 26. Storage concepts</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_Administration_Guide-Storage_Pools-Storage_Pools.html"><strong>Next</strong>Chapter 27. Storage pools</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Storage_Volumes-Cloning_volumes.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Storage_Volumes-Cloning_volumes.html
new file mode 100644
index 0000000..9340ae5
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Storage_Volumes-Cloning_volumes.html
@@ -0,0 +1,36 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>28.2. Cloning volumes</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Storage_Volumes.html" title="Chapter 28. Volumes" /><link rel="prev" href="chap-Virtualization_Administration_Guide-Storage_Volumes.html" title="Chapter 28. Volumes" /><link rel="next" href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html" title="28.3. Adding storage devices to guests" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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_Administration_Guide-Storage_Volumes.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Storage_Volumes-Cloning_volumes"><div class="titlepage"><div><div><h2 class="title">28.2. Cloning volumes</h2></div></div></div><div class="para">
+ The new volume will be allocated from storage in the same storage pool as the volume being cloned. The <code class="command"> virsh vol-clone</code> must have the <code class="literal">--pool</code> argument which dictates the name of the storage pool that contains the volume to be cloned. The rest of the command names the volume to be cloned (volume3) and the name of the new volume that was cloned (clone1). The <code class="command">virsh vol-list</code> command lists the volumes that are present in the storage pool (guest_images_disk).
+ </div><pre class="screen"># virsh vol-clone --pool <em class="replaceable"><code>guest_images_disk</code></em> <em class="replaceable"><code>volume3</code></em> <em class="replaceable"><code>clone1</code></em>
+Vol clone1 cloned from volume3
+
+# <code class="command">virsh vol-list <em class="replaceable"><code>guest_images_disk</code></em></code>
+Name Path
+-----------------------------------------
+volume1 /dev/sdb1
+volume2 /dev/sdb2
+volume3 /dev/sdb3
+clone1 /dev/sdb4
+
+
+# <code class="command">parted -s <em class="replaceable"><code>/dev/sdb</code></em> print</code>
+Model: ATA ST3500418AS (scsi)
+Disk /dev/sdb: 500GB
+Sector size (logical/physical): 512B/512B
+Partition Table: msdos
+
+Number Start End Size File system Name Flags
+1 4211MB 12.8GB 8595MB primary
+2 12.8GB 21.4GB 8595MB primary
+3 21.4GB 30.0GB 8595MB primary
+4 30.0GB 38.6GB 8595MB primary
+
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Storage_Volumes.html"><strong>Prev</strong>Chapter 28. Volumes </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-Virtualized_block_devices-Adding_storage_devices_to_guests.html"><strong>Next</strong>28.3. Adding storage devices to guests</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Storage_Volumes-Deleting_volumes.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Storage_Volumes-Deleting_volumes.html
new file mode 100644
index 0000000..c076714
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Storage_Volumes-Deleting_volumes.html
@@ -0,0 +1,15 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>28.4. Deleting and removing volumes</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Storage_Volumes.html" title="Chapter 28. Volumes" /><link rel="prev" href="sect-Managing_storage_controllers_in_a_guest.html" title="28.3.3. Managing storage controllers in a guest" /><link rel="next" href="vhostmd.html" title="Chapter 29. The Virtual Host Metrics Daemon (vhostmd)" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="pre
vious"><a accesskey="p" href="sect-Managing_storage_controllers_in_a_guest.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="vhostmd.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Storage_Volumes-Deleting_volumes"><div class="titlepage"><div><div><h2 class="title">28.4. Deleting and removing volumes</h2></div></div></div><div class="para">
+ This section shows how to delete a disk volume from a block based storage pool using the <code class="command">virsh vol-delete</code> command. In this example, the volume is <em class="replaceable"><code>volume 1</code></em> and the storage pool is <em class="replaceable"><code>guest_images</code></em>.
+ </div><pre class="screen">
+# virsh vol-delete --pool guest_images volume1
+Vol volume1 deleted
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Managing_storage_controllers_in_a_guest.html"><strong>Prev</strong>28.3.3. Managing storage controllers in a 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="vhostmd.html"><strong>Next</strong>Chapter 29. The Virtual Host Metrics Daemon (vhos...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server.html
new file mode 100644
index 0000000..3742759
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server.html
@@ -0,0 +1,16 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.9. Configuring a VNC Server</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html" title="25.8. Disable SMART disk monitoring for guests" /><link rel="next" href="sect-gracefully-shut-down-guests.html" title="25.10. Gracefully shutting down guests" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" al
t="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-gracefully-shut-down-guests.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server"><div class="titlepage"><div><div><h2 class="title">25.9. 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">
+ Use the following step set up a dedicated VNC server session:
+ </div><div class="para">
+ If needed, Create and then 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. For more information on vnc server files refer to the <em class="citetitle">Fedora Installation Guide</em>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html"><strong>Prev</strong>25.8. 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-gracefully-shut-down-guests.html"><strong>Next</strong>25.10. Gracefully shutting down guests</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html
new file mode 100644
index 0000000..3a266de
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html
@@ -0,0 +1,14 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.8. Disable SMART disk monitoring for guests</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="ch25s07.html" title="25.7. Improving guest response time" /><link rel="next" href="sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server.html" title="25.9. Configuring a VNC Server" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li clas
s="previous"><a accesskey="p" href="ch25s07.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests"><div class="titlepage"><div><div><h2 class="title">25.8. Disable SMART disk monitoring for guests</h2></div></div></div><div class="para">
+ SMART disk monitoring can be safely disabled as virtual disks and the physical storage devices are managed by the host.
+ </div><pre class="screen"># service smartd stop
+# chkconfig --del smartd
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch25s07.html"><strong>Prev</strong>25.7. Improving guest response time</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-Tips_and_tricks-Configuring_a_VNC_Server.html"><strong>Next</strong>25.9. Configuring a VNC Server</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address.html
new file mode 100644
index 0000000..b86aced
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address.html
@@ -0,0 +1,41 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.6. Generating a new unique MAC address</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="ch25s05.html" title="25.5. Setting KVM processor affinities" /><link rel="next" href="ch25s07.html" title="25.7. Improving guest response time" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch25s05.h
tml"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch25s07.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address"><div class="titlepage"><div><div><h2 class="title">25.6. Generating a new unique MAC address</h2></div></div></div><div class="para">
+ In some cases you will need to generate a new and unique MAC address 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</pre><pre class="screen">#!/usr/bin/python
+# macgen.py script to generate a MAC address for guests
+#
+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" id="form-Virtualization-Generating_a_new_unique_MAC_address-Another_method_to_generate_a_new_MAC_for_your_guest"><h5 class="formalpara">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="ch25s05.html"><strong>Prev</strong>25.5. Setting KVM 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="ch25s07.html"><strong>Next</strong>25.7. Improving guest response time</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers.html
new file mode 100644
index 0000000..b542eb0
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers.html
@@ -0,0 +1,156 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.11. Virtual machine timer management with libvirt</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="sect-gracefully-shut-down-guests.html" title="25.10. Gracefully shutting down guests" /><link rel="next" href="sect-perf-mon.html" title="25.12. Using PMU to monitor guest performance" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="p
revious"><a accesskey="p" href="sect-gracefully-shut-down-guests.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-perf-mon.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers"><div class="titlepage"><div><div><h2 class="title">25.11. Virtual machine timer management with libvirt</h2></div></div></div><div class="para">
+ Accurate time keeping on guests is a key challenge for virtualization platforms. Different hypervisors attempt to handle the problem of time keeping in a variety of ways. Libvirt provides hypervisor independent configuration settings for time management, using the <clock> and <timer> elements in the domain XML. The domain XML can be edited using the <code class="command">virsh edit</code> command. See <a class="xref" href="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html#form-Virtualization-Managing_guests_with_virsh-Editing_a_guests_configuration_file">Editing a guest's configuration file</a> for details.
+ </div><div class="formalpara"><h5 class="formalpara" id="idp9830976"><clock></h5>
+ The clock element is used to determine how the guest clock is synchronized with the host clock. The clock element has the following attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idp28599104">offset</h5>
+ Determines how the guest clock is offset from the host clock. The offset attribute has the following possible values:
+ </div><div class="table" id="clock_element_offset_attribute_values"><h6>Table 25.1. Offset attribute values</h6><div class="table-contents"><table summary="Offset attribute values" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Value
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ utc
+ </td><td class="">
+ The guest clock will be synchronized to UTC when booted.
+ </td></tr><tr><td class="">
+ localtime
+ </td><td class="">
+ The guest clock will be synchronized to the host's configured timezone when booted, if any.
+ </td></tr><tr><td class="">
+ timezone
+ </td><td class="">
+ The guest clock will be synchronized to a given timezone, specified by the <em class="parameter"><code>timezone</code></em> attribute.
+ </td></tr><tr><td class="">
+ variable
+ </td><td class="">
+ The guest clock will be synchronized to an arbitrary offset from UTC. The delta relative to UTC is specified in seconds, using the <em class="parameter"><code>adjustment</code></em> attribute. The guest is free to adjust the Real Time Clock (RTC) over time and expect that it will be honored following the next reboot. This is in contrast to <em class="parameter"><code>utc</code></em> mode, where any RTC adjustments are lost at each reboot.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The value <span class="bold bold"><strong>utc</strong></span> is set as the clock offset in a virtual machine by default. However, if the guest clock is run with the <span class="bold bold"><strong>localtime</strong></span> value, the clock offset needs to be changed to a different value in order to have the guest clock synchronized with the host clock.
+ </div></div></div></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idp9835600">timezone</h5>
+ The timezone to which the guest clock is to be synchronized.
+ </div></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idp9837488">adjustment</h5>
+ The delta for guest clock synchronization. In seconds, relative to UTC.
+ </div></li></ul></div><div class="example"><h6>Example 25.1. Always synchronize to UTC</h6><div class="example-contents"><pre class="screen"><clock offset="utc" /></pre></div></div><br class="example-break" /><div class="example"><h6>Example 25.2. Always synchronize to the host timezone</h6><div class="example-contents"><pre class="screen"><clock offset="localtime" /></pre></div></div><br class="example-break" /><div class="example"><h6>Example 25.3. Synchronize to an arbitrary timezone</h6><div class="example-contents"><pre class="screen"><clock offset="timezone" timezone="Europe/Paris" /></pre></div></div><br class="example-break" /><div class="example"><h6>Example 25.4. Synchronize to UTC + arbitrary offset</h6><div class="example-contents"><pre class="screen"><clock offset="variable" adjustment="123456" /></pre></div></div><br class="example-break" /><div class="formalpara"><h5 class="formalpara" id="idm18263056"><timer></h5>
+ A clock element can have zero or more timer elements as children. The timer element specifies a time source used for guest clock synchronization. The timer element has the following attributes. Only the <em class="parameter"><code>name</code></em> is required, all other attributes are optional.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm18260336">name</h5>
+ The name of the time source to use.
+ </div><div class="table" id="timer_element_name_attribute_values"><h6>Table 25.2. name attribute values</h6><div class="table-contents"><table summary="name attribute values" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Value
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ platform
+ </td><td class="">
+ The master virtual time source which may be used to drive the policy of other time sources.
+ </td></tr><tr><td class="">
+ pit
+ </td><td class="">
+ Programmable Interval Timer - a timer with periodic interrupts.
+ </td></tr><tr><td class="">
+ rtc
+ </td><td class="">
+ Real Time Clock - a continuously running timer with periodic interrupts.
+ </td></tr><tr><td class="">
+ hpet
+ </td><td class="">
+ High Precision Event Timer - multiple timers with periodic interrupts.
+ </td></tr><tr><td class="">
+ tsc
+ </td><td class="">
+ Time Stamp Counter - counts the number of ticks since reset, no interrupts.
+ </td></tr><tr><td class="">
+ kvmclock
+ </td><td class="">
+ KVM clock - recommended clock source for KVM guests. KVM pvclock, or kvm-clock lets guests read the host’s wall clock time.
+ </td></tr></tbody></table></div></div><br class="table-break" /></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idp2298656">track</h5>
+ The <span class="emphasis"><em>track</em></span> attribute specifies what is tracked by the timer. Only valid for a name value of <em class="parameter"><code>platform</code></em> or <em class="parameter"><code>rtc</code></em>.
+ </div><div class="table" id="timer_element_track_attribute_values"><h6>Table 25.3. track attribute values</h6><div class="table-contents"><table summary="track attribute values" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Value
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ boot
+ </td><td class="">
+ Corresponds to old <span class="emphasis"><em>host</em></span> option, this is an unsupported tracking option.
+ </td></tr><tr><td class="">
+ guest
+ </td><td class="">
+ RTC always tracks guest time.
+ </td></tr><tr><td class="">
+ wall
+ </td><td class="">
+ RTC always tracks host time.
+ </td></tr></tbody></table></div></div><br class="table-break" /></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idp1930320">tickpolicy</h5>
+ The policy used to pass ticks on to the guest.
+ </div><div class="table" id="timer_element_policy_attribute_values"><h6>Table 25.4. tickpolicy attribute values</h6><div class="table-contents"><table summary="tickpolicy attribute values" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Value
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ delay
+ </td><td class="">
+ Continue to deliver at normal rate (i.e. ticks are delayed).
+ </td></tr><tr><td class="">
+ catchup
+ </td><td class="">
+ Deliver at a higher rate to catch up.
+ </td></tr><tr><td class="">
+ merge
+ </td><td class="">
+ Ticks merged into one single tick.
+ </td></tr><tr><td class="">
+ discard
+ </td><td class="">
+ All missed ticks are discarded.
+ </td></tr></tbody></table></div></div><br class="table-break" /></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idp2290576">frequency</h5>
+ Used to set a fixed frequency, measured in Hz. This attribute is only relevant for a name value of <em class="parameter"><code>tsc</code></em>. All other timers operate at a fixed frequency (<em class="parameter"><code>pit</code></em>, <em class="parameter"><code>rtc</code></em>), or at a frequency fully controlled by the guest (<em class="parameter"><code>hpet</code></em>).
+ </div></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idp18561152">mode</h5>
+ Determines how the time source is exposed to the guest. This attribute is only relevant for a name value of <em class="parameter"><code>tsc</code></em>. All other timers are always emulated. Command is as follows: <code class="command"><timer name='tsc' frequency='NNN' mode='auto|native|emulate|smpsafe'/></code>. Mode definitions are given in the table.
+ </div><div class="table" id="timer_element_mode_attribute_values"><h6>Table 25.5. mode attribute values</h6><div class="table-contents"><table summary="mode attribute values" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Value
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ auto
+ </td><td class="">
+ Native if TSC is unstable, otherwise allow native TSC access.
+ </td></tr><tr><td class="">
+ native
+ </td><td class="">
+ Always allow native TSC access.
+ </td></tr><tr><td class="">
+ emulate
+ </td><td class="">
+ Always emulate TSC.
+ </td></tr><tr><td class="">
+ smpsafe
+ </td><td class="">
+ Always emulate TSC and interlock SMP
+ </td></tr></tbody></table></div></div><br class="table-break" /></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idp15894864">present</h5>
+ Used to override the default set of timers visible to the guest. For example, to enable or disable the HPET.
+ </div><div class="table" id="timer_element_present_attribute_values"><h6>Table 25.6. present attribute values</h6><div class="table-contents"><table summary="present attribute values" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Value
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ yes
+ </td><td class="">
+ Force this timer to the visible to the guest.
+ </td></tr><tr><td class="">
+ no
+ </td><td class="">
+ Force this timer to not be visible to the guest.
+ </td></tr></tbody></table></div></div><br class="table-break" /></li></ul></div><div class="example"><h6>Example 25.5. Clock synchronizing to local time with RTC and PIT timers, and the HPET timer disabled</h6><div class="example-contents"><pre class="screen"><clock offset="localtime">
+ <timer name="rtc" tickpolicy="catchup" track="guest" />
+ <timer name="pit" tickpolicy="delay" />
+ <timer name="hpet" present="no" />
+</clock></pre></div></div><br class="example-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-gracefully-shut-down-guests.html"><strong>Prev</strong>25.10. Gracefully shutting down 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-perf-mon.html"><strong>Next</strong>25.12. Using PMU to monitor guest performance</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM.html
new file mode 100644
index 0000000..884232d
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM.html
@@ -0,0 +1,44 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 22. Overcommitting with KVM</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt02.html" title="Part II. Administration" /><link rel="prev" href="sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes.html" title="21.3. Transport modes" /><link rel="next" href="chap-KSM.html" title="Chapter 23. KSM" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-Remote_management_of_virtualize
d_guests-Transport_modes.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-KSM.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 22. 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 a number of system resources, with the net effect of less power, cooling, and investment in server hardware.
+ </div><div class="formalpara" id="form-Virtualization-Overcommitting_with_KVM-Overcommitting_memory"><h5 class="formalpara">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. KVM can allocate more memory for guests than the host has physically available. Overcommitting requires sufficient swap space for all guests and all host processes.
+ </div><div class="para">
+ With KVM, virtual machines are Linux processes. Guests on the KVM hypervisor do not have dedicated blocks of physical RAM assigned to them, instead guests function as Linux processes. The Linux kernel allocates each process memory when the process requests more memory. KVM guests are allocated memory when requested by the guest operating system.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Ensure that the total sum of swap and memory space is greater than or equal to all the memory configured for running guests. A shortage less than this sum can cause a guest to be forcibly shut down.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="idm2126704">Configuring swap for overcommitting memory</h5>
+ 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 the physical RAM of the host.
+ </div><div class="para">
+ Red Hat <a href="http://kbase.redhat.com/faq/docs/DOC-15252">Knowledgebase</a> has an article on safely and efficiently determining the size of the swap partition.
+ </div><div class="para">
+ The swap partition must be large enough to provide virtual memory for all guests and the host system.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The example below is provided as a guide for configuring swap only. The settings listed may not be appropriate for your environment.
+ </div></div></div><div class="example"><h6>Example 22.1. Memory overcommit example</h6><div class="example-contents"><div class="para">
+ ExampleServer1 has 32GB of physical RAM. The system is being configured to run 56 guests, each with 1GB of virtualized memory. The host system itself needs a maximum of 3GB (apart from the guests).
+ </div><div class="para">
+ The total maximum memory consumption is 56GB + 3GB = 59GB. The system's physical RAM is 32GB, which leaves 27GB. Therefore, the minimum amount of swap that the host should have configured is 27GB.
+ </div></div></div><br class="example-break" /><div class="para">
+ It is possible to overcommit memory over ten times the amount of physical RAM in the system. This only works with certain types of guest, for example, desktop virtualization with minimal intensive usage or running several identical guests with KSM. Configuring swap and memory overcommit is not a formula, each environment and setup is different. Your environment must be tested and customized to ensure stability and performance.
+ </div><div class="para">
+ For more information on KSM and overcommitting, refer to <a class="xref" href="chap-KSM.html">Chapter 23, <em>KSM</em></a>.
+ </div><div class="formalpara" id="form-Virtualization-Overcommitting_with_KVM-Overcommitting_virtualized_CPUs"><h5 class="formalpara">Overcommitting virtualized CPUs</h5>
+ The KVM hypervisor supports overcommitting virtualized CPUs. Virtualized CPUs can be overcommitted as far as load limits of 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 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 five VCPUs. Overcommitting single VCPU 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 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"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><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></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes.html"><strong>Prev</strong>21.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-KSM.html"><strong>Next</strong>Chapter 23. KSM</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Using_qemu_img.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Using_qemu_img.html
new file mode 100644
index 0000000..4f2b867
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Using_qemu_img.html
@@ -0,0 +1,103 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.3. Using qemu-img</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="sect-mem-dump-off.html" title="25.2. Guest memory allocation" /><link rel="next" href="sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions.html" title="25.4. Verifying virtualization extensions" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><
ul class="docnav"><li class="previous"><a accesskey="p" href="sect-mem-dump-off.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Tips_and_tricks-Using_qemu_img"><div class="titlepage"><div><div><h2 class="title">25.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, modifying and verifying various file systems used by KVM. <code class="command">qemu-img</code> options and usages are listed below.
+ </div><div class="formalpara"><h5 class="formalpara" id="idp4056304">Check</h5>
+ Perform a consistency check on the disk image <em class="replaceable"><code>filename</code></em>.
+ </div><pre class="screen">
+# qemu-img check [-f <em class="parameter"><code>format</code></em>] <em class="replaceable"><code>filename</code></em></pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Only the <em class="replaceable"><code>qcow2</code></em> and <em class="replaceable"><code>vdi</code></em> formats support consistency checks.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="idp28448032">Commit</h5>
+ Commit any changes recorded in the specified file (<em class="replaceable"><code>filename</code></em>) to the file's base image with the <code class="command">qemu-img commit</code> command. Optionally, specify the file's format type (<em class="replaceable"><code>fmt</code></em>).
+ </div><pre class="screen"> # qemu-img commit [-f <em class="parameter"><code>fmt</code></em>] [-t <em class="parameter"><code>cache</code></em>] <em class="replaceable"><code>filename</code></em>
+</pre><div class="formalpara" id="form-Virtualization-Using_qemu_img-Convert_an_existing_image_to_another_format"><h5 class="formalpara">Convert</h5>
+ The <em class="parameter"><code>convert</code></em> option is used to convert one recognized image format to another image format.
+ </div><div class="para">
+ Command format:
+ </div><pre class="screen"># qemu-img convert [-c] [-p] [-f <em class="parameter"><code>fmt</code></em>] [-t <em class="parameter"><code>cache</code></em>] [-O <em class="parameter"><code>output_fmt</code></em>] [-o <em class="parameter"><code>options</code></em>] [-S <em class="parameter"><code>sparse_size</code></em>] <em class="replaceable"><code>filename</code></em> <em class="replaceable"><code>output_filename</code></em></pre><div class="para">
+ The <em class="parameter"><code>-p</code></em> parameter shows the progress of the command (optional and not for every command) and <em class="parameter"><code>-S</code></em> indicates the consecutive number of bytes that must contain only zeros for <code class="command">qemu-img</code> to create a sparse image during conversion.
+ </div><div class="para">
+ Convert the disk image <em class="parameter"><code>filename</code></em> to disk image <em class="parameter"><code>output_filename</code></em> using format <em class="parameter"><code>output_format</code></em>. The disk image can be optionally compressed with the <em class="parameter"><code>-c</code></em> option, or encrypted with the <em class="parameter"><code>-o</code></em> option by setting <code class="code">-o encryption</code>. Note that the options available with the <em class="parameter"><code>-o</code></em> parameter differ with the selected format.
+ </div><div class="para">
+ Only the <code class="filename">qcow2</code> format supports encryption or compression. <code class="filename">qcow2</code> encryption uses the AES format with secure 128-bit keys. <code class="filename">qcow2</code> compression is read-only, so if a compressed sector is converted from <code class="filename">qcow2</code> format, it is written to the new format as uncompressed data.
+ </div><div class="para">
+ Image conversion is also useful to get a 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" id="form-Virtualization-Using_qemu_img-Formatting_and_creating_new_images_or_devices"><h5 class="formalpara">Create</h5>
+ Create the new disk image <em class="replaceable"><code>filename</code></em> of size <em class="parameter"><code>size</code></em> and format <em class="parameter"><code>format</code></em>.
+ </div><pre class="screen"># qemu-img create [-f <em class="parameter"><code>format</code></em>] [-o <em class="replaceable"><code>options</code></em>] <em class="replaceable"><code>filename</code></em> [<em class="parameter"><code>size</code></em>]
+</pre><div class="para">
+ If a base image is specified with <code class="code">-o backing_file=<em class="replaceable"><code>filename</code></em></code>, the image will only record differences between itself and the base image. The backing file will not be modified unless you use the <code class="command">commit</code> command. No size needs to be specified in this case.
+ </div><div class="formalpara" id="form-Virtualization-Using_qemu_img-getting_image_information"><h5 class="formalpara">Info</h5>
+ The <code class="command">info</code> parameter displays information about a disk image <em class="replaceable"><code>filename</code></em>. The format for the <code class="command">info</code> option is as follows:
+ </div><pre class="screen"># qemu-img info [-f <em class="replaceable"><code>format</code></em>] <em class="replaceable"><code>filename</code></em></pre><div class="para">
+ This command is often used to discover the size reserved on disk which can be different from the displayed size. If snapshots are stored in the disk image, they are displayed also.
+ </div><div class="formalpara"><h5 class="formalpara" id="idp4056880">Rebase</h5>
+ Changes the backing file of an image.
+ </div><pre class="screen">
+# qemu-img rebase [-f <em class="replaceable"><code>fmt</code></em>] [-t <em class="replaceable"><code>cache</code></em>] [-p] [-u] -b <em class="replaceable"><code>backing_file</code></em> [-F <em class="replaceable"><code>backing_fmt</code></em>] <em class="replaceable"><code>filename</code></em></pre><div class="para">
+ The backing file is changed to <em class="replaceable"><code>backing_file</code></em> and (if the format of <em class="replaceable"><code>filename</code></em> supports the feature), the backing file format is changed to <em class="replaceable"><code>backing_format</code></em>.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Only the <em class="replaceable"><code>qcow2</code></em> format supports changing the backing file (rebase).
+ </div></div></div><div class="para">
+ There are two different modes in which <em class="replaceable"><code>rebase</code></em> can operate: <span class="bold bold"><strong>Safe</strong></span> and <span class="bold bold"><strong>Unsafe</strong></span>.
+ </div><div class="para">
+ <span class="bold bold"><strong>Safe mode</strong></span> is used by default and performs a real rebase operation. The new backing file may differ from the old one and the <code class="command">qemu-img rebase</code> command will take care of keeping the guest-visible content of <em class="replaceable"><code>filename</code></em> unchanged. In order to achieve this, any clusters that differ between <em class="replaceable"><code>backing_file</code></em> and old backing file of <em class="replaceable"><code>filename</code></em> are merged into <em class="replaceable"><code>filename</code></em> before making any changes to the backing file.
+ </div><div class="para">
+ Note that safe mode is an expensive operation, comparable to converting an image. The old backing file is required for it to complete successfully.
+ </div><div class="para">
+ <span class="bold bold"><strong>Unsafe mode</strong></span> is used if the <em class="replaceable"><code>-u</code></em> option is passed to <code class="command">qemu-img rebase</code>. In this mode, only the backing file name and format of <em class="replaceable"><code>filename</code></em> is changed, without any checks taking place on the file contents. Make sure the new backing file is specified correctly or the guest-visible content of the image will be corrupted.
+ </div><div class="para">
+ This mode is useful for renaming or moving the backing file. It can be used without an accessible old backing file. For instance, it can be used to fix an image whose backing file has already been moved or renamed.
+ </div><div class="formalpara"><h5 class="formalpara" id="idp1359504">Resize</h5>
+ Change the disk image <em class="replaceable"><code>filename</code></em> as if it had been created with size <em class="replaceable"><code>size</code></em>. Only images in raw format can be resized regardless of version. Fedora 17 and later adds the ability to grow (but not shrink) images in qcow2 format.
+ </div><div class="para">
+ Use the following to set the size of the disk image <em class="replaceable"><code>filename</code></em> to <em class="replaceable"><code>size</code></em> bytes:
+ </div><pre class="screen"># qemu-img resize <em class="replaceable"><code>filename</code></em> <em class="replaceable"><code>size</code></em></pre><div class="para">
+ You can also resize relative to the current size of the disk image. To give a size relative to the current size, prefix the number of bytes with <code class="literal">+</code> to grow, or <code class="literal">-</code> to reduce the size of the disk image by that number of bytes. Adding a unit suffix allows you to set the image size in kilobytes (K), megabytes (M), gigabytes (G) or terabytes (T).
+ </div><pre class="screen"># qemu-img resize <em class="replaceable"><code>filename</code></em> [+|-]<em class="replaceable"><code>size</code></em>[K|M|G|T]</pre><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Before using this command to shrink a disk image, you <span class="emphasis"><em>must</em></span> use file system and partitioning tools inside the VM itself to reduce allocated file systems and partition sizes accordingly. Failure to do so will result in data loss.
+ </div><div class="para">
+ After using this command to grow a disk image, you must use file system and partitioning tools inside the VM to actually begin using the new space on the device.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="idp6931664">Snapshot</h5>
+ List, apply, create, or delete an existing snapshot (<em class="replaceable"><code>snapshot</code></em>) of an image (<em class="replaceable"><code>filename</code></em>).
+ </div><pre class="screen"># qemu-img snapshot [ -l | -a <em class="replaceable"><code>snapshot</code></em> | -c <em class="replaceable"><code>snapshot</code></em> | -d <em class="replaceable"><code>snapshot</code></em> ] <em class="replaceable"><code>filename</code></em>
+</pre><div class="para">
+ <code class="command">-l</code> lists all snapshots associated with the specified disk image. The apply option, <code class="command">-a</code>, reverts the disk image (<em class="replaceable"><code>filename</code></em>) to the state of a previously saved <em class="replaceable"><code>snapshot</code></em>. <code class="command">-c</code> creates a snapshot (<em class="replaceable"><code>snapshot</code></em>) of an image (<em class="replaceable"><code>filename</code></em>). <code class="command">-d</code> deletes the specified snapshot.
+ </div><div class="formalpara" id="form-Virtualization-Using_qemu_img-Supported_formats"><h5 class="formalpara">Supported formats</h5>
+ <span class="application"><strong>qemu-img</strong></span> is designed to convert files to one of the following formats:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="command">raw</code> </span></dt><dd><div class="para">
+ Raw disk image format (default). This can be the fastest file-based format. 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 obtain the real size used by the image or <code class="command">ls -ls</code> on Unix/Linux. Although Raw images give optimal performance, only very basic features are available with a Raw image (no snapshots etc.).
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">qcow2</code> </span></dt><dd><div class="para">
+ QEMU image format, the most versatile format with the best feature set. Use it to have optional AES encryption, zlib-based compression, support of multiple VM snapshots, and smaller images, which are useful on file systems that do not support holes (non-NTFS file systems on Windows). Note that this expansive feature set comes at the cost of performance.
+ </div></dd></dl></div><div class="para">
+ Although only the formats above can be used to run on a guest or host machine, <span class="application"><strong>qemu-img</strong></span> also recognizes and supports the following formats in order to convert from them into either <code class="command">raw</code> or <code class="command">qcow2</code> format. The format of an image is usually detected automatically. In addition to converting these formats into <code class="command">raw</code> or <code class="command">qcow2</code> , they can be converted back from <code class="command">raw</code> or <code class="command">qcow2</code> to the original format.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="command">bochs</code></span></dt><dd><div class="para">
+ Bochs disk image format.
+ </div></dd><dt class="varlistentry"><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><dt class="varlistentry"><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 class="varlistentry"><span class="term"><code class="command">dmg</code></span></dt><dd><div class="para">
+ Mac disk image format.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">nbd</code></span></dt><dd><div class="para">
+ Network block device.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">parallels</code></span></dt><dd><div class="para">
+ Parallels virtualization disk image format.
+ </div></dd><dt class="varlistentry"><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 class="varlistentry"><span class="term"><code class="command">vdi</code></span></dt><dd><div class="para">
+ Oracle VM VirtualBox hard disk image format.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">vmdk</code></span></dt><dd><div class="para">
+ VMware 3 and 4 compatible image format.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">vpc</code></span></dt><dd><div class="para">
+ Windows Virtual PC disk image format. Also referred to as <code class="literal">vhd</code>, or Microsoft virtual hard disk image format.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">vvfat</code></span></dt><dd><div class="para">
+ Virtual VFAT disk image format.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-mem-dump-off.html"><strong>Prev</strong>25.2. Guest memory allocation</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-Tips_and_tricks-Verifying_virtualization_extensions.html"><strong>Next</strong>25.4. Verifying virtualization extensions</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions.html
new file mode 100644
index 0000000..45a8a83
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions.html
@@ -0,0 +1,39 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.4. Verifying virtualization extensions</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="sect-Virtualization-Tips_and_tricks-Using_qemu_img.html" title="25.3. Using qemu-img" /><link rel="next" href="ch25s05.html" title="25.5. Setting KVM processor affinities" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a a
ccesskey="p" href="sect-Virtualization-Tips_and_tricks-Using_qemu_img.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch25s05.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions"><div class="titlepage"><div><div><h2 class="title">25.4. 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-x or AMD-V) are required for full virtualization.
+ </div><div class="procedure"><ol class="1"><li class="step"><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></li><li class="step"><div class="para">
+ Analyze the output.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The following output contains a <code class="computeroutput">vmx</code> entry indicating an Intel processor with the Intel VT-x extension:
+ </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></li><li class="listitem"><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></li></ul></div><div class="para">
+ If any output is received, the processor has the hardware virtualization extensions. However in some circumstances manufacturers disable the virtualization extensions in BIOS.
+ </div><div class="para">
+ The "<code class="computeroutput">flags:</code>" output content may appear multiple times, once for each hyperthread, core or CPU on 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-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html#proc-Virtualization-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS-Enabling_virtualization_extensions_in_BIOS">Procedure A.1, “Enabling virtualization extensions in BIOS”</a>.
+ </div></li><li class="step"><p class="title"><strong>Ensure KVM subsystem is loaded</strong></p><div class="para">
+ As an additional check, verify that the <code class="computeroutput">kvm</code> modules are loaded in the kernel:
+ </div><pre class="screen"># lsmod | grep kvm</pre><div class="para">
+ If the output includes <code class="computeroutput">kvm_intel</code> or <code class="computeroutput">kvm_amd</code> then the <code class="computeroutput">kvm</code> hardware virtualization modules are loaded and your system meets requirements.
+ </div></li></ol></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If the <span class="package">libvirt</span> package is installed, the <code class="command">virsh</code> command can output a full list of virtualization system capabilities. Run <code class="command">virsh capabilities </code> as root to receive the complete list.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Tips_and_tricks-Using_qemu_img.html"><strong>Prev</strong>25.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="ch25s05.html"><strong>Next</strong>25.5. Setting KVM processor affinities</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html
new file mode 100644
index 0000000..0c5cb22
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html
@@ -0,0 +1,36 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.7. Enabling Intel VT-x and AMD-V virtualization hardware extensions in BIOS</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Troubleshooting.html" title="Appendix A. Troubleshooting" /><link rel="prev" href="live-migration-errors.html" title="A.6. Live Migration Errors" /><link rel="next" href="sect-Virtualization-Troubleshooting-KVM_networking_performance.html" title="A.8. KVM networking performance" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous
"><a accesskey="p" href="live-migration-errors.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Troubleshooting-KVM_networking_performance.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS"><div class="titlepage"><div><div><h2 class="title">A.7. Enabling Intel VT-x 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-x extensions can be disabled in the BIOS. Certain laptop vendors have disabled the Intel VT-x extensions by default in their CPUs.
+ </div><div class="para">
+ The virtualization extensions cannot be disabled in the BIOS for AMD-V.
+ </div><div class="para">
+ Refer to the following section for instructions on enabling disabled virtualization extensions.
+ </div><div class="para">
+ Verify the virtualization extensions are enabled in BIOS. The BIOS settings for Intel 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-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS-Enabling_virtualization_extensions_in_BIOS"><h6>Procedure A.1. Enabling virtualization extensions in BIOS</h6><ol class="1"><li class="step"><div class="para">
+ Reboot the computer and open the system's BIOS menu. This can usually be done by pressing the <span class="guibutton"><strong>delete</strong></span> key, the <span class="keycap"><strong>F1</strong></span> key or <span class="keycap"><strong>Alt</strong></span> and <span class="keycap"><strong>F4</strong></span> keys depending on the system.
+ </div></li><li class="step"><p class="title"><strong>Enabling the virtualization extensions in BIOS</strong></p><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Many of the steps below may vary depending on your motherboard, processor type, chipset and OEM. Refer to your system's accompanying documentation for the correct information on configuring your system.
+ </div></div></div><ol class="a"><li class="step"><div class="para">
+ Open the <span class="guilabel"><strong>Processor</strong></span> submenu The processor settings menu may be hidden in the <span class="guilabel"><strong>Chipset</strong></span>, <span class="guilabel"><strong>Advanced CPU Configuration</strong></span> or <span class="guilabel"><strong>Northbridge</strong></span>.
+ </div></li><li class="step"><div class="para">
+ Enable <span class="guilabel"><strong>Intel Virtualization Technology</strong></span> (also known as Intel VT-x). <span class="guilabel"><strong>AMD-V</strong></span> extensions cannot be disabled in the BIOS and should already be enabled. The virtualization extensions may be labeled <span class="guilabel"><strong>Virtualization Extensions</strong></span>, <span class="guilabel"><strong>Vanderpool</strong></span> or various other names depending on the OEM and system BIOS.
+ </div></li><li class="step"><div class="para">
+ Enable Intel VT-d or AMD IOMMU, if the options are available. Intel VT-d and AMD IOMMU are used for PCI device assignment.
+ </div></li><li class="step"><div class="para">
+ Select <span class="guilabel"><strong>Save & Exit</strong></span>.
+ </div></li></ol></li><li class="step"><div class="para">
+ Reboot the machine.
+ </div></li><li class="step"><div class="para">
+ When the machine has booted, run <code class="command">cat /proc/cpuinfo |grep -E "vmx|svm"</code>. Specifying <em class="parameter"><code>--color</code></em> is optional, but useful if you want the search term highlighted. 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="live-migration-errors.html"><strong>Prev</strong>A.6. Live Migration 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-Troubleshooting-KVM_networking_performance.html"><strong>Next</strong>A.8. KVM networking performance</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting-KVM_networking_performance.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting-KVM_networking_performance.html
new file mode 100644
index 0000000..2f43715
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting-KVM_networking_performance.html
@@ -0,0 +1,60 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.8. KVM networking performance</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Troubleshooting.html" title="Appendix A. Troubleshooting" /><link rel="prev" href="sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html" title="A.7. Enabling Intel VT-x and AMD-V virtualization hardware extensions in BIOS" /><link rel="next" href="sect-Virtualization-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard.html" title="A.9. Missing characters on guest console with Japanese keyboard" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" al
t="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-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-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Troubleshooting-KVM_networking_performance"><div class="titlepage"><div><div><h2 class="title">A.8. KVM networking performance</h2></div></div></div><div class="para">
+ By default, KVM virtual machines are assigned a virtual Realtek 8139 (rtl8139) NIC (network interface controller) if they are Windows guests or the guest type is not specified. Fedora guests are assigned a virtio NIC by default.
+ </div><div class="para">
+ The rtl8139 virtualized NIC works fine in most environments. However, this device can suffer from performance degradation problems on some networks, for example, a 10 Gigabit Ethernet network.
+ </div><div class="para">
+ To improve performance switch to the para-virtualized network driver.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Note that the virtualized Intel PRO/1000 (<code class="systemitem">e1000</code>) driver is also supported as an emulated driver choice. To use the <code class="computeroutput">e1000</code> driver, replace <code class="computeroutput">virtio</code> in the procedure below with <code class="computeroutput">e1000</code>. For the best performance it is recommended to use the <code class="computeroutput">virtio</code> driver.
+ </div></div></div><div class="procedure"><h6>Procedure A.2. Switching to the virtio driver</h6><ol class="1"><li class="step"><div class="para">
+ Shutdown the guest operating system.
+ </div></li><li class="step"><div class="para">
+ Edit the guest's configuration file with the <code class="command">virsh</code> command (where <em class="parameter"><code>GUEST</code></em> is the guest's name):
+ </div><pre class="screen"># virsh edit <em class="parameter"><code>GUEST</code></em>
+</pre><div class="para">
+ The <code class="command">virsh edit</code> command uses the <code class="command">$EDITOR</code> shell variable to determine which editor to use.
+ </div></li><li class="step"><div class="para">
+ Find the network interface section of the configuration. This section resembles the snippet below:
+ </div><pre class="screen"><interface type='network'>
+ <span class="emphasis"><em>[output truncated]</em></span>
+ <model type='rtl8139' />
+</interface>
+</pre></li><li class="step"><div class="para">
+ Change the type attribute of the model element from <em class="parameter"><code>'rtl8139'</code></em> to <em class="parameter"><code>'virtio'</code></em>. This will change the driver from the rtl8139 driver to the e1000 driver.
+ </div><pre class="screen"><interface type='network'>
+ <span class="emphasis"><em>[output truncated]</em></span>
+ <model type=<em class="parameter"><code>'virtio'</code></em> />
+</interface>
+</pre></li><li class="step"><div class="para">
+ Save the changes and exit the text editor
+ </div></li><li class="step"><div class="para">
+ Restart the guest operating system.
+ </div></li></ol></div><div class="formalpara"><h5 class="formalpara" id="idp2932992">Creating new guests using other network drivers</h5>
+ Alternatively, new guests can be created with a different network driver. This may be required if you are having difficulty installing guests over a network connection. This method requires you to have at least one guest already created (possibly installed from CD or DVD) to use as a template.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Create an XML template from an existing guest (in this example, named <em class="replaceable"><code>Guest1</code></em>):
+ </div><pre class="screen"># virsh dumpxml <em class="replaceable"><code>Guest1</code></em> > /tmp/<em class="replaceable"><code>guest-template</code></em>.xml
+</pre></li><li class="step"><div class="para">
+ Copy and edit the XML file and update the unique fields: virtual machine name, UUID, disk image, MAC address, and any other unique parameters. Note that you can delete the UUID and MAC address lines and virsh will generate a UUID and MAC address.
+ </div><pre class="screen"># cp /tmp/<em class="replaceable"><code>guest-template</code></em>.xml /tmp/<em class="replaceable"><code>new-guest</code></em>.xml
+# vi /tmp/<em class="replaceable"><code>new-guest</code></em>.xml
+</pre><div class="para">
+ Add the model line in the network interface section:
+ </div><pre class="screen"> <interface type='network'>
+ <span class="emphasis"><em>[output truncated]</em></span>
+ <model type='virtio' />
+</interface>
+</pre></li><li class="step"><div class="para">
+ Create the new virtual machine:
+ </div><pre class="screen"># virsh define /tmp/new-guest.xml
+# virsh start new-guest
+</pre></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html"><strong>Prev</strong>A.7. Enabling Intel VT-x 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-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard.html"><strong>Next</strong>A.9. Missing characters on guest console with Jap...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting-Loop_device_errors.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting-Loop_device_errors.html
new file mode 100644
index 0000000..eda956b
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting-Loop_device_errors.html
@@ -0,0 +1,15 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.5. Loop device errors</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Troubleshooting.html" title="Appendix A. Troubleshooting" /><link rel="prev" href="apas04.html" title="A.4. Virtualization log files" /><link rel="next" href="live-migration-errors.html" title="A.6. Live Migration Errors" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apas04.html"><strong>Prev</strong
></a></li><li class="next"><a accesskey="n" href="live-migration-errors.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Troubleshooting-Loop_device_errors"><div class="titlepage"><div><div><h2 class="title">A.5. 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 eight active loop devices. If more than eight file-based guests or loop devices are needed the number of loop devices configured can be adjusted in the <code class="filename">/etc/modprobe.d/</code>directory. Add the following line:
+ </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 use a 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="apas04.html"><strong>Prev</strong>A.4. Virtualization log 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="live-migration-errors.html"><strong>Next</strong>A.6. Live Migration Errors</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard.html
new file mode 100644
index 0000000..463f3d3
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard.html
@@ -0,0 +1,38 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.9. Missing characters on guest console with Japanese keyboard</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Troubleshooting.html" title="Appendix A. Troubleshooting" /><link rel="prev" href="sect-Virtualization-Troubleshooting-KVM_networking_performance.html" title="A.8. KVM networking performance" /><link rel="next" href="sec-known-issues-windows-xp-guests.html" title="A.10. Known Windows XP guest issues" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docna
v"><li class="previous"><a accesskey="p" href="sect-Virtualization-Troubleshooting-KVM_networking_performance.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-known-issues-windows-xp-guests.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard"><div class="titlepage"><div><div><h2 class="title">A.9. Missing characters on guest console with Japanese keyboard</h2></div></div></div><div class="para">
+ On a Fedora host, connecting a Japanese keyboard locally to a machine may result in typed characters such as the underscore (the <span class="bold bold"><strong>_</strong></span> character) not being displayed correctly in guest consoles. This occurs because the required keymap is not set correctly by default.
+ </div><div class="para">
+ When Using Fedora with Red Hat Enterprise Linux 6 guests, there is usually no error message produced when pressing the associated key. However, Red Hat Enterprise Linux 4 and Red Hat Enterprise Linux 5 guests may display an error similar to the following:
+ </div><pre class="screen">
+atkdb.c: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0).
+atkbd.c: Use 'setkeycodes 00 <keycode>' to make it known.
+</pre><div class="para">
+ To fix this issue in <code class="command">virt-manager</code>, perform the following steps:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Open the affected guest in <code class="command">virt-manager</code>.
+ </div></li><li class="listitem"><div class="para">
+ Click <span class="guimenu"><strong>View</strong></span> → <span class="guisubmenu"><strong>Details</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ Select <span class="guilabel"><strong>Display VNC</strong></span> in the list.
+ </div></li><li class="listitem"><div class="para">
+ Change <span class="bold bold"><strong>Auto</strong></span> to <span class="bold bold"><strong>ja</strong></span> in the <span class="guilabel"><strong>Keymap</strong></span> pull-down menu.
+ </div></li><li class="listitem"><div class="para">
+ Click the <span class="guilabel"><strong>Apply</strong></span> button.
+ </div></li></ul></div><div class="para">
+ Alternatively, to fix this issue using the <code class="command">virsh edit</code> command on the target guest:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Run <code class="command">virsh edit <target guest></code>
+ </div></li><li class="listitem"><div class="para">
+ Add the following attribute to the <graphics> tag: <span class="bold bold"><strong>keymap='ja'</strong></span>. For example:
+<pre class="screen">
+ <graphics type='vnc' port='-1' autoport='yes' <span class="bold bold"><strong>keymap='ja'</strong></span>/>
+</pre>
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Troubleshooting-KVM_networking_performance.html"><strong>Prev</strong>A.8. KVM networking performance</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="sec-known-issues-windows-xp-guests.html"><strong>Next</strong>A.10. Known Windows XP guest issues</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles.html
new file mode 100644
index 0000000..f5ac73e
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles.html
@@ -0,0 +1,38 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.3. Troubleshooting with serial consoles</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Troubleshooting.html" title="Appendix A. Troubleshooting" /><link rel="prev" href="apas02.html" title="A.2. kvm_stat" /><link rel="next" href="apas04.html" title="A.4. Virtualization log files" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apas02.html"><strong>Prev</strong></a></li><li class="next"><
a accesskey="n" href="apas04.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles"><div class="titlepage"><div><div><h2 class="title">A.3. 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 Fedora virtualization kernels and their guests.
+ </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 class="listitem"><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. Append the following to the <em class="parameter"><code>kernel</code></em> line: <em class="parameter"><code>console=tty0 console=ttyS0,115200</code></em>.
+ </div><pre class="screen">title Fedora Server (2.6.32-36.x86-64)
+ root (hd0,0)
+ kernel /vmlinuz-2.6.32-36.x86-64 ro root=/dev/volgroup00/logvol00 \
+ <em class="parameter"><code>console=tty0 console=ttyS0,115200</code></em>
+ initrd /initrd-2.6.32-36.x86-64.img
+</pre><div class="para">
+ Reboot the guest.
+ </div><div class="para">
+ On the host, 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 guest console window, select <span class="guilabel"><strong>Serial 1</strong></span> in <span class="guilabel"><strong>Text Consoles</strong></span> from the <span class="guilabel"><strong>View</strong></span> menu.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apas02.html"><strong>Prev</strong>A.2. kvm_stat</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="apas04.html"><strong>Next</strong>A.4. Virtualization log files</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest.html
new file mode 100644
index 0000000..c858a74
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest.html
@@ -0,0 +1,22 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.8. Attaching a virtual network to a guest</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html" title="Appendix H. Virtual Networking" /><link rel="prev" href="sect-Virtualization-Virtual_Networking-Creating_a_virtual_network.html" title="H.7. Creating a virtual network" /><link rel="next" href="sect-attch-nic-physdev.html" title="H.9. Directly attaching to physical interface" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-Virtual_Networking-Creating_a_virtual_network.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-attch-nic-physdev.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest"><div class="titlepage"><div><div><h2 class="title">H.8. Attaching a virtual network to a guest</h2></div></div></div><div class="para">
+ To attach a virtual network to a guest:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ In the <span class="guilabel"><strong>Virtual Machine Manager</strong></span> window, highlight the guest that will have the network assigned.
+ </div><div class="figure" id="guest4network"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt1.png" width="444" alt="Selecting a virtual machine to display" /></div></div><h6>Figure H.20. Selecting a virtual machine to display</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ From the Virtual Machine Manager <span class="guilabel"><strong>Edit</strong></span> menu, select <span class="guilabel"><strong>Virtual Machine Details</strong></span>.
+ </div><div class="figure" id="showdetails"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt11.png" width="444" alt="Displaying the virtual machine details" /></div></div><h6>Figure H.21. Displaying the virtual machine details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Click the <span class="guilabel"><strong>Add Hardware</strong></span> button on the Virtual Machine Details window.
+ </div><div class="figure" id="vmdetailswindow"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt4.png" width="444" alt="The Virtual Machine Details window" /></div></div><h6>Figure H.22. The Virtual Machine Details window</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ In the <span class="guilabel"><strong>Add new virtual hardware</strong></span> window, select <span class="guilabel"><strong>Network</strong></span> from the left pane, and select your network name (<span class="emphasis"><em>network1</em></span> in this example) from the <span class="guilabel"><strong>Host device</strong></span> menu and click <span class="guibutton"><strong>Finish</strong></span>.
+ </div><div class="figure" id="select_network"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic10.png" width="444" alt="Select your network from the Add new virtual hardware window" /></div></div><h6>Figure H.23. Select your network from the Add new virtual hardware window</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ The new network is now displayed as a virtual network interface that will be presented to the guest upon launch.
+ </div><div class="figure" id="newnetworkishown"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic11.png" width="444" alt="New network shown in guest hardware list" /></div></div><h6>Figure H.24. New network shown in guest hardware list</h6></div><br class="figure-break" /></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Virtual_Networking-Creating_a_virtual_network.html"><strong>Prev</strong>H.7. 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="sect-attch-nic-physdev.html"><strong>Next</strong>H.9. Directly attaching to physical interface</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtual_Networking-Creating_a_virtual_network.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtual_Networking-Creating_a_virtual_network.html
new file mode 100644
index 0000000..3903bc4
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtual_Networking-Creating_a_virtual_network.html
@@ -0,0 +1,32 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.7. Creating a virtual network</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html" title="Appendix H. Virtual Networking" /><link rel="prev" href="sect-Virtualization-Virtual_Networking-Managing_a_virtual_network.html" title="H.6. Managing a virtual network" /><link rel="next" href="sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest.html" title="H.8. Attaching a virtual network to a guest" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-Virtual_Networking-Managing_a_virtual_network.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Virtual_Networking-Creating_a_virtual_network"><div class="titlepage"><div><div><h2 class="title">H.7. 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 class="step"><div class="para">
+ Open the <span class="guilabel"><strong>Virtual Networks</strong></span> tab from within the <span class="guilabel"><strong>Connection Details</strong></span> menu. Click the <span class="guibutton"><strong>Add Network</strong></span> button, identified by a plus sign (+) icon. For more information, refer to <a class="xref" href="sect-Virtualization-Virtual_Networking-Managing_a_virtual_network.html">Section H.6, “Managing a virtual network”</a>.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Virtual_network_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic1.png" width="444" alt="Virtual network configuration" /></div></div><h6>Figure H.13. 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> window. Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Creating_a_new_virtual_network"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic2.png" width="444" alt="Creating a new virtual network" /></div></div><h6>Figure H.14. Creating a new virtual network</h6></div><br class="figure-break" /></li><li class="step"><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_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Naming_your_virtual_network"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic3.png" width="444" alt="Naming your virtual network" /></div></div><h6>Figure H.15. Naming your virtual network</h6></div><br class="figure-break" /></li><li class="step"><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_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Choosing_an_IPv4_address_space"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic4.png" width="444" alt="Choosing an IPv4 address space" /></div></div><h6>Figure H.16. Choosing an IPv4 address space</h6></div><br class="figure-break" /></li><li class="step"><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_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Selecting_the_DHCP_range"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic5.png" width="444" alt="Selecting the DHCP range" /></div></div><h6>Figure H.17. Selecting the DHCP range</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Select how the virtual network should connect to the physical network.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Connecting_to_physical_network"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic6.png" width="444" alt="Connecting to physical network" /></div></div><h6>Figure H.18. 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>Any physical device</strong></span> or a specific physical device. Also select whether the <span class="guilabel"><strong>Mode</strong></span> should be <span class="guilabel"><strong>NAT</strong></span> or <span class="guilabel"><strong>Routed</strong></span>.
+ </div><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><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_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Ready_to_create_network"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic7.png" width="444" alt="Ready to create network" /></div></div><h6>Figure H.19. Ready to create network</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ The new virtual network is now available in the <span class="guilabel"><strong>Virtual Networks</strong></span> tab of the <span class="guilabel"><strong>Connection Details</strong></span> window.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Virtual_Networking-Managing_a_virtual_network.html"><strong>Prev</strong>H.6. 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="sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest.html"><strong>Next</strong>H.8. Attaching a virtual network to a guest</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtual_Networking-Example_scenarios.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtual_Networking-Example_scenarios.html
new file mode 100644
index 0000000..6374837
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtual_Networking-Example_scenarios.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.5. Examples of common scenarios</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html" title="Appendix H. Virtual Networking" /><link rel="prev" href="sect-the-Default_Configuration-libvirt.html" title="H.4. The default configuration" /><link rel="next" href="sub-sect-nat-mode.html" title="H.5.2. NAT mode" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-the-
Default_Configuration-libvirt.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-nat-mode.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Virtual_Networking-Example_scenarios"><div class="titlepage"><div><div><h2 class="title">H.5. Examples of common scenarios</h2></div></div></div><div class="para">
+ This section demonstrates different virtual networking modes and provides some example scenarios.
+ </div><div class="section" id="sub-sect-routed-mode"><div class="titlepage"><div><div><h3 class="title">H.5.1. Routed mode</h3></div></div></div><div class="formalpara"><h5 class="formalpara" id="idm1450480">DMZ</h5>
+ Consider a network where one or more nodes are placed in a controlled subnetwork for security reasons. The deployment of a special subnetwork such as this is a common practice, and the subnetwork is known as a DMZ. Refer to the following diagram for more details on this layout:
+ </div><div class="figure" id="dmz-example-diagram"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-09-routed-mode-DMZ.png" width="444" alt="Sample DMZ configuration" /></div></div><h6>Figure H.8. Sample DMZ configuration</h6></div><br class="figure-break" /><div class="para">
+ Hosts in a DMZ typically provide services to WAN (external) hosts as well as LAN (internal) hosts. As this requires them to be accessible from multiple locations, and considering that these locations are controlled and operated in different ways based on their security and trust level, routed mode is the best configuration for this environment.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm5494192">Virtual Server hosting</h5>
+ Consider a virtual server hosting company that has several hosts, each with two physical network connections. One interface is used for management and accounting, the other is for the virtual machines to connect through. Each guest has its own public IP address, but the hosts use private IP address as management of the guests can only be performed by internal administrators. Refer to the following diagram to understand this scenario:
+ </div><div class="figure" id="virt-serv-host-diagram"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-10-routed-mode-datacenter.png" width="444" alt="Virtual server hosting sample configuration" /></div></div><h6>Figure H.9. Virtual server hosting sample configuration</h6></div><br class="figure-break" /><div class="para">
+ When the host has a public IP address and the virtual machines have static public IP addresses, bridged networking cannot be used, as the provider only accepts packets from the MAC address of the public host. The following diagram demonstrates this:
+ </div><div class="figure" id="static-ip-diagram"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-11-router-mode-mac-restricted.png" width="444" alt="Virtual server using static IP addresses" /></div></div><h6>Figure H.10. Virtual server using static IP addresses</h6></div><br class="figure-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-the-Default_Configuration-libvirt.html"><strong>Prev</strong>H.4. The default 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="sub-sect-nat-mode.html"><strong>Next</strong>H.5.2. NAT mode</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtual_Networking-Managing_a_virtual_network.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtual_Networking-Managing_a_virtual_network.html
new file mode 100644
index 0000000..329e8d9
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtual_Networking-Managing_a_virtual_network.html
@@ -0,0 +1,18 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.6. Managing a virtual network</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html" title="Appendix H. Virtual Networking" /><link rel="prev" href="sub-sect-isolated-mode.html" title="H.5.3. Isolated mode" /><link rel="next" href="sect-Virtualization-Virtual_Networking-Creating_a_virtual_network.html" title="H.7. Creating a virtual network" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="prev
ious"><a accesskey="p" href="sub-sect-isolated-mode.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Virtual_Networking-Creating_a_virtual_network.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Virtual_Networking-Managing_a_virtual_network"><div class="titlepage"><div><div><h2 class="title">H.6. 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 class="step"><div class="para">
+ From the <span class="guilabel"><strong>Edit</strong></span> menu, select <span class="guilabel"><strong>Connection Details</strong></span>.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Selecting_a_hosts_details"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_vnet_menuselect.png" width="444" alt="Selecting a host's details" /></div></div><h6>Figure H.11. Selecting a host's details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ This will open the <span class="guimenu"><strong>Connection Details</strong></span> menu. Click the <span class="guilabel"><strong>Virtual Networks</strong></span> tab.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic1.png" width="444" alt="Virtual network configuration" /></div></div><h6>Figure H.12. Virtual network configuration</h6></div><br class="figure-break" /></li><li class="step"><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="sub-sect-isolated-mode.html"><strong>Prev</strong>H.5.3. Isolated mode</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-Virtual_Networking-Creating_a_virtual_network.html"><strong>Next</strong>H.7. Creating a virtual network</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html
new file mode 100644
index 0000000..bd41007
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html
@@ -0,0 +1,99 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>28.3. Adding storage devices to guests</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Storage_Volumes.html" title="Chapter 28. Volumes" /><link rel="prev" href="sect-Virtualization-Storage_Volumes-Cloning_volumes.html" title="28.2. Cloning volumes" /><link rel="next" href="sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html" title="28.3.2. Adding hard drives and other block devices to a guest" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/image
s/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Storage_Volumes-Cloning_volumes.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests"><div class="titlepage"><div><div><h2 class="title">28.3. Adding storage devices to guests</h2></div></div></div><div class="para">
+ This section covers adding storage devices to a guest. Additional storage can only be added as needed.
+ </div><div class="section" id="sect-Virtualization-Adding_storage_devices_to_guests-Adding_file_based_storage_to_a_guest"><div class="titlepage"><div><div><h3 class="title">28.3.1. Adding file based storage to a guest</h3></div></div></div><div class="para">
+ File-based storage is a collection of files that are stored on the hosts file system that act as virtualized hard drives for guests. To add file-based storage, perform the following steps:
+ </div><div class="procedure" id="proc-Virtualization-Adding_storage_devices"><h6>Procedure 28.1. Adding file-based storage</h6><ol class="1"><li class="step"><div class="para">
+ Create a storage file or use an existing file (such as an ISO file). Note that both of the following commands create a 4GB file which can be used as additional storage for a guest:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Pre-allocated files are recommended for file-based storage images. Create a pre-allocated file using the following <code class="command">dd</code> command as shown:
+ </div><pre class="screen"># dd if=/dev/zero of=/var/lib/libvirt/images/FileName.iso bs=1M count=4096</pre></li><li class="listitem"><div class="para">
+ Alternatively, create a sparse file instead of a pre-allocated file. Sparse files are created much faster and can be used for testing, but are not recommended for production environments due to data integrity and performance issues.
+ </div><pre class="screen"># dd if=/dev/zero of=/var/lib/libvirt/images/FileName.iso bs=1M seek=4096 count=0</pre></li></ul></div></li><li class="step"><div class="para">
+ Create the additional storage by writing a <em class="replaceable"><code><disk></code></em> element in a new file. In this example, this file will be known as <code class="filename">NewStorage.xml</code>.
+ </div><div class="para">
+ A <code class="literal"><disk></code> element describes the source of the disk, and a device name for the virtual block device. The device name should be unique across all devices in the guest, and identifies the bus on which the guest will find the virtual block device. The following example defines a virtio block device whose source is a file-based storage container named <code class="filename">FileName.img</code>:
+ </div><pre class="screen">
+<disk type='file' device='disk'>
+ <driver name='qemu' type='raw' cache='none'/>
+ <source file='/var/lib/libvirt/images/FileName.img'/>
+ <target dev='vdb'/>
+</disk>
+</pre><div class="para">
+ Device names can also start with "hd" or "sd", identifying respectively an IDE and a SCSI disk. The configuration file can also contain an <code class="literal"><address></code> sub-element that specifies the position on the bus for the new device. In the case of virtio block devices, this should be a PCI address. Omitting the <code class="literal"><address></code> sub-element lets libvirt locate and assign the next available PCI slot.
+ </div></li><li class="step"><div class="para">
+ Attach the CD-ROM as follows:
+ </div><pre class="screen">
+<disk type='file' device='cdrom'>
+ <driver name='qemu' type='raw' cache='none'/>
+ <source file='/var/lib/libvirt/images/FileName.iso'/>
+ <readonly/>
+ <target dev='hdc'/>
+</disk >
+</pre></li><li class="step"><div class="para">
+ Add the device defined in <code class="filename">NewStorage.xml</code> with your guest (<code class="literal">Guest1</code>):
+ </div><pre class="screen"># virsh attach-device --config Guest1 ~/NewStorage.xml</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ This change will only apply after the guest has been destroyed and restarted. In addition, persistent devices can only be added to a persistent domain, that is a domain whose configuration has been saved with <code class="command"> virsh define </code> command.
+ </div></div></div><div class="para">
+ If the guest is running, and you want the new device to be added temporarily until the guest is destroyed, omit the <code class="literal">--config</code> option:
+ </div><pre class="screen"># virsh attach-device Guest1 ~/NewStorage.xml</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The <code class="command">virsh</code> command allows for an <code class="command">attach-disk</code> command that can set a limited number of parameters with a simpler syntax and without the need to create an XML file. The <code class="command">attach-disk</code> command is used in a similar manner to the <code class="command">attach-device</code> command mentioned previously, as shown:
+ </div><pre class="screen">
+# virsh attach-disk Guest1 /var/lib/libvirt/images/FileName.iso vdb --cache none
+</pre><div class="para">
+ Note that the <code class="command">virsh attach-disk</code> command also accepts the <code class="literal">--config</code> option.
+ </div></div></div></li><li class="step"><div class="para">
+ Start the guest machine (if it is currently not running):
+ </div><pre class="screen"># virsh start Guest1</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The following steps are Linux guest specific. Other operating systems handle new storage devices in different ways. For other systems, refer to that operating system's documentation.
+ </div></div></div></li><li class="step" id="step-partition_disk"><p class="title"><strong>Partitioning the disk drive</strong></p><div class="para">
+ The guest now has a hard disk device called <code class="filename">/dev/vdb</code>. If required, partition this disk drive and format the partitions. If you do not see the device that you added, then it indicates that there is an issue with the disk hotplug in your guest's operating system.
+ </div><ol class="a"><li class="step"><div class="para">
+ Start <code class="command">fdisk</code> for the new device:
+ </div><pre class="screen">
+# fdisk /dev/vdb
+Command (m for help):
+</pre></li><li class="step"><div class="para">
+ Type <em class="parameter"><code>n</code></em> for a new partition.
+ </div></li><li class="step"><div class="para">
+ The following appears:
+ </div><pre class="screen">
+Command action
+e extended
+p primary partition (1-4)
+</pre><div class="para">
+ Type <em class="parameter"><code>p</code></em> for a primary partition.
+ </div></li><li class="step"><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): 1</pre></li><li class="step"><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 class="step"><div class="para">
+ Select the size of the partition. In this example the entire disk is allocated by pressing <code class="command">Enter</code>.
+ </div><pre class="screen">Last cylinder or +size or +sizeM or +sizeK (2-400, default 400):</pre></li><li class="step"><div class="para">
+ Enter <code class="command">t</code> to configure the partition type.
+ </div><pre class="screen">Command (m for help): t</pre></li><li class="step"><div class="para">
+ Select the partition you created in the previous steps. In this example, the partition number is <code class="command">1</code> as there was only one partition created and fdisk automatically selected partition 1.
+ </div><pre class="screen">Partition number (1-4): 1</pre></li><li class="step"><div class="para">
+ Enter <code class="command">83</code> for a Linux partition.
+ </div><pre class="screen">Hex code (type L to list codes): 83</pre></li><li class="step"><div class="para">
+ Enter <code class="command">w</code> to write changes and quit.
+ </div><pre class="screen">
+Command (m for help): w
+</pre></li><li class="step"><div class="para">
+ Format the new partition with the <code class="systemitem">ext3</code> file system.
+ </div><pre class="screen"># mke2fs -j /dev/vdb1</pre></li></ol></li><li class="step"><div class="para">
+ Create a mount directory, and mount the disk on the guest. In this example, the directory is located in <em class="replaceable"><code>myfiles</code></em>.
+ </div><pre class="screen">
+# mkdir /myfiles
+# mount /dev/vdb1 /myfiles
+</pre><div class="para">
+ The guest now has an additional virtualized file-based storage device. Note however, that this storage will not mount persistently across reboot unless defined in the guest's <code class="filename">/etc/fstab</code> file:
+ </div><pre class="screen">/dev/vdb1 <em class="replaceable"><code>/myfiles</code></em> ext3 defaults 0 0</pre></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Storage_Volumes-Cloning_volumes.html"><strong>Prev</strong>28.2. Cloning volumes</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-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html"><strong>Next</strong>28.3.2. Adding hard drives and other block device...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install.html
new file mode 100644
index 0000000..d7d98b7
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install.html
@@ -0,0 +1,37 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.2. Creating guests with virt-install</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html" title="Chapter 6. Guest virtual machine installation overview" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html" title="Chapter 6. Guest virtual machine installation overview" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html" title="6.3. Creating guests with virt-manager" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Com
mon_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install"><div class="titlepage"><div><div><h2 class="title">6.2. 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 guest virtual machines 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 that can be passed on the command line. To see a complete list of options run the following command:
+ </div><pre class="screen"># virt-install --help</pre><div class="para">
+ Note that you need root privileges in order for <code class="command">virt-install</code> commands to complete successfully. 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>--graphics</code></em> option which allows graphical installation of a virtual machine.
+ </div><div class="example" id="exam-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Using_virt_install_with_KVM_to_create_a_Red_Hat_Enterprise_Linux_3_guest"><h6>Example 6.1. Using virt-install to install a Fedora 19 guest virtual machine</h6><div class="example-contents"><div class="para">
+ This example creates a Fedora 19 guest:
+ </div><pre class="screen">virt-install \
+ --name=guest1-rhel5-64 \
+ --file=/var/lib/libvirt/images/guest1-rhel5-64.dsk \
+ --file-size=8 \
+ --nonsparse --graphics spice \
+ --vcpus=2 --ram=2048 \
+ --location=http://example1.com/installation_tree/RHEL5.6-Server-x86_64/os \
+ --network bridge=br0 \
+ --os-type=linux \
+ --os-variant=rhel5.4</pre></div></div><br class="example-break" /><div class="para">
+ Ensure that you select the correct <em class="parameter"><code>os-type</code></em> for your operating system when running this command.
+ </div><div class="para">
+ Refer to <code class="command">man virt-install</code> for more examples.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ When installing a Windows guest with <code class="command">virt-install</code>, the <code class="command">--os-type=<em class="replaceable"><code>windows</code></em></code> option is recommended. This option prevents the CD-ROM from disconnecting when rebooting during the installation procedure. The <code class="command">--os-variant</code> option further optimizes the configuration for a specific guest operating system.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html"><strong>Prev</strong>Chapter 6. Guest virtual machine installation ove...</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_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html"><strong>Next</strong>6.3. Creating guests with virt-manager</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE.html
new file mode 100644
index 0000000..43e4b61
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE.html
@@ -0,0 +1,28 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.4. Installing guest virtual machines with PXE</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html" title="Chapter 6. Guest virtual machine installation overview" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html" title="6.3. Creating guests with virt-manager" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html" title="Chapter 7. Installing a Red Hat Enterprise Linux 6 guest virtual machine on a Red Hat Enterprise Linux 6 host" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class
="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE"><div class="titlepage"><div><div><h2 class="title">6.4. Installing guest virtual machines with PXE</h2></div></div></div><div class="formalpara"><h5 class="formalpara" id="idp26289168">Requirements</h5>
+ PXE guest installation requires a PXE server running on the same subnet as the guest virtual machines you wish to install. The method of accomplishing this depends on how the virtual machines are connected to the network. Contact Support if you require assistance setting up a PXE server.
+ </div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE-PXE_installation_with_virt_install"><h5 class="formalpara">PXE installation with virt-install</h5>
+ <code class="command">virt-install</code> PXE installations require both the <code class="command">--network=bridge:installation</code> parameter, where <em class="parameter"><code>installation</code></em> is the name of your bridge, and the <em class="parameter"><code>--pxe</code></em> parameter.
+ </div><div class="para">
+ By default, if no network is found, the guest virtual machine attempts to boot from alternative bootable devices. If there is no other bootable device found, the guest pauses. You can use the <span class="application"><strong>qemu-kvm</strong></span> boot parameter <em class="parameter"><code>reboot-timeout</code></em> to allow the guest to retry booting if no bootable device is found, like so:
+ </div><pre class="screen"># qemu-kvm -boot reboot-timeout=1000</pre><div class="example" id="exam-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE-PXE_installation_with_virt_install"><h6>Example 6.2. Fully-virtualized PXE installation with virt-install</h6><div class="example-contents"><pre class="screen"># virt-install --hvm --connect qemu:///system \
+--network=bridge:installation --pxe --graphics spice \
+--name rhel6-machine --ram=756 --vcpus=4 \
+--os-type=linux --os-variant=rhel6 \
+--disk path=/var/lib/libvirt/images/rhel6-machine.img,size=10</pre><div class="para">
+ Note that the command above cannot be executed in a text-only environment. A fully-virtualized (<em class="parameter"><code>--hvm</code></em>) guest can only be installed in a text-only environment if the <em class="parameter"><code>--location</code></em> and <em class="parameter"><code>--extra-args "console=<em class="replaceable"><code>console_type</code></em>"</code></em> are provided instead of the <em class="parameter"><code>--graphics spice</code></em> parameter.
+ </div></div></div><br class="example-break" /><div class="procedure" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE-PXE_installation_with_virt_manager"><h6>Procedure 6.2. PXE installation with virt-manager</h6><ol class="1"><li class="step" id="step-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE-Select_PXE"><p class="title"><strong>Select PXE</strong></p><div class="para">
+ Select PXE as the installation method and follow the rest of the steps to configure the OS type, memory, CPU and storage settings.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt3-pic2.png" alt="Step 1 of 5 for creating a new virtual machine with virt-manager, with Network Boot (PXE) chosen for the method of installation." /></div></div><h6>Figure 6.8. Selecting the installation method</h6></div><br class="figure-break" /><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt3-pic3.png" alt="Step 2 of 5 for creating a new virtual machine with virt-manager, with Linux chosen as OS Type and Fedora 19 chosen for version." /></div></div><h6>Figure 6.9. Selecting the installation type</h6></div><br class="figure-break" /><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt3-pic4.png" alt="Step 3 of 5 for creating a new virtual machine with virt-manager showing memory and CPU settings, with 1024MB of RAM and 2 CPUs selected
." /></div></div><h6>Figure 6.10. Specifying virtualized hardware details</h6></div><br class="figure-break" /><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt3-pic5.png" alt="Step 4 of 5 for creating a new virtual machine with virt-manager, with checkboxes selected next to "Enable storage for this virtual machine" and "Allocate entire disk now". 8GB is selected under the heading "Create a disk image on the computer's hard drive"." /></div></div><h6>Figure 6.11. Specifying storage details</h6></div><br class="figure-break" /></li><li class="step" id="step-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Start_the_installation"><p class="title"><strong>Start the installation</strong></p><div class="para">
+ The installation is ready to start.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/PXEguest_5of5.png" width="444" alt="Step 5 of 5 for creating a new virtual machine with virt-manager reads "Ready to begin installation of (guest name)" with a summary of options already chosen, and advanced options to choose from." /></div></div><h6>Figure 6.12. Finalizing virtual machine details</h6></div><br class="figure-break" /></li></ol></div><div class="para">
+ A DHCP request is sent and if a valid PXE server is found the guest virtual machine's installation processes will start.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html"><strong>Prev</strong>6.3. 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_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html"><strong>Next</strong>Chapter 7. Installing a Red Hat Enterprise Linux ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html
new file mode 100644
index 0000000..5c020a9
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html
@@ -0,0 +1,84 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.2. Installing virtualization packages on an existing Fedora system</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html" title="Chapter 5. Installing the virtualization packages" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html" title="Chapter 5. Installing the virtualization packages" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html" title="Chapter 6. Guest virtual machine installation overview" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Pr
oduct Site" /></a><a class="right" href="http://docs.redhat.com"><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_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system"><div class="titlepage"><div><div><h2 class="title">5.2. Installing virtualization packages on an existing Fedora system</h2></div></div></div><div class="para">
+ This section describes the steps for installing the KVM hypervisor on a working Fedora 16 or newer system.
+ </div><div class="para">
+ To install the packages, your machines must be registered. There are two methods of registering an unregistered installation of Fedora:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ To register via RHN Classic, run the <code class="command">rhn_register</code> command and follow the prompts.
+ </div></li><li class="listitem"><div class="para">
+ To register via Fedora, run the <code class="command">subscription-manager register</code> command and follow the prompts.
+ </div></li></ol></div><div class="para">
+ If you do not have a valid Fedora subscription, visit the <a href="https://www.redhat.com/wapps/store/catalog.html">Fedora online store</a> to obtain one.
+ </div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_the_KVM_hypervisor_with_yum"><h5 class="formalpara">Installing the virtualization packages with <code class="command">yum</code></h5>
+ To use virtualization on Fedora you require at least the <code class="filename">qemu-kvm</code> and <code class="filename">qemu-img</code> packages. These packages provide the user-level KVM emulator and disk image manager on the host Fedora system.
+ </div><div class="para">
+ To install the <code class="filename">qemu-kvm</code> and <code class="filename">qemu-img</code> packages, run the following command:
+ </div><pre class="screen"># yum install qemu-kvm qemu-img</pre><div class="para">
+ Several additional virtualization management packages are also available:
+ </div><div class="variablelist" id="vari-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Recommended_virtualization_packages"><h6>Recommended virtualization packages</h6><dl class="variablelist"><dt class="varlistentry"><span class="term"><span class="package">python-virtinst</span></span></dt><dd><div class="para">
+ Provides the <code class="command">virt-install</code> command for creating virtual machines.
+ </div></dd><dt class="varlistentry"><span class="term"><span class="package">libvirt</span></span></dt><dd><div class="para">
+ The <span class="package">libvirt</span> package provides the server and host side libraries for interacting with hypervisors and host systems. The <span class="package">libvirt</span> package provides the <code class="systemitem">libvirtd</code> daemon that handles the library calls, manages virtual machines and controls the hypervisor.
+ </div></dd><dt class="varlistentry"><span class="term"><span class="package">libvirt-python</span></span></dt><dd><div class="para">
+ The <span class="package">libvirt-python</span> package contains a module that permits applications written in the Python programming language to use the interface supplied by the <span class="package">libvirt</span> API.
+ </div></dd><dt class="varlistentry"><span class="term"><span class="package">virt-manager</span></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 <span class="package">libvirt-client</span> library as the management API.
+ </div></dd><dt class="varlistentry"><span class="term"><span class="package">libvirt-client</span></span></dt><dd><div class="para">
+ The <span class="package">libvirt-client</span> package provides the client-side APIs and libraries for accessing <span class="package">libvirt</span> servers. The <span class="package">libvirt-client</span> package includes the <code class="command">virsh</code> command line tool to manage and control virtual machines and hypervisors from the command line or a special virtualization shell.
+ </div></dd></dl></div><div class="para">
+ Install all of these recommended virtualization packages with the following command:
+ </div><pre class="screen"># yum install virt-manager libvirt libvirt-python python-virtinst libvirt-client</pre><div class="formalpara"><h5 class="formalpara" id="idp3689936">Installing Virtualization package groups</h5>
+ The virtualization packages can also be installed from package groups. The following table describes the virtualization package groups and what they provide.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Note that the <code class="command">qemu-img</code> package is installed as a dependency of the <code class="literal">Virtualization</code> package group if it is not already installed on the system. It can also be installed manually with the <code class="command">yum install qemu-img</code> command as described previously.
+ </div></div></div><div class="table"><h6>Table 5.1. Virtualization Package Groups</h6><div class="table-contents"><table summary="Virtualization Package Groups" border="1"><colgroup><col align="left" class="c1" width="25%" /><col align="left" class="c2" width="25%" /><col align="left" class="c3" width="25%" /><col align="left" class="c4" width="25%" /></colgroup><thead><tr><th class="" align="left">
+ Package Group
+ </th><th class="" align="left">
+ Description
+ </th><th class="" align="left">
+ Mandatory Packages
+ </th><th class="" align="left">
+ Optional Packages
+ </th></tr></thead><tbody><tr><td class="" align="left">
+ Virtualization
+ </td><td class="" align="left">
+ Provides an environment for hosting virtual machines
+ </td><td class="" align="left">
+ qemu-kvm
+ </td><td class="" align="left">
+ qemu-guest-agent, qemu-kvm-tools
+ </td></tr><tr><td class="" align="left">
+ Virtualization Client
+ </td><td class="" align="left">
+ Clients for installing and managing virtualization instances
+ </td><td class="" align="left">
+ python-virtinst, virt-manager, virt-viewer
+ </td><td class="" align="left">
+ virt-top
+ </td></tr><tr><td class="" align="left">
+ Virtualization Platform
+ </td><td class="" align="left">
+ Provides an interface for accessing and controlling virtual machines and containers
+ </td><td class="" align="left">
+ libvirt, libvirt-client, virt-who, virt-what
+ </td><td class="" align="left">
+ fence-virtd-libvirt, fence-virtd-multicast, fence-virtd-serial, libvirt-cim, libvirt-java, libvirt-qmf, libvirt-snmp, perl-Sys-Virt
+ </td></tr><tr><td class="" align="left">
+ Virtualization Tools
+ </td><td class="" align="left">
+ Tools for offline virtual image management
+ </td><td class="" align="left">
+ libguestfs
+ </td><td class="" align="left">
+ libguestfs-java, libguestfs-tools, virt-v2v
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ To install a package group, run the <code class="command">yum groupinstall <groupname></code> command. For instance, to install the <span class="bold bold"><strong>Virtualization Tools</strong></span> package group, run the <code class="command">yum groupinstall "Virtualization Tools"</code> command.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html"><strong>Prev</strong>Chapter 5. 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="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html"><strong>Next</strong>Chapter 6. Guest virtual machine installation ove...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html
new file mode 100644
index 0000000..0f66d87
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html
@@ -0,0 +1,21 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.3. Bridged networking with libvirt</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html" title="Chapter 11. Network configuration" /><link rel="prev" href="ch11s02.html" title="11.2. Disabling vhost-net" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html" title="Chapter 12. PCI device configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation S
ite" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt"><div class="titlepage"><div><div><h2 class="title">11.3. Bridged networking with libvirt</h2></div></div></div><div class="para">
+ Bridged networking (also known as physical device sharing) is used to dedicate 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="para">
+ To create a bridge (<code class="literal">br0</code>) based on the <code class="literal">eth0</code> interface, execute the following command on the host:
+ </div><pre class="screen"># virsh iface-bridge eth0 br0</pre><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ NetworkManager does not support bridging. NetworkManager must be disabled to use networking with the network scripts (located in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory).
+ </div><pre class="screen"># chkconfig NetworkManager off
+# chkconfig network on
+# service NetworkManager stop
+# service network start</pre><div class="para">
+ If you do not want to disable <span class="application"><strong>NetworkManager</strong></span> entirely, add "<em class="parameter"><code>NM_CONTROLLED=no</code></em>" to the <code class="filename">ifcfg-*</code> network script being used for the bridge.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s02.html"><strong>Prev</strong>11.2. Disabling vhost-net</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_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html"><strong>Next</strong>Chapter 12. PCI device configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host.html
new file mode 100644
index 0000000..721ed6c
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.2. Assigning a PCI device with virt-manager</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html" title="Chapter 12. PCI device configuration" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html" title="Chapter 12. PCI device configuration" /><link rel="next" href="ch12s03.html" title="12.3. PCI device assignment with virt-install" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" a
lt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch12s03.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host"><div class="titlepage"><div><div><h2 class="title">12.2. Assigning a PCI device with virt-manager</h2></div></div></div><div class="para">
+ PCI devices can be added to guest virtual machines using the graphical <code class="command">virt-manager</code> tool. The following procedure adds a Gigabit Ethernet controller to a guest virtual machine.
+ </div><div class="procedure"><h6>Procedure 12.4. Assigning a PCI device to a guest virtual machine using virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Open the hardware settings</strong></p><div class="para">
+ Open the guest virtual machine and click the <span class="guibutton"><strong>Add Hardware</strong></span> button to add a new device to the virtual machine.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_hardware.png" width="444" alt="The virtual machine hardware window with the Information button selected on the top taskbar and Overview selected on the left menu pane." /></div></div><h6>Figure 12.1. The virtual machine hardware information window</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Select a PCI device</strong></p><div class="para">
+ Select <span class="application"><strong>PCI Host Device</strong></span> from the <span class="guilabel"><strong>Hardware</strong></span> list on the left.
+ </div><div class="para">
+ Select an unused PCI device. Note that selecting PCI devices presently in use on the host causes errors. In this example, a spare 82576 network device is used. Click <span class="guilabel"><strong>Finish</strong></span> to complete setup.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/3_PCI_Device.png" width="444" alt="The Add new virtual hardware wizard with PCI Host Device selected on the left menu pane, showing a list of host devices for selection in the right menu pane." /></div></div><h6>Figure 12.2. The Add new virtual hardware wizard</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Add the new device</strong></p><div class="para">
+ The setup is complete and the guest virtual machine now has direct access to the PCI device.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/pci_host_device.png" width="444" alt="The virtual machine hardware window with the Information button selected on the top taskbar and Overview selected on the left menu pane, displaying the newly added PCI Device in the list of virtual machine devices in the left menu pane." /></div></div><h6>Figure 12.3. The virtual machine hardware information window</h6></div><br class="figure-break" /></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html"><strong>Prev</strong>Chapter 12. PCI device 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="ch12s03.html"><strong>Next</strong>12.3. PCI device assig
nment with virt-install</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html
new file mode 100644
index 0000000..af19c28
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html
@@ -0,0 +1,56 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.6. Using KVM para-virtualized drivers for new devices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html" title="Chapter 10. KVM Para-virtualized Drivers" /><link rel="prev" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices.html" title="10.5. Using KVM para-virtualized drivers for existing devices" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html" title="Chapter 11. Network configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><
img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices"><div class="titlepage"><div><div><h2 class="title">10.6. Using KVM para-virtualized drivers for new devices</h2></div></div></div><div class="pa
ra">
+ 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"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><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><div class="procedure"><h6>Procedure 10.5. Starting the new device wizard</h6><ol class="1"><li class="step"><div class="para">
+ Open the guest virtual machine by double clicking on the name of the guest in <code class="command">virt-manager</code>.
+ </div></li><li class="step"><div class="para">
+ Open the <span class="guilabel"><strong>Show virtual hardware details</strong></span> tab by clicking the <span class="guibutton"><strong>lightbulb</strong></span> button.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/vm_info_button_new.png" alt="The Show virtual hardware details tab" /></div></div><h6>Figure 10.30. The Show virtual hardware details tab</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ In the <span class="guilabel"><strong>Show virtual hardware details</strong></span> tab, click on the <span class="guilabel"><strong>Add Hardware</strong></span> button.
+ </div></li><li class="step"><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. The storage and network device wizards are covered in procedures <a class="xref" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html#procstore">Procedure 10.6, “Adding a storage device using the para-virtualized storage driver”</a> and <a class="xref" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html#procnet">Procedure 10.7, “Adding a network device using the para-virtualized network driver”</a>.
+ </div></li></ol></div><div class="procedure" id="procstore"><h6>Procedure 10.6. Adding a storage device using the para-virtualized storage driver</h6><ol class="1"><li class="step"><div class="para">
+ Open the guest virtual machine by double clicking on the name of the guest in <code class="command">virt-manager</code>.
+ </div></li><li class="step"><div class="para">
+ Open the <span class="guilabel"><strong>Show virtual hardware details</strong></span> tab by clicking the <span class="guibutton"><strong>lightbulb</strong></span> button.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/vm_info_button_new.png" alt="The Show virtual hardware details tab" /></div></div><h6>Figure 10.31. The Show virtual hardware details tab</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ In the <span class="guilabel"><strong>Show virtual hardware details</strong></span> tab, click on the <span class="guilabel"><strong>Add Hardware</strong></span> button.
+ </div></li><li class="step"><p class="title"><strong>Select hardware type</strong></p><div class="para">
+ Select <span class="guilabel"><strong>Network</strong></span> as the <span class="guilabel"><strong>Hardware type</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Network_hardware.png" width="444" alt="The Add new virtual hardware wizard with Storage selected as the hardware type." /></div></div><h6>Figure 10.32. The Add new virtual hardware wizard</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Select the network device and driver</strong></p><div class="para">
+ Create a new disk image or select a storage pool volume.
+ </div><div class="para">
+ Set the <span class="guilabel"><strong>Device type</strong></span> to <span class="guilabel"><strong>Virtio Disk</strong></span> to use the para-virtualized drivers. Choose the desired <span class="guilabel"><strong>Host device</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Network_hardware_virtio.png" width="444" alt="The Add new virtual hardware wizard Storage window, with "Select managed or other existing storage" selected and specified in the field below." /></div></div><h6>Figure 10.33. The Add new virtual hardware wizard</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guilabel"><strong>Finish</strong></span> to complete the procedure.
+ </div></li></ol></div><div class="procedure" id="procnet"><h6>Procedure 10.7. Adding a network device using the para-virtualized network driver</h6><ol class="1"><li class="step"><p class="title"><strong>Select hardware type</strong></p><div class="para">
+ Select <span class="guilabel"><strong>Network</strong></span> as the <span class="guilabel"><strong>Hardware type</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/virtio-network-step1.png" alt="The Add new virtual hardware wizard with Network selected as the hardware type." /></div></div><h6>Figure 10.34. The Add new virtual hardware wizard</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guilabel"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Select the network device and driver</strong></p><div class="para">
+ Select the network device from the <span class="guilabel"><strong>Host device</strong></span> list.
+ </div><div class="para">
+ Create a custom MAC address or use the one provided.
+ </div><div class="para">
+ Set the <span class="guilabel"><strong>Device model</strong></span> to <span class="guilabel"><strong>virtio</strong></span> to use the para-virtualized drivers.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/virtio-network-step2.png" alt="The Add new virtual hardware wizard Network setup, with options for selecting the network device and driver." /></div></div><h6>Figure 10.35. The Add new virtual hardware wizard</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guilabel"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Finish the procedure</strong></p><div class="para">
+ Confirm the details for the new device are correct.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/virtio-network-finish3.png" alt="The Add new virtual hardware wizard showing the details of the newly created network, and the Finish button at the bottom right corner of the window." /></div></div><h6>Figure 10.36. The Add new virtual hardware wizard</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guilabel"><strong>Finish</strong></span> to complete the procedure.
+ </div></li></ol></div><div class="para">
+ Once all new devices are added, reboot the virtual machine. Windows virtual machines may not recognize the devices until the guest is rebooted.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices.html"><strong>Prev</strong>10.5. Using KVM para-virtualized drivers for exis...</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_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html"><strong>Next</strong>Chapter 11. Network configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html
new file mode 100644
index 0000000..86e4500
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html
@@ -0,0 +1,169 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>13.2. Using SR-IOV</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html" title="Chapter 13. SR-IOV" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html" title="Chapter 13. SR-IOV" /><link rel="next" href="ch13s03.html" title="13.3. Troubleshooting SR-IOV" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch13s03.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works"><div class="titlepage"><div><div><h2 class="title">13.2. Using SR-IOV</h2></div></div></div><div class="para">
+ This section covers the use of PCI passthrough to assign a Virtual Function of an SR-IOV capable multiport network card to a virtual machine as a network device.
+ </div><div class="para">
+ SR-IOV Virtual Functions (VFs) can be assigned to virtual machines by adding a device entry in <em class="parameter"><code><hostdev></code></em> with the <code class="command">virsh edit</code> or <code class="command">virsh attach-device</code> command. However, this can be problematic because unlike a regular network device, an SR-IOV VF network device does not have a permanent unique MAC address, and is assigned a new MAC address each time the host is rebooted. Because of this, even if the guest is assigned the same VF after a reboot, when the host is rebooted the guest determines its network adapter to have a new MAC address. As a result, the guest believes there is new hardware connected each time, and will usually require re-configuration of the guest's network settings.
+ </div><div class="para">
+ <span class="package">libvirt-0.9.10</span> and newer contains the <em class="parameter"><code><interface type='hostdev'></code></em> interface device. Using this interface device, <span class="application"><strong>libvirt</strong></span> will first perform any network-specific hardware/switch initialization indicated (such as setting the MAC address, VLAN tag, or 802.1Qbh virtualport parameters), then perform the PCI device assignment to the guest.
+ </div><div class="para">
+ Using the <em class="parameter"><code><interface type='hostdev'></code></em> interface device requires:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ an SR-IOV-capable network card,
+ </div></li><li class="listitem"><div class="para">
+ host hardware that supports either the Intel VT-d or the AMD IOMMU extensions, and
+ </div></li><li class="listitem"><div class="para">
+ the PCI address of the VF to be assigned.
+ </div></li></ul></div>
+
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Assignment of an SR-IOV device to a virtual machine requires that the host hardware supports the Intel VT-d or the AMD IOMMU specification.
+ </div></div></div><div class="para">
+ To attach an SR-IOV network device on an Intel or an AMD system, follow this procedure:
+ </div><div class="procedure"><h6>Procedure 13.1. Attach an SR-IOV network device on an Intel or AMD system</h6><ol class="1"><li class="step"><p class="title"><strong>Enable Intel VT-d or the AMD IOMMU specifications in the BIOS and kernel</strong></p><div class="para">
+ On an Intel system, enable Intel VT-d in the BIOS if it is not enabled already. Refer to <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html#intel-prep">Procedure 12.1, “Preparing an Intel system for PCI device assignment”</a> for procedural help on enabling Intel VT-d in the BIOS and kernel.
+ </div><div class="para">
+ Skip this step if Intel VT-d is already enabled and working.
+ </div><div class="para">
+ On an AMD system, enable the AMD IOMMU specifications in the BIOS if they are not enabled already. Refer to <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html#amd-prep">Procedure 12.2, “Preparing an AMD system for PCI device assignment”</a> for procedural help on enabling IOMMU in the BIOS.
+ </div></li><li class="step"><p class="title"><strong>Verify support</strong></p><div class="para">
+ Verify if the PCI device with SR-IOV capabilities is detected. This example lists an Intel 82576 network interface card which supports SR-IOV. Use the <code class="command">lspci</code> command to verify whether the device was detected.
+ </div><pre class="screen"># lspci
+03:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
+03:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)</pre><div class="para">
+ Note that the output has been modified to remove all other devices.
+ </div></li><li class="step"><p class="title"><strong>Start the SR-IOV kernel modules</strong></p><div class="para">
+ If the device is supported the driver kernel module should be loaded automatically by the kernel. Optional parameters can be passed to the module using the <code class="command">modprobe</code> command. The Intel 82576 network interface card uses the <code class="command">igb</code> driver kernel module.
+ </div><pre class="screen"># modprobe igb [<option>=<VAL1>,<VAL2>,]
+# lsmod |grep igb
+igb 87592 0
+dca 6708 1 igb</pre></li><li class="step"><p class="title"><strong>Activate Virtual Functions</strong></p><div class="para">
+ The <em class="parameter"><code>max_vfs</code></em> parameter of the <code class="command">igb</code> module allocates the maximum number of Virtual Functions. The <em class="parameter"><code>max_vfs</code></em> parameter causes the driver to spawn, up to the value of the parameter in, Virtual Functions. For this particular card the valid range is <em class="parameter"><code>0</code></em> to <em class="parameter"><code>7</code></em>.
+ </div><div class="para">
+ Remove the module to change the variable.
+ </div><pre class="screen"># modprobe -r igb</pre><div class="para">
+ Restart the module with the <em class="parameter"><code>max_vfs</code></em> set to <em class="parameter"><code>7</code></em> or any number of Virtual Functions up to the maximum supported by your device.
+ </div><pre class="screen"># modprobe igb max_vfs=7</pre></li><li class="step"><p class="title"><strong>Make the Virtual Functions persistent</strong></p><div class="para">
+ Add the line <code class="option">options igb max_vfs=7</code> to any file in <code class="filename">/etc/modprobe.d</code> to make the Virtual Functions persistent. For example:
+ </div><pre class="screen"># echo "options igb max_vfs=7" >>/etc/modprobe.d/igb.conf</pre></li><li class="step"><p class="title"><strong>Inspect the new Virtual Functions</strong></p><div class="para">
+ Using the <code class="command">lspci</code> command, list the newly added Virtual Functions attached to the Intel 82576 network device. (Alternatively, use <code class="command">grep</code> to search for <code class="literal">Virtual Function</code>, to search for devices that support Virtual Functions.)
+ </div><pre class="screen"># lspci | grep 82576
+0b:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
+0b:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
+0b:10.0 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.1 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.2 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.3 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.4 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.5 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.6 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.7 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:11.0 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:11.1 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:11.2 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:11.3 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:11.4 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:11.5 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)</pre><div class="para">
+ The identifier for the PCI device is found with the <em class="parameter"><code>-n</code></em> parameter of the <code class="command">lspci</code> command. The Physical Functions correspond to <code class="computeroutput">0b:00.0</code> and <code class="computeroutput">0b:00.1</code>. All Virtual Functions have <code class="computeroutput">Virtual Function</code> in the description.
+ </div></li><li class="step"><p class="title"><strong>Verify devices exist with virsh</strong></p><div class="para">
+ The <code class="systemitem">libvirt</code> service must recognize the device before adding a device to a virtual machine. <code class="systemitem">libvirt</code> uses a similar notation to the <code class="command">lspci</code> output. All punctuation characters, <span class="keycap"><strong>;</strong></span> and <span class="keycap"><strong>.</strong></span>, in <code class="command">lspci</code> output are changed to underscores (<span class="keycap"><strong>_</strong></span>).
+ </div><div class="para">
+ Use the <code class="command">virsh nodedev-list</code> command and the <code class="command">grep</code> command to filter the Intel 82576 network device from the list of available host devices. <em class="parameter"><code>0b</code></em> is the filter for the Intel 82576 network devices in this example. This may vary for your system and may result in additional devices.
+ </div><pre class="screen"># virsh nodedev-list | grep <em class="parameter"><code>0b</code></em>
+pci_0000_0b_00_0
+pci_0000_0b_00_1
+pci_0000_0b_10_0
+pci_0000_0b_10_1
+pci_0000_0b_10_2
+pci_0000_0b_10_3
+pci_0000_0b_10_4
+pci_0000_0b_10_5
+pci_0000_0b_10_6
+pci_0000_0b_11_7
+pci_0000_0b_11_1
+pci_0000_0b_11_2
+pci_0000_0b_11_3
+pci_0000_0b_11_4
+pci_0000_0b_11_5</pre><div class="para">
+ The serial numbers for the Virtual Functions and Physical Functions should be in the list.
+ </div></li><li class="step"><p class="title"><strong>Get device details with virsh</strong></p><div class="para">
+ The <code class="computeroutput">pci_0000_0b_00_0</code> is one of the Physical Functions and <code class="computeroutput">pci_0000_0b_10_0</code> is the first corresponding Virtual Function for that Physical Function. Use the <code class="command">virsh nodedev-dumpxml</code> command to get advanced output for both devices.
+ </div><pre class="screen"># virsh nodedev-dumpxml pci_0000_0b_00_0
+<device>
+ <name>pci_0000_0b_00_0</name>
+ <parent>pci_0000_00_01_0</parent>
+ <driver>
+ <name>igb</name>
+ </driver>
+ <capability type='pci'>
+ <domain>0</domain>
+ <bus>11</bus>
+ <slot>0</slot>
+ <function>0</function>
+ <product id='0x10c9'>Intel Corporation</product>
+ <vendor id='0x8086'>82576 Gigabit Network Connection</vendor>
+ </capability>
+</device></pre><pre class="screen"># virsh nodedev-dumpxml pci_0000_0b_10_0
+<device>
+ <name>pci_0000_0b_10_0</name>
+ <parent>pci_0000_00_01_0</parent>
+ <driver>
+ <name>igbvf</name>
+ </driver>
+ <capability type='pci'>
+ <domain>0</domain>
+ <bus>11</bus>
+ <slot>16</slot>
+ <function>0</function>
+ <product id='0x10ca'>Intel Corporation</product>
+ <vendor id='0x8086'>82576 Virtual Function</vendor>
+ </capability>
+</device></pre><div class="para">
+ This example adds the Virtual Function <code class="systemitem">pci_0000_0b_10_0</code> to the virtual machine in <a class="xref" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html#step9">Step 9</a>. Note the <code class="computeroutput">bus</code>, <code class="computeroutput">slot</code> and <code class="computeroutput">function</code> parameters of the Virtual Function: these are required for adding the device.
+ </div><div class="para">
+ Copy these parameters into a temporary XML file, such as <code class="filename">/tmp/new-interface.xml</code> for example.
+ </div><pre class="programlisting">
+ <interface type='hostdev' managed='yes'>
+ <source>
+ <address type='pci' domain='0' bus='11' slot='16' function='0'/>
+ </source>
+ </interface></pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If you do not specify a MAC address, one will be automatically generated. The <em class="parameter"><code><virtualport></code></em> element is only used when connecting to an 802.11Qbh hardware switch. The <em class="parameter"><code><vlan></code></em> element was introduced for Fedora 18 and this will transparently put the guest's device on the VLAN tagged <em class="parameter"><code>42</code></em>.
+ </div><div class="para">
+ When the virtual machine starts, it should see a network device of the type provided by the physical adapter, with the configured MAC address. This MAC address will remain unchanged across host and guest reboots.
+ </div><div class="para">
+ The following <em class="parameter"><code><interface></code></em> example shows the syntax for the optional <em class="parameter"><code><mac address></code></em>, <em class="parameter"><code><virtualport></code></em>, and <em class="parameter"><code><vlan></code></em> elements. In practice, use either the <em class="parameter"><code><vlan></code></em> or <em class="parameter"><code><virtualport></code></em> element, not both simultaneously as shown in the example:
+ </div><pre class="programlisting">...
+ <devices>
+ ...
+ <interface type='hostdev' managed='yes'>
+ <source>
+ <address type='pci' domain='0' bus='11' slot='16' function='0'/>
+ </source>
+ <mac address='52:54:00:6d:90:02'>
+ <vlan>
+ <tag id='42'/>
+ </vlan>
+ <virtualport type='802.1Qbh'>
+ <parameters profileid='finance'/>
+ </virtualport>
+ </interface>
+ ...
+ </devices></pre></div></div></li><li class="step" id="step9"><p class="title"><strong>Add the Virtual Function to the virtual machine</strong></p><div class="para">
+ Add the Virtual Function to the virtual machine using the following command with the temporary file created in the previous step. This attaches the new device immediately and saves it for subsequent guest restarts.
+ </div><pre class="screen">
+virsh attach-device <em class="replaceable"><code>MyGuest</code></em> <code class="filename">/tmp/new-interface.xml</code> --live --config
+</pre><div class="para">
+ Specifying the <code class="option">--live</code> option with <code class="command">virsh attach-device</code> attaches the new device to the running guest. Using the <code class="option">--config</code> option ensures the new device is available after future guest restarts.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The <code class="option">--live</code> option is only accepted when the guest is running. <code class="command">virsh</code> will return an error if the <code class="option">--live</code> option is used on a non-running guest.
+ </div></div></div></li></ol></div><div class="para">
+ The virtual machine detects a new network interface card. This new card is the Virtual Function of the SR-IOV device.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html"><strong>Prev</strong>Chapter 13. SR-IOV</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="ch13s03.html"><strong>Next</strong>13.3. Troubleshooting SR-IOV</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html
new file mode 100644
index 0000000..ecbc6bc
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html
@@ -0,0 +1,46 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 9. Installing a fully-virtualized Windows guest</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="ch08s02.html" title="8.2. On Hyper-V" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html" title="Chapter 10. KVM Para-virtualized Drivers" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s02.html"><strong
>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 9. Installing a fully-virtualized Windows guest</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_virt-install">9.1. Using virt-install to create a guest</a></span></dt></dl></div><div class="para">
+ This chapter describes how to create a fully-virtualized Windows guest using the command-line (<code class="command">virt-install</code>), launch the operating system's installer inside the guest, and access the installer through <code class="command">virt-viewer</code>.
+ </div><div class="para">
+ To install a Windows operating system on the guest, use the <code class="command">virt-viewer</code> tool. This tool allows you to display the graphical console of a virtual machine (via the VNC protocol). In doing so, <code class="command">virt-viewer</code> allows you to install a fully-virtualized guest's operating system with that operating system's installer (for example, the Windows XP installer).
+ </div><div class="para">
+ Installing a Windows operating system involves two major steps:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Creating the guest virtual machine, using either <code class="command">virt-install</code> or <code class="command">virt-manager</code>.
+ </div></li><li class="listitem"><div class="para">
+ Installing the Windows operating system on the guest virtual machine, using <code class="command">virt-viewer</code>.
+ </div></li></ol></div><div class="para">
+ Refer to <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html">Chapter 6, <em>Guest virtual machine installation overview</em></a> for details about creating a guest virtual machine with <code class="command">virt-install</code> or <code class="command">virt-manager</code>.
+ </div><div class="para">
+ Note that this chapter does not describe how to install a Windows operating system on a fully-virtualized guest. Rather, it only covers how to create the guest and launch the installer within the guest. For information on how to install a Windows operating system, refer to the relevant Microsoft installation documentation.
+ </div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_virt-install"><div class="titlepage"><div><div><h2 class="title">9.1. Using virt-install to create a guest</h2></div></div></div><div class="para">
+ The <code class="command">virt-install</code> command allows you to create a fully-virtualized guest from a terminal, for example, without a GUI.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Before creating the guest, consider first if the guest needs to use KVM Windows para-virtualized drivers. If it does, keep in mind that you can do so <span class="emphasis"><em>during</em></span> or <span class="emphasis"><em>after</em></span> installing the Windows operating system on the guest. For more information about para-virtualized drivers, refer to <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html">Chapter 10, <em>KVM Para-virtualized Drivers</em></a>.
+ </div><div class="para">
+ For instructions on how to install KVM para-virtualized drivers, refer to <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers">Section 10.1, “Installing the KVM Windows para-virtualized drivers”</a>.
+ </div></div></div><div class="para">
+ It is possible to create a fully-virtualized guest with only a single command. To do so, run the following program (replace the values accordingly):
+ </div><pre class="screen"># virt-install \
+ --name=<em class="replaceable"><code>guest-name</code></em> \
+ --os-type=<em class="replaceable"><code>windows</code></em> \
+ --network network=default \
+ --disk path=<em class="replaceable"><code>path-to-disk</code></em>,size=<em class="replaceable"><code>disk-size</code></em> \
+ --cdrom=<em class="replaceable"><code>path-to-install-disk</code></em> \
+ --graphics spice --ram=1024</pre><div class="para">
+ The <code class="command"><em class="replaceable"><code>path-to-disk</code></em></code> must be a device (e.g. <code class="filename">/dev/sda3</code>) or image file (<code class="filename">/var/lib/libvirt/images/<em class="replaceable"><code>name</code></em>.img</code>). It must also have enough free space to support the <code class="command"><em class="replaceable"><code>disk-size</code></em></code>.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ All image files are stored in <code class="filename">/var/lib/libvirt/images/</code> by default. Other directory locations for file-based images are possible, but may require SELinux configuration. If you run SELinux in enforcing mode.
+ </div></div></div><div class="para">
+ You can also run <code class="command">virt-install</code> interactively. To do so, use the <code class="command">--prompt</code> command, as in:
+ </div><pre class="screen"># virt-install --prompt</pre><div class="para">
+ Once the fully-virtualized guest is created, <code class="command">virt-viewer</code> will launch the guest and run the operating system's installer. Refer to to the relevant Microsoft installation documentation for instructions on how to install the operating system.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s02.html"><strong>Prev</strong>8.2. On Hyper-V</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_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html"><strong>Next</strong>Chapter 10. KVM Para-virtualized Drivers</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-applying-network-filtering.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-applying-network-filtering.html
new file mode 100644
index 0000000..12723ae
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-applying-network-filtering.html
@@ -0,0 +1,52 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10. Applying network filtering</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html" title="Appendix H. Virtual Networking" /><link rel="prev" href="sect-attch-nic-physdev.html" title="H.9. Directly attaching to physical interface" /><link rel="next" href="sub-sect-filt-chain.html" title="H.10.2. Filtering chains" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href=
"sect-attch-nic-physdev.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-filt-chain.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-applying-network-filtering"><div class="titlepage"><div><div><h2 class="title">H.10. Applying network filtering</h2></div></div></div><div class="para">
+ This section provides an introduction to libvirt's network filters, their goals, concepts and XML format.
+ </div><div class="section" id="intro-sub-sect-applying-network-filtering"><div class="titlepage"><div><div><h3 class="title">H.10.1. Introduction</h3></div></div></div><div class="para">
+ The goal of the network filtering, is to enable administrators of a virtualized system to configure and enforce network traffic filtering rules on virtual machines and manage the parameters of network traffic that virtual machines are allowed to send or receive. The network traffic filtering rules are applied on the host when a virtual machine is started. Since the filtering rules cannot be circumvented from within the virtual machine, it makes them mandatory from the point of view of a virtual machine user.
+ </div><div class="para">
+ From the point of view of the guest, the network filtering system allows each virtual machine's network traffic filtering rules to be configured individually on a per interface basis. These rules are applied on the host when the virtual machine is started and can be modified while the virtual machine is running. The latter can be achieved by modifying the XML description of a network filter.
+ </div><div class="para">
+ Multiple virtual machines can make use of the same generic network filter. When such a filter is modified, the network traffic filtering rules of all running virtual machines that reference this filter are updated. The machines that are not running will update on start.
+ </div><div class="para">
+ As previously mentioned, applying network traffic filtering rules can be done on individual network interfaces that are configured for certain types of network configurations. Supported network types include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ network
+ </div></li><li class="listitem"><div class="para">
+ ethernet -- must be used in bridging mode
+ </div></li><li class="listitem"><div class="para">
+ bridge
+ </div></li></ul></div><div class="example" id="ex-net-filtering"><h6>Example H.1. An example of network filtering</h6><div class="example-contents"><div class="para">
+ The interface XML is used to reference a top-level filter. In the following example, the interface description references the filter clean-traffic.
+ </div><pre class="screen">
+ <devices>
+ <interface type='bridge'>
+ <mac address='00:16:3e:5d:c7:9e'/>
+ <filterref filter='clean-traffic'/>
+ </interface>
+ </devices>
+</pre><div class="para">
+ Network filters are written in XML and may either contain: references to other filters, rules for traffic filtering, or hold a combination of both. The above referenced filter clean-traffic is a filter that only contains references to other filters and no actual filtering rules. Since references to other filters can be used, a tree of filters can be built. The clean-traffic filter can be viewed using the command: <code class="command"># virsh nwfilter-dumpxml clean-traffic</code>.
+ </div><div class="para">
+ As previously mentioned, a single network filter can be referenced by multiple virtual machines. Since interfaces will typically have individual parameters associated with their respective traffic filtering rules, the rules described in a filter's XML can be generalized using variables. In this case, the variable name is used in the filter XML and the name and value are provided at the place where the filter is referenced.
+ </div></div></div><br class="example-break" /><div class="example"><h6>Example H.2. Description extended</h6><div class="example-contents"><div class="para">
+ In the following example, the interface description has been extended with the parameter IP and a dotted IP address as a value.
+ </div><pre class="screen">
+ <devices>
+ <interface type='bridge'>
+ <mac address='00:16:3e:5d:c7:9e'/>
+ <filterref filter='clean-traffic'>
+ <parameter name='IP' value='10.0.0.1'/>
+ </filterref>
+ </interface>
+ </devices>
+</pre><div class="para">
+ In this particular example, the clean-traffic network traffic filter will be represented with the IP address parameter 10.0.0.1 and as per the rule dictates that all traffic from this interface will always be using 10.0.0.1 as the source IP address, which is one of the purpose of this particular filter.
+ </div></div></div><br class="example-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-attch-nic-physdev.html"><strong>Prev</strong>H.9. Directly attaching to physical interface</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="sub-sect-filt-chain.html"><strong>Next</strong>H.10.2. Filtering chains</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-attch-nic-physdev.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-attch-nic-physdev.html
new file mode 100644
index 0000000..4adb4a7
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-attch-nic-physdev.html
@@ -0,0 +1,70 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.9. Directly attaching to physical interface</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html" title="Appendix H. Virtual Networking" /><link rel="prev" href="sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest.html" title="H.8. Attaching a virtual network to a guest" /><link rel="next" href="sect-applying-network-filtering.html" title="H.10. Applying network filtering" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-Virtual_Networking-Attaching_virtual_network_to_guest.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-applying-network-filtering.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-attch-nic-physdev"><div class="titlepage"><div><div><h2 class="title">H.9. Directly attaching to physical interface</h2></div></div></div><div class="para">
+ The instructions provided in this chapter will assist in the direct attachment of the virtual machine's NIC to the given physical interface of the host. This setup requires the Linux macvtap driver to be available. There are four modes that you can choose for the operation mode of the macvtap device, with 'vepa' being the default mode. Their behavior is as follows:
+ </div><div class="variablelist"><h6>Physical interface delivery modes</h6><dl class="variablelist"><dt class="varlistentry"><span class="term">vepa</span></dt><dd><div class="para">
+ All VMs' packets are sent to the external bridge. Packets whose destination is a VM on the same host as where the packet originates from are sent back to the host by the VEPA capable bridge (today's bridges are typically not VEPA capable).
+ </div></dd><dt class="varlistentry"><span class="term">bridge</span></dt><dd><div class="para">
+ Packets whose destination is on the same host as where they originate from are directly delivered to the target macvtap device. Both origin and destination devices need to be in bridge mode for direct delivery. If either one of them is in vepa mode, a VEPA capable bridge is required.
+ </div></dd><dt class="varlistentry"><span class="term">private</span></dt><dd><div class="para">
+ All packets are sent to the external bridge and will only be delivered to a target VM on the same host if they are sent through an external router or gateway and that device sends them back to the host. This procedure is followed if either the source or destination device is in private mode.
+ </div></dd><dt class="varlistentry"><span class="term">passthrough</span></dt><dd><div class="para">
+ This feature attaches a virtual function of a SRIOV capable NIC directly to a VM without losing the migration capability. All packets are sent to the VF/IF of the configured network device. Depending on the capabilities of the device additional prerequisites or limitations may apply; for example, on Linux this requires kernel 2.6.38 or newer.
+ </div></dd></dl></div><div class="para">
+ Each of the four modes is configured by changing the domain xml file. Once this file is opened, change the mode setting as shown:
+ </div><pre class="screen">
+ <devices>
+ ...
+ <interface type='direct'>
+ <source dev='eth0' mode='vepa'/>
+ </interface>
+ </devices>
+</pre><div class="para">
+ The network access of direct attached guest virtual machines can be managed by the hardware switch to which the physical interface of the host machine is connected to.
+ </div><div class="para">
+ The interface can have additional parameters as shown below, if the switch is conforming to the IEEE 802.1Qbg standard. The parameters of the virtualport element are documented in more detail in the IEEE 802.1Qbg standard. The values are network specific and should be provided by the network administrator. In 802.1Qbg terms, the Virtual Station Interface (VSI) represents the virtual interface of a virtual machine.
+ </div><div class="para">
+ Note that IEEE 802.1Qbg requires a non-zero value for the VLAN ID. Also if the switch is conforming to the IEEE 802.1Qbh standard, the values are network specific and should be provided by the network administrator.
+ </div><div class="variablelist"><h6>Virtual Station Interface types</h6><dl class="variablelist"><dt class="varlistentry"><span class="term">managerid</span></dt><dd><div class="para">
+ The VSI Manager ID identifies the database containing the VSI type and instance definitions. This is an integer value and the value 0 is reserved.
+ </div></dd><dt class="varlistentry"><span class="term">typeid</span></dt><dd><div class="para">
+ The VSI Type ID identifies a VSI type characterizing the network access. VSI types are typically managed by network administrator. This is an integer value.
+ </div></dd><dt class="varlistentry"><span class="term">typeidversion</span></dt><dd><div class="para">
+ The VSI Type Version allows multiple versions of a VSI Type. This is an integer value.
+ </div></dd><dt class="varlistentry"><span class="term">instanceid</span></dt><dd><div class="para">
+ The VSI Instance ID Identifier is generated when a VSI instance (i.e. a virtual interface of a virtual machine) is created. This is a globally unique identifier.
+ </div></dd><dt class="varlistentry"><span class="term">profileid</span></dt><dd><div class="para">
+ The profile ID contains the name of the port profile that is to be applied onto this interface. This name is resolved by the port profile database into the network parameters from the port profile, and those network parameters will be applied to this interface.
+ </div></dd></dl></div><div class="para">
+ Each of the four types is configured by changing the domain xml file. Once this file is opened, change the mode setting as shown:
+ </div><pre class="screen">
+ <devices>
+ ...
+ <interface type='direct'>
+ <source dev='eth0.2' mode='vepa'/>
+ <virtualport type="802.1Qbg">
+ <parameters managerid="11" typeid="1193047" typeidversion="2" instanceid="09b11c53-8b5c-4eeb-8f00-d84eaa0aaa4f"/>
+ </virtualport>
+ </interface>
+ </devices>
+</pre><div class="para">
+ The profile ID is shown here:
+ </div><pre class="screen">
+ <devices>
+ ...
+ <interface type='direct'>
+ <source dev='eth0' mode='private'/>
+ <virtualport type='802.1Qbh'>
+ <parameters profileid='finance'/>
+ </virtualport>
+ </interface>
+ </devices>
+ ...
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest.html"><strong>Prev</strong>H.8. Attaching a virtual network to a 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-applying-network-filtering.html"><strong>Next</strong>H.10. Applying network filtering</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-cpu-allocation.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-cpu-allocation.html
new file mode 100644
index 0000000..36c71dd
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-cpu-allocation.html
@@ -0,0 +1,26 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.4. CPU allocation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sect-smbios-sys-info.html" title="J.3. SMBIOS system information" /><link rel="next" href="sect-cpu-tuning.html" title="J.5. CPU tuning" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-smbios-sys-info.html"><strong>Prev</strong></a></li><li clas
s="next"><a accesskey="n" href="sect-cpu-tuning.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-cpu-allocation"><div class="titlepage"><div><div><h2 class="title">J.4. CPU allocation</h2></div></div></div><div class="figure"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain></span>
+ ...
+ <span class="perl_Keyword"><vcpu</span><span class="perl_Others"> placement=</span><span class="perl_String">'static'</span><span class="perl_Others"> cpuset=</span><span class="perl_String">"1-4,^3,6"</span><span class="perl_Others"> current=</span><span class="perl_String">"1"</span><span class="perl_Keyword">></span>2<span class="perl_Keyword"></vcpu></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.7. CPU allocation</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-starttag"><cpu></code> element defines the maximum number of virtual CPUs allocated for the guest OS, which must be between 1 and the maximum supported by the hypervisor. This element can contain an optional <code class="sgmltag-attribute">cpuset</code> attribute, which is a comma-separated list of physical CPU numbers that domain process and virtual CPUs can be pinned to by default.
+ </div><div class="para">
+ Note that the pinning policy of domain process and virtual CPUs can be specified separately by using the <code class="sgmltag-attribute">cputune</code> attribute. If attribute <code class="sgmltag-attribute">emulatorpin</code> of <code class="sgmltag-starttag"><cputune></code> is specified, <code class="sgmltag-attribute">cpuset</code> specified by <code class="sgmltag-starttag"><vcpu></code> will be ingored.
+ </div><div class="para">
+ Similarly, virtual CPUs that have set a value for <code class="sgmltag-attribute">vcpupin</code> cause <code class="sgmltag-attribute">cpuset</code> settings to be ignored. For virtual CPUs where <code class="sgmltag-attribute">vcpupin</code> is not specified, it will be pinned to the physical CPUs specified by <code class="sgmltag-attribute">cpuset</code>. Each element in the <code class="sgmltag-attribute">cpuset</code> list is either a single CPU number, a range of CPU numbers, or a caret (^) followed by a CPU number to be excluded from a previous range. The sgmltagal attribute <code class="sgmltag-attribute">current</code> can be used to specify whether fewer than the maximum number of virtual CPUs should be enabled.
+ </div><div class="para">
+ The optional attribute <code class="sgmltag-attribute">placement</code> can be used to indicate the CPU placement mode for domain process, its value can be either <code class="sgmltag-attvalue">static</code> or <code class="sgmltag-attvalue">auto</code>, which defaults to <code class="sgmltag-attvalue">placement</code>, or <code class="sgmltag-attvalue">numatune</code>, or <code class="sgmltag-attvalue">static</code> if <code class="sgmltag-element">cpuset</code> is specified. <code class="sgmltag-attvalue">auto</code> indicates the domain process will be pinned to the advisory nodeset from querying numad, and the value of attribute <code class="sgmltag-attribute">cpuset</code> will be ignored if it's specified. If both <code class="sgmltag-attribute">cpuset</code> and <code class="sgmltag-attribute">placement</code> are not specified, or if placement is <code class="sgmltag-attvalue">static</code>, but no <code class="sgmltag-attribute">cpuset</code> is specified, the do
main process will be pinned to all the available physical CPUs.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-smbios-sys-info.html"><strong>Prev</strong>J.3. SMBIOS system information</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-cpu-tuning.html"><strong>Next</strong>J.5. CPU tuning</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-cpu-tuning.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-cpu-tuning.html
new file mode 100644
index 0000000..a12db9e
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-cpu-tuning.html
@@ -0,0 +1,67 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.5. CPU tuning</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sect-cpu-allocation.html" title="J.4. CPU allocation" /><link rel="next" href="sect-mem-back.html" title="J.6. Memory backing" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-cpu-allocation.html"><strong>Prev</strong></a></li><li class="next"><a
accesskey="n" href="sect-mem-back.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-cpu-tuning"><div class="titlepage"><div><div><h2 class="title">J.5. CPU tuning</h2></div></div></div><div class="figure" id="fig-cpu-tuning"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain></span>
+ ...
+ <span class="perl_Keyword"><cputune></span>
+ <span class="perl_Keyword"><vcpupin</span><span class="perl_Others"> vcpu=</span><span class="perl_String">"0"</span><span class="perl_Others"> cpuset=</span><span class="perl_String">"1-4,^2"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><vcpupin</span><span class="perl_Others"> vcpu=</span><span class="perl_String">"1"</span><span class="perl_Others"> cpuset=</span><span class="perl_String">"0,1"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><vcpupin</span><span class="perl_Others"> vcpu=</span><span class="perl_String">"2"</span><span class="perl_Others"> cpuset=</span><span class="perl_String">"2,3"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><vcpupin</span><span class="perl_Others"> vcpu=</span><span class="perl_String">"3"</span><span class="perl_Others"> cpuset=</span><span class="perl_String">"0,4"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><emulatorpin</span><span class="perl_Others"> cpuset=</span><span class="perl_String">"1-3"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><shares></span>2048<span class="perl_Keyword"></shares></span>
+ <span class="perl_Keyword"><period></span>1000000<span class="perl_Keyword"></period></span>
+ <span class="perl_Keyword"><quota></span>-1<span class="perl_Keyword"></quota></span>
+ <span class="perl_Keyword"><emulator_period></span>1000000<span class="perl_Keyword"></emulator_period></span>
+ <span class="perl_Keyword"><emulator_quota></span>-1<span class="perl_Keyword"></emulator_quota></span>
+ <span class="perl_Keyword"></cputune></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.8. CPU tuning</h6></div><br class="figure-break" /><div class="para">
+ Although all are optional, the components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-cpu-turn-elem"><h6>Table J.5. CPU tuning elements</h6><div class="table-contents"><table summary="CPU tuning elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><cputune></code>
+ </td><td class="">
+ Provides details regarding the CPU tunable parameters for the domain. This is optional.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><vcpupin></code>
+ </td><td class="">
+ Specifies which of host's physical CPUs the domain VCPU will be pinned to. If this is omitted, and attribute <code class="sgmltag-attribute">cpuset</code> of element <code class="sgmltag-starttag"><vcpu></code> is not specified, the vCPU is pinned to all the physical CPUs by default. It contains two required attributes, the attribute <code class="sgmltag-element">vcpu</code> specifies <code class="sgmltag-attribute">id</code>, and the attribute <code class="sgmltag-attribute">cpuset</code> is same as attribute <code class="sgmltag-attribute">cpuset</code> of element <code class="sgmltag-starttag"><vCPU></code>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><emulatorpin></code>
+ </td><td class="">
+ Specifies which of the host physical CPUs, the "emulator", a subset of a domains not including vcpu, will be pinned to. If this is omitted, and attribute <code class="sgmltag-attribute">cpuset</code> of element <code class="sgmltag-starttag"><vcpu></code> is not specified, the "emulator" is pinned to all the physical CPUs by default. It contains one required attribute <code class="sgmltag-attribute">cpuset</code> specifying which physical CPUs to pin to. <code class="sgmltag-element">emulatorpin</code> is not allowed if attribute <code class="sgmltag-attribute">placement</code> of element <code class="sgmltag-starttag"><vcpu></code> is <code class="sgmltag-attvalue">auto</code>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><shares></code>
+ </td><td class="">
+ Specifies the proportional weighted share for the domain. If this is omitted, it defaults to the OS provided defaults. If there is no unit for the value, itn is calculated relative to the setting of other guest virtual machines. For example, if a guest virtual machine is configured with value 2048 will get twice as much CPU time as a guest virtual machine configured with value 1024.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><period></code>
+ </td><td class="">
+ Specifies the enforcement intervalin microseconds. By using <code class="sgmltag-attribute">period</code>, each of the domain's vcpu will not be allowed to consume more than its alloted quota worth of runtime. This value should be within the following range: <code class="literal">1000-1000000</code>. A <code class="sgmltag-attribute">period></code> with a value of <code class="sgmltag-attvalue">0</code> means no value.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><quota></code>
+ </td><td class="">
+ Specifies the maximum allowed bandwidth in microseconds. A domain with <code class="sgmltag-element">quota</code> as any negative value indicates that the domain has infinite bandwidth, which means that it is not bandwidth controlled. The value should be within the following range:<code class="sgmltag-attvalue">1000 - 18446744073709551</code> or less than <code class="sgmltag-attvalue">0</code>. A <code class="sgmltag-attribute">quota</code> with value of <code class="sgmltag-attvalue">0</code> means no value. You can use this feature to ensure that all vcpus run at the same speed.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><emulator_period></code>
+ </td><td class="">
+ Specifies the enforcement interval in microseconds. Within an <code class="sgmltag-starttag"><emulator_period></code>, emulator threads (those excluding vcpus) of the domain will not be allowed to consume more than the <code class="sgmltag-starttag"><emulator_quota></code> worth of runtime. The <code class="sgmltag-starttag"><emulator_period></code> value should be in the following range: <code class="sgmltag-attvalue">1000 - 1000000</code>. An <code class="sgmltag-starttag"><emulator_period></code> with value of <code class="sgmltag-attvalue">0</code>, means no value.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><emulator_quota></code>
+ </td><td class="">
+ Specifies the maximum allowed bandwidth in microseconds for the domain's emulator threads (those excluding vcpus). A domain with an <code class="sgmltag-starttag"><emulator_quota></code> as a negative value indicates that the domain has infinite bandwidth for emulator threads (those excluding vcpus), which means that it is not bandwidth controlled. The value should be in the following range: <code class="sgmltag-attvalue">1000 - 18446744073709551</code>, or less than <code class="sgmltag-attvalue">0</code>. An <code class="sgmltag-starttag"><emulator_quota></code> with value <code class="sgmltag-attvalue">0</code> means no value.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-cpu-allocation.html"><strong>Prev</strong>J.4. CPU allocation</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-mem-back.html"><strong>Next</strong>J.6. Memory backing</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-dom-xml-op-sys-boot.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-dom-xml-op-sys-boot.html
new file mode 100644
index 0000000..963bf3c
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-dom-xml-op-sys-boot.html
@@ -0,0 +1,57 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.2. Operating system booting</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="next" href="sub-sect-op-sys-host-boot.html" title="J.2.2. Host bootloader" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-lib-dom-xml.html"><strong>Prev</strong></
a></li><li class="next"><a accesskey="n" href="sub-sect-op-sys-host-boot.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-dom-xml-op-sys-boot"><div class="titlepage"><div><div><h2 class="title">J.2. Operating system booting</h2></div></div></div><div class="para">
+ There are a number of different ways to boot virtual machines each with their own pros and cons. Each one is described in the sub-sections that follow and include: BIOS bootloader, Host bootloader, direct kerel boot, and container boot.
+ </div><div class="section" id="sub-sect-op-sys-boot-bios-boot"><div class="titlepage"><div><div><h3 class="title">J.2.1. BIOS bootloader</h3></div></div></div><div class="para">
+ Booting via the BIOS is available for hypervisors supporting full virtualization. In this case the BIOS has a boot order priority (floppy, harddisk, cdrom, network) determining where to obtain/find the boot image. The OS section of the domain XML contatins the information as follows:
+ </div><div class="figure" id="fig-op-sys-boot-bios-boot"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><os></span>
+ <span class="perl_Keyword"><type></span>hvm<span class="perl_Keyword"></type></span>
+ <span class="perl_Keyword"><loader></span>/usr/lib/xen/boot/hvmloader<span class="perl_Keyword"></loader></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> dev=</span><span class="perl_String">'hd'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> dev=</span><span class="perl_String">'cdrom'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><bootmenu</span><span class="perl_Others"> enable=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><smbios</span><span class="perl_Others"> mode=</span><span class="perl_String">'sysinfo'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><bios</span><span class="perl_Others"> useserial=</span><span class="perl_String">'yes'</span><span class="perl_Others"> rebootTimeout=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></os></span>
+ ...
+</pre></div><h6>Figure J.2. BOIS bootloader domain XML</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-biosbootloader-os"><h6>Table J.2. BIOS bootloader elements</h6><div class="table-contents"><table summary="BIOS bootloader elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><type></code>
+ </td><td class="">
+ Specifies the type of operating system to be booted on the guest virtual machine. <code class="sgmltag-attvalue">hvm</code> indicates that the OS is one designed to run on bare metal, so requires full virtualization. <code class="sgmltag-attvalue">linux</code> refers to an OS that supports the Xen 3 hypervisor guest ABI. There are also two optional attributes, <code class="sgmltag-attribute">arch</code> specifying the CPU architecture to virtualization, and <code class="sgmltag-attribute">machine</code> referring to the machine type. Refer to <a href="http://libvirt.org/formatcaps.html"><em class="citetitle">Driver Capabilities</em></a> for more information.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><loader></code>
+ </td><td class="">
+ refers to a piece of firmware that is used to assist the domain creation process. It is only needed for using Xen fully virtualized domains.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><boot></code>
+ </td><td class="">
+ takes one of the values:<code class="sgmltag-attvalue">fd</code>, <code class="sgmltag-attvalue">hd</code>, <code class="sgmltag-attvalue">cdrom</code> or <code class="sgmltag-attvalue">network</code> and is used to specify the next boot device to consider. The boot element can be repeated multiple times to setup a priority list of boot devices to try in turn. Multiple devices of the same type are sorted according to their targets while preserving the order of buses. After defining the domain, its XML configuration returned by libvirt (through virDomainGetXMLDesc) lists devices in the sorted order. Once sorted, the first device is marked as bootable. For more information see <a href="http://libvirt.org/formatdomain.html#elements"><em class="citetitle">BIOS bootloader</em></a>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><bootmenu></code>
+ </td><td class="">
+ determines whether or not to enable an interactive boot menu prompt on guest startup. The <code class="sgmltag-attribute">enable</code> attribute can be either <code class="sgmltag-attvalue">yes</code> or <code class="sgmltag-attvalue">no</code>. If not specified, the hypervisor default is used
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><smbios></code>
+ </td><td class="">
+ determines how SMBIOS information is made visible in the guest. The <code class="sgmltag-attribute">mode</code> attribute must be specified, as either <code class="sgmltag-attvalue">emulate</code> (lets the hypervisor generate all values), <code class="sgmltag-attvalue">host</code>(copies all of Block 0 and Block 1, except for the UUID, from the host's SMBIOS values; the virConnectGetSysinfo call can be used to see what values are copied), or <code class="sgmltag-attvalue">sysinfo</code> (uses the values in the sysinfo element). If not specified, the hypervisor default setting is used.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><bios></code>
+ </td><td class="">
+ This element has attribute <code class="sgmltag-attribute">useserial</code> with possible values <code class="sgmltag-attvalue">yes</code> or <code class="sgmltag-attvalue">no</code>. The attribute enables or disables Serial Graphics Adapter which allows users to see BIOS messages on a serial port. Therefore, one needs to have serial port defined. Note there is another attribute, <code class="sgmltag-attribute">rebootTimeout</code> that controls whether and after how long the guest should start booting again in case the boot fails (according to BIOS). The value is in milliseconds with maximum of <code class="sgmltag-attvalue">65535</code> and special value <code class="sgmltag-attvalue">-1</code> disables the reboot.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-lib-dom-xml.html"><strong>Prev</strong>Appendix J. Manipulating the domain xml</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="sub-sect-op-sys-host-boot.html"><strong>Next</strong>J.2.2. Host bootloader</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-dynamic-vNIC.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-dynamic-vNIC.html
new file mode 100644
index 0000000..fd18618
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-dynamic-vNIC.html
@@ -0,0 +1,51 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.16. Dynamically changing a host or a network bridge that is attached to a virtual NIC</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="sect-limit-redirection.html" title="25.15. Setting a limit on device redirection" /><link rel="next" href="chap-Virtualization_Administration_Guide-Storage_Concepts.html" title="Chapter 26. Storage concepts" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul cla
ss="docnav"><li class="previous"><a accesskey="p" href="sect-limit-redirection.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_Guide-Storage_Concepts.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-dynamic-vNIC"><div class="titlepage"><div><div><h2 class="title">25.16. Dynamically changing a host or a network bridge that is attached to a virtual NIC</h2></div></div></div><div class="para">
+ This section demonstrates how to move the vNIC of a guest from one bridge to another while the guest is running without compromising the guest
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Prepare guest with a configuration similar to the following:
+ </div><pre class="screen">
+<interface type='bridge'>
+ <mac address='52:54:00:4a:c9:5e'/>
+ <source bridge='virbr0'/>
+ <model type='virtio'/>
+</interface>
+</pre></li><li class="step"><div class="para">
+ Prepare an XML file for interface update:
+ </div><pre class="screen">#<code class="command"> cat br1.xml</code></pre><pre class="screen">
+<interface type='bridge'>
+ <mac address='52:54:00:4a:c9:5e'/>
+ <source bridge='virbr1'/>
+ <model type='virtio'/>
+</interface>
+</pre></li><li class="step"><div class="para">
+ Start the guest, confirm the guest's network functionality, and check that the guest's vnetX is connected to the bridge you indicated.
+ </div><pre class="screen">
+<code class="command"># brctl show</code>
+bridge name bridge id STP enabled interfaces
+virbr0 8000.5254007da9f2 yes virbr0-nic
+
+vnet0
+virbr1 8000.525400682996 yes virbr1-nic
+</pre></li><li class="step"><div class="para">
+ Update the guest's network with the new interface parameters with the following command:
+ </div><pre class="screen">
+<code class="command"># virsh update-device test1 br1.xml </code>
+
+Device updated successfully
+
+</pre></li><li class="step"><div class="para">
+ On the guest, run <code class="command">service network restart</code>. The guest gets a new IP address for virbr1. Check the guest's vnet0 is connected to the new bridge(virbr1)
+ </div><pre class="screen">
+# <code class="command">brctl show</code>
+bridge name bridge id STP enabled interfaces
+virbr0 8000.5254007da9f2 yes virbr0-nic
+virbr1 8000.525400682996 yes virbr1-nic vnet0
+</pre></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-limit-redirection.html"><strong>Prev</strong>25.15. Setting a limit on device redirection</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_Administration_Guide-Storage_Concepts.html"><strong>Next</strong>Chapter 26. Storage concepts</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-expand-disk-image.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-expand-disk-image.html
new file mode 100644
index 0000000..241c8fb
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-expand-disk-image.html
@@ -0,0 +1,84 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.8.2. Expanding a disk image</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-virt-resize.html" title="G.8. virt-resize: resizing guests offline" /><link rel="prev" href="sect-virt-resize.html" title="G.8. virt-resize: resizing guests offline" /><link rel="next" href="sect-virt-inspector.html" title="G.9. virt-inspector: inspecting guests" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-virt-resize.html"><stro
ng>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-virt-inspector.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-expand-disk-image"><div class="titlepage"><div><div><h3 class="title">G.8.2. Expanding a disk image</h3></div></div></div><div class="para">
+ This section demonstrates a simple case of expanding a disk image:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Locate the disk image to be resized. You can use the command <code class="command">virsh dumpxml GuestName</code> for a libvirt guest.
+ </div></li><li class="listitem"><div class="para">
+ Decide on how you wish to expand the guest. Run <code class="command">virt-df -h</code> and <code class="command">virt-list-partitions -lh</code> on the guest disk, as shown in the following output:
+ </div><pre class="screen">
+# virt-df -h /dev/vg_guests/RHEL6
+Filesystem Size Used Available Use%
+RHEL6:/dev/sda1 98.7M 10.0M 83.6M 11%
+RHEL6:/dev/VolGroup00/LogVol00 6.8G 2.2G 4.3G 32%
+
+# virt-list-partitions -lh /dev/vg_guests/RHEL6
+/dev/sda1 ext3 101.9M
+/dev/sda2 pv 7.9G
+</pre></li></ol></div><div class="para">
+ This example will demonstrate how to:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Increase the size of the first (boot) partition, from approximately 100MB to 500MB.
+ </div></li><li class="listitem"><div class="para">
+ Increase the total disk size from 8GB to 16GB.
+ </div></li><li class="listitem"><div class="para">
+ Expand the second partition to fill the remaining space.
+ </div></li><li class="listitem"><div class="para">
+ Expand <code class="filename">/dev/VolGroup00/LogVol00</code> to fill the new space in the second partition.
+ </div></li></ul></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Make sure the guest is shut down.
+ </div></li><li class="listitem"><div class="para">
+ Rename the original disk as the backup. How you do this depends on the host storage environment for the original disk. If it is stored as a file, use the <code class="command">mv</code> command. For logical volumes (as demonstrated in this example), use <code class="command">lvrename</code>:
+ </div><pre class="screen">
+# lvrename /dev/vg_guests/RHEL6 /dev/vg_guests/RHEL6.backup
+</pre></li><li class="listitem"><div class="para">
+ Create the new disk. The requirements in this example are to expand the total disk size up to 16GB. Since logical volumes are used here, the following command is used:
+ </div><pre class="screen">
+# lvcreate -L 16G -n RHEL6 /dev/vg_guests
+Logical volume "RHEL6" created
+</pre></li><li class="listitem"><div class="para">
+ The requirements from step 2 are expressed by this command:
+ </div><pre class="screen">
+# virt-resize \
+ /dev/vg_guests/RHEL6.backup /dev/vg_guests/RHEL6 \
+ --resize /dev/sda1=500M \
+ --expand /dev/sda2 \
+ --LV-expand /dev/VolGroup00/LogVol00
+</pre><div class="para">
+ The first two arguments are the input disk and output disk. <code class="command">--resize /dev/sda1=500M</code> resizes the first partition up to 500MB. <code class="command">--expand /dev/sda2</code> expands the second partition to fill all remaining space. <code class="command">--LV-expand /dev/VolGroup00/LogVol00</code> expands the guest logical volume to fill the extra space in the second partition.
+ </div><div class="para">
+ <code class="command">virt-resize</code> describes what it is doing in the output:
+ </div><pre class="screen">
+Summary of changes:
+ /dev/sda1: partition will be resized from 101.9M to 500.0M
+ /dev/sda1: content will be expanded using the 'resize2fs' method
+ /dev/sda2: partition will be resized from 7.9G to 15.5G
+ /dev/sda2: content will be expanded using the 'pvresize' method
+ /dev/VolGroup00/LogVol00: LV will be expanded to maximum size
+ /dev/VolGroup00/LogVol00: content will be expanded using the 'resize2fs' method
+ Copying /dev/sda1 ...
+ [#####################################################]
+ Copying /dev/sda2 ...
+ [#####################################################]
+ Expanding /dev/sda1 using the 'resize2fs' method
+ Expanding /dev/sda2 using the 'pvresize' method
+ Expanding /dev/VolGroup00/LogVol00 using the 'resize2fs' method
+</pre></li><li class="listitem"><div class="para">
+ Try to boot the virtual machine. If it works (and after testing it thoroughly) you can delete the backup disk. If it fails, shut down the virtual machine, delete the new disk, and rename the backup disk back to its original name.
+ </div></li><li class="listitem"><div class="para">
+ Use <code class="command">virt-df</code> and/or <code class="command">virt-list-partitions</code> to show the new size:
+ </div><pre class="screen">
+# virt-df -h /dev/vg_pin/RHEL6
+ Filesystem Size Used Available Use%
+ RHEL6:/dev/sda1 484.4M 10.8M 448.6M 3%
+ RHEL6:/dev/VolGroup00/LogVol00 14.3G 2.2G 11.4G 16%
+</pre></li></ol></div><div class="para">
+ Resizing guests is not an exact science. If <code class="command">virt-resize</code> fails, there are a number of tips that you can review and attempt in the virt-resize(1) man page. For some older Red Hat Enterprise Linux guests, you may need to pay particular attention to the tip regarding GRUB.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-virt-resize.html"><strong>Prev</strong>G.8. virt-resize: resizing guests offline</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-virt-inspector.html"><strong>Next</strong>G.9. virt-inspector: inspecting guests</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-gracefully-shut-down-guests.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-gracefully-shut-down-guests.html
new file mode 100644
index 0000000..98fd85a
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-gracefully-shut-down-guests.html
@@ -0,0 +1,27 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.10. Gracefully shutting down guests</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server.html" title="25.9. Configuring a VNC Server" /><link rel="next" href="sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers.html" title="25.11. Virtual machine timer management with libvirt" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-Tips_and_tricks-Configuring_a_VNC_Server.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-gracefully-shut-down-guests"><div class="titlepage"><div><div><h2 class="title">25.10. Gracefully shutting down guests</h2></div></div></div><div class="para">
+ Installing virtualized Fedora 19 guests with the <code class="option">Minimal installation</code> option will not install the <span class="package">acpid</span> package.
+ </div><div class="para">
+ Without the <span class="package">acpid</span> package, the Fedora guest does not shut down when the <code class="command">virsh shutdown</code> command is executed. The <code class="command">virsh shutdown</code> command is designed to gracefully shut down guests.
+ </div><div class="para">
+ Using <code class="command">virsh shutdown</code> is easier and safer for system administration. Without graceful shut down with the <code class="command">virsh shutdown</code> command a system administrator must log into a guest manually or send the <span class="keycap"><strong>Ctrl</strong></span>-<span class="keycap"><strong>Alt</strong></span>-<span class="keycap"><strong>Del</strong></span> key combination to each guest.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Other virtualized operating systems may be affected by this issue. The <code class="command">virsh shutdown</code> command requires that the guest operating system is configured to handle ACPI shut down requests. Many operating systems require additional configuration on the guest operating system to accept ACPI shut down requests.
+ </div></div></div><div class="procedure"><h6>Procedure 25.1. Workaround for Fedora</h6><ol class="1"><li class="step"><p class="title"><strong>Install the acpid package</strong></p><div class="para">
+ The <code class="command">acpid</code> service listen and processes ACPI requests.
+ </div><div class="para">
+ Log into the guest and install the <span class="package">acpid</span> package on the guest:
+ </div><pre class="screen"># yum install acpid</pre></li><li class="step"><p class="title"><strong>Enable the acpid service</strong></p><div class="para">
+ Set the <code class="systemitem">acpid</code> service to start during the guest boot sequence and start the service:
+ </div><pre class="screen"># chkconfig acpid on
+# service acpid start</pre></li></ol></div><div class="para">
+ The guest is now configured to shut down when the <code class="command">virsh shutdown</code> command is used.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server.html"><strong>Prev</strong>25.9. 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-Tips_and_tricks-Libvirt_Managed_Timers.html"><strong>Next</strong>25.11. Virtual machine timer management with libv...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-guest-cpu-model-config.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-guest-cpu-model-config.html
new file mode 100644
index 0000000..9b8f5bc
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-guest-cpu-model-config.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.14. Guest CPU model configuration</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="prev" href="sub-sect-blkresize.html" title="E.13.3. Using blockresize to change the size of a domain path" /><link rel="next" href="sect-learn-about-host-cpu.html" title="E.14.2. Learning about the host CPU model" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="
docnav"><li class="previous"><a accesskey="p" href="sub-sect-blkresize.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-learn-about-host-cpu.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-guest-cpu-model-config"><div class="titlepage"><div><div><h2 class="title">E.14. Guest CPU model configuration</h2></div></div></div><div class="section" id="sect-guest-cpu-intro"><div class="titlepage"><div><div><h3 class="title">E.14.1. Introduction</h3></div></div></div><div class="para">
+ Every hypervisor has its own policy for what a guest will see for its CPUs by default. Whereas some hypervisors decide which CPU host features will be available for the guest, QEMU/KVM presents the guest with a generic model named <span class="bold bold"><strong>qemu32</strong></span> or <span class="bold bold"><strong>qemu64</strong></span>. These hypervisors perform more advanced filtering, classifying all physical CPUs into a handful of groups and have one baseline CPU model for each group that is presented to the guest. Such behavior enables the safe migration of guests between hosts, provided they all have physical CPUs that classify into the same group. libvirt does not typically enforce policy itself, rather it provides the mechanism on which the higher layers define their own desired policy. Understanding how to obtain CPU model information and define a suitable guest CPU model is critical to ensure guest migration is successful between hosts. Note that a hypervi
sor can only emulate features that it is aware of and features that were created after the hypervisor was released may not be emulated.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-blkresize.html"><strong>Prev</strong>E.13.3. Using blockresize to change the size of 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-learn-about-host-cpu.html"><strong>Next</strong>E.14.2. Learning about the host CPU model</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-learn-about-host-cpu.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-learn-about-host-cpu.html
new file mode 100644
index 0000000..ced5c88
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-learn-about-host-cpu.html
@@ -0,0 +1,44 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.14.2. Learning about the host CPU model</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-guest-cpu-model-config.html" title="E.14. Guest CPU model configuration" /><link rel="prev" href="sect-guest-cpu-model-config.html" title="E.14. Guest CPU model configuration" /><link rel="next" href="apes14s03.html" title="E.14.3. Determining a compatible CPU model to suit a pool of hosts" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="
sect-guest-cpu-model-config.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apes14s03.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-learn-about-host-cpu"><div class="titlepage"><div><div><h3 class="title">E.14.2. Learning about the host CPU model</h3></div></div></div><div class="para">
+ The <code class="command">virsh capabilities</code> command displays an XML document describing the capabilities of the hypervisor connection and host. The XML schema displayed has been extended to provide information about the host CPU model. One of the big challenges in describing a CPU model is that every architecture has a different approach to exposing their capabilities. On x86, the capabilities of a modern CPU are exposed via the CPUID instruction. Essentially this comes down to a set of 32-bit integers with each bit given a specific meaning. Fortunately AMD and Intel agree on common semantics for these bits. Other hypervisors expose the notion of CPUID masks directly in their guest configuration format. However, QEMU/KVM supports far more than just the x86 architecture, so CPUID is clearly not suitable as the canonical configuration format. QEMU ended up using a scheme which combines a CPU model name string, with a set of named flags. On x86, the CPU model maps t
o a baseline CPUID mask, and the flags can be used to then toggle bits in the mask on or off. libvirt decided to follow this lead and uses a combination of a model name and flags. Here is an example of what libvirt reports as the capabilities on a development workstation:
+ </div><pre class="screen">
+# virsh capabilities
+<capabilities>
+
+ <host>
+ <uuid>c4a68e53-3f41-6d9e-baaf-d33a181ccfa0</uuid>
+ <cpu>
+ <arch>x86_64</arch>
+ <model>core2duo</model>
+ <topology sockets='1' cores='4' threads='1'/>
+ <feature name='lahf_lm'/>
+ <feature name='sse4.1'/>
+ <feature name='xtpr'/>
+ <feature name='cx16'/>
+ <feature name='tm2'/>
+ <feature name='est'/>
+ <feature name='vmx'/>
+ <feature name='ds_cpl'/>
+ <feature name='pbe'/>
+ <feature name='tm'/>
+ <feature name='ht'/>
+ <feature name='ss'/>
+ <feature name='acpi'/>
+ <feature name='ds'/>
+ </cpu>
+
+ ... snip ...
+ </host>
+
+</capabilities>
+</pre><div class="para">
+ It is not practical to have a database listing all known CPU models, so libvirt has a small list of baseline CPU model names. It chooses the one that shares the greatest number of CPUID bits with the actual host CPU and then lists the remaining bits as named features. Notice that libvirt does not display which features the baseline CPU contains. This might seem like a flaw at first, but as will be explained in this section, it is not actually necessary to know this information.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-guest-cpu-model-config.html"><strong>Prev</strong>E.14. Guest CPU model 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="apes14s03.html"><strong>Next</strong>E.14.3. Determining a compatible CPU model to sui...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libguestfs-more-docs.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libguestfs-more-docs.html
new file mode 100644
index 0000000..37ca191
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libguestfs-more-docs.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.13. Where to find further documentation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /><link rel="prev" href="sect-libguestfs-troubleshoot.html" title="G.12. Troubleshooting" /><link rel="next" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html" title="Appendix H. Virtual Networking" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="
docnav"><li class="previous"><a accesskey="p" href="sect-libguestfs-troubleshoot.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-libguestfs-more-docs"><div class="titlepage"><div><div><h2 class="title">G.13. Where to find further documentation</h2></div></div></div><div class="para">
+ The primary source for documentation for libguestfs and the tools are the Unix man pages. The API is documented in guestfs(3). guestfish is documented in guestfish(1). The virt tools are documented in their own man pages (eg. virt-df(1)).
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libguestfs-troubleshoot.html"><strong>Prev</strong>G.12. 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="chap-Virtualization_Administration_Guide-Virtual_Networking.html"><strong>Next</strong>Appendix H. Virtual Networking</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libguestfs-troubleshoot.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libguestfs-troubleshoot.html
new file mode 100644
index 0000000..42fea0f
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libguestfs-troubleshoot.html
@@ -0,0 +1,16 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.12. Troubleshooting</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /><link rel="prev" href="sect-Using-API-Programming-Languages.html" title="G.11. Using the API from Programming Languages" /><link rel="next" href="sect-libguestfs-more-docs.html" title="G.13. Where to find further documentation" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><u
l class="docnav"><li class="previous"><a accesskey="p" href="sect-Using-API-Programming-Languages.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-libguestfs-more-docs.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-libguestfs-troubleshoot"><div class="titlepage"><div><div><h2 class="title">G.12. Troubleshooting</h2></div></div></div><div class="para">
+ A test tool is available to check that libguestfs is working. Run the following command after installing libguestfs (root access not required) to test for normal operation:
+ </div><pre class="screen">
+$ libguestfs-test-tool
+</pre><div class="para">
+ This tool prints a large amount of text to test the operation of libguestfs. If the test is successful, the following text will appear near the end of the output:
+ </div><pre class="screen">===== TEST FINISHED OK =====</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Using-API-Programming-Languages.html"><strong>Prev</strong>G.11. Using the API from Programming Languages</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-libguestfs-more-docs.html"><strong>Next</strong>G.13. Where to find further documentation</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-blk-io-tuning.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-blk-io-tuning.html
new file mode 100644
index 0000000..3554fa7
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-blk-io-tuning.html
@@ -0,0 +1,46 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.9. Block I/O tuning</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sect-libvirt-dom-xml-numa-node-tuning.html" title="J.8. NUMA node tuning" /><link rel="next" href="sect-libvirt-dom-xml-res-part.html" title="J.10. Resource partitioning" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-numa-node-
tuning.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-libvirt-dom-xml-res-part.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-libvirt-dom-xml-blk-io-tuning"><div class="titlepage"><div><div><h2 class="title">J.9. Block I/O tuning</h2></div></div></div><div class="figure" id="fig-blk-io-tuning"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain></span>
+ ...
+ <span class="perl_Keyword"><blkiotune></span>
+ <span class="perl_Keyword"><weight></span>800<span class="perl_Keyword"></weight></span>
+ <span class="perl_Keyword"><device></span>
+ <span class="perl_Keyword"><path></span>/dev/sda<span class="perl_Keyword"></path></span>
+ <span class="perl_Keyword"><weight></span>1000<span class="perl_Keyword"></weight></span>
+ <span class="perl_Keyword"></device></span>
+ <span class="perl_Keyword"><device></span>
+ <span class="perl_Keyword"><path></span>/dev/sdb<span class="perl_Keyword"></path></span>
+ <span class="perl_Keyword"><weight></span>500<span class="perl_Keyword"></weight></span>
+ <span class="perl_Keyword"></device></span>
+ <span class="perl_Keyword"></blkiotune></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.12. Block I/O tuning</h6></div><br class="figure-break" /><div class="para">
+ Although all are optional, the components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-blk-io-elem"><h6>Table J.8. Block I/O tuning elements</h6><div class="table-contents"><table summary="Block I/O tuning elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><blkiotune></code>
+ </td><td class="">
+ This optional element provides the ability to tune Blkio cgroup tunable parameters for the domain. If this is omitted, it defaults to the OS provided defaults.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><weight></code>
+ </td><td class="">
+ This optional weight element is the overall I/O weight of the guest. The value should be within the range 100 - 1000.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><device></code>
+ </td><td class="">
+ The domain may have multiple <code class="sgmltag-starttag"><device></code> elements that further tune the weights for each host block device in use by the domain. Note that multiple guest disks can share a single host block device. In addition, as they are backed by files within the same host file system, this tuning parameter is at the global domain level, rather than being associated with each guest disk device (contrast this to the <code class="sgmltag-starttag"><iotune></code> element which can be applied to a single <code class="sgmltag-starttag"><disk></code>). Each device element has two mandatory sub-elements, <code class="sgmltag-starttag"><path></code> describing the absolute path of the device, and <code class="sgmltag-starttag"><weight></code> giving the relative weight of that device, which has an acceptable range of 100 - 1000.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-numa-node-tuning.html"><strong>Prev</strong>J.8. NUMA node tuning</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-libvirt-dom-xml-res-part.html"><strong>Next</strong>J.10. Resource partitioning</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-cpu-model-top.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-cpu-model-top.html
new file mode 100644
index 0000000..9adda36
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-cpu-model-top.html
@@ -0,0 +1,124 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.11. CPU model and topology</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sect-libvirt-dom-xml-res-part.html" title="J.10. Resource partitioning" /><link rel="next" href="sect-libvirt-dom-xml-event-config.html" title="J.12. Events configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-res-part.
html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-libvirt-dom-xml-event-config.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-libvirt-dom-xml-cpu-model-top"><div class="titlepage"><div><div><h2 class="title">J.11. CPU model and topology</h2></div></div></div><div class="para">
+ This section covers the requirements for CPU model. Its features and topology is specified using the following elements from the domain XML:
+ </div><div class="figure" id="fig-xml-cpu-model-top"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><cpu</span><span class="perl_Others"> match=</span><span class="perl_String">'exact'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><model</span><span class="perl_Others"> fallback=</span><span class="perl_String">'allow'</span><span class="perl_Keyword">></span>core2duo<span class="perl_Keyword"></model></span>
+ <span class="perl_Keyword"><vendor></span>Intel<span class="perl_Keyword"></vendor></span>
+ <span class="perl_Keyword"><topology</span><span class="perl_Others"> sockets=</span><span class="perl_String">'1'</span><span class="perl_Others"> cores=</span><span class="perl_String">'2'</span><span class="perl_Others"> threads=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><feature</span><span class="perl_Others"> policy=</span><span class="perl_String">'disable'</span><span class="perl_Others"> name=</span><span class="perl_String">'lahf_lm'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></cpu></span>
+ ...
+
+</pre></div><h6>Figure J.14. CPU model and topology example 1</h6></div><br class="figure-break" /><div class="figure" id="fig-xml-cpu-model-top2"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><cpu</span><span class="perl_Others"> mode=</span><span class="perl_String">'host-model'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><model</span><span class="perl_Others"> fallback=</span><span class="perl_String">'forbid'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><topology</span><span class="perl_Others"> sockets=</span><span class="perl_String">'1'</span><span class="perl_Others"> cores=</span><span class="perl_String">'2'</span><span class="perl_Others"> threads=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+<span class="perl_Keyword"></cpu></span>
+ ...
+</pre></div><h6>Figure J.15. CPU model and topology example 2</h6></div><br class="figure-break" /><div class="figure" id="fig-xml-cpu-model-top3"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><cpu</span><span class="perl_Others"> mode=</span><span class="perl_String">'host-passthrough'</span><span class="perl_Keyword">/></span>
+
+</pre></div><h6>Figure J.16. CPU model and topology example 3</h6></div><br class="figure-break" /><div class="para">
+ In cases where no restrictions are to be put on either the CPU model nor its features, a simpler cpu element such as the following may be used.
+ </div><div class="figure" id="fig-xml-cpu-model-top4"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><cpu></span>
+ <span class="perl_Keyword"><topology</span><span class="perl_Others"> sockets=</span><span class="perl_String">'1'</span><span class="perl_Others"> cores=</span><span class="perl_String">'2'</span><span class="perl_Others"> threads=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></cpu></span>
+ ...
+
+</pre></div><h6>Figure J.17. CPU model and topology example 4</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-cpu-model-elem"><h6>Table J.9. CPU model and topology elements</h6><div class="table-contents"><table summary="CPU model and topology elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><cpu></code>
+ </td><td class="">
+ This is the main container for describing guest CPU requirements.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><match></code>
+ </td><td class="">
+ Specifies how the virtual CPU is provided to the guest match for these requirements. The <code class="sgmltag-attribute">match</code> attribute can be omitted if topology is the only element within <code class="sgmltag-starttag"><cpu></code>. Possible values for the <code class="sgmltag-attribute">match</code> attribute are:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">minimum</code> - the specified CPU model and features describes the minimum requested CPU.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">exact</code> - the virtual CPU provided to the guest will exactly match the specification
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">strict</code> - the guest will not be created unless the host CPU exactly matches the specification.
+ </div></li></ul></div>
+ Note that the <code class="sgmltag-attribute">match</code> attribute can be omitted and will default to <code class="sgmltag-attvalue">exact</code>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><mode></code>
+ </td><td class="">
+ This optional attribute may be used to make it easier to configure a guest CPU to be as close to the host CPU as possible. Possible values for the mode attribute are:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">custom</code> - describes how the CPU is presented to the guest. This is the default setting when the <code class="sgmltag-attribute">mode</code> attribute is not specified. This mode makes it so that a persistent guest will see the same hardware no matter what host the guest is booted on.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">host-model</code> - this is essentially a shortcut to copying host CPU definition from the capabilities XML into the domain XML. As the CPU definition is copied just before starting a domain, the same XML can be used on different hosts while still providing the best guest CPU each host supports. Neither the <code class="sgmltag-attribute">match</code> attribute nor any feature elements can be used in this mode. For more information see <a href="http://libvirt.org/formatdomain.html">libvirt domain XML CPU models</a>
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">host-passthrough</code> With this mode, the CPU visible to the guest is exactly the same as the host CPU including elements that cause errors within libvirt. The obvious the downside of this mode is that the guest environment cannot be reproduced on different hardware and therefore this mode is recommended with great caution. Neither <code class="sgmltag-element">model</code> nor <code class="sgmltag-element">feature</code> elements are allowed in this mode.
+ </div></li><li class="listitem"><div class="para">
+ Note that in both <code class="sgmltag-element">host-model</code> and <code class="sgmltag-element">host-passthrough</code> mode, the real (approximate in host-passthrough mode) CPU definition which would be used on current host can be determined by specifying VIR_DOMAIN_XML_UPDATE_CPU flag when calling virDomainGetXMLDesc API. When running a guest that might be prone to operating system reactivation when presented with different hardware, and which will be migrated between hosts with different capabilities, you can use this output to rewrite XML to the custom mode for more robust migration.
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><model></code>
+ </td><td class="">
+ Specifies CPU model requested by the guest. The list of available CPU models and their definition can be found in <code class="filename">cpu_map.xml</code> file installed in libvirt's data directory. If a hypervisor is not able to use the exact CPU model, libvirt automatically falls back to a closest model supported by the hypervisor while maintaining the list of CPU features. An optional <code class="sgmltag-attribute">fallback</code> attribute can be used to forbid this behavior, in which case an attempt to start a domain requesting an unsupported CPU model will fail. Supported values for fallback attribute are: <code class="sgmltag-attvalue">allow</code> (this is the default), and <code class="sgmltag-attvalue">forbid</code>. The optional <code class="sgmltag-attribute">vendor_id</code> attribute can be used to set the vendor id seen by the guest. It must be exactly 12 characters long. If not set, the vendor id of the host is used. Typical possible values are <code
class="sgmltag-attvalue">AuthenticAMD</code> and <code class="sgmltag-attvalue">GenuineIntel</code>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><vendor></code>
+ </td><td class="">
+ Specifies CPU vendor requested by the guest. If this element is missing, the guest runs on a CPU matching given features regardless of its vendor. The list of supported vendors can be found in <code class="filename">cpu_map.xml</code>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><topology></code>
+ </td><td class="">
+ Specifies requested topology of virtual CPU provided to the guest. Three non-zero values have to be given for sockets, cores, and threads: total number of CPU sockets, number of cores per socket, and number of threads per core, respectively.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><feature></code>
+ </td><td class="">
+ Can contain zero or more elements used to fine-tune features provided by the selected CPU model. The list of known feature names can be found in the same file as CPU models. The meaning of each feature element depends on its policy attribute, which has to be set to one of the following values:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">force</code> - forces the virtual to be supported regardless of whether it is actually supported by host CPU.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">require</code> - dictates that guest creation will fail unless the feature is supported by host CPU. This is the default setting
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">optional</code> - this feature is supported by virtual CPU but and only if it is supported by host CPU.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">disable</code> - this is not supported by virtual CPU.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">forbid</code> - guest creation will fail if the feature is supported by host CPU.
+ </div></li></ul></div>
+
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="section" id="sub-sect-libvirt-dom-xml-res-part-guest-numa"><div class="titlepage"><div><div><h3 class="title">J.11.1. Guest NUMA topology</h3></div></div></div><div class="para">
+ Guest NUMA topology can be specifed using the numa element and the following from the domain XML:
+ </div><div class="figure" id="fig-xml-cpu-model-top-numa"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><cpu></span>
+ ...
+ <span class="perl_Keyword"><numa></span>
+ <span class="perl_Keyword"><cell</span><span class="perl_Others"> cpus=</span><span class="perl_String">'0-3'</span><span class="perl_Others"> memory=</span><span class="perl_String">'512000'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><cell</span><span class="perl_Others"> cpus=</span><span class="perl_String">'4-7'</span><span class="perl_Others"> memory=</span><span class="perl_String">'512000'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></numa></span>
+ ...
+ <span class="perl_Keyword"></cpu></span>
+ ...
+</pre></div><h6>Figure J.18. Guest NUMA topology</h6></div><br class="figure-break" /><div class="para">
+ Each cell element specifies a NUMA cell or a NUMA node. <code class="sgmltag-attribute">cpus</code> specifies the CPU or range of CPUs that are part of the node. <code class="sgmltag-attribute">memory</code> specifies the node memory in kibibytes (i.e. blocks of 1024 bytes). Each cell or node is assigned <code class="sgmltag-attribute">cellid</code> or <code class="sgmltag-attribute">nodeid</code> in increasing order starting from 0.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-res-part.html"><strong>Prev</strong>J.10. Resource partitioning</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-libvirt-dom-xml-event-config.html"><strong>Next</strong>J.12. Events configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-devices.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-devices.html
new file mode 100644
index 0000000..b55e350
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-devices.html
@@ -0,0 +1,201 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16. Devices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sect-libvirt-dom-xml-time-keep.html" title="J.15. Time keeping" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-filesystems.html" title="J.16.2. Filesystems" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-time-keep.
html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-filesystems.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-libvirt-dom-xml-devices"><div class="titlepage"><div><div><h2 class="title">J.16. Devices</h2></div></div></div><div class="para">
+ This set of XML elements are all used to describe devices provided to the guest domain. All of the devices below are indicated as children of the main devices element.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><emulator></span>/usr/lib/xen/bin/qemu-dm<span class="perl_Keyword"></emulator></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.23. Devices - child elements</h6></div><br class="figure-break" /><div class="para">
+ The contents of the <code class="sgmltag-starttag"><emulator></code> element specify the fully qualified path to the device model emulator binary. The capabilities XML specifies the recommended default emulator to use for each particular domain type or architecture combination.
+ </div><div class="section" id="sub-sect-libvirt-dom-xml-devices"><div class="titlepage"><div><div><h3 class="title">J.16.1. Hard drives, floppy disks, CDROMs</h3></div></div></div><div class="para">
+ This section of the domain XML specifies any device that looks like a disk, be it a floppy, harddisk, cdrom, or paravirtualized driver is specified via the disk element.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-cds"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'file'</span><span class="perl_Others"> snapshot=</span><span class="perl_String">'external'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">"tap"</span><span class="perl_Others"> type=</span><span class="perl_String">"aio"</span><span class="perl_Others"> cache=</span><span class="perl_String">"default"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> file=</span><span class="perl_String">'/var/lib/xen/images/fv0'</span><span class="perl_Others"> startupPolicy=</span><span class="perl_String">'optional'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><seclabel</span><span class="perl_Others"> relabel=</span><span class="perl_String">'no'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></source></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hda'</span><span class="perl_Others"> bus=</span><span class="perl_String">'ide'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><iotune></span>
+ <span class="perl_Keyword"><total_bytes_sec></span>10000000<span class="perl_Keyword"></total_bytes_sec></span>
+ <span class="perl_Keyword"><read_iops_sec></span>400000<span class="perl_Keyword"></read_iops_sec></span>
+ <span class="perl_Keyword"><write_iops_sec></span>100000<span class="perl_Keyword"></write_iops_sec></span>
+ <span class="perl_Keyword"></iotune></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'2'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><encryption</span><span class="perl_Others"> type=</span><span class="perl_String">'...'</span><span class="perl_Keyword">></span>
+ ...
+ <span class="perl_Keyword"></encryption></span>
+ <span class="perl_Keyword"><shareable/></span>
+ <span class="perl_Keyword"><serial></span>
+ ...
+ <span class="perl_Keyword"></serial></span>
+ <span class="perl_Keyword"></disk></span>
+ ...
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">"qemu"</span><span class="perl_Others"> type=</span><span class="perl_String">"raw"</span><span class="perl_Others"> io=</span><span class="perl_String">"threads"</span><span class="perl_Others"> ioeventfd=</span><span class="perl_String">"on"</span><span class="perl_Others"> event_idx=</span><span class="perl_String">"off"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> protocol=</span><span class="perl_String">"sheepdog"</span><span class="perl_Others"> name=</span><span class="perl_String">"image_name"</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><host</span><span class="perl_Others"> name=</span><span class="perl_String">"hostname"</span><span class="perl_Others"> port=</span><span class="perl_String">"7000"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></source></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">"hdb"</span><span class="perl_Others"> bus=</span><span class="perl_String">"ide"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><transient/></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'drive'</span><span class="perl_Others"> controller=</span><span class="perl_String">'0'</span><span class="perl_Others"> bus=</span><span class="perl_String">'1'</span><span class="perl_Others"> unit=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">"qemu"</span><span class="perl_Others"> type=</span><span class="perl_String">"raw"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> protocol=</span><span class="perl_String">"rbd"</span><span class="perl_Others"> name=</span><span class="perl_String">"image_name2"</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><host</span><span class="perl_Others"> name=</span><span class="perl_String">"hostname"</span><span class="perl_Others"> port=</span><span class="perl_String">"7000"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></source></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">"hdd"</span><span class="perl_Others"> bus=</span><span class="perl_String">"ide"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><auth</span><span class="perl_Others"> username=</span><span class="perl_String">'myuser'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><secret</span><span class="perl_Others"> type=</span><span class="perl_String">'ceph'</span><span class="perl_Others"> usage=</span><span class="perl_String">'mypassid'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></auth></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'block'</span><span class="perl_Others"> device=</span><span class="perl_String">'cdrom'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">'qemu'</span><span class="perl_Others"> type=</span><span class="perl_String">'raw'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hdc'</span><span class="perl_Others"> bus=</span><span class="perl_String">'ide'</span><span class="perl_Others"> tray=</span><span class="perl_String">'open'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><readonly/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'block'</span><span class="perl_Others"> device=</span><span class="perl_String">'lun'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">'qemu'</span><span class="perl_Others"> type=</span><span class="perl_String">'raw'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> dev=</span><span class="perl_String">'/dev/sda'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'sda'</span><span class="perl_Others"> bus=</span><span class="perl_String">'scsi'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'drive'</span><span class="perl_Others"> controller=</span><span class="perl_String">'0'</span><span class="perl_Others"> bus=</span><span class="perl_String">'0'</span><span class="perl_Others"> target=</span><span class="perl_String">'3'</span><span class="perl_Others"> unit=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'block'</span><span class="perl_Others"> device=</span><span class="perl_String">'disk'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">'qemu'</span><span class="perl_Others"> type=</span><span class="perl_String">'raw'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> dev=</span><span class="perl_String">'/dev/sda'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><geometry</span><span class="perl_Others"> cyls=</span><span class="perl_String">'16383'</span><span class="perl_Others"> heads=</span><span class="perl_String">'16'</span><span class="perl_Others"> secs=</span><span class="perl_String">'63'</span><span class="perl_Others"> trans=</span><span class="perl_String">'lba'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><blockio</span><span class="perl_Others"> logical_block_size=</span><span class="perl_String">'512'</span><span class="perl_Others"> physical_block_size=</span><span class="perl_String">'4096'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hda'</span><span class="perl_Others"> bus=</span><span class="perl_String">'ide'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'volume'</span><span class="perl_Others"> device=</span><span class="perl_String">'disk'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">'qemu'</span><span class="perl_Others"> type=</span><span class="perl_String">'raw'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> pool=</span><span class="perl_String">'blk-pool0'</span><span class="perl_Others"> volume=</span><span class="perl_String">'blk-pool0-vol0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hda'</span><span class="perl_Others"> bus=</span><span class="perl_String">'ide'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.24. Devices - Hard drives, floppy disks, CDROMs</h6></div><br class="figure-break" /><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-disk"><div class="titlepage"><div><div><h4 class="title">J.16.1.1. Disk element</h4></div></div></div><div class="para">
+ The <code class="sgmltag-starttag"><disk></code> element is the main container for describing disks. The attribute <code class="sgmltag-attribute">type</code> can be used with the <code class="sgmltag-starttag"><disk></code> element. The following types are allowed:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">file</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">block</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">dir</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">network</code>
+ </div></li></ul></div><div class="para">
+ For more information, see <a href="http://libvirt.org/formatdomain.html">Disk Elements</a>
+ </div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-source"><div class="titlepage"><div><div><h4 class="title">J.16.1.2. Source element</h4></div></div></div><div class="para">
+ If the <code class="sgmltag-starttag"><disk type='file''></code>, then the <code class="sgmltag-attribute">file</code> attribute specifies the fully-qualified path to the file holding the disk. If the <code class="sgmltag-starttag"><disk type='block'></code>, then the <code class="sgmltag-attribute">dev</code> attribute specifies the path to the host device to serve as the disk. With both <code class="sgmltag-attvalue">file</code> and <code class="sgmltag-attvalue">block</code>, one or more optional sub-elements <code class="sgmltag-element">seclabel</code>, described below, can be used to override the domain security labeling policy for just that source file. If the disk type is <code class="sgmltag-attvalue">dir</code>, then the <code class="sgmltag-attribute">dir</code> attribute specifies the fully-qualified path to the directory to use as the disk. If the disk type is <code class="sgmltag-attvalue">network</code>, then the protocol attribute specifies t
he protocol to access to the requested image; possible values are <code class="sgmltag-attvalue">nbd</code>, <code class="sgmltag-attvalue">rbd</code>, <code class="sgmltag-attvalue">sheepdog</code> or <code class="sgmltag-attvalue">gluster</code>.
+ </div><div class="para">
+ If the protocol attribute is <code class="sgmltag-attvalue">rbd</code>, <code class="sgmltag-attvalue">sheepdog</code> or <code class="sgmltag-attvalue">gluster</code>, an additional attribute <code class="sgmltag-attvalue">name</code> is mandatory to specify which volume and or image will be used. When the disk type is <code class="sgmltag-attvalue">network</code>, the <code class="sgmltag-attvalue">source</code> may have zero or more <code class="sgmltag-element">host</code> sub-elements used to specify the hosts to connect, including: <code class="sgmltag-attvalue">type='dir'</code> and <code class="sgmltag-attvalue">type='network'</code>. For a <code class="sgmltag-attvalue">file</code> disk type which represents a cdrom or floppy (the device attribute), it is possible to define policy what to do with the disk if the source file is not accessible. This is done by manipulating the <code class="sgmltag-attribute">startupPolicy</code> attribute, with the following valu
es:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">mandatory</code> causes a failure if missing for any reason. This is the default setting.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">requisite</code> causes a failure if missing on boot up, drops if missing on migrate/restore/revert
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">optional</code> drops if missing at any start attempt
+ </div></li></ul></div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-mirror"><div class="titlepage"><div><div><h4 class="title">J.16.1.3. Mirror element</h4></div></div></div><div class="para">
+ This element is present if the hypervisor has started a <code class="command">BlockCopy</code> operation, where the <code class="sgmltag-starttag"><mirror></code> location in the attribute file will eventually have the same contents as the source, and with the file format in attribute format (which might differ from the format of the source). If an attribute ready is present, then it is known the disk is ready to pivot; otherwise, the disk is probably still copying. For now, this element only valid in output; it is ignored on input.
+ </div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-target"><div class="titlepage"><div><div><h4 class="title">J.16.1.4. Target element</h4></div></div></div><div class="para">
+ The <code class="sgmltag-starttag"><target></code> element controls the bus / device under which the disk is exposed to the guest OS. The dev attribute indicates the logical device name. The actual device name specified is not guaranteed to map to the device name in the guest OS. The optional bus attribute specifies the type of disk device to emulate; possible values are driver specific, with typical values being <code class="sgmltag-attvalue">ide</code>, <code class="sgmltag-attvalue">scsi</code>, <code class="sgmltag-attvalue">virtio</code>, <code class="sgmltag-attvalue">xen</code>, <code class="sgmltag-attvalue">usb</code> or <code class="sgmltag-attvalue">sata</code>. If omitted, the bus type is inferred from the style of the device name. eg, a device named <code class="filename">'sda'</code> will typically be exported using a SCSI bus. The optional attribute <code class="sgmltag-attribute">tray</code> indicates the tray status of the removable disks (i.e. CD
ROM or Floppy disk), the value can be either <code class="sgmltag-attvalue">open</code> or <code class="sgmltag-attvalue">closed</code>. The default setting is <code class="sgmltag-attvalue">closed</code>. For more information, see <a href="http://libvirt.org/formatdomain.html">target Elements</a>
+ </div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-iotune"><div class="titlepage"><div><div><h4 class="title">J.16.1.5. iotune</h4></div></div></div><div class="para">
+ The optional <code class="sgmltag-starttag"><iotune></code> element provides the ability to provide additional per-device I/O tuning, with values that can vary for each device (contrast this to the <code class="sgmltag-attvalue">blkiotune</code> element, which applies globally to the domain). This element has the following optional sub-elements. Note that any sub-element not specified or at all or specified with a value of <code class="sgmltag-attvalue">0</code> implies no limit.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><total_bytes_sec></code> - the total throughput limit in bytes per second. This element cannot be used with <code class="sgmltag-starttag"><read_bytes_sec></code> or <code class="sgmltag-starttag"><write_bytes_sec></code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><read_bytes_sec></code> - the read throughput limit in bytes per second.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><write_bytes_sec></code> - the write throughput limit in bytes per second.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><total_iops_sec></code> - the total I/O operations per second. This element cannot be used with <code class="sgmltag-starttag"><read_iops_sec></code> or <code class="sgmltag-starttag"><write_iops_sec></code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><read_iops_sec></code> - the read I/O operations per second.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><write_iops_sec></code> - the write I/O operations per second.
+ </div></li></ul></div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-driver"><div class="titlepage"><div><div><h4 class="title">J.16.1.6. driver</h4></div></div></div><div class="para">
+ The optional <code class="sgmltag-starttag"><driver></code> element allows specifying further details related to the hypervisor driver that is used to provide the disk. The following options may be used:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If the hypervisor supports multiple backend drivers, then the <code class="sgmltag-attribute">name</code> attribute selects the primary backend driver name, while the optional type attribute provides the sub-type. For a list of possible types refer to <a href="http://libvirt.org/formatdomain.html">Driver Elements</a>
+ </div></li><li class="listitem"><div class="para">
+ The optional <code class="sgmltag-attribute">cache</code> attribute controls the cache mechanism, possible values are: <code class="sgmltag-attvalue">default</code>, <code class="sgmltag-attvalue">none</code>, <code class="sgmltag-attvalue">writethrough</code>, <code class="sgmltag-attvalue">writeback</code>, <code class="sgmltag-attvalue">directsync</code> (similar to <code class="sgmltag-element">writethrough</code>, but it bypasses the host page cache) and <code class="sgmltag-attvalue">unsafe</code> (host may cache all disk io, and sync requests from guest are ignored).
+ </div></li><li class="listitem"><div class="para">
+ The optional <code class="sgmltag-attribute">error_policy</code> attribute controls how the hypervisor behaves on a disk read or write error, possible values are <code class="sgmltag-attvalue">stop</code>, <code class="sgmltag-attvalue">report</code>, <code class="sgmltag-attvalue">ignore</code>, and <code class="sgmltag-attvalue">enospace</code>. The default setting of <code class="sgmltag-attribute">error_policy</code> is <code class="sgmltag-attvalue">report</code>. There is also an optional <code class="sgmltag-attribute">rerror_policy</code> that controls behavior for read errors only. If no <code class="sgmltag-attribute">rerror_policy</code> is given, <code class="sgmltag-attribute">error_policy</code> is used for both read and write errors. If <code class="sgmltag-attribute">rerror_policy</code> is given, it overrides the <code class="sgmltag-attribute">error_policy</code> for read errors. Also note that <code class="sgmltag-attvalue">enospace</code> is not a
valid policy for read errors, so if <code class="sgmltag-attribute">error_policy</code> is set to <code class="sgmltag-attvalue">enospace</code> and <code class="sgmltag-attribute">no rerror_policy</code> is given, the read error the default setting, <code class="sgmltag-attvalue">report</code> will be used.
+ </div></li><li class="listitem"><div class="para">
+ The optional <code class="sgmltag-attribute">io</code> attribute controls specific policies on I/O; <code class="sgmltag-attribute">qemu</code> guests support <code class="sgmltag-attvalue">threads</code> and <code class="sgmltag-attvalue">native</code>. The optional <code class="sgmltag-attribute">ioeventfd</code> attribute allows users to set domain I/O asynchronous handling for disk device. The default is left to the discretion of the hypervisor. Accepted values are <code class="sgmltag-attvalue">on</code> and <code class="sgmltag-attvalue">off</code>. Enabling this allows the guest virtual machine to be executed while a separate thread handles I/O. Typically guests experiencing high system CPU utilization during I/O will benefit from this. On the other hand, an overloaded host can increase guest I/O latency. Unless you are absolutely certian that the <code class="sgmltag-attribute">io</code> needs to be manipulated, it is highly recommended that you not change the
default setting and allow the hypervisor to dictate the setting.
+ </div></li><li class="listitem"><div class="para">
+ The optional <code class="sgmltag-attribute">event_idx</code> attribute controls some aspects of device event processing and can be set to either <code class="sgmltag-attvalue">on</code> or <code class="sgmltag-attvalue">off</code> - if it is on, it will reduce the number of interrupts and exits for the guest. The default is determined by the hypervisor and the default setting is <code class="sgmltag-attvalue">on</code>. In cases that there is a situation where this behavior is suboptimal, this attribute provides a way to force the feature <code class="sgmltag-attvalue">off</code>. Unless you are absolutely certian that the <code class="sgmltag-attribute">event_idx</code> needs to be manipulated, it is highly recommended that you not change the default setting and allow the hypervisor to dictate the setting.
+ </div></li><li class="listitem"><div class="para">
+ The optional <code class="sgmltag-attribute">copy_on_read</code> attribute controls whether to copy the read backing file into the image file. The accepted values can be either <code class="sgmltag-attvalue">on</code> or <code class="sgmltag-starttag"><off></code>. <code class="sgmltag-attribute">copy-on-read</code> avoids accessing the same backing file sectors repeatedly and is useful when the backing file is over a slow network. By default <code class="sgmltag-attribute">copy-on-read</code> is <code class="sgmltag-attvalue">off</code>.
+ </div></li></ul></div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-misc"><div class="titlepage"><div><div><h4 class="title">J.16.1.7. Additional Device Elements</h4></div></div></div><div class="para">
+ The following attributes may be used within the <code class="sgmltag-element">device</code> element:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><boot></code> - Specifies that the disk is bootable.
+ </div><div class="itemizedlist"><h6>Additional boot values</h6><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><order></code> - Determines the order in which devices will be tried during boot sequence.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><per-device></code> boot elements cannot be used together with general boot elements in BIOS bootloader section
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><encryption></code> - Specifies how the volume is encrypted. See the Storage Encryption page for more information.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><readonly></code> - Indicates the device cannot be modified by the guest. This setting is the default for disks with <code class="sgmltag-attribute">attribute</code> <code class="sgmltag-attvalue">device='cdrom'</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">shareable</code> Indicates the device is expected to be shared between domains (as long as hypervisor and OS support this). If <code class="sgmltag-element">shareable</code> is used, <code class="sgmltag-attvalue">cache='no'</code> should be used for that device.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><transient></code>- Indicates that changes to the device contents should be reverted automatically when the guest exits. With some hypervisors, marking a disk <code class="sgmltag-attvalue">transient</code> prevents the domain from participating in migration or snapshots.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><serial></code>- Specifies the serial number of guest virtual machine's hard drive. For example, <code class="sgmltag-starttag"><serial></code>WD-WMAP9A966149<code class="sgmltag-endtag"></serial></code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><wwn></code> - Specifies the WWN (World Wide Name) of a virtual hard disk or CD-ROM drive. It must be composed of 16 hexadecimal digits.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><vendor></code> - Specifies the vendor of a virtual hard disk or CD-ROM device. It must not be longer than 8 printable characters.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><product></code> - Specifies the product of a virtual hard disk or CD-ROM device. It must not be longer than 16 printable characters
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><host></code> - Supports 4 attributes: <code class="sgmltag-element">viz</code>, <code class="sgmltag-element">name</code>, <code class="sgmltag-element">port</code>, <code class="sgmltag-element">transport</code> and <code class="sgmltag-element">socket</code>, which specify the hostname, the port number, transport type and path to socket, respectively. The meaning of this element and the number of the elements depend on the <code class="sgmltag-element">protocol</code> attribute as shown here:
+ </div><div class="itemizedlist"><h6>additional host attributes</h6><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">nbd</code> - Specifies a server running nbd-server and may only be used for only one host
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">rbd</code> - Monitors servers of RBD type and may be used for one or more hosts
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">sheepdog</code> - Specifies one of the sheepdog servers (default is localhost:7000) and can be used one or none of the hosts
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">gluster</code> - Specifies a server running a glusterd daemon and may be used for only only one host. The valid values for transport attribute are <code class="sgmltag-attvalue">tcp</code>, <code class="sgmltag-attvalue">rdma</code> or <code class="sgmltag-attvalue">unix</code>. If nothing is specified, <code class="sgmltag-attvalue">tcp</code> is assumed. If transport is <code class="sgmltag-attvalue">unix</code>, the <code class="sgmltag-attvalue">socket</code> attribute specifies path to unix socket.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><address></code> - Ties the disk to a given slot of a controller. The actual <code class="sgmltag-starttag"><controller></code> device can often be inferred by but it can also be explicitly specified. The <code class="sgmltag-attribute">type</code> attribute is mandatory, and is typically <code class="sgmltag-attvalue">pci</code> or <code class="sgmltag-attvalue">drive</code>. For a <code class="sgmltag-attribute">pci</code> controller, additional attributes for <code class="sgmltag-element">bus</code>, <code class="sgmltag-element">slot</code>, and <code class="sgmltag-element">function</code> must be present, as well as optional <code class="sgmltag-element">domain</code> and <code class="sgmltag-attvalue">multifunction</code>. <code class="sgmltag-attvalue">multifunction</code> defaults to <code class="sgmltag-attvalue">off</code>. For a <code class="sgmltag-attribute">drive</code> controller, additional attributes <code c
lass="sgmltag-attvalue">controller</code>, <code class="sgmltag-attvalue">bus</code>, <code class="sgmltag-attvalue">target</code>, and <code class="sgmltag-attvalue">unit</code> are available, each with a default setting of <code class="sgmltag-attvalue">0</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">auth</code> - Provides the authentication credentials needed to access the source. It includes a mandatory attribute username, which identifies the username to use during authentication, as well as a sub-element <code class="sgmltag-attvalue">secret</code> with mandatory attribute <code class="sgmltag-attribute">type</code>. More information can be found here at <a href="http://libvirt.org/formatdomain.html">Device Elements</a>
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">geometry</code> - Provides the ability to override geometry settings. This mostly useful for S390 DASD-disks or older DOS-disks.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">cyls</code> - Specifies the number of cylinders.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">heads</code> - Specifies the number of heads.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">secs</code> - Specifies the number of sectors per track.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">trans</code> - Specifies the BIOS-Translation-Modus and can have the following values:<code class="sgmltag-element">none</code>, <code class="sgmltag-element">lba</code> or <code class="sgmltag-element">auto</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">blockio</code> - Allows the block device to be overridden with any of the block device properties listed below:
+ </div><div class="itemizedlist"><h6>blockio options</h6><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">logical_block_size</code>- reports to the guest OS and describes the smallest units for disk I/O.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">physical_block_size</code> - reports to the guest OS and describes the disk's hardware sector size which can be relevant for the alignment of disk data.
+ </div></li></ul></div></li></ul></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-time-keep.html"><strong>Prev</strong>J.15. Time keeping</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="sub-section-libvirt-dom-xml-devices-filesystems.html"><strong>Next</strong>J.16.2. Filesystems</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-event-config.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-event-config.html
new file mode 100644
index 0000000..8c2582d
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-event-config.html
@@ -0,0 +1,91 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.12. Events configuration</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sect-libvirt-dom-xml-cpu-model-top.html" title="J.11. CPU model and topology" /><link rel="next" href="sect-libvirt-dom-xml-pwr-man.html" title="J.13. Power Management" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-cpu-model-to
p.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-libvirt-dom-xml-pwr-man.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-libvirt-dom-xml-event-config"><div class="titlepage"><div><div><h2 class="title">J.12. Events configuration</h2></div></div></div><div class="para">
+ Using the following sections of domain XML it is possible to override the default actions taken on various events.
+ </div><div class="figure" id="fig-xml-cpu-model-events-config"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><on_poweroff></span>destroy<span class="perl_Keyword"></on_poweroff></span>
+ <span class="perl_Keyword"><on_reboot></span>restart<span class="perl_Keyword"></on_reboot></span>
+ <span class="perl_Keyword"><on_crash></span>restart<span class="perl_Keyword"></on_crash></span>
+ <span class="perl_Keyword"><on_lockfailure></span>poweroff<span class="perl_Keyword"></on_lockfailure></span>
+ ..
+
+</pre></div><h6>Figure J.19. Events Configuration</h6></div><br class="figure-break" /><div class="para">
+ The following collections of elements allow the actions to be specified when a guest OS triggers a lifecycle operation. A common use case is to force a reboot to be treated as a poweroff when doing the initial OS installation. This allows the VM to be re-configured for the first post-install bootup.
+ </div><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-event-config-elem"><h6>Table J.10. Event configurtation elements</h6><div class="table-contents"><table summary="Event configurtation elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ State
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><on_poweroff></code>
+ </td><td class="">
+ Specifies the action that is to be executed when the guest requests a poweroff. Four possible arguements are possible:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">destroy</code> - this action terminates the domain completely and releases all resources
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">restart</code> - this action terminates the domain completely and restarts it with the same configuration
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">preserve</code> - this action terminates the domain completely but and its resources are preserved to allow for future analysis.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">rename-restart</code> - this action terminates the domain completely and then restarts it with a new name
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><on_reboot></code>
+ </td><td class="">
+ Specifies the action that is to be executed when the guest requests a reboot.Four possible arguements are possible:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">destroy</code> - this action terminates the domain completely and releases all resources
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">restart</code> - this action terminates the domain completely and restarts it with the same configuration
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">preserve</code> - this action terminates the domain completely but and its resources are preserved to allow for future analysis.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">rename-restart</code> - this action terminates the domain completely and then restarts it with a new name
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><on_crash></code>
+ </td><td class="">
+ Specifies the action that is to be executed when the guest crashes. In addition, it supports these additional actions:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">coredump-destroy</code> - the crashed domain's core is dumped, domain is terminated completely, and all resources are released.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">coredump-restart</code> - the crashed domain's core is dumped, and the domain is restarted with the same configuration settings
+ </div></li></ul></div>
+ Four possible arguements are possible:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">destroy</code> - this action terminates the domain completely and releases all resources
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">restart</code> - this action terminates the domain completely and restarts it with the same configuration
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">preserve</code> - this action terminates the domain completely but and its resources are preserved to allow for future analysis.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">rename-restart</code> - this action terminates the domain completely and then restarts it with a new name
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><on_lockfailure></code>
+ </td><td class="">
+ Specifies what action should be taken when a lock manager loses resource locks. The following actions are recognized by libvirt, although not all of them need to be supported by individual lock managers. When no action is specified, each lock manager will take its default action. The following arguements are possible:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">poweroff</code> - forcefully powers off the domain
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">restart</code> - restarts the domain to reacquire its locks.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">pause</code> - pauses the domain so that it can be manually resumed when lock issues are solved.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">ignore</code> - keeps the domain running as if nothing happened.
+ </div></li></ul></div>
+
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-cpu-model-top.html"><strong>Prev</strong>J.11. CPU model and topology</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-libvirt-dom-xml-pwr-man.html"><strong>Next</strong>J.13. Power Management</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-mem-tuning.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-mem-tuning.html
new file mode 100644
index 0000000..dab84a8
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-mem-tuning.html
@@ -0,0 +1,49 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.7. Memory tuning</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sect-mem-back.html" title="J.6. Memory backing" /><link rel="next" href="sect-libvirt-dom-xml-numa-node-tuning.html" title="J.8. NUMA node tuning" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-mem-back.html"><strong>Prev</strong></a></li><li c
lass="next"><a accesskey="n" href="sect-libvirt-dom-xml-numa-node-tuning.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-libvirt-dom-xml-mem-tuning"><div class="titlepage"><div><div><h2 class="title">J.7. Memory tuning</h2></div></div></div><div class="figure" id="fig-dom-xml-mem-tuning"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain></span>
+ ...
+ <span class="perl_Keyword"><memtune></span>
+ <span class="perl_Keyword"><hard_limit</span><span class="perl_Others"> unit=</span><span class="perl_String">'G'</span><span class="perl_Keyword">></span>1<span class="perl_Keyword"></hard_limit></span>
+ <span class="perl_Keyword"><soft_limit</span><span class="perl_Others"> unit=</span><span class="perl_String">'M'</span><span class="perl_Keyword">></span>128<span class="perl_Keyword"></soft_limit></span>
+ <span class="perl_Keyword"><swap_hard_limit</span><span class="perl_Others"> unit=</span><span class="perl_String">'G'</span><span class="perl_Keyword">></span>2<span class="perl_Keyword"></swap_hard_limit></span>
+ <span class="perl_Keyword"><min_guarantee</span><span class="perl_Others"> unit=</span><span class="perl_String">'bytes'</span><span class="perl_Keyword">></span>67108864<span class="perl_Keyword"></min_guarantee></span>
+ <span class="perl_Keyword"></memtune></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.10. Memory tuning</h6></div><br class="figure-break" /><div class="para">
+ Although all are optional, the components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-mem-tun-elem"><h6>Table J.6. Memory tuning elements</h6><div class="table-contents"><table summary="Memory tuning elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><memtune></code>
+ </td><td class="">
+ Provides details regarding the memory tunable parameters for the domain. If this is omitted, it defaults to the OS provided defaults. The parameters are applied to the process as a whole therefore when setting limits, one needs to add up guest RAM, guest video RAM, and allow for some memory overhead. The last piece is hard to determine so one use trial and error. For each tunable, it is possible to designate which unit the number is in on input, using the same values as for <code class="sgmltag-starttag"><memory></code>. For backwards compatibility, output is always in KiB.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><hard_limit></code>
+ </td><td class="">
+ This is the maximum memory the guest can use. The <code class="sgmltag-attribute">unit</code> for this value is expressed in <code class="literal">kibibytes</code> (i.e. blocks of 1024 bytes)
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><soft_limit></code>
+ </td><td class="">
+ This is the memory limit to enforce during memory contention. The <code class="sgmltag-attribute">unit</code> for this value is expressed in kibibytes (i.e. blocks of 1024 bytes)
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><swap_hard_limit></code>
+ </td><td class="">
+ This is the maximum memory plus swap the guest can use. The <code class="sgmltag-attribute">unit</code> for this value is expressed in kibibytes (i.e. blocks of 1024 bytes). This has to be more than <code class="sgmltag-starttag"><hard_limit></code> value provided
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><min_guarantee></code>
+ </td><td class="">
+ This is the guaranteed minimum memory allocation for the guest. The units for this value is expressed in kibibytes (i.e. blocks of 1024 bytes)
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-mem-back.html"><strong>Prev</strong>J.6. Memory backing</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-libvirt-dom-xml-numa-node-tuning.html"><strong>Next</strong>J.8. NUMA node tuning</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-numa-node-tuning.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-numa-node-tuning.html
new file mode 100644
index 0000000..561576a
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-numa-node-tuning.html
@@ -0,0 +1,36 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.8. NUMA node tuning</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sect-libvirt-dom-xml-mem-tuning.html" title="J.7. Memory tuning" /><link rel="next" href="sect-libvirt-dom-xml-blk-io-tuning.html" title="J.9. Block I/O tuning" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-mem-tuning.html"><st
rong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-libvirt-dom-xml-blk-io-tuning.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-libvirt-dom-xml-numa-node-tuning"><div class="titlepage"><div><div><h2 class="title">J.8. NUMA node tuning</h2></div></div></div><div class="para">
+ Once NUMA node tuning is done using conventional managment tools the following domain XML parameters are effected:
+ </div><div class="figure" id="fig-dom-xml-numa-node-tuning"><div class="figure-contents"><pre class="programlisting">
+>
+<span class="perl_Keyword"><domain></span>
+ ...
+ <span class="perl_Keyword"><numatune></span>
+ <span class="perl_Keyword"><memory</span><span class="perl_Others"> mode=</span><span class="perl_String">"strict"</span><span class="perl_Others"> nodeset=</span><span class="perl_String">"1-4,^3"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></numatune></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.11. NUMA node tuning</h6></div><br class="figure-break" /><div class="para">
+ Although all are optional, the components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-numa-tun-elem"><h6>Table J.7. NUMA node tuning elements</h6><div class="table-contents"><table summary="NUMA node tuning elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><numatune></code>
+ </td><td class="">
+ Provides details of how to tune the performance of a NUMA host via controlling NUMA policy for domain process.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><memory></code>
+ </td><td class="">
+ Specifies how to allocate memory for the domain process on a NUMA host. It contains several optional attributes. Attribute <code class="sgmltag-attribute">mode</code> is either <code class="sgmltag-attvalue">interleave</code>, <code class="sgmltag-attvalue">strict</code>, or <code class="sgmltag-attvalue">preferred</code>. If no value is given it defaults to <code class="sgmltag-attvalue">strict</code>. Attribute <code class="sgmltag-attribute">nodeset</code> specifies the NUMA nodes, using the same syntax as attribute <code class="sgmltag-attribute">cpuset</code> of element <code class="sgmltag-starttag"><vcpu></code>. Attribute <code class="sgmltag-attribute">placement</code> can be used to indicate the memory placement mode for the domain process. Its value can be either <code class="sgmltag-attvalue">static</code> or <code class="sgmltag-attvalue">auto</code>. If attribute <code class="sgmltag-starttag"><nodeset></code> is specified it defaults to the
<code class="sgmltag-starttag"><placement></code> of <code class="sgmltag-starttag"><vcpu></code>, or <code class="sgmltag-attvalue">static</code>. <code class="sgmltag-attvalue">auto</code> indicates the domain process will only allocate memory from the advisory nodeset returned from querying numad and the value of attribute nodeset will be ignored if it's specified. If attribute <code class="sgmltag-attribute">placement</code> of <code class="sgmltag-element">vcpu</code> is <code class="sgmltag-attvalue">auto</code>, and attribute <code class="sgmltag-starttag"><numatune></code> is not specified, a default numatune with <code class="sgmltag-starttag"><placement></code> <code class="sgmltag-attvalue">auto</code> and mode <code class="sgmltag-attvalue">strict</code> will be added implicitly.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-mem-tuning.html"><strong>Prev</strong>J.7. Memory tuning</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-libvirt-dom-xml-blk-io-tuning.html"><strong>Next</strong>J.9. Block I/O tuning</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-pwr-man.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-pwr-man.html
new file mode 100644
index 0000000..078c466
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-pwr-man.html
@@ -0,0 +1,23 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.13. Power Management</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sect-libvirt-dom-xml-event-config.html" title="J.12. Events configuration" /><link rel="next" href="apjs14.html" title="J.14. Hypervisor features" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-event-config.html"><strong>Prev</s
trong></a></li><li class="next"><a accesskey="n" href="apjs14.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-libvirt-dom-xml-pwr-man"><div class="titlepage"><div><div><h2 class="title">J.13. Power Management</h2></div></div></div><div class="para">
+ It is possible to forcibly enable or disable BIOS advertisements to the guest OS using conventional management tools which effects the following section of the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-pwr-man"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><pm></span>
+ <span class="perl_Keyword"><suspend-to-disk</span><span class="perl_Others"> enabled=</span><span class="perl_String">'no'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><suspend-to-mem</span><span class="perl_Others"> enabled=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></pm></span>
+ ...
+
+</pre></div><h6>Figure J.20. Power Management</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-starttag"><pm></code> element can be enabled using the arguement <code class="sgmltag-attvalue">yes</code> or disabled using the arguement <code class="sgmltag-attvalue">no</code>. BIOS support can be implemented for S3 using the arguement <code class="sgmltag-attribute">suspend-to-disk</code> and S4 using the arguement <code class="sgmltag-attribute">suspend-to-mem</code> ACPI sleep states. If nothing is specified, the hypervisor will be left with its default value.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-event-config.html"><strong>Prev</strong>J.12. Events 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="apjs14.html"><strong>Next</strong>J.14. Hypervisor features</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-res-part.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-res-part.html
new file mode 100644
index 0000000..77fb8eb
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-res-part.html
@@ -0,0 +1,23 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.10. Resource partitioning</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sect-libvirt-dom-xml-blk-io-tuning.html" title="J.9. Block I/O tuning" /><link rel="next" href="sect-libvirt-dom-xml-cpu-model-top.html" title="J.11. CPU model and topology" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-blk-io-
tuning.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-libvirt-dom-xml-cpu-model-top.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-libvirt-dom-xml-res-part"><div class="titlepage"><div><div><h2 class="title">J.10. Resource partitioning</h2></div></div></div><div class="para">
+ Hypervisors may allow for virtual machines to be placed into resource partitions, potentially with nesting of said partitions. The <code class="sgmltag-starttag"><resource></code> element groups together configuration related to resource partitioning. It currently supports a child element partition whose content defines the path of the resource partition in which to place the domain. If no partition is listed, then the domain will be placed in a default partition. It is the responsibility of the app/admin to ensure that the partition exists prior to starting the guest. Only the (hypervisor specific) default partition can be assumed to exist by default.
+ </div><div class="figure" id="fig-res-part"><div class="figure-contents"><pre class="programlisting">
+
+
+ ...
+ <span class="perl_Keyword"><resource></span>
+ <span class="perl_Keyword"><partition></span>/virtualmachines/production<span class="perl_Keyword"></partition></span>
+ <span class="perl_Keyword"></resource></span>
+ ...
+
+</pre></div><h6>Figure J.13. Resource partitioning</h6></div><br class="figure-break" /><div class="para">
+ Resource partitions are currently supported by the QEMU and LXC drivers, which map partition paths to cgroups directories in all mounted controllers.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-blk-io-tuning.html"><strong>Prev</strong>J.9. Block I/O tuning</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-libvirt-dom-xml-cpu-model-top.html"><strong>Next</strong>J.11. CPU model and topology</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-time-keep.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-time-keep.html
new file mode 100644
index 0000000..2b60602
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-time-keep.html
@@ -0,0 +1,74 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.15. Time keeping</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="apjs14.html" title="J.14. Hypervisor features" /><link rel="next" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apjs14.html"><strong>Prev</strong></a></li><li class="next"><a accesskey=
"n" href="sect-libvirt-dom-xml-devices.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-libvirt-dom-xml-time-keep"><div class="titlepage"><div><div><h2 class="title">J.15. Time keeping</h2></div></div></div><div class="para">
+ The guest clock is typically initialized from the host clock. Most operating systems expect the hardware clock to be kept in UTC, which is the default setting. Note that for Windows guests the guest must be set in <code class="sgmltag-attvalue">localtime</code>.
+ </div><div class="figure" id="fig-libvirt-dom-xml-time-keep"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><clock</span><span class="perl_Others"> offset=</span><span class="perl_String">'localtime'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><timer</span><span class="perl_Others"> name=</span><span class="perl_String">'rtc'</span><span class="perl_Others"> tickpolicy=</span><span class="perl_String">'catchup'</span><span class="perl_Others"> track=</span><span class="perl_String">'guest'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><catchup</span><span class="perl_Others"> threshold=</span><span class="perl_String">'123'</span><span class="perl_Others"> slew=</span><span class="perl_String">'120'</span><span class="perl_Others"> limit=</span><span class="perl_String">'10000'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></timer></span>
+ <span class="perl_Keyword"><timer</span><span class="perl_Others"> name=</span><span class="perl_String">'pit'</span><span class="perl_Others"> tickpolicy=</span><span class="perl_String">'delay'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></clock></span>
+ ...
+
+</pre></div><h6>Figure J.22. Time keeping</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-time-keep-elem"><h6>Table J.12. Time keeping elements</h6><div class="table-contents"><table summary="Time keeping elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ State
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><clock></code>
+ </td><td class="">
+ The <code class="sgmltag-attribute">offset</code> attribute takes four possible values, allowing for fine grained control over how the guest clock is synchronized to the host. Note that hypervisors are not required to support all policies across all time sources <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">utc</code> - Synchronizes the clock to UTC when booted. <code class="sgmltag-attvalue">utc</code> mode can be converted to <code class="sgmltag-attvalue">variable</code> mode, which can be controlled by using the adjustment attribute. If the value is <code class="sgmltag-attvalue">reset</code>, the conversion is not done. A numeric value forces the conversion to <code class="sgmltag-attvalue">variable</code> mode using the value as the initial adjustment. The default adjustment is hypervisor specific.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">localtime</code> - Synchronizes the guest clock with the host's configured timezone when booted. The adjustment attribute behaves the same as in 'utc' mode.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">timezone</code> - Synchronizes the guest clock to the requested timezone using the timezone attribute.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">variable</code> - Gives the guest clock an arbitrary offset applied relative to UTC or localtime, depending on the basis attribute. The delta relative to UTC (or localtime) is specified in seconds, using the <code class="sgmltag-attribute">adjustment</code> attribute. The guest is free to adjust the RTC over time and expect that it will be honored at next reboot. This is in contrast to <code class="sgmltag-attvalue">utc</code> and <code class="sgmltag-attvalue">localtime</code> mode (with the optional attribute <code class="sgmltag-attvalue">adjustment='reset'</code>), where the RTC adjustments are lost at each reboot. In addition the <code class="sgmltag-attribute">basis</code> attribute can be either <code class="sgmltag-attvalue">utc</code> (default) or <code class="sgmltag-attvalue">localtime</code>. The <code class="sgmltag-element">clock</code> element may have zero or more <code class="sgmltag-starttag"><timer></code> ele
ments.
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><timer></code>
+ </td><td class="">
+ See Note
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><frequency></code>
+ </td><td class="">
+ This is an unsigned integer specifying the frequency at which <code class="sgmltag-attribute">name</code>=<code class="sgmltag-attvalue">"tsc"</code> runs.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><mode></code>
+ </td><td class="">
+ The <code class="sgmltag-attribute">mode</code> attribute controls how the <code class="sgmltag-attvalue">name="tsc"</code> <code class="sgmltag-starttag"><timer></code> is managed, and can be set to: <code class="sgmltag-attvalue">auto</code>, <code class="sgmltag-attvalue">native</code>, <code class="sgmltag-attvalue">emulate</code>, <code class="sgmltag-attvalue">paravirt</code>, or <code class="sgmltag-attvalue">smpsafe</code>. Other timers are always emulated.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><present></code>
+ </td><td class="">
+ Specifies whether a particular timer is available to the guest. Can be set to <code class="sgmltag-attvalue">yes</code> or <code class="sgmltag-attvalue">no</code>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="note"><div class="admonition_header"><h2>Additional information about the <code class="sgmltag-starttag"><timer></code> element</h2></div><div class="admonition"><div class="para">
+ Each <code class="sgmltag-starttag"><timer></code> element must contain a <code class="sgmltag-attribute">name</code> attribute, and may have the following attributes depending on the name specified.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><name></code> - selects which <code class="sgmltag-element">timer</code> is being modified. The following values are acceptable:<code class="sgmltag-attvalue">platform</code>, <code class="sgmltag-attvalue">hpet</code>, <code class="sgmltag-attvalue">kvmclock</code>, <code class="sgmltag-attvalue">pit</code>, <code class="sgmltag-attvalue">rtc</code>, or <code class="sgmltag-attvalue">tsc</code>.
+ </div></li><li class="listitem"><div class="para">
+ track - specifies the timer track. The following values are acceptable: <code class="sgmltag-attvalue">boot</code>, <code class="sgmltag-attvalue">guest</code>, or <code class="sgmltag-attvalue">wall</code>. <code class="sgmltag-element">track</code> is only valid for <code class="sgmltag-attvalue">name="rtc"</code> or <code class="sgmltag-attvalue">name="platform"</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-element">tickpolicy</code> - determines what happens whens the deadline for injecting a tick to the guest is missed. The following values can be assigned:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">delay</code> -will continue to deliver ticks at the normal rate. The guest time will be delayed due to the late tick
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">catchup</code> - delivers ticks at a higher rate in order to catch up with the missed tick. The guest time is not displayed once catchup is complete. In addition, there can be three optional attributes, each a positive integer, as follows: threshold, slew, and limit.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">merge</code> - merges the missed tick(s) into one tick and injects them. The guest time may be delayed, depending on how the merge is done.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">discard</code> - throws away the missed tick(s) and continues with future injection at its default interval setting. The guest time may be delayed, unless the there is an explicit statement for handling lost ticks
+ </div></li></ul></div></li></ul></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apjs14.html"><strong>Prev</strong>J.14. Hypervisor features</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-libvirt-dom-xml-devices.html"><strong>Next</strong>J.16. Devices</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-limit-redirection.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-limit-redirection.html
new file mode 100644
index 0000000..be1695b
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-limit-redirection.html
@@ -0,0 +1,45 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.15. Setting a limit on device redirection</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="subsect-guest-synch-delimited.html" title="25.14.2. guest-sync-delimited" /><link rel="next" href="sect-dynamic-vNIC.html" title="25.16. Dynamically changing a host or a network bridge that is attached to a virtual NIC" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a>
</p><ul class="docnav"><li class="previous"><a accesskey="p" href="subsect-guest-synch-delimited.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-dynamic-vNIC.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-limit-redirection"><div class="titlepage"><div><div><h2 class="title">25.15. Setting a limit on device redirection</h2></div></div></div><div class="para">
+ To filter out certain devices from redirection, pass the filter property to <em class="parameter"><code>-device usb-redir</code></em>. The filter property takes a string consisting of filter rules, the format for a rule is:
+ </div><pre class="screen"><code class="command"><class>:<vendor>:<product>:<version>:<allow></code></pre><div class="para">
+ Use the value <em class="parameter"><code>-1 </code></em> to designate it to accept any value for a particular field. You may use multiple rules on the same command line using | as a separator. Note that if a device matches none of the passed in rules, redirecting it will not be allowed!
+ </div><div class="example" id="exam-limit-redirect"><h6>Example 25.6. An example of limiting redirection with a windows guest virtual machine </h6><div class="example-contents"><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Prepare a Windows 7 guest.
+ </div></li><li class="step"><div class="para">
+ Add the following code excerpt to the guest's' domain xml file:
+ </div><pre class="screen">
+ <redirdev bus='usb' type='spicevmc'>
+ <alias name='redir0'/>
+ <address type='usb' bus='0' port='3'/>
+ </redirdev>
+ <redirfilter>
+ <usbdev class='0x08' vendor='0x1234' product='0xBEEF' version='2.0' allow='yes'/>
+ <usbdev class='-1' vendor='-1' product='-1' version='-1' allow='no'/>
+ </redirfilter>
+</pre></li><li class="step"><div class="para">
+ Start the guest and confirm the setting changes by running the following:
+ </div><pre class="screen">#<code class="command">ps -ef | grep $guest_name</code></pre><pre class="screen"><code class="command">-device usb-redir,chardev=charredir0,id=redir0,</code>/
+<code class="command">filter=0x08:0x1234:0xBEEF:0x0200:1|-1:-1:-1:-1:0,bus=usb.0,port=3</code></pre></li><li class="step"><div class="para">
+ Plug a USB device into host, and use virt-viewer to connect to the guest.
+ </div></li><li class="step"><div class="para">
+ Click <span class="guimenuitem"><strong>USB device selection</strong></span> in the menu, which will produce the following message: "Some USB devices are blocked by host policy". Click <span class="guimenuitem"><strong>OK</strong></span> to confirm and continue.
+ </div><div class="para">
+ The filter takes effect.
+ </div></li><li class="step"><div class="para">
+ To make sure that the filter captures properly check the USB device vendor and product, then make the following changes in the host's domain XML to allow for USB redirection.
+ </div><pre class="screen">
+ <redirfilter>
+ <usbdev class='0x08' vendor='0x0951' product='0x1625' version='2.0' allow='yes'/>
+ <usbdev allow='no'/>
+ </redirfilter>
+</pre></li><li class="step"><div class="para">
+ Restart the guest, then use <span class="application"><strong>virt-viewer</strong></span> to connect to the guest. The USB device will now redirect traffic to the guest.
+ </div></li></ol></div></div></div><br class="example-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="subsect-guest-synch-delimited.html"><strong>Prev</strong>25.14.2. guest-sync-delimited</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-dynamic-vNIC.html"><strong>Next</strong>25.16. Dynamically changing a host or a network b...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-man-disk-image.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-man-disk-image.html
new file mode 100644
index 0000000..f5570d4
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-man-disk-image.html
@@ -0,0 +1,74 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.13. Disk image management with live block copy</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="prev" href="migrating_guests-with-virsh.html" title="E.12. Migrating guests with virsh" /><link rel="next" href="sub-sect-blockpull.html" title="E.13.2. Using blockpull to shorten a backing chain" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class
="previous"><a accesskey="p" href="migrating_guests-with-virsh.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-blockpull.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-man-disk-image"><div class="titlepage"><div><div><h2 class="title">E.13. Disk image management with live block copy</h2></div></div></div><div class="para">
+ Live block copy allows you to copy an in use guest disk image to a destination image and switches the guest disk image to the destination guest image while the guest is running. Whilst live migration moves the memory and registry state of the host, the guest is kept in shared storage. Live block copy allows you to move the entire guest contents to another host on the fly while the guest is running. Live block copy may also be used for live migration without requiring permanent share storage. In this method the disk image is copied to the destination host after migration, but while the guest is running.
+ </div><div class="para">
+ Live block copy is especially useful for the following applications:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ moving the guest image from local storage to a central location
+ </div></li><li class="listitem"><div class="para">
+ when maintenance is required, guests can be transferred to another location, with no loss of performance
+ </div></li><li class="listitem"><div class="para">
+ allows for management of guest images for speed and efficiency
+ </div></li><li class="listitem"><div class="para">
+ image format conversions can be done without having to shut down the guest
+ </div></li></ul></div><div class="example" id="live-blk-cpy-example"><h6>Example E.1. Example (live block copy)</h6><div class="example-contents"><div class="para">
+ This example shows what happens when live block copy is performed. The example has a backing file (base) that is shared between a source and destination. It also has two overlays (sn1 and sn2) that are only present on the source and must be copied.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ The backing file chain at the beginning looks like this:
+ </div><div class="para">
+ <code class="command"> base ← sn1 ← sn2</code>
+ </div><div class="para">
+ The components are as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ base - the original disk image
+ </div></li><li class="listitem"><div class="para">
+ sn1 - the first snapshot that was taken of the base disk image
+ </div></li><li class="listitem"><div class="para">
+ sn2 - the most current snapshot
+ </div></li><li class="listitem"><div class="para">
+ active - the copy of the disk
+ </div></li></ul></div></li><li class="step"><div class="para">
+ When a copy of the image is created as a new image on top of sn2 the result is this:
+ </div><div class="para">
+ <code class="command">base ← sn1 ← sn2 ← active </code>
+ </div></li><li class="step"><div class="para">
+ At this point the read permissions are all in the correct order and are set automatically. To make sure write permissions are set properly, a mirror mechanism redirects all writes to both sn2 and active, so that sn2 and active read the same at any time (and this mirror mechanism is the essential difference between live block copy and image streaming).
+ </div></li><li class="step"><div class="para">
+ A background task that loops over all disk clusters is executed. For each cluster, there are the following possible cases and actions:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The cluster is already allocated in active and there is nothing to do.
+ </div></li><li class="listitem"><div class="para">
+ Use <code class="command">bdrv_is_allocated()</code> to follow the backing file chain. If the cluster is read from base (which is shared) there is nothing to do.
+ </div></li><li class="listitem"><div class="para">
+ If <code class="command">bdrv_is_allocated()</code> variant is not feasible, rebase the image and compare the read data with write data in base in order to decide if a copy is needed.
+ </div></li><li class="listitem"><div class="para">
+ In all other cases, copy the cluster into <code class="filename">active</code>
+ </div></li></ul></div></li><li class="step"><div class="para">
+ When the copy has completed, the backing file of active is switched to base (similar to rebase)
+ </div></li></ol></div></div></div><br class="example-break" /><div class="para">
+ To reduce the length of a backing chain after a series of snapshots, the following commands are helpful: <code class="command">blockcommit</code> and <code class="command">blockpull</code>. See <a class="xref" href="sect-man-disk-image.html#sect-blockcommit">Section E.13.1, “Using blockcommit to shorten a backing chain”</a> for more information.
+ </div><div class="section" id="sect-blockcommit"><div class="titlepage"><div><div><h3 class="title">E.13.1. Using blockcommit to shorten a backing chain</h3></div></div></div><div class="para">
+ This section demonstrates how to use <code class="command">blockcommit</code> to shorten a backing chain. For more background on backing chains, see <a class="xref" href="sect-man-disk-image.html">Section E.13, “Disk image management with live block copy”</a>.
+ </div><div class="para">
+ <code class="command">blockcommit</code> copies data from one part of the chain down into a backing file, allowing you to pivot the rest of the chain in order to bypass the committed portions. For example, suppose this is the current state:
+ </div><pre class="screen">
+ <code class="command">base ← snap1 ← snap2 ← active</code>.
+</pre><div class="para">
+ Using <code class="command">blockcommit</code> moves the contents of snap2 into snap1, allowing you to delete snap2 from the chain, making backups much quicker.
+ </div><div class="procedure" id="pro-blockcommit"><h6>Procedure E.1. virsh blockcommit</h6><ul><li class="step"><div class="para">
+ Run the following command:
+ </div><pre class="screen">#<code class="command"> virsh blockcommit $dom $disk --base snap1 --top snap2 --wait --verbose</code></pre><div class="para">
+ The contents of snap2 are moved into snap1, resulting in:
+ </div><div class="para">
+ <code class="command">base ← snap1 ← active</code>. Snap2 is no longer valid and can be deleted
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ <code class="command">blockcommit</code> will corrupt any file that depends on the <em class="parameter"><code>--base</code></em> argument (other than files that depended on the <em class="parameter"><code>--top</code></em> argument, as those files now point to the base). To prevent this, do not commit changes into files shared by more than one guest. The <em class="parameter"><code>--verbose</code></em> option will allow the progress to be printed on the screen.
+ </div></div></div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="migrating_guests-with-virsh.html"><strong>Prev</strong>E.12. Migrating 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="sub-sect-blockpull.html"><strong>Next</strong>E.13.2. Using blockpull to shorten a backing chain</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-mem-back.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-mem-back.html
new file mode 100644
index 0000000..152d620
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-mem-back.html
@@ -0,0 +1,24 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.6. Memory backing</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sect-cpu-tuning.html" title="J.5. CPU tuning" /><link rel="next" href="sect-libvirt-dom-xml-mem-tuning.html" title="J.7. Memory tuning" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-cpu-tuning.html"><strong>Prev</strong></a></li><li class="nex
t"><a accesskey="n" href="sect-libvirt-dom-xml-mem-tuning.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-mem-back"><div class="titlepage"><div><div><h2 class="title">J.6. Memory backing</h2></div></div></div><div class="para">
+ Memory backing allows the hypervisor to properly manage large pages within the guest. Once confured the following domain XML is effected:
+ </div><div class="figure" id="fig-mem-back"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain></span>
+ ...
+ <span class="perl_Keyword"><memoryBacking></span>
+ <span class="perl_Keyword"><hugepages/></span>
+ <span class="perl_Keyword"></memoryBacking></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.9. Memory backing</h6></div><br class="figure-break" /><div class="para">
+ The optional <code class="sgmltag-starttag"><memoryBacking></code> element, may have an <code class="sgmltag-starttag"><hugepages></code> element set within it. This tells the hypervisor that the guest should have its memory allocated using hugepages instead of the normal native page size.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-cpu-tuning.html"><strong>Prev</strong>J.5. CPU tuning</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-libvirt-dom-xml-mem-tuning.html"><strong>Next</strong>J.7. Memory tuning</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-mem-dump-off.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-mem-dump-off.html
new file mode 100644
index 0000000..4b69543
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-mem-dump-off.html
@@ -0,0 +1,49 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.2. Guest memory allocation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="next" href="sect-Virtualization-Tips_and_tricks-Using_qemu_img.html" title="25.3. Using qemu-img" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Si
te" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Tips_and_tricks-Using_qemu_img.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-mem-dump-off"><div class="titlepage"><div><div><h2 class="title">25.2. Guest memory allocation</h2></div></div></div><div class="para">
+ The following procedure shows how to allocate memory for a guest. This allocation and assignement works only at boot time and any changes to any of the memory values will not take effect until the next reboot.
+ </div><div class="para">
+ Valid memory units include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="parameter"><code>b</code></em> or <em class="parameter"><code>bytes</code></em> for bytes
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>KB</code></em> for kilobytes (10<sup>3</sup> or blocks of 1,000 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>k</code></em> or <em class="parameter"><code>KiB</code></em> for kibibytes (2<sup>10</sup> or blocks of 1024 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>MB</code></em> for megabytes (10<sup>6</sup> or blocks of 1,000,000 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>M</code></em> or <em class="parameter"><code>MiB</code></em> for mebibytes (2<sup>20</sup> or blocks of 1,048,576 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>GB</code></em> for gigabytes (10<sup>9</sup> or blocks of 1,000,000,000 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>G</code></em> or <em class="parameter"><code>GiB</code></em> for gibibytes (2<sup>30</sup> or blocks of 1,073,741,824 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>TB</code></em> for terabytes (10<sup>12</sup> or blocks of 1,000,000,000,000 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>T</code></em> or <em class="parameter"><code>TiB</code></em> for tebibytes (2<sup>40</sup> or blocks of 1,099,511,627,776 bytes)
+ </div></li></ul></div><div class="para">
+ Note that all values will be rounded up to the nearest kibibyte by libvirt, and may be further rounded to the granularity supported by the hypervisor. Some hypervisors also enforce a minimum, such as 4000KiB (or 4000 x 2<sup>10</sup> or 4,096,000 bytes). The units for this value are determined by the optional attribute <em class="parameter"><code>memory unit</code></em>, which defaults to the kibibytes (KiB) as a unit of measure where the value given is multiplied by 2<sup>10</sup> or blocks of 1024 bytes.
+ </div><div class="para">
+ In the cases where the guest crashes the optional attribute <em class="parameter"><code>dumpCore</code></em> can be used to control whether the guest's memory should be included in the generated coredump (<em class="parameter"><code>dumpCore='on'</code></em>) or not included (<em class="parameter"><code>dumpCore='off'</code></em>). Note that the default setting is <em class="parameter"><code>on</code></em> so if the parameter is not set to <em class="parameter"><code>off</code></em>, the guest memory will be included in the coredump file.
+ </div><div class="para">
+ The <em class="parameter"><code>currentMemory</code></em> attribute determines the actual memory allocation for a guest. This value can be less than the maximum allocation, to allow for ballooning up the guests memory on the fly. If this is omitted, it defaults to the same value as the memory element. The unit attribute behaves the same as for memory.
+ </div><div class="para">
+ In all cases for this section, the domain XML needs to be altered as follows:
+ </div><pre class="screen">
+<domain>
+
+ <memory unit='KiB' dumpCore='off'>524288</memory>
+ <!-- changes the memory unit to KiB and does not allow the guest's memory to be included in the generated coredump file -->
+ <currentMemory unit='KiB'>524288</currentMemory>
+ <!-- makes the current memory unit 524288 KiB -->
+ ...
+</domain>
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html"><strong>Prev</strong>Chapter 25. Miscellaneous administration tasks</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-Tips_and_tricks-Using_qemu_img.html"><strong>Next</strong>25.3. Using qemu-img</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-network-protocols.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-network-protocols.html
new file mode 100644
index 0000000..465161c
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-network-protocols.html
@@ -0,0 +1,14 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.3. Networking protocols</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html" title="Appendix H. Virtual Networking" /><link rel="prev" href="sect-Network_Address_Translation-libvirt.html" title="H.2. Network Address Translation" /><link rel="next" href="sub-sect-routed-mode-libvirt.html" title="H.3.2. Routed mode" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="
p" href="sect-Network_Address_Translation-libvirt.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-routed-mode-libvirt.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-network-protocols"><div class="titlepage"><div><div><h2 class="title">H.3. Networking protocols</h2></div></div></div><div class="para">
+ The following sections describe individual networking protocols and how they are used in libvirt
+ </div><div class="section" id="sect-DNS_and_DHCP-protocols-libvirt"><div class="titlepage"><div><div><h3 class="title">H.3.1. DNS and DHCP</h3></div></div></div><div class="para">
+ IP information can be assigned to guests via DHCP. A pool of addresses can be assigned to a virtual network switch for this purpose. Libvirt uses the <code class="command">dnsmasq</code> program for this. An instance of dnsmasq is automatically configured and started by libvirt for each virtual network switch that needs it.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-Network_Address_Translation-Switch_with_DNSDHCP"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-05-switchwithdnsmasq.jpg" width="444" alt="Virtual network switch running dnsmasq" /></div></div><h6>Figure H.4. Virtual network switch running dnsmasq</h6></div><br class="figure-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Network_Address_Translation-libvirt.html"><strong>Prev</strong>H.2. Network Address Translation</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="sub-sect-routed-mode-libvirt.html"><strong>Next</strong>H.3.2. Routed mode</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-other-commands.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-other-commands.html
new file mode 100644
index 0000000..1ef495e
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-other-commands.html
@@ -0,0 +1,29 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.5. Other commands</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /><link rel="prev" href="sect-Augeas-and-libguestfs-scripting.html" title="G.4.5. Augeas and libguestfs scripting" /><link rel="next" href="sect-virt-rescue.html" title="G.6. virt-rescue: The rescue shell" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li cla
ss="previous"><a accesskey="p" href="sect-Augeas-and-libguestfs-scripting.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-virt-rescue.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-other-commands"><div class="titlepage"><div><div><h2 class="title">G.5. Other commands</h2></div></div></div><div class="para">
+ This section describes tools that are simpler equivalents to using guestfish to view and edit guest disk images.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">virt-cat</code> is similar to the guestfish <code class="command">download</code> command. It downloads and displays a single file to the guest. For example:
+ </div><pre class="screen">
+# virt-cat RHEL3 /etc/ntp.conf | grep ^server
+ server 127.127.1.0 # local clock
+</pre></li><li class="listitem"><div class="para">
+ <code class="command">virt-edit</code> is similar to the guestfish <code class="command">edit</code> command. It can be used to interactively edit a single file within a guest. For example, you may need to edit the <code class="filename">grub.conf</code> file in a Linux-based guest that will not boot:
+ </div><pre class="screen">
+# virt-edit LinuxGuest /boot/grub/grub.conf
+</pre><div class="para">
+ <code class="command">virt-edit</code> has another mode where it can be used to make simple non-interactive changes to a single file. For this, the <span class="bold bold"><strong>-e</strong></span> option is used. This command, for example, changes the root password in a Linux guest to having no password:
+ </div><pre class="screen">
+# virt-edit LinuxGuest /etc/passwd -e 's/^root:.*?:/root::/'
+</pre></li><li class="listitem"><div class="para">
+ <code class="command">virt-ls</code> is similar to the guestfish <code class="command">ls</code>, <code class="command">ll</code> and <code class="command">find</code> commands. It is used to list a directory or directories (recursively). For example, the following command would recursively list files and directories under /home in a Linux guest:
+ </div><pre class="screen">
+# virt-ls -R LinuxGuest /home/ | less
+</pre></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Augeas-and-libguestfs-scripting.html"><strong>Prev</strong>G.4.5. Augeas and libguestfs scripting</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-virt-rescue.html"><strong>Next</strong>G.6. virt-rescue: The rescue shell</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-perf-mon.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-perf-mon.html
new file mode 100644
index 0000000..a6d595f
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-perf-mon.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.12. Using PMU to monitor guest performance</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers.html" title="25.11. Virtual machine timer management with libvirt" /><link rel="next" href="sect-s3-s4.html" title="25.13. Guest virtual machine power management" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-Tips_and_tricks-Libvirt_Managed_Timers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-s3-s4.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-perf-mon"><div class="titlepage"><div><div><h2 class="title">25.12. Using PMU to monitor guest performance</h2></div></div></div><div class="para">
+ In Fedora 18 and onward, vPMU (virtual PMU )was introduced as technical-preview. vPMU is based on Intel's PMU (Performance Monitoring Units) and may only be used on Intel machines. PMU allows the tracking of statistics which indicate how a guest virtual machine is functioning.
+ </div><div class="para">
+ Using performance monitoring, allows developers to use the CPU's PMU counter while using the performance tool for profiling. The virtual performance monitoring unit feature allows virtual machine users to identify sources of possible performance problems in their guest virtual machines, thereby improving the ability to profile a KVM guest virtual machine.
+ </div><div class="para">
+ To enable the feature, the <code class="command">-cpu host </code>flag must be set.
+ </div><div class="para">
+ This feature is only supported with guests running Fedora and is disabled by default. This feature only works using the Linux perf tool. Make sure the <span class="package">perf</span> package is installed using the command:
+ </div><pre class="screen">#<code class="command"> yum install perf</code>.</pre><div class="para">
+ See the man page on <code class="command">perf</code> for more information on the perf commands.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers.html"><strong>Prev</strong>25.11. Virtual machine timer management with libv...</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-s3-s4.html"><strong>Next</strong>25.13. Guest virtual machine power management</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-qemu-ga.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-qemu-ga.html
new file mode 100644
index 0000000..7584cf5
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-qemu-ga.html
@@ -0,0 +1,35 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.14. QEMU Guest Agent Protocol</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="sect-s3-s4.html" title="25.13. Guest virtual machine power management" /><link rel="next" href="subsect-guest-synch-delimited.html" title="25.14.2. guest-sync-delimited" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a acc
esskey="p" href="sect-s3-s4.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="subsect-guest-synch-delimited.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-qemu-ga"><div class="titlepage"><div><div><h2 class="title">25.14. QEMU Guest Agent Protocol</h2></div></div></div><div class="para">
+ The QEMU guest agent protocol (QEMU-ga), uses the same protocol as QMP. <span class="package">qemu-ga</span>. There are a couple issues regarding its isa-serial/virtio-serial transport, and the following caveats have been noted:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ There is no way for <span class="package">qemu-ga</span> to detect whether or not a client has connected to the channel.
+ </div></li><li class="listitem"><div class="para">
+ There is no way for a client to detect whether or not <span class="package">qemu-ga</span> has disconnected or reconnected to the backend.
+ </div></li><li class="listitem"><div class="para">
+ If the virtio-serial device resets and <span class="package">qemu-ga</span> has not connected to the channel as a result, (generally caused by a reboot or hotplug), data from the client will be dropped.
+ </div></li><li class="listitem"><div class="para">
+ If <span class="package">qemu-ga</span> has connected to the channel following a virtio-serial device reset, data from the client will be queued (and eventually throttled if available buffers are exhausted), regardless of whether or not <span class="package">qemu-ga</span> is still running/connected.
+ </div></li></ul></div><div class="para">
+ qemu-ga uses the guest-sync or guest-sync-delimited command to address the problem of re-synchronizing the channel after re-connection or client-side timeouts. These are described below.
+ </div><div class="section" id="sect-guest-synch"><div class="titlepage"><div><div><h3 class="title">25.14.1. guest-sync</h3></div></div></div><div class="para">
+ The guest-sync request/response exchange is simple. The client provides a unique numerical token, the agent sends it back in a response:
+ </div><pre class="screen">
+ > { "execute": "guest-sync", "arguments": { "id": 123456 } }
+ < { "return": 123456}
+</pre><div class="para">
+ A successful exchange guarantees that the channel is now in sync and no unexpected data/responses will be sent. Note that for the reasons mentioned above there's no guarantee this request will be answered, so a client should implement a timeout and re-issue this periodically until a response is received for the most recent request.
+ </div><div class="para">
+ This alone does not handle synchronization issues in all cases. For example, if <span class="package">qemu-ga</span>'s parser previously received a partial request from a previous client connection, subsequent attempts to issue the guest-sync request can be misconstrued as being part of the previous partial request. Eventually <span class="package">qemu-ga</span> will hit it's recursion or token size limit and flush its parser state, at which point it will begin processing the backlog of requests, but there's no guarantee this will occur before the channel is throttled due to exhausting all available buffers. Thus, there is a potential for a deadlock situation occurring for certain instances.
+ </div><div class="para">
+ To avoid this, <span class="package">qemu-ga/QEMU</span>'s JSON parser has special handling for the 0xFF byte, which is an invalid UTF-8 character. Client requests should precede the guest-sync request with to ensure that <span class="package">qemu-ga</span> flushes it's parser state as soon as possible. As long as all clients abide by this, the deadlock state should be reliably avoidable.
+ </div><div class="para">
+ For more information see the qemu-ga wiki page on <a href="http://wiki.qemu.org/Features/QAPI/GuestAgent">wiki.qemu.org</a>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-s3-s4.html"><strong>Prev</strong>25.13. Guest virtual machine power 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="subsect-guest-synch-delimited.html"><strong>Next</strong>25.14.2. guest-sync-delimited</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-run-virt-rescue.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-run-virt-rescue.html
new file mode 100644
index 0000000..8fef566
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-run-virt-rescue.html
@@ -0,0 +1,57 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.6.2. Running virt-rescue</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-virt-rescue.html" title="G.6. virt-rescue: The rescue shell" /><link rel="prev" href="sect-virt-rescue.html" title="G.6. virt-rescue: The rescue shell" /><link rel="next" href="sect-virt-df.html" title="G.7. virt-df: Monitoring disk usage" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-virt-rescue.html"><strong>Prev</strong></a></li
><li class="next"><a accesskey="n" href="sect-virt-df.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-run-virt-rescue"><div class="titlepage"><div><div><h3 class="title">G.6.2. Running virt-rescue</h3></div></div></div><div class="para">
+ Before you use <code class="command">virt-rescue</code> on a guest, make sure the guest is not running, otherwise disk corruption will occur. When you are sure the guest is not live, enter:
+ </div><pre class="screen">
+virt-rescue GuestName
+</pre><div class="para">
+ (where GuestName is the guest name as known to libvirt), or:
+ </div><pre class="screen">
+virt-rescue /path/to/disk/image
+</pre><div class="para">
+ (where the path can be any file, any logical volume, LUN, or so on) containing a guest disk.
+ </div><div class="para">
+ You will first see output scroll past, as virt-rescue boots the rescue VM. In the end you will see:
+ </div><pre class="screen">
+Welcome to virt-rescue, the libguestfs rescue shell.
+
+ Note: The contents of / are the rescue appliance.
+ You have to mount the guest's partitions under /sysroot
+ before you can examine them.
+
+ bash: cannot set terminal process group (-1): Inappropriate ioctl for device
+ bash: no job control in this shell
+ ><rescue>
+</pre><div class="para">
+ The shell prompt here is an ordinary bash shell, and a reduced set of ordinary Fedora commands is available. For example, you can enter:
+ </div><pre class="screen">
+><rescue> fdisk -l /dev/vda
+</pre><div class="para">
+ The previous command will list disk partitions. To mount a file system, it is suggested that you mount it under <code class="filename">/sysroot</code>, which is an empty directory in the rescue machine for the user to mount anything you like. Note that the files under <code class="filename">/</code> are files from the rescue VM itself:
+ </div><pre class="screen">
+><rescue> mount /dev/vda1 /sysroot/
+EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
+><rescue> ls -l /sysroot/grub/
+ total 324
+ -rw-r--r--. 1 root root 63 Sep 16 18:14 device.map
+ -rw-r--r--. 1 root root 13200 Sep 16 18:14 e2fs_stage1_5
+ -rw-r--r--. 1 root root 12512 Sep 16 18:14 fat_stage1_5
+ -rw-r--r--. 1 root root 11744 Sep 16 18:14 ffs_stage1_5
+ -rw-------. 1 root root 1503 Oct 15 11:19 grub.conf
+ [...]
+</pre><div class="para">
+ When you are finished rescuing the guest, exit the shell by entering <code class="command">exit</code> or <code class="command">Ctrl+d</code>.
+ </div><div class="para">
+ <code class="command">virt-rescue</code> has many command line options. The options most often used are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>--ro</strong></span>: Operate in read-only mode on the guest. No changes will be saved. You can use this to experiment with the guest. As soon as you exit from the shell, all of your changes are discarded.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>--network</strong></span>: Enable network access from the rescue shell. Use this if you need to, for example, download RPM or other files into the guest.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-virt-rescue.html"><strong>Prev</strong>G.6. virt-rescue: The rescue shell</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-virt-df.html"><strong>Next</strong>G.7. virt-df: Monitoring disk usage</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-s3-s4.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-s3-s4.html
new file mode 100644
index 0000000..3315f14
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-s3-s4.html
@@ -0,0 +1,21 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.13. Guest virtual machine power management</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="sect-perf-mon.html" title="25.12. Using PMU to monitor guest performance" /><link rel="next" href="sect-qemu-ga.html" title="25.14. QEMU Guest Agent Protocol" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p"
href="sect-perf-mon.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-qemu-ga.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-s3-s4"><div class="titlepage"><div><div><h2 class="title">25.13. Guest virtual machine power management</h2></div></div></div><div class="para">
+ It is possible to forcibly enable or disable BIOS advertisements to the guest virtual machine's operating system by changing the following parameters in the Domain XML for Libvirt:
+ </div><pre class="screen">
+...
+ <pm>
+ <suspend-to-disk enabled='no'/>
+ <suspend-to-mem enabled='yes'/>
+ </pm>
+ ...
+</pre><div class="para">
+ The element <em class="parameter"><code>pm</code></em> enables ('yes') or disables ('no') BIOS support for S3 (suspend-to-disk) and S4 (suspend-to-mem) ACPI sleep states. If nothing is specified, then the hypervisor will be left with its default value.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-perf-mon.html"><strong>Prev</strong>25.12. Using PMU to monitor guest performance</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-qemu-ga.html"><strong>Next</strong>25.14. QEMU Guest Agent Protocol</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-smbios-sys-info.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-smbios-sys-info.html
new file mode 100644
index 0000000..9f8b18e
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-smbios-sys-info.html
@@ -0,0 +1,38 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.3. SMBIOS system information</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sub-sect-op-sys-cont-boot.html" title="J.2.4. Container boot" /><link rel="next" href="sect-cpu-allocation.html" title="J.4. CPU allocation" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-op-sys-cont-boot.html"><strong>Prev</strong></a></li
><li class="next"><a accesskey="n" href="sect-cpu-allocation.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-smbios-sys-info"><div class="titlepage"><div><div><h2 class="title">J.3. SMBIOS system information</h2></div></div></div><div class="para">
+ Some hypervisors allow control over what system information is presented to the guest (for example, SMBIOS fields can be populated by a hypervisor and inspected via the dmidecode command in the guest). The optional sysinfo element covers all such categories of information.
+ </div><div class="figure"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><os></span>
+ <span class="perl_Keyword"><smbios</span><span class="perl_Others"> mode=</span><span class="perl_String">'sysinfo'</span><span class="perl_Keyword">/></span>
+ ...
+ <span class="perl_Keyword"></os></span>
+ <span class="perl_Keyword"><sysinfo</span><span class="perl_Others"> type=</span><span class="perl_String">'smbios'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><bios></span>
+ <span class="perl_Keyword"><entry</span><span class="perl_Others"> name=</span><span class="perl_String">'vendor'</span><span class="perl_Keyword">></span>LENOVO<span class="perl_Keyword"></entry></span>
+ <span class="perl_Keyword"></bios></span>
+ <span class="perl_Keyword"><system></span>
+ <span class="perl_Keyword"><entry</span><span class="perl_Others"> name=</span><span class="perl_String">'manufacturer'</span><span class="perl_Keyword">></span>Fedora<span class="perl_Keyword"></entry></span>
+ <span class="perl_Keyword"><entry</span><span class="perl_Others"> name=</span><span class="perl_String">'vendor'</span><span class="perl_Keyword">></span>Virt-Manager<span class="perl_Keyword"></entry></span>
+ <span class="perl_Keyword"></system></span>
+ <span class="perl_Keyword"></sysinfo></span>
+ ...
+
+</pre></div><h6>Figure J.6. SMBIOS system information</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-starttag"><sysinfo></code> element has a mandatory attribute <code class="sgmltag-attribute">type</code> that determines the layout of sub-elements, and may be defined as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">smbios</code> - Sub-elements call out specific SMBIOS values, which will affect the guest if used in conjunction with the smbios sub-element of the os element. Each sub-element of sysinfo names a SMBIOS block, and within those elements can be a list of entry elements that describe a field within the block. The following blocks and entries are recognized:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">bios</code> - This is block 0 of SMBIOS, with entry names drawn from <code class="sgmltag-attribute">vendor</code>, <code class="sgmltag-attribute">version</code>, <code class="sgmltag-attribute">date</code>, and <code class="sgmltag-attribute">release</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><system></code> - This is block 1 of SMBIOS, with entry names drawn from <code class="sgmltag-attribute">manufacturer</code>, <code class="sgmltag-attribute">product</code>, <code class="sgmltag-attribute">version</code>, <code class="sgmltag-attribute">serial</code>, <code class="sgmltag-attribute">uuid</code>, <code class="sgmltag-attribute">sku</code>, and <code class="sgmltag-attribute">family</code>. If a <code class="sgmltag-attribute">uuid</code> entry is provided alongside a top-level uuid element, the two values must match.
+ </div></li></ul></div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-op-sys-cont-boot.html"><strong>Prev</strong>J.2.4. Container 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-cpu-allocation.html"><strong>Next</strong>J.4. CPU allocation</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-the-Default_Configuration-libvirt.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-the-Default_Configuration-libvirt.html
new file mode 100644
index 0000000..315988b
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-the-Default_Configuration-libvirt.html
@@ -0,0 +1,14 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.4. The default configuration</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html" title="Appendix H. Virtual Networking" /><link rel="prev" href="sub-sect-iso-mode.html" title="H.3.3. Isolated mode" /><link rel="next" href="sect-Virtualization-Virtual_Networking-Example_scenarios.html" title="H.5. Examples of common scenarios" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a acc
esskey="p" href="sub-sect-iso-mode.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Virtual_Networking-Example_scenarios.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-the-Default_Configuration-libvirt"><div class="titlepage"><div><div><h2 class="title">H.4. The default configuration</h2></div></div></div><div class="para">
+ When the libvirtd daemon (<code class="command">libvirtd</code>) is first installed, it contains an initial virtual network switch configuration in NAT mode. This configuration is used so that installed guests can communicate to the external network, through the host. The following image demonstrates this default configuration for <code class="systemitem">libvirtd</code>:
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-the_default_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-08-network-overview.png" width="444" alt="Default libvirt network configuration" /></div></div><h6>Figure H.7. Default libvirt network configuration</h6></div><br class="figure-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ A virtual network can be restricted to a specific physical interface. This may be useful on a physical system that has several interfaces (for example, <code class="filename">eth0</code>, <code class="filename">eth1</code> and <code class="filename">eth2</code>). This is only useful in routed and NAT modes, and can be defined in the <code class="command">dev=<interface></code> option, or in <code class="command">virt-manager</code> when creating a new virtual network.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-iso-mode.html"><strong>Prev</strong>H.3.3. Isolated mode</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-Virtual_Networking-Example_scenarios.html"><strong>Next</strong>H.5. Examples of common scenarios</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-the_guestfish_shell.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-the_guestfish_shell.html
new file mode 100644
index 0000000..93d7aac
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-the_guestfish_shell.html
@@ -0,0 +1,122 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.4. The guestfish shell</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /><link rel="prev" href="sect-Guide-Guest_Disks_libguestfs-installation.html" title="G.3. Installation" /><link rel="next" href="sect-Modifying-files-with-guestfish.html" title="G.4.2. Modifying files with guestfish" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docn
av"><li class="previous"><a accesskey="p" href="sect-Guide-Guest_Disks_libguestfs-installation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Modifying-files-with-guestfish.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-the_guestfish_shell"><div class="titlepage"><div><div><h2 class="title">G.4. The guestfish shell</h2></div></div></div><div class="para">
+ <span class="bold bold"><strong>guestfish</strong></span> is an interactive shell that you can use from the command line or from shell scripts to access guest file systems. All of the functionality of the libguestfs API is available from the shell.
+ </div><div class="para">
+ To begin viewing or editing a virtual machine disk image, run the following command, substituting the path to your desired disk image:
+ </div><pre class="screen">
+guestfish --ro -a /path/to/disk/image
+</pre><div class="para">
+ <span class="bold bold"><strong>--ro</strong></span> means that the disk image is opened read-only. This mode is always safe but does not allow write access. Only omit this option when you are <span class="bold bold"><strong>certain</strong></span> that the guest is not running, or the disk image is not attached to a live guest. It is not possible to use libguestfs to edit a live guest, and attempting to will assuredly result in irreversible disk corruption.
+ </div><div class="para">
+ <span class="bold bold"><strong>/path/to/disk/image</strong></span> is the path to the disk. This can be a file, a host logical volume (such as /dev/VG/LV), a host device (/dev/cdrom) or a SAN LUN (/dev/sdf3).
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ libguestfs and guestfish do not require root privileges. You only need to run them as root if the disk image being accessed needs root to read and/or write.
+ </div></div></div><div class="para">
+ When you start guestfish interactively, it will display this prompt:
+ </div><pre class="screen">
+ guestfish --ro -a /path/to/disk/image
+
+Welcome to guestfish, the libguestfs filesystem interactive shell for editing virtual machine filesystems.
+
+ Type: 'help' for help on commands
+ 'man' to read the manual
+ 'quit' to quit the shell
+
+><fs>
+</pre><div class="para">
+ At the prompt, type <span class="bold bold"><strong>run</strong></span> to initiate the library and attach the disk image. This can take up to 30 seconds the first time it is done. Subsequent starts will complete much faster.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ libguestfs will use hardware virtualization acceleration such as KVM (if available) to speed up this process.
+ </div></div></div><div class="para">
+ Once the <span class="bold bold"><strong>run</strong></span> command has been entered, other commands can be used, as the following section demonstrates.
+ </div><div class="section" id="sect-Viewing_file_systems_with_guestfish"><div class="titlepage"><div><div><h3 class="title">G.4.1. Viewing file systems with guestfish</h3></div></div></div><div class="section" id="sect-Manual-listing-and-viewing"><div class="titlepage"><div><div><h4 class="title">G.4.1.1. Manual listing and viewing</h4></div></div></div><div class="para">
+ The <code class="command">list-filesystems</code> command will list file systems found by libguestfs. This output shows a Red Hat Enterprise Linux 4 disk image:
+ </div><pre class="screen">
+><fs> run
+><fs> list-filesystems
+/dev/vda1: ext3
+/dev/VolGroup00/LogVol00: ext3
+/dev/VolGroup00/LogVol01: swap
+</pre><div class="para">
+ This output shows a Windows disk image:
+ </div><pre class="screen">
+><fs> run
+><fs> list-filesystems
+/dev/vda1: ntfs
+/dev/vda2: ntfs
+</pre><div class="para">
+ Other useful commands are <code class="command">list-devices</code>, <code class="command">list-partitions</code>, <code class="command">lvs</code>, <code class="command">pvs</code>, <code class="command">vfs-type</code> and <code class="command">file</code>. You can get more information and help on any command by typing <code class="command">help</code> <span class="emphasis"><em>command</em></span>, as shown in the following output:
+ </div><pre class="screen">
+><fs> help vfs-type
+ NAME
+ vfs-type - get the Linux VFS type corresponding to a mounted device
+
+ SYNOPSIS
+ vfs-type device
+
+ DESCRIPTION
+ This command gets the filesystem type corresponding to the filesystem on
+ "device".
+
+ For most filesystems, the result is the name of the Linux VFS module
+ which would be used to mount this filesystem if you mounted it without
+ specifying the filesystem type. For example a string such as "ext3" or
+ "ntfs".
+</pre><div class="para">
+ To view the actual contents of a file system, it must first be mounted. This example uses one of the Windows partitions shown in the previous output (<code class="filename">/dev/vda2</code>), which in this case is known to correspond to the <span class="bold bold"><strong>C:\</strong></span> drive:
+ </div><pre class="screen">
+><fs> mount-ro /dev/vda2 /
+><fs> ll /
+total 1834753
+ drwxrwxrwx 1 root root 4096 Nov 1 11:40 .
+ drwxr-xr-x 21 root root 4096 Nov 16 21:45 ..
+ lrwxrwxrwx 2 root root 60 Jul 14 2009 Documents and Settings
+ drwxrwxrwx 1 root root 4096 Nov 15 18:00 Program Files
+ drwxrwxrwx 1 root root 4096 Sep 19 10:34 Users
+ drwxrwxrwx 1 root root 16384 Sep 19 10:34 Windows
+</pre><div class="para">
+ You can use guestfish commands such as <code class="command">ls</code>, <code class="command">ll</code>, <code class="command">cat</code>, <code class="command">more</code>, <code class="command">download</code> and <code class="command">tar-out</code> to view and download files and directories.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ There is no concept of a current working directory in this shell. Unlike ordinary shells, you cannot for example use the <code class="command">cd</code> command to change directories. All paths must be fully qualified starting at the top with a forward slash (<span class="bold bold"><strong>/</strong></span>) character. Use the <span class="emphasis"><em>Tab</em></span> key to complete paths.
+ </div></div></div><div class="para">
+ To exit from the guestfish shell, type <code class="command">exit</code> or enter <code class="command">Ctrl+d</code>.
+ </div></div><div class="section" id="sect-Via_guestfish_inspection"><div class="titlepage"><div><div><h4 class="title">G.4.1.2. Via guestfish inspection</h4></div></div></div><div class="para">
+ Instead of listing and mounting file systems by hand, it is possible to let guestfish itself inspect the image and mount the file systems as they would be in the guest. To do this, add the <span class="bold bold"><strong>-i</strong></span> option on the command line:
+ </div><pre class="screen">
+guestfish --ro -a /path/to/disk/image -i
+
+Welcome to guestfish, the libguestfs filesystem interactive shell for
+ editing virtual machine filesystems.
+
+ Type: 'help' for help on commands
+ 'man' to read the manual
+ 'quit' to quit the shell
+
+ Operating system: Red Hat Enterprise Linux AS release 4 (Nahant Update 8)
+ /dev/VolGroup00/LogVol00 mounted on /
+ /dev/vda1 mounted on /boot
+
+ ><fs> ll /
+ total 210
+ drwxr-xr-x. 24 root root 4096 Oct 28 09:09 .
+ drwxr-xr-x 21 root root 4096 Nov 17 15:10 ..
+ drwxr-xr-x. 2 root root 4096 Oct 27 22:37 bin
+ drwxr-xr-x. 4 root root 1024 Oct 27 21:52 boot
+ drwxr-xr-x. 4 root root 4096 Oct 27 21:21 dev
+ drwxr-xr-x. 86 root root 12288 Oct 28 09:09 etc
+ [etc]
+</pre><div class="para">
+ Because guestfish needs to start up the libguestfs back end in order to perform the inspection and mounting, the <code class="command">run</code> command is not necessary when using the <code class="command">-i</code> option. The <code class="command">-i</code> option works for many common Linux and Windows guests.
+ </div></div><div class="section" id="sect-Accessing-aguesT-by-name"><div class="titlepage"><div><div><h4 class="title">G.4.1.3. Accessing a guest by name</h4></div></div></div><div class="para">
+ A guest can be accessed from the command line when you specify its name as known to libvirt (in other words, as it appears in <code class="command">virsh list --all</code>). Use the <code class="command">-d</code> option to access a guest by its name, with or without the <code class="command">-i</code> option:
+ </div><pre class="screen">
+guestfish --ro -d GuestName -i
+</pre></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Guide-Guest_Disks_libguestfs-installation.html"><strong>Prev</strong>G.3. 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-Modifying-files-with-guestfish.html"><strong>Next</strong>G.4.2. Modifying files with guestfish</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-df.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-df.html
new file mode 100644
index 0000000..7596895
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-df.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.7. virt-df: Monitoring disk usage</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /><link rel="prev" href="sect-run-virt-rescue.html" title="G.6.2. Running virt-rescue" /><link rel="next" href="run-virt-df.html" title="G.7.2. Running virt-df" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-run
-virt-rescue.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="run-virt-df.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-virt-df"><div class="titlepage"><div><div><h2 class="title">G.7. virt-df: Monitoring disk usage</h2></div></div></div><div class="section" id="sect-virt-df-intro"><div class="titlepage"><div><div><h3 class="title">G.7.1. Introduction</h3></div></div></div><div class="para">
+ This section describes <code class="command">virt-df</code>, which displays file system usage from a disk image or a guest. It is similar to the Linux <code class="command">df</code> command, but for virtual machines.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-run-virt-rescue.html"><strong>Prev</strong>G.6.2. Running virt-rescue</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="run-virt-df.html"><strong>Next</strong>G.7.2. Running virt-df</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-inspector-install.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-inspector-install.html
new file mode 100644
index 0000000..e59f68e
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-inspector-install.html
@@ -0,0 +1,16 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.9.2. Installation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-virt-inspector.html" title="G.9. virt-inspector: inspecting guests" /><link rel="prev" href="sect-virt-inspector.html" title="G.9. virt-inspector: inspecting guests" /><link rel="next" href="sect-virt-inspector-run.html" title="G.9.3. Running virt-inspector" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-virt-inspector.html"><strong
>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-virt-inspector-run.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-virt-inspector-install"><div class="titlepage"><div><div><h3 class="title">G.9.2. Installation</h3></div></div></div><div class="para">
+ To install virt-inspector and the documentation, enter the following command:
+ </div><pre class="screen">
+# yum install libguestfs-tools libguestfs-devel
+</pre><div class="para">
+ To process Windows guests you must also install <span class="package">libguestfs-winsupport</span>. Refer to <a class="xref" href="sect-virt-win-reg-install.html">Section G.10.2, “Installation”</a> for details. The documentation, including example XML output and a Relax-NG schema for the output, will be installed in <code class="filename">/usr/share/doc/libguestfs-devel-*/</code> where "*" is replaced by the version number of libguestfs.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-virt-inspector.html"><strong>Prev</strong>G.9. virt-inspector: inspecting 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-virt-inspector-run.html"><strong>Next</strong>G.9.3. Running virt-inspector</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-inspector-run.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-inspector-run.html
new file mode 100644
index 0000000..636a9cd
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-inspector-run.html
@@ -0,0 +1,82 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.9.3. Running virt-inspector</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-virt-inspector.html" title="G.9. virt-inspector: inspecting guests" /><link rel="prev" href="sect-virt-inspector-install.html" title="G.9.2. Installation" /><link rel="next" href="sect-virt-win-reg.html" title="G.10. virt-win-reg: Reading and editing the Windows Registry" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-virt-inspector
-install.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-virt-win-reg.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-virt-inspector-run"><div class="titlepage"><div><div><h3 class="title">G.9.3. Running virt-inspector</h3></div></div></div><div class="para">
+ You can run <code class="command">virt-inspector</code> against any disk image or libvirt guest as shown in the following example:
+ </div><pre class="screen">
+virt-inspector --xml disk.img > report.xml
+</pre><div class="para">
+ Or as shown here:
+ </div><pre class="screen">
+virt-inspector --xml GuestName > report.xml
+</pre><div class="para">
+ The result will be an XML report (<code class="filename">report.xml</code>). The main components of the XML file are a top-level <operatingsytems> element containing usually a single <operatingsystem> element, similar to the following:
+ </div><pre class="screen">
+ <operatingsystems>
+ <operatingsystem>
+
+ <!-- the type of operating system and Linux distribution -->
+ <name>linux</name>
+ <distro>rhel</distro>
+ <!-- the name, version and architecture -->
+ <product_name>Red Hat Enterprise Linux Server release 6.4 </product_name>
+ <major_version>6</major_version>
+ <minor_version>4</minor_version>
+ <package_format>rpm</package_format>
+ <package_management>yum</package_management>
+ <root>/dev/VolGroup/lv_root</root>
+ <!-- how the filesystems would be mounted when live -->
+ <mountpoints>
+ <mountpoint dev="/dev/VolGroup/lv_root">/</mountpoint>
+ <mountpoint dev="/dev/sda1">/boot</mountpoint>
+ <mountpoint dev="/dev/VolGroup/lv_swap">swap</mountpoint>
+ </mountpoints>
+
+ < !-- filesystems-->
+ <filesystem dev="/dev/VolGroup/lv_root">
+ <label></label>
+ <uuid>b24d9161-5613-4ab8-8649-f27a8a8068d3</uuid>
+ <type>ext4</type>
+ <content>linux-root</content>
+ <spec>/dev/mapper/VolGroup-lv_root</spec>
+ </filesystem>
+ <filesystem dev="/dev/VolGroup/lv_swap">
+ <type>swap</type>
+ <spec>/dev/mapper/VolGroup-lv_swap</spec>
+ </filesystem>
+ <!-- packages installed -->
+ <applications>
+ <application>
+ <name>firefox</name>
+ <version>3.5.5</version>
+ <release>1.fc12</release>
+ </application>
+ </applications>
+
+ </operatingsystem>
+ </operatingsystems>
+</pre><div class="para">
+ Processing these reports is best done using W3C standard XPath queries. Fedora comes with a command line program (<code class="command">xpath</code>) which can be used for simple instances; however, for long-term and advanced usage, you should consider using an XPath library along with your favorite programming language.
+ </div><div class="para">
+ As an example, you can list out all file system devices using the following XPath query:
+ </div><pre class="screen">
+virt-inspector --xml GuestName | xpath //filesystem/@dev
+ Found 3 nodes:
+ -- NODE --
+ dev="/dev/sda1"
+ -- NODE --
+ dev="/dev/vg_f12x64/lv_root"
+ -- NODE --
+ dev="/dev/vg_f12x64/lv_swap"
+</pre><div class="para">
+ Or list the names of all applications installed by entering:
+ </div><pre class="screen">
+ virt-inspector --xml GuestName | xpath //application/name
+ [...long list...]
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-virt-inspector-install.html"><strong>Prev</strong>G.9.2. 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-virt-win-reg.html"><strong>Next</strong>G.10. virt-win-reg: Reading and editing the Windo...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-inspector.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-inspector.html
new file mode 100644
index 0000000..12f1050
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-inspector.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.9. virt-inspector: inspecting guests</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /><link rel="prev" href="sect-expand-disk-image.html" title="G.8.2. Expanding a disk image" /><link rel="next" href="sect-virt-inspector-install.html" title="G.9.2. Installation" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey=
"p" href="sect-expand-disk-image.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-virt-inspector-install.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-virt-inspector"><div class="titlepage"><div><div><h2 class="title">G.9. virt-inspector: inspecting guests</h2></div></div></div><div class="section" id="sect-virt-inspector-intro"><div class="titlepage"><div><div><h3 class="title">G.9.1. Introduction</h3></div></div></div><div class="para">
+ <code class="command">virt-inspector</code> is a tool for inspecting a disk image to find out what operating system it contains.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-expand-disk-image.html"><strong>Prev</strong>G.8.2. Expanding a 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-virt-inspector-install.html"><strong>Next</strong>G.9.2. Installation</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-rescue.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-rescue.html
new file mode 100644
index 0000000..0f21a84
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-rescue.html
@@ -0,0 +1,16 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.6. virt-rescue: The rescue shell</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /><link rel="prev" href="sect-other-commands.html" title="G.5. Other commands" /><link rel="next" href="sect-run-virt-rescue.html" title="G.6.2. Running virt-rescue" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec
t-other-commands.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-run-virt-rescue.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-virt-rescue"><div class="titlepage"><div><div><h2 class="title">G.6. virt-rescue: The rescue shell</h2></div></div></div><div class="section" id="sect-virt-rescue-intro"><div class="titlepage"><div><div><h3 class="title">G.6.1. Introduction</h3></div></div></div><div class="para">
+ This section describes <code class="command">virt-rescue</code>, which can be considered analogous to a rescue CD for virtual machines. It boots a guest into a rescue shell so that maintenance can be performed to correct errors and the guest can be repaired.
+ </div><div class="para">
+ There is some overlap between virt-rescue and guestfish. It is important to distinguish their differing uses. virt-rescue is for making interactive, ad-hoc changes using ordinary Linux file system tools. It is particularly suited to rescuing a guest that has gone wrong. virt-rescue cannot be scripted.
+ </div><div class="para">
+ In contrast, guestfish is particularly useful for making scripted, structured changes through a formal set of commands (the libguestfs API), although it can also be used interactively.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-other-commands.html"><strong>Prev</strong>G.5. Other commands</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-run-virt-rescue.html"><strong>Next</strong>G.6.2. Running virt-rescue</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-resize.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-resize.html
new file mode 100644
index 0000000..fb68715
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-resize.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.8. virt-resize: resizing guests offline</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /><link rel="prev" href="run-virt-df.html" title="G.7.2. Running virt-df" /><link rel="next" href="sect-expand-disk-image.html" title="G.8.2. Expanding a disk image" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="run
-virt-df.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-expand-disk-image.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-virt-resize"><div class="titlepage"><div><div><h2 class="title">G.8. virt-resize: resizing guests offline</h2></div></div></div><div class="section" id="sect-virt-resize-intro"><div class="titlepage"><div><div><h3 class="title">G.8.1. Introduction</h3></div></div></div><div class="para">
+ This section describes <code class="command">virt-resize</code>, a tool for expanding or shrinking guests. It only works for guests which are offline (shut down). It works by copying the guest image and leaving the original disk image untouched. This is ideal because you can use the original image as a backup, however there is a trade-off as you need twice the amount of disk space.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="run-virt-df.html"><strong>Prev</strong>G.7.2. Running virt-df</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-expand-disk-image.html"><strong>Next</strong>G.8.2. Expanding a disk image</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-win-reg-install.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-win-reg-install.html
new file mode 100644
index 0000000..d597acf
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-win-reg-install.html
@@ -0,0 +1,14 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.10.2. Installation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-virt-win-reg.html" title="G.10. virt-win-reg: Reading and editing the Windows Registry" /><link rel="prev" href="sect-virt-win-reg.html" title="G.10. virt-win-reg: Reading and editing the Windows Registry" /><link rel="next" href="sect-virt-win-reg-use.html" title="G.10.3. Using virt-win-reg" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href
="sect-virt-win-reg.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-virt-win-reg-use.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-virt-win-reg-install"><div class="titlepage"><div><div><h3 class="title">G.10.2. Installation</h3></div></div></div><div class="para">
+ To use <code class="command">virt-win-reg</code> you must run the following:
+ </div><pre class="screen">
+# yum install libguestfs-tools libguestfs-winsupport
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-virt-win-reg.html"><strong>Prev</strong>G.10. virt-win-reg: Reading and editing the Windo...</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-virt-win-reg-use.html"><strong>Next</strong>G.10.3. Using virt-win-reg</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-win-reg-use.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-win-reg-use.html
new file mode 100644
index 0000000..240e23b
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-win-reg-use.html
@@ -0,0 +1,29 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.10.3. Using virt-win-reg</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-virt-win-reg.html" title="G.10. virt-win-reg: Reading and editing the Windows Registry" /><link rel="prev" href="sect-virt-win-reg-install.html" title="G.10.2. Installation" /><link rel="next" href="sect-Using-API-Programming-Languages.html" title="G.11. Using the API from Programming Languages" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" h
ref="sect-virt-win-reg-install.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Using-API-Programming-Languages.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-virt-win-reg-use"><div class="titlepage"><div><div><h3 class="title">G.10.3. Using virt-win-reg</h3></div></div></div><div class="para">
+ To read out Registry keys, specify the name of the guest (or its disk image) and the name of the Registry key. You must use single quotes to surround the name of the desired key:
+ </div><pre class="screen">
+# virt-win-reg WindowsGuest \
+ 'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall' \
+ | less
+</pre><div class="para">
+ The output is in the standard text-based format used by <code class="filename">.REG</code> files on Windows.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Hex-quoting is used for strings because the format does not properly define a portable encoding method for strings. This is the only way to ensure fidelity when transporting <code class="filename">.REG</code> files from one machine to another.
+ </div><div class="para">
+ You can make hex-quoted strings printable by piping the output of <code class="command">virt-win-reg</code> through this simple Perl script:
+ </div><pre class="screen">perl -MEncode -pe's?hex\((\d+)\):(\S+)?$t=$1;$_=$2;s,\,,,g;"str($t):\"".decode(utf16le=>pack("H*",$_))."\""?eg'
+</pre></div></div><div class="para">
+ To merge changes into the Windows Registry of an offline guest, you must first prepare a <code class="filename">.REG</code> file. There is a great deal of documentation about doing this available from MSDN, and there is a good summary in the following Wikipedia page: <a href="https://secure.wikimedia.org/wikipedia/en/wiki/Windows_Registry#.REG_files">https://secure.wikimedia.org/wikipedia/en/wiki/Windows_Registry#.REG_files</a>. When you have prepared a <code class="filename">.REG</code> file, enter the following:
+ </div><pre class="screen">
+# virt-win-reg --merge WindowsGuest input.reg
+</pre><div class="para">
+ This will update the registry in the guest.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-virt-win-reg-install.html"><strong>Prev</strong>G.10.2. 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-Using-API-Programming-Languages.html"><strong>Next</strong>G.11. Using the API from Programming Languages</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-win-reg.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-win-reg.html
new file mode 100644
index 0000000..08efffb
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-win-reg.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.10. virt-win-reg: Reading and editing the Windows Registry</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /><link rel="prev" href="sect-virt-inspector-run.html" title="G.9.3. Running virt-inspector" /><link rel="next" href="sect-virt-win-reg-install.html" title="G.10.2. Installation" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey=
"p" href="sect-virt-inspector-run.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-virt-win-reg-install.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-virt-win-reg"><div class="titlepage"><div><div><h2 class="title">G.10. virt-win-reg: Reading and editing the Windows Registry</h2></div></div></div><div class="section" id="sect-virt-win-reg-intro"><div class="titlepage"><div><div><h3 class="title">G.10.1. Introduction</h3></div></div></div><div class="para">
+ <code class="command">virt-win-reg</code> is a tool that manipulates the Registry in Windows guests. It can be used to read out registry keys. You can also use it to make changes to the Registry, but you must <span class="bold bold"><strong>never</strong></span> try to do this for live/running guests, as it will result in disk corruption.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-virt-inspector-run.html"><strong>Prev</strong>G.9.3. Running virt-inspector</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-virt-win-reg-install.html"><strong>Next</strong>G.10.2. Installation</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect_RedHat-Getting_Help_and_Giving_Feedback.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect_RedHat-Getting_Help_and_Giving_Feedback.html
new file mode 100644
index 0000000..ab04fa4
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sect_RedHat-Getting_Help_and_Giving_Feedback.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2. Getting Help and Giving Feedback</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html" title="Preface" /><link rel="prev" href="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html" title="Preface" /><link rel="next" href="sect-RedHat-We_Need_Feedback.html" title="2.2. We Need Feedback!" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previo
us"><a accesskey="p" href="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-RedHat-We_Need_Feedback.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="sect_RedHat-Getting_Help_and_Giving_Feedback" lang="en-US"><div class="titlepage"><div><div><h2 class="title">2. Getting Help and Giving Feedback</h2></div></div></div><div class="section" id="sect_RedHat-Do_You_Need_Help"><div class="titlepage"><div><div><h3 class="title">2.1. Do You Need Help?</h3></div></div></div><a id="idm13196032" class="indexterm"></a><div class="para">
+ If you experience difficulty with a procedure described in this documentation, visit the Red Hat Customer Portal at <a href="http://access.redhat.com">http://access.redhat.com</a>. Through the customer portal, you can:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ search or browse through a knowledgebase of technical support articles about Red Hat products.
+ </div></li><li class="listitem"><div class="para">
+ submit a support case to Red Hat Global Support Services (GSS).
+ </div></li><li class="listitem"><div class="para">
+ access other product documentation.
+ </div></li></ul></div><div class="para">
+ Red Hat also hosts a large number of electronic mailing lists for discussion of Red Hat software and technology. You can find a list of publicly available mailing lists at <a href="https://www.redhat.com/mailman/listinfo">https://www.redhat.com/mailman/listinfo</a>. Click on the name of any mailing list to subscribe to that list or to access the list archives.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-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="sect-RedHat-We_Need_Feedback.html"><strong>Next</strong>2.2. We Need Feedback!</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-example.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-example.html
new file mode 100644
index 0000000..3471808
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-example.html
@@ -0,0 +1,69 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.23. Example domain XML configuration</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="section-libvirt-dom-xml-security-label.html" title="J.22. Security label" /><link rel="next" href="appe-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Revision_History.html" title="Appendix K. Revision History" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="
previous"><a accesskey="p" href="section-libvirt-dom-xml-security-label.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="appe-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Revision_History.html"><strong>Next</strong></a></li></ul><div class="section" id="section-libvirt-dom-xml-example"><div class="titlepage"><div><div><h2 class="title">J.23. Example domain XML configuration</h2></div></div></div><div class="para">
+ QEMU emulated guest on x86_64
+ </div><div class="figure" id="fig-dom-xml-example-qemu"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain</span><span class="perl_Others"> type=</span><span class="perl_String">'qemu'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><name></span>QEmu-fedora-i686<span class="perl_Keyword"></name></span>
+ <span class="perl_Keyword"><uuid></span>c7a5fdbd-cdaf-9455-926a-d65c16db1809<span class="perl_Keyword"></uuid></span>
+ <span class="perl_Keyword"><memory></span>219200<span class="perl_Keyword"></memory></span>
+ <span class="perl_Keyword"><currentMemory></span>219200<span class="perl_Keyword"></currentMemory></span>
+ <span class="perl_Keyword"><vcpu></span>2<span class="perl_Keyword"></vcpu></span>
+ <span class="perl_Keyword"><os></span>
+ <span class="perl_Keyword"><type</span><span class="perl_Others"> arch=</span><span class="perl_String">'i686'</span><span class="perl_Others"> machine=</span><span class="perl_String">'pc'</span><span class="perl_Keyword">></span>hvm<span class="perl_Keyword"></type></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> dev=</span><span class="perl_String">'cdrom'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></os></span>
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><emulator></span>/usr/bin/qemu-system-x86_64<span class="perl_Keyword"></emulator></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'file'</span><span class="perl_Others"> device=</span><span class="perl_String">'cdrom'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> file=</span><span class="perl_String">'/home/user/boot.iso'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hdc'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><readonly/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'file'</span><span class="perl_Others"> device=</span><span class="perl_String">'disk'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> file=</span><span class="perl_String">'/home/user/fedora.img'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hda'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'vnc'</span><span class="perl_Others"> port=</span><span class="perl_String">'-1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.72. Example domain XML config</h6></div><br class="figure-break" /><div class="para">
+ KVM hardware accelerated guest on i686
+ </div><div class="figure" id="fig-dom-xml-example-kvm"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain</span><span class="perl_Others"> type=</span><span class="perl_String">'kvm'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><name></span>demo2<span class="perl_Keyword"></name></span>
+ <span class="perl_Keyword"><uuid></span>4dea24b3-1d52-d8f3-2516-782e98a23fa0<span class="perl_Keyword"></uuid></span>
+ <span class="perl_Keyword"><memory></span>131072<span class="perl_Keyword"></memory></span>
+ <span class="perl_Keyword"><vcpu></span>1<span class="perl_Keyword"></vcpu></span>
+ <span class="perl_Keyword"><os></span>
+ <span class="perl_Keyword"><type</span><span class="perl_Others"> arch=</span><span class="perl_String">"i686"</span><span class="perl_Keyword">></span>hvm<span class="perl_Keyword"></type></span>
+ <span class="perl_Keyword"></os></span>
+ <span class="perl_Keyword"><clock</span><span class="perl_Others"> sync=</span><span class="perl_String">"localtime"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><emulator></span>/usr/bin/qemu-kvm<span class="perl_Keyword"></emulator></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'file'</span><span class="perl_Others"> device=</span><span class="perl_String">'disk'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> file=</span><span class="perl_String">'/var/lib/libvirt/images/demo2.img'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hda'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">'24:42:53:21:52:45'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'vnc'</span><span class="perl_Others"> port=</span><span class="perl_String">'-1'</span><span class="perl_Others"> keymap=</span><span class="perl_String">'de'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.73. Example domain XML config</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="section-libvirt-dom-xml-security-label.html"><strong>Prev</strong>J.22. Security label</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-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Revision_History.html"><strong>Next</strong>Appendix K. Revision History</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-memory-baloon-device.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-memory-baloon-device.html
new file mode 100644
index 0000000..f356f3c
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-memory-baloon-device.html
@@ -0,0 +1,34 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.19. Memory balloon device</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="section-libvirt-dom-xml-watchdog.html" title="J.18. Watchdog device" /><link rel="next" href="section-libvirt-dom-xml-random-number-gen.html" title="J.20. Random number generator device" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="section-libvirt
-dom-xml-watchdog.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="section-libvirt-dom-xml-random-number-gen.html"><strong>Next</strong></a></li></ul><div class="section" id="section-libvirt-dom-xml-memory-baloon-device"><div class="titlepage"><div><div><h2 class="title">J.19. Memory balloon device</h2></div></div></div><div class="para">
+ A virtual memory balloon device is added to all Xen and KVM/QEMU guests. It will be seen as <code class="sgmltag-starttag"><memballoon></code> element. It will be automatically added when appropriate, so there is no need to explicitly add this element in the guest XML unless a specific PCI slot needs to be assigned. Note that if the memballoon device needs to be explicitly disabled, <code class="sgmltag-attribute">model='none'</code> may be used.
+ </div><div class="para">
+ The following example automatically added device with KVM
+ </div><div class="figure" id="fig-dom-xml-memory-baloon-device"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><memballoon</span><span class="perl_Others"> model=</span><span class="perl_String">'virtio'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.67. Memory balloon device</h6></div><br class="figure-break" /><div class="para">
+ Here is an example where the device is added manually with static PCI slot 2 requested
+ </div><div class="figure" id="fig-dom-xml-memory-baloon-device2"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><memballoon</span><span class="perl_Others"> model=</span><span class="perl_String">'virtio'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'pci'</span><span class="perl_Others"> domain=</span><span class="perl_String">'0x0000'</span><span class="perl_Others"> bus=</span><span class="perl_String">'0x00'</span><span class="perl_Others"> slot=</span><span class="perl_String">'0x02'</span><span class="perl_Others"> function=</span><span class="perl_String">'0x0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></memballoon></span>
+ <span class="perl_Keyword"></devices></span>
+<span class="perl_Error"><</span>/domain>
+</pre></div><h6>Figure J.68. Memory balloon device added manually</h6></div><br class="figure-break" /><div class="para">
+ The required <code class="sgmltag-element">model</code> attribute specifies what type of balloon device is provided. Valid values are specific to the virtualization platform are: <code class="sgmltag-element">'virtio'</code> which is the default setting with the KVM hypervisor or <code class="sgmltag-element">'xen'</code> which is the default setting with the Xen hypervisor.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="section-libvirt-dom-xml-watchdog.html"><strong>Prev</strong>J.18. Watchdog device</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="section-libvirt-dom-xml-random-number-gen.html"><strong>Next</strong>J.20. Random number generator device</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-random-number-gen.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-random-number-gen.html
new file mode 100644
index 0000000..7bd23fa
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-random-number-gen.html
@@ -0,0 +1,37 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.20. Random number generator device</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="section-libvirt-dom-xml-memory-baloon-device.html" title="J.19. Memory balloon device" /><link rel="next" href="section-libvirt-dom-xml-tpm-device.html" title="J.21. TPM devices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="section-libvirt-dom-xml
-memory-baloon-device.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="section-libvirt-dom-xml-tpm-device.html"><strong>Next</strong></a></li></ul><div class="section" id="section-libvirt-dom-xml-random-number-gen"><div class="titlepage"><div><div><h2 class="title">J.20. Random number generator device</h2></div></div></div><div class="para">
+ The virtual random number generator device allows the host to pass through entropy to guest operating systems.
+ </div><div class="figure" id="fig--dom-xml-random-number-gen"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><rng</span><span class="perl_Others"> model=</span><span class="perl_String">'virtio'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><rate</span><span class="perl_Others"> period=</span><span class="perl_String">"2000"</span><span class="perl_Others"> bytes=</span><span class="perl_String">"1234"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><backend</span><span class="perl_Others"> model=</span><span class="perl_String">'random'</span><span class="perl_Keyword">></span>/dev/random<span class="perl_Keyword"></backend></span>
+ <span class="perl_Comment"><!-- OR --></span>
+ <span class="perl_Keyword"><backend</span><span class="perl_Others"> model=</span><span class="perl_String">'egd'</span><span class="perl_Others"> type=</span><span class="perl_String">'udp'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'bind'</span><span class="perl_Others"> service=</span><span class="perl_String">'1234'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'connect'</span><span class="perl_Others"> host=</span><span class="perl_String">'1.2.3.4'</span><span class="perl_Others"> service=</span><span class="perl_String">'1234'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"></backend></span>
+ <span class="perl_Keyword"></rng></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.69. Random number generator device</h6></div><br class="figure-break" /><div class="para">
+ The random number generator device allows the following attributes/elements:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">model</code> - The required <code class="sgmltag-attribute">model</code> attribute specifies what type of RNG device is provided. <code class="sgmltag-attvalue">'virtio'</code> — supported by qemu and virtio-rng kernel module
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><backend></code> - The <code class="sgmltag-starttag"><backend></code> element specifies the source of entropy to be used for the domain. The source model is configured using the <code class="sgmltag-attribute">model</code> attribute. Supported source models include <code class="sgmltag-attvalue">'random'</code> — <code class="filename">/dev/random</code> (default setting) or similar device as source and <code class="sgmltag-attvalue">'egd'</code> which sets a EGD protocol backend.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">backend type='random'</code> - This <code class="sgmltag-starttag"><backend></code> type expects a non-blocking character device as input. Examples of such devices are <code class="filename">/dev/random</code> and <code class="filename">/dev/urandom</code>. The file name is specified as contents of the <code class="sgmltag-starttag"><backend></code> element. When no file name is specified the hypervisor default is used.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><backend type='egd'></code> - This backend connects to a source using the EGD protocol. The source is specified as a character device. Refer to character device host interface for more information.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="section-libvirt-dom-xml-memory-baloon-device.html"><strong>Prev</strong>J.19. Memory balloon device</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="section-libvirt-dom-xml-tpm-device.html"><strong>Next</strong>J.21. TPM devices</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-security-label.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-security-label.html
new file mode 100644
index 0000000..f54b2b7
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-security-label.html
@@ -0,0 +1,53 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.22. Security label</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="section-libvirt-dom-xml-tpm-device.html" title="J.21. TPM devices" /><link rel="next" href="section-libvirt-dom-xml-example.html" title="J.23. Example domain XML configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="section-libvirt-dom-xml-t
pm-device.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="section-libvirt-dom-xml-example.html"><strong>Next</strong></a></li></ul><div class="section" id="section-libvirt-dom-xml-security-label"><div class="titlepage"><div><div><h2 class="title">J.22. Security label</h2></div></div></div><div class="para">
+ The <code class="sgmltag-starttag"><seclabel></code> element allows control over the operation of the security drivers. There are three basic modes of operation, <code class="sgmltag-attvalue">'dynamic'</code> where libvirt automatically generates a unique security label, <code class="sgmltag-attvalue">'static'</code> where the application/administrator chooses the labels, or <code class="sgmltag-element">'none'</code> where confinement is disabled. With dynamic label generation, libvirt will always automatically relabel any resources associated with the virtual machine. With static label assignment, by default, the administrator or application must ensure labels are set correctly on any resources, however, automatic relabeling can be enabled if desired.
+ </div><div class="para">
+ If more than one security driver is used by libvirt, multiple seclabel tags can be used, one for each driver and the security driver referenced by each tag can be defined using the attribute <code class="sgmltag-attribute">model</code> Valid input XML configurations for the top-level security label are:
+ </div><div class="figure" id="fig-libvirt-dom-xml-security-label"><div class="figure-contents"><pre class="programlisting">
+
+ <span class="perl_Keyword"><seclabel</span><span class="perl_Others"> type=</span><span class="perl_String">'dynamic'</span><span class="perl_Others"> model=</span><span class="perl_String">'selinux'</span><span class="perl_Keyword">/></span>
+
+ <span class="perl_Keyword"><seclabel</span><span class="perl_Others"> type=</span><span class="perl_String">'dynamic'</span><span class="perl_Others"> model=</span><span class="perl_String">'selinux'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><baselabel></span>system_u:system_r:my_svirt_t:s0<span class="perl_Keyword"></baselabel></span>
+ <span class="perl_Keyword"></seclabel></span>
+
+ <span class="perl_Keyword"><seclabel</span><span class="perl_Others"> type=</span><span class="perl_String">'static'</span><span class="perl_Others"> model=</span><span class="perl_String">'selinux'</span><span class="perl_Others"> relabel=</span><span class="perl_String">'no'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><label></span>system_u:system_r:svirt_t:s0:c392,c662<span class="perl_Keyword"></label></span>
+ <span class="perl_Keyword"></seclabel></span>
+
+ <span class="perl_Keyword"><seclabel</span><span class="perl_Others"> type=</span><span class="perl_String">'static'</span><span class="perl_Others"> model=</span><span class="perl_String">'selinux'</span><span class="perl_Others"> relabel=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><label></span>system_u:system_r:svirt_t:s0:c392,c662<span class="perl_Keyword"></label></span>
+ <span class="perl_Keyword"></seclabel></span>
+
+ <span class="perl_Keyword"><seclabel</span><span class="perl_Others"> type=</span><span class="perl_String">'none'</span><span class="perl_Keyword">/></span>
+</pre></div><h6>Figure J.71. Security label</h6></div><br class="figure-break" /><div class="para">
+ If no <code class="sgmltag-attribute">'type'</code> attribute is provided in the input XML, then the security driver default setting will be used, which may be either <code class="sgmltag-attvalue">'none'</code> or <code class="sgmltag-attvalue">'dynamic'</code>. If a <code class="sgmltag-starttag"><baselabel></code> is set but no <code class="sgmltag-attribute">'type'</code> is set, then the type is presumed to be <code class="sgmltag-attribute">'dynamic'</code>. When viewing the XML for a running guest with automatic resource relabeling active, an additional XML element, <code class="sgmltag-attribute">imagelabel</code>, will be included. This is an output-only element, so will be ignored in user supplied XML documents.
+ </div><div class="para">
+ The following elements can be manipulated with the following values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">type</code> - Either <code class="sgmltag-element">static</code>, <code class="sgmltag-element">dynamic</code> or <code class="sgmltag-element">none</code> to determine whether libvirt automatically generates a unique security label or not.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">model</code> - A valid security model name, matching the currently activated security model
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">relabel</code> - Either <code class="sgmltag-attvalue">yes</code> or <code class="sgmltag-attvalue">no</code>. This must always be <code class="sgmltag-attvalue">yes</code> if dynamic label assignment is used. With static label assignment it will default to <code class="sgmltag-attvalue">no</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><label></code> - If static labelling is used, this must specify the full security label to assign to the virtual domain. The format of the content depends on the security driver in use:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">SELinux</code>: a SELinux context.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">AppArmor</code>: an AppArmor profile.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">DAC</code>: owner and group separated by colon. They can be defined both as user/group names or uid/gid. The driver will first try to parse these values as names, but a leading plus sign can used to force the driver to parse them as uid or gid.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><baselabel></code> - If dynamic labelling is used, this can optionally be used to specify the base security label. The format of the content depends on the security driver in use.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><imagelabel></code> - This is an output only element, which shows the security label used on resources associated with the virtual domain. The format of the content depends on the security driver in use When relabeling is in effect, it is also possible to fine-tune the labeling done for specific source file names, by either disabling the labeling (useful if the file lives on NFS or other file system that lacks security labeling) or requesting an alternate label (useful when a management application creates a special label to allow sharing of some, but not all, resources between domains). When a seclabel element is attached to a specific path rather than the top-level domain assignment, only the attribute relabel or the sub-element label are supported.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="section-libvirt-dom-xml-tpm-device.html"><strong>Prev</strong>J.21. TPM 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="section-libvirt-dom-xml-example.html"><strong>Next</strong>J.23. Example domain XML configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-sound-devices.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-sound-devices.html
new file mode 100644
index 0000000..ec085dda
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-sound-devices.html
@@ -0,0 +1,32 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.17. Sound devices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-host-interface.html" title="J.16.17. Host interface" /><link rel="next" href="section-libvirt-dom-xml-watchdog.html" title="J.18. Watchdog device" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt
-dom-xml-devices-host-interface.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="section-libvirt-dom-xml-watchdog.html"><strong>Next</strong></a></li></ul><div class="section" id="section-libvirt-dom-xml-sound-devices"><div class="titlepage"><div><div><h2 class="title">J.17. Sound devices</h2></div></div></div><div class="para">
+ A virtual sound card can be attached to the host via the sound element.
+ </div><div class="figure" id="fig-dom-xml-sound-devices"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><sound</span><span class="perl_Others"> model=</span><span class="perl_String">'es1370'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.64. Virtual sound card</h6></div><br class="figure-break" /><div class="para">
+ The sound element has one mandatory attribute, <code class="sgmltag-attribute">model</code>, which specifies what real sound device is emulated. Valid values are specific to the underlying hypervisor, though typical choices are <code class="sgmltag-attvalue">'es1370'</code>, <code class="sgmltag-attvalue">'sb16'</code>, <code class="sgmltag-attvalue">'ac97'</code>, and <code class="sgmltag-attvalue">'ich6'</code>. In addition, a sound element with ich6 model can have optional sub-elements <code class="sgmltag-element">codec</code> to attach various audio codecs to the audio device. If not specified, a default codec will be attached to allow playback and recording. Valid values are <code class="sgmltag-attvalue">'duplex'</code> (advertises a line-in and a line-out) and <code class="sgmltag-attvalue">'micro'</code> (advertises a speaker and a microphone).
+ </div><div class="figure" id="fig-dom-xml-sound-devices2"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><sound</span><span class="perl_Others"> model=</span><span class="perl_String">'ich6'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><codec</span><span class="perl_Others"> type=</span><span class="perl_String">'micro'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><sound/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.65. Sound devices</h6></div><br class="figure-break" /><div class="para">
+ Each sound element has an optional sub-element <code class="sgmltag-starttag"><address></code> which can tie the device to a particular PCI slot, documented above.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-host-interface.html"><strong>Prev</strong>J.16.17. Host interface</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="section-libvirt-dom-xml-watchdog.html"><strong>Next</strong>J.18. Watchdog device</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-tpm-device.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-tpm-device.html
new file mode 100644
index 0000000..4622988
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-tpm-device.html
@@ -0,0 +1,26 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.21. TPM devices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="section-libvirt-dom-xml-random-number-gen.html" title="J.20. Random number generator device" /><link rel="next" href="section-libvirt-dom-xml-security-label.html" title="J.22. Security label" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="section-li
bvirt-dom-xml-random-number-gen.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="section-libvirt-dom-xml-security-label.html"><strong>Next</strong></a></li></ul><div class="section" id="section-libvirt-dom-xml-tpm-device"><div class="titlepage"><div><div><h2 class="title">J.21. TPM devices</h2></div></div></div><div class="para">
+ The TPM device enables a QEMU guest to have access to TPM functionality. The TPM passthrough device type provides access to the host's TPM for one QEMU guest. No other software may be is using the TPM device, typically <code class="filename">/dev/tpm0</code>, at the time the QEMU guest is started. The following domain XML example shows the usage of the TPM passthrough device
+ </div><div class="figure" id="fig-libvirt-dom-xml-tpm-device"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><tpm</span><span class="perl_Others"> model=</span><span class="perl_String">'tpm-tis'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><backend</span><span class="perl_Others"> type=</span><span class="perl_String">'passthrough'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><backend</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/tpm0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></backend></span>
+ <span class="perl_Keyword"></tpm></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+
+</pre></div><h6>Figure J.70. TPM devices</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-attribute">model</code> attribute specifies what device model QEMU provides to the guest. If no model name is provided, tpm-tis will automatically be chosen. The <code class="sgmltag-starttag"><backend></code> element specifies the type of TPM device. The following types are supported: <code class="sgmltag-attvalue">'passthrough'</code> — uses the host's TPM device and <code class="sgmltag-attvalue">'passthrough'</code>. This backend type requires exclusive access to a TPM device on the host. An example for such a device is <code class="filename">/dev/tpm0</code>. The filename is specified as path attribute of the source element. If no file name is specified then <code class="filename">/dev/tpm0</code> is automatically used.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="section-libvirt-dom-xml-random-number-gen.html"><strong>Prev</strong>J.20. Random number generator device</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="section-libvirt-dom-xml-security-label.html"><strong>Next</strong>J.22. Security label</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-watchdog.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-watchdog.html
new file mode 100644
index 0000000..5520d70
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-watchdog.html
@@ -0,0 +1,51 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.18. Watchdog device</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="section-libvirt-dom-xml-sound-devices.html" title="J.17. Sound devices" /><link rel="next" href="section-libvirt-dom-xml-memory-baloon-device.html" title="J.19. Memory balloon device" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="section-libvirt-do
m-xml-sound-devices.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="section-libvirt-dom-xml-memory-baloon-device.html"><strong>Next</strong></a></li></ul><div class="section" id="section-libvirt-dom-xml-watchdog"><div class="titlepage"><div><div><h2 class="title">J.18. Watchdog device</h2></div></div></div><div class="para">
+ A virtual hardware watchdog device can be added to the guest via the <code class="sgmltag-starttag"><watchdog></code> element. The watchdog device requires an additional driver and management daemon in the guest. As merely enabling the watchdog in the libvirt configuration does not do anything useful on its own. Currently there is no support notification when the watchdog fires.
+ </div><div class="figure" id="fig--dom-xml-watchdog"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><watchdog</span><span class="perl_Others"> model=</span><span class="perl_String">'i6300esb'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><watchdog</span><span class="perl_Others"> model=</span><span class="perl_String">'i6300esb'</span><span class="perl_Others"> action=</span><span class="perl_String">'poweroff'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+<span class="perl_Error"><</span>/domain>
+</pre></div><h6>Figure J.66. Watchdog device</h6></div><br class="figure-break" /><div class="para">
+ The following attributes are declared in this XML:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">model</code> - The required <code class="sgmltag-attribute">model</code> attribute specifies what real watchdog device is emulated. Valid values are specific to the underlying hypervisor.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="sgmltag-attribute">model</code> attribute may take the following values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">i6300esb</code> — the recommended device, emulating a PCI Intel 6300ESB
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">ib700</code> — emulates an ISA iBase IB700
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">action</code> - The optional <code class="sgmltag-attribute">action</code> attribute describes what action to take when the watchdog expires. Valid values are specific to the underlying hypervisor. The <code class="sgmltag-attribute">action</code> attribute can have the following values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">reset</code> — default setting, forcefully resets the guest
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">shutdown</code> — gracefully shuts down the guest (not recommended)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">poweroff</code> — forcefully powers off the guest
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">pause</code> — pauses the guest
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">none</code> — does nothing
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">dump</code> — automatically dumps the guest.
+ </div></li></ul></div></li></ul></div><div class="para">
+ Note that the 'shutdown' action requires that the guest is responsive to ACPI signals. In the sort of situations where the watchdog has expired, guests are usually unable to respond to ACPI signals. Therefore using 'shutdown' is not recommended. In addition, the directory to save dump files can be configured by auto_dump_path in file /etc/libvirt/qemu.conf.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="section-libvirt-dom-xml-sound-devices.html"><strong>Prev</strong>J.17. Sound 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="section-libvirt-dom-xml-memory-baloon-device.html"><strong>Next</strong>J.19. Memory balloon device</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/shared-storage-nfs-migration.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/shared-storage-nfs-migration.html
new file mode 100644
index 0000000..d220549
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/shared-storage-nfs-migration.html
@@ -0,0 +1,33 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.3. Shared storage example: NFS for a simple migration</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-KVM_live_migration.html" title="Chapter 20. KVM live migration" /><link rel="prev" href="Live_migration_and_RHEL_compatibility.html" title="20.2. Live migration and Fedora version compatibility" /><link rel="next" href="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html" title="20.4. Live KVM migration with virsh" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documenta
tion Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="Live_migration_and_RHEL_compatibility.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html"><strong>Next</strong></a></li></ul><div class="section" id="shared-storage-nfs-migration"><div class="titlepage"><div><div><h2 class="title">20.3. Shared storage example: NFS for a simple migration</h2></div></div></div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ This example uses NFS to share guest images with other KVM hosts. Although not practical for large installations, it is presented to demonstrate migration techniques only. Do not use this example for migrating or running more than a few guests.
+ </div><div class="para">
+ iSCSI storage is a better choice for large deployments. Refer to <a class="xref" href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-iSCSI">Section 27.1.5, “iSCSI-based storage pools”</a> for configuration details.
+ </div></div></div><div class="para">
+ Also note, that the instructions provided herin are not meant to replace the detailed instructions found in <em class="citetitle">Red Hat Linux Storage Administration Guide</em>. Refer to this guide for information on configuring NFS, opening IP tables, and configuring the firewall.
+ </div><div class="para">
+ Make sure that NFS filelocking is not used as it is not supported in KVM.
+ </div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Export your libvirt image directory</strong></p><div class="para">
+ Migration requires storage to reside on a system that is separate to the migration target systems. On this separate system, export the storage by adding 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>*.example.com</code></em>(rw,no_root_squash,sync)</pre><div class="para">
+ Change the hostname parameter as required for your environment.
+ </div></li><li class="step"><p class="title"><strong>Start NFS</strong></p><ol class="a"><li class="step"><div class="para">
+ Install the NFS packages if they are not yet installed:
+ </div><pre class="screen"># yum install nfs</pre></li><li class="step"><div class="para">
+ Make sure that the ports for NFS in <code class="command">iptables</code> (2049, for example) are opened and add NFS to the <code class="filename">/etc/hosts.allow</code> file.
+ </div></li><li class="step"><div class="para">
+ Start the NFS service:
+ </div><pre class="screen"># service nfs start</pre></li></ol></li><li class="step"><p class="title"><strong>Mount the shared storage on the destination</strong></p><div class="para">
+ On the migration destination system, mount the <code class="filename">/var/lib/libvirt/images</code> directory:
+ </div><pre class="screen"># mount <em class="parameter"><code>storage_host</code></em>:/var/lib/libvirt/images /var/lib/libvirt/images
+</pre><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Whichever directory is chosen for the guests must be exactly the same on host and guest. This applies to all types of shared storage. The directory must be the same or the migration with virt-manager will fail.
+ </div></div></div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="Live_migration_and_RHEL_compatibility.html"><strong>Prev</strong>20.2. Live migration and Fedora version compatibi...</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-KVM_live_migration-Live_KVM_migration_with_virsh.html"><strong>Next</strong>20.4. Live KVM migration with virsh</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-adv-filt-topics.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-adv-filt-topics.html
new file mode 100644
index 0000000..da6b588
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-adv-filt-topics.html
@@ -0,0 +1,24 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.11. Advanced Filter Configuration Topics</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-applying-network-filtering.html" title="H.10. Applying network filtering" /><link rel="prev" href="sub-sub-sect-igmp-esp-ah-udplite-over-ipv6.html" title="H.10.10.12. IGMP, ESP, AH, UDPLITE, 'ALL' over IPv6" /><link rel="next" href="sub-sub-sect-lim-numb-conns.html" title="H.10.11.2. Limiting Number of Connections" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous
"><a accesskey="p" href="sub-sub-sect-igmp-esp-ah-udplite-over-ipv6.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-lim-numb-conns.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-adv-filt-topics"><div class="titlepage"><div><div><h3 class="title">H.10.11. Advanced Filter Configuration Topics</h3></div></div></div><div class="para">
+ The following sections discuss advanced filter configuration topics.
+ </div><div class="section" id="sub-sub-sect-conn-track"><div class="titlepage"><div><div><h4 class="title">H.10.11.1. Connection tracking</h4></div></div></div><div class="para">
+ The network filtering subsystem (on Linux) makes use of the connection tracking support of IP tables. This helps in enforcing the directionality of network traffic (state match) as well as counting and limiting the number of simultaneous connections towards a guest. As an example, if a guest has TCP port 8080 open as a server, clients may connect to the guest on port 8080. Connection tracking and enforcement of directionality then prevents the guest from initiating a connection from (TCP client) port 8080 to the host back to a remote host. More importantly, tracking helps to prevent remote attackers from establishing a connection back to a guest. For example, if the user inside the guest established a connection to port 80 on an attacker site, then the attacker will not be able to initiate a connection from TCP port 80 back towards the guest. By default the connection state match that enables connection tracking and then enforcement of directionality of traffic is turne
d on.
+ </div><div class="example"><h6>Example H.9. XML example for turning off connections to the TCP port</h6><div class="example-contents"><div class="para">
+ The following shows an example XML fragement where this feature has been turned off for incoming connections to TCP port 12345.
+ </div><pre class="screen">
+ [...]
+ <rule direction='in' action='accept' statematch='false'>
+ <cp dstportstart='12345'/>
+ </rule>
+ [...]
+</pre><div class="para">
+ This now allows incoming traffic to TCP port 12345, but would also enable the initiation from (client) TCP port 12345 within the VM, which may or may not be desirable.
+ </div></div></div><br class="example-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-igmp-esp-ah-udplite-over-ipv6.html"><strong>Prev</strong>H.10.10.12. IGMP, ESP, AH, UDPLITE, 'ALL' over IP...</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="sub-sub-sect-lim-numb-conns.html"><strong>Next</strong>H.10.11.2. Limiting Number of Connections</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-auto-IP-add-detect-dhcp-snoop.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-auto-IP-add-detect-dhcp-snoop.html
new file mode 100644
index 0000000..aa66d57
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-auto-IP-add-detect-dhcp-snoop.html
@@ -0,0 +1,18 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.5. Automatic IP address detection and DHCP snooping</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-applying-network-filtering.html" title="H.10. Applying network filtering" /><link rel="prev" href="sub-sect-vars-in-filters.html" title="H.10.4. Usage of variables in filters" /><link rel="next" href="sub-sub-sect-DHCP-snooping.html" title="H.10.5.2. DHCP snooping" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-vars-in-filters.h
tml"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-DHCP-snooping.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-auto-IP-add-detect-dhcp-snoop"><div class="titlepage"><div><div><h3 class="title">H.10.5. Automatic IP address detection and DHCP snooping</h3></div></div></div><div class="section" id="sub-sub-sect-intro-dhcp-snoop"><div class="titlepage"><div><div><h4 class="title">H.10.5.1. Introduction</h4></div></div></div><div class="para">
+ The detection of IP addresses used on a virtual machine's interface is automatically activated if the variable IP is referenced but no value has been assigned to it. The variable <em class="parameter"><code>CTRL_IP_LEARNING</code></em> can be used to specify the IP address learning method to use. Valid values include: <em class="replaceable"><code>any</code></em>, <em class="replaceable"><code>dhcp</code></em>, or <em class="replaceable"><code>none</code></em>.
+ </div><div class="para">
+ The value <em class="replaceable"><code>any</code></em> instructs libvirt to use any packet to determine the address in use by a virtual machine, which is the default setting if the variable <em class="parameter"><code>TRL_IP_LEARNING</code></em> is not set. This method will only detect a single IP address per interface. Once a guest's IP address has been detected, its IP network traffic will be locked to that address, if for example, IP address spoofing is prevented by one of its filters. In that case, the user of the VM will not be able to change the IP address on the interface inside the guest, which would be considered IP address spoofing. When a guest is migrated to another host or resumed after a suspend operation, the first packet sent by the guest will again determine the IP address that the guest can use on a particular interface.
+ </div><div class="para">
+ The value of <em class="replaceable"><code>dhcp</code></em> instucts libvirt to only honor DHCP server-assigned addresses with valid leases. This method supports the detection and usage of multiple IP address per interface. When a guest resumes after a suspend operation, any valid IP address leases are applied to its filters. Otherwise the guest is expected to use DHCP to obtain a new IP addresses. When a guest migrates to another physical host, the guest is required to re-run the DHCP protocol.
+ </div><div class="para">
+ If CTRL_IP_LEARNING is set to <em class="replaceable"><code>none</code></em>, libvirt does not do IP address learning and referencing IP without assigning it an explicit value is an error.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-vars-in-filters.html"><strong>Prev</strong>H.10.4. Usage of variables in filters</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="sub-sub-sect-DHCP-snooping.html"><strong>Next</strong>H.10.5.2. DHCP snooping</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-blkresize.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-blkresize.html
new file mode 100644
index 0000000..b153831
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-blkresize.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.13.3. Using blockresize to change the size of a domain path</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-man-disk-image.html" title="E.13. Disk image management with live block copy" /><link rel="prev" href="sub-sect-blockpull.html" title="E.13.2. Using blockpull to shorten a backing chain" /><link rel="next" href="sect-guest-cpu-model-config.html" title="E.14. Guest CPU model configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="su
b-sect-blockpull.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-guest-cpu-model-config.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-blkresize"><div class="titlepage"><div><div><h3 class="title">E.13.3. Using blockresize to change the size of a domain path</h3></div></div></div><div class="para">
+ <code class="command">blockresize</code> can be used to re-size a block device of a domain while the domain is running, using the absolute path of the block device which also corresponds to a unique target name (<code class="command"><target dev="name"/></code>) or source file (<code class="command"><source file="name"/></code>). This can be applied to one of the disk devices attached to domain (you can use the command <code class="command">domblklist</code> to print a table showing the brief information of all block devices associated with a given domain).
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Live image re-sizing will always resize the image, but may not immediately be picked up by guests. With recent guest kernels, the size of virtio-blk devices is automatically updated (older kernels require a guest reboot). With SCSI devices, it is required to manually trigger a re-scan in the guest with the command, <code class="command">echo > /sys/class/scsi_device/0:0:0:0/device/rescan</code>. In addition, with IDE it is required to reboot the guest before it picks up the new size.
+ </div></div></div><div class="procedure"><ul><li class="step"><div class="para">
+ Run the following command: <code class="command">blockresize [domain] [path size]</code> where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Domain is the unique target name or source file of the domain whose size you want to change
+ </div></li><li class="listitem"><div class="para">
+ Path size is a scaled integer which defaults to KiB (blocks of 1024 bytes) if there is no suffix. You must use a suffix of "B" to for bytes.
+ </div></li></ul></div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-blockpull.html"><strong>Prev</strong>E.13.2. Using blockpull to shorten a backing chain</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-guest-cpu-model-config.html"><strong>Next</strong>E.14. Guest CPU model configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-blockpull.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-blockpull.html
new file mode 100644
index 0000000..4949d0c
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-blockpull.html
@@ -0,0 +1,58 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.13.2. Using blockpull to shorten a backing chain</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-man-disk-image.html" title="E.13. Disk image management with live block copy" /><link rel="prev" href="sect-man-disk-image.html" title="E.13. Disk image management with live block copy" /><link rel="next" href="sub-sect-blkresize.html" title="E.13.3. Using blockresize to change the size of a domain path" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a access
key="p" href="sect-man-disk-image.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-blkresize.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-blockpull"><div class="titlepage"><div><div><h3 class="title">E.13.2. Using blockpull to shorten a backing chain</h3></div></div></div><div class="para">
+ <code class="command">blockpull</code> can be used in in the following applications:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Flattens an image by populating it with data from its backing image chain. This makes the image file self-contained so that it no longer depends on backing images and looks like this:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Before: base.img ← Active
+ </div></li><li class="listitem"><div class="para">
+ After: base.img is no longer used by the guest and Active contains all of the data.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Flattens part of the backing image chain. This can be used to flatten snapshots into the top-level image and looks like this:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Before: base ← sn1 ←sn2 ← active
+ </div></li><li class="listitem"><div class="para">
+ After: base.img ← active. Note that active now contains all data from sn1 and sn2 and neither sn1 nor sn2 are used by the guest.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Moves the disk image to a new file system on the host. This is allows image files to be moved while the guest is running and looks like this:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Before (The original image file): <code class="filename">/fs1/base.vm.img</code>
+ </div></li><li class="listitem"><div class="para">
+ After: <code class="filename">/fs2/active.vm.qcow2</code> is now the new file system and <code class="filename">/fs1/base.vm.img</code> is no longer used.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Useful in live migration with post-copy storage migration. The disk image is copied from the source host to the destination host after live migration completes.
+ </div><div class="para">
+ In short this is what happens: Before:<code class="filename">/source-host/base.vm.img</code> After:<code class="filename">/destination-host/active.vm.qcow2</code>.<code class="filename">/source-host/base.vm.img</code> is no longer used.
+ </div></li></ul></div><div class="procedure" id="virsh-blk-pull-pro"><h6>Procedure E.2. Using blockpull to shorten a backing chain</h6><ol class="1"><li class="step"><div class="para">
+ It may be helpful to run this command prior to running <code class="command">blockpull</code>:
+ </div><pre class="screen">#<code class="command"> virsh snapshot-create-as $dom $name -- disk-only</code></pre></li><li class="step"><div class="para">
+ If the chain looks like this: <code class="command">base ← snap1 ← snap2 ← active</code> run the following:
+ </div><pre class="screen">#<code class="command"> virsh blockpull $dom $disk snap1</code></pre><div class="para">
+ This command makes 'snap1' the backing file of active, by pulling data from snap2 into active resulting in: base ← snap1 ← active.
+ </div></li><li class="step"><div class="para">
+ Once the <code class="command">blockpull</code> is complete, the <span class="application"><strong>libvirt</strong></span> tracking of the snapshot that created the extra image in the chain is no longer useful. Delete the tracking on the outdated snapshot with this command:
+ </div><pre class="screen">#<code class="command"> virsh snapshot-delete $dom $name -- metadata</code></pre></li></ol></div><div class="para">
+ Additional applications of <code class="command">blockpull</code> can be done as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ To flatten a single image and populate it with data from its backing image chain:<code class="command"># virsh blockpull example-domain vda -- wait</code>
+ </div></li><li class="listitem"><div class="para">
+ To flatten part of the backing image chain:<code class="command"># virsh blockpull example-domain vda -- base /path/to/base.img -- wait</code>
+ </div></li><li class="listitem"><div class="para">
+ To move the disk image to a new file system on the host:<code class="command"># virsh snapshot-create example-domain -- xmlfile /path/to/new.xml -- disk-only</code> followed by <code class="command"># virsh blockpull example-domain vda -- wait</code>
+ </div></li><li class="listitem"><div class="para">
+ To use live migration with post-copy storage migration:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ On the destination run:
+ </div><pre class="screen"><code class="command"> # qemu-img create -f qcow2 -o backing_file=/source-host/vm.img /destination-host/vm.qcow2</code></pre></li><li class="listitem"><div class="para">
+ On the source run:
+ </div><pre class="screen"><code class="command"># virsh migrate example-domain</code></pre></li><li class="listitem"><div class="para">
+ On the destination run:
+ </div><pre class="screen"><code class="command"># virsh blockpull example-domain vda -- wait</code></pre></li></ul></div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-man-disk-image.html"><strong>Prev</strong>E.13. Disk image management with live block copy</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="sub-sect-blkresize.html"><strong>Next</strong>E.13.3. Using blockresize to change the size of a...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-element-oview.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-element-oview.html
new file mode 100644
index 0000000..e1b6b5c
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-element-oview.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.7. Element and attribute overview</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-applying-network-filtering.html" title="H.10. Applying network filtering" /><link rel="prev" href="sub-sect-vars-reserved.html" title="H.10.6. Reserved Variables" /><link rel="next" href="sub-sect-ref-filter.html" title="H.10.8. References to other filters" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-vars-reserved.html"><stro
ng>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-ref-filter.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-element-oview"><div class="titlepage"><div><div><h3 class="title">H.10.7. Element and attribute overview</h3></div></div></div><div class="para">
+ The root element required for all network filters is named filter with two possible attributes. The name attribute provides a unique name of the given filter. The chain attribute is optional but allows certain filters to be better organized for more efficient processing by the firewall subsystem of the underlying host. Currently the system only supports the chains root, ipv4, ipv6, arp and rarp.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-vars-reserved.html"><strong>Prev</strong>H.10.6. Reserved Variables</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="sub-sect-ref-filter.html"><strong>Next</strong>H.10.8. References to other filters</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-filt-chain-props.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-filt-chain-props.html
new file mode 100644
index 0000000..856c4fa
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-filt-chain-props.html
@@ -0,0 +1,48 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.3. Filtering chain priorities</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-applying-network-filtering.html" title="H.10. Applying network filtering" /><link rel="prev" href="sub-sect-filt-chain.html" title="H.10.2. Filtering chains" /><link rel="next" href="sub-sect-vars-in-filters.html" title="H.10.4. Usage of variables in filters" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-filt-chain.html"><stron
g>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-vars-in-filters.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-filt-chain-props"><div class="titlepage"><div><div><h3 class="title">H.10.3. Filtering chain priorities</h3></div></div></div><div class="para">
+ As previously mentioned, when creating a filtering rule, all chains are connected to the root chain. The order in which those chains are accessed is influenced by the priority of the chain. The following table shows the chains that can be assigned a priority and their default priorities.
+ </div><div class="table" id="tab-filtering-chain-priorities"><h6>Table H.1. Filtering chain default priorities values</h6><div class="table-contents"><table summary="Filtering chain default priorities values" border="1"><colgroup><col class="1" width="50%" /><col class="2" width="50%" /></colgroup><thead><tr><th class="">
+ Chain (prefix)
+ </th><th class="">
+ Default priority
+ </th></tr></thead><tbody><tr><td class="">
+ stp
+ </td><td class="">
+ -810
+ </td></tr><tr><td class="">
+ mac
+ </td><td class="">
+ -800
+ </td></tr><tr><td class="">
+ vlan
+ </td><td class="">
+ -750
+ </td></tr><tr><td class="">
+ ipv4
+ </td><td class="">
+ -700
+ </td></tr><tr><td class="">
+ ipv6
+ </td><td class="">
+ -600
+ </td></tr><tr><td class="">
+ arp
+ </td><td class="">
+ -500
+ </td></tr><tr><td class="">
+ rarp
+ </td><td class="">
+ -400
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ A chain with a lower priority value is accessed before one with a higher value.
+ </div><div class="para">
+ The chains listed in <a class="xref" href="sub-sect-filt-chain-props.html#tab-filtering-chain-priorities">Table H.1, “Filtering chain default priorities values”</a> can be also be assigned custom priorities by writing a value in the range [-1000 to 1000] into the priority (XML) attribute in the filter node. <a class="xref" href="sub-sect-filt-chain.html">Section H.10.2, “Filtering chains”</a>filter shows the default priority of -500 for arp chains, for example.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-filt-chain.html"><strong>Prev</strong>H.10.2. Filtering chains</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="sub-sect-vars-in-filters.html"><strong>Next</strong>H.10.4. Usage of variables in filters</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-filt-chain.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-filt-chain.html
new file mode 100644
index 0000000..37ede5a
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-filt-chain.html
@@ -0,0 +1,67 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.2. Filtering chains</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-applying-network-filtering.html" title="H.10. Applying network filtering" /><link rel="prev" href="sect-applying-network-filtering.html" title="H.10. Applying network filtering" /><link rel="next" href="sub-sect-filt-chain-props.html" title="H.10.3. Filtering chain priorities" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-applying-
network-filtering.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-filt-chain-props.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-filt-chain"><div class="titlepage"><div><div><h3 class="title">H.10.2. Filtering chains</h3></div></div></div><div class="para">
+ Filtering rules are organized in filter chains. These chains can be thought of as having a tree structure with packet filtering rules as entries in individual chains (branches).
+ </div><div class="para">
+ Packets start their filter evaluation in the root chain and can then continue their evaluation in other chains, return from those chains back into the root chain or be dropped or accepted by a filtering rule in one of the traversed chains.
+ </div><div class="para">
+ Libvirt's network filtering system automatically creates individual root chains for every virtual machine's network interface on which the user chooses to activate traffic filtering. The user may write filtering rules that are either directly instantiated in the root chain or may create protocol-specific filtering chains for efficient evaluation of protocol-specific rules.
+ </div><div class="para">
+ The following chains exist:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ root
+ </div></li><li class="listitem"><div class="para">
+ mac
+ </div></li><li class="listitem"><div class="para">
+ stp (spanning tree protocol)
+ </div></li><li class="listitem"><div class="para">
+ vlan
+ </div></li><li class="listitem"><div class="para">
+ arp and rarp
+ </div></li><li class="listitem"><div class="para">
+ ipv4
+ </div></li><li class="listitem"><div class="para">
+ ipv6
+ </div></li></ul></div><div class="para">
+ Multiple chains evaluating the mac, stp, vlan, arp, rarp, ipv4, or ipv6 protocol can be created using the protocol name only as a prefix in the chain's name.
+ </div><div class="example" id="arp-pro-example"><h6>Example H.3. ARP traffic filtering</h6><div class="example-contents"><div class="para">
+ This example allows chains with names arp-xyz or arp-test to be specified and have their ARP protocol packets evaluated in those chains.
+ </div><div class="para">
+ The following filter XML shows an example of filtering ARP traffic in the arp chain.
+ </div><pre class="screen">
+<filter name='no-arp-spoofing' chain='arp' priority='-500'>
+ <uuid>f88f1932-debf-4aa1-9fbe-f10d3aa4bc95</uuid>
+ <rule action='drop' direction='out' priority='300'>
+ <mac match='no' srcmacaddr='$MAC'/>
+ </rule>
+ <rule action='drop' direction='out' priority='350'>
+ <arp match='no' arpsrcmacaddr='$MAC'/>
+ </rule>
+ <rule action='drop' direction='out' priority='400'>
+ <arp match='no' arpsrcipaddr='$IP'/>
+ </rule>
+ <rule action='drop' direction='in' priority='450'>
+ <arp opcode='Reply'/>
+ <arp match='no' arpdstmacaddr='$MAC'/>
+ </rule>
+ <rule action='drop' direction='in' priority='500'>
+ <arp match='no' arpdstipaddr='$IP'/>
+ </rule>
+ <rule action='accept' direction='inout' priority='600'>
+ <arp opcode='Request'/>
+ </rule>
+ <rule action='accept' direction='inout' priority='650'>
+ <arp opcode='Reply'/>
+ </rule>
+ <rule action='drop' direction='inout' priority='1000'/>
+</filter>
+</pre><div class="para">
+ The consequence of putting ARP-specific rules in the arp chain, rather than for example in the root chain, is that packets protocols other than ARP do not need to be evaluated by ARP protocol-specific rules. This improves the efficiency of the traffic filtering. However, one must then pay attention to only putting filtering rules for the given protocol into the chain since other rules will not be evaluated. For example, an IPv4 rule will not be evaluated in the ARP chain since IPv4 protocol packets will not traverse the ARP chain.
+ </div></div></div><br class="example-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-applying-network-filtering.html"><strong>Prev</strong>H.10. Applying network filtering</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="sub-sect-filt-chain-props.html"><strong>Next</strong>H.10.3. Filtering chain priorities</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-filter-rules.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-filter-rules.html
new file mode 100644
index 0000000..459bd5b
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-filter-rules.html
@@ -0,0 +1,51 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.9. Filter rules</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-applying-network-filtering.html" title="H.10. Applying network filtering" /><link rel="prev" href="sub-sect-ref-filter.html" title="H.10.8. References to other filters" /><link rel="next" href="sub-sect-supp-pros.html" title="H.10.10. Supported protocols" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-ref-filter.html"><strong>Pr
ev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-supp-pros.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-filter-rules"><div class="titlepage"><div><div><h3 class="title">H.10.9. Filter rules</h3></div></div></div><div class="para">
+ The following XML shows a simple example of a network traffic filter implementing a rule to drop traffic if the IP address (provided through the value of the variable IP) in an outgoing IP packet is not the expected one, thus preventing IP address spoofing by the VM.
+ </div><div class="example" id="filter-rules-example"><h6>Example H.8. Example of network traffic filtering</h6><div class="example-contents"><pre class="screen">
+<filter name='no-ip-spoofing' chain='ipv4'>
+ <uuid>fce8ae33-e69e-83bf-262e-30786c1f8072</uuid>
+ <rule action='drop' direction='out' priority='500'>
+ <ip match='no' srcipaddr='$IP'/>
+ </rule>
+</filter>
+</pre></div></div><br class="example-break" /><div class="para">
+ The traffic filtering rule starts with the rule node. This node may contain up to three of the following attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ action is mandatory can have the following values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ drop (matching the rule silently discards the packet with no further analysis)
+ </div></li><li class="listitem"><div class="para">
+ reject (matching the rule generates an ICMP reject message with no further analysis)
+ </div></li><li class="listitem"><div class="para">
+ accept (matching the rule accepts the packet with no further analysis)
+ </div></li><li class="listitem"><div class="para">
+ return (matching the rule passes this filter, but returns control to the calling filter for further analysis)
+ </div></li><li class="listitem"><div class="para">
+ continue (matching the rule goes on to the next rule for further analysis)
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ direction is mandatory can have the following values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ in for incomming traffic
+ </div></li><li class="listitem"><div class="para">
+ out for outgoing traffic
+ </div></li><li class="listitem"><div class="para">
+ inout for incoming and outgoing traffic
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ priority is optional. The priority of the rule controls the order in which the rule will be instantiated relative to other rules. Rules with lower values will be instantiated before rules with higher values. Valid values are in the range of -1000 to 1000. If this attribute is not provided, priority 500 will be assigned by default. Note that filtering rules in the root chain are sorted with filters connected to the root chain following their priorities. This allows to interleave filtering rules with access to filter chains. Refer to <a class="xref" href="sub-sect-filt-chain-props.html">Section H.10.3, “Filtering chain priorities”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ statematch is optional. Possible values are '0' or 'false' to turn the underlying connection state matching off. The default setting is 'true' or 1
+ </div></li></ul></div><div class="para">
+ For more information see <a class="xref" href="sub-sect-adv-filt-topics.html">Section H.10.11, “Advanced Filter Configuration Topics”</a>.
+ </div><div class="para">
+ The above example <a class="xref" href="sub-sect-ref-filter.html#exam-clean-traffic">Example H.7, “An Example of a clean traffic filter”</a> indicates that the traffic of <em class="replaceable"><code>type ip</code></em> will be associated with the chain <em class="replaceable"><code>ipv4</code></em> and the rule will have <code class="command">priority=<em class="replaceable"><code>500</code></em></code>. If for example another filter is referenced whose traffic of <em class="replaceable"><code>type ip</code></em> is also associated with the chain <em class="replaceable"><code>ipv4</code></em> then that filter's rules will be ordered relative to the <code class="command">priority=<em class="replaceable"><code>500</code></em></code> of the shown rule.
+ </div><div class="para">
+ A rule may contain a single rule for filtering of traffic. The above example shows that traffic of type ip is to be filtered.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-ref-filter.html"><strong>Prev</strong>H.10.8. References to other filters</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="sub-sect-supp-pros.html"><strong>Next</strong>H.10.10. Supported protocols</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-iso-mode.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-iso-mode.html
new file mode 100644
index 0000000..b351c22
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-iso-mode.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.3.3. Isolated mode</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-network-protocols.html" title="H.3. Networking protocols" /><link rel="prev" href="sub-sect-routed-mode-libvirt.html" title="H.3.2. Routed mode" /><link rel="next" href="sect-the-Default_Configuration-libvirt.html" title="H.4. The default configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-routed-mode-libvirt.html"><st
rong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-the-Default_Configuration-libvirt.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-iso-mode"><div class="titlepage"><div><div><h3 class="title">H.3.3. Isolated mode</h3></div></div></div><div class="para">
+ When using <span class="emphasis"><em>Isolated mode</em></span>, guests connected to the virtual switch can communicate with each other, and with the host, but their traffic will not pass outside of the host, nor can they receive traffic from outside the host. Using dnsmasq in this mode is required for basic functionality such as DHCP. However, even if this network is isolated from any physical network, DNS names are still resolved. Therefore a situation can arise when DNS names resolve but ICMP echo request (ping) commands fail.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-Other_routing_types-Isolated_mode"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-07-isolated-switch.png" width="444" alt="Virtual network switch in isolated mode" /></div></div><h6>Figure H.6. Virtual network switch in isolated mode</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-routed-mode-libvirt.html"><strong>Prev</strong>H.3.2. Routed mode</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-the-Default_Configuration-libvirt.html"><strong>Next</strong>H.4. The default configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-isolated-mode.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-isolated-mode.html
new file mode 100644
index 0000000..822031a
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-isolated-mode.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.5.3. Isolated mode</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-Virtualization-Virtual_Networking-Example_scenarios.html" title="H.5. Examples of common scenarios" /><link rel="prev" href="sub-sect-nat-mode.html" title="H.5.2. NAT mode" /><link rel="next" href="sect-Virtualization-Virtual_Networking-Managing_a_virtual_network.html" title="H.6. Managing a virtual network" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a ac
cesskey="p" href="sub-sect-nat-mode.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Virtual_Networking-Managing_a_virtual_network.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-isolated-mode"><div class="titlepage"><div><div><h3 class="title">H.5.3. Isolated mode</h3></div></div></div><div class="para">
+ Isolated mode allows virtual machines to communicate with each other only. They are unable to interact with the physical network.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-nat-mode.html"><strong>Prev</strong>H.5.2. NAT mode</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-Virtual_Networking-Managing_a_virtual_network.html"><strong>Next</strong>H.6. Managing a virtual network</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-limitations-filters-network-subsystem.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-limitations-filters-network-subsystem.html
new file mode 100644
index 0000000..e794c8e
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-limitations-filters-network-subsystem.html
@@ -0,0 +1,18 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.12. Limitations</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-applying-network-filtering.html" title="H.10. Applying network filtering" /><link rel="prev" href="sub-sub-sect-samp-filter.html" title="H.10.11.6. Sample custom filter" /><link rel="next" href="appe-Virtualization-Additional_resources.html" title="Appendix I. Additional resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-
sect-samp-filter.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="appe-Virtualization-Additional_resources.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-limitations-filters-network-subsystem"><div class="titlepage"><div><div><h3 class="title">H.10.12. Limitations</h3></div></div></div><div class="para">
+ The following is a list of the currently known limitations of the network filtering subsystem.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ VM migration is only supported if the whole filter tree that is referenced by a guest's top level filter is also available on the target host. The network filter <code class="filename">clean-traffic</code> for example should be available on all libvirt installations and thus enable migration of guests that reference this filter. To assure version compatibility is not a problem make sure you are using the most current version of libvirt by updating the package regurally.
+ </div></li><li class="listitem"><div class="para">
+ Migration must occur between libvirt insallations of version 0.8.1 or later in order not to lose the network traffic filters associated with an interface.
+ </div></li><li class="listitem"><div class="para">
+ VLAN (802.1Q) packets, if sent by a guest, cannot be filtered with rules for protocol IDs arp, rarp, ipv4 and ipv6. They can only be filtered with protocol IDs, MAC and VLAN. Therefore, the example filter clean-traffic <a class="xref" href="sect-applying-network-filtering.html#ex-net-filtering">Example H.1, “An example of network filtering”</a> will not work as expected.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-samp-filter.html"><strong>Prev</strong>H.10.11.6. Sample custom filter</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-Additional_resources.html"><strong>Next</strong>Appendix I. Additional resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-nat-mode.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-nat-mode.html
new file mode 100644
index 0000000..c40133e
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-nat-mode.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.5.2. NAT mode</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-Virtualization-Virtual_Networking-Example_scenarios.html" title="H.5. Examples of common scenarios" /><link rel="prev" href="sect-Virtualization-Virtual_Networking-Example_scenarios.html" title="H.5. Examples of common scenarios" /><link rel="next" href="sub-sect-isolated-mode.html" title="H.5.3. Isolated mode" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-Virtual_Networking-Example_scenarios.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-isolated-mode.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-nat-mode"><div class="titlepage"><div><div><h3 class="title">H.5.2. NAT mode</h3></div></div></div><div class="para">
+ NAT (Network Address Translation) mode is the default mode. It can be used for testing when there is no need for direct network visibility.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Virtual_Networking-Example_scenarios.html"><strong>Prev</strong>H.5. Examples of common scenarios</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="sub-sect-isolated-mode.html"><strong>Next</strong>H.5.3. Isolated mode</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-op-sys-cont-boot.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-op-sys-cont-boot.html
new file mode 100644
index 0000000..b92bf77
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-op-sys-cont-boot.html
@@ -0,0 +1,25 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.2.4. Container boot</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-dom-xml-op-sys-boot.html" title="J.2. Operating system booting" /><link rel="prev" href="sub-sect-op-sys-dir-kern-boot.html" title="J.2.3. Direct kernel boot" /><link rel="next" href="sect-smbios-sys-info.html" title="J.3. SMBIOS system information" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-op-sys-dir-kern-boot.html"><stron
g>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-smbios-sys-info.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-op-sys-cont-boot"><div class="titlepage"><div><div><h3 class="title">J.2.4. Container boot</h3></div></div></div><div class="para">
+ When booting a domain using container based virtualization, instead of a kernel or boot image, a path to the init binary is required, using the init element. By default this will be launched with no arguments. To specify the initial argv, use the <code class="sgmltag-element">initarg</code> element, repeated as many times as required. The <code class="sgmltag-element">cmdline</code> element, provides an equivalent to <code class="filename">/proc/cmdline</code> but will not effect <code class="sgmltag-starttag"><initarg></code>.
+ </div><div class="figure" id="fig-op-sys-cont-boot"><div class="figure-contents"><pre class="programlisting">
+>
+ ...
+ <span class="perl_Keyword"><os></span>
+ <span class="perl_Keyword"><type></span>hvm<span class="perl_Keyword"></type></span>
+ <span class="perl_Keyword"><loader></span>/usr/lib/xen/boot/hvmloader<span class="perl_Keyword"></loader></span>
+ <span class="perl_Keyword"><kernel></span>/root/f8-i386-vmlinuz<span class="perl_Keyword"></kernel></span>
+ <span class="perl_Keyword"><initrd></span>/root/f8-i386-initrd<span class="perl_Keyword"></initrd></span>
+ <span class="perl_Keyword"><cmdline></span>console=ttyS0 ks=http://example.com/f8-i386/os/<span class="perl_Keyword"></cmdline></span>
+ <span class="perl_Keyword"><dtb></span>/root/ppc.dtb<span class="perl_Keyword"></dtb></span>
+ <span class="perl_Keyword"></os></span>
+ ...
+
+</pre></div><h6>Figure J.5. Container boot</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-op-sys-dir-kern-boot.html"><strong>Prev</strong>J.2.3. Direct kernel 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-smbios-sys-info.html"><strong>Next</strong>J.3. SMBIOS system information</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-op-sys-dir-kern-boot.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-op-sys-dir-kern-boot.html
new file mode 100644
index 0000000..6b9b339
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-op-sys-dir-kern-boot.html
@@ -0,0 +1,51 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.2.3. Direct kernel boot</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-dom-xml-op-sys-boot.html" title="J.2. Operating system booting" /><link rel="prev" href="sub-sect-op-sys-host-boot.html" title="J.2.2. Host bootloader" /><link rel="next" href="sub-sect-op-sys-cont-boot.html" title="J.2.4. Container boot" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-op-sys-host-boot.html"><strong>Prev</strong>
</a></li><li class="next"><a accesskey="n" href="sub-sect-op-sys-cont-boot.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-op-sys-dir-kern-boot"><div class="titlepage"><div><div><h3 class="title">J.2.3. Direct kernel boot</h3></div></div></div><div class="para">
+ When installing a new guest OS, it is often useful to boot directly from a kernel and initrd stored in the host OS, allowing command line arguments to be passed directly to the installer. This capability is usually available for both para and full virtualized guests.
+ </div><div class="figure" id="fig-op-sys-dir-kern-boot"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><os></span>
+ <span class="perl_Keyword"><type></span>hvm<span class="perl_Keyword"></type></span>
+ <span class="perl_Keyword"><loader></span>/usr/lib/xen/boot/hvmloader<span class="perl_Keyword"></loader></span>
+ <span class="perl_Keyword"><kernel></span>/root/f8-i386-vmlinuz<span class="perl_Keyword"></kernel></span>
+ <span class="perl_Keyword"><initrd></span>/root/f8-i386-initrd<span class="perl_Keyword"></initrd></span>
+ <span class="perl_Keyword"><cmdline></span>console=ttyS0 ks=http://example.com/f8-i386/os/<span class="perl_Keyword"></cmdline></span>
+ <span class="perl_Keyword"><dtb></span>/root/ppc.dtb<span class="perl_Keyword"></dtb></span>
+ <span class="perl_Keyword"></os></span>
+ ...
+
+</pre></div><h6>Figure J.4. Direct kernel boot</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-dir-kernelboot-os"><h6>Table J.4. Direct kernel boot elements</h6><div class="table-contents"><table summary="Direct kernel boot elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><type></code>
+ </td><td class="">
+ same as described in the BIOS boot section
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><loader></code>
+ </td><td class="">
+ same as described in the BIOS boot section
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><kernel></code>
+ </td><td class="">
+ secifies the fully-qualified path to the kernel image in the host OS
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><initrd></code>
+ </td><td class="">
+ specifies the fully-qualified path to the (optional) ramdisk image in the host OS.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><cmdline></code>
+ </td><td class="">
+ specifies arguments to be passed to the kernel (or installer) at boot time. This is often used to specify an alternate primary console (eg serial port), or the installation media source / kickstart file
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-op-sys-host-boot.html"><strong>Prev</strong>J.2.2. Host bootloader</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="sub-sect-op-sys-cont-boot.html"><strong>Next</strong>J.2.4. Container boot</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-op-sys-host-boot.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-op-sys-host-boot.html
new file mode 100644
index 0000000..f241cc6
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-op-sys-host-boot.html
@@ -0,0 +1,31 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.2.2. Host bootloader</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-dom-xml-op-sys-boot.html" title="J.2. Operating system booting" /><link rel="prev" href="sect-dom-xml-op-sys-boot.html" title="J.2. Operating system booting" /><link rel="next" href="sub-sect-op-sys-dir-kern-boot.html" title="J.2.3. Direct kernel boot" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-dom-xml-op-sys-boot.html"><strong>
Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-op-sys-dir-kern-boot.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-op-sys-host-boot"><div class="titlepage"><div><div><h3 class="title">J.2.2. Host bootloader</h3></div></div></div><div class="para">
+ Hypervisors employing paravirtualization do not usually emulate a BIOS, but instead the host is responsible for the operating system boot. This may use a pseudo-bootloader in the host to provide an interface to choose a kernel for the guest. An example is pygrub with Xen.
+ </div><div class="figure" id="fig-op-sys-host-boot"><div class="figure-contents"><pre class="programlisting">
+ ...
+ <span class="perl_Keyword"><bootloader></span>/usr/bin/pygrub<span class="perl_Keyword"></bootloader></span>
+ <span class="perl_Keyword"><bootloader_args></span>--append single<span class="perl_Keyword"></bootloader_args></span>
+ ...
+</pre></div><h6>Figure J.3. Host bootloader domain XML</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-hostbootloader-os"><h6>Table J.3. BIOS bootloader elements</h6><div class="table-contents"><table summary="BIOS bootloader elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><bootloader></code>
+ </td><td class="">
+ provides a fully qualified path to the bootloader executable in the host OS. This bootloader will choose which kernel to boot. The required output of the bootloader is dependent on the hypervisor in use.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><bootloader_args></code>
+ </td><td class="">
+ allows command line arguments to be passed to the bootloader (optional command)
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-dom-xml-op-sys-boot.html"><strong>Prev</strong>J.2. Operating system booting</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="sub-sect-op-sys-dir-kern-boot.html"><strong>Next</strong>J.2.3. Direct kernel boot</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-ref-filter.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-ref-filter.html
new file mode 100644
index 0000000..ce714c0
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-ref-filter.html
@@ -0,0 +1,28 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.8. References to other filters</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-applying-network-filtering.html" title="H.10. Applying network filtering" /><link rel="prev" href="sub-sect-element-oview.html" title="H.10.7. Element and attribute overview" /><link rel="next" href="sub-sect-filter-rules.html" title="H.10.9. Filter rules" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-element-oview.html"><stron
g>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-filter-rules.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-ref-filter"><div class="titlepage"><div><div><h3 class="title">H.10.8. References to other filters</h3></div></div></div><div class="para">
+ Any filter may hold references to other filters. Individual filters may be referenced multiple times in a filter tree but references between filters must not introduce loops.
+ </div><div class="example" id="exam-clean-traffic"><h6>Example H.7. An Example of a clean traffic filter</h6><div class="example-contents"><div class="para">
+ The following shows the XML of the clean-traffic network filter referencing several other filters.
+ </div><pre class="screen">
+<filter name='clean-traffic'>
+ <uuid>6ef53069-ba34-94a0-d33d-17751b9b8cb1</uuid>
+ <filterref filter='no-mac-spoofing'/>
+ <filterref filter='no-ip-spoofing'/>
+ <filterref filter='allow-incoming-ipv4'/>
+ <filterref filter='no-arp-spoofing'/>
+ <filterref filter='no-other-l2-traffic'/>
+ <filterref filter='qemu-announce-self'/>
+</filter>
+</pre><div class="para">
+ To reference another filter, the XML node filterref needs to be provided inside a filter node. This node must have the attribute filter whose value contains the name of the filter to be referenced.
+ </div></div></div><br class="example-break" /><div class="para">
+ New network filters can be defined at any time and may contain references to network filters that are not known to libvirt, yet. However, once a virtual machine is started or a network interface referencing a filter is to be hotplugged, all network filters in the filter tree must be available. Otherwise the virtual machine will not start or the network interface cannot be attached.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-element-oview.html"><strong>Prev</strong>H.10.7. Element and attribute 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="sub-sect-filter-rules.html"><strong>Next</strong>H.10.9. Filter rules</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-routed-mode-libvirt.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-routed-mode-libvirt.html
new file mode 100644
index 0000000..0133887
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-routed-mode-libvirt.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.3.2. Routed mode</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-network-protocols.html" title="H.3. Networking protocols" /><link rel="prev" href="sect-network-protocols.html" title="H.3. Networking protocols" /><link rel="next" href="sub-sect-iso-mode.html" title="H.3.3. Isolated mode" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-network-protocols.html"><strong>Prev</strong></a></li><li class
="next"><a accesskey="n" href="sub-sect-iso-mode.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-routed-mode-libvirt"><div class="titlepage"><div><div><h3 class="title">H.3.2. Routed mode</h3></div></div></div><div class="para">
+ When using <span class="emphasis"><em>routed mode</em></span>, the virtual switch connects to the physical LAN connected to the host, passing traffic back and forth without the use of NAT. The virtual switch can examine all traffic and use the information contained within the network packets to make routing decisions. When using this mode, all of the virtual machines are in their own subnet, routed through a virtual switch. This situation is not always ideal as no other hosts on the physical network are aware of the virtual machines without manual physical router configuration, and cannot access the virtual machines. Routed mode operates at Layer 3 of the OSI networking model.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-Other_routing_types-Routed_mode"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-06-routed-switch.png" width="444" alt="Virtual network switch in routed mode" /></div></div><h6>Figure H.5. Virtual network switch in routed mode</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-network-protocols.html"><strong>Prev</strong>H.3. Networking protocols</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="sub-sect-iso-mode.html"><strong>Next</strong>H.3.3. Isolated mode</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-supp-pros.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-supp-pros.html
new file mode 100644
index 0000000..991b5ec
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-supp-pros.html
@@ -0,0 +1,97 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.10. Supported protocols</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-applying-network-filtering.html" title="H.10. Applying network filtering" /><link rel="prev" href="sub-sect-filter-rules.html" title="H.10.9. Filter rules" /><link rel="next" href="sub-sub-sect-vlan.html" title="H.10.10.2. VLAN (802.1Q)" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-filter-rules.html"><strong>Prev</strong></a><
/li><li class="next"><a accesskey="n" href="sub-sub-sect-vlan.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-supp-pros"><div class="titlepage"><div><div><h3 class="title">H.10.10. Supported protocols</h3></div></div></div><div class="para">
+ The following sections list and give some details about the protocols that are supported by the network filtering subsystem. This type of traffic rule is provided in the rule node as a nested node. Depending on the traffic type a rule is filtering, the attributes are different. The above example showed the single attribute <em class="parameter"><code>srcipaddr</code></em> that is valid inside the ip traffic filtering node. The following sections show what attributes are valid and what type of data they are expecting. The following datatypes are available:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ UINT8 : 8 bit integer; range 0-255
+ </div></li><li class="listitem"><div class="para">
+ UINT16: 16 bit integer; range 0-65535
+ </div></li><li class="listitem"><div class="para">
+ MAC_ADDR: MAC address in dotted decimal format, i.e., 00:11:22:33:44:55
+ </div></li><li class="listitem"><div class="para">
+ MAC_MASK: MAC address mask in MAC address format, i.e., FF:FF:FF:FC:00:00
+ </div></li><li class="listitem"><div class="para">
+ IP_ADDR: IP address in dotted decimal format, i.e., 10.1.2.3
+ </div></li><li class="listitem"><div class="para">
+ IP_MASK: IP address mask in either dotted decimal format (255.255.248.0) or CIDR mask (0-32)
+ </div></li><li class="listitem"><div class="para">
+ IPV6_ADDR: IPv6 address in numbers format, i.e., FFFF::1
+ </div></li><li class="listitem"><div class="para">
+ IPV6_MASK: IPv6 mask in numbers format (FFFF:FFFF:FC00::) or CIDR mask (0-128)
+ </div></li><li class="listitem"><div class="para">
+ STRING: A string
+ </div></li><li class="listitem"><div class="para">
+ BOOLEAN: 'true', 'yes', '1' or 'false', 'no', '0'
+ </div></li><li class="listitem"><div class="para">
+ IPSETFLAGS: The source and destination flags of the ipset described by up to 6 'src' or 'dst' elements selecting features from either the source or destination part of the packet header; example: src,src,dst. The number of 'selectors' to provide here depends on the type of ipset that is referenced
+ </div></li></ul></div><div class="para">
+ Every attribute except for those of type <em class="parameter"><code>IP_MASK</code></em> or <em class="parameter"><code>IPV6_MASK</code></em> can be negated using the match attribute with value <em class="replaceable"><code>no</code></em>. Multiple negated attributes may be grouped together. The following XML fragment shows such an example using abstract attributes.
+ </div><pre class="screen">
+[...]
+ <rule action='drop' direction='in'>
+ <protocol match='no' attribute1='value1' attribute2='value2'/>
+ <protocol attribute3='value3'/>
+ </rule>
+[...]
+</pre><div class="para">
+ Rules behave evaluate the rule as well as look at it logically within the boundaries of the given protocol attributes. Thus, if a single attribute's value does not match the one given in the rule, the whole rule will be skipped during the evaluation process. Therefore, in the above example incoming traffic will only be dropped if: the protocol property <em class="parameter"><code>attribute1</code></em> does not match both <em class="parameter"><code>value1</code></em> and the protocol property <em class="parameter"><code>attribute2</code></em> does not match <em class="parameter"><code>value2</code></em> and the protocol property <em class="parameter"><code>attribute3</code></em> matches <em class="parameter"><code>value3</code></em>.
+ </div><div class="section" id="sub-sub-sect-mac-filter-rules"><div class="titlepage"><div><div><h4 class="title">H.10.10.1. MAC (Ethernet)</h4></div></div></div><div class="para">
+ Protocol ID: mac
+ </div><div class="para">
+ Rules of this type should go into the root chain.
+ </div><div class="table" id="table-mac-vars"><h6>Table H.3. MAC protocol types</h6><div class="table-contents"><table summary="MAC protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of destination
+ </td></tr><tr><td class="">
+ protocolid
+ </td><td class="">
+ UINT16 (0x600-0xffff), STRING
+ </td><td class="">
+ Layer 3 protocol ID. Valid strings include [arp, rarp, ipv4, ipv6]
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The filter can be written as such:
+ </div><pre class="screen">
+[...]
+<mac match='no' srcmacaddr='$MAC'/>
+[...]
+</pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-filter-rules.html"><strong>Prev</strong>H.10.9. Filter rules</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="sub-sub-sect-vlan.html"><strong>Next</strong>H.10.10.2. VLAN (802.1Q)</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-vars-in-filters.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-vars-in-filters.html
new file mode 100644
index 0000000..9210d01
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-vars-in-filters.html
@@ -0,0 +1,72 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.4. Usage of variables in filters</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-applying-network-filtering.html" title="H.10. Applying network filtering" /><link rel="prev" href="sub-sect-filt-chain-props.html" title="H.10.3. Filtering chain priorities" /><link rel="next" href="sub-sect-auto-IP-add-detect-dhcp-snoop.html" title="H.10.5. Automatic IP address detection and DHCP snooping" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a acc
esskey="p" href="sub-sect-filt-chain-props.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-auto-IP-add-detect-dhcp-snoop.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-vars-in-filters"><div class="titlepage"><div><div><h3 class="title">H.10.4. Usage of variables in filters</h3></div></div></div><div class="para">
+ There are two variables that have been reserved for usage by the network traffic filtering subsystem: MAC and IP.
+ </div><div class="para">
+ <em class="parameter"><code>MAC</code></em> is designated for the MAC address of the network interface. A filtering rule that references this variable will automatically be replaced with the MAC address of the interface. This works without the user having to explicitly provide the MAC parameter. Even though it is possible to specify the MAC parameter similar to the IP parameter above, it is discouraged since libvirt knows what MAC address an interface will be using.
+ </div><div class="para">
+ The parameter <em class="parameter"><code>IP</code></em> represents the IP address that the operating system inside the virtual machine is expected to use on the given interface. The IP parameter is special in so far as the libvirt daemon will try to determine the IP address (and thus the IP parameter's value) that is being used on an interface if the parameter is not explicitly provided but referenced. For current limitations on IP address detection, consult the section on limitations <a class="xref" href="sub-sect-limitations-filters-network-subsystem.html">Section H.10.12, “Limitations”</a> on how to use this feature and what to expect when using it. The XML file shown in <a class="xref" href="sub-sect-filt-chain.html">Section H.10.2, “Filtering chains”</a> contains the filter <em class="parameter"><code>no-arp-spoofing</code></em>, which is an example of using a network filter XML to reference the MAC and IP variables.
+ </div><div class="para">
+ Note that referenced variables are always prefixed with the character <em class="parameter"><code>$</code></em>. The format of the value of a variable must be of the type expected by the filter attribute identified in the XML. In the above example, the <em class="parameter"><code>IP</code></em> parameter must hold a legal IP address in standard format. Failure to provide the correct structure will result in the filter variable not being replaced with a value and will prevent a virtual machine from starting or will prevent an interface from attaching when hotplugging is being used. Some of the types that are expected for each XML attribute are shown in the example <a class="xref" href="sub-sect-vars-in-filters.html#example-vars-xml-iptraffic-filter">Example H.4, “Sample variable types”</a>.
+ </div><div class="example" id="example-vars-xml-iptraffic-filter"><h6>Example H.4. Sample variable types</h6><div class="example-contents"><div class="para">
+ As variables can contain lists of elements, (the variable IP can contain multiple IP addresses that are valid on a particular interface, for example), the notation for providing multiple elements for the IP variable is:
+ </div><pre class="screen">
+ <devices>
+ <interface type='bridge'>
+ <mac address='00:16:3e:5d:c7:9e'/>
+ <filterref filter='clean-traffic'>
+ <parameter name='IP' value='10.0.0.1'/>
+ <parameter name='IP' value='10.0.0.2'/>
+ <parameter name='IP' value='10.0.0.3'/>
+ </filterref>
+ </interface>
+ </devices>
+</pre><div class="para">
+ This XML file creates filters to enable multiple IP addresses per interface. Each of the IP addresses will result in a seperate filtering rule. Therefore using the XML above and the the following rule, three individual filtering rules (one for each IP address) will be created:
+ </div><pre class="screen">
+ <rule action='accept' direction='in' priority='500'>
+ <tcp srpipaddr='$IP'/>
+ </rule>
+</pre><div class="para">
+ As it is possible to access individual elements of a variable holding a list of elements, a filtering rule like the following accesses the 2nd element of the variable <em class="replaceable"><code>DSTPORTS</code></em>.
+ </div><pre class="screen">
+ <rule action='accept' direction='in' priority='500'>
+ <udp dstportstart='$DSTPORTS[1]'/>
+ </rule>
+</pre></div></div><br class="example-break" /><div class="example" id="exam-fil-rules-combo"><h6>Example H.5. Using a variety of variables</h6><div class="example-contents"><div class="para">
+ As it is possible to create filtering rules that represent all possible combinations of rules from different lists using the notation <code class="command">$VARIABLE[@<iterator id="x">]</code>. The following rule allows a virtual machine to receive traffic on a set of ports, which are specified in <em class="replaceable"><code>DSTPORTS</code></em>, from the set of source IP address specified in <em class="replaceable"><code>SRCIPADDRESSES</code></em>. The rule generates all combinations of elements of the variable <em class="replaceable"><code>DSTPORTS</code></em> with those of <em class="replaceable"><code>SRCIPADDRESSES</code></em> by using two independent iterators to access their elements.
+ </div><pre class="screen">
+ <rule action='accept' direction='in' priority='500'>
+ <ip srcipaddr='$SRCIPADDRESSES[@1]' dstportstart='$DSTPORTS[@2]'/>
+ </rule>
+</pre><div class="para">
+ Assign concrete values to <em class="replaceable"><code>SRCIPADDRESSES</code></em> and <em class="replaceable"><code>DSTPORTS</code></em> as shown:
+ </div><pre class="screen">
+ SRCIPADDRESSES = [ 10.0.0.1, 11.1.2.3 ]
+ DSTPORTS = [ 80, 8080 ]
+</pre><div class="para">
+ Assigning values to the variables using <code class="command">$SRCIPADDRESSES[@1]</code> and <code class="command">$DSTPORTS[@2]</code> would then result in all combinations of addresses and ports being created as shown:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ 10.0.0.1, 80
+ </div></li><li class="listitem"><div class="para">
+ 10.0.0.1, 8080
+ </div></li><li class="listitem"><div class="para">
+ 11.1.2.3, 80
+ </div></li><li class="listitem"><div class="para">
+ 11.1.2.3, 8080
+ </div></li></ul></div><div class="para">
+ Accessing the same variables using a single iterator, for example by using the notation <code class="command">$SRCIPADDRESSES[@1]</code> and <code class="command">$DSTPORTS[@1]</code>, would result in parallel access to both lists and result in the following combinations:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ 10.0.0.1, 80
+ </div></li><li class="listitem"><div class="para">
+ 11.1.2.3, 8080
+ </div></li></ul></div></div></div><br class="example-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ <code class="command">$VARIABLE</code> is short-hand for <code class="command">$VARIABLE[@0]</code>. The former notation always assumes the role of iterator with <code class="command">iterator id="0"</code> added as shown in the opening paragraph at the top of this section.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-filt-chain-props.html"><strong>Prev</strong>H.10.3. Filtering chain priorities</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="sub-sect-auto-IP-add-detect-dhcp-snoop.html"><strong>Next</strong>H.10.5. Automatic IP address detection and DHCP s...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-vars-reserved.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-vars-reserved.html
new file mode 100644
index 0000000..0504f04
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-vars-reserved.html
@@ -0,0 +1,40 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.6. Reserved Variables</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-applying-network-filtering.html" title="H.10. Applying network filtering" /><link rel="prev" href="sub-sub-sect-DHCP-snooping.html" title="H.10.5.2. DHCP snooping" /><link rel="next" href="sub-sect-element-oview.html" title="H.10.7. Element and attribute overview" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-DHCP-snooping.
html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-element-oview.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-vars-reserved"><div class="titlepage"><div><div><h3 class="title">H.10.6. Reserved Variables</h3></div></div></div><div class="para">
+ <a class="xref" href="sub-sect-vars-reserved.html#table-res-vars">Table H.2, “Reserved variables”</a> shows the variables that are considered reserved and are used by libvirt:
+ </div><div class="table" id="table-res-vars"><h6>Table H.2. Reserved variables</h6><div class="table-contents"><table summary="Reserved variables" border="1"><colgroup><col class="1" width="50%" /><col class="2" width="50%" /></colgroup><thead><tr><th class="">
+ Variable Name
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ MAC
+ </td><td class="">
+ The MAC address of the interface
+ </td></tr><tr><td class="">
+ IP
+ </td><td class="">
+ The list of IP addresses in use by an interface
+ </td></tr><tr><td class="">
+ IPV6
+ </td><td class="">
+ Not currently implemented: the list of IPV6 addresses in use by an interface
+ </td></tr><tr><td class="">
+ DHCPSERVER
+ </td><td class="">
+ The list of IP addresses of trusted DHCP servers
+ </td></tr><tr><td class="">
+ DHCPSERVERV6
+ </td><td class="">
+ Not currently implemented: The list of IPv6 addresses of trusted DHCP servers
+ </td></tr><tr><td class="">
+ CTRL_IP_LEARNING
+ </td><td class="">
+ The choice of the IP address detection mode
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-DHCP-snooping.html"><strong>Prev</strong>H.10.5.2. DHCP snooping</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="sub-sect-element-oview.html"><strong>Next</strong>H.10.7. Element and attribute overview</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-Network-interfaces.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-Network-interfaces.html
new file mode 100644
index 0000000..1cdcb13
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-Network-interfaces.html
@@ -0,0 +1,56 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9. Network interfaces</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-smartcard.html" title="J.16.8. Smartcard devices" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-bridge-to-lan.html" title="J.16.9.2. Bridge to LAN" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p"
href="sub-section-libvirt-dom-xml-devices-smartcard.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-bridge-to-lan.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-Network-interfaces"><div class="titlepage"><div><div><h3 class="title">J.16.9. Network interfaces</h3></div></div></div><div class="para">
+ The network interface devices are modified using managment tools that will configure the following part of the Domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'bridge'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> bridge=</span><span class="perl_String">'xenbr0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">'00:16:3e:5d:c7:9e'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><script</span><span class="perl_Others"> path=</span><span class="perl_String">'vif-bridge'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><rom</span><span class="perl_Others"> bar=</span><span class="perl_String">'off'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.36. Devices - network interfaces</h6></div><br class="figure-break" /><div class="para">
+ There are several possibilities for specifying a network interface visible to the guest. Each subsection below provides more details about common setup options. Additionally, each <code class="sgmltag-starttag"><interface></code> element has an optional <code class="sgmltag-starttag"><address></code> sub-element that can tie the interface to a particular pci slot, with attribute <code class="sgmltag-attribute">type='pci'</code> (Refer to <a class="xref" href="sub-section-libvirt-dom-xml-devices-device-addresses.html">Section J.16.3, “Device addresses”</a>).
+ </div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-virtual-network"><div class="titlepage"><div><div><h4 class="title">J.16.9.1. Virtual networks</h4></div></div></div><div class="para">
+ This is the recommended configuration for general guest connectivity on hosts with dynamic / wireless networking configurations (or multi-host environments where the host hardware details are described separately in a <code class="sgmltag-starttag"><network></code> definition). In addition, it provides a connection whose details are described by the named network definition. Depending on the virtual network's <code class="sgmltag-attribute">forward mode</code> configuration, the network may be totally isolated (no <code class="sgmltag-starttag"><forward></code> element given), NAT'ing to an explicit network device or to the default route (<code class="sgmltag-attribute">forward mode='nat'</code>), routed with no NAT (<code class="sgmltag-attribute">forward mode='route'/</code>), or connected directly to one of the host's network interfaces (via macvtap) or bridge devices (<code class="sgmltag-attribute">forward mode='bridge|private|vepa|passthrough'/</code>)
+ </div><div class="para">
+ For networks with a forward mode of bridge, private, vepa, and passthrough, it is assumed that the host has any necessary DNS and DHCP services already setup outside the scope of libvirt. In the case of isolated, nat, and routed networks, DHCP and DNS are provided on the virtual network by libvirt, and the IP range can be determined by examining the virtual network config with <code class="command">virsh net-dumpxml [networkname]</code>. There is one virtual network called 'default' setup out of the box which does NAT'ing to the default route and has an IP range of 192.168.122.0/255.255.255.0. Each guest will have an associated tun device created with a name of vnetN, which can also be overridden with the <code class="sgmltag-starttag"><target></code> element (refer to <a class="xref" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element.html">Section J.16.9.10, “Overriding the target element”</a>).
+ </div><div class="para">
+ When the source of an interface is a network, a portgroup can be specified along with the name of the network; one network may have multiple portgroups defined, with each portgroup containing slightly different configuration information for different classes of network connections. Also, similar to <code class="sgmltag-starttag"><direct></code> network connections (described below), a connection of type <code class="sgmltag-attribute">network</code> may specify a <code class="sgmltag-starttag"><virtualport></code> element, with configuration data to be forwarded to a vepa (802.1Qbg) or 802.1Qbh compliant switch, or to an Open vSwitch virtual switch.
+ </div><div class="para">
+ Since the actual type of switch may vary depending on the configuration in the <code class="sgmltag-starttag"><network></code> on the host, it is acceptable to omit the virtualport type attribute, and specify attributes from multiple different virtualport types (and also to leave out certain attributes); at domain startup time, a complete <code class="sgmltag-starttag"><virtualport></code> element will be constructed by merging together the type and attributes defined in the network and the portgroup referenced by the interface. The newly-constructed virtualport is a combination of both. The attributes from lower virtualport can't make changes on the ones defined in higher virtualport. Interfaces take the highest priority, portgroup is lowest priority.
+ </div><div class="para">
+ For example, in order to work properly with both an 802.1Qbh switch and an Open vSwitch switch, you may choose to specify no type, but both an <code class="sgmltag-attribute">profileid</code> (in case the switch is 802.1Qbh) and an <code class="sgmltag-attribute">interfaceid</code> (in case the switch is Open vSwitch) (you may also omit the other attributes, such as <code class="sgmltag-attribute">managerid</code>, <code class="sgmltag-attribute">typeid</code>, or <code class="sgmltag-attribute">profileid</code>, to be filled in from the network's <code class="sgmltag-attribute">virtualport</code>). If you want to limit a guest to connecting only to certain types of switches, you can specify the virtualport type, but still omit some/all of the parameters - in this case if the host's network has a different type of virtualport, connection of the interface will fail. The virtual network parameters are defined using management tools that modify the following part of the do
main XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-virt-net"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Others"> portgroup=</span><span class="perl_String">'engineering'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet7'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">"00:11:22:33:44:55"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><virtualport></span>
+ <span class="perl_Keyword"><parameters</span><span class="perl_Others"> instanceid=</span><span class="perl_String">'09b11c53-8b5c-4eeb-8f00-d84eaa0aaa4f'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></virtualport></span>
+
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.37. Devices - network interfaces- virtual networks</h6></div><br class="figure-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-smartcard.html"><strong>Prev</strong>J.16.8. Smartcard 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="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-bridge-to-lan.html"><strong>Next</strong>J.16.9.2. Bridge to LAN</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-channel.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-channel.html
new file mode 100644
index 0000000..19ebd51
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-channel.html
@@ -0,0 +1,42 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.16. Channel</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-guest-interface.html" title="J.16.15. Guest interfaces" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-host-interface.html" title="J.16.17. Host interface" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-secti
on-libvirt-dom-xml-devices-guest-interface.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-host-interface.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-channel"><div class="titlepage"><div><div><h3 class="title">J.16.16. Channel</h3></div></div></div><div class="para">
+ This represents a private communication channel between the host and the guest and is manipulated by making changes to your guest virtual machine using a management tool that results in changes made to the following section of the domain xml
+ </div><div class="figure" id="fig-dom-xml-devices-channel"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> type=</span><span class="perl_String">'unix'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'bind'</span><span class="perl_Others"> path=</span><span class="perl_String">'/tmp/guestfwd'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'guestfwd'</span><span class="perl_Others"> address=</span><span class="perl_String">'10.0.2.1'</span><span class="perl_Others"> port=</span><span class="perl_String">'4600'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></channel></span>
+
+ <span class="perl_Comment"><!-- KVM virtio channel --></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio'</span><span class="perl_Others"> name=</span><span class="perl_String">'arbitrary.virtio.serial.port.name'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></channel></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> type=</span><span class="perl_String">'unix'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'bind'</span><span class="perl_Others"> path=</span><span class="perl_String">'/var/lib/libvirt/qemu/f16x86_64.agent'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio'</span><span class="perl_Others"> name=</span><span class="perl_String">'org.qemu.guest_agent.0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></channel></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> type=</span><span class="perl_String">'spicevmc'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio'</span><span class="perl_Others"> name=</span><span class="perl_String">'com.redhat.spice.0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></channel></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.63. Channel</h6></div><br class="figure-break" /><div class="para">
+ This can be implemented in a variety of ways. The specific type of <code class="sgmltag-starttag"><channel></code> is given in the <code class="sgmltag-attribute">type</code> attribute of the <code class="sgmltag-starttag"><target></code> element. Different channel types have different target attributes as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">guestfwd</code> - Dictates that TCP traffic sent by the guest to a given IP address and port is forwarded to the channel device on the host. The <code class="sgmltag-element">target</code> element must have address and port attributes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">virtio</code> - Paravirtualized virtio channel. <code class="sgmltag-starttag"><channel></code> is exposed in the guest under <code class="filename">/dev/vport*</code>, and if the optional element <code class="sgmltag-attribute">name</code>is specified, <code class="filename">/dev/virtio-ports/$name</code> (for more info, please see http://fedoraproject.org/wiki/Features/VirtioSerial). The optional element <code class="sgmltag-attribute">address</code> can tie the channel to a particular <code class="sgmltag-attribute">type='virtio-serial'</code> controller, documented above. With QEMU, if name is "org.qemu.guest_agent.0", then libvirt can interact with a guest agent installed in the guest, for actions such as guest shutdown or file system quiescing.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">spicevmc</code> - Paravirtualized SPICE channel. The domain must also have a SPICE server as a graphics device, at which point the host piggy-backs messages across the main channel. The <code class="sgmltag-element">target</code> element must be present, with attribute <code class="sgmltag-attribute">type='virtio';</code> an optional attribute <code class="sgmltag-attribute">name</code> controls how the guest will have access to the channel, and defaults to <code class="sgmltag-attribute">name='com.redhat.spice.0'</code>. The optional <code class="sgmltag-starttag"><address></code> element can tie the channel to a particular <code class="sgmltag-attribute">type='virtio-serial'</code> controller.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-guest-interface.html"><strong>Prev</strong>J.16.15. Guest interfaces</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="sub-section-libvirt-dom-xml-devices-host-interface.html"><strong>Next</strong>J.16.17. Host interface</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-consoles.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-consoles.html
new file mode 100644
index 0000000..0d4e838
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-consoles.html
@@ -0,0 +1,38 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.14. Consoles, serial, parallel, and channel devices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-video.html" title="J.16.13. Video devices" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-guest-interface.html" title="J.16.15. Guest interfaces" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt
-dom-xml-devices-video.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-guest-interface.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-consoles"><div class="titlepage"><div><div><h3 class="title">J.16.14. Consoles, serial, parallel, and channel devices</h3></div></div></div><div class="para">
+ A character device provides a way to interact with the virtual machine. Paravirtualized consoles, serial ports, parallel ports and channels are all classed as character devices and so represented using the same syntax.
+ </div><div class="para">
+ To specify the consols, channel and other devices configuration settings, use a mangement tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-dom-xml-devices-consoles"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><parallel</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/2'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></parallel></span>
+ <span class="perl_Keyword"><serial</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/3'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></serial></span>
+ <span class="perl_Keyword"><console</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/4'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></console></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> type=</span><span class="perl_String">'unix'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'bind'</span><span class="perl_Others"> path=</span><span class="perl_String">'/tmp/guestfwd'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'guestfwd'</span><span class="perl_Others"> address=</span><span class="perl_String">'10.0.2.1'</span><span class="perl_Others"> port=</span><span class="perl_String">'4600'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></channel></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.59. Consoles, serial, parallel, and channel devices</h6></div><br class="figure-break" /><div class="para">
+ In each of these directives, the top-level element name (parallel, serial, console, channel) describes how the device is presented to the guest. The guest interface is configured by the target element. The interface presented to the host is given in the type attribute of the top-level element. The host interface is configured by the source element. The source element may contain an optional seclabel to override the way that labelling is done on the socket path. If this element is not present, the security label is inherited from the per-domain setting. Each character device element has an optional sub-element <code class="sgmltag-element">address</code> which can tie the device to a particular controller or PCI slot.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-video.html"><strong>Prev</strong>J.16.13. Video 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="sub-section-libvirt-dom-xml-devices-guest-interface.html"><strong>Next</strong>J.16.15. Guest interfaces</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-controllers.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-controllers.html
new file mode 100644
index 0000000..47a8c09
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-controllers.html
@@ -0,0 +1,44 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.4. Controllers</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-device-addresses.html" title="J.16.3. Device addresses" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-device-leases.html" title="J.16.5. Device leases" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-
libvirt-dom-xml-devices-device-addresses.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-device-leases.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-controllers"><div class="titlepage"><div><div><h3 class="title">J.16.4. Controllers</h3></div></div></div><div class="para">
+ Depending on the guest architecture, some device busses can appear more than once, with a group of virtual devices tied to a virtual controller. Normally, libvirt can automatically infer such controllers without requiring explicit XML markup, but sometimes it is necessary to provide an explicit controller element.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-controllers"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><controller</span><span class="perl_Others"> type=</span><span class="perl_String">'ide'</span><span class="perl_Others"> index=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><controller</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio-serial'</span><span class="perl_Others"> index=</span><span class="perl_String">'0'</span><span class="perl_Others"> ports=</span><span class="perl_String">'16'</span><span class="perl_Others"> vectors=</span><span class="perl_String">'4'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><controller</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio-serial'</span><span class="perl_Others"> index=</span><span class="perl_String">'1'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'pci'</span><span class="perl_Others"> domain=</span><span class="perl_String">'0x0000'</span><span class="perl_Others"> bus=</span><span class="perl_String">'0x00'</span><span class="perl_Others"> slot=</span><span class="perl_String">'0x0a'</span><span class="perl_Others"> function=</span><span class="perl_String">'0x0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></controller></span>
+ ...
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.26. Devices - controllers</h6></div><br class="figure-break" /><div class="para">
+ Each controller has a mandatory attribute<code class="sgmltag-attribute">type</code>, which must be one of <code class="sgmltag-element">"ide", "fdc", "scsi", "sata", "usb", "ccid", or "virtio-serial"</code>, and a mandatory attribute <code class="sgmltag-attribute">index</code> which is the decimal integer describing in which order the bus controller is encountered (for use in controller attributes of <code class="sgmltag-element">address</code>elements). The "virtio-serial" controller has two additional optional attributes ports and vectors, which control how many devices can be connected through the controller. A "scsi" controller has an optional attribute <code class="sgmltag-element">model</code>, which is one of <code class="sgmltag-element">"auto", "buslogic", "ibmvscsi", "lsilogic", "lsias1068", "virtio-scsi" or "vmpvscsi"</code>. A "usb" controller has an optional attribute <code class="sgmltag-attribute">model</code>, which is one of <code class="sgmltag-elemen
t">"piix3-uhci", "piix4-uhci", "ehci", "ich9-ehci1", "ich9-uhci1", "ich9-uhci2", "ich9-uhci3", "vt82c686b-uhci", "pci-ohci" or "nec-xhci"</code>. Additionally, if the USB bus needs to be explicitly disabled for the guest, <code class="sgmltag-attribute">model='none'</code> may be used. The PowerPC64 "spapr-vio" addresses do not have an associated controller.
+ </div><div class="para">
+ For controllers that are themselves devices on a PCI or USB bus, an optional sub-element <code class="sgmltag-element">address</code> can specify the exact relationship of the controller to its master bus, with semantics given above.
+ </div><div class="para">
+ USB companion controllers have an optional sub-element <code class="sgmltag-element">master</code> to specify the exact relationship of the companion to its master controller. A companion controller is on the same bus as its master, so the companion index value should be equal.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-controllers2"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><controller</span><span class="perl_Others"> type=</span><span class="perl_String">'usb'</span><span class="perl_Others"> index=</span><span class="perl_String">'0'</span><span class="perl_Others"> model=</span><span class="perl_String">'ich9-ehci1'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'pci'</span><span class="perl_Others"> domain=</span><span class="perl_String">'0'</span><span class="perl_Others"> bus=</span><span class="perl_String">'0'</span><span class="perl_Others"> slot=</span><span class="perl_String">'4'</span><span class="perl_Others"> function=</span><span class="perl_String">'7'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></controller></span>
+ <span class="perl_Keyword"><controller</span><span class="perl_Others"> type=</span><span class="perl_String">'usb'</span><span class="perl_Others"> index=</span><span class="perl_String">'0'</span><span class="perl_Others"> model=</span><span class="perl_String">'ich9-uhci1'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><master</span><span class="perl_Others"> startport=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'pci'</span><span class="perl_Others"> domain=</span><span class="perl_String">'0'</span><span class="perl_Others"> bus=</span><span class="perl_String">'0'</span><span class="perl_Others"> slot=</span><span class="perl_String">'4'</span><span class="perl_Others"> function=</span><span class="perl_String">'0'</span><span class="perl_Others"> multifunction=</span><span class="perl_String">'on'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></controller></span>
+ ...
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.27. Devices - controllers - USB</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-device-addresses.html"><strong>Prev</strong>J.16.3. Device addresses</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="sub-section-libvirt-dom-xml-devices-device-leases.html"><strong>Next</strong>J.16.5. Device leases</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-device-addresses.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-device-addresses.html
new file mode 100644
index 0000000..02a1818
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-device-addresses.html
@@ -0,0 +1,58 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.3. Device addresses</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-filesystems.html" title="J.16.2. Filesystems" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-controllers.html" title="J.16.4. Controllers" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xm
l-devices-filesystems.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-controllers.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-device-addresses"><div class="titlepage"><div><div><h3 class="title">J.16.3. Device addresses</h3></div></div></div><div class="para">
+ Many devices have an optional <code class="sgmltag-starttag"><address></code> sub-element to describe where the device placed on the virtual bus is presented to the guest. If an address (or any optional attribute within an address) is omitted on input, libvirt will generate an appropriate address; but an explicit address is required if more control over layout is required. See below for device examples including an address element.
+ </div><div class="para">
+ Every address has a mandatory attribute <em class="parameter"><code>type</code></em> that describes which bus the device is on. The choice of which address to use for a given device is constrained in part by the device and the architecture of the guest. For example, a disk device uses <code class="sgmltag-attribute">type='disk'</code>, while a console device would use <code class="sgmltag-attribute">type='pci'</code> on i686 or x86_64 guests, or <code class="sgmltag-attribute">type='spapr-vio'</code> on PowerPC64 pseries guests. Each address <code class="sgmltag-starttag"><type></code> has additional optional attributes that control where on the bus the device will be placed. The additional attributes are as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type='pci'</code> - PCI addresses have the following additional attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">domain</code> (a 2-byte hex integer, not currently used by qemu)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">bus</code> (a hex value between 0 and 0xff, inclusive)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">slot</code> (a hex value between 0x0 and 0x1f, inclusive)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">function</code> (a value between 0 and 7, inclusive)
+ </div></li><li class="listitem"><div class="para">
+ Also available is the <code class="sgmltag-attribute">multifunction</code> attribute, which controls turning on the multifunction bit for a particular slot/function in the PCI control register. This multifunction attribute defaults to <code class="sgmltag-attvalue">'off'</code>, but should be set to <code class="sgmltag-attvalue">'on'</code> for function 0 of a slot that will have multiple functions used.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type='drive</code> - drive addresses have the following additional attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">controller</code>- (a 2-digit controller number)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">bus</code> - (a 2-digit bus number)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">target</code> - (a 2-digit bus number)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">unit</code> - (a 2-digit unit number on the bus)
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type='virtio-serial'</code> - Each virtio-serial address has the following additional attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">controller</code> - (a 2-digit controller number)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">bus</code> - (a 2-digit bus number)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">slot</code> - (a 2-digit slot within the bus)
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type='ccid'</code> - A CCID address, used for smart-cards, has the following additional attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">bus</code> - (a 2-digit bus number)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">slot</code> attribute - (a 2-digit slot within the bus)
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type='usb'</code> - USB addresses have the following additional attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">bus</code> - (a hex value between 0 and 0xfff, inclusive)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">port</code> - (a dotted notation of up to four octets, such as 1.2 or 2.1.3.1)
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type='spapr-vio</code> - On PowerPC pseries guests, devices can be assigned to the SPAPR-VIO bus. It has a flat 64-bit address space; by convention, devices are generally assigned at a non-zero multiple of 0x1000, but other addresses are valid and permitted by libvirt. The additional attribute: reg (the hex value address of the starting register) can be assigned to this attribute.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-filesystems.html"><strong>Prev</strong>J.16.2. Filesystems</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="sub-section-libvirt-dom-xml-devices-controllers.html"><strong>Next</strong>J.16.4. Controllers</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-device-leases.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-device-leases.html
new file mode 100644
index 0000000..2ea1bde
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-device-leases.html
@@ -0,0 +1,33 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.5. Device leases</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-controllers.html" title="J.16.4. Controllers" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-host-device-assignment.html" title="J.16.6. Host device assignment" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-
section-libvirt-dom-xml-devices-controllers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-host-device-assignment.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-device-leases"><div class="titlepage"><div><div><h3 class="title">J.16.5. Device leases</h3></div></div></div><div class="para">
+ When using a lock manager, you have the option to record device leases against a guest virtual machine. The lock manager will ensure that the guest virtual machine doesn't start unless the leases can be acquired. When configured using conventional management tools, the following section of the domain xml is effected:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-device-leases"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ ...
+ <span class="perl_Keyword"><lease></span>
+ <span class="perl_Keyword"><lockspace></span>somearea<span class="perl_Keyword"></lockspace></span>
+ <span class="perl_Keyword"><key></span>somekey<span class="perl_Keyword"></key></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> path=</span><span class="perl_String">'/some/lease/path'</span><span class="perl_Others"> offset=</span><span class="perl_String">'1024'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></lease></span>
+ ...
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.28. Devices - device leases</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-element">lease</code> section can have the following arguements:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-element">lockspace</code> - an arbitrary string that identifies lockspace within which the key is held. Lock managers may impose extra restrictions on the format, or length of the lockspace name.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-element">key</code> - an arbitrary string, that uniquely identies the lease to be acquired. Lock managers may impose extra restrictions on the format, or length of the key.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-element">target</code> - the fully qualified path of the file associated with the lockspace. The offset specifies where the lease is stored within the file. If the lock manager does not require a offset, set this value to <code class="sgmltag-element">0</code>.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-controllers.html"><strong>Prev</strong>J.16.4. Controllers</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="sub-section-libvirt-dom-xml-devices-host-device-assignment.html"><strong>Next</strong>J.16.6. Host device assignment</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-filesystems.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-filesystems.html
new file mode 100644
index 0000000..9a0489c
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-filesystems.html
@@ -0,0 +1,62 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.2. Filesystems</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-device-addresses.html" title="J.16.3. Device addresses" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-devices.html"><stron
g>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-device-addresses.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-filesystems"><div class="titlepage"><div><div><h3 class="title">J.16.2. Filesystems</h3></div></div></div><div class="para">
+ A filesystems directory on the host that can be accessed directly from the guest
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-filesystems"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><filesystem</span><span class="perl_Others"> type=</span><span class="perl_String">'template'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> name=</span><span class="perl_String">'my-vm-template'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dir=</span><span class="perl_String">'/'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></filesystem></span>
+ <span class="perl_Keyword"><filesystem</span><span class="perl_Others"> type=</span><span class="perl_String">'mount'</span><span class="perl_Others"> accessmode=</span><span class="perl_String">'passthrough'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> type=</span><span class="perl_String">'path'</span><span class="perl_Others"> wrpolicy=</span><span class="perl_String">'immediate'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> dir=</span><span class="perl_String">'/export/to/guest'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dir=</span><span class="perl_String">'/import/from/host'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><readonly/></span>
+ <span class="perl_Keyword"></filesystem></span>
+ ...
+ <span class="perl_Keyword"></devices></span>
+ ...
+
+</pre></div><h6>Figure J.25. Devices - filesystems</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-attribute">filesystem</code> attribute has the following possible values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='mount'</code> - Specifies the host directory to mount in the guest. This is the default type if one is not specified. This mode also has an optional sub-element <code class="sgmltag-element">driver</code>, with an attribute <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='path'</code> or <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='handle'</code>. The driver block has an optional attribute <code class="sgmltag-attribute">wrpolicy</code> that further controls interaction with the host page cache; omitting the attribute reverts to the default setting, while specifying a value immediate means that a host writeback is immediately triggered for all pages touched during a guest file write operation
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='template'</code> - Specifies the OpenVZ filesystem template and is only used by OpenVZ driver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='file'</code> - Specifies that a host file will be treated as an image and mounted in the guest. This filesystem format will be autodetected and is only used by LXC driver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='block'</code> - Specifies the host block device to mount in the guest. The filesystem format will be autodetected and is only used by LXC driver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='ram'</code> - Specifies that an in-memory filesystem, using memory from the host OS will be used. The source element has a single attribute <code class="sgmltag-attribute">usage</code> which gives the memory usage limit in kibibytes and is only used by LXC driver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='bind'</code> - Specifies a directory inside the guest which will be bound to another directory inside the guest. This element is only used by LXC driver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">accessmode</code> which specifies the security mode for accessing the source. Currently this only works with type='mount' for the QEMU/KVM driver. The possible values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">passthrough</code> - Specifies that the source is accessed with the User's permission settings that are set from inside the virtual guest machine. This is the default accessmode if one is not specified.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">mapped</code> - Specifies that the source is accessed with the permission settings of the hypervisor.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">squash</code> - Similar to <code class="sgmltag-attvalue">'passthrough'</code>, the exception is that failure of privileged operations like <code class="sgmltag-attvalue">chown</code> are ignored. This makes a passthrough-like mode usable for people who run the hypervisor as non-root.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><source></code> - Specifies that the resource on the host that is being accessed in the guest virtual machine. The <code class="sgmltag-attribute">name</code> attribute must be used with <code class="sgmltag-starttag"><type='template'></code>, and the <code class="sgmltag-attribute">dir</code> attribute must be used with <code class="sgmltag-starttag"><type='mount'></code>. The <code class="sgmltag-attribute">usage</code> attribute is used with <code class="sgmltag-starttag"><type='ram'></code> to set the memory limit in KB.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-element">target</code> - Dictates where the source drivers can be accessed in the guest virtual machine. For most drivers this is an automatic mount point, but for QEMU-KVM this is merely an arbitrary string tag that is exported to the guest as a hint for where to mount.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">readonly</code> - Enables exporting the filesytem as a readonly mount for guest virtual machine, by default <code class="sgmltag-element">read-write</code> access is given.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">space_hard_limit</code> - Specifies the maximum space available to this guest's filesystem
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">space_soft_limit</code> - Specifies the maximum space available to this guest's filesystem. The container is permitted to exceed its soft limits for a grace period of time. Afterwards the hard limit is enforced.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-devices.html"><strong>Prev</strong>J.16. 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="sub-section-libvirt-dom-xml-devices-device-addresses.html"><strong>Next</strong>J.16.3. Device addresses</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-graphical-framebuffers.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-graphical-framebuffers.html
new file mode 100644
index 0000000..156f036
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-graphical-framebuffers.html
@@ -0,0 +1,95 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.12. Graphical framebuffers</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-hub-devices.html" title="J.16.11. Hub devices" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-video.html" title="J.16.13. Video devices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-
devices-hub-devices.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-video.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-graphical-framebuffers"><div class="titlepage"><div><div><h3 class="title">J.16.12. Graphical framebuffers</h3></div></div></div><div class="para">
+ A graphics device allows for graphical interaction with the guest OS. A guest will typically have either a framebuffer or a text console configured to allow interaction with the admin.
+ </div><div class="para">
+ To specify the graphical framebuffer devices configuration settings, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig--xml-devices-graphical-framebuffers"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'sdl'</span><span class="perl_Others"> display=</span><span class="perl_String">':0.0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'vnc'</span><span class="perl_Others"> port=</span><span class="perl_String">'5904'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><listen</span><span class="perl_Others"> type=</span><span class="perl_String">'address'</span><span class="perl_Others"> address=</span><span class="perl_String">'1.2.3.4'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></graphics></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'rdp'</span><span class="perl_Others"> autoport=</span><span class="perl_String">'yes'</span><span class="perl_Others"> multiUser=</span><span class="perl_String">'yes'</span> <span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'desktop'</span><span class="perl_Others"> fullscreen=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'spice'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><listen</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Others"> network=</span><span class="perl_String">'rednet'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></graphics></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.56. Graphical framebuffers</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-element">graphics</code> element has a mandatory <code class="sgmltag-attribute">type</code> attribute which takes the value <code class="sgmltag-element">sdl</code>, <code class="sgmltag-element">vnc</code>, <code class="sgmltag-element">rdp</code> or <code class="sgmltag-element">desktop</code> as explained below:
+ </div><div class="table" id="table--libvirt-dom-xml-devices-Network-interfaces-setting-graphical-framebuffer-sgmltags"><h6>Table J.20. Graphical framebuffer elements</h6><div class="table-contents"><table summary="Graphical framebuffer elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-element">sdl</code>
+ </td><td class="">
+ This displays a window on the host desktop, it can take 3 optional arguments: a <code class="sgmltag-attribute">display</code> attribute for the display to use, an <code class="sgmltag-attribute">xauth</code> attribute for the authentication identifier, and an optional <code class="sgmltag-attribute">fullscreen</code> attribute accepting values <code class="sgmltag-element">yes</code> or <code class="sgmltag-element">no</code>
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">vnc</code>
+ </td><td class="">
+ Starts a VNC server. The <code class="sgmltag-attribute">port</code> attribute specifies the TCP port number (with <code class="sgmltag-element">-1</code> as legacy syntax indicating that it should be auto-allocated). The <code class="sgmltag-attribute">autoport</code> attribute is the new preferred syntax for indicating autoallocation of the TCP port to use. The <code class="sgmltag-attribute">listen</code> attribute is an IP address for the server to listen on. The <code class="sgmltag-attribute">passwd</code> attribute provides a VNC password in clear text. The <code class="sgmltag-attribute">keymap</code> attribute specifies the keymap to use. It is possible to set a limit on the validity of the password be giving an <code class="sgmltag-element">timestamp passwdValidTo='2010-04-09T15:51:00'</code> assumed to be in UTC. The <code class="sgmltag-attribute">connected</code> attribute allows control of connected client during password changes. VNC accepts <code clas
s="sgmltag-element">keep</code> value only and note that it may not be supported by all hypervisors. Rather than using listen/port, QEMU supports a socket attribute for listening on a unix domain socket path.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">spice</code>
+ </td><td class="">
+ Starts a SPICE server. The <code class="sgmltag-attribute">port</code> attribute specifies the TCP port number (with -1 as legacy syntax indicating that it should be auto-allocated), while <code class="sgmltag-element">tlsPort</code> gives an alternative secure port number. The <code class="sgmltag-attribute">autoport</code> attribute is the new preferred syntax for indicating autoallocation of both port numbers. The <code class="sgmltag-attribute">listen</code> attribute is an IP address for the server to listen on. The <code class="sgmltag-attribute">passwd</code> attribute provides a SPICE password in clear text. The <code class="sgmltag-attribute">keymap</code> attribute specifies the keymap to use. It is possible to set a limit on the validity of the password be giving an <code class="sgmltag-attribute">timestamp passwdValidTo='2010-04-09T15:51:00'</code> assumed to be in UTC. The <code class="sgmltag-attribute">connected</code> attribute allows control of conne
cted client during password changes. SPICE accepts keep to keep client connected, disconnect to disconnect client and fail to fail changing password. Note it is not be supported by all hypervisors. The <code class="sgmltag-attribute">defaultMode</code> attribute sets the default channel security policy, valid values are <code class="sgmltag-element">secure</code>, <code class="sgmltag-element">insecure</code> and the default <code class="sgmltag-element">any</code> (which is <code class="sgmltag-element">secure</code> if possible, but falls back to <code class="sgmltag-element">insecure</code> rather than erroring out if no secure path is available).
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ When SPICE has both a normal and TLS secured TCP port configured, it may be desirable to restrict what channels can be run on each port. This is achieved by adding one or more <code class="sgmltag-element">channel</code> elements inside the main <code class="sgmltag-element">graphics</code> element. Valid channel names include <code class="sgmltag-element">main</code>, <code class="sgmltag-element">display</code>, <code class="sgmltag-element">inputs</code>, <code class="sgmltag-element">cursor</code>, <code class="sgmltag-element">playback</code>, <code class="sgmltag-element">record</code>; <code class="sgmltag-element">smartcard</code>; and <code class="sgmltag-element">usbredir</code>.
+ </div><div class="para">
+ To specify the SPICE configuration settings, use a mangement tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-:devices-Network-interfaces-setting-graphical-framebuffer-sgmltags-spice-cfg"><div class="figure-contents"><pre class="programlisting">
+
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'spice'</span><span class="perl_Others"> port=</span><span class="perl_String">'-1'</span><span class="perl_Others"> tlsPort=</span><span class="perl_String">'-1'</span><span class="perl_Others"> autoport=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> name=</span><span class="perl_String">'main'</span><span class="perl_Others"> mode=</span><span class="perl_String">'secure'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> name=</span><span class="perl_String">'record'</span><span class="perl_Others"> mode=</span><span class="perl_String">'insecure'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><image</span><span class="perl_Others"> compression=</span><span class="perl_String">'auto_glz'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><streaming</span><span class="perl_Others"> mode=</span><span class="perl_String">'filter'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><clipboard</span><span class="perl_Others"> copypaste=</span><span class="perl_String">'no'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><mouse</span><span class="perl_Others"> mode=</span><span class="perl_String">'client'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></graphics></span>
+</pre></div><h6>Figure J.57. SPICE configuration</h6></div><br class="figure-break" /><div class="para">
+ SPICE supports variable compression settings for audio, images and streaming. These settings are accessible via the compression attribute in all following elements: <code class="sgmltag-element">image</code> to set image compression (accepts auto_glz, auto_lz, quic, glz, lz, off), <code class="sgmltag-element">jpeg</code> for JPEG compression for images over wan (accepts auto, never, always), <code class="sgmltag-element">zlib</code> for configuring wan image compression (accepts auto, never, always) and <code class="sgmltag-element">playback</code> for enabling audio stream compression (accepts on or off).
+ </div><div class="para">
+ Streaming mode is set by the <code class="sgmltag-element">streaming</code> element, settings its <code class="sgmltag-attribute">mode</code> attribute to one of <code class="sgmltag-element">filter</code>, <code class="sgmltag-element">all</code> or <code class="sgmltag-element">off</code>.
+ </div><div class="para">
+ In addition, Copy and paste functionality (via the SPICE agent) is set by the <code class="sgmltag-element">clipboard</code> element. It is enabled by default, and can be disabled by setting the <code class="sgmltag-attribute">copypaste</code> property to <code class="sgmltag-element">no</code>.
+ </div><div class="para">
+ Mouse mode is set by the <code class="sgmltag-element">mouse</code> element, setting its <code class="sgmltag-attribute">mode</code> attribute to one of <code class="sgmltag-element">server</code> or <code class="sgmltag-element">client</code>. If no mode is specified, the qemu default will be used (<code class="sgmltag-element">client</code> mode).
+ </div><div class="para">
+ Additional elements include:
+ </div><div class="table" id="table-libvirt-dom-xml-devices-Network-interfaces-setting-graphical-framebuffer-options2"><h6>Table J.21. Additional graphical framebuffer elements</h6><div class="table-contents"><table summary="Additional graphical framebuffer elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-element">rdp</code>
+ </td><td class="">
+ Starts a RDP server. The port attribute specifies the TCP port number (with -1 as legacy syntax indicating that it should be auto-allocated). The autoport attribute is the new preferred syntax for indicating autoallocation of the TCP port to use. The replaceUser attribute is a boolean deciding whether multiple simultaneous connections to the VM are permitted. The multiUser whether the existing connection must be dropped and a new connection must be established by the VRDP server, when a new client connects in single connection mode.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">desktop</code>
+ </td><td class="">
+ This value is reserved for VirtualBox domains for the moment. It displays a window on the host desktop, similarly to "sdl", but uses the VirtualBox viewer. Just like "sdl", it accepts the optional attributes display and fullscreen.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">listen</code>
+ </td><td class="">
+ Rather than putting the address information used to set up the listening socket for graphics types vnc and spice in the <code class="sgmltag-element">graphics</code>, the <code class="sgmltag-element">listen</code> attribute, a separate subelement of <code class="sgmltag-element">graphics</code>, called <code class="sgmltag-element">listen</code> can be specified (see the examples above). <code class="sgmltag-element">listen</code> accepts the following attributes:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code> - Set to either address or network. This tells whether this listen element is specifying the address to be used directly, or by naming a network (which will then be used to determine an appropriate address for listening).
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">address</code> - this attribute will contain either an IP address or hostname (which will be resolved to an IP address via a DNS query) to listen on. In the "live" XML of a running domain, this attribute will be set to the IP address used for listening, even if <code class="sgmltag-attribute">type='network'</code>.
+ </div></li><li class="listitem"><div class="para">
+ network - if <code class="sgmltag-attribute">type='network'</code>, the network attribute will contain the name of a network in libvirt's list of configured networks. The named network configuration will be examined to determine an appropriate listen address. For example, if the network has an IPv4 address in its configuration (e.g. if it has a forward type of route, nat, or no forward type (isolated)), the first IPv4 address listed in the network's configuration will be used. If the network is describing a host bridge, the first IPv4 address associated with that bridge device will be used, and if the network is describing one of the 'direct' (macvtap) modes, the first IPv4 address of the first forward dev will be used.
+ </div></li></ul></div>
+
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-hub-devices.html"><strong>Prev</strong>J.16.11. Hub 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="sub-section-libvirt-dom-xml-devices-video.html"><strong>Next</strong>J.16.13. Video devices</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-guest-interface.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-guest-interface.html
new file mode 100644
index 0000000..5b5331b
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-guest-interface.html
@@ -0,0 +1,82 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.15. Guest interfaces</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-consoles.html" title="J.16.14. Consoles, serial, parallel, and channel devices" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-channel.html" title="J.16.16. Channel" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href=
"sub-section-libvirt-dom-xml-devices-consoles.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-channel.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-guest-interface"><div class="titlepage"><div><div><h3 class="title">J.16.15. Guest interfaces</h3></div></div></div><div class="para">
+ A character device presents itself to the guest as one of the following types.
+ </div><div class="para">
+ To set the parallel port, use a management tool to make the following change to the domain XML
+ </div><div class="figure" id="fig--devices-guest-interface"><div class="figure-contents"><pre class="programlisting">
+
+...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><parallel</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/2'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></parallel></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.60. Guest interface Parallel Port</h6></div><br class="figure-break" /><div class="para">
+ <code class="sgmltag-starttag"><target></code> can have a <code class="sgmltag-attribute">port</code> attribute, which specifies the port number. Ports are numbered starting from 0. There are usually 0, 1 or 2 parallel ports.
+ </div><div class="para">
+ To set the serial port use a management tool to make the following change to the domain XML:
+ </div><div class="figure" id="fig-devices-guest-interface-serial-port"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><serial</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/3'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></serial></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.61. Guest Interface Serial port</h6></div><br class="figure-break" /><div class="para">
+ <code class="sgmltag-starttag"><target></code> can have a <code class="sgmltag-attribute">port</code> attribute, which specifies the port number. Ports are numbered starting from 0. There are usually 0, 1 or 2 serial ports. There is also an optional <code class="sgmltag-attribute">type</code> attribute, which has two choices for its value, one is <code class="sgmltag-attvalue">isa-serial</code>, the other is <code class="sgmltag-attvalue">usb-serial</code>. If <code class="sgmltag-attribute">type</code> is missing, <code class="sgmltag-attvalue">isa-serial</code> will be used by default. For usb-serial an optional sub-element <code class="sgmltag-starttag"><address></code> with <code class="sgmltag-attribute">type='usb'</code> can tie the device to a particular controller, documented above.
+ </div><div class="para">
+ The <code class="sgmltag-starttag"><console></code> element is used to represent interactive consoles. Depending on the type of guest in use, the consoles might be paravirtualized devices, or they might be a clone of a serial device, according to the following rules:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If no <code class="sgmltag-attribute">targetType</code> attribute is set, then the default device <code class="sgmltag-attribute">type</code> is according to the hypervisor's rules. The default <code class="sgmltag-attribute">type</code> will be added when re-querying the XML fed into libvirt. For fully virtualized guests, the default device type will usually be a serial port.
+ </div></li><li class="listitem"><div class="para">
+ If the <code class="sgmltag-attribute">targetType</code> attribute is <code class="sgmltag-element">serial</code>, and if no <code class="sgmltag-starttag"><serial></code> element exists, the console element will be copied to the <code class="sgmltag-starttag"><serial></code> element. If a <code class="sgmltag-starttag"><serial></code> element does already exist, the console element will be ignored.
+ </div></li><li class="listitem"><div class="para">
+ If the <code class="sgmltag-attribute">targetType</code> attribute is not <code class="sgmltag-element">serial</code>, it will be treated normally.
+ </div></li><li class="listitem"><div class="para">
+ Only the first <code class="sgmltag-starttag"><console></code> element may use a <code class="sgmltag-attribute">targetType</code> of <code class="sgmltag-attvalue">serial</code>. Secondary consoles must all be paravirtualized.
+ </div></li><li class="listitem"><div class="para">
+ On s390, the console element may use a targetType of sclp or sclplm (line mode). SCLP is the native console type for s390. There's no controller associated to SCLP consoles.
+ </div></li></ul></div><div class="para">
+ In the example below, a virtio console device is exposed in the guest as /dev/hvc[0-7] (for more information, see http://fedoraproject.org/wiki/Features/VirtioSerial):
+ </div><div class="figure" id="fig-devices-guest-interface-serial-port-virtio-console-device"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><console</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/4'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></console></span>
+
+ <span class="perl_Comment"><!-- KVM virtio console --></span>
+ <span class="perl_Keyword"><console</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/5'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio'</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></console></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Comment"><!-- KVM s390 sclp console --></span>
+ <span class="perl_Keyword"><console</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'sclp'</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></console></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.62. Guest Interface - virtio console device</h6></div><br class="figure-break" /><div class="para">
+ If the console is presented as a serial port, the <code class="sgmltag-starttag"><target></code> element has the same attributes as for a serial port. There is usually only one console.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-consoles.html"><strong>Prev</strong>J.16.14. Consoles, serial, parallel, and channel ...</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="sub-section-libvirt-dom-xml-devices-channel.html"><strong>Next</strong>J.16.16. Channel</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-host-device-assignment.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-host-device-assignment.html
new file mode 100644
index 0000000..780e8a9
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-host-device-assignment.html
@@ -0,0 +1,78 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.6. Host device assignment</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-device-leases.html" title="J.16.5. Device leases" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-host-device-assignment-block-character-devices.html" title="J.16.6.2. Block / character devices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="
previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-device-leases.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-host-device-assignment-block-character-devices.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-host-device-assignment"><div class="titlepage"><div><div><h3 class="title">J.16.6. Host device assignment</h3></div></div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-host-device-assignment-usb-pci-devices"><div class="titlepage"><div><div><h4 class="title">J.16.6.1. USB / PCI devices</h4></div></div></div><div class="para">
+ The host's USB and PCI devices can be passed through to the guest using the <code class="sgmltag-element">hostdev</code> element, by modifying the host using a management tool the following section of the domain xml file is configured:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-host-device-assignment"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><hostdev</span><span class="perl_Others"> mode=</span><span class="perl_String">'subsystem'</span><span class="perl_Others"> type=</span><span class="perl_String">'usb'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> startupPolicy=</span><span class="perl_String">'optional'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><vendor</span><span class="perl_Others"> id=</span><span class="perl_String">'0x1234'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><product</span><span class="perl_Others"> id=</span><span class="perl_String">'0xbeef'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></source></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'2'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></hostdev></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.29. Devices - host device assignment</h6></div><br class="figure-break" /><div class="para">
+ Alternatively the following can also be done:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-host-device-assignment2"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><hostdev</span><span class="perl_Others"> mode=</span><span class="perl_String">'subsystem'</span><span class="perl_Others"> type=</span><span class="perl_String">'pci'</span><span class="perl_Others"> managed=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> bus=</span><span class="perl_String">'0x06'</span><span class="perl_Others"> slot=</span><span class="perl_String">'0x02'</span><span class="perl_Others"> function=</span><span class="perl_String">'0x0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></source></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><rom</span><span class="perl_Others"> bar=</span><span class="perl_String">'on'</span><span class="perl_Others"> file=</span><span class="perl_String">'/etc/fake/boot.bin'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></hostdev></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.30. Devices - host device assignment alternative</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-pci-managed-devices"><h6>Table J.13. Host device assignment elements</h6><div class="table-contents"><table summary="Host device assignment elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-element">hostdev</code>
+ </td><td class="">
+ This is the main container for describing host devices. For USB device passthrough <code class="sgmltag-element">mode</code> is always <code class="sgmltag-element">subsystem</code> and <code class="sgmltag-element">type</code> is <code class="sgmltag-element">usb</code> for a USB device and <code class="sgmltag-element">pci</code> for a PCI device. When <code class="sgmltag-element">managed</code> is <code class="sgmltag-element">yes</code> for a PCI device, it is detached from the host before being passed on to the guest, and reattached to the host after the guest exits. If <code class="sgmltag-element">managed</code> is omitted or <code class="sgmltag-element">no</code> for PCI and for USB devices, the user is responsible to use the arguement <code class="sgmltag-element">virNodeDeviceDettach</code> (or <code class="command">virsh nodedev-dettach</code>) before starting the guest or hot-plugging the device, and <code class="sgmltag-element">virNodeDeviceReAttach<
/code> (or <code class="command">virsh nodedev-reattach</code>) after hot-unplug or stopping the guest.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">source</code>
+ </td><td class="">
+ Describes the device as seen from the host. The USB device can either be addressed by vendor / product id using the <code class="sgmltag-element">vendor</code> and <code class="sgmltag-element">product</code> elements or by the device's address on the hosts using the <code class="sgmltag-element">address</code> element. PCI devices on the other hand can only be described by their address. Note that the source element of USB devices may contain a <code class="sgmltag-attribute">startupPolicy</code> attribute which can be used to define a rule for what to do if the specified host USB device is not found. The attribute accepts the following values:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-element">mandatory</code> - fails if missing for any reason (the default)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-element">requisite</code> - fails if missing on boot up, drops if missing on migrate/restore/revert
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-element">optional</code> - drops if missing at any start attempt
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">vendor, product</code>
+ </td><td class="">
+ These elements each have an <code class="sgmltag-attribute">id</code> attribute that specifies the USB vendor and product id. The IDs can be given in decimal, hexadecimal (starting with 0x) or octal (starting with 0) form.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">boot</code>
+ </td><td class="">
+ Specifies that the device is bootable. The attribute's order determines the order in which devices will be tried during boot sequence. The per-device boot elements cannot be used together with general boot elements in BIOS bootloader section.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">rom</code>
+ </td><td class="">
+ Used to change how a PCI device's ROM is presented to the guest. The optional <code class="sgmltag-attribute">bar</code> attribute can be set to <code class="sgmltag-element">on</code> or <code class="sgmltag-element">off</code>, and determines whether or not the device's ROM will be visible in the guest's memory map. (In PCI documentation, the <code class="sgmltag-element">rombar</code> setting controls the presence of the Base Address Register for the ROM). If no rom bar is specified, the default setting will be used. The optional <code class="sgmltag-attribute">file</code> attribute is used to point to a binary file to be presented to the guest as the device's ROM BIOS. This can be useful, for example, to provide a PXE boot ROM for a virtual function of an sr-iov capable ethernet device (which has no boot ROMs for the VFs).
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">address</code>
+ </td><td class="">
+ Also has a <code class="sgmltag-attribute">bus</code> and <code class="sgmltag-attribute">device</code> attribute to specify the USB bus and device number the device appears at on the host. The values of these attributes can be given in decimal, hexadecimal (starting with 0x) or octal (starting with 0) form. For PCI devices the element carries 3 attributes allowing to designate the device as can be found with <code class="command">lspci</code> or with <code class="command">virsh nodedev-list</code>
+ </td></tr></tbody></table></div></div><br class="table-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-device-leases.html"><strong>Prev</strong>J.16.5. Device leases</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="sub-sub-section-libvirt-dom-xml-devices-host-device-assignment-block-character-devices.html"><strong>Next</strong>J.16.6.2. Block / character devices </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-host-interface.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-host-interface.html
new file mode 100644
index 0000000..0a0e7fd
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-host-interface.html
@@ -0,0 +1,193 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.17. Host interface</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-channel.html" title="J.16.16. Channel" /><link rel="next" href="section-libvirt-dom-xml-sound-devices.html" title="J.17. Sound devices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-channel
.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="section-libvirt-dom-xml-sound-devices.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-host-interface"><div class="titlepage"><div><div><h3 class="title">J.16.17. Host interface</h3></div></div></div><div class="para">
+ A character device presents itself to the host as one of the following types:
+ </div><div class="table" id="table--libvirt-dom-xml-devices-host-interfaces-character-device-options"><h6>Table J.23. Character device elements</h6><div class="table-contents"><table summary="Character device elements" border="1"><colgroup><col width="33%" /><col width="33%" /><col width="33%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th><th class="">
+ XML snippet
+ </th></tr></thead><tbody><tr><td class="">
+ Domain logfile
+ </td><td class="">
+ Disables all input on the character device, and sends output into the virtual machine's logfile
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><console type='stdio'></code>
+ <code class="sgmltag-starttag"><target port='1'/></code>
+ <code class="sgmltag-endtag"></console></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ Device logfile
+ </td><td class="">
+ A file is opened and all data sent to the character device is written to the file.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="file"></code>
+ <code class="sgmltag-starttag"><source path="/var/log/vm/vm-serial.log"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ Virtual console
+ </td><td class="">
+ Connects the character device to the graphical framebuffer in a virtual console. This is typically accessed via a special hotkey sequence such as "ctrl+alt+3"
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type='vc'></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ Null device
+ </td><td class="">
+ Connects the character device to the void. No data is ever provided to the input. All data written is discarded.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type='null'></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ Pseudo TTY
+ </td><td class="">
+ A Pseudo TTY is allocated using <code class="filename">/dev/ptmx</code>. A suitable client such as <code class="command">virsh console</code> can connect to interact with the serial port locally.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="pty"></code>
+ <code class="sgmltag-starttag"><source path="/dev/pts/3"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ NB Special case
+ </td><td class="">
+ NB special case if <code class="sgmltag-starttag"><console type='pty'></code>, then the TTY path is also duplicated as an attribute <code class="sgmltag-attribute">tty='/dev/pts/3'</code> on the top level <code class="sgmltag-starttag"><console></code> tag. This provides compat with existing syntax for <code class="sgmltag-starttag"><console></code> tags.
+ </td><td class="auto-generated"> </td></tr><tr><td class="">
+ Host device proxy
+ </td><td class="">
+ The character device is passed through to the underlying physical character device. The device types must match, eg the emulated serial port should only be connected to a host serial port - don't connect a serial port to a parallel port.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="dev"></code>
+ <code class="sgmltag-starttag"><source path="/dev/ttyS0"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ Named pipe
+ </td><td class="">
+ The character device writes output to a named pipe. See pipe(7) MAN page for more info.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="pipe"></code>
+ <code class="sgmltag-starttag"><source path="/tmp/mypipe"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ TCP client/server
+ </td><td class="">
+ The character device acts as a TCP client connecting to a remote server.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="tcp"></code>
+ <code class="sgmltag-starttag"><source mode="connect" host="0.0.0.0" service="2445"/></code>
+ <code class="sgmltag-starttag"><protocol type="raw"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ <div class="para">
+ Or as a TCP server waiting for a client connection.
+ </div>
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="tcp"></code>
+ <code class="sgmltag-starttag"><source mode="bind" host="127.0.0.1" service="2445"/></code>
+ <code class="sgmltag-starttag"><protocol type="raw"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ <div class="para">
+ Alternatively you can use telnet instead of raw TCP. In addition, you can also use telnets (secure telnet) and tls.
+ </div>
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="tcp"></code>
+ <code class="sgmltag-starttag"><source mode="connect" host="0.0.0.0" service="2445"/></code>
+ <code class="sgmltag-starttag"><protocol type="telnet"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-starttag"><serial type="tcp"></code>
+ <code class="sgmltag-starttag"><source mode="bind" host="127.0.0.1" service="2445"/></code>
+ <code class="sgmltag-starttag"><protocol type="telnet"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+
+ </td></tr><tr><td class="">
+ UDP network console
+ </td><td class="">
+ The character device acts as a UDP netconsole service, sending and receiving packets. This is a lossy service.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="udp"></code>
+ <code class="sgmltag-starttag"><source mode="bind" host="0.0.0.0" service="2445"/></code>
+ <code class="sgmltag-starttag"><source mode="connect" host="0.0.0.0" service="2445"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ UNIX domain socket client/server
+ </td><td class="">
+ The character device acts as a UNIX domain socket server, accepting connections from local clients.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="unix"></code>
+ <code class="sgmltag-starttag"><source mode="bind" path="/tmp/foo"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-channel.html"><strong>Prev</strong>J.16.16. Channel</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="section-libvirt-dom-xml-sound-devices.html"><strong>Next</strong>J.17. Sound devices</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-hub-devices.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-hub-devices.html
new file mode 100644
index 0000000..7011c3d
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-hub-devices.html
@@ -0,0 +1,23 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.11. Hub devices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-input-devices.html" title="J.16.10. Input devices" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-graphical-framebuffers.html" title="J.16.12. Graphical framebuffers" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href
="sub-section-libvirt-dom-xml-devices-input-devices.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-graphical-framebuffers.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-hub-devices"><div class="titlepage"><div><div><h3 class="title">J.16.11. Hub devices</h3></div></div></div><div class="para">
+ A hub is a device that expands a single port into several so that there are more ports available to connect devices to a host system.
+ </div><div class="para">
+ To specify the hub devices configuration settings, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-xml-devices-hub-devices"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><hub</span><span class="perl_Others"> type=</span><span class="perl_String">'usb'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.55. Hub devices</h6></div><br class="figure-break" /><div class="para">
+ The hub element has one mandatory attribute, the type whose value can only be <code class="sgmltag-element">usb</code>. The hub element has an optional sub-element <code class="sgmltag-element">address</code> with <code class="sgmltag-attribute">type='usb'</code>which can tie the device to a particular controller.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-input-devices.html"><strong>Prev</strong>J.16.10. Input 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="sub-section-libvirt-dom-xml-devices-graphical-framebuffers.html"><strong>Next</strong>J.16.12. Graphical framebuffers</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-input-devices.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-input-devices.html
new file mode 100644
index 0000000..5041dc3
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-input-devices.html
@@ -0,0 +1,26 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.10. Input devices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-modifying-virtual-link-state.html" title="J.16.9.15. Modifying virtual link state" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-hub-devices.html" title="J.16.11. Hub devices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a acce
sskey="p" href="sub-sub-section-libvirt-dom-xml-devices-modifying-virtual-link-state.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-hub-devices.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-input-devices"><div class="titlepage"><div><div><h3 class="title">J.16.10. Input devices</h3></div></div></div><div class="para">
+ Input devices allow interaction with the graphical framebuffer in the guest virtual machine. When enabling the framebuffer, an input device is automatically provided. It may be possible to add additional devices explicitly, for example, to provide a graphics tablet for absolute cursor movement.
+ </div><div class="para">
+ To specify the input devices configuration settings, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-input-devices"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><input</span><span class="perl_Others"> type=</span><span class="perl_String">'mouse'</span><span class="perl_Others"> bus=</span><span class="perl_String">'usb'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+
+</pre></div><h6>Figure J.54. Input devices</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-starttag"><input></code> element has one mandatory attribute: <code class="sgmltag-attribute">type</code> which can be set to: <code class="sgmltag-attvalue">mouse</code> or <code class="sgmltag-attvalue">tablet</code>. The latter provides absolute cursor movement, while the former uses relative movement. The optional <code class="sgmltag-attribute">bus</code> attribute can be used to refine the exact device type and can be set to: <code class="sgmltag-attvalue">xen</code> (paravirtualized), <code class="sgmltag-attvalue">ps2</code>, and <code class="sgmltag-attvalue">usb</code>.
+ </div><div class="para">
+ The input element has an optional sub-element <code class="sgmltag-starttag"><address></code>, which can tie the device to a particular PCI slot, as documented above.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-modifying-virtual-link-state.html"><strong>Prev</strong>J.16.9.15. Modifying virtual link state</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="sub-section-libvirt-dom-xml-devices-hub-devices.html"><strong>Next</strong>J.16.11. Hub devices</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-redirected-devices.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-redirected-devices.html
new file mode 100644
index 0000000..913e838
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-redirected-devices.html
@@ -0,0 +1,44 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.7. Redirected devices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-host-device-assignment-block-character-devices.html" title="J.16.6.2. Block / character devices" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-smartcard.html" title="J.16.8. Smartcard devices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="
previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-host-device-assignment-block-character-devices.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-smartcard.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-redirected-devices"><div class="titlepage"><div><div><h3 class="title">J.16.7. Redirected devices</h3></div></div></div><div class="para">
+ USB device redirection through a character device is supported by configuring it with managment tools that modify the following section of the domain xml:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-redirected-devices"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><redirdev</span><span class="perl_Others"> bus=</span><span class="perl_String">'usb'</span><span class="perl_Others"> type=</span><span class="perl_String">'tcp'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'connect'</span><span class="perl_Others"> host=</span><span class="perl_String">'localhost'</span><span class="perl_Others"> service=</span><span class="perl_String">'4000'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></redirdev></span>
+ <span class="perl_Keyword"><redirfilter></span>
+ <span class="perl_Keyword"><usbdev</span><span class="perl_Others"> class=</span><span class="perl_String">'0x08'</span><span class="perl_Others"> vendor=</span><span class="perl_String">'0x1234'</span><span class="perl_Others"> product=</span><span class="perl_String">'0xbeef'</span><span class="perl_Others"> version=</span><span class="perl_String">'2.00'</span><span class="perl_Others"> allow=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><usbdev</span><span class="perl_Others"> allow=</span><span class="perl_String">'no'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></redirfilter></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.34. Devices - redirected devices</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-host-device-assignement-redirected-devices"><h6>Table J.15. Redirected device elements</h6><div class="table-contents"><table summary="Redirected device elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-element">redirdev</code>
+ </td><td class="">
+ This is the main container for describing redirected devices. <code class="sgmltag-attribute">bus</code> must be <code class="sgmltag-element">usb</code> for a USB device. An additional attribute type is required, matching one of the supported serial device types, to describe the host side of the tunnel; <code class="sgmltag-attribute">type='tcp'</code> or <code class="sgmltag-attribute">type='spicevmc'</code> (which uses the usbredir channel of a SPICE graphics device) are typical. The redirdev element has an optional sub-element <code class="sgmltag-element">address</code> which can tie the device to a particular controller. Further sub-elements, such as <code class="sgmltag-element">source</code>, may be required according to the given <code class="sgmltag-attribute">type</code>, although a<code class="sgmltag-element">target</code> sub-element is not required (since the consumer of the character device is the hypervisor itself, rather than a device visible in the
guest).
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">boot</code>
+ </td><td class="">
+ Specifies that the device is bootable. The order attribute determines the order in which devices will be tried during boot sequence. The per-device boot elements cannot be used together with general boot elements in BIOS bootloader section.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">redirfilter</code>
+ </td><td class="">
+ This is used for creating the filter rule to filter out certain devices from redirection. It uses sub-element <code class="sgmltag-element">usbdev</code> to define each filter rule. The <code class="sgmltag-attribute">class</code> attribute is the USB Class code.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-host-device-assignment-block-character-devices.html"><strong>Prev</strong>J.16.6.2. Block / character 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="sub-section-libvirt-dom-xml-devices-smartcard.html"><strong>Next</strong>J.16.8. Smartcard devices</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-smartcard.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-smartcard.html
new file mode 100644
index 0000000..8ef604f
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-smartcard.html
@@ -0,0 +1,55 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.8. Smartcard devices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-redirected-devices.html" title="J.16.7. Redirected devices" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href
="sub-section-libvirt-dom-xml-devices-redirected-devices.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-smartcard"><div class="titlepage"><div><div><h3 class="title">J.16.8. Smartcard devices</h3></div></div></div><div class="para">
+ A virtual smartcard device can be supplied to the guest via the <code class="sgmltag-element">smartcard</code> element. A USB smartcard reader device on the host cannot be used on a guest with simple device passthrough, as it cannot be made available to both the host and guest and can possibly lock the host computer when it is removed from the guest. Therefore, some hypervisors provide a specialized virtual device that can present a smartcard interface to the guest, with several modes for describing how the credentials are obtained from the host or even a from a channel created to a third-party smartcard provider. To set these parameters use a managment tool that will edit the following section of the domain XML:
+ </div><div class="para">
+ USB device redirection through a character device is supported by configuring it with managment tools that modify the following section of the domain xml:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-smartcard"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><smartcard</span><span class="perl_Others"> mode=</span><span class="perl_String">'host'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><smartcard</span><span class="perl_Others"> mode=</span><span class="perl_String">'host-certificates'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><certificate></span>cert1<span class="perl_Keyword"></certificate></span>
+ <span class="perl_Keyword"><certificate></span>cert2<span class="perl_Keyword"></certificate></span>
+ <span class="perl_Keyword"><certificate></span>cert3<span class="perl_Keyword"></certificate></span>
+ <span class="perl_Keyword"><database></span>/etc/pki/nssdb/<span class="perl_Keyword"></database></span>
+ <span class="perl_Keyword"></smartcard></span>
+ <span class="perl_Keyword"><smartcard</span><span class="perl_Others"> mode=</span><span class="perl_String">'passthrough'</span><span class="perl_Others"> type=</span><span class="perl_String">'tcp'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'bind'</span><span class="perl_Others"> host=</span><span class="perl_String">'127.0.0.1'</span><span class="perl_Others"> service=</span><span class="perl_String">'2001'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><protocol</span><span class="perl_Others"> type=</span><span class="perl_String">'raw'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'ccid'</span><span class="perl_Others"> controller=</span><span class="perl_String">'0'</span><span class="perl_Others"> slot=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></smartcard></span>
+ <span class="perl_Keyword"><smartcard</span><span class="perl_Others"> mode=</span><span class="perl_String">'passthrough'</span><span class="perl_Others"> type=</span><span class="perl_String">'spicevmc'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.35. Devices - smartcard devices</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-element">smartcard</code> element has a mandatory attribute <code class="sgmltag-attribute">mode</code>. The following modes are supported; in each mode, the guest sees a device on its USB bus that behaves like a physical USB CCID (Chip/Smart Card Interface Device) card.
+ </div><div class="para">
+ The mode attributes are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-host-device-assignement-smartcard-modes"><h6>Table J.16. Smartcard mode elements</h6><div class="table-contents"><table summary="Smartcard mode elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-attribute">mode='host'</code>
+ </td><td class="">
+ In this mode, the hypervisor relays all requests from the guest into direct access to the host's smartcard via NSS. No other attributes or sub-elements are required. See below about the use of an optional <code class="sgmltag-element">address</code> sub-element.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">mode='host-certificates'</code>
+ </td><td class="">
+ This mode allows you to provide three NSS certificate names residing in a database on the host, rather than requiring a smartcard to be plugged into the host. These certificates can be generated via the command <code class="sgmltag-element">certutil -d /etc/pki/nssdb -x -t CT,CT,CT -S -s CN=cert1 -n cert1,</code> and the resulting three certificate names must be supplied as the content of each of three <code class="sgmltag-element">certificate</code> sub-elements. An additional sub-element <code class="sgmltag-element">database</code> can specify the absolute path to an alternate directory (matching the <code class="sgmltag-element">-d</code> flag of the <code class="command">certutil</code> command when creating the certificates); if not present, it defaults to <code class="filename">/etc/pki/nssdb</code>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">mode='passthrough'</code>
+ </td><td class="">
+ Using this mode allows you to tunnel all requests through a secondary character device to a third-party provider (which may in turn be talking to a smartcard or using three certificate files, rather than having the hypervisor directly communicate with the host. In this mode of operation, an additional attribute <code class="sgmltag-attribute">type</code> is required, matching one of the supported serial device types, to describe the host side of the tunnel; <code class="sgmltag-attribute">type='tcp'</code> or <code class="sgmltag-attribute">type='spicevmc'</code> (which uses the smartcard channel of a SPICE graphics device) are typical. Further sub-elements, such as <code class="sgmltag-element">source</code>, may be required according to the given type, although a <code class="sgmltag-element">target</code> sub-element is not required (since the consumer of the character device is the hypervisor itself, rather than a device visible in the guest).
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Each mode supports an optional sub-element <code class="sgmltag-element">address</code>, which fine-tunes the correlation between the smartcard and a ccid bus controller (Refer to <a class="xref" href="sub-section-libvirt-dom-xml-devices-device-addresses.html">Section J.16.3, “Device addresses”</a>).
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-redirected-devices.html"><strong>Prev</strong>J.16.7. Redirected 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="sub-section-libvirt-dom-xml-devices-Network-interfaces.html"><strong>Next</strong>J.16.9. Network interfaces</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-video.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-video.html
new file mode 100644
index 0000000..006f483
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-video.html
@@ -0,0 +1,47 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.13. Video devices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-graphical-framebuffers.html" title="J.16.12. Graphical framebuffers" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-consoles.html" title="J.16.14. Consoles, serial, parallel, and channel devices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="pr
evious"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-graphical-framebuffers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-consoles.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-video"><div class="titlepage"><div><div><h3 class="title">J.16.13. Video devices</h3></div></div></div><div class="para">
+ A video device.
+ </div><div class="para">
+ To specify the video devices configuration settings, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-devices-video"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><video></span>
+ <span class="perl_Keyword"><model</span><span class="perl_Others"> type=</span><span class="perl_String">'vga'</span><span class="perl_Others"> vram=</span><span class="perl_String">'8192'</span><span class="perl_Others"> heads=</span><span class="perl_String">'1'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><acceleration</span><span class="perl_Others"> accel3d=</span><span class="perl_String">'yes'</span><span class="perl_Others"> accel2d=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></model></span>
+ <span class="perl_Keyword"></video></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.58. Video devices</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-element">graphics</code> element has a mandatory <code class="sgmltag-attribute">type</code> attribute which takes the value "sdl", "vnc", "rdp" or "desktop" as explained below:
+ </div><div class="table" id="table-libvirt-dom-xml-devices-Network-interfaces-setting-graphical-framebuffer-options"><h6>Table J.22. Graphical framebuffer elements</h6><div class="table-contents"><table summary="Graphical framebuffer elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-element">video</code>
+ </td><td class="">
+ The <code class="sgmltag-element">video</code> element is the container for describing video devices. For backwards compatibility, if no video is set but there is a <code class="sgmltag-element">graphics</code> element in domain xml, then libvirt will add a default <code class="sgmltag-element">video</code> according to the guest type. If "ram" or "vram" are not supplied a default value is used.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">model</code>
+ </td><td class="">
+ This has a mandatory <code class="sgmltag-attribute">type</code> attribute which takes the value <code class="sgmltag-element">vga</code>, <code class="sgmltag-element">cirrus</code>, <code class="sgmltag-element">vmvga</code>, <code class="sgmltag-element">xen</code>, <code class="sgmltag-element">vbox</code>, or <code class="sgmltag-element">qxl</code> depending on the hypervisor features available. You can also provide the amount of video memory in kibibytes (blocks of 1024 bytes) using vram and the number of figure with heads.
+ </td></tr><tr><td class="">
+ acceleration
+ </td><td class="">
+ If acceleration is supported it should be enabled using the <code class="sgmltag-attribute">accel3d</code> and <code class="sgmltag-attribute">accel2d</code> attributes in the <code class="sgmltag-element">acceleration</code> element.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">address</code>
+ </td><td class="">
+ The optional address sub-element can be used to tie the video device to a particular PCI slot.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-graphical-framebuffers.html"><strong>Prev</strong>J.16.12. Graphical framebuffers</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="sub-section-libvirt-dom-xml-devices-consoles.html"><strong>Next</strong>J.16.14. Consoles, serial, parallel, and channel ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-DHCP-snooping.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-DHCP-snooping.html
new file mode 100644
index 0000000..c8ffc25
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-DHCP-snooping.html
@@ -0,0 +1,25 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.5.2. DHCP snooping</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-auto-IP-add-detect-dhcp-snoop.html" title="H.10.5. Automatic IP address detection and DHCP snooping" /><link rel="prev" href="sub-sect-auto-IP-add-detect-dhcp-snoop.html" title="H.10.5. Automatic IP address detection and DHCP snooping" /><link rel="next" href="sub-sect-vars-reserved.html" title="H.10.6. Reserved Variables" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li cla
ss="previous"><a accesskey="p" href="sub-sect-auto-IP-add-detect-dhcp-snoop.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-vars-reserved.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-DHCP-snooping"><div class="titlepage"><div><div><h4 class="title">H.10.5.2. DHCP snooping</h4></div></div></div><div class="para">
+ <code class="command">CTRL_IP_LEARNING=<em class="replaceable"><code>dhcp</code></em></code> (DHCP snooping) provides additional anti-spoofing security, especially when combined with a filter allowing only trusted DHCP servers to assign IP addresses. To enable this, set the variable <em class="parameter"><code>DHCPSERVER</code></em> to the IP address of a valid DHCP server and provide filters that use this variable to filter incoming DHCP responses.
+ </div><div class="para">
+ When DHCP snooping is enabled and the DHCP lease expires, the guest will no longer be able to use the IP address until it acquires a new, valid lease from a DHCP server. If the guest is migrated, it must get a new valid DHCP lease to use an IP address (e.g., by bringing the VM interface down and up again).
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Automatic DHCP detection listens to the DHCP traffic the guest exchanges with the DHCP server of the infrastructure. To avoid denial-of-service attacks on libvirt, the evaluation of those packets is rate-limited, meaning that a guest sending an excessive number of DHCP packets per second on an interface will not have all of those packets evaluated and thus filters may not get adapted. Normal DHCP client behavior is assumed to send a low number of DHCP packets per second. Further, it is important to setup appropriate filters on all guests in the infrastructure to avoid them being able to send DHCP packets. Therefore guests must either be prevented from sending UDP and TCP traffic from port 67 to port 68 or the DHCPSERVER variable should be used on all guests to restrict DHCP server messages to only be allowed to originate from trusted DHCP servers. At the same time anti-spoofing prevention must be enabled on all guests in the subnet.
+ </div></div></div><div class="example" id="exam-dhcp-snoop"><h6>Example H.6. Activating IPs for DHCP snooping</h6><div class="example-contents"><div class="para">
+ The following XML provides an example for the activation of IP address learning using the DHCP snooping method:
+ </div><pre class="screen">
+ <interface type='bridge'>
+ <source bridge='virbr0'/>
+ <filterref filter='clean-traffic'>
+ <parameter name='CTRL_IP_LEARNING' value='dhcp'/>
+ </filterref>
+ </interface>
+</pre></div></div><br class="example-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-auto-IP-add-detect-dhcp-snoop.html"><strong>Prev</strong>H.10.5. Automatic IP address detection and DHCP 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="sub-sect-vars-reserved.html"><strong>Next</strong>H.10.6. Reserved Variables</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-chars-IPv6.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-chars-IPv6.html
new file mode 100644
index 0000000..d1a1636
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-chars-IPv6.html
@@ -0,0 +1,104 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.10.6. IPv6</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-supp-pros.html" title="H.10.10. Supported protocols" /><link rel="prev" href="sub-sub-sect-prot-Ipv4-explained.html" title="H.10.10.5. IPv4" /><link rel="next" href="sub-sub-sect-chars-tcp-udp.html" title="H.10.10.7. TCP/UDP/SCTP" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-prot-Ipv4-explained.html"><strong>Prev</stro
ng></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-chars-tcp-udp.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-chars-IPv6"><div class="titlepage"><div><div><h4 class="title">H.10.10.6. IPv6</h4></div></div></div><div class="para">
+ Protocol ID: ipv6
+ </div><div class="para">
+ Rules of this type should either go into the root or ipv6 chain.
+ </div><div class="table" id="table-ipv6-vars"><h6>Table H.8. IPv6 protocol types</h6><div class="table-contents"><table summary="IPv6 protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of destination
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ protocol
+ </td><td class="">
+ UINT8, STRING
+ </td><td class="">
+ Layer 4 protocol identifier. Valid strings for protocol are: tcp, udp, udplite, esp, ah, icmpv6, sctp
+ </td></tr><tr><td class="">
+ scrportstart
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ Start of range of valid source ports; requires protocol
+ </td></tr><tr><td class="">
+ srcportend
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ End of range of valid source ports; requires protocol
+ </td></tr><tr><td class="">
+ dstportstart
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ Start of range of valid destination ports; requires protocol
+ </td></tr><tr><td class="">
+ dstportend
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ End of range of valid destination ports; requires protocol
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-prot-Ipv4-explained.html"><strong>Prev</strong>H.10.10.5. IPv4</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="sub-sub-sect-chars-tcp-udp.html"><strong>Next</strong>H.10.10.7. TCP/UDP/SCTP</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-chars-tcp-udp.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-chars-tcp-udp.html
new file mode 100644
index 0000000..f8296cd
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-chars-tcp-udp.html
@@ -0,0 +1,128 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.10.7. TCP/UDP/SCTP</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-supp-pros.html" title="H.10.10. Supported protocols" /><link rel="prev" href="sub-sub-sect-chars-IPv6.html" title="H.10.10.6. IPv6" /><link rel="next" href="sub-sub-sect-icmp.html" title="H.10.10.8. ICMP" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-chars-IPv6.html"><strong>Prev</strong></a></li><li class="next"><a acc
esskey="n" href="sub-sub-sect-icmp.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-chars-tcp-udp"><div class="titlepage"><div><div><h4 class="title">H.10.10.7. TCP/UDP/SCTP</h4></div></div></div><div class="para">
+ Protocol ID: tcp, udp, sctp
+ </div><div class="para">
+ The chain parameter is ignored for this type of traffic and should either be omitted or set to root. .
+ </div><div class="table" id="table-tcp-udp-vars"><h6>Table H.9. TCP/UDP/SCTP protocol types</h6><div class="table-contents"><table summary="TCP/UDP/SCTP protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ scripto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of source IP address
+ </td></tr><tr><td class="">
+ srcipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of source IP address
+ </td></tr><tr><td class="">
+ dstipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of destination IP address
+ </td></tr><tr><td class="">
+ dstipto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of destination IP address
+ </td></tr><tr><td class="">
+ scrportstart
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ Start of range of valid source ports; requires protocol
+ </td></tr><tr><td class="">
+ srcportend
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ End of range of valid source ports; requires protocol
+ </td></tr><tr><td class="">
+ dstportstart
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ Start of range of valid destination ports; requires protocol
+ </td></tr><tr><td class="">
+ dstportend
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ End of range of valid destination ports; requires protocol
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr><tr><td class="">
+ state
+ </td><td class="">
+ STRING
+ </td><td class="">
+ comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE
+ </td></tr><tr><td class="">
+ flags
+ </td><td class="">
+ STRING
+ </td><td class="">
+ TCP-only: format of mask/flags with mask and flags each being a comma separated list of SYN,ACK,URG,PSH,FIN,RST or NONE or ALL
+ </td></tr><tr><td class="">
+ ipset
+ </td><td class="">
+ STRING
+ </td><td class="">
+ The name of an IPSet managed outside of libvirt
+ </td></tr><tr><td class="">
+ ipsetflags
+ </td><td class="">
+ IPSETFLAGS
+ </td><td class="">
+ flags for the IPSet; requires ipset attribute
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-chars-IPv6.html"><strong>Prev</strong>H.10.10.6. IPv6</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="sub-sub-sect-icmp.html"><strong>Next</strong>H.10.10.8. ICMP</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-icmp.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-icmp.html
new file mode 100644
index 0000000..2b6e9c6
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-icmp.html
@@ -0,0 +1,128 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.10.8. ICMP</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-supp-pros.html" title="H.10.10. Supported protocols" /><link rel="prev" href="sub-sub-sect-chars-tcp-udp.html" title="H.10.10.7. TCP/UDP/SCTP" /><link rel="next" href="sub-sub-sect-igmp-esp-ah-etc.html" title="H.10.10.9. IGMP, ESP, AH, UDPLITE, 'ALL'" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-chars-tcp-udp.html"><st
rong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-igmp-esp-ah-etc.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-icmp"><div class="titlepage"><div><div><h4 class="title">H.10.10.8. ICMP</h4></div></div></div><div class="para">
+ Protocol ID: icmp
+ </div><div class="para">
+ Note: The chain parameter is ignored for this type of traffic and should either be omitted or set to root.
+ </div><div class="table" id="table-icmp-vars"><h6>Table H.10. ICMP protocol types</h6><div class="table-contents"><table summary="ICMP protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to the MAC address of the sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAD_ADDR
+ </td><td class="">
+ MAC address of the destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to the MAC address of the destination
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ srcipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ start of range of source IP address
+ </td></tr><tr><td class="">
+ scripto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ end of range of source IP address
+ </td></tr><tr><td class="">
+ dstipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of destination IP address
+ </td></tr><tr><td class="">
+ dstipto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of destination IP address
+ </td></tr><tr><td class="">
+ type
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ ICMP type
+ </td></tr><tr><td class="">
+ code
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ ICMP code
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr><tr><td class="">
+ state
+ </td><td class="">
+ STRING
+ </td><td class="">
+ comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE
+ </td></tr><tr><td class="">
+ ipset
+ </td><td class="">
+ STRING
+ </td><td class="">
+ The name of an IPSet managed outside of libvirt
+ </td></tr><tr><td class="">
+ ipsetflags
+ </td><td class="">
+ IPSETFLAGS
+ </td><td class="">
+ flags for the IPSet; requires ipset attribute
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-chars-tcp-udp.html"><strong>Prev</strong>H.10.10.7. TCP/UDP/SCTP</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="sub-sub-sect-igmp-esp-ah-etc.html"><strong>Next</strong>H.10.10.9. IGMP, ESP, AH, UDPLITE, 'ALL'</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-icmpv6.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-icmpv6.html
new file mode 100644
index 0000000..e2a2ccd
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-icmpv6.html
@@ -0,0 +1,110 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.10.11. ICMPv6</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-supp-pros.html" title="H.10.10. Supported protocols" /><link rel="prev" href="sub-sub-sect-tcp-utp-sctp-over-ipv6.html" title="H.10.10.10. TCP/UDP/SCTP over IPV6" /><link rel="next" href="sub-sub-sect-igmp-esp-ah-udplite-over-ipv6.html" title="H.10.10.12. IGMP, ESP, AH, UDPLITE, 'ALL' over IPv6" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="
p" href="sub-sub-sect-tcp-utp-sctp-over-ipv6.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-igmp-esp-ah-udplite-over-ipv6.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-icmpv6"><div class="titlepage"><div><div><h4 class="title">H.10.10.11. ICMPv6</h4></div></div></div><div class="para">
+ Protocol ID: icmpv6
+ </div><div class="para">
+ The chain parameter is ignored for this type of traffic and should either be omitted or set to root.
+ </div><div class="table" id="table-icmpv6-protcol-types"><h6>Table H.13. ICMPv6 protocol types</h6><div class="table-contents"><table summary="ICMPv6 protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ srcipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ start of range of source IP address
+ </td></tr><tr><td class="">
+ scripto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ end of range of source IP address
+ </td></tr><tr><td class="">
+ dstipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of destination IP address
+ </td></tr><tr><td class="">
+ dstipto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of destination IP address
+ </td></tr><tr><td class="">
+ type
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ ICMPv6 type
+ </td></tr><tr><td class="">
+ code
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ ICMPv6 code
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr><tr><td class="">
+ state
+ </td><td class="">
+ STRING
+ </td><td class="">
+ comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE
+ </td></tr><tr><td class="">
+ ipset
+ </td><td class="">
+ STRING
+ </td><td class="">
+ The name of an IPSet managed outside of libvirt
+ </td></tr><tr><td class="">
+ ipsetflags
+ </td><td class="">
+ IPSETFLAGS
+ </td><td class="">
+ flags for the IPSet; requires ipset attribute
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-tcp-utp-sctp-over-ipv6.html"><strong>Prev</strong>H.10.10.10. TCP/UDP/SCTP over IPV6</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="sub-sub-sect-igmp-esp-ah-udplite-over-ipv6.html"><strong>Next</strong>H.10.10.12. IGMP, ESP, AH, UDPLITE, 'ALL' over IP...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-igmp-esp-ah-etc.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-igmp-esp-ah-etc.html
new file mode 100644
index 0000000..c0dca31
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-igmp-esp-ah-etc.html
@@ -0,0 +1,116 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.10.9. IGMP, ESP, AH, UDPLITE, 'ALL'</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-supp-pros.html" title="H.10.10. Supported protocols" /><link rel="prev" href="sub-sub-sect-icmp.html" title="H.10.10.8. ICMP" /><link rel="next" href="sub-sub-sect-tcp-utp-sctp-over-ipv6.html" title="H.10.10.10. TCP/UDP/SCTP over IPV6" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-icmp.html"><strong>Prev</strong></a></l
i><li class="next"><a accesskey="n" href="sub-sub-sect-tcp-utp-sctp-over-ipv6.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-igmp-esp-ah-etc"><div class="titlepage"><div><div><h4 class="title">H.10.10.9. IGMP, ESP, AH, UDPLITE, 'ALL'</h4></div></div></div><div class="para">
+ Protocol ID: igmp, esp, ah, udplite, all
+ </div><div class="para">
+ The chain parameter is ignored for this type of traffic and should either be omitted or set to root.
+ </div><div class="table" id="table-igmp-esp-ah-vars"><h6>Table H.11. IGMP, ESP, AH, UDPLITE, 'ALL'</h6><div class="table-contents"><table summary="IGMP, ESP, AH, UDPLITE, 'ALL'" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to the MAC address of the sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAD_ADDR
+ </td><td class="">
+ MAC address of the destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to the MAC address of the destination
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ srcipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ start of range of source IP address
+ </td></tr><tr><td class="">
+ scripto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ end of range of source IP address
+ </td></tr><tr><td class="">
+ dstipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of destination IP address
+ </td></tr><tr><td class="">
+ dstipto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of destination IP address
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr><tr><td class="">
+ state
+ </td><td class="">
+ STRING
+ </td><td class="">
+ comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE
+ </td></tr><tr><td class="">
+ ipset
+ </td><td class="">
+ STRING
+ </td><td class="">
+ The name of an IPSet managed outside of libvirt
+ </td></tr><tr><td class="">
+ ipsetflags
+ </td><td class="">
+ IPSETFLAGS
+ </td><td class="">
+ flags for the IPSet; requires ipset attribute
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-icmp.html"><strong>Prev</strong>H.10.10.8. ICMP</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="sub-sub-sect-tcp-utp-sctp-over-ipv6.html"><strong>Next</strong>H.10.10.10. TCP/UDP/SCTP over IPV6</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-igmp-esp-ah-udplite-over-ipv6.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-igmp-esp-ah-udplite-over-ipv6.html
new file mode 100644
index 0000000..48b122a
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-igmp-esp-ah-udplite-over-ipv6.html
@@ -0,0 +1,98 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.10.12. IGMP, ESP, AH, UDPLITE, 'ALL' over IPv6</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-supp-pros.html" title="H.10.10. Supported protocols" /><link rel="prev" href="sub-sub-sect-icmpv6.html" title="H.10.10.11. ICMPv6" /><link rel="next" href="sub-sect-adv-filt-topics.html" title="H.10.11. Advanced Filter Configuration Topics" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-icmpv6.html"><strong>Prev</strong>
</a></li><li class="next"><a accesskey="n" href="sub-sect-adv-filt-topics.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-igmp-esp-ah-udplite-over-ipv6"><div class="titlepage"><div><div><h4 class="title">H.10.10.12. IGMP, ESP, AH, UDPLITE, 'ALL' over IPv6</h4></div></div></div><div class="para">
+ Protocol ID: igmp-ipv6, esp-ipv6, ah-ipv6, udplite-ipv6, all-ipv6
+ </div><div class="para">
+ The chain parameter is ignored for this type of traffic and should either be omitted or set to root.
+ </div><div class="table" id="table-igmp-esp-ah-udplite-over-ipv6-vars"><h6>Table H.14. IGMP, ESP, AH, UDPLITE, 'ALL' over IPv protocol types</h6><div class="table-contents"><table summary="IGMP, ESP, AH, UDPLITE, 'ALL' over IPv protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ srcipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ start of range of source IP address
+ </td></tr><tr><td class="">
+ scripto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ end of range of source IP address
+ </td></tr><tr><td class="">
+ dstipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of destination IP address
+ </td></tr><tr><td class="">
+ dstipto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of destination IP address
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr><tr><td class="">
+ state
+ </td><td class="">
+ STRING
+ </td><td class="">
+ comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE
+ </td></tr><tr><td class="">
+ ipset
+ </td><td class="">
+ STRING
+ </td><td class="">
+ The name of an IPSet managed outside of libvirt
+ </td></tr><tr><td class="">
+ ipsetflags
+ </td><td class="">
+ IPSETFLAGS
+ </td><td class="">
+ flags for the IPSet; requires ipset attribute
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-icmpv6.html"><strong>Prev</strong>H.10.10.11. ICMPv6</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="sub-sect-adv-filt-topics.html"><strong>Next</strong>H.10.11. Advanced Filter Configuration Topics</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-lim-numb-conns.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-lim-numb-conns.html
new file mode 100644
index 0000000..47fd0e9
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-lim-numb-conns.html
@@ -0,0 +1,43 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.11.2. Limiting Number of Connections</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-adv-filt-topics.html" title="H.10.11. Advanced Filter Configuration Topics" /><link rel="prev" href="sub-sect-adv-filt-topics.html" title="H.10.11. Advanced Filter Configuration Topics" /><link rel="next" href="sub-sub-subsect-command-line-tools.html" title="H.10.11.3. Command line tools" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href
="sub-sect-adv-filt-topics.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-subsect-command-line-tools.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-lim-numb-conns"><div class="titlepage"><div><div><h4 class="title">H.10.11.2. Limiting Number of Connections</h4></div></div></div><div class="para">
+ To limit the number of connections a guest may establish, a rule must be provided that sets a limit of connections for a given type of traffic. If for example a VM is supposed to be allowed to only ping one other IP address at a time and is supposed to have only one active incoming ssh connection at a time.
+ </div><div class="example" id="ex-xml-frag-limits"><h6>Example H.10. XML sample file that sets limits to connections</h6><div class="example-contents"><div class="para">
+ The following XML fragment can be used to limit connections
+ </div><pre class="screen">
+ [...]
+ <rule action='drop' direction='in' priority='400'>
+ <tcp connlimit-above='1'/>
+ </rule>
+ <rule action='accept' direction='in' priority='500'>
+ <tcp dstportstart='22'/>
+ </rule>
+ <rule action='drop' direction='out' priority='400'>
+ <icmp connlimit-above='1'/>
+ </rule>
+ <rule action='accept' direction='out' priority='500'>
+ <icmp/>
+ </rule>
+ <rule action='accept' direction='out' priority='500'>
+ <udp dstportstart='53'/>
+ </rule>
+ <rule action='drop' direction='inout' priority='1000'>
+ <all/>
+ </rule>
+ [...]
+</pre></div></div><br class="example-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Limitation rules must be listed in the XML prior to the rules for accepting traffic. According to the XML file in <a class="xref" href="sub-sub-sect-lim-numb-conns.html#ex-xml-frag-limits">Example H.10, “XML sample file that sets limits to connections”</a>, an additional rule for allowing DNS traffic sent to port 22 go out the guest, has been added to avoid ssh sessions not getting established for reasons related to DNS lookup failures by the ssh daemon. Leaving this rule out may result in the ssh client hanging unexpectedly as it tries to connect. Additional caution should be used in regards to handling timeouts related to tracking of traffic. An ICMP ping that the user may have terminated inside the guest may have a long timeout in the host's connection tracking system and will therefore not allow another ICMP ping to go through.
+ </div><div class="para">
+ The best solution is to tune the timeout in the host's <code class="filename">sysfs</code> with the following command:# <code class="command">echo 3 > /proc/sys/net/netfilter/nf_conntrack_icmp_timeout</code>. This command sets the ICMP connection tracking timeout to 3 seconds. The effect of this is that once one ping is terminated, another one can start after 3 seconds.
+ </div><div class="para">
+ If for any reason the guest has not properly closed its TCP connection, the connection to be held open for a longer period of time, especially if the TCP timeout value was set for a large amount of time on the host. In addition, any idle connection may result in a time out in the connection tracking system which can be re-activated once packets are exchanged.
+ </div><div class="para">
+ However, if the limit is set too low, newly initiated connections may force an idle connection into TCP backoff. Therefore, the limit of connections should be set rather high so that fluctuations in new TCP connections don't cause odd traffic behavior in relation to idle connections.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-adv-filt-topics.html"><strong>Prev</strong>H.10.11. Advanced Filter Configuration Topics</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="sub-sub-subsect-command-line-tools.html"><strong>Next</strong>H.10.11.3. Command line tools</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-pre-exist-net-filter.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-pre-exist-net-filter.html
new file mode 100644
index 0000000..c110dd3
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-pre-exist-net-filter.html
@@ -0,0 +1,42 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.11.4. Pre-existing network filters</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-adv-filt-topics.html" title="H.10.11. Advanced Filter Configuration Topics" /><link rel="prev" href="sub-sub-subsect-command-line-tools.html" title="H.10.11.3. Command line tools" /><link rel="next" href="sub-sub-sect-write-own-filters.html" title="H.10.11.5. Writing your own filters" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="su
b-sub-subsect-command-line-tools.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-write-own-filters.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-pre-exist-net-filter"><div class="titlepage"><div><div><h4 class="title">H.10.11.4. Pre-existing network filters</h4></div></div></div><div class="para">
+ The following is a list of example network filters that are automatically installed with libvirt:
+ </div><div class="table" id="table-icmpv6-vars"><h6>Table H.15. ICMPv6 protocol types</h6><div class="table-contents"><table summary="ICMPv6 protocol types" border="1"><colgroup><col class="1" width="50%" /><col class="2" width="50%" /></colgroup><thead><tr><th class="">
+ Command Name
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ no-arp-spoofing
+ </td><td class="">
+ Prevents a guest from spoofing ARP traffic; this filter only allows ARP request and reply messages and enforces that those packets contain the MAC and IP addresses of the guest.
+ </td></tr><tr><td class="">
+ allow-dhcp
+ </td><td class="">
+ Allows a guest to request an IP address via DHCP (from any DHCP server)
+ </td></tr><tr><td class="">
+ allow-dhcp-server
+ </td><td class="">
+ Allows a guest to request an IP address from a specified DHCP server. The dotted decimal IP address of the DHCP server must be provided in a reference to this filter. The name of the variable must be <em class="replaceable"><code>DHCPSERVER</code></em>.
+ </td></tr><tr><td class="">
+ no-ip-spoofing
+ </td><td class="">
+ Prevents a guest from sending IP packets with a source IP address different from the one inside the packet.
+ </td></tr><tr><td class="">
+ no-ip-multicast
+ </td><td class="">
+ Prevents a guest from sending IP multicast packets.
+ </td></tr><tr><td class="">
+ clean-traffic
+ </td><td class="">
+ Prevents MAC, IP and ARP spoofing. This filter references several other filters as building blocks.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ These filters are only building blocks and require a combination with other filters to provide useful network traffic filtering. The most used one in the above list is the <em class="replaceable"><code>clean-traffic</code></em> filter. This filter itself can for example be combined with the <em class="replaceable"><code>no-ip-multicast</code></em> filter to prevent virtual machines from sending IP multicast traffic on top of the prevention of packet spoofing.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-subsect-command-line-tools.html"><strong>Prev</strong>H.10.11.3. Command line 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="sub-sub-sect-write-own-filters.html"><strong>Next</strong>H.10.11.5. Writing your own filters</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-prot-ARP-RARP-explained.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-prot-ARP-RARP-explained.html
new file mode 100644
index 0000000..c240da6
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-prot-ARP-RARP-explained.html
@@ -0,0 +1,98 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.10.4. ARP/RARP</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-supp-pros.html" title="H.10.10. Supported protocols" /><link rel="prev" href="sub-sub-sect-prot-STP-explained.html" title="H.10.10.3. STP (Spanning Tree Protocol)" /><link rel="next" href="sub-sub-sect-prot-Ipv4-explained.html" title="H.10.10.5. IPv4" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-prot-STP-explained.html
"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-prot-Ipv4-explained.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-prot-ARP-RARP-explained"><div class="titlepage"><div><div><h4 class="title">H.10.10.4. ARP/RARP</h4></div></div></div><div class="para">
+ Protocol ID: arp or rarp
+ </div><div class="para">
+ Rules of this type should either go into the root or arp/rarp chain.
+ </div><div class="table" id="table-arp-vars"><h6>Table H.6. ARP and RARP protocol types</h6><div class="table-contents"><table summary="ARP and RARP protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of destination
+ </td></tr><tr><td class="">
+ hwtype
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Hardware type
+ </td></tr><tr><td class="">
+ protocoltype
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Protocol type
+ </td></tr><tr><td class="">
+ opcode
+ </td><td class="">
+ UINT16, STRING
+ </td><td class="">
+ Opcode valid strings are: Request, Reply, Request_Reverse, Reply_Reverse, DRARP_Request, DRARP_Reply, DRARP_Error, InARP_Request, ARP_NAK
+ </td></tr><tr><td class="">
+ arpsrcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ Source MAC address in ARP/RARP packet
+ </td></tr><tr><td class="">
+ arpdstmacaddr
+ </td><td class="">
+ MAC _ADDR
+ </td><td class="">
+ Destination MAC address in ARP/RARP packet
+ </td></tr><tr><td class="">
+ arpsrcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address in ARP/RARP packet
+ </td></tr><tr><td class="">
+ arpdstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address in ARP/RARP packet
+ </td></tr><tr><td class="">
+ gratututous
+ </td><td class="">
+ BOOLEAN
+ </td><td class="">
+ Boolean indiating whether to check for a gratuitous ARP packet
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-prot-STP-explained.html"><strong>Prev</strong>H.10.10.3. STP (Spanning Tree Protocol) </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="sub-sub-sect-prot-Ipv4-explained.html"><strong>Next</strong>H.10.10.5. IPv4</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-prot-Ipv4-explained.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-prot-Ipv4-explained.html
new file mode 100644
index 0000000..d531953
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-prot-Ipv4-explained.html
@@ -0,0 +1,104 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.10.5. IPv4</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-supp-pros.html" title="H.10.10. Supported protocols" /><link rel="prev" href="sub-sub-sect-prot-ARP-RARP-explained.html" title="H.10.10.4. ARP/RARP" /><link rel="next" href="sub-sub-sect-chars-IPv6.html" title="H.10.10.6. IPv6" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-prot-ARP-RARP-explained.html"><strong>Prev</str
ong></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-chars-IPv6.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-prot-Ipv4-explained"><div class="titlepage"><div><div><h4 class="title">H.10.10.5. IPv4</h4></div></div></div><div class="para">
+ Protocol ID: ip
+ </div><div class="para">
+ Rules of this type should either go into the root or ipv4 chain.
+ </div><div class="table" id="table-ipv4-vars"><h6>Table H.7. IPv4 protocol types</h6><div class="table-contents"><table summary="IPv4 protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of destination
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ protocol
+ </td><td class="">
+ UINT8, STRING
+ </td><td class="">
+ Layer 4 protocol identifier. Valid strings for protocol are: tcp, udp, udplite, esp, ah, icmp, igmp, sctp
+ </td></tr><tr><td class="">
+ srcportstart
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Start of range of valid source ports; requires protocol
+ </td></tr><tr><td class="">
+ srcportend
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ End of range of valid source ports; requires protocol
+ </td></tr><tr><td class="">
+ dstportstart
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ Start of range of valid destination ports; requires protocol
+ </td></tr><tr><td class="">
+ dstportend
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ End of range of valid destination ports; requires protocol
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-prot-ARP-RARP-explained.html"><strong>Prev</strong>H.10.10.4. ARP/RARP</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="sub-sub-sect-chars-IPv6.html"><strong>Next</strong>H.10.10.6. IPv6</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-prot-STP-explained.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-prot-STP-explained.html
new file mode 100644
index 0000000..b0ea2d1
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-prot-STP-explained.html
@@ -0,0 +1,158 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.10.3. STP (Spanning Tree Protocol)</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-supp-pros.html" title="H.10.10. Supported protocols" /><link rel="prev" href="sub-sub-sect-vlan.html" title="H.10.10.2. VLAN (802.1Q)" /><link rel="next" href="sub-sub-sect-prot-ARP-RARP-explained.html" title="H.10.10.4. ARP/RARP" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-vlan.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="sub-sub-sect-prot-ARP-RARP-explained.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-prot-STP-explained"><div class="titlepage"><div><div><h4 class="title">H.10.10.3. STP (Spanning Tree Protocol) </h4></div></div></div><div class="para">
+ Protocol ID: stp
+ </div><div class="para">
+ Rules of this type should go either into the root or stp chain.
+ </div><div class="table" id="table-stp-vars"><h6>Table H.5. STP protocol types</h6><div class="table-contents"><table summary="STP protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of sender
+ </td></tr><tr><td class="">
+ type
+ </td><td class="">
+ UINT8
+ </td><td class="">
+ Bridge Protocol Data Unit (BPDU) type
+ </td></tr><tr><td class="">
+ flags
+ </td><td class="">
+ UINT8
+ </td><td class="">
+ BPDU flagdstmacmask
+ </td></tr><tr><td class="">
+ root-priority
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Root priority range start
+ </td></tr><tr><td class="">
+ root-priority-hi
+ </td><td class="">
+ UINT16 (0x0-0xfff, 0 - 4095)
+ </td><td class="">
+ Root priority range end
+ </td></tr><tr><td class="">
+ root-address
+ </td><td class="">
+ MAC _ADDRESS
+ </td><td class="">
+ root MAC Address
+ </td></tr><tr><td class="">
+ root-address-mask
+ </td><td class="">
+ MAC _MASK
+ </td><td class="">
+ root MAC Address mask
+ </td></tr><tr><td class="">
+ roor-cost
+ </td><td class="">
+ UINT32
+ </td><td class="">
+ Root path cost (range start)
+ </td></tr><tr><td class="">
+ root-cost-hi
+ </td><td class="">
+ UINT32
+ </td><td class="">
+ Root path cost range end
+ </td></tr><tr><td class="">
+ sender-priority-hi
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Sender prioriry range end
+ </td></tr><tr><td class="">
+ sender-address
+ </td><td class="">
+ MAC_ADDRESS
+ </td><td class="">
+ BPDU sender MAC address
+ </td></tr><tr><td class="">
+ sender-address-mask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ BPDU sender MAC address mask
+ </td></tr><tr><td class="">
+ port
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Port identifier (range start)
+ </td></tr><tr><td class="">
+ port_hi
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Port identifier range end
+ </td></tr><tr><td class="">
+ msg-age
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Message age timer (range start)
+ </td></tr><tr><td class="">
+ msg-age-hi
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Message age timer range end
+ </td></tr><tr><td class="">
+ max-age-hi
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Maximum age time range end
+ </td></tr><tr><td class="">
+ hello-time
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Hello time timer (range start)
+ </td></tr><tr><td class="">
+ hello-time-hi
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Hello time timer range end
+ </td></tr><tr><td class="">
+ forward-delay
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Forward delay (range start)
+ </td></tr><tr><td class="">
+ forward-delay-hi
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Forward delay range end
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-vlan.html"><strong>Prev</strong>H.10.10.2. VLAN (802.1Q)</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="sub-sub-sect-prot-ARP-RARP-explained.html"><strong>Next</strong>H.10.10.4. ARP/RARP</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-samp-filter.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-samp-filter.html
new file mode 100644
index 0000000..aef303b
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-samp-filter.html
@@ -0,0 +1,146 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.11.6. Sample custom filter</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-adv-filt-topics.html" title="H.10.11. Advanced Filter Configuration Topics" /><link rel="prev" href="sub-sub-sect-write-own-filters.html" title="H.10.11.5. Writing your own filters" /><link rel="next" href="sub-sect-limitations-filters-network-subsystem.html" title="H.10.12. Limitations" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href=
"sub-sub-sect-write-own-filters.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-limitations-filters-network-subsystem.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-samp-filter"><div class="titlepage"><div><div><h4 class="title">H.10.11.6. Sample custom filter</h4></div></div></div><div class="para">
+ Although one of the rules in the above XML contains the IP address of the guest as either a source or a destination address, the filtering of the traffic works correctly. The reason is that whereas the rule's evaluation occurrs internally on a per-interface basis, the rules are additionaly evaluated based on which (tap) interface has sent or will receive the packet, rather than what their source or destination IP address may be.
+ </div><div class="example"><h6>Example H.12. Sample XML for network interface descriptions</h6><div class="example-contents"><div class="para">
+ An XML fragment for a possible network interface description inside the domain XML of the test guest could then look like this:
+ </div><pre class="screen">
+ [...]
+ <interface type='bridge'>
+ <source bridge='mybridge'/>
+ <filterref filter='test-eth0'/>
+ </interface>
+ [...]
+</pre><div class="para">
+ To more strictly control the ICMP traffic and enforce that only ICMP echo requests can be sent from the guest and only ICMP echo responses be received by the guest, the above ICMP rule can be replaced with the following two rules:
+ </div><pre class="screen">
+ <!- - enable outgoing ICMP echo requests- ->
+ <rule action='accept' direction='out'>
+ <icmp type='8'/>
+ </rule>
+</pre><pre class="screen">
+ <!- - enable incoming ICMP echo replies- ->
+ <rule action='accept' direction='in'>
+ <icmp type='0'/>
+ </rule>
+</pre></div></div><br class="example-break" /><div class="example"><h6>Example H.13. Second example custom filter</h6><div class="example-contents"><div class="para">
+ This example demonstrates how to build a similar filter as in the example above, but extends the list of requirements with an ftp server located inside the guest. The requirements for this filter are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ prevents a guest's interface from MAC, IP, and ARP spoofing
+ </div></li><li class="listitem"><div class="para">
+ opens only TCP ports 22 and 80 in a guest's interface
+ </div></li><li class="listitem"><div class="para">
+ allows the guest to send ping traffic from an interface but does not allow the guest to be pinged on the interface
+ </div></li><li class="listitem"><div class="para">
+ allows the guest to do DNS lookups (UDP towards port 53)
+ </div></li><li class="listitem"><div class="para">
+ enables the ftp server (in active mode) so it can run inside the guest
+ </div></li></ul></div><div class="para">
+ The additional requirement of allowing an FTP server to be run inside the guest maps into the requirement of allowing port 21 to be reachable for FTP control traffic as well as enabling the guest to establish an outgoing TCP connection originating from the guest's TCP port 20 back to the FTP client (FTP active mode). There are several ways of how this filter can be written and two possible solutions are included in this example.
+ </div><div class="para">
+ The first solution makes use of the state attribute of the TCP protocol that provides a hook into the connection tracking framework of the Linux host. For the guest-initiated FTP data connection (FTP active mode) the RELATED state is used to enable detection that the guest-initiated FTP data connection is a consequence of ( or 'has a relationship with' ) an existing FTP control connection, thereby allowing it to pass packets through the firewall. The RELATED state, however, is only valid for the very first packet of the outgoing TCP connection for the FTP data path. Afterwards, the state is ESTABLISHED, which then applies equally to the incoming and outgoing direction. All this is related to the FTP data traffic originating from TCP port 20 of the guest. This then leads to the following solution:
+ </div><pre class="screen">
+<filter name='test-eth0'>
+ <!- - This filter (eth0) references the <code class="filename">clean traffic</code> filter to prevent MAC, IP, and ARP spoofing. By not providing an IP address parameter, libvirt will detect the IP address the guest is using. - ->
+ <filterref filter='clean-traffic'/>
+
+ <!- - This rule enables TCP port 21 (FTP-control) to be reachable - ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='21'/>
+ </rule>
+
+ <!- - This rule enables TCP port 20 for guest-initiated FTP data connection related to an existing FTP control connection - ->
+ <rule action='accept' direction='out'>
+ <tcp srcportstart='20' state='RELATED,ESTABLISHED'/>
+ </rule>
+
+ <!- - This rule accepts all packets from a client on the FTP data connection - ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='20' state='ESTABLISHED'/>
+ </rule>
+
+ <!- - This rule enables TCP port 22 (SSH) to be reachable - ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='22'/>
+ </rule>
+
+ <!- -This rule enables TCP port 80 (HTTP) to be reachable - ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='80'/>
+ </rule>
+
+ <!- - This rule enables general ICMP traffic to be initiated by the guest, including ping traffic - ->
+ <rule action='accept' direction='out'>
+ <icmp/>
+ </rule>
+
+ <!- - This rule enables outgoing DNS lookups using UDP - ->
+ <rule action='accept' direction='out'>
+ <udp dstportstart='53'/>
+ </rule>
+
+ <!- - This rule drops all other traffic - ->
+ <rule action='drop' direction='inout'>
+ <all/>
+ </rule>
+
+</filter>
+</pre><div class="para">
+ Before trying out a filter using the RELATED state, you have to make sure that the appropriate connection tracking module has been loaded into the host's kernel. Depending on the version of the kernel, you must run either one of the following two commands before the FTP connection with the guest is established:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ #<code class="command">modprobe nf_conntrack_ftp</code> - where available OR
+ </div></li><li class="listitem"><div class="para">
+ #<code class="command">modprobe ip_conntrack_ftp</code> if above is not available
+ </div></li></ul></div><div class="para">
+ If protocols other than FTP are used in conjunction with the RELATED state, their corresponding module must be loaded. Modules are available for the protocols: ftp, tftp, irc, sip, sctp, and amanda.
+ </div><div class="para">
+ The second solution makes use of the state flags of connections more than the previous solution did. This solution takes advantage of the fact that the NEW state of a connection is valid when the very first packet of a traffic flow is detected. Subsequently, if the very first packet of a flow is accepted, the flow becomes a connection and thus enters into the ESTABLISHED state. Therefore a general rule can be written for allowing packets of ESTABLISHED connections to reach the guest or be sent by the guest. This is done writing specific rules for the very first packets identified by the NEW state and dictates the ports that the data is acceptable. All packets meant for ports that are not explicitly accepted are dropped, thus not reaching an ESTABLISHED state. Any subsequent packets sent from that port are dropped as well.
+ </div><pre class="screen">
+<filter name='test-eth0'>
+ <!- - This filter references the <code class="filename">clean traffic</code> filter to prevent MAC, IP and ARP spoofing. By not providing and IP address parameter, libvirt will detect the IP address the VM is using. - ->
+ <filterref filter='clean-traffic'/>
+
+ <!- - This rule allows the packets of all previously accepted connections to reach the guest - ->
+ <rule action='accept' direction='in'>
+ <all state='ESTABLISHED'/>
+ </rule>
+
+ <!- - This rule allows the packets of all previously accepted and related connections be sent from the guest - ->
+ <rule action='accept' direction='out'>
+ <all state='ESTABLISHED,RELATED'/>
+ </rule>
+
+ <!- - This rule enables traffic towards port 21 (FTP) and port 22 (SSH)- ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='21' dstportend='22' state='NEW'/>
+ </rule>
+
+ <!- - This rule enables traffic towards port 80 (HTTP) - ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='80' state='NEW'/>
+ </rule>
+
+ <!- - This rule enables general ICMP traffic to be initiated by the guest, including ping traffic - ->
+ <rule action='accept' direction='out'>
+ <icmp state='NEW'/>
+ </rule>
+
+ <!- - This rule enables outgoing DNS lookups using UDP - ->
+ <rule action='accept' direction='out'>
+ <udp dstportstart='53' state='NEW'/>
+ </rule>
+
+ <!- - This rule drops all other traffic - ->
+ <rule action='drop' direction='inout'>
+ <all/>
+ </rule>
+
+</filter>
+</pre></div></div><br class="example-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-write-own-filters.html"><strong>Prev</strong>H.10.11.5. Writing your own filters</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="sub-sect-limitations-filters-network-subsystem.html"><strong>Next</strong>H.10.12. Limitations</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-tcp-utp-sctp-over-ipv6.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-tcp-utp-sctp-over-ipv6.html
new file mode 100644
index 0000000..924e079
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-tcp-utp-sctp-over-ipv6.html
@@ -0,0 +1,122 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.10.10. TCP/UDP/SCTP over IPV6</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-supp-pros.html" title="H.10.10. Supported protocols" /><link rel="prev" href="sub-sub-sect-igmp-esp-ah-etc.html" title="H.10.10.9. IGMP, ESP, AH, UDPLITE, 'ALL'" /><link rel="next" href="sub-sub-sect-icmpv6.html" title="H.10.10.11. ICMPv6" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-igmp-esp-ah-etc.html"><strong>Prev<
/strong></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-icmpv6.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-tcp-utp-sctp-over-ipv6"><div class="titlepage"><div><div><h4 class="title">H.10.10.10. TCP/UDP/SCTP over IPV6</h4></div></div></div><div class="para">
+ Protocol ID: tcp-ipv6, udp-ipv6, sctp-ipv6
+ </div><div class="para">
+ The chain parameter is ignored for this type of traffic and should either be omitted or set to root.
+ </div><div class="table" id="table-tcp-udp-over-IPv6-vars"><h6>Table H.12. TCP, UDP, SCTP over IPv6 protocol types</h6><div class="table-contents"><table summary="TCP, UDP, SCTP over IPv6 protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ srcipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ start of range of source IP address
+ </td></tr><tr><td class="">
+ scripto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ end of range of source IP address
+ </td></tr><tr><td class="">
+ dstipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of destination IP address
+ </td></tr><tr><td class="">
+ dstipto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of destination IP address
+ </td></tr><tr><td class="">
+ srcportstart
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Start of range of valid source ports
+ </td></tr><tr><td class="">
+ srcportend
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ End of range of valid source ports
+ </td></tr><tr><td class="">
+ dstportstart
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Start of range of valid destination ports
+ </td></tr><tr><td class="">
+ dstportend
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ End of range of valid destination ports
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr><tr><td class="">
+ state
+ </td><td class="">
+ STRING
+ </td><td class="">
+ comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE
+ </td></tr><tr><td class="">
+ ipset
+ </td><td class="">
+ STRING
+ </td><td class="">
+ The name of an IPSet managed outside of libvirt
+ </td></tr><tr><td class="">
+ ipsetflags
+ </td><td class="">
+ IPSETFLAGS
+ </td><td class="">
+ flags for the IPSet; requires ipset attribute
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-igmp-esp-ah-etc.html"><strong>Prev</strong>H.10.10.9. IGMP, ESP, AH, UDPLITE, 'ALL'</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="sub-sub-sect-icmpv6.html"><strong>Next</strong>H.10.10.11. ICMPv6</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-vlan.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-vlan.html
new file mode 100644
index 0000000..57fcf5f
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-vlan.html
@@ -0,0 +1,62 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.10.2. VLAN (802.1Q)</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-supp-pros.html" title="H.10.10. Supported protocols" /><link rel="prev" href="sub-sect-supp-pros.html" title="H.10.10. Supported protocols" /><link rel="next" href="sub-sub-sect-prot-STP-explained.html" title="H.10.10.3. STP (Spanning Tree Protocol)" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-supp-pros.html"><strong>Prev
</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-prot-STP-explained.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-vlan"><div class="titlepage"><div><div><h4 class="title">H.10.10.2. VLAN (802.1Q)</h4></div></div></div><div class="para">
+ Protocol ID: vlan
+ </div><div class="para">
+ Rules of this type should go either into the root or vlan chain.
+ </div><div class="table" id="table-vlan-vars"><h6>Table H.4. VLAN protocol types</h6><div class="table-contents"><table summary="VLAN protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of destination
+ </td></tr><tr><td class="">
+ vlan-id
+ </td><td class="">
+ UINT16 (0x0-0xfff, 0 - 4095)
+ </td><td class="">
+ VLAN ID
+ </td></tr><tr><td class="">
+ encap-protocol
+ </td><td class="">
+ UINT16 (0x03c-0xfff), String
+ </td><td class="">
+ Encapsulated layer 3 protocol ID, valid strings are arp, ipv4, ipv6
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-supp-pros.html"><strong>Prev</strong>H.10.10. Supported protocols</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="sub-sub-sect-prot-STP-explained.html"><strong>Next</strong>H.10.10.3. STP (Spanning Tree Protocol) </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-write-own-filters.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-write-own-filters.html
new file mode 100644
index 0000000..e3ace9b
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-write-own-filters.html
@@ -0,0 +1,80 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.11.5. Writing your own filters</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-adv-filt-topics.html" title="H.10.11. Advanced Filter Configuration Topics" /><link rel="prev" href="sub-sub-sect-pre-exist-net-filter.html" title="H.10.11.4. Pre-existing network filters" /><link rel="next" href="sub-sub-sect-samp-filter.html" title="H.10.11.6. Sample custom filter" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub
-sub-sect-pre-exist-net-filter.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-samp-filter.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-write-own-filters"><div class="titlepage"><div><div><h4 class="title">H.10.11.5. Writing your own filters</h4></div></div></div><div class="para">
+ Since libvirt only provides a couple of example networking filters, you may consider writing your own. When planning on doing so there are a couple of things you may need to know regarding the network filtering subsystem and how it works internally. Certainly you also have to know and understand the protocols very well that you want to be filtering on so that no further traffic than what you want can pass and that in fact the traffic you want to allow does pass.
+ </div><div class="para">
+ The network filtering subsystem is currently only available on Linux hosts and only works for Qemu and KVM type of virtual machines. On Linux, it builds upon the support for ebtables, iptables and ip6tables and makes use of their features. Considering the list found in <a class="xref" href="sub-sect-supp-pros.html">Section H.10.10, “Supported protocols”</a> the following protolcols can be implemented using ebtables:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ mac
+ </div></li><li class="listitem"><div class="para">
+ stp (spanning tree protocol)
+ </div></li><li class="listitem"><div class="para">
+ vlan (802.1Q)
+ </div></li><li class="listitem"><div class="para">
+ arp, rarp
+ </div></li><li class="listitem"><div class="para">
+ ipv4
+ </div></li><li class="listitem"><div class="para">
+ ipv6
+ </div></li></ul></div><div class="para">
+ Any protocol that runs over IPv4 is supported using iptables, those over IPv6 are implemented using ip6tables.
+ </div><div class="para">
+ Using a Linux host, all traffic filtering rules created by libvirt's network filtering subsystem first passes through the filtering support implemented by ebtables and only afterwards through iptables or ip6tables filters. If a filter tree has rules with the protocols including: mac, stp, vlan arp, rarp, ipv4, or ipv6; the ebtable rules and values listed will automatically be used first.
+ </div><div class="para">
+ Multiple chains for the same protocol can be created. The name of the chain must have a prefix of one of the previously enumerated protocols. To create an additional chain for handling of ARP traffic, a chain with name arp-test, can for example be specified.
+ </div><div class="para">
+ As an example, it is possible to filter on UDP traffic by source and destination ports using the ip protocol filter and specifying attributes for the protocol, source and destination IP addresses and ports of UDP packets that are to be accepted. This allows early filtering of UDP traffic with ebtables. However, once an IP or IPv6 packet, such as a UDP packet, has passed the ebtables layer and there is at least one rule in a filter tree that instantiates iptables or ip6tables rules, a rule to let the UDP packet pass will also be necessary to be provided for those filtering layers. This can be achieved with a rule containing an appropriate udp or udp-ipv6 traffic filtering node.
+ </div><div class="example"><h6>Example H.11. Creating a custom filter</h6><div class="example-contents"><div class="para">
+ Suppose a filter is needed to fulfill the following list of requirements:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ prevents a VM's interface from MAC, IP and ARP spoofing
+ </div></li><li class="listitem"><div class="para">
+ opens only TCP ports 22 and 80 of a VM's interface
+ </div></li><li class="listitem"><div class="para">
+ allows the VM to send ping traffic from an interface but not let the VM be pinged on the interface
+ </div></li><li class="listitem"><div class="para">
+ allows the VM to do DNS lookups (UDP towards port 53)
+ </div></li></ul></div><div class="para">
+ The requirement to prevent spoofing is fulfilled by the existing <em class="parameter"><code>clean-traffic</code></em> network filter, thus the way to do this is to reference it from a custom filter.
+ </div><div class="para">
+ To enable traffic for TCP ports 22 and 80, two rules are added to enable this type of traffic. To allow the guest to send ping traffic a rule is added for ICMP traffic. For simplicity reasons, general ICMP traffic will be allowed to be initated from the guest, and will not be specified to ICMP echo request and response messages. All other traffic will be prevented to reach or be initated by the guest. To do this a rule will be added that drops all other traffic. Assuming the guest is called <code class="filename">test</code> and the interface to associate our filter with is called <code class="filename">eth0</code>, a filter is created named <code class="filename">test-eth0</code>.
+ </div><div class="para">
+ The result of these considerations is the following network filter XML:
+ </div><pre class="screen">
+<filter name='test-eth0'>
+ <!- - This rule references the clean traffic filter to prevent MAC, IP and ARP spoofing. By not providing an IP address parameter, libvirt will detect the IP address the guest is using. - ->
+ <filterref filter='clean-traffic'/>
+
+ <!- - This rule enables TCP ports 22 (ssh) and 80 (http) to be reachable - ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='22'/>
+ </rule>
+
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='80'/>
+ </rule>
+
+ <!- - This rule enables general ICMP traffic to be initiated by the guest including ping traffic - ->
+ <rule action='accept' direction='out'>
+ <icmp/>
+ </rule>>
+
+ <!- - This rule enables outgoing DNS lookups using UDP - ->
+ <rule action='accept' direction='out'>
+ <udp dstportstart='53'/>
+ </rule>
+
+ <!- - This rule drops all other traffic - ->
+ <rule action='drop' direction='inout'>
+ <all/>
+ </rule>
+
+</filter>
+</pre></div></div><br class="example-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-pre-exist-net-filter.html"><strong>Prev</strong>H.10.11.4. Pre-existing network filters</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="sub-sub-sect-samp-filter.html"><strong>Next</strong>H.10.11.6. Sample custom filter</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-boot-order.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-boot-order.html
new file mode 100644
index 0000000..54be2d6
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-boot-order.html
@@ -0,0 +1,25 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.11. Specifying boot order</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element.html" title="J.16.9.10. Overriding the target element" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-interface-ROM-BIOS-configuration.html" title="J.16.9.12. Interface ROM BIOS configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Conten
t/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-interface-ROM-BIOS-configuration.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-boot-order"><div class="titlepage"><div><div><h4 class="title">J.16.9.11. Specifying boot order</h4></div></div></div><div class="para">
+ To specify the boot order, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig--libvirt-dom-xml-devices-Network-interfaces-boot-order"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.49. Specifying boot order</h6></div><br class="figure-break" /><div class="para">
+ For hypervisors which support it, you can set a specific NIC to be used for the network boot. The order of attributes determine the order in which devices will be tried during boot sequence. Note that the per-device boot elements cannot be used together with general boot elements in BIOS bootloader section.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element.html"><strong>Prev</strong>J.16.9.10. Overriding the target element</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="sub-sub-section-libvirt-dom-xml-devices-interface-ROM-BIOS-configuration.html"><strong>Next</strong>J.16.9.12. Interface ROM BIOS configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-bridge-to-lan.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-bridge-to-lan.html
new file mode 100644
index 0000000..8ee3e1a
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-bridge-to-lan.html
@@ -0,0 +1,37 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.2. Bridge to LAN</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-userspace-slirp-stack.html" title="J.16.9.3. Userspace SLIRP stack" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /
></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-userspace-slirp-stack.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-bridge-to-lan"><div class="titlepage"><div><div><h4 class="title">J.16.9.2. Bridge to LAN</h4></div></div></div><div class="para">
+ Note that this is the recommended configuration setting for general guest connectivity on hosts with static wired networking configurations.
+ </div><div class="para">
+ Bridge to LAN provides a bridge from the guest virtual machine directly onto the LAN. This assumes there is a bridge device on the host which has one or more of the hosts physical NICs enslaved. The guest virtual machine will have an associated <code class="sgmltag-attribute">tun</code> device created with a name of <code class="sgmltag-starttag"><vnetN></code>, which can also be overridden with the <code class="sgmltag-starttag"><target></code> element (refer to <a class="xref" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element.html">Section J.16.9.10, “Overriding the target element”</a>). The <code class="sgmltag-starttag"><tun></code> device will be enslaved to the bridge. The IP range / network configuration is whatever is used on the LAN. This provides the guest virtual machine full incoming and outgoing net access just like a physical machine.
+ </div><div class="para">
+ On Linux systems, the bridge device is normally a standard Linux host bridge. On hosts that support Open vSwitch, it is also possible to connect to an open vSwitch bridge device by adding a <code class="sgmltag-attribute">virtualport type='openvswitch'/</code> to the interface definition. The Open vSwitch type virtualport accepts two parameters in its <code class="sgmltag-element">parameters</code> element - an <code class="sgmltag-element">interfaceid</code> which is a standard uuid used to uniquely identify this particular interface to Open vSwitch (if you do no specify one, a random <code class="sgmltag-attribute">interfaceid</code> will be generated for you when you first define the interface), and an optional <code class="sgmltag-element">profileid</code> which is sent to Open vSwitch as the interfaces <code class="sgmltag-starttag"><port-profile></code>. To set the bridge to LAN settings, use a managment tool that will configure the following part of the dom
ain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-br2lan"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'bridge'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> bridge=</span><span class="perl_String">'br0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'bridge'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> bridge=</span><span class="perl_String">'br1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet7'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">"00:11:22:33:44:55"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'bridge'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> bridge=</span><span class="perl_String">'ovsbr'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><virtualport</span><span class="perl_Others"> type=</span><span class="perl_String">'openvswitch'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><parameters</span><span class="perl_Others"> profileid=</span><span class="perl_String">'menial'</span><span class="perl_Others"> interfaceid=</span><span class="perl_String">'09b11c53-8b5c-4eeb-8f00-d84eaa0aaa4f'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></virtualport></span>
+ <span class="perl_Keyword"></interface></span>
+ ...
+ <span class="perl_Keyword"></devices></span>
+</pre></div><h6>Figure J.38. Devices - network interfaces- bridge to LAN</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html"><strong>Prev</strong>J.16.9. Network interfaces</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="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-userspace-slirp-stack.html"><strong>Next</strong>J.16.9.3. Userspace SLIRP stack</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-direct-attachment-to-physical-device.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-direct-attachment-to-physical-device.html
new file mode 100644
index 0000000..138c98d
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-direct-attachment-to-physical-device.html
@@ -0,0 +1,114 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.5. Direct attachment to physical interfaces</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-generic-ethernet-connection.html" title="J.16.9.4. Generic Ethernet connection" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-pci-passthrough.html" title="J.16.9.6. PCI passthrough" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.
png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-generic-ethernet-connection.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-pci-passthrough.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-direct-attachment-to-physical-device"><div class="titlepage"><div><div><h4 class="title">J.16.9.5. Direct attachment to physical interfaces</h4></div></div></div><div class="para">
+ Manipulating the direct attachment to physical interfaces provides direct attachment of the guest virtual machine's NIC to the given taht the physial interface of the host is specified.
+ </div><div class="para">
+ This setup requires the Linux macvtap driver to be available. One of the modes <code class="sgmltag-element">vepa</code> ( 'Virtual Ethernet Port Aggregator'), <code class="sgmltag-element">bridge</code> or <code class="sgmltag-element">private</code> can be chosen for the operation mode of the macvtap device, <code class="sgmltag-element">vepa</code> being the default mode.
+ </div><div class="para">
+ Manipulating direct attachment to physical interfaces involves setting the following parameters in the following part of the domain XML.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-dir-att-2phys"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'direct'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> dev=</span><span class="perl_String">'eth0'</span><span class="perl_Others"> mode=</span><span class="perl_String">'vepa'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.41. Devices - network interfaces- direct attachment to physical interfaces</h6></div><br class="figure-break" /><div class="para">
+ The individual modes cause the delivery of packets to behave as shown in <a class="xref" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-direct-attachment-to-physical-device.html#table-libvirt-dom-xml-gen-direct-attachment-physical-interface">Table J.17, “Direct attachment to physical interface elements”</a>:
+ </div><div class="table" id="table-libvirt-dom-xml-gen-direct-attachment-physical-interface"><h6>Table J.17. Direct attachment to physical interface elements</h6><div class="table-contents"><table summary="Direct attachment to physical interface elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-attribute">vepa</code>
+ </td><td class="">
+ All of the guest virtual machines' packets are sent to the external bridge. Packets whose destination is a guest virtual machine on the same host as where the packet originates from are sent back to the host by the VEPA capable bridge (today's bridges are typically not VEPA capable).
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">bridge</code>
+ </td><td class="">
+ Packets whose destination is on the same host as where they originate from are directly delivered to the target macvtap device. Both origin and destination devices need to be in bridge mode for direct delivery. If either one of them is in <code class="sgmltag-attribute">vepa</code> mode, a VEPA capable bridge is required.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">private</code>
+ </td><td class="">
+ All packets are sent to the external bridge and will only be delivered to a target VM on the same host if they are sent through an external router or gateway and that device sends them back to the host. This procedure is followed if either the source or destination device is in private mode.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">passthrough</code>
+ </td><td class="">
+ This feature attaches a virtual function of a SRIOV capable NIC directly to a guest virtual machine without losing the migration capability. All packets are sent to the VF/IF of the configured network device. Depending on the capabilities of the device additional prerequisites or limitations may apply; for example, this requires kernel 2.6.38 or newer.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The network access of direct attached virtual machines can be managed by the hardware switch to which the physical interface of the host machine is connected to.
+ </div><div class="para">
+ The interface can have additional parameters as shown below, if the switch is conforming to the IEEE 802.1Qbg standard. The parameters of the virtualport element are documented in more detail in the IEEE 802.1Qbg standard. The values are network specific and should be provided by the network administrator. In 802.1Qbg terms, the Virtual Station Interface (VSI) represents the virtual interface of a virtual machine.
+ </div><div class="para">
+ Note that IEEE 802.1Qbg requires a non-zero value for the VLAN ID.
+ </div><div class="para">
+ Additional elements that can be manipulated are described in <a class="xref" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-direct-attachment-to-physical-device.html#table-libvirt-dom-xml-gen-direct-attachment-physical-interface2">Table J.18, “Direct attachment to physical interface additional elements”</a>:
+ </div><div class="table" id="table-libvirt-dom-xml-gen-direct-attachment-physical-interface2"><h6>Table J.18. Direct attachment to physical interface additional elements</h6><div class="table-contents"><table summary="Direct attachment to physical interface additional elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-attribute">managerid</code>
+ </td><td class="">
+ The VSI Manager ID identifies the database containing the VSI type and instance definitions. This is an integer value and the value <code class="sgmltag-element">0</code> is reserved.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">typeid</code>
+ </td><td class="">
+ The VSI Type ID identifies a VSI type characterizing the network access. VSI types are typically managed by network administrator. This is an integer value.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">typeidversion</code>
+ </td><td class="">
+ The VSI Type Version allows multiple versions of a VSI Type. This is an integer value.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">instanceid</code>
+ </td><td class="">
+ The VSI Instance ID Identifier is generated when a VSI instance (i.e. a virtual interface of a virtual machine) is created. This is a globally unique identifier.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">profileid</code>
+ </td><td class="">
+ The profile ID contains the name of the port profile that is to be applied onto this interface. This name is resolved by the port profile database into the network parameters from the port profile, and those network parameters will be applied to this interface.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Additional parameters in the domain XML include:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-dir-att-2phys2"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'direct'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> dev=</span><span class="perl_String">'eth0.2'</span><span class="perl_Others"> mode=</span><span class="perl_String">'vepa'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><virtualport</span><span class="perl_Others"> type=</span><span class="perl_String">"802.1Qbg"</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><parameters</span><span class="perl_Others"> managerid=</span><span class="perl_String">"11"</span><span class="perl_Others"> typeid=</span><span class="perl_String">"1193047"</span><span class="perl_Others"> typeidversion=</span><span class="perl_String">"2"</span><span class="perl_Others"> instanceid=</span><span class="perl_String">"09b11c53-8b5c-4eeb-8f00-d84eaa0aaa4f"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></virtualport></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.42. Devices - network interfaces- direct attachment to physical interfaces additional parameters</h6></div><br class="figure-break" /><div class="para">
+ The interface can have additional parameters as shown below if the switch is conforming to the IEEE 802.1Qbh standard. The values are network specific and should be provided by the network administrator.
+ </div><div class="para">
+ Additional parameters in the domain XML include:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-dir-att-2phys3"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'direct'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> dev=</span><span class="perl_String">'eth0'</span><span class="perl_Others"> mode=</span><span class="perl_String">'private'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><virtualport</span><span class="perl_Others"> type=</span><span class="perl_String">'802.1Qbh'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><parameters</span><span class="perl_Others"> profileid=</span><span class="perl_String">'finance'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></virtualport></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.43. Devices - network interfaces- direct attachment to physical interfaces more additional parameters</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-attribute">profileid</code> attribute, contains the name of the port profile that is to be applied to this interface. This name is resolved by the port profile database into the network parameters from the port profile, and those network parameters will be applied to this interface.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-generic-ethernet-connection.html"><strong>Prev</strong>J.16.9.4. Generic Ethernet connection</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="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-pci-passthrough.html"><strong>Next</strong>J.16.9.6. PCI passthrough</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-generic-ethernet-connection.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-generic-ethernet-connection.html
new file mode 100644
index 0000000..9edd49c
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-generic-ethernet-connection.html
@@ -0,0 +1,26 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.4. Generic Ethernet connection</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-userspace-slirp-stack.html" title="J.16.9.3. Userspace SLIRP stack" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-direct-attachment-to-physical-device.html" title="J.16.9.5. Direct attachment to physical interfaces" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="
Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-userspace-slirp-stack.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-direct-attachment-to-physical-device.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-generic-ethernet-connection"><div class="titlepage"><div><div><h4 class="title">J.16.9.4. Generic Ethernet connection</h4></div></div></div><div class="para">
+ Provides a means for the administrator to execute an arbitrary script to connect the guest's network to the LAN. The guest will have a <code class="sgmltag-element">tun</code> device created with a name of <code class="sgmltag-element">vnetN</code>, which can also be overridden with the <code class="sgmltag-element">target</code> element. After creating the <code class="sgmltag-element">tun</code> device a shell script will be run which is expected to do whatever host network integration is required. By default this script is called <code class="filename">/etc/qemu-ifup</code> but can be overridden (refer to <a class="xref" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element.html">Section J.16.9.10, “Overriding the target element”</a>).
+ </div><div class="para">
+ The generic Ethernet connection parameters are defined in the following part of the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-gen-eth-con"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'ethernet'</span><span class="perl_Keyword">/></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'ethernet'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet7'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><script</span><span class="perl_Others"> path=</span><span class="perl_String">'/etc/qemu-ifup-mynet'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.40. Devices - network interfaces- generic Ethernet connection</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-userspace-slirp-stack.html"><strong>Prev</strong>J.16.9.3. Userspace SLIRP stack</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="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-direct-attachment-to-physical-device.html"><strong>Next</strong>J.16.9.5. Direct attachment to physical interfaces</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-multicast-tunnel.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-multicast-tunnel.html
new file mode 100644
index 0000000..6e97932
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-multicast-tunnel.html
@@ -0,0 +1,22 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.7. Multicast tunnel</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-pci-passthrough.html" title="J.16.9.6. PCI passthrough" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-tcp-tunnel.html" title="J.16.9.8. TCP tunnel" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></
a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-pci-passthrough.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-tcp-tunnel.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-multicast-tunnel"><div class="titlepage"><div><div><h4 class="title">J.16.9.7. Multicast tunnel</h4></div></div></div><div class="para">
+ A multicast group may be used to represent a virtual network. Any guest virtual machine whose network devices are within the same multicast group will talk to each other, even if they reside across miltiple physical hosts. This mode may be used as an unprivileged user. There is no default DNS or DHCP support and no outgoing network access. To provide outgoing network access, one of the guest virtual machines should have a second NIC which is connected to one of the first 4 network types in order to provide appropriate routing. The multicast protocol is compatible with protocols used by <code class="command">user mode</code> linux guests as well. Note that the source address used must be from the multicast address block. A multicast tunnel is created by manipulating the <code class="command">interface type</code> using a management tool and setting/changing it to <code class="sgmltag-element">mcast</code>, and providing a mac and source address. The result is shown in ch
anges made to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-multi-cast-tun"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'mcast'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">'52:54:00:6d:90:01'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> address=</span><span class="perl_String">'230.0.0.1'</span><span class="perl_Others"> port=</span><span class="perl_String">'5558'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.45. Devices - network interfaces- multicast tunnel</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-pci-passthrough.html"><strong>Prev</strong>J.16.9.6. PCI passthrough</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="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-tcp-tunnel.html"><strong>Next</strong>J.16.9.8. TCP tunnel</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element.html
new file mode 100644
index 0000000..8a98b5e
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element.html
@@ -0,0 +1,24 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.10. Overriding the target element</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-setting-nic-driver-specific-options.html" title="J.16.9.9. Setting NIC driver-specific options" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-boot-order.html" title="J.16.9.11. Specifying boot order" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/i
mages/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-setting-nic-driver-specific-options.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-boot-order.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element"><div class="titlepage"><div><div><h4 class="title">J.16.9.10. Overriding the target element</h4></div></div></div><div class="para">
+ To override the target element, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-overriding-the-target-element"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.48. Devices - network interfaces- overriding the target element</h6></div><br class="figure-break" /><div class="para">
+ If no target is specified, certain hypervisors will automatically generate a name for the created tun device. This name can be manually specifed, however the name must not start with either 'vnet' or 'vif', which are prefixes reserved by libvirt and certain hypervisors. Manually specified targets using these prefixes will be ignored.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-setting-nic-driver-specific-options.html"><strong>Prev</strong>J.16.9.9. Setting NIC driver-specific options</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="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-boot-order.html"><strong>Next</strong>J.16.9.11. Specifying boot order</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-pci-passthrough.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-pci-passthrough.html
new file mode 100644
index 0000000..a52c529
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-pci-passthrough.html
@@ -0,0 +1,30 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.6. PCI passthrough</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-direct-attachment-to-physical-device.html" title="J.16.9.5. Direct attachment to physical interfaces" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-multicast-tunnel.html" title="J.16.9.7. Multicast tunnel" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Con
tent/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-direct-attachment-to-physical-device.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-multicast-tunnel.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-pci-passthrough"><div class="titlepage"><div><div><h4 class="title">J.16.9.6. PCI passthrough</h4></div></div></div><div class="para">
+ A PCI network device (specified by the <code class="sgmltag-element">source</code> element) is directly assigned to the guest using generic device passthrough, after first optionally setting the device's MAC address to the configured value, and associating the device with an 802.1Qbh capable switch using an optionally specified <code class="sgmltag-element">virtualport</code> element (see the examples of virtualport given above for type='direct' network devices). Note that - due to limitations in standard single-port PCI ethernet card driver design - only SR-IOV (Single Root I/O Virtualization) virtual function (VF) devices can be assigned in this manner; to assign a standard single-port PCI or PCIe ethernet card to a guest, use the traditional <code class="sgmltag-element">hostdev</code> device definition
+ </div><div class="para">
+ Note that this "intelligent passthrough" of network devices is very similar to the functionality of a standard <code class="sgmltag-element">hostdev</code> device, the difference being that this method allows specifying a MAC address and <code class="sgmltag-attribute">virtualport</code> for the passed-through device. If these capabilities are not required, if you have a standard single-port PCI, PCIe, or USB network card that doesn't support SR-IOV (and hence would anyway lose the configured MAC address during reset after being assigned to the guest domain), or if you are using a version of libvirt older than 0.9.11, you should use standard <code class="sgmltag-attribute">hostdev</code> to assign the device to the guest instead of <code class="sgmltag-attribute">interface type='hostdev'/</code>.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-pci-pass"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'hostdev'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">'vfio'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'pci'</span><span class="perl_Others"> domain=</span><span class="perl_String">'0x0000'</span><span class="perl_Others"> bus=</span><span class="perl_String">'0x00'</span><span class="perl_Others"> slot=</span><span class="perl_String">'0x07'</span><span class="perl_Others"> function=</span><span class="perl_String">'0x0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></source></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">'52:54:00:6d:90:02'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><virtualport</span><span class="perl_Others"> type=</span><span class="perl_String">'802.1Qbh'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><parameters</span><span class="perl_Others"> profileid=</span><span class="perl_String">'finance'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></virtualport></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.44. Devices - network interfaces- PCI passthrough</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-direct-attachment-to-physical-device.html"><strong>Prev</strong>J.16.9.5. Direct attachment to physical interfaces</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="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-multicast-tunnel.html"><strong>Next</strong>J.16.9.7. Multicast tunnel</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-setting-nic-driver-specific-options.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-setting-nic-driver-specific-options.html
new file mode 100644
index 0000000..c50af1d
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-setting-nic-driver-specific-options.html
@@ -0,0 +1,45 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.9. Setting NIC driver-specific options</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-tcp-tunnel.html" title="J.16.9.8. TCP tunnel" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element.html" title="J.16.9.10. Overriding the target element" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png"
alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-tcp-tunnel.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-setting-nic-driver-specific-options"><div class="titlepage"><div><div><h4 class="title">J.16.9.9. Setting NIC driver-specific options</h4></div></div></div><div class="para">
+ Some NICs may have tunable driver-specific options. These options are set as attributes of the <code class="sgmltag-element">driver</code> sub-element of the interface definition. These options are set by using management toools to configuring the following sections of the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-nic-driver-options"><div class="figure-contents"><pre class="programlisting">
+
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><model</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">'vhost'</span><span class="perl_Others"> txmode=</span><span class="perl_String">'iothread'</span><span class="perl_Others"> ioeventfd=</span><span class="perl_String">'on'</span><span class="perl_Others"> event_idx=</span><span class="perl_String">'off'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.47. Devices - network interfaces- setting NIC driver-specific options</h6></div><br class="figure-break" /><div class="para">
+ Currently the following attributes are available for the "virtio" NIC driver:
+ </div><div class="table" id="table--libvirt-dom-xml-devices-Network-interfaces-setting-nic-driver-specific-options"><h6>Table J.19. virtio NIC driver elements</h6><div class="table-contents"><table summary="virtio NIC driver elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-attribute">name</code>
+ </td><td class="">
+ The optional <code class="sgmltag-attribute">name</code> attribute forces which type of backend driver to use. The value can be either <code class="sgmltag-attribute">qemu</code> (a user-space backend) or <code class="sgmltag-attribute">vhost</code> (a kernel backend, which requires the vhost module to be provided by the kernel); an attempt to require the vhost driver without kernel support will be rejected. The default setting is <code class="sgmltag-attribute">vhost</code> if the vhost driver present, but will silently fall back to <code class="sgmltag-attribute">qemu</code> if not.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">txmode</code>
+ </td><td class="">
+ Specifies how to handle transmission of packets when the transmit buffer is full. The value can be either <code class="sgmltag-attribute">iothread</code> or <code class="sgmltag-attribute">timer</code>. If set to <code class="sgmltag-attribute">iothread</code>, packet tx is all done in an iothread in the bottom half of the driver (this option translates into adding <code class="sgmltag-attvalue">"tx=bh"</code> to the <code class="sgmltag-attribute">qemu</code> commandline -device virtio-net-pci option). If set to <code class="sgmltag-attvalue">timer</code>, tx work is done in qemu, and if there is more tx data than can be sent at the present time, a timer is set before qemu moves on to do other things; when the timer fires, another attempt is made to send more data. In general you should leave this option alone, unless you are very certain you that changing it is an absolute necessity.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">ioeventfd</code>
+ </td><td class="">
+ Allows users to set domain I/O asynchronous handling for interface device. The default is left to the discretion of the hypervisor. Accepted values are <code class="sgmltag-attvalue">on</code> and <code class="sgmltag-attvalue">off </code>. Enabling this option allows qemu to execute a guest virtual machine while a separate thread handles I/O. Typically guest virtual machines experiencing high system CPU utilization during I/O will benefit from this. On the other hand, overloading the physical host may also increase guest I/O latency. Therefore, you should leave this option alone, unless you are very certain you that changing it is an absolute necessity.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">event_idx</code>
+ </td><td class="">
+ The event_idx attribute controls some aspects of device event processing. The value can be either <code class="sgmltag-attvalue">on</code> or <code class="sgmltag-attvalue">off</code>. Choosing <code class="sgmltag-attvalue">on</code>, reduces the number of interrupts and exits for the guest virtual machine. The default is <code class="sgmltag-attvalue">on</code>. In case there is a situation where this behavior is suboptimal, this attribute provides a way to force the feature off. You should leave this option alone, unless you are very certain you that changing it is an absolute necessity.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-tcp-tunnel.html"><strong>Prev</strong>J.16.9.8. TCP tunnel</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="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element.html"><strong>Next</strong>J.16.9.10. Overriding the target element</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-tcp-tunnel.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-tcp-tunnel.html
new file mode 100644
index 0000000..05b7974
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-tcp-tunnel.html
@@ -0,0 +1,27 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.8. TCP tunnel</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-multicast-tunnel.html" title="J.16.9.7. Multicast tunnel" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-setting-nic-driver-specific-options.html" title="J.16.9.9. Setting NIC driver-specific options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/i
mages/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-multicast-tunnel.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-setting-nic-driver-specific-options.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-tcp-tunnel"><div class="titlepage"><div><div><h4 class="title">J.16.9.8. TCP tunnel</h4></div></div></div><div class="para">
+ Creating a TCP client/server architecture is another way to provide a virtual network wher one guest virtual machine provides the server end of the network and all other guest virtual machines are configured as clients. All network traffic between the guest virtual machines is routed via the guest virtual machine that is configrured as the server. This model is also available for use to unprivileged users. There is no default DNS or DHCP support and no outgoing network access. To provide outgoing network access, one of the guest virtual machines should have a second NIC which is connected to one of the first 4 network types thereby providing the appropriate routing. A TCP tunnel is created by manipulating the <code class="sgmltag-element">interface type</code> using a management tool and setting/changing it to <code class="sgmltag-element">server</code> or <code class="sgmltag-element">client</code>, and providing a mac and source address. The result is shown in changes
made to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-tcp-tun"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'server'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">'52:54:00:22:c9:42'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> address=</span><span class="perl_String">'192.168.0.1'</span><span class="perl_Others"> port=</span><span class="perl_String">'5558'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'client'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">'52:54:00:8b:c9:51'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> address=</span><span class="perl_String">'192.168.0.1'</span><span class="perl_Others"> port=</span><span class="perl_String">'5558'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.46. Devices - network interfaces- TCP tunnel</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-multicast-tunnel.html"><strong>Prev</strong>J.16.9.7. Multicast tunnel</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="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-setting-nic-driver-specific-options.html"><strong>Next</strong>J.16.9.9. Setting NIC driver-specific options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-userspace-slirp-stack.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-userspace-slirp-stack.html
new file mode 100644
index 0000000..ab1520b
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-userspace-slirp-stack.html
@@ -0,0 +1,25 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.3. Userspace SLIRP stack</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-bridge-to-lan.html" title="J.16.9.2. Bridge to LAN" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-generic-ethernet-connection.html" title="J.16.9.4. Generic Ethernet connection" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png"
alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-bridge-to-lan.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-generic-ethernet-connection.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-userspace-slirp-stack"><div class="titlepage"><div><div><h4 class="title">J.16.9.3. Userspace SLIRP stack</h4></div></div></div><div class="para">
+ Setting the userspace SLIRP stack parameters provides a virtual LAN with NAT to the outside world. The virtual network has DHCP and DNS services and will give the guest virtual machine an IP addresses starting from 10.0.2.15. The default router will be 10.0.2.2 and the DNS server will be 10.0.2.3. This networking is the only option for unprivileged users who need their guest virtual machines to have outgoing access.
+ </div><div class="para">
+ The userspace SLIP stack parameters are defined in the following part of the domain XML::
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-usr-spc-slip"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'user'</span><span class="perl_Keyword">/></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'user'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">"00:11:22:33:44:55"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.39. Devices - network interfaces- Userspace SLIRP stack</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-bridge-to-lan.html"><strong>Prev</strong>J.16.9.2. Bridge to LAN</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="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-generic-ethernet-connection.html"><strong>Next</strong>J.16.9.4. Generic Ethernet connection</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-host-device-assignment-block-character-devices.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-host-device-assignment-block-character-devices.html
new file mode 100644
index 0000000..b144d630
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-host-device-assignment-block-character-devices.html
@@ -0,0 +1,61 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.6.2. Block / character devices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-host-device-assignment.html" title="J.16.6. Host device assignment" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-host-device-assignment.html" title="J.16.6. Host device assignment" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-redirected-devices.html" title="J.16.7. Redirected devices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul cl
ass="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-host-device-assignment.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-redirected-devices.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-host-device-assignment-block-character-devices"><div class="titlepage"><div><div><h4 class="title">J.16.6.2. Block / character devices </h4></div></div></div><div class="para">
+ The host's block / character devices can be passed through to the guest by using managment tools to modify the domain xml <code class="sgmltag-element">hostdev</code> element. Note that this is only possible with container based virtualization.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-host-device-assignment-blk"><div class="figure-contents"><pre class="programlisting">
+
+...
+<span class="perl_Keyword"><hostdev</span><span class="perl_Others"> mode=</span><span class="perl_String">'capabilities'</span><span class="perl_Others"> type=</span><span class="perl_String">'storage'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source></span>
+ <span class="perl_Keyword"><block></span>/dev/sdf1<span class="perl_Keyword"></block></span>
+ <span class="perl_Keyword"></source></span>
+<span class="perl_Keyword"></hostdev></span>
+...
+
+</pre></div><h6>Figure J.31. Devices - host device assignment block character devices</h6></div><br class="figure-break" /><div class="para">
+ An alternative approach is this:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-host-device-assignment-blk2"><div class="figure-contents"><pre class="programlisting">
+
+...
+<span class="perl_Keyword"><hostdev</span><span class="perl_Others"> mode=</span><span class="perl_String">'capabilities'</span><span class="perl_Others"> type=</span><span class="perl_String">'misc'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source></span>
+ <span class="perl_Keyword"><char></span>/dev/input/event3<span class="perl_Keyword"></char></span>
+ <span class="perl_Keyword"></source></span>
+<span class="perl_Keyword"></hostdev></span>
+...
+
+</pre></div><h6>Figure J.32. Devices - host device assignment block character devices alternative 1</h6></div><br class="figure-break" /><div class="para">
+ Another alternative approach is this:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-host-device-assignment-blk3"><div class="figure-contents"><pre class="programlisting">
+
+...
+<span class="perl_Keyword"><hostdev</span><span class="perl_Others"> mode=</span><span class="perl_String">'capabilities'</span><span class="perl_Others"> type=</span><span class="perl_String">'net'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source></span>
+ <span class="perl_Keyword"><interface></span>eth0<span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></source></span>
+<span class="perl_Keyword"></hostdev></span>
+...
+
+
+</pre></div><h6>Figure J.33. Devices - host device assignment block character devices alternative 2</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-host-device-assignement-block-character-devices"><h6>Table J.14. Block / character device elements</h6><div class="table-contents"><table summary="Block / character device elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-element">hostdev</code>
+ </td><td class="">
+ This is the main container for describing host devices. For block/character devices passthrough <code class="sgmltag-attribute">mode</code> is always <code class="sgmltag-element">capabilities</code> and <code class="sgmltag-attribute">type</code> is <code class="sgmltag-element">block</code> for a block device and <code class="sgmltag-element">char</code> for a character device.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">source</code>
+ </td><td class="">
+ This describes the device as seen from the host. For block devices, the path to the block device in the host OS is provided in the nested <code class="sgmltag-element">block</code> element, while for character devices the <code class="sgmltag-element">char</code> element is used
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-host-device-assignment.html"><strong>Prev</strong>J.16.6. Host device assignment</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="sub-section-libvirt-dom-xml-devices-redirected-devices.html"><strong>Next</strong>J.16.7. Redirected devices</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-interface-ROM-BIOS-configuration.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-interface-ROM-BIOS-configuration.html
new file mode 100644
index 0000000..2e70899
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-interface-ROM-BIOS-configuration.html
@@ -0,0 +1,25 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.12. Interface ROM BIOS configuration</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-boot-order.html" title="J.16.9.11. Specifying boot order" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-qos.html" title="J.16.9.13. Quality of service" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class
="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-boot-order.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-qos.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-interface-ROM-BIOS-configuration"><div class="titlepage"><div><div><h4 class="title">J.16.9.12. Interface ROM BIOS configuration</h4></div></div></div><div class="para">
+ To specify the ROM BIOS configuration settings, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-interface-ROM-BIOS-configuration"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><rom</span><span class="perl_Others"> bar=</span><span class="perl_String">'on'</span><span class="perl_Others"> file=</span><span class="perl_String">'/etc/fake/boot.bin'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.50. Interface ROM BIOS configuration</h6></div><br class="figure-break" /><div class="para">
+ For hypervisors which support it, you can change how a PCI Network device's ROM is presented to the guest virtual machine. The <code class="sgmltag-attribute">bar</code> attribute can be set to <code class="sgmltag-element">on</code> or <code class="sgmltag-element">off</code>, and determines whether or not the device's ROM will be visible in the guest's memory map. (In PCI documentation, the "rombar" setting controls the presence of the Base Address Register for the ROM). If no rom bar is specified, the qemu default will be used (older versions of qemu used a default of <code class="sgmltag-element">off</code>, while newer qemus have a default of <code class="sgmltag-element">on</code>). The optional <code class="sgmltag-element">file</code> attribute is used to point to a binary file to be presented to the guest as the device's ROM BIOS. This can be useful to provide an alternative boot ROM for a network device.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-boot-order.html"><strong>Prev</strong>J.16.9.11. Specifying boot order</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="sub-sub-section-libvirt-dom-xml-devices-qos.html"><strong>Next</strong>J.16.9.13. Quality of service</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-modifying-virtual-link-state.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-modifying-virtual-link-state.html
new file mode 100644
index 0000000..a0a547c
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-modifying-virtual-link-state.html
@@ -0,0 +1,25 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.15. Modifying virtual link state</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-setting-vlan-tag.html" title="J.16.9.14. Setting VLAN tag (on supported network types only)" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-input-devices.html" title="J.16.10. Input devices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></
a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-setting-vlan-tag.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-input-devices.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-modifying-virtual-link-state"><div class="titlepage"><div><div><h4 class="title">J.16.9.15. Modifying virtual link state</h4></div></div></div><div class="para">
+ This element provides means of setting state of the virtual network link. Possible values for attribute <code class="sgmltag-attribute">state</code> are <code class="sgmltag-attvalue">up</code> and <code class="sgmltag-attvalue">down</code>. If <code class="sgmltag-attvalue">down</code> is specified as the value, the interface behaves as if it had the network cable disconnected. Default behavior if this element is unspecified is to have the link state <code class="sgmltag-attvalue">up</code>.
+ </div><div class="para">
+ To specify the virtual link state configuration settings, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-dom-xml-devices-modifying-virtual-link-state"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><link</span><span class="perl_Others"> state=</span><span class="perl_String">'down'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><devices></span>
+ ...
+</pre></div><h6>Figure J.53. Modifying virtual link state</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-setting-vlan-tag.html"><strong>Prev</strong>J.16.9.14. Setting VLAN tag (on supported 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="sub-section-libvirt-dom-xml-devices-input-devices.html"><strong>Next</strong>J.16.10. Input devices</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-qos.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-qos.html
new file mode 100644
index 0000000..bf57dab
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-qos.html
@@ -0,0 +1,32 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.13. Quality of service</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-interface-ROM-BIOS-configuration.html" title="J.16.9.12. Interface ROM BIOS configuration" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-setting-vlan-tag.html" title="J.16.9.14. Setting VLAN tag (on supported network types only)" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/im
age_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-interface-ROM-BIOS-configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-setting-vlan-tag.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-qos"><div class="titlepage"><div><div><h4 class="title">J.16.9.13. Quality of service</h4></div></div></div><div class="para">
+ This section of the domain XML provides setting quality of service. Incoming and outgoing traffic can be shaped independently. The <code class="sgmltag-element">bandwidth</code> element can have at most one inbound and at most one outbound child elements. Leaving any of these children element out results in no QoS being applied on that traffic direction. Therefore, when you want to shape only domain's incoming traffic, use inbound only, and vice versa.
+ </div><div class="para">
+ Each of these elements has one mandatory attribute <code class="sgmltag-attribute">average</code> (or <code class="sgmltag-attribute">floor</code> as described below). <code class="sgmltag-attribute">average</code> specifies average bit rate on the interface being shaped. Then there are two optional attributes: <code class="sgmltag-attribute">peak</code>, which specifies maximum rate at which interface can send data, and <code class="sgmltag-attribute">burst</code>, which specifies the amount of bytes that can be burst at peak speed. Accepted values for attributes are integer numbers.
+ </div><div class="para">
+ The units for <code class="sgmltag-attribute">average</code> and <code class="sgmltag-attribute">peak</code> attributes are kilobytes per second, whereas <code class="sgmltag-attribute">burst</code> is only set in kilobytes. In addtion, inbound traffic can optionally have a <code class="sgmltag-attribute">floor</code> attribute. This guarantees minimal throughput for shaped interfaces. Using the <code class="sgmltag-attribute">floor</code> requires that all traffic goes through one point where QoS decisions can take place. As such it may only be used in cases where the <code class="sgmltag-element">interface type='network'/</code> with a <code class="sgmltag-element">forward</code> type of <code class="sgmltag-element">route</code>, <code class="sgmltag-element">nat</code>, or no forward at all). It should be noted that within a virtual network, all connected interfaces are required to have at least the inbound QoS set (<code class="sgmltag-element">average</code> at le
ast) but the floor attribute doesn't require specifying <code class="sgmltag-element">average</code>. However, <code class="sgmltag-element">peak</code> and <code class="sgmltag-element">burst</code> attributes still require <code class="sgmltag-element">average</code>. At the present time, ingress qdiscs may not have any classes, and therefore <code class="sgmltag-attribute">floor</code> may only be applied only on inbound and not outbound traffic.
+ </div><div class="para">
+ To specify the QoS configuration settings, use a managment tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-qos"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><bandwidth></span>
+ <span class="perl_Keyword"><inbound</span><span class="perl_Others"> average=</span><span class="perl_String">'1000'</span><span class="perl_Others"> peak=</span><span class="perl_String">'5000'</span><span class="perl_Others"> floor=</span><span class="perl_String">'200'</span><span class="perl_Others"> burst=</span><span class="perl_String">'1024'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><outbound</span><span class="perl_Others"> average=</span><span class="perl_String">'128'</span><span class="perl_Others"> peak=</span><span class="perl_String">'256'</span><span class="perl_Others"> burst=</span><span class="perl_String">'256'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></bandwidth></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><devices></span>
+ ...
+</pre></div><h6>Figure J.51. Quality of service</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-interface-ROM-BIOS-configuration.html"><strong>Prev</strong>J.16.9.12. Interface ROM BIOS 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="sub-sub-section-libvirt-dom-xml-devices-setting-vlan-tag.html"><strong>Next</strong>J.16.9.14. Setting VLAN tag (on supported network...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-setting-vlan-tag.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-setting-vlan-tag.html
new file mode 100644
index 0000000..1596588
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-setting-vlan-tag.html
@@ -0,0 +1,30 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.14. Setting VLAN tag (on supported network types only)</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-qos.html" title="J.16.9.13. Quality of service" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-modifying-virtual-link-state.html" title="J.16.9.15. Modifying virtual link state" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul
class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-qos.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-modifying-virtual-link-state.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-setting-vlan-tag"><div class="titlepage"><div><div><h4 class="title">J.16.9.14. Setting VLAN tag (on supported network types only)</h4></div></div></div><div class="para">
+ To specify the VLAN tag configuration settings, use a mangement tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-setting-vlan-tag"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'bridge'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><vlan></span>
+ <span class="perl_Keyword"><tag</span><span class="perl_Others"> id=</span><span class="perl_String">'42'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></vlan></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> bridge=</span><span class="perl_String">'ovsbr0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><virtualport</span><span class="perl_Others"> type=</span><span class="perl_String">'openvswitch'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><parameters</span><span class="perl_Others"> interfaceid=</span><span class="perl_String">'09b11c53-8b5c-4eeb-8f00-d84eaa0aaa4f'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></virtualport></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><devices></span>
+ ...
+
+</pre></div><h6>Figure J.52. Setting VLAN tag (on supported network types only)</h6></div><br class="figure-break" /><div class="para">
+ If (and only if) the network connection used by the guest supports vlan tagging transparent to the guest, an optional <code class="sgmltag-element">vlan</code> element can specify one or more vlan tags to apply to the guest's network traffic (openvswitch and <code class="sgmltag-element">type='hostdev'</code> SR-IOV interfaces do support transparent vlan tagging of guest traffic; everything else, including standard linux bridges and libvirt's own virtual networks, do not support it. 802.1Qbh (vn-link) and 802.1Qbg (VEPA) switches provide their own way (outside of libvirt) to tag guest traffic onto specific vlans.) To allow for specification of multiple tags (in the case of vlan trunking), a subelement, <code class="sgmltag-element">tag</code>, specifies which vlan tag to use (for example: <code class="sgmltag-attribute">tag id='42'/</code>. If an interface has more than one <code class="sgmltag-element">vlan</code> element defined, it is assumed that the user wants to d
o VLAN trunking using all the specified tags. In the case that vlan trunking with a single tag is desired, the optional attribute <code class="sgmltag-attribute">trunk='yes'</code> can be added to the toplevel vlan element.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-qos.html"><strong>Prev</strong>J.16.9.13. Quality of service</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="sub-sub-section-libvirt-dom-xml-devices-modifying-virtual-link-state.html"><strong>Next</strong>J.16.9.15. Modifying virtual link state</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-subsect-command-line-tools.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-subsect-command-line-tools.html
new file mode 100644
index 0000000..53e8566
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-subsect-command-line-tools.html
@@ -0,0 +1,22 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.11.3. Command line tools</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-adv-filt-topics.html" title="H.10.11. Advanced Filter Configuration Topics" /><link rel="prev" href="sub-sub-sect-lim-numb-conns.html" title="H.10.11.2. Limiting Number of Connections" /><link rel="next" href="sub-sub-sect-pre-exist-net-filter.html" title="H.10.11.4. Pre-existing network filters" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey=
"p" href="sub-sub-sect-lim-numb-conns.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-pre-exist-net-filter.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-subsect-command-line-tools"><div class="titlepage"><div><div><h4 class="title">H.10.11.3. Command line tools</h4></div></div></div><div class="para">
+ virsh has been extended with life-cycle support for network filters. All commands related to the network filtering subsystem start with the prefix <em class="parameter"><code>nwfilter</code></em>. The following commands are available:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">nwfilter-list</code> : lists UUIDs and names of all network filters
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">nwfilter-define</code> : defines a new network filter or updates an existing one (must supply a name)
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">nwfilter-undefine</code> : deletes a specified network filter (must supply a name). In addition, it cannot currently be in use
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">nwfilter-dumpxml</code> : displays a specified network filter (must supply a name)
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">nwfilter-edit</code> : edits a specified network filter (must supply a name)
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-lim-numb-conns.html"><strong>Prev</strong>H.10.11.2. Limiting Number of Connections</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="sub-sub-sect-pre-exist-net-filter.html"><strong>Next</strong>H.10.11.4. Pre-existing network filters</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/subsect-guest-synch-delimited.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/subsect-guest-synch-delimited.html
new file mode 100644
index 0000000..83a0031
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/subsect-guest-synch-delimited.html
@@ -0,0 +1,26 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.14.2. guest-sync-delimited</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-qemu-ga.html" title="25.14. QEMU Guest Agent Protocol" /><link rel="prev" href="sect-qemu-ga.html" title="25.14. QEMU Guest Agent Protocol" /><link rel="next" href="sect-limit-redirection.html" title="25.15. Setting a limit on device redirection" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-qemu-ga.html"><strong>Prev</strong></a><
/li><li class="next"><a accesskey="n" href="sect-limit-redirection.html"><strong>Next</strong></a></li></ul><div class="section" id="subsect-guest-synch-delimited"><div class="titlepage"><div><div><h3 class="title">25.14.2. guest-sync-delimited</h3></div></div></div><div class="para">
+ If <span class="package">qemu-ga</span> attempts to communicate with a client, and the client receives a partial response from a previous <span class="package">qemu-ga</span> instance, the client might misconstrue responses to guest-sync as being part of this previous request. For client implementations that treat newlines as a delimiter for <span class="package">qemu-ga</span> responses, use <code class="command">guest-synch-delimited</code>.
+ </div><div class="para">
+ Even in some cases where there are JSON stream-based implementations that do not rely on newline delimiters, it may be considered invasive to implement a client's response/JSON handling, as it is the same deadlock scenario described previously. Using the <code class="command">guest-sync-delimited</code> on the client, tells qemu-ga to place the same 0xFF character in front of the response, thereby preventing confusion.
+ </div><pre class="screen">
+> { "execute": "guest-sync-delimited", "arguments": { "id": 123456 } }
+< { "return": 123456}
+</pre><div class="para">
+ Actual hex values sent:
+ </div><pre class="screen">
+> 7b 27 65 78 65 63 75 74 65 27 3a 27 67 75 65 73 74 2d 73 79 6e 63 2d 64 65
+ 6c 69 6d 69 74 65 64 27 2c 27 61 72 67 75 6d 65 6e 74 73 27 3a 7b 27 69 64
+ 27 3a 31 32 33 34 35 36 7d 7d 0a
+< ff 7b 22 72 65 74 75 72 6e 22 3a 20 31 32 33 34 35 36 7d 0a
+</pre><div class="para">
+ As stated above, the request should also be preceded with a 0xFF to flush <span class="package">qemu-ga</span>'s parser state.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-qemu-ga.html"><strong>Prev</strong>25.14. QEMU Guest Agent Protocol</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-limit-redirection.html"><strong>Next</strong>25.15. Setting a limit on device redirection</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/vhostmd.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/vhostmd.html
new file mode 100644
index 0000000..8e3a295
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/vhostmd.html
@@ -0,0 +1,18 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 29. The Virtual Host Metrics Daemon (vhostmd)</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt02.html" title="Part II. Administration" /><link rel="prev" href="sect-Virtualization-Storage_Volumes-Deleting_volumes.html" title="28.4. Deleting and removing volumes" /><link rel="next" href="ch29s02.html" title="29.2. Configuration of vhostmd" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-Storage_Volumes-Deleting_vo
lumes.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch29s02.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="vhostmd" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 29. The Virtual Host Metrics Daemon (vhostmd)</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="vhostmd.html#idm2331248">29.1. Installing vhostmd on the host</a></span></dt><dt><span class="section"><a href="ch29s02.html">29.2. Configuration of vhostmd</a></span></dt><dt><span class="section"><a href="ch29s03.html">29.3. Starting and stopping the daemon</a></span></dt><dt><span class="section"><a href="ch29s04.html">29.4. Verifying that vhostmd is working from the host</a></span></dt><dt><span class="section"><a href="ch29s05.html">29.5. Configuring guests to see the metrics</a></span></dt><dt><span class="section"><a href="ch29s06.html">29.6. Using vm-dump-metrics in Fedora guests to verify oper
ation</a></span></dt></dl></div><div class="para">
+ <span class="application"><strong>vhostmd</strong></span> (the Virtual Host Metrics Daemon) allows virtual machines to see limited information about the host they are running on.
+ </div><div class="para">
+ In the host, a daemon (<span class="application"><strong>vhostmd</strong></span>) runs which writes metrics periodically into a disk image. This disk image is exported read-only to guests. Guests can read the disk image to see metrics. Simple synchronization stops guests from seeing out of date or corrupt metrics.
+ </div><div class="para">
+ The system administrator chooses which metrics the guests can see, and also which guests get to see the metrics at all.
+ </div><div class="section" id="idm2331248"><div class="titlepage"><div><div><h2 class="title" id="idm2331248">29.1. Installing vhostmd on the host</h2></div></div></div><div class="para">
+ The <span class="application"><strong>vhostmd</strong></span> package is available from RHN and is located in the Downloads area. It must be installed on each host where guests are required to get host metrics.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Storage_Volumes-Deleting_volumes.html"><strong>Prev</strong>28.4. Deleting and removing volumes</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="ch29s02.html"><strong>Next</strong>29.2. Configuration of vhostmd</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/virsh-migration-arguements.html b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/virsh-migration-arguements.html
new file mode 100644
index 0000000..4662fe1
--- /dev/null
+++ b/public_html/en-US/Fedora/19/html/Virtualization_Deployment_and_Administration_Guide/virsh-migration-arguements.html
@@ -0,0 +1,46 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.4.2. Additional options for the virsh migrate command</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html" title="20.4. Live KVM migration with virsh" /><link rel="prev" href="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html" title="20.4. Live KVM migration with virsh" /><link rel="next" href="sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager.html" title="20.5. Migrating with virt-manager" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><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-KVM_live_migration-Live_KVM_migration_with_virsh.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager.html"><strong>Next</strong></a></li></ul><div class="section" id="virsh-migration-arguements"><div class="titlepage"><div><div><h3 class="title">20.4.2. Additional options for the virsh migrate command</h3></div></div></div><div class="para">
+ In addition to <em class="replaceable"><code>--live</code></em>, virsh migrate accepts the following options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ --direct - used for direct migration
+ </div></li><li class="listitem"><div class="para">
+ --p2p - used for peer-2-peer migration
+ </div></li><li class="listitem"><div class="para">
+ --tunnelled - used for tunnelled migration
+ </div></li><li class="listitem"><div class="para">
+ --persistent - leaves the domain persistent on destination host
+ </div></li><li class="listitem"><div class="para">
+ --undefinesource - undefines the domain on the source host
+ </div></li><li class="listitem"><div class="para">
+ --suspend - leaves the domain paused on the destination host
+ </div></li><li class="listitem"><div class="para">
+ --copy-storage-all - indicates migration with non-shared storage with full disk copy
+ </div></li><li class="listitem"><div class="para">
+ --copy-storage-inc - indicates migration with non-shared storage with incremental copy (same base image shared between source and destination). In both cases the disk images have to exist on the destination host, the --copy-storage-.options only tell libvirt to transfer data from the images on source host to the images found at the same place on the destination host
+ </div></li><li class="listitem"><div class="para">
+ --change-protection - enforces that no incompatible configuration changes will be made to the domain while the migration is underway; this flag is implicitly enabled when supported by the hypervisor, but can be explicitly used to reject the migration if the hypervisor lacks change protection support.
+ </div></li><li class="listitem"><div class="para">
+ --unsafe - forces the migration to occur, ignoring all safety procedures.
+ </div></li><li class="listitem"><div class="para">
+ --verbose displays the progress of migration as it is occurring
+ </div></li><li class="listitem"><div class="para">
+ migrateuri - the migration URI which is usually omitted.
+ </div></li><li class="listitem"><div class="para">
+ --timeout seconds - forces a guest to suspend when the live migration counter exceeds N seconds. It can only be used with a live migration. Once the timeout is initiated, the migration continues on the suspended guest.
+ </div></li><li class="listitem"><div class="para">
+ dname - is used for renaming the domain to new name during migration, which also usually can be omitted
+ </div></li><li class="listitem"><div class="para">
+ s
+ </div></li><li class="listitem"><div class="para">
+ --xml file can be used to supply an alternative XML file for use on the destination to supply a larger set of changes to any host-specific portions of the domain XML, such as accounting for naming differences between source and destination in accessing underlying storage. This option is usually omitted.
+ </div></li></ul></div><div class="para">
+ Refer to the virsh man page for more information.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html"><strong>Prev</strong>20.4. 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="sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager.html"><strong>Next</strong>20.5. Migrating with virt-manager</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/19/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf b/public_html/en-US/Fedora/19/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf
new file mode 100644
index 0000000..fc89ce3
Binary files /dev/null and b/public_html/en-US/Fedora/19/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub b/public_html/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub
new file mode 100644
index 0000000..4df0d74
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/common.css b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/common.css
new file mode 100644
index 0000000..d7dc3f2
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/common.css
@@ -0,0 +1,1528 @@
+* {
+ widows: 2 !important;
+ orphans: 2 !important;
+}
+
+body, h1, h2, h3, h4, h5, h6, pre, li, div {
+ line-height: 1.29em;
+}
+
+body {
+ background-color: white;
+ margin:0 auto;
+ font-family: "liberation sans", "Myriad ", "Bitstream Vera Sans", "Lucida Grande", "Luxi Sans", "Trebuchet MS", helvetica, verdana, arial, sans-serif;
+ font-size:12px;
+ max-width:55em;
+ color:black;
+}
+
+body.toc_embeded {
+ /*for web hosting system only*/
+ margin-left: 300px;
+}
+
+object.toc, iframe.toc {
+ /*for web hosting system only*/
+ border-style:none;
+ position:fixed;
+ width:290px;
+ height:99.99%;
+ top:0;
+ left:0;
+ z-index: 100;
+ border-style:none;
+ border-right:1px solid #999;
+}
+
+/* Hide web menu */
+
+body.notoc {
+ margin-left: 3em;
+}
+
+iframe.notoc {
+ border-style:none;
+ border: none;
+ padding: 0em;
+ position:fixed;
+ width: 21px;
+ height: 29px;
+ top: 0px;
+ left:0;
+ overflow: hidden;
+ margin: 0em;
+ margin-left: -3px;
+}
+/* End hide web menu */
+
+/* desktop styles */
+body.desktop {
+ margin-left: 26em;
+}
+
+body.desktop .book > .toc {
+ display:block;
+ width:24em;
+ height:99%;
+ position:fixed;
+ overflow:auto;
+ top:0px;
+ left:0px;
+ padding-left:1em;
+ background-color:#EEEEEE;
+}
+
+.toc {
+ line-height:1.35em;
+}
+
+.toc .glossary,
+.toc .chapter, .toc .appendix {
+ margin-top:1em;
+}
+
+.toc .part {
+ margin-top:1em;
+ display:block;
+}
+
+span.glossary,
+span.appendix {
+ display:block;
+ margin-top:0.5em;
+}
+
+div {
+ padding-top:0px;
+}
+
+div.section {
+ padding-top:1em;
+}
+
+p, div.para, div.formalpara {
+ padding-top:0px;
+ margin-top:0.3em;
+ padding-bottom:0px;
+ margin-bottom:1em;
+}
+
+/*Links*/
+a {
+ outline: none;
+}
+
+a:link {
+ text-decoration:none;
+ border-bottom: 1px dotted ;
+ color:#3366cc;
+}
+
+a:visited {
+ text-decoration:none;
+ border-bottom: 1px dotted ;
+ color:#003366;
+}
+
+div.longdesc-link {
+ float:right;
+ color:#999;
+}
+
+.toc a, .qandaset a {
+ font-weight:normal;
+ border:none;
+}
+
+.toc a:hover, .qandaset a:hover
+{
+ border-bottom: 1px dotted;
+}
+
+/*headings*/
+h1, h2, h3, h4, h5, h6 {
+ color: #336699;
+ margin-top: 0em;
+ margin-bottom: 0em;
+ background-color: transparent;
+ page-break-inside: avoid;
+ page-break-after: avoid;
+}
+
+h1 {
+ font-size:2.0em;
+}
+
+.titlepage h1.title {
+ font-size: 3.0em;
+ padding-top: 1em;
+ text-align:left;
+}
+
+.book > .titlepage h1.title {
+ text-align:center;
+}
+
+.article > .titlepage h1.title {
+ text-align:center;
+}
+
+.set .titlepage > div > div > h1.title {
+ text-align:center;
+}
+
+.producttitle {
+ margin-top: 0em;
+ margin-bottom: 0em;
+ font-size: 3.0em;
+ font-weight: bold;
+ background: #003d6e url(../images/h1-bg.png) top left repeat-x;
+ color: white;
+ text-align: center;
+ padding: 0.7em;
+}
+
+.titlepage .corpauthor {
+ margin-top: 1em;
+ text-align: center;
+}
+
+.section h1.title {
+ font-size: 1.6em;
+ padding: 0em;
+ color: #336699;
+ text-align: left;
+ background: white;
+}
+
+h2 {
+ font-size:1.6em;
+}
+
+
+h2.subtitle, h3.subtitle {
+ margin-top: 1em;
+ margin-bottom: 1em;
+ font-size: 1.4em;
+ text-align: center;
+}
+
+.preface > div > div > div > h2.title {
+ margin-top: 1em;
+ font-size: 2.0em;
+}
+
+.appendix h2 {
+ margin-top: 1em;
+ font-size: 2.0em;
+}
+
+
+
+h3 {
+ font-size:1.3em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+h4 {
+ font-size:1.1em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+
+h5 {
+ font-size:1em;
+}
+
+h6 {
+ font-size:1em;
+}
+
+h5.formalpara {
+ font-size:1em;
+ margin-top:2em;
+ margin-bottom:.8em;
+}
+
+.abstract h6 {
+ margin-top:1em;
+ margin-bottom:.5em;
+ font-size:2em;
+}
+
+/*element rules*/
+hr {
+ border-collapse: collapse;
+ border-style:none;
+ border-top: 1px dotted #ccc;
+ width:100%;
+ margin-top: 3em;
+}
+
+/* web site rules */
+ul.languages, .languages li {
+ display:inline;
+ padding:0em;
+}
+
+.languages li a {
+ padding:0em .5em;
+ text-decoration: none;
+}
+
+.languages li p, .languages li div.para {
+ display:inline;
+}
+
+.languages li a:link, .languages li a:visited {
+ color:#444;
+}
+
+.languages li a:hover, .languages li a:focus, .languages li a:active {
+ color:black;
+}
+
+ul.languages {
+ display:block;
+ background-color:#eee;
+ padding:.5em;
+}
+
+/*supporting stylesheets*/
+
+/*unique to the webpage only*/
+.books {
+ position:relative;
+}
+
+.versions li {
+ width:100%;
+ clear:both;
+ display:block;
+}
+
+a.version {
+ font-size:2em;
+ text-decoration:none;
+ width:100%;
+ display:block;
+ padding:1em 0em .2em 0em;
+ clear:both;
+}
+
+a.version:before {
+ content:"Version";
+ font-size:smaller;
+}
+
+a.version:visited, a.version:link {
+ color:#666;
+}
+
+a.version:focus, a.version:hover {
+ color:black;
+}
+
+.books {
+ display:block;
+ position:relative;
+ clear:both;
+ width:100%;
+}
+
+.books li {
+ display:block;
+ width:200px;
+ float:left;
+ position:relative;
+ clear: none ;
+}
+
+.books .html {
+ width:170px;
+ display:block;
+}
+
+.books .pdf {
+ position:absolute;
+ left:170px;
+ top:0px;
+ font-size:smaller;
+}
+
+.books .pdf:link, .books .pdf:visited {
+ color:#555;
+}
+
+.books .pdf:hover, .books .pdf:focus {
+ color:#000;
+}
+
+.books li a {
+ text-decoration:none;
+}
+
+.books li a:hover {
+ color:black;
+}
+
+/*products*/
+.products li {
+ display: block;
+ width:300px;
+ float:left;
+}
+
+.products li a {
+ width:300px;
+ padding:.5em 0em;
+}
+
+.products ul {
+ clear:both;
+}
+
+/*revision history*/
+.revhistory {
+ display:block;
+}
+
+.revhistory table {
+ background-color:transparent;
+ border-color:#fff;
+ padding:0em;
+ margin: 0;
+ border-collapse:collapse;
+ border-style:none;
+}
+
+.revhistory td {
+ text-align :left;
+ padding:0em;
+ border: none;
+ border-top: 1px solid #fff;
+ font-weight: bold;
+}
+
+.revhistory .simplelist td {
+ font-weight: normal;
+}
+
+.revhistory .simplelist {
+ margin-bottom: 1.5em;
+ margin-left: 1em;
+}
+
+.revhistory table th {
+ display: none;
+}
+
+
+/*credits*/
+.authorgroup div {
+ clear:both;
+ text-align: center;
+}
+
+h3.author {
+ margin: 0em;
+ padding: 0em;
+ padding-top: 1em;
+}
+
+.authorgroup h4 {
+ padding: 0em;
+ margin: 0em;
+ padding-top: 1em;
+ margin-top: 1em;
+}
+
+.author,
+.editor,
+.translator,
+.othercredit,
+.contrib {
+ display: block;
+}
+
+.revhistory .author {
+ display: inline;
+}
+
+.othercredit h3 {
+ padding-top: 1em;
+}
+
+
+.othercredit {
+ margin:0em;
+ padding:0em;
+}
+
+.releaseinfo {
+ clear: both;
+}
+
+.copyright {
+ margin-top: 1em;
+}
+
+/* qanda sets */
+.answer {
+ margin-bottom:1em;
+ border-bottom:1px dotted #ccc;
+}
+
+.qandaset .toc {
+ border-bottom:1px dotted #ccc;
+}
+
+.question {
+ font-weight:bold;
+}
+
+.answer .data, .question .data {
+ padding-left: 2.6em;
+}
+
+.answer label, .question label {
+ float:left;
+ font-weight:bold;
+}
+
+/* inline syntax highlighting */
+.perl_Alert {
+ color: #0000ff;
+}
+
+.perl_BaseN {
+ color: #007f00;
+}
+
+.perl_BString {
+ color: #5C3566;
+}
+
+.perl_Char {
+ color: #ff00ff;
+}
+
+.perl_Comment {
+ color: #FF00FF;
+}
+
+
+.perl_DataType {
+ color: #0000ff;
+}
+
+
+.perl_DecVal {
+ color: #00007f;
+}
+
+
+.perl_Error {
+ color: #ff0000;
+}
+
+
+.perl_Float {
+ color: #00007f;
+}
+
+
+.perl_Function {
+ color: #007f00;
+}
+
+
+.perl_IString {
+ color: #5C3566;
+}
+
+
+.perl_Keyword {
+ color: #002F5D;
+}
+
+
+.perl_Operator {
+ color: #ffa500;
+}
+
+
+.perl_Others {
+ color: #b03060;
+}
+
+
+.perl_RegionMarker {
+ color: #96b9ff;
+}
+
+
+.perl_Reserved {
+ color: #9b30ff;
+}
+
+
+.perl_String {
+ color: #5C3566;
+}
+
+
+.perl_Variable {
+ color: #0000ff;
+}
+
+
+.perl_Warning {
+ color: #0000ff;
+}
+
+/*Lists*/
+ul {
+ padding-left:1.6em;
+ list-style-image:url(../images/dot.png);
+ list-style-type: circle;
+}
+
+ul ul {
+ list-style-image:url(../images/dot2.png);
+ list-style-type: circle;
+}
+
+ol {
+ list-style-image:none;
+ list-style-type: decimal;
+}
+
+ol ol {
+ list-style-type: lower-alpha;
+}
+
+ol.arabic {
+ list-style-type: decimal;
+}
+
+ol.loweralpha {
+ list-style-type: lower-alpha;
+}
+
+ol.lowerroman {
+ list-style-type: lower-roman;
+}
+
+ol.upperalpha {
+ list-style-type: upper-alpha;
+}
+
+ol.upperroman {
+ list-style-type: upper-roman;
+}
+
+dt {
+ font-weight:bold;
+ margin-bottom:0em;
+ padding-bottom:0em;
+}
+
+dd {
+ margin:0em;
+ margin-left:2em;
+ padding-top:0em;
+ padding-bottom: 1em;
+}
+
+li {
+ padding-top:0px;
+ margin-top:0em;
+ padding-bottom:0px;
+ margin-bottom:0.4em;
+}
+
+li p, li div.para {
+ padding-top:0px;
+ margin-top:0em;
+ padding-bottom:0px;
+ margin-bottom:0.3em;
+}
+
+/*images*/
+img {
+ display:block;
+ margin: 2em 0;
+}
+
+.inlinemediaobject, .inlinemediaobject img {
+ display:inline;
+ margin:0em;
+}
+
+.figure img {
+ display:block;
+ margin:0;
+ page-break-inside: avoid;
+}
+
+.figure .title {
+ margin:0em;
+ margin-bottom:2em;
+ padding:0px;
+}
+
+/*document modes*/
+.confidential {
+ background-color:#900;
+ color:White;
+ padding:.5em .5em;
+ text-transform:uppercase;
+ text-align:center;
+}
+
+.longdesc-link {
+ display:none;
+}
+
+.longdesc {
+ display:none;
+}
+
+.prompt {
+ padding:0em .3em;
+}
+
+/*user interface styles*/
+.screen .replaceable {
+}
+
+.guibutton, .guilabel {
+ font-family: "liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight: bold;
+ white-space: nowrap;
+}
+
+.example {
+ background-color: #ffffff;
+ border-left: 3px solid #aaaaaa;
+ padding-top: 1em;
+ padding-bottom: 0.1em;
+}
+
+.example h6 {
+ padding-left: 10px;
+}
+
+.example-contents {
+ padding-left: 10px;
+ background-color: #ffffff;
+}
+
+.example-contents .para {
+/* padding: 10px;*/
+}
+
+/*terminal/console text*/
+.computeroutput,
+.option {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight:bold;
+}
+
+.replaceable {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-style: italic;
+}
+
+.command, .filename, .keycap, .classname, .literal {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight:bold;
+}
+
+/* no bold in toc */
+.toc * {
+ font-weight: inherit;
+}
+
+pre {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ display:block;
+ background-color: #f5f5f5;
+ color: #000000;
+ border: 1px solid #aaaaaa;
+ margin-bottom: 0.3em;
+ padding:.5em 1em;
+ white-space: pre-wrap; /* css-3 */
+ white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
+ white-space: -pre-wrap; /* Opera 4-6 */
+ white-space: -o-pre-wrap; /* Opera 7 */
+ word-wrap: break-word; /* Internet Explorer 5.5+ */
+ font-size: 0.9em;
+}
+
+pre .replaceable,
+pre .keycap {
+}
+
+code {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+/* white-space: nowrap;*/
+ white-space: pre-wrap;
+ word-wrap: break-word;
+ font-weight:bold;
+}
+
+.parameter code {
+ display: inline;
+ white-space: pre-wrap; /* css-3 */
+ white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
+ white-space: -pre-wrap; /* Opera 4-6 */
+ white-space: -o-pre-wrap; /* Opera 7 */
+ word-wrap: break-word; /* Internet Explorer 5.5+ */
+}
+
+/*Notifications*/
+div.warning:before {
+ content:url(../images/warning.png);
+ padding-left: 5px;
+}
+
+div.note:before {
+ content:url(../images/note.png);
+ padding-left: 5px;
+}
+
+div.important:before {
+ content:url(../images/important.png);
+ padding-left: 5px;
+}
+
+div.warning, div.note, div.important {
+ color: black;
+ margin: 0em;
+ padding: 0em;
+ background: none;
+ background-color: white;
+ margin-bottom: 1em;
+ border-bottom: 1px solid #aaaaaa;
+ page-break-inside: avoid;
+}
+
+div.warning h2, div.note h2,div.important h2 {
+ margin: 0em;
+ padding: 0em;
+ color: #eeeeec;
+ padding-top: 0px;
+ padding-bottom: 0px;
+ height: 1.4em;
+ line-height: 1.4em;
+ font-size: 1.4em;
+ display:inline;
+}
+
+div.admonition_header {
+ clear: both;
+ margin: 0em;
+ padding: 0em;
+ margin-top: -3.3em;
+ padding-left: 58px;
+ line-height: 1.0em;
+ font-size: 1.0em;
+}
+
+div.warning div.admonition_header {
+ background: url(../images/red.png) top left repeat-x;
+ background-color: #590000;
+}
+
+div.note div.admonition_header {
+ background: url(../images/green.png) top right repeat-x;
+ background-color: #597800;
+}
+
+div.important div.admonition_header {
+ background: url(../images/yellow.png) top right repeat-x;
+ background-color: #a6710f;
+}
+
+div.warning p, div.warning div.para,
+div.note p, div.note div.para,
+div.important p, div.important div.para {
+ padding: 0em;
+ margin: 0em;
+}
+
+div.admonition {
+ border: none;
+ border-left: 1px solid #aaaaaa;
+ border-right: 1px solid #aaaaaa;
+ padding:0em;
+ margin:0em;
+ padding-top: 1.5em;
+ padding-bottom: 1em;
+ padding-left: 2em;
+ padding-right: 1em;
+ background-color: #eeeeec;
+ -moz-border-radius: 0px;
+ -webkit-border-radius: 0px;
+ border-radius: 0px;
+}
+
+/*Page Title*/
+#title {
+ display:block;
+ height:45px;
+ padding-bottom:1em;
+ margin:0em;
+}
+
+#title a.left{
+ display:inline;
+ border:none;
+}
+
+#title a.left img{
+ border:none;
+ float:left;
+ margin:0em;
+ margin-top:.7em;
+}
+
+#title a.right {
+ padding-bottom:1em;
+}
+
+#title a.right img {
+ border:none;
+ float:right;
+ margin:0em;
+ margin-top:.7em;
+}
+
+/*Table*/
+div.table {
+ page-break-inside: avoid;
+}
+
+table {
+ border:1px solid #6c614b;
+ width:100%;
+ border-collapse:collapse;
+}
+
+table.simplelist, .calloutlist table {
+ border-style: none;
+}
+
+table th {
+ text-align:left;
+ background-color:#6699cc;
+ padding:.3em .5em;
+ color:white;
+}
+
+table td {
+ padding:.15em .5em;
+}
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+table th p:first-child, table td p:first-child, table li p:first-child,
+table th div.para:first-child, table td div.para:first-child, table li div.para:first-child {
+ margin-top:0em;
+ padding-top:0em;
+ display:inline;
+}
+
+th, td {
+ border-style:none;
+ vertical-align: top;
+ border: 1px solid #000;
+}
+
+.simplelist th, .simplelist td {
+ border: none;
+}
+
+table table td {
+ border-bottom:1px dotted #aaa;
+ background-color:white;
+ padding:.6em 0em;
+}
+
+table table {
+ border:1px solid white;
+}
+
+td.remarkval {
+ color:#444;
+}
+
+td.fieldval {
+ font-weight:bold;
+}
+
+.lbname, .lbtype, .lbdescr, .lbdriver, .lbhost {
+ color:white;
+ font-weight:bold;
+ background-color:#999;
+ width:120px;
+}
+
+td.remarkval {
+ width:230px;
+}
+
+td.tname {
+ font-weight:bold;
+}
+
+th.dbfield {
+ width:120px;
+}
+
+th.dbtype {
+ width:70px;
+}
+
+th.dbdefault {
+ width:70px;
+}
+
+th.dbnul {
+ width:70px;
+}
+
+th.dbkey {
+ width:70px;
+}
+
+span.book {
+ margin-top:4em;
+ display:block;
+ font-size:11pt;
+}
+
+span.book a{
+ font-weight:bold;
+}
+span.chapter {
+ display:block;
+ margin-top:0.5em;
+}
+
+table.simplelist td, .calloutlist table td {
+ border-style: none;
+}
+
+/*Breadcrumbs*/
+#breadcrumbs ul li.first:before {
+ content:" ";
+}
+
+#breadcrumbs {
+ color:#900;
+ padding:3px;
+ margin-bottom:25px;
+}
+
+#breadcrumbs ul {
+ margin-left:0;
+ padding-left:0;
+ display:inline;
+ border:none;
+}
+
+#breadcrumbs ul li {
+ margin-left:0;
+ padding-left:2px;
+ border:none;
+ list-style:none;
+ display:inline;
+}
+
+#breadcrumbs ul li:before {
+ content:"\0020 \0020 \0020 \00BB \0020";
+ color:#333;
+}
+
+/*index*/
+.glossary h3,
+.index h3 {
+ font-size: 2em;
+ color:#aaa;
+ margin:0em;
+}
+
+.indexdiv {
+ margin-bottom:1em;
+}
+
+.glossary dt,
+.index dt {
+ color:#444;
+ padding-top:.5em;
+}
+
+.glossary dl dl dt,
+.index dl dl dt {
+ color:#777;
+ font-weight:normal;
+ padding-top:0em;
+}
+
+.index dl dl dt:before {
+ content:"- ";
+ color:#ccc;
+}
+
+/*changes*/
+.footnote {
+ font-size: .7em;
+ margin:0em;
+ color:#222;
+}
+
+table .footnote {
+}
+
+sup {
+ color:#999;
+ margin:0em;
+ padding:0em;
+ line-height: .4em;
+ font-size: 1em;
+ padding-left:0em;
+}
+
+.footnote {
+ position:relative;
+}
+
+.footnote sup {
+ color:#e3dcc0;
+ position:absolute;
+ left: .4em;
+}
+
+.footnote sup a:link,
+.footnote sup a:visited {
+ color:#92917d;
+ text-decoration:none;
+}
+
+.footnote:hover sup a {
+ text-decoration:none;
+}
+
+.footnote p,.footnote div.para {
+ padding-left:2em;
+}
+
+.footnote a:link,
+.footnote a:visited {
+ color:#00537c;
+}
+
+.footnote a:hover {
+}
+
+/**/
+div.chapter {
+ margin-top:3em;
+ page-break-inside: avoid;
+}
+
+div.preface {
+ page-break-inside: avoid;
+}
+
+div.section {
+ margin-top:1em;
+ page-break-inside: auto;
+}
+
+div.note .replaceable,
+div.important .replaceable,
+div.warning .replaceable,
+div.note .keycap,
+div.important .keycap,
+div.warning .keycap
+{
+}
+
+ul li p:last-child, ul li div.para:last-child {
+ margin-bottom:0em;
+ padding-bottom:0em;
+}
+
+/*document navigation*/
+.docnav a, .docnav strong {
+ border:none;
+ text-decoration:none;
+ font-weight:normal;
+}
+
+.docnav {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+ position:relative;
+ width:100%;
+ padding-bottom:2em;
+ padding-top:1em;
+ border-top:1px dotted #ccc;
+}
+
+.docnav li {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+ display:inline;
+ font-size:.8em;
+}
+
+.docnav li:before {
+ content:" ";
+}
+
+.docnav li.previous, .docnav li.next {
+ position:absolute;
+ top:1em;
+}
+
+.docnav li.up, .docnav li.home {
+ margin:0em 1.5em;
+}
+
+.docnav li.previous {
+ left:0px;
+ text-align:left;
+}
+
+.docnav li.next {
+ right:0px;
+ text-align:right;
+}
+
+.docnav li.previous strong, .docnav li.next strong {
+ height:22px;
+ display:block;
+}
+
+.docnav {
+ margin:0 auto;
+ text-align:center;
+}
+
+.docnav li.next a strong {
+ background: url(../images/stock-go-forward.png) top right no-repeat;
+ padding-top:3px;
+ padding-bottom:4px;
+ padding-right:28px;
+ font-size:1.2em;
+}
+
+.docnav li.previous a strong {
+ background: url(../images/stock-go-back.png) top left no-repeat;
+ padding-top:3px;
+ padding-bottom:4px;
+ padding-left:28px;
+ padding-right:0.5em;
+ font-size:1.2em;
+}
+
+.docnav li.home a strong {
+ background: url(../images/stock-home.png) top left no-repeat;
+ padding:5px;
+ padding-left:28px;
+ font-size:1.2em;
+}
+
+.docnav li.up a strong {
+ background: url(../images/stock-go-up.png) top left no-repeat;
+ padding:5px;
+ padding-left:28px;
+ font-size:1.2em;
+}
+
+.docnav a:link, .docnav a:visited {
+ color:#666;
+}
+
+.docnav a:hover, .docnav a:focus, .docnav a:active {
+ color:black;
+}
+
+.docnav a {
+ max-width: 10em;
+ overflow:hidden;
+}
+
+.docnav a:link strong {
+ text-decoration:none;
+}
+
+.docnav {
+ margin:0 auto;
+ text-align:center;
+}
+
+ul.docnav {
+ margin-bottom: 1em;
+}
+/* Reports */
+.reports ul {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+}
+
+.reports li{
+ margin:0em;
+ padding:0em;
+}
+
+.reports li.odd {
+ background-color: #eeeeee;
+ margin:0em;
+ padding:0em;
+}
+
+.reports dl {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ float:right;
+ margin-right: 17em;
+ margin-top:-1.3em;
+}
+
+.reports dt {
+ display:inline;
+ margin:0em;
+ padding:0em;
+}
+
+.reports dd {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ padding-right:.5em;
+}
+
+.reports h2, .reports h3{
+ display:inline;
+ padding-right:.5em;
+ font-size:10pt;
+ font-weight:normal;
+}
+
+.reports div.progress {
+ display:inline;
+ float:right;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ margin:0em;
+ margin-top:-1.3em;
+ padding:0em;
+ border:none;
+}
+
+/*uniform*/
+body.results, body.reports {
+ max-width:57em ;
+ padding:0em;
+}
+
+/*Progress Bar*/
+div.progress {
+ display:block;
+ float:left;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ height:1em;
+}
+
+div.progress span {
+ height:1em;
+ float:left;
+}
+
+div.progress span.translated {
+ background:#6c3 url(../images/shine.png) top left repeat-x;
+}
+
+div.progress span.fuzzy {
+ background:#ff9f00 url(../images/shine.png) top left repeat-x;
+}
+
+
+/*Results*/
+
+.results ul {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+}
+
+.results li{
+ margin:0em;
+ padding:0em;
+}
+
+.results li.odd {
+ background-color: #eeeeee;
+ margin:0em;
+ padding:0em;
+}
+
+.results dl {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ float:right;
+ margin-right: 17em;
+ margin-top:-1.3em;
+}
+
+.results dt {
+ display:inline;
+ margin:0em;
+ padding:0em;
+}
+
+.results dd {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ padding-right:.5em;
+}
+
+.results h2, .results h3 {
+ display:inline;
+ padding-right:.5em;
+ font-size:10pt;
+ font-weight:normal;
+}
+
+.results div.progress {
+ display:inline;
+ float:right;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ margin:0em;
+ margin-top:-1.3em;
+ padding:0em;
+ border:none;
+}
+
+/* Dirty EVIL Mozilla hack for round corners */
+pre {
+ -moz-border-radius:11px;
+ -webkit-border-radius:11px;
+ border-radius: 11px;
+ page-break-inside: avoid;
+}
+
+.example {
+ -moz-border-radius:0px;
+ -webkit-border-radius:0px;
+ border-radius: 0px;
+ page-break-inside: avoid;
+}
+
+.package, .citetitle {
+ font-style: italic;
+}
+
+.titlepage .edition {
+ color: #336699;
+ background-color: transparent;
+ margin-top: 1em;
+ margin-bottom: 1em;
+ font-size: 1.4em;
+ font-weight: bold;
+ text-align: center;
+}
+
+span.remark {
+ background-color: #ff00ff;
+}
+
+.draft {
+ background-image: url(../images/watermark-draft.png);
+ background-repeat: repeat-y;
+ background-position: center;
+}
+
+.foreignphrase {
+ font-style: inherit;
+}
+
+dt {
+ clear:both;
+}
+
+dt img {
+ border-style: none;
+ max-width: 112px;
+}
+
+dt object {
+ max-width: 112px;
+}
+
+dt .inlinemediaobject, dt object {
+ display: inline;
+ float: left;
+ margin-bottom: 1em;
+ padding-right: 1em;
+ width: 112px;
+}
+
+dl:after {
+ display: block;
+ clear: both;
+ content: "";
+}
+
+.toc dd {
+ padding-bottom: 0em;
+ margin-bottom: 1em;
+ padding-left: 1.3em;
+ margin-left: 0em;
+}
+
+div.toc > dl > dt {
+ padding-bottom: 0em;
+ margin-bottom: 0em;
+ margin-top: 1em;
+}
+
+
+.strikethrough {
+ text-decoration: line-through;
+}
+
+.underline {
+ text-decoration: underline;
+}
+
+.calloutlist img, .callout {
+ padding: 0em;
+ margin: 0em;
+ width: 12pt;
+ display: inline;
+ vertical-align: middle;
+}
+
+.stepalternatives {
+ list-style-image: none;
+ list-style-type: none;
+}
+
+
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/default.css b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/default.css
new file mode 100644
index 0000000..bf38ebb
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/default.css
@@ -0,0 +1,3 @@
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/lang.css b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/lang.css
new file mode 100644
index 0000000..81c3115
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/lang.css
@@ -0,0 +1,2 @@
+/* place holder */
+
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/menu.css b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/menu.css
new file mode 100644
index 0000000..f574cc5
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/menu.css
@@ -0,0 +1,48 @@
+a:link {
+ color:#0066cc;
+}
+
+a:visited {
+ color:#6699cc;
+}
+
+h1,h2,h3,h4,h5,h6 {
+ color:#a70000;
+}
+
+div.producttitle {
+ color:#a70000;
+}
+
+.section h1.title {
+ color:#a70000;
+}
+
+table {
+ border:1px solid #aaa;
+}
+
+table th {
+ background-color:#900;
+}
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+.revhistory table th {
+ color:#a70000;
+}
+
+.titlepage .edition {
+ color: #a70000;
+}
+
+span.remark{
+ background-color: #ffff00;
+}
+
+.home{
+ color: #a70000;
+}
+
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/overrides.css b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/overrides.css
new file mode 100644
index 0000000..db64f48
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/overrides.css
@@ -0,0 +1,55 @@
+a:link {
+ color:#0066cc;
+}
+
+a:hover, a:active {
+ color:#003366;
+}
+
+a:visited {
+ color:#6699cc;
+}
+
+
+h1 {
+ color:#3c6eb4
+}
+
+.producttitle {
+ background: #3c6eb4 url(../images/h1-bg.png) top left repeat;
+}
+
+.section h1.title {
+ color:#3c6eb4;
+}
+
+
+h2,h3,h4,h5,h6 {
+ color:#3c6eb4;
+}
+
+table {
+ border:1px solid #3c6eb4;
+}
+
+table th {
+ background-color:#3c6eb4;
+}
+
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+.term{
+ color:#3c6eb4
+}
+
+.revhistory table th {
+ color:#3c6eb4;
+}
+
+.edition {
+ color: #3c6eb4;
+}
+
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/pdf.css b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/pdf.css
new file mode 100644
index 0000000..cbeab47
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/pdf.css
@@ -0,0 +1,138 @@
+
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
+
+/* Cover Page styles */
+
+html {
+ height: 260mm;
+}
+
+body.cover {
+ height: 100%;
+ background-color: white;
+/* margin-left: 10em;
+ margin-right: 10em;
+*/ padding: 0px;
+ font-family: "overpass", sans-serif;
+ font-weight:300;
+}
+
+body.cover > div {
+ height: 100%;
+}
+
+body.cover * {
+ text-align: left;
+ box-sizing: border-box;
+ -moz-box-sizing: border-box;
+ -webkit-box-sizing: border-box;
+}
+
+body.cover div.logo {
+ height: 30%;
+ background-position: 50% 0%;
+ margin-top: 15mm;
+ background-image: url(../images/title_logo.svg);
+ background-repeat: no-repeat;
+}
+
+
+body.cover div.leader {
+ display: inline-block;
+ font-size: 40px;
+ font-weight: 600;
+ margin-top: 2em;
+}
+
+body.cover div.product {
+ display: inline;
+}
+
+
+body.cover div.edition {
+ display: inline;
+}
+
+body.cover div.docname {
+ font-size: 40px;
+ font-weight: 600;
+ height: 10%;
+}
+
+body.cover div.subtitle {
+ height: 20%;
+ font-weight:300;
+ font-size: 20px;
+ color: black;
+ border-top: .1em solid black;
+ padding-top: 40px;
+}
+body.cover div.authors {
+}
+
+body.cover div.author {
+ float: left;
+ min-width: 33%;
+ font-weight: 300;
+ font-size: 20px;
+}
+
+div.draft {
+ background-image: url(../images/watermark-draft.png);
+ background-repeat: repeat-y;
+ background-position: center;
+}
+
+body.titlepages {
+ text-align: left;
+}
+
+body.titlepages > div {
+ height: 100%;
+}
+body.titlepages .legalnotice {
+ page-break-before: always;
+}
+
+body.titlepages .title {
+ font-size: 20px;
+ color: black;
+ font-weight: normal;
+ margin-bottom: 0.1em;
+}
+
+body.titlepages .subtitle {
+ color: black;
+ font-weight: normal;
+ text-align: left;
+ font-size: 12px;
+ margin-top: 0.1em;
+ margin-bottom: 2em;
+}
+
+body.titlepages .contributor {
+ margin-bottom: 1em;
+ font-size: 12px;
+}
+
+body.titlepages .abstract {
+ page-break-before: avoid !important;
+ font-size: 14px;
+}
+
+body.titlepages h1 {
+ color: black;
+ font-size: 14px;
+ font-weight: normal;
+}
+
+body.titlepages .editors h1,
+body.titlepages .othercredit h1,
+body.titlepages .legalnotice h1,
+body.titlepages .keywords h1,
+body.titlepages .abstract h1 {
+ font-weight: bold;
+}
+
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/print.css b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/print.css
new file mode 100644
index 0000000..773d8ae
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/print.css
@@ -0,0 +1,16 @@
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
+
+#tocframe {
+ display: none;
+}
+
+body.toc_embeded {
+ margin-left: 30px;
+}
+
+.producttitle {
+ color: #336699;
+}
+
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/1.png
new file mode 100644
index 0000000..1098dab
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/1.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/1.svg
new file mode 100644
index 0000000..3736523
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/1.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 17.993,22.013004 L 17.993,10.113004 L 15.239,10.113004 C 14.899001,11.218003 14.286999,11.643004 12.757,11.728004 L 12.757,13.819004 L 14.763,13.819004 L 14.763,22.013004 L 17.993,22.013004"
+ id="text2207"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/10.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/10.png
new file mode 100644
index 0000000..ef058e3
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/10.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/10.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/10.svg
new file mode 100644
index 0000000..84ee18f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/10.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 12.252562,22 L 12.252562,10.1 L 9.4985624,10.1 C 9.1585628,11.204999 8.5465609,11.63 7.0165624,11.715 L 7.0165624,13.806 L 9.0225624,13.806 L 9.0225624,22 L 12.252562,22 M 24.983438,16.033 C 24.983438,12.072004 22.705435,9.913 19.611438,9.913 C 16.517441,9.913 14.205438,12.106004 14.205438,16.067 C 14.205438,20.027996 16.483441,22.187 19.577438,22.187 C 22.671435,22.187 24.983438,19.993996 24.983438,16.033 M 21.600438,16.067 C 21.600438,18.242998 20.886437,19.348 19.611438,19.348 C 18.336439,19.348 17.588438,18.208998 17.588438,16.033 C 17.588438,13.857002 18.302439,12.752 19.577438,12.752 C 20.852437,12.752 21.600438,13.891002 21.600438,16.067"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/11.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/11.png
new file mode 100644
index 0000000..fa20ec4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/11.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/11.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/11.svg
new file mode 100644
index 0000000..47f0c80
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/11.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 14.623052,22 L 14.623052,10.1 L 11.869052,10.1 C 11.529053,11.204999 10.917051,11.63 9.3870527,11.715 L 9.3870527,13.806 L 11.393052,13.806 L 11.393052,22 L 14.623052,22 M 21.794928,22 L 21.794928,10.1 L 19.040928,10.1 C 18.700928,11.204999 18.088926,11.63 16.558928,11.715 L 16.558928,13.806 L 18.564928,13.806 L 18.564928,22 L 21.794928,22"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/12.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/12.png
new file mode 100644
index 0000000..84c132a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/12.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/12.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/12.svg
new file mode 100644
index 0000000..94ddaac
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/12.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 12.677562,22 L 12.677562,10.1 L 9.9235624,10.1 C 9.5835628,11.204999 8.9715609,11.63 7.4415624,11.715 L 7.4415624,13.806 L 9.4475624,13.806 L 9.4475624,22 L 12.677562,22 M 24.558438,22 L 24.558438,19.314 L 18.353438,19.314 C 18.608438,18.600001 19.27144,17.936999 21.651438,16.832 C 23.929436,15.778001 24.473438,14.825998 24.473438,13.262 C 24.473438,11.103002 22.926435,9.913 19.968438,9.913 C 17.92844,9.913 16.381436,10.491001 14.868438,11.46 L 16.381438,13.891 C 17.571437,13.092001 18.727439,12.684 19.917438,12.684 C 20.869437,12.684 21.243438,12.973001 21.243438,13.5 C 21.243438,13.976 21.056437,14.163001 19.798438,14.724 C 16.823441,16.049999 14.936438,17.988004 14.834438,22 L 24.558438,22"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/13.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/13.png
new file mode 100644
index 0000000..f41ec8f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/13.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/13.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/13.svg
new file mode 100644
index 0000000..040dd6c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/13.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 12.550062,22 L 12.550062,10.1 L 9.7960624,10.1 C 9.4560628,11.204999 8.8440609,11.63 7.3140624,11.715 L 7.3140624,13.806 L 9.3200624,13.806 L 9.3200624,22 L 12.550062,22 M 24.685938,18.226 C 24.685938,16.713002 23.716937,15.914 22.611938,15.659 C 23.427937,15.268 24.192938,14.638999 24.192938,13.33 C 24.192938,10.814003 22.288935,9.913 19.432938,9.913 C 17.35894,9.913 15.930937,10.610001 14.825938,11.46 L 16.389938,13.602 C 17.307937,12.939001 18.191939,12.582 19.347938,12.582 C 20.520937,12.582 20.996938,12.922001 20.996938,13.551 C 20.996938,14.332999 20.656937,14.554 19.619938,14.554 L 18.089938,14.554 L 18.089938,17.121 L 19.806938,17.121 C 21.013937,17.121 21.489938,17.427001 21.489938,18.26 C 21.489938,19.075999 20.911937,19.467 19.534938,19.467 C 18.225939,19.467 17.120937,18.973999 16.151938,18.226 L 14.451938,20.368 C 15.726937,21.489999 17.44394,22.187 19.466938,22.187 C 22.696935,22.187 24.685938,20.979997 24.685938,18.226"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/14.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/14.png
new file mode 100644
index 0000000..c491206
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/14.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/14.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/14.svg
new file mode 100644
index 0000000..7f4fcfd
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/14.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 12.040062,22 L 12.040062,10.1 L 9.2860624,10.1 C 8.9460628,11.204999 8.3340609,11.63 6.8040624,11.715 L 6.8040624,13.806 L 8.8100624,13.806 L 8.8100624,22 L 12.040062,22 M 25.195938,19.96 L 25.195938,17.172 L 23.665938,17.172 L 23.665938,10.1 L 20.401938,10.1 L 13.992938,17.461 L 13.992938,19.875 L 20.707938,19.875 L 20.707938,22 L 23.665938,22 L 23.665938,19.96 L 25.195938,19.96 M 20.758938,13.432 C 20.724938,13.992999 20.707938,15.302001 20.707938,15.999 L 20.707938,17.172 L 19.823938,17.172 C 19.007939,17.172 18.191937,17.189 17.596938,17.223 C 18.038938,16.798 18.531939,16.253999 19.160938,15.489 L 19.330938,15.285 C 20.112937,14.350001 20.435938,13.925 20.758938,13.432"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/15.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/15.png
new file mode 100644
index 0000000..7656c94
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/15.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/15.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/15.svg
new file mode 100644
index 0000000..a8eba4d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/15.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 12.388562,22 L 12.388562,10.1 L 9.6345624,10.1 C 9.2945628,11.204999 8.6825609,11.63 7.1525624,11.715 L 7.1525624,13.806 L 9.1585624,13.806 L 9.1585624,22 L 12.388562,22 M 24.847438,17.852 C 24.847438,15.200003 23.164435,13.908 20.597438,13.908 C 19.407439,13.908 18.693437,14.112 18.030438,14.435 L 18.132438,12.786 L 24.133438,12.786 L 24.133438,10.1 L 15.463438,10.1 L 15.055438,16.271 L 17.877438,17.223 C 18.472437,16.798 19.067439,16.543 20.070438,16.543 C 21.090437,16.543 21.668438,17.019001 21.668438,17.937 C 21.668438,18.888999 21.107436,19.45 19.577438,19.45 C 18.302439,19.45 16.891437,18.956999 15.752438,18.277 L 14.409438,20.742 C 15.871436,21.625999 17.43544,22.187 19.492438,22.187 C 22.875435,22.187 24.847438,20.622997 24.847438,17.852"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/16.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/16.png
new file mode 100644
index 0000000..1f2535a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/16.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/16.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/16.svg
new file mode 100644
index 0000000..1adc217
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/16.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 12.405562,22 L 12.405562,10.1 L 9.6515624,10.1 C 9.3115628,11.204999 8.6995609,11.63 7.1695624,11.715 L 7.1695624,13.806 L 9.1755624,13.806 L 9.1755624,22 L 12.405562,22 M 24.830438,17.903 C 24.830438,15.387003 23.096435,14.214 20.631438,14.214 C 19.203439,14.214 18.336437,14.486 17.571438,14.911 C 18.472437,13.534001 20.104441,12.616 23.215438,12.616 L 23.215438,9.913 C 16.415445,9.913 14.341438,14.112003 14.341438,17.257 C 14.341438,20.537997 16.415441,22.187 19.407438,22.187 C 22.773435,22.187 24.830438,20.588997 24.830438,17.903 M 21.651438,18.124 C 21.651438,19.075999 20.818437,19.586 19.577438,19.586 C 18.132439,19.586 17.486438,18.990999 17.486438,18.141 C 17.486438,17.206001 18.183439,16.645 19.645438,16.645 C 20.903437,16.645 21.651438,17.206001 21.651438,18.124"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/17.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/17.png
new file mode 100644
index 0000000..67fe7ce
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/17.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/17.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/17.svg
new file mode 100644
index 0000000..b007799
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/17.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 12.652062,22 L 12.652062,10.1 L 9.8980624,10.1 C 9.5580628,11.204999 8.9460609,11.63 7.4160624,11.715 L 7.4160624,13.806 L 9.4220624,13.806 L 9.4220624,22 L 12.652062,22 M 24.583938,12.48 L 24.583938,10.1 L 14.740938,10.1 L 14.740938,12.786 L 20.656938,12.786 C 18.36194,15.131998 17.239938,17.920004 17.205938,22 L 20.435938,22 C 20.435938,18.141004 21.098941,15.675997 24.583938,12.48"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/18.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/18.png
new file mode 100644
index 0000000..76aa05b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/18.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/18.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/18.svg
new file mode 100644
index 0000000..140c8ec
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/18.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 12.176062,22 L 12.176062,10.1 L 9.4220624,10.1 C 9.0820628,11.204999 8.4700609,11.63 6.9400624,11.715 L 6.9400624,13.806 L 8.9460624,13.806 L 8.9460624,22 L 12.176062,22 M 25.059938,18.294 C 25.059938,16.764002 23.971937,15.948 23.206938,15.642 C 23.954937,15.166 24.549938,14.519999 24.549938,13.449 C 24.549938,11.171002 22.526935,9.913 19.653938,9.913 C 16.780941,9.913 14.723938,11.171002 14.723938,13.449 C 14.723938,14.519999 15.352939,15.251 16.066938,15.676 C 15.301939,15.982 14.213938,16.764002 14.213938,18.294 C 14.213938,20.707998 16.287941,22.187 19.619938,22.187 C 22.951935,22.187 25.059938,20.707998 25.059938,18.294 M 21.387938,13.5 C 21.387938,14.094999 20.945937,14.639 19.653938,14.639 C 18.361939,14.639 17.885938,14.094999 17.885938,13.5 C 17.885938,12.905001 18.327939,12.31 19.619938,12.31 C 20.911937,12.31 21.387938,12.905001 21.387938,13.5 M 21.897938,18.26 C 21.897938,19.075999 21.149936,19.688 19.653938,19.688 C 18.157939,19.688 17.375938,19.07599
9 17.375938,18.26 C 17.375938,17.444001 18.106939,16.849 19.619938,16.849 C 21.115936,16.849 21.897938,17.444001 21.897938,18.26"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/19.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/19.png
new file mode 100644
index 0000000..5f5ada0
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/19.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/19.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/19.svg
new file mode 100644
index 0000000..ae864c4
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/19.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 12.414062,22 L 12.414062,10.1 L 9.6600624,10.1 C 9.3200628,11.204999 8.7080609,11.63 7.1780624,11.715 L 7.1780624,13.806 L 9.1840624,13.806 L 9.1840624,22 L 12.414062,22 M 24.821938,14.843 C 24.821938,11.562003 22.747935,9.913 19.755938,9.913 C 16.389941,9.913 14.332938,11.511003 14.332938,14.197 C 14.332938,16.712997 16.06694,17.886 18.531938,17.886 C 19.959937,17.886 20.826939,17.614 21.591938,17.189 C 20.690939,18.565999 19.058935,19.484 15.947938,19.484 L 15.947938,22.187 C 22.747931,22.187 24.821938,17.987997 24.821938,14.843 M 21.676938,13.959 C 21.676938,14.893999 20.979936,15.455 19.517938,15.455 C 18.259939,15.455 17.511938,14.893999 17.511938,13.976 C 17.511938,13.024001 18.344939,12.514 19.585938,12.514 C 21.030936,12.514 21.676938,13.109001 21.676938,13.959"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/2.png
new file mode 100644
index 0000000..8fe3709
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/2.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/2.svg
new file mode 100644
index 0000000..ee96128
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/2.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 20.862,22.013004 L 20.862,19.327004 L 14.657,19.327004 C 14.912,18.613005 15.575003,17.950003 17.955,16.845004 C 20.232998,15.791005 20.777,14.839003 20.777,13.275004 C 20.777,11.116006 19.229997,9.9260043 16.272,9.9260043 C 14.232002,9.9260043 12.684999,10.504005 11.172,11.473004 L 12.685,13.904004 C 13.874999,13.105005 15.031001,12.697004 16.221,12.697004 C 17.172999,12.697004 17.547,12.986005 17.547,13.513004 C 17.547,13.989004 17.359999,14.176005 16.102,14.737004 C 13.127003,16.063003 11.24,18.001008 11.138,22.013004 L 20.862,22.013004"
+ id="text2207"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/20.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/20.png
new file mode 100644
index 0000000..5e2ad33
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/20.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/20.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/20.svg
new file mode 100644
index 0000000..1678a9f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/20.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 14.685,22 L 14.685,19.314 L 8.4799999,19.314 C 8.7349997,18.600001 9.3980023,17.936999 11.778,16.832 C 14.055998,15.778001 14.6,14.825998 14.6,13.262 C 14.6,11.103002 13.052997,9.913 10.095,9.913 C 8.055002,9.913 6.5079984,10.491001 4.9949999,11.46 L 6.5079999,13.891 C 7.6979988,13.092001 8.8540011,12.684 10.044,12.684 C 10.995999,12.684 11.37,12.973001 11.37,13.5 C 11.37,13.976 11.182999,14.163001 9.9249999,14.724 C 6.9500029,16.049999 5.0629998,17.988004 4.9609999,22 L 14.685,22 M 27.421719,16.033 C 27.421719,12.072004 25.143716,9.913 22.049719,9.913 C 18.955722,9.913 16.643719,12.106004 16.643719,16.067 C 16.643719,20.027996 18.921722,22.187 22.015719,22.187 C 25.109716,22.187 27.421719,19.993996 27.421719,16.033 M 24.038719,16.067 C 24.038719,18.242998 23.324717,19.348 22.049719,19.348 C 20.77472,19.348 20.026719,18.208998 20.026719,16.033 C 20.026719,13.857002 20.74072,12.752 22.015719,12.752 C 23.290717,12.752 24.038719,13.891002 24.038719,16.067"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/21.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/21.png
new file mode 100644
index 0000000..cfafd1f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/21.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/21.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/21.svg
new file mode 100644
index 0000000..4199512
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/21.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 16.648141,22 L 16.648141,19.314 L 10.44314,19.314 C 10.69814,18.600001 11.361143,17.936999 13.741141,16.832 C 16.019139,15.778001 16.563141,14.825998 16.563141,13.262 C 16.563141,11.103002 15.016138,9.913 12.058141,9.913 C 10.018143,9.913 8.471139,10.491001 6.9581405,11.46 L 8.4711405,13.891 C 9.661139,13.092001 10.817142,12.684 12.007141,12.684 C 12.95914,12.684 13.333141,12.973001 13.333141,13.5 C 13.333141,13.976 13.14614,14.163001 11.88814,14.724 C 8.9131435,16.049999 7.0261404,17.988004 6.9241405,22 L 16.648141,22 M 23.82586,22 L 23.82586,10.1 L 21.07186,10.1 C 20.73186,11.204999 20.119858,11.63 18.58986,11.715 L 18.58986,13.806 L 20.59586,13.806 L 20.59586,22 L 23.82586,22"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/22.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/22.png
new file mode 100644
index 0000000..5415d35
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/22.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/22.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/22.svg
new file mode 100644
index 0000000..c1f4479
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/22.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 14.685,22 L 14.685,19.314 L 8.4799999,19.314 C 8.7349997,18.600001 9.3980023,17.936999 11.778,16.832 C 14.055998,15.778001 14.6,14.825998 14.6,13.262 C 14.6,11.103002 13.052997,9.913 10.095,9.913 C 8.055002,9.913 6.5079984,10.491001 4.9949999,11.46 L 6.5079999,13.891 C 7.6979988,13.092001 8.8540011,12.684 10.044,12.684 C 10.995999,12.684 11.37,12.973001 11.37,13.5 C 11.37,13.976 11.182999,14.163001 9.9249999,14.724 C 6.9500029,16.049999 5.0629998,17.988004 4.9609999,22 L 14.685,22 M 26.571719,22 L 26.571719,19.314 L 20.366719,19.314 C 20.621718,18.600001 21.284721,17.936999 23.664719,16.832 C 25.942716,15.778001 26.486719,14.825998 26.486719,13.262 C 26.486719,11.103002 24.939716,9.913 21.981719,9.913 C 19.941721,9.913 18.394717,10.491001 16.881719,11.46 L 18.394719,13.891 C 19.584718,13.092001 20.74072,12.684 21.930719,12.684 C 22.882718,12.684 23.256719,12.973001 23.256719,13.5 C 23.256719,13.976 23.069717,14.163001 21.811719,14.724 C 18.836722,16.049999 16.94971
9,17.988004 16.847719,22 L 26.571719,22"
+ id="number"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/23.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/23.png
new file mode 100644
index 0000000..658e22b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/23.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/23.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/23.svg
new file mode 100644
index 0000000..ea3c85a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/23.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 15.32239,22.013004 L 15.32239,19.327004 L 9.1173907,19.327004 C 9.3723904,18.613005 10.035393,17.950003 12.41539,16.845004 C 14.693388,15.791005 15.23739,14.839003 15.23739,13.275004 C 15.23739,11.116006 13.690387,9.9260043 10.73239,9.9260043 C 8.6923927,9.9260043 7.1453891,10.504005 5.6323906,11.473004 L 7.1453906,13.904004 C 8.3353896,13.105005 9.4913919,12.697004 10.68139,12.697004 C 11.633389,12.697004 12.00739,12.986005 12.00739,13.513004 C 12.00739,13.989004 11.820389,14.176005 10.56239,14.737004 C 7.5873937,16.063003 5.7003905,18.001008 5.5983906,22.013004 L 15.32239,22.013004 M 26.401609,18.239004 C 26.401609,16.726006 25.432608,15.927004 24.327609,15.672004 C 25.143608,15.281005 25.908609,14.652003 25.908609,13.343004 C 25.908609,10.827007 24.004606,9.9260043 21.148609,9.9260043 C 19.074611,9.9260043 17.646608,10.623005 16.541609,11.473004 L 18.105609,13.615004 C 19.023608,12.952005 19.90761,12.595004 21.063609,12.595004 C 22.236608,12.595004 22.712609,12.
935005 22.712609,13.564004 C 22.712609,14.346004 22.372608,14.567004 21.335609,14.567004 L 19.805609,14.567004 L 19.805609,17.134004 L 21.522609,17.134004 C 22.729608,17.134004 23.205609,17.440005 23.205609,18.273004 C 23.205609,19.089003 22.627608,19.480004 21.250609,19.480004 C 19.94161,19.480004 18.836608,18.987004 17.867609,18.239004 L 16.167609,20.381004 C 17.442608,21.503003 19.159611,22.200004 21.182609,22.200004 C 24.412606,22.200004 26.401609,20.993002 26.401609,18.239004"
+ id="text2207"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/24.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/24.png
new file mode 100644
index 0000000..863ce3b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/24.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/24.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/24.svg
new file mode 100644
index 0000000..27e1d39
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/24.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/25.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/25.png
new file mode 100644
index 0000000..cc23b9b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/25.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/25.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/25.svg
new file mode 100644
index 0000000..114e1a2
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/25.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/26.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/26.png
new file mode 100644
index 0000000..583fe34
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/26.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/26.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/26.svg
new file mode 100644
index 0000000..e9b5d23
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/26.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/27.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/27.png
new file mode 100644
index 0000000..d1c3dfa
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/27.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/27.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/27.svg
new file mode 100644
index 0000000..4a80177
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/27.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/28.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/28.png
new file mode 100644
index 0000000..f5db747
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/28.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/28.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/28.svg
new file mode 100644
index 0000000..d453f29
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/28.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/29.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/29.png
new file mode 100644
index 0000000..9a3141e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/29.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/29.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/29.svg
new file mode 100644
index 0000000..04b5c50
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/29.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/3.png
new file mode 100644
index 0000000..449ef5a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/3.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/3.svg
new file mode 100644
index 0000000..d3a7e73
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/3.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 21.117,18.239004 C 21.117,16.726006 20.147999,15.927004 19.043,15.672004 C 19.858999,15.281005 20.624,14.652003 20.624,13.343004 C 20.624,10.827007 18.719997,9.9260043 15.864,9.9260043 C 13.790002,9.9260043 12.361999,10.623005 11.257,11.473004 L 12.821,13.615004 C 13.738999,12.952005 14.623001,12.595004 15.779,12.595004 C 16.951999,12.595004 17.428,12.935005 17.428,13.564004 C 17.428,14.346004 17.087999,14.567004 16.051,14.567004 L 14.521,14.567004 L 14.521,17.134004 L 16.238,17.134004 C 17.444999,17.134004 17.921,17.440005 17.921,18.273004 C 17.921,19.089003 17.342999,19.480004 15.966,19.480004 C 14.657002,19.480004 13.551999,18.987004 12.583,18.239004 L 10.883,20.381004 C 12.157999,21.503003 13.875002,22.200004 15.898,22.200004 C 19.127997,22.200004 21.117,20.993002 21.117,18.239004"
+ id="text2207"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/30.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/30.png
new file mode 100644
index 0000000..9d3db24
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/30.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/30.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/30.svg
new file mode 100644
index 0000000..5cdcf65
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/30.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/31.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/31.png
new file mode 100644
index 0000000..9e2675d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/31.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/31.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/31.svg
new file mode 100644
index 0000000..f0fdb29
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/31.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/32.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/32.png
new file mode 100644
index 0000000..20f1bb2
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/32.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/32.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/32.svg
new file mode 100644
index 0000000..9382928
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/32.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c 0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141 0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801 0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648 -0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083 -1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l -1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/33.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/33.png
new file mode 100644
index 0000000..01407e6
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/33.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/33.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/33.svg
new file mode 100644
index 0000000..f46815f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/33.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883 -0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579 2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273 -0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534 -1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l 0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961 0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414 0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289 -0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032 -0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269 0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026 -0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l -1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868 0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393 1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/34.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/34.png
new file mode 100644
index 0000000..ba44352
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/34.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/34.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/34.svg
new file mode 100644
index 0000000..7bbdf5b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/34.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/35.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/35.png
new file mode 100644
index 0000000..21d4575
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/35.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/35.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/35.svg
new file mode 100644
index 0000000..8e19553
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/35.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/36.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/36.png
new file mode 100644
index 0000000..b5402b5
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/36.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/36.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/36.svg
new file mode 100644
index 0000000..d364dbf
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/36.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/37.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/37.png
new file mode 100644
index 0000000..9fd99d2
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/37.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/37.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/37.svg
new file mode 100644
index 0000000..771fa4d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/37.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/38.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/38.png
new file mode 100644
index 0000000..3ce6027
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/38.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/38.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/38.svg
new file mode 100644
index 0000000..487e0ef
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/38.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/39.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/39.png
new file mode 100644
index 0000000..d689450
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/39.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/39.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/39.svg
new file mode 100644
index 0000000..cea69f7
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/39.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/4.png
new file mode 100644
index 0000000..0a2634a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/4.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/4.svg
new file mode 100644
index 0000000..e6bbe8e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/4.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 20.573772,19.96 L 20.573772,17.172 L 19.043772,17.172 L 19.043772,10.1 L 15.779772,10.1 L 9.3707718,17.461 L 9.3707718,19.875 L 16.085772,19.875 L 16.085772,22 L 19.043772,22 L 19.043772,19.96 L 20.573772,19.96 M 16.136772,13.432 C 16.102772,13.992999 16.085772,15.302001 16.085772,15.999 L 16.085772,17.172 L 15.201772,17.172 C 14.385773,17.172 13.569771,17.189 12.974772,17.223 C 13.416772,16.798 13.909773,16.253999 14.538772,15.489 L 14.708772,15.285 C 15.490771,14.350001 15.813772,13.925 16.136772,13.432"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/40.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/40.png
new file mode 100644
index 0000000..0d3532e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/40.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/40.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/40.svg
new file mode 100644
index 0000000..bb4e1d7
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/40.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.440535,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.0136719,0 0,-1.784668 5.1547849,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262863,0.520191 -0.42334,0.780274 l -2.0253904,3.071289 2.7558594,0"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/5.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/5.png
new file mode 100644
index 0000000..bc1d337
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/5.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/5.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/5.svg
new file mode 100644
index 0000000..d8578f2
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/5.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 21.219,17.852 C 21.219,15.200003 19.535997,13.908 16.969,13.908 C 15.779001,13.908 15.064999,14.112 14.402,14.435 L 14.504,12.786 L 20.505,12.786 L 20.505,10.1 L 11.835,10.1 L 11.427,16.271 L 14.249,17.223 C 14.843999,16.798 15.439001,16.543 16.442,16.543 C 17.461999,16.543 18.04,17.019001 18.04,17.937 C 18.04,18.888999 17.478998,19.45 15.949,19.45 C 14.674001,19.45 13.262999,18.956999 12.124,18.277 L 10.781,20.742 C 12.242999,21.625999 13.807002,22.187 15.864,22.187 C 19.246997,22.187 21.219,20.622997 21.219,17.852"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/6.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/6.png
new file mode 100644
index 0000000..68cb4b6
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/6.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/6.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/6.svg
new file mode 100644
index 0000000..14d62e0
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/6.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 21.2445,17.903 C 21.2445,15.387003 19.510497,14.214 17.0455,14.214 C 15.617501,14.214 14.750499,14.486 13.9855,14.911 C 14.886499,13.534001 16.518503,12.616 19.6295,12.616 L 19.6295,9.913 C 12.829507,9.913 10.7555,14.112003 10.7555,17.257 C 10.7555,20.537997 12.829503,22.187 15.8215,22.187 C 19.187497,22.187 21.2445,20.588997 21.2445,17.903 M 18.0655,18.124 C 18.0655,19.075999 17.232499,19.586 15.9915,19.586 C 14.546501,19.586 13.9005,18.990999 13.9005,18.141 C 13.9005,17.206001 14.597501,16.645 16.0595,16.645 C 17.317499,16.645 18.0655,17.206001 18.0655,18.124"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/7.png
new file mode 100644
index 0000000..3b6cc72
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/7.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/7.svg
new file mode 100644
index 0000000..8d71ee3
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/7.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 20.9215,12.48 L 20.9215,10.1 L 11.0785,10.1 L 11.0785,12.786 L 16.9945,12.786 C 14.699502,15.131998 13.5775,17.920004 13.5435,22 L 16.7735,22 C 16.7735,18.141004 17.436503,15.675997 20.9215,12.48"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/8.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/8.png
new file mode 100644
index 0000000..b092185
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/8.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/8.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/8.svg
new file mode 100644
index 0000000..1c31e86
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/8.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 21.423,18.294 C 21.423,16.764002 20.334999,15.948 19.57,15.642 C 20.317999,15.166 20.913,14.519999 20.913,13.449 C 20.913,11.171002 18.889997,9.913 16.017,9.913 C 13.144003,9.913 11.087,11.171002 11.087,13.449 C 11.087,14.519999 11.716001,15.251 12.43,15.676 C 11.665001,15.982 10.577,16.764002 10.577,18.294 C 10.577,20.707998 12.651003,22.187 15.983,22.187 C 19.314997,22.187 21.423,20.707998 21.423,18.294 M 17.751,13.5 C 17.751,14.094999 17.308999,14.639 16.017,14.639 C 14.725001,14.639 14.249,14.094999 14.249,13.5 C 14.249,12.905001 14.691001,12.31 15.983,12.31 C 17.274999,12.31 17.751,12.905001 17.751,13.5 M 18.261,18.26 C 18.261,19.075999 17.512998,19.688 16.017,19.688 C 14.521001,19.688 13.739,19.075999 13.739,18.26 C 13.739,17.444001 14.470002,16.849 15.983,16.849 C 17.478998,16.849 18.261,17.444001 18.261,18.26"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/9.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/9.png
new file mode 100644
index 0000000..7706583
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/9.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/9.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/9.svg
new file mode 100644
index 0000000..851e9a3
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/9.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 22.128383,14.843 C 22.128383,11.562003 20.05438,9.913 17.062383,9.913 C 13.696386,9.913 11.639383,11.511003 11.639383,14.197 C 11.639383,16.712997 13.373385,17.886 15.838383,17.886 C 17.266382,17.886 18.133384,17.614 18.898383,17.189 C 17.997384,18.565999 16.36538,19.484 13.254383,19.484 L 13.254383,22.187 C 20.054376,22.187 22.128383,17.987997 22.128383,14.843 M 18.983383,13.959 C 18.983383,14.893999 18.286381,15.455 16.824383,15.455 C 15.566384,15.455 14.818383,14.893999 14.818383,13.976 C 14.818383,13.024001 15.651384,12.514 16.892383,12.514 C 18.337381,12.514 18.983383,13.109001 18.983383,13.959"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/bkgrnd_greydots.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/bkgrnd_greydots.png
new file mode 100644
index 0000000..2333a6d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/bkgrnd_greydots.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/bullet_arrowblue.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/bullet_arrowblue.png
new file mode 100644
index 0000000..c235534
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/bullet_arrowblue.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/documentation.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/documentation.png
new file mode 100644
index 0000000..79d0a80
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/documentation.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/dot.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/dot.png
new file mode 100644
index 0000000..36a6859
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/dot.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/dot2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/dot2.png
new file mode 100644
index 0000000..40aff92
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/dot2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/green.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/green.png
new file mode 100644
index 0000000..ebb3c24
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/green.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/h1-bg.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/h1-bg.png
new file mode 100644
index 0000000..a2aad24
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/h1-bg.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/image_left.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/image_left.png
new file mode 100644
index 0000000..e8fe7a4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/image_left.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/image_right.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/image_right.png
new file mode 100644
index 0000000..166cb79
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/image_right.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/important.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/important.png
new file mode 100644
index 0000000..f7594a3
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/important.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/important.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/important.svg
new file mode 100644
index 0000000..2d33045
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/important.svg
@@ -0,0 +1,106 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="important.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/important.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata2611">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="681"
+ inkscape:window-width="738"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="20"
+ inkscape:cy="20"
+ inkscape:window-x="0"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective2613" />
+ </defs>
+ <g
+ transform="matrix(0.4626799,0,0,0.4626799,-5.2934127,-3.3160376)"
+ id="g5485">
+ <path
+ d="M 29.97756,91.885882 L 55.586992,80.409826 L 81.231619,91.807015 L 78.230933,63.90468 L 96.995009,43.037218 L 69.531053,37.26873 L 55.483259,12.974592 L 41.510292,37.311767 L 14.064204,43.164717 L 32.892392,63.97442 L 29.97756,91.885882 z"
+ id="path6799"
+ style="fill:#f3de82;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.536215,56.538729 L 55.48324,12.974601 L 41.51028,37.311813 L 55.536215,56.538729 z"
+ id="path6824"
+ style="opacity:0.91005291;fill:#f9f2cb;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.57947,56.614318 L 78.241135,63.937979 L 96.976198,43.044318 L 55.57947,56.614318 z"
+ id="use6833"
+ style="opacity:1;fill:#d0bc64;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.523838,56.869126 L 55.667994,80.684281 L 81.379011,91.931065 L 55.523838,56.869126 z"
+ id="use6835"
+ style="opacity:1;fill:#e0c656;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.283346,56.742618 L 13.877363,43.200977 L 32.640089,64.069652 L 55.283346,56.742618 z"
+ id="use6831"
+ style="opacity:1;fill:#d1ba59;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.472076,56.869126 L 55.32792,80.684281 L 29.616903,91.931065 L 55.472076,56.869126 z"
+ id="use6837"
+ style="opacity:1;fill:#d2b951;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.57947,56.614318 L 96.976198,43.044318 L 69.504294,37.314027 L 55.57947,56.614318 z"
+ id="path7073"
+ style="opacity:1;fill:#f6e7a3;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.523838,56.869126 L 81.379011,91.931065 L 78.214821,64.046881 L 55.523838,56.869126 z"
+ id="path7075"
+ style="opacity:1;fill:#f6e7a3;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.283346,56.742618 L 41.341708,37.434209 L 13.877363,43.200977 L 55.283346,56.742618 z"
+ id="path7077"
+ style="opacity:1;fill:#f6e59d;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.472076,56.869126 L 29.616903,91.931065 L 32.781093,64.046881 L 55.472076,56.869126 z"
+ id="path7079"
+ style="opacity:1;fill:#f3df8b;fill-opacity:1;enable-background:new" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/logo.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/logo.png
new file mode 100644
index 0000000..66a3104
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/logo.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/note.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/note.png
new file mode 100644
index 0000000..d6c4518
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/note.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/note.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/note.svg
new file mode 100644
index 0000000..70e43b6
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/note.svg
@@ -0,0 +1,111 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="note.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/note.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata16">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="1024"
+ inkscape:window-width="1205"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="22.217181"
+ inkscape:cy="20"
+ inkscape:window-x="334"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective18" />
+ </defs>
+ <g
+ transform="matrix(0.468275,0,0,0.468275,-5.7626904,-7.4142703)"
+ id="layer1">
+ <g
+ transform="matrix(0.115136,0,0,0.115136,9.7283,21.77356)"
+ id="g8014"
+ style="enable-background:new">
+ <g
+ id="g8518"
+ style="opacity:1">
+ <path
+ d="M -2512.4524,56.33197 L 3090.4719,56.33197 L 3090.4719,4607.3813 L -2512.4524,4607.3813 L -2512.4524,56.33197 z"
+ transform="matrix(0.1104659,-2.3734892e-2,2.2163258e-2,0.1031513,308.46782,74.820675)"
+ id="rect8018"
+ style="fill:#ffe680;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.1;stroke-linecap:butt;stroke-miterlimit:4;stroke-dashoffset:0;stroke-opacity:1" />
+ </g>
+ <g
+ transform="matrix(0.5141653,-7.1944682e-2,7.1944682e-2,0.5141653,146.04015,-82.639785)"
+ id="g8020">
+ <path
+ d="M 511.14114,441.25315 C 527.3248,533.52772 464.31248,622.82928 370.39916,640.71378 C 276.48584,658.59828 187.23462,598.29322 171.05095,506.01865 C 154.86728,413.74408 217.8796,324.44253 311.79292,306.55803 C 405.70624,288.67353 494.95747,348.97858 511.14114,441.25315 z"
+ id="path8022"
+ style="opacity:1;fill:#e0c96f;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.0804934;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625 404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C 280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695 527.8214,324.97052 527.8214,393.1416 z"
+ transform="matrix(1.2585415,-0.2300055,0.2168789,1.1867072,-248.76141,68.254424)"
+ id="path8024"
+ style="opacity:1;fill:#c00000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.0804934;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 358.5625,281.15625 C 348.09597,281.05155 337.43773,281.94729 326.71875,283.90625 C 240.96686,299.57789 183.37901,377.92385 198.15625,458.78125 C 209.70749,521.98673 262.12957,567.92122 325.40625,577.5625 L 357.25,433.6875 L 509.34375,405.875 C 509.14405,404.58166 509.0804,403.29487 508.84375,402 C 495.91366,331.24978 431.82821,281.88918 358.5625,281.15625 z"
+ id="path8026"
+ style="opacity:1;fill:#b60000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.1;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 294.2107,361.9442 L 282.79367,370.38482 L 261.73414,386.13346 C 253.13706,404.40842 254.3359,423.7989 259.7176,444.39774 C 273.6797,497.83861 313.42636,523.96124 369.50989,517.58957 C 398.21848,514.32797 424.51832,504.67345 440.64696,484.15958 L 469.89512,447.48298 L 294.2107,361.9442 z"
+ id="path8028"
+ style="fill:#750000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.09999999;stroke-linecap:butt;stroke-miterlimit:4;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625 404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C 280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695 527.8214,324.97052 527.8214,393.1416 z"
+ transform="matrix(0.9837071,-0.1797787,0.1695165,0.9275553,-78.013985,79.234385)"
+ id="path8030"
+ style="opacity:1;fill:#d40000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.10298239;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625 404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C 280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695 527.8214,324.97052 527.8214,393.1416 z"
+ transform="matrix(0.9837071,-0.1797787,0.1695165,0.9275553,-69.306684,71.273294)"
+ id="path8032"
+ style="opacity:1;fill:#e11212;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.10298239;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ </g>
+ </g>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/red.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/red.png
new file mode 100644
index 0000000..d32d5e2
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/red.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/redhat-logo.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/redhat-logo.svg
new file mode 100644
index 0000000..1001776
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/redhat-logo.svg
@@ -0,0 +1,94 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://web.resource.org/cc/"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:xlink="http://www.w3.org/1999/xlink"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ width="300"
+ height="140"
+ id="svg2812"
+ sodipodi:version="0.32"
+ inkscape:version="0.45+devel"
+ version="1.0"
+ sodipodi:docname="redhat-logo.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape">
+ <defs
+ id="defs3" />
+ <sodipodi:namedview
+ inkscape:document-units="mm"
+ id="base"
+ pagecolor="#ffffff"
+ bordercolor="#666666"
+ borderopacity="1.0"
+ inkscape:pageopacity="0.0"
+ inkscape:pageshadow="2"
+ inkscape:zoom="1"
+ inkscape:cx="174.26394"
+ inkscape:cy="40.358463"
+ inkscape:current-layer="layer1"
+ inkscape:window-width="722"
+ inkscape:window-height="523"
+ inkscape:window-x="71"
+ inkscape:window-y="636"
+ width="300px"
+ height="140px" />
+ <metadata
+ id="metadata4">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <g
+ inkscape:label="Layer 1"
+ inkscape:groupmode="layer"
+ id="layer1"
+ transform="translate(-13.714282,-252.57246)">
+ <g
+ transform="matrix(2.1166666,0,0,2.1166666,-32.193429,187.76029)"
+ id="shadowman">
+ <path
+ d="M 55.68466,68.503937 C 55.68466,79.688581 46.617715,88.755526 35.433071,88.755526 C 24.248427,88.755526 15.181482,79.688581 15.181482,68.503937 C 15.181482,57.319293 24.248427,48.252348 35.433071,48.252348 C 46.617715,48.252348 55.68466,57.319293 55.68466,68.503937 z"
+ transform="matrix(1.10693,0,0,1.10693,5.005761,-12.00975)"
+ style="fill:#ffffff"
+ id="path4548" />
+ <path
+ d="M 147.81332,72.126073 C 147.81332,73.329962 147.86057,74.57586 148.03519,75.740362 L 146.64882,75.740362 L 146.42826,73.559712 L 146.35605,73.559712 C 145.61822,74.733404 143.92333,76.086957 141.50635,76.086957 C 138.4461,76.086957 137.02164,73.933874 137.02164,71.904202 C 137.02164,68.394942 140.11998,66.27862 146.30878,66.34295 L 146.30878,65.937278 C 146.30878,64.432747 146.01471,61.431561 142.41879,61.45388 C 141.08756,61.45388 139.70118,61.810976 138.5997,62.588186 L 138.1205,61.494579 C 139.51083,60.551948 141.20703,60.180411 142.58291,60.180411 C 146.97178,60.180411 147.81201,63.475677 147.81201,66.194597 L 147.81201,72.126073 L 147.81332,72.126073 z M 146.30878,67.609855 C 142.99645,67.514016 138.62333,68.015527 138.62333,71.667888 C 138.62333,73.853791 140.06616,74.835806 141.65077,74.835806 C 144.1859,74.835806 145.62742,73.266945 146.15124,71.786044 C 146.26152,71.460456 146.3101,71.134869 146.3101,70.874924 L 146.3101,67.609855 L 146.30878,67.609855 z
M 153.80387,57.175286 L 153.80387,60.527004 L 158.13891,60.527004 L 158.13891,61.747959 L 153.80387,61.747959 L 153.80387,71.635066 C 153.80387,73.568902 154.40385,74.780665 156.03835,74.780665 C 156.82343,74.780665 157.37877,74.676951 157.76606,74.541727 L 157.94856,75.707542 C 157.45754,75.912347 156.76567,76.072514 155.84798,76.072514 C 154.73862,76.072514 153.81831,75.723296 153.22358,74.994662 C 152.53566,74.195133 152.29934,72.917726 152.29934,71.365932 L 152.29934,61.746646 L 149.7314,61.746646 L 149.7314,60.525692 L 152.29934,60.525692 L 152.29934,57.729312 L 153.80387,57.175286 z M 129.02767,60.179099 C 127.87105,60.179099 126.8339,60.512563 125.96348,61.052146 C 125.05891,61.581226 124.3224,62.399135 123.88522,63.247239 L 123.8222,63.247239 L 123.8222,55.719331 L 122.31767,55.309721 L 122.31767,75.740362 L 123.8222,75.740362 L 123.8222,66.437475 C 123.8222,65.819121 123.86947,65.39113 124.02832,64.938196 C 124.67818,63.046372 126.45974,61.493265 128.61545,61.49326
5 C 131.72953,61.493265 132.80739,63.990315 132.80739,66.730242 L 132.80739,75.73905 L 134.31191,75.73905 L 134.31191,66.564822 C 134.31191,60.899855 130.4692,60.179099 129.02767,60.179099 z"
+ id="path620" />
+ <path
+ d="M 78.208384,65.270348 C 78.208384,63.205228 78.16506,61.686255 78.08235,60.311696 L 81.460325,60.311696 L 81.604739,63.240675 L 81.713705,63.240675 C 82.473849,61.069213 84.273772,59.961164 85.938472,59.961164 C 86.319199,59.961164 86.541071,59.976918 86.853532,60.045187 L 86.853532,63.719867 C 86.488557,63.648972 86.147215,63.609587 85.677213,63.609587 C 83.819525,63.609587 82.528988,64.792469 82.181081,66.560884 C 82.115438,66.904852 82.079992,67.318401 82.079992,67.738514 L 82.079992,75.73905 L 78.176875,75.73905 L 78.208384,65.270348 z M 91.56274,69.076313 C 91.666455,71.871381 93.83004,73.093647 96.328402,73.093647 C 98.123074,73.093647 99.405732,72.814009 100.58599,72.379455 L 101.16365,75.064243 C 99.842914,75.623519 98.010169,76.042319 95.771752,76.042319 C 90.763211,76.042319 87.82767,72.949234 87.82767,68.220332 C 87.82767,63.961432 90.411366,59.933594 95.372644,59.933594 C 100.38906,59.933594 102.02225,64.059896 102.02225,67.436558 C 102.02225,68.16256
6 101.95792,68.744161 101.88309,69.103883 L 91.56274,69.076313 z M 98.348885,66.358704 C 98.365952,64.929006 97.743659,62.59869 95.129766,62.59869 C 92.728556,62.59869 91.730785,64.778027 91.554863,66.358704 L 98.348885,66.358704 z M 118.82942,54.363153 L 114.93024,53.307617 L 114.93024,61.97377 L 114.8659,61.97377 C 114.17665,60.834212 112.65375,59.962477 110.54268,59.962477 C 106.83386,59.962477 103.60162,63.033244 103.62656,68.201952 C 103.62656,72.945296 106.54372,76.086957 110.22759,76.086957 C 112.45288,76.086957 114.31582,75.024857 115.23745,73.297141 L 115.30703,73.297141 L 115.48164,75.73905 L 118.95675,75.73905 C 118.88586,74.690078 118.82809,72.991246 118.82809,71.411881 L 118.82809,54.363153 L 118.82942,54.363153 z M 114.92893,69.050056 C 114.92893,69.459667 114.90136,69.840395 114.81077,70.189614 C 114.41823,71.877945 113.0371,72.966301 111.44198,72.966301 C 108.98563,72.966301 107.57957,70.894617 107.57957,68.060164 C 107.57957,65.198141 108.97382,62.983355 111
.48662,62.983355 C 113.2406,62.983355 114.49568,64.220064 114.84228,65.72197 C 114.90922,66.038368 114.92893,66.428286 114.92893,66.738119 L 114.92893,69.050056 L 114.92893,69.050056 z"
+ id="path616" />
+ <path
+ d="M 161.80517,73.528501 C 160.90479,73.528501 160.18937,74.243893 160.18939,75.144292 C 160.18939,76.044668 160.90478,76.760094 161.80517,76.760081 C 162.70554,76.760081 163.42095,76.041202 163.42097,75.144292 C 163.42097,74.24046 162.70554,73.528501 161.80517,73.528501 z M 161.80517,73.803529 C 162.54687,73.803529 163.14594,74.402585 163.14593,75.144292 C 163.14593,75.882533 162.54342,76.485053 161.80517,76.485053 C 161.06348,76.485053 160.46441,75.882523 160.46441,75.144292 C 160.46441,74.402596 161.06346,73.80354 161.80517,73.803529 z M 161.25512,74.319207 L 161.25512,75.969376 L 161.49577,75.969376 L 161.49577,75.247426 L 161.80517,75.247426 L 162.2521,75.969376 L 162.52712,75.969376 L 162.04582,75.247426 C 162.29078,75.216382 162.49274,75.06625 162.49274,74.766128 C 162.49273,74.438393 162.30159,74.319207 161.90832,74.319207 L 161.25512,74.319207 z M 161.49577,74.525479 L 161.83955,74.525479 C 162.0155,74.525467 162.21771,74.562596 162.21771,74.766128 C 162.21
773,75.02142 162.01906,75.041156 161.80517,75.041156 L 161.49577,75.041156 L 161.49577,74.525479 z"
+ id="path650" />
+ <path
+ d="M 63.115808,76.090895 C 60.810796,75.504093 58.522203,75.797079 56.285026,76.486064 C 56.010655,76.526189 56.159301,76.830359 56.114355,76.953441 C 56.240389,77.319727 56.032958,77.717522 54.998429,77.944646 C 53.465014,78.282048 52.496128,79.864039 51.942103,80.389181 C 51.290927,81.007536 49.45293,81.388262 49.729943,81.01935 C 49.946565,80.730522 50.773662,79.83253 51.276485,78.861018 C 51.726795,77.99322 52.127215,77.746405 52.678614,76.919305 C 52.841408,76.676428 53.46764,75.824385 53.650127,75.149578 C 53.854932,74.490525 53.786663,73.663427 53.865435,73.323398 C 53.97834,72.83239 54.440465,71.767665 54.477226,71.166377 C 54.496918,70.825035 53.056716,71.650821 52.372719,71.650821 C 51.688722,71.650821 51.024417,71.242523 50.412627,71.21364 C 49.657736,71.17688 49.17198,71.795235 48.489295,71.68758 C 48.098065,71.625877 47.769852,71.281909 47.087167,71.255652 C 46.115654,71.220205 44.928834,71.795235 42.698294,71.724341 C 40.507139,71.653447 38.480092,68.9
52905 38.204394,68.523601 C 37.880118,68.019465 37.484949,68.019465 37.054333,68.414634 C 36.622404,68.809804 36.090697,68.498657 35.939718,68.234773 C 35.652203,67.73195 34.882871,66.258927 33.692111,65.951719 C 32.044479,65.523729 31.210817,66.864153 31.31847,67.928878 C 31.427438,69.010669 32.127189,69.31394 32.451465,69.887656 C 32.77574,70.462687 32.94116,70.834225 33.54901,71.088919 C 33.980939,71.267467 34.142421,71.53529 34.013762,71.888448 C 33.900856,72.198281 33.451859,72.269175 33.156467,72.282304 C 31.933813,72.291845 31.468231,71.67907 30.76576,70.807968 C 30.388969,70.188301 29.79556,69.919166 29.103685,69.919166 C 28.774159,69.919166 28.465638,70.005814 28.191252,70.147603 C 27.106833,70.710817 25.817611,71.045595 24.429922,71.045595 L 22.863688,71.045595 C 22.102232,68.784859 21.688683,66.365268 21.688683,63.847213 C 21.688683,51.409229 31.770093,41.32782 44.208077,41.32782 C 56.646061,41.32782 66.72747,51.410542 66.72747,63.847213 C 66.730097,68.36212 65.40
1488,72.565881 63.115808,76.090895 z M 49.170707,74.025807 C 49.286239,74.138712 49.485793,74.518127 49.241602,75.001258 C 49.105065,75.257265 48.956712,75.437126 48.694141,75.647183 C 48.37643,75.900564 47.758075,76.194643 46.908658,75.65506 C 46.451785,75.364919 46.424215,75.267768 45.794044,75.349165 C 45.343735,75.408243 45.163874,74.953995 45.326668,74.575893 C 45.488149,74.199104 46.152454,73.893208 46.980865,74.378965 C 47.353716,74.598211 47.932685,75.059024 48.44076,74.649413 C 48.65213,74.481367 48.778164,74.368462 49.069618,74.031058 C 49.082746,74.015304 49.101126,74.007427 49.122132,74.007427 C 49.140512,74.007427 49.157579,74.013991 49.170707,74.025807 z"
+ id="path632" />
+ <path
+ d="M 63.115853,76.089615 C 65.401534,72.564599 66.72883,68.36215 66.72883,63.849868 C 66.72883,51.411879 56.647417,41.330466 44.209428,41.330466 C 31.77144,41.330466 21.690027,51.413192 21.690027,63.849868 C 21.690027,66.367923 22.103576,68.787515 22.865032,71.046939 C 25.868844,79.95466 34.290809,86.367957 44.209428,86.367957 C 52.133821,86.367957 59.101143,82.275788 63.115853,76.089615 z"
+ style="fill:none"
+ id="path646" />
+ <path
+ d="M 56.917822,57.857972 C 56.694636,58.606299 56.378238,59.562056 54.970858,60.285439 C 54.766053,60.390468 54.687282,60.218483 54.781807,60.057003 C 55.313513,59.151133 55.409352,58.925322 55.562956,58.568226 C 55.779577,58.047022 55.892482,57.303946 55.463179,55.754779 C 54.615075,52.707643 52.849285,48.633855 51.564001,47.31181 C 50.32598,46.037029 48.079686,45.677306 46.050011,46.19851 C 45.302998,46.390186 43.839164,47.151642 41.126807,46.539852 C 36.433353,45.483004 35.738853,47.833013 35.468405,48.857041 C 35.197956,49.881066 34.552032,52.791666 34.552032,52.791666 C 34.33541,53.977174 34.05446,56.038354 41.342116,57.426043 C 44.737158,58.071966 44.910455,58.950266 45.060119,59.58175 C 45.329254,60.712117 45.761183,61.360667 46.245627,61.682316 C 46.731383,62.006591 46.245627,62.274414 45.707356,62.329554 C 44.260592,62.480532 38.917273,60.947118 35.754607,59.151133 C 33.168283,57.570457 33.124958,56.147322 33.717056,54.939495 C 29.808689,54.516756 26.877084
,55.304469 26.345378,57.155594 C 25.431631,60.330077 33.324513,65.752165 42.311003,68.473712 C 51.741236,71.329172 61.440606,69.336258 62.519772,63.40872 C 63.012093,60.71343 60.74348,58.721829 56.917822,57.857972 z M 42.458041,52.053841 C 39.857276,52.241579 39.586829,52.52253 39.099759,53.041108 C 38.411824,53.772368 37.507268,52.090601 37.507268,52.090601 C 36.965059,51.976382 36.306006,51.100708 36.661789,50.2828 C 37.012321,49.474082 37.658246,49.71696 37.860425,49.969029 C 38.107242,50.274923 38.633697,50.777747 39.315068,50.759366 C 39.997753,50.7423 40.785465,50.597886 41.884324,50.597886 C 42.998938,50.597886 43.745953,51.014061 43.789276,51.371156 C 43.823411,51.675739 43.698689,51.964567 42.458041,52.053841 z M 45.191406,47.754243 C 45.187466,47.754243 45.183528,47.755556 45.179589,47.755556 C 45.138891,47.755556 45.107383,47.72536 45.107383,47.687287 C 45.107383,47.659717 45.123137,47.636085 45.14808,47.625583 C 45.652218,47.359073 46.404482,47.147704 47.265715,4
7.059743 C 47.524347,47.032172 47.776416,47.019045 48.019294,47.016418 C 48.062617,47.016418 48.103316,47.016418 48.147954,47.017731 C 49.592094,47.04924 50.746092,47.622957 50.729025,48.299078 C 50.711958,48.973884 49.527763,49.495088 48.084936,49.46358 C 47.617561,49.453076 47.179067,49.384807 46.800965,49.275842 C 46.756328,49.264025 46.723506,49.225952 46.723506,49.181315 C 46.723506,49.135365 46.756328,49.097292 46.802278,49.08679 C 47.702895,48.878046 48.310747,48.538016 48.268737,48.215055 C 48.212283,47.788376 47.03334,47.557315 45.637776,47.696476 C 45.484171,47.713544 45.334507,47.733237 45.191406,47.754243 z"
+ style="fill:#cc0000"
+ id="path648" />
+ <use
+ transform="translate(-94.61853,1.913321)"
+ id="use4312"
+ x="0"
+ y="0"
+ width="744.09448"
+ height="1052.3622"
+ xlink:href="#path650" />
+ </g>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/rhlogo.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/rhlogo.png
new file mode 100644
index 0000000..ecd4856
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/rhlogo.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/shade.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/shade.png
new file mode 100644
index 0000000..a73afdf
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/shade.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/shine.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/shine.png
new file mode 100644
index 0000000..a18f7c4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/shine.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-back.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-back.png
new file mode 100644
index 0000000..d320f26
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-back.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-forward.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-forward.png
new file mode 100644
index 0000000..1ee5a29
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-forward.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-up.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-up.png
new file mode 100644
index 0000000..1cd7332
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-up.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-home.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-home.png
new file mode 100644
index 0000000..122536d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-home.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/title_logo.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/title_logo.png
new file mode 100644
index 0000000..d5182b4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/title_logo.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/title_logo.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/title_logo.svg
new file mode 100644
index 0000000..e84ee0e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/title_logo.svg
@@ -0,0 +1,109 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="220"
+ height="70"
+ id="svg6180"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="title_logo.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape">
+ <metadata
+ id="metadata16">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="990"
+ inkscape:window-width="1680"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ showguides="true"
+ inkscape:guide-bbox="true"
+ inkscape:zoom="7.4053365"
+ inkscape:cx="173.22629"
+ inkscape:cy="36.314321"
+ inkscape:window-x="-5"
+ inkscape:window-y="-3"
+ inkscape:current-layer="svg6180" />
+ <defs
+ id="defs6182">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 35 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="220 : 35 : 1"
+ inkscape:persp3d-origin="110 : 23.333333 : 1"
+ id="perspective18" />
+ </defs>
+ <g
+ transform="translate(-266.55899,-345.34488)"
+ id="layer1">
+ <path
+ d="M 316.7736,397.581 C 316.7736,397.581 316.7736,397.581 296.23471,397.581 C 296.56741,402.03345 300.15628,405.35709 304.94186,405.35709 C 308.33169,405.35709 311.25642,403.96093 313.5828,401.70202 C 314.04833,401.23523 314.58006,401.1024 315.17799,401.1024 C 315.9758,401.1024 316.7736,401.50172 317.30491,402.16628 C 317.63761,402.63181 317.83707,403.16354 317.83707,403.69485 C 317.83707,404.42603 317.50437,405.22342 316.90601,405.82219 C 314.11411,408.81271 309.39515,410.80722 304.74198,410.80722 C 296.30049,410.80722 289.52124,404.02755 289.52124,395.58564 C 289.52124,387.14415 296.10146,380.3649 304.54295,380.3649 C 312.91824,380.3649 319.16618,386.87807 319.16618,395.45239 C 319.16618,396.71657 318.03694,397.581 316.7736,397.581 z M 304.54295,385.81588 C 300.08966,385.81588 297.0321,388.74061 296.36796,392.99319 C 306.40422,392.99319 312.71879,392.99319 312.71879,392.99319 C 312.12043,388.93964 308.93005,385.81588 304.54295,385.81588 z"
+ id="path11"
+ style="fill:#3c6eb4" />
+ <path
+ d="M 375.46344,410.80807 C 367.02238,410.80807 360.2427,404.02839 360.2427,395.58648 C 360.2427,387.14499 367.02238,380.36574 375.46344,380.36574 C 383.90578,380.36574 390.68503,387.14499 390.68503,395.58648 C 390.68461,404.02797 383.90535,410.80807 375.46344,410.80807 z M 375.46344,386.14815 C 370.14656,386.14815 366.68967,390.40242 366.68967,395.58648 C 366.68967,400.77012 370.14656,405.02481 375.46344,405.02481 C 380.78075,405.02481 384.23848,400.77012 384.23848,395.58648 C 384.23806,390.40242 380.78075,386.14815 375.46344,386.14815 z"
+ id="path13"
+ style="fill:#3c6eb4" />
+ <path
+ d="M 412.66183,380.36574 C 408.2022,380.36574 405.25217,381.68474 402.64792,384.9953 L 402.40756,383.45535 L 402.40756,383.45535 C 402.20558,381.84792 400.8343,380.60609 399.17374,380.60609 C 397.37235,380.60609 395.91168,382.06509 395.91168,383.8669 C 395.91168,383.86943 395.91168,383.87196 395.91168,383.87449 L 395.91168,383.87449 L 395.91168,383.87744 L 395.91168,383.87744 L 395.91168,407.28456 C 395.91168,409.0792 397.37362,410.54199 399.16868,410.54199 C 400.96333,410.54199 402.42612,409.0792 402.42612,407.28456 L 402.42612,394.72247 C 402.42612,389.00626 407.41114,386.14815 412.66225,386.14815 C 414.25744,386.14815 415.51951,384.81862 415.51951,383.223 C 415.51951,381.62739 414.25744,380.36574 412.66183,380.36574 z"
+ id="path15"
+ style="fill:#3c6eb4" />
+ <path
+ d="M 447.02614,395.58648 C 447.09277,387.41107 441.24288,380.36574 431.80414,380.36574 C 423.36222,380.36574 416.51635,387.14499 416.51635,395.58648 C 416.51635,404.02839 423.16319,410.80807 431.2062,410.80807 C 435.22054,410.80807 438.83302,408.74186 440.44466,406.58289 L 441.23825,408.59723 L 441.23825,408.59723 C 441.66414,409.729 442.75585,410.5344 444.03605,410.5344 C 445.68606,410.5344 447.02361,409.19769 447.02614,407.54895 L 447.02614,407.54895 L 447.02614,399.74208 L 447.02614,399.74208 L 447.02614,395.58648 z M 431.80414,405.02481 C 426.48641,405.02481 423.02995,400.77012 423.02995,395.58648 C 423.02995,390.40242 426.48599,386.14815 431.80414,386.14815 C 437.12144,386.14815 440.57833,390.40242 440.57833,395.58648 C 440.57833,400.77012 437.12144,405.02481 431.80414,405.02481 z"
+ id="path17"
+ style="fill:#3c6eb4" />
+ <path
+ d="M 355.01479,368.3337 C 355.01479,366.5399 353.55285,365.14373 351.7582,365.14373 C 349.96398,365.14373 348.50077,366.54032 348.50077,368.3337 L 348.50077,385.4836 C 346.8398,382.42604 343.25051,380.36574 338.99582,380.36574 C 330.3553,380.36574 324.57246,386.87892 324.57246,395.58648 C 324.57246,404.29405 330.55475,410.80807 338.99582,410.80807 C 342.76137,410.80807 346.02639,409.25378 347.98169,406.55253 L 348.70486,408.38681 C 349.15268,409.64593 350.35403,410.54705 351.76537,410.54705 C 353.55158,410.54705 355.01521,409.0927 355.01521,407.2989 C 355.01521,407.29384 355.01521,407.29004 355.01521,407.28498 L 355.01521,407.28498 L 355.01521,368.3337 L 355.01479,368.3337 z M 339.79363,405.02481 C 334.47632,405.02481 331.08648,400.77012 331.08648,395.58648 C 331.08648,390.40242 334.47632,386.14815 339.79363,386.14815 C 345.11136,386.14815 348.50077,390.20255 348.50077,395.58648 C 348.50077,400.96957 345.11136,405.02481 339.79363,405.02481 z"
+ id="path19"
+ style="fill:#3c6eb4" />
+ <path
+ d="M 287.21553,365.34023 C 286.62139,365.25253 286.01587,365.20825 285.41456,365.20825 C 278.68338,365.20825 273.2071,370.68495 273.2071,377.41613 L 273.2071,381.22933 L 269.21807,381.22933 C 267.7557,381.22933 266.55899,382.42604 266.55899,383.88714 C 266.55899,385.35035 267.7557,386.82452 269.21807,386.82452 L 273.20626,386.82452 L 273.20626,407.28456 C 273.20626,409.0792 274.66862,410.54199 276.46284,410.54199 C 278.25791,410.54199 279.72028,409.0792 279.72028,407.28456 L 279.72028,386.82452 L 284.13014,386.82452 C 285.59208,386.82452 286.78837,385.35035 286.78837,383.88714 C 286.78837,382.42562 285.59208,381.22891 284.13014,381.22891 L 279.72281,381.22891 L 279.72281,377.41571 C 279.72281,374.27719 282.27604,371.30102 285.41456,371.30102 C 285.6975,371.30102 285.98213,371.3221 286.26128,371.363 C 288.04159,371.62655 289.69708,370.82031 289.96147,369.03958 C 290.22417,367.26054 288.99541,365.6042 287.21553,365.34023 z"
+ id="path21"
+ style="fill:#3c6eb4" />
+ <path
+ d="M 482.01243,363.57426 C 482.01243,353.50638 473.85135,345.34488 463.78346,345.34488 C 453.72064,345.34488 445.56167,353.49963 445.55492,363.56119 L 445.5545,363.56077 L 445.5545,377.66787 L 445.55492,377.66829 C 445.5604,379.95292 447.41324,381.80238 449.69955,381.80238 C 449.7063,381.80238 449.71221,381.80154 449.71895,381.80154 L 449.72022,381.80238 L 463.79105,381.80238 L 463.79105,381.80238 C 473.85514,381.79817 482.01243,373.63962 482.01243,363.57426 z"
+ id="path25"
+ style="fill:#294172" />
+ <path
+ d="M 469.13577,349.66577 C 464.41049,349.66577 460.58001,353.49626 460.58001,358.22154 C 460.58001,358.22322 460.58001,358.22533 460.58001,358.22744 L 460.58001,362.7558 L 456.06557,362.7558 C 456.06472,362.7558 456.06472,362.7558 456.0643,362.7558 C 451.33902,362.7558 447.50854,366.56773 447.50854,371.29258 C 447.50854,376.01786 451.33902,379.84835 456.0643,379.84835 C 460.78916,379.84835 464.61964,376.01786 464.61964,371.29258 C 464.61964,371.2909 464.61964,371.28879 464.61964,371.28668 L 464.61964,366.73935 L 469.13408,366.73935 C 469.13493,366.73935 469.13535,366.73935 469.13577,366.73935 C 473.86063,366.73935 477.69111,362.94639 477.69111,358.22154 C 477.69111,353.49626 473.86063,349.66577 469.13577,349.66577 z M 460.58001,371.3006 C 460.57621,373.79058 458.55555,375.80871 456.0643,375.80871 C 453.57052,375.80871 451.53004,373.78678 451.53004,371.29301 C 451.53004,368.7988 453.57052,366.73935 456.0643,366.73935 C 456.06641,366.73935 456.06852,366.73977 456.0702,3
66.73977 L 459.93991,366.73977 C 459.94117,366.73977 459.94201,366.73935 459.94286,366.73935 C 460.29495,366.73935 460.58085,367.0244 460.58085,367.3765 C 460.58085,367.37692 460.58043,367.37734 460.58043,367.37776 L 460.58043,371.3006 L 460.58001,371.3006 z M 469.13535,362.7558 C 469.13408,362.7558 469.1324,362.7558 469.13113,362.7558 L 465.2589,362.7558 C 465.25806,362.7558 465.25721,362.7558 465.25679,362.7558 C 464.90427,362.7558 464.61922,362.47074 464.61922,362.11822 L 464.61922,362.1178 L 464.61922,358.21437 C 464.62344,355.72354 466.64368,353.70583 469.13493,353.70583 C 471.62871,353.70583 473.66961,355.72776 473.66961,358.22196 C 473.67003,360.71532 471.62913,362.7558 469.13535,362.7558 z"
+ id="path29"
+ style="fill:#3c6eb4" />
+ <path
+ d="M 460.58001,362.7558 L 460.58001,358.22744 C 460.58001,358.22533 460.58001,358.22322 460.58001,358.22154 C 460.58001,353.49626 464.41049,349.66577 469.13577,349.66577 C 469.85262,349.66577 470.362,349.74631 471.02529,349.92046 C 471.99303,350.17431 472.78325,350.96664 472.78367,351.88968 C 472.78409,353.00543 471.97448,353.81589 470.76427,353.81589 C 470.18785,353.81589 469.97954,353.70541 469.13535,353.70541 C 466.6441,353.70541 464.62386,355.72312 464.61964,358.21395 L 464.61964,362.1178 L 464.61964,362.11822 C 464.61964,362.47074 464.90469,362.7558 465.25721,362.7558 C 465.25764,362.7558 465.25848,362.7558 465.25932,362.7558 L 468.22453,362.7558 C 469.32974,362.7558 470.222,363.64047 470.22285,364.74863 C 470.22285,365.85679 469.32932,366.73977 468.22453,366.73977 L 464.61964,366.73977 L 464.61964,371.2871 C 464.61964,371.28921 464.61964,371.29132 464.61964,371.29343 C 464.61964,376.01828 460.78916,379.84877 456.0643,379.84877 C 455.34746,379.84877 454.83807,379
.76823 454.17478,379.59408 C 453.20704,379.34065 452.4164,378.5479 452.41598,377.62528 C 452.41598,376.50953 453.22517,375.69865 454.4358,375.69865 C 455.0118,375.69865 455.22053,375.80913 456.0643,375.80913 C 458.55555,375.80913 460.57621,373.79142 460.58043,371.30102 C 460.58043,371.30102 460.58043,367.37734 460.58043,367.37692 C 460.58043,367.02524 460.29453,366.74019 459.94244,366.74019 C 459.94201,366.74019 459.94159,366.74019 459.94075,366.74019 L 456.97554,366.73977 C 455.87033,366.73977 454.97723,365.85763 454.97723,364.74947 C 454.9768,363.63414 455.87961,362.7558 456.99662,362.7558 L 460.58001,362.7558 L 460.58001,362.7558 z"
+ id="path31"
+ style="fill:#ffffff" />
+ <path
+ d="M 477.41661,378.55292 L 480.23219,378.55292 L 480.23219,378.9319 L 479.05067,378.9319 L 479.05067,381.88125 L 478.59813,381.88125 L 478.59813,378.9319 L 477.41661,378.9319 L 477.41661,378.55292 M 480.67805,378.55292 L 481.34906,378.55292 L 482.19843,380.81788 L 483.05224,378.55292 L 483.72326,378.55292 L 483.72326,381.88125 L 483.28409,381.88125 L 483.28409,378.95865 L 482.42581,381.24144 L 481.97326,381.24144 L 481.11499,378.95865 L 481.11499,381.88125 L 480.67805,381.88125 L 480.67805,378.55292"
+ id="text6223"
+ style="fill:#294172;enable-background:new" />
+ </g>
+ <path
+ d="M 181.98344,61.675273 L 184.79902,61.675273 L 184.79902,62.054253 L 183.6175,62.054253 L 183.6175,65.003603 L 183.16496,65.003603 L 183.16496,62.054253 L 181.98344,62.054253 L 181.98344,61.675273 M 185.24488,61.675273 L 185.91589,61.675273 L 186.76526,63.940233 L 187.61907,61.675273 L 188.29009,61.675273 L 188.29009,65.003603 L 187.85092,65.003603 L 187.85092,62.081003 L 186.99264,64.363793 L 186.54009,64.363793 L 185.68182,62.081003 L 185.68182,65.003603 L 185.24488,65.003603 L 185.24488,61.675273"
+ id="path2391"
+ style="fill:#294172;enable-background:new" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/warning.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/warning.png
new file mode 100644
index 0000000..ce09951
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/warning.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/warning.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/warning.svg
new file mode 100644
index 0000000..5f2612c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/warning.svg
@@ -0,0 +1,89 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="warning.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/warning.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata2482">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="910"
+ inkscape:window-width="1284"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="20"
+ inkscape:cy="20"
+ inkscape:window-x="0"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective2484" />
+ </defs>
+ <g
+ transform="matrix(0.4536635,0,0,0.4536635,-5.1836431,-4.6889387)"
+ id="layer1">
+ <g
+ transform="translate(2745.6887,-1555.5977)"
+ id="g8304"
+ style="enable-background:new">
+ <path
+ d="M -1603,1054.4387 L -1577.0919,1027.891 L -1540,1027.4387 L -1513.4523,1053.3468 L -1513,1090.4387 L -1538.9081,1116.9864 L -1576,1117.4387 L -1602.5477,1091.5306 L -1603,1054.4387 z"
+ transform="matrix(0.8233528,8.9983906e-3,-8.9983906e-3,0.8233528,-1398.5561,740.7914)"
+ id="path8034"
+ style="opacity:1;fill:#efd259;fill-opacity:1;stroke:#efd259;stroke-opacity:1" />
+ <path
+ d="M -1603,1054.4387 L -1577.0919,1027.891 L -1540,1027.4387 L -1513.4523,1053.3468 L -1513,1090.4387 L -1538.9081,1116.9864 L -1576,1117.4387 L -1602.5477,1091.5306 L -1603,1054.4387 z"
+ transform="matrix(0.6467652,7.0684723e-3,-7.0684723e-3,0.6467652,-1675.7492,927.16391)"
+ id="path8036"
+ style="opacity:1;fill:#a42324;fill-opacity:1;stroke:#a42324;stroke-opacity:1" />
+ <path
+ d="M -2686.7886,1597.753 C -2686.627,1596.5292 -2686.5462,1595.6987 -2686.5462,1595.218 C -2686.5462,1593.1637 -2688.0814,1592.0711 -2690.9899,1592.0711 C -2693.8985,1592.0711 -2695.4336,1593.12 -2695.4336,1595.218 C -2695.4336,1595.961 -2695.3528,1596.7914 -2695.1912,1597.753 L -2692.929,1614.4491 L -2689.0508,1614.4491 L -2686.7886,1597.753"
+ id="path8038"
+ style="font-size:107.13574219px;font-style:normal;font-weight:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream Charter" />
+ <path
+ d="M -2690.9899,1617.8197 C -2693.6124,1617.8197 -2695.8118,1619.9346 -2695.8118,1622.6416 C -2695.8118,1625.3486 -2693.6124,1627.4635 -2690.9899,1627.4635 C -2688.2829,1627.4635 -2686.168,1625.264 -2686.168,1622.6416 C -2686.168,1619.9346 -2688.2829,1617.8197 -2690.9899,1617.8197"
+ id="path8040"
+ style="font-size:107.13574219px;font-style:normal;font-weight:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream Charter" />
+ </g>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/watermark-draft.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/watermark-draft.png
new file mode 100644
index 0000000..0ead5af
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/watermark-draft.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/yellow.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/yellow.png
new file mode 100644
index 0000000..223865d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/yellow.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/1-7RHEL_local_install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/1-7RHEL_local_install.png
new file mode 100644
index 0000000..68ad5bb
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/1-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/1-Iso_general.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/1-Iso_general.png
new file mode 100644
index 0000000..564c85d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/1-Iso_general.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/1-files_PV-win.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/1-files_PV-win.png
new file mode 100644
index 0000000..bfb31dc
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/1-files_PV-win.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-7RHEL_local_install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-7RHEL_local_install.png
new file mode 100644
index 0000000..309f788
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverchosen.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverchosen.png
new file mode 100644
index 0000000..92e56a0
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverchosen.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverchosen_win7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverchosen_win7.png
new file mode 100644
index 0000000..abd28c8
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverchosen_win7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverstart.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverstart.png
new file mode 100644
index 0000000..83b8d25
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverstart.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverstart_win7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverstart_win7.png
new file mode 100644
index 0000000..e02377c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverstart_win7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/11-7RHEL_local_install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/11-7RHEL_local_install.png
new file mode 100644
index 0000000..c11a72a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/11-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/12-DriverInstalled.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/12-DriverInstalled.png
new file mode 100644
index 0000000..cb71880
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/12-DriverInstalled.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/14-StartInstallSerial.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/14-StartInstallSerial.png
new file mode 100644
index 0000000..ad1a744
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/14-StartInstallSerial.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/2-7RHEL_local_install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/2-7RHEL_local_install.png
new file mode 100644
index 0000000..5cc3eef
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/2-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/2-Iso_Balloon_Os.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/2-Iso_Balloon_Os.png
new file mode 100644
index 0000000..7280b22
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/2-Iso_Balloon_Os.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/3-7RHEL_local_install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/3-7RHEL_local_install.png
new file mode 100644
index 0000000..ec3adc0
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/3-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/3-Iso_Balloon_Os_arch.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/3-Iso_Balloon_Os_arch.png
new file mode 100644
index 0000000..72ed471
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/3-Iso_Balloon_Os_arch.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/3_PCI_Device.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/3_PCI_Device.png
new file mode 100644
index 0000000..6d45920
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/3_PCI_Device.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/4-7RHEL_local_install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/4-7RHEL_local_install.png
new file mode 100644
index 0000000..ba41670
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/4-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/4-Iso_balloon_files.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/4-Iso_balloon_files.png
new file mode 100644
index 0000000..bc73a65
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/4-Iso_balloon_files.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/4_finish.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/4_finish.png
new file mode 100644
index 0000000..92a37ea
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/4_finish.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/5-7RHEL_local_install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/5-7RHEL_local_install.png
new file mode 100644
index 0000000..05c4e27
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/5-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/6-7RHEL_local_install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/6-7RHEL_local_install.png
new file mode 100644
index 0000000..211498b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/6-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/6.4-2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/6.4-2.png
new file mode 100644
index 0000000..88f6dd9
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/6.4-2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/6.4-3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/6.4-3.png
new file mode 100644
index 0000000..985c268
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/6.4-3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/6.4-4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/6.4-4.png
new file mode 100644
index 0000000..ee00ec2
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/6.4-4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/7-7RHEL_local_install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/7-7RHEL_local_install.png
new file mode 100644
index 0000000..9bca57c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/7-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/8-7RHEL_local_install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/8-7RHEL_local_install.png
new file mode 100644
index 0000000..accbc04
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/8-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/8-BrowseForDriver.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/8-BrowseForDriver.png
new file mode 100644
index 0000000..9adc468
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/8-BrowseForDriver.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/8-BrowseForDriver_win7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/8-BrowseForDriver_win7.png
new file mode 100644
index 0000000..cdc6ad1
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/8-BrowseForDriver_win7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/9-7RHEL_local_install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/9-7RHEL_local_install.png
new file mode 100644
index 0000000..0b5c0eb
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/9-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/9-BrowseToDirectory.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/9-BrowseToDirectory.png
new file mode 100644
index 0000000..fa98b9c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/9-BrowseToDirectory.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/9-BrowseToDirectory_win7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/9-BrowseToDirectory_win7.png
new file mode 100644
index 0000000..a41edd6
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/9-BrowseToDirectory_win7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/COPYME.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/COPYME.png
new file mode 100644
index 0000000..f99eaad
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/COPYME.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ChangeType.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ChangeType.png
new file mode 100644
index 0000000..5b78310
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ChangeType.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Connection_Details.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Connection_Details.png
new file mode 100644
index 0000000..27f542b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Connection_Details.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Create-1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Create-1.png
new file mode 100644
index 0000000..4e3e649
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Create-1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/DevManagerStart.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/DevManagerStart.png
new file mode 100644
index 0000000..930a787
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/DevManagerStart.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/DevManagerStart_win7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/DevManagerStart_win7.png
new file mode 100644
index 0000000..2fba9a8
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/DevManagerStart_win7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-Expand.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-Expand.png
new file mode 100644
index 0000000..3b49f18
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-Expand.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-OpenWizard.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-OpenWizard.png
new file mode 100644
index 0000000..74918fc
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-OpenWizard.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-OpenWizard_win7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-OpenWizard_win7.png
new file mode 100644
index 0000000..aeaa604
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-OpenWizard_win7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/DriverInstallExpand_win7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/DriverInstallExpand_win7.png
new file mode 100644
index 0000000..d906057
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/DriverInstallExpand_win7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/DuringInstallation.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/DuringInstallation.png
new file mode 100644
index 0000000..389ed9a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/DuringInstallation.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Iso_Balloon_files.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Iso_Balloon_files.png
new file mode 100644
index 0000000..e024530
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Iso_Balloon_files.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Iso_general.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Iso_general.png
new file mode 100644
index 0000000..f99eaad
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Iso_general.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ManageStart.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ManageStart.png
new file mode 100644
index 0000000..3ab0161
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ManageStart.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Network_hardware.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Network_hardware.png
new file mode 100644
index 0000000..a4d305b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Network_hardware.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Network_hardware_virtio.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Network_hardware_virtio.png
new file mode 100644
index 0000000..4c18960
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Network_hardware_virtio.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/PCIremoval.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/PCIremoval.png
new file mode 100644
index 0000000..5817e55
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/PCIremoval.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/PXEguest_5of5.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/PXEguest_5of5.png
new file mode 100644
index 0000000..1348bf3
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/PXEguest_5of5.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_cpu+ram.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_cpu+ram.png
new file mode 100644
index 0000000..ad33769
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_cpu+ram.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_finish_advanced.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_finish_advanced.png
new file mode 100644
index 0000000..057d47d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_finish_advanced.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_storage.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_storage.png
new file mode 100644
index 0000000..fcd4b8a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_storage.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_storage_local.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_storage_local.png
new file mode 100644
index 0000000..613e684
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_storage_local.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_virt-manager_new_1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_virt-manager_new_1.png
new file mode 100644
index 0000000..73bf11f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_virt-manager_new_1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6local_choose.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6local_choose.png
new file mode 100644
index 0000000..0178c2c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6local_choose.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6local_selectedISO.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6local_selectedISO.png
new file mode 100644
index 0000000..de74827
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHEL6local_selectedISO.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELKVMpackages-2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELKVMpackages-2.png
new file mode 100644
index 0000000..65aa27a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELKVMpackages-2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELKVMpackages.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELKVMpackages.png
new file mode 100644
index 0000000..ef73b85
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELKVMpackages.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELcustomize14.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELcustomize14.png
new file mode 100644
index 0000000..83050fc
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELcustomize14.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELcustomize15.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELcustomize15.png
new file mode 100644
index 0000000..597f744
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELcustomize15.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELkvmSelect.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELkvmSelect.png
new file mode 100644
index 0000000..6b897c6
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/RHELkvmSelect.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/SR-IOV_implementation.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/SR-IOV_implementation.png
new file mode 100644
index 0000000..7327f39
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/SR-IOV_implementation.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-VIrt-Manager-fig31pt18.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-VIrt-Manager-fig31pt18.png
new file mode 100644
index 0000000..1299ffa
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-VIrt-Manager-fig31pt18.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt1.png
new file mode 100644
index 0000000..2319393
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt11.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt11.png
new file mode 100644
index 0000000..8cad81e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt11.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt13.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt13.png
new file mode 100644
index 0000000..caf6608
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt13.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt14.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt14.png
new file mode 100644
index 0000000..3254d26
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt14.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt15.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt15.png
new file mode 100644
index 0000000..362e28b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt15.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt16.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt16.png
new file mode 100644
index 0000000..841484e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt16.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt17.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt17.png
new file mode 100644
index 0000000..cd88714
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt17.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt19.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt19.png
new file mode 100644
index 0000000..e0d075d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt19.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt2.png
new file mode 100644
index 0000000..95665bc
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt24.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt24.png
new file mode 100644
index 0000000..c1c6edf
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt24.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt24a.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt24a.png
new file mode 100644
index 0000000..48c1808
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt24a.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt27.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt27.png
new file mode 100644
index 0000000..541d6d9
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt27.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt28.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt28.png
new file mode 100644
index 0000000..fb670c0
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt28.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt29.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt29.png
new file mode 100644
index 0000000..4b1904b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt29.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt3.png
new file mode 100644
index 0000000..d19603a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt4.png
new file mode 100644
index 0000000..c4439e4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt5.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt5.png
new file mode 100644
index 0000000..9801530
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt5.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt6.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt6.png
new file mode 100644
index 0000000..baf2a69
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt6.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt7.png
new file mode 100644
index 0000000..955b48b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt25.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt25.png
new file mode 100644
index 0000000..6cc2283
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt25.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt25a.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt25a.png
new file mode 100644
index 0000000..bd59c7e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt25a.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt26.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt26.png
new file mode 100644
index 0000000..08eca7b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt26.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic1.png
new file mode 100644
index 0000000..7c133fa
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic10.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic10.png
new file mode 100644
index 0000000..2967923
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic10.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic11.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic11.png
new file mode 100644
index 0000000..ddd69b4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic11.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic2.png
new file mode 100644
index 0000000..52a4bec
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic3.png
new file mode 100644
index 0000000..7be870b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic4.png
new file mode 100644
index 0000000..79d74a5
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic5.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic5.png
new file mode 100644
index 0000000..67e8ac5
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic5.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic6.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic6.png
new file mode 100644
index 0000000..5a53e96
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic6.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic7.png
new file mode 100644
index 0000000..4e17f51
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic8.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic8.png
new file mode 100644
index 0000000..ceee7d9
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic8.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic9.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic9.png
new file mode 100644
index 0000000..97d8476
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic9.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic1-virt-mgr-guests.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic1-virt-mgr-guests.png
new file mode 100644
index 0000000..ea86b26
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic1-virt-mgr-guests.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic2-add-connection-pull-down.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic2-add-connection-pull-down.png
new file mode 100644
index 0000000..82c0542
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic2-add-connection-pull-down.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic3-Add Connection.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic3-Add Connection.png
new file mode 100644
index 0000000..ffff21f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic3-Add Connection.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic3-Add-Connection.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic3-Add-Connection.png
new file mode 100644
index 0000000..bc5028e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic3-Add-Connection.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic4-OpenSSH.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic4-OpenSSH.png
new file mode 100644
index 0000000..314c36a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic4-OpenSSH.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic5-guest-select-migrate.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic5-guest-select-migrate.png
new file mode 100644
index 0000000..70018bf
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic5-guest-select-migrate.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic6-final-before-migrate.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic6-final-before-migrate.png
new file mode 100644
index 0000000..f244ff7
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic6-final-before-migrate.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic7-Migrating-guest1-rhel6-64.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic7-Migrating-guest1-rhel6-64.png
new file mode 100644
index 0000000..12202b4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic7-Migrating-guest1-rhel6-64.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic8-migrated.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic8-migrated.png
new file mode 100644
index 0000000..3cce087
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic8-migrated.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-rhel6pv-virt-method.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-rhel6pv-virt-method.png
new file mode 100644
index 0000000..5f6957a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-rhel6pv-virt-method.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic1.png
new file mode 100644
index 0000000..604e0d8
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic2.png
new file mode 100644
index 0000000..7807aa3
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic4.png
new file mode 100644
index 0000000..09e2781
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic5.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic5.png
new file mode 100644
index 0000000..6950418
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic5.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic6.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic6.png
new file mode 100644
index 0000000..c267406
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic6.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic7-managed.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic7-managed.png
new file mode 100644
index 0000000..a635499
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic7-managed.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic7.png
new file mode 100644
index 0000000..c642653
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic8-create-lvm.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic8-create-lvm.png
new file mode 100644
index 0000000..010c7d0
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic8-create-lvm.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic8-new-storage-volume.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic8-new-storage-volume.png
new file mode 100644
index 0000000..542c15d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic8-new-storage-volume.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic9-local-storage.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic9-local-storage.png
new file mode 100644
index 0000000..8875f30
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic9-local-storage.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic9-storage-volume.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic9-storage-volume.png
new file mode 100644
index 0000000..9d58e09
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic9-storage-volume.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt2-pic2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt2-pic2.png
new file mode 100644
index 0000000..b6e48c8
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt2-pic2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt2-pic3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt2-pic3.png
new file mode 100644
index 0000000..135ac84
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt2-pic3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic2.png
new file mode 100644
index 0000000..b1b8667
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic3.png
new file mode 100644
index 0000000..17becd5
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic4.png
new file mode 100644
index 0000000..4d42817
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic5.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic5.png
new file mode 100644
index 0000000..c642653
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic5.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic6.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic6.png
new file mode 100644
index 0000000..2135749
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic6.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-virtlab22-Host-Details.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-virtlab22-Host-Details.png
new file mode 100644
index 0000000..d5a3eb3
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-virtlab22-Host-Details.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Section_11_pt_2_pt_2_step3_substep_c.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Section_11_pt_2_pt_2_step3_substep_c.png
new file mode 100644
index 0000000..1cb3707
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Section_11_pt_2_pt_2_step3_substep_c.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Section_11_pt_2_pt_2_step3_substep_d.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Section_11_pt_2_pt_2_step3_substep_d.png
new file mode 100644
index 0000000..650b0bb
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Section_11_pt_2_pt_2_step3_substep_d.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Select_storage_pools.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Select_storage_pools.png
new file mode 100644
index 0000000..7e4c07d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Select_storage_pools.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/StartDevManagerInVM.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/StartDevManagerInVM.png
new file mode 100644
index 0000000..438e32b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/StartDevManagerInVM.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/StartDevManagerInVM_win7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/StartDevManagerInVM_win7.png
new file mode 100644
index 0000000..4b59a25
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/StartDevManagerInVM_win7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/StartInstallingBalloon-1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/StartInstallingBalloon-1.png
new file mode 100644
index 0000000..e496e60
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/StartInstallingBalloon-1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/StartInstallingBalloon-1_win7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/StartInstallingBalloon-1_win7.png
new file mode 100644
index 0000000..c03a94a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/StartInstallingBalloon-1_win7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virt-Manager-Add-Connection.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virt-Manager-Add-Connection.png
new file mode 100644
index 0000000..44d5e61
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virt-Manager-Add-Connection.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install.png
new file mode 100644
index 0000000..a7ef6cc
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-cpumem.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-cpumem.png
new file mode 100644
index 0000000..20afcae
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-cpumem.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-import.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-import.png
new file mode 100644
index 0000000..1b8a5c1
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-import.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-local.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-local.png
new file mode 100644
index 0000000..5cb5c11
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-local.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP4.png
new file mode 100644
index 0000000..304089a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP5-finish.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP5-finish.png
new file mode 100644
index 0000000..55f87df
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP5-finish.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_final-hardware.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_final-hardware.png
new file mode 100644
index 0000000..def864d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_final-hardware.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-capture.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-capture.png
new file mode 100644
index 0000000..aaf7cdb
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-capture.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-select-driver.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-select-driver.png
new file mode 100644
index 0000000..bc2449f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-select-driver.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-select2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-select2.png
new file mode 100644
index 0000000..22f75f7
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-select2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/after_virtualization.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/after_virtualization.png
new file mode 100644
index 0000000..96bd1ee
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/after_virtualization.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/before_virtualization.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/before_virtualization.png
new file mode 100644
index 0000000..e47e9e0
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/before_virtualization.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/block_finish-virtio-win.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/block_finish-virtio-win.png
new file mode 100644
index 0000000..61fb164
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/block_finish-virtio-win.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/block_start-virtio-win.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/block_start-virtio-win.png
new file mode 100644
index 0000000..35abf5e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/block_start-virtio-win.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/bridgePXE.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/bridgePXE.png
new file mode 100644
index 0000000..4c5945f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/bridgePXE.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/bridgefinish.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/bridgefinish.png
new file mode 100644
index 0000000..7ecb971
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/bridgefinish.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/bz734652-step3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/bz734652-step3.png
new file mode 100644
index 0000000..5f9cd87
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/bz734652-step3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/done-KVM_PV.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/done-KVM_PV.png
new file mode 100644
index 0000000..5176b1c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/done-KVM_PV.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/exception-virtio-win.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/exception-virtio-win.png
new file mode 100644
index 0000000..f7df9dd
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/exception-virtio-win.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/icon.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/icon.svg
new file mode 100644
index 0000000..b2f16d0
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/icon.svg
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<svg xmlns:svg="http://www.w3.org/2000/svg" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.0" width="32" height="32" id="svg3017">
+ <defs id="defs3019">
+ <linearGradient id="linearGradient2381">
+ <stop id="stop2383" style="stop-color:#ffffff;stop-opacity:1" offset="0"/>
+ <stop id="stop2385" style="stop-color:#ffffff;stop-opacity:0" offset="1"/>
+ </linearGradient>
+ <linearGradient x1="296.4996" y1="188.81061" x2="317.32471" y2="209.69398" id="linearGradient2371" xlink:href="#linearGradient2381" gradientUnits="userSpaceOnUse" gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)"/>
+ </defs>
+ <g transform="matrix(0.437808,-0.437808,0.437808,0.437808,-220.8237,43.55311)" id="g5089">
+ <path d="m 8.4382985,-6.28125 c -0.6073916,0 -4.3132985,5.94886271 -4.3132985,8.25 l 0,26.71875 c 0,0.846384 0.5818159,1.125 1.15625,1.125 l 25.5625,0 c 0.632342,0 1.125001,-0.492658 1.125,-1.125 l 0,-5.21875 0.28125,0 c 0.49684,0 0.906249,-0.409411 0.90625,-0.90625 l 0,-27.9375 c 0,-0.4968398 -0.40941,-0.90625 -0.90625,-0.90625 l -23.8117015,0 z" transform="translate(282.8327,227.1903)" id="path5091" style="fill:#5c5c4f;stroke:#000000;stroke-width:3.23021388;stroke-miterlimit:4;stroke-dasharray:none"/>
+ <rect width="27.85074" height="29.369793" rx="1.1414107" ry="1.1414107" x="286.96509" y="227.63805" id="rect5093" style="fill:#032c87"/>
+ <path d="m 288.43262,225.43675 25.2418,0 0,29.3698 -26.37615,0.0241 1.13435,-29.39394 z" id="rect5095" style="fill:#ffffff"/>
+ <path d="m 302.44536,251.73726 c 1.38691,7.85917 -0.69311,11.28365 -0.69311,11.28365 2.24384,-1.60762 3.96426,-3.47694 4.90522,-5.736 0.96708,2.19264 1.83294,4.42866 4.27443,5.98941 0,0 -1.59504,-7.2004 -1.71143,-11.53706 l -6.77511,0 z" id="path5097" style="fill:#a70000;fill-opacity:1;stroke-width:2"/>
+ <rect width="25.241802" height="29.736675" rx="0.89682275" ry="0.89682275" x="290.73544" y="220.92249" id="rect5099" style="fill:#809cc9"/>
+ <path d="m 576.47347,725.93939 6.37084,0.41502 0.4069,29.51809 c -1.89202,-1.31785 -6.85427,-3.7608 -8.26232,-1.68101 l 0,-26.76752 c 0,-0.82246 0.66212,-1.48458 1.48458,-1.48458 z" transform="matrix(0.499065,-0.866565,0,1,0,0)" id="rect5101" style="fill:#4573b3;fill-opacity:1"/>
+ <path d="m 293.2599,221.89363 20.73918,0 c 0.45101,0 0.8141,0.3631 0.8141,0.81411 0.21547,6.32836 -19.36824,21.7635 -22.36739,17.59717 l 0,-17.59717 c 0,-0.45101 0.3631,-0.81411 0.81411,-0.81411 z" id="path5103" style="opacity:0.65536726;fill:url(#linearGradient2371);fill-opacity:1"/>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio-add-hardware.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio-add-hardware.png
new file mode 100644
index 0000000..16c8abd
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio-add-hardware.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio-remove-dev.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio-remove-dev.png
new file mode 100644
index 0000000..d21be2c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio-remove-dev.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio1.png
new file mode 100755
index 0000000..4fe8553
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio1replacement.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio1replacement.png
new file mode 100644
index 0000000..e7f1805
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio1replacement.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio2.png
new file mode 100755
index 0000000..b31e7c7
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio3.png
new file mode 100755
index 0000000..3fbefbe
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio4.png
new file mode 100755
index 0000000..bbefebc
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio5.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio5.png
new file mode 100755
index 0000000..d3888d7
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio5.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio5replacement.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio5replacement.png
new file mode 100644
index 0000000..8941fd0
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio5replacement.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio6.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio6.png
new file mode 100755
index 0000000..a843646
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio6.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio6replacement.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio6replacement.png
new file mode 100644
index 0000000..530f0aa
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio6replacement.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio7.png
new file mode 100755
index 0000000..35fbb90
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio7replacement.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio7replacement.png
new file mode 100644
index 0000000..9fe1ad5
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio7replacement.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/infotabbutton.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/infotabbutton.png
new file mode 100644
index 0000000..31082a3
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/infotabbutton.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/installmedia-blank.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/installmedia-blank.png
new file mode 100644
index 0000000..365f435
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/installmedia-blank.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/installmedia-select-os1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/installmedia-select-os1.png
new file mode 100644
index 0000000..19b7495
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/installmedia-select-os1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/installmedia-select-volume.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/installmedia-select-volume.png
new file mode 100644
index 0000000..e6344cd
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/installmedia-select-volume.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/network_finish-virtio-win.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/network_finish-virtio-win.png
new file mode 100644
index 0000000..b387250
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/network_finish-virtio-win.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/network_performance-virtio-win.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/network_performance-virtio-win.png
new file mode 100644
index 0000000..130bd7e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/network_performance-virtio-win.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/network_start-virtio-win.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/network_start-virtio-win.png
new file mode 100644
index 0000000..0db3f0e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/network_start-virtio-win.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-0-click-configure-before-install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-0-click-configure-before-install.png
new file mode 100644
index 0000000..71783ad
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-0-click-configure-before-install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-0-click-configure-before-install_win7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-0-click-configure-before-install_win7.png
new file mode 100644
index 0000000..0a9ce10
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-0-click-configure-before-install_win7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-1-click-add-hardware.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-1-click-add-hardware.png
new file mode 100644
index 0000000..e8b7783
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-1-click-add-hardware.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-10-select-custom-installation.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-10-select-custom-installation.png
new file mode 100644
index 0000000..3b12745
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-10-select-custom-installation.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-11-load-driver.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-11-load-driver.png
new file mode 100644
index 0000000..94bb9a0
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-11-load-driver.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-12-insert-disk.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-12-insert-disk.png
new file mode 100644
index 0000000..8fe079e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-12-insert-disk.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-13-select-driver-arch.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-13-select-driver-arch.png
new file mode 100644
index 0000000..21e58f3
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-13-select-driver-arch.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-14-view-drivers-loaded.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-14-view-drivers-loaded.png
new file mode 100644
index 0000000..b6be79f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-14-view-drivers-loaded.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2-disk-type.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2-disk-type.png
new file mode 100644
index 0000000..940a1ec
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2-disk-type.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2a-select-existing-storage.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2a-select-existing-storage.png
new file mode 100644
index 0000000..eae4416
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2a-select-existing-storage.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2b-select-browse-local.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2b-select-browse-local.png
new file mode 100644
index 0000000..0068c9c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2b-select-browse-local.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2c-virtio-win-vfd.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2c-virtio-win-vfd.png
new file mode 100644
index 0000000..76529b4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2c-virtio-win-vfd.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2z-select-storage.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2z-select-storage.png
new file mode 100644
index 0000000..bf7cc17
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2z-select-storage.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-3-floppy-advanced-options.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-3-floppy-advanced-options.png
new file mode 100644
index 0000000..2448048
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-3-floppy-advanced-options.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-4-after-adding-virtio-disk.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-4-after-adding-virtio-disk.png
new file mode 100644
index 0000000..3350be3
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-4-after-adding-virtio-disk.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-5-begin-installation.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-5-begin-installation.png
new file mode 100644
index 0000000..54eb223
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-5-begin-installation.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-6-windows-install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-6-windows-install.png
new file mode 100644
index 0000000..8df17e7
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-6-windows-install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-6a-select-installation-type.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-6a-select-installation-type.png
new file mode 100644
index 0000000..01196df
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-6a-select-installation-type.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-8-agree-to-license-terms.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-8-agree-to-license-terms.png
new file mode 100644
index 0000000..63a83f8
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-8-agree-to-license-terms.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-adding-virtio-disk.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-adding-virtio-disk.png
new file mode 100644
index 0000000..e87cc64
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-adding-virtio-disk.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-click-begin-installation.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-click-begin-installation.png
new file mode 100644
index 0000000..b5da7ee
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-click-begin-installation.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-floppy-settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-floppy-settings.png
new file mode 100644
index 0000000..f3a29de
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-floppy-settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-settings.png
new file mode 100644
index 0000000..3a2ea73
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-virtio-disk-in-use.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-virtio-disk-in-use.png
new file mode 100644
index 0000000..78d5e93
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-virtio-disk-in-use.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-device-type-virtio-finish.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-device-type-virtio-finish.png
new file mode 100644
index 0000000..2219703
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-device-type-virtio-finish.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-device-type-virtiodisk.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-device-type-virtiodisk.png
new file mode 100644
index 0000000..44ffd8e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-device-type-virtiodisk.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-remove-disk1-2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-remove-disk1-2.png
new file mode 100644
index 0000000..4f4f38d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-remove-disk1-2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-remove-disk1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-remove-disk1.png
new file mode 100644
index 0000000..634439d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-remove-disk1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-review-virtio-settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-review-virtio-settings.png
new file mode 100644
index 0000000..5c5f00c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-review-virtio-settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-select-device-type-floppy.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-select-device-type-floppy.png
new file mode 100644
index 0000000..c62349c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-select-device-type-floppy.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-storage-win7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-storage-win7.png
new file mode 100644
index 0000000..1236b8d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/paravirt-storage-win7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/pci_host_device.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/pci_host_device.png
new file mode 100644
index 0000000..a4a3ea2
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/pci_host_device.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_create_vm.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_create_vm.png
new file mode 100644
index 0000000..211647e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_create_vm.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_finish.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_finish.png
new file mode 100644
index 0000000..d76cba1
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_finish.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_finish_3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_finish_3.png
new file mode 100644
index 0000000..7fce9df
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_finish_3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_install_method.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_install_method.png
new file mode 100644
index 0000000..2f9d04f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_install_method.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_install_source_2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_install_source_2.png
new file mode 100644
index 0000000..2293268
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_install_source_2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_mem_n_cpu_alloc.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_mem_n_cpu_alloc.png
new file mode 100644
index 0000000..93dccd9
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_mem_n_cpu_alloc.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_network.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_network.png
new file mode 100644
index 0000000..56f4ec9
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_network.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_storage.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_storage.png
new file mode 100644
index 0000000..e71f549
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_storage.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_virt_install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_virt_install.png
new file mode 100644
index 0000000..c9c3557
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_virt_install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6-Screenshot-step2-existing-disk-image.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6-Screenshot-step2-existing-disk-image.png
new file mode 100644
index 0000000..3805b84
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6-Screenshot-step2-existing-disk-image.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-guest1-rhel5-64-final.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-guest1-rhel5-64-final.png
new file mode 100644
index 0000000..a0685cd
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-guest1-rhel5-64-final.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step1.png
new file mode 100644
index 0000000..a2d0836
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step2.png
new file mode 100644
index 0000000..e55c49a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step3.png
new file mode 100644
index 0000000..f5bc777
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step4.png
new file mode 100644
index 0000000..4791de4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step5.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step5.png
new file mode 100644
index 0000000..5aa1fa0
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step5.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_virt_manager.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_virt_manager.png
new file mode 100644
index 0000000..d2538a7
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/rhel6_virt_manager.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/selinux_uuid_block.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/selinux_uuid_block.png
new file mode 100644
index 0000000..d1a69a9
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/selinux_uuid_block.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-1.png
new file mode 100644
index 0000000..eddb949
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-2.png
new file mode 100644
index 0000000..3738c87
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-3.png
new file mode 100644
index 0000000..5f3de0f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-4.png
new file mode 100644
index 0000000..b17a6fb
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step-1-1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step-1-1.png
new file mode 100644
index 0000000..ed6dc3b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step-1-1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step1-1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step1-1.png
new file mode 100644
index 0000000..87a0e0b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step1-1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step1-2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step1-2.png
new file mode 100644
index 0000000..871e7bb
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step1-2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step2-1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step2-1.png
new file mode 100644
index 0000000..b7f01ae
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step2-1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step2-2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step2-2.png
new file mode 100644
index 0000000..25f3edd
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step2-2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step2-3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step2-3.png
new file mode 100644
index 0000000..99b51fc
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step2-3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step2-4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step2-4.png
new file mode 100644
index 0000000..8910ab3
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step2-4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step3-1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step3-1.png
new file mode 100644
index 0000000..689a2a7
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step3-1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step4-1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step4-1.png
new file mode 100644
index 0000000..f12e5fd
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step4-1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step4-2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step4-2.png
new file mode 100644
index 0000000..de53e6c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step4-2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step5-1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step5-1.png
new file mode 100644
index 0000000..d636dcd
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step5-1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step5-2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step5-2.png
new file mode 100644
index 0000000..b76a181
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step5-2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step5-3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step5-3.png
new file mode 100644
index 0000000..bd1e219
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/step5-3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/type_assigned-KVM_PV.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/type_assigned-KVM_PV.png
new file mode 100644
index 0000000..cdc7c6d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/type_assigned-KVM_PV.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/type_assigned-KVM_PV_new.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/type_assigned-KVM_PV_new.png
new file mode 100644
index 0000000..adb335f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/type_assigned-KVM_PV_new.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/v2v-add_storagepool.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/v2v-add_storagepool.png
new file mode 100644
index 0000000..82710ae
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/v2v-add_storagepool.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/v2v-select_host.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/v2v-select_host.png
new file mode 100644
index 0000000..b9b1c99
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/v2v-select_host.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/v2v-storage_tab.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/v2v-storage_tab.png
new file mode 100644
index 0000000..fea967c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/v2v-storage_tab.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager-enable-disk-io.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager-enable-disk-io.png
new file mode 100644
index 0000000..9840461
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager-enable-disk-io.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager-enable-networkio.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager-enable-networkio.png
new file mode 100644
index 0000000..6260da0
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager-enable-networkio.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_nfs_step1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_nfs_step1.png
new file mode 100644
index 0000000..43d4e7e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_nfs_step1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_nfs_step2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_nfs_step2.png
new file mode 100644
index 0000000..7e5d6c8
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_nfs_step2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_storage_pool1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_storage_pool1.png
new file mode 100644
index 0000000..3896a18
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_storage_pool1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_storage_pool2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_storage_pool2.png
new file mode 100644
index 0000000..1a29807
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_storage_pool2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_hardware.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_hardware.png
new file mode 100644
index 0000000..08568e6
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_hardware.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_hardware_wizard1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_hardware_wizard1.png
new file mode 100644
index 0000000..b45e590
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_hardware_wizard1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_home.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_home.png
new file mode 100644
index 0000000..62dbd94
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_home.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_host_details_storage.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_host_details_storage.png
new file mode 100644
index 0000000..e4c7c00
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_host_details_storage.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_main.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_main.png
new file mode 100644
index 0000000..e6b7b0d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_main.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_newicon.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_newicon.png
new file mode 100644
index 0000000..9c0a829
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_newicon.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_select_host.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_select_host.png
new file mode 100644
index 0000000..cf2fc41
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_select_host.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_1_name_and_type.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_1_name_and_type.png
new file mode 100644
index 0000000..4c1aa23
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_1_name_and_type.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_2_target_path.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_2_target_path.png
new file mode 100644
index 0000000..67d9310
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_2_target_path.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_3_result.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_3_result.png
new file mode 100644
index 0000000..c2dc6ba
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_3_result.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_1_name_and_type.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_1_name_and_type.png
new file mode 100644
index 0000000..516a12c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_1_name_and_type.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_2_paths_and_format.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_2_paths_and_format.png
new file mode 100644
index 0000000..86a2e05
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_2_paths_and_format.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_3_result.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_3_result.png
new file mode 100644
index 0000000..20ee4b6
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_3_result.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_1_name_and_type.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_1_name_and_type.png
new file mode 100644
index 0000000..7879370
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_1_name_and_type.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_2a_paths_and_pool.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_2a_paths_and_pool.png
new file mode 100644
index 0000000..1547ee7
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_2a_paths_and_pool.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_2b_format_warning.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_2b_format_warning.png
new file mode 100644
index 0000000..0b88899
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_2b_format_warning.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_3_result.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_3_result.png
new file mode 100644
index 0000000..9510682
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_3_result.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_virtualization_method.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_virtualization_method.png
new file mode 100644
index 0000000..6dab167
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_virtualization_method.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-disk2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-disk2.png
new file mode 100644
index 0000000..cebc522
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-disk2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-finish3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-finish3.png
new file mode 100644
index 0000000..afaed72
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-finish3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-step1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-step1.png
new file mode 100644
index 0000000..1f8e7c4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-step1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-step2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-step2.png
new file mode 100644
index 0000000..bdef1fd
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-step2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-finish3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-finish3.png
new file mode 100644
index 0000000..700e4bc
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-finish3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step1-new.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step1-new.png
new file mode 100644
index 0000000..3c24dd8
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step1-new.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step1.png
new file mode 100644
index 0000000..3235be4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step2-new.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step2-new.png
new file mode 100644
index 0000000..293c735
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step2-new.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step2.png
new file mode 100644
index 0000000..f61cc79
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio0-customize.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio0-customize.png
new file mode 100644
index 0000000..49e56bb
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio0-customize.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio3-finished.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio3-finished.png
new file mode 100644
index 0000000..603725e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtio3-finished.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtual_machine_overview.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtual_machine_overview.png
new file mode 100644
index 0000000..8a60772
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/virtual_machine_overview.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm-add_hardware1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm-add_hardware1.png
new file mode 100644
index 0000000..e4e761d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm-add_hardware1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm_add_hardware.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm_add_hardware.png
new file mode 100644
index 0000000..ca4b140
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm_add_hardware.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm_add_hardware_new.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm_add_hardware_new.png
new file mode 100644
index 0000000..406dc05
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm_add_hardware_new.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm_info_button.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm_info_button.png
new file mode 100644
index 0000000..7c080f7
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm_info_button.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm_info_button_new.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm_info_button_new.png
new file mode 100644
index 0000000..4156307
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vm_info_button_new.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create1.png
new file mode 100644
index 0000000..1768ae8
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create2.png
new file mode 100644
index 0000000..6adb9fe
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create3_ipv4addspace.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create3_ipv4addspace.png
new file mode 100644
index 0000000..6b884c5
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create3_ipv4addspace.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create4_dhcprange.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create4_dhcprange.png
new file mode 100644
index 0000000..f72639a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create4_dhcprange.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create5_connectphysnet.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create5_connectphysnet.png
new file mode 100644
index 0000000..0219a18
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create5_connectphysnet.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create6_finish.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create6_finish.png
new file mode 100644
index 0000000..632def4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create6_finish.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create7_maintab.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create7_maintab.png
new file mode 100644
index 0000000..b7df642
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create7_maintab.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_maintab.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_maintab.png
new file mode 100644
index 0000000..d2104e8
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_maintab.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_menuselect.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_menuselect.png
new file mode 100644
index 0000000..7a7623d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_menuselect.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-01-switch.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-01-switch.png
new file mode 100644
index 0000000..9aa78c1
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-01-switch.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-02-switchandtwoguests.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-02-switchandtwoguests.png
new file mode 100644
index 0000000..9256a76
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-02-switchandtwoguests.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-03-hostwithswitch.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-03-hostwithswitch.png
new file mode 100644
index 0000000..d41424a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-03-hostwithswitch.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-04-hostwithnatswitch.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-04-hostwithnatswitch.png
new file mode 100644
index 0000000..e94c04d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-04-hostwithnatswitch.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-05-switchwithdnsmasq.jpg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-05-switchwithdnsmasq.jpg
new file mode 100644
index 0000000..204d854
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-05-switchwithdnsmasq.jpg differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-06-routed-switch.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-06-routed-switch.png
new file mode 100644
index 0000000..5b5af96
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-06-routed-switch.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-07-isolated-switch.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-07-isolated-switch.png
new file mode 100644
index 0000000..1c234cb
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-07-isolated-switch.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-08-network-overview.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-08-network-overview.png
new file mode 100644
index 0000000..61c1342
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-08-network-overview.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-09-routed-mode-DMZ.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-09-routed-mode-DMZ.png
new file mode 100644
index 0000000..f1ea4e9
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-09-routed-mode-DMZ.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-10-routed-mode-datacenter.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-10-routed-mode-datacenter.png
new file mode 100644
index 0000000..35cd345
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-10-routed-mode-datacenter.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-11-router-mode-mac-restricted.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-11-router-mode-mac-restricted.png
new file mode 100644
index 0000000..bbf3882
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-11-router-mode-mac-restricted.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-12-network-tab-default.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-12-network-tab-default.png
new file mode 100644
index 0000000..63d3582
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/vn-12-network-tab-default.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/w7x86driverchosen.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/w7x86driverchosen.png
new file mode 100644
index 0000000..3f1a832
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/w7x86driverchosen.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/win2003_select_hal.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/win2003_select_hal.png
new file mode 100644
index 0000000..c8d4ecd
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/win2003_select_hal.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/win7paravirt-click-configure-before-install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/win7paravirt-click-configure-before-install.png
new file mode 100644
index 0000000..b692e68
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/images/win7paravirt-click-configure-before-install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html
new file mode 100644
index 0000000..f01a19d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html
@@ -0,0 +1,12693 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Virtualization Deployment and Administration Guide</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><meta name="description" content="This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a
preview. The included information and instructions should not be considered complete, and should be used with caution." /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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><div xml:lang="en-US" class="book" id="idp4733488" lang="en-US"><div class="titlepage"><div><div class="producttitle" font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><span class="productname">Fedora Draft Documentation</span> <span class="productnumber"></span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="idp4733488" class="title">Virtuali
zation Deployment and Administration Guide</h1></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h2 class="subtitle">Virtualization Documentation</h2></div><p class="edition">Edition 19.0.1</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 class="corpauthor">
+ <span class="inlinemediaobject"><object data="Common_Content/images/title_logo.svg" type="image/svg+xml"> </object></span>
+
+ </h3></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div xml:lang="en-US" class="authorgroup" lang="en-US"><div class="author"><h3 class="author"><span class="firstname">Laura</span> <span class="surname">Novich</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div></div><div class="author"><h3 class="author"><span class="firstname">Tahlia</span> <span class="surname">Richardson</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div></div><div class="author"><h3 class="author"><span class="firstname">Laura</span> <span class="surname">Bailey</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div></div><div class="author"><h3 class="author"><span class="firstname">Dayle</spa
n> <span class="surname">Parker</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div></div></div></div><hr /><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div id="idm118833520" class="legalnotice"><h1 class="legalnotice">Legal Notice</h1><div class="para">
+ Copyright <span class="trademark"></span>© 2013 Red Hat, Inc.
+ </div><div class="para">
+ The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at <a href="http://creativecommons.org/licenses/by-sa/3.0/">http://creativecommons.org/licenses/by-sa/3.0/</a>. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
+ </div><div class="para">
+ Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
+ </div><div class="para">
+ Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
+ </div><div class="para">
+ For guidelines on the permitted uses of the Fedora trademarks, refer to <a href="https://fedoraproject.org/wiki/Legal:Trademark_guidelines">https://fedoraproject.org/wiki/Legal:Trademark_guidelines</a>.
+ </div><div class="para">
+ <span class="trademark">Linux</span>® is the registered trademark of Linus Torvalds in the United States and other countries.
+ </div><div class="para">
+ <span class="trademark">Java</span>® is a registered trademark of Oracle and/or its affiliates.
+ </div><div class="para">
+ <span class="trademark">XFS</span>® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
+ </div><div class="para">
+ All other trademarks are the property of their respective owners.
+ </div></div></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div class="abstract"><h6>Abstract</h6><div class="para">
+
+ </div><div class="para">
+ This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization.
+ </div><div class="para">
+ Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.
+ </div></div></div></div><hr /></div><div class="toc"><dl><dt><span class="preface"><a href="#pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface">Preface</a></span></dt><dd><dl><dt><span class="section"><a href="#idm92841536">1. Document Conventions</a></span></dt><dd><dl><dt><span class="section"><a href="#idm105061744">1.1. Typographic Conventions</a></span></dt><dt><span class="section"><a href="#idm85695376">1.2. Pull-quote Conventions</a></span></dt><dt><span class="section"><a href="#idm90991408">1.3. Notes and Warnings</a></span></dt></dl></dd><dt><span class="section"><a href="#idm91623248">2. We Need Feedback!</a></span></dt></dl></dd><dt><span class="part"><a href="#idm75191904">I. Deployment</a></span></dt><dd><dl><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction">1. Introduction</a></span></dt><dd><dl><dt><span class="section"><a href="#idm103429472">1.1. What is i
n this guide?</a></span></dt><dt><span class="section"><a href="#idm108614496">1.2. Virtualization Documentation Suite</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_Requirements">2. System requirements</a></span></dt><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility">3. KVM guest virtual machine compatibility</a></span></dt><dd><dl><dt><span class="section"><a href="#idm93407568">3.1. Fedora 6 support limits</a></span></dt><dt><span class="section"><a href="#idm104483712">3.2. Supported CPU Models</a></span></dt><dd><dl><dt><span class="section"><a href="#para-CPU_Models">3.2.1. Guest CPU models</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions">4. Virtualization restrictions</a></span></dt><dd><dl><d
t><span class="section"><a href="#sect-chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-KVM_Restrictions">4.1. KVM restrictions</a></span></dt><dt><span class="section"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions">4.2. Application restrictions</a></span></dt><dt><span class="section"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions">4.3. Other restrictions</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation">5. Installing the virtualization packages</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_with_a_new_Red_Hat_Enterprise_Linux_installation">5.1. Configuring a V
irtualization Host installation</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system">5.2. Installing virtualization packages on an existing Fedora system</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation">6. Guest virtual machine installation overview</a></span></dt><dd><dl><dt><span class="section"><a href="#idm101231408">6.1. Guest virtual machine prerequisites and considerations</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install">6.2. Creating guests with virt-install</a></span></dt><dt><span class="section"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_
Virt_Manager-Creating_guests_with_virt_manager">6.3. Creating guests with virt-manager</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE">6.4. Installing guest virtual machines with PXE</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install">7. Installing a Red Hat Enterprise Linux 6 guest virtual machine on a Red Hat Enterprise Linux 6 host</a></span></dt><dd><dl><dt><span class="section"><a href="#idm112752688">7.1. Creating a Red Hat Enterprise Linux 6 guest with local installation media</a></span></dt><dt><span class="section"><a href="#idm78294688">7.2. Creating a Red Hat Enterprise Linux 6 guest with a network installation tree</a></span></dt><dt><span class="section"><a href="#idm86720352">7.3. Creating a Red Hat Enterprise Linux 6 guest with PXE</a></span></dt></dl></
dd><dt><span class="chapter"><a href="#idm74619792">8. Virtualizing Fedora on Other Platforms</a></span></dt><dd><dl><dt><span class="section"><a href="#idm119852976">8.1. On VMWare</a></span></dt><dt><span class="section"><a href="#idm93540832">8.2. On Hyper-V</a></span></dt></dl></dd><dt><span class="chapter"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest">9. Installing a fully-virtualized Windows guest</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_virt-install">9.1. Using virt-install to create a guest</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers">10. KVM Para-virtualized Drivers</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-
Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers">10.1. Installing the KVM Windows para-virtualized drivers</a></span></dt><dt><span class="section"><a href="#form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager">10.2. Installing the drivers on an installed Windows guest virtual machine</a></span></dt><dt><span class="section"><a href="#form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk">10.3. Installing drivers during the Windows installation</a></span></dt><dt><span class="section"><a href="#idm123282160">10.4. Using the para-virtualized drivers with Red Hat Enterprise Linux 3.9 guests</a></span></dt><dt><span class="section"><a href="#form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_driver
s-Using_KVM_para_virtualized_drivers_for_existing_devices">10.5. Using KVM para-virtualized drivers for existing devices</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices">10.6. Using KVM para-virtualized drivers for new devices</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration">11. Network configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_address_translation_NAT_with_libvirt">11.1. Network Address Translation (NAT) with libvirt</a></span></dt><dt><span class="section"><a href="#idm103889488">11.2. Disabling vhost-net</a></span></dt><dt><span class="section"><a hr
ef="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt">11.3. Bridged networking with libvirt</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config">12. PCI device configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-AI_device_to_a_host">12.1. Assigning a PCI device with virsh</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host">12.2. Assigning a PCI device with virt-manager</a></span></dt><dt><span class="section"><a href="#idm113629632">12.3. PCI device assignment with virt-install</a></span></dt><dt><span class="section"><a href="#idm123828480">12.4. Detaching an assigned PCI d
evice</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV">13. SR-IOV</a></span></dt><dd><dl><dt><span class="section"><a href="#idm96737120">13.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works">13.2. Using SR-IOV</a></span></dt><dt><span class="section"><a href="#idm98028304">13.3. Troubleshooting SR-IOV</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management">14. KVM guest timing management</a></span></dt><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting">15. Network booting with libvirt</a></span></dt><dd><dl><dt><span class="section"><a href="#idm104740480">15.1. Preparing the boot server</a></spa
n></dt><dd><dl><dt><span class="section"><a href="#idm120289520">15.1.1. Setting up a PXE boot server on a private libvirt network</a></span></dt></dl></dd><dt><span class="section"><a href="#idm79200128">15.2. Booting a guest using PXE</a></span></dt><dd><dl><dt><span class="section"><a href="#idm108221824">15.2.1. Using bridged networking</a></span></dt><dt><span class="section"><a href="#idm94661024">15.2.2. Using a private libvirt network</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#qemu-ga">16. QEMU Guest Agent</a></span></dt><dd><dl><dt><span class="section"><a href="#idm117719760">16.1. Set Up Communication between Guest Agent and Host</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="#idm99059024">II. Administration</a></span></dt><dd><dl><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-Server_best_practices">17. Server best practices</a></span></dt><dt><span class="chapter"><a href="#chap-Virtual
ization-Security_for_virtualization">18. Security for virtualization</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Security_for_virtualization-Storage_security_issues">18.1. Storage security issues</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization">18.2. SELinux and virtualization</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Security_for_virtualization-SELinux_considerations">18.3. SELinux</a></span></dt><dt><span class="section"><a href="#idm81619664">18.4. Virtualization firewall information</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-sVirt">19. sVirt</a></span></dt><dd><dl><dt><span class="section"><a href="#idm100037280">19.1. Security and Virtualization</a></span></dt><dt><span class="section"><a href="#idm96599200">19.2. sVirt labeling</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization
_Administration_Guide-KVM_live_migration">20. KVM live migration</a></span></dt><dd><dl><dt><span class="section"><a href="#Live_migration_requirements">20.1. Live migration requirements</a></span></dt><dt><span class="section"><a href="#Live_migration_and_RHEL_compatibility">20.2. Live migration and Fedora version compatibility </a></span></dt><dt><span class="section"><a href="#shared-storage-nfs-migration">20.3. Shared storage example: NFS for a simple migration</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh">20.4. Live KVM migration with virsh</a></span></dt><dd><dl><dt><span class="section"><a href="#add-notes">20.4.1. Additonal tips for migration with virsh </a></span></dt><dt><span class="section"><a href="#virsh-migration-arguements">20.4.2. Additional options for the virsh migrate command</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Virtualization-KVM_live_migration-Migrati
ng_with_virt_manager">20.5. Migrating with virt-manager</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests">21. Remote management of guests</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_with_SSH">21.1. Remote management with SSH</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL">21.2. Remote management over TLS and SSL</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes">21.3. Transport modes</a></span></dt></dl></dd><dt><span class="chapter"><a href="#sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM">22. Overcommitting with KVM</a></span></dt><dt><span class="chapter"><a href="#chap-KSM">23. KSM</a></span></dt><dt><s
pan class="chapter"><a href="#chap-Virtualization_Administration_GuideAdvanced">24. Advanced virtualization administration</a></span></dt><dd><dl><dt><span class="section"><a href="#idm108086240">24.1. Control Groups (cgroups)</a></span></dt><dt><span class="section"><a href="#idm115160736">24.2. Hugepage support</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-Tips_and_tricks">25. Miscellaneous administration tasks</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Automatically_starting_guests">25.1. Automatically starting guests</a></span></dt><dt><span class="section"><a href="#sect-mem-dump-off">25.2. Guest memory allocation</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Using_qemu_img">25.3. Using qemu-img</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions">25.4.
Verifying virtualization extensions</a></span></dt><dt><span class="section"><a href="#idm110949808">25.5. Setting KVM processor affinities</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address">25.6. Generating a new unique MAC address</a></span></dt><dt><span class="section"><a href="#idm106199024">25.7. Improving guest response time</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests">25.8. Disable SMART disk monitoring for guests</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server">25.9. Configuring a VNC Server</a></span></dt><dt><span class="section"><a href="#sect-gracefully-shut-down-guests">25.10. Gracefully shutting down guests</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers">25.11. Virtual machine time
r management with libvirt</a></span></dt><dt><span class="section"><a href="#sect-perf-mon">25.12. Using PMU to monitor guest performance</a></span></dt><dt><span class="section"><a href="#sect-s3-s4">25.13. Guest virtual machine power management</a></span></dt><dt><span class="section"><a href="#sect-qemu-ga">25.14. QEMU Guest Agent Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-guest-synch">25.14.1. guest-sync</a></span></dt><dt><span class="section"><a href="#subsect-guest-synch-delimited">25.14.2. guest-sync-delimited</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-limit-redirection">25.15. Setting a limit on device redirection</a></span></dt><dt><span class="section"><a href="#sect-dynamic-vNIC">25.16. Dynamically changing a host or a network bridge that is attached to a virtual NIC</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-Storage_Concepts">26. Storage concepts</a></
span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Storage_Concepts-Storage_Pools">26.1. Storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Concepts-Volumes">26.2. Volumes </a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools">27. Storage pools</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating_Storage_Pools">27.1. Creating storage pools </a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-Dedicated_Disk_Devices">27.1.1. Disk-based storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-File_Systems">27.1.2. Partition-based storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-Local_Directories">27.1.3. Directory-based storage poo
ls</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-LVM">27.1.4. LVM-based storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-iSCSI">27.1.5. iSCSI-based storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-NFS">27.1.6. NFS-based storage pools</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-Storage_Volumes">28. Volumes </a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Storage_Volumes-Creating_volumes">28.1. Creating volumes</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Volumes-Cloning_volumes">28.2. Cloning volumes</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests">28.3. Adding storage devices to guests</a></span></dt
><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Adding_storage_devices_to_guests-Adding_file_based_storage_to_a_guest">28.3.1. Adding file based storage to a guest</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest">28.3.2. Adding hard drives and other block devices to a guest</a></span></dt><dt><span class="section"><a href="#sect-Managing_storage_controllers_in_a_guest">28.3.3. Managing storage controllers in a guest</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Virtualization-Storage_Volumes-Deleting_volumes">28.4. Deleting and removing volumes</a></span></dt></dl></dd><dt><span class="chapter"><a href="#vhostmd">29. The Virtual Host Metrics Daemon (vhostmd)</a></span></dt><dd><dl><dt><span class="section"><a href="#idm109965248">29.1. Installing vhostmd on the host</a></span></dt><dt><span class="section"><a href="#idm99221600">2
9.2. Configuration of vhostmd</a></span></dt><dt><span class="section"><a href="#idm74152464">29.3. Starting and stopping the daemon</a></span></dt><dt><span class="section"><a href="#idm100836656">29.4. Verifying that vhostmd is working from the host</a></span></dt><dt><span class="section"><a href="#idm92004288">29.5. Configuring guests to see the metrics</a></span></dt><dt><span class="section"><a href="#idm97572736">29.6. Using vm-dump-metrics in Fedora guests to verify operation</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="#idm94886384">III. Appendicies</a></span></dt><dd><dl><dt><span class="appendix"><a href="#chap-Virtualization_Administration_Guide-Troubleshooting">A. Troubleshooting</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Troubleshooting_-Debugging_and_troubleshooting_">A.1. Debugging and troubleshooting tools</a></span></dt><dt><span class="section"><a href="#idm114039008">A.2. kvm_stat</a></span></dt><d
t><span class="section"><a href="#sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles">A.3. Troubleshooting with serial consoles</a></span></dt><dt><span class="section"><a href="#idm124509312">A.4. Virtualization log files</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Troubleshooting-Loop_device_errors">A.5. Loop device errors</a></span></dt><dt><span class="section"><a href="#live-migration-errors">A.6. Live Migration Errors</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS">A.7. Enabling Intel VT-x and AMD-V virtualization hardware extensions in BIOS</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Troubleshooting-KVM_networking_performance">A.8. KVM networking performance</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Troubleshooting-Missing_Characters_Guest_Console_Japanes
e_Keyboard">A.9. Missing characters on guest console with Japanese keyboard</a></span></dt><dt><span class="section"><a href="#sec-known-issues-windows-xp-guests">A.10. Known Windows XP guest issues</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idm61545728">B. Common <span class="application"><strong>libvirt</strong></span> errors and troubleshooting</a></span></dt><dd><dl><dt><span class="section"><a href="#App_Libvirt_Daemon">B.1. <span class="application"><strong>libvirtd</strong></span> failed to start</a></span></dt><dt><span class="section"><a href="#App_Hypervisor_Connection_Fail">B.2. The URI failed to connect to the hypervisor</a></span></dt><dd><dl><dt><span class="section"><a href="#Sect_Cannot_read_CA_certificate">B.2.1. Cannot read CA certificate</a></span></dt><dt><span class="section"><a href="#Sect_Failed_to_connect_socket">B.2.2. Failed to connect socket ... : Permission denied</a></span></dt><dt><span class="section"><a href="#Sect_Other_Con
nectivity_Errors">B.2.3. Other connectivity errors</a></span></dt></dl></dd><dt><span class="section"><a href="#App_Domain_Processor">B.3. The guest virtual machine cannot be started: <code class="computeroutput">internal error guest CPU is not compatible with host CPU</code></a></span></dt><dt><span class="section"><a href="#App_Domain_Monitor_Socket">B.4. Guest starting fails with error: <code class="computeroutput">monitor socket did not show up</code></a></span></dt><dt><span class="section"><a href="#App_Domain_Console">B.5. <code class="computeroutput">Internal error cannot find character device (null)</code></a></span></dt><dt><span class="section"><a href="#App_Domain_Not_Booting">B.6. Guest virtual machine booting stalls with error: <code class="computeroutput">No boot device</code></a></span></dt><dt><span class="section"><a href="#App_Virt_Net_Not_Starting">B.7. Virtual network <em class="replaceable"><code>default</code></em> has not been started</a></span></dt><
dt><span class="section"><a href="#App_PXE_Guest_Boot_Fail">B.8. PXE boot (or DHCP) on guest failed</a></span></dt><dt><span class="section"><a href="#App_Macvtap">B.9. Guest can reach outside network, but cannot reach host when using macvtap interface</a></span></dt><dt><span class="section"><a href="#App_DHCP_Response_Checksums">B.10. Could not add rule to fixup DHCP response checksums on network <em class="replaceable"><code>'default'</code></em></a></span></dt><dt><span class="section"><a href="#App_Bridge_Device">B.11. Unable to add bridge br0 port vnet0: No such device</a></span></dt><dt><span class="section"><a href="#App_Generic_Ethernet">B.12. Guest is unable to start with error: <code class="computeroutput">warning: could not open /dev/net/tun</code></a></span></dt><dt><span class="section"><a href="#App_Migration_Address">B.13. Migration fails with <code class="computeroutput">Error: unable to resolve address</code></a></span></dt><dt><span class="section"><a href
="#App_Migration_Disk_Image">B.14. Migration fails with <code class="computeroutput">Unable to allow access for disk path: No such file or directory</code></a></span></dt><dt><span class="section"><a href="#App_No_Guest_Machines">B.15. No guest virtual machines are present when <span class="application"><strong>libvirtd</strong></span> is started</a></span></dt><dt><span class="section"><a href="#App_TCP_Ports">B.16. Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor</a></span></dt><dt><span class="section"><a href="#App_XML_Errors">B.17. Common XML errors</a></span></dt><dd><dl><dt><span class="section"><a href="#idm115560112">B.17.1. Editing domain definition</a></span></dt><dt><span class="section"><a href="#idm117772112">B.17.2. XML syntax errors</a></span></dt><dt><span class="section"><a href="#idm115393088">B.17.3. Logic and configuration errors</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a
href="#netkvm-parameters">C. NetKVM Driver Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idm107871952">C.1. Configurable parameters for NetKVM</a></span></dt></dl></dd><dt><span class="appendix"><a href="#chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist">D. qemu-kvm Whitelist</a></span></dt><dd><dl><dt><span class="section"><a href="#idm107978896">D.1. Introduction</a></span></dt><dt><span class="section"><a href="#idm77975568">D.2. Basic options</a></span></dt><dt><span class="section"><a href="#idm77194320">D.3. Disk options</a></span></dt><dt><span class="section"><a href="#idm104274176">D.4. Display options</a></span></dt><dt><span class="section"><a href="#idm114721584">D.5. Network options</a></span></dt><dt><span class="section"><a href="#idm93867376">D.6. Device options</a></span></dt><dt><span class="section"><a href="#idm89508384">D.7. Linux/Multiboot boot </a></span></dt><dt><span class="section"><a href="#idm97161328">D.8. Expe
rt options</a></span></dt><dt><span class="section"><a href="#idm79818416">D.9. Help and information options</a></span></dt><dt><span class="section"><a href="#idm99738544">D.10. Miscellaneous options</a></span></dt></dl></dd><dt><span class="appendix"><a href="#chap-Virtualization_Administration_Guide-Managing_guests_with_virsh">E. Managing guests with virsh</a></span></dt><dd><dl><dt><span class="section"><a href="#idm93487200">E.1. virsh command quick reference</a></span></dt><dt><span class="section"><a href="#sect-Attaching_and_updating_a_device_with_virsh">E.2. Attaching and updating a device with virsh</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor">E.3. Connecting to the hypervisor</a></span></dt><dt><span class="section"><a href="#form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file">E.4. Creating a virtual machine XML dump (configuration
file)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-multifunction-pci-install">E.4.1. Adding multifunction PCI devices to KVM guests</a></span></dt></dl></dd><dt><span class="section"><a href="#idm115600896">E.5. Suspending, resuming, saving and restoring a guest</a></span></dt><dt><span class="section"><a href="#idm70012976">E.6. Shutting down, rebooting and force-shutdown of a guest</a></span></dt><dt><span class="section"><a href="#idm103535312">E.7. Retrieving guest information</a></span></dt><dt><span class="section"><a href="#idm123330576">E.8. Retrieving node information</a></span></dt><dt><span class="section"><a href="#idm107205776">E.9. Storage pool information</a></span></dt><dt><span class="section"><a href="#idm114956880">E.10. Displaying per-guest information</a></span></dt><dt><span class="section"><a href="#idm92394304">E.11. Managing virtual networks</a></span></dt><dt><span class="section"><a href="#migrating_guests-with-virsh">E.12. Migra
ting guests with virsh</a></span></dt><dt><span class="section"><a href="#sect-man-disk-image">E.13. Disk image management with live block copy</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-blockcommit">E.13.1. Using blockcommit to shorten a backing chain</a></span></dt><dt><span class="section"><a href="#sub-sect-blockpull">E.13.2. Using blockpull to shorten a backing chain</a></span></dt><dt><span class="section"><a href="#sub-sect-blkresize">E.13.3. Using blockresize to change the size of a domain path</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-guest-cpu-model-config">E.14. Guest CPU model configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-guest-cpu-intro">E.14.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-learn-about-host-cpu">E.14.2. Learning about the host CPU model</a></span></dt><dt><span class="section"><a href="#idm90465808">E.14.3. Determining a compatible CPU model to su
it a pool of hosts</a></span></dt><dt><span class="section"><a href="#idm111893984">E.14.4. Configuring the guest CPU model</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager">F. Managing guests with the Virtual Machine Manager (virt-manager)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Starting_virt_manager">F.1. Starting virt-manager</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window">F.2. The Virtual Machine Manager main window</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_">F.3. The virtual hardware details
window</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_">F.4. Virtual Machine graphical console</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window">F.5. Adding a remote connection</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details">F.6. Displaying guest details</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring">F.7. Performance monitoring</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage">F.8. Displaying CPU usage for guests</a></span></dt><dt><
span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage">F.9. Displaying CPU usage for hosts</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO">F.10. Displaying Disk I/O</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO">F.11. Displaying Network I/O</a></span></dt></dl></dd><dt><span class="appendix"><a href="#chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs">G. Guest disk access with offline tools</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-introduction-Virtualization_Administration_Guide-Guest_Disks_libguestfs">G.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-Terminology-Guest_Disks_libguestfs">G.2. Terminology</a></span></dt><dt
><span class="section"><a href="#sect-Guide-Guest_Disks_libguestfs-installation">G.3. Installation</a></span></dt><dt><span class="section"><a href="#sect-the_guestfish_shell">G.4. The guestfish shell</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Viewing_file_systems_with_guestfish">G.4.1. Viewing file systems with guestfish</a></span></dt><dt><span class="section"><a href="#sect-Modifying-files-with-guestfish">G.4.2. Modifying files with guestfish</a></span></dt><dt><span class="section"><a href="#sect-Other-actions-with-guestfish">G.4.3. Other actions with guestfish</a></span></dt><dt><span class="section"><a href="#sect-Shell-scripting-with-guestfish">G.4.4. Shell scripting with guestfish</a></span></dt><dt><span class="section"><a href="#sect-Augeas-and-libguestfs-scripting">G.4.5. Augeas and libguestfs scripting</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-other-commands">G.5. Other commands</a></span></dt><dt><span class="section"
><a href="#sect-virt-rescue">G.6. virt-rescue: The rescue shell</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-virt-rescue-intro">G.6.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-run-virt-rescue">G.6.2. Running virt-rescue</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-virt-df">G.7. virt-df: Monitoring disk usage</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-virt-df-intro">G.7.1. Introduction</a></span></dt><dt><span class="section"><a href="#run-virt-df">G.7.2. Running virt-df</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-virt-resize">G.8. virt-resize: resizing guests offline</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-virt-resize-intro">G.8.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-expand-disk-image">G.8.2. Expanding a disk image</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-virt-inspector">G.9. virt-insp
ector: inspecting guests</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-virt-inspector-intro">G.9.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-virt-inspector-install">G.9.2. Installation</a></span></dt><dt><span class="section"><a href="#sect-virt-inspector-run">G.9.3. Running virt-inspector</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-virt-win-reg">G.10. virt-win-reg: Reading and editing the Windows Registry</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-virt-win-reg-intro">G.10.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-virt-win-reg-install">G.10.2. Installation</a></span></dt><dt><span class="section"><a href="#sect-virt-win-reg-use">G.10.3. Using virt-win-reg</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Using-API-Programming-Languages">G.11. Using the API from Programming Languages</a></span></dt><dd><dl><dt><span class="section"><a href="#A
PI-and-C">G.11.1. Interaction with the API via a C program</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-libguestfs-troubleshoot">G.12. Troubleshooting</a></span></dt><dt><span class="section"><a href="#sect-libguestfs-more-docs">G.13. Where to find further documentation</a></span></dt></dl></dd><dt><span class="appendix"><a href="#chap-Virtualization_Administration_Guide-Virtual_Networking">H. Virtual Networking</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-virtual_network-switches-livbvirt">H.1. Virtual network switches</a></span></dt><dt><span class="section"><a href="#sect-Network_Address_Translation-libvirt">H.2. Network Address Translation</a></span></dt><dt><span class="section"><a href="#sect-network-protocols">H.3. Networking protocols</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-DNS_and_DHCP-protocols-libvirt">H.3.1. DNS and DHCP</a></span></dt><dt><span class="section"><a href="#sub-sect-routed-mode-libvirt"
>H.3.2. Routed mode</a></span></dt><dt><span class="section"><a href="#sub-sect-iso-mode">H.3.3. Isolated mode</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-the-Default_Configuration-libvirt">H.4. The default configuration</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Virtual_Networking-Example_scenarios">H.5. Examples of common scenarios</a></span></dt><dd><dl><dt><span class="section"><a href="#sub-sect-routed-mode">H.5.1. Routed mode</a></span></dt><dt><span class="section"><a href="#sub-sect-nat-mode">H.5.2. NAT mode</a></span></dt><dt><span class="section"><a href="#sub-sect-isolated-mode">H.5.3. Isolated mode</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Virtualization-Virtual_Networking-Managing_a_virtual_network">H.6. Managing a virtual network</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Virtual_Networking-Creating_a_virtual_network">H.7. Creating a virtual network</a></span><
/dt><dt><span class="section"><a href="#sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest">H.8. Attaching a virtual network to a guest</a></span></dt><dt><span class="section"><a href="#sect-attch-nic-physdev">H.9. Directly attaching to physical interface</a></span></dt><dt><span class="section"><a href="#sect-applying-network-filtering">H.10. Applying network filtering</a></span></dt><dd><dl><dt><span class="section"><a href="#intro-sub-sect-applying-network-filtering">H.10.1. Introduction</a></span></dt><dt><span class="section"><a href="#sub-sect-filt-chain">H.10.2. Filtering chains</a></span></dt><dt><span class="section"><a href="#sub-sect-filt-chain-props">H.10.3. Filtering chain priorities</a></span></dt><dt><span class="section"><a href="#sub-sect-vars-in-filters">H.10.4. Usage of variables in filters</a></span></dt><dt><span class="section"><a href="#sub-sect-auto-IP-add-detect-dhcp-snoop">H.10.5. Automatic IP address detection and DHCP snoop
ing</a></span></dt><dt><span class="section"><a href="#sub-sect-vars-reserved">H.10.6. Reserved Variables</a></span></dt><dt><span class="section"><a href="#sub-sect-element-oview">H.10.7. Element and attribute overview</a></span></dt><dt><span class="section"><a href="#sub-sect-ref-filter">H.10.8. References to other filters</a></span></dt><dt><span class="section"><a href="#sub-sect-filter-rules">H.10.9. Filter rules</a></span></dt><dt><span class="section"><a href="#sub-sect-supp-pros">H.10.10. Supported protocols</a></span></dt><dt><span class="section"><a href="#sub-sect-adv-filt-topics">H.10.11. Advanced Filter Configuration Topics</a></span></dt><dt><span class="section"><a href="#sub-sect-limitations-filters-network-subsystem">H.10.12. Limitations</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#appe-Virtualization-Additional_resources">I. Additional resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Additi
onal_resources-Online_resources">I.1. Online resources</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Additional_resources-Installed_documentation">I.2. Installed documentation</a></span></dt></dl></dd><dt><span class="appendix"><a href="#ch-lib-dom-xml">J. Manipulating the domain xml</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-gen-metadata">J.1. General information and metadata</a></span></dt><dt><span class="section"><a href="#sect-dom-xml-op-sys-boot">J.2. Operating system booting</a></span></dt><dd><dl><dt><span class="section"><a href="#sub-sect-op-sys-boot-bios-boot">J.2.1. BIOS bootloader</a></span></dt><dt><span class="section"><a href="#sub-sect-op-sys-host-boot">J.2.2. Host bootloader</a></span></dt><dt><span class="section"><a href="#sub-sect-op-sys-dir-kern-boot">J.2.3. Direct kernel boot</a></span></dt><dt><span class="section"><a href="#sub-sect-op-sys-cont-boot">J.2.4. Container boot</a></span></dt></dl></dd><dt><spa
n class="section"><a href="#sect-smbios-sys-info">J.3. SMBIOS system information</a></span></dt><dt><span class="section"><a href="#sect-cpu-allocation">J.4. CPU allocation</a></span></dt><dt><span class="section"><a href="#sect-cpu-tuning">J.5. CPU tuning</a></span></dt><dt><span class="section"><a href="#sect-mem-back">J.6. Memory backing</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-mem-tuning">J.7. Memory tuning</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-numa-node-tuning">J.8. NUMA node tuning</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-blk-io-tuning">J.9. Block I/O tuning</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-res-part">J.10. Resource partitioning</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-cpu-model-top">J.11. CPU model and topology</a></span></dt><dd><dl><dt><span class="section"><a href="#sub-sect-libvirt-dom-xml-res-part-gue
st-numa">J.11.1. Guest NUMA topology</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-libvirt-dom-xml-event-config">J.12. Events configuration</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-pwr-man">J.13. Power Management</a></span></dt><dt><span class="section"><a href="#idm101742368">J.14. Hypervisor features</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-time-keep">J.15. Time keeping</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-devices">J.16. Devices</a></span></dt><dd><dl><dt><span class="section"><a href="#sub-sect-libvirt-dom-xml-devices">J.16.1. Hard drives, floppy disks, CDROMs</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-filesystems">J.16.2. Filesystems</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-device-addresses">J.16.3. Device addresses</a></span></dt><dt><span class="section"><a href="#s
ub-section-libvirt-dom-xml-devices-controllers">J.16.4. Controllers</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-device-leases">J.16.5. Device leases</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-host-device-assignment">J.16.6. Host device assignment</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-redirected-devices">J.16.7. Redirected devices</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-smartcard">J.16.8. Smartcard devices</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-Network-interfaces">J.16.9. Network interfaces</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-input-devices">J.16.10. Input devices</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-hub-devices">J.16.11. Hub devices</a></span></dt><d
t><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-graphical-framebuffers">J.16.12. Graphical framebuffers</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-video">J.16.13. Video devices</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-consoles">J.16.14. Consoles, serial, parallel, and channel devices</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-guest-interface">J.16.15. Guest interfaces</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-channel">J.16.16. Channel</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-host-interface">J.16.17. Host interface</a></span></dt></dl></dd><dt><span class="section"><a href="#section-libvirt-dom-xml-sound-devices">J.17. Sound devices</a></span></dt><dt><span class="section"><a href="#section-libvirt-dom-xml-watchdog">J.18. Watchdog de
vice</a></span></dt><dt><span class="section"><a href="#section-libvirt-dom-xml-memory-baloon-device">J.19. Memory balloon device</a></span></dt><dt><span class="section"><a href="#section-libvirt-dom-xml-random-number-gen">J.20. Random number generator device</a></span></dt><dt><span class="section"><a href="#section-libvirt-dom-xml-tpm-device">J.21. TPM devices</a></span></dt><dt><span class="section"><a href="#section-libvirt-dom-xml-security-label">J.22. Security label</a></span></dt><dt><span class="section"><a href="#section-libvirt-dom-xml-example">J.23. Example domain XML configuration</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#appe-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Revision_History">K. Revision History</a></span></dt></dl></div><div xml:lang="en-US" class="preface" id="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface" lang="en-US"><div class="titlepage"><div><div><h1 c
lass="title">Preface</h1></div></div></div><div xml:lang="en-US" class="section" id="idm92841536" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm92841536">1. 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" id="idm105061744"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm105061744">1.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 keycaps 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 keycap, all presented in mono-spaced bold and all distinguishable thanks to context.
+ </div><div class="para">
+ Key combinations can be distinguished from keycaps 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>F2</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>F1</strong></span> to return to your X-Windows session.
+ </div></blockquote></div><div class="para">
+ The first paragraph highlights the particular keycap to press. The second highlights two key combinations (each a set of three keycaps with 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; dialog box text; labeled 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</strong></span> → <span class="guisubmenu"><strong>Preferences</strong></span> → <span class="guimenuitem"><strong>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</strong></span> → <span class="guisubmenu"><strong>Accessories</strong></span> → <span class="guimenuitem"><strong>Character Map</strong></span> from the main menu bar. Next, choose <span class="guimenu"><strong>Search</strong></span> → <span class="guimenuitem"><strong>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"><stron
g>Copy</strong></span> button. Now switch back to your document and choose <span class="guimenu"><strong>Edit</strong></span> → <span class="guimenuitem"><strong>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">
+ <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">
+ Publican is a <em class="firstterm">DocBook</em> publishing system.
+ </div></blockquote></div></div><div class="section" id="idm85695376"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm85695376">1.2. Pull-quote Conventions</h3></div></div></div><div class="para">
+ Terminal output and source code listings 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 add syntax highlighting as follows:
+ </div><pre class="programlisting">package org.<span class="perl_Function">jboss</span>.<span class="perl_Function">book</span>.<span class="perl_Function">jca</span>.<span class="perl_Function">ex1</span>;
+
+<span class="perl_Keyword">import</span> javax.naming.InitialContext;
+
+<span class="perl_Keyword">public</span> <span class="perl_Keyword">class</span> ExClient
+{
+ <span class="perl_Keyword">public</span> <span class="perl_DataType">static</span> <span class="perl_DataType">void</span> <span class="perl_Function">main</span>(String args[])
+ <span class="perl_Keyword">throws</span> Exception
+ {
+ InitialContext iniCtx = <span class="perl_Keyword">new</span> InitialContext();
+ Object ref = iniCtx.<span class="perl_Function">lookup</span>(<span class="perl_String">"EchoBean"</span>);
+ EchoHome home = (EchoHome) ref;
+ Echo echo = home.<span class="perl_Function">create</span>();
+
+ System.<span class="perl_Function">out</span>.<span class="perl_Function">println</span>(<span class="perl_String">"Created Echo"</span>);
+
+ System.<span class="perl_Function">out</span>.<span class="perl_Function">println</span>(<span class="perl_String">"Echo.echo('Hello') = "</span> + echo.<span class="perl_Function">echo</span>(<span class="perl_String">"Hello"</span>));
+ }
+}</pre></div><div class="section" id="idm90991408"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm90991408">1.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"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Notes are tips, shortcuts or alternative approaches 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><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><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 a box labeled 'Important' will not cause data loss but may cause irritation and frustration.
+ </div></div></div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Warnings should not be ignored. Ignoring warnings will most likely cause data loss.
+ </div></div></div></div></div><div xml:lang="en-US" class="section" id="idm91623248" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm91623248">2. We Need Feedback!</h2></div></div></div><a id="idm124111360" class="indexterm"></a><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>Documentation.</strong></span>
+ </div><div class="para">
+ When submitting a bug report, be sure to mention the manual's identifier: <em class="citetitle">doc-Virtualization_Deployment_and_Administration_Guide</em>
+ </div><div class="para">
+ If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.
+ </div></div></div><div class="part" id="idm75191904"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part I. Deployment</h1></div></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction">1. Introduction</a></span></dt><dd><dl><dt><span class="section"><a href="#idm103429472">1.1. What is in this guide?</a></span></dt><dt><span class="section"><a href="#idm108614496">1.2. Virtualization Documentation Suite</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_Requirements">2. System requirements</a></span></dt><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility">3. KVM guest virtual machine compatibility</a></span></dt><dd><dl><dt><span class="section"><a href="#idm934
07568">3.1. Fedora 6 support limits</a></span></dt><dt><span class="section"><a href="#idm104483712">3.2. Supported CPU Models</a></span></dt><dd><dl><dt><span class="section"><a href="#para-CPU_Models">3.2.1. Guest CPU models</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions">4. Virtualization restrictions</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-KVM_Restrictions">4.1. KVM restrictions</a></span></dt><dt><span class="section"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions">4.2. Application restrictions</a></span></dt><dt><span class="section"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restric
tions">4.3. Other restrictions</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation">5. Installing the virtualization packages</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_with_a_new_Red_Hat_Enterprise_Linux_installation">5.1. Configuring a Virtualization Host installation</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system">5.2. Installing virtualization packages on an existing Fedora system</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation">6. Guest virtual machine installation overview</a></span></dt><dd><dl><dt><span
class="section"><a href="#idm101231408">6.1. Guest virtual machine prerequisites and considerations</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install">6.2. Creating guests with virt-install</a></span></dt><dt><span class="section"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager">6.3. Creating guests with virt-manager</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE">6.4. Installing guest virtual machines with PXE</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install">7. Installing a Red Hat Enterprise Linux 6 guest virtual machine on a Red Hat Enterprise Linu
x 6 host</a></span></dt><dd><dl><dt><span class="section"><a href="#idm112752688">7.1. Creating a Red Hat Enterprise Linux 6 guest with local installation media</a></span></dt><dt><span class="section"><a href="#idm78294688">7.2. Creating a Red Hat Enterprise Linux 6 guest with a network installation tree</a></span></dt><dt><span class="section"><a href="#idm86720352">7.3. Creating a Red Hat Enterprise Linux 6 guest with PXE</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idm74619792">8. Virtualizing Fedora on Other Platforms</a></span></dt><dd><dl><dt><span class="section"><a href="#idm119852976">8.1. On VMWare</a></span></dt><dt><span class="section"><a href="#idm93540832">8.2. On Hyper-V</a></span></dt></dl></dd><dt><span class="chapter"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest">9. Installing a fully-virtualized Windows guest</a></span></dt><dd><dl><d
t><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_virt-install">9.1. Using virt-install to create a guest</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers">10. KVM Para-virtualized Drivers</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers">10.1. Installing the KVM Windows para-virtualized drivers</a></span></dt><dt><span class="section"><a href="#form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager">10.2. Installing the drivers on an installed Windows guest virtual machine</a></span></dt><dt><span class="section"><a href="#form-Virtualization_Host_Config
uration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk">10.3. Installing drivers during the Windows installation</a></span></dt><dt><span class="section"><a href="#idm123282160">10.4. Using the para-virtualized drivers with Red Hat Enterprise Linux 3.9 guests</a></span></dt><dt><span class="section"><a href="#form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices">10.5. Using KVM para-virtualized drivers for existing devices</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices">10.6. Using KVM para-virtualized drivers for new devices</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_In
stallation_Guide-Network_Configuration">11. Network configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_address_translation_NAT_with_libvirt">11.1. Network Address Translation (NAT) with libvirt</a></span></dt><dt><span class="section"><a href="#idm103889488">11.2. Disabling vhost-net</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt">11.3. Bridged networking with libvirt</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config">12. PCI device configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-AI_device_to_a_host">12.1. Assi
gning a PCI device with virsh</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host">12.2. Assigning a PCI device with virt-manager</a></span></dt><dt><span class="section"><a href="#idm113629632">12.3. PCI device assignment with virt-install</a></span></dt><dt><span class="section"><a href="#idm123828480">12.4. Detaching an assigned PCI device</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV">13. SR-IOV</a></span></dt><dd><dl><dt><span class="section"><a href="#idm96737120">13.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works">13.2. Using SR-IOV</a></span></dt><dt><span class="section"><a href="#idm98028304">13.3. Troubleshooting SR-IOV</a></span></dt></dl></dd><dt>
<span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management">14. KVM guest timing management</a></span></dt><dt><span class="chapter"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting">15. Network booting with libvirt</a></span></dt><dd><dl><dt><span class="section"><a href="#idm104740480">15.1. Preparing the boot server</a></span></dt><dd><dl><dt><span class="section"><a href="#idm120289520">15.1.1. Setting up a PXE boot server on a private libvirt network</a></span></dt></dl></dd><dt><span class="section"><a href="#idm79200128">15.2. Booting a guest using PXE</a></span></dt><dd><dl><dt><span class="section"><a href="#idm108221824">15.2.1. Using bridged networking</a></span></dt><dt><span class="section"><a href="#idm94661024">15.2.2. Using a private libvirt network</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#qemu-ga">16. QEMU Gu
est Agent</a></span></dt><dd><dl><dt><span class="section"><a href="#idm117719760">16.1. Set Up Communication between Guest Agent and Host</a></span></dt></dl></dd></dl></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 1. Introduction</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#idm103429472">1.1. What is in this guide?</a></span></dt><dt><span class="section"><a href="#idm108614496">1.2. Virtualization Documentation Suite</a></span></dt></dl></div><div class="section" id="idm103429472"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm103429472">1.1. What is in this guide?</h2></div></div></div><div class="para">
+ The <em class="citetitle">Virtualization Deployment and Administration Guide</em>, introduced in Fedora 19, resulted from the merger of the <em class="citetitle">Virtualization Host Installation and Guest Configuration Guide</em> and the <em class="citetitle">Virtualization Administration Guide</em>. This new guide provides complete information on both deploying a virtual setup on a Fedora virtualization host as well as how to administer and maintain the system. As such, this guide has 2 main parts:Deployment and Adminsitration. The appendix sections contain references and troubleshooting.
+ </div><div class="para">
+ The initial chapters in this guide outline the prerequisites to enable a Fedora host machine to deploy virtualization. System requirements, compatible hardware, support and product restrictions are covered in detail. The first part of this guide (Deployment) covers basic host configuration, including mandatory and optional virtualization packages, which are covered in <a class="xref" href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation">Chapter 5, <em>Installing the virtualization packages</em></a>. Later chapters in this part include guest virtual machine installation, which is covered in detail starting from <a class="xref" href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation">Chapter 6, <em>Guest virtual machine installation overview</em></a>, with procedures for installing fully virtualized Fedora guests and Windows para-virtualized guests using virt-manager and virsh. The part conclude
s with More detailed information on networking, PCI device configuration, SR-IOV, KVM guest timing management, and troubleshooting help for libvirt and SR-IOV is included later in the guide.
+ </div><div class="para">
+ The second part of this guide (Administration) covers more advanced configuration tactics, creating various storage pools and volumes, manipulating and finetuning memory and other resources, as well as administration tasks that can be performed using virsh and virt-manager to administer both hosts and guests.
+ </div><div class="para">
+ The last part of this guide (Appendix) contains troubleshooting information with steps that should be done before getting technical support (if possible), detailed reference guides for using QEMU-KVM flags, describing the Domain XML, and a complete CLI description of the commands used in Virsh and the screens used in Virt-manager. Additional tools that may be useful are also described in this part as well.
+ </div></div><div class="section" id="idm108614496"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm108614496">1.2. Virtualization Documentation Suite</h2></div></div></div><div class="para">
+ Fedora offers a wealth of documentation solutions across its various virtualization products. Coverage of Fedora and its inbuilt virtualization products include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="citetitle">Fedora — Virtualization Getting Started Guide</em>: This guide provides an introduction to virtualization concepts, advantages, and tools, and an overview of Red Hat virtualization documentation and products.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Fedora — Virtualization Deployment and Administration Guide</em> covers the installation, configuration, and maintenance of virtualization hosts and virtual machines.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Fedora — Virtualization Security Guide</em>: This guide provides an overview of virtualization security technologies provided by Red Hat. Also included are recommendations for securing hosts, guests, and shared infrastructure and resources in virtualized environments.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Fedora — Virtualization Tuning and Optimization Guide</em>: This guide provides tips, tricks and suggestions for making full use of virtualization performance features and options for your systems and guest virtual machines.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Fedora — V2V Guide</em> describes importing virtual machines from KVM, Xen and VMware ESX/ESX(i) hypervisors to Red Hat Enterprise Virtualization and KVM managed by libvirt.
+ </div></li></ul></div><div class="para">
+ The oVirt documentation suite provides information on installation, development of applications, configuration and usage of the Red Hat Enterprise Virtualization platform and its related products.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Administration Guide</em> describes how to set up, configure and manage Red Hat Enterprise Virtualization. It assumes that you have successfully installed the Red Hat Enterprise Virtualization Manager and hosts.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Command Line Shell Guide</em> contains information for installing and using the Red Hat Enterprise Virtualization Manager command line shell.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Developer Guide</em> explains how to use the REST API. It covers the fundamentals of the REST architectural concepts in the context of a virtualization environment and provides examples of the API in operation. It also documents the installation and use of the Python Software Development Kit.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Evaluation Guide</em> enables prospective customers to evaluate the features of Red Hat Enterprise Virtualization. Use this guide if you have an evaluation license.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Installation Guide</em> describes the installation prerequisites and procedures. Read this if you need to install Red Hat Enterprise Virtualization. The installation of hosts, Manager and storage are covered in this guide. You will need to refer to the <em class="citetitle">Red Hat Enterprise Virtualization Administration Guide</em> to configure the system before you can start using the platform.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Manager Release Notes</em> contain release specific information for Red Hat Enterprise Virtualization Managers.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Power User Portal Guide</em> describes how power users can create and manage virtual machines from the Red Hat Enterprise Virtualization User Portal.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Quick Start Guide</em> provides quick and simple instructions for first time users to set up a basic Red Hat Enterprise Virtualization environment.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Technical Notes</em> describe the changes made between the current release and the previous one.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Red Hat Enterprise Virtualization — Technical Reference Guide</em> describes the technical architecture of Red Hat Enterprise Virtualization and its interactions with existing infrastructure.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Red Hat Enterprise Virtualization — User Portal Guide</em> describes how users of the Red Hat Enterprise Virtualization system can access and use virtual desktops from the User Portal.
+ </div></li></ul></div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_Requirements" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 2. System requirements</h2></div></div></div><div class="para">
+ This chapter lists system requirements for successfully running virtual machines, referred to as VMs on Fedora. Virtualization is available for Fedora on the Intel 64 and AMD64 architecture.
+ </div><div class="para">
+ The KVM hypervisor is provided with Fedora 16.
+ </div><div class="para">
+ For information on installing the virtualization packages, see <a class="xref" href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation">Chapter 5, <em>Installing the virtualization packages</em></a>.
+ </div><div class="itemizedlist" id="item-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_requirements-Minimum_system_requirements"><h6>Minimum system requirements</h6><ul><li class="listitem"><div class="para">
+ 6 GB free disk space.
+ </div></li><li class="listitem"><div class="para">
+ 2 GB of RAM.
+ </div></li></ul></div><div class="itemizedlist" id="item-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_requirements-Recommended_system_requirements"><h6>Recommended system requirements</h6><ul><li class="listitem"><div class="para">
+ One processor core or hyper-thread for the maximum number of virtualized CPUs in a guest virtual machine and one for the host.
+ </div></li><li class="listitem"><div class="para">
+ 2 GB of RAM plus additional RAM for virtual machines.
+ </div></li><li class="listitem"><div class="para">
+ 6 GB disk space for the host, plus the required disk space for each virtual machine.
+ </div><div class="para">
+ Most guest operating systems will require at least 6GB of disk space, but the additional storage space required for each guest depends on its image format.
+ </div><div class="para">
+ For guest virtual machines using raw images, the guest's total required space <code class="literal">(total for raw format)</code> is equal to or greater than the sum of the space required by the guest's raw image files <code class="literal">(images)</code>, the 6GB space required by the host operating system <code class="literal">(host)</code>, and the swap space that guest will require <code class="literal">(swap)</code>.
+ </div><div class="equation"><h6>Equation 2.1. Calculating required space for guest virtual machines using raw images</h6><div class="equation-contents"><span class="mathphrase">total for raw format = images + host + swap</span></div></div><br class="equation-break" /><div class="para">
+ For qcow images, you must also calculate the expected maximum storage requirements of the guest <code class="literal">(total for qcow format)</code>, as qcow and qcow2 images grow as required. To allow for this expansion, first multiply the expected maximum storage requirements of the guest <code class="literal">(expected maximum guest storage)</code> by 1.01, and add to this the space required by the host <code class="literal">(host)</code>, and the necessary swap space <code class="literal">(swap)</code>.
+ </div><div class="equation"><h6>Equation 2.2. Calculating required space for guest virtual machines using qcow images</h6><div class="equation-contents"><span class="mathphrase">total for qcow format = (expected maximum guest storage * 1.01) + host + swap</span></div></div><br class="equation-break" /></li></ul></div><div class="para">
+ For more information on Guest virtual machine requirements refer to <a class="xref" href="#sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM">Chapter 22, <em>Overcommitting with KVM</em></a>.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm99730144">Calculating swap space</h5>
+ Using swap space can provide additional memory beyond the available physical memory. 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 the physical RAM of the host.
+ </div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_requirements-KVM_requirements"><h5 class="formalpara">KVM requirements</h5>
+ The KVM hypervisor requires:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ an Intel processor with the Intel VT-x and Intel 64 extensions for x86-based systems, or
+ </div></li><li class="listitem"><div class="para">
+ an AMD processor with the AMD-V and the AMD64 extensions.
+ </div></li></ul></div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_requirements-Storage_support"><h5 class="formalpara">Storage support</h5>
+ The guest virtual machine storage methods are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ files on local storage,
+ </div></li><li class="listitem"><div class="para">
+ physical disk partitions,
+ </div></li><li class="listitem"><div class="para">
+ locally connected physical LUNs,
+ </div></li><li class="listitem"><div class="para">
+ LVM partitions,
+ </div></li><li class="listitem"><div class="para">
+ NFS shared file systems,
+ </div></li><li class="listitem"><div class="para">
+ iSCSI,
+ </div></li><li class="listitem"><div class="para">
+ GFS2 clustered file systems,
+ </div></li><li class="listitem"><div class="para">
+ Fibre Channel-based LUNs, and
+ </div></li><li class="listitem"><div class="para">
+ Fibre Channel over Ethernet (FCoE).
+ </div></li></ul></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 3. KVM guest virtual machine compatibility</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#idm93407568">3.1. Fedora 6 support limits</a></span></dt><dt><span class="section"><a href="#idm104483712">3.2. Supported CPU Models</a></span></dt><dd><dl><dt><span class="section"><a href="#para-CPU_Models">3.2.1. Guest CPU models</a></span></dt></dl></dd></dl></div><div class="para">
+ To verify whether your processor supports the virtualization extensions and for information on enabling the virtualization extensions if they are disabled, refer to the <em class="citetitle">Fedora Virtualization Administration Guide</em>.
+ </div><div class="section" id="idm93407568"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm93407568">3.1. Fedora 6 support limits</h2></div></div></div><div class="para">
+ Fedora 19 servers have certain support limits.
+ </div><div class="para">
+ The following URLs explain the processor and memory amount limitations for Fedora 19:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ For host systems: <a href="http://www.redhat.com/resourcelibrary/articles/articles-red-hat-enterprise-linux-6-technology-capabilities-and-limits">http://www.redhat.com/resourcelibrary/articles/articles-red-hat-enterprise-linux-6-technology-capabilities-and-limits</a>
+ </div></li><li class="listitem"><div class="para">
+ For hypervisors: <a href="http://www.redhat.com/resourcelibrary/articles/virtualization-limits-rhel-hypervisors">http://www.redhat.com/resourcelibrary/articles/virtualization-limits-rhel-hypervisors</a>
+ </div></li></ul></div><div class="para">
+ The following URL is a complete reference showing supported operating systems and host and guest combinations:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.redhat.com/resourcelibrary/articles/enterprise-linux-virtualization-support">http://www.redhat.com/resourcelibrary/articles/enterprise-linux-virtualization-support</a>
+ </div></li></ul></div></div><div class="section" id="idm104483712"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm104483712">3.2. Supported CPU Models</h2></div></div></div><div class="para">
+ Fedora 19 supports the use of the following QEMU CPU model definitions:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><em class="parameter"><code>Opteron_G4</code></em></span></dt><dd><div class="para">
+ AMD Opteron 62xx (Gen 4 Class Opteron)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Opteron_G3</code></em></span></dt><dd><div class="para">
+ AMD Opteron 23xx (Gen 3 Class Opteron)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Opteron_G2</code></em></span></dt><dd><div class="para">
+ AMD Opteron 22xx (Gen 2 Class Opteron)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Opteron_G1</code></em></span></dt><dd><div class="para">
+ AMD Opteron 240 (Gen 1 Class Opteron)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>SandyBridge</code></em></span></dt><dd><div class="para">
+ Intel Xeon E312xx (Sandy Bridge)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Nehalem</code></em></span></dt><dd><div class="para">
+ Intel Core i7 9xx (Nehalem Class Core i7)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Penryn</code></em></span></dt><dd><div class="para">
+ Intel Core 2 Duo P9xxx (Penryn Class Core 2)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Conroe</code></em></span></dt><dd><div class="para">
+ Intel Celeron_4x0 (Conroe/Merom Class Core 2)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Westmere</code></em></span></dt><dd><div class="para">
+ Westmere E56xx/L56xx/X56xx (Nehalem-C)
+ </div></dd></dl></div><div class="section" id="para-CPU_Models"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.2.1. Guest CPU models</h3></div></div></div><div class="para">
+ Historically, CPU model definitions were hard-coded in <span class="application"><strong>qemu</strong></span>. This method of defining CPU models was inflexible, and made it difficult to create virtual CPUs with feature sets that matched existing physical CPUs. Typically, users modified a basic CPU model definition with feature flags in order to provide the CPU characteristics required by a virtual machine. Unless these feature sets were carefully controlled, safe migration — which requires feature sets between current and prospective hosts to match — was difficult to support.
+ </div><div class="para">
+ <span class="application"><strong>qemu-kvm</strong></span> has now replaced most hard-wired definitions with configuration file based CPU model definitions. Definitions for a number of current processor models are now included by default, allowing users to specify features more accurately and migrate more safely.
+ </div><div class="para">
+ A list of supported guest CPU models can be viewed with the <code class="command">/usr/libexec/qemu-kvm -cpu ?model</code> command. This command outputs the <em class="parameter"><code>name</code></em> used to select the CPU model at the command line, and a model identifier that corresponds to a commercial instance of that processor class.
+ </div><div class="para">
+ Configuration details for all of these CPU models can be viewed with the <code class="command">/usr/libexec/qemu-kvm -cpu ?dump</code> command, but they are also stored in the <code class="filename">/usr/share/qemu-kvm/cpu-model/cpu-x86_64.conf</code> file by default. Each CPU model definition begins with <code class="literal">[cpudef]</code>, as shown:
+ </div><pre class="screen">[cpudef]
+ name = "Nehalem"
+ level = "2"
+ vendor = "GenuineIntel"
+ family = "6"
+ model = "26"
+ stepping = "3"
+ feature_edx = "sse2 sse fxsr mmx clflush pse36 pat cmov mca \
+ pge mtrr sep apic cx8 mce pae msr tsc pse de fpu"
+ feature_ecx = "popcnt x2apic sse4.2 sse4.1 cx16 ssse3 sse3"
+ extfeature_edx = "i64 syscall xd"
+ extfeature_ecx = "lahf_lm"
+ xlevel = "0x8000000A"
+ model_id = "Intel Core i7 9xx (Nehalem Class Core i7)"</pre><div class="para">
+ The four CPUID fields, <code class="literal">feature_edx</code>, <code class="literal">feature_ecx</code>, <code class="literal">extfeature_edx</code> and <code class="literal">extfeature_ecx</code>, accept named flag values from the corresponding feature sets listed by the <code class="command">/usr/libexec/qemu-kvm -cpu ?cpuid</code> command, as shown:
+ </div><pre class="screen"># /usr/libexec/qemu-kvm -cpu ?cpuid
+Recognized CPUID flags:
+ f_edx: pbe ia64 tm ht ss sse2 sse fxsr mmx acpi ds clflush pn \
+ pse36 pat cmov mca pge mtrr sep apic cx8 mce pae msr tsc \
+ pse de vme fpu
+ f_ecx: hypervisor avx osxsave xsave aes popcnt movbe x2apic \
+ sse4.2|sse4_2 sse4.1|sse4_1 dca pdcm xtpr cx16 fma cid \
+ ssse3 tm2 est smx vmx ds_cpl monitor dtes64 pclmuldq \
+ pni|sse3
+ extf_edx: 3dnow 3dnowext lm rdtscp pdpe1gb fxsr_opt fxsr mmx \
+ mmxext nx pse36 pat cmov mca pge mtrr syscall apic cx8 \
+ mce pae msr tsc pse de vme fpu
+ extf_ecx: nodeid_msr cvt16 fma4 wdt skinit xop ibs osvw \
+ 3dnowprefetch misalignsse sse4a abm cr8legacy extapic svm \
+ cmp_legacy lahf_lm</pre><div class="para">
+ These feature sets are described in greater detail in the appropriate Intel and AMD specifications.
+ </div><div class="para">
+ It is important to use the <code class="code">check</code> flag to verify that all configured features are available.
+ </div><pre class="screen"># /usr/libexec/qemu-kvm -cpu Nehalem,check
+warning: host cpuid 0000_0001 lacks requested flag 'sse4.2|sse4_2' [0x00100000]
+warning: host cpuid 0000_0001 lacks requested flag 'popcnt' [0x00800000]</pre><div class="para">
+ If a defined feature is not available, those features will fail silently by default.
+ </div></div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 4. Virtualization restrictions</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-KVM_Restrictions">4.1. KVM restrictions</a></span></dt><dt><span class="section"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions">4.2. Application restrictions</a></span></dt><dt><span class="section"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions">4.3. Other restrictions</a></span></dt></dl></div><div class="para">
+ This chapter covers additional support and product restrictions of the virtualization packages in Fedora 19.
+ </div><div class="section" id="sect-chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-KVM_Restrictions"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.1. KVM restrictions</h2></div></div></div><div class="para">
+ The following restrictions apply to the KVM hypervisor:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Maximum vCPUs per guest</span></dt><dd><div class="para">
+ Guest virtual machines support up to a maximum of 160 virtual CPUs in Fedora 19.
+ </div></dd><dt class="varlistentry"><span class="term">Constant TSC bit</span></dt><dd><div class="para">
+ Systems without a Constant Time Stamp Counter require additional configuration. Refer to <a class="xref" href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management">Chapter 14, <em>KVM guest timing management</em></a> for details on determining whether you have a Constant Time Stamp Counter and configuration steps for fixing any related issues.
+ </div></dd><dt class="varlistentry"><span class="term">Memory overcommit</span></dt><dd><div class="para">
+ KVM supports memory overcommit and can store the memory of guest virtual machines in swap. A virtual machine will run slower if it is swapped frequently. Fedora Knowledgebase has an article on safely and efficiently determining the size of the swap partition, available here: <a href="https://access.redhat.com/knowledge/solutions/15244">https://access.redhat.com/knowledge/solutions/15244</a>. When KSM is used for memory overcommitting, make sure that the swap size follows the recommendations described in this article.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ When device assignment is in use, all virtual machine memory must be statically pre-allocated to enable DMA with the assigned device. Memory overcommit is therefore not supported with device assignment.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">CPU overcommit</span></dt><dd><div class="para">
+ It is not recommended to have more than 10 virtual CPUs per physical processor core. Customers are encouraged to use a capacity planning tool in order to determine the CPU overcommit ratio. Estimating an ideal ratio is difficult as it is highly dependent on each workload. For instance, a guest virtual machine may consume 100% CPU on one use case, and multiple guests may be completely idle on another.
+ </div><div class="para">
+ Fedora does not support running more vCPUs to a single guest than the amount of overall physical cores that exist on the system. While Hyperthreads can be considered as cores, their performance can also vary from one scenario to the next, and they should not be expected to perform as well as regular cores.
+ </div><div class="para">
+ Refer to the <em class="citetitle">Fedora Virtualization Administration Guide</em> for tips and recommendations on overcommitting CPUs.
+ </div></dd><dt class="varlistentry"><span class="term">Virtualized SCSI devices</span></dt><dd><div class="para">
+ SCSI emulation is not supported with KVM in Fedora.
+ </div></dd><dt class="varlistentry"><span class="term">Virtualized IDE devices</span></dt><dd><div class="para">
+ KVM is limited to a maximum of four virtualized (emulated) IDE devices per guest virtual machine.
+ </div></dd><dt class="varlistentry"><span class="term">Para-virtualized devices</span></dt><dd><div class="para">
+ Para-virtualized devices are also known as Virtio devices. They are purely virtual devices designed to work optimally in a virtual machine.
+ </div><div class="para">
+ Fedora 19 supports 32 PCI device slots per virtual machine, and 8 PCI functions per device slot. This gives a theoretical maximum of 256 PCI functions per guest when multi-function capabilities are enabled.
+ </div><div class="para">
+ However, this theoretical maximum is subject to the following limitations:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Each virtual machine supports a maximum of 8 assigned device functions.
+ </div></li><li class="listitem"><div class="para">
+ 4 PCI device slots are configured with emulated devices by default. However, users can explicitly remove 2 of the emulated devices that are configured by default (the video adapter device in slot 2, and the memory balloon driver device in slot 3). This gives users a supported functional maximum of 30 PCI device slots per virtual machine.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term">Migration restrictions</span></dt><dd><div class="para">
+ Device assignment refers to physical devices that have been exposed to a virtual machine, for the exclusive use of that virtual machine. Because device assignment uses hardware on the specific host where the virtual machine runs, migration and save/restore are not supported when device assignment is in use. If the guest operating system supports hot-plugging, assigned devices can be removed prior to the migration or save/restore operation to enable this feature.
+ </div><div class="para">
+ Live migration is only possible between hosts with the same CPU type (that is, Intel to Intel or AMD to AMD only).
+ </div><div class="para">
+ For live migration, both hosts must have the same value set for the No eXecution (NX) bit, either <code class="literal">on</code> or <code class="literal">off</code>.
+ </div><div class="para">
+ For migration to work, <code class="code">cache=none</code> must be specified for all block devices opened in write mode.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Failing to include the <code class="code">cache=none</code> option can result in disk corruption.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">Storage restrictions</span></dt><dd><div class="para">
+ There are risks associated with giving guest virtual machines write access to entire disks or block devices (such as <code class="filename">/dev/sdb</code>). If a guest virtual machine has access to an entire block device, it can share any volume label or partition table with the host machine. If bugs exist in the host system's partition recognition code, this can create a security risk. Avoid this risk by configuring the host machine to ignore devices assigned to a guest virtual machine.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Failing to adhere to storage restrictions can result in risks to security.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">SR-IOV restrictions</span></dt><dd><div class="para">
+ SR-IOV is only thoroughly tested with the following devices (other SR-IOV devices may work but have not been tested at the time of release):
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Intel® 82576NS Gigabit Ethernet Controller (<code class="command">igb</code> driver)
+ </div></li><li class="listitem"><div class="para">
+ Intel® 82576EB Gigabit Ethernet Controller (<code class="command">igb</code> driver)
+ </div></li><li class="listitem"><div class="para">
+ Intel® 82599ES 10 Gigabit Ethernet Controller (<code class="command">ixgbe</code> driver)
+ </div></li><li class="listitem"><div class="para">
+ Intel® 82599EB 10 Gigabit Ethernet Controller (<code class="command">ixgbe</code> driver)
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term">Core dumping restrictions</span></dt><dd><div class="para">
+ Because core dumping is currently implemented on top of migration, it is not supported when device assignment is in use.
+ </div></dd><dt class="varlistentry"><span class="term">PCI device assignment restrictions</span></dt><dd><div class="para">
+ PCI device assignment (attaching PCI devices to virtual machines) requires host systems to have AMD IOMMU or Intel VT-d support to enable device assignment of PCI-e devices.
+ </div><div class="para">
+ For parallel/legacy PCI, only single devices behind a PCI bridge are supported.
+ </div><div class="para">
+ Multiple PCIe endpoints connected through a non-root PCIe switch require ACS support in the PCIe bridges of the PCIe switch. To disable this restriction, edit the <code class="filename">/etc/libvirt/qemu.conf</code> file and insert the line:
+ </div><pre class="programlisting">relaxed_acs_check=1</pre><div class="para">
+ Fedora 19 has limited PCI configuration space access by guest device drivers. This limitation could cause drivers that are dependent on PCI configuration space to fail configuration.
+ </div><div class="para">
+ Fedora 17 introduced interrupt remapping as a requirement for PCI device assignment. If your platform does not provide support for interrupt remapping, circumvent the KVM check for this support with the following command as the root user at the command line prompt:
+ </div><pre class="screen"># echo 1 > /sys/module/kvm/parameters/allow_unsafe_assigned_interrupts</pre></dd></dl></div></div><div class="section" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.2. Application restrictions</h2></div></div></div><div class="para">
+ There are aspects of virtualization which make it unsuitable for certain types of applications.
+ </div><div class="para">
+ Applications with high I/O throughput requirements should use the para-virtualized drivers for fully-virtualized guests. Without the para-virtualized drivers certain applications may be unpredictable under heavy I/O loads.
+ </div><div class="para">
+ The following applications should be avoided due to high I/O requirements:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>kdump</strong></span> server
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>netdump</strong></span> server
+ </div></li></ul></div><div class="para">
+ You should carefully evaluate applications and tools that heavily utilize I/O or those that require real-time performance. Consider the para-virtualized drivers or PCI device assignment for increased I/O performance. Refer to <a class="xref" href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers">Chapter 10, <em>KVM Para-virtualized Drivers</em></a> for more information on the para-virtualized drivers for fully virtualized guests. Refer to <a class="xref" href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config">Chapter 12, <em>PCI device configuration</em></a> for more information on PCI device assignment.
+ </div><div class="para">
+ Applications suffer a small performance loss from running in virtualized environments. The performance benefits of virtualization through consolidating to newer and faster hardware should be evaluated against the potential application performance issues associated with using virtualization.
+ </div></div><div class="section" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.3. Other restrictions</h2></div></div></div><div class="para">
+ For the list of all other restrictions and issues affecting virtualization read the <em class="citetitle">Fedora 19 Release Notes</em>. The <em class="citetitle">Fedora 19 Release Notes</em> cover the present new features, known issues and restrictions as they are updated or discovered.
+ </div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 5. Installing the virtualization packages</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_with_a_new_Red_Hat_Enterprise_Linux_installation">5.1. Configuring a Virtualization Host installation</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system">5.2. Installing virtualization 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 your computer. Virtualization packages can be installed either during the host installation sequence or after host installation using the <code class="command">yum</code> command and the Fedora Project download page.
+ </div><div class="para">
+ The KVM hypervisor uses the default Fedora kernel with the <span class="package">kvm</span> kernel module.
+ </div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_with_a_new_Red_Hat_Enterprise_Linux_installation"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.1. Configuring a Virtualization Host installation</h2></div></div></div><div class="para">
+ This section covers installing virtualization tools and virtualization packages as part of a fresh Fedora installation.
+ </div><div class="procedure"><h6>Procedure 5.1. Installing the virtualization package group</h6><ol class="1"><li class="step"><p class="title"><strong>Launch the Fedora installation program</strong></p><div class="para">
+ Start an interactive Fedora installation from the Fedora Installation CD-ROM, DVD or PXE.
+ </div></li><li class="step"><p class="title"><strong>Continue installation up to package selection</strong></p><div class="para">
+ Complete the other steps up to the package selection step.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/RHELcustomize15.png" width="444" alt="The Fedora package selection screen showing options to select a different set of software from regular installation. Virtualization Host is selected in the upper menu, and Fedora is selected from the list of additional repositories. Customize now is selected at the bottom of the window, with Back and Next buttons shown at the bottom right corner of the window." /></div></div><h6>Figure 5.1. The Fedora package selection screen</h6></div><br class="figure-break" /><div class="para">
+ Select the <span class="guilabel"><strong>Virtualization Host</strong></span> server role to install a platform for guest virtual machines. Alternatively, ensure that the <span class="guilabel"><strong>Customize Now</strong></span> radio button is selected before proceeding, to specify individual packages.
+ </div></li><li class="step"><p class="title"><strong>Select the <span class="guilabel"><strong>Virtualization</strong></span> package group.</strong></p><div class="para">
+ This selects the qemu-kvm emulator, <code class="command">virt-manager</code>, <code class="command">libvirt</code> and <code class="command">virt-viewer</code> for installation.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/RHELkvmSelect.png" width="444" alt="The Fedora package selection screen with Virtualization selected in the left menu." /></div></div><h6>Figure 5.2. The Fedora package selection screen</h6></div><br class="figure-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If you wish to create virtual machines in a graphical user interface (<span class="application"><strong>virt-manager</strong></span>) later, you should also select the <code class="systemitem">General Purpose Desktop</code> package group.
+ </div></div></div></li><li class="step" id="step-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Customize_the_packages_if_required"><p class="title"><strong>Customize the packages (if required)</strong></p><div class="para">
+ Customize the <span class="guilabel"><strong>Virtualization</strong></span> group if you require other virtualization packages.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/RHELKVMpackages-2.png" width="444" alt="The Fedora package selection screen with a pop-up Packages in Virtualization window showing the packages available to be installed." /></div></div><h6>Figure 5.3. The Fedora package selection screen</h6></div><br class="figure-break" /><div class="para">
+ Click on the <span class="guilabel"><strong>Close</strong></span> button, then the <span class="guilabel"><strong>Next</strong></span> button to continue the installation.
+ </div></li></ol></div><div class="para">
+ When the installation is complete, reboot the system.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ You require a valid RHN virtualization entitlement to receive updates for the virtualization packages.
+ </div></div></div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_with_Kickstart_files"><h5 class="formalpara">Installing KVM packages with Kickstart files</h5>
+ Kickstart files allow for large, automated installations without a user manually installing each individual host system. This section describes how to create and use 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 groups:
+ </div><pre class="screen">@virtualization
+ at virtualization-client
+ at virtualization-platform
+ at virtualization-tools</pre><div class="para">
+ For more information about Kickstart files, refer to the Fedora <em class="citetitle">Installation Guide</em>, available from <a href="https://access.redhat.com/knowledge/docs/Red_Hat_Enterprise_Linux/">https://access.redhat.com/knowledge/docs/Red_Hat_Enterprise_Linux/</a>.
+ </div></div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.2. Installing virtualization packages on an existing Fedora system</h2></div></div></div><div class="para">
+ This section describes the steps for installing the KVM hypervisor on a working Fedora 16 or newer system.
+ </div><div class="para">
+ To install the packages, your machines must be registered. There are two methods of registering an unregistered installation of Fedora:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ To register via RHN Classic, run the <code class="command">rhn_register</code> command and follow the prompts.
+ </div></li><li class="listitem"><div class="para">
+ To register via Fedora, run the <code class="command">subscription-manager register</code> command and follow the prompts.
+ </div></li></ol></div><div class="para">
+ If you do not have a valid Fedora subscription, visit the <a href="https://www.redhat.com/wapps/store/catalog.html">Fedora online store</a> to obtain one.
+ </div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_the_KVM_hypervisor_with_yum"><h5 class="formalpara">Installing the virtualization packages with <code class="command">yum</code></h5>
+ To use virtualization on Fedora you require at least the <code class="filename">qemu-kvm</code> and <code class="filename">qemu-img</code> packages. These packages provide the user-level KVM emulator and disk image manager on the host Fedora system.
+ </div><div class="para">
+ To install the <code class="filename">qemu-kvm</code> and <code class="filename">qemu-img</code> packages, run the following command:
+ </div><pre class="screen"># yum install qemu-kvm qemu-img</pre><div class="para">
+ Several additional virtualization management packages are also available:
+ </div><div class="variablelist" id="vari-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Recommended_virtualization_packages"><h6>Recommended virtualization packages</h6><dl class="variablelist"><dt class="varlistentry"><span class="term"><span class="package">python-virtinst</span></span></dt><dd><div class="para">
+ Provides the <code class="command">virt-install</code> command for creating virtual machines.
+ </div></dd><dt class="varlistentry"><span class="term"><span class="package">libvirt</span></span></dt><dd><div class="para">
+ The <span class="package">libvirt</span> package provides the server and host side libraries for interacting with hypervisors and host systems. The <span class="package">libvirt</span> package provides the <code class="systemitem">libvirtd</code> daemon that handles the library calls, manages virtual machines and controls the hypervisor.
+ </div></dd><dt class="varlistentry"><span class="term"><span class="package">libvirt-python</span></span></dt><dd><div class="para">
+ The <span class="package">libvirt-python</span> package contains a module that permits applications written in the Python programming language to use the interface supplied by the <span class="package">libvirt</span> API.
+ </div></dd><dt class="varlistentry"><span class="term"><span class="package">virt-manager</span></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 <span class="package">libvirt-client</span> library as the management API.
+ </div></dd><dt class="varlistentry"><span class="term"><span class="package">libvirt-client</span></span></dt><dd><div class="para">
+ The <span class="package">libvirt-client</span> package provides the client-side APIs and libraries for accessing <span class="package">libvirt</span> servers. The <span class="package">libvirt-client</span> package includes the <code class="command">virsh</code> command line tool to manage and control virtual machines and hypervisors from the command line or a special virtualization shell.
+ </div></dd></dl></div><div class="para">
+ Install all of these recommended virtualization packages with the following command:
+ </div><pre class="screen"># yum install virt-manager libvirt libvirt-python python-virtinst libvirt-client</pre><div class="formalpara"><h5 class="formalpara" id="idm98882912">Installing Virtualization package groups</h5>
+ The virtualization packages can also be installed from package groups. The following table describes the virtualization package groups and what they provide.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Note that the <code class="command">qemu-img</code> package is installed as a dependency of the <code class="literal">Virtualization</code> package group if it is not already installed on the system. It can also be installed manually with the <code class="command">yum install qemu-img</code> command as described previously.
+ </div></div></div><div class="table"><h6>Table 5.1. Virtualization Package Groups</h6><div class="table-contents"><table summary="Virtualization Package Groups" border="1"><colgroup><col align="left" class="c1" width="25%" /><col align="left" class="c2" width="25%" /><col align="left" class="c3" width="25%" /><col align="left" class="c4" width="25%" /></colgroup><thead><tr><th class="" align="left">
+ Package Group
+ </th><th class="" align="left">
+ Description
+ </th><th class="" align="left">
+ Mandatory Packages
+ </th><th class="" align="left">
+ Optional Packages
+ </th></tr></thead><tbody><tr><td class="" align="left">
+ Virtualization
+ </td><td class="" align="left">
+ Provides an environment for hosting virtual machines
+ </td><td class="" align="left">
+ qemu-kvm
+ </td><td class="" align="left">
+ qemu-guest-agent, qemu-kvm-tools
+ </td></tr><tr><td class="" align="left">
+ Virtualization Client
+ </td><td class="" align="left">
+ Clients for installing and managing virtualization instances
+ </td><td class="" align="left">
+ python-virtinst, virt-manager, virt-viewer
+ </td><td class="" align="left">
+ virt-top
+ </td></tr><tr><td class="" align="left">
+ Virtualization Platform
+ </td><td class="" align="left">
+ Provides an interface for accessing and controlling virtual machines and containers
+ </td><td class="" align="left">
+ libvirt, libvirt-client, virt-who, virt-what
+ </td><td class="" align="left">
+ fence-virtd-libvirt, fence-virtd-multicast, fence-virtd-serial, libvirt-cim, libvirt-java, libvirt-qmf, libvirt-snmp, perl-Sys-Virt
+ </td></tr><tr><td class="" align="left">
+ Virtualization Tools
+ </td><td class="" align="left">
+ Tools for offline virtual image management
+ </td><td class="" align="left">
+ libguestfs
+ </td><td class="" align="left">
+ libguestfs-java, libguestfs-tools, virt-v2v
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ To install a package group, run the <code class="command">yum groupinstall <groupname></code> command. For instance, to install the <span class="bold bold"><strong>Virtualization Tools</strong></span> package group, run the <code class="command">yum groupinstall "Virtualization Tools"</code> command.
+ </div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 6. Guest virtual machine installation overview</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#idm101231408">6.1. Guest virtual machine prerequisites and considerations</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install">6.2. Creating guests with virt-install</a></span></dt><dt><span class="section"><a href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager">6.3. Creating guests with virt-manager</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Ins
tallation-Installing_guests_with_PXE">6.4. Installing guest virtual machines 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 guest virtual machines 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 in the following chapters for specific versions of Fedora and Microsoft Windows.
+ </div><div class="section" id="idm101231408"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm101231408">6.1. Guest virtual machine prerequisites and considerations</h2></div></div></div><div class="para">
+ Various factors should be considered before creating any guest virtual machines. Not only should the role of a virtual machine be considered before deployment, but regular ongoing monitoring and assessment based on variable factors (load, amount of clients) should be performed. Some factors include:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Performance</span></dt><dd><div class="para">
+ Guest virtual machines should be deployed and configured based on their intended tasks. Some guest systems (for instance, guests running a database server) may require special performance considerations. Guests may require more assigned CPUs or memory based on their role and projected system load.
+ </div></dd><dt class="varlistentry"><span class="term">Input/Output requirements and types of Input/Output</span></dt><dd><div class="para">
+ Some guest virtual machines may have a particularly high I/O requirement or may require further considerations or projections based on the type of I/O (for instance, typical disk block size access, or the amount of clients).
+ </div></dd><dt class="varlistentry"><span class="term">Storage</span></dt><dd><div class="para">
+ Some guest virtual machines may require higher priority access to storage or faster disk types, or may require exclusive access to areas of storage. The amount of storage used by guests should also be regularly monitored and taken into account when deploying and maintaining storage.
+ </div></dd><dt class="varlistentry"><span class="term">Networking and network infrastructure</span></dt><dd><div class="para">
+ Depending upon your environment, some guest virtual machines could require faster network links than other guests. Bandwidth or latency are often factors when deploying and maintaining guests, especially as requirements or load changes.
+ </div></dd><dt class="varlistentry"><span class="term">Request requirements</span></dt><dd><div class="para">
+ SCSI requests can only be issued to guest virtual machines on virtio drives if the virtio drives are backed by whole disks, and the disk device parameter is set to <code class="literal">lun</code>, as shown in the following example:
+ </div><pre class="screen"><devices>
+ <emulator>/usr/libexec/qemu-kvm</emulator>
+ <disk type='block' device='lun'></pre></dd></dl></div></div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.2. 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 guest virtual machines 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 that can be passed on the command line. To see a complete list of options run the following command:
+ </div><pre class="screen"># virt-install --help</pre><div class="para">
+ Note that you need root privileges in order for <code class="command">virt-install</code> commands to complete successfully. 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>--graphics</code></em> option which allows graphical installation of a virtual machine.
+ </div><div class="example" id="exam-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Using_virt_install_with_KVM_to_create_a_Red_Hat_Enterprise_Linux_3_guest"><h6>Example 6.1. Using virt-install to install a Fedora 19 guest virtual machine</h6><div class="example-contents"><div class="para">
+ This example creates a Fedora 19 guest:
+ </div><pre class="screen">virt-install \
+ --name=guest1-rhel5-64 \
+ --file=/var/lib/libvirt/images/guest1-rhel5-64.dsk \
+ --file-size=8 \
+ --nonsparse --graphics spice \
+ --vcpus=2 --ram=2048 \
+ --location=http://example1.com/installation_tree/RHEL5.6-Server-x86_64/os \
+ --network bridge=br0 \
+ --os-type=linux \
+ --os-variant=rhel5.4</pre></div></div><br class="example-break" /><div class="para">
+ Ensure that you select the correct <em class="parameter"><code>os-type</code></em> for your operating system when running this command.
+ </div><div class="para">
+ Refer to <code class="command">man virt-install</code> for more examples.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ When installing a Windows guest with <code class="command">virt-install</code>, the <code class="command">--os-type=<em class="replaceable"><code>windows</code></em></code> option is recommended. This option prevents the CD-ROM from disconnecting when rebooting during the installation procedure. The <code class="command">--os-variant</code> option further optimizes the configuration for a specific guest operating system.
+ </div></div></div></div><div xml:lang="en-US" class="section" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.3. 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 guest virtual machines.
+ </div><div class="procedure" id="proc-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_a_virtualized_guest_with_virt_manager"><h6>Procedure 6.1. Creating a guest virtual machine with <span class="application"><strong>virt-manager</strong></span></h6><ol class="1"><li class="step"><p class="title"><strong>Open virt-manager</strong></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 class="step"><p class="title"><strong>Optional: Open a remote hypervisor</strong></p><div class="para">
+ Select the hypervisor and press the <span class="guibutton"><strong>Connect</strong></span> button to connect to the remote hypervisor.
+ </div></li><li class="step"><p class="title"><strong>Create a new virtual machine</strong></p><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>Create a new virtual machine</strong></span> button (<a class="xref" href="#virt-manager_main-png">Figure 6.1, “Virtual Machine Manager window”</a>) to open the <span class="guimenu"><strong>New VM</strong></span> wizard.
+ </div><div class="figure" id="virt-manager_main-png"><div class="figure-contents"><div class="mediaobject"><img src="images/rhel6_virt_manager.png" alt="Virtual Machine Manager window" /></div></div><h6>Figure 6.1. Virtual Machine Manager window</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guimenu"><strong>New VM</strong></span> wizard breaks down the virtual machine creation process into five steps:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Naming the guest virtual machine and choosing the installation type
+ </div></li><li class="listitem"><div class="para">
+ Locating and configuring the installation media
+ </div></li><li class="listitem"><div class="para">
+ Configuring memory and CPU options
+ </div></li><li class="listitem"><div class="para">
+ Configuring the virtual machine's storage
+ </div></li><li class="listitem"><div class="para">
+ Configuring networking, architecture, and other hardware settings
+ </div></li></ol></div><div class="para">
+ Ensure that <code class="command">virt-manager</code> can access the installation media (whether locally or over the network) before you continue.
+ </div></li><li class="step"><p class="title"><strong>Specify name and installation type</strong></p><div class="para">
+ The guest virtual machine creation process starts with the selection of a name and installation type. Virtual machine names can have underscores (<code class="computeroutput">_</code>), periods (<code class="computeroutput">.</code>), and hyphens (<code class="computeroutput">-</code>).
+ </div><div class="figure" id="Virtual_Machine_Name-guest-install-png"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt2-pic2.png" alt="Name virtual machine and select installation method" /></div></div><h6>Figure 6.2. Name virtual machine and select installation method</h6></div><br class="figure-break" /><div class="para">
+ Type in a virtual machine name and choose an installation type:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Local install media (ISO image or CDROM)</span></dt><dd><div class="para">
+ This method uses a CD-ROM, DVD, or image of an installation disk (for example, <code class="filename">.iso</code>).
+ </div></dd><dt class="varlistentry"><span class="term">Network Install (HTTP, FTP, or NFS)</span></dt><dd><div class="para">
+ Network installing involves the use of a mirrored Fedora installation tree to install a guest. The installation tree must be accessible through either HTTP, FTP, or NFS.
+ </div></dd><dt class="varlistentry"><span class="term">Network Boot (PXE)</span></dt><dd><div class="para">
+ This method uses a Preboot eXecution Environment (PXE) server to install the guest virtual machine. Setting up a PXE server is covered in the <em class="citetitle">Deployment Guide</em>. To install via network boot, the guest must have a routable IP address or shared network device. For information on the required networking configuration for PXE installation, refer to <a class="xref" href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE">Section 6.4, “Installing guest virtual machines with PXE”</a>.
+ </div></dd><dt class="varlistentry"><span class="term">Import existing disk image</span></dt><dd><div class="para">
+ This method allows you to create a new guest virtual machine and import a disk image (containing a pre-installed, bootable operating system) to it.
+ </div></dd></dl></div><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Configure installation</strong></p><div class="para">
+ Next, configure the <span class="guimenuitem"><strong>OS type</strong></span> and <span class="guimenuitem"><strong>Version</strong></span> of the installation. Ensure that you select the appropriate OS type for your virtual machine. Depending on the method of installation, provide the install URL or existing storage path.
+ </div><div class="figure" id="Virtual_Machine_Name-guest-install_STEP2-local-png"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt2-pic3.png" alt="Remote installation URL" /></div></div><h6>Figure 6.3. Remote installation URL</h6></div><br class="figure-break" /><div class="figure" id="Virtual_Machine_Name-guest-install_STEP2-import-png"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt1-pic5.png" alt="Local ISO image installation" /></div></div><h6>Figure 6.4. Local ISO image installation</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Configure CPU and memory</strong></p><div class="para">
+ The next step involves configuring the number of CPUs and amount of memory to allocate to the virtual machine. The wizard shows the number of CPUs and amount of memory you can allocate; configure these settings and click <span class="guibutton"><strong>Forward</strong></span>.
+ </div><div class="figure" id="Virtual_Machine_Name-guest-install_STEP2-cpumem-png"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt1-pic6.png" alt="Configuring CPU and Memory" /></div></div><h6>Figure 6.5. Configuring CPU and Memory</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Configure storage</strong></p><div class="para">
+ Assign storage to the guest virtual machine.
+ </div><div class="figure" id="Virtual_Machine_Name-guest-install_STEP4-png"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt1-pic7.png" alt="Configuring virtual storage" /></div></div><h6>Figure 6.6. Configuring virtual storage</h6></div><br class="figure-break" /><div class="para">
+ If you chose to import an existing disk image during the first step, <code class="command">virt-manager</code> will skip this step.
+ </div><div class="para">
+ Assign sufficient space for your virtual machine and any applications it requires, then click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Final configuration</strong></p><div class="para">
+ Verify the settings of the virtual machine and click <span class="guibutton"><strong>Finish</strong></span> when you are satisfied; doing so will create the virtual machine with default networking settings, virtualization type, and architecture.
+ </div><div class="figure" id="Virtual_Machine_Name-guest-install_STEP5-finish-png"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt1-pic9-local-storage.png" alt="Verifying the configuration" /></div></div><h6>Figure 6.7. Verifying the configuration</h6></div><br class="figure-break" /><div class="para">
+ If you prefer to further configure the virtual machine's hardware first, check the <span class="guimenuitem"><strong>Customize configuration before install</strong></span> box first before clicking <span class="guibutton"><strong>Finish</strong></span>. Doing so will open another wizard that will allow you to add, remove, and configure the virtual machine's hardware settings.
+ </div><div class="para">
+ After configuring the virtual machine's hardware, click <span class="guibutton"><strong>Apply</strong></span>. <code class="command">virt-manager</code> will then create the virtual machine with your specified hardware settings.
+ </div></li></ol></div></div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.4. Installing guest virtual machines with PXE</h2></div></div></div><div class="formalpara"><h5 class="formalpara" id="idm119674960">Requirements</h5>
+ PXE guest installation requires a PXE server running on the same subnet as the guest virtual machines you wish to install. The method of accomplishing this depends on how the virtual machines are connected to the network. Contact Support if you require assistance setting up a PXE server.
+ </div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE-PXE_installation_with_virt_install"><h5 class="formalpara">PXE installation with virt-install</h5>
+ <code class="command">virt-install</code> PXE installations require both the <code class="command">--network=bridge:installation</code> parameter, where <em class="parameter"><code>installation</code></em> is the name of your bridge, and the <em class="parameter"><code>--pxe</code></em> parameter.
+ </div><div class="para">
+ By default, if no network is found, the guest virtual machine attempts to boot from alternative bootable devices. If there is no other bootable device found, the guest pauses. You can use the <span class="application"><strong>qemu-kvm</strong></span> boot parameter <em class="parameter"><code>reboot-timeout</code></em> to allow the guest to retry booting if no bootable device is found, like so:
+ </div><pre class="screen"># qemu-kvm -boot reboot-timeout=1000</pre><div class="example" id="exam-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE-PXE_installation_with_virt_install"><h6>Example 6.2. Fully-virtualized PXE installation with virt-install</h6><div class="example-contents"><pre class="screen"># virt-install --hvm --connect qemu:///system \
+--network=bridge:installation --pxe --graphics spice \
+--name rhel6-machine --ram=756 --vcpus=4 \
+--os-type=linux --os-variant=rhel6 \
+--disk path=/var/lib/libvirt/images/rhel6-machine.img,size=10</pre><div class="para">
+ Note that the command above cannot be executed in a text-only environment. A fully-virtualized (<em class="parameter"><code>--hvm</code></em>) guest can only be installed in a text-only environment if the <em class="parameter"><code>--location</code></em> and <em class="parameter"><code>--extra-args "console=<em class="replaceable"><code>console_type</code></em>"</code></em> are provided instead of the <em class="parameter"><code>--graphics spice</code></em> parameter.
+ </div></div></div><br class="example-break" /><div class="procedure" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE-PXE_installation_with_virt_manager"><h6>Procedure 6.2. PXE installation with virt-manager</h6><ol class="1"><li class="step" id="step-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE-Select_PXE"><p class="title"><strong>Select PXE</strong></p><div class="para">
+ Select PXE as the installation method and follow the rest of the steps to configure the OS type, memory, CPU and storage settings.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt3-pic2.png" alt="Step 1 of 5 for creating a new virtual machine with virt-manager, with Network Boot (PXE) chosen for the method of installation." /></div></div><h6>Figure 6.8. Selecting the installation method</h6></div><br class="figure-break" /><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt3-pic3.png" alt="Step 2 of 5 for creating a new virtual machine with virt-manager, with Linux chosen as OS Type and Fedora 19 chosen for version." /></div></div><h6>Figure 6.9. Selecting the installation type</h6></div><br class="figure-break" /><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt3-pic4.png" alt="Step 3 of 5 for creating a new virtual machine with virt-manager showing memory and CPU settings, with 1024MB of RAM and 2 CPUs selected
." /></div></div><h6>Figure 6.10. Specifying virtualized hardware details</h6></div><br class="figure-break" /><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt3-pic5.png" alt="Step 4 of 5 for creating a new virtual machine with virt-manager, with checkboxes selected next to "Enable storage for this virtual machine" and "Allocate entire disk now". 8GB is selected under the heading "Create a disk image on the computer's hard drive"." /></div></div><h6>Figure 6.11. Specifying storage details</h6></div><br class="figure-break" /></li><li class="step" id="step-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Start_the_installation"><p class="title"><strong>Start the installation</strong></p><div class="para">
+ The installation is ready to start.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/PXEguest_5of5.png" width="444" alt="Step 5 of 5 for creating a new virtual machine with virt-manager reads "Ready to begin installation of (guest name)" with a summary of options already chosen, and advanced options to choose from." /></div></div><h6>Figure 6.12. Finalizing virtual machine details</h6></div><br class="figure-break" /></li></ol></div><div class="para">
+ A DHCP request is sent and if a valid PXE server is found the guest virtual machine's installation processes will start.
+ </div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 7. Installing a Red Hat Enterprise Linux 6 guest virtual machine on a Red Hat Enterprise Linux 6 host</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#idm112752688">7.1. Creating a Red Hat Enterprise Linux 6 guest with local installation media</a></span></dt><dt><span class="section"><a href="#idm78294688">7.2. Creating a Red Hat Enterprise Linux 6 guest with a network installation tree</a></span></dt><dt><span class="section"><a href="#idm86720352">7.3. Creating a Red Hat Enterprise Linux 6 guest with PXE</a></span></dt></dl></div><div class="para">
+ This chapter covers how to install a Red Hat Enterprise Linux 6 guest virtual machine on a Red Hat Enterprise Linux 6 host.
+ </div><div class="para">
+ These procedures assume that the KVM hypervisor and all other required packages are installed and the host is configured for virtualization.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ For more information on installing the virtualization packages, refer to <a class="xref" href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation">Chapter 5, <em>Installing the virtualization packages</em></a>.
+ </div></div></div><div class="section" id="idm112752688"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm112752688">7.1. Creating a Red Hat Enterprise Linux 6 guest with local installation media</h2></div></div></div><div class="para">
+ This procedure covers creating a Red Hat Enterprise Linux 6 guest virtual machine with a locally stored installation DVD or DVD image. DVD images are available from <a href="http://access.redhat.com">http://access.redhat.com</a> for Red Hat Enterprise Linux 6.
+ </div><div class="procedure"><h6>Procedure 7.1. Creating a Red Hat Enterprise Linux 6 guest virtual machine with virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Optional: Preparation</strong></p><div class="para">
+ Prepare the storage environment for the virtual machine. For more information on preparing storage, refer to the <em class="citetitle">Red Hat Enterprise Linux 6 Virtualization Administration Guide</em>.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Various storage types may be used for storing guest virtual machines. However, for a virtual machine to be able to use migration features the virtual machine must be created on networked storage.
+ </div></div></div><div class="para">
+ Red Hat Enterprise Linux 6 requires at least 1GB of storage space. However, Red Hat recommends at least 5GB of storage space for a Red Hat Enterprise Linux 6 installation and for the procedures in this guide.
+ </div></li><li class="step"><p class="title"><strong>Open virt-manager and start the wizard</strong></p><div class="para">
+ Open virt-manager by executing the <code class="command">virt-manager</code> command as root or opening <span class="guilabel"><strong>Applications</strong></span> → <span class="guilabel"><strong>System Tools</strong></span> → <span class="guilabel"><strong>Virtual Machine Manager</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/1-7RHEL_local_install.png" width="444" alt="The Virtual Machine Manager window" /></div></div><h6>Figure 7.1. The Virtual Machine Manager window</h6></div><br class="figure-break" /><div class="para">
+ Click on the <span class="guibutton"><strong>Create a new virtual machine</strong></span> button to start the new virtualized guest wizard.
+ </div><div class="figure" id="gofigurego"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_newicon.png" alt="The Create a new virtual machine button" /></div></div><h6>Figure 7.2. The Create a new virtual machine button</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guilabel"><strong>New VM</strong></span> window opens.
+ </div></li><li class="step"><p class="title"><strong>Name the virtual machine</strong></p><div class="para">
+ Virtual machine names can contain letters, numbers and the following characters: '<span class="keycap"><strong>_</strong></span>', '<span class="keycap"><strong>.</strong></span>' and '<span class="keycap"><strong>-</strong></span>'. Virtual machine names must be unique for migration and cannot consist only of numbers.
+ </div><div class="para">
+ Choose the <span class="guilabel"><strong>Local install media (ISO image or CDROM)</strong></span> radio button.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/2-7RHEL_local_install.png" width="444" alt="The New VM window - Step 1" /></div></div><h6>Figure 7.3. The New VM window - Step 1</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Select the installation media</strong></p><div class="para">
+ Select the appropriate radio button for your installation media.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/3-7RHEL_local_install.png" width="444" alt="Locate your install media" /></div></div><h6>Figure 7.4. Locate your install media</h6></div><br class="figure-break" /><ul class="stepalternatives">
+ <li class="step"><div class="para">
+ If you wish to install from a CD-ROM or DVD, select the <span class="guilabel"><strong>Use CDROM or DVD</strong></span> radio button, and select the appropriate disk drive from the drop-down list of drives available.
+ </div></li>
+ <li class="step"><div class="para">
+ If you wish to install from an ISO image, select <span class="guilabel"><strong>Use ISO image</strong></span>, and then click the <span class="guibutton"><strong>Browse...</strong></span> button to open the <span class="guilabel"><strong>Locate media volume</strong></span> window.
+ </div><div class="para">
+ Select the installation image you wish to use, and click <span class="guibutton"><strong>Choose Volume</strong></span>.
+ </div><div class="para">
+ If no images are displayed in the <span class="guilabel"><strong>Locate media volume</strong></span> window, click on the <span class="guibutton"><strong>Browse Local</strong></span> button to browse the host machine for the installation image or DVD drive containing the installation disk. Select the installation image or DVD drive containing the installation disk and click <span class="guibutton"><strong>Open</strong></span>; the volume is selected for use and you are returned to the <span class="guilabel"><strong>Create a new virtual machine</strong></span> wizard.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ For ISO image files and guest storage images, the recommended location to use is <code class="filename">/var/lib/libvirt/images/</code>. Any other location may require additional configuration by SELinux. Refer to the Red Hat Enterprise Linux 6 <em class="citetitle">Virtualization Administration Guide</em> for more details on configuring SELinux.
+ </div></div></div></li>
+
+ </ul><div class="para">
+ Select the operating system type and version which match the installation media you have selected.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/5-7RHEL_local_install.png" width="444" alt="The New VM window - Step 2" /></div></div><h6>Figure 7.5. The New VM window - Step 2</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title" id="RAM-and-VCPUs"><strong>Set RAM and virtual CPUs</strong></p><div class="para">
+ Choose appropriate values for the virtual CPUs and RAM allocation. These values affect the host's and guest's performance. Memory and virtual CPUs can be overcommitted. For more information on overcommitting, refer to the <em class="citetitle">Red Hat Enterprise Linux 6 Virtualization Administration Guide</em>.
+ </div><div class="para">
+ Virtual machines require sufficient physical memory (RAM) to run efficiently and effectively. Red Hat supports a minimum of 512MB of RAM for a virtual machine. Red Hat recommends at least 1024MB of RAM for each logical core.
+ </div><div class="para">
+ Assign sufficient virtual CPUs for the virtual machine. If the virtual machine runs a multithreaded application, assign the number of virtual CPUs the guest virtual machine will require to run efficiently.
+ </div><div class="para">
+ You cannot assign more virtual CPUs than there are physical processors (or hyper-threads) available on the host system. The number of virtual CPUs available is noted in the <span class="guilabel"><strong>Up to <em class="replaceable"><code>X</code></em> available</strong></span> field.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/6-7RHEL_local_install.png" width="444" alt="The new VM window - Step 3" /></div></div><h6>Figure 7.6. The new VM window - Step 3</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Storage</strong></p><div class="para">
+ Enable and assign storage for the Red Hat Enterprise Linux 6 guest virtual machine. Assign at least 5GB for a desktop installation or at least 1GB for a minimal installation.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Live and offline migrations require virtual machines to be installed on shared network storage. For information on setting up shared storage for virtual machines, refer to the <em class="citetitle">Red Hat Enterprise Linux Virtualization Administration Guide</em>.
+ </div></div></div><ol class="a"><li class="step"><p class="title"><strong>With the default local storage</strong></p><div class="para">
+ Select the <span class="guilabel"><strong>Create a disk image on the computer's hard drive</strong></span> radio button to create a file-based image in the default storage pool, the <code class="filename">/var/lib/libvirt/images/</code> directory. Enter the size of the disk image to be created. If the <span class="guilabel"><strong>Allocate entire disk now</strong></span> check box is selected, a disk image of the size specified will be created immediately. If not, the disk image will grow as it becomes filled.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/7-7RHEL_local_install.png" width="444" alt="The New VM window - Step 4" /></div></div><h6>Figure 7.7. The New VM window - Step 4</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to create a disk image on the local hard drive. Alternatively, select <span class="guilabel"><strong>Select managed or other existing storage</strong></span>, then select <span class="guilabel"><strong>Browse</strong></span> to configure managed storage.
+ </div></li><li class="step"><p class="title"><strong>With a storage pool</strong></p><div class="para">
+ If you selected <span class="guilabel"><strong>Select managed or other existing storage</strong></span> in the previous step to use a storage pool and clicked <span class="guilabel"><strong>Browse</strong></span>, the <span class="guilabel"><strong>Locate or create storage volume</strong></span> window will appear.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/8-7RHEL_local_install.png" width="444" alt="The Locate or create storage volume window" /></div></div><h6>Figure 7.8. The Locate or create storage volume window</h6></div><br class="figure-break" /><ol class="i"><li class="step"><div class="para">
+ Select a storage pool from the <span class="guilabel"><strong>Storage Pools</strong></span> list.
+ </div></li><li class="step"><div class="para">
+ Optional: Click on the <span class="guilabel"><strong>New Volume</strong></span> button to create a new storage volume. The <span class="guilabel"><strong>Add a Storage Volume</strong></span> screen will appear. Enter the name of the new storage volume.
+ </div><div class="para">
+ Choose a format option from the <span class="guilabel"><strong>Format</strong></span> dropdown menu. Format options include raw, cow, qcow, qcow2, qed, vmdk, and vpc. Adjust other fields as desired.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/9-7RHEL_local_install.png" width="444" alt="The Add a Storage Volume window" /></div></div><h6>Figure 7.9. The Add a Storage Volume window</h6></div><br class="figure-break" /></li></ol></li></ol><div class="para">
+ Click <span class="guibutton"><strong>Finish</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Verify and finish</strong></p><div class="para">
+ Verify there were no errors made during the wizard and everything appears as expected.
+ </div><div class="para">
+ Select the <span class="guilabel"><strong>Customize configuration before install</strong></span> check box to change the guest's storage or network devices, to use the para-virtualized drivers or to add additional devices.
+ </div><div class="para">
+ Click on the <code class="systemitem">Advanced options</code> down arrow to inspect and modify advanced options. For a standard Red Hat Enterprise Linux 6 installation, none of these options require modification.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/11-7RHEL_local_install.png" width="444" alt="The New VM window - local storage" /></div></div><h6>Figure 7.10. The New VM window - local storage</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Finish</strong></span> to continue into the Red Hat Enterprise Linux installation sequence. For more information on installing Red Hat Enterprise Linux 6 refer to the Red Hat Enterprise Linux 6 <em class="citetitle">Installation Guide</em>.
+ </div></li></ol></div><div class="para">
+ A Red Hat Enterprise Linux 6 guest virtual machine is now created from an ISO installation disc image.
+ </div></div><div class="section" id="idm78294688"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm78294688">7.2. Creating a Red Hat Enterprise Linux 6 guest with a network installation tree</h2></div></div></div><div class="procedure"><h6>Procedure 7.2. Creating a Red Hat Enterprise Linux 6 guest with virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Optional: Preparation</strong></p><div class="para">
+ Prepare the storage environment for the guest virtual machine. For more information on preparing storage, refer to the <em class="citetitle">Red Hat Enterprise Linux 6 Virtualization Administration Guide</em>.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ >Various storage types may be used for storing guest virtual machines. However, for a virtual machine to be able to use migration features the virtual machine must be created on networked storage.
+ </div></div></div><div class="para">
+ Red Hat Enterprise Linux 6 requires at least 1GB of storage space. However, Red Hat recommends at least 5GB of storage space for a Red Hat Enterprise Linux 6 installation and for the procedures in this guide.
+ </div></li><li class="step"><p class="title"><strong>Open virt-manager and start the wizard</strong></p><div class="para">
+ Open virt-manager by executing the <code class="command">virt-manager</code> command as root or opening <span class="guilabel"><strong>Applications</strong></span> → <span class="guilabel"><strong>System Tools</strong></span> → <span class="guilabel"><strong>Virtual Machine Manager</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt1-pic1.png" alt="The main virt-manager window" /></div></div><h6>Figure 7.11. The main virt-manager window</h6></div><br class="figure-break" /><div class="para">
+ Click on the <span class="guibutton"><strong>Create a new virtual machine</strong></span> button to start the new virtual machine wizard.
+ </div><div class="figure" id="gofigurego2"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_newicon.png" alt="The Create a new virtual machine button" /></div></div><h6>Figure 7.12. The Create a new virtual machine button</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guilabel"><strong>Create a new virtual machine</strong></span> window opens.
+ </div></li><li class="step"><p class="title"><strong>Name the virtual machine</strong></p><div class="para">
+ Virtual machine names can contain letters, numbers and the following characters: '<span class="keycap"><strong>_</strong></span>', '<span class="keycap"><strong>.</strong></span>' and '<span class="keycap"><strong>-</strong></span>'. Virtual machine names must be unique for migration and cannot consist only of numbers.
+ </div><div class="para">
+ Choose the installation method from the list of radio buttons.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/rhel6_Screenshot-step1.png" width="444" alt="The New VM window - Step 1" /></div></div><h6>Figure 7.13. The New VM window - Step 1</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><div class="para">
+ Provide the installation URL, and the Kickstart URL and Kernel options if required.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt2-pic3.png" alt="The New VM window - Step 2" /></div></div><h6>Figure 7.14. The New VM window - Step 2</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><div class="para">
+ The remaining steps are the same as the ISO installation procedure. Continue from <a class="xref" href="#RAM-and-VCPUs">Step 5</a> of the ISO installation procedure.
+ </div></li></ol></div></div><div class="section" id="idm86720352"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm86720352">7.3. Creating a Red Hat Enterprise Linux 6 guest with PXE</h2></div></div></div><div class="procedure"><h6>Procedure 7.3. Creating a Red Hat Enterprise Linux 6 guest with virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Optional: Preparation</strong></p><div class="para">
+ Prepare the storage environment for the virtual machine. For more information on preparing storage, refer to the <em class="citetitle">Red Hat Enterprise Linux 6 Virtualization Administration Guide</em>.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Various storage types may be used for storing guest virtual machines. However, for a virtual machine to be able to use migration features the virtual machine must be created on networked storage.
+ </div></div></div><div class="para">
+ Red Hat Enterprise Linux 6 requires at least 1GB of storage space. However, Red Hat recommends at least 5GB of storage space for a Red Hat Enterprise Linux 6 installation and for the procedures in this guide.
+ </div></li><li class="step"><p class="title"><strong>Open virt-manager and start the wizard</strong></p><div class="para">
+ Open virt-manager by executing the <code class="command">virt-manager</code> command as root or opening <span class="guilabel"><strong>Applications</strong></span> → <span class="guilabel"><strong>System Tools</strong></span> → <span class="guilabel"><strong>Virtual Machine Manager</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt1-pic1.png" alt="The main virt-manager window" /></div></div><h6>Figure 7.15. The main virt-manager window</h6></div><br class="figure-break" /><div class="para">
+ Click on the <span class="guibutton"><strong>Create new virtualized guest</strong></span> button to start the new virtualized guest wizard.
+ </div><div class="figure" id="gofigurego3"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_newicon.png" alt="The create new virtualized guest button" /></div></div><h6>Figure 7.16. The create new virtualized guest button</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guilabel"><strong>New VM</strong></span> window opens.
+ </div></li><li class="step"><p class="title"><strong>Name the virtual machine</strong></p><div class="para">
+ Virtual machine names can contain letters, numbers and the following characters: '<span class="keycap"><strong>_</strong></span>', '<span class="keycap"><strong>.</strong></span>' and '<span class="keycap"><strong>-</strong></span>'. Virtual machine names must be unique for migration and cannot consist only of numbers.
+ </div><div class="para">
+ Choose the installation method from the list of radio buttons.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt3-pic2.png" alt="The New VM window - Step 1" /></div></div><h6>Figure 7.17. The New VM window - Step 1</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><div class="para">
+ The remaining steps are the same as the ISO installation procedure. Continue from <a class="xref" href="#RAM-and-VCPUs">Step 5</a> of the ISO installation procedure. From this point, the only difference in this PXE procedure is on the final <span class="guilabel"><strong>New VM</strong></span> screen, which shows the <span class="guilabel"><strong>Install: PXE Install</strong></span> field.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt3-pic6.png" alt="The New VM window - Step 5 - PXE Install" /></div></div><h6>Figure 7.18. The New VM window - Step 5 - PXE Install</h6></div><br class="figure-break" /></li></ol></div></div></div><div xml:lang="en-US" class="chapter" id="idm74619792" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="idm74619792">Chapter 8. Virtualizing Fedora on Other Platforms</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#idm119852976">8.1. On VMWare</a></span></dt><dt><span class="section"><a href="#idm93540832">8.2. On Hyper-V</a></span></dt></dl></div><div class="para">
+ This chapter contains useful reference material for customers running Fedora as a virtualized operating system on other virtualization hosts.
+ </div><div class="section" id="idm119852976"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm119852976">8.1. On VMWare</h2></div></div></div><div class="para">
+ Fedora 17 and onwards provide the <code class="systemitem">vmxnet3</code> driver, a para-virtualized network adapter used when running Red Hat Enterprise Linux on VMWare hosts. For further information about this driver, refer to <a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001805">http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001805</a>.
+ </div><div class="para">
+ Fedora 18 and onwards provide the <code class="systemitem">vmw_pvscsi</code> driver, a para-virtualized SCSI adapter used when running Red Hat Enterprise Linux on VMWare hosts. For further information about this driver, refer to <a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010398">http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010398</a>.
+ </div></div><div class="section" id="idm93540832"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm93540832">8.2. On Hyper-V</h2></div></div></div><div class="para">
+ Fedora 18 and onwards provide Microsoft's Linux Integration Services, a set of drivers that enable synthetic device support in supported virtualized operating systems. Fedora is a supported virtualized operating system under Linux Integration Services version 3.4. Further details about the drivers provided are available from <a href="http://www.microsoft.com/en-us/download/details.aspx?id=34603">http://www.microsoft.com/en-us/download/details.aspx?id=34603</a>.
+ </div></div></div><div xml:lang="en-US" class="chapter" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 9. Installing a fully-virtualized Windows guest</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_virt-install">9.1. Using virt-install to create a guest</a></span></dt></dl></div><div class="para">
+ This chapter describes how to create a fully-virtualized Windows guest using the command-line (<code class="command">virt-install</code>), launch the operating system's installer inside the guest, and access the installer through <code class="command">virt-viewer</code>.
+ </div><div class="para">
+ To install a Windows operating system on the guest, use the <code class="command">virt-viewer</code> tool. This tool allows you to display the graphical console of a virtual machine (via the VNC protocol). In doing so, <code class="command">virt-viewer</code> allows you to install a fully-virtualized guest's operating system with that operating system's installer (for example, the Windows XP installer).
+ </div><div class="para">
+ Installing a Windows operating system involves two major steps:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Creating the guest virtual machine, using either <code class="command">virt-install</code> or <code class="command">virt-manager</code>.
+ </div></li><li class="listitem"><div class="para">
+ Installing the Windows operating system on the guest virtual machine, using <code class="command">virt-viewer</code>.
+ </div></li></ol></div><div class="para">
+ Refer to <a class="xref" href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation">Chapter 6, <em>Guest virtual machine installation overview</em></a> for details about creating a guest virtual machine with <code class="command">virt-install</code> or <code class="command">virt-manager</code>.
+ </div><div class="para">
+ Note that this chapter does not describe how to install a Windows operating system on a fully-virtualized guest. Rather, it only covers how to create the guest and launch the installer within the guest. For information on how to install a Windows operating system, refer to the relevant Microsoft installation documentation.
+ </div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_virt-install"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.1. Using virt-install to create a guest</h2></div></div></div><div class="para">
+ The <code class="command">virt-install</code> command allows you to create a fully-virtualized guest from a terminal, for example, without a GUI.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Before creating the guest, consider first if the guest needs to use KVM Windows para-virtualized drivers. If it does, keep in mind that you can do so <span class="emphasis"><em>during</em></span> or <span class="emphasis"><em>after</em></span> installing the Windows operating system on the guest. For more information about para-virtualized drivers, refer to <a class="xref" href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers">Chapter 10, <em>KVM Para-virtualized Drivers</em></a>.
+ </div><div class="para">
+ For instructions on how to install KVM para-virtualized drivers, refer to <a class="xref" href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers">Section 10.1, “Installing the KVM Windows para-virtualized drivers”</a>.
+ </div></div></div><div class="para">
+ It is possible to create a fully-virtualized guest with only a single command. To do so, run the following program (replace the values accordingly):
+ </div><pre class="screen"># virt-install \
+ --name=<em class="replaceable"><code>guest-name</code></em> \
+ --os-type=<em class="replaceable"><code>windows</code></em> \
+ --network network=default \
+ --disk path=<em class="replaceable"><code>path-to-disk</code></em>,size=<em class="replaceable"><code>disk-size</code></em> \
+ --cdrom=<em class="replaceable"><code>path-to-install-disk</code></em> \
+ --graphics spice --ram=1024</pre><div class="para">
+ The <code class="command"><em class="replaceable"><code>path-to-disk</code></em></code> must be a device (e.g. <code class="filename">/dev/sda3</code>) or image file (<code class="filename">/var/lib/libvirt/images/<em class="replaceable"><code>name</code></em>.img</code>). It must also have enough free space to support the <code class="command"><em class="replaceable"><code>disk-size</code></em></code>.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ All image files are stored in <code class="filename">/var/lib/libvirt/images/</code> by default. Other directory locations for file-based images are possible, but may require SELinux configuration. If you run SELinux in enforcing mode.
+ </div></div></div><div class="para">
+ You can also run <code class="command">virt-install</code> interactively. To do so, use the <code class="command">--prompt</code> command, as in:
+ </div><pre class="screen"># virt-install --prompt</pre><div class="para">
+ Once the fully-virtualized guest is created, <code class="command">virt-viewer</code> will launch the guest and run the operating system's installer. Refer to to the relevant Microsoft installation documentation for instructions on how to install the operating system.
+ </div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 10. KVM Para-virtualized Drivers</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers">10.1. Installing the KVM Windows para-virtualized drivers</a></span></dt><dt><span class="section"><a href="#form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager">10.2. Installing the drivers on an installed Windows guest virtual machine</a></span></dt><dt><span class="section"><a href="#form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk"
>10.3. Installing drivers during the Windows installation</a></span></dt><dt><span class="section"><a href="#idm123282160">10.4. Using the para-virtualized drivers with Red Hat Enterprise Linux 3.9 guests</a></span></dt><dt><span class="section"><a href="#form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices">10.5. Using KVM para-virtualized drivers for existing devices</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices">10.6. Using KVM para-virtualized drivers for new devices</a></span></dt></dl></div><div class="para">
+ Para-virtualized drivers are available for Windows guest virtual machines 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 the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Red Hat Enterprise Linux 4.8 and newer
+ </div></li><li class="listitem"><div class="para">
+ Red Hat Enterprise Linux 5.3 and newer
+ </div></li><li class="listitem"><div class="para">
+ Red Hat Enterprise Linux 6 and newer
+ </div></li><li class="listitem"><div class="para">
+ Some versions of Linux based on the 2.6.27 kernel or newer kernel versions.
+ </div></li></ul></div><div class="para">
+ Versions of Red Hat Enterprise Linux in the list above detect and install the drivers, additional installation steps are not required.
+ </div><div class="para">
+ In Red Hat Enterprise Linux 3 (3.9 and above), manual installation is required.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ PCI devices are limited by the virtualized system architecture. Refer to <a class="xref" href="#chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config">Chapter 12, <em>PCI device configuration</em></a> for additional limitations when using assigned devices.
+ </div></div></div><div class="para">
+ Using KVM para-virtualized drivers, the following Microsoft Windows versions are expected to run similarly to bare-metal-based systems.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Windows XP Service Pack 3 and newer (32-bit only)
+ </div></li><li class="listitem"><div class="para">
+ Windows Server 2003 (32-bit and 64-bit versions)
+ </div></li><li class="listitem"><div class="para">
+ Windows Server 2008 (32-bit and 64-bit versions)
+ </div></li><li class="listitem"><div class="para">
+ Windows Server 2008 R2 (64-bit only)
+ </div></li><li class="listitem"><div class="para">
+ Windows 7 (32-bit and 64-bit versions)
+ </div></li></ul></div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.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 a guest virtual machine using one of the following methods:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ hosting the installation files on a network accessible to the virtual machine,
+ </div></li><li class="listitem"><div class="para">
+ using a virtualized CD-ROM device of the driver installation disk .iso file, or
+ </div></li><li class="listitem"><div class="para">
+ using a virtualized floppy device to install the drivers during boot time.
+ </div></li></ul></div><div class="para">
+ This guide describes installation from the para-virtualized installer disk as a virtualized CD-ROM device.
+ </div><div class="procedure"><ol class="1"><li class="step" id="step-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Download_the_drivers"><p class="title"><strong>Download the drivers</strong></p><div class="para">
+ The <span class="package">virtio-win</span> package contains the para-virtualized block and network drivers for all supported Windows guest virtual machines.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The <span class="package">virtio-win</span> package can be found here in RHN: <a href="https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=602010">https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=602010</a>. It requires access to one of the following channels:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ RHEL Client Supplementary (v. 6)
+ </div></li><li class="listitem"><div class="para">
+ RHEL Server Supplementary (v. 6)
+ </div></li><li class="listitem"><div class="para">
+ RHEL Workstation Supplementary (v. 6)
+ </div></li></ul></div></div></div><div class="para">
+ Download and install the <span class="package">virtio-win</span> package on the host with the <code class="command">yum</code> command.
+ </div><pre class="screen"> # yum install virtio-win</pre><div class="para">
+ The list of virtio-win packages that are supported on Windows operating systems, and the current certified package version, can be found at the following URL: <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">
+ Note that the Red Hat Enterprise Virtualization Hypervisor and Red Hat Enterprise Linux are created on the same code base so the drivers for the same version (for example, Red Hat Enterprise Virtualization Hypervisor 3.0 and Red Hat Enterprise Linux 6) are supported for both environments.
+ </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 class="step" id="step-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Install_the_para_virtualized_drivers"><p class="title"><strong>Install the para-virtualized drivers</strong></p><div class="para">
+ It is recommended to install the drivers on the virtual machine 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 virtual machine, the drivers must be installed before the device is modified. If the drivers are not installed on the virtual machine and the driver is set to the virtio driver the virtual machine will not boot.
+ </div></li></ol></div></div><div class="section" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.2. Installing the drivers on an installed Windows guest virtual machine</h2></div></div></div><div class="para">
+ This procedure covers installing the para-virtualized drivers with a virtualized CD-ROM after Windows is installed.
+ </div><div class="para">
+ Follow <a class="xref" href="#proc-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_virt_manager_to_mount_a_CD_ROM_image_for_a_Windows_guest">Procedure 10.1, “Installing from the driver CD-ROM image with virt-manager”</a> to add a CD-ROM image with <code class="command">virt-manager</code> and then install the drivers.
+ </div><div class="procedure" id="proc-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_virt_manager_to_mount_a_CD_ROM_image_for_a_Windows_guest"><h6>Procedure 10.1. Installing from the driver CD-ROM image with virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Open virt-manager and the guest virtual machine</strong></p><div class="para">
+ Open <code class="command">virt-manager</code>, then open the guest virtual machine from the list by double-clicking the guest name.
+ </div></li><li class="step"><p class="title"><strong>Open the hardware window</strong></p><div class="para">
+ Click the lightbulb icon on the toolbar at the top of the window to view virtual hardware details.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/vm_info_button_new.png" alt="The Show virtual hardware details button." /></div></div><h6>Figure 10.1. The virtual hardware details button</h6></div><br class="figure-break" /><div class="para">
+ Then click the <span class="guibutton"><strong>Add Hardware</strong></span> button at the bottom of the new view that appears.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/vm_add_hardware_new.png" alt="The Add Hardware button." /></div></div><h6>Figure 10.2. The virtual machine hardware information window</h6></div><br class="figure-break" /><div class="para">
+ This opens a wizard for adding the new device.
+ </div></li><li class="step"><p class="title"><strong>Select the device type — for Red Hat Enterprise Linux 6 versions prior to 6.2</strong></p><div class="para">
+ Skip this step if you are using Red Hat Enterprise Linux 6.2 or later.
+ </div><div class="para">
+ On Red Hat Enterprise Linux 6 versions prior to version 6.2, you must select the type of device you wish to add. In this case, select <span class="guilabel"><strong>Storage</strong></span> from the dropdown menu.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_hardware_wizard1.png" alt="The Add new virtual hardware wizard window in Red Hat Enterprise Linux 6.1 with Storage selected as the hardware type." /></div></div><h6>Figure 10.3. The Add new virtual hardware wizard in Red Hat Enterprise Linux 6.1</h6></div><br class="figure-break" /><div class="para">
+ Click the <span class="guibutton"><strong>Finish</strong></span> button to proceed.
+ </div></li><li class="step"><p class="title"><strong>Select the ISO file</strong></p><div class="para">
+ Ensure that the <span class="guilabel"><strong>Select managed or other existing storage</strong></span> radio button is selected, and browse to the para-virtualized driver's <code class="filename">.iso</code> image file. The default location for the latest version of the drivers is <code class="filename">/usr/share/virtio-win/virtio-win.iso</code>.
+ </div><div class="para">
+ Change the <span class="guilabel"><strong>Device type</strong></span> to <span class="guilabel"><strong>IDE cdrom</strong></span> and click the <span class="guibutton"><strong>Forward</strong></span> button to proceed.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/type_assigned-KVM_PV_new.png" width="444" alt="Selecting the ISO file in the Add new virtual hardware wizard window." /></div></div><h6>Figure 10.4. The Add new virtual hardware wizard</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Finish adding virtual hardware — for Red Hat Enterprise Linux 6 versions prior to 6.2</strong></p><div class="para">
+ If you are using Red Hat Enterprise Linux 6.2 or later, skip this step.
+ </div><div class="para">
+ On Red Hat Enterprise Linux 6 versions prior to version 6.2, click on the <span class="guibutton"><strong>Finish</strong></span> button to finish adding the virtual hardware and close the wizard.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/done-KVM_PV.png" alt="The final screen of the Add new virtual hardware wizard in Red Hat Enterprise Linux 6.1." /></div></div><h6>Figure 10.5. The Add new virtual hardware wizard in Red Hat Enterprise Linux 6.1</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Reboot</strong></p><div class="para">
+ Reboot or start the virtual machine to begin using the driver disc. Virtualized IDE devices require a restart to for the virtual machine to recognize the new device.
+ </div></li></ol></div><div class="para">
+ Once the CD-ROM with the drivers is attached and the virtual machine has started, proceed with <a class="xref" href="#wooras">Procedure 10.2, “Windows installation on a Windows 7 virtual machine”</a>.
+ </div><div class="procedure" id="wooras"><h6>Procedure 10.2. Windows installation on a Windows 7 virtual machine</h6><div class="para">
+ This procedure installs the drivers on a Windows 7 virtual machine as an example. Adapt the Windows installation instructions to your guest's version of Windows.
+ </div><ol class="1"><li class="step"><p class="title"><strong>Open the Computer Management window</strong></p><div class="para">
+ On the desktop of the Windows virtual machine, click the <span class="guibutton"><strong>Windows</strong></span> icon at the bottom corner of the screen to open the Start menu.
+ </div><div class="para">
+ Right-click on <span class="guilabel"><strong>Computer</strong></span> and select <span class="guilabel"><strong>Manage</strong></span> from the pop-up menu.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/StartDevManagerInVM_win7.png" width="444" alt="A menu window opens on the Computer Management window when right-clicking D the My Computer icon on the desktop." /></div></div><h6>Figure 10.6. The Computer Management window</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Open the Device Manager</strong></p><div class="para">
+ Select the <span class="guilabel"><strong>Device Manager</strong></span> from the left-most pane. This can be found under <span class="guilabel"><strong>Computer Management</strong></span> > <span class="guilabel"><strong>System Tools</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/DevManagerStart_win7.png" width="444" alt="Opening the Device Manager on the right hand side of the Computer Management window." /></div></div><h6>Figure 10.7. The Computer Management window</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Start the driver update wizard</strong></p><ol class="a"><li class="step"><p class="title"><strong>View available system devices</strong></p><div class="para">
+ Expand <span class="guilabel"><strong>System devices</strong></span> by clicking on the arrow to its left.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/DriverInstall-Expand.png" width="444" alt="Detail of viewing available system devices from the Computer Management window." /></div></div><h6>Figure 10.8. Viewing available system devices in the Computer Management window</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Locate the appropriate device</strong></p><div class="para">
+ There are up to four drivers available: the balloon driver, the serial driver, the network driver, and the block driver.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">Balloon</code>, the balloon driver, affects the <span class="guilabel"><strong>PCI standard RAM Controller</strong></span> in the <span class="guilabel"><strong>System devices</strong></span> group.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">vioserial</code>, the serial driver, affects the <span class="guilabel"><strong>PCI Simple Communication Controller</strong></span> in the <span class="guilabel"><strong>System devices</strong></span> group.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">NetKVM</code>, the network driver, affects the <span class="guilabel"><strong>Network adapters</strong></span> group. This driver is only available if a virtio NIC is configured. Configurable parameters for this driver are documented in <a class="xref" href="#netkvm-parameters">Appendix C, <em>NetKVM Driver Parameters</em></a>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">viostor</code>, the block driver, affects the <span class="guilabel"><strong>Disk drives</strong></span> group. This driver is only available if a virtio disk is configured.
+ </div></li></ul></div><div class="para">
+ Right-click on the device whose driver you wish to update, and select <span class="guilabel"><strong>Update Driver...</strong></span> from the pop-up menu.
+ </div><div class="para">
+ This example installs the balloon driver, so right-click on <span class="guilabel"><strong>PCI standard RAM Controller</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/StartInstallingBalloon-1_win7.png" width="444" alt="Locate the appropriate device under the expanded System Devices entry in the Computer Management window." /></div></div><h6>Figure 10.9. The Computer Management window</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Open the driver update wizard</strong></p><div class="para">
+ From the drop-down menu, select <span class="guilabel"><strong>Update Driver Software...</strong></span> to access the driver update wizard.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/DriverInstall-OpenWizard_win7.png" alt="Open the driver update wizard by right-clicking the device to be updated and selecting the first menu option, Update Driver Software, in the Computer Management window." /></div></div><h6>Figure 10.10. Opening the driver update wizard</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Specify how to find the driver</strong></p><div class="para">
+ The first page of the driver update wizard asks how you want to search for driver software. Click on the second option, <span class="guilabel"><strong>Browse my computer for driver software</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/8-BrowseForDriver_win7.png" width="444" alt="The driver update wizard provides two options for searching for driver software." /></div></div><h6>Figure 10.11. The driver update wizard</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Select the driver to install</strong></p><ol class="a"><li class="step"><p class="title"><strong>Open a file browser</strong></p><div class="para">
+ Click on <span class="guilabel"><strong>Browse...</strong></span>
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/10-w7x86driverstart_win7.png" width="444" alt="The driver update wizard." /></div></div><h6>Figure 10.12. The driver update wizard</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Browse to the location of the driver</strong></p><div class="para">
+ A separate driver is provided for each of the various combinations of operating system and architecture. The drivers are arranged hierarchically according to their driver type, the operating system, and the architecture on which they will be installed: <code class="filename"><em class="replaceable"><code>driver_type</code></em>/<em class="replaceable"><code>os</code></em>/<em class="replaceable"><code>arch</code></em>/</code>. For example, the Balloon driver for a Windows 7 operating system with an x86 (32-bit) architecture, resides in the <code class="filename">Balloon/w7/x86</code> directory.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/9-BrowseToDirectory_win7.png" alt="The Browse For Folder window, which pops up after choosing "Browse" to search for driver software on your computer. Select the folder that contains drivers for your hardware from this window." /></div></div><h6>Figure 10.13. The Browse for driver software pop-up window</h6></div><br class="figure-break" /><div class="para">
+ Once you have navigated to the correct location, click <span class="guilabel"><strong>OK</strong></span>.
+ </div></li><li class="step"><p class="title"><strong>Click <span class="guilabel"><strong>Next</strong></span> to continue</strong></p><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/10-w7x86driverchosen_win7.png" width="444" alt="The Update Driver Software wizard, with the specified location to search for driver software selected, with the Browse button on the right, and the Next and Cancel buttons at the bottom right of the window." /></div></div><h6>Figure 10.14. The Update Driver Software wizard</h6></div><br class="figure-break" /><div class="para">
+ The following screen is displayed while the driver installs:
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/DuringInstallation.png" width="444" alt="As the driver software installs, a flashing bar in the Update Driver Software wizard window shows the system is busy." /></div></div><h6>Figure 10.15. The Update Driver Software wizard</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Close the installer</strong></p><div class="para">
+ The following screen is displayed when installation is complete:
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/12-DriverInstalled.png" width="444" alt="After the driver software installs, the Update Driver Software wizard window read "Windows has successfully updated your driver software"." /></div></div><h6>Figure 10.16. The Update Driver Software wizard</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guilabel"><strong>Close</strong></span> to close the installer.
+ </div></li><li class="step"><p class="title"><strong>Reboot</strong></p><div class="para">
+ Reboot the virtual machine to complete the driver installation.
+ </div></li></ol></div></div><div class="section" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.3. Installing drivers during the Windows installation</h2></div></div></div><div class="para">
+ This procedure covers installing the para-virtualized drivers during a Windows installation.
+ </div><div class="para">
+ This method allows a Windows guest virtual machine to use the para-virtualized (<code class="command">virtio</code>) drivers for the default storage device.
+ </div><div class="procedure"><h6>Procedure 10.3. Installing para-virtualized drivers during the Windows installation</h6><ol class="1"><li class="step"><div class="para">
+ Install the virtio-win package:
+ </div><pre class="screen"># yum install virtio-win</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The <span class="package">virtio-win</span> package can be found here in RHN: <a href="https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=602010">https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=602010</a>. It requires access to one of the following channels:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ RHEL Client Supplementary (v. 6)
+ </div></li><li class="listitem"><div class="para">
+ RHEL Server Supplementary (v. 6)
+ </div></li><li class="listitem"><div class="para">
+ RHEL Workstation Supplementary (v. 6)
+ </div></li></ul></div></div></div></li><li class="step"><p class="title"><strong>Creating the guest virtual machine</strong></p><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Create the virtual machine, as normal, without starting the virtual machine. Follow one of the procedures below.
+ </div></div></div><div class="para">
+ Select <span class="emphasis"><em>one</em></span> of the following guest-creation methods, and follow the instructions.
+ </div><ol class="a"><li class="step"><p class="title"><strong>Creating the guest virtual machine with virsh</strong></p><div class="para">
+ This method attaches the para-virtualized driver floppy disk to a Windows guest <span class="emphasis"><em>before</em></span> the installation.
+ </div><div class="para">
+ If the virtual machine is created from an XML definition file with <code class="command">virsh</code>, use the <code class="command">virsh define</code> command not the <code class="command">virsh create</code> command.
+ </div><ol class="i"><li class="step"><div class="para">
+ Create, but do not start, the virtual machine. Refer to the <em class="citetitle">Red Hat Enterprise Linux Virtualization Administration Guide</em> for details on creating virtual machines with the <code class="command">virsh</code> command.
+ </div></li><li class="step"><div class="para">
+ Add the driver disk as a virtualized floppy disk with the <code class="command">virsh</code> command. This example can be copied and used if there are no other virtualized floppy devices attached to the guest virtual machine. Note that <em class="replaceable"><code>vm_name</code></em> should be replaced with the name of the virtual machine.
+ </div><pre class="screen"># virsh attach-disk <em class="replaceable"><code>vm_name</code></em> /usr/share/virtio-win/virtio-win.vfd fda --type floppy</pre><div class="para">
+ You can now continue with <a class="xref" href="#aftercreation">Step 3</a>.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Creating the guest virtual machine with virt-manager and changing the disk type</strong></p><ol class="i"><li class="step"><div class="para">
+ At the final step of the virt-manager guest creation wizard, check the <span class="guilabel"><strong>Customize configuration before install</strong></span> checkbox.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-0-click-configure-before-install.png" alt="Step 5 of 5 of creating a new virtual machine with virt-manager, with a checkbox selected under Storage to customize configuration before install." /></div></div><h6>Figure 10.17. The virt-manager guest creation wizard</h6></div><br class="figure-break" /><div class="para">
+ Click on the <span class="guibutton"><strong>Finish</strong></span> button to continue.
+ </div></li><li class="step"><p class="title"><strong>Open the Add Hardware wizard</strong></p><div class="para">
+ Click the <span class="guilabel"><strong>Add Hardware</strong></span> button in the bottom left of the new panel.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-1-click-add-hardware.png" alt="The Add Hardware button." /></div></div><h6>Figure 10.18. The Add Hardware button</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Select storage device</strong></p><div class="para">
+ <span class="guilabel"><strong>Storage</strong></span> is the default selection in the <span class="guilabel"><strong>Hardware type</strong></span> list.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-2z-select-storage.png" width="444" alt="The Add new virtual hardware wizard with Storage selected in the Hardware type field." /></div></div><h6>Figure 10.19. The Add new virtual hardware wizard</h6></div><br class="figure-break" /><div class="para">
+ Ensure the <span class="guilabel"><strong>Select managed or other existing storage</strong></span> radio button is selected. Click <span class="guibutton"><strong>Browse...</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-2a-select-existing-storage.png" alt="The Add new virtual hardware wizard with Storage selected in the Hardware type field, and the Select managed or other existing storage radio button selected." /></div></div><h6>Figure 10.20. Select managed or existing storage</h6></div><br class="figure-break" /><div class="para">
+ In the new window that opens, click <span class="guilabel"><strong>Browse Local</strong></span>. Navigate to <code class="filename">/usr/share/virtio-win/virtio-win.vfd</code>, and click <span class="guibutton"><strong>Select</strong></span> to confirm.
+ </div><div class="para">
+ Change <span class="guilabel"><strong>Device type</strong></span> to <span class="guilabel"><strong>Floppy disk</strong></span>, and click <span class="guibutton"><strong>Finish</strong></span> to continue.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-select-device-type-floppy.png" alt="The Device type field, set to Floppy Disk." /></div></div><h6>Figure 10.21. Change the Device type</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Confirm settings</strong></p><div class="para">
+ Review the device settings.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-confirm-floppy-settings.png" width="444" alt="The virtual machine hardware information window with the target device (Floppy 1) selected." /></div></div><h6>Figure 10.22. The virtual machine hardware information window</h6></div><br class="figure-break" /><div class="para">
+ You have now created a removable device accessible by your virtual machine.
+ </div></li><li class="step"><p class="title"><strong>Change the hard disk type</strong></p><div class="para">
+ To change the hard disk type from <em class="replaceable"><code>IDE Disk</code></em> to <em class="replaceable"><code>Virtio Disk</code></em>, we must first remove the existing hard disk, Disk 1. Select the disk and click on the <span class="guibutton"><strong>Remove</strong></span> button.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-remove-disk1.png" width="444" alt="The virtual machine hardware information window with virtual disk Disk 1 selected, with the Remove button available at the bottom right corner of the window." /></div></div><h6>Figure 10.23. The virtual machine hardware information window</h6></div><br class="figure-break" /><div class="para">
+ Add a new virtual storage device by clicking <span class="guilabel"><strong>Add Hardware</strong></span>. Then, change the <span class="guilabel"><strong>Device type</strong></span> from <em class="replaceable"><code>IDE disk</code></em> to <em class="replaceable"><code>Virtio Disk</code></em>. Click <span class="guibutton"><strong>Finish</strong></span> to confirm the operation.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-device-type-virtio-finish.png" width="444" alt="The virtual machine hardware information window with the Floppy 1 target device selected, and the Add Hardware on the left bottom corner of the window." /></div></div><h6>Figure 10.24. The virtual machine hardware information window</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Ensure settings are correct</strong></p><div class="para">
+ Review the settings for <em class="replaceable"><code>VirtIO Disk 1</code></em>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-review-virtio-settings.png" width="444" alt="The virtual machine hardware information window with the Overview option selected, showing Basic Details, Hypervisor Details, plus expandable headings Machine Setting and Security, in the right part of the window." /></div></div><h6>Figure 10.25. The virtual machine hardware information window</h6></div><br class="figure-break" /><div class="para">
+ When you are satisfied with the configuration details, click the <span class="guilabel"><strong>Begin Installation</strong></span> button.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-5-begin-installation.png" alt="The Begin Installation button." /></div></div><h6>Figure 10.26. The Begin Installation button</h6></div><br class="figure-break" /><div class="para">
+ You can now continue with <a class="xref" href="#aftercreation">Step 3</a>.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Creating the guest virtual machine with virt-install</strong></p><div class="para">
+ Append the following parameter exactly as listed below to add the driver disk to the installation with the <code class="command">virt-install</code> command:
+ </div><pre class="screen">--disk path=/usr/share/virtio-win/virtio-win.vfd,device=floppy</pre><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ If the device you wish to add is a <code class="literal">disk</code> (that is, not a <code class="literal">floppy</code> or a <code class="literal">cdrom</code>), you will also need to add the <code class="code">bus=virtio</code> option to the end of the <em class="parameter"><code>--disk</code></em> parameter, like so:
+ </div><pre class="screen">--disk path=/usr/share/virtio-win/virtio-win.vfd,device=disk,bus=virtio</pre></div></div><div class="para">
+ According to the version of Windows you are installing, append one of the following options to the <code class="command">virt-install</code> command:
+ </div><pre class="screen">--os-variant winxp</pre><pre class="screen">--os-variant win2k3</pre><pre class="screen">--os-variant win7</pre><div class="para">
+ You can now continue with <a class="xref" href="#aftercreation">Step 3</a>.
+ </div></li></ol></li><li class="step" id="aftercreation"><p class="title"><strong>Additional steps for driver installation</strong></p><div class="para">
+ During the installation, additional steps are required to install drivers, depending on the type of Windows guest.
+ </div><ol class="a"><li class="step" id="step-Virtualization-Installing_the_KVM_Windows_para_virtualized_drivers-Windows_Server_2003"><p class="title"><strong>Windows Server 2003 and Windows XP</strong></p><div class="para">
+ Before the installation blue screen repeatedly press <span class="keycap"><strong>F6</strong></span> for third party drivers.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/XP-driver-capture.png" width="444" alt="The Windows pre-installation blue screen reads Window Setup at the top in plain text, and "Press F6 if you need to install a third party SCSI or RAID driver..." at the bottom." /></div></div><h6>Figure 10.27. The Windows Setup screen</h6></div><br class="figure-break" /><div class="para">
+ Press <span class="keycap"><strong>S</strong></span> to install additional device drivers.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/XP-driver-select2.png" width="444" alt="The next Windows pre-installation blue screen reads Window Setup at the top in plain text and details the option to install an additional device. Options at the bottom of the screen include S to "Specify Additional Device", ENTER to continue, or F3 to exit." /></div></div><h6>Figure 10.28. The Windows Setup screen</h6></div><br class="figure-break" /><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/XP-driver-select-driver.png" width="444" alt="The next Windows blue screen reads Window Setup at the top in plain text and provides options to select the SCSI Adapter to be installed. Options at the bottom of the screen include ENTER to select, or F3 to exit." /></div></div><h6>Figure 10.29. The Windows Setup screen</h6></div><br class="figure-break" /><div class="para">
+ Press <span class="keycap"><strong>Enter</strong></span> to continue the installation.
+ </div></li><li class="step" id="step-Virtualization-Installing_the_KVM_Windows_para_virtualized_drivers-Windows_Server_2008"><p class="title"><strong>Windows Server 2008</strong></p><div class="para">
+ Follow the same procedure for Windows Server 2003, but when the installer prompts you for the driver, click on <span class="guilabel"><strong>Load Driver</strong></span>, point the installer to <code class="systemitem">Drive A:</code> and pick the driver that suits your guest operating system and architecture.
+ </div></li></ol></li></ol></div></div><div class="section" id="idm123282160"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm123282160">10.4. Using the para-virtualized drivers with Red Hat Enterprise Linux 3.9 guests</h2></div></div></div><div class="para">
+ Para-virtualized drivers for Red Hat Enterprise Linux 3.9 consist of five kernel modules: <code class="command">virtio</code>, <code class="command">virtio_blk</code>, <code class="command">virtio_net</code>, <code class="command">virtio_pci</code> and <code class="command">virtio_ring</code>. All five modules must be loaded to use both the para-virtualized block and network devices drivers.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ For Red Hat Enterprise Linux 3.9 guests, the <span class="package">kmod-virtio</span> package is a requirement for the <code class="command">virtio</code> module.
+ </div></div></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ To use the network device driver only, load the <code class="command">virtio</code>, <code class="command">virtio_net</code> and <code class="command">virtio_pci</code> modules. To use the block device driver only, load the <code class="command">virtio</code>, <code class="command">virtio_ring</code>, <code class="command">virtio_blk</code> and <code class="command">virtio_pci</code> modules.
+ </div></div></div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The <span class="package">virtio</span> package modifies the initrd RAM disk file in the <code class="filename">/boot</code> directory. The original initrd file is saved to <code class="filename">/boot/initrd-<em class="replaceable"><code>kernel-version</code></em>.img.virtio.orig</code>. The original initrd file is replaced with a new initrd RAM disk containing the <code class="command">virtio</code> driver modules. The initrd RAM disk is modified to allow the virtual machine to boot from a storage device using the para-virtualized drivers. To use a different initrd file, you must ensure that drivers are loaded with the <code class="filename">sysinit</code> script (<a class="xref" href="#proc1">Loading the para-virtualized drivers with the sysinit script</a>) or when creating new initrd RAM disk (<a class="xref" href="#proc2">Adding the para-virtualized drivers to the initrd RAM disk</a>).
+ </div></div></div><div class="formalpara" id="proc1"><h5 class="formalpara">Loading the para-virtualized drivers with the sysinit script</h5>
+ This procedure covers loading the para-virtualized driver modules during the boot sequence on a Red Hat Enterprise Linux 3.9 or newer guest with the <code class="filename">sysinit</code> script. Note that the guest virtual machine cannot use the para-virtualized drivers for the default boot disk if the modules are loaded with the <code class="filename">sysinit</code> script.
+ </div><div class="para">
+ The drivers must be loaded in the following order:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <code class="command">virtio</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">virtio_ring</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">virtio_pci</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">virtio_blk</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">virtio_net</code>
+ </div></li></ol></div><div class="para">
+ <code class="command">virtio_net</code> and <code class="command">virtio_blk</code> are the only drivers whose order can be changed. If other drivers are loaded in a different order, they will not work.
+ </div><div class="para">
+ Next, configure the modules. Locate the following section of the <code class="filename">/etc/rc.d/rc.sysinit</code> file.
+ </div><pre class="screen">if [ -f /etc/rc.modules ]; then
+ /etc/rc.modules
+fi</pre><div class="para">
+ Append the following lines after that section:
+ </div><pre class="screen">if [ -f /etc/rc.modules ]; then
+ /etc/rc.modules
+fi
+
+modprobe virtio
+modprobe virtio_ring # Comment this out if you do not need block driver
+modprobe virtio_blk # Comment this out if you do not need block driver
+modprobe virtio_net # Comment this out if you do not need net driver
+modprobe virtio_pci</pre><div class="para">
+ Reboot the guest virtual machine to load the kernel modules.
+ </div><div class="formalpara" id="proc2"><h5 class="formalpara">Adding the para-virtualized drivers to the initrd RAM disk</h5>
+ This procedure covers loading the para-virtualized driver modules with the kernel on a Red Hat Enterprise Linux 3.9 or newer guest by including the modules in the initrd RAM disk. The mkinitrd tool configures the initrd RAM disk to load the modules. Specify the additional modules with the <em class="parameter"><code>--with</code></em> parameter for the <code class="command">mkinitrd</code> command. Append following set of parameters, in the exact order, when using the <code class="command">mkinitrd</code> command to create a custom initrd RAM disk:
+ </div><pre class="screen">--with virtio --with virtio_ring --with virtio_blk --with virtio_net --with virtio_pci</pre><div class="formalpara"><h5 class="formalpara" id="idm103605488">AMD64 and Intel 64 issues</h5>
+ Use the <code class="filename">x86_64</code> version of the <span class="package">virtio</span> package for AMD64 systems.
+ </div><div class="para">
+ Use the <code class="filename">ia32e</code> version of the <span class="package">virtio</span> package for Intel 64 systems. Using the <code class="filename">x86_64</code> version of the <span class="package">virtio</span> may cause a '<code class="computeroutput">Unresolved symbol</code>' error during the boot sequence on Intel 64 systems.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm102623552">Network performance issues</h5>
+ If you experience low performance with the para-virtualized network drivers, verify the setting for the GSO and TSO features on the host system. The para-virtualized network drivers require that the GSO and TSO options are disabled for optimal performance.
+ </div><div class="para">
+ Verify the status of the GSO and TSO settings, use the command on the host (replacing <em class="replaceable"><code>interface</code></em> with the network interface used by the guest):
+ </div><pre class="screen"># ethtool -k <em class="replaceable"><code>interface</code></em></pre><div class="para">
+ Disable the GSO and TSO options with the following commands on the host:
+ </div><pre class="screen"># ethtool -K <em class="replaceable"><code>interface</code></em> gso off
+# ethtool -K <em class="replaceable"><code>interface</code></em> tso off</pre><div class="formalpara"><h5 class="formalpara" id="idm97761376">Para-virtualized driver swap partition issue</h5>
+ After activating the para-virtualized block device driver the swap partition may not be available. This issue is may be caused by a change in disk device name. To fix this issue, open the <code class="filename">/etc/fstab</code> file and locate the lines containing swap partitions, for example:
+ </div><pre class="screen">/dev/hda3 swap swap defaults 0 0</pre><div class="para">
+ The para-virtualized drivers use the <code class="command">/dev/vd*</code> naming convention, not the <code class="command">/dev/hd*</code> naming convention. To resolve this issue modify the incorrect swap entries in the <code class="filename">/etc/fstab</code> file to use the <code class="command">/dev/vd*</code> convention, for the example above:
+ </div><pre class="screen">/dev/vda3 swap swap defaults 0 0</pre><div class="para">
+ Save the changes and reboot the guest virtual machine. The virtual machine should now have swap partitions.
+ </div></div><div class="section" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.5. Using KVM para-virtualized drivers for existing devices</h2></div></div></div><div class="para">
+ You can modify an existing hard disk device attached to the guest to use the <code class="command">virtio</code> driver instead of the virtualized IDE driver. The example shown in this section edits libvirt configuration files. Note that the guest virtual machine does not need to be shut down to perform these steps, however the change will not be applied until the guest is completely shut down and rebooted.
+ </div><div class="procedure"><h6>Procedure 10.4. Using KVM para-virtualized drivers for existing devices</h6><ol class="1"><li class="step"><div class="para">
+ Ensure that you have installed the appropriate driver (<code class="classname">viostor</code>), as described in <a class="xref" href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers">Section 10.1, “Installing the KVM Windows para-virtualized drivers”</a>, before continuing with this procedure.
+ </div></li><li class="step"><div class="para">
+ Run the <code class="command">virsh edit <guestname></code> command as root to edit the XML configuration file for your device. For example, <code class="command">virsh edit guest1</code>. The configuration files are located in <code class="filename">/etc/libvirt/qemu</code>.
+ </div></li><li class="step"><div class="para">
+ Below is a file-based block device using the virtualized IDE driver. This is a typical entry for a virtual machine 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 class="step"><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>. Note that if the disk was previously IDE it will have a target similar to hda, hdb, or hdc and so on. When changing to <span class="bold bold"><strong>bus=virtio</strong></span> the target needs to be changed to vda, vdb, or vdc accordingly.
+ </div><pre class="screen"><disk type='file' device='disk'>
+ <source file='/var/lib/libvirt/images/disk1.img'/>
+ <target <span class="bold bold"><strong>dev='vda'</strong></span> <span class="bold bold"><strong>bus='virtio'/></strong></span>
+</disk></pre></li><li class="step"><div class="para">
+ Remove the <span class="bold bold"><strong>address</strong></span> tag inside the <span class="bold bold"><strong>disk</strong></span> tags. This must be done for this procedure to work. Libvirt will regenerate the <span class="bold bold"><strong>address</strong></span> tag appropriately the next time the virtual machine is started.
+ </div></li></ol></div><div class="para">
+ 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.
+ </div><div class="para">
+ Refer to the libvirt website for more details on using Virtio: <a href="http://www.linux-kvm.org/page/Virtio">http://www.linux-kvm.org/page/Virtio</a>
+ </div></div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.6. Using KVM para-virtualized drivers for new devices</h2></div></div></div><div class="para">
+ 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"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><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><div class="procedure"><h6>Procedure 10.5. Starting the new device wizard</h6><ol class="1"><li class="step"><div class="para">
+ Open the guest virtual machine by double clicking on the name of the guest in <code class="command">virt-manager</code>.
+ </div></li><li class="step"><div class="para">
+ Open the <span class="guilabel"><strong>Show virtual hardware details</strong></span> tab by clicking the <span class="guibutton"><strong>lightbulb</strong></span> button.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/vm_info_button_new.png" alt="The Show virtual hardware details tab" /></div></div><h6>Figure 10.30. The Show virtual hardware details tab</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ In the <span class="guilabel"><strong>Show virtual hardware details</strong></span> tab, click on the <span class="guilabel"><strong>Add Hardware</strong></span> button.
+ </div></li><li class="step"><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. The storage and network device wizards are covered in procedures <a class="xref" href="#procstore">Procedure 10.6, “Adding a storage device using the para-virtualized storage driver”</a> and <a class="xref" href="#procnet">Procedure 10.7, “Adding a network device using the para-virtualized network driver”</a>.
+ </div></li></ol></div><div class="procedure" id="procstore"><h6>Procedure 10.6. Adding a storage device using the para-virtualized storage driver</h6><ol class="1"><li class="step"><div class="para">
+ Open the guest virtual machine by double clicking on the name of the guest in <code class="command">virt-manager</code>.
+ </div></li><li class="step"><div class="para">
+ Open the <span class="guilabel"><strong>Show virtual hardware details</strong></span> tab by clicking the <span class="guibutton"><strong>lightbulb</strong></span> button.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/vm_info_button_new.png" alt="The Show virtual hardware details tab" /></div></div><h6>Figure 10.31. The Show virtual hardware details tab</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ In the <span class="guilabel"><strong>Show virtual hardware details</strong></span> tab, click on the <span class="guilabel"><strong>Add Hardware</strong></span> button.
+ </div></li><li class="step"><p class="title"><strong>Select hardware type</strong></p><div class="para">
+ Select <span class="guilabel"><strong>Network</strong></span> as the <span class="guilabel"><strong>Hardware type</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Network_hardware.png" width="444" alt="The Add new virtual hardware wizard with Storage selected as the hardware type." /></div></div><h6>Figure 10.32. The Add new virtual hardware wizard</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Select the network device and driver</strong></p><div class="para">
+ Create a new disk image or select a storage pool volume.
+ </div><div class="para">
+ Set the <span class="guilabel"><strong>Device type</strong></span> to <span class="guilabel"><strong>Virtio Disk</strong></span> to use the para-virtualized drivers. Choose the desired <span class="guilabel"><strong>Host device</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Network_hardware_virtio.png" width="444" alt="The Add new virtual hardware wizard Storage window, with "Select managed or other existing storage" selected and specified in the field below." /></div></div><h6>Figure 10.33. The Add new virtual hardware wizard</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guilabel"><strong>Finish</strong></span> to complete the procedure.
+ </div></li></ol></div><div class="procedure" id="procnet"><h6>Procedure 10.7. Adding a network device using the para-virtualized network driver</h6><ol class="1"><li class="step"><p class="title"><strong>Select hardware type</strong></p><div class="para">
+ Select <span class="guilabel"><strong>Network</strong></span> as the <span class="guilabel"><strong>Hardware type</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/virtio-network-step1.png" alt="The Add new virtual hardware wizard with Network selected as the hardware type." /></div></div><h6>Figure 10.34. The Add new virtual hardware wizard</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guilabel"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Select the network device and driver</strong></p><div class="para">
+ Select the network device from the <span class="guilabel"><strong>Host device</strong></span> list.
+ </div><div class="para">
+ Create a custom MAC address or use the one provided.
+ </div><div class="para">
+ Set the <span class="guilabel"><strong>Device model</strong></span> to <span class="guilabel"><strong>virtio</strong></span> to use the para-virtualized drivers.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/virtio-network-step2.png" alt="The Add new virtual hardware wizard Network setup, with options for selecting the network device and driver." /></div></div><h6>Figure 10.35. The Add new virtual hardware wizard</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guilabel"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Finish the procedure</strong></p><div class="para">
+ Confirm the details for the new device are correct.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/virtio-network-finish3.png" alt="The Add new virtual hardware wizard showing the details of the newly created network, and the Finish button at the bottom right corner of the window." /></div></div><h6>Figure 10.36. The Add new virtual hardware wizard</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guilabel"><strong>Finish</strong></span> to complete the procedure.
+ </div></li></ol></div><div class="para">
+ Once all new devices are added, reboot the virtual machine. Windows virtual machines may not recognize the devices until the guest is rebooted.
+ </div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 11. Network configuration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_address_translation_NAT_with_libvirt">11.1. Network Address Translation (NAT) with libvirt</a></span></dt><dt><span class="section"><a href="#idm103889488">11.2. Disabling vhost-net</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt">11.3. Bridged networking with libvirt</a></span></dt></dl></div><div class="para">
+ This chapter provides an introduction to the common networking configurations used by libvirt based guest virtual machines. For additional information, consult the libvirt network architecture documentation: <a href="http://libvirt.org/intro.html">http://libvirt.org/intro.html</a>.
+ </div><div class="para">
+ Fedora supports the following networking setups for virtualization:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ virtual networks using Network Address Translation (<em class="firstterm">NAT</em>)
+ </div></li><li class="listitem"><div class="para">
+ directly allocated physical devices using PCI device assignment
+ </div></li><li class="listitem"><div class="para">
+ directly allocated virtual functions using PCIe SR-IOV
+ </div></li><li class="listitem"><div class="para">
+ bridged networks
+ </div></li></ul></div><div class="para">
+ You must enable NAT, network bridging or directly assign a PCI device to allow external hosts access to network services on guest virtual machines.
+ </div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_address_translation_NAT_with_libvirt"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">11.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 known as virtual networks).
+ </div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_address_translation_NAT_with_libvirt-Host_configuration"><h5 class="formalpara">Host configuration</h5>
+ Every standard <code class="systemitem">libvirt</code> installation provides NAT-based connectivity to virtual machines as the 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. The new device uses NAT and IP forwarding to connect to the physical network. 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 guest virtual machines 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" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_address_translation_NAT_with_libvirt-Guest_configuration"><h5 class="formalpara">Guest virtual machine configuration</h5>
+ Once the host configuration is complete, a guest virtual machine can be connected to the virtual network based on its name. To connect a guest to the 'default' virtual network, the following could be used in the XML configuration file (such as <code class="filename">/etc/libvirtd/qemu/myguest.xml</code>) for the guest:
+ </div><pre class="screen"><interface type='network'>
+ <source network='default'/>
+</interface></pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Defining a MAC address is optional. If you do not define one, a MAC address is automatically generated and used as the MAC address of the bridge device used by the network. Manually setting the MAC address may be useful to maintain consistency or easy reference throughout your environment, or to avoid the very small chance of a conflict.
+ </div><pre class="screen"><interface type='network'>
+ <source network='default'/>
+ <mac address='00:16:3e:1a:b3:4a'/>
+</interface></pre></div></div></div><div class="section" id="idm103889488"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm103889488">11.2. Disabling vhost-net</h2></div></div></div><div class="para">
+ The <code class="command">vhost-net</code> module is a kernel-level backend for virtio networking that reduces virtualization overhead by moving virtio packet processing tasks out of user space (the qemu process) and into the kernel (the <code class="systemitem">vhost-net</code> driver). vhost-net is only available for virtio network interfaces. If the vhost-net kernel module is loaded, it is enabled by default for all virtio interfaces, but can be disabled in the interface configuration in the case that a particular workload experiences a degradation in performance when vhost-net is in use.
+ </div><div class="para">
+ Specifically, when UDP traffic is sent from a host machine to a guest virtual machine on that host, performance degradation can occur if the guest virtual machine processes incoming data at a rate slower than the host machine sends it. In this situation, enabling <code class="command">vhost-net</code> causes the UDP socket's receive buffer to overflow more quickly, which results in greater packet loss. It is therefore better to disable <code class="command">vhost-net</code> in this situation to slow the traffic, and improve overall performance.
+ </div><div class="para">
+ To disable <code class="command">vhost-net</code>, edit the <code class="code"><interface></code> sub-element in the guest virtual machine's XML configuration file and define the network as follows:
+ </div><pre class="screen"><interface type="network">
+ ...
+ <model type="virtio"/>
+ <driver name="qemu"/>
+ ...
+</interface></pre><div class="para">
+ Setting the driver name to <code class="literal">qemu</code> forces packet processing into qemu user space, effectively disabling vhost-net for that interface.
+ </div></div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">11.3. Bridged networking with libvirt</h2></div></div></div><div class="para">
+ Bridged networking (also known as physical device sharing) is used to dedicate 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="para">
+ To create a bridge (<code class="literal">br0</code>) based on the <code class="literal">eth0</code> interface, execute the following command on the host:
+ </div><pre class="screen"># virsh iface-bridge eth0 br0</pre><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ NetworkManager does not support bridging. NetworkManager must be disabled to use networking with the network scripts (located in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory).
+ </div><pre class="screen"># chkconfig NetworkManager off
+# chkconfig network on
+# service NetworkManager stop
+# service network start</pre><div class="para">
+ If you do not want to disable <span class="application"><strong>NetworkManager</strong></span> entirely, add "<em class="parameter"><code>NM_CONTROLLED=no</code></em>" to the <code class="filename">ifcfg-*</code> network script being used for the bridge.
+ </div></div></div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 12. PCI device configuration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-AI_device_to_a_host">12.1. Assigning a PCI device with virsh</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host">12.2. Assigning a PCI device with virt-manager</a></span></dt><dt><span class="section"><a href="#idm113629632">12.3. PCI device assignment with virt-install</a></span></dt><dt><span class="section"><a href="#idm123828480">12.4. Detaching an assigned PCI device</a></span></dt></dl></div><div class="para">
+ Red Hat Enterprise Linux 6 exposes three classes of device to its virtual machines:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="firstterm">Emulated devices</em> are purely virtual devices that mimic real hardware, allowing unmodified guest operating systems to work with them using their standard in-box drivers.
+ </div></li><li class="listitem"><div class="para">
+ <em class="firstterm">Virtio devices</em> are purely virtual devices designed to work optimally in a virtual machine. Virtio devices are similar to emulated devices, however, non-Linux virtual machines do not include the drivers they require by default. Virtualization management software like the Virtual Machine Manager (<span class="application"><strong>virt-manager</strong></span>) and the Red Hat Enterprise Virtualization Hypervisor install these drivers automatically for supported non-Linux guest operating systems.
+ </div></li><li class="listitem"><div class="para">
+ <em class="firstterm">Assigned devices</em> are physical devices that are exposed to the virtual machine. This method is also known as 'passthrough'. Device assignment allows virtual machines exclusive access to PCI devices for a range of tasks, and allows PCI devices to appear and behave as if they were physically attached to the guest operating system.
+ </div><div class="para">
+ Device assignment is supported on PCI Express devices, except graphics cards. Parallel PCI devices may be supported as assigned devices, but they have severe limitations due to security and system configuration conflicts.
+ </div></li></ul></div><div class="para">
+ Red Hat Enterprise Linux 6 supports 32 PCI device slots per virtual machine, and 8 PCI functions per device slot. This gives a theoretical maximum of 256 configurable PCI functions per guest.
+ </div><div class="para">
+ However, this theoretical maximum is subject to the following limitations:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Each virtual machine supports a maximum of 8 assigned device functions.
+ </div></li><li class="listitem"><div class="para">
+ 4 PCI device slots are configured with emulated devices by default. However, users can explicitly remove 2 of the emulated devices that are configured by default (the video adapter device in slot 2, and the memory balloon driver device in slot 3). This gives users a supported functional maximum of 30 PCI device slots per virtual machine.
+ </div></li></ul></div><div class="para">
+ Red Hat Enterprise Linux 6.0 and newer supports hot plugging assigned PCI devices into virtual machines. However, PCI device hot plugging operates at the slot level and therefore does not support multi-function PCI devices. Multi-function PCI devices are recommended for static device configuration only.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Red Hat Enterprise Linux 6.0 limited guest operating system driver access to a device's standard and extended configuration space. Limitations that were present in Red Hat Enterprise Linux 6.0 are significantly reduced in Red Hat Enterprise Linux 6.1, and enable a much larger set of PCI Express devices to be successfully assigned to KVM guests.
+ </div></div></div><div class="para">
+ Secure device assignment also requires interrupt remapping support. If a platform does not support interrupt remapping, device assignment will fail. To use device assignment without interrupt remapping support in a development environment, set the <em class="parameter"><code>allow_unsafe_assigned_interrupts</code></em> KVM module parameter to <code class="literal">1</code>.
+ </div><div class="para">
+ PCI device assignment is only available on hardware platforms supporting either Intel VT-d or AMD IOMMU. These Intel VT-d or AMD IOMMU specifications must be enabled in BIOS for PCI device assignment to function.
+ </div><div class="procedure" id="intel-prep"><h6>Procedure 12.1. Preparing an Intel system for PCI device assignment</h6><ol class="1"><li class="step"><p class="title"><strong>Enable the Intel VT-d specifications</strong></p><div class="para">
+ The Intel VT-d specifications provide hardware support for directly assigning a physical device to a virtual machine. These specifications are required to use PCI device assignment with Red Hat Enterprise Linux.
+ </div><div class="para">
+ The Intel VT-d specifications must be enabled in the BIOS. Some system manufacturers disable these specifications by default. The terms used to refer to these specifications can differ between manufacturers; consult your system manufacturer's documentation for the appropriate terms.
+ </div></li><li class="step"><p class="title"><strong>Activate Intel VT-d in the kernel</strong></p><div class="para">
+ Activate Intel VT-d in the kernel by adding the <em class="parameter"><code>intel_iommu=on</code></em> parameter to the kernel line in the <code class="filename">/boot/grub/grub.conf</code> file.
+ </div><div class="para">
+ The example below is a modified <code class="filename">grub.conf</code> file with Intel VT-d activated.
+ </div><pre class="screen">default=0
+timeout=5
+splashimage=(hd0,0)/grub/splash.xpm.gz
+hiddenmenu
+title Red Hat Enterprise Linux Server (2.6.32-330.x86_645)
+ root (hd0,0)
+ kernel /vmlinuz-2.6.32-330.x86_64 ro root=/dev/VolGroup00/LogVol00 rhgb quiet <span class="bold bold"><strong>intel_iommu=on</strong></span>
+ initrd /initrd-2.6.32-330.x86_64.img</pre></li><li class="step"><p class="title"><strong>Ready to use</strong></p><div class="para">
+ Reboot the system to enable the changes. Your system is now capable of PCI device assignment.
+ </div></li></ol></div><div class="procedure" id="amd-prep"><h6>Procedure 12.2. Preparing an AMD system for PCI device assignment</h6><ol class="1"><li class="step"><p class="title"><strong>Enable the AMD IOMMU specifications</strong></p><div class="para">
+ The AMD IOMMU specifications are required to use PCI device assignment in Red Hat Enterprise Linux. These specifications must be enabled in the BIOS. Some system manufacturers disable these specifications by default.
+ </div></li><li class="step"><p class="title"><strong>Enable IOMMU kernel support</strong></p><div class="para">
+ Append <em class="parameter"><code>amd_iommu=on</code></em> to the kernel command line in <code class="filename">/boot/grub/grub.conf</code> so that AMD IOMMU specifications are enabled at boot.
+ </div></li></ol></div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-AI_device_to_a_host"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">12.1. Assigning a PCI device with virsh</h2></div></div></div><div class="para">
+ These steps cover assigning a PCI device to a virtual machine on a KVM hypervisor.
+ </div><div class="para">
+ This example uses a PCIe network controller with the PCI identifier code, <code class="computeroutput">pci_0000_01_00_0</code>, and a fully virtualized guest machine named <em class="replaceable"><code>guest1-F19</code></em>.
+ </div><div class="procedure"><h6>Procedure 12.3. Assigning a PCI device to a guest virtual machine with virsh</h6><ol class="1"><li class="step"><p class="title"><strong>Identify the device</strong></p><div class="para">
+ First, identify the PCI device designated for device assignment to the virtual machine. Use the <code class="command">lspci</code> command to list the available PCI devices. You can refine the output of <code class="command">lspci</code> with <code class="command">grep</code>.
+ </div><div class="para">
+ This example uses the Ethernet controller highlighted in the following output:
+ </div><pre class="screen"># lspci | grep Ethernet
+<span class="bold bold"><strong>00:19.0 Ethernet controller: Intel Corporation 82567LM-2 Gigabit Network Connection</strong></span>
+01:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
+01:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)</pre><div class="para">
+ This Ethernet controller is shown with the short identifier <code class="literal">00:19.0</code>. We need to find out the full identifier used by <code class="command">virsh</code> in order to assign this PCI device to a virtual machine.
+ </div><div class="para">
+ To do so, combine the <code class="command">virsh nodedev-list</code> command with the <code class="command">grep</code> command to list all devices of a particular type (<code class="literal">pci</code>) that are attached to the host machine. Then look at the output for the string that maps to the short identifier of the device you wish to use.
+ </div><div class="para">
+ This example highlights the string that maps to the Ethernet controller with the short identifier <code class="literal">00:19.0</code>. Note that the <code class="literal">:</code> and <code class="literal">.</code> characters are replaced with underscores in the full identifier.
+ </div><pre class="screen"># virsh nodedev-list --cap pci
+pci_0000_00_00_0
+pci_0000_00_01_0
+pci_0000_00_03_0
+pci_0000_00_07_0
+pci_0000_00_10_0
+pci_0000_00_10_1
+pci_0000_00_14_0
+pci_0000_00_14_1
+pci_0000_00_14_2
+pci_0000_00_14_3
+pci_0000_<span class="bold bold"><strong>00_19_0</strong></span>
+pci_0000_00_1a_0
+pci_0000_00_1a_1
+pci_0000_00_1a_2
+pci_0000_00_1a_7
+pci_0000_00_1b_0
+pci_0000_00_1c_0
+pci_0000_00_1c_1
+pci_0000_00_1c_4
+pci_0000_00_1d_0
+pci_0000_00_1d_1
+pci_0000_00_1d_2
+pci_0000_00_1d_7
+pci_0000_00_1e_0
+pci_0000_00_1f_0
+pci_0000_00_1f_2
+pci_0000_00_1f_3
+pci_0000_01_00_0
+pci_0000_01_00_1
+pci_0000_02_00_0
+pci_0000_02_00_1
+pci_0000_06_00_0
+pci_0000_07_02_0
+pci_0000_07_03_0</pre><div class="para">
+ Record the PCI device number that maps to the device you want to use; this is required in other steps.
+ </div></li><li class="step"><p class="title"><strong>Review device information</strong></p><div class="para">
+ Information on the domain, bus, and function are available from output of the <code class="command">virsh nodedev-dumpxml</code> command:
+ </div><pre class="screen">virsh nodedev-dumpxml pci_0000_00_19_0
+<device>
+ <name>pci_0000_00_19_0</name>
+ <parent>computer</parent>
+ <driver>
+ <name>e1000e</name>
+ </driver>
+ <capability type='pci'>
+ <domain>0</domain>
+ <bus>0</bus>
+ <slot>25</slot>
+ <function>0</function>
+ <product id='0x1502'>82579LM Gigabit Network Connection</product>
+ <vendor id='0x8086'>Intel Corporation</vendor>
+ <capability type='virt_functions'>
+ </capability>
+ </capability>
+</device></pre></li><li class="step"><p class="title"><strong>Determine required configuration details</strong></p><div class="para">
+ Refer to the output from the <code class="command">virsh nodedev-dumpxml pci_0000_00_19_0</code> command for the values required for the configuration file.
+ </div><div class="para">
+ Optionally, convert slot and function values to hexadecimal values (from decimal) to get the PCI bus addresses. Append "0x" to the beginning of the output to tell the computer that the value is a hexadecimal number.
+ </div><div class="para">
+ The example device has the following values: bus = 0, slot = 25 and function = 0. The decimal configuration uses those three values:
+ </div><pre class="screen">bus='0'
+slot='25'
+function='0'</pre><div class="para">
+ If you want to convert to hexadecimal values, you can use the <code class="command">printf</code> utility to convert from decimal values, as shown in the following example:
+ </div><pre class="screen">$ printf %x 0
+0
+$ printf %x 25
+19
+$ printf %x 0
+0</pre><div class="para">
+ The example device would use the following hexadecimal values in the configuration file:
+ </div><pre class="screen">bus='0x0'
+slot='0x19'
+function='0x0'</pre></li><li class="step"><p class="title"><strong>Add configuration details</strong></p><div class="para">
+ Run <code class="command">virsh edit</code>, specifying the virtual machine name, and add a device entry in the <code class="computeroutput"><source></code> section to assign the PCI device to the guest virtual machine.
+ </div><pre class="screen"># virsh edit <em class="replaceable"><code>guest1-F19</code></em>
+<hostdev mode='subsystem' type='pci' managed='yes'>
+ <source>
+ <address domain='0x0' bus='0x0' slot='0x19' function='0x0'/>
+ </source>
+</hostdev></pre><div class="para">
+ Alternately, run <code class="command">virsh attach-device</code>, specifying the virtual machine name and the guest's XML file:
+ </div><pre class="screen">virsh attach-device <em class="replaceable"><code>guest1-F19</code></em> <code class="filename">file.xml</code></pre></li><li class="step"><p class="title"><strong>Allow device management</strong></p><div class="para">
+ Set an SELinux boolean to allow the management of the PCI device from the virtual machine:
+ </div><pre class="screen"># setsebool -P virt_use_sysfs 1</pre></li><li class="step"><p class="title"><strong>Start the virtual machine</strong></p><pre class="screen"># virsh start <em class="replaceable"><code>guest1-F19</code></em></pre></li></ol></div><div class="para">
+ The PCI device should now be successfully assigned to the virtual machine, and accessible to the guest operating system.
+ </div></div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">12.2. Assigning a PCI device with virt-manager</h2></div></div></div><div class="para">
+ PCI devices can be added to guest virtual machines using the graphical <code class="command">virt-manager</code> tool. The following procedure adds a Gigabit Ethernet controller to a guest virtual machine.
+ </div><div class="procedure"><h6>Procedure 12.4. Assigning a PCI device to a guest virtual machine using virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Open the hardware settings</strong></p><div class="para">
+ Open the guest virtual machine and click the <span class="guibutton"><strong>Add Hardware</strong></span> button to add a new device to the virtual machine.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_hardware.png" width="444" alt="The virtual machine hardware window with the Information button selected on the top taskbar and Overview selected on the left menu pane." /></div></div><h6>Figure 12.1. The virtual machine hardware information window</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Select a PCI device</strong></p><div class="para">
+ Select <span class="application"><strong>PCI Host Device</strong></span> from the <span class="guilabel"><strong>Hardware</strong></span> list on the left.
+ </div><div class="para">
+ Select an unused PCI device. Note that selecting PCI devices presently in use on the host causes errors. In this example, a spare 82576 network device is used. Click <span class="guilabel"><strong>Finish</strong></span> to complete setup.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/3_PCI_Device.png" width="444" alt="The Add new virtual hardware wizard with PCI Host Device selected on the left menu pane, showing a list of host devices for selection in the right menu pane." /></div></div><h6>Figure 12.2. The Add new virtual hardware wizard</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Add the new device</strong></p><div class="para">
+ The setup is complete and the guest virtual machine now has direct access to the PCI device.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/pci_host_device.png" width="444" alt="The virtual machine hardware window with the Information button selected on the top taskbar and Overview selected on the left menu pane, displaying the newly added PCI Device in the list of virtual machine devices in the left menu pane." /></div></div><h6>Figure 12.3. The virtual machine hardware information window</h6></div><br class="figure-break" /></li></ol></div></div><div class="section" id="idm113629632"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm113629632">12.3. PCI device assignment with virt-install</h2></div></div></div><div class="para">
+ To use <span class="application"><strong>virt-install</strong></span> to assign a PCI device, use the <em class="parameter"><code>--host-device</code></em> parameter.
+ </div><div class="procedure"><h6>Procedure 12.5. Assigning a PCI device to a virtual machine with virt-install</h6><ol class="1"><li class="step"><p class="title"><strong>Identify the device</strong></p><div class="para">
+ Identify the PCI device designated for device assignment to the guest virtual machine.
+ </div><pre class="screen"># lspci | grep Ethernet
+00:19.0 Ethernet controller: Intel Corporation 82567LM-2 Gigabit Network Connection
+01:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
+01:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)</pre><div class="para">
+ The <code class="command">virsh nodedev-list</code> command lists all devices attached to the system, and identifies each PCI device with a string. To limit output to only PCI devices, run the following command:
+ </div><pre class="screen"># virsh nodedev-list --cap pci
+pci_0000_00_00_0
+pci_0000_00_01_0
+pci_0000_00_03_0
+pci_0000_00_07_0
+pci_0000_00_10_0
+pci_0000_00_10_1
+pci_0000_00_14_0
+pci_0000_00_14_1
+pci_0000_00_14_2
+pci_0000_00_14_3
+pci_0000_00_19_0
+pci_0000_00_1a_0
+pci_0000_00_1a_1
+pci_0000_00_1a_2
+pci_0000_00_1a_7
+pci_0000_00_1b_0
+pci_0000_00_1c_0
+pci_0000_00_1c_1
+pci_0000_00_1c_4
+pci_0000_00_1d_0
+pci_0000_00_1d_1
+pci_0000_00_1d_2
+pci_0000_00_1d_7
+pci_0000_00_1e_0
+pci_0000_00_1f_0
+pci_0000_00_1f_2
+pci_0000_00_1f_3
+pci_0000_01_00_0
+pci_0000_01_00_1
+pci_0000_02_00_0
+pci_0000_02_00_1
+pci_0000_06_00_0
+pci_0000_07_02_0
+pci_0000_07_03_0</pre><div class="para">
+ Record the PCI device number; the number is needed in other steps.
+ </div><div class="para">
+ Information on the domain, bus and function are available from output of the <code class="command">virsh nodedev-dumpxml</code> command:
+ </div><pre class="screen"># virsh nodedev-dumpxml pci_0000_01_00_0
+<device>
+ <name>pci_0000_01_00_0</name>
+ <parent>pci_0000_00_01_0</parent>
+ <driver>
+ <name>igb</name>
+ </driver>
+ <capability type='pci'>
+ <domain>0</domain>
+ <bus>1</bus>
+ <slot>0</slot>
+ <function>0</function>
+ <product id='0x10c9'>82576 Gigabit Network Connection</product>
+ <vendor id='0x8086'>Intel Corporation</vendor>
+ <capability type='virt_functions'>
+ </capability>
+ </capability>
+</device></pre></li><li class="step"><p class="title"><strong>Add the device</strong></p><div class="para">
+ Use the PCI identifier output from the <code class="command">virsh nodedev</code> command as the value for the <em class="parameter"><code>--host-device</code></em> parameter.
+ </div><pre class="screen">virt-install \
+--name=guest1-F19 \
+--disk path=/var/lib/libvirt/images/guest1-F19.img,size=8 \
+--nonsparse --graphics spice \
+--vcpus=2 --ram=2048 \
+--location=http://example1.com/installation_tree/f19-Server-x86_64/os \
+--nonetworks \
+--os-type=linux \
+--os-variant=fedora
+--host-device=<span class="emphasis"><em>pci_0000_01_00_0</em></span></pre></li><li class="step"><p class="title"><strong>Complete the installation</strong></p><div class="para">
+ Complete the guest installation. The PCI device should be attached to the guest.
+ </div></li></ol></div></div><div class="section" id="idm123828480"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm123828480">12.4. Detaching an assigned PCI device</h2></div></div></div><div class="para">
+ When a host PCI device has been assigned to a guest machine, the host can no longer use the device. Read this section to learn how to detach the device from the guest with <code class="command">virsh</code> or <span class="application"><strong>virt-manager</strong></span> so it is available for host use.
+ </div><div class="procedure"><h6>Procedure 12.6. Detaching a PCI device from a guest with virsh</h6><ol class="1"><li class="step"><p class="title"><strong>Detach the device</strong></p><div class="para">
+ Use the following command to detach the PCI device from the guest by removing it in the guest's XML file:
+ </div><pre class="screen"># virsh detach-device <em class="replaceable"><code>name_of_guest</code></em> <em class="replaceable"><code>file.xml</code></em></pre></li><li class="step"><p class="title"><strong>Re-attach the device to the host (optional)</strong></p><div class="para">
+ If the device is in <em class="parameter"><code>managed</code></em> mode, skip this step. The device will be returned to the host automatically.
+ </div><div class="para">
+ If the device is not using <em class="parameter"><code>managed</code></em> mode, use the following command to re-attach the PCI device to the host machine:
+ </div><pre class="screen"># virsh nodedev-reattach <em class="replaceable"><code>device</code></em></pre><div class="para">
+ For example, to re-attach the <code class="literal">pci_0000_01_00_0</code> device to the host:
+ </div><pre class="screen">virsh nodedev-reattach pci_0000_01_00_0</pre><div class="para">
+ The device is now available for host use.
+ </div></li></ol></div><div class="procedure"><h6>Procedure 12.7. Detaching a PCI Device from a guest with virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Open the virtual hardware details screen</strong></p><div class="para">
+ In <span class="application"><strong>virt-manager</strong></span>, double-click on the virtual machine that contains the device. Select the <span class="guilabel"><strong>Show virtual hardware details</strong></span> button to display a list of virtual hardware.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/vm_info_button_new.png" alt="The Show virtual hardware details button." /></div></div><h6>Figure 12.4. The virtual hardware details button</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Select and remove the device</strong></p><div class="para">
+ Select the PCI device to be detached from the list of virtual devices in the left panel.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/PCIremoval.png" width="444" alt="The PCI device details and the Remove button." /></div></div><h6>Figure 12.5. Selecting the PCI device to be detached</h6></div><br class="figure-break" /><div class="para">
+ Click the <span class="guibutton"><strong>Remove</strong></span> button to confirm. The device is now available for host use.
+ </div></li></ol></div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 13. SR-IOV</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#idm96737120">13.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works">13.2. Using SR-IOV</a></span></dt><dt><span class="section"><a href="#idm98028304">13.3. Troubleshooting SR-IOV</a></span></dt></dl></div><div class="section" id="idm96737120"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm96737120">13.1. Introduction</h2></div></div></div><div class="para">
+ Developed by the PCI-SIG (PCI Special Interest Group), the Single Root I/O Virtualization (SR-IOV) specification is a standard for a type of PCI device assignment that can share a single device to multiple virtual machines. SR-IOV improves device performance for virtual machines.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/SR-IOV_implementation_2.png" width="444" alt="How SR-IOV works" /></div></div><h6>Figure 13.1. How SR-IOV works</h6></div><br class="figure-break" /><div class="para">
+ SR-IOV enables a Single Root Function (for example, a single Ethernet port), to appear as multiple, separate, physical devices. A physical device with SR-IOV capabilities can be configured to appear in the PCI configuration space as multiple functions. Each device has its own configuration space complete with Base Address Registers (BARs).
+ </div><div class="para">
+ SR-IOV uses two PCI functions:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Physical Functions (PFs) are full PCIe devices that include the SR-IOV capabilities. Physical Functions are discovered, managed, and configured as normal PCI devices. Physical Functions configure and manage the SR-IOV functionality by assigning Virtual Functions.
+ </div></li><li class="listitem"><div class="para">
+ Virtual Functions (VFs) are simple PCIe functions that only process I/O. Each Virtual Function is derived from a Physical Function. The number of Virtual Functions a device may have is limited by the device hardware. A single Ethernet port, the Physical Device, may map to many Virtual Functions that can be shared to virtual machines.
+ </div></li></ul></div><div class="para">
+ The hypervisor can map one or more Virtual Functions to a virtual machine. The Virtual Function's configuration space is then mapped to the configuration space presented to the guest.
+ </div><div class="para">
+ Each Virtual Function can only be mapped to a single guest at a time, as Virtual Functions require real hardware resources. A virtual machine can have multiple Virtual Functions. A Virtual Function appears as a network card in the same way as a normal network card would appear to an operating system.
+ </div><div class="para">
+ The SR-IOV drivers are implemented in the kernel. The core implementation is contained in the PCI subsystem, but there must also be driver support for both the Physical Function (PF) and Virtual Function (VF) devices. An SR-IOV capable device can allocate VFs from a PF. The VFs appear as PCI devices which are backed on the physical PCI device by resources such as queues and register sets.
+ </div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-Libvirt_Strengths"><h5 class="formalpara">Advantages of SR-IOV</h5>
+ SR-IOV devices can share a single physical port with multiple virtual machines.
+ </div><div class="para">
+ Virtual Functions have near-native performance and provide better performance than para-virtualized drivers and emulated access. Virtual Functions provide data protection between virtual machines on the same physical server as the data is managed and controlled by the hardware.
+ </div><div class="para">
+ These features allow for increased virtual machine density on hosts within a data center.
+ </div><div class="para">
+ SR-IOV is better able to utilize the bandwidth of devices with multiple guests.
+ </div></div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">13.2. Using SR-IOV</h2></div></div></div><div class="para">
+ This section covers the use of PCI passthrough to assign a Virtual Function of an SR-IOV capable multiport network card to a virtual machine as a network device.
+ </div><div class="para">
+ SR-IOV Virtual Functions (VFs) can be assigned to virtual machines by adding a device entry in <em class="parameter"><code><hostdev></code></em> with the <code class="command">virsh edit</code> or <code class="command">virsh attach-device</code> command. However, this can be problematic because unlike a regular network device, an SR-IOV VF network device does not have a permanent unique MAC address, and is assigned a new MAC address each time the host is rebooted. Because of this, even if the guest is assigned the same VF after a reboot, when the host is rebooted the guest determines its network adapter to have a new MAC address. As a result, the guest believes there is new hardware connected each time, and will usually require re-configuration of the guest's network settings.
+ </div><div class="para">
+ <span class="package">libvirt-0.9.10</span> and newer contains the <em class="parameter"><code><interface type='hostdev'></code></em> interface device. Using this interface device, <span class="application"><strong>libvirt</strong></span> will first perform any network-specific hardware/switch initialization indicated (such as setting the MAC address, VLAN tag, or 802.1Qbh virtualport parameters), then perform the PCI device assignment to the guest.
+ </div><div class="para">
+ Using the <em class="parameter"><code><interface type='hostdev'></code></em> interface device requires:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ an SR-IOV-capable network card,
+ </div></li><li class="listitem"><div class="para">
+ host hardware that supports either the Intel VT-d or the AMD IOMMU extensions, and
+ </div></li><li class="listitem"><div class="para">
+ the PCI address of the VF to be assigned.
+ </div></li></ul></div>
+
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Assignment of an SR-IOV device to a virtual machine requires that the host hardware supports the Intel VT-d or the AMD IOMMU specification.
+ </div></div></div><div class="para">
+ To attach an SR-IOV network device on an Intel or an AMD system, follow this procedure:
+ </div><div class="procedure"><h6>Procedure 13.1. Attach an SR-IOV network device on an Intel or AMD system</h6><ol class="1"><li class="step"><p class="title"><strong>Enable Intel VT-d or the AMD IOMMU specifications in the BIOS and kernel</strong></p><div class="para">
+ On an Intel system, enable Intel VT-d in the BIOS if it is not enabled already. Refer to <a class="xref" href="#intel-prep">Procedure 12.1, “Preparing an Intel system for PCI device assignment”</a> for procedural help on enabling Intel VT-d in the BIOS and kernel.
+ </div><div class="para">
+ Skip this step if Intel VT-d is already enabled and working.
+ </div><div class="para">
+ On an AMD system, enable the AMD IOMMU specifications in the BIOS if they are not enabled already. Refer to <a class="xref" href="#amd-prep">Procedure 12.2, “Preparing an AMD system for PCI device assignment”</a> for procedural help on enabling IOMMU in the BIOS.
+ </div></li><li class="step"><p class="title"><strong>Verify support</strong></p><div class="para">
+ Verify if the PCI device with SR-IOV capabilities is detected. This example lists an Intel 82576 network interface card which supports SR-IOV. Use the <code class="command">lspci</code> command to verify whether the device was detected.
+ </div><pre class="screen"># lspci
+03:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
+03:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)</pre><div class="para">
+ Note that the output has been modified to remove all other devices.
+ </div></li><li class="step"><p class="title"><strong>Start the SR-IOV kernel modules</strong></p><div class="para">
+ If the device is supported the driver kernel module should be loaded automatically by the kernel. Optional parameters can be passed to the module using the <code class="command">modprobe</code> command. The Intel 82576 network interface card uses the <code class="command">igb</code> driver kernel module.
+ </div><pre class="screen"># modprobe igb [<option>=<VAL1>,<VAL2>,]
+# lsmod |grep igb
+igb 87592 0
+dca 6708 1 igb</pre></li><li class="step"><p class="title"><strong>Activate Virtual Functions</strong></p><div class="para">
+ The <em class="parameter"><code>max_vfs</code></em> parameter of the <code class="command">igb</code> module allocates the maximum number of Virtual Functions. The <em class="parameter"><code>max_vfs</code></em> parameter causes the driver to spawn, up to the value of the parameter in, Virtual Functions. For this particular card the valid range is <em class="parameter"><code>0</code></em> to <em class="parameter"><code>7</code></em>.
+ </div><div class="para">
+ Remove the module to change the variable.
+ </div><pre class="screen"># modprobe -r igb</pre><div class="para">
+ Restart the module with the <em class="parameter"><code>max_vfs</code></em> set to <em class="parameter"><code>7</code></em> or any number of Virtual Functions up to the maximum supported by your device.
+ </div><pre class="screen"># modprobe igb max_vfs=7</pre></li><li class="step"><p class="title"><strong>Make the Virtual Functions persistent</strong></p><div class="para">
+ Add the line <code class="option">options igb max_vfs=7</code> to any file in <code class="filename">/etc/modprobe.d</code> to make the Virtual Functions persistent. For example:
+ </div><pre class="screen"># echo "options igb max_vfs=7" >>/etc/modprobe.d/igb.conf</pre></li><li class="step"><p class="title"><strong>Inspect the new Virtual Functions</strong></p><div class="para">
+ Using the <code class="command">lspci</code> command, list the newly added Virtual Functions attached to the Intel 82576 network device. (Alternatively, use <code class="command">grep</code> to search for <code class="literal">Virtual Function</code>, to search for devices that support Virtual Functions.)
+ </div><pre class="screen"># lspci | grep 82576
+0b:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
+0b:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
+0b:10.0 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.1 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.2 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.3 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.4 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.5 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.6 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.7 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:11.0 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:11.1 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:11.2 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:11.3 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:11.4 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:11.5 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)</pre><div class="para">
+ The identifier for the PCI device is found with the <em class="parameter"><code>-n</code></em> parameter of the <code class="command">lspci</code> command. The Physical Functions correspond to <code class="computeroutput">0b:00.0</code> and <code class="computeroutput">0b:00.1</code>. All Virtual Functions have <code class="computeroutput">Virtual Function</code> in the description.
+ </div></li><li class="step"><p class="title"><strong>Verify devices exist with virsh</strong></p><div class="para">
+ The <code class="systemitem">libvirt</code> service must recognize the device before adding a device to a virtual machine. <code class="systemitem">libvirt</code> uses a similar notation to the <code class="command">lspci</code> output. All punctuation characters, <span class="keycap"><strong>;</strong></span> and <span class="keycap"><strong>.</strong></span>, in <code class="command">lspci</code> output are changed to underscores (<span class="keycap"><strong>_</strong></span>).
+ </div><div class="para">
+ Use the <code class="command">virsh nodedev-list</code> command and the <code class="command">grep</code> command to filter the Intel 82576 network device from the list of available host devices. <em class="parameter"><code>0b</code></em> is the filter for the Intel 82576 network devices in this example. This may vary for your system and may result in additional devices.
+ </div><pre class="screen"># virsh nodedev-list | grep <em class="parameter"><code>0b</code></em>
+pci_0000_0b_00_0
+pci_0000_0b_00_1
+pci_0000_0b_10_0
+pci_0000_0b_10_1
+pci_0000_0b_10_2
+pci_0000_0b_10_3
+pci_0000_0b_10_4
+pci_0000_0b_10_5
+pci_0000_0b_10_6
+pci_0000_0b_11_7
+pci_0000_0b_11_1
+pci_0000_0b_11_2
+pci_0000_0b_11_3
+pci_0000_0b_11_4
+pci_0000_0b_11_5</pre><div class="para">
+ The serial numbers for the Virtual Functions and Physical Functions should be in the list.
+ </div></li><li class="step"><p class="title"><strong>Get device details with virsh</strong></p><div class="para">
+ The <code class="computeroutput">pci_0000_0b_00_0</code> is one of the Physical Functions and <code class="computeroutput">pci_0000_0b_10_0</code> is the first corresponding Virtual Function for that Physical Function. Use the <code class="command">virsh nodedev-dumpxml</code> command to get advanced output for both devices.
+ </div><pre class="screen"># virsh nodedev-dumpxml pci_0000_0b_00_0
+<device>
+ <name>pci_0000_0b_00_0</name>
+ <parent>pci_0000_00_01_0</parent>
+ <driver>
+ <name>igb</name>
+ </driver>
+ <capability type='pci'>
+ <domain>0</domain>
+ <bus>11</bus>
+ <slot>0</slot>
+ <function>0</function>
+ <product id='0x10c9'>Intel Corporation</product>
+ <vendor id='0x8086'>82576 Gigabit Network Connection</vendor>
+ </capability>
+</device></pre><pre class="screen"># virsh nodedev-dumpxml pci_0000_0b_10_0
+<device>
+ <name>pci_0000_0b_10_0</name>
+ <parent>pci_0000_00_01_0</parent>
+ <driver>
+ <name>igbvf</name>
+ </driver>
+ <capability type='pci'>
+ <domain>0</domain>
+ <bus>11</bus>
+ <slot>16</slot>
+ <function>0</function>
+ <product id='0x10ca'>Intel Corporation</product>
+ <vendor id='0x8086'>82576 Virtual Function</vendor>
+ </capability>
+</device></pre><div class="para">
+ This example adds the Virtual Function <code class="systemitem">pci_0000_0b_10_0</code> to the virtual machine in <a class="xref" href="#step9">Step 9</a>. Note the <code class="computeroutput">bus</code>, <code class="computeroutput">slot</code> and <code class="computeroutput">function</code> parameters of the Virtual Function: these are required for adding the device.
+ </div><div class="para">
+ Copy these parameters into a temporary XML file, such as <code class="filename">/tmp/new-interface.xml</code> for example.
+ </div><pre class="programlisting">
+ <interface type='hostdev' managed='yes'>
+ <source>
+ <address type='pci' domain='0' bus='11' slot='16' function='0'/>
+ </source>
+ </interface></pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If you do not specify a MAC address, one will be automatically generated. The <em class="parameter"><code><virtualport></code></em> element is only used when connecting to an 802.11Qbh hardware switch. The <em class="parameter"><code><vlan></code></em> element was introduced for Fedora 18 and this will transparently put the guest's device on the VLAN tagged <em class="parameter"><code>42</code></em>.
+ </div><div class="para">
+ When the virtual machine starts, it should see a network device of the type provided by the physical adapter, with the configured MAC address. This MAC address will remain unchanged across host and guest reboots.
+ </div><div class="para">
+ The following <em class="parameter"><code><interface></code></em> example shows the syntax for the optional <em class="parameter"><code><mac address></code></em>, <em class="parameter"><code><virtualport></code></em>, and <em class="parameter"><code><vlan></code></em> elements. In practice, use either the <em class="parameter"><code><vlan></code></em> or <em class="parameter"><code><virtualport></code></em> element, not both simultaneously as shown in the example:
+ </div><pre class="programlisting">...
+ <devices>
+ ...
+ <interface type='hostdev' managed='yes'>
+ <source>
+ <address type='pci' domain='0' bus='11' slot='16' function='0'/>
+ </source>
+ <mac address='52:54:00:6d:90:02'>
+ <vlan>
+ <tag id='42'/>
+ </vlan>
+ <virtualport type='802.1Qbh'>
+ <parameters profileid='finance'/>
+ </virtualport>
+ </interface>
+ ...
+ </devices></pre></div></div></li><li class="step" id="step9"><p class="title"><strong>Add the Virtual Function to the virtual machine</strong></p><div class="para">
+ Add the Virtual Function to the virtual machine using the following command with the temporary file created in the previous step. This attaches the new device immediately and saves it for subsequent guest restarts.
+ </div><pre class="screen">
+virsh attach-device <em class="replaceable"><code>MyGuest</code></em> <code class="filename">/tmp/new-interface.xml</code> --live --config
+</pre><div class="para">
+ Specifying the <code class="option">--live</code> option with <code class="command">virsh attach-device</code> attaches the new device to the running guest. Using the <code class="option">--config</code> option ensures the new device is available after future guest restarts.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The <code class="option">--live</code> option is only accepted when the guest is running. <code class="command">virsh</code> will return an error if the <code class="option">--live</code> option is used on a non-running guest.
+ </div></div></div></li></ol></div><div class="para">
+ The virtual machine detects a new network interface card. This new card is the Virtual Function of the SR-IOV device.
+ </div></div><div class="section" id="idm98028304"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm98028304">13.3. Troubleshooting SR-IOV</h2></div></div></div><div class="para">
+ This section contains solutions for problems which may affect SR-IOV.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Error starting the guest</span></dt><dd><div class="para">
+ When starting a configured virtual machine, an error occurs as follows:
+ </div><pre class="screen"># virsh start test
+error: Failed to start domain test
+error: internal error unable to start guest: char device redirected to
+/dev/pts/2
+get_real_device: /sys/bus/pci/devices/0000:03:10.0/config: Permission denied
+init_assigned_device: Error: Couldn't get real device (03:10.0)!
+Failed to initialize assigned device host=03:10.0</pre><div class="para">
+ This error is often caused by a device that is already assigned to another guest or to the host itself.
+ </div></dd><dt class="varlistentry"><span class="term">Error migrating, saving, or dumping the guest</span></dt><dd><div class="para">
+ Attempts to migrate and dump the virtual machine cause an error similar to the following:
+ </div><pre class="screen"># virsh dump --crash 5 /tmp/vmcore
+error: Failed to core dump domain 5 to /tmp/vmcore
+error: internal error unable to execute QEMU command 'migrate': An undefined
+error has occurred</pre><div class="para">
+ Because device assignment uses hardware on the specific host where the virtual machine was started, guest migration and save are not supported when device assignment is in use. Currently, the same limitation also applies to core-dumping a guest; this may change in the future.
+ </div></dd></dl></div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 14. KVM guest timing management</h2></div></div></div><div class="para">
+ Virtualization involves several intrinsic challenges for time keeping in guest virtual machines. Interrupts cannot always be delivered simultaneously and instantaneously to all guest virtual machines, because interrupts in virtual machines are not true interrupts; they are injected into the guest virtual machine by the host machine. The host may be running another guest virtual machine, or a different process, meaning that the precise timing typically required by interrupts may not always be possible.
+ </div><div class="para">
+ Guest virtual machines without accurate time keeping may experience issues with network applications and processes, as session validity, migration, and other network activities rely on timestamps to remain correct.
+ </div><div class="para">
+ KVM avoids these issues by providing guest virtual machines with a para-virtualized clock (<span class="application"><strong>kvm-clock</strong></span>). However, it is still vital to test timing before attempting activities that may be affected by time keeping inaccuracies.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Fedora 17 and newer, uses <span class="application"><strong>kvm-clock</strong></span> as their default clock source. Running without <span class="application"><strong>kvm-clock</strong></span> requires special configuration, and is not recommended.
+ </div></div></div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The Network Time Protocol (NTP) daemon should be running on the host and the guest virtual machines. 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">
+ The <code class="systemitem">ntpd</code> service will correct the effects of clock skew as long as the clock runs no more than 0.05% faster or slower than the reference time source. The <code class="systemitem">ntp</code> startup script adjusts the clock offset from the reference time by adjusting the system clock at startup time, if required.
+ </div></div></div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management-Determining_if_your_CPU_has_the_constant_Time_Stamp_Counter"><h5 class="formalpara">Constant Time Stamp Counter (TSC)</h5>
+ Modern Intel and AMD CPUs provide a constant Time Stamp Counter (TSC). The count frequency of the constant TSC does not vary when the CPU core itself changes frequency, for example, to comply with a power saving policy. A CPU with a constant TSC frequency is necessary in order to use the TSC as a clock source for KVM guests.
+ </div><div class="para">
+ 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" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management-Configuring_hosts_without_a_constant_Time_Stamp_Counter"><h5 class="formalpara">Configuring hosts without a constant Time Stamp Counter</h5>
+ Systems without a constant TSC frequency cannot use the TSC as a clock source for virtual machines, and require additional configuration. Power management features interfere with accurate time keeping and must be disabled for guest virtual machines to accurately keep time with KVM.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ These instructions are for AMD revision F CPUs only.
+ </div></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. Deep C sleep states can stop the TSC. To prevent the kernel using deep C states append <code class="command">processor.max_cstate=1</code> to the kernel boot options in the <code class="filename">grub.conf</code> file on the host:
+ </div><pre class="screen">title Fedora (2.6.32-330.x86_64)
+ root (hd0,0)
+ kernel /vmlinuz-2.6.32-330.x86_64 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" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management-Required_parameters_for_RHEL_guests"><h5 class="formalpara">Required parameters for Fedora Linux guests</h5>
+ For certain Fedroa guest virtual machines, additional kernel parameters are required. These parameters can be set by appending them to the end of the <code class="literal">/kernel</code> line in the <code class="filename">/boot/grub/grub.conf</code> file of the guest virtual machine.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The <em class="parameter"><code>lpj</code></em> parameter requires a numeric value equal to the <span class="emphasis"><em>loops per jiffy</em></span> value of the specific CPU on which the guest virtual machine runs. If you do not know this value, do not set the <em class="parameter"><code>lpj</code></em> parameter.
+ </div></div></div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ The <em class="parameter"><code>divider</code></em> kernel parameter was previously recommended for Fedora guest virtual machines that did not have high responsiveness requirements, or exist on systems with high guest density. It is no longer recommended for use with guests running Fedora versions prior to version 16.
+ </div></div></div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management-KVM_guest_timing_management-Using_the_Real_Time_Clock_with_Windows_guests"><h5 class="formalpara">Using the Real-Time Clock with Windows Server 2003 and Windows XP guests</h5>
+ Windows uses the both the Real-Time Clock (RTC) and the Time Stamp Counter (TSC). For Windows guest virtual machines the Real-Time Clock can be used instead of the TSC for all time sources which resolves guest timing issues.
+ </div><div class="para">
+ To enable the Real-Time Clock for the <code class="computeroutput">PMTIMER</code> clock source (the <code class="computeroutput">PMTIMER</code> usually uses the TSC), add the following option to the Windows boot settings. Windows boot settings are stored in the boot.ini file. Add the following option to the end of the Windows boot line in the <code class="filename">boot.ini</code> file:
+ </div><pre class="screen">/usepmtimer
+</pre><div class="para">
+ For more information on Windows boot settings and the usepmtimer 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 class="formalpara"><h5 class="formalpara" id="idm41630944">Using the Real-Time Clock with Windows Server 2008, Windows Server 2008 R2, and Windows 7 guests</h5>
+ Windows uses the both the Real-Time Clock (RTC) and the Time Stamp Counter (TSC). For Windows guest virtual machines the Real-Time Clock can be used instead of the TSC for all time sources, which resolves guest timing issues.
+ </div><div class="para">
+ The <code class="filename">boot.ini</code> file is no longer used as of Windows Server 2008 and newer. Windows Server 2008, Windows Server 2008 R2, and Windows 7 do not use the TSC as a time source if the <code class="literal">hypervisor-present</code> bit is set. The Fedora KVM hypervisor enables this CPUID bit by default, so it is no longer necessary to use the <span class="application"><strong>Boot Configuration Data Editor</strong></span> (<code class="command">bcdedit.exe</code>) to modify the Windows boot parameters.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Open the Windows guest virtual machine.
+ </div></li><li class="step"><div class="para">
+ Open the <span class="guimenuitem"><strong>Accessories</strong></span> menu of the <span class="guimenuitem"><strong>start</strong></span> menu. Right click on the <span class="application"><strong>Command Prompt</strong></span> application, select <span class="guilabel"><strong>Run as Administrator</strong></span>.
+ </div></li><li class="step"><div class="para">
+ Confirm the security exception, if prompted.
+ </div></li><li class="step"><div class="para">
+ Set the boot manager to use the platform clock. This should instruct Windows to use the PM timer for the primary clock source. The system UUID (<em class="parameter"><code>{default}</code></em> in the example below) should be changed if the system UUID is different than the default boot device.
+ </div><pre class="screen">C:\Windows\system32>bcdedit /set {default} USEPLATFORMCLOCK on
+The operation completed successfully</pre></li></ol></div><div class="para">
+ This fix should improve time keeping for Windows Server 2008 and Windows 7 guests.
+ </div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management-Steal_Time_Accounting"><h5 class="formalpara">Steal time accounting</h5>
+ Steal time is the amount of CPU time desired by a guest virtual machine that is not provided by the host. Steal time occurs when the host allocates these resources elsewhere: for example, to another guest.
+ </div><div class="para">
+ Steal time is reported in the CPU time fields in <code class="filename">/proc/stat</code> as <em class="parameter"><code>st</code></em>. It is automatically reported by utilities such as <code class="command">top</code> and <code class="command">vmstat</code>, and cannot be switched off.
+ </div><div class="para">
+ Large amounts of steal time indicate CPU contention, which can reduce guest performance. To relieve CPU contention, increase the guest's CPU priority or CPU quota, or run fewer guests on the host.
+ </div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 15. Network booting with libvirt</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#idm104740480">15.1. Preparing the boot server</a></span></dt><dd><dl><dt><span class="section"><a href="#idm120289520">15.1.1. Setting up a PXE boot server on a private libvirt network</a></span></dt></dl></dd><dt><span class="section"><a href="#idm79200128">15.2. Booting a guest using PXE</a></span></dt><dd><dl><dt><span class="section"><a href="#idm108221824">15.2.1. Using bridged networking</a></span></dt><dt><span class="section"><a href="#idm94661024">15.2.2. Using a private libvirt network</a></span></dt></dl></dd></dl></div><div class="para">
+ Guest virtual machines can be booted with PXE enabled. PXE allows guest virtual machines to boot and load their configuration off the network itself. This section demonstrates some basic configuration steps to configure PXE guests with libvirt.
+ </div><div class="para">
+ This section does not cover the creation of boot images or PXE servers. It is used to explain how to configure libvirt, in a private or bridged network, to boot a guest virtual machine with PXE booting enabled.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ These procedures are provided only as an example. Ensure that you have sufficient backups before proceeding.
+ </div></div></div><div class="section" id="idm104740480"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm104740480">15.1. Preparing the boot server</h2></div></div></div><div class="para">
+ To perform the steps in this chapter you will need:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ A PXE Server (DHCP and TFTP) - This can be a libvirt internal server, manually-configured dhcpd and tftpd, dnsmasq, a server configured by Cobbler, or some other server.
+ </div></li><li class="listitem"><div class="para">
+ Boot images - for example, PXELINUX configured manually or by Cobbler.
+ </div></li></ul></div><div class="section" id="idm120289520"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm120289520">15.1.1. Setting up a PXE boot server on a private libvirt network</h3></div></div></div><div class="para">
+ This example uses the <span class="emphasis"><em>default</em></span> network. Perform the following steps:
+ </div><div class="procedure"><h6>Procedure 15.1. Configuring the PXE boot server</h6><ol class="1"><li class="step"><div class="para">
+ Place the PXE boot images and configuration in <code class="filename">/var/lib/tftp</code>.
+ </div></li><li class="step"><div class="para">
+ Run the following commands:
+ </div><pre class="screen"># virsh net-destroy default
+# virsh net-edit default</pre></li><li class="step"><div class="para">
+ Edit the <code class="code"><ip></code> element in the configuration file for the <span class="emphasis"><em>default</em></span> network to include the appropriate address, network mask, DHCP address range, and boot file, where <em class="replaceable"><code>BOOT_FILENAME</code></em> represents the file name you are using to boot the guest virtual machine.
+ </div><pre class="screen"><ip address='192.168.122.1' netmask='255.255.255.0'>
+ <tftp root='/var/lib/tftp' />
+ <dhcp>
+ <range start='192.168.122.2' end='192.168.122.254' />
+ <bootp file='<em class="replaceable"><code>BOOT_FILENAME</code></em>' />
+ </dhcp>
+</ip></pre></li><li class="step"><div class="para">
+ Boot the guest using PXE (refer to <a class="xref" href="#booting-guest-with-pxe">Section 15.2, “Booting a guest using PXE”</a>).
+ </div></li></ol></div></div></div><div class="section" id="idm79200128"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm79200128">15.2. Booting a guest using PXE</h2></div></div></div><div class="para">
+ This section demonstrates how to boot a guest virtual machine with PXE.
+ </div><div class="section" id="idm108221824"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm108221824">15.2.1. Using bridged networking</h3></div></div></div><div class="procedure"><h6>Procedure 15.2. Booting a guest using PXE and bridged networking</h6><ol class="1"><li class="step"><div class="para">
+ Ensure bridging is enabled such that the PXE boot server is available on the network.
+ </div></li><li class="step"><div class="para">
+ Boot a guest virtual machine with PXE booting enabled. You can use the <code class="command">virt-install</code> command to create a new virtual machine with PXE booting enabled, as shown in the following example command:
+ </div><pre class="screen">virt-install --pxe --network bridge=breth0 --prompt</pre><div class="para">
+ Alternatively, ensure that the guest network is configured to use your bridged network, and that the XML guest configuration file has a <code class="code"><boot dev='network'/></code> element inside the <code class="code"><os></code> element, as shown in the following example:
+ </div><pre class="screen"><os>
+ <type arch='x86_64' machine='rhel6.2.0'>hvm</type>
+ <boot dev='network'/>
+ <boot dev='hd'/>
+</os>
+<interface type='bridge'>
+ <mac address='52:54:00:5a:ad:cb'/>
+ <source bridge='breth0'/>
+ <target dev='vnet0'/>
+ <alias name='net0'/>
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
+</interface></pre></li></ol></div></div><div class="section" id="idm94661024"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm94661024">15.2.2. Using a private libvirt network</h3></div></div></div><div class="procedure"><h6>Procedure 15.3. Using a private libvirt network</h6><ol class="1"><li class="step"><div class="para">
+ Configure PXE booting on libvirt as shown in <a class="xref" href="#setting-up-server-private">Section 15.1.1, “Setting up a PXE boot server on a private libvirt network”</a>.
+ </div></li><li class="step"><div class="para">
+ Boot a guest virtual machine using libvirt with PXE booting enabled. You can use the <code class="command">virt-install</code> command to create/install a new virtual machine using PXE:
+ </div><pre class="screen">virt-install --pxe --network network=default --prompt</pre></li></ol></div><div class="para">
+ Alternatively, ensure that the guest network is configured to use your bridged network, and that the XML guest configuration file has a <code class="code"><boot dev='network'/></code> element inside the <code class="code"><os></code> element, as shown in the following example:
+ </div><pre class="screen"><os>
+ <type arch='x86_64' machine='rhel6.2.0'>hvm</type>
+ <boot dev='network'/>
+ <boot dev='hd'/>
+</os></pre><div class="para">
+ Also ensure that the guest virtual machine is connected to the private network:
+ </div><pre class="screen"><interface type='network'>
+ <mac address='52:54:00:66:79:14'/>
+ <source network='default'/>
+ <target dev='vnet0'/>
+ <alias name='net0'/>
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
+</interface></pre></div></div></div><div xml:lang="en-US" class="chapter" id="qemu-ga" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 16. QEMU Guest Agent</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#idm117719760">16.1. Set Up Communication between Guest Agent and Host</a></span></dt></dl></div><div class="para">
+ The QEMU Guest Agent allows the host machine to issue commands to the guest operating system. The guest operating system then responds to those commands asynchronously.
+ </div><div class="para">
+ This section covers the options and commands available to the guest agent in detail. It also covers how to run the guest agent in the foreground, or as a daemon in the background.
+ </div><div class="section" id="idm117719760"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm117719760">16.1. Set Up Communication between Guest Agent and Host</h2></div></div></div><div class="para">
+ The host machine communicates with the guest agent through a VirtIO serial connection between the host and guest machines. A VirtIO serial channel is connected to the host via a character device driver (typically a Unix socket), and the guest listens on this serial channel. The following procedure shows how to set up the host and guest machines for guest agent use.
+ </div><div class="procedure"><h6>Procedure 16.1. Set Up Host-Agent Communication</h6><ol class="1"><li class="step"><p class="title"><strong>Launch QEMU with a character device driver</strong></p><div class="para">
+ Launch QEMU as usual, with additional definitions for the character device driver required to communicate with the guest agent.
+ </div><div class="para">
+ The following example launches QEMU to communicate over the Unix socket <code class="filename">/tmp/qga.sock</code>.
+ </div><pre class="screen">/usr/libexec/qemu-kvm [...] -chardev socket,path=/tmp/qga.sock,server,nowait,id=qga0 \
+ -device virtio-serial \
+ -device virtserialport,chardev=qga0,name=org.qemu.guest_agent.0</pre></li><li class="step"><p class="title"><strong>Start the Guest Agent</strong></p><div class="para">
+ On the guest, run the following command to start the Guest Agent:
+ </div><pre class="screen">qemu-ga --path <em class="replaceable"><code>device_path</code></em> --method <em class="replaceable"><code>method</code></em></pre><div class="para">
+ The guest agent now parses incoming QMP messages for commands, and acts upon them if valid.
+ </div><div class="para">
+ If no other method or path is specified with the <code class="option">--method</code> or <code class="option">--path</code> options respectively, the Guest Agent listens over <code class="literal">virtio-serial</code>, through the <code class="filename">/dev/virtio-ports/org.qemu.guest_agent.0</code> device path.
+ </div></li></ol></div><div class="para">
+ You can now communicate with the guest by sending valid QMP commands over the established character device driver.
+ </div></div></div></div><div class="part" id="idm99059024"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part II. Administration</h1></div></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-Server_best_practices">17. Server best practices</a></span></dt><dt><span class="chapter"><a href="#chap-Virtualization-Security_for_virtualization">18. Security for virtualization</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Security_for_virtualization-Storage_security_issues">18.1. Storage security issues</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization">18.2. SELinux and virtualization</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Security_for_virtualization-SELinux_considerations">18.3. SELinux</a></span></dt><dt><span class
="section"><a href="#idm81619664">18.4. Virtualization firewall information</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-sVirt">19. sVirt</a></span></dt><dd><dl><dt><span class="section"><a href="#idm100037280">19.1. Security and Virtualization</a></span></dt><dt><span class="section"><a href="#idm96599200">19.2. sVirt labeling</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-KVM_live_migration">20. KVM live migration</a></span></dt><dd><dl><dt><span class="section"><a href="#Live_migration_requirements">20.1. Live migration requirements</a></span></dt><dt><span class="section"><a href="#Live_migration_and_RHEL_compatibility">20.2. Live migration and Fedora version compatibility </a></span></dt><dt><span class="section"><a href="#shared-storage-nfs-migration">20.3. Shared storage example: NFS for a simple migration</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-KVM_live_migratio
n-Live_KVM_migration_with_virsh">20.4. Live KVM migration with virsh</a></span></dt><dd><dl><dt><span class="section"><a href="#add-notes">20.4.1. Additonal tips for migration with virsh </a></span></dt><dt><span class="section"><a href="#virsh-migration-arguements">20.4.2. Additional options for the virsh migrate command</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager">20.5. Migrating with virt-manager</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests">21. Remote management of guests</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_with_SSH">21.1. Remote management with SSH</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL">
21.2. Remote management over TLS and SSL</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes">21.3. Transport modes</a></span></dt></dl></dd><dt><span class="chapter"><a href="#sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM">22. Overcommitting with KVM</a></span></dt><dt><span class="chapter"><a href="#chap-KSM">23. KSM</a></span></dt><dt><span class="chapter"><a href="#chap-Virtualization_Administration_GuideAdvanced">24. Advanced virtualization administration</a></span></dt><dd><dl><dt><span class="section"><a href="#idm108086240">24.1. Control Groups (cgroups)</a></span></dt><dt><span class="section"><a href="#idm115160736">24.2. Hugepage support</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-Tips_and_tricks">25. Miscellaneous administration tasks</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Tips_a
nd_tricks-Automatically_starting_guests">25.1. Automatically starting guests</a></span></dt><dt><span class="section"><a href="#sect-mem-dump-off">25.2. Guest memory allocation</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Using_qemu_img">25.3. Using qemu-img</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions">25.4. Verifying virtualization extensions</a></span></dt><dt><span class="section"><a href="#idm110949808">25.5. Setting KVM processor affinities</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address">25.6. Generating a new unique MAC address</a></span></dt><dt><span class="section"><a href="#idm106199024">25.7. Improving guest response time</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests">25.8. Disable SMART di
sk monitoring for guests</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server">25.9. Configuring a VNC Server</a></span></dt><dt><span class="section"><a href="#sect-gracefully-shut-down-guests">25.10. Gracefully shutting down guests</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers">25.11. Virtual machine timer management with libvirt</a></span></dt><dt><span class="section"><a href="#sect-perf-mon">25.12. Using PMU to monitor guest performance</a></span></dt><dt><span class="section"><a href="#sect-s3-s4">25.13. Guest virtual machine power management</a></span></dt><dt><span class="section"><a href="#sect-qemu-ga">25.14. QEMU Guest Agent Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-guest-synch">25.14.1. guest-sync</a></span></dt><dt><span class="section"><a href="#subsect-guest-synch-delimited">25.14.2. guest-sync-delimited</a><
/span></dt></dl></dd><dt><span class="section"><a href="#sect-limit-redirection">25.15. Setting a limit on device redirection</a></span></dt><dt><span class="section"><a href="#sect-dynamic-vNIC">25.16. Dynamically changing a host or a network bridge that is attached to a virtual NIC</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-Storage_Concepts">26. Storage concepts</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Storage_Concepts-Storage_Pools">26.1. Storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Concepts-Volumes">26.2. Volumes </a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools">27. Storage pools</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating_Storage_Pools">27.1. Creating storage pools </a></span></dt><dd><dl
><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-Dedicated_Disk_Devices">27.1.1. Disk-based storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-File_Systems">27.1.2. Partition-based storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-Local_Directories">27.1.3. Directory-based storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-LVM">27.1.4. LVM-based storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-iSCSI">27.1.5. iSCSI-based storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-NFS">27.1.6. NFS-based storage pools</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Virtualization_Administration_Guide-Storage_Volumes">28. Volumes </a></span></dt>
<dd><dl><dt><span class="section"><a href="#sect-Virtualization-Storage_Volumes-Creating_volumes">28.1. Creating volumes</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Volumes-Cloning_volumes">28.2. Cloning volumes</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests">28.3. Adding storage devices to guests</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Adding_storage_devices_to_guests-Adding_file_based_storage_to_a_guest">28.3.1. Adding file based storage to a guest</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest">28.3.2. Adding hard drives and other block devices to a guest</a></span></dt><dt><span class="section"><a href="#sect-Managing_storage_controllers_in_a_guest">28.3.3. Managing storage controllers in a guest</a></span><
/dt></dl></dd><dt><span class="section"><a href="#sect-Virtualization-Storage_Volumes-Deleting_volumes">28.4. Deleting and removing volumes</a></span></dt></dl></dd><dt><span class="chapter"><a href="#vhostmd">29. The Virtual Host Metrics Daemon (vhostmd)</a></span></dt><dd><dl><dt><span class="section"><a href="#idm109965248">29.1. Installing vhostmd on the host</a></span></dt><dt><span class="section"><a href="#idm99221600">29.2. Configuration of vhostmd</a></span></dt><dt><span class="section"><a href="#idm74152464">29.3. Starting and stopping the daemon</a></span></dt><dt><span class="section"><a href="#idm100836656">29.4. Verifying that vhostmd is working from the host</a></span></dt><dt><span class="section"><a href="#idm92004288">29.5. Configuring guests to see the metrics</a></span></dt><dt><span class="section"><a href="#idm97572736">29.6. Using vm-dump-metrics in Fedora guests to verify operation</a></span></dt></dl></dd></dl></div><div xml:lang="en-US" class="chap
ter" id="chap-Virtualization_Administration_Guide-Server_best_practices" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 17. 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 host.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Run SELinux in enforcing mode. Set SELinux to run in enforcing mode with the <code class="command">setenforce</code> command.
+ </div><pre class="screen"># setenforce 1
+</pre></li><li class="listitem"><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 class="listitem"><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 class="listitem"><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 class="listitem"><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. Use of shareable, network storage in a central location is highly recommended.
+ </div></li></ul></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization-Security_for_virtualization" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 18. Security for virtualization</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Virtualization-Security_for_virtualization-Storage_security_issues">18.1. Storage security issues</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization">18.2. SELinux and virtualization</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Security_for_virtualization-SELinux_considerations">18.3. SELinux</a></span></dt><dt><span class="section"><a href="#idm81619664">18.4. Virtualization firewall information</a></span></dt></dl></div><div class="para">
+ When deploying virtualization technologies, you must ensure that the host cannot be compromised. The host is a Fedora system that manages the system, devices, memory and networks as well as all virtualized guests. If the host is insecure, all guests 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 class="listitem"><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 class="listitem"><div class="para">
+ Enable SELinux on the hypervisor. Read <a class="xref" href="#sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization">Section 18.2, “SELinux and virtualization”</a> for more information on using SELinux and virtualization.
+ </div></li><li class="listitem"><div class="para">
+ Use a firewall to restrict traffic to the host. You can setup a firewall with default-reject rules that will help secure the host from attacks. It is also important to limit network-facing services.
+ </div></li><li class="listitem"><div class="para">
+ Do not allow normal users to access the host. The host is privileged, and granting access to unprivileged accounts may compromise the level of security.
+ </div></li></ul></div><div class="section" id="sect-Virtualization-Security_for_virtualization-Storage_security_issues"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">18.1. Storage security issues</h2></div></div></div><div class="para">
+ Administrators of virtualized guests can change the partitions the host boots in certain circumstances. To prevent this administrators should follow these recommendations:
+ </div><div class="para">
+ The host should not use disk labels to identify file systems in the <code class="filename">fstab</code> file, the <code class="filename">initrd</code> file or used by the kernel command line. If less privileged users, especially virtualized guests, have write access to whole partitions or LVM volumes.
+ </div><div class="para">
+ Guests should not be given write access to whole disks or block devices (for example, <code class="filename">/dev/sdb</code>). Use partitions (for example, <code class="filename">/dev/sdb1</code>) or LVM volumes.
+ </div></div><div class="section" id="sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">18.2. 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 attacker's abilities and works to prevent many common security exploits such as buffer overflow attacks and privilege escalation. It is because of these benefits that all Fedora systems should run with SELinux enabled and in enforcing mode.
+ </div><div class="formalpara" id="form-Virtualization-SELinux_and_virtualization-Adding_LVM_based_storage_with_SELinux_in_enforcing_mode"><h5 class="formalpara">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-SELinux_and_virtualization-Creating_and_mounting_a_logical_volume_on_a_virtualized_guest_with_SELinux_enabled"><h6>Procedure 18.1. Creating and mounting a logical volume on a virtualized guest with SELinux enabled</h6><ol class="1"><li class="step"><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 class="step"><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 class="step"><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 class="step"><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 class="step"><div class="para">
+ Set the correct SELinux type for the libvirt image location.
+ </div><pre class="screen"># semanage fcontext -a -t virt_image_t "/virtstorage(/.*)?"
+</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:virt_image_t:s0
+</pre></li><li class="step"><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">virt_image_t</code> (the <code class="command">restorecon</code> and <code class="command">setfiles</code> commands read the files in <code class="filename">/etc/selinux/targeted/contexts/files/</code>).
+ </div><pre class="screen"># restorecon -R -v /virtstorage
+</pre></li></ol></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Create a new file (using the <code class="command">touch</code> command) on the file system.
+ </div><pre class="screen"># touch <em class="replaceable"><code>/virtstorage/newfile</code></em></pre><div class="para">
+ Verify the file has been relabeled using the following command:
+ </div><pre class="screen"># sudo ls -Z <em class="replaceable"><code>/virtstorage</code></em>
+-rw-------. root root system_u:object_r:virt_image_t:s0 <em class="replaceable"><code>newfile</code></em></pre><div class="para">
+ The output shows that the new file has the correct attribute, <code class="filename">virt_image_t</code>.
+ </div></div></div></div><div class="section" id="sect-Virtualization-Security_for_virtualization-SELinux_considerations"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">18.3. SELinux</h2></div></div></div><div class="para">
+ This section contains topics to consider when using SELinux with 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. Make sure that you have installed the <code class="filename">policycoreutilis-python</code> package (<code class="command">yum install policycoreutilis-python</code>) before running the command.
+ </div><pre class="screen"># semanage fcontext -a -t virt_image_t -f -b /dev/sda2
+# restorecon /dev/sda2
+</pre><div class="formalpara"><h5 class="formalpara" id="idm122347008">KVM and SELinux</h5>
+ The following table shows the SELinux Booleans which affect KVM when launched by libvirt.
+ </div><div class="segmentedlist"><div class="title"><strong><span class="title">KVM SELinux Booleans</span></strong></div><table border="0"><thead><tr class="segtitle"><th>SELinux Boolean</th><th>Description</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">virt_use_comm</td><td class="seg">Allow virt to use serial/parallel communication ports.</td></tr><tr class="seglistitem"><td class="seg">virt_use_fusefs</td><td class="seg">Allow virt to read fuse files.</td></tr><tr class="seglistitem"><td class="seg">virt_use_nfs</td><td class="seg">Allow virt to manage NFS files.</td></tr><tr class="seglistitem"><td class="seg">virt_use_samba</td><td class="seg">Allow virt to manage CIFS files.</td></tr><tr class="seglistitem"><td class="seg">virt_use_sanlock</td><td class="seg">Allow sanlock to manage virt lib files.</td></tr><tr class="seglistitem"><td class="seg">virt_use_sysfs</td><td class="seg">Allow virt to manage device configuration (PCI).</td></tr><tr class=
"seglistitem"><td class="seg">virt_use_xserver</td><td class="seg">Allow virtual machine to interact with the xserver.</td></tr><tr class="seglistitem"><td class="seg">virt_use_usb</td><td class="seg">Allow virt to use USB devices.</td></tr></tbody></table></div></div><div class="section" id="idm81619664"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm81619664">18.4. Virtualization firewall information</h2></div></div></div><div class="para">
+ Various ports are used for communication between virtualized guests and management utilities.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Any network service on a virtualized guest must have the applicable ports open on the guest to allow external access. If a network service on a guest is firewalled it will be inaccessible. Always verify the guests network configuration first.
+ </div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ ICMP requests must be accepted. ICMP packets are used for network testing. You cannot ping guests if ICMP packets are blocked.
+ </div></li><li class="listitem"><div class="para">
+ Port 22 should be open for SSH access and the initial installation.
+ </div></li><li class="listitem"><div class="para">
+ Ports 80 or 443 (depending on the security settings on the RHEV Manager) are used by the vdsm-reg service to communicate information about the host.
+ </div></li><li class="listitem"><div class="para">
+ Ports 5634 to 6166 are used for guest console access with the SPICE protocol.
+ </div></li><li class="listitem"><div class="para">
+ Ports 49152 to 49216 are used for migrations with KVM. Migration may use any port in this range depending on the number of concurrent migrations occurring.
+ </div></li><li class="listitem"><div class="para">
+ Enabling IP forwarding (<code class="computeroutput">net.ipv4.ip_forward = 1</code>) is also required for shared bridges and the default bridge. Note that installing libvirt enables this variable so it will be enabled when the virtualization packages are installed unless it was manually disabled.
+ </div></li></ul></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Note that enabling IP forwarding is <span class="bold bold"><strong>not</strong></span> required for physical bridge devices. When a guest is connected through a physical bridge, traffic only operates at a level that does not require IP configuration such as IP forwarding.
+ </div></div></div></div></div><div xml:lang="en-US" class="chapter" id="chap-sVirt" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 19. sVirt</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#idm100037280">19.1. Security and Virtualization</a></span></dt><dt><span class="section"><a href="#idm96599200">19.2. sVirt labeling</a></span></dt></dl></div><div class="para">
+ sVirt is a technology included in Fedora that integrates SELinux and virtualization. sVirt applies Mandatory Access Control (MAC) to improve security when using virtualized guests. The main reasons for integrating these technologies are to improve security and harden the system against bugs in the hypervisor that might be used as an attack vector aimed toward the host or to another virtualized guest.
+ </div><div class="para">
+ This chapter describes how sVirt integrates with virtualization technologies in Fedora.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm6678576">Non-virtualized environments</h5>
+ In a non-virtualized environment, hosts are separated from each other physically and each host has a self-contained environment, consisting of services such as a web server, or a DNS server. These services communicate directly to their own user space, host kernel and physical host, offering their services directly to the network. The following image represents a non-virtualized environment:
+ </div><div class="mediaobject"><img src="./images/before_virtualization.png" /></div><div class="formalpara"><h5 class="formalpara" id="idm84778832">Virtualized environments</h5>
+ In a virtualized environment, several operating systems can run on a single host kernel and physical host. The following image represents a virtualized environment:
+ </div><div class="mediaobject"><img src="./images/after_virtualization.png" /></div><div class="section" id="idm100037280"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm100037280">19.1. Security and Virtualization</h2></div></div></div><div class="para">
+ When services are not virtualized, machines are physically separated. Any exploit is usually contained to the affected machine, with the obvious exception of network attacks. When services are grouped together in a virtualized environment, extra vulnerabilities emerge in the system. If there is a security flaw in the hypervisor that can be exploited by a guest instance, this guest may be able to not only attack the host, but also other guests running on that host. These attacks can extend beyond the guest instance and could expose other guests to attack.
+ </div><div class="para">
+ sVirt is an effort to isolate guests and limit their ability to launch further attacks if exploited. This is demonstrated in the following image, where an attack can not break out of the virtualized guest and extend to another guest instance:
+ </div><div class="mediaobject"><img src="./images/selinux_uuid_block.png" /></div><div class="para">
+ SELinux introduces a pluggable security framework for virtualized instances in its implementation of Mandatory Access Control (MAC). The sVirt framework allows guests and their resources to be uniquely labeled. Once labeled, rules can be applied which can reject access between different guests.
+ </div></div><div class="section" id="idm96599200"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm96599200">19.2. sVirt labeling</h2></div></div></div><div class="para">
+ Like other services under the protection of SELinux, sVirt uses process-based mechanisms and restrictions to provide an extra layer of security over guest instances. Under typical use, you should not even notice that sVirt is working in the background. This section describes the labeling features of sVirt.
+ </div><div class="para">
+ As shown in the following output, when using sVirt, each virtualized guest process is labeled and runs with a dynamically generated level. Each process is isolated from other VMs with different levels:
+ </div><pre class="screen">
+# ps -eZ | grep qemu
+
+system_u:system_r:svirt_t:s0:c87,c520 27950 ? 00:00:17 qemu-kvm
+</pre><div class="para">
+ The actual disk images are automatically labeled to match the processes, as shown in the following output:
+ </div><pre class="screen">
+# ls -lZ /var/lib/libvirt/images/*
+
+ system_u:object_r:svirt_image_t:s0:c87,c520 image1
+</pre><div class="para">
+ The following table outlines the different labels that can be assigned when using sVirt:
+ </div><div class="table"><h6>Table 19.1. sVirt labels</h6><div class="table-contents"><table summary="sVirt labels" border="1"><colgroup><col align="left" class="c1" width="50%" /><col align="left" class="c2" width="50%" /></colgroup><thead><tr><th class="" align="left">
+ Type/Description
+ </th><th class="" align="left">
+ SELinux Context
+ </th></tr></thead><tbody><tr><td class="" align="left">
+ Virtualized guest processes. MCS1 is a random MCS field. Approximately 500,000 labels are supported.
+ </td><td class="" align="left">
+ system_u:system_r:svirt_t:MCS1
+ </td></tr><tr><td class="" align="left">
+ Virtualized guest images. Only <span class="emphasis"><em>svirt_t</em></span> processes with the same MCS fields can read/write these images.
+ </td><td class="" align="left">
+ system_u:object_r:svirt_image_t:MCS1
+ </td></tr><tr><td class="" align="left">
+ Virtualized guest shared read/write content. All <span class="emphasis"><em>svirt_t</em></span> processes can write to the svirt_image_t:s0 files.
+ </td><td class="" align="left">
+ system_u:object_r:svirt_image_t:s0
+ </td></tr><tr><td class="" align="left">
+ Virtualized guest shared read only content. All svirt_t processes can read these files/devices.
+ </td><td class="" align="left">
+ system_u:object_r:svirt_content_t:s0
+ </td></tr><tr><td class="" align="left">
+ Virtualized guest images. Default label for when an image exits. No <span class="emphasis"><em>svirt_t</em></span> virtual processes can read files/devices with this label.
+ </td><td class="" align="left">
+ system_u:object_r:virt_content_t:s0
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ It is also possible to perform static labeling when using sVirt. Static labels allow the administrator to select a specific label, including the MCS/MLS field, for a virtualized guest. Administrators who run statically-labeled virtualized guests are responsible for setting the correct label on the image files. The virtualized guest will always be started with that label, and the sVirt system will never modify the label of a statically-labeled virtual machine's content. This allows the sVirt component to run in an MLS environment. You can also run multiple virtualized guests with different sensitivity levels on a system, depending on your requirements.
+ </div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_Guide-KVM_live_migration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 20. KVM live migration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#Live_migration_requirements">20.1. Live migration requirements</a></span></dt><dt><span class="section"><a href="#Live_migration_and_RHEL_compatibility">20.2. Live migration and Fedora version compatibility </a></span></dt><dt><span class="section"><a href="#shared-storage-nfs-migration">20.3. Shared storage example: NFS for a simple migration</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh">20.4. Live KVM migration with virsh</a></span></dt><dd><dl><dt><span class="section"><a href="#add-notes">20.4.1. Additonal tips for migration with virsh </a></span></dt><dt><span class="section"><a href="#virsh-migration-a
rguements">20.4.2. Additional options for the virsh migrate command</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager">20.5. 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 describes the process of moving a guest from one host to another. This is possible because guests are running in a virtualized environment instead of directly on the hardware. Migration is useful for:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Load balancing - guests can be moved to hosts with lower usage when their host becomes overloaded, or another host is under-utilized.
+ </div></li><li class="listitem"><div class="para">
+ Hardware independence - when we need to upgrade, add, or remove hardware devices on the host, we can safely relocate guests to other hosts. This means that guests do not experience any downtime for hardware improvements.
+ </div></li><li class="listitem"><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 class="listitem"><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">
+ Migration works by sending the state of the guest's memory and any virtualized devices to a destination host. It is recommended to use shared, networked storage to store guest images to be migrated. It is also recommended to libvirt-managed storage pools for shared storage when migrating virtual machines.
+ </div><div class="para">
+ Migrations can be performed live or not.
+ </div><div class="para">
+ In a live migration, the guest continues to run on the source host while its memory pages are transferred, in order, to the destination host. During migration, KVM monitors the source for any changes in pages it has already transferred, and begins to transfer these changes when all of the initial pages have been transferred. KVM also estimates transfer speed during migration, so when the remaining amount of data to transfer will take a certain configurable period of time (10ms by default), KVM suspends the original guest, transfers the remaining data, and resumes the guest on the destination host.
+ </div><div class="para">
+ A migration that is not performed live, suspends the guest, then moves an image of the guest's memory to the destination host. The guest is then resumed on the destination host and the memory the guest used on the source host is freed. The time it takes to complete such a migration depends on network bandwidth and latency. If the network is experiencing heavy use or low bandwidth, the migration will take much longer.
+ </div><div class="para">
+ If the original guest modifies pages faster than KVM can transfer them to the destination host, offline migration must be used, as live migration would never complete.
+ </div><div class="section" id="Live_migration_requirements"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.1. Live migration requirements</h2></div></div></div><div class="para">
+ Migrating guests requires the following:
+ </div><div class="itemizedlist" id="item-Virtualization-Live_migration_requirements-Migration_requirements"><h6>Migration requirements</h6><ul><li class="listitem"><div class="para">
+ A guest installed on shared storage using one of the following protocols:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Fibre Channel-based LUNs
+ </div></li><li class="listitem"><div class="para">
+ iSCSI
+ </div></li><li class="listitem"><div class="para">
+ FCoE
+ </div></li><li class="listitem"><div class="para">
+ NFS
+ </div></li><li class="listitem"><div class="para">
+ GFS2
+ </div></li><li class="listitem"><div class="para">
+ SCSI RDMA protocols (SCSI RCP): the block export protocol used in Infiniband and 10GbE iWARP adapters
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Both systems must have the appropriate TCP/IP ports open.
+ </div></li><li class="listitem"><div class="para">
+ A separate system exporting the shared storage medium. Storage should not reside on either of the two hosts being used for migration.
+ </div></li><li class="listitem"><div class="para">
+ Shared storage must mount at the same location on source and destination systems. The mounted directory names must be identical. Although it is possible to keep the images using different paths, it is not recommended. Note that, if you are intending to use virt-manager to perform the migration, the path names must be identical. If however you intend to use virsh to perform the migration, different network configurations and mount directories can be used with the help of --xml option or pre-hooks when doing migrations. Even with out shared storage, migration can still succeed with the command <code class="command">--copy-storage-all</code>. For more information on <code class="command">prehooks</code>, refer to <a href="http://www.libvirt.org/hooks.html"> libvirt.org</a>, and for more information on the XML option, see the virsh manual.
+ </div></li><li class="listitem"><div class="para">
+ When migration is attempted on an existing guest in a public bridge+tap network, the source and destination hosts must be located in the same network. Otherwise, the guest network will not operate after migration.
+ </div></li></ul></div><div class="para">
+ Make sure that the <code class="filename">libvirtd</code> service is enabled (<code class="command"># chkconfig libvirtd on</code>) and running (<code class="command"># service libvirtd start</code>). It is also important to note that the ability to migrate effectively is dependent on the parameter settings in the <code class="filename">/etc/libvirt/libvirtd.conf</code> configuration file.
+ </div><div class="procedure" id="change-libvirt-config"><h6>Procedure 20.1. Configuring libvirtd.conf</h6><ol class="1"><li class="step"><div class="para">
+ Opening the <code class="filename">libvirtd.conf</code> requires running the command as root:
+ </div><pre class="screen"># vim /etc/libvirt/libvirtd.conf</pre></li><li class="step"><div class="para">
+ Change the parameters as needed and save the file.
+ </div></li><li class="step"><div class="para">
+ Restart the <code class="filename">libvirtd</code> service:
+ </div><pre class="screen"># service libvirtd restart</pre></li></ol></div></div><div class="section" id="Live_migration_and_RHEL_compatibility"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.2. Live migration and Fedora version compatibility </h2></div></div></div><div class="para">
+ Live Migration should only be performed in cases where the guest virtual machine and the host physical machine are running the same version of Fedora. Should you perform a live migration using different versions be forwarned that the migration may fail.
+ </div><div class="para">
+ <span class="bold bold"><strong>Issues with the migration protocol</strong></span> — If backward migration ends with "unknown section error", repeating the migration process can repair the issue as it may be a transient error. If not, please report the problem.
+ </div><div class="formalpara" id="form-Virtualization-Live_migration_requirements-Configuring_network_storage"><h5 class="formalpara">Configuring network storage</h5>
+ Configure shared storage and install a guest on the shared storage.
+ </div><div class="para">
+ Alternatively, use the NFS example in <a class="xref" href="#shared-storage-nfs-migration">Section 20.3, “Shared storage example: NFS for a simple migration”</a>
+ </div></div><div class="section" id="shared-storage-nfs-migration"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.3. Shared storage example: NFS for a simple migration</h2></div></div></div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ This example uses NFS to share guest images with other KVM hosts. Although not practical for large installations, it is presented to demonstrate migration techniques only. Do not use this example for migrating or running more than a few guests.
+ </div><div class="para">
+ iSCSI storage is a better choice for large deployments. Refer to <a class="xref" href="#sect-Virtualization-Storage_Pools-Creating-iSCSI">Section 27.1.5, “iSCSI-based storage pools”</a> for configuration details.
+ </div></div></div><div class="para">
+ Also note, that the instructions provided herin are not meant to replace the detailed instructions found in <em class="citetitle">Red Hat Linux Storage Administration Guide</em>. Refer to this guide for information on configuring NFS, opening IP tables, and configuring the firewall.
+ </div><div class="para">
+ Make sure that NFS filelocking is not used as it is not supported in KVM.
+ </div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Export your libvirt image directory</strong></p><div class="para">
+ Migration requires storage to reside on a system that is separate to the migration target systems. On this separate system, export the storage by adding 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>*.example.com</code></em>(rw,no_root_squash,sync)</pre><div class="para">
+ Change the hostname parameter as required for your environment.
+ </div></li><li class="step"><p class="title"><strong>Start NFS</strong></p><ol class="a"><li class="step"><div class="para">
+ Install the NFS packages if they are not yet installed:
+ </div><pre class="screen"># yum install nfs</pre></li><li class="step"><div class="para">
+ Make sure that the ports for NFS in <code class="command">iptables</code> (2049, for example) are opened and add NFS to the <code class="filename">/etc/hosts.allow</code> file.
+ </div></li><li class="step"><div class="para">
+ Start the NFS service:
+ </div><pre class="screen"># service nfs start</pre></li></ol></li><li class="step"><p class="title"><strong>Mount the shared storage on the destination</strong></p><div class="para">
+ On the migration destination system, mount the <code class="filename">/var/lib/libvirt/images</code> directory:
+ </div><pre class="screen"># mount <em class="parameter"><code>storage_host</code></em>:/var/lib/libvirt/images /var/lib/libvirt/images
+</pre><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Whichever directory is chosen for the guests must be exactly the same on host and guest. This applies to all types of shared storage. The directory must be the same or the migration with virt-manager will fail.
+ </div></div></div></li></ol></div></div><div class="section" id="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.4. 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">
+ Note that the <em class="replaceable"><code>--live</code></em> option may be eliminated when live migration is not desired. Additional options are listed in <a class="xref" href="#virsh-migration-arguements">Section 20.4.2, “Additional options for the virsh migrate command”</a>.
+ </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 connection URL of the destination host. 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="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The <em class="parameter"><code>DestinationURL</code></em> parameter for normal migration and peer2peer migration has different semantics:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ normal migration: the <em class="parameter"><code>DestinationURL</code></em> is the URL of the target host as seen from the source guest.
+ </div></li><li class="listitem"><div class="para">
+ peer2peer migration: <em class="parameter"><code>DestinationURL</code></em> is the URL of the target host as seen from the source host.
+ </div></li></ul></div></div></div><div class="para">
+ Once the command is entered, you will be prompted for the root password of the destination system.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ An entry for the destination host, in the <code class="filename">/etc/hosts</code> file on the source server is required for migration to succeed. Enter the IP address and hostname for the destination host in this file as shown in the following example, substituting your destination host's IP address and hostname:
+<pre class="screen">
+10.0.0.20 host2.example.com
+</pre>
+ </div></div></div><div class="formalpara" id="form-Virtualization-Live_KVM_migration_with_virsh-Example_live_migration_with_virsh"><h5 class="formalpara">Example: live migration with virsh</h5>
+ This example migrates from <code class="systemitem">host1.example.com</code> to <code class="systemitem">host2.example.com</code>. Change the host names for your environment. This example migrates a virtual machine named <code class="filename">guest1-F19</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="#item-Virtualization-Live_migration_requirements-Migration_requirements">Migration requirements</a>).
+ </div><div class="procedure"><ol class="1"><li class="step" id="step-Virtualization_Administration_Guide-Live_KVM_migration_with_virsh-Verify_the_guest_is_running"><p class="title"><strong>Verify the guest is running</strong></p><div class="para">
+ From the source system, <code class="systemitem">host1.example.com</code>, verify <code class="systemitem">guest1-F19</code> is running:
+ </div><pre class="screen">[root at host1 ~]# virsh list
+Id Name State
+----------------------------------
+ 10 guest1-F19 running
+</pre></li><li class="step" id="step-Virtualization_Administration_Guide-Live_KVM_migration_with_virsh-Migrate_the_guest"><p class="title"><strong>Migrate the guest</strong></p><div class="para">
+ Execute the following command to live migrate the guest to the destination, <code class="systemitem">host2.example.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>guest1-F19 qemu+ssh://host2.example.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 class="step" id="step-Virtualization_Administration_Guide-Live_KVM_migration_with_virsh-Wait"><p class="title"><strong>Wait</strong></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 class="step" id="step-Virtualization_Administration_Guide-Live_KVM_migration_with_virsh-Verify_the_guest_has_arrived_at_the_destination_host"><p class="title"><strong>Verify the guest has arrived at the destination host</strong></p><div class="para">
+ From the destination system, <code class="systemitem">host2.example.com</code>, verify <code class="systemitem">guest1-F19</code> is running:
+ </div><pre class="screen">[root at host2 ~]# virsh list
+Id Name State
+----------------------------------
+ 10 guest1-F19 running
+</pre></li></ol></div><div class="para">
+ The live migration is now complete.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ libvirt supports a variety of networking methods including TLS/SSL, UNIX sockets, SSH, and unencrypted TCP. Refer to <a class="xref" href="#chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests">Chapter 21, <em>Remote management of guests</em></a> for more information on using other methods.
+ </div></div></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Non-running guests cannot be migrated with the <code class="command">virsh migrate</code> command. To migrate a non-running guest, the following script should be used:
+<pre class="screen">
+virsh dumpxml Guest1 > Guest1.xml
+virsh -c qemu+ssh://<target-system-FQDN> define Guest1.xml
+virsh undefine Guest1
+</pre>
+ </div></div></div><div class="section" id="add-notes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.4.1. Additonal tips for migration with virsh </h3></div></div></div><div class="para">
+ It is possible to perform multiple, concurrent live migrations where each migration runs in a separate command shell. However, this should be done with caution and should involve careful calculations as each migration instance uses one MAX_CLIENT from each side (source and target). As the default setting is 20, there is enough to run 10 instances without changing the settings. Should you need to change the settings, refer to the procedure <a class="xref" href="#change-libvirt-config">Procedure 20.1, “Configuring libvirtd.conf”</a>.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Open the libvirtd.conf file as described in <a class="xref" href="#change-libvirt-config">Procedure 20.1, “Configuring libvirtd.conf”</a>.
+ </div></li><li class="step"><div class="para">
+ Look for the Processing controls section.
+ </div><pre class="screen">
+#################################################################
+#
+# Processing controls
+#
+
+# The maximum number of concurrent client connections to allow
+# over all sockets combined.
+#max_clients = 20
+
+
+# The minimum limit sets the number of workers to start up
+# initially. If the number of active clients exceeds this,
+# then more threads are spawned, upto max_workers limit.
+# Typically you'd want max_workers to equal maximum number
+# of clients allowed
+#min_workers = 5
+#max_workers = 20
+
+
+# The number of priority workers. If all workers from above
+# pool will stuck, some calls marked as high priority
+# (notably domainDestroy) can be executed in this pool.
+#prio_workers = 5
+
+# Total global limit on concurrent RPC calls. Should be
+# at least as large as max_workers. Beyond this, RPC requests
+# will be read into memory and queued. This directly impact
+# memory usage, currently each request requires 256 KB of
+# memory. So by default upto 5 MB of memory is used
+#
+# XXX this isn't actually enforced yet, only the per-client
+# limit is used so far
+#max_requests = 20
+
+# Limit on concurrent requests from a single client
+# connection. To avoid one client monopolizing the server
+# this should be a small fraction of the global max_requests
+# and max_workers parameter
+#max_client_requests = 5
+
+#################################################################
+</pre></li><li class="step"><div class="para">
+ Change the <em class="parameter"><code>max_clients</code></em> and <em class="parameter"><code>max_workers</code></em> parameters settings. It is recommended that the number be the same in both parameters. The <em class="parameter"><code>max_clients</code></em> will use 2 clients per migration (one per side) and <em class="parameter"><code>max_workers</code></em> will use 1 worker on the source and 0 workers on the destination during the perform phase and 1 worker on the destination during the finish phase.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The <em class="parameter"><code>max_clients</code></em> and <em class="parameter"><code>max_workers</code></em> parameters settings are effected by all guest connections to the libvirtd service. This means that any user that is using the same guest and is performing a migration at the same time will also beholden to the limits set in the the <em class="parameter"><code>max_clients</code></em> and <em class="parameter"><code>max_workers</code></em> parameters settings. This is why the maximum value needs to be considered carefully before performing a concurrent live migration.
+ </div></div></div></li><li class="step"><div class="para">
+ Save the file and restart the service.
+ </div></li></ol></div></div><div class="section" id="virsh-migration-arguements"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.4.2. Additional options for the virsh migrate command</h3></div></div></div><div class="para">
+ In addition to <em class="replaceable"><code>--live</code></em>, virsh migrate accepts the following options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ --direct - used for direct migration
+ </div></li><li class="listitem"><div class="para">
+ --p2p - used for peer-2-peer migration
+ </div></li><li class="listitem"><div class="para">
+ --tunnelled - used for tunnelled migration
+ </div></li><li class="listitem"><div class="para">
+ --persistent - leaves the domain persistent on destination host
+ </div></li><li class="listitem"><div class="para">
+ --undefinesource - undefines the domain on the source host
+ </div></li><li class="listitem"><div class="para">
+ --suspend - leaves the domain paused on the destination host
+ </div></li><li class="listitem"><div class="para">
+ --copy-storage-all - indicates migration with non-shared storage with full disk copy
+ </div></li><li class="listitem"><div class="para">
+ --copy-storage-inc - indicates migration with non-shared storage with incremental copy (same base image shared between source and destination). In both cases the disk images have to exist on the destination host, the --copy-storage-.options only tell libvirt to transfer data from the images on source host to the images found at the same place on the destination host
+ </div></li><li class="listitem"><div class="para">
+ --change-protection - enforces that no incompatible configuration changes will be made to the domain while the migration is underway; this flag is implicitly enabled when supported by the hypervisor, but can be explicitly used to reject the migration if the hypervisor lacks change protection support.
+ </div></li><li class="listitem"><div class="para">
+ --unsafe - forces the migration to occur, ignoring all safety procedures.
+ </div></li><li class="listitem"><div class="para">
+ --verbose displays the progress of migration as it is occurring
+ </div></li><li class="listitem"><div class="para">
+ migrateuri - the migration URI which is usually omitted.
+ </div></li><li class="listitem"><div class="para">
+ --timeout seconds - forces a guest to suspend when the live migration counter exceeds N seconds. It can only be used with a live migration. Once the timeout is initiated, the migration continues on the suspended guest.
+ </div></li><li class="listitem"><div class="para">
+ dname - is used for renaming the domain to new name during migration, which also usually can be omitted
+ </div></li><li class="listitem"><div class="para">
+ s
+ </div></li><li class="listitem"><div class="para">
+ --xml file can be used to supply an alternative XML file for use on the destination to supply a larger set of changes to any host-specific portions of the domain XML, such as accounting for naming differences between source and destination in accessing underlying storage. This option is usually omitted.
+ </div></li></ul></div><div class="para">
+ Refer to the virsh man page for more information.
+ </div></div></div><div class="section" id="sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.5. Migrating with virt-manager</h2></div></div></div><div class="para">
+ This section covers migrating a KVM guest with <code class="command">virt-manager</code> from one host to another.
+ </div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Open virt-manager</strong></p><div class="para">
+ Open <code class="command">virt-manager</code>. Choose <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>Virtual Machine Manager</strong></span> from the main menu bar to launch <code class="command">virt-manager</code>.
+ </div><div class="figure" id="launch-virt-man-mig-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic1-virt-mgr-guests.png" width="444" alt="Virt-Manager main menu" /></div></div><h6>Figure 20.1. Virt-Manager main menu</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Connect to the target host</strong></p><div class="para">
+ Connect to the target host by clicking on the <span class="guimenu"><strong>File</strong></span> menu, then click <span class="guimenuitem"><strong>Add Connection</strong></span>.
+ <div class="figure" id="add-conn-mig-screen-step1"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic2-add-connection-pull-down.png" width="444" alt="Open Add Connection window" /></div></div><h6>Figure 20.2. Open Add Connection window</h6></div><br class="figure-break" />
+
+ </div></li><li class="step"><p class="title"><strong>Add connection</strong></p><div class="para">
+ The <span class="guilabel"><strong>Add Connection</strong></span> window appears.
+ </div><div class="figure" id="add-conn-mig-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic3-Add-Connection.png" alt="Adding a connection to the target host" /></div></div><h6>Figure 20.3. Adding a connection to the target host</h6></div><br class="figure-break" /><div class="para">
+ Enter the following details:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Hypervisor</strong></span>: Select <span class="guimenuitem"><strong>QEMU/KVM</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Method</strong></span>: Select the connection method.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Username</strong></span>: Enter the username for the remote host.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Hostname</strong></span>: Enter the hostname for the remote host.
+ </div></li></ul></div><div class="para">
+ Click the <span class="guibutton"><strong>Connect</strong></span> button. An SSH connection is used in this example, so the specified user's password must be entered in the next step.
+ </div><div class="figure" id="pass-ssh-mig-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic4-OpenSSH.png" alt="Enter password" /></div></div><h6>Figure 20.4. Enter password</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Migrate guest</strong></p><div class="para">
+ Right-click on the host to be migrated (<span class="bold bold"><strong>guest1-F19</strong></span> in this example) and click <span class="guimenuitem"><strong>Migrate</strong></span>.
+ </div><div class="figure" id="choose-host-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic5-guest-select-migrate.png" width="444" alt="Choosing the host to migrate" /></div></div><h6>Figure 20.5. Choosing the host to migrate</h6></div><br class="figure-break" /><div class="para">
+ Select the host you wish to migrate to and click <span class="guimenuitem"><strong>Migrate</strong></span>.
+ </div><div class="figure" id="mig-last-step-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic6-final-before-migrate.png" alt="Migrating the host" /></div></div><h6>Figure 20.6. Migrating the host</h6></div><br class="figure-break" /><div class="para">
+ A progress window will appear.
+ </div><div class="figure" id="mig-status-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic7-Migrating-guest1-rhel6-64.png" alt="Progress window" /></div></div><h6>Figure 20.7. Progress window</h6></div><br class="figure-break" /><div class="para">
+ <code class="command">virt-manager</code> now displays the newly migrated guest.
+ </div><div class="figure" id="mig-results-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic8-migrated.png" width="444" alt="Migrated guest status" /></div></div><h6>Figure 20.8. Migrated guest status</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>View the storage details for the host</strong></p><div class="para">
+ In the <span class="guimenu"><strong>Edit</strong></span> menu, click <span class="guimenuitem"><strong>Connection Details</strong></span>, the Connection Details window appears.
+ </div><div class="para">
+ Click the <span class="guibutton"><strong>Storage</strong></span> tab. The iSCSI target details for this host is shown.
+ </div><div class="figure" id="host-details-screenshot"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-virtlab22-Host-Details.png" width="444" alt="Storage details" /></div></div><h6>Figure 20.9. Storage details</h6></div><br class="figure-break" /><div class="para">
+ This host was defined by the following XML configuration:
+ </div><pre class="screen">
+<pool type='iscsi'>
+ <name>iscsirhel6guest</name>
+ <source>
+ <host name='virtlab22.example.com.'/>
+ <device path='iqn.2001-05.com.iscsivendor:0-8a0906-fbab74a06-a700000017a4cc89-rhevh'/>
+ </source>
+ <target>
+ <path>/dev/disk/by-path</path>
+ </target>
+</pool>
+</pre></li></ol></div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 21. Remote management of guests</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_with_SSH">21.1. Remote management with SSH</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL">21.2. Remote management over TLS and SSL</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes">21.3. Transport modes</a></span></dt></dl></div><div class="para">
+ This section explains how to remotely manage your guests using <code class="command">ssh</code> or TLS and SSL. More information on SSH can be found in the <em class="citetitle">Fedora Deployment Guide</em>
+ </div><div class="section" id="sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_with_SSH"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">21.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 is tunneled over <span class="application"><strong>SSH</strong></span>.
+ </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><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ you require root log in access to the remote machine for managing virtual machines,
+ </div></li><li class="listitem"><div class="para">
+ the initial connection setup process may be slow,
+ </div></li><li class="listitem"><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 class="listitem"><div class="para">
+ ssh does not scale well with larger numbers of remote machines.
+ </div></li></ul></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Fedora enables remote management of large numbers of virtual machines. Refer to the oVirt documentation for further details.
+ </div></div></div><div class="para">
+ The following packages are required for ssh access:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="package">openssh</span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">openssh-askpass</span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">openssh-clients</span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">openssh-server</span>
+ </div></li></ul></div><div class="formalpara" id="form-Virtualization-Remote_management_with_SSH-Configuring_SSH_access_for_virt_manager"><h5 class="formalpara">Configuring password less or password managed <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. If you have SSH keys set up and copied to the other systems you can skip this procedure.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ SSH keys are user dependent and may only be used by their owners. A key's owner is the one who generated it. Keys may not be shared.
+ </div><div class="para">
+ <code class="command">virt-manager</code> must be run by the user who owns the keys to connect to the remote host. That means, if the remote systems are managed by a non-root user <code class="command">virt-manager</code> must be run in unprivileged mode. If the remote systems are managed by the local root user then the SSH keys must be owned and created by root.
+ </div><div class="para">
+ You cannot manage the local host as an unprivileged user with <code class="command">virt-manager</code>.
+ </div></div></div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Optional: Changing user</strong></p><div class="para">
+ Change user, if required. This example uses the local root user for remotely managing the other hosts and the local host.
+ </div><pre class="screen">$<code class="command"> su -</code></pre></li><li class="step"><p class="title"><strong>Generating the SSH key pair</strong></p><div class="para">
+ Generate a public key pair on the machine <code class="command">virt-manager</code> is used. This example uses the default key location, in the <code class="filename">~/.ssh/</code> directory.
+ </div><pre class="screen"># <code class="command">ssh-keygen -t rsa</code></pre></li><li class="step"><p class="title"><strong>Copying the keys to the remote hosts</strong></p><div class="para">
+ Remote login without a password, or with a passphrase, requires an SSH key to be distributed to the systems being managed. Use the <code class="command">ssh-copy-id</code> command to copy the key to root user at the system address provided (in the example, <em class="parameter"><code>root at host2.example.com</code></em>).
+ </div><pre class="screen"># <code class="command">ssh-copy-id -i ~/.ssh/id_rsa.pub root at host2.example.com</code>
+root at host2.example.com's password:
+</pre><div class="para">
+ Now try logging into the machine, with the <code class="command">ssh root at host2.example.com</code> command and check in the <code class="filename">.ssh/authorized_keys</code> file to make sure unexpected keys have not been added.
+ </div><div class="para">
+ Repeat for other systems, as required.
+ </div></li><li class="step"><p class="title"><strong>Optional: Add the passphrase to the ssh-agent</strong></p><div class="para">
+ The instructions below describe how to add a passphrase to an existing ssh-agent. It will fail to run if the ssh-agent is not running. To avoid errors or conflicts make sure that your SSH parameters are set correctly. Refer to the <em class="citetitle">Fedora Deployment Guide</em> for more information.
+ </div><div class="para">
+ Add the passphrase for the SSH key to the <code class="command">ssh-agent</code>, if required. On the local host, use the following command to add the passphrase (if there was one) to enable password-less login.
+ </div><pre class="screen"># <code class="command">ssh-add ~/.ssh/id_rsa.pub</code></pre><div class="para">
+ The SSH key is added to the remote system.
+ </div></li></ol></div><div class="formalpara" id="form-Virtualization-Remote_management_with_SSH-The_libvirt_daemon_libvirtd"><h5 class="formalpara">The <code class="command">libvirt</code> daemon (<code class="systemitem">libvirtd</code>)</h5>
+ The <code class="systemitem">libvirt</code> daemon provides an interface for managing virtual machines. You must have the <code class="systemitem">libvirtd</code> daemon installed and running on every remote host that needs managing.
+ </div><pre class="screen">$ <code class="command">ssh root@<em class="replaceable"><code>somehost</code></em></code>
+<code class="command"># chkconfig libvirtd on</code>
+<code class="command"># service libvirtd start</code></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 class="formalpara" id="form-Virtualization-Remote_management_with_SSH-Accessing_remote_hosts_with_virt_manager"><h5 class="formalpara">Accessing remote hosts with virt-manager</h5>
+ Remote hosts can be managed with the virt-manager GUI tool. SSH keys must belong to the user executing virt-manager for password-less login to work.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Start virt-manager.
+ </div></li><li class="step"><div class="para">
+ Open the <span class="guimenuitem"><strong>File</strong></span>-><span class="guimenuitem"><strong>Add Connection</strong></span> menu.
+ </div><div class="figure" id="add-connection"><div class="figure-contents"><div class="mediaobject"><img src="images/Virt-Manager-Add-Connection.png" alt="Add connection menu" /></div></div><h6>Figure 21.1. Add connection menu</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Use the drop down menu to select hypervisor type, and click the <span class="guimenuitem"><strong>Connect to remote host</strong></span> check box to open the Connection <span class="guimenuitem"><strong>Method</strong></span> (in this case Remote tunnel over SSH), and enter the desired <span class="guimenuitem"><strong>User name</strong></span> and <span class="guimenuitem"><strong>Hostname</strong></span>, then click <span class="guimenuitem"><strong>Connect</strong></span>.
+ </div></li></ol></div></div><div class="section" id="sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">21.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="#sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_with_SSH">Section 21.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. The procedures that follow provide instructions on creating and deploying authentication certificates for TLS and SSL management.
+ </div><div class="procedure" id="createCA-key"><h6>Procedure 21.1. Creating a certificate authority (CA) key for TLS management</h6><ol class="1"><li class="step"><div class="para">
+ Before you begin, confirm that <code class="command">certtool</code> is installed. If not:
+ </div><pre class="screen">#<code class="command"> yum install certtool</code></pre></li><li class="step"><div class="para">
+ Generate a private key, using the following command:
+ </div><pre class="screen"># <code class="command">certtool --generate-privkey > cakey.pem</code></pre></li><li class="step"><div class="para">
+ Once the key generates, the next step is to create a signature file so the key can be self-signed. To do this, create a file with signature details and name it <code class="filename">ca.info</code>. This file should contain the following:
+ </div><pre class="screen"># <code class="command">vim ca.info</code></pre><pre class="screen">
+cn = Name of your organization
+ca
+cert_signing_key
+</pre></li><li class="step"><div class="para">
+ Generate the self-signed key with the following command:
+ </div><pre class="screen"># <code class="command">certtool --generate-self-signed --load-privkey cakey.perm --template ca.info --outfile cacert.pem</code></pre><div class="para">
+ Once the file generates, the ca.info file may be deleted using the <code class="command">rm</code> command. The file that results from the generation process is named <code class="filename">cacert.pem</code>. This file is the public key (certificate). The loaded file <code class="filename">cakey.pem</code> is the private key. This file should not be kept in a shared space. Keep this key private.
+ </div></li><li class="step"><div class="para">
+ Install the <code class="filename">cacert.pem</code> Certificate Authority Certificate file on all clients and servers in the <code class="filename">/etc/pki/CA/cacert.pem</code> directory to let them know that the certificate issued by your CA can be trusted. To view the contents of this file, run:
+<pre class="screen"># <code class="command">certtool -i --infile cacert.pem</code></pre>
+
+ </div><div class="para">
+ This is all that is required to set up your CA. Keep the CA's private key safe as you will need it in order to issue certificates for your clients and servers.
+ </div></li></ol></div><div class="procedure" id="issue-server-cetificate-ca"><h6>Procedure 21.2. Issuing a server certificate</h6><div class="para">
+ This procedure demonstrates how to issue a certificate with the X.509 CommonName (CN)field set to the hostname of the server. The CN must match the hostname which clients will be using to connect to the server. In this example, clients will be connecting to the server using the URI: <code class="filename">qemu://mycommonname/system</code>, so the CN field should be identical, ie mycommoname.
+ </div><ol class="1"><li class="step"><div class="para">
+ Create a private key for the server.
+ </div><pre class="screen"># <code class="command">certtool --generate-privkey > serverkey.pem</code></pre></li><li class="step"><div class="para">
+ Generate a signature for the CA's private key by first creating a template file called <code class="filename">server.info </code>. Make sure that the CN is set to be the same as the server's hostname:
+ </div><pre class="screen">
+organization = Name of your organization
+cn = mycommonname
+tls_www_server
+encryption_key
+signing_key
+</pre></li><li class="step"><div class="para">
+ Create the certificate with the following command:
+ </div><pre class="screen">
+# <code class="command">certtool --generate-certificate --load-privkey serverkey.pem --load-ca-certificate cacert.pem --load-ca-privkey cakey.pem \ --template server.info --outfile servercert.pem</code></pre></li><li class="step"><div class="para">
+ This results in two files being generated:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ serverkey.pem - The server's private key
+ </div></li><li class="listitem"><div class="para">
+ servercert.pem - The server's public key
+ </div></li></ul></div><div class="para">
+ Make sure to keep the location of the private key secret. To view the contents of the file, perform the following command:
+ </div><pre class="screen">
+# <code class="command">certtool -i -inifile servercert.pem</code></pre><div class="para">
+ When opening this file the <code class="filename">CN=</code> parameter should be the same as the CN that you set earlier. For example, <code class="filename">mycommonname</code>.
+ </div></li><li class="step"><div class="para">
+ Install the two files in the following locations:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">serverkey.pem</code> - the server's private key. Place this file in the following location: <code class="filename">/etc/pki/libvirt/private/serverkey.pem</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">servercert.pem</code> - the server's certificate. Install it in the following location on the server:<code class="filename"> /etc/pki/libvirt/servercert.pem</code>
+ </div></li></ul></div></li></ol></div><div class="procedure" id="pro-issue-client-certs-CA"><h6>Procedure 21.3. Issuing a client certificate</h6><ol class="1"><li class="step"><div class="para">
+ For every client (ie. any program linked with libvirt, such as virt-manager), you need to issue a certificate with the X.509 Distinguished Name (DN) set to a suitable name. This needs to be decided on a corporate level.
+ </div><div class="para">
+ For example purposes the following information will be used:
+ </div><pre class="screen"><em class="replaceable"><code>C=USA,ST=North Carolina,L=Raleigh,O=Fedora,CN=name_of_client</code></em></pre><div class="para">
+ This process is quite similar to <a class="xref" href="#issue-server-cetificate-ca">Procedure 21.2, “Issuing a server certificate”</a>, with the following exceptions noted.
+ </div></li><li class="step"><div class="para">
+ Make a private key with the following command:
+ </div><pre class="screen"># <code class="command">certtool --generate-privkey > clientkey.pem</code></pre></li><li class="step"><div class="para">
+ Generate a signature for the CA's private key by first creating a template file called <code class="filename">client.info </code>. The file should contain the following (fields should be customized to reflect your region/location):
+ </div><pre class="screen">
+country = USA
+state = North Carolina
+locality = Raleigh
+organization = Fedora
+cn = client1
+tls_www_client
+encryption_key
+signing_key
+</pre></li><li class="step"><div class="para">
+ Sign the certificate with the following command:
+ </div><pre class="screen">
+# <code class="command">certtool --generate-certificate --load-privkey clientkey.pem --load-ca-certificate cacert.pem \ --load-ca-privkey cakey.pem --template client.info --outfile clientcert.pem</code></pre></li><li class="step"><div class="para">
+ Install the certificates on the client machine:
+ </div><pre class="screen">
+# <code class="command">cp clientkey.pem /etc/pki/libvirt/private/clientkey.pem</code>
+# <code class="command">cp clientcert.pem /etc/pki/libvirt/clientcert.pem</code></pre></li></ol></div></div><div class="section" id="sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">21.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" id="form-Virtualization-Transport_modes-Transport_Layer_Security_TLS"><h5 class="formalpara">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" id="form-Virtualization-Transport_modes-UNIX_sockets"><h5 class="formalpara">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" id="form-Virtualization-Transport_modes-SSH"><h5 class="formalpara">SSH</h5>
+ Transported over a 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" id="form-Virtualization-Transport_modes-ext"><h5 class="formalpara">ext</h5>
+ The <em class="parameter"><code>ext</code></em> parameter is used for any external program which can make a connection to the remote machine by means outside the scope of libvirt. This parameter is unsupported.
+ </div><div class="formalpara" id="form-Virtualization-Transport_modes-tcp"><h5 class="formalpara">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" id="form-Virtualization-Transport_modes-Remote_URIs"><h5 class="formalpara">Remote URIs</h5>
+ A Uniform Resource Identifier (URI) is used by <code class="command">virsh</code> and <span class="package">libvirt</span> 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.
+ </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">
+ The transport method or the hostname must be provided to target an external location.
+ </div><div class="itemizedlist" id="item-Virtualization-Transport_modes-Examples_of_remote_management_parameters"><h6>Examples of remote management parameters</h6><ul><li class="listitem"><div class="para">
+ Connect to a remote KVM host named <code class="systemitem">host2</code>, using SSH transport and the SSH username <code class="systemitem">virtuser</code>.
+ </div><pre class="screen"><code class="command">qemu+ssh://virtuser@host2/</code></pre></li><li class="listitem"><div class="para">
+ Connect to a remote KVM hypervisor on the host named <code class="systemitem">host2</code> using TLS.
+ </div><pre class="screen"><code class="command">qemu://host2/</code></pre></li></ul></div><div class="itemizedlist" id="item-Virtualization-Transport_modes-Testing_examples"><h6>Testing examples</h6><ul><li class="listitem"><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"><code class="command">qemu+unix:///system?socket=/opt/libvirt/run/libvirt/libvirt-sock</code></pre></li><li class="listitem"><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"><code class="command">test+tcp://10.1.1.10:5000/default</code></pre></li></ul></div><div class="formalpara" id="form-Virtualization-Transport_modes-Extra_URI_parameters"><h5 class="formalpara">Extra URI parameters</h5>
+ Extra parameters can be appended to remote URIs. The table below <a class="xref" href="#tabl-Virtualization-Transport_modes-Extra_URI_parameters">Table 21.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-Transport_modes-Extra_URI_parameters"><h6>Table 21.1. Extra URI parameters</h6><div class="table-contents"><table summary="Extra URI parameters" border="1"><colgroup><col width="25%" /><col width="25%" /><col width="25%" /><col width="25%" /></colgroup><thead><tr><th class="">
+ Name
+ </th><th class="">
+ Transport mode
+ </th><th class="">
+ Description
+ </th><th class="">
+ Example usage
+ </th></tr></thead><tbody><tr><td class="">
+ name
+ </td><td class="">
+ all modes
+ </td><td class="">
+ 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 class="">
+ name=qemu:///system
+ </td></tr><tr><td class="">
+ command
+ </td><td class="">
+ ssh and ext
+ </td><td class="">
+ The external command. For ext transport this is required. For ssh the default is ssh. The PATH is searched for the command.
+ </td><td class="">
+ command=/opt/openssh/bin/ssh
+ </td></tr><tr><td class="">
+ socket
+ </td><td class="">
+ unix and ssh
+ </td><td class="">
+ 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 class="">
+ socket=/opt/libvirt/run/libvirt/libvirt-sock
+ </td></tr><tr><td class="">
+ netcat
+ </td><td class="">
+ ssh
+ </td><td class="">
+ <div class="para">
+ The <code class="command">netcat</code> command can be used to connect to remote systems. The default netcat parameter uses the <code class="command">nc</code> command. For SSH transport, libvirt constructs an SSH command using the form below:
+ </div>
+ <div class="para">
+ <em class="parameter"><code>command</code></em> -p <em class="parameter"><code>port</code></em> [-l <em class="parameter"><code>username</code></em>] <em class="parameter"><code>hostname</code></em>
+ </div>
+ <div class="para">
+ <em class="parameter"><code>netcat</code></em> -U socket
+ </div>
+ <div class="para">
+ The <em class="parameter"><code>port</code></em>, <em class="parameter"><code>username</code></em> and <em class="parameter"><code>hostname</code></em> parameters can be specified as part of the remote URI. The <em class="parameter"><code>command</code></em>, <em class="parameter"><code>netcat</code></em> and <em class="parameter"><code>socket</code></em> come from other extra parameters.
+ </div>
+
+ </td><td class="">
+ netcat=/opt/netcat/bin/nc
+ </td></tr><tr><td class="">
+ no_verify
+ </td><td class="">
+ tls
+ </td><td class="">
+ 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 class="">
+ no_verify=1
+ </td></tr><tr><td class="">
+ no_tty
+ </td><td class="">
+ ssh
+ </td><td class="">
+ 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 class="">
+ no_tty=1
+ </td></tr></tbody></table></div></div><br class="table-break" /></div></div><div xml:lang="en-US" class="chapter" id="sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 22. 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 a number of system resources, with the net effect of less power, cooling, and investment in server hardware.
+ </div><div class="formalpara" id="form-Virtualization-Overcommitting_with_KVM-Overcommitting_memory"><h5 class="formalpara">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. KVM can allocate more memory for guests than the host has physically available. Overcommitting requires sufficient swap space for all guests and all host processes.
+ </div><div class="para">
+ With KVM, virtual machines are Linux processes. Guests on the KVM hypervisor do not have dedicated blocks of physical RAM assigned to them, instead guests function as Linux processes. The Linux kernel allocates each process memory when the process requests more memory. KVM guests are allocated memory when requested by the guest operating system.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Ensure that the total sum of swap and memory space is greater than or equal to all the memory configured for running guests. A shortage less than this sum can cause a guest to be forcibly shut down.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="idm121354912">Configuring swap for overcommitting memory</h5>
+ 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 the physical RAM of the host.
+ </div><div class="para">
+ Red Hat <a href="http://kbase.redhat.com/faq/docs/DOC-15252">Knowledgebase</a> has an article on safely and efficiently determining the size of the swap partition.
+ </div><div class="para">
+ The swap partition must be large enough to provide virtual memory for all guests and the host system.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The example below is provided as a guide for configuring swap only. The settings listed may not be appropriate for your environment.
+ </div></div></div><div class="example"><h6>Example 22.1. Memory overcommit example</h6><div class="example-contents"><div class="para">
+ ExampleServer1 has 32GB of physical RAM. The system is being configured to run 56 guests, each with 1GB of virtualized memory. The host system itself needs a maximum of 3GB (apart from the guests).
+ </div><div class="para">
+ The total maximum memory consumption is 56GB + 3GB = 59GB. The system's physical RAM is 32GB, which leaves 27GB. Therefore, the minimum amount of swap that the host should have configured is 27GB.
+ </div></div></div><br class="example-break" /><div class="para">
+ It is possible to overcommit memory over ten times the amount of physical RAM in the system. This only works with certain types of guest, for example, desktop virtualization with minimal intensive usage or running several identical guests with KSM. Configuring swap and memory overcommit is not a formula, each environment and setup is different. Your environment must be tested and customized to ensure stability and performance.
+ </div><div class="para">
+ For more information on KSM and overcommitting, refer to <a class="xref" href="#chap-KSM">Chapter 23, <em>KSM</em></a>.
+ </div><div class="formalpara" id="form-Virtualization-Overcommitting_with_KVM-Overcommitting_virtualized_CPUs"><h5 class="formalpara">Overcommitting virtualized CPUs</h5>
+ The KVM hypervisor supports overcommitting virtualized CPUs. Virtualized CPUs can be overcommitted as far as load limits of 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 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 five VCPUs. Overcommitting single VCPU 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 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"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><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></div><div xml:lang="en-US" class="chapter" id="chap-KSM" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 23. KSM</h2></div></div></div><div class="para">
+ The concept of shared memory is common in modern operating systems. For example, when a program is first started it shares all of its memory with the parent program. When either the child or parent program tries to modify this memory, the kernel allocates a new memory region, copies the original contents and allows the program to modify this new region. This is known as copy on write.
+ </div><div class="para">
+ KSM is a new Linux feature which uses this concept in reverse. KSM enables the kernel to examine two or more already running programs and compare their memory. If any memory regions or pages are identical, KSM reduces multiple identical memory pages to a single page. This page is then marked copy on write. If the contents of the page is modified by a guest, a new page is created for that guest.
+ </div><div class="para">
+ This is useful for virtualization with KVM. When a guest is started, it only inherits the memory from the parent <code class="systemitem">qemu-kvm</code> process. Once the guest is running the contents of the guest operating system image can be shared when guests are running the same operating system or applications. KSM only identifies and merges identical pages which does not interfere with the guest or impact the security of the host or the guests. KSM allows KVM to request that these identical guest memory regions be shared.
+ </div><div class="para">
+ KSM provides enhanced memory speed and utilization. With KSM, common process data is stored in cache or in main memory. This reduces cache misses for the KVM guests which can improve performance for some applications and operating systems. Secondly, sharing memory reduces the overall memory usage of guests which allows for higher densities and greater utilization of resources.
+ </div><div class="para">
+ Starting in Fedora 18, KSM is NUMA aware
+ </div><div class="para">
+ Fedora uses two separate methods for controlling KSM:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <code class="systemitem">ksm</code> service starts and stops the KSM kernel thread.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="systemitem">ksmtuned</code> service controls and tunes the <code class="systemitem">ksm</code>, dynamically managing same-page merging. The <code class="systemitem">ksmtuned</code> service starts <code class="systemitem">ksm</code> and stops the <code class="systemitem">ksm</code> service if memory sharing is not necessary. The <code class="systemitem">ksmtuned</code> service must be told with the <em class="parameter"><code>retune</code></em> parameter to run when new guests are created or destroyed.
+ </div></li></ul></div><div class="para">
+ Both of these services are controlled with the standard service management tools.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm74320704">The KSM service</h5>
+ The <code class="systemitem">ksm</code> service is included in the <span class="package">qemu-kvm</span> package. KSM is off by default on Fedora. When using Fedora as a KVM host, however, it is likely turned on by the <code class="systemitem">ksm/ksmtuned</code> services.
+ </div><div class="para">
+ When the <code class="systemitem">ksm</code> service is not started, KSM shares only 2000 pages. This default is low and provides limited memory saving benefits.
+ </div><div class="para">
+ When the <code class="systemitem">ksm</code> service is started, KSM will share up to half of the host system's main memory. Start the <code class="systemitem">ksm</code> service to enable KSM to share more memory.
+ </div><pre class="screen"># service ksm start
+Starting ksm: [ OK ]</pre><div class="para">
+ The <code class="systemitem">ksm</code> service can be added to the default startup sequence. Make the <code class="systemitem">ksm</code> service persistent with the chkconfig command.
+ </div><pre class="screen"># chkconfig ksm on</pre><div class="formalpara"><h5 class="formalpara" id="idm122708464">The KSM tuning service</h5>
+ The <code class="systemitem">ksmtuned</code> service does not have any options. The <code class="systemitem">ksmtuned</code> service loops and adjusts <code class="systemitem">ksm</code>. The <code class="systemitem">ksmtuned</code> service is notified by libvirt when a guest is created or destroyed.
+ </div><pre class="screen"># service ksmtuned start
+Starting ksmtuned: [ OK ]</pre><div class="para">
+ The <code class="systemitem">ksmtuned</code> service can be tuned with the <em class="parameter"><code>retune</code></em> parameter. The <em class="parameter"><code>retune</code></em> parameter instructs <code class="systemitem">ksmtuned</code> to run tuning functions manually.
+ </div><div class="para">
+ The <code class="filename">/etc/ksmtuned.conf</code> file is the configuration file for the <code class="systemitem">ksmtuned</code> service. The file output below is the default <code class="filename">ksmtuned.conf</code> file.
+ </div><pre class="screen"># Configuration file for ksmtuned.
+
+# How long ksmtuned should sleep between tuning adjustments
+# KSM_MONITOR_INTERVAL=60
+
+# Millisecond sleep between ksm scans for 16Gb server.
+# Smaller servers sleep more, bigger sleep less.
+# KSM_SLEEP_MSEC=10
+
+# KSM_NPAGES_BOOST=300
+# KSM_NPAGES_DECAY=-50
+# KSM_NPAGES_MIN=64
+# KSM_NPAGES_MAX=1250
+
+# KSM_THRES_COEF=20
+# KSM_THRES_CONST=2048
+
+# uncomment the following to enable ksmtuned debug information
+# LOGFILE=/var/log/ksmtuned
+# DEBUG=1
+</pre><div class="formalpara"><h5 class="formalpara" id="idm65324224">KSM variables and monitoring</h5>
+ KSM stores monitoring data in the <code class="filename">/sys/kernel/mm/ksm/</code> directory. Files in this directory are updated by the kernel and are an accurate record of KSM usage and statistics.
+ </div><div class="para">
+ The variables in the list below are also configurable variables in the <code class="filename">/etc/ksmtuned.conf</code> file as noted below.
+ </div><div class="variablelist"><h6>The <code class="filename">/sys/kernel/mm/ksm/</code> files</h6><dl class="variablelist"><dt class="varlistentry"><span class="term">full_scans</span></dt><dd><div class="para">
+ Full scans run.
+ </div></dd><dt class="varlistentry"><span class="term">pages_shared</span></dt><dd><div class="para">
+ Total pages shared.
+ </div></dd><dt class="varlistentry"><span class="term">pages_sharing</span></dt><dd><div class="para">
+ Pages presently shared.
+ </div></dd><dt class="varlistentry"><span class="term">pages_to_scan</span></dt><dd><div class="para">
+ Pages not scanned.
+ </div></dd><dt class="varlistentry"><span class="term">pages_unshared</span></dt><dd><div class="para">
+ Pages no longer shared.
+ </div></dd><dt class="varlistentry"><span class="term">pages_volatile</span></dt><dd><div class="para">
+ Number of volatile pages.
+ </div></dd><dt class="varlistentry"><span class="term">run</span></dt><dd><div class="para">
+ Whether the KSM process is running.
+ </div></dd><dt class="varlistentry"><span class="term">sleep_millisecs</span></dt><dd><div class="para">
+ Sleep milliseconds.
+ </div></dd></dl></div><div class="para">
+ KSM tuning activity is stored in the <code class="filename">/var/log/ksmtuned</code> log file if the <em class="parameter"><code>DEBUG=1</code></em> line is added to the <code class="filename">/etc/ksmtuned.conf</code> file. The log file location can be changed with the <em class="parameter"><code>LOGFILE</code></em> parameter. Changing the log file location is not advised and may require special configuration of SELinux settings.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm89585200">Deactivating KSM</h5>
+ KSM has a performance overhead which may be too large for certain environments or host systems.
+ </div><div class="para">
+ KSM can be deactivated by stopping the <code class="systemitem">ksmtuned</code> and the <code class="systemitem">ksm</code> service. Stopping the services deactivates KSM but does not persist after restarting.
+ </div><pre class="screen">
+# service ksmtuned stop
+Stopping ksmtuned: [ OK ]
+# service ksm stop
+Stopping ksm: [ OK ]
+
+</pre><div class="para">
+ Persistently deactivate KSM with the <code class="command">chkconfig</code> command. To turn off the services, run the following commands:
+ </div><pre class="screen"># chkconfig ksm off
+# chkconfig ksmtuned off</pre><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Ensure the swap size is sufficient for the committed RAM even with KSM. KSM reduces the RAM usage of identical or similar guests. Overcommitting guests with KSM without sufficient swap space may be possible but is not recommended because guest memory use can result in pages becoming unshared.
+ </div></div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_GuideAdvanced" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 24. Advanced virtualization administration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#idm108086240">24.1. Control Groups (cgroups)</a></span></dt><dt><span class="section"><a href="#idm115160736">24.2. Hugepage support</a></span></dt></dl></div><div class="para">
+ This chapter covers advanced administration tools for fine tuning and controlling guests and host system resources.
+ </div><div class="section" id="idm108086240"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm108086240">24.1. Control Groups (cgroups)</h2></div></div></div><div class="para">
+ Fedora 19 provides a new kernel feature: <em class="firstterm">control groups</em>, which are often referred to as <em class="firstterm">cgroups</em>. Cgroups allow you to allocate resources such as CPU time, system memory, network bandwidth, or combinations of these resources among user-defined groups of tasks (processes) running on a system. You can monitor the cgroups you configure, deny cgroups access to certain resources, and even reconfigure your cgroups dynamically on a running system.
+ </div><div class="para">
+ The cgroup functionality is fully supported by libvirt. By default, libvirt puts each guest into a separate control group for various controllers (such as memory, cpu, blkio, device).
+ </div><div class="para">
+ When a guest is started, it is already in a cgroup. The only configuration that may be required is the setting of policies on the cgroups. Refer to the <em class="citetitle">Fedora Resource Management Guide</em> for more information on cgroups.
+ </div></div><div class="section" id="idm115160736"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm115160736">24.2. Hugepage support</h2></div></div></div><div class="formalpara"><h5 class="formalpara" id="idm106679360">Introduction</h5>
+ x86 CPUs usually address memory in 4kB pages, but they are capable of using larger pages known as <span class="bold bold"><strong>huge pages</strong></span>. KVM guests can be deployed with huge page memory support in order to reduce memory consumption and improve performance by reducing CPU cache usage.
+ </div><div class="para">
+ By using huge pages for a KVM guest, less memory is used for page tables and TLB (Translation Lookaside Buffer) misses are reduced, thereby significantly increasing performance, especially for memory-intensive situations.
+ </div><div class="para">
+ <span class="bold bold"><strong>Transparent Hugepage Support</strong></span> is a kernel feature that reduces TLB entries needed for an application. By also allowing all free memory to be used as cache, performance is increased.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm92548704">Using Transparent Hugepage Support</h5>
+ To use Transparent Hugepage Support, no special configuration in the <code class="filename">qemu.conf</code> file is required. Hugepages are used by default if <code class="filename">/sys/kernel/mm/redhat_transparent_hugepage/enabled</code> is set to <span class="bold bold"><strong>always</strong></span>.
+ </div><div class="para">
+ Transparent Hugepage Support does not prevent the use of hugetlbfs. However, when hugetlbfs is not used, KVM will use transparent hugepages instead of the regular 4kB page size.
+ </div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_Guide-Tips_and_tricks" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 25. Miscellaneous administration tasks</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Automatically_starting_guests">25.1. Automatically starting guests</a></span></dt><dt><span class="section"><a href="#sect-mem-dump-off">25.2. Guest memory allocation</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Using_qemu_img">25.3. Using qemu-img</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions">25.4. Verifying virtualization extensions</a></span></dt><dt><span class="section"><a href="#idm110949808">25.5. Setting KVM processor affinities</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_
tricks-Generating_a_new_unique_MAC_address">25.6. Generating a new unique MAC address</a></span></dt><dt><span class="section"><a href="#idm106199024">25.7. Improving guest response time</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests">25.8. Disable SMART disk monitoring for guests</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server">25.9. Configuring a VNC Server</a></span></dt><dt><span class="section"><a href="#sect-gracefully-shut-down-guests">25.10. Gracefully shutting down guests</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers">25.11. Virtual machine timer management with libvirt</a></span></dt><dt><span class="section"><a href="#sect-perf-mon">25.12. Using PMU to monitor guest performance</a></span></dt><dt><span class="section"><a href="#sect-s3-s4">25.13. Guest virtua
l machine power management</a></span></dt><dt><span class="section"><a href="#sect-qemu-ga">25.14. QEMU Guest Agent Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-guest-synch">25.14.1. guest-sync</a></span></dt><dt><span class="section"><a href="#subsect-guest-synch-delimited">25.14.2. guest-sync-delimited</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-limit-redirection">25.15. Setting a limit on device redirection</a></span></dt><dt><span class="section"><a href="#sect-dynamic-vNIC">25.16. Dynamically changing a host or a network bridge that is attached to a virtual NIC</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" id="sect-Virtualization-Tips_and_tricks-Automatically_starting_guests"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.1. Automatically starting guests</h2></div></div></div><div class="para">
+ This section covers how to make 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 class="section" id="sect-mem-dump-off"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.2. Guest memory allocation</h2></div></div></div><div class="para">
+ The following procedure shows how to allocate memory for a guest. This allocation and assignement works only at boot time and any changes to any of the memory values will not take effect until the next reboot.
+ </div><div class="para">
+ Valid memory units include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="parameter"><code>b</code></em> or <em class="parameter"><code>bytes</code></em> for bytes
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>KB</code></em> for kilobytes (10<sup>3</sup> or blocks of 1,000 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>k</code></em> or <em class="parameter"><code>KiB</code></em> for kibibytes (2<sup>10</sup> or blocks of 1024 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>MB</code></em> for megabytes (10<sup>6</sup> or blocks of 1,000,000 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>M</code></em> or <em class="parameter"><code>MiB</code></em> for mebibytes (2<sup>20</sup> or blocks of 1,048,576 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>GB</code></em> for gigabytes (10<sup>9</sup> or blocks of 1,000,000,000 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>G</code></em> or <em class="parameter"><code>GiB</code></em> for gibibytes (2<sup>30</sup> or blocks of 1,073,741,824 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>TB</code></em> for terabytes (10<sup>12</sup> or blocks of 1,000,000,000,000 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>T</code></em> or <em class="parameter"><code>TiB</code></em> for tebibytes (2<sup>40</sup> or blocks of 1,099,511,627,776 bytes)
+ </div></li></ul></div><div class="para">
+ Note that all values will be rounded up to the nearest kibibyte by libvirt, and may be further rounded to the granularity supported by the hypervisor. Some hypervisors also enforce a minimum, such as 4000KiB (or 4000 x 2<sup>10</sup> or 4,096,000 bytes). The units for this value are determined by the optional attribute <em class="parameter"><code>memory unit</code></em>, which defaults to the kibibytes (KiB) as a unit of measure where the value given is multiplied by 2<sup>10</sup> or blocks of 1024 bytes.
+ </div><div class="para">
+ In the cases where the guest crashes the optional attribute <em class="parameter"><code>dumpCore</code></em> can be used to control whether the guest's memory should be included in the generated coredump (<em class="parameter"><code>dumpCore='on'</code></em>) or not included (<em class="parameter"><code>dumpCore='off'</code></em>). Note that the default setting is <em class="parameter"><code>on</code></em> so if the parameter is not set to <em class="parameter"><code>off</code></em>, the guest memory will be included in the coredump file.
+ </div><div class="para">
+ The <em class="parameter"><code>currentMemory</code></em> attribute determines the actual memory allocation for a guest. This value can be less than the maximum allocation, to allow for ballooning up the guests memory on the fly. If this is omitted, it defaults to the same value as the memory element. The unit attribute behaves the same as for memory.
+ </div><div class="para">
+ In all cases for this section, the domain XML needs to be altered as follows:
+ </div><pre class="screen">
+<domain>
+
+ <memory unit='KiB' dumpCore='off'>524288</memory>
+ <!-- changes the memory unit to KiB and does not allow the guest's memory to be included in the generated coredump file -->
+ <currentMemory unit='KiB'>524288</currentMemory>
+ <!-- makes the current memory unit 524288 KiB -->
+ ...
+</domain>
+</pre></div><div class="section" id="sect-Virtualization-Tips_and_tricks-Using_qemu_img"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.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, modifying and verifying various file systems used by KVM. <code class="command">qemu-img</code> options and usages are listed below.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm102083280">Check</h5>
+ Perform a consistency check on the disk image <em class="replaceable"><code>filename</code></em>.
+ </div><pre class="screen">
+# qemu-img check [-f <em class="parameter"><code>format</code></em>] <em class="replaceable"><code>filename</code></em></pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Only the <em class="replaceable"><code>qcow2</code></em> and <em class="replaceable"><code>vdi</code></em> formats support consistency checks.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="idm93849088">Commit</h5>
+ Commit any changes recorded in the specified file (<em class="replaceable"><code>filename</code></em>) to the file's base image with the <code class="command">qemu-img commit</code> command. Optionally, specify the file's format type (<em class="replaceable"><code>fmt</code></em>).
+ </div><pre class="screen"> # qemu-img commit [-f <em class="parameter"><code>fmt</code></em>] [-t <em class="parameter"><code>cache</code></em>] <em class="replaceable"><code>filename</code></em>
+</pre><div class="formalpara" id="form-Virtualization-Using_qemu_img-Convert_an_existing_image_to_another_format"><h5 class="formalpara">Convert</h5>
+ The <em class="parameter"><code>convert</code></em> option is used to convert one recognized image format to another image format.
+ </div><div class="para">
+ Command format:
+ </div><pre class="screen"># qemu-img convert [-c] [-p] [-f <em class="parameter"><code>fmt</code></em>] [-t <em class="parameter"><code>cache</code></em>] [-O <em class="parameter"><code>output_fmt</code></em>] [-o <em class="parameter"><code>options</code></em>] [-S <em class="parameter"><code>sparse_size</code></em>] <em class="replaceable"><code>filename</code></em> <em class="replaceable"><code>output_filename</code></em></pre><div class="para">
+ The <em class="parameter"><code>-p</code></em> parameter shows the progress of the command (optional and not for every command) and <em class="parameter"><code>-S</code></em> indicates the consecutive number of bytes that must contain only zeros for <code class="command">qemu-img</code> to create a sparse image during conversion.
+ </div><div class="para">
+ Convert the disk image <em class="parameter"><code>filename</code></em> to disk image <em class="parameter"><code>output_filename</code></em> using format <em class="parameter"><code>output_format</code></em>. The disk image can be optionally compressed with the <em class="parameter"><code>-c</code></em> option, or encrypted with the <em class="parameter"><code>-o</code></em> option by setting <code class="code">-o encryption</code>. Note that the options available with the <em class="parameter"><code>-o</code></em> parameter differ with the selected format.
+ </div><div class="para">
+ Only the <code class="filename">qcow2</code> format supports encryption or compression. <code class="filename">qcow2</code> encryption uses the AES format with secure 128-bit keys. <code class="filename">qcow2</code> compression is read-only, so if a compressed sector is converted from <code class="filename">qcow2</code> format, it is written to the new format as uncompressed data.
+ </div><div class="para">
+ Image conversion is also useful to get a 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" id="form-Virtualization-Using_qemu_img-Formatting_and_creating_new_images_or_devices"><h5 class="formalpara">Create</h5>
+ Create the new disk image <em class="replaceable"><code>filename</code></em> of size <em class="parameter"><code>size</code></em> and format <em class="parameter"><code>format</code></em>.
+ </div><pre class="screen"># qemu-img create [-f <em class="parameter"><code>format</code></em>] [-o <em class="replaceable"><code>options</code></em>] <em class="replaceable"><code>filename</code></em> [<em class="parameter"><code>size</code></em>]
+</pre><div class="para">
+ If a base image is specified with <code class="code">-o backing_file=<em class="replaceable"><code>filename</code></em></code>, the image will only record differences between itself and the base image. The backing file will not be modified unless you use the <code class="command">commit</code> command. No size needs to be specified in this case.
+ </div><div class="formalpara" id="form-Virtualization-Using_qemu_img-getting_image_information"><h5 class="formalpara">Info</h5>
+ The <code class="command">info</code> parameter displays information about a disk image <em class="replaceable"><code>filename</code></em>. The format for the <code class="command">info</code> option is as follows:
+ </div><pre class="screen"># qemu-img info [-f <em class="replaceable"><code>format</code></em>] <em class="replaceable"><code>filename</code></em></pre><div class="para">
+ This command is often used to discover the size reserved on disk which can be different from the displayed size. If snapshots are stored in the disk image, they are displayed also.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm100397552">Rebase</h5>
+ Changes the backing file of an image.
+ </div><pre class="screen">
+# qemu-img rebase [-f <em class="replaceable"><code>fmt</code></em>] [-t <em class="replaceable"><code>cache</code></em>] [-p] [-u] -b <em class="replaceable"><code>backing_file</code></em> [-F <em class="replaceable"><code>backing_fmt</code></em>] <em class="replaceable"><code>filename</code></em></pre><div class="para">
+ The backing file is changed to <em class="replaceable"><code>backing_file</code></em> and (if the format of <em class="replaceable"><code>filename</code></em> supports the feature), the backing file format is changed to <em class="replaceable"><code>backing_format</code></em>.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Only the <em class="replaceable"><code>qcow2</code></em> format supports changing the backing file (rebase).
+ </div></div></div><div class="para">
+ There are two different modes in which <em class="replaceable"><code>rebase</code></em> can operate: <span class="bold bold"><strong>Safe</strong></span> and <span class="bold bold"><strong>Unsafe</strong></span>.
+ </div><div class="para">
+ <span class="bold bold"><strong>Safe mode</strong></span> is used by default and performs a real rebase operation. The new backing file may differ from the old one and the <code class="command">qemu-img rebase</code> command will take care of keeping the guest-visible content of <em class="replaceable"><code>filename</code></em> unchanged. In order to achieve this, any clusters that differ between <em class="replaceable"><code>backing_file</code></em> and old backing file of <em class="replaceable"><code>filename</code></em> are merged into <em class="replaceable"><code>filename</code></em> before making any changes to the backing file.
+ </div><div class="para">
+ Note that safe mode is an expensive operation, comparable to converting an image. The old backing file is required for it to complete successfully.
+ </div><div class="para">
+ <span class="bold bold"><strong>Unsafe mode</strong></span> is used if the <em class="replaceable"><code>-u</code></em> option is passed to <code class="command">qemu-img rebase</code>. In this mode, only the backing file name and format of <em class="replaceable"><code>filename</code></em> is changed, without any checks taking place on the file contents. Make sure the new backing file is specified correctly or the guest-visible content of the image will be corrupted.
+ </div><div class="para">
+ This mode is useful for renaming or moving the backing file. It can be used without an accessible old backing file. For instance, it can be used to fix an image whose backing file has already been moved or renamed.
+ </div><div class="formalpara"><h5 class="formalpara" id="idp82032">Resize</h5>
+ Change the disk image <em class="replaceable"><code>filename</code></em> as if it had been created with size <em class="replaceable"><code>size</code></em>. Only images in raw format can be resized regardless of version. Fedora 17 and later adds the ability to grow (but not shrink) images in qcow2 format.
+ </div><div class="para">
+ Use the following to set the size of the disk image <em class="replaceable"><code>filename</code></em> to <em class="replaceable"><code>size</code></em> bytes:
+ </div><pre class="screen"># qemu-img resize <em class="replaceable"><code>filename</code></em> <em class="replaceable"><code>size</code></em></pre><div class="para">
+ You can also resize relative to the current size of the disk image. To give a size relative to the current size, prefix the number of bytes with <code class="literal">+</code> to grow, or <code class="literal">-</code> to reduce the size of the disk image by that number of bytes. Adding a unit suffix allows you to set the image size in kilobytes (K), megabytes (M), gigabytes (G) or terabytes (T).
+ </div><pre class="screen"># qemu-img resize <em class="replaceable"><code>filename</code></em> [+|-]<em class="replaceable"><code>size</code></em>[K|M|G|T]</pre><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Before using this command to shrink a disk image, you <span class="emphasis"><em>must</em></span> use file system and partitioning tools inside the VM itself to reduce allocated file systems and partition sizes accordingly. Failure to do so will result in data loss.
+ </div><div class="para">
+ After using this command to grow a disk image, you must use file system and partitioning tools inside the VM to actually begin using the new space on the device.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="idm77720416">Snapshot</h5>
+ List, apply, create, or delete an existing snapshot (<em class="replaceable"><code>snapshot</code></em>) of an image (<em class="replaceable"><code>filename</code></em>).
+ </div><pre class="screen"># qemu-img snapshot [ -l | -a <em class="replaceable"><code>snapshot</code></em> | -c <em class="replaceable"><code>snapshot</code></em> | -d <em class="replaceable"><code>snapshot</code></em> ] <em class="replaceable"><code>filename</code></em>
+</pre><div class="para">
+ <code class="command">-l</code> lists all snapshots associated with the specified disk image. The apply option, <code class="command">-a</code>, reverts the disk image (<em class="replaceable"><code>filename</code></em>) to the state of a previously saved <em class="replaceable"><code>snapshot</code></em>. <code class="command">-c</code> creates a snapshot (<em class="replaceable"><code>snapshot</code></em>) of an image (<em class="replaceable"><code>filename</code></em>). <code class="command">-d</code> deletes the specified snapshot.
+ </div><div class="formalpara" id="form-Virtualization-Using_qemu_img-Supported_formats"><h5 class="formalpara">Supported formats</h5>
+ <span class="application"><strong>qemu-img</strong></span> is designed to convert files to one of the following formats:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="command">raw</code> </span></dt><dd><div class="para">
+ Raw disk image format (default). This can be the fastest file-based format. 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 obtain the real size used by the image or <code class="command">ls -ls</code> on Unix/Linux. Although Raw images give optimal performance, only very basic features are available with a Raw image (no snapshots etc.).
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">qcow2</code> </span></dt><dd><div class="para">
+ QEMU image format, the most versatile format with the best feature set. Use it to have optional AES encryption, zlib-based compression, support of multiple VM snapshots, and smaller images, which are useful on file systems that do not support holes (non-NTFS file systems on Windows). Note that this expansive feature set comes at the cost of performance.
+ </div></dd></dl></div><div class="para">
+ Although only the formats above can be used to run on a guest or host machine, <span class="application"><strong>qemu-img</strong></span> also recognizes and supports the following formats in order to convert from them into either <code class="command">raw</code> or <code class="command">qcow2</code> format. The format of an image is usually detected automatically. In addition to converting these formats into <code class="command">raw</code> or <code class="command">qcow2</code> , they can be converted back from <code class="command">raw</code> or <code class="command">qcow2</code> to the original format.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="command">bochs</code></span></dt><dd><div class="para">
+ Bochs disk image format.
+ </div></dd><dt class="varlistentry"><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><dt class="varlistentry"><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 class="varlistentry"><span class="term"><code class="command">dmg</code></span></dt><dd><div class="para">
+ Mac disk image format.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">nbd</code></span></dt><dd><div class="para">
+ Network block device.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">parallels</code></span></dt><dd><div class="para">
+ Parallels virtualization disk image format.
+ </div></dd><dt class="varlistentry"><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 class="varlistentry"><span class="term"><code class="command">vdi</code></span></dt><dd><div class="para">
+ Oracle VM VirtualBox hard disk image format.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">vmdk</code></span></dt><dd><div class="para">
+ VMware 3 and 4 compatible image format.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">vpc</code></span></dt><dd><div class="para">
+ Windows Virtual PC disk image format. Also referred to as <code class="literal">vhd</code>, or Microsoft virtual hard disk image format.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">vvfat</code></span></dt><dd><div class="para">
+ Virtual VFAT disk image format.
+ </div></dd></dl></div></div><div class="section" id="sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.4. 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-x or AMD-V) are required for full virtualization.
+ </div><div class="procedure"><ol class="1"><li class="step"><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></li><li class="step"><div class="para">
+ Analyze the output.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The following output contains a <code class="computeroutput">vmx</code> entry indicating an Intel processor with the Intel VT-x extension:
+ </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></li><li class="listitem"><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></li></ul></div><div class="para">
+ If any output is received, the processor has the hardware virtualization extensions. However in some circumstances manufacturers disable the virtualization extensions in BIOS.
+ </div><div class="para">
+ The "<code class="computeroutput">flags:</code>" output content may appear multiple times, once for each hyperthread, core or CPU on 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="#proc-Virtualization-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS-Enabling_virtualization_extensions_in_BIOS">Procedure A.1, “Enabling virtualization extensions in BIOS”</a>.
+ </div></li><li class="step"><p class="title"><strong>Ensure KVM subsystem is loaded</strong></p><div class="para">
+ As an additional check, verify that the <code class="computeroutput">kvm</code> modules are loaded in the kernel:
+ </div><pre class="screen"># lsmod | grep kvm</pre><div class="para">
+ If the output includes <code class="computeroutput">kvm_intel</code> or <code class="computeroutput">kvm_amd</code> then the <code class="computeroutput">kvm</code> hardware virtualization modules are loaded and your system meets requirements.
+ </div></li></ol></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If the <span class="package">libvirt</span> package is installed, the <code class="command">virsh</code> command can output a full list of virtualization system capabilities. Run <code class="command">virsh capabilities </code> as root to receive the complete list.
+ </div></div></div></div><div xml:lang="en-US" class="section" id="idm110949808" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm110949808">25.5. Setting KVM processor affinities</h2></div></div></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ <span class="application"><strong>libvirt</strong></span> refers to a NUMA node as a <span class="emphasis"><em>cell</em></span>.
+ </div></div></div><div class="para">
+ This section covers setting processor and processing core affinities with <span class="application"><strong>libvirt</strong></span> and KVM guests.
+ </div><div class="para">
+ By default, libvirt provisions guests using the hypervisor's default policy. For most hypervisors, the policy is to run guests on any available processing core or CPU. There are times when an explicit policy may be better, particularly for systems with a NUMA (Non-Uniform Memory Access) architecture. A guest on a NUMA system can be pinned to a processing core so that its memory allocations are always local to the node it is running on. This avoids cross-node memory transports which have less bandwidth and can significantly degrade performance.
+ </div><div class="para">
+ On non-NUMA systems some form of explicit placement across the hosts’ sockets, cores and hyperthreads may be more efficient.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm112742848">Identifying CPU and NUMA topology</h5>
+ The first step in deciding which policy to apply is to determine the host’s memory and CPU topology. The <code class="command">virsh nodeinfo</code> command provides information about how many sockets, cores and hyperthreads are attached to a host.
+ </div><pre class="screen"># virsh nodeinfo
+CPU model: x86_64
+CPU(s): 8
+CPU frequency: 1000 MHz
+CPU socket(s): 2
+Core(s) per socket: 4
+Thread(s) per core: 1
+NUMA cell(s): 2
+Memory size: 8179176 kB</pre><div class="para">
+ This output shows that the system has eight CPU cores and two sockets. Each CPU socket has four cores. This splitting of CPU cores across multiple sockets suggests that the system has Non-Uniform Memory Access (NUMA) architecture.
+ </div><div class="para">
+ NUMA architecture can be more complex than other architectures. Use the <code class="command">virsh capabilities</code> command to get additional output data about the CPU configuration.
+ </div><pre class="programlisting"># virsh capabilities
+<capabilities>
+ <host>
+ <cpu>
+ <arch>x86_64</arch>
+ </cpu>
+ <migration_features>
+ <live/>
+ <uri_transports>
+ <uri_transport>tcp</uri_transport>
+ </uri_transports>
+ </migration_features>
+ <topology>
+ <cells num='2'>
+ <cell id='0'>
+ <cpus num='4'>
+ <cpu id='0'/>
+ <cpu id='1'/>
+ <cpu id='2'/>
+ <cpu id='3'/>
+ </cpus>
+ </cell>
+ <cell id='1'>
+ <cpus num='4'>
+ <cpu id='4'/>
+ <cpu id='5'/>
+ <cpu id='6'/>
+ <cpu id='7'/>
+ </cpus>
+ </cell>
+ </cells>
+ </topology>
+ <secmodel>
+ <model>selinux</model>
+ <doi>0</doi>
+ </secmodel>
+ </host>
+
+ <span class="emphasis"><em>[ Additional XML removed ]</em></span>
+
+</capabilities></pre><div class="para">
+ This output shows two NUMA nodes (also know as NUMA cells), each containing four logical CPUs (four processing cores). This system has two sockets, therefore it can be inferred that each socket is a separate NUMA node. For a guest with four virtual CPUs, it is optimal to lock the guest to physical CPUs 0 to 3, or 4 to 7, to avoid accessing non-local memory, which is significantly slower than accessing local memory.
+ </div><div class="para">
+ If a guest requires eight virtual CPUs, you could run two sets of four virtual CPU guests and split the work between them, since each NUMA node only has four physical CPUs. Running across multiple NUMA nodes significantly degrades performance for physical and virtualized tasks.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm109137072">Decide which NUMA node can run the guest</h5>
+ Locking a guest to a particular NUMA node offers no benefit if that node does not have sufficient free memory for that guest. libvirt stores information on the free memory available on each node. Use the <code class="command">virsh freecell --all</code> command to display the free memory on all NUMA nodes.
+ </div><pre class="screen"># virsh freecell --all
+0: 2203620 kB
+1: 3354784 kB</pre><div class="para">
+ If a guest requires 3 GB of RAM allocated, then the guest should be run on NUMA node (cell) 1. Node 0 only has 2.2GB free which may not be sufficient for certain guests.
+ </div><div class="formalpara"><h5 class="formalpara" id="idp79840">Lock a guest to a NUMA node or physical CPU set</h5>
+ Once you have determined which node to run the guest on, refer to the capabilities data (the output of the <code class="command">virsh capabilities</code> command) about NUMA topology.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Extract from the <code class="command">virsh capabilities</code> output.
+ </div><pre class="screen"><topology>
+ <cells num='2'>
+ <cell id='0'>
+ <cpus num='4'>
+ <cpu id='0'/>
+ <cpu id='1'/>
+ <cpu id='2'/>
+ <cpu id='3'/>
+ </cpus>
+ </cell>
+ <cell id='1'>
+ <cpus num='4'>
+ <cpu id='4'/>
+ <cpu id='5'/>
+ <cpu id='6'/>
+ <cpu id='7'/>
+ </cpus>
+ </cell>
+ </cells>
+</topology></pre></li><li class="step"><div class="para">
+ Observe that the node 1, <code class="computeroutput"><cell id='1'></code>, uses physical CPUs 4 to 7.
+ </div></li><li class="step"><div class="para">
+ The guest can be locked to a set of CPUs by appending the <code class="computeroutput">cpuset</code> attribute to the configuration file.
+ </div><ol class="a"><li class="step"><div class="para">
+ While the guest is offline, open the configuration file with <code class="command">virsh edit</code>.
+ </div></li><li class="step"><div class="para">
+ Locate the guest's virtual CPU count, defined in the <code class="computeroutput">vcpus</code> element.
+ </div><pre class="screen"><vcpus>4</vcpus></pre><div class="para">
+ The guest in this example has four CPUs.
+ </div></li><li class="step"><div class="para">
+ Add a <code class="computeroutput">cpuset</code> attribute with the CPU numbers for the relevant NUMA cell.
+ </div><pre class="screen"><vcpus cpuset='4-7'>4</vcpus></pre></li></ol></li><li class="step"><div class="para">
+ Save the configuration file and restart the guest.
+ </div></li></ol></div><div class="para">
+ The guest has been locked to CPUs 4 to 7.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm76092208">Automatically locking guests to CPUs with virt-install</h5>
+ The <code class="command">virt-install</code> provisioning tool provides a simple way to automatically apply a 'best fit' NUMA policy when guests are created.
+ </div><div class="para">
+ The <em class="parameter"><code>cpuset</code></em> option for <code class="command">virt-install</code> can use a CPU set of processors or the parameter <em class="parameter"><code>auto</code></em>. The <em class="parameter"><code>auto</code></em> parameter automatically determines the optimal CPU locking using the available NUMA data.
+ </div><div class="para">
+ For a NUMA system, use the <em class="parameter"><code>--cpuset=auto</code></em> with the <code class="command">virt-install</code> command when creating new guests.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm100396672">Tuning CPU affinity on running guests</h5>
+ There may be times where modifying CPU affinities on running guests is preferable to rebooting the guest. The <code class="command">virsh vcpuinfo</code> and <code class="command">virsh vcpupin</code> commands can perform CPU affinity changes on running guests.
+ </div><div class="para">
+ The <code class="command">virsh vcpuinfo</code> command gives up to date information about where each virtual CPU is running.
+ </div><div class="para">
+ In this example, <em class="replaceable"><code>guest1</code></em> is a guest with four virtual CPUs is running on a KVM host.
+ </div><pre class="screen"># virsh vcpuinfo <em class="replaceable"><code>guest1</code></em>
+VCPU: 0
+CPU: 3
+State: running
+CPU time: 0.5s
+CPU Affinity: yyyyyyyy
+VCPU: 1
+CPU: 1
+State: running
+CPU Affinity: yyyyyyyy
+VCPU: 2
+CPU: 1
+State: running
+CPU Affinity: yyyyyyyy
+VCPU: 3
+CPU: 2
+State: running
+CPU Affinity: yyyyyyyy</pre><div class="para">
+ The <code class="command">virsh vcpuinfo</code> output (the <code class="computeroutput">yyyyyyyy</code> value of <code class="computeroutput">CPU Affinity</code>) shows that the guest can presently run on any CPU.
+ </div><div class="para">
+ To lock the virtual CPUs to the second NUMA node (CPUs four to seven), run the following commands.
+ </div><pre class="screen"># virsh vcpupin <em class="replaceable"><code>guest1</code></em> 0 4
+# virsh vcpupin <em class="replaceable"><code>guest1</code></em> 1 5
+# virsh vcpupin <em class="replaceable"><code>guest1</code></em> 2 6
+# virsh vcpupin <em class="replaceable"><code>guest1</code></em> 3 7</pre><div class="para">
+ The <code class="command">virsh vcpuinfo</code> command confirms the change in affinity.
+ </div><pre class="screen"># virsh vcpuinfo <em class="replaceable"><code>guest1</code></em>
+VCPU: 0
+CPU: 4
+State: running
+CPU time: 32.2s
+CPU Affinity: ----y---
+VCPU: 1
+CPU: 5
+State: running
+CPU time: 16.9s
+CPU Affinity: -----y--
+VCPU: 2
+CPU: 6
+State: running
+CPU time: 11.9s
+CPU Affinity: ------y-
+VCPU: 3
+CPU: 7
+State: running
+CPU time: 14.6s
+CPU Affinity: -------y</pre></div><div class="section" id="sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.6. Generating a new unique MAC address</h2></div></div></div><div class="para">
+ In some cases you will need to generate a new and unique MAC address 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</pre><pre class="screen">#!/usr/bin/python
+# macgen.py script to generate a MAC address for guests
+#
+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" id="form-Virtualization-Generating_a_new_unique_MAC_address-Another_method_to_generate_a_new_MAC_for_your_guest"><h5 class="formalpara">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><div class="section" id="idm106199024"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm106199024">25.7. Improving guest response time</h2></div></div></div><div class="para">
+ Guests can sometimes be slow to respond with certain workloads and usage patterns. Examples of situations which may cause slow or unresponsive guests:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Severely overcommitted memory.
+ </div></li><li class="listitem"><div class="para">
+ Overcommitted memory with high processor usage
+ </div></li><li class="listitem"><div class="para">
+ Other (not <code class="command">qemu-kvm</code> processes) busy or stalled processes on the host.
+ </div></li></ul></div><div class="para">
+ These types of workload may cause guests to appear slow or unresponsive. Usually, the guest's memory is eventually fully loaded into the host's main memory from swap. Once the guest is loaded in main memory, the guest will perform normally. Note, the process of loading a guest from swap to main memory may take several seconds per gigabyte of RAM assigned to the guest, depending on the type of storage used for swap and the performance of the components.
+ </div><div class="para">
+ KVM guests function as Linux processes. Linux processes are not permanently kept in main memory (physical RAM). The kernel scheduler swaps process memory into virtual memory (swap). Swap, with conventional hard disk drives, is thousands of times slower than main memory in modern computers. If a guest is inactive for long periods of time, the guest may be placed into swap by the kernel.
+ </div><div class="para">
+ KVM guests processes may be moved to swap regardless of whether memory is overcommitted or overall memory usage.
+ </div><div class="para">
+ Using unsafe overcommit levels or overcommitting with swap turned off guest processes or other critical processesis not recommended. Always ensure the host has sufficient swap space when overcommitting memory.
+ </div><div class="para">
+ For more information on overcommitting with KVM, refer to <a class="xref" href="#sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM">Chapter 22, <em>Overcommitting with KVM</em></a>.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Virtual memory allows a Linux system to use more memory than there is physical RAM on the system. Underused processes are swapped out which allows active processes to use memory, improving memory utilization. Disabling swap reduces memory utilization as all processes are stored in physical RAM.
+ </div><div class="para">
+ If swap is turned off, do not overcommit guests. Overcommitting guests without any swap can cause guests or the host system to crash.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="idm111750496">Turning off swap</h5>
+ Swap usage can be completely turned off to prevent guests from being unresponsive while they are moved back to main memory. Swap may also not be desired for guests as it can be resource-intensive on some systems.
+ </div><div class="para">
+ The <code class="command">swapoff</code> command can disable all swap partitions and swap files on a system.
+ </div><pre class="screen"># swapoff -a</pre><div class="para">
+ To make this change permanent, remove <em class="parameter"><code>swap</code></em> lines from the <code class="filename">/etc/fstab</code> file and restart the host system.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm90320944">Using SSDs for swap</h5>
+ Using Solid State Drives (SSDs) for swap storage may improve the performance of guests.
+ </div><div class="para">
+ Using RAID arrays, faster disks or separate drives dedicated to swap may also improve performance.
+ </div></div><div class="section" id="sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.8. Disable SMART disk monitoring for guests</h2></div></div></div><div class="para">
+ SMART disk monitoring can be safely disabled as virtual disks and the physical storage devices are managed by the host.
+ </div><pre class="screen"># service smartd stop
+# chkconfig --del smartd
+</pre></div><div class="section" id="sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.9. 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">
+ Use the following step set up a dedicated VNC server session:
+ </div><div class="para">
+ If needed, Create and then 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. For more information on vnc server files refer to the <em class="citetitle">Fedora Installation Guide</em>.
+ </div></div><div class="section" id="sect-gracefully-shut-down-guests"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.10. Gracefully shutting down guests</h2></div></div></div><div class="para">
+ Installing virtualized Fedora 19 guests with the <code class="option">Minimal installation</code> option will not install the <span class="package">acpid</span> package.
+ </div><div class="para">
+ Without the <span class="package">acpid</span> package, the Fedora guest does not shut down when the <code class="command">virsh shutdown</code> command is executed. The <code class="command">virsh shutdown</code> command is designed to gracefully shut down guests.
+ </div><div class="para">
+ Using <code class="command">virsh shutdown</code> is easier and safer for system administration. Without graceful shut down with the <code class="command">virsh shutdown</code> command a system administrator must log into a guest manually or send the <span class="keycap"><strong>Ctrl</strong></span>-<span class="keycap"><strong>Alt</strong></span>-<span class="keycap"><strong>Del</strong></span> key combination to each guest.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Other virtualized operating systems may be affected by this issue. The <code class="command">virsh shutdown</code> command requires that the guest operating system is configured to handle ACPI shut down requests. Many operating systems require additional configuration on the guest operating system to accept ACPI shut down requests.
+ </div></div></div><div class="procedure"><h6>Procedure 25.1. Workaround for Fedora</h6><ol class="1"><li class="step"><p class="title"><strong>Install the acpid package</strong></p><div class="para">
+ The <code class="command">acpid</code> service listen and processes ACPI requests.
+ </div><div class="para">
+ Log into the guest and install the <span class="package">acpid</span> package on the guest:
+ </div><pre class="screen"># yum install acpid</pre></li><li class="step"><p class="title"><strong>Enable the acpid service</strong></p><div class="para">
+ Set the <code class="systemitem">acpid</code> service to start during the guest boot sequence and start the service:
+ </div><pre class="screen"># chkconfig acpid on
+# service acpid start</pre></li></ol></div><div class="para">
+ The guest is now configured to shut down when the <code class="command">virsh shutdown</code> command is used.
+ </div></div><div class="section" id="sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.11. Virtual machine timer management with libvirt</h2></div></div></div><div class="para">
+ Accurate time keeping on guests is a key challenge for virtualization platforms. Different hypervisors attempt to handle the problem of time keeping in a variety of ways. Libvirt provides hypervisor independent configuration settings for time management, using the <clock> and <timer> elements in the domain XML. The domain XML can be edited using the <code class="command">virsh edit</code> command. See <a class="xref" href="#form-Virtualization-Managing_guests_with_virsh-Editing_a_guests_configuration_file">Editing a guest's configuration file</a> for details.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm76550112"><clock></h5>
+ The clock element is used to determine how the guest clock is synchronized with the host clock. The clock element has the following attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm34843472">offset</h5>
+ Determines how the guest clock is offset from the host clock. The offset attribute has the following possible values:
+ </div><div class="table" id="clock_element_offset_attribute_values"><h6>Table 25.1. Offset attribute values</h6><div class="table-contents"><table summary="Offset attribute values" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Value
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ utc
+ </td><td class="">
+ The guest clock will be synchronized to UTC when booted.
+ </td></tr><tr><td class="">
+ localtime
+ </td><td class="">
+ The guest clock will be synchronized to the host's configured timezone when booted, if any.
+ </td></tr><tr><td class="">
+ timezone
+ </td><td class="">
+ The guest clock will be synchronized to a given timezone, specified by the <em class="parameter"><code>timezone</code></em> attribute.
+ </td></tr><tr><td class="">
+ variable
+ </td><td class="">
+ The guest clock will be synchronized to an arbitrary offset from UTC. The delta relative to UTC is specified in seconds, using the <em class="parameter"><code>adjustment</code></em> attribute. The guest is free to adjust the Real Time Clock (RTC) over time and expect that it will be honored following the next reboot. This is in contrast to <em class="parameter"><code>utc</code></em> mode, where any RTC adjustments are lost at each reboot.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The value <span class="bold bold"><strong>utc</strong></span> is set as the clock offset in a virtual machine by default. However, if the guest clock is run with the <span class="bold bold"><strong>localtime</strong></span> value, the clock offset needs to be changed to a different value in order to have the guest clock synchronized with the host clock.
+ </div></div></div></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm103316640">timezone</h5>
+ The timezone to which the guest clock is to be synchronized.
+ </div></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm103314752">adjustment</h5>
+ The delta for guest clock synchronization. In seconds, relative to UTC.
+ </div></li></ul></div><div class="example"><h6>Example 25.1. Always synchronize to UTC</h6><div class="example-contents"><pre class="screen"><clock offset="utc" /></pre></div></div><br class="example-break" /><div class="example"><h6>Example 25.2. Always synchronize to the host timezone</h6><div class="example-contents"><pre class="screen"><clock offset="localtime" /></pre></div></div><br class="example-break" /><div class="example"><h6>Example 25.3. Synchronize to an arbitrary timezone</h6><div class="example-contents"><pre class="screen"><clock offset="timezone" timezone="Europe/Paris" /></pre></div></div><br class="example-break" /><div class="example"><h6>Example 25.4. Synchronize to UTC + arbitrary offset</h6><div class="example-contents"><pre class="screen"><clock offset="variable" adjustment="123456" /></pre></div></div><br class="example-break" /><div class="formalpara"><h5 class="formalpara" id="idm109929984"><timer></h5>
+ A clock element can have zero or more timer elements as children. The timer element specifies a time source used for guest clock synchronization. The timer element has the following attributes. Only the <em class="parameter"><code>name</code></em> is required, all other attributes are optional.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm95408896">name</h5>
+ The name of the time source to use.
+ </div><div class="table" id="timer_element_name_attribute_values"><h6>Table 25.2. name attribute values</h6><div class="table-contents"><table summary="name attribute values" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Value
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ platform
+ </td><td class="">
+ The master virtual time source which may be used to drive the policy of other time sources.
+ </td></tr><tr><td class="">
+ pit
+ </td><td class="">
+ Programmable Interval Timer - a timer with periodic interrupts.
+ </td></tr><tr><td class="">
+ rtc
+ </td><td class="">
+ Real Time Clock - a continuously running timer with periodic interrupts.
+ </td></tr><tr><td class="">
+ hpet
+ </td><td class="">
+ High Precision Event Timer - multiple timers with periodic interrupts.
+ </td></tr><tr><td class="">
+ tsc
+ </td><td class="">
+ Time Stamp Counter - counts the number of ticks since reset, no interrupts.
+ </td></tr><tr><td class="">
+ kvmclock
+ </td><td class="">
+ KVM clock - recommended clock source for KVM guests. KVM pvclock, or kvm-clock lets guests read the host’s wall clock time.
+ </td></tr></tbody></table></div></div><br class="table-break" /></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm87467184">track</h5>
+ The <span class="emphasis"><em>track</em></span> attribute specifies what is tracked by the timer. Only valid for a name value of <em class="parameter"><code>platform</code></em> or <em class="parameter"><code>rtc</code></em>.
+ </div><div class="table" id="timer_element_track_attribute_values"><h6>Table 25.3. track attribute values</h6><div class="table-contents"><table summary="track attribute values" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Value
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ boot
+ </td><td class="">
+ Corresponds to old <span class="emphasis"><em>host</em></span> option, this is an unsupported tracking option.
+ </td></tr><tr><td class="">
+ guest
+ </td><td class="">
+ RTC always tracks guest time.
+ </td></tr><tr><td class="">
+ wall
+ </td><td class="">
+ RTC always tracks host time.
+ </td></tr></tbody></table></div></div><br class="table-break" /></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm85676304">tickpolicy</h5>
+ The policy used to pass ticks on to the guest.
+ </div><div class="table" id="timer_element_policy_attribute_values"><h6>Table 25.4. tickpolicy attribute values</h6><div class="table-contents"><table summary="tickpolicy attribute values" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Value
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ delay
+ </td><td class="">
+ Continue to deliver at normal rate (i.e. ticks are delayed).
+ </td></tr><tr><td class="">
+ catchup
+ </td><td class="">
+ Deliver at a higher rate to catch up.
+ </td></tr><tr><td class="">
+ merge
+ </td><td class="">
+ Ticks merged into one single tick.
+ </td></tr><tr><td class="">
+ discard
+ </td><td class="">
+ All missed ticks are discarded.
+ </td></tr></tbody></table></div></div><br class="table-break" /></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm109094336">frequency</h5>
+ Used to set a fixed frequency, measured in Hz. This attribute is only relevant for a name value of <em class="parameter"><code>tsc</code></em>. All other timers operate at a fixed frequency (<em class="parameter"><code>pit</code></em>, <em class="parameter"><code>rtc</code></em>), or at a frequency fully controlled by the guest (<em class="parameter"><code>hpet</code></em>).
+ </div></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm85764432">mode</h5>
+ Determines how the time source is exposed to the guest. This attribute is only relevant for a name value of <em class="parameter"><code>tsc</code></em>. All other timers are always emulated. Command is as follows: <code class="command"><timer name='tsc' frequency='NNN' mode='auto|native|emulate|smpsafe'/></code>. Mode definitions are given in the table.
+ </div><div class="table" id="timer_element_mode_attribute_values"><h6>Table 25.5. mode attribute values</h6><div class="table-contents"><table summary="mode attribute values" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Value
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ auto
+ </td><td class="">
+ Native if TSC is unstable, otherwise allow native TSC access.
+ </td></tr><tr><td class="">
+ native
+ </td><td class="">
+ Always allow native TSC access.
+ </td></tr><tr><td class="">
+ emulate
+ </td><td class="">
+ Always emulate TSC.
+ </td></tr><tr><td class="">
+ smpsafe
+ </td><td class="">
+ Always emulate TSC and interlock SMP
+ </td></tr></tbody></table></div></div><br class="table-break" /></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm103019312">present</h5>
+ Used to override the default set of timers visible to the guest. For example, to enable or disable the HPET.
+ </div><div class="table" id="timer_element_present_attribute_values"><h6>Table 25.6. present attribute values</h6><div class="table-contents"><table summary="present attribute values" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Value
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ yes
+ </td><td class="">
+ Force this timer to the visible to the guest.
+ </td></tr><tr><td class="">
+ no
+ </td><td class="">
+ Force this timer to not be visible to the guest.
+ </td></tr></tbody></table></div></div><br class="table-break" /></li></ul></div><div class="example"><h6>Example 25.5. Clock synchronizing to local time with RTC and PIT timers, and the HPET timer disabled</h6><div class="example-contents"><pre class="screen"><clock offset="localtime">
+ <timer name="rtc" tickpolicy="catchup" track="guest" />
+ <timer name="pit" tickpolicy="delay" />
+ <timer name="hpet" present="no" />
+</clock></pre></div></div><br class="example-break" /></div><div class="section" id="sect-perf-mon"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.12. Using PMU to monitor guest performance</h2></div></div></div><div class="para">
+ In Fedora 18 and onward, vPMU (virtual PMU )was introduced as technical-preview. vPMU is based on Intel's PMU (Performance Monitoring Units) and may only be used on Intel machines. PMU allows the tracking of statistics which indicate how a guest virtual machine is functioning.
+ </div><div class="para">
+ Using performance monitoring, allows developers to use the CPU's PMU counter while using the performance tool for profiling. The virtual performance monitoring unit feature allows virtual machine users to identify sources of possible performance problems in their guest virtual machines, thereby improving the ability to profile a KVM guest virtual machine.
+ </div><div class="para">
+ To enable the feature, the <code class="command">-cpu host </code>flag must be set.
+ </div><div class="para">
+ This feature is only supported with guests running Fedora and is disabled by default. This feature only works using the Linux perf tool. Make sure the <span class="package">perf</span> package is installed using the command:
+ </div><pre class="screen">#<code class="command"> yum install perf</code>.</pre><div class="para">
+ See the man page on <code class="command">perf</code> for more information on the perf commands.
+ </div></div><div class="section" id="sect-s3-s4"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.13. Guest virtual machine power management</h2></div></div></div><div class="para">
+ It is possible to forcibly enable or disable BIOS advertisements to the guest virtual machine's operating system by changing the following parameters in the Domain XML for Libvirt:
+ </div><pre class="screen">
+...
+ <pm>
+ <suspend-to-disk enabled='no'/>
+ <suspend-to-mem enabled='yes'/>
+ </pm>
+ ...
+</pre><div class="para">
+ The element <em class="parameter"><code>pm</code></em> enables ('yes') or disables ('no') BIOS support for S3 (suspend-to-disk) and S4 (suspend-to-mem) ACPI sleep states. If nothing is specified, then the hypervisor will be left with its default value.
+ </div></div><div class="section" id="sect-qemu-ga"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.14. QEMU Guest Agent Protocol</h2></div></div></div><div class="para">
+ The QEMU guest agent protocol (QEMU-ga), uses the same protocol as QMP. <span class="package">qemu-ga</span>. There are a couple issues regarding its isa-serial/virtio-serial transport, and the following caveats have been noted:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ There is no way for <span class="package">qemu-ga</span> to detect whether or not a client has connected to the channel.
+ </div></li><li class="listitem"><div class="para">
+ There is no way for a client to detect whether or not <span class="package">qemu-ga</span> has disconnected or reconnected to the backend.
+ </div></li><li class="listitem"><div class="para">
+ If the virtio-serial device resets and <span class="package">qemu-ga</span> has not connected to the channel as a result, (generally caused by a reboot or hotplug), data from the client will be dropped.
+ </div></li><li class="listitem"><div class="para">
+ If <span class="package">qemu-ga</span> has connected to the channel following a virtio-serial device reset, data from the client will be queued (and eventually throttled if available buffers are exhausted), regardless of whether or not <span class="package">qemu-ga</span> is still running/connected.
+ </div></li></ul></div><div class="para">
+ qemu-ga uses the guest-sync or guest-sync-delimited command to address the problem of re-synchronizing the channel after re-connection or client-side timeouts. These are described below.
+ </div><div class="section" id="sect-guest-synch"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">25.14.1. guest-sync</h3></div></div></div><div class="para">
+ The guest-sync request/response exchange is simple. The client provides a unique numerical token, the agent sends it back in a response:
+ </div><pre class="screen">
+ > { "execute": "guest-sync", "arguments": { "id": 123456 } }
+ < { "return": 123456}
+</pre><div class="para">
+ A successful exchange guarantees that the channel is now in sync and no unexpected data/responses will be sent. Note that for the reasons mentioned above there's no guarantee this request will be answered, so a client should implement a timeout and re-issue this periodically until a response is received for the most recent request.
+ </div><div class="para">
+ This alone does not handle synchronization issues in all cases. For example, if <span class="package">qemu-ga</span>'s parser previously received a partial request from a previous client connection, subsequent attempts to issue the guest-sync request can be misconstrued as being part of the previous partial request. Eventually <span class="package">qemu-ga</span> will hit it's recursion or token size limit and flush its parser state, at which point it will begin processing the backlog of requests, but there's no guarantee this will occur before the channel is throttled due to exhausting all available buffers. Thus, there is a potential for a deadlock situation occurring for certain instances.
+ </div><div class="para">
+ To avoid this, <span class="package">qemu-ga/QEMU</span>'s JSON parser has special handling for the 0xFF byte, which is an invalid UTF-8 character. Client requests should precede the guest-sync request with to ensure that <span class="package">qemu-ga</span> flushes it's parser state as soon as possible. As long as all clients abide by this, the deadlock state should be reliably avoidable.
+ </div><div class="para">
+ For more information see the qemu-ga wiki page on <a href="http://wiki.qemu.org/Features/QAPI/GuestAgent">wiki.qemu.org</a>.
+ </div></div><div class="section" id="subsect-guest-synch-delimited"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">25.14.2. guest-sync-delimited</h3></div></div></div><div class="para">
+ If <span class="package">qemu-ga</span> attempts to communicate with a client, and the client receives a partial response from a previous <span class="package">qemu-ga</span> instance, the client might misconstrue responses to guest-sync as being part of this previous request. For client implementations that treat newlines as a delimiter for <span class="package">qemu-ga</span> responses, use <code class="command">guest-synch-delimited</code>.
+ </div><div class="para">
+ Even in some cases where there are JSON stream-based implementations that do not rely on newline delimiters, it may be considered invasive to implement a client's response/JSON handling, as it is the same deadlock scenario described previously. Using the <code class="command">guest-sync-delimited</code> on the client, tells qemu-ga to place the same 0xFF character in front of the response, thereby preventing confusion.
+ </div><pre class="screen">
+> { "execute": "guest-sync-delimited", "arguments": { "id": 123456 } }
+< { "return": 123456}
+</pre><div class="para">
+ Actual hex values sent:
+ </div><pre class="screen">
+> 7b 27 65 78 65 63 75 74 65 27 3a 27 67 75 65 73 74 2d 73 79 6e 63 2d 64 65
+ 6c 69 6d 69 74 65 64 27 2c 27 61 72 67 75 6d 65 6e 74 73 27 3a 7b 27 69 64
+ 27 3a 31 32 33 34 35 36 7d 7d 0a
+< ff 7b 22 72 65 74 75 72 6e 22 3a 20 31 32 33 34 35 36 7d 0a
+</pre><div class="para">
+ As stated above, the request should also be preceded with a 0xFF to flush <span class="package">qemu-ga</span>'s parser state.
+ </div></div></div><div class="section" id="sect-limit-redirection"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.15. Setting a limit on device redirection</h2></div></div></div><div class="para">
+ To filter out certain devices from redirection, pass the filter property to <em class="parameter"><code>-device usb-redir</code></em>. The filter property takes a string consisting of filter rules, the format for a rule is:
+ </div><pre class="screen"><code class="command"><class>:<vendor>:<product>:<version>:<allow></code></pre><div class="para">
+ Use the value <em class="parameter"><code>-1 </code></em> to designate it to accept any value for a particular field. You may use multiple rules on the same command line using | as a separator. Note that if a device matches none of the passed in rules, redirecting it will not be allowed!
+ </div><div class="example" id="exam-limit-redirect"><h6>Example 25.6. An example of limiting redirection with a windows guest virtual machine </h6><div class="example-contents"><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Prepare a Windows 7 guest.
+ </div></li><li class="step"><div class="para">
+ Add the following code excerpt to the guest's' domain xml file:
+ </div><pre class="screen">
+ <redirdev bus='usb' type='spicevmc'>
+ <alias name='redir0'/>
+ <address type='usb' bus='0' port='3'/>
+ </redirdev>
+ <redirfilter>
+ <usbdev class='0x08' vendor='0x1234' product='0xBEEF' version='2.0' allow='yes'/>
+ <usbdev class='-1' vendor='-1' product='-1' version='-1' allow='no'/>
+ </redirfilter>
+</pre></li><li class="step"><div class="para">
+ Start the guest and confirm the setting changes by running the following:
+ </div><pre class="screen">#<code class="command">ps -ef | grep $guest_name</code></pre><pre class="screen"><code class="command">-device usb-redir,chardev=charredir0,id=redir0,</code>/
+<code class="command">filter=0x08:0x1234:0xBEEF:0x0200:1|-1:-1:-1:-1:0,bus=usb.0,port=3</code></pre></li><li class="step"><div class="para">
+ Plug a USB device into host, and use virt-viewer to connect to the guest.
+ </div></li><li class="step"><div class="para">
+ Click <span class="guimenuitem"><strong>USB device selection</strong></span> in the menu, which will produce the following message: "Some USB devices are blocked by host policy". Click <span class="guimenuitem"><strong>OK</strong></span> to confirm and continue.
+ </div><div class="para">
+ The filter takes effect.
+ </div></li><li class="step"><div class="para">
+ To make sure that the filter captures properly check the USB device vendor and product, then make the following changes in the host's domain XML to allow for USB redirection.
+ </div><pre class="screen">
+ <redirfilter>
+ <usbdev class='0x08' vendor='0x0951' product='0x1625' version='2.0' allow='yes'/>
+ <usbdev allow='no'/>
+ </redirfilter>
+</pre></li><li class="step"><div class="para">
+ Restart the guest, then use <span class="application"><strong>virt-viewer</strong></span> to connect to the guest. The USB device will now redirect traffic to the guest.
+ </div></li></ol></div></div></div><br class="example-break" /></div><div class="section" id="sect-dynamic-vNIC"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.16. Dynamically changing a host or a network bridge that is attached to a virtual NIC</h2></div></div></div><div class="para">
+ This section demonstrates how to move the vNIC of a guest from one bridge to another while the guest is running without compromising the guest
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Prepare guest with a configuration similar to the following:
+ </div><pre class="screen">
+<interface type='bridge'>
+ <mac address='52:54:00:4a:c9:5e'/>
+ <source bridge='virbr0'/>
+ <model type='virtio'/>
+</interface>
+</pre></li><li class="step"><div class="para">
+ Prepare an XML file for interface update:
+ </div><pre class="screen">#<code class="command"> cat br1.xml</code></pre><pre class="screen">
+<interface type='bridge'>
+ <mac address='52:54:00:4a:c9:5e'/>
+ <source bridge='virbr1'/>
+ <model type='virtio'/>
+</interface>
+</pre></li><li class="step"><div class="para">
+ Start the guest, confirm the guest's network functionality, and check that the guest's vnetX is connected to the bridge you indicated.
+ </div><pre class="screen">
+<code class="command"># brctl show</code>
+bridge name bridge id STP enabled interfaces
+virbr0 8000.5254007da9f2 yes virbr0-nic
+
+vnet0
+virbr1 8000.525400682996 yes virbr1-nic
+</pre></li><li class="step"><div class="para">
+ Update the guest's network with the new interface parameters with the following command:
+ </div><pre class="screen">
+<code class="command"># virsh update-device test1 br1.xml </code>
+
+Device updated successfully
+
+</pre></li><li class="step"><div class="para">
+ On the guest, run <code class="command">service network restart</code>. The guest gets a new IP address for virbr1. Check the guest's vnet0 is connected to the new bridge(virbr1)
+ </div><pre class="screen">
+# <code class="command">brctl show</code>
+bridge name bridge id STP enabled interfaces
+virbr0 8000.5254007da9f2 yes virbr0-nic
+virbr1 8000.525400682996 yes virbr1-nic vnet0
+</pre></li></ol></div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_Guide-Storage_Concepts" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 26. Storage concepts</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Virtualization-Storage_Concepts-Storage_Pools">26.1. Storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Concepts-Volumes">26.2. Volumes </a></span></dt></dl></div><div class="para">
+ This chapter introduces the concepts used for describing and managing storage devices. Terms such as Storage Pools and Volumes are explained in the sections that follow.
+ </div><div class="section" id="sect-Virtualization-Storage_Concepts-Storage_Pools"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">26.1. Storage pools</h2></div></div></div><div class="para">
+ A <em class="firstterm">storage pool</em> is a file, directory, or storage device managed by libvirt for the purpose of providing storage to guests. The storage pool can be local or it can be shared over a network.
+ </div><div class="para">
+ libvirt uses a directory-based storage pool, the <code class="filename">/var/lib/libvirt/images/</code> directory, as the default storage pool. The default storage pool can be changed to another storage pool.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Local storage pools</strong></span> - Local storage pools are directly attached to the host server. Local storage pools include: local directories, directly attached disks, physical partitions, and LVM volume groups. These storage volumes store guest images or are attached to guests as additional storage. As local storage pools are directly attached to the host server, they are useful for development, testing and small deployments that do not require migration or large numbers of guests. Local storage pools are not suitable for many production environments as local storage pools do not support live migration.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Networked (shared) storage pools</strong></span> - Networked storage pools include storage devices shared over a network using standard protocols. Networked storage is required when migrating virtual machines between hosts with virt-manager, but is optional when migrating with virsh. Networked storage pools are managed by libvirt. Supported protocols for networked storage pools include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Fibre Channel-based LUNs
+ </div></li><li class="listitem"><div class="para">
+ iSCSI
+ </div></li><li class="listitem"><div class="para">
+ NFS
+ </div></li><li class="listitem"><div class="para">
+ GFS2
+ </div></li><li class="listitem"><div class="para">
+ SCSI RDMA protocols (SCSI RCP), the block export protocol used in InfiniBand and 10GbE iWARP adapters.
+ </div></li></ul></div></li></ul></div></div><div class="section" id="sect-Virtualization-Storage_Concepts-Volumes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">26.2. Volumes </h2></div></div></div><div class="para">
+ Storage pools are divided into storage volumes. Storage volumes are an abstraction of physical partitions, LVM logical volumes, file-based disk images and other storage types handled by libvirt. Storage volumes are presented to guests as local storage devices regardless of the underlying hardware.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm110292576"> Referencing volumes</h5>
+ To reference a specific volume, three approaches are possible:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">The name of the volume and the storage pool</span></dt><dd><div class="para">
+ A volume may be referred to by name, along with an identifier for the storage pool it belongs in. On the virsh command line, this takes the form <em class="parameter"><code>--pool</code></em> <em class="replaceable"><code>storage_pool</code></em> <em class="replaceable"><code>volume_name</code></em>.
+ </div><div class="para">
+ For example, a volume named <em class="replaceable"><code>firstimage</code></em> in the <em class="replaceable"><code>guest_images</code></em> pool.
+ </div><pre class="screen"># virsh vol-info --pool <em class="replaceable"><code>guest_images</code></em> <em class="replaceable"><code>firstimage</code></em>
+Name: <em class="replaceable"><code>firstimage</code></em>
+Type: block
+Capacity: 20.00 GB
+Allocation: 20.00 GB
+
+virsh #</pre></dd><dt class="varlistentry"><span class="term">The full path to the storage on the host system</span></dt><dd><div class="para">
+ A volume may also be referred to by its full path on the file system. When using this approach, a pool identifier does not need to be included.
+ </div><div class="para">
+ For example, a volume named <em class="replaceable"><code>secondimage.img</code></em>, visible to the host system as <em class="replaceable"><code>/images/secondimage.img</code></em>. The image can be referred to as <em class="replaceable"><code>/images/secondimage.img</code></em>.
+ </div><pre class="screen"># virsh vol-info <em class="replaceable"><code>/images/secondimage.img</code></em>
+Name: <em class="replaceable"><code>secondimage.img</code></em>
+Type: file
+Capacity: 20.00 GB
+Allocation: 136.00 kB
+</pre></dd><dt class="varlistentry"><span class="term">The unique volume key</span></dt><dd><div class="para">
+ When a volume is first created in the virtualization system, a unique identifier is generated and assigned to it. The unique identifier is termed the <em class="firstterm">volume key</em>. The format of this volume key varies upon the storage used.
+ </div><div class="para">
+ When used with block based storage such as LVM, the volume key may follow this format:
+ </div><pre class="screen">c3pKz4-qPVc-Xf7M-7WNM-WJc8-qSiz-mtvpGn</pre><div class="para">
+ When used with file based storage, the volume key may instead be a copy of the full path to the volume storage.
+ </div><pre class="screen">/images/secondimage.img</pre><div class="para">
+ For example, a volume with the volume key of <em class="replaceable"><code>Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr</code></em>:
+ </div><pre class="screen"># virsh vol-info Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr
+Name: <em class="replaceable"><code>firstimage</code></em>
+Type: block
+Capacity: 20.00 GB
+Allocation: 20.00 GB
+</pre></dd></dl></div><div class="para">
+ <code class="command">virsh</code> provides commands for converting between a volume name, volume path, or volume key:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> vol-name </span></dt><dd><div class="para">
+ Returns the volume name when provided with a volume path or volume key.
+ </div><pre class="screen"># virsh vol-name /dev/<em class="replaceable"><code>guest_images</code></em>/<em class="replaceable"><code>firstimage</code></em>
+<em class="replaceable"><code>firstimage</code></em>
+# virsh vol-name <em class="replaceable"><code>Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr</code></em></pre></dd><dt class="varlistentry"><span class="term">vol-path</span></dt><dd><div class="para">
+ Returns the volume path when provided with a volume key, or a storage pool identifier and volume name.
+ </div><pre class="screen"># virsh vol-path Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr
+/dev/<em class="replaceable"><code>guest_images</code></em>/<em class="replaceable"><code>firstimage</code></em>
+# virsh vol-path --pool <em class="replaceable"><code>guest_images</code></em> <em class="replaceable"><code>firstimage</code></em>
+/dev/<em class="replaceable"><code>guest_images</code></em>/<em class="replaceable"><code>firstimage</code></em></pre></dd><dt class="varlistentry"><span class="term">The vol-key command</span></dt><dd><div class="para">
+ Returns the volume key when provided with a volume path, or a storage pool identifier and volume name.
+ </div><pre class="screen"># virsh vol-key /dev/<em class="replaceable"><code>guest_images</code></em>/<em class="replaceable"><code>firstimage</code></em>
+Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr
+# virsh vol-key --pool <em class="replaceable"><code>guest_images</code></em> <em class="replaceable"><code>firstimage</code></em>
+Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr
+</pre></dd></dl></div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 27. Storage pools</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating_Storage_Pools">27.1. Creating storage pools </a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-Dedicated_Disk_Devices">27.1.1. Disk-based storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-File_Systems">27.1.2. Partition-based storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-Local_Directories">27.1.3. Directory-based storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-LVM">27.1.4. LVM-based storage po
ols</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-iSCSI">27.1.5. iSCSI-based storage pools</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Pools-Creating-NFS">27.1.6. NFS-based storage pools</a></span></dt></dl></dd></dl></div><div class="para">
+ This chapter includes instructions on creating storage pools of assorted types. A <em class="firstterm">storage pool</em> is a quantity of storage set aside by an administrator, often a dedicated storage administrator, for use by virtual machines. Storage pools are often divided into storage volumes either by the storage administrator or the system administrator, and the volumes are assigned to guest virtual machines as block devices.
+ </div><div class="example"><h6>Example 27.1. NFS storage pool</h6><div class="example-contents"><div class="para">
+ Suppose a storage administrator responsible for an NFS server creates a share to store guest virtual machines' data. The system administrator defines a pool on the host with the details of the share (nfs.example.com:<code class="filename">/path/to/share</code> should be mounted on <code class="filename">/vm_data</code>). When the pool is started, libvirt mounts the share on the specified directory, just as if the system administrator logged in and executed <code class="command">mount nfs.example.com:/path/to/share /vmdata</code>. If the pool is configured to autostart, libvirt ensures that the NFS share is mounted on the directory specified when libvirt is started.
+ </div><div class="para">
+ Once the pool starts, the files that the NFS share, are reported as volumes, and the storage volumes' paths are then queried using the libvirt APIs. The volumes' paths can then be copied into the section of a guest virtual machine's XML definition file describing the source storage for the guest virtual machine's block devices. With NFS, applications using the libvirt APIs can create and delete volumes in the pool (files within the NFS share) up to the limit of the size of the pool (the maximum storage capacity of the share). Not all pool types support creating and deleting volumes. Stopping the pool negates the start operation, in this case, unmounts the NFS share. The data on the share is not modified by the destroy operation, despite the name. See man virsh for more details.
+ </div></div></div><br class="example-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Storage pools and volumes are not required for the proper operation of guest virtual machines. Pools and volumes provide a way for libvirt to ensure that a particular piece of storage will be available for a guest virtual machine, but some administrators will prefer to manage their own storage and guest virtual machines will operate properly without any pools or volumes defined. On systems that do not use pools, system administrators must ensure the availability of the guest virtual machines' storage using whatever tools they prefer, for example, adding the NFS share to the host's fstab so that the share is mounted at boot time.
+ </div></div></div><div class="section" id="sect-Virtualization-Storage_Pools-Creating_Storage_Pools"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">27.1. Creating storage pools </h2></div></div></div><div xml:lang="en-US" class="section" id="sect-Virtualization-Storage_Pools-Creating-Dedicated_Disk_Devices" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">27.1.1. Disk-based storage pools</h3></div></div></div><div class="para">
+ This section covers creating disk based storage devices for guest virtual machines.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Guests should not be given write access to whole disks or block devices (for example, <code class="filename">/dev/sdb</code>). Use partitions (for example, <code class="filename">/dev/sdb1</code>) or LVM volumes.
+ </div><div class="para">
+ If you pass an entire block device to the guest, the guest will likely partition it or create its own LVM groups on it. This can cause the host to detect these partitions or LVM groups and cause errors.
+ </div></div></div><div class="section" id="idm80592784"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm80592784">27.1.1.1. Creating a disk based storage pool using virsh</h4></div></div></div><div class="para">
+ This procedure creates a new storage pool using a disk device with the <code class="command">virsh</code> command.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Dedicating a disk to a storage pool will reformat and erase all data presently stored on the disk device! It is strongly recommended to back up the storage device before commencing with the following procedure:
+ </div></div></div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong> Create a GPT disk label on the disk </strong></p><div class="para">
+ The disk must be relabeled with a <em class="firstterm">GUID Partition Table</em> (GPT) disk label. GPT disk labels allow for creating a large numbers of partitions, up to 128 partitions, on each device. GPT partition tables can store partition data for far more partitions than the MS-DOS partition table.
+ </div><pre class="screen"># parted /dev/sdb
+GNU Parted 2.1
+Using /dev/sdb
+Welcome to GNU Parted! Type 'help' to view a list of commands.
+(parted) mklabel
+New disk label type? gpt
+(parted) quit
+Information: You may need to update /etc/fstab.
+#
+</pre></li><li class="step"><p class="title"><strong>Create the storage pool configuration file</strong></p><div class="para">
+ Create a temporary XML text file containing the storage pool information required for the new device.
+ </div><div class="para">
+ The file must be in the format shown below, and contain the following fields:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><name>guest_images_disk</name></span></dt><dd><div class="para">
+ The <em class="parameter"><code>name</code></em> parameter determines the name of the storage pool. This example uses the name <em class="replaceable"><code>guest_images_disk</code></em> in the example below.
+ </div></dd><dt class="varlistentry"><span class="term"> <device path='<em class="replaceable"><code>/dev/sdb</code></em>'/></span></dt><dd><div class="para">
+ The <em class="parameter"><code>device</code></em> parameter with the <em class="parameter"><code>path</code></em> attribute specifies the device path of the storage device. This example uses the device <em class="replaceable"><code>/dev/sdb</code></em>.
+ </div></dd><dt class="varlistentry"><span class="term"><target> <path><em class="replaceable"><code>/dev</code></em></path></target></span></dt><dd><div class="para">
+ The file system <em class="parameter"><code>target</code></em> parameter with the <em class="parameter"><code>path</code></em> sub-parameter determines the location on the host file system to attach volumes created with this storage pool.
+ </div><div class="para">
+ For example, sdb1, sdb2, sdb3. Using <em class="replaceable"><code>/dev/</code></em>, as in the example below, means volumes created from this storage pool can be accessed as <em class="replaceable"><code>/dev</code></em>/sdb1, <em class="replaceable"><code>/dev</code></em>/sdb2, <em class="replaceable"><code>/dev</code></em>/sdb3.
+ </div></dd><dt class="varlistentry"><span class="term"><format type='<em class="replaceable"><code>gpt</code></em>'/></span></dt><dd><div class="para">
+ The <em class="parameter"><code>format</code></em> parameter specifies the partition table type. This example uses the <em class="replaceable"><code>gpt</code></em> in the example below, to match the GPT disk label type created in the previous step.
+ </div></dd></dl></div><div class="para">
+ Create the XML file for the storage pool device with a text editor.
+ </div><div class="example"><h6>Example 27.2. Disk based storage device storage pool</h6><div class="example-contents"><pre class="screen">
+<pool type='disk'>
+ <name><em class="replaceable"><code>guest_images_disk</code></em></name>
+ <source>
+ <device path='<em class="replaceable"><code>/dev/sdb</code></em>'/>
+ <format type='<em class="replaceable"><code>gpt</code></em>'/>
+ </source>
+ <target>
+ <path><em class="replaceable"><code>/dev</code></em></path>
+ </target>
+</pool>
+</pre></div></div><br class="example-break" /></li><li class="step"><p class="title"><strong>Attach the device</strong></p><div class="para">
+ Add the storage pool definition using the <code class="command">virsh pool-define</code> command with the XML configuration file created in the previous step.
+ </div><pre class="screen"># virsh pool-define ~/guest_images_disk.xml
+Pool guest_images_disk defined from /root/guest_images_disk.xml
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_disk inactive no
+</pre></li><li class="step"><p class="title"><strong>Start the storage pool</strong></p><div class="para">
+ Start the storage pool with the <code class="command">virsh pool-start</code> command. Verify the pool is started with the <code class="command">virsh pool-list --all</code> command.
+ </div><pre class="screen"># virsh pool-start <em class="replaceable"><code>guest_images_disk</code></em>
+Pool guest_images_disk started
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_disk active no
+</pre></li><li class="step"><p class="title"><strong>Turn on autostart</strong></p><div class="para">
+ Turn on <em class="parameter"><code>autostart</code></em> for the storage pool. Autostart configures the <code class="systemitem">libvirtd</code> service to start the storage pool when the service starts.
+ </div><pre class="screen"># virsh pool-autostart <em class="replaceable"><code>guest_images_disk</code></em>
+Pool guest_images_disk marked as autostarted
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_disk active yes
+</pre></li><li class="step"><p class="title"><strong>Verify the storage pool configuration</strong></p><div class="para">
+ Verify the storage pool was created correctly, the sizes reported correctly, and the state reports as <code class="computeroutput">running</code>.
+ </div><pre class="screen"># virsh pool-info <em class="replaceable"><code>guest_images_disk</code></em>
+Name: guest_images_disk
+UUID: 551a67c8-5f2a-012c-3844-df29b167431c
+State: running
+Capacity: 465.76 GB
+Allocation: 0.00
+Available: 465.76 GB
+# ls -la /dev/sdb
+brw-rw----. 1 root disk 8, 16 May 30 14:08 /dev/sdb
+# virsh vol-list guest_images_disk
+Name Path
+-----------------------------------------
+</pre></li><li class="step"><p class="title"><strong>Optional: Remove the temporary configuration file</strong></p><div class="para">
+ Remove the temporary storage pool XML configuration file if it is not needed.
+ </div><pre class="screen"># rm ~/<em class="replaceable"><code>guest_images_disk</code></em>.xml</pre></li></ol></div><div class="para">
+ A disk based storage pool is now available.
+ </div></div><div class="section" id="delete-ded-disk-storage-pool"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">27.1.1.2. Deleting a storage pool using virsh</h4></div></div></div><div class="para">
+ The following demonstrates how to delete a storage pool using virsh:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it.
+ </div><pre class="screen"># virsh pool-destroy <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Remove the storage pool's definition
+ </div><pre class="screen"># virsh pool-undefine <em class="replaceable"><code>guest_images_disk</code></em></pre></li></ol></div></div></div><div xml:lang="en-US" class="section" id="sect-Virtualization-Storage_Pools-Creating-File_Systems" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">27.1.2. Partition-based storage pools</h3></div></div></div><div class="para">
+ This section covers using a pre-formatted block device, a partition, as a storage pool.
+ </div><div class="para">
+ For the following examples, a host has a 500GB hard drive (<code class="systemitem">/dev/sdc</code>) partitioned into one 500GB, ext4 formatted partition (<code class="systemitem">/dev/sdc1</code>). We set up a storage pool for it using the procedure below.
+ </div><div class="section" id="create-part-stor-pool"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">27.1.2.1. Creating a partition-based storage pool using virt-manager</h4></div></div></div><div class="para">
+ This procedure creates a new storage pool using a partition of a storage device.
+ </div><div class="procedure"><h6>Procedure 27.1. Creating a partition-based storage pool with virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Open the storage pool settings</strong></p><ol class="a"><li class="step"><div class="para">
+ In the <code class="command">virt-manager</code> graphical interface, select the host from the main window.
+ </div><div class="para">
+ Open the <span class="guilabel"><strong>Edit</strong></span> menu and select <span class="guilabel"><strong>Connection Details</strong></span>
+ </div><div class="figure" id="connection_details"><div class="figure-contents"><div class="mediaobject"><img src="images/Connection_Details.png" width="444" alt="Connection Details" /></div></div><h6>Figure 27.1. Connection Details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Click on the <span class="guilabel"><strong>Storage</strong></span> tab of the <span class="guilabel"><strong>Connection Details</strong></span> window.
+ </div><div class="figure" id="storage-tab"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Storage tab" /></div></div><h6>Figure 27.2. Storage tab</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Create the new storage pool</strong></p><ol class="a"><li class="step"><p class="title"><strong>Add a new pool (part 1)</strong></p><div class="para">
+ Press the <span class="guilabel"><strong>+</strong></span> button (the add pool button). The <span class="guilabel"><strong>Add a New Storage Pool</strong></span> wizard appears.
+ </div><div class="para">
+ Choose a <span class="guibutton"><strong>Name</strong></span> for the storage pool. This example uses the name <em class="replaceable"><code>guest_images_fs</code></em>. Change the <span class="guibutton"><strong>Type</strong></span> to <code class="command">fs: Pre-Formatted Block Device</code>.
+ </div><div class="figure" id="name-and-type"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_fs_step_1_name_and_type.png" width="444" alt="Storage pool name and type" /></div></div><h6>Figure 27.3. Storage pool name and type</h6></div><br class="figure-break" /><div class="para">
+ Press the <span class="guibutton"><strong>Forward</strong></span> button to continue.
+ </div></li><li class="step"><p class="title"><strong>Add a new pool (part 2)</strong></p><div class="para">
+ Change the <span class="guibutton"><strong>Target Path</strong></span>, <span class="guibutton"><strong>Format</strong></span>, and <span class="guibutton"><strong>Source Path</strong></span> fields.
+ </div><div class="figure" id="path-and-format"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_fs_step_2_paths_and_format.png" width="444" alt="Storage pool path and format" /></div></div><h6>Figure 27.4. Storage pool path and format</h6></div><br class="figure-break" /><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Target Path</span></dt><dd><div class="para">
+ Enter the location to mount the source device for the storage pool in the <span class="guibutton"><strong>Target Path</strong></span> field. If the location does not already exist, <code class="command">virt-manager</code> will create the directory.
+ </div></dd><dt class="varlistentry"><span class="term">Format</span></dt><dd><div class="para">
+ Select a format from the <span class="guibutton"><strong>Format</strong></span> list. The device is formatted with the selected format.
+ </div><div class="para">
+ This example uses the <em class="replaceable"><code>ext4</code></em> file system, the default Fedora file system.
+ </div></dd><dt class="varlistentry"><span class="term">Source Path</span></dt><dd><div class="para">
+ Enter the device in the <code class="command">Source Path</code> field.
+ </div><div class="para">
+ This example uses the <em class="replaceable"><code>/dev/sdc1</code></em> device.
+ </div></dd></dl></div><div class="para">
+ Verify the details and press the <span class="guibutton"><strong>Finish</strong></span> button to create the storage pool.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Verify the new storage pool</strong></p><div class="para">
+ The new storage pool appears in the storage list on the left after a few seconds. Verify the size is reported as expected, <em class="replaceable"><code>458.20 GB Free</code></em> in this example. Verify the <span class="guibutton"><strong>State</strong></span> field reports the new storage pool as <em class="replaceable"><code>Active</code></em>.
+ </div><div class="para">
+ Select the storage pool. In the <span class="guibutton"><strong>Autostart</strong></span> field, click the <span class="guibutton"><strong>On Boot</strong></span> checkbox. This will make sure the storage device starts whenever the <code class="systemitem">libvirtd</code> service starts.
+ </div><div class="figure" id="confirmation"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_fs_step_3_result.png" width="444" alt="Storage list confirmation" /></div></div><h6>Figure 27.5. Storage list confirmation</h6></div><br class="figure-break" /><div class="para">
+ The storage pool is now created, close the <span class="guilabel"><strong>Connection Details</strong></span> window.
+ </div></li></ol></div></div><div class="section" id="del-stor-pool-vmana-part"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">27.1.2.2. Deleting a storage pool using virt-manager</h4></div></div></div><div class="para">
+ This procedure demonstrates how to delete a storage pool.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it. To do this, select the storage pool you want to stop and click the red X icon at the bottom of the Storage window.
+ </div><div class="figure" id="stop-icon"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Stop Icon" /></div></div><h6>Figure 27.6. Stop Icon</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Delete the storage pool by clicking the Trash can icon. This icon is only enabled if you stop the storage pool first.
+ </div></li></ol></div></div><div class="section" id="idm107784672"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm107784672">27.1.2.3. Creating a partition-based storage pool using virsh</h4></div></div></div><div class="para">
+ This section covers creating a partition-based storage pool with the <code class="command">virsh</code> command.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Do not use this procedure to assign an entire disk as a storage pool (for example, <code class="filename">/dev/sdb</code>). Guests should not be given write access to whole disks or block devices. Only use this method to assign partitions (for example, <code class="filename">/dev/sdb1</code>) to storage pools.
+ </div></div></div><div class="procedure"><h6>Procedure 27.2. Creating pre-formatted block device storage pools using virsh</h6><ol class="1"><li class="step"><p class="title"><strong> Create the storage pool definition </strong></p><div class="para">
+ Use the virsh <code class="command">pool-define-as</code> command to create a new storage pool definition. There are three options that must be provided to define a pre-formatted disk as a storage pool:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Partition name</span></dt><dd><div class="para">
+ The <em class="parameter"><code>name</code></em> parameter determines the name of the storage pool. This example uses the name <em class="replaceable"><code>guest_images_fs</code></em> in the example below.
+ </div></dd><dt class="varlistentry"><span class="term">device</span></dt><dd><div class="para">
+ The <em class="parameter"><code>device</code></em> parameter with the <em class="parameter"><code>path</code></em> attribute specifies the device path of the storage device. This example uses the partition <em class="replaceable"><code>/dev/sdc1</code></em>.
+ </div></dd><dt class="varlistentry"><span class="term">mountpoint</span></dt><dd><div class="para">
+ The <em class="parameter"><code>mountpoint</code></em> on the local file system where the formatted device will be mounted. If the mount point directory does not exist, the <code class="command">virsh</code> command can create the directory.
+ </div><div class="para">
+ The directory <em class="replaceable"><code>/guest_images</code></em> is used in this example.
+ </div></dd></dl></div><pre class="screen"># virsh pool-define-as <em class="replaceable"><code>guest_images_fs</code></em> fs - - <em class="replaceable"><code>/dev/sdc1</code></em> - "<em class="replaceable"><code>/guest_images</code></em>"
+Pool guest_images_fs defined
+</pre><div class="para">
+ The new pool and mount points are now created.
+ </div></li><li class="step"><p class="title"><strong>Verify the new pool</strong></p><div class="para">
+ List the present storage pools.
+ </div><pre class="screen">
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+<em class="replaceable"><code>guest_images_fs</code></em> inactive no
+</pre></li><li class="step"><p class="title"><strong> Create the mount point </strong></p><div class="para">
+ Use the <code class="command">virsh pool-build</code> command to create a mount point for a pre-formatted file system storage pool.
+ </div><pre class="screen">
+# virsh pool-build <em class="replaceable"><code>guest_images_fs</code></em>
+Pool guest_images_fs built
+# ls -la /<em class="replaceable"><code>guest_images</code></em>
+total 8
+drwx------. 2 root root 4096 May 31 19:38 .
+dr-xr-xr-x. 25 root root 4096 May 31 19:38 ..
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_fs inactive no
+</pre></li><li class="step"><p class="title"><strong> Start the storage pool </strong></p><div class="para">
+ Use the <code class="command">virsh pool-start</code> command to mount the file system onto the mount point and make the pool available for use.
+ </div><pre class="screen">
+# virsh pool-start <em class="replaceable"><code>guest_images_fs</code></em>
+Pool guest_images_fs started
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_fs active no
+</pre></li><li class="step"><p class="title"><strong> Turn on autostart </strong></p><div class="para">
+ By default, a storage pool is defined with <code class="command">virsh</code> is not set to automatically start each time <code class="systemitem">libvirtd</code> starts. Turn on automatic start with the <code class="command">virsh pool-autostart</code> command. The storage pool is now automatically started each time <code class="systemitem">libvirtd</code> starts.
+ </div><pre class="screen">
+# virsh pool-autostart <em class="replaceable"><code>guest_images_fs</code></em>
+Pool guest_images_fs marked as autostarted
+
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_fs active yes
+</pre></li><li class="step"><p class="title"><strong> Verify the storage pool </strong></p><div class="para">
+ Verify the storage pool was created correctly, the sizes reported are as expected, and the state is reported as <code class="command">running</code>. Verify there is a "lost+found" directory in the mount point on the file system, indicating the device is mounted.
+ </div><pre class="screen">
+# virsh pool-info <em class="replaceable"><code>guest_images_fs</code></em>
+Name: guest_images_fs
+UUID: c7466869-e82a-a66c-2187-dc9d6f0877d0
+State: running
+Persistent: yes
+Autostart: yes
+Capacity: 458.39 GB
+Allocation: 197.91 MB
+Available: 458.20 GB
+# mount | grep /guest_images
+/dev/sdc1 on /guest_images type ext4 (rw)
+# ls -la /guest_images
+total 24
+drwxr-xr-x. 3 root root 4096 May 31 19:47 .
+dr-xr-xr-x. 25 root root 4096 May 31 19:38 ..
+drwx------. 2 root root 16384 May 31 14:18 lost+found
+</pre></li></ol></div></div><div class="section" id="delete-ded-part-storage-pool-virsh"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">27.1.2.4. Deleting a storage pool using virsh</h4></div></div></div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it.
+ </div><pre class="screen"># virsh pool-destroy <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Optionally, if you want to remove the directory where the storage pool resides use the following command:
+ </div><pre class="screen"># virsh pool-delete <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Remove the storage pool's definition
+ </div><pre class="screen"># virsh pool-undefine <em class="replaceable"><code>guest_images_disk</code></em></pre></li></ol></div></div></div><div xml:lang="en-US" class="section" id="sect-Virtualization-Storage_Pools-Creating-Local_Directories" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">27.1.3. Directory-based storage pools</h3></div></div></div><div class="para">
+ This section covers storing guests in a directory on the host.
+ </div><div class="para">
+ Directory-based storage pools can be created with <code class="command">virt-manager</code> or the <code class="command">virsh</code> command line tools.
+ </div><div class="section" id="idm84762144"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm84762144">27.1.3.1. Creating a directory-based storage pool with virt-manager</h4></div></div></div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Create the local directory</strong></p><ol class="a"><li class="step"><p class="title"><strong>Optional: Create a new directory for the storage pool</strong></p><div class="para">
+ Create the directory on the host for the storage pool. This example uses a directory named <em class="replaceable"><code>/guest_images</code></em>.
+ </div><pre class="screen"># mkdir <em class="replaceable"><code>/guest_images</code></em></pre></li><li class="step"><p class="title"><strong>Set directory ownership</strong></p><div class="para">
+ Change the user and group ownership of the directory. The directory must be owned by the root user.
+ </div><pre class="screen"># chown root:root <em class="replaceable"><code>/guest_images</code></em></pre></li><li class="step"><p class="title"><strong>Set directory permissions</strong></p><div class="para">
+ Change the file permissions of the directory.
+ </div><pre class="screen"># chmod 700 <em class="replaceable"><code>/guest_images</code></em></pre></li><li class="step"><p class="title"><strong>Verify the changes</strong></p><div class="para">
+ Verify the permissions were modified. The output shows a correctly configured empty directory.
+ </div><pre class="screen"># ls -la <em class="replaceable"><code>/guest_images</code></em>
+total 8
+drwx------. 2 root root 4096 May 28 13:57 .
+dr-xr-xr-x. 26 root root 4096 May 28 13:57 ..
+</pre></li></ol></li><li class="step"><p class="title"><strong>Configure SELinux file contexts</strong></p><div class="para">
+ Configure the correct SELinux context for the new directory. Note that the name of the pool and the directory do not have to match. However, when you shutdown the guest virtual machine, libvirt has to set the context back to a default value. The context of the directory determines what this default value is. It is worth explicitly labelling the directory virt_image_t, so that when the guest virtual machine is shutdown, the images get labeled 'virt_image_t' and are thus isolated from other processes running on the host.
+ </div><pre class="screen">
+# semanage fcontext -a -t virt_image_t '/guest_images(/.*)?'
+# restorecon -R /guest_images
+</pre></li><li class="step"><p class="title"><strong>Open the storage pool settings</strong></p><ol class="a"><li class="step"><div class="para">
+ In the <code class="command">virt-manager</code> graphical interface, select the host from the main window.
+ </div><div class="para">
+ Open the <span class="guilabel"><strong>Edit</strong></span> menu and select <span class="guilabel"><strong>Connection Details</strong></span>
+ </div><div class="figure" id="conn-details-screenshot"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_select_host.png" width="444" alt="Connection details window" /></div></div><h6>Figure 27.7. Connection details window</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Click on the <span class="guilabel"><strong>Storage</strong></span> tab of the <span class="guilabel"><strong>Connection Details</strong></span> window.
+ </div><div class="figure" id="host-details-screenshot-storagepools-dir"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Storage tab" /></div></div><h6>Figure 27.8. Storage tab</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Create the new storage pool</strong></p><ol class="a"><li class="step"><p class="title"><strong>Add a new pool (part 1)</strong></p><div class="para">
+ Press the <span class="guilabel"><strong>+</strong></span> button (the add pool button). The <span class="guilabel"><strong>Add a New Storage Pool</strong></span> wizard appears.
+ </div><div class="para">
+ Choose a <span class="guibutton"><strong>Name</strong></span> for the storage pool. This example uses the name <em class="replaceable"><code>guest_images</code></em>. Change the <span class="guibutton"><strong>Type</strong></span> to <code class="command">dir: Filesystem Directory</code>.
+ </div><div class="figure" id="screenshot-pick-pool-name"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_dir_step_1_name_and_type.png" width="444" alt="Name the storage pool" /></div></div><h6>Figure 27.9. Name the storage pool</h6></div><br class="figure-break" /><div class="para">
+ Press the <span class="guibutton"><strong>Forward</strong></span> button to continue.
+ </div></li><li class="step"><p class="title"><strong>Add a new pool (part 2)</strong></p><div class="para">
+ Change the <span class="guibutton"><strong>Target Path</strong></span> field. For example, <em class="replaceable"><code>/guest_images</code></em>.
+ </div><div class="para">
+ Verify the details and press the <span class="guibutton"><strong>Finish</strong></span> button to create the storage pool.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Verify the new storage pool</strong></p><div class="para">
+ The new storage pool appears in the storage list on the left after a few seconds. Verify the size is reported as expected, <em class="replaceable"><code>36.41 GB Free</code></em> in this example. Verify the <span class="guibutton"><strong>State</strong></span> field reports the new storage pool as <em class="replaceable"><code>Active</code></em>.
+ </div><div class="para">
+ Select the storage pool. In the <span class="guibutton"><strong>Autostart</strong></span> field, confirm that the <span class="guibutton"><strong>On Boot</strong></span> checkbox is checked. This will make sure the storage pool starts whenever the <code class="systemitem">libvirtd</code> service starts.
+ </div><div class="figure" id="verify-pool-screenshot"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_dir_step_3_result.png" width="444" alt="Verify the storage pool information" /></div></div><h6>Figure 27.10. Verify the storage pool information</h6></div><br class="figure-break" /><div class="para">
+ The storage pool is now created, close the <span class="guilabel"><strong>Connection Details</strong></span> window.
+ </div></li></ol></div></div><div class="section" id="del-stor-pool-dir"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">27.1.3.2. Deleting a storage pool using virt-manager</h4></div></div></div><div class="para">
+ This procedure demonstrates how to delete a storage pool.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it. To do this, select the storage pool you want to stop and click the red X icon at the bottom of the Storage window.
+ </div><div class="figure" id="stop-icon2"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Stop Icon" /></div></div><h6>Figure 27.11. Stop Icon</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Delete the storage pool by clicking the Trash can icon. This icon is only enabled if you stop the storage pool first.
+ </div></li></ol></div></div><div class="section" id="idm85430960"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm85430960">27.1.3.3. Creating a directory-based storage pool with virsh</h4></div></div></div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong> Create the storage pool definition </strong></p><div class="para">
+ Use the <code class="command">virsh pool-define-as</code> command to define a new storage pool. There are two options required for creating directory-based storage pools:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <code class="command">name</code> of the storage pool.
+ </div><div class="para">
+ This example uses the name <em class="replaceable"><code>guest_images</code></em>. All further <code class="command">virsh</code> commands used in this example use this name.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="command">path</code> to a file system directory for storing guest image files. If this directory does not exist, <code class="command">virsh</code> will create it.
+ </div><div class="para">
+ This example uses the <em class="replaceable"><code>/guest_images</code></em> directory.
+ </div></li></ul></div><pre class="screen"> # virsh pool-define-as <em class="replaceable"><code>guest_images</code></em> dir - - - - "<em class="replaceable"><code>/guest_images</code></em>"
+Pool guest_images defined</pre></li><li class="step"><p class="title"><strong>Verify the storage pool is listed</strong></p><div class="para">
+ Verify the storage pool object is created correctly and the state reports it as <code class="computeroutput">inactive</code>.
+ </div><pre class="screen"># virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images inactive no</pre></li><li class="step"><p class="title"><strong> Create the local directory </strong></p><div class="para">
+ Use the <code class="command">virsh pool-build</code> command to build the directory-based storage pool for the directory <em class="replaceable"><code>guest_images</code></em> (for example), as shown:
+ </div><pre class="screen"># virsh pool-build <em class="replaceable"><code>guest_images</code></em>
+Pool guest_images built
+# ls -la /<em class="replaceable"><code>guest_images</code></em>
+total 8
+drwx------. 2 root root 4096 May 30 02:44 .
+dr-xr-xr-x. 26 root root 4096 May 30 02:44 ..
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images inactive no</pre></li><li class="step"><p class="title"><strong>Start the storage pool</strong></p><div class="para">
+ Use the virsh command <code class="command">pool-start</code> to enable a directory storage pool, thereby allowing allowing volumes of the pool to be used as guest disk images.
+ </div><pre class="screen"># virsh pool-start <em class="replaceable"><code>guest_images</code></em>
+Pool guest_images started
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images active no
+</pre></li><li class="step"><p class="title"><strong>Turn on autostart</strong></p><div class="para">
+ Turn on <em class="parameter"><code>autostart</code></em> for the storage pool. Autostart configures the <code class="systemitem">libvirtd</code> service to start the storage pool when the service starts.
+ </div><pre class="screen"># virsh pool-autostart <em class="replaceable"><code>guest_images</code></em>
+Pool guest_images marked as autostarted
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images active yes
+</pre></li><li class="step"><p class="title"><strong>Verify the storage pool configuration</strong></p><div class="para">
+ Verify the storage pool was created correctly, the size is reported correctly, and the state is reported as <code class="computeroutput">running</code>. If you want the pool to be accessible even if the guest is not running, make sure that <code class="computeroutput">Persistent</code> is reported as <code class="computeroutput">yes</code>. If you want the pool to start automatically when the service starts, make sure that <code class="computeroutput">Autostart</code> is reported as <code class="computeroutput">yes</code>.
+ </div><pre class="screen"># virsh pool-info <em class="replaceable"><code>guest_images</code></em>
+Name: guest_images
+UUID: 779081bf-7a82-107b-2874-a19a9c51d24c
+State: running
+Persistent: yes
+Autostart: yes
+Capacity: 49.22 GB
+Allocation: 12.80 GB
+Available: 36.41 GB
+
+# ls -la /guest_images
+total 8
+drwx------. 2 root root 4096 May 30 02:44 .
+dr-xr-xr-x. 26 root root 4096 May 30 02:44 ..
+#
+</pre></li></ol></div><div class="para">
+ A directory-based storage pool is now available.
+ </div></div><div class="section" id="delete-dir-storage-pool-virsh"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">27.1.3.4. Deleting a storage pool using virsh</h4></div></div></div><div class="para">
+ The following demonstrates how to delete a storage pool using virsh:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it.
+ </div><pre class="screen"># virsh pool-destroy <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Optionally, if you want to remove the directory where the storage pool resides use the following command:
+ </div><pre class="screen"># virsh pool-delete <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Remove the storage pool's definition
+ </div><pre class="screen"># virsh pool-undefine <em class="replaceable"><code>guest_images_disk</code></em></pre></li></ol></div></div></div><div xml:lang="en-US" class="section" id="sect-Virtualization-Storage_Pools-Creating-LVM" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">27.1.4. LVM-based storage pools</h3></div></div></div><div class="para">
+ This chapter covers using LVM volume groups as storage pools.
+ </div><div class="para">
+ LVM-based storage groups provide the full flexibility of LVM.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Please refer to the <em class="citetitle">Fedora Storage Administration Guide</em> for more details on LVM.
+ </div></div></div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ LVM-based storage pools require a full disk partition. If activating a new partition/device with these procedures, the partition will be formatted and all data will be erased. If using the host's existing Volume Group (VG) nothing will be erased. It is recommended to back up the storage device before commencing the following procedure.
+ </div></div></div><div class="section" id="idm76102560"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm76102560">27.1.4.1. Creating an LVM-based storage pool with virt-manager</h4></div></div></div><div class="para">
+ LVM-based storage pools can use existing LVM volume groups or create new LVM volume groups on a blank partition.
+ </div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Optional: Create new partition for LVM volumes</strong></p><div class="para">
+ These steps describe how to create a new partition and LVM volume group on a new hard disk drive.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ This procedure will remove all data from the selected storage device.
+ </div></div></div><ol class="a"><li class="step"><p class="title"><strong>Create a new partition</strong></p><div class="para">
+ Use the <code class="command">fdisk</code> command to create a new disk partition from the command line. The following example creates a new partition that uses the entire disk on the storage device <code class="computeroutput">/dev/sdb</code>.
+ </div><pre class="screen"># fdisk /dev/sdb
+Command (m for help):
+</pre><div class="para">
+ Press <em class="parameter"><code>n</code></em> for a new partition.
+ </div></li><li class="step"><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 class="step"><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 class="step"><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 class="step"><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 class="step"><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 class="step"><div class="para">
+ Choose the partition you created in the previous steps. In this example, the partition number is <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 class="step"><div class="para">
+ Enter <em class="parameter"><code>8e</code></em> for a Linux LVM partition.
+ </div><pre class="screen">Hex code (type L to list codes): <em class="parameter"><code>8e</code></em>
+</pre></li><li class="step"><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 class="step"><p class="title"><strong>Create a new LVM volume group</strong></p><div class="para">
+ Create a new LVM volume group with the <code class="command">vgcreate</code> command. This example creates a volume group named <em class="replaceable"><code>guest_images_lvm</code></em>.
+ </div><pre class="screen"># vgcreate <em class="replaceable"><code>guest_images_lvm</code></em> /dev/sdb1
+ Physical volume "/dev/vdb1" successfully created
+ Volume group "<em class="replaceable"><code>guest_images_lvm</code></em>" successfully created
+</pre></li></ol><div class="para">
+ The new LVM volume group, <em class="replaceable"><code>guest_images_lvm</code></em>, can now be used for an LVM-based storage pool.
+ </div></li><li class="step"><p class="title"><strong>Open the storage pool settings</strong></p><ol class="a"><li class="step"><div class="para">
+ In the <code class="command">virt-manager</code> graphical interface, select the host from the main window.
+ </div><div class="para">
+ Open the <span class="guilabel"><strong>Edit</strong></span> menu and select <span class="guilabel"><strong>Connection Details</strong></span>
+ </div><div class="figure" id="connection-details"><div class="figure-contents"><div class="mediaobject"><img src="images/Connection_Details.png" width="444" alt="Connection details" /></div></div><h6>Figure 27.12. Connection details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Click on the <span class="guilabel"><strong>Storage</strong></span> tab.
+ </div><div class="figure" id="lvm-storage-tab"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Storage tab" /></div></div><h6>Figure 27.13. Storage tab</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Create the new storage pool</strong></p><ol class="a"><li class="step"><p class="title"><strong>Start the Wizard</strong></p><div class="para">
+ Press the <span class="guilabel"><strong>+</strong></span> button (the add pool button). The <span class="guilabel"><strong>Add a New Storage Pool</strong></span> wizard appears.
+ </div><div class="para">
+ Choose a <span class="guibutton"><strong>Name</strong></span> for the storage pool. We use <em class="replaceable"><code>guest_images_lvm</code></em> for this example. Then change the <span class="guibutton"><strong>Type</strong></span> to <code class="command">logical: LVM Volume Group</code>, and
+ </div><div class="figure" id="lvm-add"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_lvm_step_1_name_and_type.png" width="444" alt="Add LVM storage pool" /></div></div><h6>Figure 27.14. Add LVM storage pool</h6></div><br class="figure-break" /><div class="para">
+ Press the <span class="guibutton"><strong>Forward</strong></span> button to continue.
+ </div></li><li class="step"><p class="title"><strong>Add a new pool (part 2)</strong></p><div class="para">
+ Change the <span class="guibutton"><strong>Target Path</strong></span> field. This example uses <em class="replaceable"><code>/guest_images</code></em>.
+ </div><div class="para">
+ Now fill in the <span class="guibutton"><strong>Target Path</strong></span> and <span class="guibutton"><strong>Source Path</strong></span> fields, then tick the <span class="guibutton"><strong>Build Pool</strong></span> check box.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Use the <span class="guibutton"><strong>Target Path</strong></span> field to <span class="emphasis"><em>either</em></span> select an existing LVM volume group or as the name for a new volume group. The default format is <code class="computeroutput">/dev/</code><em class="replaceable"><code>storage_pool_name</code></em>.
+ </div><div class="para">
+ This example uses a new volume group named <em class="replaceable"><code>/dev/guest_images_lvm</code></em>.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="command">Source Path</code> field is optional if an existing LVM volume group is used in the <span class="guibutton"><strong>Target Path</strong></span>.
+ </div><div class="para">
+ For new LVM volume groups, input the location of a storage device in the <code class="command">Source Path</code> field. This example uses a blank partition <em class="replaceable"><code>/dev/sdc</code></em>.
+ </div></li><li class="listitem"><div class="para">
+ The <span class="guibutton"><strong>Build Pool</strong></span> checkbox instructs <code class="command">virt-manager</code> to create a new LVM volume group. If you are using an existing volume group you should not select the <span class="guibutton"><strong>Build Pool</strong></span> checkbox.
+ </div><div class="para">
+ This example is using a blank partition to create a new volume group so the <span class="guibutton"><strong>Build Pool</strong></span> checkbox must be selected.
+ </div></li></ul></div><div class="figure" id="lvm-pool-step2"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_lvm_step_2a_paths_and_pool.png" width="444" alt="Add target and source" /></div></div><h6>Figure 27.15. Add target and source</h6></div><br class="figure-break" /><div class="para">
+ Verify the details and press the <span class="guibutton"><strong>Finish</strong></span> button format the LVM volume group and create the storage pool.
+ </div></li><li class="step"><p class="title"><strong>Confirm the device to be formatted</strong></p><div class="para">
+ A warning message appears.
+ </div><div class="figure" id="lvm-warning-message"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_lvm_step_2b_format_warning.png" alt="Warning message" /></div></div><h6>Figure 27.16. Warning message</h6></div><br class="figure-break" /><div class="para">
+ Press the <span class="guilabel"><strong>Yes</strong></span> button to proceed to erase all data on the storage device and create the storage pool.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Verify the new storage pool</strong></p><div class="para">
+ The new storage pool will appear in the list on the left after a few seconds. Verify the details are what you expect, <em class="replaceable"><code>465.76 GB Free</code></em> in our example. Also verify the <span class="guibutton"><strong>State</strong></span> field reports the new storage pool as <em class="replaceable"><code>Active</code></em>.
+ </div><div class="para">
+ It is generally a good idea to have the <span class="guibutton"><strong>Autostart</strong></span> check box enabled, to ensure the storage pool starts automatically with libvirtd.
+ </div><div class="figure" id="confirm-lvm-pool"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_lvm_step_3_result.png" width="444" alt="Confirm LVM storage pool details" /></div></div><h6>Figure 27.17. Confirm LVM storage pool details</h6></div><br class="figure-break" /><div class="para">
+ Close the Host Details dialog, as the task is now complete.
+ </div></li></ol></div></div><div class="section" id="del-stor-pool-lvm"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">27.1.4.2. Deleting a storage pool using virt-manager</h4></div></div></div><div class="para">
+ This procedure demonstrates how to delete a storage pool.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it. To do this, select the storage pool you want to stop and click the red X icon at the bottom of the Storage window.
+ </div><div class="figure" id="stop-icon3"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Stop Icon" /></div></div><h6>Figure 27.18. Stop Icon</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Delete the storage pool by clicking the Trash can icon. This icon is only enabled if you stop the storage pool first.
+ </div></li></ol></div></div><div class="section" id="idm122939664"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm122939664">27.1.4.3. Creating an LVM-based storage pool with virsh</h4></div></div></div><div class="para">
+ This section outlines the steps required to create an LVM-based storage pool with the <code class="command">virsh</code> command. It uses the example of a pool named <span class="bold bold"><strong>guest_images_lvm</strong></span> from a single drive (<code class="filename">/dev/sdc</code>). This is only an example and your settings should be substituted as appropriate.
+ </div><div class="procedure"><h6>Procedure 27.3. Creating an LVM-based storage pool with virsh</h6><ol class="1"><li class="step"><div class="para">
+ Define the pool name <span class="bold bold"><strong>guest_images_lvm</strong></span>.
+ </div><pre class="screen"># virsh pool-define-as <em class="replaceable"><code>guest_images_lvm</code></em> logical - - <em class="replaceable"><code>/dev/sdc</code></em> <em class="replaceable"><code>libvirt_lvm</code></em> \ /dev/<em class="replaceable"><code>libvirt_lvm</code></em>
+Pool guest_images_lvm defined
+</pre></li><li class="step"><div class="para">
+ Build the pool according to the specified name.
+ </div><pre class="screen">
+# virsh pool-build <em class="replaceable"><code>guest_images_lvm</code></em>
+
+Pool guest_images_lvm built
+</pre></li><li class="step"><div class="para">
+ Initialize the new pool.
+ </div><pre class="screen">
+# virsh pool-start <em class="replaceable"><code>guest_images_lvm</code></em>
+
+Pool guest_images_lvm started
+</pre></li><li class="step"><div class="para">
+ Show the volume group information with the <code class="command">vgs</code> command.
+ </div><pre class="screen">
+# vgs
+VG #PV #LV #SN Attr VSize VFree
+libvirt_lvm 1 0 0 wz--n- 465.76g 465.76g
+</pre></li><li class="step"><div class="para">
+ Set the pool to start automatically.
+ </div><pre class="screen">
+# virsh pool-autostart <em class="replaceable"><code>guest_images_lvm</code></em>
+Pool guest_images_lvm marked as autostarted
+</pre></li><li class="step"><div class="para">
+ List the available pools with the <code class="command">virsh</code> command.
+ </div><pre class="screen">
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_lvm active yes
+</pre></li><li class="step"><div class="para">
+ The following commands demonstrate the creation of three volumes (<span class="emphasis"><em>volume1</em></span>, <span class="emphasis"><em>volume2</em></span> and <span class="emphasis"><em>volume3</em></span>) within this pool.
+ </div><pre class="screen">
+# virsh vol-create-as <em class="replaceable"><code>guest_images_lvm</code></em> <em class="replaceable"><code>volume1</code></em> <em class="replaceable"><code>8G</code></em>
+Vol volume1 created
+
+# virsh vol-create-as <em class="replaceable"><code>guest_images_lvm</code></em> <em class="replaceable"><code>volume2</code></em> <em class="replaceable"><code>8G</code></em>
+Vol volume2 created
+
+# virsh vol-create-as <em class="replaceable"><code>guest_images_lvm</code></em> <em class="replaceable"><code>volume3</code></em> <em class="replaceable"><code>8G</code></em>
+Vol volume3 created
+</pre></li><li class="step"><div class="para">
+ List the available volumes in this pool with the <code class="command">virsh</code> command.
+ </div><pre class="screen">
+# virsh vol-list <em class="replaceable"><code>guest_images_lvm</code></em>
+Name Path
+-----------------------------------------
+volume1 /dev/libvirt_lvm/volume1
+volume2 /dev/libvirt_lvm/volume2
+volume3 /dev/libvirt_lvm/volume3
+</pre></li><li class="step"><div class="para">
+ The following two commands (<code class="command">lvscan</code> and <code class="command">lvs</code>) display further information about the newly created volumes.
+ </div><pre class="screen">
+# lvscan
+ACTIVE '/dev/libvirt_lvm/volume1' [8.00 GiB] inherit
+ACTIVE '/dev/libvirt_lvm/volume2' [8.00 GiB] inherit
+ACTIVE '/dev/libvirt_lvm/volume3' [8.00 GiB] inherit
+
+# lvs
+LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
+volume1 libvirt_lvm -wi-a- 8.00g
+volume2 libvirt_lvm -wi-a- 8.00g
+volume3 libvirt_lvm -wi-a- 8.00g
+</pre></li></ol></div></div><div class="section" id="delete-lvm-storage-pool-virsh"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">27.1.4.4. Deleting a storage pool using virsh</h4></div></div></div><div class="para">
+ The following demonstrates how to delete a storage pool using virsh:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it.
+ </div><pre class="screen"># virsh pool-destroy <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Optionally, if you want to remove the directory where the storage pool resides use the following command:
+ </div><pre class="screen"># virsh pool-delete <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Remove the storage pool's definition
+ </div><pre class="screen"># virsh pool-undefine <em class="replaceable"><code>guest_images_disk</code></em></pre></li></ol></div></div></div><div xml:lang="en-US" class="section" id="sect-Virtualization-Storage_Pools-Creating-iSCSI" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">27.1.5. iSCSI-based storage pools</h3></div></div></div><div class="para">
+ This section covers using iSCSI-based devices to store guests.
+ </div><div class="para">
+ iSCSI (Internet Small Computer System Interface) is a network protocol for sharing storage devices. iSCSI connects initiators (storage clients) to targets (storage servers) using SCSI instructions over the IP layer.
+ </div><div class="section" id="idm75530912"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm75530912">27.1.5.1. Configuring a software iSCSI target</h4></div></div></div><div class="para">
+ The <span class="package">scsi-target-utils</span> package provides a tool for creating software-backed iSCSI targets.
+ </div><div class="procedure"><h6>Procedure 27.4. Creating an iSCSI target</h6><ol class="1"><li class="step"><p class="title"><strong>Install the required packages</strong></p><div class="para">
+ Install the <span class="package">scsi-target-utils</span> package and all dependencies
+ </div><pre class="screen"># yum install scsi-target-utils</pre></li><li class="step"><p class="title"><strong>Start the tgtd service</strong></p><div class="para">
+ The <code class="command">tgtd</code> service hosts SCSI targets and uses the iSCSI protocol to host targets. Start the <code class="command">tgtd</code> service and make the service persistent after restarting with the <code class="command">chkconfig</code> command.
+ </div><pre class="screen"># service tgtd start
+# chkconfig tgtd on</pre></li><li class="step"><p class="title"><strong>Optional: Create LVM volumes</strong></p><div class="para">
+ LVM volumes are useful for iSCSI backing images. LVM snapshots and resizing can be beneficial for guests. This example creates an LVM image named <em class="replaceable"><code>virtimage1</code></em> on a new volume group named <em class="replaceable"><code>virtstore</code></em> on a RAID5 array for hosting guests with iSCSI.
+ </div><ol class="a"><li class="step"><p class="title"><strong>Create the RAID array</strong></p><div class="para">
+ Creating software RAID5 arrays is covered by the <em class="citetitle">Fedora Deployment Guide</em>.
+ </div></li><li class="step"><p class="title"><strong>Create the LVM volume group</strong></p><div class="para">
+ Create a volume group named <em class="replaceable"><code>virtstore</code></em> with the <code class="command">vgcreate</code> command.
+ </div><pre class="screen"># vgcreate <em class="replaceable"><code>virtstore</code></em> /dev/md1</pre></li><li class="step"><p class="title"><strong>Create a LVM logical volume</strong></p><div class="para">
+ Create a logical volume group named <em class="replaceable"><code>virtimage1</code></em> on the <em class="replaceable"><code>virtstore</code></em> volume group with a size of 20GB using the <code class="command">lvcreate</code> command.
+ </div><pre class="screen"># lvcreate --size 20G -n <em class="replaceable"><code>virtimage1 virtstore</code></em></pre><div class="para">
+ The new logical volume, <em class="replaceable"><code>virtimage1</code></em>, is ready to use for iSCSI.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Optional: Create file-based images</strong></p><div class="para">
+ File-based storage is sufficient for testing but is not recommended for production environments or any significant I/O activity. This optional procedure creates a file based imaged named <em class="replaceable"><code>virtimage2.img</code></em> for an iSCSI target.
+ </div><ol class="a"><li class="step"><p class="title"><strong>Create a new directory for the image</strong></p><div class="para">
+ Create a new directory to store the image. The directory must have the correct SELinux contexts.
+ </div><pre class="screen"># mkdir -p /var/lib/tgtd/<em class="replaceable"><code>virtualization</code></em>
+</pre></li><li class="step"><p class="title"><strong>Create the image file</strong></p><div class="para">
+ Create an image named <em class="replaceable"><code>virtimage2.img</code></em> with a size of 10GB.
+ </div><pre class="screen"># dd if=/dev/zero of=/var/lib/tgtd/<em class="replaceable"><code>virtualization</code></em>/<em class="replaceable"><code>virtimage2.img</code></em> bs=1M seek=10000 count=0</pre></li><li class="step"><p class="title"><strong>Configure SELinux file contexts</strong></p><div class="para">
+ Configure the correct SELinux context for the new image and directory.
+ </div><pre class="screen"># restorecon -R /var/lib/tgtd</pre><div class="para">
+ The new file-based image, <em class="replaceable"><code>virtimage2.img</code></em>, is ready to use for iSCSI.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Create targets</strong></p><div class="para">
+ Targets can be created by adding a XML entry to the <code class="filename">/etc/tgt/targets.conf</code> file. The <code class="computeroutput">target</code> attribute requires an iSCSI Qualified Name (IQN). The IQN is in the format:
+ </div><pre class="screen">iqn.<em class="replaceable"><code>yyyy</code></em>-<em class="replaceable"><code>mm</code></em>.<em class="replaceable"><code>reversed domain name</code></em>:<em class="replaceable"><code>optional identifier text</code></em>
+</pre><div class="para">
+ Where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="replaceable"><code>yyyy</code></em>-<em class="replaceable"><code>mm</code></em> represents the year and month the device was started (for example: <em class="replaceable"><code>2010-05</code></em>);
+ </div></li><li class="listitem"><div class="para">
+ <em class="replaceable"><code>reversed domain name</code></em> is the hosts domain name in reverse (for example <em class="replaceable"><code>server1.example.com</code></em> in an IQN would be <em class="replaceable"><code>com.example.server1</code></em>); and
+ </div></li><li class="listitem"><div class="para">
+ <em class="replaceable"><code>optional identifier text</code></em> is any text string, without spaces, that assists the administrator in identifying devices or hardware.
+ </div></li></ul></div><div class="para">
+ This example creates iSCSI targets for the two types of images created in the optional steps on <em class="replaceable"><code>server1.example.com</code></em> with an optional identifier <em class="replaceable"><code>trial</code></em>. Add the following to the <code class="filename">/etc/tgt/targets.conf</code> file.
+ </div><pre class="screen">
+<target iqn.2010-05.com.example.<em class="replaceable"><code>server1</code></em>:<em class="replaceable"><code>trial</code></em>>
+ backing-store /dev/<em class="replaceable"><code>virtstore</code></em>/<em class="replaceable"><code>virtimage1</code></em> #LUN 1
+ backing-store /var/lib/tgtd/<em class="replaceable"><code>virtualization</code></em>/<em class="replaceable"><code>virtimage2.img</code></em> #LUN 2
+ write-cache off
+</target>
+</pre><div class="para">
+ Ensure that the <code class="filename">/etc/tgt/targets.conf</code> file contains the <code class="computeroutput">default-driver iscsi</code> line to set the driver type as iSCSI. The driver uses iSCSI by default.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ This example creates a globally accessible target without access control. Refer to the scsi-target-utils for information on implementing secure access.
+ </div></div></div></li><li class="step"><p class="title"><strong>Restart the tgtd service</strong></p><div class="para">
+ Restart the <code class="systemitem">tgtd</code> service to reload the configuration changes.
+ </div><pre class="screen"># service tgtd restart</pre></li><li class="step"><p class="title"><strong>iptables configuration</strong></p><div class="para">
+ Open port 3260 for iSCSI access with <code class="command">iptables</code>.
+ </div><pre class="screen"># iptables -I INPUT -p tcp -m tcp --dport 3260 -j ACCEPT
+# service iptables save
+# service iptables restart</pre></li><li class="step"><p class="title"><strong>Verify the new targets</strong></p><div class="para">
+ View the new targets to ensure the setup was successful with the <code class="command">tgt-admin --show</code> command.
+ </div><pre class="screen">
+# tgt-admin --show
+Target 1: iqn.2010-05.com.example.server1:trial
+System information:
+Driver: iscsi
+State: ready
+I_T nexus information:
+LUN information:
+LUN: 0
+ Type: controller
+ SCSI ID: IET 00010000
+ SCSI SN: beaf10
+ Size: 0 MB
+ Online: Yes
+ Removable media: No
+ Backing store type: rdwr
+ Backing store path: None
+LUN: 1
+ Type: disk
+ SCSI ID: IET 00010001
+ SCSI SN: beaf11
+ Size: 20000 MB
+ Online: Yes
+ Removable media: No
+ Backing store type: rdwr
+ Backing store path: /dev/<em class="replaceable"><code>virtstore</code></em>/<em class="replaceable"><code>virtimage1</code></em>
+LUN: 2
+ Type: disk
+ SCSI ID: IET 00010002
+ SCSI SN: beaf12
+ Size: 10000 MB
+ Online: Yes
+ Removable media: No
+ Backing store type: rdwr
+ Backing store path: /var/lib/tgtd/<em class="replaceable"><code>virtualization</code></em>/<em class="replaceable"><code>virtimage2.img</code></em>
+Account information:
+ACL information:
+ALL
+</pre><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ The ACL list is set to all. This allows all systems on the local network to access this device. It is recommended to set host access ACLs for production environments.
+ </div></div></div></li><li class="step"><p class="title"><strong>Optional: Test discovery</strong></p><div class="para">
+ Test whether the new iSCSI device is discoverable.
+ </div><pre class="screen"># iscsiadm --mode discovery --type sendtargets --portal server1.example.com
+127.0.0.1:3260,1 iqn.2010-05.com.example.server1:iscsirhel6guest</pre></li><li class="step"><p class="title"><strong>Optional: Test attaching the device</strong></p><div class="para">
+ Attach the new device (<em class="replaceable"><code>iqn.2010-05.com.example.server1:iscsirhel6guest</code></em>) to determine whether the device can be attached.
+ </div><pre class="screen"># iscsiadm -d2 -m node --login
+scsiadm: Max file limits 1024 1024
+
+Logging in to [iface: default, target: iqn.2010-05.com.example.server1:iscsirhel6guest, portal: 10.0.0.1,3260]
+Login to [iface: default, target: iqn.2010-05.com.example.server1:iscsirhel6guest, portal: 10.0.0.1,3260] successful.</pre><div class="para">
+ Detach the device.
+ </div><pre class="screen"># iscsiadm -d2 -m node --logout
+scsiadm: Max file limits 1024 1024
+
+Logging out of session [sid: 2, target: iqn.2010-05.com.example.server1:iscsirhel6guest, portal: 10.0.0.1,3260
+Logout of [sid: 2, target: iqn.2010-05.com.example.server1:iscsirhel6guest, portal: 10.0.0.1,3260] successful.</pre></li></ol></div><div class="para">
+ An iSCSI device is now ready to use for virtualization.
+ </div></div><div class="section" id="idm53692640"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm53692640">27.1.5.2. Adding an iSCSI target to virt-manager</h4></div></div></div><div class="para">
+ This procedure covers creating a storage pool with an iSCSI target in <code class="command">virt-manager</code>.
+ </div><div class="procedure"><h6>Procedure 27.5. Adding an iSCSI device to virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Open the host storage tab</strong></p><div class="para">
+ Open the <span class="guilabel"><strong>Storage</strong></span> tab in the <span class="guilabel"><strong>Host Details</strong></span> window.
+ </div><ol class="a"><li class="step"><div class="para">
+ Open <code class="command">virt-manager</code>.
+ </div></li><li class="step"><div class="para">
+ Select a host from the main <code class="command">virt-manager</code> window. Click <span class="guilabel"><strong>Edit menu</strong></span> and select <span class="guilabel"><strong>Connection Details</strong></span>.
+ </div><div class="figure" id="scsi-connection-details"><div class="figure-contents"><div class="mediaobject"><img src="images/Connection_Details.png" width="444" alt="Connection details" /></div></div><h6>Figure 27.19. Connection details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Click on the <span class="guilabel"><strong>Storage</strong></span> tab.
+ </div><div class="figure" id="scsi-storage-tab"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Storage menu" /></div></div><h6>Figure 27.20. Storage menu</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Add a new pool (part 1)</strong></p><div class="para">
+ Press the <span class="guilabel"><strong>+</strong></span> button (the add pool button). The <span class="guilabel"><strong>Add a New Storage Pool</strong></span> wizard appears.
+ </div><div class="figure" id="iscsi-storage-pool"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_add_storage_pool1.png" width="444" alt="Add an iscsi storage pool name and type" /></div></div><h6>Figure 27.21. Add an iscsi storage pool name and type</h6></div><br class="figure-break" /><div class="para">
+ Choose a name for the storage pool, change the Type to iscsi, and press <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Add a new pool (part 2)</strong></p><div class="para">
+ Enter the target path for the device, the host name of the target and the source path (the IQN). The <span class="guilabel"><strong>Format</strong></span> option is not available as formatting is handled by the guests. It is not advised to edit the <span class="guilabel"><strong>Target Path</strong></span>. The default target path value, <code class="filename">/dev/disk/by-path/</code>, adds the drive path to that directory. The target path should be the same on all hosts for migration.
+ </div><div class="para">
+ Enter the hostname or IP address of the iSCSI target. This example uses <code class="computeroutput">server1.example.com</code>.
+ </div><div class="para">
+ Enter the source path, for the iSCSI target. This example uses <code class="computeroutput">demo-target</code>.
+ </div><div class="para">
+ Check the <span class="guilabel"><strong>IQN</strong></span> checkbox to enter the IQN. This example uses <code class="computeroutput">iqn.2010-05.com.example.server1:iscsirhel6guest</code>.
+ </div><div class="figure" id="storage-pool-iscsi-add"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_add_storage_pool2.png" width="444" alt="Create an iscsi storage pool" /></div></div><h6>Figure 27.22. Create an iscsi storage pool</h6></div><br class="figure-break" /><div class="para">
+ Press <span class="guibutton"><strong>Finish</strong></span> to create the new storage pool.
+ </div></li></ol></div></div><div class="section" id="del-stor-pool-iscsi"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">27.1.5.3. Deleting a storage pool using virt-manager</h4></div></div></div><div class="para">
+ This procedure demonstrates how to delete a storage pool.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it. To do this, select the storage pool you want to stop and click the red X icon at the bottom of the Storage window.
+ </div><div class="figure" id="stop-icon4"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Stop Icon" /></div></div><h6>Figure 27.23. Stop Icon</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Delete the storage pool by clicking the Trash can icon. This icon is only enabled if you stop the storage pool first.
+ </div></li></ol></div></div><div class="section" id="idm66133952"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm66133952">27.1.5.4. Creating an iSCSI-based storage pool with virsh</h4></div></div></div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Use pool-define-as to define the pool from the command line</strong></p><div class="para">
+ Storage pool definitions can be created with the <code class="command">virsh</code> command line tool. Creating storage pools with <code class="command">virsh</code> is useful for systems administrators using scripts to create multiple storage pools.
+ </div><div class="para">
+ The <code class="command">virsh pool-define-as</code> command has several parameters which are accepted in the following format:
+ </div><pre class="screen">virsh pool-define-as <em class="parameter"><code>name type source-host source-path source-dev source-name</code></em> <em class="replaceable"><code>target</code></em>
+</pre><div class="para">
+ The parameters are explained as follows:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">type</span></dt><dd><div class="para">
+ defines this pool as a particular type, iscsi for example
+ </div></dd><dt class="varlistentry"><span class="term">name</span></dt><dd><div class="para">
+ must be unique and sets the name for the storage pool
+ </div></dd><dt class="varlistentry"><span class="term">source-host and source-path</span></dt><dd><div class="para">
+ the hostname and iSCSI IQN respectively
+ </div></dd><dt class="varlistentry"><span class="term">source-dev and source-name</span></dt><dd><div class="para">
+ these parameters are not required for iSCSI-based pools, use a <span class="keycap"><strong>-</strong></span> character to leave the field blank.
+ </div></dd><dt class="varlistentry"><span class="term">target</span></dt><dd><div class="para">
+ defines the location for mounting the iSCSI device on the host
+ </div></dd></dl></div><div class="para">
+ The example below creates the same iSCSI-based storage pool as the previous step.
+ </div><pre class="screen"># virsh pool-define-as --name scsirhel6guest --type iscsi \
+ --source-host server1.example.com \
+ --source-dev iqn.2010-05.com.example.server1:iscsirhel6guest
+ --target /dev/disk/by-path
+Pool iscsirhel6guest defined</pre></li><li class="step"><p class="title"><strong>Verify the storage pool is listed</strong></p><div class="para">
+ Verify the storage pool object is created correctly and the state reports as <code class="computeroutput">inactive</code>.
+ </div><pre class="screen"># virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+<em class="replaceable"><code>iscsirhel6guest</code></em> inactive no</pre></li><li class="step"><p class="title"><strong>Start the storage pool</strong></p><div class="para">
+ Use the virsh command <code class="command">pool-start</code> for this. <code class="command">pool-start</code> enables a directory storage pool, allowing it to be used for volumes and guests.
+ </div><pre class="screen"># virsh pool-start <em class="replaceable"><code>guest_images_disk</code></em>
+Pool guest_images_disk started
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+<em class="replaceable"><code>iscsirhel6guest</code></em> active no
+</pre></li><li class="step"><p class="title"><strong>Turn on autostart</strong></p><div class="para">
+ Turn on <em class="parameter"><code>autostart</code></em> for the storage pool. Autostart configures the <code class="systemitem">libvirtd</code> service to start the storage pool when the service starts.
+ </div><pre class="screen"># virsh pool-autostart <em class="replaceable"><code>iscsirhel6guest</code></em>
+Pool iscsirhel6guest marked as autostarted</pre><div class="para">
+ Verify that the <em class="replaceable"><code>iscsirhel6guest</code></em> pool has autostart set:
+ </div><pre class="screen"># virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+<em class="replaceable"><code>iscsirhel6guest</code></em> active yes
+</pre></li><li class="step"><p class="title"><strong>Verify the storage pool configuration</strong></p><div class="para">
+ Verify the storage pool was created correctly, the sizes reported correctly, and the state reports as <code class="computeroutput">running</code>.
+ </div><pre class="screen"># virsh pool-info <em class="replaceable"><code>iscsirhel6guest</code></em>
+Name: <em class="replaceable"><code>iscsirhel6guest</code></em>
+UUID: afcc5367-6770-e151-bcb3-847bc36c5e28
+State: running
+Persistent: unknown
+Autostart: yes
+Capacity: 100.31 GB
+Allocation: 0.00
+Available: 100.31 GB
+</pre></li></ol></div><div class="para">
+ An iSCSI-based storage pool is now available.
+ </div></div><div class="section" id="delete-iscsi-storage-pool-virsh"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">27.1.5.5. Deleting a storage pool using virsh</h4></div></div></div><div class="para">
+ The following demonstrates how to delete a storage pool using virsh:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it.
+ </div><pre class="screen"># virsh pool-destroy <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Remove the storage pool's definition
+ </div><pre class="screen"># virsh pool-undefine <em class="replaceable"><code>guest_images_disk</code></em></pre></li></ol></div></div></div><div xml:lang="en-US" class="section" id="sect-Virtualization-Storage_Pools-Creating-NFS" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">27.1.6. NFS-based storage pools</h3></div></div></div><div class="para">
+ This procedure covers creating a storage pool with a NFS mount point in <code class="command">virt-manager</code>.
+ </div><div class="section" id="idm83290176"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm83290176">27.1.6.1. Creating a NFS-based storage pool with virt-manager</h4></div></div></div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Open the host storage tab</strong></p><div class="para">
+ Open the <span class="guilabel"><strong>Storage</strong></span> tab in the <span class="guilabel"><strong>Host Details</strong></span> window.
+ </div><ol class="a"><li class="step"><div class="para">
+ Open <code class="command">virt-manager</code>.
+ </div></li><li class="step"><div class="para">
+ Select a host from the main <code class="command">virt-manager</code> window. Click <span class="guilabel"><strong>Edit menu</strong></span> and select <span class="guilabel"><strong>Connection Details</strong></span>.
+ </div><div class="figure" id="nfs-connection-details"><div class="figure-contents"><div class="mediaobject"><img src="images/Connection_Details.png" width="444" alt="Connection details" /></div></div><h6>Figure 27.24. Connection details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Click on the Storage tab.
+ </div><div class="figure" id="nfs-storage-tab"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Storage tab" /></div></div><h6>Figure 27.25. Storage tab</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Create a new pool (part 1)</strong></p><div class="para">
+ Press the <span class="guilabel"><strong>+</strong></span> button (the add pool button). The <span class="guilabel"><strong>Add a New Storage Pool</strong></span> wizard appears.
+ </div><div class="figure" id="add-nfs-pool-1"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_add_nfs_step1.png" width="444" alt="Add an NFS name and type" /></div></div><h6>Figure 27.26. Add an NFS name and type</h6></div><br class="figure-break" /><div class="para">
+ Choose a name for the storage pool and press <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Create a new pool (part 2)</strong></p><div class="para">
+ Enter the target path for the device, the hostname and the NFS share path. Set the <span class="guilabel"><strong>Format</strong></span> option to <span class="guilabel"><strong>NFS</strong></span> or <span class="guilabel"><strong>auto</strong></span> (to detect the type). The target path must be identical on all hosts for migration.
+ </div><div class="para">
+ Enter the hostname or IP address of the NFS server. This example uses <code class="computeroutput">server1.example.com</code>.
+ </div><div class="para">
+ Enter the NFS path. This example uses <code class="computeroutput">/nfstrial</code>.
+ </div><div class="figure" id="nfs-add-pool-2"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_add_nfs_step2.png" width="444" alt="Create an NFS storage pool" /></div></div><h6>Figure 27.27. Create an NFS storage pool</h6></div><br class="figure-break" /><div class="para">
+ Press <span class="guibutton"><strong>Finish</strong></span> to create the new storage pool.
+ </div></li></ol></div></div><div class="section" id="del-stor-pool-nfs"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">27.1.6.2. Deleting a storage pool using virt-manager</h4></div></div></div><div class="para">
+ This procedure demonstrates how to delete a storage pool.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it. To do this, select the storage pool you want to stop and click the red X icon at the bottom of the Storage window.
+ </div><div class="figure" id="stop-icon5"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Stop Icon" /></div></div><h6>Figure 27.28. Stop Icon</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Delete the storage pool by clicking the Trash can icon. This icon is only enabled if you stop the storage pool first.
+ </div></li></ol></div></div></div></div></div><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_Guide-Storage_Volumes" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 28. Volumes </h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Virtualization-Storage_Volumes-Creating_volumes">28.1. Creating volumes</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Storage_Volumes-Cloning_volumes">28.2. Cloning volumes</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests">28.3. Adding storage devices to guests</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Adding_storage_devices_to_guests-Adding_file_based_storage_to_a_guest">28.3.1. Adding file based storage to a guest</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Adding_storage_devices_to_guests-
Adding_hard_drives_and_other_block_devices_to_a_guest">28.3.2. Adding hard drives and other block devices to a guest</a></span></dt><dt><span class="section"><a href="#sect-Managing_storage_controllers_in_a_guest">28.3.3. Managing storage controllers in a guest</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Virtualization-Storage_Volumes-Deleting_volumes">28.4. Deleting and removing volumes</a></span></dt></dl></div><div class="section" id="sect-Virtualization-Storage_Volumes-Creating_volumes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">28.1. Creating volumes</h2></div></div></div><div class="para">
+ This section shows how to create disk volumes inside a block based storage pool. In the example below, the <code class="command">virsh vol-create-as</code> command will create a storage volume with a specific size in GB within the <em class="replaceable"><code>guest_images_disk</code></em> storage pool. As this command is repeated per volume needed, three volumes are created as shown in the example.
+ </div><pre class="screen"># virsh vol-create-as <em class="replaceable"><code>guest_images_disk</code></em> <em class="replaceable"><code>volume1</code></em> <em class="replaceable"><code>8</code></em>G
+Vol volume1 created
+
+# virsh vol-create-as <em class="replaceable"><code>guest_images_disk</code></em> <em class="replaceable"><code>volume2</code></em> <em class="replaceable"><code>8</code></em>G
+Vol volume2 created
+
+# virsh vol-create-as <em class="replaceable"><code>guest_images_disk</code></em> <em class="replaceable"><code>volume3</code></em> <em class="replaceable"><code>8</code></em>G
+Vol volume3 created
+
+# virsh vol-list <em class="replaceable"><code>guest_images_disk</code></em>
+Name Path
+-----------------------------------------
+volume1 /dev/sdb1
+volume2 /dev/sdb2
+volume3 /dev/sdb3
+
+# <code class="command">parted -s <em class="replaceable"><code>/dev/sdb</code></em> print</code>
+Model: ATA ST3500418AS (scsi)
+Disk /dev/sdb: 500GB
+Sector size (logical/physical): 512B/512B
+Partition Table: gpt
+
+Number Start End Size File system Name Flags
+2 17.4kB 8590MB 8590MB primary
+3 8590MB 17.2GB 8590MB primary
+1 21.5GB 30.1GB 8590MB primary
+
+</pre></div><div class="section" id="sect-Virtualization-Storage_Volumes-Cloning_volumes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">28.2. Cloning volumes</h2></div></div></div><div class="para">
+ The new volume will be allocated from storage in the same storage pool as the volume being cloned. The <code class="command"> virsh vol-clone</code> must have the <code class="literal">--pool</code> argument which dictates the name of the storage pool that contains the volume to be cloned. The rest of the command names the volume to be cloned (volume3) and the name of the new volume that was cloned (clone1). The <code class="command">virsh vol-list</code> command lists the volumes that are present in the storage pool (guest_images_disk).
+ </div><pre class="screen"># virsh vol-clone --pool <em class="replaceable"><code>guest_images_disk</code></em> <em class="replaceable"><code>volume3</code></em> <em class="replaceable"><code>clone1</code></em>
+Vol clone1 cloned from volume3
+
+# <code class="command">virsh vol-list <em class="replaceable"><code>guest_images_disk</code></em></code>
+Name Path
+-----------------------------------------
+volume1 /dev/sdb1
+volume2 /dev/sdb2
+volume3 /dev/sdb3
+clone1 /dev/sdb4
+
+
+# <code class="command">parted -s <em class="replaceable"><code>/dev/sdb</code></em> print</code>
+Model: ATA ST3500418AS (scsi)
+Disk /dev/sdb: 500GB
+Sector size (logical/physical): 512B/512B
+Partition Table: msdos
+
+Number Start End Size File system Name Flags
+1 4211MB 12.8GB 8595MB primary
+2 12.8GB 21.4GB 8595MB primary
+3 21.4GB 30.0GB 8595MB primary
+4 30.0GB 38.6GB 8595MB primary
+
+</pre></div><div class="section" id="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">28.3. Adding storage devices to guests</h2></div></div></div><div class="para">
+ This section covers adding storage devices to a guest. Additional storage can only be added as needed.
+ </div><div class="section" id="sect-Virtualization-Adding_storage_devices_to_guests-Adding_file_based_storage_to_a_guest"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">28.3.1. Adding file based storage to a guest</h3></div></div></div><div class="para">
+ File-based storage is a collection of files that are stored on the hosts file system that act as virtualized hard drives for guests. To add file-based storage, perform the following steps:
+ </div><div class="procedure" id="proc-Virtualization-Adding_storage_devices"><h6>Procedure 28.1. Adding file-based storage</h6><ol class="1"><li class="step"><div class="para">
+ Create a storage file or use an existing file (such as an ISO file). Note that both of the following commands create a 4GB file which can be used as additional storage for a guest:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Pre-allocated files are recommended for file-based storage images. Create a pre-allocated file using the following <code class="command">dd</code> command as shown:
+ </div><pre class="screen"># dd if=/dev/zero of=/var/lib/libvirt/images/FileName.iso bs=1M count=4096</pre></li><li class="listitem"><div class="para">
+ Alternatively, create a sparse file instead of a pre-allocated file. Sparse files are created much faster and can be used for testing, but are not recommended for production environments due to data integrity and performance issues.
+ </div><pre class="screen"># dd if=/dev/zero of=/var/lib/libvirt/images/FileName.iso bs=1M seek=4096 count=0</pre></li></ul></div></li><li class="step"><div class="para">
+ Create the additional storage by writing a <em class="replaceable"><code><disk></code></em> element in a new file. In this example, this file will be known as <code class="filename">NewStorage.xml</code>.
+ </div><div class="para">
+ A <code class="literal"><disk></code> element describes the source of the disk, and a device name for the virtual block device. The device name should be unique across all devices in the guest, and identifies the bus on which the guest will find the virtual block device. The following example defines a virtio block device whose source is a file-based storage container named <code class="filename">FileName.img</code>:
+ </div><pre class="screen">
+<disk type='file' device='disk'>
+ <driver name='qemu' type='raw' cache='none'/>
+ <source file='/var/lib/libvirt/images/FileName.img'/>
+ <target dev='vdb'/>
+</disk>
+</pre><div class="para">
+ Device names can also start with "hd" or "sd", identifying respectively an IDE and a SCSI disk. The configuration file can also contain an <code class="literal"><address></code> sub-element that specifies the position on the bus for the new device. In the case of virtio block devices, this should be a PCI address. Omitting the <code class="literal"><address></code> sub-element lets libvirt locate and assign the next available PCI slot.
+ </div></li><li class="step"><div class="para">
+ Attach the CD-ROM as follows:
+ </div><pre class="screen">
+<disk type='file' device='cdrom'>
+ <driver name='qemu' type='raw' cache='none'/>
+ <source file='/var/lib/libvirt/images/FileName.iso'/>
+ <readonly/>
+ <target dev='hdc'/>
+</disk >
+</pre></li><li class="step"><div class="para">
+ Add the device defined in <code class="filename">NewStorage.xml</code> with your guest (<code class="literal">Guest1</code>):
+ </div><pre class="screen"># virsh attach-device --config Guest1 ~/NewStorage.xml</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ This change will only apply after the guest has been destroyed and restarted. In addition, persistent devices can only be added to a persistent domain, that is a domain whose configuration has been saved with <code class="command"> virsh define </code> command.
+ </div></div></div><div class="para">
+ If the guest is running, and you want the new device to be added temporarily until the guest is destroyed, omit the <code class="literal">--config</code> option:
+ </div><pre class="screen"># virsh attach-device Guest1 ~/NewStorage.xml</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The <code class="command">virsh</code> command allows for an <code class="command">attach-disk</code> command that can set a limited number of parameters with a simpler syntax and without the need to create an XML file. The <code class="command">attach-disk</code> command is used in a similar manner to the <code class="command">attach-device</code> command mentioned previously, as shown:
+ </div><pre class="screen">
+# virsh attach-disk Guest1 /var/lib/libvirt/images/FileName.iso vdb --cache none
+</pre><div class="para">
+ Note that the <code class="command">virsh attach-disk</code> command also accepts the <code class="literal">--config</code> option.
+ </div></div></div></li><li class="step"><div class="para">
+ Start the guest machine (if it is currently not running):
+ </div><pre class="screen"># virsh start Guest1</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The following steps are Linux guest specific. Other operating systems handle new storage devices in different ways. For other systems, refer to that operating system's documentation.
+ </div></div></div></li><li class="step" id="step-partition_disk"><p class="title"><strong>Partitioning the disk drive</strong></p><div class="para">
+ The guest now has a hard disk device called <code class="filename">/dev/vdb</code>. If required, partition this disk drive and format the partitions. If you do not see the device that you added, then it indicates that there is an issue with the disk hotplug in your guest's operating system.
+ </div><ol class="a"><li class="step"><div class="para">
+ Start <code class="command">fdisk</code> for the new device:
+ </div><pre class="screen">
+# fdisk /dev/vdb
+Command (m for help):
+</pre></li><li class="step"><div class="para">
+ Type <em class="parameter"><code>n</code></em> for a new partition.
+ </div></li><li class="step"><div class="para">
+ The following appears:
+ </div><pre class="screen">
+Command action
+e extended
+p primary partition (1-4)
+</pre><div class="para">
+ Type <em class="parameter"><code>p</code></em> for a primary partition.
+ </div></li><li class="step"><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): 1</pre></li><li class="step"><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 class="step"><div class="para">
+ Select the size of the partition. In this example the entire disk is allocated by pressing <code class="command">Enter</code>.
+ </div><pre class="screen">Last cylinder or +size or +sizeM or +sizeK (2-400, default 400):</pre></li><li class="step"><div class="para">
+ Enter <code class="command">t</code> to configure the partition type.
+ </div><pre class="screen">Command (m for help): t</pre></li><li class="step"><div class="para">
+ Select the partition you created in the previous steps. In this example, the partition number is <code class="command">1</code> as there was only one partition created and fdisk automatically selected partition 1.
+ </div><pre class="screen">Partition number (1-4): 1</pre></li><li class="step"><div class="para">
+ Enter <code class="command">83</code> for a Linux partition.
+ </div><pre class="screen">Hex code (type L to list codes): 83</pre></li><li class="step"><div class="para">
+ Enter <code class="command">w</code> to write changes and quit.
+ </div><pre class="screen">
+Command (m for help): w
+</pre></li><li class="step"><div class="para">
+ Format the new partition with the <code class="systemitem">ext3</code> file system.
+ </div><pre class="screen"># mke2fs -j /dev/vdb1</pre></li></ol></li><li class="step"><div class="para">
+ Create a mount directory, and mount the disk on the guest. In this example, the directory is located in <em class="replaceable"><code>myfiles</code></em>.
+ </div><pre class="screen">
+# mkdir /myfiles
+# mount /dev/vdb1 /myfiles
+</pre><div class="para">
+ The guest now has an additional virtualized file-based storage device. Note however, that this storage will not mount persistently across reboot unless defined in the guest's <code class="filename">/etc/fstab</code> file:
+ </div><pre class="screen">/dev/vdb1 <em class="replaceable"><code>/myfiles</code></em> ext3 defaults 0 0</pre></li></ol></div></div><div class="section" id="sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">28.3.2. Adding hard drives and other block devices to a guest</h3></div></div></div><div class="para">
+ System administrators use additional hard drives to provide increased storage space for a guest, or to separate system data from user data.
+ </div><div class="procedure" id="proc-Virtualization-Adding_storage_devices_to_guests-Adding_physical_block_devices_to_virtualized_guests"><h6>Procedure 28.2. Adding physical block devices to guests</h6><ol class="1"><li class="step"><div class="para">
+ This procedure describes how to add a hard drive on the host to a guest. It applies to all physical block devices, including CD-ROM, DVD and floppy devices.
+ </div><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 class="step"><div class="para">
+ Do one of the following:
+ </div><ol class="a"><li class="step"><div class="para">
+ Create the additional storage by writing a <code class="command">disk</code> element in a new file. In this example, this file will be known as <code class="filename">NewStorage.xml</code>. The following example is a configuration file section which contains an additional device-based storage container for the host partition <code class="filename">/dev/sr0:</code>
+ </div><pre class="screen">
+<disk type='block' device='disk'>
+ <driver name='qemu' type='raw' cache='none'/>
+ <source dev='/dev/sr0'/>
+ <target dev='vdc' bus='virtio'/>
+</disk>
+</pre></li><li class="step"><div class="para">
+ Follow the instruction in the previous section to attach the device to the guest. Alternatively, you can use the <em class="parameter"><code>virsh attach-disk</code></em> command, as shown:
+ </div><pre class="screen">
+# virsh attach-disk Guest1 /dev/sr0 vdc
+</pre><div class="para">
+ Note that the following options are available:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The<code class="command">virsh attach-disk</code> command also accepts the <em class="parameter"><code>--config</code></em>, <em class="parameter"><code>--type</code></em>, and <em class="parameter"><code>--mode</code></em> options, as shown:
+ </div><pre class="screen">
+# <code class="command">virsh attach-disk Guest1 /dev/sr0 vdc --config --type cdrom --mode readonly</code></pre></li><li class="listitem"><div class="para">
+ Additionally, <em class="parameter"><code> --type</code></em> also accepts <em class="parameter"><code>--type disk</code></em> in cases where the device is a hard drive.
+ </div></li></ul></div></li></ol></li><li class="step"><div class="para">
+ The guest now has a new hard disk device called <code class="filename">/dev/vdc</code> on Linux (or something similar, depending on what the guest OS chooses) or <code class="filename">D: drive</code> (for example) on Windows. You can now initialize the disk from the guest, following the standard procedures for the guest's operating system. Refer to <a class="xref" href="#proc-Virtualization-Adding_storage_devices">Procedure 28.1, “Adding file-based storage”</a> and <a class="xref" href="#step-partition_disk">Step 6</a> for an example.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ The host should not use filesystem labels to identify file systems in the <code class="filename">fstab</code> file, the <code class="filename">initrd</code> file or on the kernel command line. Doing so presents a security risk if less privileged users, such as guests, have write access to whole partitions or LVM volumes, because a guest could potentially write a filesystem label belonging to the host, to its own block device storage. Upon reboot of the host, the host could then mistakenly use the guest's disk as a system disk, which would compromise the host system.
+ </div><div class="para">
+ It is preferable to use the UUID of a device to identify it in the <code class="filename">fstab</code> file, the <code class="filename">initrd</code> file or on the kernel command line. While using UUIDs is still not completely secure on certain file systems, a similar compromise with UUID is significantly less feasible.
+ </div></div></div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Guests should not be given write access to whole disks or block devices (for example, <code class="filename">/dev/sdb</code>). Guests with access to whole block devices may be able to modify volume labels, which can be used to compromise the host system. Use partitions (for example, <code class="filename">/dev/sdb1</code>) or LVM volumes to prevent this issue.
+ </div></div></div></li></ol></div></div><div class="section" id="sect-Managing_storage_controllers_in_a_guest"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">28.3.3. Managing storage controllers in a guest</h3></div></div></div><div class="para">
+ Starting from Red Hat Enterprise Linux 6.3, SCSI devices are also supported inside guests.
+ </div><div class="para">
+ Unlike virtio disks, SCSI devices require the presence of a controller in the guest.
+ </div><div class="para">
+ This section details the necessary steps to create a virtual SCSI controller (also known as "Host Bus Adapter", or HBA), and to add SCSI storage to the guest.
+ </div><div class="procedure" id="proc-Creating_a_virtual_SCSI_controller"><h6>Procedure 28.3. Creating a virtual SCSI controller</h6><ol class="1"><li class="step"><div class="para">
+ Display the configuration of the guest (<code class="literal">Guest1</code>) and look for a pre-existing SCSI controller:
+ </div><pre class="screen">
+# virsh dumpxml Guest1 | grep controller.*scsi
+</pre><div class="para">
+ If a controller is present, the command will output one or more lines similar to the following:
+ </div><pre class="screen">
+<controller type='scsi' model='virtio-scsi' index='0'/>
+</pre></li><li class="step"><div class="para">
+ If the previous step did not show a controller, create the description for one in a new file and add it to the virtual machine, using the following steps:
+ </div><ol class="a"><li class="step"><div class="para">
+ Create the controller by writing a <code class="literal"><controller></code> element in a new file and save this file with an XML extension. <code class="filename">NewHBA.xml</code>, for example.
+ </div><pre class="screen">
+<controller type='scsi' model='virtio-scsi'/>
+</pre></li><li class="step"><div class="para">
+ Associate the device in the <code class="filename">NewHBA.xml</code> you just created with your guest:
+ </div><pre class="screen">
+# virsh attach-device --config Guest1 ~/NewHBA.xml
+</pre><div class="para">
+ In this example the <code class="literal">--config</code> option behaves the same as it does for disks. Refer to <a class="xref" href="#proc-Virtualization-Adding_storage_devices_to_guests-Adding_physical_block_devices_to_virtualized_guests">Procedure 28.2, “Adding physical block devices to guests”</a> for more information.
+ </div></li></ol></li><li class="step"><div class="para">
+ Add a new SCSI disk or CD-ROM. The new disk can be added using the methods in sections <a class="xref" href="#sect-Virtualization-Adding_storage_devices_to_guests-Adding_file_based_storage_to_a_guest">Section 28.3.1, “Adding file based storage to a guest”</a> and <a class="xref" href="#sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest">Section 28.3.2, “Adding hard drives and other block devices to a guest”</a>. In order to create a SCSI disk, specify a target device name that starts with <em class="replaceable"><code>sd</code></em>.
+ </div><pre class="screen">
+# virsh attach-disk Guest1 /var/lib/libvirt/images/FileName.iso sdb --cache none
+</pre><div class="para">
+ Depending on the version of the driver in the guest, the new disk may not be detected immediately by a running guest. Follow the steps in the <em class="citetitle">Red Hat Enterprise Linux Storage Administration Guide</em>.
+ </div></li></ol></div></div></div><div class="section" id="sect-Virtualization-Storage_Volumes-Deleting_volumes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">28.4. Deleting and removing volumes</h2></div></div></div><div class="para">
+ This section shows how to delete a disk volume from a block based storage pool using the <code class="command">virsh vol-delete</code> command. In this example, the volume is <em class="replaceable"><code>volume 1</code></em> and the storage pool is <em class="replaceable"><code>guest_images</code></em>.
+ </div><pre class="screen">
+# virsh vol-delete --pool guest_images volume1
+Vol volume1 deleted
+</pre></div></div><div xml:lang="en-US" class="chapter" id="vhostmd" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 29. The Virtual Host Metrics Daemon (vhostmd)</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#idm109965248">29.1. Installing vhostmd on the host</a></span></dt><dt><span class="section"><a href="#idm99221600">29.2. Configuration of vhostmd</a></span></dt><dt><span class="section"><a href="#idm74152464">29.3. Starting and stopping the daemon</a></span></dt><dt><span class="section"><a href="#idm100836656">29.4. Verifying that vhostmd is working from the host</a></span></dt><dt><span class="section"><a href="#idm92004288">29.5. Configuring guests to see the metrics</a></span></dt><dt><span class="section"><a href="#idm97572736">29.6. Using vm-dump-metrics in Fedora guests to verify operation</a></span></dt></dl></div><div class="para">
+ <span class="application"><strong>vhostmd</strong></span> (the Virtual Host Metrics Daemon) allows virtual machines to see limited information about the host they are running on.
+ </div><div class="para">
+ In the host, a daemon (<span class="application"><strong>vhostmd</strong></span>) runs which writes metrics periodically into a disk image. This disk image is exported read-only to guests. Guests can read the disk image to see metrics. Simple synchronization stops guests from seeing out of date or corrupt metrics.
+ </div><div class="para">
+ The system administrator chooses which metrics the guests can see, and also which guests get to see the metrics at all.
+ </div><div class="section" id="idm109965248"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm109965248">29.1. Installing vhostmd on the host</h2></div></div></div><div class="para">
+ The <span class="application"><strong>vhostmd</strong></span> package is available from RHN and is located in the Downloads area. It must be installed on each host where guests are required to get host metrics.
+ </div></div><div class="section" id="idm99221600"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm99221600">29.2. Configuration of vhostmd</h2></div></div></div><div class="para">
+ After installing the package, but before starting the daemon, it is a good idea to understand exactly what metrics <span class="application"><strong>vhostmd</strong></span> will expose to guests, and how this happens.
+ </div><div class="para">
+ The metrics are controlled by the file <code class="filename">/etc/vhostmd/vhostmd.conf</code>.
+ </div><div class="para">
+ There are two parts of particular importance in this XML file. Firstly <em class="parameter"><code><update_period>60</update_period></code></em> controls how often the metrics are updated (in seconds). Since updating metrics can be an expensive operation, you can reduce the load on the host by increasing this period. Secondly, each <em class="parameter"><code><metric>...</metric></code></em> section controls what information is exposed by <span class="application"><strong>vhostmd</strong></span>. For example:
+ </div><pre class="screen"><metric type="string" context="host">
+ <name>HostName</name>
+ <action>hostname</action>
+</metric></pre><div class="para">
+ means that the hostname of the host is exposed to selected guests. To disable particular metrics, you can comment out <em class="parameter"><code><metric></code></em> sections by putting <code class="literal"><!-- ... --></code> around them. Note that disabling metrics may cause problems for guest software such as SAP that may rely on these metrics being available.
+ </div><div class="para">
+ When the daemon (also called <span class="application"><strong>vhostmd</strong></span>) is running, it writes the metrics into a temporary file called <code class="filename">/dev/shm/vhostmd0</code>. This file contains a small binary header followed by the selected metrics encoded as XML. In practice you can display this file with a tool like <span class="application"><strong>less</strong></span>. The file is updated every 60 seconds (or however often <em class="parameter"><code><update_period></code></em> was set).
+ </div><div class="para">
+ The vhostmd(8) man page contains a detailed description of the configuration file, as well as examples of the XML output in <code class="filename">/dev/shm/vhostmd0</code>. To read this, do:
+ </div><pre class="screen"># man vhostmd</pre><div class="para">
+ In addition, there is a README file which covers some of the same information:
+ </div><pre class="screen">less /usr/share/doc/vhostmd-*/README</pre></div><div class="section" id="idm74152464"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm74152464">29.3. Starting and stopping the daemon</h2></div></div></div><div class="para">
+ The daemon (<span class="application"><strong>vhostmd</strong></span>) will not be started automatically. To enable it to be started at boot, run:
+ </div><pre class="screen"># /sbin/chkconfig vhostmd on</pre><div class="para">
+ To start the daemon running, do:
+ </div><pre class="screen"># /sbin/service vhostmd start</pre><div class="para">
+ To stop the daemon running, do:
+ </div><pre class="screen"># /sbin/service vhostmd stop</pre><div class="para">
+ To disable the daemon from being started at boot, do:
+ </div><pre class="screen"># /sbin/chkconfig vhostmd off</pre></div><div class="section" id="idm100836656"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm100836656">29.4. Verifying that vhostmd is working from the host</h2></div></div></div><div class="para">
+ A short time after the daemon has started, you should see a metrics disk appearing. Do:
+ </div><pre class="screen"># ls -l /dev/shm
+# less /dev/shm/vhostmd0</pre><div class="para">
+ This file has a short binary header, followed by XML. The <span class="application"><strong>less</strong></span> program identifies it as binary and asks:
+ </div><pre class="screen">"/dev/shm/vhostmd0" may be a binary file. See it anyway?</pre><div class="para">
+ Press the <span class="keycap"><strong>y</strong></span> key to indicate that you wish to view it.
+ </div><div class="para">
+ You should see the binary header appearing as garbled characters, followed by the <em class="parameter"><code><metrics></code></em> XML, and after that, many zero bytes (displayed as <code class="literal">^@^@^@</code>...).
+ </div></div><div class="section" id="idm92004288"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm92004288">29.5. Configuring guests to see the metrics</h2></div></div></div><div class="para">
+ Although metrics are written to <code class="filename">/dev/shm/vhostmd0</code>, they are not made available to guests by default. The administrator must choose which guests get to see metrics, and must manually change the configuration of selected guests to see metrics.
+ </div><div class="para">
+ The guest must be shut down before the disk is attached. (Hot attaching the metrics disk is also possible, but only for a limited number of guest configurations. In particular it is NOT possible to hot-add the metrics disk to guests that do not have virtio / PV drivers installed. See the vhostmd README file for more information).
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ It is extremely important that the metrics disk is added in readonly mode to all guests. If this is not done, then it would be possible for a guest to modify the metrics and possibly subvert other guests that are reading it.
+ </div></div></div><div class="procedure"><h6>Procedure 29.1. Configuring KVM guests</h6><ol class="1"><li class="step"><div class="para">
+ Shut down the guest.
+ </div></li><li class="step"><div class="para">
+ Do:
+ </div><pre class="screen"># virsh edit GuestName</pre><div class="para">
+ and add the following section into <em class="parameter"><code><devices></code></em>:
+ </div><pre class="screen"><disk type='file' device='disk'>
+ <driver name='qemu' type='raw'/>
+ <source file='/dev/shm/vhostmd0'/>
+ <target dev='vdd' bus='virtio'/>
+ <readonly/>
+ </disk></pre></li><li class="step"><div class="para">
+ Reboot the guest.
+ </div></li></ol></div><div class="procedure"><h6>Procedure 29.2. Configuring Xen guests</h6><ol class="1"><li class="step"><div class="para">
+ Shut down the guest.
+ </div></li><li class="step"><div class="para">
+ Do:
+ </div><pre class="screen"># virsh edit GuestName</pre><div class="para">
+ and add the following section into <em class="parameter"><code><devices></code></em>:
+ </div><pre class="screen"><disk type='file' device='disk'>
+ <source dev='/dev/shm/vhostmd0'/>
+ <target dev='hdd' bus='ide'/>
+ <readonly/>
+ </disk></pre></li><li class="step"><div class="para">
+ Reboot the guest.
+ </div></li></ol></div></div><div class="section" id="idm97572736"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm97572736">29.6. Using vm-dump-metrics in Fedora guests to verify operation</h2></div></div></div><div class="para">
+ Optionally, the <span class="package">vm-dump-metrics</span> package from the RHN Downloads area may be installed in Fedora guests. This package provides a simple command line tool (also called <span class="application"><strong>vm-dump-metrics</strong></span>) which allows host metrics to be displayed in the guest.
+ </div><div class="para">
+ This is useful for verifying correct operation of <span class="application"><strong>vhostmd</strong></span> from a guest.
+ </div><div class="para">
+ In the guest, run the following command as root:
+ </div><pre class="screen"># vm-dump-metrics</pre><div class="para">
+ If everything is working, this should print out a long XML document starting with <code class="literal"><metrics></code>.
+ </div><div class="para">
+ If this does not work, then verify that the metrics disk has appeared in the guest. It should appear as <code class="filename">/dev/vd*</code> (for example, <code class="filename">/dev/vdb</code>, <code class="filename">/dev/vdd</code>).
+ </div><div class="para">
+ On the host, verify that the libvirt configuration changes have been made by using the command:
+ </div><pre class="screen"># virsh dumpxml GuestName</pre><div class="para">
+ Verify that vhostmd is running on the host and the /dev/shm/vhostmd0 file exists.
+ </div></div></div></div><div class="part" id="idm94886384"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part III. Appendicies</h1></div></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl><dt><span class="appendix"><a href="#chap-Virtualization_Administration_Guide-Troubleshooting">A. Troubleshooting</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Troubleshooting_-Debugging_and_troubleshooting_">A.1. Debugging and troubleshooting tools</a></span></dt><dt><span class="section"><a href="#idm114039008">A.2. kvm_stat</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles">A.3. Troubleshooting with serial consoles</a></span></dt><dt><span class="section"><a href="#idm124509312">A.4. Virtualization log files</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Troubleshooting-Loop_device_errors">A.5. Loop device
errors</a></span></dt><dt><span class="section"><a href="#live-migration-errors">A.6. Live Migration Errors</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS">A.7. Enabling Intel VT-x and AMD-V virtualization hardware extensions in BIOS</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Troubleshooting-KVM_networking_performance">A.8. KVM networking performance</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard">A.9. Missing characters on guest console with Japanese keyboard</a></span></dt><dt><span class="section"><a href="#sec-known-issues-windows-xp-guests">A.10. Known Windows XP guest issues</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idm61545728">B. Common <span class="application"><strong>libvirt</strong></span> errors and troubleshooting</
a></span></dt><dd><dl><dt><span class="section"><a href="#App_Libvirt_Daemon">B.1. <span class="application"><strong>libvirtd</strong></span> failed to start</a></span></dt><dt><span class="section"><a href="#App_Hypervisor_Connection_Fail">B.2. The URI failed to connect to the hypervisor</a></span></dt><dd><dl><dt><span class="section"><a href="#Sect_Cannot_read_CA_certificate">B.2.1. Cannot read CA certificate</a></span></dt><dt><span class="section"><a href="#Sect_Failed_to_connect_socket">B.2.2. Failed to connect socket ... : Permission denied</a></span></dt><dt><span class="section"><a href="#Sect_Other_Connectivity_Errors">B.2.3. Other connectivity errors</a></span></dt></dl></dd><dt><span class="section"><a href="#App_Domain_Processor">B.3. The guest virtual machine cannot be started: <code class="computeroutput">internal error guest CPU is not compatible with host CPU</code></a></span></dt><dt><span class="section"><a href="#App_Domain_Monitor_Socket">B.4. Guest star
ting fails with error: <code class="computeroutput">monitor socket did not show up</code></a></span></dt><dt><span class="section"><a href="#App_Domain_Console">B.5. <code class="computeroutput">Internal error cannot find character device (null)</code></a></span></dt><dt><span class="section"><a href="#App_Domain_Not_Booting">B.6. Guest virtual machine booting stalls with error: <code class="computeroutput">No boot device</code></a></span></dt><dt><span class="section"><a href="#App_Virt_Net_Not_Starting">B.7. Virtual network <em class="replaceable"><code>default</code></em> has not been started</a></span></dt><dt><span class="section"><a href="#App_PXE_Guest_Boot_Fail">B.8. PXE boot (or DHCP) on guest failed</a></span></dt><dt><span class="section"><a href="#App_Macvtap">B.9. Guest can reach outside network, but cannot reach host when using macvtap interface</a></span></dt><dt><span class="section"><a href="#App_DHCP_Response_Checksums">B.10. Could not add rule to fixup DHC
P response checksums on network <em class="replaceable"><code>'default'</code></em></a></span></dt><dt><span class="section"><a href="#App_Bridge_Device">B.11. Unable to add bridge br0 port vnet0: No such device</a></span></dt><dt><span class="section"><a href="#App_Generic_Ethernet">B.12. Guest is unable to start with error: <code class="computeroutput">warning: could not open /dev/net/tun</code></a></span></dt><dt><span class="section"><a href="#App_Migration_Address">B.13. Migration fails with <code class="computeroutput">Error: unable to resolve address</code></a></span></dt><dt><span class="section"><a href="#App_Migration_Disk_Image">B.14. Migration fails with <code class="computeroutput">Unable to allow access for disk path: No such file or directory</code></a></span></dt><dt><span class="section"><a href="#App_No_Guest_Machines">B.15. No guest virtual machines are present when <span class="application"><strong>libvirtd</strong></span> is started</a></span></dt><dt><s
pan class="section"><a href="#App_TCP_Ports">B.16. Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor</a></span></dt><dt><span class="section"><a href="#App_XML_Errors">B.17. Common XML errors</a></span></dt><dd><dl><dt><span class="section"><a href="#idm115560112">B.17.1. Editing domain definition</a></span></dt><dt><span class="section"><a href="#idm117772112">B.17.2. XML syntax errors</a></span></dt><dt><span class="section"><a href="#idm115393088">B.17.3. Logic and configuration errors</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#netkvm-parameters">C. NetKVM Driver Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idm107871952">C.1. Configurable parameters for NetKVM</a></span></dt></dl></dd><dt><span class="appendix"><a href="#chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist">D. qemu-kvm Whitelist</a></span></dt><dd><dl><dt><span class="section"><a href=
"#idm107978896">D.1. Introduction</a></span></dt><dt><span class="section"><a href="#idm77975568">D.2. Basic options</a></span></dt><dt><span class="section"><a href="#idm77194320">D.3. Disk options</a></span></dt><dt><span class="section"><a href="#idm104274176">D.4. Display options</a></span></dt><dt><span class="section"><a href="#idm114721584">D.5. Network options</a></span></dt><dt><span class="section"><a href="#idm93867376">D.6. Device options</a></span></dt><dt><span class="section"><a href="#idm89508384">D.7. Linux/Multiboot boot </a></span></dt><dt><span class="section"><a href="#idm97161328">D.8. Expert options</a></span></dt><dt><span class="section"><a href="#idm79818416">D.9. Help and information options</a></span></dt><dt><span class="section"><a href="#idm99738544">D.10. Miscellaneous options</a></span></dt></dl></dd><dt><span class="appendix"><a href="#chap-Virtualization_Administration_Guide-Managing_guests_with_virsh">E. Managing guests with virsh</a></spa
n></dt><dd><dl><dt><span class="section"><a href="#idm93487200">E.1. virsh command quick reference</a></span></dt><dt><span class="section"><a href="#sect-Attaching_and_updating_a_device_with_virsh">E.2. Attaching and updating a device with virsh</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor">E.3. Connecting to the hypervisor</a></span></dt><dt><span class="section"><a href="#form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file">E.4. Creating a virtual machine XML dump (configuration file)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-multifunction-pci-install">E.4.1. Adding multifunction PCI devices to KVM guests</a></span></dt></dl></dd><dt><span class="section"><a href="#idm115600896">E.5. Suspending, resuming, saving and restoring a guest</a></span></dt><dt><span class="section"><a href="#idm70012976">E.6. Shutting down, rebo
oting and force-shutdown of a guest</a></span></dt><dt><span class="section"><a href="#idm103535312">E.7. Retrieving guest information</a></span></dt><dt><span class="section"><a href="#idm123330576">E.8. Retrieving node information</a></span></dt><dt><span class="section"><a href="#idm107205776">E.9. Storage pool information</a></span></dt><dt><span class="section"><a href="#idm114956880">E.10. Displaying per-guest information</a></span></dt><dt><span class="section"><a href="#idm92394304">E.11. Managing virtual networks</a></span></dt><dt><span class="section"><a href="#migrating_guests-with-virsh">E.12. Migrating guests with virsh</a></span></dt><dt><span class="section"><a href="#sect-man-disk-image">E.13. Disk image management with live block copy</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-blockcommit">E.13.1. Using blockcommit to shorten a backing chain</a></span></dt><dt><span class="section"><a href="#sub-sect-blockpull">E.13.2. Using blockpull t
o shorten a backing chain</a></span></dt><dt><span class="section"><a href="#sub-sect-blkresize">E.13.3. Using blockresize to change the size of a domain path</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-guest-cpu-model-config">E.14. Guest CPU model configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-guest-cpu-intro">E.14.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-learn-about-host-cpu">E.14.2. Learning about the host CPU model</a></span></dt><dt><span class="section"><a href="#idm90465808">E.14.3. Determining a compatible CPU model to suit a pool of hosts</a></span></dt><dt><span class="section"><a href="#idm111893984">E.14.4. Configuring the guest CPU model</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager">F. Managing guests with the Virtual Machine Manager (virt-manager)</a>
</span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Starting_virt_manager">F.1. Starting virt-manager</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window">F.2. The Virtual Machine Manager main window</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_">F.3. The virtual hardware details window</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_">F.4. Virtual Machine graphical console</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_wi
ndow">F.5. Adding a remote connection</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details">F.6. Displaying guest details</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring">F.7. Performance monitoring</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage">F.8. Displaying CPU usage for guests</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage">F.9. Displaying CPU usage for hosts</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO">F.10. Displaying Disk I/O</a></span></dt>
<dt><span class="section"><a href="#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO">F.11. Displaying Network I/O</a></span></dt></dl></dd><dt><span class="appendix"><a href="#chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs">G. Guest disk access with offline tools</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-introduction-Virtualization_Administration_Guide-Guest_Disks_libguestfs">G.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-Terminology-Guest_Disks_libguestfs">G.2. Terminology</a></span></dt><dt><span class="section"><a href="#sect-Guide-Guest_Disks_libguestfs-installation">G.3. Installation</a></span></dt><dt><span class="section"><a href="#sect-the_guestfish_shell">G.4. The guestfish shell</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Viewing_file_systems_with_guestfish">G.4.1. Viewing file systems with guestfish</a></span></dt><dt><span
class="section"><a href="#sect-Modifying-files-with-guestfish">G.4.2. Modifying files with guestfish</a></span></dt><dt><span class="section"><a href="#sect-Other-actions-with-guestfish">G.4.3. Other actions with guestfish</a></span></dt><dt><span class="section"><a href="#sect-Shell-scripting-with-guestfish">G.4.4. Shell scripting with guestfish</a></span></dt><dt><span class="section"><a href="#sect-Augeas-and-libguestfs-scripting">G.4.5. Augeas and libguestfs scripting</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-other-commands">G.5. Other commands</a></span></dt><dt><span class="section"><a href="#sect-virt-rescue">G.6. virt-rescue: The rescue shell</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-virt-rescue-intro">G.6.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-run-virt-rescue">G.6.2. Running virt-rescue</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-virt-df">G.7. virt-df: Monitoring dis
k usage</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-virt-df-intro">G.7.1. Introduction</a></span></dt><dt><span class="section"><a href="#run-virt-df">G.7.2. Running virt-df</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-virt-resize">G.8. virt-resize: resizing guests offline</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-virt-resize-intro">G.8.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-expand-disk-image">G.8.2. Expanding a disk image</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-virt-inspector">G.9. virt-inspector: inspecting guests</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-virt-inspector-intro">G.9.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-virt-inspector-install">G.9.2. Installation</a></span></dt><dt><span class="section"><a href="#sect-virt-inspector-run">G.9.3. Running virt-inspector</a></span></dt></dl></dd><dt><spa
n class="section"><a href="#sect-virt-win-reg">G.10. virt-win-reg: Reading and editing the Windows Registry</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-virt-win-reg-intro">G.10.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-virt-win-reg-install">G.10.2. Installation</a></span></dt><dt><span class="section"><a href="#sect-virt-win-reg-use">G.10.3. Using virt-win-reg</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Using-API-Programming-Languages">G.11. Using the API from Programming Languages</a></span></dt><dd><dl><dt><span class="section"><a href="#API-and-C">G.11.1. Interaction with the API via a C program</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-libguestfs-troubleshoot">G.12. Troubleshooting</a></span></dt><dt><span class="section"><a href="#sect-libguestfs-more-docs">G.13. Where to find further documentation</a></span></dt></dl></dd><dt><span class="appendix"><a href="#chap-Virtualizat
ion_Administration_Guide-Virtual_Networking">H. Virtual Networking</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-virtual_network-switches-livbvirt">H.1. Virtual network switches</a></span></dt><dt><span class="section"><a href="#sect-Network_Address_Translation-libvirt">H.2. Network Address Translation</a></span></dt><dt><span class="section"><a href="#sect-network-protocols">H.3. Networking protocols</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-DNS_and_DHCP-protocols-libvirt">H.3.1. DNS and DHCP</a></span></dt><dt><span class="section"><a href="#sub-sect-routed-mode-libvirt">H.3.2. Routed mode</a></span></dt><dt><span class="section"><a href="#sub-sect-iso-mode">H.3.3. Isolated mode</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-the-Default_Configuration-libvirt">H.4. The default configuration</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Virtual_Networking-Example_scenarios">H.5. Examples of c
ommon scenarios</a></span></dt><dd><dl><dt><span class="section"><a href="#sub-sect-routed-mode">H.5.1. Routed mode</a></span></dt><dt><span class="section"><a href="#sub-sect-nat-mode">H.5.2. NAT mode</a></span></dt><dt><span class="section"><a href="#sub-sect-isolated-mode">H.5.3. Isolated mode</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Virtualization-Virtual_Networking-Managing_a_virtual_network">H.6. Managing a virtual network</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Virtual_Networking-Creating_a_virtual_network">H.7. Creating a virtual network</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest">H.8. Attaching a virtual network to a guest</a></span></dt><dt><span class="section"><a href="#sect-attch-nic-physdev">H.9. Directly attaching to physical interface</a></span></dt><dt><span class="section"><a href="#sect-applying-network-filtering">H.10.
Applying network filtering</a></span></dt><dd><dl><dt><span class="section"><a href="#intro-sub-sect-applying-network-filtering">H.10.1. Introduction</a></span></dt><dt><span class="section"><a href="#sub-sect-filt-chain">H.10.2. Filtering chains</a></span></dt><dt><span class="section"><a href="#sub-sect-filt-chain-props">H.10.3. Filtering chain priorities</a></span></dt><dt><span class="section"><a href="#sub-sect-vars-in-filters">H.10.4. Usage of variables in filters</a></span></dt><dt><span class="section"><a href="#sub-sect-auto-IP-add-detect-dhcp-snoop">H.10.5. Automatic IP address detection and DHCP snooping</a></span></dt><dt><span class="section"><a href="#sub-sect-vars-reserved">H.10.6. Reserved Variables</a></span></dt><dt><span class="section"><a href="#sub-sect-element-oview">H.10.7. Element and attribute overview</a></span></dt><dt><span class="section"><a href="#sub-sect-ref-filter">H.10.8. References to other filters</a></span></dt><dt><span class="section"><
a href="#sub-sect-filter-rules">H.10.9. Filter rules</a></span></dt><dt><span class="section"><a href="#sub-sect-supp-pros">H.10.10. Supported protocols</a></span></dt><dt><span class="section"><a href="#sub-sect-adv-filt-topics">H.10.11. Advanced Filter Configuration Topics</a></span></dt><dt><span class="section"><a href="#sub-sect-limitations-filters-network-subsystem">H.10.12. Limitations</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#appe-Virtualization-Additional_resources">I. Additional resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Virtualization-Additional_resources-Online_resources">I.1. Online resources</a></span></dt><dt><span class="section"><a href="#sect-Virtualization-Additional_resources-Installed_documentation">I.2. Installed documentation</a></span></dt></dl></dd><dt><span class="appendix"><a href="#ch-lib-dom-xml">J. Manipulating the domain xml</a></span></dt><dd><dl><dt><span class="section"><a href="#s
ect-gen-metadata">J.1. General information and metadata</a></span></dt><dt><span class="section"><a href="#sect-dom-xml-op-sys-boot">J.2. Operating system booting</a></span></dt><dd><dl><dt><span class="section"><a href="#sub-sect-op-sys-boot-bios-boot">J.2.1. BIOS bootloader</a></span></dt><dt><span class="section"><a href="#sub-sect-op-sys-host-boot">J.2.2. Host bootloader</a></span></dt><dt><span class="section"><a href="#sub-sect-op-sys-dir-kern-boot">J.2.3. Direct kernel boot</a></span></dt><dt><span class="section"><a href="#sub-sect-op-sys-cont-boot">J.2.4. Container boot</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-smbios-sys-info">J.3. SMBIOS system information</a></span></dt><dt><span class="section"><a href="#sect-cpu-allocation">J.4. CPU allocation</a></span></dt><dt><span class="section"><a href="#sect-cpu-tuning">J.5. CPU tuning</a></span></dt><dt><span class="section"><a href="#sect-mem-back">J.6. Memory backing</a></span></dt><dt><span cl
ass="section"><a href="#sect-libvirt-dom-xml-mem-tuning">J.7. Memory tuning</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-numa-node-tuning">J.8. NUMA node tuning</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-blk-io-tuning">J.9. Block I/O tuning</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-res-part">J.10. Resource partitioning</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-cpu-model-top">J.11. CPU model and topology</a></span></dt><dd><dl><dt><span class="section"><a href="#sub-sect-libvirt-dom-xml-res-part-guest-numa">J.11.1. Guest NUMA topology</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-libvirt-dom-xml-event-config">J.12. Events configuration</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-pwr-man">J.13. Power Management</a></span></dt><dt><span class="section"><a href="#idm101742368">J.14. Hypervisor features</a></span></dt>
<dt><span class="section"><a href="#sect-libvirt-dom-xml-time-keep">J.15. Time keeping</a></span></dt><dt><span class="section"><a href="#sect-libvirt-dom-xml-devices">J.16. Devices</a></span></dt><dd><dl><dt><span class="section"><a href="#sub-sect-libvirt-dom-xml-devices">J.16.1. Hard drives, floppy disks, CDROMs</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-filesystems">J.16.2. Filesystems</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-device-addresses">J.16.3. Device addresses</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-controllers">J.16.4. Controllers</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-device-leases">J.16.5. Device leases</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-host-device-assignment">J.16.6. Host device assignment</a></span></dt><dt><span class="sect
ion"><a href="#sub-section-libvirt-dom-xml-devices-redirected-devices">J.16.7. Redirected devices</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-smartcard">J.16.8. Smartcard devices</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-Network-interfaces">J.16.9. Network interfaces</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-input-devices">J.16.10. Input devices</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-hub-devices">J.16.11. Hub devices</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-graphical-framebuffers">J.16.12. Graphical framebuffers</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-video">J.16.13. Video devices</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-consoles">J.16.14. Consoles, serial, par
allel, and channel devices</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-guest-interface">J.16.15. Guest interfaces</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-channel">J.16.16. Channel</a></span></dt><dt><span class="section"><a href="#sub-section-libvirt-dom-xml-devices-host-interface">J.16.17. Host interface</a></span></dt></dl></dd><dt><span class="section"><a href="#section-libvirt-dom-xml-sound-devices">J.17. Sound devices</a></span></dt><dt><span class="section"><a href="#section-libvirt-dom-xml-watchdog">J.18. Watchdog device</a></span></dt><dt><span class="section"><a href="#section-libvirt-dom-xml-memory-baloon-device">J.19. Memory balloon device</a></span></dt><dt><span class="section"><a href="#section-libvirt-dom-xml-random-number-gen">J.20. Random number generator device</a></span></dt><dt><span class="section"><a href="#section-libvirt-dom-xml-tpm-device">J.21. TPM devices</a><
/span></dt><dt><span class="section"><a href="#section-libvirt-dom-xml-security-label">J.22. Security label</a></span></dt><dt><span class="section"><a href="#section-libvirt-dom-xml-example">J.23. Example domain XML configuration</a></span></dt></dl></dd></dl></div><div xml:lang="en-US" class="appendix" id="chap-Virtualization_Administration_Guide-Troubleshooting" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Troubleshooting</h1></div></div></div><div class="para">
+ This chapter covers common problems and solutions for Fedora virtualization issues.
+ </div><div class="para">
+ Read this chapter to develop an understanding of some of the common problems associated with virtualization technologies. Troubleshooting takes practice and experience which are difficult to learn from a book. It is recommended that you experiment and test virtualization on Fedora 19 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="#sect-Virtualization-Additional_resources-Online_resources">Section I.1, “Online resources”</a> for a list of Linux virtualization websites.
+ </div><div class="section" id="sect-Virtualization-Troubleshooting_-Debugging_and_troubleshooting_"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.1. Debugging and troubleshooting tools</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="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">kvm_stat</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">trace-cmd</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">vmstat</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">iostat</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">lsof</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">systemtap</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">crash</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">sysrq</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">sysrq t</code>
+ </div></li><li class="listitem"><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 class="listitem"><div class="para">
+ <code class="command">ifconfig</code>
+ </div></li><li class="listitem"><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 class="listitem"><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 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
+-----------------------------------------------------------------------------
+virtbr0 8000.feffffff yes eth0
+
+# brctl showmacs virtbr0
+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 virtbr0
+virtbr0
+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.
+ </div><div class="itemizedlist"><ul><li class="listitem"><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 class="listitem"><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 class="listitem"><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 class="section" id="idm114039008"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm114039008">A.2. kvm_stat</h2></div></div></div><div class="para">
+ The <code class="command">kvm_stat</code> command is a python script which retrieves runtime statistics from the <code class="systemitem">kvm</code> kernel module. The <code class="command">kvm_stat</code> command can be used to diagnose guest behavior visible to <code class="systemitem">kvm</code>. In particular, performance related issues with guests. Currently, the reported statistics are for the entire system; the behavior of all running guests is reported.
+ </div><div class="para">
+ The <code class="command">kvm_stat</code> command requires that the <code class="systemitem">kvm</code> kernel module is loaded and <code class="command">debugfs</code> is mounted. If either of these features are not enabled, the command will output the required steps to enable <code class="command">debugfs</code> or the <code class="systemitem">kvm</code> module. For example:
+ </div><pre class="screen"># kvm_stat
+Please mount debugfs ('mount -t debugfs debugfs /sys/kernel/debug')
+and ensure the kvm modules are loaded</pre><div class="para">
+ Mount <code class="command">debugfs</code> if required:
+ </div><pre class="screen"># mount -t debugfs debugfs /sys/kernel/debug</pre><div class="formalpara"><h5 class="formalpara" id="idm66562368">kvm_stat output</h5>
+ The <code class="command">kvm_stat</code> command outputs statistics for all guests and the host. The output is updated until the command is terminated (using <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>c</strong></span> or the <span class="keycap"><strong>q</strong></span> key).
+ </div><pre class="screen"># kvm_stat
+
+kvm statistics
+
+efer_reload 94 0
+exits 4003074 31272
+fpu_reload 1313881 10796
+halt_exits 14050 259
+halt_wakeup 4496 203
+host_state_reload 1638354 24893
+hypercalls 0 0
+insn_emulation 1093850 1909
+insn_emulation_fail 0 0
+invlpg 75569 0
+io_exits 1596984 24509
+irq_exits 21013 363
+irq_injections 48039 1222
+irq_window 24656 870
+largepages 0 0
+mmio_exits 11873 0
+mmu_cache_miss 42565 8
+mmu_flooded 14752 0
+mmu_pde_zapped 58730 0
+mmu_pte_updated 6 0
+mmu_pte_write 138795 0
+mmu_recycled 0 0
+mmu_shadow_zapped 40358 0
+mmu_unsync 793 0
+nmi_injections 0 0
+nmi_window 0 0
+pf_fixed 697731 3150
+pf_guest 279349 0
+remote_tlb_flush 5 0
+request_irq 0 0
+signal_exits 1 0
+tlb_flush 200190 0
+</pre><div class="variablelist"><h6>Explanation of variables:</h6><dl class="variablelist"><dt class="varlistentry"><span class="term">efer_reload</span></dt><dd><div class="para">
+ The number of Extended Feature Enable Register (EFER) reloads.
+ </div></dd><dt class="varlistentry"><span class="term">exits</span></dt><dd><div class="para">
+ The count of all <code class="computeroutput">VMEXIT</code> calls.
+ </div></dd><dt class="varlistentry"><span class="term">fpu_reload</span></dt><dd><div class="para">
+ The number of times a <code class="computeroutput">VMENTRY</code> reloaded the FPU state. The <code class="command">fpu_reload</code> is incremented when a guest is using the Floating Point Unit (FPU).
+ </div></dd><dt class="varlistentry"><span class="term">halt_exits</span></dt><dd><div class="para">
+ Number of guest exits due to <code class="computeroutput">halt</code> calls. This type of exit is usually seen when a guest is idle.
+ </div></dd><dt class="varlistentry"><span class="term">halt_wakeup</span></dt><dd><div class="para">
+ Number of wakeups from a <code class="computeroutput">halt</code>.
+ </div></dd><dt class="varlistentry"><span class="term">host_state_reload</span></dt><dd><div class="para">
+ Count of full reloads of the host state (currently tallies MSR setup and guest MSR reads).
+ </div></dd><dt class="varlistentry"><span class="term">hypercalls</span></dt><dd><div class="para">
+ Number of guest hypervisor service calls.
+ </div></dd><dt class="varlistentry"><span class="term">insn_emulation</span></dt><dd><div class="para">
+ Number of guest instructions emulated by the host.
+ </div></dd><dt class="varlistentry"><span class="term">insn_emulation_fail</span></dt><dd><div class="para">
+ Number of failed <code class="computeroutput">insn_emulation</code> attempts.
+ </div></dd><dt class="varlistentry"><span class="term">io_exits</span></dt><dd><div class="para">
+ Number of guest exits from I/O port accesses.
+ </div></dd><dt class="varlistentry"><span class="term">irq_exits</span></dt><dd><div class="para">
+ Number of guest exits due to external interrupts.
+ </div></dd><dt class="varlistentry"><span class="term">irq_injections</span></dt><dd><div class="para">
+ Number of interrupts sent to guests.
+ </div></dd><dt class="varlistentry"><span class="term">irq_window</span></dt><dd><div class="para">
+ Number of guest exits from an outstanding interrupt window.
+ </div></dd><dt class="varlistentry"><span class="term">largepages</span></dt><dd><div class="para">
+ Number of large pages currently in use.
+ </div></dd><dt class="varlistentry"><span class="term">mmio_exits</span></dt><dd><div class="para">
+ Number of guest exits due to memory mapped I/O (MMIO) accesses.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_cache_miss</span></dt><dd><div class="para">
+ Number of KVM MMU shadow pages created.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_flooded</span></dt><dd><div class="para">
+ Detection count of excessive write operations to an MMU page. This counts detected write operations not of individual write operations.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_pde_zapped</span></dt><dd><div class="para">
+ Number of page directory entry (PDE) destruction operations.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_pte_updated</span></dt><dd><div class="para">
+ Number of page table entry (PTE) destruction operations.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_pte_write</span></dt><dd><div class="para">
+ Number of guest page table entry (PTE) write operations.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_recycled</span></dt><dd><div class="para">
+ Number of shadow pages that can be reclaimed.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_shadow_zapped</span></dt><dd><div class="para">
+ Number of invalidated shadow pages.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_unsync</span></dt><dd><div class="para">
+ Number of non-synchronized pages which are not yet unlinked.
+ </div></dd><dt class="varlistentry"><span class="term">nmi_injections</span></dt><dd><div class="para">
+ Number of Non-maskable Interrupt (NMI) injections to the guest.
+ </div></dd><dt class="varlistentry"><span class="term">nmi_window</span></dt><dd><div class="para">
+ Number of guest exits from (outstanding) Non-maskable Interrupt (NMI) windows.
+ </div></dd><dt class="varlistentry"><span class="term">pf_fixed</span></dt><dd><div class="para">
+ Number of fixed (non-paging) page table entry (PTE) maps.
+ </div></dd><dt class="varlistentry"><span class="term">pf_guest</span></dt><dd><div class="para">
+ Number of page faults injected into guests.
+ </div></dd><dt class="varlistentry"><span class="term">remote_tlb_flush</span></dt><dd><div class="para">
+ Number of remote (sibling CPU) Translation Lookaside Buffer (TLB) flush requests.
+ </div></dd><dt class="varlistentry"><span class="term">request_irq</span></dt><dd><div class="para">
+ Number of guest interrupt window request exits.
+ </div></dd><dt class="varlistentry"><span class="term">signal_exits</span></dt><dd><div class="para">
+ Number of guest exits due to pending signals from the host.
+ </div></dd><dt class="varlistentry"><span class="term">tlb_flush</span></dt><dd><div class="para">
+ Number of <code class="computeroutput">tlb_flush</code> operations performed by the hypervisor.
+ </div></dd></dl></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The output information from the <code class="command">kvm_stat</code> command is exported by the KVM hypervisor as pseudo files located in the <code class="filename">/sys/kernel/debug/kvm/</code> directory.
+ </div></div></div></div><div class="section" id="sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.3. 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 Fedora virtualization kernels and their guests.
+ </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 class="listitem"><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. Append the following to the <em class="parameter"><code>kernel</code></em> line: <em class="parameter"><code>console=tty0 console=ttyS0,115200</code></em>.
+ </div><pre class="screen">title Fedora Server (2.6.32-36.x86-64)
+ root (hd0,0)
+ kernel /vmlinuz-2.6.32-36.x86-64 ro root=/dev/volgroup00/logvol00 \
+ <em class="parameter"><code>console=tty0 console=ttyS0,115200</code></em>
+ initrd /initrd-2.6.32-36.x86-64.img
+</pre><div class="para">
+ Reboot the guest.
+ </div><div class="para">
+ On the host, 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 guest console window, select <span class="guilabel"><strong>Serial 1</strong></span> in <span class="guilabel"><strong>Text Consoles</strong></span> from the <span class="guilabel"><strong>View</strong></span> menu.
+ </div></div><div class="section" id="idm124509312"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm124509312">A.4. Virtualization log files</h2></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Each fully virtualized guest log is in the <code class="filename">/var/log/libvirt/qemu/</code> directory. Each guest log is named as <em class="replaceable"><code>GuestName</code></em>.log and will be periodically compressed once a size limit is reached.
+ </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">$HOME/.virt-manager</code> directory.
+ </div></div><div class="section" id="sect-Virtualization-Troubleshooting-Loop_device_errors"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.5. 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 eight active loop devices. If more than eight file-based guests or loop devices are needed the number of loop devices configured can be adjusted in the <code class="filename">/etc/modprobe.d/</code>directory. Add the following line:
+ </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 use a 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><div class="section" id="live-migration-errors"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.6. Live Migration Errors</h2></div></div></div><div class="para">
+ There may be cases where a live migration causes the memory contents to be re-transfered over and over again This process causes the guest to be in a state where it is constantly writing to memory and therefore will slow down migration. If this should occur, and the guest is writing more than several tens of MBs per second, then live migration may fail to finish (converge). This issue is scheduled to be fixed in Fedora 19 or 20.
+ </div><div class="para">
+ The current live-migration implementation has a default migration time configured to 30ms. This value determines the guest pause time at the end of the migration in order to transfer the leftovers. Higher values increase the odds that live migration will converge
+ </div></div><div class="section" id="sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.7. Enabling Intel VT-x 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-x extensions can be disabled in the BIOS. Certain laptop vendors have disabled the Intel VT-x extensions by default in their CPUs.
+ </div><div class="para">
+ The virtualization extensions cannot be disabled in the BIOS for AMD-V.
+ </div><div class="para">
+ Refer to the following section for instructions on enabling disabled virtualization extensions.
+ </div><div class="para">
+ Verify the virtualization extensions are enabled in BIOS. The BIOS settings for Intel 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-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS-Enabling_virtualization_extensions_in_BIOS"><h6>Procedure A.1. Enabling virtualization extensions in BIOS</h6><ol class="1"><li class="step"><div class="para">
+ Reboot the computer and open the system's BIOS menu. This can usually be done by pressing the <span class="guibutton"><strong>delete</strong></span> key, the <span class="keycap"><strong>F1</strong></span> key or <span class="keycap"><strong>Alt</strong></span> and <span class="keycap"><strong>F4</strong></span> keys depending on the system.
+ </div></li><li class="step"><p class="title"><strong>Enabling the virtualization extensions in BIOS</strong></p><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Many of the steps below may vary depending on your motherboard, processor type, chipset and OEM. Refer to your system's accompanying documentation for the correct information on configuring your system.
+ </div></div></div><ol class="a"><li class="step"><div class="para">
+ Open the <span class="guilabel"><strong>Processor</strong></span> submenu The processor settings menu may be hidden in the <span class="guilabel"><strong>Chipset</strong></span>, <span class="guilabel"><strong>Advanced CPU Configuration</strong></span> or <span class="guilabel"><strong>Northbridge</strong></span>.
+ </div></li><li class="step"><div class="para">
+ Enable <span class="guilabel"><strong>Intel Virtualization Technology</strong></span> (also known as Intel VT-x). <span class="guilabel"><strong>AMD-V</strong></span> extensions cannot be disabled in the BIOS and should already be enabled. The virtualization extensions may be labeled <span class="guilabel"><strong>Virtualization Extensions</strong></span>, <span class="guilabel"><strong>Vanderpool</strong></span> or various other names depending on the OEM and system BIOS.
+ </div></li><li class="step"><div class="para">
+ Enable Intel VT-d or AMD IOMMU, if the options are available. Intel VT-d and AMD IOMMU are used for PCI device assignment.
+ </div></li><li class="step"><div class="para">
+ Select <span class="guilabel"><strong>Save & Exit</strong></span>.
+ </div></li></ol></li><li class="step"><div class="para">
+ Reboot the machine.
+ </div></li><li class="step"><div class="para">
+ When the machine has booted, run <code class="command">cat /proc/cpuinfo |grep -E "vmx|svm"</code>. Specifying <em class="parameter"><code>--color</code></em> is optional, but useful if you want the search term highlighted. 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><div class="section" id="sect-Virtualization-Troubleshooting-KVM_networking_performance"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.8. KVM networking performance</h2></div></div></div><div class="para">
+ By default, KVM virtual machines are assigned a virtual Realtek 8139 (rtl8139) NIC (network interface controller) if they are Windows guests or the guest type is not specified. Fedora guests are assigned a virtio NIC by default.
+ </div><div class="para">
+ The rtl8139 virtualized NIC works fine in most environments. However, this device can suffer from performance degradation problems on some networks, for example, a 10 Gigabit Ethernet network.
+ </div><div class="para">
+ To improve performance switch to the para-virtualized network driver.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Note that the virtualized Intel PRO/1000 (<code class="systemitem">e1000</code>) driver is also supported as an emulated driver choice. To use the <code class="computeroutput">e1000</code> driver, replace <code class="computeroutput">virtio</code> in the procedure below with <code class="computeroutput">e1000</code>. For the best performance it is recommended to use the <code class="computeroutput">virtio</code> driver.
+ </div></div></div><div class="procedure"><h6>Procedure A.2. Switching to the virtio driver</h6><ol class="1"><li class="step"><div class="para">
+ Shutdown the guest operating system.
+ </div></li><li class="step"><div class="para">
+ Edit the guest's configuration file with the <code class="command">virsh</code> command (where <em class="parameter"><code>GUEST</code></em> is the guest's name):
+ </div><pre class="screen"># virsh edit <em class="parameter"><code>GUEST</code></em>
+</pre><div class="para">
+ The <code class="command">virsh edit</code> command uses the <code class="command">$EDITOR</code> shell variable to determine which editor to use.
+ </div></li><li class="step"><div class="para">
+ Find the network interface section of the configuration. This section resembles the snippet below:
+ </div><pre class="screen"><interface type='network'>
+ <span class="emphasis"><em>[output truncated]</em></span>
+ <model type='rtl8139' />
+</interface>
+</pre></li><li class="step"><div class="para">
+ Change the type attribute of the model element from <em class="parameter"><code>'rtl8139'</code></em> to <em class="parameter"><code>'virtio'</code></em>. This will change the driver from the rtl8139 driver to the e1000 driver.
+ </div><pre class="screen"><interface type='network'>
+ <span class="emphasis"><em>[output truncated]</em></span>
+ <model type=<em class="parameter"><code>'virtio'</code></em> />
+</interface>
+</pre></li><li class="step"><div class="para">
+ Save the changes and exit the text editor
+ </div></li><li class="step"><div class="para">
+ Restart the guest operating system.
+ </div></li></ol></div><div class="formalpara"><h5 class="formalpara" id="idm114482368">Creating new guests using other network drivers</h5>
+ Alternatively, new guests can be created with a different network driver. This may be required if you are having difficulty installing guests over a network connection. This method requires you to have at least one guest already created (possibly installed from CD or DVD) to use as a template.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Create an XML template from an existing guest (in this example, named <em class="replaceable"><code>Guest1</code></em>):
+ </div><pre class="screen"># virsh dumpxml <em class="replaceable"><code>Guest1</code></em> > /tmp/<em class="replaceable"><code>guest-template</code></em>.xml
+</pre></li><li class="step"><div class="para">
+ Copy and edit the XML file and update the unique fields: virtual machine name, UUID, disk image, MAC address, and any other unique parameters. Note that you can delete the UUID and MAC address lines and virsh will generate a UUID and MAC address.
+ </div><pre class="screen"># cp /tmp/<em class="replaceable"><code>guest-template</code></em>.xml /tmp/<em class="replaceable"><code>new-guest</code></em>.xml
+# vi /tmp/<em class="replaceable"><code>new-guest</code></em>.xml
+</pre><div class="para">
+ Add the model line in the network interface section:
+ </div><pre class="screen"> <interface type='network'>
+ <span class="emphasis"><em>[output truncated]</em></span>
+ <model type='virtio' />
+</interface>
+</pre></li><li class="step"><div class="para">
+ Create the new virtual machine:
+ </div><pre class="screen"># virsh define /tmp/new-guest.xml
+# virsh start new-guest
+</pre></li></ol></div></div><div class="section" id="sect-Virtualization-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.9. Missing characters on guest console with Japanese keyboard</h2></div></div></div><div class="para">
+ On a Fedora host, connecting a Japanese keyboard locally to a machine may result in typed characters such as the underscore (the <span class="bold bold"><strong>_</strong></span> character) not being displayed correctly in guest consoles. This occurs because the required keymap is not set correctly by default.
+ </div><div class="para">
+ When Using Fedora with Red Hat Enterprise Linux 6 guests, there is usually no error message produced when pressing the associated key. However, Red Hat Enterprise Linux 4 and Red Hat Enterprise Linux 5 guests may display an error similar to the following:
+ </div><pre class="screen">
+atkdb.c: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0).
+atkbd.c: Use 'setkeycodes 00 <keycode>' to make it known.
+</pre><div class="para">
+ To fix this issue in <code class="command">virt-manager</code>, perform the following steps:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Open the affected guest in <code class="command">virt-manager</code>.
+ </div></li><li class="listitem"><div class="para">
+ Click <span class="guimenu"><strong>View</strong></span> → <span class="guisubmenu"><strong>Details</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ Select <span class="guilabel"><strong>Display VNC</strong></span> in the list.
+ </div></li><li class="listitem"><div class="para">
+ Change <span class="bold bold"><strong>Auto</strong></span> to <span class="bold bold"><strong>ja</strong></span> in the <span class="guilabel"><strong>Keymap</strong></span> pull-down menu.
+ </div></li><li class="listitem"><div class="para">
+ Click the <span class="guilabel"><strong>Apply</strong></span> button.
+ </div></li></ul></div><div class="para">
+ Alternatively, to fix this issue using the <code class="command">virsh edit</code> command on the target guest:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Run <code class="command">virsh edit <target guest></code>
+ </div></li><li class="listitem"><div class="para">
+ Add the following attribute to the <graphics> tag: <span class="bold bold"><strong>keymap='ja'</strong></span>. For example:
+<pre class="screen">
+ <graphics type='vnc' port='-1' autoport='yes' <span class="bold bold"><strong>keymap='ja'</strong></span>/>
+</pre>
+ </div></li></ul></div></div><div class="section" id="sec-known-issues-windows-xp-guests"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.10. Known Windows XP guest issues</h2></div></div></div><div class="para">
+ If you perform device-add quickly followed by device-del using a Windows XP guest, the guest does not eject the device and instead it displays the following error: "The device (device name) cannot be stopped because of an unknown error. Since the device is still being used, do not remove it". It should be noted that newer Windows OS version guests as well as all known Linux guests do not experience this problem. To prevent this issue from happening, wait to delete a device that you just added.
+ </div></div></div><div xml:lang="en-US" class="appendix" id="idm61545728" lang="en-US"><div class="titlepage"><div><div><h1 id="idm61545728" class="title">Common <span class="application"><strong>libvirt</strong></span> errors and troubleshooting</h1></div></div></div><div class="para">
+ This appendix documents common <span class="application"><strong>libvirt</strong></span>-related problems and errors along with instructions for dealing with them.
+ </div><div class="para">
+ Locate the error on the table below and follow the corresponding link under <code class="literal">Solution</code> for detailed troubleshooting information.
+ </div><div class="table"><h6>Table B.1. Common <span class="application">libvirt</span> errors</h6><div class="table-contents"><table summary="Common libvirt errors" border="1"><colgroup><col align="left" class="c1" width="33%" /><col align="left" class="c2" width="33%" /><col align="left" class="c3" width="33%" /></colgroup><thead><tr><th class="" align="left">
+ Error
+ </th><th class="" align="left">
+ Description of problem
+ </th><th class="" align="left">
+ Solution
+ </th></tr></thead><tbody><tr><td class="" align="left">
+ <code class="computeroutput"><span class="application"><strong>libvirtd</strong></span> failed to start</code>
+ </td><td class="" align="left">
+ The <span class="application"><strong>libvirt</strong></span> daemon failed to start. However, there is no information about this error in <code class="filename">/var/log/messages</code>.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Libvirt_Daemon">Section B.1, “<span class="application"><strong>libvirtd</strong></span> failed to start”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Cannot read CA certificate</code>
+ </td><td class="" align="left">
+ This is one of several errors that occur when the URI fails to connect to the hypervisor.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Hypervisor_Connection_Fail">Section B.2, “The URI failed to connect to the hypervisor”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Failed to connect socket ... : Permission denied</code>
+ </td><td class="" align="left">
+ This is one of several errors that occur when the URI fails to connect to the hypervisor.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Hypervisor_Connection_Fail">Section B.2, “The URI failed to connect to the hypervisor”</a>
+ </td></tr><tr><td class="" align="left">
+ Other connectivity errors
+ </td><td class="" align="left">
+ These are other errors that occur when the URI fails to connect to the hypervisor.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Hypervisor_Connection_Fail">Section B.2, “The URI failed to connect to the hypervisor”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Internal error guest CPU is not compatible with host CPU</code>
+ </td><td class="" align="left">
+ The guest virtual machine cannot be started because the host and guest processors are different.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Domain_Processor">Section B.3, “The guest virtual machine cannot be started: <code class="computeroutput">internal error guest CPU is not compatible with host CPU</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Failed to create domain from vm.xml error: monitor socket did not show up.: Connection refused</code>
+ </td><td class="" align="left">
+ The guest virtual machine (or domain) starting fails and returns this error or similar.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Domain_Monitor_Socket">Section B.4, “Guest starting fails with error: <code class="computeroutput">monitor socket did not show up</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Internal error cannot find character device (null)</code>
+ </td><td class="" align="left">
+ This error can occur when attempting to connect a guest's console. It reports that there is no serial console configured for the guest virtual machine.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Domain_Console">Section B.5, “<code class="computeroutput">Internal error cannot find character device (null)</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">No boot device</code>
+ </td><td class="" align="left">
+ After building a guest virtual machine from an existing disk image, the guest booting stalls. However, the guest can start successfully using the <code class="command">QEMU</code> command directly.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Domain_Not_Booting">Section B.6, “Guest virtual machine booting stalls with error: <code class="computeroutput">No boot device</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">The virtual network <em class="replaceable"><code>"default"</code></em> has not been started</code>
+ </td><td class="" align="left">
+ <div class="para">
+ If the <em class="replaceable"><code>default</code></em> network (or other locally-created network) is unable to start, any virtual machine configured to use that network for its connectivity will also fail to start.
+ </div>
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Virt_Net_Not_Starting">Section B.7, “Virtual network <em class="replaceable"><code>default</code></em> has not been started”</a>
+ </td></tr><tr><td class="" align="left">
+ PXE boot (or DHCP) on guest failed
+ </td><td class="" align="left">
+ A guest virtual machine starts successfully, but is unable to acquire an IP address from DHCP, boot using the PXE protocol, or both. This is often a result of a long forward delay time set for the bridge, or when the <span class="package">iptables</span> package and kernel do not support checksum mangling rules.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_PXE_Guest_Boot_Fail">Section B.8, “PXE boot (or DHCP) on guest failed”</a>
+ </td></tr><tr><td class="" align="left">
+ Guest can reach outside network, but cannot reach host when using macvtap interface
+ </td><td class="" align="left">
+ <div class="para">
+ A guest can communicate with other guests, but cannot connect to the host machine after being configured to use a macvtap (or <em class="parameter"><code>type='direct'</code></em>) network interface.
+ </div>
+ <div class="para">
+ This is actually not an error — it is the defined behavior of macvtap.
+ </div>
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Macvtap">Section B.9, “Guest can reach outside network, but cannot reach host when using macvtap interface”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Could not add rule to fixup DHCP response checksums on network <em class="replaceable"><code>'default'</code></em></code>
+ </td><td class="" align="left">
+ This warning message is almost always harmless, but is often mistakenly seen as evidence of a problem.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_DHCP_Response_Checksums">Section B.10, “Could not add rule to fixup DHCP response checksums on network <em class="replaceable"><code>'default'</code></em>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Unable to add bridge br0 port vnet0: No such device</code>
+ </td><td class="" align="left">
+ This error message or the similar <code class="computeroutput">Failed to add tap interface to bridge <em class="replaceable"><code>'br0'</code></em>: No such device</code> reveal that the bridge device specified in the guest's (or domain's) <code class="code"><interface></code> definition does not exist.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Bridge_Device">Section B.11, “Unable to add bridge br0 port vnet0: No such device”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Warning: could not open /dev/net/tun: no virtual network emulation qemu-kvm: -netdev tap,script=/etc/my-qemu-ifup,id=hostnet0: Device 'tap' could not be initialized</code>
+ </td><td class="" align="left">
+ The guest virtual machine does not start after configuring a <code class="code">type='ethernet'</code> (or 'generic ethernet') interface in the host system. This error or similar appears either in <code class="filename">libvirtd.log</code>, <code class="filename">/var/log/libvirt/qemu/<em class="replaceable"><code>name_of_guest</code></em>.log</code>, or in both.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Generic_Ethernet">Section B.12, “Guest is unable to start with error: <code class="computeroutput">warning: could not open /dev/net/tun</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Unable to resolve address <em class="replaceable"><code>name_of_host</code></em> service '49155': Name or service not known</code>
+ </td><td class="" align="left">
+ <span class="application"><strong>QEMU</strong></span> guest migration fails and this error message appears with an unfamiliar hostname.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Migration_Address">Section B.13, “Migration fails with <code class="computeroutput">Error: unable to resolve address</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Unable to allow access for disk path /var/lib/libvirt/images/qemu.img: No such file or directory</code>
+ </td><td class="" align="left">
+ A guest virtual machine cannot be migrated because <span class="application"><strong>libvirt</strong></span> cannot access the disk image(s).
+ </td><td class="" align="left">
+ <a class="xref" href="#App_Migration_Disk_Image">Section B.14, “Migration fails with <code class="computeroutput">Unable to allow access for disk path: No such file or directory</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ No guest virtual machines are present when <span class="application"><strong>libvirtd</strong></span> is started
+ </td><td class="" align="left">
+ The <span class="application"><strong>libvirt</strong></span> daemon is successfully started, but no guest virtual machines appear to be present when running <code class="command">virsh list --all</code>.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_No_Guest_Machines">Section B.15, “No guest virtual machines are present when <span class="application"><strong>libvirtd</strong></span> is started”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor</code>
+ </td><td class="" align="left">
+ While <span class="application"><strong>libvirtd</strong></span> should listen on TCP ports for connections, the connection to the hypervisor fails.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_TCP_Ports">Section B.16, “Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor”</a>
+ </td></tr><tr><td class="" align="left">
+ Common XML errors
+ </td><td class="" align="left">
+ <span class="application"><strong>libvirt</strong></span> uses XML documents to store structured data. Several common errors occur with XML documents when they are passed to <span class="application"><strong>libvirt</strong></span> through the API. This entry provides instructions for editing guest XML definitions, and details common errors in XML syntax and configuration.
+ </td><td class="" align="left">
+ <a class="xref" href="#App_XML_Errors">Section B.17, “Common XML errors”</a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div xml:lang="en-US" class="section" id="App_Libvirt_Daemon" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.1. <span class="application"><strong>libvirtd</strong></span> failed to start</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The <span class="application"><strong>libvirt</strong></span> daemon does not start automatically. Starting the <span class="application"><strong>libvirt</strong></span> daemon manually fails as well:
+ </div><pre class="screen"># /etc/init.d/libvirtd start
+* Caching service dependencies ... [ ok ]
+* Starting libvirtd ...
+/usr/sbin/libvirtd: error: Unable to initialize network sockets. Check /var/log/messages or run without --daemon for more info.
+* start-stop-daemon: failed to start `/usr/sbin/libvirtd' [ !! ]
+* ERROR: libvirtd failed to start</pre><div class="para">
+ Moreover, there is not <code class="literal">'more info'</code> about this error in <code class="filename">/var/log/messages</code>.
+ </div></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ Change <span class="application"><strong>libvirt's</strong></span> logging in <code class="filename">/etc/libvirt/libvirtd.conf</code> by uncommenting the line below. To uncomment the line, open the <code class="filename">/etc/libvirt/libvirtd.conf</code> file in a text editor, remove the hash (or <code class="literal">#</code>) symbol from the beginning of the following line, and save the change:
+ </div><pre class="screen">log_outputs="3:syslog:libvirtd"</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ This line is commented out by default to prevent <span class="application"><strong>libvirt</strong></span> from producing excessive log messages. After diagnosing the problem, it is recommended to comment this line again in the <code class="filename">/etc/libvirt/libvirtd.conf</code> file.
+ </div></div></div><div class="para">
+ Restart <span class="application"><strong>libvirt</strong></span> to determine if this has solved the problem.
+ </div><div class="para">
+ If <code class="filename">libvirtd</code> still does not start successfully, an error similar to the following will be shown in the <code class="filename">/var/log/messages</code> file:
+ </div><pre class="programlisting">Feb 6 17:22:09 bart libvirtd: 17576: info : libvirt version: 0.9.9
+Feb 6 17:22:09 bart libvirtd: 17576: error : virNetTLSContextCheckCertFile:92: Cannot read CA certificate '/etc/pki/CA/cacert.pem': No such file or directory
+Feb 6 17:22:09 bart /etc/init.d/libvirtd[17573]: start-stop-daemon: failed to start `/usr/sbin/libvirtd'
+Feb 6 17:22:09 bart /etc/init.d/libvirtd[17565]: ERROR: libvirtd failed to start</pre><div class="para">
+ The <span class="application"><strong>libvirtd</strong></span> man page shows that the missing <code class="filename">cacert.pem</code> file is used as TLS authority when <span class="application"><strong>libvirt</strong></span> is run in <code class="literal">Listen for TCP/IP connections</code> mode. This means the <em class="parameter"><code>--listen</code></em> parameter is being passed.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Configure the <span class="application"><strong>libvirt</strong></span> daemon's settings with one of the following methods:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Install a CA certificate.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ For more information on CA certificates and configuring system authentication, refer to the Configuring Authentication chapter in the <em class="citetitle">Fedora Deployment Guide</em>.
+ </div></div></div></li><li class="listitem"><div class="para">
+ Do not use TLS; use bare TCP instead. In <code class="filename">/etc/libvirt/libvirtd.conf</code> set <code class="option">listen_tls = 0</code> and <code class="option">listen_tcp = 1</code>. The default values are <code class="option">listen_tls = 1</code> and <code class="option">listen_tcp = 0</code>.
+ </div></li><li class="listitem"><div class="para">
+ Do not pass the <em class="parameter"><code>--listen</code></em> parameter. In <code class="filename">/etc/sysconfig/libvirtd.conf</code> change the <em class="parameter"><code>LIBVIRTD_ARGS</code></em> variable.
+ </div></li></ul></div></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_Hypervisor_Connection_Fail" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.2. The URI failed to connect to the hypervisor</h2></div></div></div><div class="para">
+ Several different errors can occur when connecting to the server (for example, when running <code class="command">virsh</code>).
+ </div><div class="section" id="Sect_Cannot_read_CA_certificate"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">B.2.1. Cannot read CA certificate</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ When running a command, the following error (or similar) appears:
+ </div><pre class="screen">$ virsh -c <em class="replaceable"><code>name_of_uri</code></em> list
+error: Cannot read CA certificate '/etc/pki/CA/cacert.pem': No such file or directory
+error: failed to connect to the hypervisor</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ The error message is misleading about the actual cause. This error can be caused by a variety of factors, such as an incorrectly specified URI, or a connection that is not configured.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Incorrectly specified URI</span></dt><dd><div class="para">
+ When specifying <em class="parameter"><code>qemu://system</code></em> or <em class="parameter"><code>qemu://session</code></em> as a connection URI, <code class="command">virsh</code> attempts to connect to hostnames <em class="parameter"><code>system</code></em> or <em class="parameter"><code>session</code></em> respectively. This is because <code class="command">virsh</code> recognizes the text after the second forward slash as the host.
+ </div><div class="para">
+ Use three forward slashes to connect to the local host. For example, specifying <em class="parameter"><code>qemu:///system</code></em> instructs <code class="command">virsh</code> connect to the <em class="parameter"><code>system</code></em> instance of <span class="application"><strong>libvirtd</strong></span> on the local host.
+ </div><div class="para">
+ When a hostname is specified, the <span class="application"><strong>QEMU</strong></span> transport defaults to <code class="systemitem">TLS</code>. This results in certificates.
+ </div></dd><dt class="varlistentry"><span class="term">Connection is not configured</span></dt><dd><div class="para">
+ The URI is correct (for example, <em class="parameter"><code>qemu[+tls]://server/system</code></em>) but the certificates are not set up properly on your machine. For information on configuring TLS, see <a href="http://wiki.libvirt.org/page/TLSSetup">Setting up <span class="application"><strong>libvirt</strong></span> for TLS</a> available from the <span class="application"><strong>libvirt</strong></span> website.
+ </div></dd></dl></div></dd></dl></div></div><div class="section" id="Sect_Failed_to_connect_socket"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">B.2.2. Failed to connect socket ... : Permission denied</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ When running a <code class="command">virsh</code> command, the following error (or similar) appears:
+ </div><pre class="screen">$ virsh -c qemu:///system list
+error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Permission denied
+error: failed to connect to the hypervisor</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ Without any hostname specified, the connection to <span class="application"><strong>QEMU</strong></span> uses UNIX sockets by default. If there is no error running this command as root, the UNIX socket options in <code class="filename">/etc/libvirt/libvirtd.conf</code> are likely misconfigured.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ To connect as a non-root user using UNIX sockets, configure the following options in <code class="filename">/etc/libvirt/libvirtd.conf</code>:
+ </div><pre class="programlisting">unix_sock_group = <code class="literal"><group></code>
+unix_sock_ro_perms = <perms>
+unix_sock_rw_perms = <perms></pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The user running <code class="command">virsh</code> must be a member of the <code class="literal">group</code> specified in the <code class="option">unix_sock_group</code> option.
+ </div></div></div></dd></dl></div></div><div class="section" id="Sect_Other_Connectivity_Errors"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">B.2.3. Other connectivity errors</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Unable to connect to server at <code class="literal">server:port</code>: Connection refused</span></dt><dd><div class="para">
+ The daemon is not running on the server or is configured not to listen, using configuration option <code class="option">listen_tcp</code> or <code class="option">listen_tls</code>.
+ </div></dd><dt class="varlistentry"><span class="term">End of file while reading data: nc: using stream socket: Input/output error</span></dt><dd><div class="para">
+ If you specified <code class="systemitem">ssh</code> transport, the daemon is likely not running on the server. Solve this error by verifying that the daemon is running on the server.
+ </div></dd></dl></div></div></div><div xml:lang="en-US" class="section" id="App_Domain_Processor" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.3. The guest virtual machine cannot be started: <code class="computeroutput">internal error guest CPU is not compatible with host CPU</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ Running on an Intel Core i7 processor (which <span class="application"><strong>virt-manager</strong></span> refers to as <code class="literal">Nehalem</code>, or the older Core 2 Duo, referred to as <code class="literal">Penryn</code>), a KVM guest (or domain) is created using <span class="application"><strong>virt-manager</strong></span>. After installation, the guest's processor is changed to match the host's CPU. The guest is then unable to start and reports this error:
+ </div><pre class="screen">2012-02-06 17:49:15.985+0000: 20757: error : qemuBuildCpuArgStr:3565 : internal error guest CPU is not compatible with host CPU</pre><div class="para">
+ Additionally, clicking <code class="literal">Copy host CPU configuration</code> in <span class="application"><strong>virt-manager</strong></span> shows Pentium III instead of <code class="literal">Nehalem</code> or <code class="literal">Penryn</code>.
+ </div></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ The <code class="filename">/usr/share/libvirt/cpu_map.xml</code> file lists the flags that define each CPU model. The <code class="literal">Nehalem</code> and <code class="literal">Penryn</code> definitions contain this:
+ </div><pre class="programlisting"><feature name='nx'/></pre><div class="para">
+ As a result, the <code class="literal">NX</code> (or <code class="literal">No eXecute</code>) flag needs to be presented to identify the CPU as <code class="literal">Nehalem</code> or <code class="literal">Penryn</code>. However, in <code class="filename">/proc/cpuinfo</code>, this flag is missing.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Nearly all new BIOSes allow enabling or disabling of the <code class="literal">No eXecute</code> bit. However, if disabled, some CPUs do not report this flag and thus <span class="application"><strong>libvirt</strong></span> detects a different CPU. Enabling this functionality instructs <span class="application"><strong>libvirt</strong></span> to report the correct CPU. Refer to your hardware documentation for further instructions on this subject.
+ </div></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_Domain_Monitor_Socket" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.4. Guest starting fails with error: <code class="computeroutput">monitor socket did not show up</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The guest virtual machine (or domain) starting fails with this error (or similar):
+ </div><pre class="screen"># virsh -c qemu:///system create <em class="replaceable"><code>name_of_guest</code></em>.xml error: Failed to create domain from <em class="replaceable"><code>name_of_guest</code></em>.xml error: monitor socket did not show up.: Connection refused</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This error message shows:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <span class="application"><strong>libvirt</strong></span> is working;
+ </div></li><li class="listitem"><div class="para">
+ The <span class="application"><strong>QEMU</strong></span> process failed to start up; and
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>libvirt</strong></span> quits when trying to connect <span class="application"><strong>QEMU</strong></span> or the QEMU agent monitor socket.
+ </div></li></ol></div><div class="para">
+ To understand the error details, examine the guest log:
+ </div><pre class="screen"># cat /var/log/libvirt/qemu/<em class="replaceable"><code>name_of_guest</code></em>.log
+LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-kvm -S -M pc -enable-kvm -m 768 -smp 1,sockets=1,cores=1,threads=1 -name <em class="replaceable"><code>name_of_guest</code></em> -uuid ebfaadbe-e908-ba92-fdb8-3fa2db557a42 -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/<em class="replaceable"><code>name_of_guest</code></em>.monitor,server,nowait -mon chardev=monitor,mode=readline -no-reboot -boot c -kernel /var/lib/libvirt/boot/vmlinuz -initrd /var/lib/libvirt/boot/initrd.img -append method=http://www.example.com/pub/product/release/version/x86_64/os/ -drive file=/var/lib/libvirt/images/<em class="replaceable"><code>name_of_guest</code></em>.img,if=none,id=drive-ide0-0-0,boot=on -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -device virtio-net-pci,vlan=0,id=net0,mac=52:40:00:f4:f1:0a,bus=pci.0,addr=0x4 -net tap,fd=42,vlan=0,name=hostnet0 -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -vnc 127
.0.0.1:0 -k en-gb -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,
+addr=0x3
+char device redirected to /dev/pts/1
+qemu: could not load kernel '/var/lib/libvirt/boot/vmlinuz':
+Permission denied</pre></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ The guest log contains the details needed to fix the error.
+ </div><div class="para">
+ If a host is shut down while the guest is still running a <span class="application"><strong>libvirt</strong></span> version prior to 0.9.5, the libvirt-guest's init script attempts to perform a managed save of the guest. If the managed save was incomplete (for example, due to loss of power before the managed save image was flushed to disk), the save image is corrupted and will not be loaded by <span class="application"><strong>QEMU</strong></span>. The older version of <span class="application"><strong>libvirt</strong></span> does not recognize the corruption, making the problem perpetual. In this case, the guest log will show an attempt to use <code class="command">-incoming</code> as one of its arguments, meaning that <span class="application"><strong>libvirt</strong></span> is trying to start <span class="application"><strong>QEMU</strong></span> by migrating in the saved state file.
+ </div><div class="para">
+ This problem can be fixed by running <code class="command">virsh managedsave-remove <em class="replaceable"><code>name_of_guest</code></em></code> to remove the corrupted managed save image. Newer versions of <span class="application"><strong>libvirt</strong></span> take steps to avoid the corruption in the first place, as well as adding <code class="command">virsh start --force-boot <em class="replaceable"><code>name_of_guest</code></em></code> to bypass any managed save image.
+ </div></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_Domain_Console" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.5. <code class="computeroutput">Internal error cannot find character device (null)</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ This error message appears when attempting to connect to a guest virtual machine's console:
+ </div><pre class="screen"># virsh console test2 Connected to domain test2 Escape character is ^] error: internal error cannot find character device (null)</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This error message shows that there is no serial console configured for the guest virtual machine.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Set up a serial console in the guest's XML file.
+ </div><div class="procedure"><h6>Procedure B.1. Setting up a serial console in the guest's XML</h6><ol class="1"><li class="step"><div class="para">
+ Add the following XML to the guest virtual machine's XML using <span class="application"><strong>virsh edit</strong></span>:
+ </div><pre class="programlisting"><serial type='pty'>
+ <target port='0'/>
+</serial>
+<console type='pty'>
+ <target type='serial' port='0'/>
+</console></pre></li><li class="step"><div class="para">
+ Set up the console in the guest kernel command line.
+ </div><div class="para">
+ To do this, either log in to the guest virtual machine to edit the <code class="filename">/boot/grub/grub.conf</code> file directly, or use the <span class="application"><strong>virt-edit</strong></span> command line tool. Add the following to the guest kernel command line:
+ </div><pre class="screen">console=ttyS0,115200</pre></li><li class="step"><div class="para">
+ Run the followings command:
+ </div><pre class="screen"># virsh start vm && virsh console vm</pre></li></ol></div></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_Domain_Not_Booting" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.6. Guest virtual machine booting stalls with error: <code class="computeroutput">No boot device</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ After building a guest virtual machine from an existing disk image, the guest booting stalls with the error message <code class="computeroutput">No boot device</code>. However, the guest virtual machine can start successfully using the <code class="command">QEMU</code> command directly.
+ </div></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ The disk's bus type is not specified in the command for importing the existing disk image:
+ </div><pre class="screen"># virt-install \
+--connect qemu:///system \
+--ram 2048 -n rhel_64 \
+--os-type=linux --os-variant=rhel5 \
+--disk path=/root/RHEL-Server-5.8-64-virtio.qcow2,device=disk,format=qcow2 \
+--vcpus=2 --graphics spice --noautoconsole --import
+</pre><div class="para">
+ However, the command line used to boot up the guest virtual machine using <span class="application"><strong>QEMU</strong></span> directly shows that it uses <code class="literal">virtio</code> for its bus type:
+ </div><pre class="screen"># ps -ef | grep qemu
+/usr/libexec/qemu-kvm -monitor stdio -drive file=/root/RHEL-Server-5.8-32-virtio.qcow2,index=0,<span class="bold bold"><strong>if=virtio</strong></span>,media=disk,cache=none,format=qcow2 -net nic,vlan=0,model=rtl8139,macaddr=00:30:91:aa:04:74 -net tap,vlan=0,script=/etc/qemu-ifup,downscript=no -m 2048 -smp 2,cores=1,threads=1,sockets=2 -cpu qemu64,+sse2 -soundhw ac97 -rtc-td-hack -M rhel5.6.0 -usbdevice tablet -vnc :10 -boot c -no-kvm-pit-reinjection</pre><div class="para">
+ Note the <em class="parameter"><code>bus=</code></em> in the guest's XML generated by <span class="application"><strong>libvirt</strong></span> for the imported guest:
+ </div><pre class="programlisting">
+<domain type='qemu'>
+ <name>rhel_64</name>
+ <uuid>6cd34d52-59e3-5a42-29e4-1d173759f3e7</uuid>
+ <memory>2097152</memory>
+ <currentMemory>2097152</currentMemory>
+ <vcpu>2</vcpu>
+ <os>
+ <type arch='x86_64' machine='rhel5.4.0'>hvm</type>
+ <boot dev='hd'/>
+ </os>
+ <features>
+ <acpi/>
+ <apic/>
+ <pae/>
+ </features>
+ <clock offset='utc'>
+ <timer name='pit' tickpolicy='delay'/>
+ </clock>
+ <on_poweroff>destroy</on_poweroff>
+ <on_reboot>restart</on_reboot>
+ <on_crash>restart</on_crash>
+ <devices>
+ <emulator>/usr/libexec/qemu-kvm</emulator>
+ <disk type='file' device='disk'>
+ <driver name='qemu' type='qcow2' cache='none'/>
+ <source file='/root/RHEL-Server-5.8-64-virtio.qcow2'/>
+ <emphasis role="bold"><target dev='hda' bus='ide'/></emphasis>
+ <address type='drive' controller='0' bus='0' unit='0'/>
+ </disk>
+ <controller type='ide' index='0'/>
+ <interface type='bridge'>
+ <mac address='54:52:00:08:3e:8c'/>
+ <source bridge='br0'/>
+ </interface>
+ <serial type='pty'>
+ <target port='0'/>
+ </serial>
+ <console type='pty'>
+ <target port='0'/>
+ </console>
+ <input type='mouse' bus='ps2'/>
+ <graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
+ <video>
+ <model type='cirrus' vram='9216' heads='1'/>
+ </video>
+ </devices>
+ </domain>
+</pre><div class="para">
+ The bus type for the disk is set as <em class="parameter"><code>ide</code></em>, which is the default value set by <span class="application"><strong>libvirt</strong></span>. This is the incorrect bus type, and has caused the unsuccessful boot for the imported guest.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="procedure"><h6>Procedure B.2. Correcting the disk bus type</h6><ol class="1"><li class="step"><div class="para">
+ Undefine the imported guest, then re-import it with <em class="parameter"><code>bus=virtio</code></em> and the following:
+ </div><pre class="screen"># virsh destroy rhel_64
+# virsh undefine rhel_64
+# virt-install \
+--connect qemu:///system \
+--ram 1024 -n rhel_64 -r 2048 \
+--os-type=linux --os-variant=rhel5 \
+--disk path=/root/RHEL-Server-5.8-64-virtio.qcow2,device=disk,<span class="bold bold"><strong>bus=virtio</strong></span>,format=qcow2 \
+--vcpus=2 --graphics spice --noautoconsole --import</pre></li><li class="step"><div class="para">
+ Edit the imported guest's XML using <code class="command">virsh edit</code> and correct the disk bus type.
+ </div></li></ol></div></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_Virt_Net_Not_Starting" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.7. Virtual network <em class="replaceable"><code>default</code></em> has not been started</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ Normally, the configuration for a virtual network named <em class="replaceable"><code>default</code></em> is installed as part of the <span class="package">libvirt</span> package, and is configured to autostart when <span class="application"><strong>libvirtd</strong></span> is started.
+ </div><div class="para">
+ If the <em class="replaceable"><code>default</code></em> network (or any other locally-created network) is unable to start, any virtual machine configured to use that network for its connectivity will also fail to start, resulting in this error message:
+ </div><pre class="screen">Virtual network <em class="replaceable"><code>default</code></em> has not been started</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ One of the most common reasons for a <span class="application"><strong>libvirt</strong></span> virtual network's failure to start is that the dnsmasq instance required to serve DHCP and DNS requests from clients on that network has failed to start.
+ </div><div class="para">
+ To determine if this is the cause, run <code class="command">virsh net-start default</code> from a root shell to start the <em class="replaceable"><code>default</code></em> virtual network.
+ </div><div class="para">
+ If this action does not successfully start the virtual network, open <code class="filename">/var/log/libvirt/libvirtd.log</code> to view the complete error log message.
+ </div><div class="para">
+ If a message similar to the following appears, the problem is likely a systemwide dnsmasq instance that is already listening on <span class="application"><strong>libvirt</strong></span>'s bridge, and is preventing <span class="application"><strong>libvirt</strong></span>'s own dnsmasq instance from doing so. The most important parts to note in the error message are <code class="literal">dnsmasq</code> and <code class="literal">exit status 2</code>:
+ </div><pre class="screen">Could not start virtual network <em class="replaceable"><code>default</code></em>: internal error
+Child process (/usr/sbin/dnsmasq --strict-order --bind-interfaces
+--pid-file=/var/run/libvirt/network/<em class="replaceable"><code>default</code></em>.pid --conf-file=
+--except-interface lo --listen-address 192.168.122.1
+--dhcp-range 192.168.122.2,192.168.122.254
+--dhcp-leasefile=/var/lib/libvirt/dnsmasq/<em class="replaceable"><code>default</code></em>.leases
+--dhcp-lease-max=253 --dhcp-no-override) status unexpected: exit status 2</pre></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ If the machine is not using dnsmasq to serve DHCP for the physical network, disable dnsmasq completely.
+ </div><div class="para">
+ If it is necessary to run dnsmasq to serve DHCP for the physical network, edit the <code class="filename">/etc/dnsmasq.conf</code> file. Add or uncomment the first line, as well as one of the two lines following that line. Do not add or uncomment all three lines:
+ </div><pre class="programlisting">bind-interfaces
+interface=<em class="replaceable"><code>name_of_physical_interface</code></em>
+listen-address=<em class="replaceable"><code>chosen_IP_address</code></em></pre><div class="para">
+ After making this change and saving the file, restart the systemwide dnsmasq service.
+ </div><div class="para">
+ Next, start the <em class="replaceable"><code>default</code></em> network with the <code class="command">virsh net-start default</code> command.
+ </div><div class="para">
+ Start the virtual machines.
+ </div></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_PXE_Guest_Boot_Fail" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.8. PXE boot (or DHCP) on guest failed</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ A guest virtual machine starts successfully, but is then either unable to acquire an IP address from DHCP or boot using the PXE protocol, or both. There are two common causes of this error: having a long forward delay time set for the bridge, and when the <span class="package">iptables</span> package and kernel do not support checksum mangling rules.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Long forward delay time on bridge</span></dt><dd><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This is the most common cause of this error. If the guest network interface is connecting to a bridge device that has STP (Spanning Tree Protocol) enabled, as well as a long forward delay set, the bridge will not forward network packets from the guest virtual machine onto the bridge until at least that number of forward delay seconds have elapsed since the guest connected to the bridge. This delay allows the bridge time to watch traffic from the interface and determine the MAC addresses behind it, and prevent forwarding loops in the network topology.
+ </div><div class="para">
+ If the forward delay is longer than the timeout of the guest's PXE or DHCP client, then the client's operation will fail, and the guest will either fail to boot (in the case of PXE) or fail to acquire an IP address (in the case of DHCP).
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ If this is the case, change the forward delay on the bridge to 0, disable STP on the bridge, or both.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ This solution applies only if the bridge is not used to connect multiple networks, but just to connect multiple endpoints to a single network (the most common use case for bridges used by <span class="application"><strong>libvirt</strong></span>).
+ </div></div></div><div class="para">
+ If the guest has interfaces connecting to a <span class="application"><strong>libvirt</strong></span>-managed virtual network, edit the definition for the network, and restart it. For example, edit the default network with the following command:
+ </div><pre class="screen"># virsh net-edit default</pre><div class="para">
+ Add the following attributes to the <code class="code"><bridge></code> element:
+ </div><pre class="programlisting"><<em class="replaceable"><code>name_of_bridge</code></em>='virbr0' <code class="code">delay='0' stp='on'</code>/></pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ <code class="code">delay='0'</code> and <code class="code">stp='on'</code> are the default settings for virtual networks, so this step is only necessary if the configuration has been modified from the default.
+ </div></div></div><div class="para">
+ If the guest interface is connected to a host bridge that was configured outside of <span class="application"><strong>libvirt</strong></span>, change the delay setting.
+ </div><div class="para">
+ Add or edit the following lines in the <code class="filename">/etc/sysconfig/network-scripts/ifcfg-<em class="replaceable"><code>name_of_bridge</code></em></code> file to turn STP on with a 0 second delay:
+ </div><pre class="programlisting">STP=on
+DELAY=0</pre><div class="para">
+ After changing the configuration file, restart the bridge device:
+ </div><pre class="programlisting">/sbin/ifdown <em class="replaceable"><code>name_of_bridge</code></em>
+/sbin/ifup <em class="replaceable"><code>name_of_bridge</code></em></pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If <em class="replaceable"><code>name_of_bridge</code></em> is not the root bridge in the network, that bridge's delay will eventually reset to the delay time configured for the root bridge. In this case, the only solution is to disable STP completely on <em class="replaceable"><code>name_of_bridge</code></em>.
+ </div></div></div></dd></dl></div></dd></dl></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">The <span class="package">iptables</span> package and kernel do not support checksum mangling rules</span></dt><dd><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This message is only a problem if all four of the following conditions are true:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The guest is using <span class="application"><strong>virtio</strong></span> network devices.
+ </div><div class="para">
+ If so, the configuration file will contain <code class="code">model type='virtio'</code>
+ </div></li><li class="listitem"><div class="para">
+ The host has the <code class="literal">vhost-net</code> module loaded.
+ </div><div class="para">
+ This is true if <code class="computeroutput"><code class="command">ls</code> <code class="filename">/dev/vhost-net</code></code> does not return an empty result.
+ </div></li><li class="listitem"><div class="para">
+ The guest is attempting to get an IP address from a DHCP server that is running directly on the host.
+ </div></li><li class="listitem"><div class="para">
+ The <span class="package">iptables</span> version on the host is older than 1.4.10.
+ </div><div class="para">
+ <span class="package">iptables</span> 1.4.10 was the first version to add the <code class="literal">libxt_CHECKSUM</code> extension. This is the case if the following message appears in the <span class="application"><strong>libvirtd</strong></span> logs:
+ </div><pre class="screen">warning: Could not add rule to fixup DHCP response checksums on network <em class="replaceable"><code>default</code></em>
+warning: May need to update iptables package and kernel to support CHECKSUM rule.</pre><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Unless all of the other three conditions in this list are also true, the above warning message can be disregarded, and is not an indicator of any other problems.
+ </div></div></div></li></ul></div><div class="para">
+ When these conditions occur, UDP packets sent from the host to the guest have uncomputed checksums. This makes the host's UDP packets seem invalid to the guest's network stack.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ To solve this problem, invalidate any of the four points above. The best solution is to update the host <span class="package">iptables</span> and kernel to <span class="package">iptables-1.4.10</span> or newer where possible. Otherwise, the most specific fix is to disable the <code class="literal">vhost-net</code> driver for this particular guest. To do this, edit the guest configuration with this command:
+ </div><pre class="screen">virsh edit <em class="replaceable"><code>name_of_guest</code></em></pre><div class="para">
+ Change or add a <code class="code"><driver></code> line to the <code class="code"><interface></code> section:
+ </div><pre class="programlisting"><interface type='network'>
+ <model type='virtio'/>
+ <driver name='qemu'/>
+ ...
+</interface></pre><div class="para">
+ Save the changes, shut down the guest, and then restart it.
+ </div><div class="para">
+ If this problem is still not resolved, the issue may be due to a conflict between <span class="application"><strong>firewalld</strong></span> and the default <span class="application"><strong>libvirt</strong></span> network.
+ </div><div class="para">
+ To fix this, stop <span class="application"><strong>firewalld</strong></span> with the <code class="command">service firewalld stop</code> command, then restart <span class="application"><strong>libvirt</strong></span> with the <code class="command">service libvirtd restart</code> command.
+ </div></dd></dl></div></dd></dl></div></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_Macvtap" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.9. Guest can reach outside network, but cannot reach host when using macvtap interface</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ A guest virtual machine can communicate with other guests, but cannot connect to the host machine after being configured to use a macvtap (also known as <em class="parameter"><code>type='direct'</code></em>) network interface.
+ </div></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ Even when not connecting to a Virtual Ethernet Port Aggregator (VEPA) or VN-Link capable switch, macvtap interfaces can be useful. Setting the mode of such an interface to <code class="option">bridge</code> allows the guest to be directly connected to the physical network in a very simple manner without the setup issues (or <span class="package">NetworkManager</span> incompatibility) that can accompany the use of a traditional host bridge device.
+ </div><div class="para">
+ However, when a guest virtual machine is configured to use a <em class="parameter"><code>type='direct'</code></em> network interface such as macvtap, despite having the ability to communicate with other guests and other external hosts on the network, the guest cannot communicate with its own host.
+ </div><div class="para">
+ This situation is actually not an error — it is the defined behavior of macvtap. Due to the way in which the host's physical Ethernet is attached to the macvtap bridge, traffic into that bridge from the guests that is forwarded to the physical interface cannot be bounced back up to the host's IP stack. Additionally, traffic from the host's IP stack that is sent to the physical interface cannot be bounced back up to the macvtap bridge for forwarding to the guests.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Use <span class="application"><strong>libvirt</strong></span> to create an isolated network, and create a second interface for each guest virtual machine that is connected to this network. The host and guests can then directly communicate over this isolated network, while also maintaining compatibility with <span class="package">NetworkManager</span>.
+ </div><div class="procedure"><h6>Procedure B.3. Creating an isolated network with <span class="application"><strong>libvirt</strong></span></h6><ol class="1"><li class="step"><div class="para">
+ Add and save the following XML in the <code class="filename">/tmp/isolated.xml</code> file. If the 192.168.254.0/24 network is already in use elsewhere on your network, you can choose a different network.
+ </div><pre class="programlisting"><network>
+ <name>isolated</name>
+ <ip address='192.168.254.1' netmask='255.255.255.0'>
+ <dhcp>
+ <range start='192.168.254.2' end='192.168.254.254' />
+ </dhcp>
+ </ip>
+</network></pre></li><li class="step"><div class="para">
+ Create the network with this command: <code class="command">virsh net-define /tmp/isolated.xml</code>
+ </div></li><li class="step"><div class="para">
+ Set the network to autostart with the <code class="command">virsh net-autostart isolated</code> command.
+ </div></li><li class="step"><div class="para">
+ Start the network with the <code class="command">virsh net-start isolated</code> command.
+ </div></li><li class="step"><div class="para">
+ Using <code class="command">virsh edit <em class="replaceable"><code>name_of_guest</code></em></code>, edit the configuration of each guest that uses macvtap for its network connection and add a new <em class="parameter"><code><interface></code></em> in the <em class="parameter"><code><devices></code></em> section similar to the following (note the <em class="parameter"><code><model type='virtio'/></code></em> line is optional to include):
+ </div><pre class="programlisting"><interface type='network'>
+ <source network='isolated'/>
+ <model type='virtio'/>
+</interface></pre></li><li class="step"><div class="para">
+ Shut down, then restart each of these guests.
+ </div></li></ol></div><div class="para">
+ The guests are now able to reach the host at the address 192.168.254.1, and the host will be able to reach the guests at the IP address they acquired from DHCP (alternatively, you can manually configure the IP addresses for the guests). Since this new network is isolated to only the host and guests, all other communication from the guests will use the macvtap interface.
+ </div></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_DHCP_Response_Checksums" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.10. Could not add rule to fixup DHCP response checksums on network <em class="replaceable"><code>'default'</code></em></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ This message appears:
+ </div><pre class="screen">Could not add rule to fixup DHCP response checksums on network <em class="replaceable"><code>'default'</code></em></pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ Although this message appears to be evidence of an error, it is almost always harmless.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Unless the problem you are experiencing is that the guest virtual machines are unable to acquire IP addresses through DHCP, this message can be ignored.
+ </div><div class="para">
+ If this is the case, refer to <a class="xref" href="#App_PXE_Guest_Boot_Fail">Section B.8, “PXE boot (or DHCP) on guest failed”</a> for further details on this situation.
+ </div></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_Bridge_Device" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.11. Unable to add bridge br0 port vnet0: No such device</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The following error message appears:
+ </div><pre class="screen">Unable to add bridge <em class="replaceable"><code>name_of_bridge</code></em> port vnet0: No such device</pre><div class="para">
+ For example, if the bridge name is <em class="replaceable"><code>br0</code></em>, the error message will appear as:
+ </div><pre class="screen">Unable to add bridge br0 port vnet0: No such device</pre><div class="para">
+ In <span class="application"><strong>libvirt</strong></span> versions 0.9.6 and earlier, the same error appears as:
+ </div><pre class="screen">Failed to add tap interface to bridge <em class="replaceable"><code>name_of_bridge</code></em>: No such device</pre><div class="para">
+ Or for example, if the bridge is named <em class="replaceable"><code>br0</code></em>:
+ </div><pre class="screen">Failed to add tap interface to bridge <em class="replaceable"><code>'br0'</code></em>: No such device</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ Both error messages reveal that the bridge device specified in the guest's (or domain's) <code class="code"><interface></code> definition does not exist.
+ </div><div class="para">
+ To verify the bridge device listed in the error message does not exist, use the shell command <code class="command">ifconfig <em class="replaceable"><code>br0</code></em></code>.
+ </div><div class="para">
+ A message similar to this confirms the host has no bridge by that name:
+ </div><pre class="screen"><em class="replaceable"><code>br0</code></em>: error fetching interface information: Device not found</pre><div class="para">
+ If this is the case, continue to the solution.
+ </div><div class="para">
+ However, if the resulting message is similar to the following, the issue exists elsewhere:
+ </div><pre class="screen"><em class="replaceable"><code>br0</code></em> Link encap:Ethernet HWaddr 00:00:5A:11:70:48
+ inet addr:10.22.1.5 Bcast:10.255.255.255 Mask:255.0.0.0
+ UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
+ RX packets:249841 errors:0 dropped:0 overruns:0 frame:0
+ TX packets:281948 errors:0 dropped:0 overruns:0 carrier:0
+ collisions:0 txqueuelen:0
+ RX bytes:106327234 (101.4 MiB) TX bytes:21182634 (20.2 MiB)</pre></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Edit the existing bridge or create a new bridge with <code class="command">virsh</code></span></dt><dd><div class="para">
+ Use <code class="command">virsh</code> to either edit the settings of an existing bridge or network, or to add the bridge device to the host system configuration.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Edit the existing bridge settings using <code class="command">virsh</code></span></dt><dd><div class="para">
+ Use <code class="command">virsh edit <em class="replaceable"><code>name_of_guest</code></em></code> to change the <code class="code"><interface></code> definition to use a bridge or network that already exists.
+ </div><div class="para">
+ For example, change <code class="code">type='bridge'</code> to <code class="code">type='network'</code>, and <code class="code"><source bridge='br0'/></code> to <code class="code"><source network='default'/></code>.
+ </div></dd><dt class="varlistentry"><span class="term">Create a host bridge using <code class="command">virsh</code></span></dt><dd><div class="para">
+ For <span class="application"><strong>libvirt</strong></span> version 0.9.8 and later, a bridge device can be created with the <code class="command">virsh iface-bridge</code> command. This will create a bridge device <em class="replaceable"><code>br0</code></em> with <code class="filename">eth0</code>, the physical network interface which is set as part of a bridge, attached:
+ </div><pre class="screen">virsh iface-bridge eth0 <em class="replaceable"><code>br0</code></em></pre><div class="para">
+ Optional: If desired, remove this bridge and restore the original <code class="filename">eth0</code> configuration with this command:
+ </div><pre class="screen">virsh iface-unbridge <em class="replaceable"><code>br0</code></em></pre></dd></dl></div></dd><dt class="varlistentry"><span class="term">Create a host bridge manually</span></dt><dd><div class="para">
+ For older versions of <span class="application"><strong>libvirt</strong></span>, it is possible to manually create a bridge device on the host. Refer to <a class="xref" href="#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt">Section 11.3, “Bridged networking with libvirt”</a> for instructions.
+ </div></dd></dl></div></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_Generic_Ethernet" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.12. Guest is unable to start with error: <code class="computeroutput">warning: could not open /dev/net/tun</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The guest virtual machine does not start after configuring a <code class="code">type='ethernet'</code> (also known as 'generic ethernet') interface in the host system. An error appears either in <code class="filename">libvirtd.log</code>, <code class="filename">/var/log/libvirt/qemu/<em class="replaceable"><code>name_of_guest</code></em>.log</code>, or in both, similar to the below message:
+ </div><pre class="screen">warning: could not open /dev/net/tun: no virtual network emulation qemu-kvm: -netdev tap,script=/etc/my-qemu-ifup,id=hostnet0: Device 'tap' could not be initialized</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ Use of the generic ethernet interface type (<code class="code"><interface type='ethernet'></code>) is discouraged, because using it requires lowering the level of host protection against potential security flaws in <span class="application"><strong>QEMU</strong></span> and its guests. However, it is sometimes necessary to use this type of interface to take advantage of some other facility that is not yet supported directly in <span class="application"><strong>libvirt</strong></span>. For example, <span class="application"><strong>openvswitch</strong></span> was not supported in <span class="application"><strong>libvirt</strong></span> until <span class="package">libvirt-0.9.11</span>, so in older versions of <span class="application"><strong>libvirt</strong></span>, <code class="code"><interface type='ethernet'></code> was the only way to connect a guest to an <span class="application"><strong>openvswitch</strong></span> bridge.
+ </div><div class="para">
+ However, if you configure a <code class="code"><interface type='ethernet'></code> interface without making any other changes to the host system, the guest virtual machine will not start successfully.
+ </div><div class="para">
+ The reason for this failure is that for this type of interface, a script called by <span class="application"><strong>QEMU</strong></span> needs to manipulate the tap device. However, with <code class="code">type='ethernet'</code> configured, in an attempt to lock down <span class="application"><strong>QEMU</strong></span>, <span class="application"><strong>libvirt</strong></span> and SELinux have put in place several checks to prevent this. (Normally, <span class="application"><strong>libvirt</strong></span> performs all of the tap device creation and manipulation, and passes an open file descriptor for the tap device to <span class="application"><strong>QEMU</strong></span>.)
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Reconfigure the host system to be compatible with the generic ethernet interface.
+ </div><div class="procedure"><h6>Procedure B.4. Reconfiguring the host system to use the generic ethernet interface</h6><ol class="1"><li class="step"><div class="para">
+ Set SELinux to permissive by configuring <code class="code">SELINUX=permissive</code> in <code class="filename">/etc/selinux/config</code>:
+ </div><pre class="screen"># This file controls the state of SELinux on the system.
+# SELINUX= can take one of these three values:
+# enforcing - SELinux security policy is enforced.
+# permissive - SELinux prints warnings instead of enforcing.
+# disabled - No SELinux policy is loaded.
+SELINUX=permissive
+# SELINUXTYPE= can take one of these two values:
+# targeted - Targeted processes are protected,
+# mls - Multi Level Security protection.
+SELINUXTYPE=targeted</pre></li><li class="step"><div class="para">
+ From a root shell, run the command <code class="command">setenforce permissive</code>.
+ </div></li><li class="step"><div class="para">
+ In <code class="filename">/etc/libvirt/qemu.conf</code> add or edit the following lines:
+ </div><pre class="screen">clear_emulator_capabilities = 0</pre><pre class="screen">user = "root"</pre><pre class="screen">group = "root"</pre><pre class="screen">cgroup_device_acl = [
+ "/dev/null", "/dev/full", "/dev/zero",
+ "/dev/random", "/dev/urandom",
+ "/dev/ptmx", "/dev/kvm", "/dev/kqemu",
+ "/dev/rtc", "/dev/hpet", "/dev/net/tun",</pre></li><li class="step"><div class="para">
+ Restart <code class="filename">libvirtd</code>.
+ </div></li></ol></div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Since each of these steps significantly decreases the host's security protections against <span class="application"><strong>QEMU</strong></span> guest domains, this configuration should only be used if there is no alternative to using <code class="code"><interface type='ethernet'></code>.
+ </div></div></div></dd></dl></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ For more information on SELinux, refer to the <em class="citetitle">Fedora Security Guide</em>.
+ </div></div></div></div><div xml:lang="en-US" class="section" id="App_Migration_Address" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.13. Migration fails with <code class="computeroutput">Error: unable to resolve address</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ <span class="application"><strong>QEMU</strong></span> guest migration fails and this error message appears:
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://192.168.122.12/system
+ error: Unable to resolve address <em class="replaceable"><code>name_of_host</code></em> service '49155': Name or service not known</pre><div class="para">
+ For example, if the destination hostname is "newyork", the error message will appear as:
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://192.168.122.12/system
+error: Unable to resolve address <em class="replaceable"><code>'newyork'</code></em> service '49155': Name or service not known</pre><div class="para">
+ However, this error looks strange as we did not use "newyork" hostname anywhere.
+ </div></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ During migration, <span class="application"><strong>libvirtd</strong></span> running on the destination host creates a URI from an address and port where it expects to receive migration data and sends it back to <span class="application"><strong>libvirtd</strong></span> running on the source host.
+ </div><div class="para">
+ In this case, the destination host (<code class="literal">192.168.122.12</code>) has its name set to <em class="replaceable"><code>'newyork'</code></em>. For some reason, <span class="application"><strong>libvirtd</strong></span> running on that host is unable to resolve the name to an IP address that could be sent back and still be useful. For this reason, it returned the <em class="replaceable"><code>'newyork'</code></em> hostname hoping the source <span class="application"><strong>libvirtd</strong></span> would be more successful with resolving the name. This can happen if DNS is not properly configured or <code class="filename">/etc/hosts</code> has the hostname associated with local loopback address (<code class="filename">127.0.0.1</code>).
+ </div><div class="para">
+ Note that the address used for migration data cannot be automatically determined from the address used for connecting to destination <span class="application"><strong>libvirtd</strong></span> (for example, from <code class="filename">qemu+tcp://192.168.122.12/system</code>). This is because to communicate with the destination <span class="application"><strong>libvirtd</strong></span>, the source <span class="application"><strong>libvirtd</strong></span> may need to use network infrastructure different from that which <span class="application"><strong>virsh</strong></span> (possibly running on a separate machine) requires.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ The best solution is to configure DNS correctly so that all hosts involved in migration are able to resolve all host names.
+ </div><div class="para">
+ If DNS cannot be configured to do this, a list of every host used for migration can be added manually to the <code class="filename">/etc/hosts</code> file on each of the hosts. However, it is difficult to keep such lists consistent in a dynamic environment.
+ </div><div class="para">
+ If the host names cannot be made resolvable by any means, <code class="command">virsh migrate</code> supports specifying the migration host:
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://192.168.122.12/system tcp://192.168.122.12</pre><div class="para">
+ Destination <span class="application"><strong>libvirtd</strong></span> will take the <code class="literal">tcp://192.168.122.12</code> URI and append an automatically generated port number. If this is not desirable (because of firewall configuration, for example), the port number can be specified in this command:
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://192.168.122.12/system tcp://192.168.122.12:12345</pre><div class="para">
+ Another option is to use tunnelled migration. Tunnelled migration does not create a separate connection for migration data, but instead tunnels the data through the connection used for communication with destination <span class="application"><strong>libvirtd</strong></span> (for example, <code class="filename">qemu+tcp://192.168.122.12/system</code>):
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://192.168.122.12/system --p2p --tunnelled</pre></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_Migration_Disk_Image" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.14. Migration fails with <code class="computeroutput">Unable to allow access for disk path: No such file or directory</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ A guest virtual machine (or domain) cannot be migrated because <span class="application"><strong>libvirt</strong></span> cannot access the disk image(s):
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://<em class="replaceable"><code>name_of_host</code></em>/system
+error: Unable to allow access for disk path /var/lib/libvirt/images/qemu.img: No such file or directory</pre><div class="para">
+ For example, if the destination hostname is "newyork", the error message will appear as:
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://<em class="replaceable"><code>newyork</code></em>/system
+error: Unable to allow access for disk path /var/lib/libvirt/images/qemu.img: No such file or directory</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ By default, migration only transfers the in-memory state of a running guest (such as memory or CPU state). Although disk images are not transferred during migration, they need to remain accessible at the same path by both hosts.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Set up and mount shared storage at the same location on both hosts. The simplest way to do this is to use NFS:
+ </div><div class="procedure"><h6>Procedure B.5. Setting up shared storage</h6><ol class="1"><li class="step"><div class="para">
+ Set up an NFS server on a host serving as shared storage. The NFS server can be one of the hosts involved in the migration, as long as all hosts involved are accessing the shared storage through NFS.
+ </div><pre class="screen"># mkdir -p /exports/images
+# cat >>/etc/exports <<EOF
+/exports/images 192.168.122.0/24(rw,no_root_squash)
+EOF</pre></li><li class="step"><div class="para">
+ Mount the exported directory at a common location on all hosts running <span class="application"><strong>libvirt</strong></span>. For example, if the IP address of the NFS server is 192.168.122.1, mount the directory with the following commands:
+ </div><pre class="screen"># cat >>/etc/fstab <<EOF
+192.168.122.1:/exports/images /var/lib/libvirt/images nfs auto 0 0
+EOF
+# mount /var/lib/libvirt/images</pre></li></ol></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ It is not possible to export a local directory from one host using NFS and mount it at the same path on another host — the directory used for storing disk images must be mounted from shared storage on both hosts. If this is not configured correctly, the guest virtual machine may lose access to its disk images during migration, because the source host's <span class="application"><strong>libvirt</strong></span> daemon may change the owner, permissions, and SELinux labels on the disk images after it successfully migrates the guest to its destination.
+ </div><div class="para">
+ If <span class="application"><strong>libvirt</strong></span> detects that the disk images are mounted from a shared storage location, it will not make these changes.
+ </div></div></div></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_No_Guest_Machines" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.15. No guest virtual machines are present when <span class="application"><strong>libvirtd</strong></span> is started</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The <span class="application"><strong>libvirt</strong></span> daemon is successfully started, but no guest virtual machines appear to be present.
+ </div><pre class="screen"># virsh list --all
+ Id Name State
+----------------------------------------------------
+#
+</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ There are various possible causes of this problem. Performing these tests will help to determine the cause of this situation:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Verify KVM kernel modules</span></dt><dd><div class="para">
+ Verify that KVM kernel modules are inserted in the kernel:
+ </div><pre class="screen"># lsmod | grep kvm
+kvm_intel 121346 0
+kvm 328927 1 kvm_intel</pre><div class="para">
+ If you are using an AMD machine, verify the <code class="systemitem">kvm_amd</code> kernel modules are inserted in the kernel instead, using the similar command <code class="command">lsmod | grep kvm_amd</code> in the root shell.
+ </div><div class="para">
+ If the modules are not present, insert them using the <code class="command">modprobe <em class="replaceable"><code><modulename></code></em></code> command.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Although it is uncommon, KVM virtualization support may be compiled into the kernel. In this case, modules are not needed.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">Verify virtualization extensions</span></dt><dd><div class="para">
+ Verify that virtualization extensions are supported and enabled on the host:
+ </div><pre class="screen"># egrep "(vmx|svm)" /proc/cpuinfo
+flags : fpu vme de pse tsc ... svm ... skinit wdt npt lbrv svm_lock nrip_save
+flags : fpu vme de pse tsc ... svm ... skinit wdt npt lbrv svm_lock nrip_save</pre><div class="para">
+ Enable virtualization extensions in your hardware's firmware configuration within the BIOS setup. Refer to your hardware documentation for further details on this.
+ </div></dd><dt class="varlistentry"><span class="term">Verify client URI configuration</span></dt><dd><div class="para">
+ Verify that the URI of the client is configured as desired:
+ </div><pre class="screen"># virsh uri
+vbox:///system</pre><div class="para">
+ For example, this message shows the URI is connected to the <span class="application"><strong>VirtualBox</strong></span> hypervisor, not <span class="application"><strong>QEMU</strong></span>, and reveals a configuration error for a URI that is otherwise set to connect to a <span class="application"><strong>QEMU</strong></span> hypervisor. If the URI was correctly connecting to <span class="application"><strong>QEMU</strong></span>, the same message would appear instead as:
+ </div><pre class="screen"># virsh uri
+qemu:///system</pre><div class="para">
+ This situation occurs when there are other hypervisors present, which <span class="application"><strong>libvirt</strong></span> may speak to by default.
+ </div></dd></dl></div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ After performing these tests, use the following command to view a list of guest virtual machines:
+ </div><pre class="screen"># virsh list --all</pre></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_TCP_Ports" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.16. Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ While <span class="application"><strong>libvirtd</strong></span> should listen on TCP ports for connections, the connections fail:
+ </div><pre class="screen"># virsh -c qemu+tcp://host/system
+error: unable to connect to server at 'host:16509': Connection refused
+error: failed to connect to the hypervisor</pre><div class="para">
+ The <span class="application"><strong>libvirt</strong></span> daemon is not listening on TCP ports even after changing configuration in <code class="filename">/etc/libvirt/libvirtd.conf</code>:
+ </div><pre class="screen"># grep listen_ /etc/libvirt/libvirtd.conf
+listen_tls = 1
+listen_tcp = 1
+listen_addr = "0.0.0.0"</pre><div class="para">
+ However, the TCP ports for <span class="application"><strong>libvirt</strong></span> are still not open after changing configuration:
+ </div><pre class="screen"># netstat -lntp | grep libvirtd
+#</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ The <span class="application"><strong>libvirt</strong></span> daemon was started without the <code class="option">--listen</code> option. Verify this by running this command:
+ </div><pre class="screen"># ps aux | grep libvirtd
+root 27314 0.0 0.0 1000920 18304 ? Sl Feb16 1:19 libvirtd --daemon</pre><div class="para">
+ The output does not contain the <code class="option">--listen</code> option.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Start the daemon with the <code class="option">--listen</code> option.
+ </div><div class="para">
+ To do this, modify the <code class="filename">/etc/sysconfig/libvirtd</code> file and uncomment the following line:
+ </div><pre class="screen">#LIBVIRTD_ARGS="--listen"</pre><div class="para">
+ Then restart the <span class="application"><strong>libvirtd</strong></span> service with this command:
+ </div><pre class="screen"># /etc/init.d/libvirtd restart</pre></dd></dl></div></div><div xml:lang="en-US" class="section" id="App_XML_Errors" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.17. Common XML errors</h2></div></div></div><div class="para">
+ The <span class="application"><strong>libvirt</strong></span> tool uses XML documents to store structured data. A variety of common errors occur with XML documents when they are passed to <span class="application"><strong>libvirt</strong></span> through the API. Several common XML errors — including misformatted XML, inappropriate values, and missing elements — are detailed below.
+ </div><div class="section" id="idm115560112"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm115560112">B.17.1. Editing domain definition</h3></div></div></div><div class="para">
+ Although it is not recommended, it is sometimes necessary to edit a guest virtual machine's (or a domain's) XML file manually. To access the guest's XML for editing, use the following command:
+ </div><pre class="screen"># virsh edit <em class="replaceable"><code>name_of_guest.xml</code></em></pre><div class="para">
+ This command opens the file in a text editor with the current definition of the guest virtual machine. After finishing the edits and saving the changes, the XML is reloaded and parsed by <span class="application"><strong>libvirt</strong></span>. If the XML is correct, the following message is displayed:
+ </div><pre class="screen"># virsh edit <em class="replaceable"><code>name_of_guest.xml</code></em>
+
+Domain <em class="replaceable"><code>name_of_guest.xml</code></em> XML configuration edited.</pre><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ When using the <code class="command">edit</code> command in <span class="application"><strong>virsh</strong></span> to edit an XML document, save all changes before exiting the editor.
+ </div></div></div><div class="para">
+ After saving the XML file, use the <code class="command">xmllint</code> command to validate that the XML is well-formed, or the <code class="command">virt-xml-validate</code> command to check for usage problems:
+ </div><pre class="screen"># xmllint --noout config.xml</pre><pre class="screen"># virt-xml-validate config.xml</pre><div class="para">
+ If no errors are returned, the XML description is well-formed and matches the <span class="application"><strong>libvirt</strong></span> schema. While the schema does not catch all constraints, fixing any reported errors will further troubleshooting.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">XML documents stored by <span class="application"><strong>libvirt</strong></span></span></dt><dd><div class="para">
+ These documents contain definitions of states and configurations for the guests. These documents are automatically generated and should not be edited manually. Errors in these documents contain the file name of the broken document. The file name is valid only on the host machine defined by the URI, which may refer to the machine the command was run on.
+ </div><div class="para">
+ Errors in files created by <span class="application"><strong>libvirt</strong></span> are rare. However, one possible source of these errors is a downgrade of <span class="application"><strong>libvirt</strong></span> — while newer versions of <span class="application"><strong>libvirt</strong></span> can always read XML generated by older versions, older versions of <span class="application"><strong>libvirt</strong></span> may be confused by XML elements added in a newer version.
+ </div></dd></dl></div></div><div class="section" id="idm117772112"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm117772112">B.17.2. XML syntax errors</h3></div></div></div><div class="para">
+ Syntax errors are caught by the XML parser. The error message contains information for identifying the problem.
+ </div><div class="para">
+ This example error message from the XML parser consists of three lines — the first line denotes the error message, and the two following lines contain the context and location of the XML code containing the error. The third line contains an indicator showing approximately where the error lies on the line above it:
+ </div><pre class="screen">error: (<em class="replaceable"><code>name_of_guest.xml</code></em>):6: StartTag: invalid element name
+<vcpu>2</vcpu><
+-----------------^</pre><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Information contained in this message:</span></dt><dd><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">(<em class="replaceable"><code>name_of_guest.xml</code></em>)</span></dt><dd><div class="para">
+ This is the file name of the document that contains the error. File names in parentheses are symbolic names to describe XML documents parsed from memory, and do not directly correspond to files on disk. File names that are not contained in parentheses are local files that reside on the target of the connection.
+ </div></dd><dt class="varlistentry"><span class="term">6</span></dt><dd><div class="para">
+ This is the line number in the XML file that contains the error.
+ </div></dd><dt class="varlistentry"><span class="term">StartTag: invalid element name </span></dt><dd><div class="para">
+ This is the error message from the <span class="application"><strong>libxml2</strong></span> parser, which describes the specific XML error.
+ </div></dd></dl></div></dd></dl></div><div class="section" id="idm65312304"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm65312304">B.17.2.1. Stray <code class="literal"><</code> in the document</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The following error occurs:
+ </div><pre class="screen">error: (<em class="replaceable"><code>name_of_guest.xml</code></em>):6: StartTag: invalid element name
+<vcpu>2</vcpu><
+-----------------^</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This error message shows that the parser expects a new element name after the <code class="literal"><</code> symbol on line 6 of a guest's XML file.
+ </div><div class="para">
+ Ensure line number display is enabled in your text editor. Open the XML file, and locate the text on line 6:
+ </div><pre class="screen"><domain type='kvm'>
+ <name><em class="replaceable"><code>name_of_guest</code></em></name>
+<memory>524288</memory>
+<vcpu>2</vcpu><
+</pre><div class="para">
+ This snippet of a guest's XML file contains an extra <code class="literal"><</code> in the document:
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Remove the extra <code class="literal"><</code> or finish the new element.
+ </div></dd></dl></div></div><div class="section" id="idm96690864"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm96690864">B.17.2.2. Unterminated attribute</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The following error occurs:
+ </div><pre class="screen">error: (<em class="replaceable"><code>name_of_guest.xml</code></em>):2: Unescaped '<' not allowed in attributes values
+<name><em class="replaceable"><code>name_of_guest</code></em></name>
+--^</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This snippet of a guest's XML file contains an unterminated element attribute value:
+ </div><pre class="screen"><domain type='kvm>
+<name><em class="replaceable"><code>name_of_guest</code></em></name></pre><div class="para">
+ In this case, <code class="literal">'kvm'</code> is missing a second quotation mark. Strings of attribute values, such as quotation marks and apostrophes, must be opened and closed, similar to XML start and end tags.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Correctly open and close all attribute value strings.
+ </div></dd></dl></div></div><div class="section" id="idm90942352"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm90942352">B.17.2.3. Opening and ending tag mismatch</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The following error occurs:
+ </div><pre class="screen">error: (<em class="replaceable"><code>name_of_guest.xml</code></em>):61: Opening and ending tag mismatch: clock line 16 and domain
+</domain>
+---------^</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ The error message above contains three clues to identify the offending tag:
+ </div><div class="para">
+ The message following the last colon, <code class="literal">clock line 16 and domain</code>, reveals that <code class="literal"><clock></code> contains a mismatched tag on line 16 of the document. The last hint is the pointer in the context part of the message, which identifies the second offending tag.
+ </div><div class="para">
+ Unpaired tags must be closed with <code class="literal">/></code>. The following snippet does not follow this rule and has produced the error message shown above:
+ </div><pre class="screen"><domain type='kvm'>
+ ...
+ <clock offset='utc'></pre><div class="para">
+ This error is caused by mismatched XML tags in the file. Every XML tag must have a matching start and end tag.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Other examples of mismatched XML tags</span></dt><dd><div class="para">
+ The following examples produce similar error messages and show variations of mismatched XML tags.
+ </div><div class="para">
+ This snippet contains an unended pair tag for <code class="literal"><features></code>:
+ </div><pre class="screen"><domain type='kvm'>
+ ...
+ <features>
+ <acpi/>
+ <pae/>
+ ...
+ </domain></pre><div class="para">
+ This snippet contains an end tag (<code class="literal"></name></code>) without a corresponding start tag:
+ </div><pre class="screen"><domain type='kvm'>
+ </name>
+ ...
+</domain></pre></dd></dl></div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Ensure all XML tags start and end correctly.
+ </div></dd></dl></div></div><div class="section" id="idm119405616"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm119405616">B.17.2.4. Typographical errors in tags</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The following error message appears:
+ </div><pre class="screen">error: (name_of_guest.xml):1: Specification mandate value for attribute ty
+<domain ty pe='kvm'>
+-----------^</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ XML errors are easily caused by a simple typographical error. This error message highlights the XML error — in this case, an extra white space within the word <code class="literal">type</code> — with a pointer.
+ </div><pre class="screen"><domain ty pe='kvm'></pre><div class="para">
+ These XML examples will not parse correctly because of typographical errors such as a missing special character, or an additional character:
+ </div><pre class="screen"><domain type 'kvm'></pre><pre class="screen"><dom#ain type='kvm'></pre></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ To identify the problematic tag, read the error message for the context of the file, and locate the error with the pointer. Correct the XML and save the changes.
+ </div></dd></dl></div></div></div><div class="section" id="idm115393088"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm115393088">B.17.3. Logic and configuration errors</h3></div></div></div><div class="para">
+ A well-formatted XML document can contain errors that are correct in syntax but <span class="application"><strong>libvirt</strong></span> cannot parse. Many of these errors exist, with two of the most common cases outlined below.
+ </div><div class="section" id="idm122199920"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm122199920">B.17.3.1. Vanishing parts</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ Parts of the change you have made do not show up and have no effect after editing or defining the domain. The <code class="command">define</code> or <code class="command">edit</code> command works, but when dumping the XML once again, the change disappears.
+ </div></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This error likely results from a broken construct or syntax that libvirt does not parse. The <span class="application"><strong>libvirt</strong></span> tool will generally only look for constructs it knows but ignore everything else, resulting in some of the XML changes vanishing after <span class="application"><strong>libvirt</strong></span> parses the input.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Validate the XML input before passing it to the <code class="command">edit</code> or <code class="command">define</code> commands. The <span class="application"><strong>libvirt</strong></span> developers maintain a set of XML schemas bundled with <span class="application"><strong>libvirt</strong></span> which define the majority of the constructs allowed in XML documents used by <span class="application"><strong>libvirt</strong></span>.
+ </div><div class="para">
+ Validate <span class="application"><strong>libvirt</strong></span> XML files using the following command:
+ </div><pre class="screen"># virt-xml-validate libvirt.xml</pre><div class="para">
+ If this command passes, <span class="application"><strong>libvirt</strong></span> will likely understand all constructs from your XML, except if the schemas cannot detect options which are valid only for a given hypervisor. Any XML generated by <span class="application"><strong>libvirt</strong></span> as a result of a <code class="command">virsh dump</code> command, for example, should validate without error.
+ </div></dd></dl></div></div><div class="section" id="idm99413056"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm99413056">B.17.3.2. Incorrect drive device type</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The definition of the source image for the CD-ROM virtual drive is not present, despite being added:
+ </div><pre class="screen"># virsh dumpxml domain
+<domain type='kvm'>
+ ...
+ <disk type='block' device='cdrom'>
+ <driver name='qemu' type='raw'/>
+ <target dev='hdc' bus='ide'/>
+ <readonly/>
+ </disk>
+ ...
+</domain></pre></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Correct the XML by adding the missing <code class="code"><source></code> parameter as follows:
+ </div><pre class="screen"><disk type='block' device='cdrom'>
+ <driver name='qemu' type='raw'/>
+ <source file='/path/to/image.iso'/>
+ <target dev='hdc' bus='ide'/>
+ <readonly/>
+</disk></pre><div class="para">
+ A <code class="code">type='block'</code> disk device expects that the source is a physical device. To use the disk with an image file, use <code class="code">type='file'</code> instead.
+ </div></dd></dl></div></div></div></div></div><div xml:lang="en-US" class="appendix" id="netkvm-parameters" lang="en-US"><div class="titlepage"><div><div><h1 class="title">NetKVM Driver Parameters</h1></div></div></div><div class="para">
+ After the NetKVM driver is installed, you can configure it to better suit your environment. The parameters listed in this section can be configured in the Windows <span class="guilabel"><strong>Device Manager</strong></span> (<code class="filename">devmgmt.msc</code>).
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Modifying the driver's parameters causes Windows to re-load that driver. This interrupts existing network activity.
+ </div></div></div><div class="procedure"><h6>Procedure C.1. Configuring NetKVM Parameters</h6><ol class="1"><li class="step"><p class="title"><strong>Open <span class="guilabel"><strong>Device Manager</strong></span></strong></p><div class="para">
+ Click on the <span class="guibutton"><strong>Start</strong></span> button. In the right-hand pane, right-click on <span class="guilabel"><strong>Computer</strong></span>, and click <span class="guilabel"><strong>Manage</strong></span>. If prompted, click <span class="guibutton"><strong>Continue</strong></span> on the <span class="guilabel"><strong>User Account Control</strong></span> window. This opens the <span class="guilabel"><strong>Computer Management</strong></span> window.
+ </div><div class="para">
+ In the left-hand pane of the <span class="guilabel"><strong>Computer Management</strong></span> window, click <span class="guilabel"><strong>Device Manager</strong></span>.
+ </div></li><li class="step"><p class="title"><strong>Locate the correct device</strong></p><div class="para">
+ In the central pane of the <span class="guilabel"><strong>Computer Management</strong></span> window, click on the <span class="guilabel"><strong>+</strong></span> symbol beside <span class="guilabel"><strong>Network adapters</strong></span>.
+ </div><div class="para">
+ Under the list of <span class="guilabel"><strong>Fedora VirtIO Ethernet Adapter</strong></span> devices, double-click on <span class="guilabel"><strong>NetKVM</strong></span>. This opens the <span class="guilabel"><strong>Properties</strong></span> window for that device.
+ </div></li><li class="step"><p class="title"><strong>View device parameters</strong></p><div class="para">
+ In the <span class="guilabel"><strong>Properties</strong></span> window, click on the <span class="guilabel"><strong>Advanced</strong></span> tab.
+ </div></li><li class="step"><p class="title"><strong>Modify device parameters</strong></p><div class="para">
+ Click on the parameter you wish to modify to display the options for that parameter.
+ </div><div class="para">
+ Modify the options as appropriate, then click on <span class="guibutton"><strong>OK</strong></span> to save your changes.
+ </div></li></ol></div><div class="section" id="idm107871952"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm107871952">C.1. Configurable parameters for NetKVM</h2></div></div></div><div class="variablelist"><h6>Logging parameters</h6><dl class="variablelist"><dt class="varlistentry"><span class="term">Logging.Enable</span></dt><dd><div class="para">
+ A Boolean value that determines whether logging is enabled. The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">Logging.Level</span></dt><dd><div class="para">
+ An integer that defines the logging level. As the integer increases, so does the verbosity of the log. The default value is <code class="literal">0</code> (errors only). <code class="literal">1-2</code> adds configuration messages. <code class="literal">3-4</code> adds packet flow information. <code class="literal">5-6</code> adds interrupt and DPC level trace information.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ High logging levels will slow down your guest virtual machine.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">Logging.Statistics(sec)</span></dt><dd><div class="para">
+ An integer that defines whether log statistics are printed, and the time in seconds between each periodical statistics printout. The default value is <code class="literal">0</code> (no logging statistics).
+ </div></dd></dl></div><div class="variablelist"><h6>Initial parameters</h6><dl class="variablelist"><dt class="varlistentry"><span class="term">Assign MAC</span></dt><dd><div class="para">
+ A string that defines the locally-administered MAC address for the para-virtualized NIC. This is not set by default.
+ </div></dd><dt class="varlistentry"><span class="term">Init.ConnectionRate(Mb)</span></dt><dd><div class="para">
+ An integer that represents the connection rate in megabytes. The default value for Windows 2008 and later is <code class="literal">10000</code>.
+ </div></dd><dt class="varlistentry"><span class="term">Init.Do802.1PQ</span></dt><dd><div class="para">
+ A Boolean value that enables Priority/VLAN tag population and removal support. The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">Init.UseMergedBuffers</span></dt><dd><div class="para">
+ A Boolean value that enables merge-able RX buffers. The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">Init.UsePublishEvents</span></dt><dd><div class="para">
+ A Boolean value that enables published event use. The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">Init.MTUSize</span></dt><dd><div class="para">
+ An integer that defines the maximum transmission unit (MTU). The default value is <code class="literal">1500</code>. Any value from 500 to 65500 is acceptable.
+ </div></dd><dt class="varlistentry"><span class="term">Init.IndirectTx</span></dt><dd><div class="para">
+ Controls whether indirect ring descriptors are in use. The default value is <code class="literal">Disable</code>, which disables use of indirect ring descriptors. Other valid values are <code class="literal">Enable</code>, which enables indirect ring descriptor usage; and <code class="literal">Enable*</code>, which enables conditional use of indirect ring descriptors.
+ </div></dd><dt class="varlistentry"><span class="term">Init.MaxTxBuffers</span></dt><dd><div class="para">
+ An integer that represents the amount of TX ring descriptors that will be allocated. The default value is <code class="literal">1024</code>. Valid values are: 16, 32, 64, 128, 256, 512, or 1024.
+ </div></dd><dt class="varlistentry"><span class="term">Init.MaxRxBuffers</span></dt><dd><div class="para">
+ An integer that represents the amount of RX ring descriptors that will be allocated. The default value is <code class="literal">256</code>. Valid values are: 16, 32, 64, 128, 256, 512, or 1024.
+ </div></dd><dt class="varlistentry"><span class="term">Offload.Tx.Checksum</span></dt><dd><div class="para">
+ Specifies the TX checksum offloading mode.
+ </div><div class="para">
+ In Fedora 18 and onward, the valid values for this parameter are <code class="literal">All</code> (the default), which enables IP, TCP and UDP checksum offloading for both IPv4 and IPv6; <code class="literal">TCP/UDP(v4,v6)</code>, which enables TCP and UDP checksum offloading for both IPv4 and IPv6; <code class="literal">TCP/UDP(v4)</code>, which enables TCP and UDP checksum offloading for IPv4 only; and <code class="literal">TCP(v4)</code>, which enables only TCP checksum offloading for IPv4 only.
+ </div><div class="para">
+ In Fedora 17 and earlier, the valid values for this parameter are <code class="literal">TCP/UDP</code> (the default value), which enables TCP and UDP checksum offload; <code class="literal">TCP</code>, which enables only TCP checksum offload; or <code class="literal">Disable</code>, which disables TX checksum offload.
+ </div></dd><dt class="varlistentry"><span class="term">Offload.Tx.LSO</span></dt><dd><div class="para">
+ A Boolean value that enables TX TCP Large Segment Offload (LSO). The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">Offload.Rx.Checksum</span></dt><dd><div class="para">
+ Specifies the RX checksum offloading mode.
+ </div><div class="para">
+ In Fedora 18 and onward, the valid values for this parameter are <code class="literal">All</code> (the default), which enables IP, TCP and UDP checksum offloading for both IPv4 and IPv6; <code class="literal">TCP/UDP(v4,v6)</code>, which enables TCP and UDP checksum offloading for both IPv4 and IPv6; <code class="literal">TCP/UDP(v4)</code>, which enables TCP and UDP checksum offloading for IPv4 only; and <code class="literal">TCP(v4)</code>, which enables only TCP checksum offloading for IPv4 only.
+ </div><div class="para">
+ In Fedora 17 and earlier, the valid values are <code class="literal">Disable</code> (the default), which disables RX checksum offloading; <code class="literal">All</code>, which enables TCP, UDP, and IP checksum offloading; <code class="literal">TCP/UDP</code>, which enables TCP and UDP checksum offloading; and <code class="literal">TCP</code>, which enables only TCP checksum offloading.
+ </div></dd></dl></div><div class="variablelist"><h6>Test and debug parameters</h6><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Test and debug parameters should only be used for testing or debugging; they should not be used in production.
+ </div></div></div><dl class="variablelist"><dt class="varlistentry"><span class="term">TestOnly.DelayConnect(ms)</span></dt><dd><div class="para">
+ The period for which to delay connection upon startup, in milliseconds. The default value is <code class="literal">0</code>.
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.DPCChecking</span></dt><dd><div class="para">
+ Sets the DPC checking mode. <code class="literal">0</code> (the default) disables DPC checking. <code class="literal">1</code> enables DPC checking; each hang test verifies DPC activity and acts as if the DPC was spawned. <code class="literal">2</code> clears the device interrupt status and is otherwise identical to <code class="literal">1</code>.
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.Scatter-Gather</span></dt><dd><div class="para">
+ A Boolean value that determines whether scatter-gather functionality is enabled. The default value is <code class="literal">1</code> (enabled). Setting this value to <code class="literal">0</code> disables scatter-gather functionality and all dependent capabilities.
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.InterruptRecovery</span></dt><dd><div class="para">
+ A Boolean value that determines whether interrupt recovery is enabled. The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.PacketFilter</span></dt><dd><div class="para">
+ A Boolean value that determines whether packet filtering is enabled. The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.BatchReceive</span></dt><dd><div class="para">
+ A Boolean value that determines whether packets are received in batches, or singularly. The default value is <code class="literal">1</code>, which enables batched packet receipt.
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.Promiscuous</span></dt><dd><div class="para">
+ A Boolean value that determines whether promiscuous mode is enabled. The default value is <code class="literal">0</code> (disabled).
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.AnalyzeIPPackets</span></dt><dd><div class="para">
+ A Boolean value that determines whether the checksum fields of outgoing IP packets are tested and verified for debugging purposes. The default value is <code class="literal">0</code> (no checking).
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.RXThrottle</span></dt><dd><div class="para">
+ An integer that determines the number of receive packets handled in a single DPC. The default value is <code class="literal">1000</code>.
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.UseSwTxChecksum</span></dt><dd><div class="para">
+ A Boolean value that determines whether hardware checksumming is enabled. The default value is <code class="literal">0</code> (disabled).
+ </div></dd></dl></div></div></div><div xml:lang="en-US" class="appendix" id="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist" lang="en-US"><div class="titlepage"><div><div><h1 class="title">qemu-kvm Whitelist</h1></div></div></div><div class="section" id="idm107978896"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm107978896">D.1. Introduction</h2></div></div></div><h4 id="idm82296432">Product identification</h4><div class="para">
+ Fedora
+ </div><h4 id="idm101008864">Objectives</h4><div class="para">
+ The primary objective of this whitelist is to provide a complete list of the supported options of the <code class="command">qemu-kvm</code> utility used as an emulator and a virtualizer in Fedora. This is a comprehensive summary of the supported options.
+ </div><h4 id="idm84977984">Background</h4><div class="para">
+ Fedora uses KVM as an underlying virtualization technology. The machine emulator and virtualizer used is a modified version of QEMU called qemu-kvm. This version does not support all configuration options of the original QEMU and it adds some additional options.
+ </div><h4 id="idm104371424">Scope of the chapter</h4><h4 id="idm76433216">Used format</h4><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong><name></strong></span> - When used in a syntax description, this string shoud be replaced by user-defined value.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>[a|b|c]</strong></span> - When used in a syntax description, only one of the strings separated by | is used.
+ </div></li><li class="listitem"><div class="para">
+ When no comment is present, an option is supported with all possible values.
+ </div></li></ul></div></div><div class="section" id="idm77975568"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm77975568">D.2. Basic options</h2></div></div></div><h4 id="idm118379584">Emulated machine</h4><div class="para">
+ <span class="application"><strong>-M</strong></span> <machine-type>
+ </div><h4 id="idm92804912">Processor type</h4><div class="para">
+ <span class="application"><strong>-cpu</strong></span> <model>[,<FEATURE>][...]
+ </div><div class="para">
+ We support exposing additional features and placing restrictions. Supported models are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>Opteron_G5</strong></span> - AMD Opteron 63xx class CPU
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Opteron_G4</strong></span> - AMD Opteron 62xx class CPU
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Opteron_G3</strong></span> - AMD Opteron 23xx (AMD Opteron Gen 3)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Opteron_G2</strong></span> - AMD Opteron 22xx (AMD Opteron Gen 2)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Opteron_G1</strong></span> - AMD Opteron 240 (AMD Opteron Gen 1)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Westmere</strong></span> - Westmere E56xx/L56xx/X56xx (Nehalem-C)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Haswell</strong></span> - Intel Core Processor (Haswell)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>SandyBridge</strong></span> - Intel Xeon E312xx (Sandy Bridge)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Nehalem</strong></span> - Intel Core i7 9xx (Nehalem Class Core i7)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Penryn</strong></span> - Intel Core 2 Duo P9xxx (Penryn Class Core 2)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Conroe</strong></span> - Intel Celeron_4x0 (Conroe/Merom Class Core 2)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>cpu64-rhel5</strong></span> - Red Hat Enterprise Linux 5 supported QEMU Virtual CPU version
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>cpu64-rhel6</strong></span> - Red Hat Enterprise Linux 6 supported QEMU Virtual CPU version
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>default</strong></span> - special option use default option from above.
+ </div></li></ul></div><h4 id="idm123230032">Processor Topology</h4><div class="para">
+ <span class="application"><strong>-smp</strong></span> <n>[,cores=<ncores>][,threads=<nthreads>][,sockets=<nsocks>][,maxcpus=<maxcpus>]
+ </div><div class="para">
+ Hypervisor and guest operating system limits on processor topology apply.
+ </div><h4 id="idm77173248">NUMA system</h4><div class="para">
+ <span class="application"><strong>-numa</strong></span> <nodes>[,mem=<size>][,cpus=<cpu[-cpu>]][,nodeid=<node>]
+ </div><div class="para">
+ Hypervisor and guest operating system limits on processor topology apply.
+ </div><h4 id="idm73755664">Memory size</h4><div class="para">
+ <span class="application"><strong>-m</strong></span> <megs>
+ </div><div class="para">
+ Supported values are limited by guest minimal and maximal values and hypervisor limits.
+ </div><h4 id="idm106871552">Keyboard layout</h4><div class="para">
+ <span class="application"><strong>-k</strong></span> <language>
+ </div><h4 id="idm104720608">Guest name</h4><div class="para">
+ <span class="application"><strong>-name</strong></span> <name>
+ </div><h4 id="idm104718976">Guest UUID</h4><div class="para">
+ <span class="application"><strong>-uuid</strong></span> <uuid>
+ </div></div><div class="section" id="idm77194320"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm77194320">D.3. Disk options</h2></div></div></div><h4 id="idm77193520">Generic drive</h4><div class="para">
+ <span class="application"><strong>-drive</strong></span> <option>[,<option>[,<option>[,...]]]
+ </div><div class="para">
+ Supported with the following options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>readonly</strong></span>[on|off]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>werror</strong></span>[enospc|report|stop|ignore]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>rerror</strong></span>[report|stop|ignore]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>id</strong></span>=<id>
+ </div><div class="para">
+ Id of the drive has the following limitaton for if=none:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ IDE disk has to have <id> in following format: drive-ide0-<BUS>-<UNIT>
+ </div><div class="para">
+ Example of correct format:
+ </div><div class="para">
+ -drive if=none,id=drive-ide0-<BUS>-<UNIT>,... -device ide-drive,drive=drive-ide0-<BUS>-<UNIT>,bus=ide.<BUS>,unit=<UNIT>
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>file</strong></span>=<file>
+ </div><div class="para">
+ Value of <file> is parsed with the following rules:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Passing floppy device as <file> is not supported.
+ </div></li><li class="listitem"><div class="para">
+ Passing cd-rom device as <file> is supported only with cdrom media type (media=cdrom) and only as IDE drive (either if=ide or if=none + -device ide-drive).
+ </div></li><li class="listitem"><div class="para">
+ If <file> is neither block nor character device, it must not contain ':'.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>if</strong></span>=<interface>
+ </div><div class="para">
+ The following interfaces are supported: none, ide, virtio, floppy.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>index</strong></span>=<index>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>media</strong></span>=<media>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>cache</strong></span>=<cache>
+ </div><div class="para">
+ Supported values: none, writeback or writethrough.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>copy-on-read</strong></span>=[on|off]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>snapshot</strong></span>=[yes|no]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>serial</strong></span>=<serial>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>aio</strong></span>=<aio>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>format</strong></span>=<format>
+ </div><div class="para">
+ This option is not required and can be omitted. However, this is not recommended for raw images because it represents security risk. Supported formats are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>qcow2</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>raw</strong></span>
+ </div></li></ul></div></li></ul></div><h4 id="idm98759680">Boot option</h4><div class="para">
+ <span class="application"><strong>-boot</strong></span> [order=<drives>][,menu=[on|off]]
+ </div><h4 id="idm98758080">Snapshot mode</h4><div class="para">
+ <span class="application"><strong>-snapshot</strong></span>
+ </div></div><div class="section" id="idm104274176"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm104274176">D.4. Display options</h2></div></div></div><h4 id="idm104273376">Disable graphics</h4><div class="para">
+ <span class="application"><strong>-nographic</strong></span>
+ </div><h4 id="idm125340800">VGA card emulation</h4><div class="para">
+ <span class="application"><strong>-vga</strong></span> <type>
+ </div><div class="para">
+ Supported types:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>cirrus</strong></span> - Cirrus Logic GD5446 Video card.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>std</strong></span> - Standard VGA card with Bochs VBE extensions.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>qxl</strong></span> - Spice paravirtual card.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>none</strong></span> - Disable VGA card.
+ </div></li></ul></div><h4 id="idm120185920">VNC display</h4><div class="para">
+ <span class="application"><strong>-vnc</strong></span> <display>[,<option>[,<option>[,...]]]
+ </div><div class="para">
+ Supported display value:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ [<host>]:<port>
+ </div></li><li class="listitem"><div class="para">
+ unix:<path>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>share</strong></span>[allow-exclusive|force-shared|ignore]
+ </div></li><li class="listitem"><div class="para">
+ none - Supported with no other options specified.
+ </div></li></ul></div><div class="para">
+ Supported options are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>to</strong></span>=<port>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>reverse</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>password</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>tls</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>x509</strong></span>=</path/to/certificate/dir> - Supported when <span class="application"><strong>tls</strong></span> specified.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>x509verify</strong></span>=</path/to/certificate/dir> - Supported when <span class="application"><strong>tls</strong></span> specified.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>sasl</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>acl</strong></span>
+ </div></li></ul></div><h4 id="idm101650112">Spice desktop</h4><div class="para">
+ <span class="application"><strong>-spice</strong></span> option[,option[,...]]
+ </div><div class="para">
+ Supported options are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>port</strong></span>=<number>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>addr</strong></span>=<addr>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>ipv4</strong></span>
+ </div><div class="para">
+ <span class="application"><strong>ipv6</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>password</strong></span>=<secret>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>disable-ticketing</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>disable-copy-paste</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>tls-port</strong></span>=<number>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>x509-dir</strong></span>=</path/to/certificate/dir>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>x509-key-file</strong></span>=<file>
+ </div><div class="para">
+ <span class="application"><strong>x509-key-password</strong></span>=<file>
+ </div><div class="para">
+ <span class="application"><strong>x509-cert-file</strong></span>=<file>
+ </div><div class="para">
+ <span class="application"><strong>x509-cacert-file</strong></span>=<file>
+ </div><div class="para">
+ <span class="application"><strong>x509-dh-key-file</strong></span>=<file>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>tls-cipher</strong></span>=<list>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>tls-channel</strong></span>[main|display|cursor|inputs|record|playback]
+ </div><div class="para">
+ <span class="application"><strong>plaintext-channel</strong></span>[main|display|cursor|inputs|record|playback]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>image-compression</strong></span>=<compress>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>jpeg-wan-compression</strong></span>=<value>
+ </div><div class="para">
+ <span class="application"><strong>zlib-glz-wan-compression</strong></span>=<value>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>streaming-video</strong></span>=[off|all|filter]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>agent-mouse</strong></span>=[on|off]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>playback-compression</strong></span>=[on|off]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>seamless-migratio</strong></span>=[on|off]
+ </div></li></ul></div></div><div class="section" id="idm114721584"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm114721584">D.5. Network options</h2></div></div></div><h4 id="idm114720784">TAP network</h4><div class="para">
+ <span class="application"><strong>-netdev tap</strong></span>,id=<id>][,<options>...]
+ </div><div class="para">
+ The following options are supported (all use name=value format):
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ ifname
+ </div></li><li class="listitem"><div class="para">
+ fd
+ </div></li><li class="listitem"><div class="para">
+ script
+ </div></li><li class="listitem"><div class="para">
+ downscript
+ </div></li><li class="listitem"><div class="para">
+ sndbuf
+ </div></li><li class="listitem"><div class="para">
+ vnet_hdr
+ </div></li><li class="listitem"><div class="para">
+ vhost
+ </div></li><li class="listitem"><div class="para">
+ vhostfd
+ </div></li><li class="listitem"><div class="para">
+ vhostforce
+ </div></li></ul></div></div><div class="section" id="idm93867376"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm93867376">D.6. Device options</h2></div></div></div><h4 id="idm93866576">General device</h4><div class="para">
+ <span class="application"><strong>-device</strong></span> <driver>[,<prop>[=<value>][,...]]
+ </div><div class="para">
+ All drivers support following properties
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ id
+ </div></li><li class="listitem"><div class="para">
+ bus
+ </div></li></ul></div><div class="para">
+ Following drivers are supported (with available properties):
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>pci-assign</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ host
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ configfd
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li><li class="listitem"><div class="para">
+ rombar
+ </div></li><li class="listitem"><div class="para">
+ romfile
+ </div></li><li class="listitem"><div class="para">
+ multifunction
+ </div></li></ul></div><div class="para">
+ If the device has multiple functions, all of them need to be assigned to the same guest.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>rtl8139</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ mac
+ </div></li><li class="listitem"><div class="para">
+ netdev
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>e1000</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ mac
+ </div></li><li class="listitem"><div class="para">
+ netdev
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>virtio-net-pci</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ ioeventfd
+ </div></li><li class="listitem"><div class="para">
+ vectors
+ </div></li><li class="listitem"><div class="para">
+ indirect
+ </div></li><li class="listitem"><div class="para">
+ event_idx
+ </div></li><li class="listitem"><div class="para">
+ csum
+ </div></li><li class="listitem"><div class="para">
+ guest_csum
+ </div></li><li class="listitem"><div class="para">
+ gso
+ </div></li><li class="listitem"><div class="para">
+ guest_tso4
+ </div></li><li class="listitem"><div class="para">
+ guest_tso6
+ </div></li><li class="listitem"><div class="para">
+ guest_ecn
+ </div></li><li class="listitem"><div class="para">
+ guest_ufo
+ </div></li><li class="listitem"><div class="para">
+ host_tso4
+ </div></li><li class="listitem"><div class="para">
+ host_tso6
+ </div></li><li class="listitem"><div class="para">
+ host_ecn
+ </div></li><li class="listitem"><div class="para">
+ host_ufo
+ </div></li><li class="listitem"><div class="para">
+ mrg_rxbuf
+ </div></li><li class="listitem"><div class="para">
+ status
+ </div></li><li class="listitem"><div class="para">
+ ctrl_vq
+ </div></li><li class="listitem"><div class="para">
+ ctrl_rx
+ </div></li><li class="listitem"><div class="para">
+ ctrl_vlan
+ </div></li><li class="listitem"><div class="para">
+ ctrl_rx_extra
+ </div></li><li class="listitem"><div class="para">
+ mac
+ </div></li><li class="listitem"><div class="para">
+ netdev
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ x-txtimer
+ </div></li><li class="listitem"><div class="para">
+ x-txburst
+ </div></li><li class="listitem"><div class="para">
+ tx
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>qxl</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ ram_size
+ </div></li><li class="listitem"><div class="para">
+ vram_size
+ </div></li><li class="listitem"><div class="para">
+ revision
+ </div></li><li class="listitem"><div class="para">
+ cmdlog
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>ide-drive</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ unit
+ </div></li><li class="listitem"><div class="para">
+ drive
+ </div></li><li class="listitem"><div class="para">
+ physical_block_size
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ ver
+ </div></li><li class="listitem"><div class="para">
+ wwn
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>virtio-blk-pci</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ class
+ </div></li><li class="listitem"><div class="para">
+ drive
+ </div></li><li class="listitem"><div class="para">
+ logical_block_size
+ </div></li><li class="listitem"><div class="para">
+ physical_block_size
+ </div></li><li class="listitem"><div class="para">
+ min_io_size
+ </div></li><li class="listitem"><div class="para">
+ opt_io_size
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ ioeventfd
+ </div></li><li class="listitem"><div class="para">
+ vectors
+ </div></li><li class="listitem"><div class="para">
+ indirect_desc
+ </div></li><li class="listitem"><div class="para">
+ event_idx
+ </div></li><li class="listitem"><div class="para">
+ scsi
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>isa-debugcon</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>isa-serial</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ index
+ </div></li><li class="listitem"><div class="para">
+ iobase
+ </div></li><li class="listitem"><div class="para">
+ irq
+ </div></li><li class="listitem"><div class="para">
+ chardev
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>virtserialport</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ nr
+ </div></li><li class="listitem"><div class="para">
+ chardev
+ </div></li><li class="listitem"><div class="para">
+ name
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>virtconsole</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ nr
+ </div></li><li class="listitem"><div class="para">
+ chardev
+ </div></li><li class="listitem"><div class="para">
+ name
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>virtio-serial-pci</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ vectors
+ </div></li><li class="listitem"><div class="para">
+ class
+ </div></li><li class="listitem"><div class="para">
+ indirect_desc
+ </div></li><li class="listitem"><div class="para">
+ event_idx
+ </div></li><li class="listitem"><div class="para">
+ max_ports
+ </div></li><li class="listitem"><div class="para">
+ flow_control
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>ES1370</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>AC97</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>intel-hda</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>hda-duplex</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ cad
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>hda-micro</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ cad
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>hda-output</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ cad
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>i6300esb</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>ib700</strong></span> - no properties
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>sga</strong></span> - no properties
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>virtio-balloon-pci</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ indirect_desc
+ </div></li><li class="listitem"><div class="para">
+ event_idx
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-tablet</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ migrate
+ </div></li><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-kbd</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ migrate
+ </div></li><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-mouse</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ migrate
+ </div></li><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-ccid</strong></span> - supported since 6.2
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ port
+ </div></li><li class="listitem"><div class="para">
+ slot
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-host</strong></span> - tech preview since 6.2
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ hostbus
+ </div></li><li class="listitem"><div class="para">
+ hostaddr
+ </div></li><li class="listitem"><div class="para">
+ hostport
+ </div></li><li class="listitem"><div class="para">
+ vendorid
+ </div></li><li class="listitem"><div class="para">
+ productid
+ </div></li><li class="listitem"><div class="para">
+ isobufs
+ </div></li><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-hub</strong></span> - supported since 6.2
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-ehci</strong></span> - tech preview since 6.2
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ freq
+ </div></li><li class="listitem"><div class="para">
+ maxframes
+ </div></li><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-storage</strong></span> - tech preview since 6.2
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ drive
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ serial
+ </div></li><li class="listitem"><div class="para">
+ removable
+ </div></li><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-redir</strong></span> - tech preview since 6.3
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ chardev
+ </div></li><li class="listitem"><div class="para">
+ filter
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>scsi-cd</strong></span> - tech preview for 6.3
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ drive
+ </div></li><li class="listitem"><div class="para">
+ logical_block_size
+ </div></li><li class="listitem"><div class="para">
+ physical_block_size
+ </div></li><li class="listitem"><div class="para">
+ min_io_size
+ </div></li><li class="listitem"><div class="para">
+ opt_io_size
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ ver
+ </div></li><li class="listitem"><div class="para">
+ serial
+ </div></li><li class="listitem"><div class="para">
+ scsi-id
+ </div></li><li class="listitem"><div class="para">
+ lun
+ </div></li><li class="listitem"><div class="para">
+ channel-scsi
+ </div></li><li class="listitem"><div class="para">
+ wwn
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>scsi-hd</strong></span> -tech preview for 6.3
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ drive
+ </div></li><li class="listitem"><div class="para">
+ logical_block_size
+ </div></li><li class="listitem"><div class="para">
+ physical_block_size
+ </div></li><li class="listitem"><div class="para">
+ min_io_size
+ </div></li><li class="listitem"><div class="para">
+ opt_io_size
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ ver
+ </div></li><li class="listitem"><div class="para">
+ serial
+ </div></li><li class="listitem"><div class="para">
+ scsi-id
+ </div></li><li class="listitem"><div class="para">
+ lun
+ </div></li><li class="listitem"><div class="para">
+ channel-scsi
+ </div></li><li class="listitem"><div class="para">
+ wwn
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>scsi-block</strong></span> -tech preview for 6.3
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ drive
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>scsi-disk</strong></span> -tech preview for 6.3
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ drive=drive
+ </div></li><li class="listitem"><div class="para">
+ logical_block_size
+ </div></li><li class="listitem"><div class="para">
+ physical_block_size
+ </div></li><li class="listitem"><div class="para">
+ min_io_size
+ </div></li><li class="listitem"><div class="para">
+ opt_io_size
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ ver
+ </div></li><li class="listitem"><div class="para">
+ serial
+ </div></li><li class="listitem"><div class="para">
+ scsi-id
+ </div></li><li class="listitem"><div class="para">
+ lun
+ </div></li><li class="listitem"><div class="para">
+ channel-scsi
+ </div></li><li class="listitem"><div class="para">
+ wwn
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>piix3-usb-uhci</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>piix4-usb-uhci</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>ccid-card-passthru</strong></span>
+ </div></li></ul></div><h4 id="idm118020480">Global device setting</h4><div class="para">
+ <span class="application"><strong>-global</strong></span> <device>.<property>=<value>
+ </div><div class="para">
+ Supported devices and properties as in "General device" section with these additional devices:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>isa-fdc</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ driveA
+ </div></li><li class="listitem"><div class="para">
+ driveB
+ </div></li><li class="listitem"><div class="para">
+ bootindexA
+ </div></li><li class="listitem"><div class="para">
+ bootindexB
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>qxl-vga</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ ram_size
+ </div></li><li class="listitem"><div class="para">
+ vram_size
+ </div></li><li class="listitem"><div class="para">
+ revision
+ </div></li><li class="listitem"><div class="para">
+ cmdlog
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li></ul></div><h4 id="idm108126176">Character device</h4><div class="para">
+ <span class="application"><strong>-chardev</strong></span> backend,id=<id>[,<options>]
+ </div><div class="para">
+ Supported backends are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>null</strong></span>,id=<id> - null device
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>socket</strong></span>,id=<id>,port=<port>[,host=<host>][,to=<to>][,ipv4][,ipv6][,nodelay][,server][,nowait][,telnet] - tcp socket
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>socket</strong></span>,id=<id>,path=<path>[,server][,nowait][,telnet] - unix socket
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>file</strong></span>,id=<id>,path=<path> - trafit to file.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>stdio</strong></span>,id=<id> - standard i/o
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>spicevmc</strong></span>,id=<id>,name=<name> - spice channel
+ </div></li></ul></div><h4 id="idm108295920">Enable USB</h4><div class="para">
+ <span class="application"><strong>-usb</strong></span>
+ </div></div><div class="section" id="idm89508384"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm89508384">D.7. Linux/Multiboot boot </h2></div></div></div><h4 id="idm89507584">Kernel file</h4><div class="para">
+ <span class="application"><strong>-kernel</strong></span> <bzImage>
+ </div><div class="para">
+ Note: multiboot images are not supported
+ </div><h4 id="idm85583440">Ram disk</h4><div class="para">
+ <span class="application"><strong>-initrd</strong></span> <file>
+ </div><h4 id="idm4967264">Command line parameter</h4><div class="para">
+ <span class="application"><strong>-append</strong></span> <cmdline>
+ </div></div><div class="section" id="idm97161328"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm97161328">D.8. Expert options</h2></div></div></div><h4 id="idm97160528">KVM virtualization</h4><div class="para">
+ <span class="application"><strong>-enable-kvm</strong></span>
+ </div><div class="para">
+ Qemu-kvm supports only KVM virtualization and it is used by default if available. If -enable-kvm is used and KVM is not available, qemu-kvm fails. However, if -enable-kvm is not used and KVM is not available, qemu-kvm runs in TCG mode, which is not supported.
+ </div><h4 id="idm88184848">Disable kernel mode PIT reinjection</h4><div class="para">
+ <span class="application"><strong>-no-kvm-pit-reinjection</strong></span>
+ </div><h4 id="idm98330640">No shutdown</h4><div class="para">
+ <span class="application"><strong>-no-shutdown</strong></span>
+ </div><h4 id="idm98329008">No reboot</h4><div class="para">
+ <span class="application"><strong>-no-reboot</strong></span>
+ </div><h4 id="idm85540320">Serial port, monitor, QMP</h4><div class="para">
+ <span class="application"><strong>-serial</strong></span> <dev>
+ </div><div class="para">
+ <span class="application"><strong>-monitor</strong></span> <dev>
+ </div><div class="para">
+ <span class="application"><strong>-qmp</strong></span> <dev>
+ </div><div class="para">
+ Supported devices are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>stdio</strong></span> - standard input/output
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>null</strong></span> - null device
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>file</strong></span>:<filename> - output to file.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>tcp</strong></span>:[<host>]:<port>[,server][,nowait][,nodelay] - TCP Net console.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>unix</strong></span>:<path>[,server][,nowait] - Unix domain socket.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>mon</strong></span>:<dev_string> - Any device above, used to multiplex monitor too.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>none</strong></span> - disable, valid only for -serial.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>chardev</strong></span>:<id> - character device created with -chardev.
+ </div></li></ul></div><h4 id="idm90329184">Monitor redirect</h4><div class="para">
+ <span class="application"><strong>-mon</strong></span> <chardev_id>[,mode=[readline|control]][,default=[on|off]]
+ </div><h4 id="idm88182096">Manual CPU start</h4><div class="para">
+ <span class="application"><strong>-S</strong></span>
+ </div><h4 id="idm111510528">RTC</h4><div class="para">
+ <span class="application"><strong>-rtc</strong></span> [base=utc|localtime|date][,clock=host|vm][,driftfix=none|slew]
+ </div><h4 id="idm111508928">Watchdog</h4><div class="para">
+ <span class="application"><strong>-watchdog</strong></span> model
+ </div><h4 id="idm93247712">Watchdog reaction</h4><div class="para">
+ <span class="application"><strong>-watchdog-action</strong></span> <action>
+ </div><h4 id="idm2176944">Guest memory backing</h4><div class="para">
+ <span class="application"><strong>-mem-prealloc</strong></span> <span class="application"><strong>-mem-path</strong></span> /dev/hugepages
+ </div><h4 id="idm77999776">SMBIOS entry</h4><div class="para">
+ <span class="application"><strong>-smbios</strong></span> type=0[,vendor=<str>][,<version=str>][,date=<str>][,release=%d.%d]
+ </div><div class="para">
+ <span class="application"><strong>-smbios</strong></span> type=1[,manufacturer=<str>][,product=<str>][,version=<str>][,serial=<str>][,uuid=<uuid>][,sku=<str>][,family=<str>]
+ </div></div><div class="section" id="idm79818416"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm79818416">D.9. Help and information options</h2></div></div></div><h4 id="idm79817648">Help</h4><div class="para">
+ <span class="application"><strong>-h</strong></span>
+ </div><div class="para">
+ <span class="application"><strong>-help</strong></span>
+ </div><h4 id="idm99659504">Version</h4><div class="para">
+ <span class="application"><strong>-version</strong></span>
+ </div><h4 id="idm99740336">Audio help</h4><div class="para">
+ <span class="application"><strong>-audio-help</strong></span>
+ </div></div><div class="section" id="idm99738544"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm99738544">D.10. Miscellaneous options</h2></div></div></div><h4 id="idm98815568">Migration</h4><div class="para">
+ <span class="application"><strong>-incoming</strong></span>
+ </div><h4 id="idm98813936">No default configuration</h4><div class="para">
+ <span class="application"><strong>-nodefconfig</strong></span>
+ </div><div class="para">
+ <span class="application"><strong>-nodefaults</strong></span>
+ </div><div class="para">
+ Running without -nodefaults is not supported
+ </div><h4 id="idm95244912">Device configuration file</h4><div class="para">
+ <span class="application"><strong>-readconfig</strong></span> <file>
+ </div><div class="para">
+ <span class="application"><strong>-writeconfig</strong></span> <file>
+ </div><h4 id="idm92594016">Loaded saved state</h4><div class="para">
+ <span class="application"><strong>-loadvm</strong></span> <file>
+ </div></div></div><div xml:lang="en-US" class="appendix" id="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Managing guests with virsh</h1></div></div></div><div class="para">
+ <code class="command">virsh</code> is a command line interface tool for managing guests and the hypervisor. The <code class="command">virsh</code> command-line tool is built on the <code class="command">libvirt</code> management API and operates as an alternative to the <code class="command">qemu-kvm</code> command and the graphical <code class="command">virt-manager</code> application. The <code class="command">virsh</code> command can be used in read-only mode by unprivileged users or, with root access, full administration functionality. The <code class="command">virsh</code> command is ideal for scripting virtualization administration.
+ </div><div class="section" id="idm93487200"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm93487200">E.1. virsh command quick reference</h2></div></div></div><div class="para">
+ The following tables provide a quick reference for all virsh command line options.
+ </div><div class="table" id="tabl-Virtualization-Managing_guests_with_virsh-Guest_management_commands"><h6>Table E.1. Guest management commands</h6><div class="table-contents"><table summary="Guest management commands" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">help</code>
+ </td><td class="">
+ Prints basic help information.
+ </td></tr><tr><td class="">
+ <code class="command">list</code>
+ </td><td class="">
+ Lists all guests.
+ </td></tr><tr><td class="">
+ <code class="command">dumpxml</code>
+ </td><td class="">
+ Outputs the XML configuration file for the guest.
+ </td></tr><tr><td class="">
+ <code class="command">create</code>
+ </td><td class="">
+ Creates a guest from an XML configuration file and starts the new guest.
+ </td></tr><tr><td class="">
+ <code class="command">start</code>
+ </td><td class="">
+ Starts an inactive guest.
+ </td></tr><tr><td class="">
+ <code class="command">destroy</code>
+ </td><td class="">
+ Forces a guest to stop.
+ </td></tr><tr><td class="">
+ <code class="command">define</code>
+ </td><td class="">
+ Creates a guest from an XML configuration file without starting the new guest.
+ </td></tr><tr><td class="">
+ <code class="command">domid</code>
+ </td><td class="">
+ Displays the guest's ID.
+ </td></tr><tr><td class="">
+ <code class="command">domuuid</code>
+ </td><td class="">
+ Displays the guest's UUID.
+ </td></tr><tr><td class="">
+ <code class="command">dominfo</code>
+ </td><td class="">
+ Displays guest information.
+ </td></tr><tr><td class="">
+ <code class="command">domname</code>
+ </td><td class="">
+ Displays the guest's name.
+ </td></tr><tr><td class="">
+ <code class="command">domstate</code>
+ </td><td class="">
+ Displays the state of a guest.
+ </td></tr><tr><td class="">
+ <code class="command">quit</code>
+ </td><td class="">
+ Quits the interactive terminal.
+ </td></tr><tr><td class="">
+ <code class="command">reboot</code>
+ </td><td class="">
+ Reboots a guest.
+ </td></tr><tr><td class="">
+ <code class="command">restore</code>
+ </td><td class="">
+ Restores a previously saved guest stored in a file.
+ </td></tr><tr><td class="">
+ <code class="command">resume</code>
+ </td><td class="">
+ Resumes a paused guest.
+ </td></tr><tr><td class="">
+ <code class="command">save</code>
+ </td><td class="">
+ Saves the present state of a guest to a file.
+ </td></tr><tr><td class="">
+ <code class="command">shutdown</code>
+ </td><td class="">
+ Gracefully shuts down a guest.
+ </td></tr><tr><td class="">
+ <code class="command">suspend</code>
+ </td><td class="">
+ Pauses a guest.
+ </td></tr><tr><td class="">
+ <code class="command">undefine</code>
+ </td><td class="">
+ Deletes all files associated with a guest.
+ </td></tr><tr><td class="">
+ <code class="command">migrate</code>
+ </td><td class="">
+ Migrates a guest to another host.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The following <code class="command">virsh</code> command options manage guest and hypervisor resources:
+ </div><div class="table" id="tabl-Virtualization-Managing_guests_with_virsh-Resource_management_options"><h6>Table E.2. Resource management options</h6><div class="table-contents"><table summary="Resource management options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">setmem</code>
+ </td><td class="">
+ Sets the allocated memory for a guest. Refer to the <code class="command">virsh</code> manpage for more details.
+ </td></tr><tr><td class="">
+ <code class="command">setmaxmem</code>
+ </td><td class="">
+ Sets maximum memory limit for the hypervisor. Refer to the <code class="command">virsh</code> manpage for more details.
+ </td></tr><tr><td class="">
+ <code class="command">setvcpus</code>
+ </td><td class="">
+ Changes number of virtual CPUs assigned to a guest. Refer to the <code class="command">virsh</code> manpage for more details.
+ </td></tr><tr><td class="">
+ <code class="command">vcpuinfo</code>
+ </td><td class="">
+ Displays virtual CPU information about a guest.
+ </td></tr><tr><td class="">
+ <code class="command">vcpupin</code>
+ </td><td class="">
+ Controls the virtual CPU affinity of a guest.
+ </td></tr><tr><td class="">
+ <code class="command">domblkstat</code>
+ </td><td class="">
+ Displays block device statistics for a running guest.
+ </td></tr><tr><td class="">
+ <code class="command">domifstat</code>
+ </td><td class="">
+ Displays network interface statistics for a running guest.
+ </td></tr><tr><td class="">
+ <code class="command">attach-device</code>
+ </td><td class="">
+ Attach a device to a guest, using a device definition in an XML file.
+ </td></tr><tr><td class="">
+ <code class="command">attach-disk</code>
+ </td><td class="">
+ Attaches a new disk device to a guest.
+ </td></tr><tr><td class="">
+ <code class="command">attach-interface</code>
+ </td><td class="">
+ Attaches a new network interface to a guest.
+ </td></tr><tr><td class="">
+ <code class="command">update-device</code>
+ </td><td class="">
+ Detaches a disk image from a guest's CD-ROM drive. See <a class="xref" href="#sect-Attaching_and_updating_a_device_with_virsh">Section E.2, “Attaching and updating a device with virsh”</a> for more details.
+ </td></tr><tr><td class="">
+ <code class="command">detach-device</code>
+ </td><td class="">
+ Detaches a device from a guest, takes the same kind of XML descriptions as command <code class="command">attach-device</code>.
+ </td></tr><tr><td class="">
+ <code class="command">detach-disk</code>
+ </td><td class="">
+ Detaches a disk device from a guest.
+ </td></tr><tr><td class="">
+ <code class="command">detach-interface</code>
+ </td><td class="">
+ Detach a network interface from a guest.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The <code class="command">virsh</code> commands for managing and creating storage pools and volumes.
+ </div><div class="para">
+ For more information on using storage pools with virsh, refer to <a href="http://libvirt.org/formatstorage.html">http://libvirt.org/formatstorage.html</a>
+ </div><div class="table" id="tabl-Virtualization-Managing_gunagement_options"><h6>Table E.3. Storage Pool options</h6><div class="table-contents"><table summary="Storage Pool options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">find-storage-pool-sources</code>
+ </td><td class="">
+ Returns the XML definition for all storage pools of a given type that could be found.
+ </td></tr><tr><td class="">
+ <code class="command">find-storage-pool-sources</code> <em class="parameter"><code>host port</code></em>
+ </td><td class="">
+ Returns data on all storage pools of a given type that could be found as XML. If the host and port are provided, this command can be run remotely.
+ </td></tr><tr><td class="">
+ <code class="command">pool-autostart </code>
+ </td><td class="">
+ Sets the storage pool to start at boot time.
+ </td></tr><tr><td class="">
+ <code class="command">pool-build</code>
+ </td><td class="">
+ The <code class="command">pool-build</code> command builds a defined pool. This command can format disks and create partitions.
+ </td></tr><tr><td class="">
+ <code class="command">pool-create</code>
+ </td><td class="">
+ <code class="command">pool-create</code> creates and starts a storage pool from the provided XML storage pool definition file.
+ </td></tr><tr><td class="">
+ <code class="command">pool-create-as name</code>
+ </td><td class="">
+ Creates and starts a storage pool from the provided parameters. If the <em class="parameter"><code>--print-xml</code></em> parameter is specified, the command prints the XML definition for the storage pool without creating the storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-define</code>
+ </td><td class="">
+ Creates a storage bool from an XML definition file but does not start the new storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-define-as name</code>
+ </td><td class="">
+ Creates but does not start, a storage pool from the provided parameters. If the <em class="parameter"><code>--print-xml</code></em> parameter is specified, the command prints the XML definition for the storage pool without creating the storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-destroy</code>
+ </td><td class="">
+ Permanently destroys a storage pool in <code class="command">libvirt</code>. The raw data contained in the storage pool is not changed and can be recovered with the <code class="command">pool-create</code> command.
+ </td></tr><tr><td class="">
+ <code class="command">pool-delete</code>
+ </td><td class="">
+ Destroys the storage resources used by a storage pool. This operation cannot be recovered. The storage pool still exists after this command but all data is deleted.
+ </td></tr><tr><td class="">
+ <code class="command">pool-dumpxml</code>
+ </td><td class="">
+ Prints the XML definition for a storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-edit</code>
+ </td><td class="">
+ Opens the XML definition file for a storage pool in the users default text editor.
+ </td></tr><tr><td class="">
+ <code class="command">pool-info</code>
+ </td><td class="">
+ Returns information about a storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-list</code>
+ </td><td class="">
+ Lists storage pools known to libvirt. By default, <code class="command">pool-list</code> lists pools in use by active guests. The <em class="parameter"><code>--inactive</code></em> parameter lists inactive pools and the <em class="parameter"><code>--all</code></em> parameter lists all pools.
+ </td></tr><tr><td class="">
+ <code class="command">pool-undefine</code>
+ </td><td class="">
+ Deletes the definition for an inactive storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-uuid</code>
+ </td><td class="">
+ Returns the UUID of the named pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-name </code>
+ </td><td class="">
+ Prints a storage pool's name when provided the UUID of a storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-refresh</code>
+ </td><td class="">
+ Refreshes the list of volumes contained in a storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-start</code>
+ </td><td class="">
+ Starts a storage pool that is defined but inactive.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><h6>Table E.4. Volume options</h6><div class="table-contents"><table summary="Volume options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">vol-create</code>
+ </td><td class="">
+ Create a volume from an XML file.
+ </td></tr><tr><td class="">
+ <code class="command">vol-create-from</code>
+ </td><td class="">
+ Create a volume using another volume as input.
+ </td></tr><tr><td class="">
+ <code class="command">vol-create-as</code>
+ </td><td class="">
+ Create a volume from a set of arguments.
+ </td></tr><tr><td class="">
+ <code class="command">vol-clone</code>
+ </td><td class="">
+ Clone a volume.
+ </td></tr><tr><td class="">
+ <code class="command">vol-delete</code>
+ </td><td class="">
+ Delete a volume.
+ </td></tr><tr><td class="">
+ <code class="command">vol-wipe</code>
+ </td><td class="">
+ Wipe a volume.
+ </td></tr><tr><td class="">
+ <code class="command">vol-dumpxml</code>
+ </td><td class="">
+ Show volume information in XML.
+ </td></tr><tr><td class="">
+ <code class="command">vol-info</code>
+ </td><td class="">
+ Show storage volume information.
+ </td></tr><tr><td class="">
+ <code class="command">vol-list</code>
+ </td><td class="">
+ List volumes.
+ </td></tr><tr><td class="">
+ <code class="command">vol-pool</code>
+ </td><td class="">
+ Returns the storage pool for a given volume key or path.
+ </td></tr><tr><td class="">
+ <code class="command">vol-path</code>
+ </td><td class="">
+ Returns the volume path for a given volume name or key.
+ </td></tr><tr><td class="">
+ <code class="command">vol-name</code>
+ </td><td class="">
+ Returns the volume name for a given volume key or path.
+ </td></tr><tr><td class="">
+ <code class="command">vol-key</code>
+ </td><td class="">
+ Returns the volume key for a given volume name or path.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><h6>Table E.5. Secret options</h6><div class="table-contents"><table summary="Secret options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">secret-define</code>
+ </td><td class="">
+ Define or modify a secret from an XML file.
+ </td></tr><tr><td class="">
+ <code class="command">secret-dumpxml</code>
+ </td><td class="">
+ Show secret attributes in XML.
+ </td></tr><tr><td class="">
+ <code class="command">secret-set-value</code>
+ </td><td class="">
+ Set a secret value.
+ </td></tr><tr><td class="">
+ <code class="command">secret-get-value</code>
+ </td><td class="">
+ Output a secret value.
+ </td></tr><tr><td class="">
+ <code class="command">secret-undefine</code>
+ </td><td class="">
+ Undefine a secret.
+ </td></tr><tr><td class="">
+ <code class="command">secret-list</code>
+ </td><td class="">
+ List secrets.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><h6>Table E.6. Network filter options</h6><div class="table-contents"><table summary="Network filter options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">nwfilter-define</code>
+ </td><td class="">
+ Define or update a network filter from an XML file.
+ </td></tr><tr><td class="">
+ <code class="command">nwfilter-undefine</code>
+ </td><td class="">
+ Undefine a network filter.
+ </td></tr><tr><td class="">
+ <code class="command">nwfilter-dumpxml</code>
+ </td><td class="">
+ Show network filter information in XML.
+ </td></tr><tr><td class="">
+ <code class="command">nwfilter-list</code>
+ </td><td class="">
+ List network filters.
+ </td></tr><tr><td class="">
+ <code class="command">nwfilter-edit</code>
+ </td><td class="">
+ Edit XML configuration for a network filter.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ This table contains <code class="command">virsh</code> command options for snapshots:
+ </div><div class="table"><h6>Table E.7. Snapshot options</h6><div class="table-contents"><table summary="Snapshot options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">snapshot-create</code>
+ </td><td class="">
+ Create a snapshot.
+ </td></tr><tr><td class="">
+ <code class="command">snapshot-current</code>
+ </td><td class="">
+ Get the current snapshot.
+ </td></tr><tr><td class="">
+ <code class="command">snapshot-delete</code>
+ </td><td class="">
+ Delete a domain snapshot.
+ </td></tr><tr><td class="">
+ <code class="command">snapshot-dumpxml</code>
+ </td><td class="">
+ Dump XML for a domain snapshot.
+ </td></tr><tr><td class="">
+ <code class="command">snapshot-list</code>
+ </td><td class="">
+ List snapshots for a domain.
+ </td></tr><tr><td class="">
+ <code class="command">snapshot-revert</code>
+ </td><td class="">
+ Revert a domain to a snapshot.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ This table contains miscellaneous <code class="command">virsh</code> commands:
+ </div><div class="table" id="tabl-Virtualization-Managing_guests_with_virsh-Miscellaneous_options"><h6>Table E.8. Miscellaneous options</h6><div class="table-contents"><table summary="Miscellaneous options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">version</code>
+ </td><td class="">
+ Displays the version of <code class="command">virsh</code>.
+ </td></tr><tr><td class="">
+ <code class="command">nodeinfo</code>
+ </td><td class="">
+ Outputs information about the hypervisor.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sect-Attaching_and_updating_a_device_with_virsh"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">E.2. Attaching and updating a device with virsh</h2></div></div></div><div class="para">
+ For information on this procedure refer to <a class="xref" href="#sect-Virtualization-Adding_storage_devices_to_guests-Adding_file_based_storage_to_a_guest">Section 28.3.1, “Adding file based storage to a guest”</a>
+ </div></div><div class="section" id="sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">E.3. Connecting to the hypervisor</h2></div></div></div><div class="para">
+ Connect to a hypervisor session with <code class="command">virsh</code>:
+ </div><pre class="screen"># virsh connect <em class="parameter"><code>{name}</code></em></pre><div class="para">
+ Where <em class="parameter"><code>{name}</code></em> is the machine name (hostname) or URL (the output of the <code class="command">virsh uri</code> command) of the hypervisor. To initiate a read-only connection, append the above command with <code class="command">--readonly</code>.
+ </div></div><div class="section" id="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">E.4. Creating a virtual machine XML dump (configuration file)</h2></div></div></div><div class="para">
+ Output a guest's XML configuration file with <code class="command">virsh</code>:
+ </div><pre class="screen"># virsh dumpxml <em class="parameter"><code>{guest-id, guestname or 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>:
+ </div><pre class="screen"># virsh dumpxml <em class="replaceable"><code>GuestID</code></em> > <em class="replaceable"><code>guest.xml</code></em></pre><div class="para">
+ This file <code class="filename">guest.xml</code> can recreate the guest (refer to <a class="xref" href="#form-Virtualization-Managing_guests_with_virsh-Editing_a_guests_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.
+ </div><div class="para">
+ An example of <code class="command">virsh dumpxml</code> output:
+ </div><pre class="screen"># virsh dumpxml guest1-rhel6-64
+<domain type='kvm'>
+ <name>guest1-rhel6-64</name>
+ <uuid>b8d7388a-bbf2-db3a-e962-b97ca6e514bd</uuid>
+ <memory>2097152</memory>
+ <currentMemory>2097152</currentMemory>
+ <vcpu>2</vcpu>
+ <os>
+ <type arch='x86_64' machine='rhel6.2.0'>hvm</type>
+ <boot dev='hd'/>
+ </os>
+ <features>
+ <acpi/>
+ <apic/>
+ <pae/>
+ </features>
+ <clock offset='utc'/>
+ <on_poweroff>destroy</on_poweroff>
+ <on_reboot>restart</on_reboot>
+ <on_crash>restart</on_crash>
+ <devices>
+ <emulator>/usr/libexec/qemu-kvm</emulator>
+ <disk type='file' device='disk'>
+ <driver name='qemu' type='raw' cache='none' io='threads'/>
+ <source file='/home/guest-images/guest1-rhel6-64.img'/>
+ <target dev='vda' bus='virtio'/>
+ <shareable/<
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
+ </disk>
+ <interface type='bridge'>
+ <mac address='52:54:00:b9:35:a9'/>
+ <source bridge='br0'/>
+ <model type='virtio'/>
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
+ </interface>
+ <serial type='pty'>
+ <target port='0'/>
+ </serial>
+ <console type='pty'>
+ <target type='serial' port='0'/>
+ </console>
+ <input type='tablet' bus='usb'/>
+ <input type='mouse' bus='ps2'/>
+ <graphics type='vnc' port='-1' autoport='yes'/>
+ <sound model='ich6'>
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
+ </sound>
+ <video>
+ <model type='cirrus' vram='9216' heads='1'/>
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
+ </video>
+ <memballoon model='virtio'>
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
+ </memballoon>
+ </devices>
+</domain>
+
+
+</pre><div class="para">
+ Note that the <shareable/> flag is set. This indicates the device is expected to be shared between domains (assuming the hypervisor and OS support this), which means that caching should be deactivated for that device.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Creating_a_guest_from_a_configuration_file"><h5 class="formalpara">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="#form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file">Section E.4, “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" id="form-Virtualization-Managing_guests_with_virsh-Editing_a_guests_configuration_file"><h5 class="formalpara">Editing a guest's configuration file</h5>
+ Instead of using the <code class="command">dumpxml</code> option (refer to <a class="xref" href="#form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file">Section E.4, “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="section" id="sect-multifunction-pci-install"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.4.1. Adding multifunction PCI devices to KVM guests</h3></div></div></div><div class="para">
+ This section will demonstrate how to add multi-function PCI devices to KVM guests.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Run the <code class="command">virsh edit <em class="replaceable"><code>[guestname]</code></em></code> command to edit the XML configuration file for the guest.
+ </div></li><li class="step"><div class="para">
+ In the address type tag, add a <code class="command">multifunction='on'</code> entry for <code class="command">function='0x0'</code>.
+ </div><div class="para">
+ This enables the guest to use the multifunction PCI devices.
+ </div><pre class="screen">
+<disk type='file' device='disk'>
+<driver name='qemu' type='raw' cache='none'/>
+<source file='/var/lib/libvirt/images/rhel62-1.img'/>
+<target dev='vda' bus='virtio'/>
+<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0' multifunction='on'/
+</disk>
+</pre><div class="para">
+ For a PCI device with two functions, amend the XML configuration file to include a second device with the same slot number as the first device and a different function number, such as <code class="command">function='0x1'</code>.
+ </div><div class="para">
+ For Example:
+ </div><pre class="screen">
+<disk type='file' device='disk'>
+<driver name='qemu' type='raw' cache='none'/>
+<source file='/var/lib/libvirt/images/rhel62-1.img'/>
+<target dev='vda' bus='virtio'/>
+<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0' multifunction='on'/>
+</disk>
+<disk type='file' device='disk'>
+<driver name='qemu' type='raw' cache='none'/>
+<source file='/var/lib/libvirt/images/rhel62-2.img'/>
+<target dev='vdb' bus='virtio'/>
+<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x1'/>
+</disk>
+</pre></li><li class="step"><div class="para">
+ <code class="command">lspci</code> output from the KVM guest shows:
+ </div><pre class="screen">
+$ lspci
+
+00:05.0 SCSI storage controller: Fedora, Inc Virtio block device
+00:05.1 SCSI storage controller: Fedora, Inc Virtio block device
+</pre></li></ol></div></div></div><div class="section" id="idm115600896"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm115600896">E.5. Suspending, resuming, saving and restoring a guest</h2></div></div></div><div class="formalpara"><h5 class="formalpara" id="idm86139552">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="#form-Virtualization-Managing_guests_with_virsh-Resuming_a_guest">Resuming a guest</a>) option.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Resuming_a_guest"><h5 class="formalpara">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" id="form-Virtualization-Managing_guests_with_virsh-Save_a_guest"><h5 class="formalpara">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="#form-Virtualization-Managing_guests_with_virsh-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" id="form-Virtualization-Managing_guests_with_virsh-Restore_a_guest"><h5 class="formalpara">Restore a guest</h5>
+ Restore a guest previously saved with the <code class="command">virsh save</code> command (<a class="xref" href="#form-Virtualization-Managing_guests_with_virsh-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><div class="section" id="idm70012976"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm70012976">E.6. Shutting down, rebooting and force-shutdown of a guest</h2></div></div></div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Shut_down_a_guest"><h5 class="formalpara">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.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Rebooting_a_guest"><h5 class="formalpara">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> element in the guest's configuration file.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Forcing_a_guest_to_stop"><h5 class="formalpara">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.
+ </div></div><div class="section" id="idm103535312"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm103535312">E.7. Retrieving guest information</h2></div></div></div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Getting_the_domain_ID_of_a_guest"><h5 class="formalpara">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" id="form-Virtualization-Managing_guests_with_virsh-Getting_the_domain_name_of_a_guest"><h5 class="formalpara">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" id="form-Virtualization-Managing_guests_with_virsh-Getting_the_UUID_of_a_guest"><h5 class="formalpara">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" id="form-Virtualization-Managing_guests_with_virsh-Displaying_guest_Information_"><h5 class="formalpara">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 vr-rhel6u1-x86_64-kvm
+Id: 9
+Name: vr-rhel6u1-x86_64-kvm
+UUID: a03093a1-5da6-a2a2-3baf-a845db2f10b9
+OS Type: hvm
+State: running
+CPU(s): 1
+CPU time: 21.6s
+Max memory: 2097152 kB
+Used memory: 1025000 kB
+Persistent: yes
+Autostart: disable
+Security model: selinux
+Security DOI: 0
+Security label: system_u:system_r:svirt_t:s0:c612,c921 (permissive)
+</pre></div><div class="section" id="idm123330576"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm123330576">E.8. Retrieving node information</h2></div></div></div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Displaying_node_information"><h5 class="formalpara">Displaying node information</h5>
+ To display information about the node:
+ </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">
+ Returns basic information about the node, including the model number, number of CPUs, type of CPU, and size of the physical memory. The output corresponds to virNodeInfo structure. Specifically, the "CPU socket(s)" field indicates the number of CPU sockets per NUMA cell.
+ </div></div><div class="section" id="idm107205776"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm107205776">E.9. Storage pool information</h2></div></div></div><div class="formalpara" id="asfdqsdgasdfsadgwr"><h5 class="formalpara">Editing a storage pool definition</h5>
+ The <code class="command">virsh pool-edit</code> command takes the name or UUID for a storage pool and opens the XML definition file for a storage pool in the users default text editor.
+ </div><div class="para">
+ The <code class="command">virsh pool-edit</code> command is equivalent to running the following commands:
+ </div><pre class="screen"># virsh pool-dumpxml <em class="parameter"><code>pool</code></em> > <em class="parameter"><code>pool</code></em>.xml
+# vim <em class="parameter"><code>pool</code></em>.xml
+# virsh pool-define <em class="parameter"><code>pool</code></em>.xml
+</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The default editor is defined by the <code class="command">$VISUAL</code> or <code class="command">$EDITOR</code> environment variables, and default is <code class="command">vi</code>.
+ </div></div></div></div><div class="section" id="idm114956880"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm114956880">E.10. Displaying per-guest information</h2></div></div></div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Displaying_the_guests"><h5 class="formalpara">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">
+ There are seven states that can be visible using this command:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Running - The <code class="computeroutput">running</code> state refers to guests which are currently active on a CPU.
+ </div></li><li class="listitem"><div class="para">
+ Idle - The <code class="computeroutput">idle</code> state indicates that the domain is idle, and may not be running or able to run. This can be caused because the domain is waiting on IO (a traditional wait state) or has gone to sleep because there was nothing else for it to do.
+ </div></li><li class="listitem"><div class="para">
+ Paused - 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 class="listitem"><div class="para">
+ Shutdown - 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 class="listitem"><div class="para">
+ Shut off - The <code class="computeroutput">shut off</code> state indicates that the domain is not running. This can be caused when a domain completly shuts down or has not been started.
+ </div></li><li class="listitem"><div class="para">
+ Crashed - The <code class="computeroutput">crashed</code> state indicates that the domain has crashed and can only occur if the guest has been configured not to restart on crash.
+ </div></li><li class="listitem"><div class="para">
+ Dying - 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></ul></div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Displaying_virtual_CPU_information"><h5 class="formalpara">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" id="form-Virtualization-Managing_guests_with_virsh-Configuring_virtual_CPU_affinity"><h5 class="formalpara">Configuring virtual CPU affinity</h5>
+ To configure the affinity of virtual CPUs with physical CPUs:
+ </div><pre class="screen"># virsh vcpupin <em class="parameter"><code>domain-id vcpu cpulist</code></em></pre><div class="para">
+ The <code class="command">domain-id</code> parameter is the guest's ID number or name.
+ </div><div class="para">
+ The <code class="command">vcpu</code> parameter denotes the number of virtualized CPUs allocated to the guest.The <code class="command">vcpu</code> parameter must be provided.
+ </div><div class="para">
+ The <code class="command">cpulist</code> parameter is a list of physical CPU identifier numbers separated by commas. The <code class="command">cpulist</code> parameter determines which physical CPUs the VCPUs can run on.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Configuring_virtual_CPU_count"><h5 class="formalpara">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">
+ This <em class="parameter"><code>count</code></em> value cannot exceed the number of CPUs that were assigned to the guest when it was created.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Configuring_memory_allocation"><h5 class="formalpara">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><pre class="screen"># <code class="command">virsh setmem</code> <em class="replaceable"><code>vr-rhel6u1-x86_64-kvm</code></em> <em class="replaceable"><code>--kilobytes 1025000</code></em></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 does not affect active guests. If the new value is lower than the available memory, it will shrink possibly causing the guest to crash.
+ </div><div class="para">
+ This command has the following options
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ [--domain] <string> domain name, id or uuid
+ </div></li><li class="listitem"><div class="para">
+ [--size] <number> new memory size, as scaled integer (default KiB)
+ </div></li><li class="listitem"><div class="para">
+ --config takes affect next boot
+ </div></li><li class="listitem"><div class="para">
+ --live controls the memory of the running domain
+ </div></li><li class="listitem"><div class="para">
+ --current controls the memory on the current domain
+ </div></li></ul></div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Configuring_memory_tuning"><h5 class="formalpara">Configuring memory Tuning</h5>
+ The element memtune provides details regarding the memory tunable parameters for the domain. If this is omitted, it defaults to the OS provided defaults. For QEMU/KVM, the parameters are applied to the QEMU process as a whole. Thus, when counting them, one needs to add up guest RAM, guest video RAM, and some memory overhead of QEMU itself. The last piece is hard to determine so one needs guess and try. For each tunable, it is possible to designate which unit the number is in on input, using the same values as for <memory>. For backwards compatibility, output is always in KiB. units.
+ </div><div class="para">
+ Here is an example XML with the memtune options used:
+ </div><pre class="screen">
+<domain>
+
+ <memtune>
+ <hard_limit unit='G'>1</hard_limit>
+ <soft_limit unit='M'>128</soft_limit>
+ <swap_hard_limit unit='G'>2</swap_hard_limit>
+ <min_guarantee unit='bytes'>67108864</min_guarantee>
+ </memtune>
+ ...
+</domain>
+</pre><div class="para">
+ memtune has the following options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ hard_limit - The optional hard_limit element is the maximum memory the guest can use. The units for this value are kibibytes (i.e. blocks of 1024 bytes)
+ </div></li><li class="listitem"><div class="para">
+ soft_limit - The optional soft_limit element is the memory limit to enforce during memory contention. The units for this value are kibibytes (i.e. blocks of 1024 bytes)
+ </div></li><li class="listitem"><div class="para">
+ swap_hard_limit - The optional swap_hard_limit element is the maximum memory plus swap the guest can use. The units for this value are kibibytes (i.e. blocks of 1024 bytes). This has to be more than hard_limit value provided
+ </div></li><li class="listitem"><div class="para">
+ min_guarantee - The optional min_guarantee element is the guaranteed minimum memory allocation for the guest. The units for this value are kibibytes (i.e. blocks of 1024 bytes)
+ </div></li></ul></div><pre class="screen">
+# virsh memtune vr-rhel6u1-x86_64-kvm --hard-limit 512000
+
+# virsh memtune vr-rhel6u1-x86_64-kvm
+hard_limit : 512000 kB
+soft_limit : unlimited
+swap_hard_limit: unlimited
+</pre><div class="para">
+ hard_limit is 512000 kB, it is maximum memory the guest domain can use.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Displaying_guest_block_device_information"><h5 class="formalpara">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" id="form-Virtualization-Managing_guests_with_virsh-Displaying_guest_network_device_information"><h5 class="formalpara">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><div class="section" id="idm92394304"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm92394304">E.11. Managing virtual networks</h2></div></div></div><div class="para">
+ 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 class="listitem"><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 class="listitem"><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 class="listitem"><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 class="listitem"><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 class="listitem"><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 class="listitem"><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 class="listitem"><div class="para">
+ <code class="command">virsh net-start <em class="replaceable"><code>nameOfInactiveNetwork</code></em> </code> — starts an inactive network.
+ </div></li><li class="listitem"><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><div class="section" id="migrating_guests-with-virsh"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">E.12. Migrating guests with virsh</h2></div></div></div><div class="para">
+ Information on migration using virsh is located in the section entitled Live KVM Migration with virsh Refer to <a class="xref" href="#sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh">Section 20.4, “Live KVM migration with virsh”</a>
+ </div></div><div class="section" id="sect-man-disk-image"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">E.13. Disk image management with live block copy</h2></div></div></div><div class="para">
+ Live block copy allows you to copy an in use guest disk image to a destination image and switches the guest disk image to the destination guest image while the guest is running. Whilst live migration moves the memory and registry state of the host, the guest is kept in shared storage. Live block copy allows you to move the entire guest contents to another host on the fly while the guest is running. Live block copy may also be used for live migration without requiring permanent share storage. In this method the disk image is copied to the destination host after migration, but while the guest is running.
+ </div><div class="para">
+ Live block copy is especially useful for the following applications:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ moving the guest image from local storage to a central location
+ </div></li><li class="listitem"><div class="para">
+ when maintenance is required, guests can be transferred to another location, with no loss of performance
+ </div></li><li class="listitem"><div class="para">
+ allows for management of guest images for speed and efficiency
+ </div></li><li class="listitem"><div class="para">
+ image format conversions can be done without having to shut down the guest
+ </div></li></ul></div><div class="example" id="live-blk-cpy-example"><h6>Example E.1. Example (live block copy)</h6><div class="example-contents"><div class="para">
+ This example shows what happens when live block copy is performed. The example has a backing file (base) that is shared between a source and destination. It also has two overlays (sn1 and sn2) that are only present on the source and must be copied.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ The backing file chain at the beginning looks like this:
+ </div><div class="para">
+ <code class="command"> base ← sn1 ← sn2</code>
+ </div><div class="para">
+ The components are as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ base - the original disk image
+ </div></li><li class="listitem"><div class="para">
+ sn1 - the first snapshot that was taken of the base disk image
+ </div></li><li class="listitem"><div class="para">
+ sn2 - the most current snapshot
+ </div></li><li class="listitem"><div class="para">
+ active - the copy of the disk
+ </div></li></ul></div></li><li class="step"><div class="para">
+ When a copy of the image is created as a new image on top of sn2 the result is this:
+ </div><div class="para">
+ <code class="command">base ← sn1 ← sn2 ← active </code>
+ </div></li><li class="step"><div class="para">
+ At this point the read permissions are all in the correct order and are set automatically. To make sure write permissions are set properly, a mirror mechanism redirects all writes to both sn2 and active, so that sn2 and active read the same at any time (and this mirror mechanism is the essential difference between live block copy and image streaming).
+ </div></li><li class="step"><div class="para">
+ A background task that loops over all disk clusters is executed. For each cluster, there are the following possible cases and actions:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The cluster is already allocated in active and there is nothing to do.
+ </div></li><li class="listitem"><div class="para">
+ Use <code class="command">bdrv_is_allocated()</code> to follow the backing file chain. If the cluster is read from base (which is shared) there is nothing to do.
+ </div></li><li class="listitem"><div class="para">
+ If <code class="command">bdrv_is_allocated()</code> variant is not feasible, rebase the image and compare the read data with write data in base in order to decide if a copy is needed.
+ </div></li><li class="listitem"><div class="para">
+ In all other cases, copy the cluster into <code class="filename">active</code>
+ </div></li></ul></div></li><li class="step"><div class="para">
+ When the copy has completed, the backing file of active is switched to base (similar to rebase)
+ </div></li></ol></div></div></div><br class="example-break" /><div class="para">
+ To reduce the length of a backing chain after a series of snapshots, the following commands are helpful: <code class="command">blockcommit</code> and <code class="command">blockpull</code>. See <a class="xref" href="#sect-blockcommit">Section E.13.1, “Using blockcommit to shorten a backing chain”</a> for more information.
+ </div><div class="section" id="sect-blockcommit"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.13.1. Using blockcommit to shorten a backing chain</h3></div></div></div><div class="para">
+ This section demonstrates how to use <code class="command">blockcommit</code> to shorten a backing chain. For more background on backing chains, see <a class="xref" href="#sect-man-disk-image">Section E.13, “Disk image management with live block copy”</a>.
+ </div><div class="para">
+ <code class="command">blockcommit</code> copies data from one part of the chain down into a backing file, allowing you to pivot the rest of the chain in order to bypass the committed portions. For example, suppose this is the current state:
+ </div><pre class="screen">
+ <code class="command">base ← snap1 ← snap2 ← active</code>.
+</pre><div class="para">
+ Using <code class="command">blockcommit</code> moves the contents of snap2 into snap1, allowing you to delete snap2 from the chain, making backups much quicker.
+ </div><div class="procedure" id="pro-blockcommit"><h6>Procedure E.1. virsh blockcommit</h6><ul><li class="step"><div class="para">
+ Run the following command:
+ </div><pre class="screen">#<code class="command"> virsh blockcommit $dom $disk --base snap1 --top snap2 --wait --verbose</code></pre><div class="para">
+ The contents of snap2 are moved into snap1, resulting in:
+ </div><div class="para">
+ <code class="command">base ← snap1 ← active</code>. Snap2 is no longer valid and can be deleted
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ <code class="command">blockcommit</code> will corrupt any file that depends on the <em class="parameter"><code>--base</code></em> argument (other than files that depended on the <em class="parameter"><code>--top</code></em> argument, as those files now point to the base). To prevent this, do not commit changes into files shared by more than one guest. The <em class="parameter"><code>--verbose</code></em> option will allow the progress to be printed on the screen.
+ </div></div></div></li></ul></div></div><div class="section" id="sub-sect-blockpull"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.13.2. Using blockpull to shorten a backing chain</h3></div></div></div><div class="para">
+ <code class="command">blockpull</code> can be used in in the following applications:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Flattens an image by populating it with data from its backing image chain. This makes the image file self-contained so that it no longer depends on backing images and looks like this:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Before: base.img ← Active
+ </div></li><li class="listitem"><div class="para">
+ After: base.img is no longer used by the guest and Active contains all of the data.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Flattens part of the backing image chain. This can be used to flatten snapshots into the top-level image and looks like this:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Before: base ← sn1 ←sn2 ← active
+ </div></li><li class="listitem"><div class="para">
+ After: base.img ← active. Note that active now contains all data from sn1 and sn2 and neither sn1 nor sn2 are used by the guest.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Moves the disk image to a new file system on the host. This is allows image files to be moved while the guest is running and looks like this:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Before (The original image file): <code class="filename">/fs1/base.vm.img</code>
+ </div></li><li class="listitem"><div class="para">
+ After: <code class="filename">/fs2/active.vm.qcow2</code> is now the new file system and <code class="filename">/fs1/base.vm.img</code> is no longer used.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Useful in live migration with post-copy storage migration. The disk image is copied from the source host to the destination host after live migration completes.
+ </div><div class="para">
+ In short this is what happens: Before:<code class="filename">/source-host/base.vm.img</code> After:<code class="filename">/destination-host/active.vm.qcow2</code>.<code class="filename">/source-host/base.vm.img</code> is no longer used.
+ </div></li></ul></div><div class="procedure" id="virsh-blk-pull-pro"><h6>Procedure E.2. Using blockpull to shorten a backing chain</h6><ol class="1"><li class="step"><div class="para">
+ It may be helpful to run this command prior to running <code class="command">blockpull</code>:
+ </div><pre class="screen">#<code class="command"> virsh snapshot-create-as $dom $name -- disk-only</code></pre></li><li class="step"><div class="para">
+ If the chain looks like this: <code class="command">base ← snap1 ← snap2 ← active</code> run the following:
+ </div><pre class="screen">#<code class="command"> virsh blockpull $dom $disk snap1</code></pre><div class="para">
+ This command makes 'snap1' the backing file of active, by pulling data from snap2 into active resulting in: base ← snap1 ← active.
+ </div></li><li class="step"><div class="para">
+ Once the <code class="command">blockpull</code> is complete, the <span class="application"><strong>libvirt</strong></span> tracking of the snapshot that created the extra image in the chain is no longer useful. Delete the tracking on the outdated snapshot with this command:
+ </div><pre class="screen">#<code class="command"> virsh snapshot-delete $dom $name -- metadata</code></pre></li></ol></div><div class="para">
+ Additional applications of <code class="command">blockpull</code> can be done as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ To flatten a single image and populate it with data from its backing image chain:<code class="command"># virsh blockpull example-domain vda -- wait</code>
+ </div></li><li class="listitem"><div class="para">
+ To flatten part of the backing image chain:<code class="command"># virsh blockpull example-domain vda -- base /path/to/base.img -- wait</code>
+ </div></li><li class="listitem"><div class="para">
+ To move the disk image to a new file system on the host:<code class="command"># virsh snapshot-create example-domain -- xmlfile /path/to/new.xml -- disk-only</code> followed by <code class="command"># virsh blockpull example-domain vda -- wait</code>
+ </div></li><li class="listitem"><div class="para">
+ To use live migration with post-copy storage migration:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ On the destination run:
+ </div><pre class="screen"><code class="command"> # qemu-img create -f qcow2 -o backing_file=/source-host/vm.img /destination-host/vm.qcow2</code></pre></li><li class="listitem"><div class="para">
+ On the source run:
+ </div><pre class="screen"><code class="command"># virsh migrate example-domain</code></pre></li><li class="listitem"><div class="para">
+ On the destination run:
+ </div><pre class="screen"><code class="command"># virsh blockpull example-domain vda -- wait</code></pre></li></ul></div></li></ul></div></div><div class="section" id="sub-sect-blkresize"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.13.3. Using blockresize to change the size of a domain path</h3></div></div></div><div class="para">
+ <code class="command">blockresize</code> can be used to re-size a block device of a domain while the domain is running, using the absolute path of the block device which also corresponds to a unique target name (<code class="command"><target dev="name"/></code>) or source file (<code class="command"><source file="name"/></code>). This can be applied to one of the disk devices attached to domain (you can use the command <code class="command">domblklist</code> to print a table showing the brief information of all block devices associated with a given domain).
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Live image re-sizing will always resize the image, but may not immediately be picked up by guests. With recent guest kernels, the size of virtio-blk devices is automatically updated (older kernels require a guest reboot). With SCSI devices, it is required to manually trigger a re-scan in the guest with the command, <code class="command">echo > /sys/class/scsi_device/0:0:0:0/device/rescan</code>. In addition, with IDE it is required to reboot the guest before it picks up the new size.
+ </div></div></div><div class="procedure"><ul><li class="step"><div class="para">
+ Run the following command: <code class="command">blockresize [domain] [path size]</code> where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Domain is the unique target name or source file of the domain whose size you want to change
+ </div></li><li class="listitem"><div class="para">
+ Path size is a scaled integer which defaults to KiB (blocks of 1024 bytes) if there is no suffix. You must use a suffix of "B" to for bytes.
+ </div></li></ul></div></li></ul></div></div></div><div class="section" id="sect-guest-cpu-model-config"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">E.14. Guest CPU model configuration</h2></div></div></div><div class="section" id="sect-guest-cpu-intro"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.14.1. Introduction</h3></div></div></div><div class="para">
+ Every hypervisor has its own policy for what a guest will see for its CPUs by default. Whereas some hypervisors decide which CPU host features will be available for the guest, QEMU/KVM presents the guest with a generic model named <span class="bold bold"><strong>qemu32</strong></span> or <span class="bold bold"><strong>qemu64</strong></span>. These hypervisors perform more advanced filtering, classifying all physical CPUs into a handful of groups and have one baseline CPU model for each group that is presented to the guest. Such behavior enables the safe migration of guests between hosts, provided they all have physical CPUs that classify into the same group. libvirt does not typically enforce policy itself, rather it provides the mechanism on which the higher layers define their own desired policy. Understanding how to obtain CPU model information and define a suitable guest CPU model is critical to ensure guest migration is successful between hosts. Note that a hypervi
sor can only emulate features that it is aware of and features that were created after the hypervisor was released may not be emulated.
+ </div></div><div class="section" id="sect-learn-about-host-cpu"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.14.2. Learning about the host CPU model</h3></div></div></div><div class="para">
+ The <code class="command">virsh capabilities</code> command displays an XML document describing the capabilities of the hypervisor connection and host. The XML schema displayed has been extended to provide information about the host CPU model. One of the big challenges in describing a CPU model is that every architecture has a different approach to exposing their capabilities. On x86, the capabilities of a modern CPU are exposed via the CPUID instruction. Essentially this comes down to a set of 32-bit integers with each bit given a specific meaning. Fortunately AMD and Intel agree on common semantics for these bits. Other hypervisors expose the notion of CPUID masks directly in their guest configuration format. However, QEMU/KVM supports far more than just the x86 architecture, so CPUID is clearly not suitable as the canonical configuration format. QEMU ended up using a scheme which combines a CPU model name string, with a set of named flags. On x86, the CPU model maps t
o a baseline CPUID mask, and the flags can be used to then toggle bits in the mask on or off. libvirt decided to follow this lead and uses a combination of a model name and flags. Here is an example of what libvirt reports as the capabilities on a development workstation:
+ </div><pre class="screen">
+# virsh capabilities
+<capabilities>
+
+ <host>
+ <uuid>c4a68e53-3f41-6d9e-baaf-d33a181ccfa0</uuid>
+ <cpu>
+ <arch>x86_64</arch>
+ <model>core2duo</model>
+ <topology sockets='1' cores='4' threads='1'/>
+ <feature name='lahf_lm'/>
+ <feature name='sse4.1'/>
+ <feature name='xtpr'/>
+ <feature name='cx16'/>
+ <feature name='tm2'/>
+ <feature name='est'/>
+ <feature name='vmx'/>
+ <feature name='ds_cpl'/>
+ <feature name='pbe'/>
+ <feature name='tm'/>
+ <feature name='ht'/>
+ <feature name='ss'/>
+ <feature name='acpi'/>
+ <feature name='ds'/>
+ </cpu>
+
+ ... snip ...
+ </host>
+
+</capabilities>
+</pre><div class="para">
+ It is not practical to have a database listing all known CPU models, so libvirt has a small list of baseline CPU model names. It chooses the one that shares the greatest number of CPUID bits with the actual host CPU and then lists the remaining bits as named features. Notice that libvirt does not display which features the baseline CPU contains. This might seem like a flaw at first, but as will be explained in this section, it is not actually necessary to know this information.
+ </div></div><div class="section" id="idm90465808"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm90465808">E.14.3. Determining a compatible CPU model to suit a pool of hosts</h3></div></div></div><div class="para">
+ Now that it is possible to find out what CPU capabilities a single host has, the next step is to determine what CPU capabilities are best to expose to the guest. If it is known that the guest will never need to be migrated to another host, the host CPU model can be passed straight through unmodified. A virtualized data center may have a set of configurations that can guarantee all servers will have 100% identical CPUs. Again the host CPU model can be passed straight through unmodified. The more common case, though, is where there is variation in CPUs between hosts. In this mixed CPU environment, the lowest common denominator CPU must be determined. This is not entirely straightforward, so libvirt provides an API for exactly this task. If libvirt is provided a list of XML documents, each describing a CPU model for a host, libvirt will internally convert these to CPUID masks, calculate their intersection, and convert the CPUID mask result back into an XML CPU description.
Taking the CPU description from a server:
+ </div><pre class="screen">
+# virsh capabilities
+<capabilities>
+
+ <host>
+ <uuid>8e8e4e67-9df4-9117-bf29-ffc31f6b6abb</uuid>
+ <cpu>
+ <arch>x86_64</arch>
+ <model>Westmere</model>
+ <vendor>Intel</vendor>
+ <topology sockets='2' cores='4' threads='2'/>
+ <feature name='rdtscp'/>
+ <feature name='pdpe1gb'/>
+ <feature name='dca'/>
+ <feature name='xtpr'/>
+ <feature name='tm2'/>
+ <feature name='est'/>
+ <feature name='vmx'/>
+ <feature name='ds_cpl'/>
+ <feature name='monitor'/>
+ <feature name='pbe'/>
+ <feature name='tm'/>
+ <feature name='ht'/>
+ <feature name='ss'/>
+ <feature name='acpi'/>
+ <feature name='ds'/>
+ <feature name='vme'/>
+ </cpu>
+
+ ... snip ...
+
+</capabilities>
+</pre><div class="para">
+ A quick check can be made to see whether this CPU description is compatible with the previous workstation CPU description, using the <code class="command">virsh cpu-compare</code> command. To do so, the <code class="command">virsh capabilities > virsh-caps-workstation-full.xml</code> command was executed on the workstation. The file <code class="filename">virsh-caps-workstation-full.xml</code> was edited and reduced to just the following content:
+ </div><pre class="screen">
+<cpu>
+ <arch>x86_64</arch>
+ <model>core2duo</model>
+ <topology sockets='1' cores='4' threads='1'/>
+ <feature name='lahf_lm'/>
+ <feature name='sse4.1'/>
+ <feature name='xtpr'/>
+ <feature name='cx16'/>
+ <feature name='tm2'/>
+ <feature name='est'/>
+ <feature name='vmx'/>
+ <feature name='ds_cpl'/>
+ <feature name='pbe'/>
+ <feature name='tm'/>
+ <feature name='ht'/>
+ <feature name='ss'/>
+ <feature name='acpi'/>
+ <feature name='ds'/>
+ </cpu>
+</pre><div class="para">
+ The reduced content was stored in a file named <code class="filename">virsh-caps-workstation-cpu-only.xml</code> and the <code class="command">virsh cpu-compare</code> command can be executed using this file:
+ </div><pre class="screen">
+virsh cpu-compare virsh-caps-workstation-cpu-only.xml
+Host CPU is a superset of CPU described in virsh-caps-workstation-cpu-only.xml
+</pre><div class="para">
+ As seen in this output, libvirt is correctly reporting the CPUs are not strictly compatible, because there are several features in the server CPU that are missing in the workstation CPU. To be able to migrate between the workstation and the server, it will be necessary to mask out some features, but to determine which ones, libvirt provides an API for this, shown via the <code class="command">virsh cpu-baseline</code> command:
+ </div><pre class="screen">
+# virsh cpu-baseline virsh-cap-weybridge-strictly-cpu-only.xml
+<cpu match='exact'>
+ <model>Penryn</model>
+ <feature policy='require' name='xtpr'/>
+ <feature policy='require' name='tm2'/>
+ <feature policy='require' name='est'/>
+ <feature policy='require' name='vmx'/>
+ <feature policy='require' name='ds_cpl'/>
+ <feature policy='require' name='monitor'/>
+ <feature policy='require' name='pbe'/>
+ <feature policy='require' name='tm'/>
+ <feature policy='require' name='ht'/>
+ <feature policy='require' name='ss'/>
+ <feature policy='require' name='acpi'/>
+ <feature policy='require' name='ds'/>
+ <feature policy='require' name='vme'/>
+</cpu>
+</pre><div class="para">
+ Similarly, if the two <cpu>...</cpu> elements are put into a single file named <code class="filename">both-cpus.xml</code>, the following command would generate the same result:
+ </div><pre class="screen"> # virsh cpu-baseline both-cpus.xml</pre><div class="para">
+ In this case, libvirt has determined that in order to safely migrate a guest between the workstation and the server, it is necessary to mask out 3 features from the XML description for the server, and 3 features from the XML description for the workstation.
+ </div></div><div class="section" id="idm111893984"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm111893984">E.14.4. Configuring the guest CPU model</h3></div></div></div><div class="para">
+ For simple defaults, the guest CPU configuration accepts the same basic XML representation as the host capabilities XML exposes. In other words, the XML from the <code class="command">cpu-baseline</code> virsh command can now be copied directly into the guest XML at the top level under the <domain> element. As the observant reader will have noticed from the previous XML snippet, there are a few extra attributes available when describing a CPU in the guest XML. These can mostly be ignored, but for the curious here is a quick description of what they do. The top level <cpu> element has an attribute called <span class="emphasis"><em>match</em></span> with possible values of:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ match='minimum' - the host CPU must have at least the CPU features described in the guest XML. If the host has additional features beyond the guest configuration, these will also be exposed to the guest.
+ </div></li><li class="listitem"><div class="para">
+ match='exact' - the host CPU must have at least the CPU features described in the guest XML. If the host has additional features beyond the guest configuration, these will be masked out from the guest.
+ </div></li><li class="listitem"><div class="para">
+ match='strict' - the host CPU must have exactly the same CPU features described in the guest XML.
+ </div></li></ul></div><div class="para">
+ The next enhancement is that the <feature> elements can each have an extra 'policy' attribute with possible values of:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ policy='force' - expose the feature to the guest even if the host does not have it. This is usually only useful in the case of software emulation.
+ </div></li><li class="listitem"><div class="para">
+ policy='require' - expose the feature to the guest and fail if the host does not have it. This is the sensible default.
+ </div></li><li class="listitem"><div class="para">
+ policy='optional' - expose the feature to the guest if it happens to support it.
+ </div></li><li class="listitem"><div class="para">
+ policy='disable' - if the host has this feature, then hide it from the guest.
+ </div></li><li class="listitem"><div class="para">
+ policy='forbid' - if the host has this feature, then fail and refuse to start the guest.
+ </div></li></ul></div><div class="para">
+ The 'forbid' policy is for a niche scenario where an incorrectly functioning application will try to use a feature even if it is not in the CPUID mask, and you wish to prevent accidentally running the guest on a host with that feature. The 'optional' policy has special behavior with respect to migration. When the guest is initially started the flag is optional, but when the guest is live migrated, this policy turns into 'require', since you cannot have features disappearing across migration.
+ </div></div></div></div><div xml:lang="en-US" class="appendix" id="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Managing guests with the Virtual Machine Manager (virt-manager)</h1></div></div></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 guests on your host system and on remote host systems. <code class="command">virt-manager</code> can perform virtualization management tasks, including:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ defining and creating guests,
+ </div></li><li class="listitem"><div class="para">
+ assigning memory,
+ </div></li><li class="listitem"><div class="para">
+ assigning virtual CPUs,
+ </div></li><li class="listitem"><div class="para">
+ monitoring operational performance,
+ </div></li><li class="listitem"><div class="para">
+ saving and restoring, pausing and resuming, and shutting down and starting guests,
+ </div></li><li class="listitem"><div class="para">
+ links to the textual and graphical consoles, and
+ </div></li><li class="listitem"><div class="para">
+ live and offline migrations.
+ </div></li></ul></div><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Starting_virt_manager"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">F.1. 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_Administration_Guide-Starting_virt_manager-Starting_virt_manager"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt1.png" width="444" alt="Starting virt-manager" /></div></div><h6>Figure F.1. 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:
+ </div><pre class="screen">ssh -X <em class="replaceable"><code>host's address</code></em>
+[remotehost]# virt-manager
+</pre><div class="para">
+ Using <code class="command">ssh</code> to manage virtual machines and hosts is discussed further in <a class="xref" href="#sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_with_SSH">Section 21.1, “Remote management with SSH”</a>.
+ </div></div><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">F.2. The Virtual Machine Manager main window</h2></div></div></div><div class="para">
+ This main window displays all the running guests and resources used by guests. Select a guest by double clicking the guest's name.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-The_Virtual_Machine_Manager_main_window-Virtual_Machine_Manager_main_window"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt2.png" width="444" alt="Virtual Machine Manager main window" /></div></div><h6>Figure F.2. Virtual Machine Manager main window</h6></div><br class="figure-break" /></div><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">F.3. The virtual hardware details window</h2></div></div></div><div class="para">
+ The virtual hardware details window displays information about the virtual hardware configured for the guest. Virtual hardware resources can be added, removed and modified in this window. To access the virtual hardware details window, click on the icon in the toolbar.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-The_Virtual_Machine_Manager_details_window_-virt_manager_details_button"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt3.png" width="444" alt="The virtual hardware details icon" /></div></div><h6>Figure F.3. The virtual hardware details icon</h6></div><br class="figure-break" /><div class="para">
+ Clicking the icon displays the virtual hardware details window.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-The_Virtual_Machine_Manager_details_window_-virt_manager_details_window"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt4.png" width="444" alt="The virtual hardware details window" /></div></div><h6>Figure F.4. The virtual hardware details window</h6></div><br class="figure-break" /></div><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">F.4. Virtual Machine graphical console</h2></div></div></div><div class="para">
+ This window displays a guest's graphical console. Guests can use several different protocols to export their graphical framebuffers: <code class="command">virt-manager</code> supports <span class="application"><strong>VNC</strong></span> and <span class="application"><strong>SPICE</strong></span>. 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_Administration_Guide-Virtual_Machine_graphical_console_-Graphical_console_window"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt5.png" width="444" alt="Graphical console window" /></div></div><h6>Figure F.5. Graphical console window</h6></div><br class="figure-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><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'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. Although virt-manager is configured to listen to other public network interfaces and alternative methods can be configured, it is not recommended.
+ </div><div class="para">
+ Remote administration can be performed by tunneling over SSH which encrypts the traffic. Although VNC can be configured to access remotely without tunneling over SSH, for security reasons, it is not recommended. To remotely administer the guest follow the instructions in: <a class="xref" href="#chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests">Chapter 21, <em>Remote management of guests</em></a>. TLS can provide enterprise level security for managing guest and host systems.
+ </div></div></div><div class="para">
+ Your local desktop can intercept key combinations (for example, Ctrl+Alt+F1) to prevent them from being sent to the guest machine. You can use the <span class="guimenuitem"><strong>Send key</strong></span> menu option to send these sequences. From the guest machine window, click the <span class="guimenuitem"><strong>Send key</strong></span> menu and select the key sequence to send. In addition, from this menu you can also capture the screen output.
+ </div><div class="para">
+ SPICE is an alternative to VNC available for Fedora.
+ </div></div><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">F.5. Adding a remote connection</h2></div></div></div><div class="para">
+ This procedure covers how to set up a connection to a remote system using <code class="command">virt-manager</code>.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To create a new connection open the <span class="guilabel"><strong>File</strong></span> menu and select the <span class="guilabel"><strong>Add Connection...</strong></span> menu item.
+ </div></li><li class="step"><div class="para">
+ The <span class="guilabel"><strong>Add Connection</strong></span> wizard appears. Select the hypervisor. For Fedora systems select <span class="guilabel"><strong>QEMU/KVM</strong></span>. Select Local for the local system or one of the remote connection options and click <span class="guilabel"><strong>Connect</strong></span>. This example uses Remote tunnel over SSH which works on default installations. For more information on configuring remote connections refer to <a class="xref" href="#chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests">Chapter 21, <em>Remote management of guests</em></a>
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Remote_management-Add_connection"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt6.png" alt="Add Connection" /></div></div><h6>Figure F.6. Add Connection</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Enter the root password for the selected host when prompted.
+ </div></li></ol></div><div class="para">
+ A remote host is now connected and appears in the main <code class="command">virt-manager</code> window.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Remote_management-Remove_host_in_the_main_virt-manager_window"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt7.png" width="444" alt="Remote host in the main virt-manager window" /></div></div><h6>Figure F.7. Remote host in the main virt-manager window</h6></div><br class="figure-break" /></div><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">F.6. Displaying guest details</h2></div></div></div><div class="para">
+ You can use the Virtual Machine Monitor to view activity 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 class="step"><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_Administration_Guide-Displaying_guest_details-Selecting_a_virtual_machine_to_display_"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt1.png" width="444" alt="Selecting a virtual machine to display" /></div></div><h6>Figure F.8. Selecting a virtual machine to display </h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ From the Virtual Machine Manager <span class="guilabel"><strong>Edit</strong></span> menu, select <span class="guilabel"><strong>Virtual Machine Details</strong></span>.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Displaying_virtual_machine_details_menu"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt11.png" width="444" alt="Displaying the virtual machine details" /></div></div><h6>Figure F.9. Displaying the virtual machine details</h6></div><br class="figure-break" /><div class="para">
+ When the Virtual Machine details window opens, there may be a console displayed. Should this happen, clikc <span class="guilabel"><strong>View</strong></span> and then select <span class="guilabel"><strong>Details</strong></span>. The Overview window opens first by default. To go back to this window, select <span class="guilabel"><strong>Overview</strong></span> from the navigation pane on the left hand side.
+ </div><div class="para">
+ The <span class="guilabel"><strong>Overview</strong></span> view shows a summary of configuration details for the guest.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Displaying_guest_details_overview"><div class="figure-contents"><div class="mediaobject"><img src="images/virtual_machine_overview.png" width="444" alt="Displaying guest details overview" /></div></div><h6>Figure F.10. Displaying guest details overview</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Select <span class="guilabel"><strong>Performance</strong></span> from the navigation pane on the left hand side.
+ </div><div class="para">
+ The <span class="guilabel"><strong>Performance</strong></span> view shows a summary of guest performance, including CPU and Memory usage.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Displaying_guest_performance"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt13.png" width="444" alt="Displaying guest performance details" /></div></div><h6>Figure F.11. Displaying guest performance details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Select <span class="guilabel"><strong>Processor</strong></span> from the navigation pane on the left hand side. The <span class="guilabel"><strong>Processor</strong></span> view allows you to view or change the current processor allocation.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Processor_allocation_panel"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt14.png" width="444" alt="Processor allocation panel" /></div></div><h6>Figure F.12. Processor allocation panel</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Select <span class="guilabel"><strong>Memory</strong></span> from the navigation pane on the left hand side. The <span class="guilabel"><strong>Memory</strong></span> view allows you to view or change the current memory allocation.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Displaying_memory_allocation"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt15.png" width="444" alt="Displaying memory allocation" /></div></div><h6>Figure F.13. Displaying memory allocation</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Each virtual disk attached to the virtual machine is displayed in the navigation pane. Click on a virtual disk to modify or remove it.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Displaying_disk_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt16.png" width="444" alt="Displaying disk configuration" /></div></div><h6>Figure F.14. Displaying disk configuration</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Each virtual network interface attached to the virtual machine is displayed in the navigation pane. Click on a virtual network interface to modify or remove it.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Displaying_network_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt17.png" width="444" alt="Displaying network configuration" /></div></div><h6>Figure F.15. Displaying network configuration</h6></div><br class="figure-break" /></li></ol></div></div><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">F.7. Performance monitoring</h2></div></div></div><div class="para">
+ Performance monitoring preferences can be modified with <code class="command">virt-manager</code>'s preferences window.
+ </div><div class="para">
+ To configure performance monitoring:
+ </div><div class="procedure"><ol class="1"><li class="step"><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_Administration_Guide-Status_monitoring-Modifying_guest_preferences"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-VIrt-Manager-fig31pt18.png" width="444" alt="Modifying guest preferences" /></div></div><h6>Figure F.16. Modifying guest preferences</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guilabel"><strong>Preferences</strong></span> window appears.
+ </div></li><li class="step"><div class="para">
+ From the <span class="guilabel"><strong>Stats</strong></span> tab specify the time in seconds or stats polling options.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Status_monitoring-Configuring_status_monitoring"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt19.png" alt="Configuring performance monitoring" /></div></div><h6>Figure F.17. Configuring performance monitoring</h6></div><br class="figure-break" /></li></ol></div></div><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">F.8. Displaying CPU usage for guests</h2></div></div></div><div class="para">
+ To view the CPU usage for all guests on your system:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ From the <span class="guilabel"><strong>View</strong></span> menu, select <span class="guilabel"><strong>Graph</strong></span>, then the <span class="guilabel"><strong>Guest CPU Usage</strong></span> check box.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_CPU_usage-Selecting_guest-CPU_usage"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt24.png" width="444" alt="Enabling guest CPU usage statistics graphing" /></div></div><h6>Figure F.18. Enabling guest CPU usage statistics graphing</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ The Virtual Machine Manager shows a graph of CPU usage for all virtual machines on your system.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_CPU_usage-Displaying_CPU_usage"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager_fig31pt25.png" width="444" alt="Guest CPU usage graph" /></div></div><h6>Figure F.19. Guest CPU usage graph</h6></div><br class="figure-break" /></li></ol></div></div><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">F.9. Displaying CPU usage for hosts</h2></div></div></div><div class="para">
+ To view the CPU usage for all hosts on your system:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ From the <span class="guilabel"><strong>View</strong></span> menu, select <span class="guilabel"><strong>Graph</strong></span>, then the <span class="guilabel"><strong>Host CPU Usage</strong></span> check box.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_Host-CPU_usage-Selecting_CPU_usage"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt24a.png" width="444" alt="Enabling host CPU usage statistics graphing" /></div></div><h6>Figure F.20. Enabling host CPU usage statistics graphing</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ The Virtual Machine Manager shows a graph of host CPU usage on your system.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_host-CPU_usage-Displaying_CPU_usage"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager_fig31pt25a.png" width="444" alt="Host CPU usage graph" /></div></div><h6>Figure F.21. Host CPU usage graph</h6></div><br class="figure-break" /></li></ol></div></div><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">F.10. Displaying Disk I/O</h2></div></div></div><div class="para">
+ To view the disk I/O for all virtual machines on your system:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Make sure that the Disk I/O statisctics collection is enabled. To do this, from the <span class="guilabel"><strong>Edit</strong></span> menu, select <span class="guilabel"><strong>Preferences</strong></span> and click the <span class="guilabel"><strong>Stats</strong></span>tab.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Disk I/O </strong></span>checkbox.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-enabling_Disk_IO-stats"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager-enable-disk-io.png" alt="Enabling Disk I/O" /></div></div><h6>Figure F.22. Enabling Disk I/O</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ To enable the Disk I.O display, from the <span class="guilabel"><strong>View</strong></span> menu, select <span class="guilabel"><strong>Graph</strong></span>, then the <span class="guilabel"><strong>Disk I/O</strong></span> check box.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_Disk_IO-Selecting_Disk_IO"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager_fig31pt26.png" width="444" alt="Selecting Disk I/O" /></div></div><h6>Figure F.23. Selecting Disk I/O</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ The Virtual Machine Manager shows a graph of Disk I/O for all virtual machines on your system.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_Disk_IO-Displaying_Disk_IO"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt27.png" width="444" alt="Displaying Disk I/O" /></div></div><h6>Figure F.24. Displaying Disk I/O</h6></div><br class="figure-break" /></li></ol></div></div><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">F.11. Displaying Network I/O</h2></div></div></div><div class="para">
+ To view the network I/O for all virtual machines on your system:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Make sure that the Network I/O statisctics collection is enabled. To do this, from the <span class="guilabel"><strong>Edit</strong></span> menu, select <span class="guilabel"><strong>Preferences</strong></span> and click the <span class="guilabel"><strong>Stats</strong></span>tab.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Network I/O </strong></span>checkbox.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-enabling_network_IO-stats"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager-enable-networkio.png" alt="Enabling Network I/O" /></div></div><h6>Figure F.25. Enabling Network I/O</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ To display the Network I/O statistics, from the <span class="guilabel"><strong>View</strong></span> menu, select <span class="guilabel"><strong>Graph</strong></span>, then the <span class="guilabel"><strong>Network I/O</strong></span> check box.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_Network_IO-Selecting_Network_IO"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt28.png" width="444" alt="Selecting Network I/O" /></div></div><h6>Figure F.26. Selecting Network I/O</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ The Virtual Machine Manager shows a graph of Network I/O for all virtual machines on your system.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_Network_IO-Displaying_Network_IO"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt29.png" width="444" alt="Displaying Network I/O" /></div></div><h6>Figure F.27. Displaying Network I/O</h6></div><br class="figure-break" /></li></ol></div></div></div><div xml:lang="en-US" class="appendix" id="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Guest disk access with offline tools</h1></div></div></div><div class="section" id="sect-introduction-Virtualization_Administration_Guide-Guest_Disks_libguestfs"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">G.1. Introduction</h2></div></div></div><div class="para">
+ Fedora comes with tools to access, edit and create guest disks or other disk images. There are several uses for these tools, including:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Viewing or downloading files located on a guest disk.
+ </div></li><li class="listitem"><div class="para">
+ Editing or uploading files onto a guest disk.
+ </div></li><li class="listitem"><div class="para">
+ Reading or writing guest configuration.
+ </div></li><li class="listitem"><div class="para">
+ Reading or writing the Windows Registry in Windows guests.
+ </div></li><li class="listitem"><div class="para">
+ Preparing new disk images containing files, directories, file systems, partitions, logical volumes and other options.
+ </div></li><li class="listitem"><div class="para">
+ Rescuing and repairing guests that fail to boot or those that need boot configuration changes.
+ </div></li><li class="listitem"><div class="para">
+ Monitoring disk usage of guests.
+ </div></li><li class="listitem"><div class="para">
+ Auditing compliance of guests, for example to organizational security standards.
+ </div></li><li class="listitem"><div class="para">
+ Deploying guests by cloning and modifying templates.
+ </div></li><li class="listitem"><div class="para">
+ Reading CD and DVD ISO and floppy disk images.
+ </div></li></ul></div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ You must <span class="bold bold"><strong>never</strong></span> use these tools to write to a guest or disk image which is attached to a running virtual machine, not even to open such a disk image in write mode. Doing so will result in disk corruption of the guest. The tools try to prevent you from doing this, however do not catch all cases. If there is any suspicion that a guest might be running, it is strongly recommended that the tools not be used, or at least <span class="bold bold"><strong>always</strong></span> use the tools in read-only mode.
+ </div></div></div></div><div class="section" id="sect-Terminology-Guest_Disks_libguestfs"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">G.2. Terminology</h2></div></div></div><div class="para">
+ This section explains the terms used throughout this chapter.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>libguestfs (GUEST FileSystem LIBrary)</strong></span> - the underlying C library that provides the basic functionality for opening disk images, reading and writing files and so on. You can write C programs directly to this API, but it is quite low level.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>guestfish (GUEST Filesystem Interactive SHell)</strong></span> is an interactive shell that you can use from the command line or from shell scripts. It exposes all of the functionality of the libguestfs API.
+ </div></li><li class="listitem"><div class="para">
+ Various virt tools are built on top of libguestfs, and these provide a way to perform specific single tasks from the command line. Tools include <span class="bold bold"><strong>virt-df</strong></span>, <span class="bold bold"><strong>virt-rescue</strong></span>, <span class="bold bold"><strong>virt-resize</strong></span> and <span class="bold bold"><strong>virt-edit</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>hivex</strong></span> and <span class="bold bold"><strong>Augeas</strong></span> are libraries for editing the Windows Registry and Linux configuration files respectively. Although these are separate from libguestfs, much of the value of libguestfs comes from the combination of these tools.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>guestmount</strong></span> is an interface between libguestfs and FUSE. It is primarily used to mount file systems from disk images on your host. This functionality is not necessary, but can be useful.
+ </div></li></ul></div></div><div class="section" id="sect-Guide-Guest_Disks_libguestfs-installation"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">G.3. Installation</h2></div></div></div><div class="para">
+ To install libguestfs, guestfish, the libguestfs tools, guestmount and support for Windows guests, subscribe to the RHEL V2WIN channel, go to the <a href="https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=631818">Fedora Website</a> and run the following command:
+ </div><pre class="screen">
+# yum install libguestfs guestfish libguestfs-tools libguestfs-mount libguestfs-winsupport
+</pre><div class="para">
+ To install every libguestfs-related package including the language bindings, run the following command:
+ </div><pre class="screen">
+# yum install '*guestf*'
+</pre></div><div class="section" id="sect-the_guestfish_shell"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">G.4. The guestfish shell</h2></div></div></div><div class="para">
+ <span class="bold bold"><strong>guestfish</strong></span> is an interactive shell that you can use from the command line or from shell scripts to access guest file systems. All of the functionality of the libguestfs API is available from the shell.
+ </div><div class="para">
+ To begin viewing or editing a virtual machine disk image, run the following command, substituting the path to your desired disk image:
+ </div><pre class="screen">
+guestfish --ro -a /path/to/disk/image
+</pre><div class="para">
+ <span class="bold bold"><strong>--ro</strong></span> means that the disk image is opened read-only. This mode is always safe but does not allow write access. Only omit this option when you are <span class="bold bold"><strong>certain</strong></span> that the guest is not running, or the disk image is not attached to a live guest. It is not possible to use libguestfs to edit a live guest, and attempting to will assuredly result in irreversible disk corruption.
+ </div><div class="para">
+ <span class="bold bold"><strong>/path/to/disk/image</strong></span> is the path to the disk. This can be a file, a host logical volume (such as /dev/VG/LV), a host device (/dev/cdrom) or a SAN LUN (/dev/sdf3).
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ libguestfs and guestfish do not require root privileges. You only need to run them as root if the disk image being accessed needs root to read and/or write.
+ </div></div></div><div class="para">
+ When you start guestfish interactively, it will display this prompt:
+ </div><pre class="screen">
+ guestfish --ro -a /path/to/disk/image
+
+Welcome to guestfish, the libguestfs filesystem interactive shell for editing virtual machine filesystems.
+
+ Type: 'help' for help on commands
+ 'man' to read the manual
+ 'quit' to quit the shell
+
+><fs>
+</pre><div class="para">
+ At the prompt, type <span class="bold bold"><strong>run</strong></span> to initiate the library and attach the disk image. This can take up to 30 seconds the first time it is done. Subsequent starts will complete much faster.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ libguestfs will use hardware virtualization acceleration such as KVM (if available) to speed up this process.
+ </div></div></div><div class="para">
+ Once the <span class="bold bold"><strong>run</strong></span> command has been entered, other commands can be used, as the following section demonstrates.
+ </div><div class="section" id="sect-Viewing_file_systems_with_guestfish"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.4.1. Viewing file systems with guestfish</h3></div></div></div><div class="section" id="sect-Manual-listing-and-viewing"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">G.4.1.1. Manual listing and viewing</h4></div></div></div><div class="para">
+ The <code class="command">list-filesystems</code> command will list file systems found by libguestfs. This output shows a Red Hat Enterprise Linux 4 disk image:
+ </div><pre class="screen">
+><fs> run
+><fs> list-filesystems
+/dev/vda1: ext3
+/dev/VolGroup00/LogVol00: ext3
+/dev/VolGroup00/LogVol01: swap
+</pre><div class="para">
+ This output shows a Windows disk image:
+ </div><pre class="screen">
+><fs> run
+><fs> list-filesystems
+/dev/vda1: ntfs
+/dev/vda2: ntfs
+</pre><div class="para">
+ Other useful commands are <code class="command">list-devices</code>, <code class="command">list-partitions</code>, <code class="command">lvs</code>, <code class="command">pvs</code>, <code class="command">vfs-type</code> and <code class="command">file</code>. You can get more information and help on any command by typing <code class="command">help</code> <span class="emphasis"><em>command</em></span>, as shown in the following output:
+ </div><pre class="screen">
+><fs> help vfs-type
+ NAME
+ vfs-type - get the Linux VFS type corresponding to a mounted device
+
+ SYNOPSIS
+ vfs-type device
+
+ DESCRIPTION
+ This command gets the filesystem type corresponding to the filesystem on
+ "device".
+
+ For most filesystems, the result is the name of the Linux VFS module
+ which would be used to mount this filesystem if you mounted it without
+ specifying the filesystem type. For example a string such as "ext3" or
+ "ntfs".
+</pre><div class="para">
+ To view the actual contents of a file system, it must first be mounted. This example uses one of the Windows partitions shown in the previous output (<code class="filename">/dev/vda2</code>), which in this case is known to correspond to the <span class="bold bold"><strong>C:\</strong></span> drive:
+ </div><pre class="screen">
+><fs> mount-ro /dev/vda2 /
+><fs> ll /
+total 1834753
+ drwxrwxrwx 1 root root 4096 Nov 1 11:40 .
+ drwxr-xr-x 21 root root 4096 Nov 16 21:45 ..
+ lrwxrwxrwx 2 root root 60 Jul 14 2009 Documents and Settings
+ drwxrwxrwx 1 root root 4096 Nov 15 18:00 Program Files
+ drwxrwxrwx 1 root root 4096 Sep 19 10:34 Users
+ drwxrwxrwx 1 root root 16384 Sep 19 10:34 Windows
+</pre><div class="para">
+ You can use guestfish commands such as <code class="command">ls</code>, <code class="command">ll</code>, <code class="command">cat</code>, <code class="command">more</code>, <code class="command">download</code> and <code class="command">tar-out</code> to view and download files and directories.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ There is no concept of a current working directory in this shell. Unlike ordinary shells, you cannot for example use the <code class="command">cd</code> command to change directories. All paths must be fully qualified starting at the top with a forward slash (<span class="bold bold"><strong>/</strong></span>) character. Use the <span class="emphasis"><em>Tab</em></span> key to complete paths.
+ </div></div></div><div class="para">
+ To exit from the guestfish shell, type <code class="command">exit</code> or enter <code class="command">Ctrl+d</code>.
+ </div></div><div class="section" id="sect-Via_guestfish_inspection"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">G.4.1.2. Via guestfish inspection</h4></div></div></div><div class="para">
+ Instead of listing and mounting file systems by hand, it is possible to let guestfish itself inspect the image and mount the file systems as they would be in the guest. To do this, add the <span class="bold bold"><strong>-i</strong></span> option on the command line:
+ </div><pre class="screen">
+guestfish --ro -a /path/to/disk/image -i
+
+Welcome to guestfish, the libguestfs filesystem interactive shell for
+ editing virtual machine filesystems.
+
+ Type: 'help' for help on commands
+ 'man' to read the manual
+ 'quit' to quit the shell
+
+ Operating system: Red Hat Enterprise Linux AS release 4 (Nahant Update 8)
+ /dev/VolGroup00/LogVol00 mounted on /
+ /dev/vda1 mounted on /boot
+
+ ><fs> ll /
+ total 210
+ drwxr-xr-x. 24 root root 4096 Oct 28 09:09 .
+ drwxr-xr-x 21 root root 4096 Nov 17 15:10 ..
+ drwxr-xr-x. 2 root root 4096 Oct 27 22:37 bin
+ drwxr-xr-x. 4 root root 1024 Oct 27 21:52 boot
+ drwxr-xr-x. 4 root root 4096 Oct 27 21:21 dev
+ drwxr-xr-x. 86 root root 12288 Oct 28 09:09 etc
+ [etc]
+</pre><div class="para">
+ Because guestfish needs to start up the libguestfs back end in order to perform the inspection and mounting, the <code class="command">run</code> command is not necessary when using the <code class="command">-i</code> option. The <code class="command">-i</code> option works for many common Linux and Windows guests.
+ </div></div><div class="section" id="sect-Accessing-aguesT-by-name"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">G.4.1.3. Accessing a guest by name</h4></div></div></div><div class="para">
+ A guest can be accessed from the command line when you specify its name as known to libvirt (in other words, as it appears in <code class="command">virsh list --all</code>). Use the <code class="command">-d</code> option to access a guest by its name, with or without the <code class="command">-i</code> option:
+ </div><pre class="screen">
+guestfish --ro -d GuestName -i
+</pre></div></div><div class="section" id="sect-Modifying-files-with-guestfish"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.4.2. Modifying files with guestfish</h3></div></div></div><div class="para">
+ To modify files, create directories or make other changes to a guest, first heed the warning at the beginning of this section: <span class="bol bol">your guest must be shut down</span>. Editing or changing a running disk with guestfish <span class="bold bold"><strong>will</strong></span> result in disk corruption. This section gives an example of editing the <code class="filename">/boot/grub/grub.conf</code> file. When you are sure the guest is shut down you can omit the <code class="command">--ro</code> flag in order to get write access via a command such as:
+ </div><pre class="screen">
+guestfish -d RHEL3 -i
+
+Welcome to guestfish, the libguestfs filesystem interactive shell for
+ editing virtual machine filesystems.
+
+ Type: 'help' for help on commands
+ 'man' to read the manual
+ 'quit' to quit the shell
+
+ Operating system: Red Hat Enterprise Linux AS release 3 (Taroon Update 9)
+ /dev/vda2 mounted on /
+ /dev/vda1 mounted on /boot
+
+><fs> edit /boot/grub/grub.conf
+</pre><div class="para">
+ Commands to edit files include <code class="command">edit</code>, <code class="command">vi</code> and <code class="command">emacs</code>. Many commands also exist for creating files and directories, such as <code class="command">write</code>, <code class="command">mkdir</code>, <code class="command">upload</code> and <code class="command">tar-in</code>.
+ </div></div><div class="section" id="sect-Other-actions-with-guestfish"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.4.3. Other actions with guestfish</h3></div></div></div><div class="para">
+ You can also format file systems, create partitions, create and resize LVM logical volumes and much more, with commands such as <code class="command">mkfs</code>, <code class="command">part-add</code>, <code class="command">lvresize</code>, <code class="command">lvcreate</code>, <code class="command">vgcreate</code> and <code class="command">pvcreate</code>.
+ </div></div><div class="section" id="sect-Shell-scripting-with-guestfish"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.4.4. Shell scripting with guestfish</h3></div></div></div><div class="para">
+ Once you are familiar with using guestfish interactively, according to your needs, writing shell scripts with it may be useful. The following is a simple shell script to add a new MOTD (message of the day) to a guest:
+ </div><pre class="screen">
+#!/bin/bash -
+ set -e
+ guestname="$1"
+
+ guestfish -d "$guestname" -i <<'EOF'
+ write /etc/motd "Welcome to Acme Incorporated."
+ chmod 0644 /etc/motd
+ EOF
+</pre></div><div class="section" id="sect-Augeas-and-libguestfs-scripting"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.4.5. Augeas and libguestfs scripting</h3></div></div></div><div class="para">
+ Combining libguestfs with Augeas can help when writing scripts to manipulate Linux guest configuration. For example, the following script uses Augeas to parse the keyboard configuration of a guest, and to print out the layout. Note that this example only works with guests running Red Hat Enterprise Linux:
+ </div><pre class="screen">
+#!/bin/bash -
+ set -e
+ guestname="$1"
+
+ guestfish -d "$1" -i --ro <<'EOF'
+ aug-init / 0
+ aug-get /files/etc/sysconfig/keyboard/LAYOUT
+ EOF
+</pre><div class="para">
+ Augeas can also be used to modify configuration files. You can modify the above script to <span class="bold bold"><strong>change</strong></span> the keyboard layout:
+ </div><pre class="screen">
+#!/bin/bash -
+ set -e
+ guestname="$1"
+
+ guestfish -d "$1" -i <<'EOF'
+ aug-init / 0
+ aug-set /files/etc/sysconfig/keyboard/LAYOUT '"gb"'
+ aug-save
+ EOF
+</pre><div class="para">
+ Note the three changes between the two scripts:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ The <code class="command">--ro</code> option has been removed in the second example, giving the ability to write to the guest.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="command">aug-get</code> command has been changed to <code class="command">aug-set</code> to modify the value instead of fetching it. The new value will be <code class="command">"gb"</code> (including the quotes).
+ </div></li><li class="listitem"><div class="para">
+ The <code class="command">aug-save</code> command is used here so Augeas will write the changes out to disk.
+ </div></li></ol></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ More information about Augeas can be found on the website <a href="http://augeas.net">http://augeas.net</a>.
+ </div></div></div><div class="para">
+ guestfish can do much more than we can cover in this introductory document. For example, creating disk images from scratch:
+ </div><pre class="screen">
+guestfish -N fs
+</pre><div class="para">
+ Or copying out whole directories from a disk image:
+ </div><pre class="screen">
+><fs> copy-out /home /tmp/home
+</pre><div class="para">
+ For more information see the man page guestfish(1).
+ </div></div></div><div class="section" id="sect-other-commands"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">G.5. Other commands</h2></div></div></div><div class="para">
+ This section describes tools that are simpler equivalents to using guestfish to view and edit guest disk images.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">virt-cat</code> is similar to the guestfish <code class="command">download</code> command. It downloads and displays a single file to the guest. For example:
+ </div><pre class="screen">
+# virt-cat RHEL3 /etc/ntp.conf | grep ^server
+ server 127.127.1.0 # local clock
+</pre></li><li class="listitem"><div class="para">
+ <code class="command">virt-edit</code> is similar to the guestfish <code class="command">edit</code> command. It can be used to interactively edit a single file within a guest. For example, you may need to edit the <code class="filename">grub.conf</code> file in a Linux-based guest that will not boot:
+ </div><pre class="screen">
+# virt-edit LinuxGuest /boot/grub/grub.conf
+</pre><div class="para">
+ <code class="command">virt-edit</code> has another mode where it can be used to make simple non-interactive changes to a single file. For this, the <span class="bold bold"><strong>-e</strong></span> option is used. This command, for example, changes the root password in a Linux guest to having no password:
+ </div><pre class="screen">
+# virt-edit LinuxGuest /etc/passwd -e 's/^root:.*?:/root::/'
+</pre></li><li class="listitem"><div class="para">
+ <code class="command">virt-ls</code> is similar to the guestfish <code class="command">ls</code>, <code class="command">ll</code> and <code class="command">find</code> commands. It is used to list a directory or directories (recursively). For example, the following command would recursively list files and directories under /home in a Linux guest:
+ </div><pre class="screen">
+# virt-ls -R LinuxGuest /home/ | less
+</pre></li></ul></div></div><div class="section" id="sect-virt-rescue"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">G.6. virt-rescue: The rescue shell</h2></div></div></div><div class="section" id="sect-virt-rescue-intro"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.6.1. Introduction</h3></div></div></div><div class="para">
+ This section describes <code class="command">virt-rescue</code>, which can be considered analogous to a rescue CD for virtual machines. It boots a guest into a rescue shell so that maintenance can be performed to correct errors and the guest can be repaired.
+ </div><div class="para">
+ There is some overlap between virt-rescue and guestfish. It is important to distinguish their differing uses. virt-rescue is for making interactive, ad-hoc changes using ordinary Linux file system tools. It is particularly suited to rescuing a guest that has gone wrong. virt-rescue cannot be scripted.
+ </div><div class="para">
+ In contrast, guestfish is particularly useful for making scripted, structured changes through a formal set of commands (the libguestfs API), although it can also be used interactively.
+ </div></div><div class="section" id="sect-run-virt-rescue"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.6.2. Running virt-rescue</h3></div></div></div><div class="para">
+ Before you use <code class="command">virt-rescue</code> on a guest, make sure the guest is not running, otherwise disk corruption will occur. When you are sure the guest is not live, enter:
+ </div><pre class="screen">
+virt-rescue GuestName
+</pre><div class="para">
+ (where GuestName is the guest name as known to libvirt), or:
+ </div><pre class="screen">
+virt-rescue /path/to/disk/image
+</pre><div class="para">
+ (where the path can be any file, any logical volume, LUN, or so on) containing a guest disk.
+ </div><div class="para">
+ You will first see output scroll past, as virt-rescue boots the rescue VM. In the end you will see:
+ </div><pre class="screen">
+Welcome to virt-rescue, the libguestfs rescue shell.
+
+ Note: The contents of / are the rescue appliance.
+ You have to mount the guest's partitions under /sysroot
+ before you can examine them.
+
+ bash: cannot set terminal process group (-1): Inappropriate ioctl for device
+ bash: no job control in this shell
+ ><rescue>
+</pre><div class="para">
+ The shell prompt here is an ordinary bash shell, and a reduced set of ordinary Fedora commands is available. For example, you can enter:
+ </div><pre class="screen">
+><rescue> fdisk -l /dev/vda
+</pre><div class="para">
+ The previous command will list disk partitions. To mount a file system, it is suggested that you mount it under <code class="filename">/sysroot</code>, which is an empty directory in the rescue machine for the user to mount anything you like. Note that the files under <code class="filename">/</code> are files from the rescue VM itself:
+ </div><pre class="screen">
+><rescue> mount /dev/vda1 /sysroot/
+EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
+><rescue> ls -l /sysroot/grub/
+ total 324
+ -rw-r--r--. 1 root root 63 Sep 16 18:14 device.map
+ -rw-r--r--. 1 root root 13200 Sep 16 18:14 e2fs_stage1_5
+ -rw-r--r--. 1 root root 12512 Sep 16 18:14 fat_stage1_5
+ -rw-r--r--. 1 root root 11744 Sep 16 18:14 ffs_stage1_5
+ -rw-------. 1 root root 1503 Oct 15 11:19 grub.conf
+ [...]
+</pre><div class="para">
+ When you are finished rescuing the guest, exit the shell by entering <code class="command">exit</code> or <code class="command">Ctrl+d</code>.
+ </div><div class="para">
+ <code class="command">virt-rescue</code> has many command line options. The options most often used are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>--ro</strong></span>: Operate in read-only mode on the guest. No changes will be saved. You can use this to experiment with the guest. As soon as you exit from the shell, all of your changes are discarded.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>--network</strong></span>: Enable network access from the rescue shell. Use this if you need to, for example, download RPM or other files into the guest.
+ </div></li></ul></div></div></div><div class="section" id="sect-virt-df"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">G.7. virt-df: Monitoring disk usage</h2></div></div></div><div class="section" id="sect-virt-df-intro"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.7.1. Introduction</h3></div></div></div><div class="para">
+ This section describes <code class="command">virt-df</code>, which displays file system usage from a disk image or a guest. It is similar to the Linux <code class="command">df</code> command, but for virtual machines.
+ </div></div><div class="section" id="run-virt-df"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.7.2. Running virt-df</h3></div></div></div><div class="para">
+ To display file system usage for all file systems found in a disk image, enter the following:
+ </div><pre class="screen">
+# virt-df /dev/vg_guests/RHEL6
+ Filesystem 1K-blocks Used Available Use%
+ RHEL6:/dev/sda1 101086 10233 85634 11%
+ RHEL6:/dev/VolGroup00/LogVol00 7127864 2272744 4493036 32%
+</pre><div class="para">
+ (Where <code class="filename">/dev/vg_guests/RHEL6</code> is a Red Hat Enterprise Linux 4 guest disk image. The path in this case is the host logical volume where this disk image is located.)
+ </div><div class="para">
+ You can also use <code class="command">virt-df</code> on its own to list information about all of your guests (ie. those known to libvirt). The <code class="command">virt-df</code> command recognizes some of the same options as the standard <code class="command">df</code> such as <code class="command">-h</code> (human-readable) and <code class="command">-i</code> (show inodes instead of blocks).
+ </div><div class="para">
+ <code class="command">virt-df</code> also works on Windows guests:
+ </div><pre class="screen">
+# virt-df -h
+ Filesystem Size Used Available Use%
+ F14x64:/dev/sda1 484.2M 66.3M 392.9M 14%
+ F14x64:/dev/vg_f14x64/lv_root 7.4G 3.0G 4.4G 41%
+ RHEL6brewx64:/dev/sda1 484.2M 52.6M 406.6M 11%
+ RHEL6brewx64:/dev/vg_rhel6brewx64/lv_root
+ 13.3G 3.4G 9.2G 26%
+ Win7x32:/dev/sda1 100.0M 24.1M 75.9M 25%
+ Win7x32:/dev/sda2 19.9G 7.4G 12.5G 38%
+</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ You can use <code class="command">virt-df</code> safely on live guests, since it only needs read-only access. However, you should not expect the numbers to be precisely the same as those from a <code class="command">df</code> command running inside the guest. This is because what is on disk will be slightly out of synch with the state of the live guest. Nevertheless it should be a good enough approximation for analysis and monitoring purposes.
+ </div></div></div><div class="para">
+ virt-df is designed to allow you to integrate the statistics into monitoring tools, databases and so on. This allows system administrators to generate reports on trends in disk usage, and alerts if a guest is about to run out of disk space. To do this you should use the <code class="command">--csv</code> option to generate machine-readable Comma-Separated-Values (CSV) output. CSV output is readable by most databases, spreadsheet software and a variety of other tools and programming languages. The raw CSV looks like the following:
+ </div><pre class="screen">
+# virt-df --csv WindowsGuest
+ Virtual Machine,Filesystem,1K-blocks,Used,Available,Use%
+ Win7x32,/dev/sda1,102396,24712,77684,24.1%
+ Win7x32,/dev/sda2,20866940,7786652,13080288,37.3%
+</pre><div class="para">
+ For resources and ideas on how to process this output to produce trends and alerts, refer to the following URL: <a href=" http://virt-tools.org/learning/advanced-virt-df/"> http://virt-tools.org/learning/advanced-virt-df/</a>.
+ </div></div></div><div class="section" id="sect-virt-resize"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">G.8. virt-resize: resizing guests offline</h2></div></div></div><div class="section" id="sect-virt-resize-intro"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.8.1. Introduction</h3></div></div></div><div class="para">
+ This section describes <code class="command">virt-resize</code>, a tool for expanding or shrinking guests. It only works for guests which are offline (shut down). It works by copying the guest image and leaving the original disk image untouched. This is ideal because you can use the original image as a backup, however there is a trade-off as you need twice the amount of disk space.
+ </div></div><div class="section" id="sect-expand-disk-image"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.8.2. Expanding a disk image</h3></div></div></div><div class="para">
+ This section demonstrates a simple case of expanding a disk image:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Locate the disk image to be resized. You can use the command <code class="command">virsh dumpxml GuestName</code> for a libvirt guest.
+ </div></li><li class="listitem"><div class="para">
+ Decide on how you wish to expand the guest. Run <code class="command">virt-df -h</code> and <code class="command">virt-list-partitions -lh</code> on the guest disk, as shown in the following output:
+ </div><pre class="screen">
+# virt-df -h /dev/vg_guests/RHEL6
+Filesystem Size Used Available Use%
+RHEL6:/dev/sda1 98.7M 10.0M 83.6M 11%
+RHEL6:/dev/VolGroup00/LogVol00 6.8G 2.2G 4.3G 32%
+
+# virt-list-partitions -lh /dev/vg_guests/RHEL6
+/dev/sda1 ext3 101.9M
+/dev/sda2 pv 7.9G
+</pre></li></ol></div><div class="para">
+ This example will demonstrate how to:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Increase the size of the first (boot) partition, from approximately 100MB to 500MB.
+ </div></li><li class="listitem"><div class="para">
+ Increase the total disk size from 8GB to 16GB.
+ </div></li><li class="listitem"><div class="para">
+ Expand the second partition to fill the remaining space.
+ </div></li><li class="listitem"><div class="para">
+ Expand <code class="filename">/dev/VolGroup00/LogVol00</code> to fill the new space in the second partition.
+ </div></li></ul></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Make sure the guest is shut down.
+ </div></li><li class="listitem"><div class="para">
+ Rename the original disk as the backup. How you do this depends on the host storage environment for the original disk. If it is stored as a file, use the <code class="command">mv</code> command. For logical volumes (as demonstrated in this example), use <code class="command">lvrename</code>:
+ </div><pre class="screen">
+# lvrename /dev/vg_guests/RHEL6 /dev/vg_guests/RHEL6.backup
+</pre></li><li class="listitem"><div class="para">
+ Create the new disk. The requirements in this example are to expand the total disk size up to 16GB. Since logical volumes are used here, the following command is used:
+ </div><pre class="screen">
+# lvcreate -L 16G -n RHEL6 /dev/vg_guests
+Logical volume "RHEL6" created
+</pre></li><li class="listitem"><div class="para">
+ The requirements from step 2 are expressed by this command:
+ </div><pre class="screen">
+# virt-resize \
+ /dev/vg_guests/RHEL6.backup /dev/vg_guests/RHEL6 \
+ --resize /dev/sda1=500M \
+ --expand /dev/sda2 \
+ --LV-expand /dev/VolGroup00/LogVol00
+</pre><div class="para">
+ The first two arguments are the input disk and output disk. <code class="command">--resize /dev/sda1=500M</code> resizes the first partition up to 500MB. <code class="command">--expand /dev/sda2</code> expands the second partition to fill all remaining space. <code class="command">--LV-expand /dev/VolGroup00/LogVol00</code> expands the guest logical volume to fill the extra space in the second partition.
+ </div><div class="para">
+ <code class="command">virt-resize</code> describes what it is doing in the output:
+ </div><pre class="screen">
+Summary of changes:
+ /dev/sda1: partition will be resized from 101.9M to 500.0M
+ /dev/sda1: content will be expanded using the 'resize2fs' method
+ /dev/sda2: partition will be resized from 7.9G to 15.5G
+ /dev/sda2: content will be expanded using the 'pvresize' method
+ /dev/VolGroup00/LogVol00: LV will be expanded to maximum size
+ /dev/VolGroup00/LogVol00: content will be expanded using the 'resize2fs' method
+ Copying /dev/sda1 ...
+ [#####################################################]
+ Copying /dev/sda2 ...
+ [#####################################################]
+ Expanding /dev/sda1 using the 'resize2fs' method
+ Expanding /dev/sda2 using the 'pvresize' method
+ Expanding /dev/VolGroup00/LogVol00 using the 'resize2fs' method
+</pre></li><li class="listitem"><div class="para">
+ Try to boot the virtual machine. If it works (and after testing it thoroughly) you can delete the backup disk. If it fails, shut down the virtual machine, delete the new disk, and rename the backup disk back to its original name.
+ </div></li><li class="listitem"><div class="para">
+ Use <code class="command">virt-df</code> and/or <code class="command">virt-list-partitions</code> to show the new size:
+ </div><pre class="screen">
+# virt-df -h /dev/vg_pin/RHEL6
+ Filesystem Size Used Available Use%
+ RHEL6:/dev/sda1 484.4M 10.8M 448.6M 3%
+ RHEL6:/dev/VolGroup00/LogVol00 14.3G 2.2G 11.4G 16%
+</pre></li></ol></div><div class="para">
+ Resizing guests is not an exact science. If <code class="command">virt-resize</code> fails, there are a number of tips that you can review and attempt in the virt-resize(1) man page. For some older Red Hat Enterprise Linux guests, you may need to pay particular attention to the tip regarding GRUB.
+ </div></div></div><div class="section" id="sect-virt-inspector"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">G.9. virt-inspector: inspecting guests</h2></div></div></div><div class="section" id="sect-virt-inspector-intro"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.9.1. Introduction</h3></div></div></div><div class="para">
+ <code class="command">virt-inspector</code> is a tool for inspecting a disk image to find out what operating system it contains.
+ </div></div><div class="section" id="sect-virt-inspector-install"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.9.2. Installation</h3></div></div></div><div class="para">
+ To install virt-inspector and the documentation, enter the following command:
+ </div><pre class="screen">
+# yum install libguestfs-tools libguestfs-devel
+</pre><div class="para">
+ To process Windows guests you must also install <span class="package">libguestfs-winsupport</span>. Refer to <a class="xref" href="#sect-virt-win-reg-install">Section G.10.2, “Installation”</a> for details. The documentation, including example XML output and a Relax-NG schema for the output, will be installed in <code class="filename">/usr/share/doc/libguestfs-devel-*/</code> where "*" is replaced by the version number of libguestfs.
+ </div></div><div class="section" id="sect-virt-inspector-run"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.9.3. Running virt-inspector</h3></div></div></div><div class="para">
+ You can run <code class="command">virt-inspector</code> against any disk image or libvirt guest as shown in the following example:
+ </div><pre class="screen">
+virt-inspector --xml disk.img > report.xml
+</pre><div class="para">
+ Or as shown here:
+ </div><pre class="screen">
+virt-inspector --xml GuestName > report.xml
+</pre><div class="para">
+ The result will be an XML report (<code class="filename">report.xml</code>). The main components of the XML file are a top-level <operatingsytems> element containing usually a single <operatingsystem> element, similar to the following:
+ </div><pre class="screen">
+ <operatingsystems>
+ <operatingsystem>
+
+ <!-- the type of operating system and Linux distribution -->
+ <name>linux</name>
+ <distro>rhel</distro>
+ <!-- the name, version and architecture -->
+ <product_name>Red Hat Enterprise Linux Server release 6.4 </product_name>
+ <major_version>6</major_version>
+ <minor_version>4</minor_version>
+ <package_format>rpm</package_format>
+ <package_management>yum</package_management>
+ <root>/dev/VolGroup/lv_root</root>
+ <!-- how the filesystems would be mounted when live -->
+ <mountpoints>
+ <mountpoint dev="/dev/VolGroup/lv_root">/</mountpoint>
+ <mountpoint dev="/dev/sda1">/boot</mountpoint>
+ <mountpoint dev="/dev/VolGroup/lv_swap">swap</mountpoint>
+ </mountpoints>
+
+ < !-- filesystems-->
+ <filesystem dev="/dev/VolGroup/lv_root">
+ <label></label>
+ <uuid>b24d9161-5613-4ab8-8649-f27a8a8068d3</uuid>
+ <type>ext4</type>
+ <content>linux-root</content>
+ <spec>/dev/mapper/VolGroup-lv_root</spec>
+ </filesystem>
+ <filesystem dev="/dev/VolGroup/lv_swap">
+ <type>swap</type>
+ <spec>/dev/mapper/VolGroup-lv_swap</spec>
+ </filesystem>
+ <!-- packages installed -->
+ <applications>
+ <application>
+ <name>firefox</name>
+ <version>3.5.5</version>
+ <release>1.fc12</release>
+ </application>
+ </applications>
+
+ </operatingsystem>
+ </operatingsystems>
+</pre><div class="para">
+ Processing these reports is best done using W3C standard XPath queries. Fedora comes with a command line program (<code class="command">xpath</code>) which can be used for simple instances; however, for long-term and advanced usage, you should consider using an XPath library along with your favorite programming language.
+ </div><div class="para">
+ As an example, you can list out all file system devices using the following XPath query:
+ </div><pre class="screen">
+virt-inspector --xml GuestName | xpath //filesystem/@dev
+ Found 3 nodes:
+ -- NODE --
+ dev="/dev/sda1"
+ -- NODE --
+ dev="/dev/vg_f12x64/lv_root"
+ -- NODE --
+ dev="/dev/vg_f12x64/lv_swap"
+</pre><div class="para">
+ Or list the names of all applications installed by entering:
+ </div><pre class="screen">
+ virt-inspector --xml GuestName | xpath //application/name
+ [...long list...]
+</pre></div></div><div class="section" id="sect-virt-win-reg"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">G.10. virt-win-reg: Reading and editing the Windows Registry</h2></div></div></div><div class="section" id="sect-virt-win-reg-intro"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.10.1. Introduction</h3></div></div></div><div class="para">
+ <code class="command">virt-win-reg</code> is a tool that manipulates the Registry in Windows guests. It can be used to read out registry keys. You can also use it to make changes to the Registry, but you must <span class="bold bold"><strong>never</strong></span> try to do this for live/running guests, as it will result in disk corruption.
+ </div></div><div class="section" id="sect-virt-win-reg-install"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.10.2. Installation</h3></div></div></div><div class="para">
+ To use <code class="command">virt-win-reg</code> you must run the following:
+ </div><pre class="screen">
+# yum install libguestfs-tools libguestfs-winsupport
+</pre></div><div class="section" id="sect-virt-win-reg-use"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.10.3. Using virt-win-reg</h3></div></div></div><div class="para">
+ To read out Registry keys, specify the name of the guest (or its disk image) and the name of the Registry key. You must use single quotes to surround the name of the desired key:
+ </div><pre class="screen">
+# virt-win-reg WindowsGuest \
+ 'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall' \
+ | less
+</pre><div class="para">
+ The output is in the standard text-based format used by <code class="filename">.REG</code> files on Windows.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Hex-quoting is used for strings because the format does not properly define a portable encoding method for strings. This is the only way to ensure fidelity when transporting <code class="filename">.REG</code> files from one machine to another.
+ </div><div class="para">
+ You can make hex-quoted strings printable by piping the output of <code class="command">virt-win-reg</code> through this simple Perl script:
+ </div><pre class="screen">perl -MEncode -pe's?hex\((\d+)\):(\S+)?$t=$1;$_=$2;s,\,,,g;"str($t):\"".decode(utf16le=>pack("H*",$_))."\""?eg'
+</pre></div></div><div class="para">
+ To merge changes into the Windows Registry of an offline guest, you must first prepare a <code class="filename">.REG</code> file. There is a great deal of documentation about doing this available from MSDN, and there is a good summary in the following Wikipedia page: <a href="https://secure.wikimedia.org/wikipedia/en/wiki/Windows_Registry#.REG_files">https://secure.wikimedia.org/wikipedia/en/wiki/Windows_Registry#.REG_files</a>. When you have prepared a <code class="filename">.REG</code> file, enter the following:
+ </div><pre class="screen">
+# virt-win-reg --merge WindowsGuest input.reg
+</pre><div class="para">
+ This will update the registry in the guest.
+ </div></div></div><div class="section" id="sect-Using-API-Programming-Languages"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">G.11. Using the API from Programming Languages</h2></div></div></div><div class="para">
+ The libguestfs API can be used directly from the following languages in Fedora 19: C, C++, Perl, Python, Java, Ruby and OCaml.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ To install C and C++ bindings, enter the following command:
+ </div><pre class="screen">
+# yum install libguestfs-devel
+</pre></li><li class="listitem"><div class="para">
+ To install Perl bindings:
+ </div><pre class="screen">
+# yum install 'perl(Sys::Guestfs)'
+</pre></li><li class="listitem"><div class="para">
+ To install Python bindings:
+ </div><pre class="screen">
+# yum install python-libguestfs
+</pre></li><li class="listitem"><div class="para">
+ To install Java bindings:
+ </div><pre class="screen">
+# yum install libguestfs-java libguestfs-java-devel libguestfs-javadoc
+</pre></li><li class="listitem"><div class="para">
+ To install Ruby bindings:
+ </div><pre class="screen">
+# yum install ruby-libguestfs
+</pre></li><li class="listitem"><div class="para">
+ To install OCaml bindings:
+ </div><pre class="screen">
+# yum install ocaml-libguestfs ocaml-libguestfs-devel
+</pre></li></ul></div><div class="para">
+ The binding for each language is essentially the same, but with minor syntactic changes. A C statement:
+ </div><pre class="screen">
+guestfs_launch (g);
+</pre><div class="para">
+ Would appear like the following in Perl:
+ </div><pre class="screen">
+$g->launch ()
+</pre><div class="para">
+ Or like the following in OCaml:
+ </div><pre class="screen">
+g#launch ()
+</pre><div class="para">
+ Only the API from C is detailed in this section.
+ </div><div class="para">
+ In the C and C++ bindings, you must manually check for errors. In the other bindings, errors are converted into exceptions; the additional error checks shown in the examples below are not necessary for other languages, but conversely you may wish to add code to catch exceptions. Refer to the following list for some points of interest regarding the architecture of the libguestfs API:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The libguestfs API is synchronous. Each call blocks until it has completed. If you want to make calls asynchronously, you have to create a thread.
+ </div></li><li class="listitem"><div class="para">
+ The libguestfs API is not thread safe: each handle should be used only from a single thread, or if you want to share a handle between threads you should implement your own mutex to ensure that two threads cannot execute commands on one handle at the same time.
+ </div></li><li class="listitem"><div class="para">
+ You should not open multiple handles on the same disk image. It is permissible if all the handles are read-only, but still not recommended.
+ </div></li><li class="listitem"><div class="para">
+ You should not add a disk image for writing if anything else could be using that disk image (eg. a live VM). Doing this will cause disk corruption.
+ </div></li><li class="listitem"><div class="para">
+ Opening a read-only handle on a disk image which is currently in use (eg. by a live VM) is possible; however, the results may be unpredictable or inconsistent particularly if the disk image is being heavily written to at the time you are reading it.
+ </div></li></ul></div><div class="section" id="API-and-C"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.11.1. Interaction with the API via a C program</h3></div></div></div><div class="para">
+ Your C program should start by including the <guestfs.h> header file, and creating a handle:
+ </div><pre class="screen">
+#include <stdio.h>
+#include <stdlib.h>
+#include <guestfs.h>
+
+int
+main (int argc, char *argv[])
+{
+ guestfs_h *g;
+
+ g = guestfs_create ();
+ if (g == NULL) {
+ perror ("failed to create libguestfs handle");
+ exit (EXIT_FAILURE);
+ }
+
+ /* ... */
+
+ guestfs_close (g);
+
+ exit (EXIT_SUCCESS);
+ }
+</pre><div class="para">
+ Save this program to a file (<code class="filename">test.c</code>). Compile this program and run it with the following two commands:
+ </div><pre class="screen">
+gcc -Wall test.c -o test -lguestfs
+./test
+</pre><div class="para">
+ At this stage it should print no output. The rest of this section demonstrates an example showing how to extend this program to create a new disk image, partition it, format it with an ext4 file system, and create some files in the file system. The disk image will be called <code class="filename">disk.img</code> and be created in the current directory.
+ </div><div class="para">
+ The outline of the program is:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Create the handle.
+ </div></li><li class="listitem"><div class="para">
+ Add disk(s) to the handle.
+ </div></li><li class="listitem"><div class="para">
+ Launch the libguestfs back end.
+ </div></li><li class="listitem"><div class="para">
+ Create the partition, file system and files.
+ </div></li><li class="listitem"><div class="para">
+ Close the handle and exit.
+ </div></li></ul></div><div class="para">
+ Here is the modified program:
+ </div><pre class="screen">
+#include <stdio.h>
+#include <stdlib.h>
+#include <string.h>
+#include <fcntl.h>
+#include <unistd.h>
+#include <guestfs.h>
+
+ int
+ main (int argc, char *argv[])
+ {
+ guestfs_h *g;
+ size_t i;
+
+ g = guestfs_create ();
+ if (g == NULL) {
+ perror ("failed to create libguestfs handle");
+ exit (EXIT_FAILURE);
+ }
+
+ /* Create a raw-format sparse disk image, 512 MB in size. */
+ int fd = open ("disk.img", O_CREAT|O_WRONLY|O_TRUNC|O_NOCTTY, 0666);
+ if (fd == -1) {
+ perror ("disk.img");
+ exit (EXIT_FAILURE);
+ }
+ if (ftruncate (fd, 512 * 1024 * 1024) == -1) {
+ perror ("disk.img: truncate");
+ exit (EXIT_FAILURE);
+ }
+ if (close (fd) == -1) {
+ perror ("disk.img: close");
+ exit (EXIT_FAILURE);
+ }
+
+ /* Set the trace flag so that we can see each libguestfs call. */
+ guestfs_set_trace (g, 1);
+
+ /* Set the autosync flag so that the disk will be synchronized
+ * automatically when the libguestfs handle is closed.
+ */
+ guestfs_set_autosync (g, 1);
+
+ /* Add the disk image to libguestfs. */
+ if (guestfs_add_drive_opts (g, "disk.img",
+ GUESTFS_ADD_DRIVE_OPTS_FORMAT, "raw", /* raw format */
+ GUESTFS_ADD_DRIVE_OPTS_READONLY, 0, /* for write */
+ -1 /* this marks end of optional arguments */ )
+ == -1)
+ exit (EXIT_FAILURE);
+
+ /* Run the libguestfs back-end. */
+ if (guestfs_launch (g) == -1)
+ exit (EXIT_FAILURE);
+
+ /* Get the list of devices. Because we only added one drive
+ * above, we expect that this list should contain a single
+ * element.
+ */
+ char **devices = guestfs_list_devices (g);
+ if (devices == NULL)
+ exit (EXIT_FAILURE);
+ if (devices[0] == NULL || devices[1] != NULL) {
+ fprintf (stderr,
+ "error: expected a single device from list-devices\n");
+ exit (EXIT_FAILURE);
+ }
+
+ /* Partition the disk as one single MBR partition. */
+ if (guestfs_part_disk (g, devices[0], "mbr") == -1)
+ exit (EXIT_FAILURE);
+
+ /* Get the list of partitions. We expect a single element, which
+ * is the partition we have just created.
+ */
+ char **partitions = guestfs_list_partitions (g);
+ if (partitions == NULL)
+ exit (EXIT_FAILURE);
+ if (partitions[0] == NULL || partitions[1] != NULL) {
+ fprintf (stderr,
+ "error: expected a single partition from list-partitions\n");
+ exit (EXIT_FAILURE);
+ }
+
+ /* Create an ext4 filesystem on the partition. */
+ if (guestfs_mkfs (g, "ext4", partitions[0]) == -1)
+ exit (EXIT_FAILURE);
+
+ /* Now mount the filesystem so that we can add files. */
+ if (guestfs_mount_options (g, "", partitions[0], "/") == -1)
+ exit (EXIT_FAILURE);
+
+ /* Create some files and directories. */
+ if (guestfs_touch (g, "/empty") == -1)
+ exit (EXIT_FAILURE);
+
+ const char *message = "Hello, world\n";
+ if (guestfs_write (g, "/hello", message, strlen (message)) == -1)
+ exit (EXIT_FAILURE);
+
+ if (guestfs_mkdir (g, "/foo") == -1)
+ exit (EXIT_FAILURE);
+
+ /* This uploads the local file /etc/resolv.conf into the disk image. */
+ if (guestfs_upload (g, "/etc/resolv.conf", "/foo/resolv.conf") == -1)
+ exit (EXIT_FAILURE);
+
+ /* Because 'autosync' was set (above) we can just close the handle
+ * and the disk contents will be synchronized. You can also do
+ * this manually by calling guestfs_umount_all and guestfs_sync.
+ */
+ guestfs_close (g);
+
+ /* Free up the lists. */
+ for (i = 0; devices[i] != NULL; ++i)
+ free (devices[i]);
+ free (devices);
+ for (i = 0; partitions[i] != NULL; ++i)
+ free (partitions[i]);
+ free (partitions);
+
+ exit (EXIT_SUCCESS);
+ }
+</pre><div class="para">
+ Compile and run this program with the following two commands:
+ </div><pre class="screen">
+gcc -Wall test.c -o test -lguestfs
+./test
+</pre><div class="para">
+ If the program runs to completion successfully then you should be left with a disk image called <code class="filename">disk.img</code>, which you can examine with guestfish:
+ </div><pre class="screen">
+guestfish --ro -a disk.img -m /dev/sda1
+><fs> ll /
+><fs> cat /foo/resolv.conf
+</pre><div class="para">
+ By default (for C and C++ bindings only), libguestfs prints errors to stderr. You can change this behavior by setting an error handler. The guestfs(3) man page discusses this in detail.
+ </div></div></div><div class="section" id="sect-libguestfs-troubleshoot"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">G.12. Troubleshooting</h2></div></div></div><div class="para">
+ A test tool is available to check that libguestfs is working. Run the following command after installing libguestfs (root access not required) to test for normal operation:
+ </div><pre class="screen">
+$ libguestfs-test-tool
+</pre><div class="para">
+ This tool prints a large amount of text to test the operation of libguestfs. If the test is successful, the following text will appear near the end of the output:
+ </div><pre class="screen">===== TEST FINISHED OK =====</pre></div><div class="section" id="sect-libguestfs-more-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">G.13. Where to find further documentation</h2></div></div></div><div class="para">
+ The primary source for documentation for libguestfs and the tools are the Unix man pages. The API is documented in guestfs(3). guestfish is documented in guestfish(1). The virt tools are documented in their own man pages (eg. virt-df(1)).
+ </div></div></div><div xml:lang="en-US" class="appendix" id="chap-Virtualization_Administration_Guide-Virtual_Networking" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Virtual Networking</h1></div></div></div><div class="para">
+ This chapter introduces the concepts needed to create, start, stop, remove, and modify virtual networks with libvirt.
+ </div><div class="para">
+ Additional information can be found in the libvirt reference chapter
+ </div><div class="section" id="sect-virtual_network-switches-livbvirt"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">H.1. Virtual network switches</h2></div></div></div><div class="para">
+ Libvirt virtual networking uses the concept of a <span class="emphasis"><em>virtual network switch</em></span>. A virtual network switch is a software construct that operates on a host server, to which virtual machines (guests) connect. The network traffic for a guest is directed through this switch:
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-Switch_with_two_guests"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-02-switchandtwoguests.png" alt="Virtual network switch with two guests" /></div></div><h6>Figure H.1. Virtual network switch with two guests</h6></div><br class="figure-break" /><div class="para">
+ Linux host servers represent a virtual network switch as a network interface. When the libvirtd daemon (<code class="command">libvirtd</code>) is first installed and started, the default network interface representing the virtual network switch is <code class="command">virbr0</code>.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-Linux_host_with_switch"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-03-hostwithswitch.png" alt="Linux host with an interface to a virtual network switch" /></div></div><h6>Figure H.2. Linux host with an interface to a virtual network switch</h6></div><br class="figure-break" /><div class="para">
+ This <code class="command">virbr0</code> interface can be viewed with the <code class="command">ifconfig</code> and <code class="command">ip</code> commands like any other interface:
+ </div><pre class="screen">
+$ ifconfig virbr0
+ virbr0 Link encap:Ethernet HWaddr 1B:C4:94:CF:FD:17
+ inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
+ UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
+ RX packets:0 errors:0 dropped:0 overruns:0 frame:0
+ TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
+ collisions:0 txqueuelen:0
+ RX bytes:0 (0.0 b) TX bytes:3097 (3.0 KiB)
+</pre><pre class="screen">
+ $ ip addr show virbr0
+ 3: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
+ link/ether 1b:c4:94:cf:fd:17 brd ff:ff:ff:ff:ff:ff
+ inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
+</pre></div><div class="section" id="sect-Network_Address_Translation-libvirt"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">H.2. Network Address Translation</h2></div></div></div><div class="para">
+ By default, virtual network switches operate in NAT mode. They use IP masquerading rather than SNAT (Source-NAT) or DNAT (Destination-NAT). IP masquerading enables connected guests to use the host IP address for communication to any external network. By default, computers that are placed externally to the host cannot communicate to the guests inside when the virtual network switch is operating in NAT mode, as shown in the following diagram:
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-Network_Address_Translation-Switch_in_NAT_mode_with_two_guests"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-04-hostwithnatswitch.png" width="444" alt="Virtual network switch using NAT with two guests" /></div></div><h6>Figure H.3. Virtual network switch using NAT with two guests</h6></div><br class="figure-break" /><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Virtual network switches use NAT configured by iptables rules. Editing these rules while the switch is running is not recommended, as incorrect rules may result in the switch being unable to communicate.
+ </div></div></div></div><div class="section" id="sect-network-protocols"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">H.3. Networking protocols</h2></div></div></div><div class="para">
+ The following sections describe individual networking protocols and how they are used in libvirt
+ </div><div class="section" id="sect-DNS_and_DHCP-protocols-libvirt"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.3.1. DNS and DHCP</h3></div></div></div><div class="para">
+ IP information can be assigned to guests via DHCP. A pool of addresses can be assigned to a virtual network switch for this purpose. Libvirt uses the <code class="command">dnsmasq</code> program for this. An instance of dnsmasq is automatically configured and started by libvirt for each virtual network switch that needs it.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-Network_Address_Translation-Switch_with_DNSDHCP"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-05-switchwithdnsmasq.jpg" width="444" alt="Virtual network switch running dnsmasq" /></div></div><h6>Figure H.4. Virtual network switch running dnsmasq</h6></div><br class="figure-break" /></div><div class="section" id="sub-sect-routed-mode-libvirt"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.3.2. Routed mode</h3></div></div></div><div class="para">
+ When using <span class="emphasis"><em>routed mode</em></span>, the virtual switch connects to the physical LAN connected to the host, passing traffic back and forth without the use of NAT. The virtual switch can examine all traffic and use the information contained within the network packets to make routing decisions. When using this mode, all of the virtual machines are in their own subnet, routed through a virtual switch. This situation is not always ideal as no other hosts on the physical network are aware of the virtual machines without manual physical router configuration, and cannot access the virtual machines. Routed mode operates at Layer 3 of the OSI networking model.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-Other_routing_types-Routed_mode"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-06-routed-switch.png" width="444" alt="Virtual network switch in routed mode" /></div></div><h6>Figure H.5. Virtual network switch in routed mode</h6></div><br class="figure-break" /></div><div class="section" id="sub-sect-iso-mode"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.3.3. Isolated mode</h3></div></div></div><div class="para">
+ When using <span class="emphasis"><em>Isolated mode</em></span>, guests connected to the virtual switch can communicate with each other, and with the host, but their traffic will not pass outside of the host, nor can they receive traffic from outside the host. Using dnsmasq in this mode is required for basic functionality such as DHCP. However, even if this network is isolated from any physical network, DNS names are still resolved. Therefore a situation can arise when DNS names resolve but ICMP echo request (ping) commands fail.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-Other_routing_types-Isolated_mode"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-07-isolated-switch.png" width="444" alt="Virtual network switch in isolated mode" /></div></div><h6>Figure H.6. Virtual network switch in isolated mode</h6></div><br class="figure-break" /></div></div><div class="section" id="sect-the-Default_Configuration-libvirt"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">H.4. The default configuration</h2></div></div></div><div class="para">
+ When the libvirtd daemon (<code class="command">libvirtd</code>) is first installed, it contains an initial virtual network switch configuration in NAT mode. This configuration is used so that installed guests can communicate to the external network, through the host. The following image demonstrates this default configuration for <code class="systemitem">libvirtd</code>:
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-the_default_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-08-network-overview.png" width="444" alt="Default libvirt network configuration" /></div></div><h6>Figure H.7. Default libvirt network configuration</h6></div><br class="figure-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ A virtual network can be restricted to a specific physical interface. This may be useful on a physical system that has several interfaces (for example, <code class="filename">eth0</code>, <code class="filename">eth1</code> and <code class="filename">eth2</code>). This is only useful in routed and NAT modes, and can be defined in the <code class="command">dev=<interface></code> option, or in <code class="command">virt-manager</code> when creating a new virtual network.
+ </div></div></div></div><div class="section" id="sect-Virtualization-Virtual_Networking-Example_scenarios"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">H.5. Examples of common scenarios</h2></div></div></div><div class="para">
+ This section demonstrates different virtual networking modes and provides some example scenarios.
+ </div><div class="section" id="sub-sect-routed-mode"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.5.1. Routed mode</h3></div></div></div><div class="formalpara"><h5 class="formalpara" id="idm122244256">DMZ</h5>
+ Consider a network where one or more nodes are placed in a controlled subnetwork for security reasons. The deployment of a special subnetwork such as this is a common practice, and the subnetwork is known as a DMZ. Refer to the following diagram for more details on this layout:
+ </div><div class="figure" id="dmz-example-diagram"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-09-routed-mode-DMZ.png" width="444" alt="Sample DMZ configuration" /></div></div><h6>Figure H.8. Sample DMZ configuration</h6></div><br class="figure-break" /><div class="para">
+ Hosts in a DMZ typically provide services to WAN (external) hosts as well as LAN (internal) hosts. As this requires them to be accessible from multiple locations, and considering that these locations are controlled and operated in different ways based on their security and trust level, routed mode is the best configuration for this environment.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm104918576">Virtual Server hosting</h5>
+ Consider a virtual server hosting company that has several hosts, each with two physical network connections. One interface is used for management and accounting, the other is for the virtual machines to connect through. Each guest has its own public IP address, but the hosts use private IP address as management of the guests can only be performed by internal administrators. Refer to the following diagram to understand this scenario:
+ </div><div class="figure" id="virt-serv-host-diagram"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-10-routed-mode-datacenter.png" width="444" alt="Virtual server hosting sample configuration" /></div></div><h6>Figure H.9. Virtual server hosting sample configuration</h6></div><br class="figure-break" /><div class="para">
+ When the host has a public IP address and the virtual machines have static public IP addresses, bridged networking cannot be used, as the provider only accepts packets from the MAC address of the public host. The following diagram demonstrates this:
+ </div><div class="figure" id="static-ip-diagram"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-11-router-mode-mac-restricted.png" width="444" alt="Virtual server using static IP addresses" /></div></div><h6>Figure H.10. Virtual server using static IP addresses</h6></div><br class="figure-break" /></div><div class="section" id="sub-sect-nat-mode"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.5.2. NAT mode</h3></div></div></div><div class="para">
+ NAT (Network Address Translation) mode is the default mode. It can be used for testing when there is no need for direct network visibility.
+ </div></div><div class="section" id="sub-sect-isolated-mode"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.5.3. Isolated mode</h3></div></div></div><div class="para">
+ Isolated mode allows virtual machines to communicate with each other only. They are unable to interact with the physical network.
+ </div></div></div><div class="section" id="sect-Virtualization-Virtual_Networking-Managing_a_virtual_network"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">H.6. 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 class="step"><div class="para">
+ From the <span class="guilabel"><strong>Edit</strong></span> menu, select <span class="guilabel"><strong>Connection Details</strong></span>.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Selecting_a_hosts_details"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_vnet_menuselect.png" width="444" alt="Selecting a host's details" /></div></div><h6>Figure H.11. Selecting a host's details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ This will open the <span class="guimenu"><strong>Connection Details</strong></span> menu. Click the <span class="guilabel"><strong>Virtual Networks</strong></span> tab.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic1.png" width="444" alt="Virtual network configuration" /></div></div><h6>Figure H.12. Virtual network configuration</h6></div><br class="figure-break" /></li><li class="step"><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><div class="section" id="sect-Virtualization-Virtual_Networking-Creating_a_virtual_network"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">H.7. 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 class="step"><div class="para">
+ Open the <span class="guilabel"><strong>Virtual Networks</strong></span> tab from within the <span class="guilabel"><strong>Connection Details</strong></span> menu. Click the <span class="guibutton"><strong>Add Network</strong></span> button, identified by a plus sign (+) icon. For more information, refer to <a class="xref" href="#sect-Virtualization-Virtual_Networking-Managing_a_virtual_network">Section H.6, “Managing a virtual network”</a>.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Virtual_network_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic1.png" width="444" alt="Virtual network configuration" /></div></div><h6>Figure H.13. 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> window. Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Creating_a_new_virtual_network"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic2.png" width="444" alt="Creating a new virtual network" /></div></div><h6>Figure H.14. Creating a new virtual network</h6></div><br class="figure-break" /></li><li class="step"><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_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Naming_your_virtual_network"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic3.png" width="444" alt="Naming your virtual network" /></div></div><h6>Figure H.15. Naming your virtual network</h6></div><br class="figure-break" /></li><li class="step"><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_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Choosing_an_IPv4_address_space"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic4.png" width="444" alt="Choosing an IPv4 address space" /></div></div><h6>Figure H.16. Choosing an IPv4 address space</h6></div><br class="figure-break" /></li><li class="step"><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_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Selecting_the_DHCP_range"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic5.png" width="444" alt="Selecting the DHCP range" /></div></div><h6>Figure H.17. Selecting the DHCP range</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Select how the virtual network should connect to the physical network.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Connecting_to_physical_network"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic6.png" width="444" alt="Connecting to physical network" /></div></div><h6>Figure H.18. 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>Any physical device</strong></span> or a specific physical device. Also select whether the <span class="guilabel"><strong>Mode</strong></span> should be <span class="guilabel"><strong>NAT</strong></span> or <span class="guilabel"><strong>Routed</strong></span>.
+ </div><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><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_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Ready_to_create_network"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic7.png" width="444" alt="Ready to create network" /></div></div><h6>Figure H.19. Ready to create network</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ The new virtual network is now available in the <span class="guilabel"><strong>Virtual Networks</strong></span> tab of the <span class="guilabel"><strong>Connection Details</strong></span> window.
+ </div></li></ol></div></div><div class="section" id="sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">H.8. Attaching a virtual network to a guest</h2></div></div></div><div class="para">
+ To attach a virtual network to a guest:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ In the <span class="guilabel"><strong>Virtual Machine Manager</strong></span> window, highlight the guest that will have the network assigned.
+ </div><div class="figure" id="guest4network"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt1.png" width="444" alt="Selecting a virtual machine to display" /></div></div><h6>Figure H.20. Selecting a virtual machine to display</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ From the Virtual Machine Manager <span class="guilabel"><strong>Edit</strong></span> menu, select <span class="guilabel"><strong>Virtual Machine Details</strong></span>.
+ </div><div class="figure" id="showdetails"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt11.png" width="444" alt="Displaying the virtual machine details" /></div></div><h6>Figure H.21. Displaying the virtual machine details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Click the <span class="guilabel"><strong>Add Hardware</strong></span> button on the Virtual Machine Details window.
+ </div><div class="figure" id="vmdetailswindow"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt4.png" width="444" alt="The Virtual Machine Details window" /></div></div><h6>Figure H.22. The Virtual Machine Details window</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ In the <span class="guilabel"><strong>Add new virtual hardware</strong></span> window, select <span class="guilabel"><strong>Network</strong></span> from the left pane, and select your network name (<span class="emphasis"><em>network1</em></span> in this example) from the <span class="guilabel"><strong>Host device</strong></span> menu and click <span class="guibutton"><strong>Finish</strong></span>.
+ </div><div class="figure" id="select_network"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic10.png" width="444" alt="Select your network from the Add new virtual hardware window" /></div></div><h6>Figure H.23. Select your network from the Add new virtual hardware window</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ The new network is now displayed as a virtual network interface that will be presented to the guest upon launch.
+ </div><div class="figure" id="newnetworkishown"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic11.png" width="444" alt="New network shown in guest hardware list" /></div></div><h6>Figure H.24. New network shown in guest hardware list</h6></div><br class="figure-break" /></li></ol></div></div><div class="section" id="sect-attch-nic-physdev"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">H.9. Directly attaching to physical interface</h2></div></div></div><div class="para">
+ The instructions provided in this chapter will assist in the direct attachment of the virtual machine's NIC to the given physical interface of the host. This setup requires the Linux macvtap driver to be available. There are four modes that you can choose for the operation mode of the macvtap device, with 'vepa' being the default mode. Their behavior is as follows:
+ </div><div class="variablelist"><h6>Physical interface delivery modes</h6><dl class="variablelist"><dt class="varlistentry"><span class="term">vepa</span></dt><dd><div class="para">
+ All VMs' packets are sent to the external bridge. Packets whose destination is a VM on the same host as where the packet originates from are sent back to the host by the VEPA capable bridge (today's bridges are typically not VEPA capable).
+ </div></dd><dt class="varlistentry"><span class="term">bridge</span></dt><dd><div class="para">
+ Packets whose destination is on the same host as where they originate from are directly delivered to the target macvtap device. Both origin and destination devices need to be in bridge mode for direct delivery. If either one of them is in vepa mode, a VEPA capable bridge is required.
+ </div></dd><dt class="varlistentry"><span class="term">private</span></dt><dd><div class="para">
+ All packets are sent to the external bridge and will only be delivered to a target VM on the same host if they are sent through an external router or gateway and that device sends them back to the host. This procedure is followed if either the source or destination device is in private mode.
+ </div></dd><dt class="varlistentry"><span class="term">passthrough</span></dt><dd><div class="para">
+ This feature attaches a virtual function of a SRIOV capable NIC directly to a VM without losing the migration capability. All packets are sent to the VF/IF of the configured network device. Depending on the capabilities of the device additional prerequisites or limitations may apply; for example, on Linux this requires kernel 2.6.38 or newer.
+ </div></dd></dl></div><div class="para">
+ Each of the four modes is configured by changing the domain xml file. Once this file is opened, change the mode setting as shown:
+ </div><pre class="screen">
+ <devices>
+ ...
+ <interface type='direct'>
+ <source dev='eth0' mode='vepa'/>
+ </interface>
+ </devices>
+</pre><div class="para">
+ The network access of direct attached guest virtual machines can be managed by the hardware switch to which the physical interface of the host machine is connected to.
+ </div><div class="para">
+ The interface can have additional parameters as shown below, if the switch is conforming to the IEEE 802.1Qbg standard. The parameters of the virtualport element are documented in more detail in the IEEE 802.1Qbg standard. The values are network specific and should be provided by the network administrator. In 802.1Qbg terms, the Virtual Station Interface (VSI) represents the virtual interface of a virtual machine.
+ </div><div class="para">
+ Note that IEEE 802.1Qbg requires a non-zero value for the VLAN ID. Also if the switch is conforming to the IEEE 802.1Qbh standard, the values are network specific and should be provided by the network administrator.
+ </div><div class="variablelist"><h6>Virtual Station Interface types</h6><dl class="variablelist"><dt class="varlistentry"><span class="term">managerid</span></dt><dd><div class="para">
+ The VSI Manager ID identifies the database containing the VSI type and instance definitions. This is an integer value and the value 0 is reserved.
+ </div></dd><dt class="varlistentry"><span class="term">typeid</span></dt><dd><div class="para">
+ The VSI Type ID identifies a VSI type characterizing the network access. VSI types are typically managed by network administrator. This is an integer value.
+ </div></dd><dt class="varlistentry"><span class="term">typeidversion</span></dt><dd><div class="para">
+ The VSI Type Version allows multiple versions of a VSI Type. This is an integer value.
+ </div></dd><dt class="varlistentry"><span class="term">instanceid</span></dt><dd><div class="para">
+ The VSI Instance ID Identifier is generated when a VSI instance (i.e. a virtual interface of a virtual machine) is created. This is a globally unique identifier.
+ </div></dd><dt class="varlistentry"><span class="term">profileid</span></dt><dd><div class="para">
+ The profile ID contains the name of the port profile that is to be applied onto this interface. This name is resolved by the port profile database into the network parameters from the port profile, and those network parameters will be applied to this interface.
+ </div></dd></dl></div><div class="para">
+ Each of the four types is configured by changing the domain xml file. Once this file is opened, change the mode setting as shown:
+ </div><pre class="screen">
+ <devices>
+ ...
+ <interface type='direct'>
+ <source dev='eth0.2' mode='vepa'/>
+ <virtualport type="802.1Qbg">
+ <parameters managerid="11" typeid="1193047" typeidversion="2" instanceid="09b11c53-8b5c-4eeb-8f00-d84eaa0aaa4f"/>
+ </virtualport>
+ </interface>
+ </devices>
+</pre><div class="para">
+ The profile ID is shown here:
+ </div><pre class="screen">
+ <devices>
+ ...
+ <interface type='direct'>
+ <source dev='eth0' mode='private'/>
+ <virtualport type='802.1Qbh'>
+ <parameters profileid='finance'/>
+ </virtualport>
+ </interface>
+ </devices>
+ ...
+</pre></div><div class="section" id="sect-applying-network-filtering"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">H.10. Applying network filtering</h2></div></div></div><div class="para">
+ This section provides an introduction to libvirt's network filters, their goals, concepts and XML format.
+ </div><div class="section" id="intro-sub-sect-applying-network-filtering"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.10.1. Introduction</h3></div></div></div><div class="para">
+ The goal of the network filtering, is to enable administrators of a virtualized system to configure and enforce network traffic filtering rules on virtual machines and manage the parameters of network traffic that virtual machines are allowed to send or receive. The network traffic filtering rules are applied on the host when a virtual machine is started. Since the filtering rules cannot be circumvented from within the virtual machine, it makes them mandatory from the point of view of a virtual machine user.
+ </div><div class="para">
+ From the point of view of the guest, the network filtering system allows each virtual machine's network traffic filtering rules to be configured individually on a per interface basis. These rules are applied on the host when the virtual machine is started and can be modified while the virtual machine is running. The latter can be achieved by modifying the XML description of a network filter.
+ </div><div class="para">
+ Multiple virtual machines can make use of the same generic network filter. When such a filter is modified, the network traffic filtering rules of all running virtual machines that reference this filter are updated. The machines that are not running will update on start.
+ </div><div class="para">
+ As previously mentioned, applying network traffic filtering rules can be done on individual network interfaces that are configured for certain types of network configurations. Supported network types include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ network
+ </div></li><li class="listitem"><div class="para">
+ ethernet -- must be used in bridging mode
+ </div></li><li class="listitem"><div class="para">
+ bridge
+ </div></li></ul></div><div class="example" id="ex-net-filtering"><h6>Example H.1. An example of network filtering</h6><div class="example-contents"><div class="para">
+ The interface XML is used to reference a top-level filter. In the following example, the interface description references the filter clean-traffic.
+ </div><pre class="screen">
+ <devices>
+ <interface type='bridge'>
+ <mac address='00:16:3e:5d:c7:9e'/>
+ <filterref filter='clean-traffic'/>
+ </interface>
+ </devices>
+</pre><div class="para">
+ Network filters are written in XML and may either contain: references to other filters, rules for traffic filtering, or hold a combination of both. The above referenced filter clean-traffic is a filter that only contains references to other filters and no actual filtering rules. Since references to other filters can be used, a tree of filters can be built. The clean-traffic filter can be viewed using the command: <code class="command"># virsh nwfilter-dumpxml clean-traffic</code>.
+ </div><div class="para">
+ As previously mentioned, a single network filter can be referenced by multiple virtual machines. Since interfaces will typically have individual parameters associated with their respective traffic filtering rules, the rules described in a filter's XML can be generalized using variables. In this case, the variable name is used in the filter XML and the name and value are provided at the place where the filter is referenced.
+ </div></div></div><br class="example-break" /><div class="example"><h6>Example H.2. Description extended</h6><div class="example-contents"><div class="para">
+ In the following example, the interface description has been extended with the parameter IP and a dotted IP address as a value.
+ </div><pre class="screen">
+ <devices>
+ <interface type='bridge'>
+ <mac address='00:16:3e:5d:c7:9e'/>
+ <filterref filter='clean-traffic'>
+ <parameter name='IP' value='10.0.0.1'/>
+ </filterref>
+ </interface>
+ </devices>
+</pre><div class="para">
+ In this particular example, the clean-traffic network traffic filter will be represented with the IP address parameter 10.0.0.1 and as per the rule dictates that all traffic from this interface will always be using 10.0.0.1 as the source IP address, which is one of the purpose of this particular filter.
+ </div></div></div><br class="example-break" /></div><div class="section" id="sub-sect-filt-chain"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.10.2. Filtering chains</h3></div></div></div><div class="para">
+ Filtering rules are organized in filter chains. These chains can be thought of as having a tree structure with packet filtering rules as entries in individual chains (branches).
+ </div><div class="para">
+ Packets start their filter evaluation in the root chain and can then continue their evaluation in other chains, return from those chains back into the root chain or be dropped or accepted by a filtering rule in one of the traversed chains.
+ </div><div class="para">
+ Libvirt's network filtering system automatically creates individual root chains for every virtual machine's network interface on which the user chooses to activate traffic filtering. The user may write filtering rules that are either directly instantiated in the root chain or may create protocol-specific filtering chains for efficient evaluation of protocol-specific rules.
+ </div><div class="para">
+ The following chains exist:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ root
+ </div></li><li class="listitem"><div class="para">
+ mac
+ </div></li><li class="listitem"><div class="para">
+ stp (spanning tree protocol)
+ </div></li><li class="listitem"><div class="para">
+ vlan
+ </div></li><li class="listitem"><div class="para">
+ arp and rarp
+ </div></li><li class="listitem"><div class="para">
+ ipv4
+ </div></li><li class="listitem"><div class="para">
+ ipv6
+ </div></li></ul></div><div class="para">
+ Multiple chains evaluating the mac, stp, vlan, arp, rarp, ipv4, or ipv6 protocol can be created using the protocol name only as a prefix in the chain's name.
+ </div><div class="example" id="arp-pro-example"><h6>Example H.3. ARP traffic filtering</h6><div class="example-contents"><div class="para">
+ This example allows chains with names arp-xyz or arp-test to be specified and have their ARP protocol packets evaluated in those chains.
+ </div><div class="para">
+ The following filter XML shows an example of filtering ARP traffic in the arp chain.
+ </div><pre class="screen">
+<filter name='no-arp-spoofing' chain='arp' priority='-500'>
+ <uuid>f88f1932-debf-4aa1-9fbe-f10d3aa4bc95</uuid>
+ <rule action='drop' direction='out' priority='300'>
+ <mac match='no' srcmacaddr='$MAC'/>
+ </rule>
+ <rule action='drop' direction='out' priority='350'>
+ <arp match='no' arpsrcmacaddr='$MAC'/>
+ </rule>
+ <rule action='drop' direction='out' priority='400'>
+ <arp match='no' arpsrcipaddr='$IP'/>
+ </rule>
+ <rule action='drop' direction='in' priority='450'>
+ <arp opcode='Reply'/>
+ <arp match='no' arpdstmacaddr='$MAC'/>
+ </rule>
+ <rule action='drop' direction='in' priority='500'>
+ <arp match='no' arpdstipaddr='$IP'/>
+ </rule>
+ <rule action='accept' direction='inout' priority='600'>
+ <arp opcode='Request'/>
+ </rule>
+ <rule action='accept' direction='inout' priority='650'>
+ <arp opcode='Reply'/>
+ </rule>
+ <rule action='drop' direction='inout' priority='1000'/>
+</filter>
+</pre><div class="para">
+ The consequence of putting ARP-specific rules in the arp chain, rather than for example in the root chain, is that packets protocols other than ARP do not need to be evaluated by ARP protocol-specific rules. This improves the efficiency of the traffic filtering. However, one must then pay attention to only putting filtering rules for the given protocol into the chain since other rules will not be evaluated. For example, an IPv4 rule will not be evaluated in the ARP chain since IPv4 protocol packets will not traverse the ARP chain.
+ </div></div></div><br class="example-break" /></div><div class="section" id="sub-sect-filt-chain-props"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.10.3. Filtering chain priorities</h3></div></div></div><div class="para">
+ As previously mentioned, when creating a filtering rule, all chains are connected to the root chain. The order in which those chains are accessed is influenced by the priority of the chain. The following table shows the chains that can be assigned a priority and their default priorities.
+ </div><div class="table" id="tab-filtering-chain-priorities"><h6>Table H.1. Filtering chain default priorities values</h6><div class="table-contents"><table summary="Filtering chain default priorities values" border="1"><colgroup><col class="1" width="50%" /><col class="2" width="50%" /></colgroup><thead><tr><th class="">
+ Chain (prefix)
+ </th><th class="">
+ Default priority
+ </th></tr></thead><tbody><tr><td class="">
+ stp
+ </td><td class="">
+ -810
+ </td></tr><tr><td class="">
+ mac
+ </td><td class="">
+ -800
+ </td></tr><tr><td class="">
+ vlan
+ </td><td class="">
+ -750
+ </td></tr><tr><td class="">
+ ipv4
+ </td><td class="">
+ -700
+ </td></tr><tr><td class="">
+ ipv6
+ </td><td class="">
+ -600
+ </td></tr><tr><td class="">
+ arp
+ </td><td class="">
+ -500
+ </td></tr><tr><td class="">
+ rarp
+ </td><td class="">
+ -400
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ A chain with a lower priority value is accessed before one with a higher value.
+ </div><div class="para">
+ The chains listed in <a class="xref" href="#tab-filtering-chain-priorities">Table H.1, “Filtering chain default priorities values”</a> can be also be assigned custom priorities by writing a value in the range [-1000 to 1000] into the priority (XML) attribute in the filter node. <a class="xref" href="#sub-sect-filt-chain">Section H.10.2, “Filtering chains”</a>filter shows the default priority of -500 for arp chains, for example.
+ </div></div></div></div><div class="section" id="sub-sect-vars-in-filters"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.10.4. Usage of variables in filters</h3></div></div></div><div class="para">
+ There are two variables that have been reserved for usage by the network traffic filtering subsystem: MAC and IP.
+ </div><div class="para">
+ <em class="parameter"><code>MAC</code></em> is designated for the MAC address of the network interface. A filtering rule that references this variable will automatically be replaced with the MAC address of the interface. This works without the user having to explicitly provide the MAC parameter. Even though it is possible to specify the MAC parameter similar to the IP parameter above, it is discouraged since libvirt knows what MAC address an interface will be using.
+ </div><div class="para">
+ The parameter <em class="parameter"><code>IP</code></em> represents the IP address that the operating system inside the virtual machine is expected to use on the given interface. The IP parameter is special in so far as the libvirt daemon will try to determine the IP address (and thus the IP parameter's value) that is being used on an interface if the parameter is not explicitly provided but referenced. For current limitations on IP address detection, consult the section on limitations <a class="xref" href="#sub-sect-limitations-filters-network-subsystem">Section H.10.12, “Limitations”</a> on how to use this feature and what to expect when using it. The XML file shown in <a class="xref" href="#sub-sect-filt-chain">Section H.10.2, “Filtering chains”</a> contains the filter <em class="parameter"><code>no-arp-spoofing</code></em>, which is an example of using a network filter XML to reference the MAC and IP variables.
+ </div><div class="para">
+ Note that referenced variables are always prefixed with the character <em class="parameter"><code>$</code></em>. The format of the value of a variable must be of the type expected by the filter attribute identified in the XML. In the above example, the <em class="parameter"><code>IP</code></em> parameter must hold a legal IP address in standard format. Failure to provide the correct structure will result in the filter variable not being replaced with a value and will prevent a virtual machine from starting or will prevent an interface from attaching when hotplugging is being used. Some of the types that are expected for each XML attribute are shown in the example <a class="xref" href="#example-vars-xml-iptraffic-filter">Example H.4, “Sample variable types”</a>.
+ </div><div class="example" id="example-vars-xml-iptraffic-filter"><h6>Example H.4. Sample variable types</h6><div class="example-contents"><div class="para">
+ As variables can contain lists of elements, (the variable IP can contain multiple IP addresses that are valid on a particular interface, for example), the notation for providing multiple elements for the IP variable is:
+ </div><pre class="screen">
+ <devices>
+ <interface type='bridge'>
+ <mac address='00:16:3e:5d:c7:9e'/>
+ <filterref filter='clean-traffic'>
+ <parameter name='IP' value='10.0.0.1'/>
+ <parameter name='IP' value='10.0.0.2'/>
+ <parameter name='IP' value='10.0.0.3'/>
+ </filterref>
+ </interface>
+ </devices>
+</pre><div class="para">
+ This XML file creates filters to enable multiple IP addresses per interface. Each of the IP addresses will result in a seperate filtering rule. Therefore using the XML above and the the following rule, three individual filtering rules (one for each IP address) will be created:
+ </div><pre class="screen">
+ <rule action='accept' direction='in' priority='500'>
+ <tcp srpipaddr='$IP'/>
+ </rule>
+</pre><div class="para">
+ As it is possible to access individual elements of a variable holding a list of elements, a filtering rule like the following accesses the 2nd element of the variable <em class="replaceable"><code>DSTPORTS</code></em>.
+ </div><pre class="screen">
+ <rule action='accept' direction='in' priority='500'>
+ <udp dstportstart='$DSTPORTS[1]'/>
+ </rule>
+</pre></div></div><br class="example-break" /><div class="example" id="exam-fil-rules-combo"><h6>Example H.5. Using a variety of variables</h6><div class="example-contents"><div class="para">
+ As it is possible to create filtering rules that represent all possible combinations of rules from different lists using the notation <code class="command">$VARIABLE[@<iterator id="x">]</code>. The following rule allows a virtual machine to receive traffic on a set of ports, which are specified in <em class="replaceable"><code>DSTPORTS</code></em>, from the set of source IP address specified in <em class="replaceable"><code>SRCIPADDRESSES</code></em>. The rule generates all combinations of elements of the variable <em class="replaceable"><code>DSTPORTS</code></em> with those of <em class="replaceable"><code>SRCIPADDRESSES</code></em> by using two independent iterators to access their elements.
+ </div><pre class="screen">
+ <rule action='accept' direction='in' priority='500'>
+ <ip srcipaddr='$SRCIPADDRESSES[@1]' dstportstart='$DSTPORTS[@2]'/>
+ </rule>
+</pre><div class="para">
+ Assign concrete values to <em class="replaceable"><code>SRCIPADDRESSES</code></em> and <em class="replaceable"><code>DSTPORTS</code></em> as shown:
+ </div><pre class="screen">
+ SRCIPADDRESSES = [ 10.0.0.1, 11.1.2.3 ]
+ DSTPORTS = [ 80, 8080 ]
+</pre><div class="para">
+ Assigning values to the variables using <code class="command">$SRCIPADDRESSES[@1]</code> and <code class="command">$DSTPORTS[@2]</code> would then result in all combinations of addresses and ports being created as shown:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ 10.0.0.1, 80
+ </div></li><li class="listitem"><div class="para">
+ 10.0.0.1, 8080
+ </div></li><li class="listitem"><div class="para">
+ 11.1.2.3, 80
+ </div></li><li class="listitem"><div class="para">
+ 11.1.2.3, 8080
+ </div></li></ul></div><div class="para">
+ Accessing the same variables using a single iterator, for example by using the notation <code class="command">$SRCIPADDRESSES[@1]</code> and <code class="command">$DSTPORTS[@1]</code>, would result in parallel access to both lists and result in the following combinations:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ 10.0.0.1, 80
+ </div></li><li class="listitem"><div class="para">
+ 11.1.2.3, 8080
+ </div></li></ul></div></div></div><br class="example-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ <code class="command">$VARIABLE</code> is short-hand for <code class="command">$VARIABLE[@0]</code>. The former notation always assumes the role of iterator with <code class="command">iterator id="0"</code> added as shown in the opening paragraph at the top of this section.
+ </div></div></div></div><div class="section" id="sub-sect-auto-IP-add-detect-dhcp-snoop"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.10.5. Automatic IP address detection and DHCP snooping</h3></div></div></div><div class="section" id="sub-sub-sect-intro-dhcp-snoop"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.5.1. Introduction</h4></div></div></div><div class="para">
+ The detection of IP addresses used on a virtual machine's interface is automatically activated if the variable IP is referenced but no value has been assigned to it. The variable <em class="parameter"><code>CTRL_IP_LEARNING</code></em> can be used to specify the IP address learning method to use. Valid values include: <em class="replaceable"><code>any</code></em>, <em class="replaceable"><code>dhcp</code></em>, or <em class="replaceable"><code>none</code></em>.
+ </div><div class="para">
+ The value <em class="replaceable"><code>any</code></em> instructs libvirt to use any packet to determine the address in use by a virtual machine, which is the default setting if the variable <em class="parameter"><code>TRL_IP_LEARNING</code></em> is not set. This method will only detect a single IP address per interface. Once a guest's IP address has been detected, its IP network traffic will be locked to that address, if for example, IP address spoofing is prevented by one of its filters. In that case, the user of the VM will not be able to change the IP address on the interface inside the guest, which would be considered IP address spoofing. When a guest is migrated to another host or resumed after a suspend operation, the first packet sent by the guest will again determine the IP address that the guest can use on a particular interface.
+ </div><div class="para">
+ The value of <em class="replaceable"><code>dhcp</code></em> instucts libvirt to only honor DHCP server-assigned addresses with valid leases. This method supports the detection and usage of multiple IP address per interface. When a guest resumes after a suspend operation, any valid IP address leases are applied to its filters. Otherwise the guest is expected to use DHCP to obtain a new IP addresses. When a guest migrates to another physical host, the guest is required to re-run the DHCP protocol.
+ </div><div class="para">
+ If CTRL_IP_LEARNING is set to <em class="replaceable"><code>none</code></em>, libvirt does not do IP address learning and referencing IP without assigning it an explicit value is an error.
+ </div></div><div class="section" id="sub-sub-sect-DHCP-snooping"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.5.2. DHCP snooping</h4></div></div></div><div class="para">
+ <code class="command">CTRL_IP_LEARNING=<em class="replaceable"><code>dhcp</code></em></code> (DHCP snooping) provides additional anti-spoofing security, especially when combined with a filter allowing only trusted DHCP servers to assign IP addresses. To enable this, set the variable <em class="parameter"><code>DHCPSERVER</code></em> to the IP address of a valid DHCP server and provide filters that use this variable to filter incoming DHCP responses.
+ </div><div class="para">
+ When DHCP snooping is enabled and the DHCP lease expires, the guest will no longer be able to use the IP address until it acquires a new, valid lease from a DHCP server. If the guest is migrated, it must get a new valid DHCP lease to use an IP address (e.g., by bringing the VM interface down and up again).
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Automatic DHCP detection listens to the DHCP traffic the guest exchanges with the DHCP server of the infrastructure. To avoid denial-of-service attacks on libvirt, the evaluation of those packets is rate-limited, meaning that a guest sending an excessive number of DHCP packets per second on an interface will not have all of those packets evaluated and thus filters may not get adapted. Normal DHCP client behavior is assumed to send a low number of DHCP packets per second. Further, it is important to setup appropriate filters on all guests in the infrastructure to avoid them being able to send DHCP packets. Therefore guests must either be prevented from sending UDP and TCP traffic from port 67 to port 68 or the DHCPSERVER variable should be used on all guests to restrict DHCP server messages to only be allowed to originate from trusted DHCP servers. At the same time anti-spoofing prevention must be enabled on all guests in the subnet.
+ </div></div></div><div class="example" id="exam-dhcp-snoop"><h6>Example H.6. Activating IPs for DHCP snooping</h6><div class="example-contents"><div class="para">
+ The following XML provides an example for the activation of IP address learning using the DHCP snooping method:
+ </div><pre class="screen">
+ <interface type='bridge'>
+ <source bridge='virbr0'/>
+ <filterref filter='clean-traffic'>
+ <parameter name='CTRL_IP_LEARNING' value='dhcp'/>
+ </filterref>
+ </interface>
+</pre></div></div><br class="example-break" /></div></div><div class="section" id="sub-sect-vars-reserved"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.10.6. Reserved Variables</h3></div></div></div><div class="para">
+ <a class="xref" href="#table-res-vars">Table H.2, “Reserved variables”</a> shows the variables that are considered reserved and are used by libvirt:
+ </div><div class="table" id="table-res-vars"><h6>Table H.2. Reserved variables</h6><div class="table-contents"><table summary="Reserved variables" border="1"><colgroup><col class="1" width="50%" /><col class="2" width="50%" /></colgroup><thead><tr><th class="">
+ Variable Name
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ MAC
+ </td><td class="">
+ The MAC address of the interface
+ </td></tr><tr><td class="">
+ IP
+ </td><td class="">
+ The list of IP addresses in use by an interface
+ </td></tr><tr><td class="">
+ IPV6
+ </td><td class="">
+ Not currently implemented: the list of IPV6 addresses in use by an interface
+ </td></tr><tr><td class="">
+ DHCPSERVER
+ </td><td class="">
+ The list of IP addresses of trusted DHCP servers
+ </td></tr><tr><td class="">
+ DHCPSERVERV6
+ </td><td class="">
+ Not currently implemented: The list of IPv6 addresses of trusted DHCP servers
+ </td></tr><tr><td class="">
+ CTRL_IP_LEARNING
+ </td><td class="">
+ The choice of the IP address detection mode
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sect-element-oview"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.10.7. Element and attribute overview</h3></div></div></div><div class="para">
+ The root element required for all network filters is named filter with two possible attributes. The name attribute provides a unique name of the given filter. The chain attribute is optional but allows certain filters to be better organized for more efficient processing by the firewall subsystem of the underlying host. Currently the system only supports the chains root, ipv4, ipv6, arp and rarp.
+ </div></div><div class="section" id="sub-sect-ref-filter"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.10.8. References to other filters</h3></div></div></div><div class="para">
+ Any filter may hold references to other filters. Individual filters may be referenced multiple times in a filter tree but references between filters must not introduce loops.
+ </div><div class="example" id="exam-clean-traffic"><h6>Example H.7. An Example of a clean traffic filter</h6><div class="example-contents"><div class="para">
+ The following shows the XML of the clean-traffic network filter referencing several other filters.
+ </div><pre class="screen">
+<filter name='clean-traffic'>
+ <uuid>6ef53069-ba34-94a0-d33d-17751b9b8cb1</uuid>
+ <filterref filter='no-mac-spoofing'/>
+ <filterref filter='no-ip-spoofing'/>
+ <filterref filter='allow-incoming-ipv4'/>
+ <filterref filter='no-arp-spoofing'/>
+ <filterref filter='no-other-l2-traffic'/>
+ <filterref filter='qemu-announce-self'/>
+</filter>
+</pre><div class="para">
+ To reference another filter, the XML node filterref needs to be provided inside a filter node. This node must have the attribute filter whose value contains the name of the filter to be referenced.
+ </div></div></div><br class="example-break" /><div class="para">
+ New network filters can be defined at any time and may contain references to network filters that are not known to libvirt, yet. However, once a virtual machine is started or a network interface referencing a filter is to be hotplugged, all network filters in the filter tree must be available. Otherwise the virtual machine will not start or the network interface cannot be attached.
+ </div></div><div class="section" id="sub-sect-filter-rules"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.10.9. Filter rules</h3></div></div></div><div class="para">
+ The following XML shows a simple example of a network traffic filter implementing a rule to drop traffic if the IP address (provided through the value of the variable IP) in an outgoing IP packet is not the expected one, thus preventing IP address spoofing by the VM.
+ </div><div class="example" id="filter-rules-example"><h6>Example H.8. Example of network traffic filtering</h6><div class="example-contents"><pre class="screen">
+<filter name='no-ip-spoofing' chain='ipv4'>
+ <uuid>fce8ae33-e69e-83bf-262e-30786c1f8072</uuid>
+ <rule action='drop' direction='out' priority='500'>
+ <ip match='no' srcipaddr='$IP'/>
+ </rule>
+</filter>
+</pre></div></div><br class="example-break" /><div class="para">
+ The traffic filtering rule starts with the rule node. This node may contain up to three of the following attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ action is mandatory can have the following values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ drop (matching the rule silently discards the packet with no further analysis)
+ </div></li><li class="listitem"><div class="para">
+ reject (matching the rule generates an ICMP reject message with no further analysis)
+ </div></li><li class="listitem"><div class="para">
+ accept (matching the rule accepts the packet with no further analysis)
+ </div></li><li class="listitem"><div class="para">
+ return (matching the rule passes this filter, but returns control to the calling filter for further analysis)
+ </div></li><li class="listitem"><div class="para">
+ continue (matching the rule goes on to the next rule for further analysis)
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ direction is mandatory can have the following values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ in for incomming traffic
+ </div></li><li class="listitem"><div class="para">
+ out for outgoing traffic
+ </div></li><li class="listitem"><div class="para">
+ inout for incoming and outgoing traffic
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ priority is optional. The priority of the rule controls the order in which the rule will be instantiated relative to other rules. Rules with lower values will be instantiated before rules with higher values. Valid values are in the range of -1000 to 1000. If this attribute is not provided, priority 500 will be assigned by default. Note that filtering rules in the root chain are sorted with filters connected to the root chain following their priorities. This allows to interleave filtering rules with access to filter chains. Refer to <a class="xref" href="#sub-sect-filt-chain-props">Section H.10.3, “Filtering chain priorities”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ statematch is optional. Possible values are '0' or 'false' to turn the underlying connection state matching off. The default setting is 'true' or 1
+ </div></li></ul></div><div class="para">
+ For more information see <a class="xref" href="#sub-sect-adv-filt-topics">Section H.10.11, “Advanced Filter Configuration Topics”</a>.
+ </div><div class="para">
+ The above example <a class="xref" href="#exam-clean-traffic">Example H.7, “An Example of a clean traffic filter”</a> indicates that the traffic of <em class="replaceable"><code>type ip</code></em> will be associated with the chain <em class="replaceable"><code>ipv4</code></em> and the rule will have <code class="command">priority=<em class="replaceable"><code>500</code></em></code>. If for example another filter is referenced whose traffic of <em class="replaceable"><code>type ip</code></em> is also associated with the chain <em class="replaceable"><code>ipv4</code></em> then that filter's rules will be ordered relative to the <code class="command">priority=<em class="replaceable"><code>500</code></em></code> of the shown rule.
+ </div><div class="para">
+ A rule may contain a single rule for filtering of traffic. The above example shows that traffic of type ip is to be filtered.
+ </div></div><div class="section" id="sub-sect-supp-pros"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.10.10. Supported protocols</h3></div></div></div><div class="para">
+ The following sections list and give some details about the protocols that are supported by the network filtering subsystem. This type of traffic rule is provided in the rule node as a nested node. Depending on the traffic type a rule is filtering, the attributes are different. The above example showed the single attribute <em class="parameter"><code>srcipaddr</code></em> that is valid inside the ip traffic filtering node. The following sections show what attributes are valid and what type of data they are expecting. The following datatypes are available:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ UINT8 : 8 bit integer; range 0-255
+ </div></li><li class="listitem"><div class="para">
+ UINT16: 16 bit integer; range 0-65535
+ </div></li><li class="listitem"><div class="para">
+ MAC_ADDR: MAC address in dotted decimal format, i.e., 00:11:22:33:44:55
+ </div></li><li class="listitem"><div class="para">
+ MAC_MASK: MAC address mask in MAC address format, i.e., FF:FF:FF:FC:00:00
+ </div></li><li class="listitem"><div class="para">
+ IP_ADDR: IP address in dotted decimal format, i.e., 10.1.2.3
+ </div></li><li class="listitem"><div class="para">
+ IP_MASK: IP address mask in either dotted decimal format (255.255.248.0) or CIDR mask (0-32)
+ </div></li><li class="listitem"><div class="para">
+ IPV6_ADDR: IPv6 address in numbers format, i.e., FFFF::1
+ </div></li><li class="listitem"><div class="para">
+ IPV6_MASK: IPv6 mask in numbers format (FFFF:FFFF:FC00::) or CIDR mask (0-128)
+ </div></li><li class="listitem"><div class="para">
+ STRING: A string
+ </div></li><li class="listitem"><div class="para">
+ BOOLEAN: 'true', 'yes', '1' or 'false', 'no', '0'
+ </div></li><li class="listitem"><div class="para">
+ IPSETFLAGS: The source and destination flags of the ipset described by up to 6 'src' or 'dst' elements selecting features from either the source or destination part of the packet header; example: src,src,dst. The number of 'selectors' to provide here depends on the type of ipset that is referenced
+ </div></li></ul></div><div class="para">
+ Every attribute except for those of type <em class="parameter"><code>IP_MASK</code></em> or <em class="parameter"><code>IPV6_MASK</code></em> can be negated using the match attribute with value <em class="replaceable"><code>no</code></em>. Multiple negated attributes may be grouped together. The following XML fragment shows such an example using abstract attributes.
+ </div><pre class="screen">
+[...]
+ <rule action='drop' direction='in'>
+ <protocol match='no' attribute1='value1' attribute2='value2'/>
+ <protocol attribute3='value3'/>
+ </rule>
+[...]
+</pre><div class="para">
+ Rules behave evaluate the rule as well as look at it logically within the boundaries of the given protocol attributes. Thus, if a single attribute's value does not match the one given in the rule, the whole rule will be skipped during the evaluation process. Therefore, in the above example incoming traffic will only be dropped if: the protocol property <em class="parameter"><code>attribute1</code></em> does not match both <em class="parameter"><code>value1</code></em> and the protocol property <em class="parameter"><code>attribute2</code></em> does not match <em class="parameter"><code>value2</code></em> and the protocol property <em class="parameter"><code>attribute3</code></em> matches <em class="parameter"><code>value3</code></em>.
+ </div><div class="section" id="sub-sub-sect-mac-filter-rules"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.10.1. MAC (Ethernet)</h4></div></div></div><div class="para">
+ Protocol ID: mac
+ </div><div class="para">
+ Rules of this type should go into the root chain.
+ </div><div class="table" id="table-mac-vars"><h6>Table H.3. MAC protocol types</h6><div class="table-contents"><table summary="MAC protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of destination
+ </td></tr><tr><td class="">
+ protocolid
+ </td><td class="">
+ UINT16 (0x600-0xffff), STRING
+ </td><td class="">
+ Layer 3 protocol ID. Valid strings include [arp, rarp, ipv4, ipv6]
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The filter can be written as such:
+ </div><pre class="screen">
+[...]
+<mac match='no' srcmacaddr='$MAC'/>
+[...]
+</pre></div><div class="section" id="sub-sub-sect-vlan"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.10.2. VLAN (802.1Q)</h4></div></div></div><div class="para">
+ Protocol ID: vlan
+ </div><div class="para">
+ Rules of this type should go either into the root or vlan chain.
+ </div><div class="table" id="table-vlan-vars"><h6>Table H.4. VLAN protocol types</h6><div class="table-contents"><table summary="VLAN protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of destination
+ </td></tr><tr><td class="">
+ vlan-id
+ </td><td class="">
+ UINT16 (0x0-0xfff, 0 - 4095)
+ </td><td class="">
+ VLAN ID
+ </td></tr><tr><td class="">
+ encap-protocol
+ </td><td class="">
+ UINT16 (0x03c-0xfff), String
+ </td><td class="">
+ Encapsulated layer 3 protocol ID, valid strings are arp, ipv4, ipv6
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sub-sect-prot-STP-explained"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.10.3. STP (Spanning Tree Protocol) </h4></div></div></div><div class="para">
+ Protocol ID: stp
+ </div><div class="para">
+ Rules of this type should go either into the root or stp chain.
+ </div><div class="table" id="table-stp-vars"><h6>Table H.5. STP protocol types</h6><div class="table-contents"><table summary="STP protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of sender
+ </td></tr><tr><td class="">
+ type
+ </td><td class="">
+ UINT8
+ </td><td class="">
+ Bridge Protocol Data Unit (BPDU) type
+ </td></tr><tr><td class="">
+ flags
+ </td><td class="">
+ UINT8
+ </td><td class="">
+ BPDU flagdstmacmask
+ </td></tr><tr><td class="">
+ root-priority
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Root priority range start
+ </td></tr><tr><td class="">
+ root-priority-hi
+ </td><td class="">
+ UINT16 (0x0-0xfff, 0 - 4095)
+ </td><td class="">
+ Root priority range end
+ </td></tr><tr><td class="">
+ root-address
+ </td><td class="">
+ MAC _ADDRESS
+ </td><td class="">
+ root MAC Address
+ </td></tr><tr><td class="">
+ root-address-mask
+ </td><td class="">
+ MAC _MASK
+ </td><td class="">
+ root MAC Address mask
+ </td></tr><tr><td class="">
+ roor-cost
+ </td><td class="">
+ UINT32
+ </td><td class="">
+ Root path cost (range start)
+ </td></tr><tr><td class="">
+ root-cost-hi
+ </td><td class="">
+ UINT32
+ </td><td class="">
+ Root path cost range end
+ </td></tr><tr><td class="">
+ sender-priority-hi
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Sender prioriry range end
+ </td></tr><tr><td class="">
+ sender-address
+ </td><td class="">
+ MAC_ADDRESS
+ </td><td class="">
+ BPDU sender MAC address
+ </td></tr><tr><td class="">
+ sender-address-mask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ BPDU sender MAC address mask
+ </td></tr><tr><td class="">
+ port
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Port identifier (range start)
+ </td></tr><tr><td class="">
+ port_hi
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Port identifier range end
+ </td></tr><tr><td class="">
+ msg-age
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Message age timer (range start)
+ </td></tr><tr><td class="">
+ msg-age-hi
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Message age timer range end
+ </td></tr><tr><td class="">
+ max-age-hi
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Maximum age time range end
+ </td></tr><tr><td class="">
+ hello-time
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Hello time timer (range start)
+ </td></tr><tr><td class="">
+ hello-time-hi
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Hello time timer range end
+ </td></tr><tr><td class="">
+ forward-delay
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Forward delay (range start)
+ </td></tr><tr><td class="">
+ forward-delay-hi
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Forward delay range end
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sub-sect-prot-ARP-RARP-explained"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.10.4. ARP/RARP</h4></div></div></div><div class="para">
+ Protocol ID: arp or rarp
+ </div><div class="para">
+ Rules of this type should either go into the root or arp/rarp chain.
+ </div><div class="table" id="table-arp-vars"><h6>Table H.6. ARP and RARP protocol types</h6><div class="table-contents"><table summary="ARP and RARP protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of destination
+ </td></tr><tr><td class="">
+ hwtype
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Hardware type
+ </td></tr><tr><td class="">
+ protocoltype
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Protocol type
+ </td></tr><tr><td class="">
+ opcode
+ </td><td class="">
+ UINT16, STRING
+ </td><td class="">
+ Opcode valid strings are: Request, Reply, Request_Reverse, Reply_Reverse, DRARP_Request, DRARP_Reply, DRARP_Error, InARP_Request, ARP_NAK
+ </td></tr><tr><td class="">
+ arpsrcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ Source MAC address in ARP/RARP packet
+ </td></tr><tr><td class="">
+ arpdstmacaddr
+ </td><td class="">
+ MAC _ADDR
+ </td><td class="">
+ Destination MAC address in ARP/RARP packet
+ </td></tr><tr><td class="">
+ arpsrcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address in ARP/RARP packet
+ </td></tr><tr><td class="">
+ arpdstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address in ARP/RARP packet
+ </td></tr><tr><td class="">
+ gratututous
+ </td><td class="">
+ BOOLEAN
+ </td><td class="">
+ Boolean indiating whether to check for a gratuitous ARP packet
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sub-sect-prot-Ipv4-explained"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.10.5. IPv4</h4></div></div></div><div class="para">
+ Protocol ID: ip
+ </div><div class="para">
+ Rules of this type should either go into the root or ipv4 chain.
+ </div><div class="table" id="table-ipv4-vars"><h6>Table H.7. IPv4 protocol types</h6><div class="table-contents"><table summary="IPv4 protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of destination
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ protocol
+ </td><td class="">
+ UINT8, STRING
+ </td><td class="">
+ Layer 4 protocol identifier. Valid strings for protocol are: tcp, udp, udplite, esp, ah, icmp, igmp, sctp
+ </td></tr><tr><td class="">
+ srcportstart
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Start of range of valid source ports; requires protocol
+ </td></tr><tr><td class="">
+ srcportend
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ End of range of valid source ports; requires protocol
+ </td></tr><tr><td class="">
+ dstportstart
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ Start of range of valid destination ports; requires protocol
+ </td></tr><tr><td class="">
+ dstportend
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ End of range of valid destination ports; requires protocol
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sub-sect-chars-IPv6"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.10.6. IPv6</h4></div></div></div><div class="para">
+ Protocol ID: ipv6
+ </div><div class="para">
+ Rules of this type should either go into the root or ipv6 chain.
+ </div><div class="table" id="table-ipv6-vars"><h6>Table H.8. IPv6 protocol types</h6><div class="table-contents"><table summary="IPv6 protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of destination
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ protocol
+ </td><td class="">
+ UINT8, STRING
+ </td><td class="">
+ Layer 4 protocol identifier. Valid strings for protocol are: tcp, udp, udplite, esp, ah, icmpv6, sctp
+ </td></tr><tr><td class="">
+ scrportstart
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ Start of range of valid source ports; requires protocol
+ </td></tr><tr><td class="">
+ srcportend
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ End of range of valid source ports; requires protocol
+ </td></tr><tr><td class="">
+ dstportstart
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ Start of range of valid destination ports; requires protocol
+ </td></tr><tr><td class="">
+ dstportend
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ End of range of valid destination ports; requires protocol
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sub-sect-chars-tcp-udp"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.10.7. TCP/UDP/SCTP</h4></div></div></div><div class="para">
+ Protocol ID: tcp, udp, sctp
+ </div><div class="para">
+ The chain parameter is ignored for this type of traffic and should either be omitted or set to root. .
+ </div><div class="table" id="table-tcp-udp-vars"><h6>Table H.9. TCP/UDP/SCTP protocol types</h6><div class="table-contents"><table summary="TCP/UDP/SCTP protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ scripto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of source IP address
+ </td></tr><tr><td class="">
+ srcipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of source IP address
+ </td></tr><tr><td class="">
+ dstipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of destination IP address
+ </td></tr><tr><td class="">
+ dstipto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of destination IP address
+ </td></tr><tr><td class="">
+ scrportstart
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ Start of range of valid source ports; requires protocol
+ </td></tr><tr><td class="">
+ srcportend
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ End of range of valid source ports; requires protocol
+ </td></tr><tr><td class="">
+ dstportstart
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ Start of range of valid destination ports; requires protocol
+ </td></tr><tr><td class="">
+ dstportend
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ End of range of valid destination ports; requires protocol
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr><tr><td class="">
+ state
+ </td><td class="">
+ STRING
+ </td><td class="">
+ comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE
+ </td></tr><tr><td class="">
+ flags
+ </td><td class="">
+ STRING
+ </td><td class="">
+ TCP-only: format of mask/flags with mask and flags each being a comma separated list of SYN,ACK,URG,PSH,FIN,RST or NONE or ALL
+ </td></tr><tr><td class="">
+ ipset
+ </td><td class="">
+ STRING
+ </td><td class="">
+ The name of an IPSet managed outside of libvirt
+ </td></tr><tr><td class="">
+ ipsetflags
+ </td><td class="">
+ IPSETFLAGS
+ </td><td class="">
+ flags for the IPSet; requires ipset attribute
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sub-sect-icmp"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.10.8. ICMP</h4></div></div></div><div class="para">
+ Protocol ID: icmp
+ </div><div class="para">
+ Note: The chain parameter is ignored for this type of traffic and should either be omitted or set to root.
+ </div><div class="table" id="table-icmp-vars"><h6>Table H.10. ICMP protocol types</h6><div class="table-contents"><table summary="ICMP protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to the MAC address of the sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAD_ADDR
+ </td><td class="">
+ MAC address of the destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to the MAC address of the destination
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ srcipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ start of range of source IP address
+ </td></tr><tr><td class="">
+ scripto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ end of range of source IP address
+ </td></tr><tr><td class="">
+ dstipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of destination IP address
+ </td></tr><tr><td class="">
+ dstipto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of destination IP address
+ </td></tr><tr><td class="">
+ type
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ ICMP type
+ </td></tr><tr><td class="">
+ code
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ ICMP code
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr><tr><td class="">
+ state
+ </td><td class="">
+ STRING
+ </td><td class="">
+ comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE
+ </td></tr><tr><td class="">
+ ipset
+ </td><td class="">
+ STRING
+ </td><td class="">
+ The name of an IPSet managed outside of libvirt
+ </td></tr><tr><td class="">
+ ipsetflags
+ </td><td class="">
+ IPSETFLAGS
+ </td><td class="">
+ flags for the IPSet; requires ipset attribute
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sub-sect-igmp-esp-ah-etc"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.10.9. IGMP, ESP, AH, UDPLITE, 'ALL'</h4></div></div></div><div class="para">
+ Protocol ID: igmp, esp, ah, udplite, all
+ </div><div class="para">
+ The chain parameter is ignored for this type of traffic and should either be omitted or set to root.
+ </div><div class="table" id="table-igmp-esp-ah-vars"><h6>Table H.11. IGMP, ESP, AH, UDPLITE, 'ALL'</h6><div class="table-contents"><table summary="IGMP, ESP, AH, UDPLITE, 'ALL'" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to the MAC address of the sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAD_ADDR
+ </td><td class="">
+ MAC address of the destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to the MAC address of the destination
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ srcipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ start of range of source IP address
+ </td></tr><tr><td class="">
+ scripto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ end of range of source IP address
+ </td></tr><tr><td class="">
+ dstipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of destination IP address
+ </td></tr><tr><td class="">
+ dstipto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of destination IP address
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr><tr><td class="">
+ state
+ </td><td class="">
+ STRING
+ </td><td class="">
+ comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE
+ </td></tr><tr><td class="">
+ ipset
+ </td><td class="">
+ STRING
+ </td><td class="">
+ The name of an IPSet managed outside of libvirt
+ </td></tr><tr><td class="">
+ ipsetflags
+ </td><td class="">
+ IPSETFLAGS
+ </td><td class="">
+ flags for the IPSet; requires ipset attribute
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sub-sect-tcp-utp-sctp-over-ipv6"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.10.10. TCP/UDP/SCTP over IPV6</h4></div></div></div><div class="para">
+ Protocol ID: tcp-ipv6, udp-ipv6, sctp-ipv6
+ </div><div class="para">
+ The chain parameter is ignored for this type of traffic and should either be omitted or set to root.
+ </div><div class="table" id="table-tcp-udp-over-IPv6-vars"><h6>Table H.12. TCP, UDP, SCTP over IPv6 protocol types</h6><div class="table-contents"><table summary="TCP, UDP, SCTP over IPv6 protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ srcipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ start of range of source IP address
+ </td></tr><tr><td class="">
+ scripto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ end of range of source IP address
+ </td></tr><tr><td class="">
+ dstipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of destination IP address
+ </td></tr><tr><td class="">
+ dstipto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of destination IP address
+ </td></tr><tr><td class="">
+ srcportstart
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Start of range of valid source ports
+ </td></tr><tr><td class="">
+ srcportend
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ End of range of valid source ports
+ </td></tr><tr><td class="">
+ dstportstart
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Start of range of valid destination ports
+ </td></tr><tr><td class="">
+ dstportend
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ End of range of valid destination ports
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr><tr><td class="">
+ state
+ </td><td class="">
+ STRING
+ </td><td class="">
+ comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE
+ </td></tr><tr><td class="">
+ ipset
+ </td><td class="">
+ STRING
+ </td><td class="">
+ The name of an IPSet managed outside of libvirt
+ </td></tr><tr><td class="">
+ ipsetflags
+ </td><td class="">
+ IPSETFLAGS
+ </td><td class="">
+ flags for the IPSet; requires ipset attribute
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sub-sect-icmpv6"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.10.11. ICMPv6</h4></div></div></div><div class="para">
+ Protocol ID: icmpv6
+ </div><div class="para">
+ The chain parameter is ignored for this type of traffic and should either be omitted or set to root.
+ </div><div class="table" id="table-icmpv6-protcol-types"><h6>Table H.13. ICMPv6 protocol types</h6><div class="table-contents"><table summary="ICMPv6 protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ srcipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ start of range of source IP address
+ </td></tr><tr><td class="">
+ scripto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ end of range of source IP address
+ </td></tr><tr><td class="">
+ dstipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of destination IP address
+ </td></tr><tr><td class="">
+ dstipto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of destination IP address
+ </td></tr><tr><td class="">
+ type
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ ICMPv6 type
+ </td></tr><tr><td class="">
+ code
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ ICMPv6 code
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr><tr><td class="">
+ state
+ </td><td class="">
+ STRING
+ </td><td class="">
+ comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE
+ </td></tr><tr><td class="">
+ ipset
+ </td><td class="">
+ STRING
+ </td><td class="">
+ The name of an IPSet managed outside of libvirt
+ </td></tr><tr><td class="">
+ ipsetflags
+ </td><td class="">
+ IPSETFLAGS
+ </td><td class="">
+ flags for the IPSet; requires ipset attribute
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sub-sect-igmp-esp-ah-udplite-over-ipv6"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.10.12. IGMP, ESP, AH, UDPLITE, 'ALL' over IPv6</h4></div></div></div><div class="para">
+ Protocol ID: igmp-ipv6, esp-ipv6, ah-ipv6, udplite-ipv6, all-ipv6
+ </div><div class="para">
+ The chain parameter is ignored for this type of traffic and should either be omitted or set to root.
+ </div><div class="table" id="table-igmp-esp-ah-udplite-over-ipv6-vars"><h6>Table H.14. IGMP, ESP, AH, UDPLITE, 'ALL' over IPv protocol types</h6><div class="table-contents"><table summary="IGMP, ESP, AH, UDPLITE, 'ALL' over IPv protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ srcipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ start of range of source IP address
+ </td></tr><tr><td class="">
+ scripto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ end of range of source IP address
+ </td></tr><tr><td class="">
+ dstipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of destination IP address
+ </td></tr><tr><td class="">
+ dstipto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of destination IP address
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr><tr><td class="">
+ state
+ </td><td class="">
+ STRING
+ </td><td class="">
+ comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE
+ </td></tr><tr><td class="">
+ ipset
+ </td><td class="">
+ STRING
+ </td><td class="">
+ The name of an IPSet managed outside of libvirt
+ </td></tr><tr><td class="">
+ ipsetflags
+ </td><td class="">
+ IPSETFLAGS
+ </td><td class="">
+ flags for the IPSet; requires ipset attribute
+ </td></tr></tbody></table></div></div><br class="table-break" /></div></div><div class="section" id="sub-sect-adv-filt-topics"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.10.11. Advanced Filter Configuration Topics</h3></div></div></div><div class="para">
+ The following sections discuss advanced filter configuration topics.
+ </div><div class="section" id="sub-sub-sect-conn-track"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.11.1. Connection tracking</h4></div></div></div><div class="para">
+ The network filtering subsystem (on Linux) makes use of the connection tracking support of IP tables. This helps in enforcing the directionality of network traffic (state match) as well as counting and limiting the number of simultaneous connections towards a guest. As an example, if a guest has TCP port 8080 open as a server, clients may connect to the guest on port 8080. Connection tracking and enforcement of directionality then prevents the guest from initiating a connection from (TCP client) port 8080 to the host back to a remote host. More importantly, tracking helps to prevent remote attackers from establishing a connection back to a guest. For example, if the user inside the guest established a connection to port 80 on an attacker site, then the attacker will not be able to initiate a connection from TCP port 80 back towards the guest. By default the connection state match that enables connection tracking and then enforcement of directionality of traffic is turne
d on.
+ </div><div class="example"><h6>Example H.9. XML example for turning off connections to the TCP port</h6><div class="example-contents"><div class="para">
+ The following shows an example XML fragement where this feature has been turned off for incoming connections to TCP port 12345.
+ </div><pre class="screen">
+ [...]
+ <rule direction='in' action='accept' statematch='false'>
+ <cp dstportstart='12345'/>
+ </rule>
+ [...]
+</pre><div class="para">
+ This now allows incoming traffic to TCP port 12345, but would also enable the initiation from (client) TCP port 12345 within the VM, which may or may not be desirable.
+ </div></div></div><br class="example-break" /></div><div class="section" id="sub-sub-sect-lim-numb-conns"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.11.2. Limiting Number of Connections</h4></div></div></div><div class="para">
+ To limit the number of connections a guest may establish, a rule must be provided that sets a limit of connections for a given type of traffic. If for example a VM is supposed to be allowed to only ping one other IP address at a time and is supposed to have only one active incoming ssh connection at a time.
+ </div><div class="example" id="ex-xml-frag-limits"><h6>Example H.10. XML sample file that sets limits to connections</h6><div class="example-contents"><div class="para">
+ The following XML fragment can be used to limit connections
+ </div><pre class="screen">
+ [...]
+ <rule action='drop' direction='in' priority='400'>
+ <tcp connlimit-above='1'/>
+ </rule>
+ <rule action='accept' direction='in' priority='500'>
+ <tcp dstportstart='22'/>
+ </rule>
+ <rule action='drop' direction='out' priority='400'>
+ <icmp connlimit-above='1'/>
+ </rule>
+ <rule action='accept' direction='out' priority='500'>
+ <icmp/>
+ </rule>
+ <rule action='accept' direction='out' priority='500'>
+ <udp dstportstart='53'/>
+ </rule>
+ <rule action='drop' direction='inout' priority='1000'>
+ <all/>
+ </rule>
+ [...]
+</pre></div></div><br class="example-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Limitation rules must be listed in the XML prior to the rules for accepting traffic. According to the XML file in <a class="xref" href="#ex-xml-frag-limits">Example H.10, “XML sample file that sets limits to connections”</a>, an additional rule for allowing DNS traffic sent to port 22 go out the guest, has been added to avoid ssh sessions not getting established for reasons related to DNS lookup failures by the ssh daemon. Leaving this rule out may result in the ssh client hanging unexpectedly as it tries to connect. Additional caution should be used in regards to handling timeouts related to tracking of traffic. An ICMP ping that the user may have terminated inside the guest may have a long timeout in the host's connection tracking system and will therefore not allow another ICMP ping to go through.
+ </div><div class="para">
+ The best solution is to tune the timeout in the host's <code class="filename">sysfs</code> with the following command:# <code class="command">echo 3 > /proc/sys/net/netfilter/nf_conntrack_icmp_timeout</code>. This command sets the ICMP connection tracking timeout to 3 seconds. The effect of this is that once one ping is terminated, another one can start after 3 seconds.
+ </div><div class="para">
+ If for any reason the guest has not properly closed its TCP connection, the connection to be held open for a longer period of time, especially if the TCP timeout value was set for a large amount of time on the host. In addition, any idle connection may result in a time out in the connection tracking system which can be re-activated once packets are exchanged.
+ </div><div class="para">
+ However, if the limit is set too low, newly initiated connections may force an idle connection into TCP backoff. Therefore, the limit of connections should be set rather high so that fluctuations in new TCP connections don't cause odd traffic behavior in relation to idle connections.
+ </div></div></div></div><div class="section" id="sub-sub-subsect-command-line-tools"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.11.3. Command line tools</h4></div></div></div><div class="para">
+ virsh has been extended with life-cycle support for network filters. All commands related to the network filtering subsystem start with the prefix <em class="parameter"><code>nwfilter</code></em>. The following commands are available:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">nwfilter-list</code> : lists UUIDs and names of all network filters
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">nwfilter-define</code> : defines a new network filter or updates an existing one (must supply a name)
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">nwfilter-undefine</code> : deletes a specified network filter (must supply a name). In addition, it cannot currently be in use
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">nwfilter-dumpxml</code> : displays a specified network filter (must supply a name)
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">nwfilter-edit</code> : edits a specified network filter (must supply a name)
+ </div></li></ul></div></div><div class="section" id="sub-sub-sect-pre-exist-net-filter"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.11.4. Pre-existing network filters</h4></div></div></div><div class="para">
+ The following is a list of example network filters that are automatically installed with libvirt:
+ </div><div class="table" id="table-icmpv6-vars"><h6>Table H.15. ICMPv6 protocol types</h6><div class="table-contents"><table summary="ICMPv6 protocol types" border="1"><colgroup><col class="1" width="50%" /><col class="2" width="50%" /></colgroup><thead><tr><th class="">
+ Command Name
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ no-arp-spoofing
+ </td><td class="">
+ Prevents a guest from spoofing ARP traffic; this filter only allows ARP request and reply messages and enforces that those packets contain the MAC and IP addresses of the guest.
+ </td></tr><tr><td class="">
+ allow-dhcp
+ </td><td class="">
+ Allows a guest to request an IP address via DHCP (from any DHCP server)
+ </td></tr><tr><td class="">
+ allow-dhcp-server
+ </td><td class="">
+ Allows a guest to request an IP address from a specified DHCP server. The dotted decimal IP address of the DHCP server must be provided in a reference to this filter. The name of the variable must be <em class="replaceable"><code>DHCPSERVER</code></em>.
+ </td></tr><tr><td class="">
+ no-ip-spoofing
+ </td><td class="">
+ Prevents a guest from sending IP packets with a source IP address different from the one inside the packet.
+ </td></tr><tr><td class="">
+ no-ip-multicast
+ </td><td class="">
+ Prevents a guest from sending IP multicast packets.
+ </td></tr><tr><td class="">
+ clean-traffic
+ </td><td class="">
+ Prevents MAC, IP and ARP spoofing. This filter references several other filters as building blocks.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ These filters are only building blocks and require a combination with other filters to provide useful network traffic filtering. The most used one in the above list is the <em class="replaceable"><code>clean-traffic</code></em> filter. This filter itself can for example be combined with the <em class="replaceable"><code>no-ip-multicast</code></em> filter to prevent virtual machines from sending IP multicast traffic on top of the prevention of packet spoofing.
+ </div></div><div class="section" id="sub-sub-sect-write-own-filters"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.11.5. Writing your own filters</h4></div></div></div><div class="para">
+ Since libvirt only provides a couple of example networking filters, you may consider writing your own. When planning on doing so there are a couple of things you may need to know regarding the network filtering subsystem and how it works internally. Certainly you also have to know and understand the protocols very well that you want to be filtering on so that no further traffic than what you want can pass and that in fact the traffic you want to allow does pass.
+ </div><div class="para">
+ The network filtering subsystem is currently only available on Linux hosts and only works for Qemu and KVM type of virtual machines. On Linux, it builds upon the support for ebtables, iptables and ip6tables and makes use of their features. Considering the list found in <a class="xref" href="#sub-sect-supp-pros">Section H.10.10, “Supported protocols”</a> the following protolcols can be implemented using ebtables:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ mac
+ </div></li><li class="listitem"><div class="para">
+ stp (spanning tree protocol)
+ </div></li><li class="listitem"><div class="para">
+ vlan (802.1Q)
+ </div></li><li class="listitem"><div class="para">
+ arp, rarp
+ </div></li><li class="listitem"><div class="para">
+ ipv4
+ </div></li><li class="listitem"><div class="para">
+ ipv6
+ </div></li></ul></div><div class="para">
+ Any protocol that runs over IPv4 is supported using iptables, those over IPv6 are implemented using ip6tables.
+ </div><div class="para">
+ Using a Linux host, all traffic filtering rules created by libvirt's network filtering subsystem first passes through the filtering support implemented by ebtables and only afterwards through iptables or ip6tables filters. If a filter tree has rules with the protocols including: mac, stp, vlan arp, rarp, ipv4, or ipv6; the ebtable rules and values listed will automatically be used first.
+ </div><div class="para">
+ Multiple chains for the same protocol can be created. The name of the chain must have a prefix of one of the previously enumerated protocols. To create an additional chain for handling of ARP traffic, a chain with name arp-test, can for example be specified.
+ </div><div class="para">
+ As an example, it is possible to filter on UDP traffic by source and destination ports using the ip protocol filter and specifying attributes for the protocol, source and destination IP addresses and ports of UDP packets that are to be accepted. This allows early filtering of UDP traffic with ebtables. However, once an IP or IPv6 packet, such as a UDP packet, has passed the ebtables layer and there is at least one rule in a filter tree that instantiates iptables or ip6tables rules, a rule to let the UDP packet pass will also be necessary to be provided for those filtering layers. This can be achieved with a rule containing an appropriate udp or udp-ipv6 traffic filtering node.
+ </div><div class="example"><h6>Example H.11. Creating a custom filter</h6><div class="example-contents"><div class="para">
+ Suppose a filter is needed to fulfill the following list of requirements:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ prevents a VM's interface from MAC, IP and ARP spoofing
+ </div></li><li class="listitem"><div class="para">
+ opens only TCP ports 22 and 80 of a VM's interface
+ </div></li><li class="listitem"><div class="para">
+ allows the VM to send ping traffic from an interface but not let the VM be pinged on the interface
+ </div></li><li class="listitem"><div class="para">
+ allows the VM to do DNS lookups (UDP towards port 53)
+ </div></li></ul></div><div class="para">
+ The requirement to prevent spoofing is fulfilled by the existing <em class="parameter"><code>clean-traffic</code></em> network filter, thus the way to do this is to reference it from a custom filter.
+ </div><div class="para">
+ To enable traffic for TCP ports 22 and 80, two rules are added to enable this type of traffic. To allow the guest to send ping traffic a rule is added for ICMP traffic. For simplicity reasons, general ICMP traffic will be allowed to be initated from the guest, and will not be specified to ICMP echo request and response messages. All other traffic will be prevented to reach or be initated by the guest. To do this a rule will be added that drops all other traffic. Assuming the guest is called <code class="filename">test</code> and the interface to associate our filter with is called <code class="filename">eth0</code>, a filter is created named <code class="filename">test-eth0</code>.
+ </div><div class="para">
+ The result of these considerations is the following network filter XML:
+ </div><pre class="screen">
+<filter name='test-eth0'>
+ <!- - This rule references the clean traffic filter to prevent MAC, IP and ARP spoofing. By not providing an IP address parameter, libvirt will detect the IP address the guest is using. - ->
+ <filterref filter='clean-traffic'/>
+
+ <!- - This rule enables TCP ports 22 (ssh) and 80 (http) to be reachable - ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='22'/>
+ </rule>
+
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='80'/>
+ </rule>
+
+ <!- - This rule enables general ICMP traffic to be initiated by the guest including ping traffic - ->
+ <rule action='accept' direction='out'>
+ <icmp/>
+ </rule>>
+
+ <!- - This rule enables outgoing DNS lookups using UDP - ->
+ <rule action='accept' direction='out'>
+ <udp dstportstart='53'/>
+ </rule>
+
+ <!- - This rule drops all other traffic - ->
+ <rule action='drop' direction='inout'>
+ <all/>
+ </rule>
+
+</filter>
+</pre></div></div><br class="example-break" /></div><div class="section" id="sub-sub-sect-samp-filter"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.11.6. Sample custom filter</h4></div></div></div><div class="para">
+ Although one of the rules in the above XML contains the IP address of the guest as either a source or a destination address, the filtering of the traffic works correctly. The reason is that whereas the rule's evaluation occurrs internally on a per-interface basis, the rules are additionaly evaluated based on which (tap) interface has sent or will receive the packet, rather than what their source or destination IP address may be.
+ </div><div class="example"><h6>Example H.12. Sample XML for network interface descriptions</h6><div class="example-contents"><div class="para">
+ An XML fragment for a possible network interface description inside the domain XML of the test guest could then look like this:
+ </div><pre class="screen">
+ [...]
+ <interface type='bridge'>
+ <source bridge='mybridge'/>
+ <filterref filter='test-eth0'/>
+ </interface>
+ [...]
+</pre><div class="para">
+ To more strictly control the ICMP traffic and enforce that only ICMP echo requests can be sent from the guest and only ICMP echo responses be received by the guest, the above ICMP rule can be replaced with the following two rules:
+ </div><pre class="screen">
+ <!- - enable outgoing ICMP echo requests- ->
+ <rule action='accept' direction='out'>
+ <icmp type='8'/>
+ </rule>
+</pre><pre class="screen">
+ <!- - enable incoming ICMP echo replies- ->
+ <rule action='accept' direction='in'>
+ <icmp type='0'/>
+ </rule>
+</pre></div></div><br class="example-break" /><div class="example"><h6>Example H.13. Second example custom filter</h6><div class="example-contents"><div class="para">
+ This example demonstrates how to build a similar filter as in the example above, but extends the list of requirements with an ftp server located inside the guest. The requirements for this filter are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ prevents a guest's interface from MAC, IP, and ARP spoofing
+ </div></li><li class="listitem"><div class="para">
+ opens only TCP ports 22 and 80 in a guest's interface
+ </div></li><li class="listitem"><div class="para">
+ allows the guest to send ping traffic from an interface but does not allow the guest to be pinged on the interface
+ </div></li><li class="listitem"><div class="para">
+ allows the guest to do DNS lookups (UDP towards port 53)
+ </div></li><li class="listitem"><div class="para">
+ enables the ftp server (in active mode) so it can run inside the guest
+ </div></li></ul></div><div class="para">
+ The additional requirement of allowing an FTP server to be run inside the guest maps into the requirement of allowing port 21 to be reachable for FTP control traffic as well as enabling the guest to establish an outgoing TCP connection originating from the guest's TCP port 20 back to the FTP client (FTP active mode). There are several ways of how this filter can be written and two possible solutions are included in this example.
+ </div><div class="para">
+ The first solution makes use of the state attribute of the TCP protocol that provides a hook into the connection tracking framework of the Linux host. For the guest-initiated FTP data connection (FTP active mode) the RELATED state is used to enable detection that the guest-initiated FTP data connection is a consequence of ( or 'has a relationship with' ) an existing FTP control connection, thereby allowing it to pass packets through the firewall. The RELATED state, however, is only valid for the very first packet of the outgoing TCP connection for the FTP data path. Afterwards, the state is ESTABLISHED, which then applies equally to the incoming and outgoing direction. All this is related to the FTP data traffic originating from TCP port 20 of the guest. This then leads to the following solution:
+ </div><pre class="screen">
+<filter name='test-eth0'>
+ <!- - This filter (eth0) references the <code class="filename">clean traffic</code> filter to prevent MAC, IP, and ARP spoofing. By not providing an IP address parameter, libvirt will detect the IP address the guest is using. - ->
+ <filterref filter='clean-traffic'/>
+
+ <!- - This rule enables TCP port 21 (FTP-control) to be reachable - ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='21'/>
+ </rule>
+
+ <!- - This rule enables TCP port 20 for guest-initiated FTP data connection related to an existing FTP control connection - ->
+ <rule action='accept' direction='out'>
+ <tcp srcportstart='20' state='RELATED,ESTABLISHED'/>
+ </rule>
+
+ <!- - This rule accepts all packets from a client on the FTP data connection - ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='20' state='ESTABLISHED'/>
+ </rule>
+
+ <!- - This rule enables TCP port 22 (SSH) to be reachable - ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='22'/>
+ </rule>
+
+ <!- -This rule enables TCP port 80 (HTTP) to be reachable - ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='80'/>
+ </rule>
+
+ <!- - This rule enables general ICMP traffic to be initiated by the guest, including ping traffic - ->
+ <rule action='accept' direction='out'>
+ <icmp/>
+ </rule>
+
+ <!- - This rule enables outgoing DNS lookups using UDP - ->
+ <rule action='accept' direction='out'>
+ <udp dstportstart='53'/>
+ </rule>
+
+ <!- - This rule drops all other traffic - ->
+ <rule action='drop' direction='inout'>
+ <all/>
+ </rule>
+
+</filter>
+</pre><div class="para">
+ Before trying out a filter using the RELATED state, you have to make sure that the appropriate connection tracking module has been loaded into the host's kernel. Depending on the version of the kernel, you must run either one of the following two commands before the FTP connection with the guest is established:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ #<code class="command">modprobe nf_conntrack_ftp</code> - where available OR
+ </div></li><li class="listitem"><div class="para">
+ #<code class="command">modprobe ip_conntrack_ftp</code> if above is not available
+ </div></li></ul></div><div class="para">
+ If protocols other than FTP are used in conjunction with the RELATED state, their corresponding module must be loaded. Modules are available for the protocols: ftp, tftp, irc, sip, sctp, and amanda.
+ </div><div class="para">
+ The second solution makes use of the state flags of connections more than the previous solution did. This solution takes advantage of the fact that the NEW state of a connection is valid when the very first packet of a traffic flow is detected. Subsequently, if the very first packet of a flow is accepted, the flow becomes a connection and thus enters into the ESTABLISHED state. Therefore a general rule can be written for allowing packets of ESTABLISHED connections to reach the guest or be sent by the guest. This is done writing specific rules for the very first packets identified by the NEW state and dictates the ports that the data is acceptable. All packets meant for ports that are not explicitly accepted are dropped, thus not reaching an ESTABLISHED state. Any subsequent packets sent from that port are dropped as well.
+ </div><pre class="screen">
+<filter name='test-eth0'>
+ <!- - This filter references the <code class="filename">clean traffic</code> filter to prevent MAC, IP and ARP spoofing. By not providing and IP address parameter, libvirt will detect the IP address the VM is using. - ->
+ <filterref filter='clean-traffic'/>
+
+ <!- - This rule allows the packets of all previously accepted connections to reach the guest - ->
+ <rule action='accept' direction='in'>
+ <all state='ESTABLISHED'/>
+ </rule>
+
+ <!- - This rule allows the packets of all previously accepted and related connections be sent from the guest - ->
+ <rule action='accept' direction='out'>
+ <all state='ESTABLISHED,RELATED'/>
+ </rule>
+
+ <!- - This rule enables traffic towards port 21 (FTP) and port 22 (SSH)- ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='21' dstportend='22' state='NEW'/>
+ </rule>
+
+ <!- - This rule enables traffic towards port 80 (HTTP) - ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='80' state='NEW'/>
+ </rule>
+
+ <!- - This rule enables general ICMP traffic to be initiated by the guest, including ping traffic - ->
+ <rule action='accept' direction='out'>
+ <icmp state='NEW'/>
+ </rule>
+
+ <!- - This rule enables outgoing DNS lookups using UDP - ->
+ <rule action='accept' direction='out'>
+ <udp dstportstart='53' state='NEW'/>
+ </rule>
+
+ <!- - This rule drops all other traffic - ->
+ <rule action='drop' direction='inout'>
+ <all/>
+ </rule>
+
+</filter>
+</pre></div></div><br class="example-break" /></div></div><div class="section" id="sub-sect-limitations-filters-network-subsystem"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.10.12. Limitations</h3></div></div></div><div class="para">
+ The following is a list of the currently known limitations of the network filtering subsystem.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ VM migration is only supported if the whole filter tree that is referenced by a guest's top level filter is also available on the target host. The network filter <code class="filename">clean-traffic</code> for example should be available on all libvirt installations and thus enable migration of guests that reference this filter. To assure version compatibility is not a problem make sure you are using the most current version of libvirt by updating the package regurally.
+ </div></li><li class="listitem"><div class="para">
+ Migration must occur between libvirt insallations of version 0.8.1 or later in order not to lose the network traffic filters associated with an interface.
+ </div></li><li class="listitem"><div class="para">
+ VLAN (802.1Q) packets, if sent by a guest, cannot be filtered with rules for protocol IDs arp, rarp, ipv4 and ipv6. They can only be filtered with protocol IDs, MAC and VLAN. Therefore, the example filter clean-traffic <a class="xref" href="#ex-net-filtering">Example H.1, “An example of network filtering”</a> will not work as expected.
+ </div></li></ul></div></div></div></div><div xml:lang="en-US" class="appendix" id="appe-Virtualization-Additional_resources" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Additional resources</h1></div></div></div><div class="para">
+ To learn more about virtualization and Fedora, refer to the following resources.
+ </div><div class="section" id="sect-Virtualization-Additional_resources-Online_resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">I.1. Online resources</h2></div></div></div><a id="idm95080192" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><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 class="listitem"><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 class="listitem"><div class="para">
+ Open Virtualization Center
+ </div><div class="para">
+ <a href="http://www.openvirtualization.com/">http://www.openvirtualization.com</a>
+ </div></li><li class="listitem"><div class="para">
+ Fedora Documentation
+ </div><div class="para">
+ <a href="http://docs.fedoraproject.org">http://docs.fedoraproject.org</a>
+ </div></li><li class="listitem"><div class="para">
+ Virtualization technologies overview
+ </div><div class="para">
+ <a href="http://virt.kernelnewbies.org/">http://virt.kernelnewbies.org</a>
+ </div></li><li class="listitem"><div class="para">
+ Fedora Community
+ </div><div class="para">
+ <a href="https://fedoraproject.org/en/join-fedora">https://fedoraproject.org/en/join-fedora</a>
+ </div></li></ul></div></div><div class="section" id="sect-Virtualization-Additional_resources-Installed_documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">I.2. Installed documentation</h2></div></div></div><a id="idm98943168" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><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 class="listitem"><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 class="listitem"><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 class="listitem"><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 distributions inside of virtual machines.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/virt-manager-<em class="replaceable"><code><version-number></code></em></code> — Provides documentation on the Virtual Machine Manager, which provides a graphical tool for administering virtual machines.
+ </div></li></ul></div></div></div><div xml:lang="en-US" class="appendix" id="ch-lib-dom-xml" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Manipulating the domain xml</h1></div></div></div><div class="para">
+ This section describes the XML format used to represent one or more libvirt domains. Whereas a libvirt domain refers to a specified guest virtual machine, here the term <em class="firstterm">domain</em> refers to the root <code class="sgmltag-starttag"><domain></code> element required for defining the parameters of all guest virtual machines. The <code class="sgmltag-starttag"><domain></code> element has two attributes: <code class="sgmltag-attribute">type</code> specifies the hypervisor used for running the domain. The allowed values are driver specific, but include <code class="sgmltag-attvalue"> KVM</code> and others. <code class="sgmltag-attribute">id</code> is a unique integer identifier for the running guest machine. Inactive machines have no id value. The sections in this chapter will address the components of the domain XML. Additional chapters in this manual may refer to this chapter when manipulation of the domain XML is required.
+ </div><div class="section" id="sect-gen-metadata"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.1. General information and metadata</h2></div></div></div><div class="para">
+ This information is in this part of the domain XML:
+ </div><div class="figure" id="ch-lib-dom-xml-example"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain</span><span class="perl_Others"> type=</span><span class="perl_String">'xen'</span><span class="perl_Others"> id=</span><span class="perl_String">'3'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><name></span>fv0<span class="perl_Keyword"></name></span>
+ <span class="perl_Keyword"><uuid></span>4dea22b31d52d8f32516782e98ab3fa0<span class="perl_Keyword"></uuid></span>
+ <span class="perl_Keyword"><title></span>A short description - title - of the domain<span class="perl_Keyword"></title></span>
+ <span class="perl_Keyword"><description></span>Some human readable description<span class="perl_Keyword"></description></span>
+ <span class="perl_Keyword"><metadata></span>
+ <span class="perl_Keyword"><app1:foo</span><span class="perl_Others"> xmlns:app1=</span><span class="perl_String">"http://app1.org/app1/"</span><span class="perl_Keyword">></span>..<span class="perl_Keyword"></app1:foo></span>
+ <span class="perl_Keyword"><app2:bar</span><span class="perl_Others"> xmlns:app2=</span><span class="perl_String">"http://app1.org/app2/"</span><span class="perl_Keyword">></span>..<span class="perl_Keyword"></app2:bar></span>
+ <span class="perl_Keyword"></metadata></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.1. Domain XML metadata</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-gen-metadata"><h6>Table J.1. General metadata elements</h6><div class="table-contents"><table summary="General metadata elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><name></code>
+ </td><td class="">
+ Assigns a name for the virtual machine. This name should consist only of alpha-numeric characters and is required to be unique within the scope of a single host. It is often used to form the filename for storing the persistent configuration files.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><uuid></code>
+ </td><td class="">
+ assigns a globally unique identifier for the virtual machine. The format must be RFC 4122 compliant, eg <code class="sgmltag-attvalue">3e3fce45-4f53-4fa7-bb32-11f34168b82b</code>. If omitted when defining/creating a new machine, a random UUID is generated. It is also possible to provide the UUID via a sysinfo specification.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><title></code>
+ </td><td class="">
+ <code class="sgmltag-element">title</code> Creates space for a short description of the domain. The title should not contain any newlines.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><description></code>
+ </td><td class="">
+ Different from the title, This data is not used by libvirt in any way, it can contain any information the user wants to display.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><metadata></code>
+ </td><td class="">
+ Can be used by applications to store custom metadata in the form of XML nodes/trees. Applications must use custom namespaces on their XML nodes/trees, with only one top-level element per namespace (if the application needs structure, they should have sub-elements to their namespace element)
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sect-dom-xml-op-sys-boot"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.2. Operating system booting</h2></div></div></div><div class="para">
+ There are a number of different ways to boot virtual machines each with their own pros and cons. Each one is described in the sub-sections that follow and include: BIOS bootloader, Host bootloader, direct kerel boot, and container boot.
+ </div><div class="section" id="sub-sect-op-sys-boot-bios-boot"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.2.1. BIOS bootloader</h3></div></div></div><div class="para">
+ Booting via the BIOS is available for hypervisors supporting full virtualization. In this case the BIOS has a boot order priority (floppy, harddisk, cdrom, network) determining where to obtain/find the boot image. The OS section of the domain XML contatins the information as follows:
+ </div><div class="figure" id="fig-op-sys-boot-bios-boot"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><os></span>
+ <span class="perl_Keyword"><type></span>hvm<span class="perl_Keyword"></type></span>
+ <span class="perl_Keyword"><loader></span>/usr/lib/xen/boot/hvmloader<span class="perl_Keyword"></loader></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> dev=</span><span class="perl_String">'hd'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> dev=</span><span class="perl_String">'cdrom'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><bootmenu</span><span class="perl_Others"> enable=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><smbios</span><span class="perl_Others"> mode=</span><span class="perl_String">'sysinfo'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><bios</span><span class="perl_Others"> useserial=</span><span class="perl_String">'yes'</span><span class="perl_Others"> rebootTimeout=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></os></span>
+ ...
+</pre></div><h6>Figure J.2. BOIS bootloader domain XML</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-biosbootloader-os"><h6>Table J.2. BIOS bootloader elements</h6><div class="table-contents"><table summary="BIOS bootloader elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><type></code>
+ </td><td class="">
+ Specifies the type of operating system to be booted on the guest virtual machine. <code class="sgmltag-attvalue">hvm</code> indicates that the OS is one designed to run on bare metal, so requires full virtualization. <code class="sgmltag-attvalue">linux</code> refers to an OS that supports the Xen 3 hypervisor guest ABI. There are also two optional attributes, <code class="sgmltag-attribute">arch</code> specifying the CPU architecture to virtualization, and <code class="sgmltag-attribute">machine</code> referring to the machine type. Refer to <a href="http://libvirt.org/formatcaps.html"><em class="citetitle">Driver Capabilities</em></a> for more information.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><loader></code>
+ </td><td class="">
+ refers to a piece of firmware that is used to assist the domain creation process. It is only needed for using Xen fully virtualized domains.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><boot></code>
+ </td><td class="">
+ takes one of the values:<code class="sgmltag-attvalue">fd</code>, <code class="sgmltag-attvalue">hd</code>, <code class="sgmltag-attvalue">cdrom</code> or <code class="sgmltag-attvalue">network</code> and is used to specify the next boot device to consider. The boot element can be repeated multiple times to setup a priority list of boot devices to try in turn. Multiple devices of the same type are sorted according to their targets while preserving the order of buses. After defining the domain, its XML configuration returned by libvirt (through virDomainGetXMLDesc) lists devices in the sorted order. Once sorted, the first device is marked as bootable. For more information see <a href="http://libvirt.org/formatdomain.html#elements"><em class="citetitle">BIOS bootloader</em></a>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><bootmenu></code>
+ </td><td class="">
+ determines whether or not to enable an interactive boot menu prompt on guest startup. The <code class="sgmltag-attribute">enable</code> attribute can be either <code class="sgmltag-attvalue">yes</code> or <code class="sgmltag-attvalue">no</code>. If not specified, the hypervisor default is used
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><smbios></code>
+ </td><td class="">
+ determines how SMBIOS information is made visible in the guest. The <code class="sgmltag-attribute">mode</code> attribute must be specified, as either <code class="sgmltag-attvalue">emulate</code> (lets the hypervisor generate all values), <code class="sgmltag-attvalue">host</code>(copies all of Block 0 and Block 1, except for the UUID, from the host's SMBIOS values; the virConnectGetSysinfo call can be used to see what values are copied), or <code class="sgmltag-attvalue">sysinfo</code> (uses the values in the sysinfo element). If not specified, the hypervisor default setting is used.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><bios></code>
+ </td><td class="">
+ This element has attribute <code class="sgmltag-attribute">useserial</code> with possible values <code class="sgmltag-attvalue">yes</code> or <code class="sgmltag-attvalue">no</code>. The attribute enables or disables Serial Graphics Adapter which allows users to see BIOS messages on a serial port. Therefore, one needs to have serial port defined. Note there is another attribute, <code class="sgmltag-attribute">rebootTimeout</code> that controls whether and after how long the guest should start booting again in case the boot fails (according to BIOS). The value is in milliseconds with maximum of <code class="sgmltag-attvalue">65535</code> and special value <code class="sgmltag-attvalue">-1</code> disables the reboot.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sect-op-sys-host-boot"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.2.2. Host bootloader</h3></div></div></div><div class="para">
+ Hypervisors employing paravirtualization do not usually emulate a BIOS, but instead the host is responsible for the operating system boot. This may use a pseudo-bootloader in the host to provide an interface to choose a kernel for the guest. An example is pygrub with Xen.
+ </div><div class="figure" id="fig-op-sys-host-boot"><div class="figure-contents"><pre class="programlisting">
+ ...
+ <span class="perl_Keyword"><bootloader></span>/usr/bin/pygrub<span class="perl_Keyword"></bootloader></span>
+ <span class="perl_Keyword"><bootloader_args></span>--append single<span class="perl_Keyword"></bootloader_args></span>
+ ...
+</pre></div><h6>Figure J.3. Host bootloader domain XML</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-hostbootloader-os"><h6>Table J.3. BIOS bootloader elements</h6><div class="table-contents"><table summary="BIOS bootloader elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><bootloader></code>
+ </td><td class="">
+ provides a fully qualified path to the bootloader executable in the host OS. This bootloader will choose which kernel to boot. The required output of the bootloader is dependent on the hypervisor in use.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><bootloader_args></code>
+ </td><td class="">
+ allows command line arguments to be passed to the bootloader (optional command)
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sect-op-sys-dir-kern-boot"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.2.3. Direct kernel boot</h3></div></div></div><div class="para">
+ When installing a new guest OS, it is often useful to boot directly from a kernel and initrd stored in the host OS, allowing command line arguments to be passed directly to the installer. This capability is usually available for both para and full virtualized guests.
+ </div><div class="figure" id="fig-op-sys-dir-kern-boot"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><os></span>
+ <span class="perl_Keyword"><type></span>hvm<span class="perl_Keyword"></type></span>
+ <span class="perl_Keyword"><loader></span>/usr/lib/xen/boot/hvmloader<span class="perl_Keyword"></loader></span>
+ <span class="perl_Keyword"><kernel></span>/root/f8-i386-vmlinuz<span class="perl_Keyword"></kernel></span>
+ <span class="perl_Keyword"><initrd></span>/root/f8-i386-initrd<span class="perl_Keyword"></initrd></span>
+ <span class="perl_Keyword"><cmdline></span>console=ttyS0 ks=http://example.com/f8-i386/os/<span class="perl_Keyword"></cmdline></span>
+ <span class="perl_Keyword"><dtb></span>/root/ppc.dtb<span class="perl_Keyword"></dtb></span>
+ <span class="perl_Keyword"></os></span>
+ ...
+
+</pre></div><h6>Figure J.4. Direct kernel boot</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-dir-kernelboot-os"><h6>Table J.4. Direct kernel boot elements</h6><div class="table-contents"><table summary="Direct kernel boot elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><type></code>
+ </td><td class="">
+ same as described in the BIOS boot section
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><loader></code>
+ </td><td class="">
+ same as described in the BIOS boot section
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><kernel></code>
+ </td><td class="">
+ secifies the fully-qualified path to the kernel image in the host OS
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><initrd></code>
+ </td><td class="">
+ specifies the fully-qualified path to the (optional) ramdisk image in the host OS.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><cmdline></code>
+ </td><td class="">
+ specifies arguments to be passed to the kernel (or installer) at boot time. This is often used to specify an alternate primary console (eg serial port), or the installation media source / kickstart file
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sect-op-sys-cont-boot"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.2.4. Container boot</h3></div></div></div><div class="para">
+ When booting a domain using container based virtualization, instead of a kernel or boot image, a path to the init binary is required, using the init element. By default this will be launched with no arguments. To specify the initial argv, use the <code class="sgmltag-element">initarg</code> element, repeated as many times as required. The <code class="sgmltag-element">cmdline</code> element, provides an equivalent to <code class="filename">/proc/cmdline</code> but will not effect <code class="sgmltag-starttag"><initarg></code>.
+ </div><div class="figure" id="fig-op-sys-cont-boot"><div class="figure-contents"><pre class="programlisting">
+>
+ ...
+ <span class="perl_Keyword"><os></span>
+ <span class="perl_Keyword"><type></span>hvm<span class="perl_Keyword"></type></span>
+ <span class="perl_Keyword"><loader></span>/usr/lib/xen/boot/hvmloader<span class="perl_Keyword"></loader></span>
+ <span class="perl_Keyword"><kernel></span>/root/f8-i386-vmlinuz<span class="perl_Keyword"></kernel></span>
+ <span class="perl_Keyword"><initrd></span>/root/f8-i386-initrd<span class="perl_Keyword"></initrd></span>
+ <span class="perl_Keyword"><cmdline></span>console=ttyS0 ks=http://example.com/f8-i386/os/<span class="perl_Keyword"></cmdline></span>
+ <span class="perl_Keyword"><dtb></span>/root/ppc.dtb<span class="perl_Keyword"></dtb></span>
+ <span class="perl_Keyword"></os></span>
+ ...
+
+</pre></div><h6>Figure J.5. Container boot</h6></div><br class="figure-break" /></div></div><div class="section" id="sect-smbios-sys-info"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.3. SMBIOS system information</h2></div></div></div><div class="para">
+ Some hypervisors allow control over what system information is presented to the guest (for example, SMBIOS fields can be populated by a hypervisor and inspected via the dmidecode command in the guest). The optional sysinfo element covers all such categories of information.
+ </div><div class="figure"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><os></span>
+ <span class="perl_Keyword"><smbios</span><span class="perl_Others"> mode=</span><span class="perl_String">'sysinfo'</span><span class="perl_Keyword">/></span>
+ ...
+ <span class="perl_Keyword"></os></span>
+ <span class="perl_Keyword"><sysinfo</span><span class="perl_Others"> type=</span><span class="perl_String">'smbios'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><bios></span>
+ <span class="perl_Keyword"><entry</span><span class="perl_Others"> name=</span><span class="perl_String">'vendor'</span><span class="perl_Keyword">></span>LENOVO<span class="perl_Keyword"></entry></span>
+ <span class="perl_Keyword"></bios></span>
+ <span class="perl_Keyword"><system></span>
+ <span class="perl_Keyword"><entry</span><span class="perl_Others"> name=</span><span class="perl_String">'manufacturer'</span><span class="perl_Keyword">></span>Fedora<span class="perl_Keyword"></entry></span>
+ <span class="perl_Keyword"><entry</span><span class="perl_Others"> name=</span><span class="perl_String">'vendor'</span><span class="perl_Keyword">></span>Virt-Manager<span class="perl_Keyword"></entry></span>
+ <span class="perl_Keyword"></system></span>
+ <span class="perl_Keyword"></sysinfo></span>
+ ...
+
+</pre></div><h6>Figure J.6. SMBIOS system information</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-starttag"><sysinfo></code> element has a mandatory attribute <code class="sgmltag-attribute">type</code> that determines the layout of sub-elements, and may be defined as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">smbios</code> - Sub-elements call out specific SMBIOS values, which will affect the guest if used in conjunction with the smbios sub-element of the os element. Each sub-element of sysinfo names a SMBIOS block, and within those elements can be a list of entry elements that describe a field within the block. The following blocks and entries are recognized:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">bios</code> - This is block 0 of SMBIOS, with entry names drawn from <code class="sgmltag-attribute">vendor</code>, <code class="sgmltag-attribute">version</code>, <code class="sgmltag-attribute">date</code>, and <code class="sgmltag-attribute">release</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><system></code> - This is block 1 of SMBIOS, with entry names drawn from <code class="sgmltag-attribute">manufacturer</code>, <code class="sgmltag-attribute">product</code>, <code class="sgmltag-attribute">version</code>, <code class="sgmltag-attribute">serial</code>, <code class="sgmltag-attribute">uuid</code>, <code class="sgmltag-attribute">sku</code>, and <code class="sgmltag-attribute">family</code>. If a <code class="sgmltag-attribute">uuid</code> entry is provided alongside a top-level uuid element, the two values must match.
+ </div></li></ul></div></li></ul></div></div><div class="section" id="sect-cpu-allocation"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.4. CPU allocation</h2></div></div></div><div class="figure"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain></span>
+ ...
+ <span class="perl_Keyword"><vcpu</span><span class="perl_Others"> placement=</span><span class="perl_String">'static'</span><span class="perl_Others"> cpuset=</span><span class="perl_String">"1-4,^3,6"</span><span class="perl_Others"> current=</span><span class="perl_String">"1"</span><span class="perl_Keyword">></span>2<span class="perl_Keyword"></vcpu></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.7. CPU allocation</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-starttag"><cpu></code> element defines the maximum number of virtual CPUs allocated for the guest OS, which must be between 1 and the maximum supported by the hypervisor. This element can contain an optional <code class="sgmltag-attribute">cpuset</code> attribute, which is a comma-separated list of physical CPU numbers that domain process and virtual CPUs can be pinned to by default.
+ </div><div class="para">
+ Note that the pinning policy of domain process and virtual CPUs can be specified separately by using the <code class="sgmltag-attribute">cputune</code> attribute. If attribute <code class="sgmltag-attribute">emulatorpin</code> of <code class="sgmltag-starttag"><cputune></code> is specified, <code class="sgmltag-attribute">cpuset</code> specified by <code class="sgmltag-starttag"><vcpu></code> will be ingored.
+ </div><div class="para">
+ Similarly, virtual CPUs that have set a value for <code class="sgmltag-attribute">vcpupin</code> cause <code class="sgmltag-attribute">cpuset</code> settings to be ignored. For virtual CPUs where <code class="sgmltag-attribute">vcpupin</code> is not specified, it will be pinned to the physical CPUs specified by <code class="sgmltag-attribute">cpuset</code>. Each element in the <code class="sgmltag-attribute">cpuset</code> list is either a single CPU number, a range of CPU numbers, or a caret (^) followed by a CPU number to be excluded from a previous range. The sgmltagal attribute <code class="sgmltag-attribute">current</code> can be used to specify whether fewer than the maximum number of virtual CPUs should be enabled.
+ </div><div class="para">
+ The optional attribute <code class="sgmltag-attribute">placement</code> can be used to indicate the CPU placement mode for domain process, its value can be either <code class="sgmltag-attvalue">static</code> or <code class="sgmltag-attvalue">auto</code>, which defaults to <code class="sgmltag-attvalue">placement</code>, or <code class="sgmltag-attvalue">numatune</code>, or <code class="sgmltag-attvalue">static</code> if <code class="sgmltag-element">cpuset</code> is specified. <code class="sgmltag-attvalue">auto</code> indicates the domain process will be pinned to the advisory nodeset from querying numad, and the value of attribute <code class="sgmltag-attribute">cpuset</code> will be ignored if it's specified. If both <code class="sgmltag-attribute">cpuset</code> and <code class="sgmltag-attribute">placement</code> are not specified, or if placement is <code class="sgmltag-attvalue">static</code>, but no <code class="sgmltag-attribute">cpuset</code> is specified, the do
main process will be pinned to all the available physical CPUs.
+ </div></div><div class="section" id="sect-cpu-tuning"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.5. CPU tuning</h2></div></div></div><div class="figure" id="fig-cpu-tuning"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain></span>
+ ...
+ <span class="perl_Keyword"><cputune></span>
+ <span class="perl_Keyword"><vcpupin</span><span class="perl_Others"> vcpu=</span><span class="perl_String">"0"</span><span class="perl_Others"> cpuset=</span><span class="perl_String">"1-4,^2"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><vcpupin</span><span class="perl_Others"> vcpu=</span><span class="perl_String">"1"</span><span class="perl_Others"> cpuset=</span><span class="perl_String">"0,1"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><vcpupin</span><span class="perl_Others"> vcpu=</span><span class="perl_String">"2"</span><span class="perl_Others"> cpuset=</span><span class="perl_String">"2,3"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><vcpupin</span><span class="perl_Others"> vcpu=</span><span class="perl_String">"3"</span><span class="perl_Others"> cpuset=</span><span class="perl_String">"0,4"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><emulatorpin</span><span class="perl_Others"> cpuset=</span><span class="perl_String">"1-3"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><shares></span>2048<span class="perl_Keyword"></shares></span>
+ <span class="perl_Keyword"><period></span>1000000<span class="perl_Keyword"></period></span>
+ <span class="perl_Keyword"><quota></span>-1<span class="perl_Keyword"></quota></span>
+ <span class="perl_Keyword"><emulator_period></span>1000000<span class="perl_Keyword"></emulator_period></span>
+ <span class="perl_Keyword"><emulator_quota></span>-1<span class="perl_Keyword"></emulator_quota></span>
+ <span class="perl_Keyword"></cputune></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.8. CPU tuning</h6></div><br class="figure-break" /><div class="para">
+ Although all are optional, the components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-cpu-turn-elem"><h6>Table J.5. CPU tuning elements</h6><div class="table-contents"><table summary="CPU tuning elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><cputune></code>
+ </td><td class="">
+ Provides details regarding the CPU tunable parameters for the domain. This is optional.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><vcpupin></code>
+ </td><td class="">
+ Specifies which of host's physical CPUs the domain VCPU will be pinned to. If this is omitted, and attribute <code class="sgmltag-attribute">cpuset</code> of element <code class="sgmltag-starttag"><vcpu></code> is not specified, the vCPU is pinned to all the physical CPUs by default. It contains two required attributes, the attribute <code class="sgmltag-element">vcpu</code> specifies <code class="sgmltag-attribute">id</code>, and the attribute <code class="sgmltag-attribute">cpuset</code> is same as attribute <code class="sgmltag-attribute">cpuset</code> of element <code class="sgmltag-starttag"><vCPU></code>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><emulatorpin></code>
+ </td><td class="">
+ Specifies which of the host physical CPUs, the "emulator", a subset of a domains not including vcpu, will be pinned to. If this is omitted, and attribute <code class="sgmltag-attribute">cpuset</code> of element <code class="sgmltag-starttag"><vcpu></code> is not specified, the "emulator" is pinned to all the physical CPUs by default. It contains one required attribute <code class="sgmltag-attribute">cpuset</code> specifying which physical CPUs to pin to. <code class="sgmltag-element">emulatorpin</code> is not allowed if attribute <code class="sgmltag-attribute">placement</code> of element <code class="sgmltag-starttag"><vcpu></code> is <code class="sgmltag-attvalue">auto</code>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><shares></code>
+ </td><td class="">
+ Specifies the proportional weighted share for the domain. If this is omitted, it defaults to the OS provided defaults. If there is no unit for the value, itn is calculated relative to the setting of other guest virtual machines. For example, if a guest virtual machine is configured with value 2048 will get twice as much CPU time as a guest virtual machine configured with value 1024.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><period></code>
+ </td><td class="">
+ Specifies the enforcement intervalin microseconds. By using <code class="sgmltag-attribute">period</code>, each of the domain's vcpu will not be allowed to consume more than its alloted quota worth of runtime. This value should be within the following range: <code class="literal">1000-1000000</code>. A <code class="sgmltag-attribute">period></code> with a value of <code class="sgmltag-attvalue">0</code> means no value.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><quota></code>
+ </td><td class="">
+ Specifies the maximum allowed bandwidth in microseconds. A domain with <code class="sgmltag-element">quota</code> as any negative value indicates that the domain has infinite bandwidth, which means that it is not bandwidth controlled. The value should be within the following range:<code class="sgmltag-attvalue">1000 - 18446744073709551</code> or less than <code class="sgmltag-attvalue">0</code>. A <code class="sgmltag-attribute">quota</code> with value of <code class="sgmltag-attvalue">0</code> means no value. You can use this feature to ensure that all vcpus run at the same speed.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><emulator_period></code>
+ </td><td class="">
+ Specifies the enforcement interval in microseconds. Within an <code class="sgmltag-starttag"><emulator_period></code>, emulator threads (those excluding vcpus) of the domain will not be allowed to consume more than the <code class="sgmltag-starttag"><emulator_quota></code> worth of runtime. The <code class="sgmltag-starttag"><emulator_period></code> value should be in the following range: <code class="sgmltag-attvalue">1000 - 1000000</code>. An <code class="sgmltag-starttag"><emulator_period></code> with value of <code class="sgmltag-attvalue">0</code>, means no value.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><emulator_quota></code>
+ </td><td class="">
+ Specifies the maximum allowed bandwidth in microseconds for the domain's emulator threads (those excluding vcpus). A domain with an <code class="sgmltag-starttag"><emulator_quota></code> as a negative value indicates that the domain has infinite bandwidth for emulator threads (those excluding vcpus), which means that it is not bandwidth controlled. The value should be in the following range: <code class="sgmltag-attvalue">1000 - 18446744073709551</code>, or less than <code class="sgmltag-attvalue">0</code>. An <code class="sgmltag-starttag"><emulator_quota></code> with value <code class="sgmltag-attvalue">0</code> means no value.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sect-mem-back"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.6. Memory backing</h2></div></div></div><div class="para">
+ Memory backing allows the hypervisor to properly manage large pages within the guest. Once confured the following domain XML is effected:
+ </div><div class="figure" id="fig-mem-back"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain></span>
+ ...
+ <span class="perl_Keyword"><memoryBacking></span>
+ <span class="perl_Keyword"><hugepages/></span>
+ <span class="perl_Keyword"></memoryBacking></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.9. Memory backing</h6></div><br class="figure-break" /><div class="para">
+ The optional <code class="sgmltag-starttag"><memoryBacking></code> element, may have an <code class="sgmltag-starttag"><hugepages></code> element set within it. This tells the hypervisor that the guest should have its memory allocated using hugepages instead of the normal native page size.
+ </div></div><div class="section" id="sect-libvirt-dom-xml-mem-tuning"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.7. Memory tuning</h2></div></div></div><div class="figure" id="fig-dom-xml-mem-tuning"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain></span>
+ ...
+ <span class="perl_Keyword"><memtune></span>
+ <span class="perl_Keyword"><hard_limit</span><span class="perl_Others"> unit=</span><span class="perl_String">'G'</span><span class="perl_Keyword">></span>1<span class="perl_Keyword"></hard_limit></span>
+ <span class="perl_Keyword"><soft_limit</span><span class="perl_Others"> unit=</span><span class="perl_String">'M'</span><span class="perl_Keyword">></span>128<span class="perl_Keyword"></soft_limit></span>
+ <span class="perl_Keyword"><swap_hard_limit</span><span class="perl_Others"> unit=</span><span class="perl_String">'G'</span><span class="perl_Keyword">></span>2<span class="perl_Keyword"></swap_hard_limit></span>
+ <span class="perl_Keyword"><min_guarantee</span><span class="perl_Others"> unit=</span><span class="perl_String">'bytes'</span><span class="perl_Keyword">></span>67108864<span class="perl_Keyword"></min_guarantee></span>
+ <span class="perl_Keyword"></memtune></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.10. Memory tuning</h6></div><br class="figure-break" /><div class="para">
+ Although all are optional, the components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-mem-tun-elem"><h6>Table J.6. Memory tuning elements</h6><div class="table-contents"><table summary="Memory tuning elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><memtune></code>
+ </td><td class="">
+ Provides details regarding the memory tunable parameters for the domain. If this is omitted, it defaults to the OS provided defaults. The parameters are applied to the process as a whole therefore when setting limits, one needs to add up guest RAM, guest video RAM, and allow for some memory overhead. The last piece is hard to determine so one use trial and error. For each tunable, it is possible to designate which unit the number is in on input, using the same values as for <code class="sgmltag-starttag"><memory></code>. For backwards compatibility, output is always in KiB.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><hard_limit></code>
+ </td><td class="">
+ This is the maximum memory the guest can use. The <code class="sgmltag-attribute">unit</code> for this value is expressed in <code class="literal">kibibytes</code> (i.e. blocks of 1024 bytes)
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><soft_limit></code>
+ </td><td class="">
+ This is the memory limit to enforce during memory contention. The <code class="sgmltag-attribute">unit</code> for this value is expressed in kibibytes (i.e. blocks of 1024 bytes)
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><swap_hard_limit></code>
+ </td><td class="">
+ This is the maximum memory plus swap the guest can use. The <code class="sgmltag-attribute">unit</code> for this value is expressed in kibibytes (i.e. blocks of 1024 bytes). This has to be more than <code class="sgmltag-starttag"><hard_limit></code> value provided
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><min_guarantee></code>
+ </td><td class="">
+ This is the guaranteed minimum memory allocation for the guest. The units for this value is expressed in kibibytes (i.e. blocks of 1024 bytes)
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sect-libvirt-dom-xml-numa-node-tuning"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.8. NUMA node tuning</h2></div></div></div><div class="para">
+ Once NUMA node tuning is done using conventional managment tools the following domain XML parameters are effected:
+ </div><div class="figure" id="fig-dom-xml-numa-node-tuning"><div class="figure-contents"><pre class="programlisting">
+>
+<span class="perl_Keyword"><domain></span>
+ ...
+ <span class="perl_Keyword"><numatune></span>
+ <span class="perl_Keyword"><memory</span><span class="perl_Others"> mode=</span><span class="perl_String">"strict"</span><span class="perl_Others"> nodeset=</span><span class="perl_String">"1-4,^3"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></numatune></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.11. NUMA node tuning</h6></div><br class="figure-break" /><div class="para">
+ Although all are optional, the components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-numa-tun-elem"><h6>Table J.7. NUMA node tuning elements</h6><div class="table-contents"><table summary="NUMA node tuning elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><numatune></code>
+ </td><td class="">
+ Provides details of how to tune the performance of a NUMA host via controlling NUMA policy for domain process.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><memory></code>
+ </td><td class="">
+ Specifies how to allocate memory for the domain process on a NUMA host. It contains several optional attributes. Attribute <code class="sgmltag-attribute">mode</code> is either <code class="sgmltag-attvalue">interleave</code>, <code class="sgmltag-attvalue">strict</code>, or <code class="sgmltag-attvalue">preferred</code>. If no value is given it defaults to <code class="sgmltag-attvalue">strict</code>. Attribute <code class="sgmltag-attribute">nodeset</code> specifies the NUMA nodes, using the same syntax as attribute <code class="sgmltag-attribute">cpuset</code> of element <code class="sgmltag-starttag"><vcpu></code>. Attribute <code class="sgmltag-attribute">placement</code> can be used to indicate the memory placement mode for the domain process. Its value can be either <code class="sgmltag-attvalue">static</code> or <code class="sgmltag-attvalue">auto</code>. If attribute <code class="sgmltag-starttag"><nodeset></code> is specified it defaults to the
<code class="sgmltag-starttag"><placement></code> of <code class="sgmltag-starttag"><vcpu></code>, or <code class="sgmltag-attvalue">static</code>. <code class="sgmltag-attvalue">auto</code> indicates the domain process will only allocate memory from the advisory nodeset returned from querying numad and the value of attribute nodeset will be ignored if it's specified. If attribute <code class="sgmltag-attribute">placement</code> of <code class="sgmltag-element">vcpu</code> is <code class="sgmltag-attvalue">auto</code>, and attribute <code class="sgmltag-starttag"><numatune></code> is not specified, a default numatune with <code class="sgmltag-starttag"><placement></code> <code class="sgmltag-attvalue">auto</code> and mode <code class="sgmltag-attvalue">strict</code> will be added implicitly.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sect-libvirt-dom-xml-blk-io-tuning"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.9. Block I/O tuning</h2></div></div></div><div class="figure" id="fig-blk-io-tuning"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain></span>
+ ...
+ <span class="perl_Keyword"><blkiotune></span>
+ <span class="perl_Keyword"><weight></span>800<span class="perl_Keyword"></weight></span>
+ <span class="perl_Keyword"><device></span>
+ <span class="perl_Keyword"><path></span>/dev/sda<span class="perl_Keyword"></path></span>
+ <span class="perl_Keyword"><weight></span>1000<span class="perl_Keyword"></weight></span>
+ <span class="perl_Keyword"></device></span>
+ <span class="perl_Keyword"><device></span>
+ <span class="perl_Keyword"><path></span>/dev/sdb<span class="perl_Keyword"></path></span>
+ <span class="perl_Keyword"><weight></span>500<span class="perl_Keyword"></weight></span>
+ <span class="perl_Keyword"></device></span>
+ <span class="perl_Keyword"></blkiotune></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.12. Block I/O tuning</h6></div><br class="figure-break" /><div class="para">
+ Although all are optional, the components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-blk-io-elem"><h6>Table J.8. Block I/O tuning elements</h6><div class="table-contents"><table summary="Block I/O tuning elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><blkiotune></code>
+ </td><td class="">
+ This optional element provides the ability to tune Blkio cgroup tunable parameters for the domain. If this is omitted, it defaults to the OS provided defaults.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><weight></code>
+ </td><td class="">
+ This optional weight element is the overall I/O weight of the guest. The value should be within the range 100 - 1000.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><device></code>
+ </td><td class="">
+ The domain may have multiple <code class="sgmltag-starttag"><device></code> elements that further tune the weights for each host block device in use by the domain. Note that multiple guest disks can share a single host block device. In addition, as they are backed by files within the same host file system, this tuning parameter is at the global domain level, rather than being associated with each guest disk device (contrast this to the <code class="sgmltag-starttag"><iotune></code> element which can be applied to a single <code class="sgmltag-starttag"><disk></code>). Each device element has two mandatory sub-elements, <code class="sgmltag-starttag"><path></code> describing the absolute path of the device, and <code class="sgmltag-starttag"><weight></code> giving the relative weight of that device, which has an acceptable range of 100 - 1000.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sect-libvirt-dom-xml-res-part"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.10. Resource partitioning</h2></div></div></div><div class="para">
+ Hypervisors may allow for virtual machines to be placed into resource partitions, potentially with nesting of said partitions. The <code class="sgmltag-starttag"><resource></code> element groups together configuration related to resource partitioning. It currently supports a child element partition whose content defines the path of the resource partition in which to place the domain. If no partition is listed, then the domain will be placed in a default partition. It is the responsibility of the app/admin to ensure that the partition exists prior to starting the guest. Only the (hypervisor specific) default partition can be assumed to exist by default.
+ </div><div class="figure" id="fig-res-part"><div class="figure-contents"><pre class="programlisting">
+
+
+ ...
+ <span class="perl_Keyword"><resource></span>
+ <span class="perl_Keyword"><partition></span>/virtualmachines/production<span class="perl_Keyword"></partition></span>
+ <span class="perl_Keyword"></resource></span>
+ ...
+
+</pre></div><h6>Figure J.13. Resource partitioning</h6></div><br class="figure-break" /><div class="para">
+ Resource partitions are currently supported by the QEMU and LXC drivers, which map partition paths to cgroups directories in all mounted controllers.
+ </div></div><div class="section" id="sect-libvirt-dom-xml-cpu-model-top"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.11. CPU model and topology</h2></div></div></div><div class="para">
+ This section covers the requirements for CPU model. Its features and topology is specified using the following elements from the domain XML:
+ </div><div class="figure" id="fig-xml-cpu-model-top"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><cpu</span><span class="perl_Others"> match=</span><span class="perl_String">'exact'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><model</span><span class="perl_Others"> fallback=</span><span class="perl_String">'allow'</span><span class="perl_Keyword">></span>core2duo<span class="perl_Keyword"></model></span>
+ <span class="perl_Keyword"><vendor></span>Intel<span class="perl_Keyword"></vendor></span>
+ <span class="perl_Keyword"><topology</span><span class="perl_Others"> sockets=</span><span class="perl_String">'1'</span><span class="perl_Others"> cores=</span><span class="perl_String">'2'</span><span class="perl_Others"> threads=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><feature</span><span class="perl_Others"> policy=</span><span class="perl_String">'disable'</span><span class="perl_Others"> name=</span><span class="perl_String">'lahf_lm'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></cpu></span>
+ ...
+
+</pre></div><h6>Figure J.14. CPU model and topology example 1</h6></div><br class="figure-break" /><div class="figure" id="fig-xml-cpu-model-top2"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><cpu</span><span class="perl_Others"> mode=</span><span class="perl_String">'host-model'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><model</span><span class="perl_Others"> fallback=</span><span class="perl_String">'forbid'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><topology</span><span class="perl_Others"> sockets=</span><span class="perl_String">'1'</span><span class="perl_Others"> cores=</span><span class="perl_String">'2'</span><span class="perl_Others"> threads=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+<span class="perl_Keyword"></cpu></span>
+ ...
+</pre></div><h6>Figure J.15. CPU model and topology example 2</h6></div><br class="figure-break" /><div class="figure" id="fig-xml-cpu-model-top3"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><cpu</span><span class="perl_Others"> mode=</span><span class="perl_String">'host-passthrough'</span><span class="perl_Keyword">/></span>
+
+</pre></div><h6>Figure J.16. CPU model and topology example 3</h6></div><br class="figure-break" /><div class="para">
+ In cases where no restrictions are to be put on either the CPU model nor its features, a simpler cpu element such as the following may be used.
+ </div><div class="figure" id="fig-xml-cpu-model-top4"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><cpu></span>
+ <span class="perl_Keyword"><topology</span><span class="perl_Others"> sockets=</span><span class="perl_String">'1'</span><span class="perl_Others"> cores=</span><span class="perl_String">'2'</span><span class="perl_Others"> threads=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></cpu></span>
+ ...
+
+</pre></div><h6>Figure J.17. CPU model and topology example 4</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-cpu-model-elem"><h6>Table J.9. CPU model and topology elements</h6><div class="table-contents"><table summary="CPU model and topology elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><cpu></code>
+ </td><td class="">
+ This is the main container for describing guest CPU requirements.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><match></code>
+ </td><td class="">
+ Specifies how the virtual CPU is provided to the guest match for these requirements. The <code class="sgmltag-attribute">match</code> attribute can be omitted if topology is the only element within <code class="sgmltag-starttag"><cpu></code>. Possible values for the <code class="sgmltag-attribute">match</code> attribute are:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">minimum</code> - the specified CPU model and features describes the minimum requested CPU.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">exact</code> - the virtual CPU provided to the guest will exactly match the specification
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">strict</code> - the guest will not be created unless the host CPU exactly matches the specification.
+ </div></li></ul></div>
+ Note that the <code class="sgmltag-attribute">match</code> attribute can be omitted and will default to <code class="sgmltag-attvalue">exact</code>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><mode></code>
+ </td><td class="">
+ This optional attribute may be used to make it easier to configure a guest CPU to be as close to the host CPU as possible. Possible values for the mode attribute are:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">custom</code> - describes how the CPU is presented to the guest. This is the default setting when the <code class="sgmltag-attribute">mode</code> attribute is not specified. This mode makes it so that a persistent guest will see the same hardware no matter what host the guest is booted on.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">host-model</code> - this is essentially a shortcut to copying host CPU definition from the capabilities XML into the domain XML. As the CPU definition is copied just before starting a domain, the same XML can be used on different hosts while still providing the best guest CPU each host supports. Neither the <code class="sgmltag-attribute">match</code> attribute nor any feature elements can be used in this mode. For more information see <a href="http://libvirt.org/formatdomain.html">libvirt domain XML CPU models</a>
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">host-passthrough</code> With this mode, the CPU visible to the guest is exactly the same as the host CPU including elements that cause errors within libvirt. The obvious the downside of this mode is that the guest environment cannot be reproduced on different hardware and therefore this mode is recommended with great caution. Neither <code class="sgmltag-element">model</code> nor <code class="sgmltag-element">feature</code> elements are allowed in this mode.
+ </div></li><li class="listitem"><div class="para">
+ Note that in both <code class="sgmltag-element">host-model</code> and <code class="sgmltag-element">host-passthrough</code> mode, the real (approximate in host-passthrough mode) CPU definition which would be used on current host can be determined by specifying VIR_DOMAIN_XML_UPDATE_CPU flag when calling virDomainGetXMLDesc API. When running a guest that might be prone to operating system reactivation when presented with different hardware, and which will be migrated between hosts with different capabilities, you can use this output to rewrite XML to the custom mode for more robust migration.
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><model></code>
+ </td><td class="">
+ Specifies CPU model requested by the guest. The list of available CPU models and their definition can be found in <code class="filename">cpu_map.xml</code> file installed in libvirt's data directory. If a hypervisor is not able to use the exact CPU model, libvirt automatically falls back to a closest model supported by the hypervisor while maintaining the list of CPU features. An optional <code class="sgmltag-attribute">fallback</code> attribute can be used to forbid this behavior, in which case an attempt to start a domain requesting an unsupported CPU model will fail. Supported values for fallback attribute are: <code class="sgmltag-attvalue">allow</code> (this is the default), and <code class="sgmltag-attvalue">forbid</code>. The optional <code class="sgmltag-attribute">vendor_id</code> attribute can be used to set the vendor id seen by the guest. It must be exactly 12 characters long. If not set, the vendor id of the host is used. Typical possible values are <code
class="sgmltag-attvalue">AuthenticAMD</code> and <code class="sgmltag-attvalue">GenuineIntel</code>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><vendor></code>
+ </td><td class="">
+ Specifies CPU vendor requested by the guest. If this element is missing, the guest runs on a CPU matching given features regardless of its vendor. The list of supported vendors can be found in <code class="filename">cpu_map.xml</code>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><topology></code>
+ </td><td class="">
+ Specifies requested topology of virtual CPU provided to the guest. Three non-zero values have to be given for sockets, cores, and threads: total number of CPU sockets, number of cores per socket, and number of threads per core, respectively.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><feature></code>
+ </td><td class="">
+ Can contain zero or more elements used to fine-tune features provided by the selected CPU model. The list of known feature names can be found in the same file as CPU models. The meaning of each feature element depends on its policy attribute, which has to be set to one of the following values:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">force</code> - forces the virtual to be supported regardless of whether it is actually supported by host CPU.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">require</code> - dictates that guest creation will fail unless the feature is supported by host CPU. This is the default setting
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">optional</code> - this feature is supported by virtual CPU but and only if it is supported by host CPU.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">disable</code> - this is not supported by virtual CPU.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">forbid</code> - guest creation will fail if the feature is supported by host CPU.
+ </div></li></ul></div>
+
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="section" id="sub-sect-libvirt-dom-xml-res-part-guest-numa"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.11.1. Guest NUMA topology</h3></div></div></div><div class="para">
+ Guest NUMA topology can be specifed using the numa element and the following from the domain XML:
+ </div><div class="figure" id="fig-xml-cpu-model-top-numa"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><cpu></span>
+ ...
+ <span class="perl_Keyword"><numa></span>
+ <span class="perl_Keyword"><cell</span><span class="perl_Others"> cpus=</span><span class="perl_String">'0-3'</span><span class="perl_Others"> memory=</span><span class="perl_String">'512000'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><cell</span><span class="perl_Others"> cpus=</span><span class="perl_String">'4-7'</span><span class="perl_Others"> memory=</span><span class="perl_String">'512000'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></numa></span>
+ ...
+ <span class="perl_Keyword"></cpu></span>
+ ...
+</pre></div><h6>Figure J.18. Guest NUMA topology</h6></div><br class="figure-break" /><div class="para">
+ Each cell element specifies a NUMA cell or a NUMA node. <code class="sgmltag-attribute">cpus</code> specifies the CPU or range of CPUs that are part of the node. <code class="sgmltag-attribute">memory</code> specifies the node memory in kibibytes (i.e. blocks of 1024 bytes). Each cell or node is assigned <code class="sgmltag-attribute">cellid</code> or <code class="sgmltag-attribute">nodeid</code> in increasing order starting from 0.
+ </div></div></div><div class="section" id="sect-libvirt-dom-xml-event-config"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.12. Events configuration</h2></div></div></div><div class="para">
+ Using the following sections of domain XML it is possible to override the default actions taken on various events.
+ </div><div class="figure" id="fig-xml-cpu-model-events-config"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><on_poweroff></span>destroy<span class="perl_Keyword"></on_poweroff></span>
+ <span class="perl_Keyword"><on_reboot></span>restart<span class="perl_Keyword"></on_reboot></span>
+ <span class="perl_Keyword"><on_crash></span>restart<span class="perl_Keyword"></on_crash></span>
+ <span class="perl_Keyword"><on_lockfailure></span>poweroff<span class="perl_Keyword"></on_lockfailure></span>
+ ..
+
+</pre></div><h6>Figure J.19. Events Configuration</h6></div><br class="figure-break" /><div class="para">
+ The following collections of elements allow the actions to be specified when a guest OS triggers a lifecycle operation. A common use case is to force a reboot to be treated as a poweroff when doing the initial OS installation. This allows the VM to be re-configured for the first post-install bootup.
+ </div><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-event-config-elem"><h6>Table J.10. Event configurtation elements</h6><div class="table-contents"><table summary="Event configurtation elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ State
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><on_poweroff></code>
+ </td><td class="">
+ Specifies the action that is to be executed when the guest requests a poweroff. Four possible arguements are possible:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">destroy</code> - this action terminates the domain completely and releases all resources
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">restart</code> - this action terminates the domain completely and restarts it with the same configuration
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">preserve</code> - this action terminates the domain completely but and its resources are preserved to allow for future analysis.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">rename-restart</code> - this action terminates the domain completely and then restarts it with a new name
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><on_reboot></code>
+ </td><td class="">
+ Specifies the action that is to be executed when the guest requests a reboot.Four possible arguements are possible:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">destroy</code> - this action terminates the domain completely and releases all resources
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">restart</code> - this action terminates the domain completely and restarts it with the same configuration
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">preserve</code> - this action terminates the domain completely but and its resources are preserved to allow for future analysis.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">rename-restart</code> - this action terminates the domain completely and then restarts it with a new name
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><on_crash></code>
+ </td><td class="">
+ Specifies the action that is to be executed when the guest crashes. In addition, it supports these additional actions:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">coredump-destroy</code> - the crashed domain's core is dumped, domain is terminated completely, and all resources are released.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">coredump-restart</code> - the crashed domain's core is dumped, and the domain is restarted with the same configuration settings
+ </div></li></ul></div>
+ Four possible arguements are possible:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">destroy</code> - this action terminates the domain completely and releases all resources
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">restart</code> - this action terminates the domain completely and restarts it with the same configuration
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">preserve</code> - this action terminates the domain completely but and its resources are preserved to allow for future analysis.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">rename-restart</code> - this action terminates the domain completely and then restarts it with a new name
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><on_lockfailure></code>
+ </td><td class="">
+ Specifies what action should be taken when a lock manager loses resource locks. The following actions are recognized by libvirt, although not all of them need to be supported by individual lock managers. When no action is specified, each lock manager will take its default action. The following arguements are possible:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">poweroff</code> - forcefully powers off the domain
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">restart</code> - restarts the domain to reacquire its locks.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">pause</code> - pauses the domain so that it can be manually resumed when lock issues are solved.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">ignore</code> - keeps the domain running as if nothing happened.
+ </div></li></ul></div>
+
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sect-libvirt-dom-xml-pwr-man"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.13. Power Management</h2></div></div></div><div class="para">
+ It is possible to forcibly enable or disable BIOS advertisements to the guest OS using conventional management tools which effects the following section of the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-pwr-man"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><pm></span>
+ <span class="perl_Keyword"><suspend-to-disk</span><span class="perl_Others"> enabled=</span><span class="perl_String">'no'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><suspend-to-mem</span><span class="perl_Others"> enabled=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></pm></span>
+ ...
+
+</pre></div><h6>Figure J.20. Power Management</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-starttag"><pm></code> element can be enabled using the arguement <code class="sgmltag-attvalue">yes</code> or disabled using the arguement <code class="sgmltag-attvalue">no</code>. BIOS support can be implemented for S3 using the arguement <code class="sgmltag-attribute">suspend-to-disk</code> and S4 using the arguement <code class="sgmltag-attribute">suspend-to-mem</code> ACPI sleep states. If nothing is specified, the hypervisor will be left with its default value.
+ </div></div><div class="section" id="idm101742368"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm101742368">J.14. Hypervisor features</h2></div></div></div><div class="para">
+ Hypervisors may allow certain CPU / machine features to be enabled (<code class="sgmltag-attvalue">state='on')</code> or disabled (<code class="sgmltag-attvalue">state='off'</code>).
+ </div><div class="figure" id="fig-libvirt-dom-xml-hypr-feat"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><features></span>
+ <span class="perl_Keyword"><pae/></span>
+ <span class="perl_Keyword"><acpi/></span>
+ <span class="perl_Keyword"><apic/></span>
+ <span class="perl_Keyword"><hap/></span>
+ <span class="perl_Keyword"><privnet/></span>
+ <span class="perl_Keyword"><hyperv></span>
+ <span class="perl_Keyword"><relaxed</span><span class="perl_Others"> state=</span><span class="perl_String">'on'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></hyperv></span>
+ <span class="perl_Keyword"></features></span>
+ ...
+
+</pre></div><h6>Figure J.21. Hypervisor features</h6></div><br class="figure-break" /><div class="para">
+ All features are listed within the <code class="sgmltag-starttag"><features></code> element, if a <code class="sgmltag-starttag"><state></code> is not specified it is disabled. The available features can be found by calling the <code class="filename">capabilities</code> XML, but a common set for fully virtualized domains are:
+ </div><div class="table" id="table-libvirt-dom-xml-hyp-feat-elem"><h6>Table J.11. Hypervisor features elements</h6><div class="table-contents"><table summary="Hypervisor features elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ State
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><pae></code>
+ </td><td class="">
+ Physical address extension mode allows 32-bit guests to address more than 4 GB of memory.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><acpi></code>
+ </td><td class="">
+ Useful for power management, for example, with KVM guests it is required for graceful shutdown to work.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><apic></code>
+ </td><td class="">
+ Allows the use of programmable IRQ management. For this element, there is an optional attribute <code class="sgmltag-attribute">eoi</code> with values <code class="sgmltag-attvalue">on</code> and <code class="sgmltag-attvalue">off</code> which sets the availability of EOI (End of Interrupt) for the guest.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><hap></code>
+ </td><td class="">
+ Enables the use of Hardware Assisted Paging if it is available in the hardware.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">hyperv</code>
+ </td><td class="">
+ Enables various features to improve the behavior of guests running Microsoft Windows. Using the optional attribute <code class="sgmltag-attribute">relaxed</code> with values <code class="sgmltag-attvalue">on</code> or <code class="sgmltag-attvalue">off</code> enables or disables the relax constraints on timers
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sect-libvirt-dom-xml-time-keep"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.15. Time keeping</h2></div></div></div><div class="para">
+ The guest clock is typically initialized from the host clock. Most operating systems expect the hardware clock to be kept in UTC, which is the default setting. Note that for Windows guests the guest must be set in <code class="sgmltag-attvalue">localtime</code>.
+ </div><div class="figure" id="fig-libvirt-dom-xml-time-keep"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><clock</span><span class="perl_Others"> offset=</span><span class="perl_String">'localtime'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><timer</span><span class="perl_Others"> name=</span><span class="perl_String">'rtc'</span><span class="perl_Others"> tickpolicy=</span><span class="perl_String">'catchup'</span><span class="perl_Others"> track=</span><span class="perl_String">'guest'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><catchup</span><span class="perl_Others"> threshold=</span><span class="perl_String">'123'</span><span class="perl_Others"> slew=</span><span class="perl_String">'120'</span><span class="perl_Others"> limit=</span><span class="perl_String">'10000'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></timer></span>
+ <span class="perl_Keyword"><timer</span><span class="perl_Others"> name=</span><span class="perl_String">'pit'</span><span class="perl_Others"> tickpolicy=</span><span class="perl_String">'delay'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></clock></span>
+ ...
+
+</pre></div><h6>Figure J.22. Time keeping</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-time-keep-elem"><h6>Table J.12. Time keeping elements</h6><div class="table-contents"><table summary="Time keeping elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ State
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><clock></code>
+ </td><td class="">
+ The <code class="sgmltag-attribute">offset</code> attribute takes four possible values, allowing for fine grained control over how the guest clock is synchronized to the host. Note that hypervisors are not required to support all policies across all time sources <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">utc</code> - Synchronizes the clock to UTC when booted. <code class="sgmltag-attvalue">utc</code> mode can be converted to <code class="sgmltag-attvalue">variable</code> mode, which can be controlled by using the adjustment attribute. If the value is <code class="sgmltag-attvalue">reset</code>, the conversion is not done. A numeric value forces the conversion to <code class="sgmltag-attvalue">variable</code> mode using the value as the initial adjustment. The default adjustment is hypervisor specific.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">localtime</code> - Synchronizes the guest clock with the host's configured timezone when booted. The adjustment attribute behaves the same as in 'utc' mode.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">timezone</code> - Synchronizes the guest clock to the requested timezone using the timezone attribute.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">variable</code> - Gives the guest clock an arbitrary offset applied relative to UTC or localtime, depending on the basis attribute. The delta relative to UTC (or localtime) is specified in seconds, using the <code class="sgmltag-attribute">adjustment</code> attribute. The guest is free to adjust the RTC over time and expect that it will be honored at next reboot. This is in contrast to <code class="sgmltag-attvalue">utc</code> and <code class="sgmltag-attvalue">localtime</code> mode (with the optional attribute <code class="sgmltag-attvalue">adjustment='reset'</code>), where the RTC adjustments are lost at each reboot. In addition the <code class="sgmltag-attribute">basis</code> attribute can be either <code class="sgmltag-attvalue">utc</code> (default) or <code class="sgmltag-attvalue">localtime</code>. The <code class="sgmltag-element">clock</code> element may have zero or more <code class="sgmltag-starttag"><timer></code> ele
ments.
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><timer></code>
+ </td><td class="">
+ See Note
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><frequency></code>
+ </td><td class="">
+ This is an unsigned integer specifying the frequency at which <code class="sgmltag-attribute">name</code>=<code class="sgmltag-attvalue">"tsc"</code> runs.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><mode></code>
+ </td><td class="">
+ The <code class="sgmltag-attribute">mode</code> attribute controls how the <code class="sgmltag-attvalue">name="tsc"</code> <code class="sgmltag-starttag"><timer></code> is managed, and can be set to: <code class="sgmltag-attvalue">auto</code>, <code class="sgmltag-attvalue">native</code>, <code class="sgmltag-attvalue">emulate</code>, <code class="sgmltag-attvalue">paravirt</code>, or <code class="sgmltag-attvalue">smpsafe</code>. Other timers are always emulated.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><present></code>
+ </td><td class="">
+ Specifies whether a particular timer is available to the guest. Can be set to <code class="sgmltag-attvalue">yes</code> or <code class="sgmltag-attvalue">no</code>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="note"><div class="admonition_header"><h2>Additional information about the <code class="sgmltag-starttag"><timer></code> element</h2></div><div class="admonition"><div class="para">
+ Each <code class="sgmltag-starttag"><timer></code> element must contain a <code class="sgmltag-attribute">name</code> attribute, and may have the following attributes depending on the name specified.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><name></code> - selects which <code class="sgmltag-element">timer</code> is being modified. The following values are acceptable:<code class="sgmltag-attvalue">platform</code>, <code class="sgmltag-attvalue">hpet</code>, <code class="sgmltag-attvalue">kvmclock</code>, <code class="sgmltag-attvalue">pit</code>, <code class="sgmltag-attvalue">rtc</code>, or <code class="sgmltag-attvalue">tsc</code>.
+ </div></li><li class="listitem"><div class="para">
+ track - specifies the timer track. The following values are acceptable: <code class="sgmltag-attvalue">boot</code>, <code class="sgmltag-attvalue">guest</code>, or <code class="sgmltag-attvalue">wall</code>. <code class="sgmltag-element">track</code> is only valid for <code class="sgmltag-attvalue">name="rtc"</code> or <code class="sgmltag-attvalue">name="platform"</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-element">tickpolicy</code> - determines what happens whens the deadline for injecting a tick to the guest is missed. The following values can be assigned:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">delay</code> -will continue to deliver ticks at the normal rate. The guest time will be delayed due to the late tick
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">catchup</code> - delivers ticks at a higher rate in order to catch up with the missed tick. The guest time is not displayed once catchup is complete. In addition, there can be three optional attributes, each a positive integer, as follows: threshold, slew, and limit.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">merge</code> - merges the missed tick(s) into one tick and injects them. The guest time may be delayed, depending on how the merge is done.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">discard</code> - throws away the missed tick(s) and continues with future injection at its default interval setting. The guest time may be delayed, unless the there is an explicit statement for handling lost ticks
+ </div></li></ul></div></li></ul></div></div></div></div><div class="section" id="sect-libvirt-dom-xml-devices"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.16. Devices</h2></div></div></div><div class="para">
+ This set of XML elements are all used to describe devices provided to the guest domain. All of the devices below are indicated as children of the main devices element.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><emulator></span>/usr/lib/xen/bin/qemu-dm<span class="perl_Keyword"></emulator></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.23. Devices - child elements</h6></div><br class="figure-break" /><div class="para">
+ The contents of the <code class="sgmltag-starttag"><emulator></code> element specify the fully qualified path to the device model emulator binary. The capabilities XML specifies the recommended default emulator to use for each particular domain type or architecture combination.
+ </div><div class="section" id="sub-sect-libvirt-dom-xml-devices"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.1. Hard drives, floppy disks, CDROMs</h3></div></div></div><div class="para">
+ This section of the domain XML specifies any device that looks like a disk, be it a floppy, harddisk, cdrom, or paravirtualized driver is specified via the disk element.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-cds"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'file'</span><span class="perl_Others"> snapshot=</span><span class="perl_String">'external'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">"tap"</span><span class="perl_Others"> type=</span><span class="perl_String">"aio"</span><span class="perl_Others"> cache=</span><span class="perl_String">"default"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> file=</span><span class="perl_String">'/var/lib/xen/images/fv0'</span><span class="perl_Others"> startupPolicy=</span><span class="perl_String">'optional'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><seclabel</span><span class="perl_Others"> relabel=</span><span class="perl_String">'no'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></source></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hda'</span><span class="perl_Others"> bus=</span><span class="perl_String">'ide'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><iotune></span>
+ <span class="perl_Keyword"><total_bytes_sec></span>10000000<span class="perl_Keyword"></total_bytes_sec></span>
+ <span class="perl_Keyword"><read_iops_sec></span>400000<span class="perl_Keyword"></read_iops_sec></span>
+ <span class="perl_Keyword"><write_iops_sec></span>100000<span class="perl_Keyword"></write_iops_sec></span>
+ <span class="perl_Keyword"></iotune></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'2'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><encryption</span><span class="perl_Others"> type=</span><span class="perl_String">'...'</span><span class="perl_Keyword">></span>
+ ...
+ <span class="perl_Keyword"></encryption></span>
+ <span class="perl_Keyword"><shareable/></span>
+ <span class="perl_Keyword"><serial></span>
+ ...
+ <span class="perl_Keyword"></serial></span>
+ <span class="perl_Keyword"></disk></span>
+ ...
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">"qemu"</span><span class="perl_Others"> type=</span><span class="perl_String">"raw"</span><span class="perl_Others"> io=</span><span class="perl_String">"threads"</span><span class="perl_Others"> ioeventfd=</span><span class="perl_String">"on"</span><span class="perl_Others"> event_idx=</span><span class="perl_String">"off"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> protocol=</span><span class="perl_String">"sheepdog"</span><span class="perl_Others"> name=</span><span class="perl_String">"image_name"</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><host</span><span class="perl_Others"> name=</span><span class="perl_String">"hostname"</span><span class="perl_Others"> port=</span><span class="perl_String">"7000"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></source></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">"hdb"</span><span class="perl_Others"> bus=</span><span class="perl_String">"ide"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><transient/></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'drive'</span><span class="perl_Others"> controller=</span><span class="perl_String">'0'</span><span class="perl_Others"> bus=</span><span class="perl_String">'1'</span><span class="perl_Others"> unit=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">"qemu"</span><span class="perl_Others"> type=</span><span class="perl_String">"raw"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> protocol=</span><span class="perl_String">"rbd"</span><span class="perl_Others"> name=</span><span class="perl_String">"image_name2"</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><host</span><span class="perl_Others"> name=</span><span class="perl_String">"hostname"</span><span class="perl_Others"> port=</span><span class="perl_String">"7000"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></source></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">"hdd"</span><span class="perl_Others"> bus=</span><span class="perl_String">"ide"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><auth</span><span class="perl_Others"> username=</span><span class="perl_String">'myuser'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><secret</span><span class="perl_Others"> type=</span><span class="perl_String">'ceph'</span><span class="perl_Others"> usage=</span><span class="perl_String">'mypassid'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></auth></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'block'</span><span class="perl_Others"> device=</span><span class="perl_String">'cdrom'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">'qemu'</span><span class="perl_Others"> type=</span><span class="perl_String">'raw'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hdc'</span><span class="perl_Others"> bus=</span><span class="perl_String">'ide'</span><span class="perl_Others"> tray=</span><span class="perl_String">'open'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><readonly/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'block'</span><span class="perl_Others"> device=</span><span class="perl_String">'lun'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">'qemu'</span><span class="perl_Others"> type=</span><span class="perl_String">'raw'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> dev=</span><span class="perl_String">'/dev/sda'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'sda'</span><span class="perl_Others"> bus=</span><span class="perl_String">'scsi'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'drive'</span><span class="perl_Others"> controller=</span><span class="perl_String">'0'</span><span class="perl_Others"> bus=</span><span class="perl_String">'0'</span><span class="perl_Others"> target=</span><span class="perl_String">'3'</span><span class="perl_Others"> unit=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'block'</span><span class="perl_Others"> device=</span><span class="perl_String">'disk'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">'qemu'</span><span class="perl_Others"> type=</span><span class="perl_String">'raw'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> dev=</span><span class="perl_String">'/dev/sda'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><geometry</span><span class="perl_Others"> cyls=</span><span class="perl_String">'16383'</span><span class="perl_Others"> heads=</span><span class="perl_String">'16'</span><span class="perl_Others"> secs=</span><span class="perl_String">'63'</span><span class="perl_Others"> trans=</span><span class="perl_String">'lba'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><blockio</span><span class="perl_Others"> logical_block_size=</span><span class="perl_String">'512'</span><span class="perl_Others"> physical_block_size=</span><span class="perl_String">'4096'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hda'</span><span class="perl_Others"> bus=</span><span class="perl_String">'ide'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'volume'</span><span class="perl_Others"> device=</span><span class="perl_String">'disk'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">'qemu'</span><span class="perl_Others"> type=</span><span class="perl_String">'raw'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> pool=</span><span class="perl_String">'blk-pool0'</span><span class="perl_Others"> volume=</span><span class="perl_String">'blk-pool0-vol0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hda'</span><span class="perl_Others"> bus=</span><span class="perl_String">'ide'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.24. Devices - Hard drives, floppy disks, CDROMs</h6></div><br class="figure-break" /><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-disk"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.1.1. Disk element</h4></div></div></div><div class="para">
+ The <code class="sgmltag-starttag"><disk></code> element is the main container for describing disks. The attribute <code class="sgmltag-attribute">type</code> can be used with the <code class="sgmltag-starttag"><disk></code> element. The following types are allowed:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">file</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">block</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">dir</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">network</code>
+ </div></li></ul></div><div class="para">
+ For more information, see <a href="http://libvirt.org/formatdomain.html">Disk Elements</a>
+ </div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-source"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.1.2. Source element</h4></div></div></div><div class="para">
+ If the <code class="sgmltag-starttag"><disk type='file''></code>, then the <code class="sgmltag-attribute">file</code> attribute specifies the fully-qualified path to the file holding the disk. If the <code class="sgmltag-starttag"><disk type='block'></code>, then the <code class="sgmltag-attribute">dev</code> attribute specifies the path to the host device to serve as the disk. With both <code class="sgmltag-attvalue">file</code> and <code class="sgmltag-attvalue">block</code>, one or more optional sub-elements <code class="sgmltag-element">seclabel</code>, described below, can be used to override the domain security labeling policy for just that source file. If the disk type is <code class="sgmltag-attvalue">dir</code>, then the <code class="sgmltag-attribute">dir</code> attribute specifies the fully-qualified path to the directory to use as the disk. If the disk type is <code class="sgmltag-attvalue">network</code>, then the protocol attribute specifies t
he protocol to access to the requested image; possible values are <code class="sgmltag-attvalue">nbd</code>, <code class="sgmltag-attvalue">rbd</code>, <code class="sgmltag-attvalue">sheepdog</code> or <code class="sgmltag-attvalue">gluster</code>.
+ </div><div class="para">
+ If the protocol attribute is <code class="sgmltag-attvalue">rbd</code>, <code class="sgmltag-attvalue">sheepdog</code> or <code class="sgmltag-attvalue">gluster</code>, an additional attribute <code class="sgmltag-attvalue">name</code> is mandatory to specify which volume and or image will be used. When the disk type is <code class="sgmltag-attvalue">network</code>, the <code class="sgmltag-attvalue">source</code> may have zero or more <code class="sgmltag-element">host</code> sub-elements used to specify the hosts to connect, including: <code class="sgmltag-attvalue">type='dir'</code> and <code class="sgmltag-attvalue">type='network'</code>. For a <code class="sgmltag-attvalue">file</code> disk type which represents a cdrom or floppy (the device attribute), it is possible to define policy what to do with the disk if the source file is not accessible. This is done by manipulating the <code class="sgmltag-attribute">startupPolicy</code> attribute, with the following valu
es:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">mandatory</code> causes a failure if missing for any reason. This is the default setting.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">requisite</code> causes a failure if missing on boot up, drops if missing on migrate/restore/revert
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">optional</code> drops if missing at any start attempt
+ </div></li></ul></div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-mirror"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.1.3. Mirror element</h4></div></div></div><div class="para">
+ This element is present if the hypervisor has started a <code class="command">BlockCopy</code> operation, where the <code class="sgmltag-starttag"><mirror></code> location in the attribute file will eventually have the same contents as the source, and with the file format in attribute format (which might differ from the format of the source). If an attribute ready is present, then it is known the disk is ready to pivot; otherwise, the disk is probably still copying. For now, this element only valid in output; it is ignored on input.
+ </div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-target"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.1.4. Target element</h4></div></div></div><div class="para">
+ The <code class="sgmltag-starttag"><target></code> element controls the bus / device under which the disk is exposed to the guest OS. The dev attribute indicates the logical device name. The actual device name specified is not guaranteed to map to the device name in the guest OS. The optional bus attribute specifies the type of disk device to emulate; possible values are driver specific, with typical values being <code class="sgmltag-attvalue">ide</code>, <code class="sgmltag-attvalue">scsi</code>, <code class="sgmltag-attvalue">virtio</code>, <code class="sgmltag-attvalue">xen</code>, <code class="sgmltag-attvalue">usb</code> or <code class="sgmltag-attvalue">sata</code>. If omitted, the bus type is inferred from the style of the device name. eg, a device named <code class="filename">'sda'</code> will typically be exported using a SCSI bus. The optional attribute <code class="sgmltag-attribute">tray</code> indicates the tray status of the removable disks (i.e. CD
ROM or Floppy disk), the value can be either <code class="sgmltag-attvalue">open</code> or <code class="sgmltag-attvalue">closed</code>. The default setting is <code class="sgmltag-attvalue">closed</code>. For more information, see <a href="http://libvirt.org/formatdomain.html">target Elements</a>
+ </div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-iotune"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.1.5. iotune</h4></div></div></div><div class="para">
+ The optional <code class="sgmltag-starttag"><iotune></code> element provides the ability to provide additional per-device I/O tuning, with values that can vary for each device (contrast this to the <code class="sgmltag-attvalue">blkiotune</code> element, which applies globally to the domain). This element has the following optional sub-elements. Note that any sub-element not specified or at all or specified with a value of <code class="sgmltag-attvalue">0</code> implies no limit.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><total_bytes_sec></code> - the total throughput limit in bytes per second. This element cannot be used with <code class="sgmltag-starttag"><read_bytes_sec></code> or <code class="sgmltag-starttag"><write_bytes_sec></code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><read_bytes_sec></code> - the read throughput limit in bytes per second.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><write_bytes_sec></code> - the write throughput limit in bytes per second.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><total_iops_sec></code> - the total I/O operations per second. This element cannot be used with <code class="sgmltag-starttag"><read_iops_sec></code> or <code class="sgmltag-starttag"><write_iops_sec></code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><read_iops_sec></code> - the read I/O operations per second.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><write_iops_sec></code> - the write I/O operations per second.
+ </div></li></ul></div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-driver"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.1.6. driver</h4></div></div></div><div class="para">
+ The optional <code class="sgmltag-starttag"><driver></code> element allows specifying further details related to the hypervisor driver that is used to provide the disk. The following options may be used:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If the hypervisor supports multiple backend drivers, then the <code class="sgmltag-attribute">name</code> attribute selects the primary backend driver name, while the optional type attribute provides the sub-type. For a list of possible types refer to <a href="http://libvirt.org/formatdomain.html">Driver Elements</a>
+ </div></li><li class="listitem"><div class="para">
+ The optional <code class="sgmltag-attribute">cache</code> attribute controls the cache mechanism, possible values are: <code class="sgmltag-attvalue">default</code>, <code class="sgmltag-attvalue">none</code>, <code class="sgmltag-attvalue">writethrough</code>, <code class="sgmltag-attvalue">writeback</code>, <code class="sgmltag-attvalue">directsync</code> (similar to <code class="sgmltag-element">writethrough</code>, but it bypasses the host page cache) and <code class="sgmltag-attvalue">unsafe</code> (host may cache all disk io, and sync requests from guest are ignored).
+ </div></li><li class="listitem"><div class="para">
+ The optional <code class="sgmltag-attribute">error_policy</code> attribute controls how the hypervisor behaves on a disk read or write error, possible values are <code class="sgmltag-attvalue">stop</code>, <code class="sgmltag-attvalue">report</code>, <code class="sgmltag-attvalue">ignore</code>, and <code class="sgmltag-attvalue">enospace</code>. The default setting of <code class="sgmltag-attribute">error_policy</code> is <code class="sgmltag-attvalue">report</code>. There is also an optional <code class="sgmltag-attribute">rerror_policy</code> that controls behavior for read errors only. If no <code class="sgmltag-attribute">rerror_policy</code> is given, <code class="sgmltag-attribute">error_policy</code> is used for both read and write errors. If <code class="sgmltag-attribute">rerror_policy</code> is given, it overrides the <code class="sgmltag-attribute">error_policy</code> for read errors. Also note that <code class="sgmltag-attvalue">enospace</code> is not a
valid policy for read errors, so if <code class="sgmltag-attribute">error_policy</code> is set to <code class="sgmltag-attvalue">enospace</code> and <code class="sgmltag-attribute">no rerror_policy</code> is given, the read error the default setting, <code class="sgmltag-attvalue">report</code> will be used.
+ </div></li><li class="listitem"><div class="para">
+ The optional <code class="sgmltag-attribute">io</code> attribute controls specific policies on I/O; <code class="sgmltag-attribute">qemu</code> guests support <code class="sgmltag-attvalue">threads</code> and <code class="sgmltag-attvalue">native</code>. The optional <code class="sgmltag-attribute">ioeventfd</code> attribute allows users to set domain I/O asynchronous handling for disk device. The default is left to the discretion of the hypervisor. Accepted values are <code class="sgmltag-attvalue">on</code> and <code class="sgmltag-attvalue">off</code>. Enabling this allows the guest virtual machine to be executed while a separate thread handles I/O. Typically guests experiencing high system CPU utilization during I/O will benefit from this. On the other hand, an overloaded host can increase guest I/O latency. Unless you are absolutely certian that the <code class="sgmltag-attribute">io</code> needs to be manipulated, it is highly recommended that you not change the
default setting and allow the hypervisor to dictate the setting.
+ </div></li><li class="listitem"><div class="para">
+ The optional <code class="sgmltag-attribute">event_idx</code> attribute controls some aspects of device event processing and can be set to either <code class="sgmltag-attvalue">on</code> or <code class="sgmltag-attvalue">off</code> - if it is on, it will reduce the number of interrupts and exits for the guest. The default is determined by the hypervisor and the default setting is <code class="sgmltag-attvalue">on</code>. In cases that there is a situation where this behavior is suboptimal, this attribute provides a way to force the feature <code class="sgmltag-attvalue">off</code>. Unless you are absolutely certian that the <code class="sgmltag-attribute">event_idx</code> needs to be manipulated, it is highly recommended that you not change the default setting and allow the hypervisor to dictate the setting.
+ </div></li><li class="listitem"><div class="para">
+ The optional <code class="sgmltag-attribute">copy_on_read</code> attribute controls whether to copy the read backing file into the image file. The accepted values can be either <code class="sgmltag-attvalue">on</code> or <code class="sgmltag-starttag"><off></code>. <code class="sgmltag-attribute">copy-on-read</code> avoids accessing the same backing file sectors repeatedly and is useful when the backing file is over a slow network. By default <code class="sgmltag-attribute">copy-on-read</code> is <code class="sgmltag-attvalue">off</code>.
+ </div></li></ul></div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-misc"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.1.7. Additional Device Elements</h4></div></div></div><div class="para">
+ The following attributes may be used within the <code class="sgmltag-element">device</code> element:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><boot></code> - Specifies that the disk is bootable.
+ </div><div class="itemizedlist"><h6>Additional boot values</h6><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><order></code> - Determines the order in which devices will be tried during boot sequence.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><per-device></code> boot elements cannot be used together with general boot elements in BIOS bootloader section
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><encryption></code> - Specifies how the volume is encrypted. See the Storage Encryption page for more information.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><readonly></code> - Indicates the device cannot be modified by the guest. This setting is the default for disks with <code class="sgmltag-attribute">attribute</code> <code class="sgmltag-attvalue">device='cdrom'</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">shareable</code> Indicates the device is expected to be shared between domains (as long as hypervisor and OS support this). If <code class="sgmltag-element">shareable</code> is used, <code class="sgmltag-attvalue">cache='no'</code> should be used for that device.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><transient></code>- Indicates that changes to the device contents should be reverted automatically when the guest exits. With some hypervisors, marking a disk <code class="sgmltag-attvalue">transient</code> prevents the domain from participating in migration or snapshots.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><serial></code>- Specifies the serial number of guest virtual machine's hard drive. For example, <code class="sgmltag-starttag"><serial></code>WD-WMAP9A966149<code class="sgmltag-endtag"></serial></code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><wwn></code> - Specifies the WWN (World Wide Name) of a virtual hard disk or CD-ROM drive. It must be composed of 16 hexadecimal digits.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><vendor></code> - Specifies the vendor of a virtual hard disk or CD-ROM device. It must not be longer than 8 printable characters.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><product></code> - Specifies the product of a virtual hard disk or CD-ROM device. It must not be longer than 16 printable characters
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><host></code> - Supports 4 attributes: <code class="sgmltag-element">viz</code>, <code class="sgmltag-element">name</code>, <code class="sgmltag-element">port</code>, <code class="sgmltag-element">transport</code> and <code class="sgmltag-element">socket</code>, which specify the hostname, the port number, transport type and path to socket, respectively. The meaning of this element and the number of the elements depend on the <code class="sgmltag-element">protocol</code> attribute as shown here:
+ </div><div class="itemizedlist"><h6>additional host attributes</h6><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">nbd</code> - Specifies a server running nbd-server and may only be used for only one host
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">rbd</code> - Monitors servers of RBD type and may be used for one or more hosts
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">sheepdog</code> - Specifies one of the sheepdog servers (default is localhost:7000) and can be used one or none of the hosts
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">gluster</code> - Specifies a server running a glusterd daemon and may be used for only only one host. The valid values for transport attribute are <code class="sgmltag-attvalue">tcp</code>, <code class="sgmltag-attvalue">rdma</code> or <code class="sgmltag-attvalue">unix</code>. If nothing is specified, <code class="sgmltag-attvalue">tcp</code> is assumed. If transport is <code class="sgmltag-attvalue">unix</code>, the <code class="sgmltag-attvalue">socket</code> attribute specifies path to unix socket.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><address></code> - Ties the disk to a given slot of a controller. The actual <code class="sgmltag-starttag"><controller></code> device can often be inferred by but it can also be explicitly specified. The <code class="sgmltag-attribute">type</code> attribute is mandatory, and is typically <code class="sgmltag-attvalue">pci</code> or <code class="sgmltag-attvalue">drive</code>. For a <code class="sgmltag-attribute">pci</code> controller, additional attributes for <code class="sgmltag-element">bus</code>, <code class="sgmltag-element">slot</code>, and <code class="sgmltag-element">function</code> must be present, as well as optional <code class="sgmltag-element">domain</code> and <code class="sgmltag-attvalue">multifunction</code>. <code class="sgmltag-attvalue">multifunction</code> defaults to <code class="sgmltag-attvalue">off</code>. For a <code class="sgmltag-attribute">drive</code> controller, additional attributes <code c
lass="sgmltag-attvalue">controller</code>, <code class="sgmltag-attvalue">bus</code>, <code class="sgmltag-attvalue">target</code>, and <code class="sgmltag-attvalue">unit</code> are available, each with a default setting of <code class="sgmltag-attvalue">0</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">auth</code> - Provides the authentication credentials needed to access the source. It includes a mandatory attribute username, which identifies the username to use during authentication, as well as a sub-element <code class="sgmltag-attvalue">secret</code> with mandatory attribute <code class="sgmltag-attribute">type</code>. More information can be found here at <a href="http://libvirt.org/formatdomain.html">Device Elements</a>
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">geometry</code> - Provides the ability to override geometry settings. This mostly useful for S390 DASD-disks or older DOS-disks.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">cyls</code> - Specifies the number of cylinders.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">heads</code> - Specifies the number of heads.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">secs</code> - Specifies the number of sectors per track.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">trans</code> - Specifies the BIOS-Translation-Modus and can have the following values:<code class="sgmltag-element">none</code>, <code class="sgmltag-element">lba</code> or <code class="sgmltag-element">auto</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">blockio</code> - Allows the block device to be overridden with any of the block device properties listed below:
+ </div><div class="itemizedlist"><h6>blockio options</h6><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">logical_block_size</code>- reports to the guest OS and describes the smallest units for disk I/O.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">physical_block_size</code> - reports to the guest OS and describes the disk's hardware sector size which can be relevant for the alignment of disk data.
+ </div></li></ul></div></li></ul></div></div></div><div class="section" id="sub-section-libvirt-dom-xml-devices-filesystems"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.2. Filesystems</h3></div></div></div><div class="para">
+ A filesystems directory on the host that can be accessed directly from the guest
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-filesystems"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><filesystem</span><span class="perl_Others"> type=</span><span class="perl_String">'template'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> name=</span><span class="perl_String">'my-vm-template'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dir=</span><span class="perl_String">'/'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></filesystem></span>
+ <span class="perl_Keyword"><filesystem</span><span class="perl_Others"> type=</span><span class="perl_String">'mount'</span><span class="perl_Others"> accessmode=</span><span class="perl_String">'passthrough'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> type=</span><span class="perl_String">'path'</span><span class="perl_Others"> wrpolicy=</span><span class="perl_String">'immediate'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> dir=</span><span class="perl_String">'/export/to/guest'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dir=</span><span class="perl_String">'/import/from/host'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><readonly/></span>
+ <span class="perl_Keyword"></filesystem></span>
+ ...
+ <span class="perl_Keyword"></devices></span>
+ ...
+
+</pre></div><h6>Figure J.25. Devices - filesystems</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-attribute">filesystem</code> attribute has the following possible values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='mount'</code> - Specifies the host directory to mount in the guest. This is the default type if one is not specified. This mode also has an optional sub-element <code class="sgmltag-element">driver</code>, with an attribute <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='path'</code> or <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='handle'</code>. The driver block has an optional attribute <code class="sgmltag-attribute">wrpolicy</code> that further controls interaction with the host page cache; omitting the attribute reverts to the default setting, while specifying a value immediate means that a host writeback is immediately triggered for all pages touched during a guest file write operation
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='template'</code> - Specifies the OpenVZ filesystem template and is only used by OpenVZ driver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='file'</code> - Specifies that a host file will be treated as an image and mounted in the guest. This filesystem format will be autodetected and is only used by LXC driver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='block'</code> - Specifies the host block device to mount in the guest. The filesystem format will be autodetected and is only used by LXC driver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='ram'</code> - Specifies that an in-memory filesystem, using memory from the host OS will be used. The source element has a single attribute <code class="sgmltag-attribute">usage</code> which gives the memory usage limit in kibibytes and is only used by LXC driver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='bind'</code> - Specifies a directory inside the guest which will be bound to another directory inside the guest. This element is only used by LXC driver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">accessmode</code> which specifies the security mode for accessing the source. Currently this only works with type='mount' for the QEMU/KVM driver. The possible values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">passthrough</code> - Specifies that the source is accessed with the User's permission settings that are set from inside the virtual guest machine. This is the default accessmode if one is not specified.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">mapped</code> - Specifies that the source is accessed with the permission settings of the hypervisor.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">squash</code> - Similar to <code class="sgmltag-attvalue">'passthrough'</code>, the exception is that failure of privileged operations like <code class="sgmltag-attvalue">chown</code> are ignored. This makes a passthrough-like mode usable for people who run the hypervisor as non-root.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><source></code> - Specifies that the resource on the host that is being accessed in the guest virtual machine. The <code class="sgmltag-attribute">name</code> attribute must be used with <code class="sgmltag-starttag"><type='template'></code>, and the <code class="sgmltag-attribute">dir</code> attribute must be used with <code class="sgmltag-starttag"><type='mount'></code>. The <code class="sgmltag-attribute">usage</code> attribute is used with <code class="sgmltag-starttag"><type='ram'></code> to set the memory limit in KB.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-element">target</code> - Dictates where the source drivers can be accessed in the guest virtual machine. For most drivers this is an automatic mount point, but for QEMU-KVM this is merely an arbitrary string tag that is exported to the guest as a hint for where to mount.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">readonly</code> - Enables exporting the filesytem as a readonly mount for guest virtual machine, by default <code class="sgmltag-element">read-write</code> access is given.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">space_hard_limit</code> - Specifies the maximum space available to this guest's filesystem
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">space_soft_limit</code> - Specifies the maximum space available to this guest's filesystem. The container is permitted to exceed its soft limits for a grace period of time. Afterwards the hard limit is enforced.
+ </div></li></ul></div></div><div class="section" id="sub-section-libvirt-dom-xml-devices-device-addresses"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.3. Device addresses</h3></div></div></div><div class="para">
+ Many devices have an optional <code class="sgmltag-starttag"><address></code> sub-element to describe where the device placed on the virtual bus is presented to the guest. If an address (or any optional attribute within an address) is omitted on input, libvirt will generate an appropriate address; but an explicit address is required if more control over layout is required. See below for device examples including an address element.
+ </div><div class="para">
+ Every address has a mandatory attribute <em class="parameter"><code>type</code></em> that describes which bus the device is on. The choice of which address to use for a given device is constrained in part by the device and the architecture of the guest. For example, a disk device uses <code class="sgmltag-attribute">type='disk'</code>, while a console device would use <code class="sgmltag-attribute">type='pci'</code> on i686 or x86_64 guests, or <code class="sgmltag-attribute">type='spapr-vio'</code> on PowerPC64 pseries guests. Each address <code class="sgmltag-starttag"><type></code> has additional optional attributes that control where on the bus the device will be placed. The additional attributes are as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type='pci'</code> - PCI addresses have the following additional attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">domain</code> (a 2-byte hex integer, not currently used by qemu)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">bus</code> (a hex value between 0 and 0xff, inclusive)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">slot</code> (a hex value between 0x0 and 0x1f, inclusive)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">function</code> (a value between 0 and 7, inclusive)
+ </div></li><li class="listitem"><div class="para">
+ Also available is the <code class="sgmltag-attribute">multifunction</code> attribute, which controls turning on the multifunction bit for a particular slot/function in the PCI control register. This multifunction attribute defaults to <code class="sgmltag-attvalue">'off'</code>, but should be set to <code class="sgmltag-attvalue">'on'</code> for function 0 of a slot that will have multiple functions used.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type='drive</code> - drive addresses have the following additional attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">controller</code>- (a 2-digit controller number)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">bus</code> - (a 2-digit bus number)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">target</code> - (a 2-digit bus number)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">unit</code> - (a 2-digit unit number on the bus)
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type='virtio-serial'</code> - Each virtio-serial address has the following additional attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">controller</code> - (a 2-digit controller number)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">bus</code> - (a 2-digit bus number)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">slot</code> - (a 2-digit slot within the bus)
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type='ccid'</code> - A CCID address, used for smart-cards, has the following additional attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">bus</code> - (a 2-digit bus number)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">slot</code> attribute - (a 2-digit slot within the bus)
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type='usb'</code> - USB addresses have the following additional attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">bus</code> - (a hex value between 0 and 0xfff, inclusive)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">port</code> - (a dotted notation of up to four octets, such as 1.2 or 2.1.3.1)
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type='spapr-vio</code> - On PowerPC pseries guests, devices can be assigned to the SPAPR-VIO bus. It has a flat 64-bit address space; by convention, devices are generally assigned at a non-zero multiple of 0x1000, but other addresses are valid and permitted by libvirt. The additional attribute: reg (the hex value address of the starting register) can be assigned to this attribute.
+ </div></li></ul></div></div><div class="section" id="sub-section-libvirt-dom-xml-devices-controllers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.4. Controllers</h3></div></div></div><div class="para">
+ Depending on the guest architecture, some device busses can appear more than once, with a group of virtual devices tied to a virtual controller. Normally, libvirt can automatically infer such controllers without requiring explicit XML markup, but sometimes it is necessary to provide an explicit controller element.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-controllers"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><controller</span><span class="perl_Others"> type=</span><span class="perl_String">'ide'</span><span class="perl_Others"> index=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><controller</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio-serial'</span><span class="perl_Others"> index=</span><span class="perl_String">'0'</span><span class="perl_Others"> ports=</span><span class="perl_String">'16'</span><span class="perl_Others"> vectors=</span><span class="perl_String">'4'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><controller</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio-serial'</span><span class="perl_Others"> index=</span><span class="perl_String">'1'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'pci'</span><span class="perl_Others"> domain=</span><span class="perl_String">'0x0000'</span><span class="perl_Others"> bus=</span><span class="perl_String">'0x00'</span><span class="perl_Others"> slot=</span><span class="perl_String">'0x0a'</span><span class="perl_Others"> function=</span><span class="perl_String">'0x0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></controller></span>
+ ...
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.26. Devices - controllers</h6></div><br class="figure-break" /><div class="para">
+ Each controller has a mandatory attribute<code class="sgmltag-attribute">type</code>, which must be one of <code class="sgmltag-element">"ide", "fdc", "scsi", "sata", "usb", "ccid", or "virtio-serial"</code>, and a mandatory attribute <code class="sgmltag-attribute">index</code> which is the decimal integer describing in which order the bus controller is encountered (for use in controller attributes of <code class="sgmltag-element">address</code>elements). The "virtio-serial" controller has two additional optional attributes ports and vectors, which control how many devices can be connected through the controller. A "scsi" controller has an optional attribute <code class="sgmltag-element">model</code>, which is one of <code class="sgmltag-element">"auto", "buslogic", "ibmvscsi", "lsilogic", "lsias1068", "virtio-scsi" or "vmpvscsi"</code>. A "usb" controller has an optional attribute <code class="sgmltag-attribute">model</code>, which is one of <code class="sgmltag-elemen
t">"piix3-uhci", "piix4-uhci", "ehci", "ich9-ehci1", "ich9-uhci1", "ich9-uhci2", "ich9-uhci3", "vt82c686b-uhci", "pci-ohci" or "nec-xhci"</code>. Additionally, if the USB bus needs to be explicitly disabled for the guest, <code class="sgmltag-attribute">model='none'</code> may be used. The PowerPC64 "spapr-vio" addresses do not have an associated controller.
+ </div><div class="para">
+ For controllers that are themselves devices on a PCI or USB bus, an optional sub-element <code class="sgmltag-element">address</code> can specify the exact relationship of the controller to its master bus, with semantics given above.
+ </div><div class="para">
+ USB companion controllers have an optional sub-element <code class="sgmltag-element">master</code> to specify the exact relationship of the companion to its master controller. A companion controller is on the same bus as its master, so the companion index value should be equal.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-controllers2"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><controller</span><span class="perl_Others"> type=</span><span class="perl_String">'usb'</span><span class="perl_Others"> index=</span><span class="perl_String">'0'</span><span class="perl_Others"> model=</span><span class="perl_String">'ich9-ehci1'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'pci'</span><span class="perl_Others"> domain=</span><span class="perl_String">'0'</span><span class="perl_Others"> bus=</span><span class="perl_String">'0'</span><span class="perl_Others"> slot=</span><span class="perl_String">'4'</span><span class="perl_Others"> function=</span><span class="perl_String">'7'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></controller></span>
+ <span class="perl_Keyword"><controller</span><span class="perl_Others"> type=</span><span class="perl_String">'usb'</span><span class="perl_Others"> index=</span><span class="perl_String">'0'</span><span class="perl_Others"> model=</span><span class="perl_String">'ich9-uhci1'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><master</span><span class="perl_Others"> startport=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'pci'</span><span class="perl_Others"> domain=</span><span class="perl_String">'0'</span><span class="perl_Others"> bus=</span><span class="perl_String">'0'</span><span class="perl_Others"> slot=</span><span class="perl_String">'4'</span><span class="perl_Others"> function=</span><span class="perl_String">'0'</span><span class="perl_Others"> multifunction=</span><span class="perl_String">'on'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></controller></span>
+ ...
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.27. Devices - controllers - USB</h6></div><br class="figure-break" /></div><div class="section" id="sub-section-libvirt-dom-xml-devices-device-leases"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.5. Device leases</h3></div></div></div><div class="para">
+ When using a lock manager, you have the option to record device leases against a guest virtual machine. The lock manager will ensure that the guest virtual machine doesn't start unless the leases can be acquired. When configured using conventional management tools, the following section of the domain xml is effected:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-device-leases"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ ...
+ <span class="perl_Keyword"><lease></span>
+ <span class="perl_Keyword"><lockspace></span>somearea<span class="perl_Keyword"></lockspace></span>
+ <span class="perl_Keyword"><key></span>somekey<span class="perl_Keyword"></key></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> path=</span><span class="perl_String">'/some/lease/path'</span><span class="perl_Others"> offset=</span><span class="perl_String">'1024'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></lease></span>
+ ...
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.28. Devices - device leases</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-element">lease</code> section can have the following arguements:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-element">lockspace</code> - an arbitrary string that identifies lockspace within which the key is held. Lock managers may impose extra restrictions on the format, or length of the lockspace name.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-element">key</code> - an arbitrary string, that uniquely identies the lease to be acquired. Lock managers may impose extra restrictions on the format, or length of the key.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-element">target</code> - the fully qualified path of the file associated with the lockspace. The offset specifies where the lease is stored within the file. If the lock manager does not require a offset, set this value to <code class="sgmltag-element">0</code>.
+ </div></li></ul></div></div><div class="section" id="sub-section-libvirt-dom-xml-devices-host-device-assignment"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.6. Host device assignment</h3></div></div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-host-device-assignment-usb-pci-devices"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.6.1. USB / PCI devices</h4></div></div></div><div class="para">
+ The host's USB and PCI devices can be passed through to the guest using the <code class="sgmltag-element">hostdev</code> element, by modifying the host using a management tool the following section of the domain xml file is configured:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-host-device-assignment"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><hostdev</span><span class="perl_Others"> mode=</span><span class="perl_String">'subsystem'</span><span class="perl_Others"> type=</span><span class="perl_String">'usb'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> startupPolicy=</span><span class="perl_String">'optional'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><vendor</span><span class="perl_Others"> id=</span><span class="perl_String">'0x1234'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><product</span><span class="perl_Others"> id=</span><span class="perl_String">'0xbeef'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></source></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'2'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></hostdev></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.29. Devices - host device assignment</h6></div><br class="figure-break" /><div class="para">
+ Alternatively the following can also be done:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-host-device-assignment2"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><hostdev</span><span class="perl_Others"> mode=</span><span class="perl_String">'subsystem'</span><span class="perl_Others"> type=</span><span class="perl_String">'pci'</span><span class="perl_Others"> managed=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> bus=</span><span class="perl_String">'0x06'</span><span class="perl_Others"> slot=</span><span class="perl_String">'0x02'</span><span class="perl_Others"> function=</span><span class="perl_String">'0x0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></source></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><rom</span><span class="perl_Others"> bar=</span><span class="perl_String">'on'</span><span class="perl_Others"> file=</span><span class="perl_String">'/etc/fake/boot.bin'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></hostdev></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.30. Devices - host device assignment alternative</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-pci-managed-devices"><h6>Table J.13. Host device assignment elements</h6><div class="table-contents"><table summary="Host device assignment elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-element">hostdev</code>
+ </td><td class="">
+ This is the main container for describing host devices. For USB device passthrough <code class="sgmltag-element">mode</code> is always <code class="sgmltag-element">subsystem</code> and <code class="sgmltag-element">type</code> is <code class="sgmltag-element">usb</code> for a USB device and <code class="sgmltag-element">pci</code> for a PCI device. When <code class="sgmltag-element">managed</code> is <code class="sgmltag-element">yes</code> for a PCI device, it is detached from the host before being passed on to the guest, and reattached to the host after the guest exits. If <code class="sgmltag-element">managed</code> is omitted or <code class="sgmltag-element">no</code> for PCI and for USB devices, the user is responsible to use the arguement <code class="sgmltag-element">virNodeDeviceDettach</code> (or <code class="command">virsh nodedev-dettach</code>) before starting the guest or hot-plugging the device, and <code class="sgmltag-element">virNodeDeviceReAttach<
/code> (or <code class="command">virsh nodedev-reattach</code>) after hot-unplug or stopping the guest.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">source</code>
+ </td><td class="">
+ Describes the device as seen from the host. The USB device can either be addressed by vendor / product id using the <code class="sgmltag-element">vendor</code> and <code class="sgmltag-element">product</code> elements or by the device's address on the hosts using the <code class="sgmltag-element">address</code> element. PCI devices on the other hand can only be described by their address. Note that the source element of USB devices may contain a <code class="sgmltag-attribute">startupPolicy</code> attribute which can be used to define a rule for what to do if the specified host USB device is not found. The attribute accepts the following values:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-element">mandatory</code> - fails if missing for any reason (the default)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-element">requisite</code> - fails if missing on boot up, drops if missing on migrate/restore/revert
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-element">optional</code> - drops if missing at any start attempt
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">vendor, product</code>
+ </td><td class="">
+ These elements each have an <code class="sgmltag-attribute">id</code> attribute that specifies the USB vendor and product id. The IDs can be given in decimal, hexadecimal (starting with 0x) or octal (starting with 0) form.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">boot</code>
+ </td><td class="">
+ Specifies that the device is bootable. The attribute's order determines the order in which devices will be tried during boot sequence. The per-device boot elements cannot be used together with general boot elements in BIOS bootloader section.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">rom</code>
+ </td><td class="">
+ Used to change how a PCI device's ROM is presented to the guest. The optional <code class="sgmltag-attribute">bar</code> attribute can be set to <code class="sgmltag-element">on</code> or <code class="sgmltag-element">off</code>, and determines whether or not the device's ROM will be visible in the guest's memory map. (In PCI documentation, the <code class="sgmltag-element">rombar</code> setting controls the presence of the Base Address Register for the ROM). If no rom bar is specified, the default setting will be used. The optional <code class="sgmltag-attribute">file</code> attribute is used to point to a binary file to be presented to the guest as the device's ROM BIOS. This can be useful, for example, to provide a PXE boot ROM for a virtual function of an sr-iov capable ethernet device (which has no boot ROMs for the VFs).
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">address</code>
+ </td><td class="">
+ Also has a <code class="sgmltag-attribute">bus</code> and <code class="sgmltag-attribute">device</code> attribute to specify the USB bus and device number the device appears at on the host. The values of these attributes can be given in decimal, hexadecimal (starting with 0x) or octal (starting with 0) form. For PCI devices the element carries 3 attributes allowing to designate the device as can be found with <code class="command">lspci</code> or with <code class="command">virsh nodedev-list</code>
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-host-device-assignment-block-character-devices"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.6.2. Block / character devices </h4></div></div></div><div class="para">
+ The host's block / character devices can be passed through to the guest by using managment tools to modify the domain xml <code class="sgmltag-element">hostdev</code> element. Note that this is only possible with container based virtualization.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-host-device-assignment-blk"><div class="figure-contents"><pre class="programlisting">
+
+...
+<span class="perl_Keyword"><hostdev</span><span class="perl_Others"> mode=</span><span class="perl_String">'capabilities'</span><span class="perl_Others"> type=</span><span class="perl_String">'storage'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source></span>
+ <span class="perl_Keyword"><block></span>/dev/sdf1<span class="perl_Keyword"></block></span>
+ <span class="perl_Keyword"></source></span>
+<span class="perl_Keyword"></hostdev></span>
+...
+
+</pre></div><h6>Figure J.31. Devices - host device assignment block character devices</h6></div><br class="figure-break" /><div class="para">
+ An alternative approach is this:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-host-device-assignment-blk2"><div class="figure-contents"><pre class="programlisting">
+
+...
+<span class="perl_Keyword"><hostdev</span><span class="perl_Others"> mode=</span><span class="perl_String">'capabilities'</span><span class="perl_Others"> type=</span><span class="perl_String">'misc'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source></span>
+ <span class="perl_Keyword"><char></span>/dev/input/event3<span class="perl_Keyword"></char></span>
+ <span class="perl_Keyword"></source></span>
+<span class="perl_Keyword"></hostdev></span>
+...
+
+</pre></div><h6>Figure J.32. Devices - host device assignment block character devices alternative 1</h6></div><br class="figure-break" /><div class="para">
+ Another alternative approach is this:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-host-device-assignment-blk3"><div class="figure-contents"><pre class="programlisting">
+
+...
+<span class="perl_Keyword"><hostdev</span><span class="perl_Others"> mode=</span><span class="perl_String">'capabilities'</span><span class="perl_Others"> type=</span><span class="perl_String">'net'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source></span>
+ <span class="perl_Keyword"><interface></span>eth0<span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></source></span>
+<span class="perl_Keyword"></hostdev></span>
+...
+
+
+</pre></div><h6>Figure J.33. Devices - host device assignment block character devices alternative 2</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-host-device-assignement-block-character-devices"><h6>Table J.14. Block / character device elements</h6><div class="table-contents"><table summary="Block / character device elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-element">hostdev</code>
+ </td><td class="">
+ This is the main container for describing host devices. For block/character devices passthrough <code class="sgmltag-attribute">mode</code> is always <code class="sgmltag-element">capabilities</code> and <code class="sgmltag-attribute">type</code> is <code class="sgmltag-element">block</code> for a block device and <code class="sgmltag-element">char</code> for a character device.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">source</code>
+ </td><td class="">
+ This describes the device as seen from the host. For block devices, the path to the block device in the host OS is provided in the nested <code class="sgmltag-element">block</code> element, while for character devices the <code class="sgmltag-element">char</code> element is used
+ </td></tr></tbody></table></div></div><br class="table-break" /></div></div><div class="section" id="sub-section-libvirt-dom-xml-devices-redirected-devices"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.7. Redirected devices</h3></div></div></div><div class="para">
+ USB device redirection through a character device is supported by configuring it with managment tools that modify the following section of the domain xml:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-redirected-devices"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><redirdev</span><span class="perl_Others"> bus=</span><span class="perl_String">'usb'</span><span class="perl_Others"> type=</span><span class="perl_String">'tcp'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'connect'</span><span class="perl_Others"> host=</span><span class="perl_String">'localhost'</span><span class="perl_Others"> service=</span><span class="perl_String">'4000'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></redirdev></span>
+ <span class="perl_Keyword"><redirfilter></span>
+ <span class="perl_Keyword"><usbdev</span><span class="perl_Others"> class=</span><span class="perl_String">'0x08'</span><span class="perl_Others"> vendor=</span><span class="perl_String">'0x1234'</span><span class="perl_Others"> product=</span><span class="perl_String">'0xbeef'</span><span class="perl_Others"> version=</span><span class="perl_String">'2.00'</span><span class="perl_Others"> allow=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><usbdev</span><span class="perl_Others"> allow=</span><span class="perl_String">'no'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></redirfilter></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.34. Devices - redirected devices</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-host-device-assignement-redirected-devices"><h6>Table J.15. Redirected device elements</h6><div class="table-contents"><table summary="Redirected device elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-element">redirdev</code>
+ </td><td class="">
+ This is the main container for describing redirected devices. <code class="sgmltag-attribute">bus</code> must be <code class="sgmltag-element">usb</code> for a USB device. An additional attribute type is required, matching one of the supported serial device types, to describe the host side of the tunnel; <code class="sgmltag-attribute">type='tcp'</code> or <code class="sgmltag-attribute">type='spicevmc'</code> (which uses the usbredir channel of a SPICE graphics device) are typical. The redirdev element has an optional sub-element <code class="sgmltag-element">address</code> which can tie the device to a particular controller. Further sub-elements, such as <code class="sgmltag-element">source</code>, may be required according to the given <code class="sgmltag-attribute">type</code>, although a<code class="sgmltag-element">target</code> sub-element is not required (since the consumer of the character device is the hypervisor itself, rather than a device visible in the
guest).
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">boot</code>
+ </td><td class="">
+ Specifies that the device is bootable. The order attribute determines the order in which devices will be tried during boot sequence. The per-device boot elements cannot be used together with general boot elements in BIOS bootloader section.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">redirfilter</code>
+ </td><td class="">
+ This is used for creating the filter rule to filter out certain devices from redirection. It uses sub-element <code class="sgmltag-element">usbdev</code> to define each filter rule. The <code class="sgmltag-attribute">class</code> attribute is the USB Class code.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-section-libvirt-dom-xml-devices-smartcard"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.8. Smartcard devices</h3></div></div></div><div class="para">
+ A virtual smartcard device can be supplied to the guest via the <code class="sgmltag-element">smartcard</code> element. A USB smartcard reader device on the host cannot be used on a guest with simple device passthrough, as it cannot be made available to both the host and guest and can possibly lock the host computer when it is removed from the guest. Therefore, some hypervisors provide a specialized virtual device that can present a smartcard interface to the guest, with several modes for describing how the credentials are obtained from the host or even a from a channel created to a third-party smartcard provider. To set these parameters use a managment tool that will edit the following section of the domain XML:
+ </div><div class="para">
+ USB device redirection through a character device is supported by configuring it with managment tools that modify the following section of the domain xml:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-smartcard"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><smartcard</span><span class="perl_Others"> mode=</span><span class="perl_String">'host'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><smartcard</span><span class="perl_Others"> mode=</span><span class="perl_String">'host-certificates'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><certificate></span>cert1<span class="perl_Keyword"></certificate></span>
+ <span class="perl_Keyword"><certificate></span>cert2<span class="perl_Keyword"></certificate></span>
+ <span class="perl_Keyword"><certificate></span>cert3<span class="perl_Keyword"></certificate></span>
+ <span class="perl_Keyword"><database></span>/etc/pki/nssdb/<span class="perl_Keyword"></database></span>
+ <span class="perl_Keyword"></smartcard></span>
+ <span class="perl_Keyword"><smartcard</span><span class="perl_Others"> mode=</span><span class="perl_String">'passthrough'</span><span class="perl_Others"> type=</span><span class="perl_String">'tcp'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'bind'</span><span class="perl_Others"> host=</span><span class="perl_String">'127.0.0.1'</span><span class="perl_Others"> service=</span><span class="perl_String">'2001'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><protocol</span><span class="perl_Others"> type=</span><span class="perl_String">'raw'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'ccid'</span><span class="perl_Others"> controller=</span><span class="perl_String">'0'</span><span class="perl_Others"> slot=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></smartcard></span>
+ <span class="perl_Keyword"><smartcard</span><span class="perl_Others"> mode=</span><span class="perl_String">'passthrough'</span><span class="perl_Others"> type=</span><span class="perl_String">'spicevmc'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.35. Devices - smartcard devices</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-element">smartcard</code> element has a mandatory attribute <code class="sgmltag-attribute">mode</code>. The following modes are supported; in each mode, the guest sees a device on its USB bus that behaves like a physical USB CCID (Chip/Smart Card Interface Device) card.
+ </div><div class="para">
+ The mode attributes are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-host-device-assignement-smartcard-modes"><h6>Table J.16. Smartcard mode elements</h6><div class="table-contents"><table summary="Smartcard mode elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-attribute">mode='host'</code>
+ </td><td class="">
+ In this mode, the hypervisor relays all requests from the guest into direct access to the host's smartcard via NSS. No other attributes or sub-elements are required. See below about the use of an optional <code class="sgmltag-element">address</code> sub-element.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">mode='host-certificates'</code>
+ </td><td class="">
+ This mode allows you to provide three NSS certificate names residing in a database on the host, rather than requiring a smartcard to be plugged into the host. These certificates can be generated via the command <code class="sgmltag-element">certutil -d /etc/pki/nssdb -x -t CT,CT,CT -S -s CN=cert1 -n cert1,</code> and the resulting three certificate names must be supplied as the content of each of three <code class="sgmltag-element">certificate</code> sub-elements. An additional sub-element <code class="sgmltag-element">database</code> can specify the absolute path to an alternate directory (matching the <code class="sgmltag-element">-d</code> flag of the <code class="command">certutil</code> command when creating the certificates); if not present, it defaults to <code class="filename">/etc/pki/nssdb</code>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">mode='passthrough'</code>
+ </td><td class="">
+ Using this mode allows you to tunnel all requests through a secondary character device to a third-party provider (which may in turn be talking to a smartcard or using three certificate files, rather than having the hypervisor directly communicate with the host. In this mode of operation, an additional attribute <code class="sgmltag-attribute">type</code> is required, matching one of the supported serial device types, to describe the host side of the tunnel; <code class="sgmltag-attribute">type='tcp'</code> or <code class="sgmltag-attribute">type='spicevmc'</code> (which uses the smartcard channel of a SPICE graphics device) are typical. Further sub-elements, such as <code class="sgmltag-element">source</code>, may be required according to the given type, although a <code class="sgmltag-element">target</code> sub-element is not required (since the consumer of the character device is the hypervisor itself, rather than a device visible in the guest).
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Each mode supports an optional sub-element <code class="sgmltag-element">address</code>, which fine-tunes the correlation between the smartcard and a ccid bus controller (Refer to <a class="xref" href="#sub-section-libvirt-dom-xml-devices-device-addresses">Section J.16.3, “Device addresses”</a>).
+ </div></div><div class="section" id="sub-section-libvirt-dom-xml-devices-Network-interfaces"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.9. Network interfaces</h3></div></div></div><div class="para">
+ The network interface devices are modified using managment tools that will configure the following part of the Domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'bridge'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> bridge=</span><span class="perl_String">'xenbr0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">'00:16:3e:5d:c7:9e'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><script</span><span class="perl_Others"> path=</span><span class="perl_String">'vif-bridge'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><rom</span><span class="perl_Others"> bar=</span><span class="perl_String">'off'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.36. Devices - network interfaces</h6></div><br class="figure-break" /><div class="para">
+ There are several possibilities for specifying a network interface visible to the guest. Each subsection below provides more details about common setup options. Additionally, each <code class="sgmltag-starttag"><interface></code> element has an optional <code class="sgmltag-starttag"><address></code> sub-element that can tie the interface to a particular pci slot, with attribute <code class="sgmltag-attribute">type='pci'</code> (Refer to <a class="xref" href="#sub-section-libvirt-dom-xml-devices-device-addresses">Section J.16.3, “Device addresses”</a>).
+ </div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-virtual-network"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.1. Virtual networks</h4></div></div></div><div class="para">
+ This is the recommended configuration for general guest connectivity on hosts with dynamic / wireless networking configurations (or multi-host environments where the host hardware details are described separately in a <code class="sgmltag-starttag"><network></code> definition). In addition, it provides a connection whose details are described by the named network definition. Depending on the virtual network's <code class="sgmltag-attribute">forward mode</code> configuration, the network may be totally isolated (no <code class="sgmltag-starttag"><forward></code> element given), NAT'ing to an explicit network device or to the default route (<code class="sgmltag-attribute">forward mode='nat'</code>), routed with no NAT (<code class="sgmltag-attribute">forward mode='route'/</code>), or connected directly to one of the host's network interfaces (via macvtap) or bridge devices (<code class="sgmltag-attribute">forward mode='bridge|private|vepa|passthrough'/</code>)
+ </div><div class="para">
+ For networks with a forward mode of bridge, private, vepa, and passthrough, it is assumed that the host has any necessary DNS and DHCP services already setup outside the scope of libvirt. In the case of isolated, nat, and routed networks, DHCP and DNS are provided on the virtual network by libvirt, and the IP range can be determined by examining the virtual network config with <code class="command">virsh net-dumpxml [networkname]</code>. There is one virtual network called 'default' setup out of the box which does NAT'ing to the default route and has an IP range of 192.168.122.0/255.255.255.0. Each guest will have an associated tun device created with a name of vnetN, which can also be overridden with the <code class="sgmltag-starttag"><target></code> element (refer to <a class="xref" href="#sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element">Section J.16.9.10, “Overriding the target element”</a>).
+ </div><div class="para">
+ When the source of an interface is a network, a portgroup can be specified along with the name of the network; one network may have multiple portgroups defined, with each portgroup containing slightly different configuration information for different classes of network connections. Also, similar to <code class="sgmltag-starttag"><direct></code> network connections (described below), a connection of type <code class="sgmltag-attribute">network</code> may specify a <code class="sgmltag-starttag"><virtualport></code> element, with configuration data to be forwarded to a vepa (802.1Qbg) or 802.1Qbh compliant switch, or to an Open vSwitch virtual switch.
+ </div><div class="para">
+ Since the actual type of switch may vary depending on the configuration in the <code class="sgmltag-starttag"><network></code> on the host, it is acceptable to omit the virtualport type attribute, and specify attributes from multiple different virtualport types (and also to leave out certain attributes); at domain startup time, a complete <code class="sgmltag-starttag"><virtualport></code> element will be constructed by merging together the type and attributes defined in the network and the portgroup referenced by the interface. The newly-constructed virtualport is a combination of both. The attributes from lower virtualport can't make changes on the ones defined in higher virtualport. Interfaces take the highest priority, portgroup is lowest priority.
+ </div><div class="para">
+ For example, in order to work properly with both an 802.1Qbh switch and an Open vSwitch switch, you may choose to specify no type, but both an <code class="sgmltag-attribute">profileid</code> (in case the switch is 802.1Qbh) and an <code class="sgmltag-attribute">interfaceid</code> (in case the switch is Open vSwitch) (you may also omit the other attributes, such as <code class="sgmltag-attribute">managerid</code>, <code class="sgmltag-attribute">typeid</code>, or <code class="sgmltag-attribute">profileid</code>, to be filled in from the network's <code class="sgmltag-attribute">virtualport</code>). If you want to limit a guest to connecting only to certain types of switches, you can specify the virtualport type, but still omit some/all of the parameters - in this case if the host's network has a different type of virtualport, connection of the interface will fail. The virtual network parameters are defined using management tools that modify the following part of the do
main XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-virt-net"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Others"> portgroup=</span><span class="perl_String">'engineering'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet7'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">"00:11:22:33:44:55"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><virtualport></span>
+ <span class="perl_Keyword"><parameters</span><span class="perl_Others"> instanceid=</span><span class="perl_String">'09b11c53-8b5c-4eeb-8f00-d84eaa0aaa4f'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></virtualport></span>
+
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.37. Devices - network interfaces- virtual networks</h6></div><br class="figure-break" /></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-bridge-to-lan"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.2. Bridge to LAN</h4></div></div></div><div class="para">
+ Note that this is the recommended configuration setting for general guest connectivity on hosts with static wired networking configurations.
+ </div><div class="para">
+ Bridge to LAN provides a bridge from the guest virtual machine directly onto the LAN. This assumes there is a bridge device on the host which has one or more of the hosts physical NICs enslaved. The guest virtual machine will have an associated <code class="sgmltag-attribute">tun</code> device created with a name of <code class="sgmltag-starttag"><vnetN></code>, which can also be overridden with the <code class="sgmltag-starttag"><target></code> element (refer to <a class="xref" href="#sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element">Section J.16.9.10, “Overriding the target element”</a>). The <code class="sgmltag-starttag"><tun></code> device will be enslaved to the bridge. The IP range / network configuration is whatever is used on the LAN. This provides the guest virtual machine full incoming and outgoing net access just like a physical machine.
+ </div><div class="para">
+ On Linux systems, the bridge device is normally a standard Linux host bridge. On hosts that support Open vSwitch, it is also possible to connect to an open vSwitch bridge device by adding a <code class="sgmltag-attribute">virtualport type='openvswitch'/</code> to the interface definition. The Open vSwitch type virtualport accepts two parameters in its <code class="sgmltag-element">parameters</code> element - an <code class="sgmltag-element">interfaceid</code> which is a standard uuid used to uniquely identify this particular interface to Open vSwitch (if you do no specify one, a random <code class="sgmltag-attribute">interfaceid</code> will be generated for you when you first define the interface), and an optional <code class="sgmltag-element">profileid</code> which is sent to Open vSwitch as the interfaces <code class="sgmltag-starttag"><port-profile></code>. To set the bridge to LAN settings, use a managment tool that will configure the following part of the dom
ain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-br2lan"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'bridge'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> bridge=</span><span class="perl_String">'br0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'bridge'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> bridge=</span><span class="perl_String">'br1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet7'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">"00:11:22:33:44:55"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'bridge'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> bridge=</span><span class="perl_String">'ovsbr'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><virtualport</span><span class="perl_Others"> type=</span><span class="perl_String">'openvswitch'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><parameters</span><span class="perl_Others"> profileid=</span><span class="perl_String">'menial'</span><span class="perl_Others"> interfaceid=</span><span class="perl_String">'09b11c53-8b5c-4eeb-8f00-d84eaa0aaa4f'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></virtualport></span>
+ <span class="perl_Keyword"></interface></span>
+ ...
+ <span class="perl_Keyword"></devices></span>
+</pre></div><h6>Figure J.38. Devices - network interfaces- bridge to LAN</h6></div><br class="figure-break" /></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-userspace-slirp-stack"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.3. Userspace SLIRP stack</h4></div></div></div><div class="para">
+ Setting the userspace SLIRP stack parameters provides a virtual LAN with NAT to the outside world. The virtual network has DHCP and DNS services and will give the guest virtual machine an IP addresses starting from 10.0.2.15. The default router will be 10.0.2.2 and the DNS server will be 10.0.2.3. This networking is the only option for unprivileged users who need their guest virtual machines to have outgoing access.
+ </div><div class="para">
+ The userspace SLIP stack parameters are defined in the following part of the domain XML::
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-usr-spc-slip"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'user'</span><span class="perl_Keyword">/></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'user'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">"00:11:22:33:44:55"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.39. Devices - network interfaces- Userspace SLIRP stack</h6></div><br class="figure-break" /></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-generic-ethernet-connection"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.4. Generic Ethernet connection</h4></div></div></div><div class="para">
+ Provides a means for the administrator to execute an arbitrary script to connect the guest's network to the LAN. The guest will have a <code class="sgmltag-element">tun</code> device created with a name of <code class="sgmltag-element">vnetN</code>, which can also be overridden with the <code class="sgmltag-element">target</code> element. After creating the <code class="sgmltag-element">tun</code> device a shell script will be run which is expected to do whatever host network integration is required. By default this script is called <code class="filename">/etc/qemu-ifup</code> but can be overridden (refer to <a class="xref" href="#sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element">Section J.16.9.10, “Overriding the target element”</a>).
+ </div><div class="para">
+ The generic Ethernet connection parameters are defined in the following part of the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-gen-eth-con"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'ethernet'</span><span class="perl_Keyword">/></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'ethernet'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet7'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><script</span><span class="perl_Others"> path=</span><span class="perl_String">'/etc/qemu-ifup-mynet'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.40. Devices - network interfaces- generic Ethernet connection</h6></div><br class="figure-break" /></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-direct-attachment-to-physical-device"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.5. Direct attachment to physical interfaces</h4></div></div></div><div class="para">
+ Manipulating the direct attachment to physical interfaces provides direct attachment of the guest virtual machine's NIC to the given taht the physial interface of the host is specified.
+ </div><div class="para">
+ This setup requires the Linux macvtap driver to be available. One of the modes <code class="sgmltag-element">vepa</code> ( 'Virtual Ethernet Port Aggregator'), <code class="sgmltag-element">bridge</code> or <code class="sgmltag-element">private</code> can be chosen for the operation mode of the macvtap device, <code class="sgmltag-element">vepa</code> being the default mode.
+ </div><div class="para">
+ Manipulating direct attachment to physical interfaces involves setting the following parameters in the following part of the domain XML.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-dir-att-2phys"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'direct'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> dev=</span><span class="perl_String">'eth0'</span><span class="perl_Others"> mode=</span><span class="perl_String">'vepa'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.41. Devices - network interfaces- direct attachment to physical interfaces</h6></div><br class="figure-break" /><div class="para">
+ The individual modes cause the delivery of packets to behave as shown in <a class="xref" href="#table-libvirt-dom-xml-gen-direct-attachment-physical-interface">Table J.17, “Direct attachment to physical interface elements”</a>:
+ </div><div class="table" id="table-libvirt-dom-xml-gen-direct-attachment-physical-interface"><h6>Table J.17. Direct attachment to physical interface elements</h6><div class="table-contents"><table summary="Direct attachment to physical interface elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-attribute">vepa</code>
+ </td><td class="">
+ All of the guest virtual machines' packets are sent to the external bridge. Packets whose destination is a guest virtual machine on the same host as where the packet originates from are sent back to the host by the VEPA capable bridge (today's bridges are typically not VEPA capable).
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">bridge</code>
+ </td><td class="">
+ Packets whose destination is on the same host as where they originate from are directly delivered to the target macvtap device. Both origin and destination devices need to be in bridge mode for direct delivery. If either one of them is in <code class="sgmltag-attribute">vepa</code> mode, a VEPA capable bridge is required.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">private</code>
+ </td><td class="">
+ All packets are sent to the external bridge and will only be delivered to a target VM on the same host if they are sent through an external router or gateway and that device sends them back to the host. This procedure is followed if either the source or destination device is in private mode.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">passthrough</code>
+ </td><td class="">
+ This feature attaches a virtual function of a SRIOV capable NIC directly to a guest virtual machine without losing the migration capability. All packets are sent to the VF/IF of the configured network device. Depending on the capabilities of the device additional prerequisites or limitations may apply; for example, this requires kernel 2.6.38 or newer.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The network access of direct attached virtual machines can be managed by the hardware switch to which the physical interface of the host machine is connected to.
+ </div><div class="para">
+ The interface can have additional parameters as shown below, if the switch is conforming to the IEEE 802.1Qbg standard. The parameters of the virtualport element are documented in more detail in the IEEE 802.1Qbg standard. The values are network specific and should be provided by the network administrator. In 802.1Qbg terms, the Virtual Station Interface (VSI) represents the virtual interface of a virtual machine.
+ </div><div class="para">
+ Note that IEEE 802.1Qbg requires a non-zero value for the VLAN ID.
+ </div><div class="para">
+ Additional elements that can be manipulated are described in <a class="xref" href="#table-libvirt-dom-xml-gen-direct-attachment-physical-interface2">Table J.18, “Direct attachment to physical interface additional elements”</a>:
+ </div><div class="table" id="table-libvirt-dom-xml-gen-direct-attachment-physical-interface2"><h6>Table J.18. Direct attachment to physical interface additional elements</h6><div class="table-contents"><table summary="Direct attachment to physical interface additional elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-attribute">managerid</code>
+ </td><td class="">
+ The VSI Manager ID identifies the database containing the VSI type and instance definitions. This is an integer value and the value <code class="sgmltag-element">0</code> is reserved.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">typeid</code>
+ </td><td class="">
+ The VSI Type ID identifies a VSI type characterizing the network access. VSI types are typically managed by network administrator. This is an integer value.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">typeidversion</code>
+ </td><td class="">
+ The VSI Type Version allows multiple versions of a VSI Type. This is an integer value.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">instanceid</code>
+ </td><td class="">
+ The VSI Instance ID Identifier is generated when a VSI instance (i.e. a virtual interface of a virtual machine) is created. This is a globally unique identifier.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">profileid</code>
+ </td><td class="">
+ The profile ID contains the name of the port profile that is to be applied onto this interface. This name is resolved by the port profile database into the network parameters from the port profile, and those network parameters will be applied to this interface.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Additional parameters in the domain XML include:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-dir-att-2phys2"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'direct'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> dev=</span><span class="perl_String">'eth0.2'</span><span class="perl_Others"> mode=</span><span class="perl_String">'vepa'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><virtualport</span><span class="perl_Others"> type=</span><span class="perl_String">"802.1Qbg"</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><parameters</span><span class="perl_Others"> managerid=</span><span class="perl_String">"11"</span><span class="perl_Others"> typeid=</span><span class="perl_String">"1193047"</span><span class="perl_Others"> typeidversion=</span><span class="perl_String">"2"</span><span class="perl_Others"> instanceid=</span><span class="perl_String">"09b11c53-8b5c-4eeb-8f00-d84eaa0aaa4f"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></virtualport></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.42. Devices - network interfaces- direct attachment to physical interfaces additional parameters</h6></div><br class="figure-break" /><div class="para">
+ The interface can have additional parameters as shown below if the switch is conforming to the IEEE 802.1Qbh standard. The values are network specific and should be provided by the network administrator.
+ </div><div class="para">
+ Additional parameters in the domain XML include:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-dir-att-2phys3"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'direct'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> dev=</span><span class="perl_String">'eth0'</span><span class="perl_Others"> mode=</span><span class="perl_String">'private'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><virtualport</span><span class="perl_Others"> type=</span><span class="perl_String">'802.1Qbh'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><parameters</span><span class="perl_Others"> profileid=</span><span class="perl_String">'finance'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></virtualport></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.43. Devices - network interfaces- direct attachment to physical interfaces more additional parameters</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-attribute">profileid</code> attribute, contains the name of the port profile that is to be applied to this interface. This name is resolved by the port profile database into the network parameters from the port profile, and those network parameters will be applied to this interface.
+ </div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-pci-passthrough"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.6. PCI passthrough</h4></div></div></div><div class="para">
+ A PCI network device (specified by the <code class="sgmltag-element">source</code> element) is directly assigned to the guest using generic device passthrough, after first optionally setting the device's MAC address to the configured value, and associating the device with an 802.1Qbh capable switch using an optionally specified <code class="sgmltag-element">virtualport</code> element (see the examples of virtualport given above for type='direct' network devices). Note that - due to limitations in standard single-port PCI ethernet card driver design - only SR-IOV (Single Root I/O Virtualization) virtual function (VF) devices can be assigned in this manner; to assign a standard single-port PCI or PCIe ethernet card to a guest, use the traditional <code class="sgmltag-element">hostdev</code> device definition
+ </div><div class="para">
+ Note that this "intelligent passthrough" of network devices is very similar to the functionality of a standard <code class="sgmltag-element">hostdev</code> device, the difference being that this method allows specifying a MAC address and <code class="sgmltag-attribute">virtualport</code> for the passed-through device. If these capabilities are not required, if you have a standard single-port PCI, PCIe, or USB network card that doesn't support SR-IOV (and hence would anyway lose the configured MAC address during reset after being assigned to the guest domain), or if you are using a version of libvirt older than 0.9.11, you should use standard <code class="sgmltag-attribute">hostdev</code> to assign the device to the guest instead of <code class="sgmltag-attribute">interface type='hostdev'/</code>.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-pci-pass"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'hostdev'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">'vfio'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'pci'</span><span class="perl_Others"> domain=</span><span class="perl_String">'0x0000'</span><span class="perl_Others"> bus=</span><span class="perl_String">'0x00'</span><span class="perl_Others"> slot=</span><span class="perl_String">'0x07'</span><span class="perl_Others"> function=</span><span class="perl_String">'0x0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></source></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">'52:54:00:6d:90:02'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><virtualport</span><span class="perl_Others"> type=</span><span class="perl_String">'802.1Qbh'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><parameters</span><span class="perl_Others"> profileid=</span><span class="perl_String">'finance'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></virtualport></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.44. Devices - network interfaces- PCI passthrough</h6></div><br class="figure-break" /></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-multicast-tunnel"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.7. Multicast tunnel</h4></div></div></div><div class="para">
+ A multicast group may be used to represent a virtual network. Any guest virtual machine whose network devices are within the same multicast group will talk to each other, even if they reside across miltiple physical hosts. This mode may be used as an unprivileged user. There is no default DNS or DHCP support and no outgoing network access. To provide outgoing network access, one of the guest virtual machines should have a second NIC which is connected to one of the first 4 network types in order to provide appropriate routing. The multicast protocol is compatible with protocols used by <code class="command">user mode</code> linux guests as well. Note that the source address used must be from the multicast address block. A multicast tunnel is created by manipulating the <code class="command">interface type</code> using a management tool and setting/changing it to <code class="sgmltag-element">mcast</code>, and providing a mac and source address. The result is shown in ch
anges made to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-multi-cast-tun"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'mcast'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">'52:54:00:6d:90:01'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> address=</span><span class="perl_String">'230.0.0.1'</span><span class="perl_Others"> port=</span><span class="perl_String">'5558'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.45. Devices - network interfaces- multicast tunnel</h6></div><br class="figure-break" /></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-tcp-tunnel"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.8. TCP tunnel</h4></div></div></div><div class="para">
+ Creating a TCP client/server architecture is another way to provide a virtual network wher one guest virtual machine provides the server end of the network and all other guest virtual machines are configured as clients. All network traffic between the guest virtual machines is routed via the guest virtual machine that is configrured as the server. This model is also available for use to unprivileged users. There is no default DNS or DHCP support and no outgoing network access. To provide outgoing network access, one of the guest virtual machines should have a second NIC which is connected to one of the first 4 network types thereby providing the appropriate routing. A TCP tunnel is created by manipulating the <code class="sgmltag-element">interface type</code> using a management tool and setting/changing it to <code class="sgmltag-element">server</code> or <code class="sgmltag-element">client</code>, and providing a mac and source address. The result is shown in changes
made to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-tcp-tun"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'server'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">'52:54:00:22:c9:42'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> address=</span><span class="perl_String">'192.168.0.1'</span><span class="perl_Others"> port=</span><span class="perl_String">'5558'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'client'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">'52:54:00:8b:c9:51'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> address=</span><span class="perl_String">'192.168.0.1'</span><span class="perl_Others"> port=</span><span class="perl_String">'5558'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.46. Devices - network interfaces- TCP tunnel</h6></div><br class="figure-break" /></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-setting-nic-driver-specific-options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.9. Setting NIC driver-specific options</h4></div></div></div><div class="para">
+ Some NICs may have tunable driver-specific options. These options are set as attributes of the <code class="sgmltag-element">driver</code> sub-element of the interface definition. These options are set by using management toools to configuring the following sections of the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-nic-driver-options"><div class="figure-contents"><pre class="programlisting">
+
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><model</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">'vhost'</span><span class="perl_Others"> txmode=</span><span class="perl_String">'iothread'</span><span class="perl_Others"> ioeventfd=</span><span class="perl_String">'on'</span><span class="perl_Others"> event_idx=</span><span class="perl_String">'off'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.47. Devices - network interfaces- setting NIC driver-specific options</h6></div><br class="figure-break" /><div class="para">
+ Currently the following attributes are available for the "virtio" NIC driver:
+ </div><div class="table" id="table--libvirt-dom-xml-devices-Network-interfaces-setting-nic-driver-specific-options"><h6>Table J.19. virtio NIC driver elements</h6><div class="table-contents"><table summary="virtio NIC driver elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-attribute">name</code>
+ </td><td class="">
+ The optional <code class="sgmltag-attribute">name</code> attribute forces which type of backend driver to use. The value can be either <code class="sgmltag-attribute">qemu</code> (a user-space backend) or <code class="sgmltag-attribute">vhost</code> (a kernel backend, which requires the vhost module to be provided by the kernel); an attempt to require the vhost driver without kernel support will be rejected. The default setting is <code class="sgmltag-attribute">vhost</code> if the vhost driver present, but will silently fall back to <code class="sgmltag-attribute">qemu</code> if not.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">txmode</code>
+ </td><td class="">
+ Specifies how to handle transmission of packets when the transmit buffer is full. The value can be either <code class="sgmltag-attribute">iothread</code> or <code class="sgmltag-attribute">timer</code>. If set to <code class="sgmltag-attribute">iothread</code>, packet tx is all done in an iothread in the bottom half of the driver (this option translates into adding <code class="sgmltag-attvalue">"tx=bh"</code> to the <code class="sgmltag-attribute">qemu</code> commandline -device virtio-net-pci option). If set to <code class="sgmltag-attvalue">timer</code>, tx work is done in qemu, and if there is more tx data than can be sent at the present time, a timer is set before qemu moves on to do other things; when the timer fires, another attempt is made to send more data. In general you should leave this option alone, unless you are very certain you that changing it is an absolute necessity.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">ioeventfd</code>
+ </td><td class="">
+ Allows users to set domain I/O asynchronous handling for interface device. The default is left to the discretion of the hypervisor. Accepted values are <code class="sgmltag-attvalue">on</code> and <code class="sgmltag-attvalue">off </code>. Enabling this option allows qemu to execute a guest virtual machine while a separate thread handles I/O. Typically guest virtual machines experiencing high system CPU utilization during I/O will benefit from this. On the other hand, overloading the physical host may also increase guest I/O latency. Therefore, you should leave this option alone, unless you are very certain you that changing it is an absolute necessity.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">event_idx</code>
+ </td><td class="">
+ The event_idx attribute controls some aspects of device event processing. The value can be either <code class="sgmltag-attvalue">on</code> or <code class="sgmltag-attvalue">off</code>. Choosing <code class="sgmltag-attvalue">on</code>, reduces the number of interrupts and exits for the guest virtual machine. The default is <code class="sgmltag-attvalue">on</code>. In case there is a situation where this behavior is suboptimal, this attribute provides a way to force the feature off. You should leave this option alone, unless you are very certain you that changing it is an absolute necessity.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.10. Overriding the target element</h4></div></div></div><div class="para">
+ To override the target element, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-overriding-the-target-element"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.48. Devices - network interfaces- overriding the target element</h6></div><br class="figure-break" /><div class="para">
+ If no target is specified, certain hypervisors will automatically generate a name for the created tun device. This name can be manually specifed, however the name must not start with either 'vnet' or 'vif', which are prefixes reserved by libvirt and certain hypervisors. Manually specified targets using these prefixes will be ignored.
+ </div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-boot-order"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.11. Specifying boot order</h4></div></div></div><div class="para">
+ To specify the boot order, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig--libvirt-dom-xml-devices-Network-interfaces-boot-order"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.49. Specifying boot order</h6></div><br class="figure-break" /><div class="para">
+ For hypervisors which support it, you can set a specific NIC to be used for the network boot. The order of attributes determine the order in which devices will be tried during boot sequence. Note that the per-device boot elements cannot be used together with general boot elements in BIOS bootloader section.
+ </div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-interface-ROM-BIOS-configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.12. Interface ROM BIOS configuration</h4></div></div></div><div class="para">
+ To specify the ROM BIOS configuration settings, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-interface-ROM-BIOS-configuration"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><rom</span><span class="perl_Others"> bar=</span><span class="perl_String">'on'</span><span class="perl_Others"> file=</span><span class="perl_String">'/etc/fake/boot.bin'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.50. Interface ROM BIOS configuration</h6></div><br class="figure-break" /><div class="para">
+ For hypervisors which support it, you can change how a PCI Network device's ROM is presented to the guest virtual machine. The <code class="sgmltag-attribute">bar</code> attribute can be set to <code class="sgmltag-element">on</code> or <code class="sgmltag-element">off</code>, and determines whether or not the device's ROM will be visible in the guest's memory map. (In PCI documentation, the "rombar" setting controls the presence of the Base Address Register for the ROM). If no rom bar is specified, the qemu default will be used (older versions of qemu used a default of <code class="sgmltag-element">off</code>, while newer qemus have a default of <code class="sgmltag-element">on</code>). The optional <code class="sgmltag-element">file</code> attribute is used to point to a binary file to be presented to the guest as the device's ROM BIOS. This can be useful to provide an alternative boot ROM for a network device.
+ </div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-qos"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.13. Quality of service</h4></div></div></div><div class="para">
+ This section of the domain XML provides setting quality of service. Incoming and outgoing traffic can be shaped independently. The <code class="sgmltag-element">bandwidth</code> element can have at most one inbound and at most one outbound child elements. Leaving any of these children element out results in no QoS being applied on that traffic direction. Therefore, when you want to shape only domain's incoming traffic, use inbound only, and vice versa.
+ </div><div class="para">
+ Each of these elements has one mandatory attribute <code class="sgmltag-attribute">average</code> (or <code class="sgmltag-attribute">floor</code> as described below). <code class="sgmltag-attribute">average</code> specifies average bit rate on the interface being shaped. Then there are two optional attributes: <code class="sgmltag-attribute">peak</code>, which specifies maximum rate at which interface can send data, and <code class="sgmltag-attribute">burst</code>, which specifies the amount of bytes that can be burst at peak speed. Accepted values for attributes are integer numbers.
+ </div><div class="para">
+ The units for <code class="sgmltag-attribute">average</code> and <code class="sgmltag-attribute">peak</code> attributes are kilobytes per second, whereas <code class="sgmltag-attribute">burst</code> is only set in kilobytes. In addtion, inbound traffic can optionally have a <code class="sgmltag-attribute">floor</code> attribute. This guarantees minimal throughput for shaped interfaces. Using the <code class="sgmltag-attribute">floor</code> requires that all traffic goes through one point where QoS decisions can take place. As such it may only be used in cases where the <code class="sgmltag-element">interface type='network'/</code> with a <code class="sgmltag-element">forward</code> type of <code class="sgmltag-element">route</code>, <code class="sgmltag-element">nat</code>, or no forward at all). It should be noted that within a virtual network, all connected interfaces are required to have at least the inbound QoS set (<code class="sgmltag-element">average</code> at le
ast) but the floor attribute doesn't require specifying <code class="sgmltag-element">average</code>. However, <code class="sgmltag-element">peak</code> and <code class="sgmltag-element">burst</code> attributes still require <code class="sgmltag-element">average</code>. At the present time, ingress qdiscs may not have any classes, and therefore <code class="sgmltag-attribute">floor</code> may only be applied only on inbound and not outbound traffic.
+ </div><div class="para">
+ To specify the QoS configuration settings, use a managment tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-qos"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><bandwidth></span>
+ <span class="perl_Keyword"><inbound</span><span class="perl_Others"> average=</span><span class="perl_String">'1000'</span><span class="perl_Others"> peak=</span><span class="perl_String">'5000'</span><span class="perl_Others"> floor=</span><span class="perl_String">'200'</span><span class="perl_Others"> burst=</span><span class="perl_String">'1024'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><outbound</span><span class="perl_Others"> average=</span><span class="perl_String">'128'</span><span class="perl_Others"> peak=</span><span class="perl_String">'256'</span><span class="perl_Others"> burst=</span><span class="perl_String">'256'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></bandwidth></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><devices></span>
+ ...
+</pre></div><h6>Figure J.51. Quality of service</h6></div><br class="figure-break" /></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-setting-vlan-tag"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.14. Setting VLAN tag (on supported network types only)</h4></div></div></div><div class="para">
+ To specify the VLAN tag configuration settings, use a mangement tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-setting-vlan-tag"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'bridge'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><vlan></span>
+ <span class="perl_Keyword"><tag</span><span class="perl_Others"> id=</span><span class="perl_String">'42'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></vlan></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> bridge=</span><span class="perl_String">'ovsbr0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><virtualport</span><span class="perl_Others"> type=</span><span class="perl_String">'openvswitch'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><parameters</span><span class="perl_Others"> interfaceid=</span><span class="perl_String">'09b11c53-8b5c-4eeb-8f00-d84eaa0aaa4f'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></virtualport></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><devices></span>
+ ...
+
+</pre></div><h6>Figure J.52. Setting VLAN tag (on supported network types only)</h6></div><br class="figure-break" /><div class="para">
+ If (and only if) the network connection used by the guest supports vlan tagging transparent to the guest, an optional <code class="sgmltag-element">vlan</code> element can specify one or more vlan tags to apply to the guest's network traffic (openvswitch and <code class="sgmltag-element">type='hostdev'</code> SR-IOV interfaces do support transparent vlan tagging of guest traffic; everything else, including standard linux bridges and libvirt's own virtual networks, do not support it. 802.1Qbh (vn-link) and 802.1Qbg (VEPA) switches provide their own way (outside of libvirt) to tag guest traffic onto specific vlans.) To allow for specification of multiple tags (in the case of vlan trunking), a subelement, <code class="sgmltag-element">tag</code>, specifies which vlan tag to use (for example: <code class="sgmltag-attribute">tag id='42'/</code>. If an interface has more than one <code class="sgmltag-element">vlan</code> element defined, it is assumed that the user wants to d
o VLAN trunking using all the specified tags. In the case that vlan trunking with a single tag is desired, the optional attribute <code class="sgmltag-attribute">trunk='yes'</code> can be added to the toplevel vlan element.
+ </div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-modifying-virtual-link-state"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.15. Modifying virtual link state</h4></div></div></div><div class="para">
+ This element provides means of setting state of the virtual network link. Possible values for attribute <code class="sgmltag-attribute">state</code> are <code class="sgmltag-attvalue">up</code> and <code class="sgmltag-attvalue">down</code>. If <code class="sgmltag-attvalue">down</code> is specified as the value, the interface behaves as if it had the network cable disconnected. Default behavior if this element is unspecified is to have the link state <code class="sgmltag-attvalue">up</code>.
+ </div><div class="para">
+ To specify the virtual link state configuration settings, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-dom-xml-devices-modifying-virtual-link-state"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><link</span><span class="perl_Others"> state=</span><span class="perl_String">'down'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><devices></span>
+ ...
+</pre></div><h6>Figure J.53. Modifying virtual link state</h6></div><br class="figure-break" /></div></div><div class="section" id="sub-section-libvirt-dom-xml-devices-input-devices"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.10. Input devices</h3></div></div></div><div class="para">
+ Input devices allow interaction with the graphical framebuffer in the guest virtual machine. When enabling the framebuffer, an input device is automatically provided. It may be possible to add additional devices explicitly, for example, to provide a graphics tablet for absolute cursor movement.
+ </div><div class="para">
+ To specify the input devices configuration settings, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-input-devices"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><input</span><span class="perl_Others"> type=</span><span class="perl_String">'mouse'</span><span class="perl_Others"> bus=</span><span class="perl_String">'usb'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+
+</pre></div><h6>Figure J.54. Input devices</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-starttag"><input></code> element has one mandatory attribute: <code class="sgmltag-attribute">type</code> which can be set to: <code class="sgmltag-attvalue">mouse</code> or <code class="sgmltag-attvalue">tablet</code>. The latter provides absolute cursor movement, while the former uses relative movement. The optional <code class="sgmltag-attribute">bus</code> attribute can be used to refine the exact device type and can be set to: <code class="sgmltag-attvalue">xen</code> (paravirtualized), <code class="sgmltag-attvalue">ps2</code>, and <code class="sgmltag-attvalue">usb</code>.
+ </div><div class="para">
+ The input element has an optional sub-element <code class="sgmltag-starttag"><address></code>, which can tie the device to a particular PCI slot, as documented above.
+ </div></div><div class="section" id="sub-section-libvirt-dom-xml-devices-hub-devices"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.11. Hub devices</h3></div></div></div><div class="para">
+ A hub is a device that expands a single port into several so that there are more ports available to connect devices to a host system.
+ </div><div class="para">
+ To specify the hub devices configuration settings, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-xml-devices-hub-devices"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><hub</span><span class="perl_Others"> type=</span><span class="perl_String">'usb'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.55. Hub devices</h6></div><br class="figure-break" /><div class="para">
+ The hub element has one mandatory attribute, the type whose value can only be <code class="sgmltag-element">usb</code>. The hub element has an optional sub-element <code class="sgmltag-element">address</code> with <code class="sgmltag-attribute">type='usb'</code>which can tie the device to a particular controller.
+ </div></div><div class="section" id="sub-section-libvirt-dom-xml-devices-graphical-framebuffers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.12. Graphical framebuffers</h3></div></div></div><div class="para">
+ A graphics device allows for graphical interaction with the guest OS. A guest will typically have either a framebuffer or a text console configured to allow interaction with the admin.
+ </div><div class="para">
+ To specify the graphical framebuffer devices configuration settings, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig--xml-devices-graphical-framebuffers"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'sdl'</span><span class="perl_Others"> display=</span><span class="perl_String">':0.0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'vnc'</span><span class="perl_Others"> port=</span><span class="perl_String">'5904'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><listen</span><span class="perl_Others"> type=</span><span class="perl_String">'address'</span><span class="perl_Others"> address=</span><span class="perl_String">'1.2.3.4'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></graphics></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'rdp'</span><span class="perl_Others"> autoport=</span><span class="perl_String">'yes'</span><span class="perl_Others"> multiUser=</span><span class="perl_String">'yes'</span> <span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'desktop'</span><span class="perl_Others"> fullscreen=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'spice'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><listen</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Others"> network=</span><span class="perl_String">'rednet'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></graphics></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.56. Graphical framebuffers</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-element">graphics</code> element has a mandatory <code class="sgmltag-attribute">type</code> attribute which takes the value <code class="sgmltag-element">sdl</code>, <code class="sgmltag-element">vnc</code>, <code class="sgmltag-element">rdp</code> or <code class="sgmltag-element">desktop</code> as explained below:
+ </div><div class="table" id="table--libvirt-dom-xml-devices-Network-interfaces-setting-graphical-framebuffer-sgmltags"><h6>Table J.20. Graphical framebuffer elements</h6><div class="table-contents"><table summary="Graphical framebuffer elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-element">sdl</code>
+ </td><td class="">
+ This displays a window on the host desktop, it can take 3 optional arguments: a <code class="sgmltag-attribute">display</code> attribute for the display to use, an <code class="sgmltag-attribute">xauth</code> attribute for the authentication identifier, and an optional <code class="sgmltag-attribute">fullscreen</code> attribute accepting values <code class="sgmltag-element">yes</code> or <code class="sgmltag-element">no</code>
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">vnc</code>
+ </td><td class="">
+ Starts a VNC server. The <code class="sgmltag-attribute">port</code> attribute specifies the TCP port number (with <code class="sgmltag-element">-1</code> as legacy syntax indicating that it should be auto-allocated). The <code class="sgmltag-attribute">autoport</code> attribute is the new preferred syntax for indicating autoallocation of the TCP port to use. The <code class="sgmltag-attribute">listen</code> attribute is an IP address for the server to listen on. The <code class="sgmltag-attribute">passwd</code> attribute provides a VNC password in clear text. The <code class="sgmltag-attribute">keymap</code> attribute specifies the keymap to use. It is possible to set a limit on the validity of the password be giving an <code class="sgmltag-element">timestamp passwdValidTo='2010-04-09T15:51:00'</code> assumed to be in UTC. The <code class="sgmltag-attribute">connected</code> attribute allows control of connected client during password changes. VNC accepts <code clas
s="sgmltag-element">keep</code> value only and note that it may not be supported by all hypervisors. Rather than using listen/port, QEMU supports a socket attribute for listening on a unix domain socket path.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">spice</code>
+ </td><td class="">
+ Starts a SPICE server. The <code class="sgmltag-attribute">port</code> attribute specifies the TCP port number (with -1 as legacy syntax indicating that it should be auto-allocated), while <code class="sgmltag-element">tlsPort</code> gives an alternative secure port number. The <code class="sgmltag-attribute">autoport</code> attribute is the new preferred syntax for indicating autoallocation of both port numbers. The <code class="sgmltag-attribute">listen</code> attribute is an IP address for the server to listen on. The <code class="sgmltag-attribute">passwd</code> attribute provides a SPICE password in clear text. The <code class="sgmltag-attribute">keymap</code> attribute specifies the keymap to use. It is possible to set a limit on the validity of the password be giving an <code class="sgmltag-attribute">timestamp passwdValidTo='2010-04-09T15:51:00'</code> assumed to be in UTC. The <code class="sgmltag-attribute">connected</code> attribute allows control of conne
cted client during password changes. SPICE accepts keep to keep client connected, disconnect to disconnect client and fail to fail changing password. Note it is not be supported by all hypervisors. The <code class="sgmltag-attribute">defaultMode</code> attribute sets the default channel security policy, valid values are <code class="sgmltag-element">secure</code>, <code class="sgmltag-element">insecure</code> and the default <code class="sgmltag-element">any</code> (which is <code class="sgmltag-element">secure</code> if possible, but falls back to <code class="sgmltag-element">insecure</code> rather than erroring out if no secure path is available).
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ When SPICE has both a normal and TLS secured TCP port configured, it may be desirable to restrict what channels can be run on each port. This is achieved by adding one or more <code class="sgmltag-element">channel</code> elements inside the main <code class="sgmltag-element">graphics</code> element. Valid channel names include <code class="sgmltag-element">main</code>, <code class="sgmltag-element">display</code>, <code class="sgmltag-element">inputs</code>, <code class="sgmltag-element">cursor</code>, <code class="sgmltag-element">playback</code>, <code class="sgmltag-element">record</code>; <code class="sgmltag-element">smartcard</code>; and <code class="sgmltag-element">usbredir</code>.
+ </div><div class="para">
+ To specify the SPICE configuration settings, use a mangement tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-:devices-Network-interfaces-setting-graphical-framebuffer-sgmltags-spice-cfg"><div class="figure-contents"><pre class="programlisting">
+
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'spice'</span><span class="perl_Others"> port=</span><span class="perl_String">'-1'</span><span class="perl_Others"> tlsPort=</span><span class="perl_String">'-1'</span><span class="perl_Others"> autoport=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> name=</span><span class="perl_String">'main'</span><span class="perl_Others"> mode=</span><span class="perl_String">'secure'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> name=</span><span class="perl_String">'record'</span><span class="perl_Others"> mode=</span><span class="perl_String">'insecure'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><image</span><span class="perl_Others"> compression=</span><span class="perl_String">'auto_glz'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><streaming</span><span class="perl_Others"> mode=</span><span class="perl_String">'filter'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><clipboard</span><span class="perl_Others"> copypaste=</span><span class="perl_String">'no'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><mouse</span><span class="perl_Others"> mode=</span><span class="perl_String">'client'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></graphics></span>
+</pre></div><h6>Figure J.57. SPICE configuration</h6></div><br class="figure-break" /><div class="para">
+ SPICE supports variable compression settings for audio, images and streaming. These settings are accessible via the compression attribute in all following elements: <code class="sgmltag-element">image</code> to set image compression (accepts auto_glz, auto_lz, quic, glz, lz, off), <code class="sgmltag-element">jpeg</code> for JPEG compression for images over wan (accepts auto, never, always), <code class="sgmltag-element">zlib</code> for configuring wan image compression (accepts auto, never, always) and <code class="sgmltag-element">playback</code> for enabling audio stream compression (accepts on or off).
+ </div><div class="para">
+ Streaming mode is set by the <code class="sgmltag-element">streaming</code> element, settings its <code class="sgmltag-attribute">mode</code> attribute to one of <code class="sgmltag-element">filter</code>, <code class="sgmltag-element">all</code> or <code class="sgmltag-element">off</code>.
+ </div><div class="para">
+ In addition, Copy and paste functionality (via the SPICE agent) is set by the <code class="sgmltag-element">clipboard</code> element. It is enabled by default, and can be disabled by setting the <code class="sgmltag-attribute">copypaste</code> property to <code class="sgmltag-element">no</code>.
+ </div><div class="para">
+ Mouse mode is set by the <code class="sgmltag-element">mouse</code> element, setting its <code class="sgmltag-attribute">mode</code> attribute to one of <code class="sgmltag-element">server</code> or <code class="sgmltag-element">client</code>. If no mode is specified, the qemu default will be used (<code class="sgmltag-element">client</code> mode).
+ </div><div class="para">
+ Additional elements include:
+ </div><div class="table" id="table-libvirt-dom-xml-devices-Network-interfaces-setting-graphical-framebuffer-options2"><h6>Table J.21. Additional graphical framebuffer elements</h6><div class="table-contents"><table summary="Additional graphical framebuffer elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-element">rdp</code>
+ </td><td class="">
+ Starts a RDP server. The port attribute specifies the TCP port number (with -1 as legacy syntax indicating that it should be auto-allocated). The autoport attribute is the new preferred syntax for indicating autoallocation of the TCP port to use. The replaceUser attribute is a boolean deciding whether multiple simultaneous connections to the VM are permitted. The multiUser whether the existing connection must be dropped and a new connection must be established by the VRDP server, when a new client connects in single connection mode.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">desktop</code>
+ </td><td class="">
+ This value is reserved for VirtualBox domains for the moment. It displays a window on the host desktop, similarly to "sdl", but uses the VirtualBox viewer. Just like "sdl", it accepts the optional attributes display and fullscreen.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">listen</code>
+ </td><td class="">
+ Rather than putting the address information used to set up the listening socket for graphics types vnc and spice in the <code class="sgmltag-element">graphics</code>, the <code class="sgmltag-element">listen</code> attribute, a separate subelement of <code class="sgmltag-element">graphics</code>, called <code class="sgmltag-element">listen</code> can be specified (see the examples above). <code class="sgmltag-element">listen</code> accepts the following attributes:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code> - Set to either address or network. This tells whether this listen element is specifying the address to be used directly, or by naming a network (which will then be used to determine an appropriate address for listening).
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">address</code> - this attribute will contain either an IP address or hostname (which will be resolved to an IP address via a DNS query) to listen on. In the "live" XML of a running domain, this attribute will be set to the IP address used for listening, even if <code class="sgmltag-attribute">type='network'</code>.
+ </div></li><li class="listitem"><div class="para">
+ network - if <code class="sgmltag-attribute">type='network'</code>, the network attribute will contain the name of a network in libvirt's list of configured networks. The named network configuration will be examined to determine an appropriate listen address. For example, if the network has an IPv4 address in its configuration (e.g. if it has a forward type of route, nat, or no forward type (isolated)), the first IPv4 address listed in the network's configuration will be used. If the network is describing a host bridge, the first IPv4 address associated with that bridge device will be used, and if the network is describing one of the 'direct' (macvtap) modes, the first IPv4 address of the first forward dev will be used.
+ </div></li></ul></div>
+
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-section-libvirt-dom-xml-devices-video"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.13. Video devices</h3></div></div></div><div class="para">
+ A video device.
+ </div><div class="para">
+ To specify the video devices configuration settings, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-devices-video"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><video></span>
+ <span class="perl_Keyword"><model</span><span class="perl_Others"> type=</span><span class="perl_String">'vga'</span><span class="perl_Others"> vram=</span><span class="perl_String">'8192'</span><span class="perl_Others"> heads=</span><span class="perl_String">'1'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><acceleration</span><span class="perl_Others"> accel3d=</span><span class="perl_String">'yes'</span><span class="perl_Others"> accel2d=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></model></span>
+ <span class="perl_Keyword"></video></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.58. Video devices</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-element">graphics</code> element has a mandatory <code class="sgmltag-attribute">type</code> attribute which takes the value "sdl", "vnc", "rdp" or "desktop" as explained below:
+ </div><div class="table" id="table-libvirt-dom-xml-devices-Network-interfaces-setting-graphical-framebuffer-options"><h6>Table J.22. Graphical framebuffer elements</h6><div class="table-contents"><table summary="Graphical framebuffer elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-element">video</code>
+ </td><td class="">
+ The <code class="sgmltag-element">video</code> element is the container for describing video devices. For backwards compatibility, if no video is set but there is a <code class="sgmltag-element">graphics</code> element in domain xml, then libvirt will add a default <code class="sgmltag-element">video</code> according to the guest type. If "ram" or "vram" are not supplied a default value is used.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">model</code>
+ </td><td class="">
+ This has a mandatory <code class="sgmltag-attribute">type</code> attribute which takes the value <code class="sgmltag-element">vga</code>, <code class="sgmltag-element">cirrus</code>, <code class="sgmltag-element">vmvga</code>, <code class="sgmltag-element">xen</code>, <code class="sgmltag-element">vbox</code>, or <code class="sgmltag-element">qxl</code> depending on the hypervisor features available. You can also provide the amount of video memory in kibibytes (blocks of 1024 bytes) using vram and the number of figure with heads.
+ </td></tr><tr><td class="">
+ acceleration
+ </td><td class="">
+ If acceleration is supported it should be enabled using the <code class="sgmltag-attribute">accel3d</code> and <code class="sgmltag-attribute">accel2d</code> attributes in the <code class="sgmltag-element">acceleration</code> element.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">address</code>
+ </td><td class="">
+ The optional address sub-element can be used to tie the video device to a particular PCI slot.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="sub-section-libvirt-dom-xml-devices-consoles"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.14. Consoles, serial, parallel, and channel devices</h3></div></div></div><div class="para">
+ A character device provides a way to interact with the virtual machine. Paravirtualized consoles, serial ports, parallel ports and channels are all classed as character devices and so represented using the same syntax.
+ </div><div class="para">
+ To specify the consols, channel and other devices configuration settings, use a mangement tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-dom-xml-devices-consoles"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><parallel</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/2'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></parallel></span>
+ <span class="perl_Keyword"><serial</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/3'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></serial></span>
+ <span class="perl_Keyword"><console</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/4'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></console></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> type=</span><span class="perl_String">'unix'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'bind'</span><span class="perl_Others"> path=</span><span class="perl_String">'/tmp/guestfwd'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'guestfwd'</span><span class="perl_Others"> address=</span><span class="perl_String">'10.0.2.1'</span><span class="perl_Others"> port=</span><span class="perl_String">'4600'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></channel></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.59. Consoles, serial, parallel, and channel devices</h6></div><br class="figure-break" /><div class="para">
+ In each of these directives, the top-level element name (parallel, serial, console, channel) describes how the device is presented to the guest. The guest interface is configured by the target element. The interface presented to the host is given in the type attribute of the top-level element. The host interface is configured by the source element. The source element may contain an optional seclabel to override the way that labelling is done on the socket path. If this element is not present, the security label is inherited from the per-domain setting. Each character device element has an optional sub-element <code class="sgmltag-element">address</code> which can tie the device to a particular controller or PCI slot.
+ </div></div><div class="section" id="sub-section-libvirt-dom-xml-devices-guest-interface"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.15. Guest interfaces</h3></div></div></div><div class="para">
+ A character device presents itself to the guest as one of the following types.
+ </div><div class="para">
+ To set the parallel port, use a management tool to make the following change to the domain XML
+ </div><div class="figure" id="fig--devices-guest-interface"><div class="figure-contents"><pre class="programlisting">
+
+...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><parallel</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/2'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></parallel></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.60. Guest interface Parallel Port</h6></div><br class="figure-break" /><div class="para">
+ <code class="sgmltag-starttag"><target></code> can have a <code class="sgmltag-attribute">port</code> attribute, which specifies the port number. Ports are numbered starting from 0. There are usually 0, 1 or 2 parallel ports.
+ </div><div class="para">
+ To set the serial port use a management tool to make the following change to the domain XML:
+ </div><div class="figure" id="fig-devices-guest-interface-serial-port"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><serial</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/3'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></serial></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.61. Guest Interface Serial port</h6></div><br class="figure-break" /><div class="para">
+ <code class="sgmltag-starttag"><target></code> can have a <code class="sgmltag-attribute">port</code> attribute, which specifies the port number. Ports are numbered starting from 0. There are usually 0, 1 or 2 serial ports. There is also an optional <code class="sgmltag-attribute">type</code> attribute, which has two choices for its value, one is <code class="sgmltag-attvalue">isa-serial</code>, the other is <code class="sgmltag-attvalue">usb-serial</code>. If <code class="sgmltag-attribute">type</code> is missing, <code class="sgmltag-attvalue">isa-serial</code> will be used by default. For usb-serial an optional sub-element <code class="sgmltag-starttag"><address></code> with <code class="sgmltag-attribute">type='usb'</code> can tie the device to a particular controller, documented above.
+ </div><div class="para">
+ The <code class="sgmltag-starttag"><console></code> element is used to represent interactive consoles. Depending on the type of guest in use, the consoles might be paravirtualized devices, or they might be a clone of a serial device, according to the following rules:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If no <code class="sgmltag-attribute">targetType</code> attribute is set, then the default device <code class="sgmltag-attribute">type</code> is according to the hypervisor's rules. The default <code class="sgmltag-attribute">type</code> will be added when re-querying the XML fed into libvirt. For fully virtualized guests, the default device type will usually be a serial port.
+ </div></li><li class="listitem"><div class="para">
+ If the <code class="sgmltag-attribute">targetType</code> attribute is <code class="sgmltag-element">serial</code>, and if no <code class="sgmltag-starttag"><serial></code> element exists, the console element will be copied to the <code class="sgmltag-starttag"><serial></code> element. If a <code class="sgmltag-starttag"><serial></code> element does already exist, the console element will be ignored.
+ </div></li><li class="listitem"><div class="para">
+ If the <code class="sgmltag-attribute">targetType</code> attribute is not <code class="sgmltag-element">serial</code>, it will be treated normally.
+ </div></li><li class="listitem"><div class="para">
+ Only the first <code class="sgmltag-starttag"><console></code> element may use a <code class="sgmltag-attribute">targetType</code> of <code class="sgmltag-attvalue">serial</code>. Secondary consoles must all be paravirtualized.
+ </div></li><li class="listitem"><div class="para">
+ On s390, the console element may use a targetType of sclp or sclplm (line mode). SCLP is the native console type for s390. There's no controller associated to SCLP consoles.
+ </div></li></ul></div><div class="para">
+ In the example below, a virtio console device is exposed in the guest as /dev/hvc[0-7] (for more information, see http://fedoraproject.org/wiki/Features/VirtioSerial):
+ </div><div class="figure" id="fig-devices-guest-interface-serial-port-virtio-console-device"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><console</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/4'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></console></span>
+
+ <span class="perl_Comment"><!-- KVM virtio console --></span>
+ <span class="perl_Keyword"><console</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/5'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio'</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></console></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Comment"><!-- KVM s390 sclp console --></span>
+ <span class="perl_Keyword"><console</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'sclp'</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></console></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.62. Guest Interface - virtio console device</h6></div><br class="figure-break" /><div class="para">
+ If the console is presented as a serial port, the <code class="sgmltag-starttag"><target></code> element has the same attributes as for a serial port. There is usually only one console.
+ </div></div><div class="section" id="sub-section-libvirt-dom-xml-devices-channel"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.16. Channel</h3></div></div></div><div class="para">
+ This represents a private communication channel between the host and the guest and is manipulated by making changes to your guest virtual machine using a management tool that results in changes made to the following section of the domain xml
+ </div><div class="figure" id="fig-dom-xml-devices-channel"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> type=</span><span class="perl_String">'unix'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'bind'</span><span class="perl_Others"> path=</span><span class="perl_String">'/tmp/guestfwd'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'guestfwd'</span><span class="perl_Others"> address=</span><span class="perl_String">'10.0.2.1'</span><span class="perl_Others"> port=</span><span class="perl_String">'4600'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></channel></span>
+
+ <span class="perl_Comment"><!-- KVM virtio channel --></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio'</span><span class="perl_Others"> name=</span><span class="perl_String">'arbitrary.virtio.serial.port.name'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></channel></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> type=</span><span class="perl_String">'unix'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'bind'</span><span class="perl_Others"> path=</span><span class="perl_String">'/var/lib/libvirt/qemu/f16x86_64.agent'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio'</span><span class="perl_Others"> name=</span><span class="perl_String">'org.qemu.guest_agent.0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></channel></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> type=</span><span class="perl_String">'spicevmc'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio'</span><span class="perl_Others"> name=</span><span class="perl_String">'com.redhat.spice.0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></channel></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.63. Channel</h6></div><br class="figure-break" /><div class="para">
+ This can be implemented in a variety of ways. The specific type of <code class="sgmltag-starttag"><channel></code> is given in the <code class="sgmltag-attribute">type</code> attribute of the <code class="sgmltag-starttag"><target></code> element. Different channel types have different target attributes as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">guestfwd</code> - Dictates that TCP traffic sent by the guest to a given IP address and port is forwarded to the channel device on the host. The <code class="sgmltag-element">target</code> element must have address and port attributes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">virtio</code> - Paravirtualized virtio channel. <code class="sgmltag-starttag"><channel></code> is exposed in the guest under <code class="filename">/dev/vport*</code>, and if the optional element <code class="sgmltag-attribute">name</code>is specified, <code class="filename">/dev/virtio-ports/$name</code> (for more info, please see http://fedoraproject.org/wiki/Features/VirtioSerial). The optional element <code class="sgmltag-attribute">address</code> can tie the channel to a particular <code class="sgmltag-attribute">type='virtio-serial'</code> controller, documented above. With QEMU, if name is "org.qemu.guest_agent.0", then libvirt can interact with a guest agent installed in the guest, for actions such as guest shutdown or file system quiescing.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">spicevmc</code> - Paravirtualized SPICE channel. The domain must also have a SPICE server as a graphics device, at which point the host piggy-backs messages across the main channel. The <code class="sgmltag-element">target</code> element must be present, with attribute <code class="sgmltag-attribute">type='virtio';</code> an optional attribute <code class="sgmltag-attribute">name</code> controls how the guest will have access to the channel, and defaults to <code class="sgmltag-attribute">name='com.redhat.spice.0'</code>. The optional <code class="sgmltag-starttag"><address></code> element can tie the channel to a particular <code class="sgmltag-attribute">type='virtio-serial'</code> controller.
+ </div></li></ul></div></div><div class="section" id="sub-section-libvirt-dom-xml-devices-host-interface"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.17. Host interface</h3></div></div></div><div class="para">
+ A character device presents itself to the host as one of the following types:
+ </div><div class="table" id="table--libvirt-dom-xml-devices-host-interfaces-character-device-options"><h6>Table J.23. Character device elements</h6><div class="table-contents"><table summary="Character device elements" border="1"><colgroup><col width="33%" /><col width="33%" /><col width="33%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th><th class="">
+ XML snippet
+ </th></tr></thead><tbody><tr><td class="">
+ Domain logfile
+ </td><td class="">
+ Disables all input on the character device, and sends output into the virtual machine's logfile
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><console type='stdio'></code>
+ <code class="sgmltag-starttag"><target port='1'/></code>
+ <code class="sgmltag-endtag"></console></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ Device logfile
+ </td><td class="">
+ A file is opened and all data sent to the character device is written to the file.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="file"></code>
+ <code class="sgmltag-starttag"><source path="/var/log/vm/vm-serial.log"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ Virtual console
+ </td><td class="">
+ Connects the character device to the graphical framebuffer in a virtual console. This is typically accessed via a special hotkey sequence such as "ctrl+alt+3"
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type='vc'></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ Null device
+ </td><td class="">
+ Connects the character device to the void. No data is ever provided to the input. All data written is discarded.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type='null'></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ Pseudo TTY
+ </td><td class="">
+ A Pseudo TTY is allocated using <code class="filename">/dev/ptmx</code>. A suitable client such as <code class="command">virsh console</code> can connect to interact with the serial port locally.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="pty"></code>
+ <code class="sgmltag-starttag"><source path="/dev/pts/3"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ NB Special case
+ </td><td class="">
+ NB special case if <code class="sgmltag-starttag"><console type='pty'></code>, then the TTY path is also duplicated as an attribute <code class="sgmltag-attribute">tty='/dev/pts/3'</code> on the top level <code class="sgmltag-starttag"><console></code> tag. This provides compat with existing syntax for <code class="sgmltag-starttag"><console></code> tags.
+ </td><td class="auto-generated"> </td></tr><tr><td class="">
+ Host device proxy
+ </td><td class="">
+ The character device is passed through to the underlying physical character device. The device types must match, eg the emulated serial port should only be connected to a host serial port - don't connect a serial port to a parallel port.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="dev"></code>
+ <code class="sgmltag-starttag"><source path="/dev/ttyS0"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ Named pipe
+ </td><td class="">
+ The character device writes output to a named pipe. See pipe(7) MAN page for more info.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="pipe"></code>
+ <code class="sgmltag-starttag"><source path="/tmp/mypipe"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ TCP client/server
+ </td><td class="">
+ The character device acts as a TCP client connecting to a remote server.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="tcp"></code>
+ <code class="sgmltag-starttag"><source mode="connect" host="0.0.0.0" service="2445"/></code>
+ <code class="sgmltag-starttag"><protocol type="raw"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ <div class="para">
+ Or as a TCP server waiting for a client connection.
+ </div>
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="tcp"></code>
+ <code class="sgmltag-starttag"><source mode="bind" host="127.0.0.1" service="2445"/></code>
+ <code class="sgmltag-starttag"><protocol type="raw"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ <div class="para">
+ Alternatively you can use telnet instead of raw TCP. In addition, you can also use telnets (secure telnet) and tls.
+ </div>
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="tcp"></code>
+ <code class="sgmltag-starttag"><source mode="connect" host="0.0.0.0" service="2445"/></code>
+ <code class="sgmltag-starttag"><protocol type="telnet"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-starttag"><serial type="tcp"></code>
+ <code class="sgmltag-starttag"><source mode="bind" host="127.0.0.1" service="2445"/></code>
+ <code class="sgmltag-starttag"><protocol type="telnet"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+
+ </td></tr><tr><td class="">
+ UDP network console
+ </td><td class="">
+ The character device acts as a UDP netconsole service, sending and receiving packets. This is a lossy service.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="udp"></code>
+ <code class="sgmltag-starttag"><source mode="bind" host="0.0.0.0" service="2445"/></code>
+ <code class="sgmltag-starttag"><source mode="connect" host="0.0.0.0" service="2445"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ UNIX domain socket client/server
+ </td><td class="">
+ The character device acts as a UNIX domain socket server, accepting connections from local clients.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="unix"></code>
+ <code class="sgmltag-starttag"><source mode="bind" path="/tmp/foo"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr></tbody></table></div></div><br class="table-break" /></div></div><div class="section" id="section-libvirt-dom-xml-sound-devices"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.17. Sound devices</h2></div></div></div><div class="para">
+ A virtual sound card can be attached to the host via the sound element.
+ </div><div class="figure" id="fig-dom-xml-sound-devices"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><sound</span><span class="perl_Others"> model=</span><span class="perl_String">'es1370'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.64. Virtual sound card</h6></div><br class="figure-break" /><div class="para">
+ The sound element has one mandatory attribute, <code class="sgmltag-attribute">model</code>, which specifies what real sound device is emulated. Valid values are specific to the underlying hypervisor, though typical choices are <code class="sgmltag-attvalue">'es1370'</code>, <code class="sgmltag-attvalue">'sb16'</code>, <code class="sgmltag-attvalue">'ac97'</code>, and <code class="sgmltag-attvalue">'ich6'</code>. In addition, a sound element with ich6 model can have optional sub-elements <code class="sgmltag-element">codec</code> to attach various audio codecs to the audio device. If not specified, a default codec will be attached to allow playback and recording. Valid values are <code class="sgmltag-attvalue">'duplex'</code> (advertises a line-in and a line-out) and <code class="sgmltag-attvalue">'micro'</code> (advertises a speaker and a microphone).
+ </div><div class="figure" id="fig-dom-xml-sound-devices2"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><sound</span><span class="perl_Others"> model=</span><span class="perl_String">'ich6'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><codec</span><span class="perl_Others"> type=</span><span class="perl_String">'micro'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><sound/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.65. Sound devices</h6></div><br class="figure-break" /><div class="para">
+ Each sound element has an optional sub-element <code class="sgmltag-starttag"><address></code> which can tie the device to a particular PCI slot, documented above.
+ </div></div><div class="section" id="section-libvirt-dom-xml-watchdog"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.18. Watchdog device</h2></div></div></div><div class="para">
+ A virtual hardware watchdog device can be added to the guest via the <code class="sgmltag-starttag"><watchdog></code> element. The watchdog device requires an additional driver and management daemon in the guest. As merely enabling the watchdog in the libvirt configuration does not do anything useful on its own. Currently there is no support notification when the watchdog fires.
+ </div><div class="figure" id="fig--dom-xml-watchdog"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><watchdog</span><span class="perl_Others"> model=</span><span class="perl_String">'i6300esb'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><watchdog</span><span class="perl_Others"> model=</span><span class="perl_String">'i6300esb'</span><span class="perl_Others"> action=</span><span class="perl_String">'poweroff'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+<span class="perl_Error"><</span>/domain>
+</pre></div><h6>Figure J.66. Watchdog device</h6></div><br class="figure-break" /><div class="para">
+ The following attributes are declared in this XML:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">model</code> - The required <code class="sgmltag-attribute">model</code> attribute specifies what real watchdog device is emulated. Valid values are specific to the underlying hypervisor.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="sgmltag-attribute">model</code> attribute may take the following values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">i6300esb</code> — the recommended device, emulating a PCI Intel 6300ESB
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">ib700</code> — emulates an ISA iBase IB700
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">action</code> - The optional <code class="sgmltag-attribute">action</code> attribute describes what action to take when the watchdog expires. Valid values are specific to the underlying hypervisor. The <code class="sgmltag-attribute">action</code> attribute can have the following values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">reset</code> — default setting, forcefully resets the guest
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">shutdown</code> — gracefully shuts down the guest (not recommended)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">poweroff</code> — forcefully powers off the guest
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">pause</code> — pauses the guest
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">none</code> — does nothing
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">dump</code> — automatically dumps the guest.
+ </div></li></ul></div></li></ul></div><div class="para">
+ Note that the 'shutdown' action requires that the guest is responsive to ACPI signals. In the sort of situations where the watchdog has expired, guests are usually unable to respond to ACPI signals. Therefore using 'shutdown' is not recommended. In addition, the directory to save dump files can be configured by auto_dump_path in file /etc/libvirt/qemu.conf.
+ </div></div><div class="section" id="section-libvirt-dom-xml-memory-baloon-device"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.19. Memory balloon device</h2></div></div></div><div class="para">
+ A virtual memory balloon device is added to all Xen and KVM/QEMU guests. It will be seen as <code class="sgmltag-starttag"><memballoon></code> element. It will be automatically added when appropriate, so there is no need to explicitly add this element in the guest XML unless a specific PCI slot needs to be assigned. Note that if the memballoon device needs to be explicitly disabled, <code class="sgmltag-attribute">model='none'</code> may be used.
+ </div><div class="para">
+ The following example automatically added device with KVM
+ </div><div class="figure" id="fig-dom-xml-memory-baloon-device"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><memballoon</span><span class="perl_Others"> model=</span><span class="perl_String">'virtio'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.67. Memory balloon device</h6></div><br class="figure-break" /><div class="para">
+ Here is an example where the device is added manually with static PCI slot 2 requested
+ </div><div class="figure" id="fig-dom-xml-memory-baloon-device2"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><memballoon</span><span class="perl_Others"> model=</span><span class="perl_String">'virtio'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'pci'</span><span class="perl_Others"> domain=</span><span class="perl_String">'0x0000'</span><span class="perl_Others"> bus=</span><span class="perl_String">'0x00'</span><span class="perl_Others"> slot=</span><span class="perl_String">'0x02'</span><span class="perl_Others"> function=</span><span class="perl_String">'0x0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></memballoon></span>
+ <span class="perl_Keyword"></devices></span>
+<span class="perl_Error"><</span>/domain>
+</pre></div><h6>Figure J.68. Memory balloon device added manually</h6></div><br class="figure-break" /><div class="para">
+ The required <code class="sgmltag-element">model</code> attribute specifies what type of balloon device is provided. Valid values are specific to the virtualization platform are: <code class="sgmltag-element">'virtio'</code> which is the default setting with the KVM hypervisor or <code class="sgmltag-element">'xen'</code> which is the default setting with the Xen hypervisor.
+ </div></div><div class="section" id="section-libvirt-dom-xml-random-number-gen"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.20. Random number generator device</h2></div></div></div><div class="para">
+ The virtual random number generator device allows the host to pass through entropy to guest operating systems.
+ </div><div class="figure" id="fig--dom-xml-random-number-gen"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><rng</span><span class="perl_Others"> model=</span><span class="perl_String">'virtio'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><rate</span><span class="perl_Others"> period=</span><span class="perl_String">"2000"</span><span class="perl_Others"> bytes=</span><span class="perl_String">"1234"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><backend</span><span class="perl_Others"> model=</span><span class="perl_String">'random'</span><span class="perl_Keyword">></span>/dev/random<span class="perl_Keyword"></backend></span>
+ <span class="perl_Comment"><!-- OR --></span>
+ <span class="perl_Keyword"><backend</span><span class="perl_Others"> model=</span><span class="perl_String">'egd'</span><span class="perl_Others"> type=</span><span class="perl_String">'udp'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'bind'</span><span class="perl_Others"> service=</span><span class="perl_String">'1234'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'connect'</span><span class="perl_Others"> host=</span><span class="perl_String">'1.2.3.4'</span><span class="perl_Others"> service=</span><span class="perl_String">'1234'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"></backend></span>
+ <span class="perl_Keyword"></rng></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.69. Random number generator device</h6></div><br class="figure-break" /><div class="para">
+ The random number generator device allows the following attributes/elements:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">model</code> - The required <code class="sgmltag-attribute">model</code> attribute specifies what type of RNG device is provided. <code class="sgmltag-attvalue">'virtio'</code> — supported by qemu and virtio-rng kernel module
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><backend></code> - The <code class="sgmltag-starttag"><backend></code> element specifies the source of entropy to be used for the domain. The source model is configured using the <code class="sgmltag-attribute">model</code> attribute. Supported source models include <code class="sgmltag-attvalue">'random'</code> — <code class="filename">/dev/random</code> (default setting) or similar device as source and <code class="sgmltag-attvalue">'egd'</code> which sets a EGD protocol backend.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">backend type='random'</code> - This <code class="sgmltag-starttag"><backend></code> type expects a non-blocking character device as input. Examples of such devices are <code class="filename">/dev/random</code> and <code class="filename">/dev/urandom</code>. The file name is specified as contents of the <code class="sgmltag-starttag"><backend></code> element. When no file name is specified the hypervisor default is used.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><backend type='egd'></code> - This backend connects to a source using the EGD protocol. The source is specified as a character device. Refer to character device host interface for more information.
+ </div></li></ul></div></div><div class="section" id="section-libvirt-dom-xml-tpm-device"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.21. TPM devices</h2></div></div></div><div class="para">
+ The TPM device enables a QEMU guest to have access to TPM functionality. The TPM passthrough device type provides access to the host's TPM for one QEMU guest. No other software may be is using the TPM device, typically <code class="filename">/dev/tpm0</code>, at the time the QEMU guest is started. The following domain XML example shows the usage of the TPM passthrough device
+ </div><div class="figure" id="fig-libvirt-dom-xml-tpm-device"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><tpm</span><span class="perl_Others"> model=</span><span class="perl_String">'tpm-tis'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><backend</span><span class="perl_Others"> type=</span><span class="perl_String">'passthrough'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><backend</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/tpm0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></backend></span>
+ <span class="perl_Keyword"></tpm></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+
+</pre></div><h6>Figure J.70. TPM devices</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-attribute">model</code> attribute specifies what device model QEMU provides to the guest. If no model name is provided, tpm-tis will automatically be chosen. The <code class="sgmltag-starttag"><backend></code> element specifies the type of TPM device. The following types are supported: <code class="sgmltag-attvalue">'passthrough'</code> — uses the host's TPM device and <code class="sgmltag-attvalue">'passthrough'</code>. This backend type requires exclusive access to a TPM device on the host. An example for such a device is <code class="filename">/dev/tpm0</code>. The filename is specified as path attribute of the source element. If no file name is specified then <code class="filename">/dev/tpm0</code> is automatically used.
+ </div></div><div class="section" id="section-libvirt-dom-xml-security-label"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.22. Security label</h2></div></div></div><div class="para">
+ The <code class="sgmltag-starttag"><seclabel></code> element allows control over the operation of the security drivers. There are three basic modes of operation, <code class="sgmltag-attvalue">'dynamic'</code> where libvirt automatically generates a unique security label, <code class="sgmltag-attvalue">'static'</code> where the application/administrator chooses the labels, or <code class="sgmltag-element">'none'</code> where confinement is disabled. With dynamic label generation, libvirt will always automatically relabel any resources associated with the virtual machine. With static label assignment, by default, the administrator or application must ensure labels are set correctly on any resources, however, automatic relabeling can be enabled if desired.
+ </div><div class="para">
+ If more than one security driver is used by libvirt, multiple seclabel tags can be used, one for each driver and the security driver referenced by each tag can be defined using the attribute <code class="sgmltag-attribute">model</code> Valid input XML configurations for the top-level security label are:
+ </div><div class="figure" id="fig-libvirt-dom-xml-security-label"><div class="figure-contents"><pre class="programlisting">
+
+ <span class="perl_Keyword"><seclabel</span><span class="perl_Others"> type=</span><span class="perl_String">'dynamic'</span><span class="perl_Others"> model=</span><span class="perl_String">'selinux'</span><span class="perl_Keyword">/></span>
+
+ <span class="perl_Keyword"><seclabel</span><span class="perl_Others"> type=</span><span class="perl_String">'dynamic'</span><span class="perl_Others"> model=</span><span class="perl_String">'selinux'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><baselabel></span>system_u:system_r:my_svirt_t:s0<span class="perl_Keyword"></baselabel></span>
+ <span class="perl_Keyword"></seclabel></span>
+
+ <span class="perl_Keyword"><seclabel</span><span class="perl_Others"> type=</span><span class="perl_String">'static'</span><span class="perl_Others"> model=</span><span class="perl_String">'selinux'</span><span class="perl_Others"> relabel=</span><span class="perl_String">'no'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><label></span>system_u:system_r:svirt_t:s0:c392,c662<span class="perl_Keyword"></label></span>
+ <span class="perl_Keyword"></seclabel></span>
+
+ <span class="perl_Keyword"><seclabel</span><span class="perl_Others"> type=</span><span class="perl_String">'static'</span><span class="perl_Others"> model=</span><span class="perl_String">'selinux'</span><span class="perl_Others"> relabel=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><label></span>system_u:system_r:svirt_t:s0:c392,c662<span class="perl_Keyword"></label></span>
+ <span class="perl_Keyword"></seclabel></span>
+
+ <span class="perl_Keyword"><seclabel</span><span class="perl_Others"> type=</span><span class="perl_String">'none'</span><span class="perl_Keyword">/></span>
+</pre></div><h6>Figure J.71. Security label</h6></div><br class="figure-break" /><div class="para">
+ If no <code class="sgmltag-attribute">'type'</code> attribute is provided in the input XML, then the security driver default setting will be used, which may be either <code class="sgmltag-attvalue">'none'</code> or <code class="sgmltag-attvalue">'dynamic'</code>. If a <code class="sgmltag-starttag"><baselabel></code> is set but no <code class="sgmltag-attribute">'type'</code> is set, then the type is presumed to be <code class="sgmltag-attribute">'dynamic'</code>. When viewing the XML for a running guest with automatic resource relabeling active, an additional XML element, <code class="sgmltag-attribute">imagelabel</code>, will be included. This is an output-only element, so will be ignored in user supplied XML documents.
+ </div><div class="para">
+ The following elements can be manipulated with the following values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">type</code> - Either <code class="sgmltag-element">static</code>, <code class="sgmltag-element">dynamic</code> or <code class="sgmltag-element">none</code> to determine whether libvirt automatically generates a unique security label or not.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">model</code> - A valid security model name, matching the currently activated security model
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">relabel</code> - Either <code class="sgmltag-attvalue">yes</code> or <code class="sgmltag-attvalue">no</code>. This must always be <code class="sgmltag-attvalue">yes</code> if dynamic label assignment is used. With static label assignment it will default to <code class="sgmltag-attvalue">no</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><label></code> - If static labelling is used, this must specify the full security label to assign to the virtual domain. The format of the content depends on the security driver in use:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">SELinux</code>: a SELinux context.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">AppArmor</code>: an AppArmor profile.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">DAC</code>: owner and group separated by colon. They can be defined both as user/group names or uid/gid. The driver will first try to parse these values as names, but a leading plus sign can used to force the driver to parse them as uid or gid.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><baselabel></code> - If dynamic labelling is used, this can optionally be used to specify the base security label. The format of the content depends on the security driver in use.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><imagelabel></code> - This is an output only element, which shows the security label used on resources associated with the virtual domain. The format of the content depends on the security driver in use When relabeling is in effect, it is also possible to fine-tune the labeling done for specific source file names, by either disabling the labeling (useful if the file lives on NFS or other file system that lacks security labeling) or requesting an alternate label (useful when a management application creates a special label to allow sharing of some, but not all, resources between domains). When a seclabel element is attached to a specific path rather than the top-level domain assignment, only the attribute relabel or the sub-element label are supported.
+ </div></li></ul></div></div><div class="section" id="section-libvirt-dom-xml-example"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.23. Example domain XML configuration</h2></div></div></div><div class="para">
+ QEMU emulated guest on x86_64
+ </div><div class="figure" id="fig-dom-xml-example-qemu"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain</span><span class="perl_Others"> type=</span><span class="perl_String">'qemu'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><name></span>QEmu-fedora-i686<span class="perl_Keyword"></name></span>
+ <span class="perl_Keyword"><uuid></span>c7a5fdbd-cdaf-9455-926a-d65c16db1809<span class="perl_Keyword"></uuid></span>
+ <span class="perl_Keyword"><memory></span>219200<span class="perl_Keyword"></memory></span>
+ <span class="perl_Keyword"><currentMemory></span>219200<span class="perl_Keyword"></currentMemory></span>
+ <span class="perl_Keyword"><vcpu></span>2<span class="perl_Keyword"></vcpu></span>
+ <span class="perl_Keyword"><os></span>
+ <span class="perl_Keyword"><type</span><span class="perl_Others"> arch=</span><span class="perl_String">'i686'</span><span class="perl_Others"> machine=</span><span class="perl_String">'pc'</span><span class="perl_Keyword">></span>hvm<span class="perl_Keyword"></type></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> dev=</span><span class="perl_String">'cdrom'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></os></span>
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><emulator></span>/usr/bin/qemu-system-x86_64<span class="perl_Keyword"></emulator></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'file'</span><span class="perl_Others"> device=</span><span class="perl_String">'cdrom'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> file=</span><span class="perl_String">'/home/user/boot.iso'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hdc'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><readonly/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'file'</span><span class="perl_Others"> device=</span><span class="perl_String">'disk'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> file=</span><span class="perl_String">'/home/user/fedora.img'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hda'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'vnc'</span><span class="perl_Others"> port=</span><span class="perl_String">'-1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.72. Example domain XML config</h6></div><br class="figure-break" /><div class="para">
+ KVM hardware accelerated guest on i686
+ </div><div class="figure" id="fig-dom-xml-example-kvm"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain</span><span class="perl_Others"> type=</span><span class="perl_String">'kvm'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><name></span>demo2<span class="perl_Keyword"></name></span>
+ <span class="perl_Keyword"><uuid></span>4dea24b3-1d52-d8f3-2516-782e98a23fa0<span class="perl_Keyword"></uuid></span>
+ <span class="perl_Keyword"><memory></span>131072<span class="perl_Keyword"></memory></span>
+ <span class="perl_Keyword"><vcpu></span>1<span class="perl_Keyword"></vcpu></span>
+ <span class="perl_Keyword"><os></span>
+ <span class="perl_Keyword"><type</span><span class="perl_Others"> arch=</span><span class="perl_String">"i686"</span><span class="perl_Keyword">></span>hvm<span class="perl_Keyword"></type></span>
+ <span class="perl_Keyword"></os></span>
+ <span class="perl_Keyword"><clock</span><span class="perl_Others"> sync=</span><span class="perl_String">"localtime"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><emulator></span>/usr/bin/qemu-kvm<span class="perl_Keyword"></emulator></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'file'</span><span class="perl_Others"> device=</span><span class="perl_String">'disk'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> file=</span><span class="perl_String">'/var/lib/libvirt/images/demo2.img'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hda'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">'24:42:53:21:52:45'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'vnc'</span><span class="perl_Others"> port=</span><span class="perl_String">'-1'</span><span class="perl_Others"> keymap=</span><span class="perl_String">'de'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.73. Example domain XML config</h6></div><br class="figure-break" /></div></div></div><div xml:lang="en-US" class="appendix" id="appe-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Revision_History" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Revision History</h1></div></div></div><div class="para">
+ <div class="revhistory"><table summary="Revision History"><tr><th align="left" valign="top" colspan="3"><strong>Revision History</strong></th></tr><tr><td align="left">Revision 0.2-0</td><td align="left">Tue May 28 2013</td><td align="left"><span class="author"><span class="firstname">Laura</span> <span class="surname">Novich</span></span></td></tr><tr><td align="left" colspan="3">
+ <table border="0" summary="Simple list" class="simplelist"><tr><td>Completed merger of guides and prepared for final publishing.</td></tr></table>
+
+ </td></tr><tr><td align="left">Revision 0.1-0</td><td align="left">Tue Jan 15 2013</td><td align="left"><span class="author"><span class="firstname">Laura</span> <span class="surname">Bailey</span></span></td></tr><tr><td align="left" colspan="3">
+ <table border="0" summary="Simple list" class="simplelist"><tr><td>Combined F18 Virtualization Administration Guide and Virtualization Host Configuration and Guest Installation Guide for use in Fedora 19.</td></tr></table>
+
+ </td></tr></table></div>
+
+ </div></div></div></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Bridge_Device.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Bridge_Device.html
new file mode 100644
index 0000000..78a51ac
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Bridge_Device.html
@@ -0,0 +1,46 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.11. Unable to add bridge br0 port vnet0: No such device</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_DHCP_Response_Checksums.html" title="B.10. Could not add rule to fixup DHCP response checksums on network 'default'" /><link rel="next" href="App_Generic_Ethernet.html" title="B.12. Guest is unable to start with error: warning: could not open /dev/net/tun" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="App_DHCP_Response_Checksums.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_Generic_Ethernet.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_Bridge_Device" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.11. Unable to add bridge br0 port vnet0: No such device</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The following error message appears:
+ </div><pre class="screen">Unable to add bridge <em class="replaceable"><code>name_of_bridge</code></em> port vnet0: No such device</pre><div class="para">
+ For example, if the bridge name is <em class="replaceable"><code>br0</code></em>, the error message will appear as:
+ </div><pre class="screen">Unable to add bridge br0 port vnet0: No such device</pre><div class="para">
+ In <span class="application"><strong>libvirt</strong></span> versions 0.9.6 and earlier, the same error appears as:
+ </div><pre class="screen">Failed to add tap interface to bridge <em class="replaceable"><code>name_of_bridge</code></em>: No such device</pre><div class="para">
+ Or for example, if the bridge is named <em class="replaceable"><code>br0</code></em>:
+ </div><pre class="screen">Failed to add tap interface to bridge <em class="replaceable"><code>'br0'</code></em>: No such device</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ Both error messages reveal that the bridge device specified in the guest's (or domain's) <code class="code"><interface></code> definition does not exist.
+ </div><div class="para">
+ To verify the bridge device listed in the error message does not exist, use the shell command <code class="command">ifconfig <em class="replaceable"><code>br0</code></em></code>.
+ </div><div class="para">
+ A message similar to this confirms the host has no bridge by that name:
+ </div><pre class="screen"><em class="replaceable"><code>br0</code></em>: error fetching interface information: Device not found</pre><div class="para">
+ If this is the case, continue to the solution.
+ </div><div class="para">
+ However, if the resulting message is similar to the following, the issue exists elsewhere:
+ </div><pre class="screen"><em class="replaceable"><code>br0</code></em> Link encap:Ethernet HWaddr 00:00:5A:11:70:48
+ inet addr:10.22.1.5 Bcast:10.255.255.255 Mask:255.0.0.0
+ UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
+ RX packets:249841 errors:0 dropped:0 overruns:0 frame:0
+ TX packets:281948 errors:0 dropped:0 overruns:0 carrier:0
+ collisions:0 txqueuelen:0
+ RX bytes:106327234 (101.4 MiB) TX bytes:21182634 (20.2 MiB)</pre></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Edit the existing bridge or create a new bridge with <code class="command">virsh</code></span></dt><dd><div class="para">
+ Use <code class="command">virsh</code> to either edit the settings of an existing bridge or network, or to add the bridge device to the host system configuration.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Edit the existing bridge settings using <code class="command">virsh</code></span></dt><dd><div class="para">
+ Use <code class="command">virsh edit <em class="replaceable"><code>name_of_guest</code></em></code> to change the <code class="code"><interface></code> definition to use a bridge or network that already exists.
+ </div><div class="para">
+ For example, change <code class="code">type='bridge'</code> to <code class="code">type='network'</code>, and <code class="code"><source bridge='br0'/></code> to <code class="code"><source network='default'/></code>.
+ </div></dd><dt class="varlistentry"><span class="term">Create a host bridge using <code class="command">virsh</code></span></dt><dd><div class="para">
+ For <span class="application"><strong>libvirt</strong></span> version 0.9.8 and later, a bridge device can be created with the <code class="command">virsh iface-bridge</code> command. This will create a bridge device <em class="replaceable"><code>br0</code></em> with <code class="filename">eth0</code>, the physical network interface which is set as part of a bridge, attached:
+ </div><pre class="screen">virsh iface-bridge eth0 <em class="replaceable"><code>br0</code></em></pre><div class="para">
+ Optional: If desired, remove this bridge and restore the original <code class="filename">eth0</code> configuration with this command:
+ </div><pre class="screen">virsh iface-unbridge <em class="replaceable"><code>br0</code></em></pre></dd></dl></div></dd><dt class="varlistentry"><span class="term">Create a host bridge manually</span></dt><dd><div class="para">
+ For older versions of <span class="application"><strong>libvirt</strong></span>, it is possible to manually create a bridge device on the host. Refer to <a class="xref" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html">Section 11.3, “Bridged networking with libvirt”</a> for instructions.
+ </div></dd></dl></div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_DHCP_Response_Checksums.html"><strong>Prev</strong>B.10. Could not add rule to fixup DHCP response c...</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="App_Generic_Ethernet.html"><strong>Next</strong>B.12. Guest is unable to start with error: warnin...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_DHCP_Response_Checksums.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_DHCP_Response_Checksums.html
new file mode 100644
index 0000000..a9d7a8e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_DHCP_Response_Checksums.html
@@ -0,0 +1,18 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.10. Could not add rule to fixup DHCP response checksums on network 'default'</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_Macvtap.html" title="B.9. Guest can reach outside network, but cannot reach host when using macvtap interface" /><link rel="next" href="App_Bridge_Device.html" title="B.11. Unable to add bridge br0 port vnet0: No such device" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="App_Macvtap.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_Bridge_Device.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_DHCP_Response_Checksums" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.10. Could not add rule to fixup DHCP response checksums on network <em class="replaceable"><code>'default'</code></em></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ This message appears:
+ </div><pre class="screen">Could not add rule to fixup DHCP response checksums on network <em class="replaceable"><code>'default'</code></em></pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ Although this message appears to be evidence of an error, it is almost always harmless.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Unless the problem you are experiencing is that the guest virtual machines are unable to acquire IP addresses through DHCP, this message can be ignored.
+ </div><div class="para">
+ If this is the case, refer to <a class="xref" href="App_PXE_Guest_Boot_Fail.html">Section B.8, “PXE boot (or DHCP) on guest failed”</a> for further details on this situation.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_Macvtap.html"><strong>Prev</strong>B.9. Guest can reach outside network, but cannot ...</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="App_Bridge_Device.html"><strong>Next</strong>B.11. Unable to add bridge br0 port vnet0: No suc...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Domain_Console.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Domain_Console.html
new file mode 100644
index 0000000..7262006
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Domain_Console.html
@@ -0,0 +1,29 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.5. Internal error cannot find character device (null)</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_Domain_Monitor_Socket.html" title="B.4. Guest starting fails with error: monitor socket did not show up" /><link rel="next" href="App_Domain_Not_Booting.html" title="B.6. Guest virtual machine booting stalls with error: No boot device" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 clas
s="docnav"><li class="previous"><a accesskey="p" href="App_Domain_Monitor_Socket.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_Domain_Not_Booting.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_Domain_Console" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.5. <code class="computeroutput">Internal error cannot find character device (null)</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ This error message appears when attempting to connect to a guest virtual machine's console:
+ </div><pre class="screen"># virsh console test2 Connected to domain test2 Escape character is ^] error: internal error cannot find character device (null)</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This error message shows that there is no serial console configured for the guest virtual machine.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Set up a serial console in the guest's XML file.
+ </div><div class="procedure"><h6>Procedure B.1. Setting up a serial console in the guest's XML</h6><ol class="1"><li class="step"><div class="para">
+ Add the following XML to the guest virtual machine's XML using <span class="application"><strong>virsh edit</strong></span>:
+ </div><pre class="programlisting"><serial type='pty'>
+ <target port='0'/>
+</serial>
+<console type='pty'>
+ <target type='serial' port='0'/>
+</console></pre></li><li class="step"><div class="para">
+ Set up the console in the guest kernel command line.
+ </div><div class="para">
+ To do this, either log in to the guest virtual machine to edit the <code class="filename">/boot/grub/grub.conf</code> file directly, or use the <span class="application"><strong>virt-edit</strong></span> command line tool. Add the following to the guest kernel command line:
+ </div><pre class="screen">console=ttyS0,115200</pre></li><li class="step"><div class="para">
+ Run the followings command:
+ </div><pre class="screen"># virsh start vm && virsh console vm</pre></li></ol></div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_Domain_Monitor_Socket.html"><strong>Prev</strong>B.4. Guest starting fails with error: monitor soc...</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="App_Domain_Not_Booting.html"><strong>Next</strong>B.6. Guest virtual machine booting stalls with er...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Domain_Monitor_Socket.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Domain_Monitor_Socket.html
new file mode 100644
index 0000000..fc56440
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Domain_Monitor_Socket.html
@@ -0,0 +1,33 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.4. Guest starting fails with error: monitor socket did not show up</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_Domain_Processor.html" title="B.3. The guest virtual machine cannot be started: internal error guest CPU is not compatible with host CPU" /><link rel="next" href="App_Domain_Console.html" title="B.5. Internal error cannot find character device (null)" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="App_Domain_Processor.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_Domain_Console.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_Domain_Monitor_Socket" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.4. Guest starting fails with error: <code class="computeroutput">monitor socket did not show up</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The guest virtual machine (or domain) starting fails with this error (or similar):
+ </div><pre class="screen"># virsh -c qemu:///system create <em class="replaceable"><code>name_of_guest</code></em>.xml error: Failed to create domain from <em class="replaceable"><code>name_of_guest</code></em>.xml error: monitor socket did not show up.: Connection refused</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This error message shows:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <span class="application"><strong>libvirt</strong></span> is working;
+ </div></li><li class="listitem"><div class="para">
+ The <span class="application"><strong>QEMU</strong></span> process failed to start up; and
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>libvirt</strong></span> quits when trying to connect <span class="application"><strong>QEMU</strong></span> or the QEMU agent monitor socket.
+ </div></li></ol></div><div class="para">
+ To understand the error details, examine the guest log:
+ </div><pre class="screen"># cat /var/log/libvirt/qemu/<em class="replaceable"><code>name_of_guest</code></em>.log
+LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-kvm -S -M pc -enable-kvm -m 768 -smp 1,sockets=1,cores=1,threads=1 -name <em class="replaceable"><code>name_of_guest</code></em> -uuid ebfaadbe-e908-ba92-fdb8-3fa2db557a42 -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/<em class="replaceable"><code>name_of_guest</code></em>.monitor,server,nowait -mon chardev=monitor,mode=readline -no-reboot -boot c -kernel /var/lib/libvirt/boot/vmlinuz -initrd /var/lib/libvirt/boot/initrd.img -append method=http://www.example.com/pub/product/release/version/x86_64/os/ -drive file=/var/lib/libvirt/images/<em class="replaceable"><code>name_of_guest</code></em>.img,if=none,id=drive-ide0-0-0,boot=on -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -device virtio-net-pci,vlan=0,id=net0,mac=52:40:00:f4:f1:0a,bus=pci.0,addr=0x4 -net tap,fd=42,vlan=0,name=hostnet0 -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -vnc 127
.0.0.1:0 -k en-gb -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,
+addr=0x3
+char device redirected to /dev/pts/1
+qemu: could not load kernel '/var/lib/libvirt/boot/vmlinuz':
+Permission denied</pre></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ The guest log contains the details needed to fix the error.
+ </div><div class="para">
+ If a host is shut down while the guest is still running a <span class="application"><strong>libvirt</strong></span> version prior to 0.9.5, the libvirt-guest's init script attempts to perform a managed save of the guest. If the managed save was incomplete (for example, due to loss of power before the managed save image was flushed to disk), the save image is corrupted and will not be loaded by <span class="application"><strong>QEMU</strong></span>. The older version of <span class="application"><strong>libvirt</strong></span> does not recognize the corruption, making the problem perpetual. In this case, the guest log will show an attempt to use <code class="command">-incoming</code> as one of its arguments, meaning that <span class="application"><strong>libvirt</strong></span> is trying to start <span class="application"><strong>QEMU</strong></span> by migrating in the saved state file.
+ </div><div class="para">
+ This problem can be fixed by running <code class="command">virsh managedsave-remove <em class="replaceable"><code>name_of_guest</code></em></code> to remove the corrupted managed save image. Newer versions of <span class="application"><strong>libvirt</strong></span> take steps to avoid the corruption in the first place, as well as adding <code class="command">virsh start --force-boot <em class="replaceable"><code>name_of_guest</code></em></code> to bypass any managed save image.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_Domain_Processor.html"><strong>Prev</strong>B.3. The guest virtual machine cannot be started:...</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="App_Domain_Console.html"><strong>Next</strong>B.5. Internal error cannot find character device ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Domain_Not_Booting.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Domain_Not_Booting.html
new file mode 100644
index 0000000..be72da4
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Domain_Not_Booting.html
@@ -0,0 +1,86 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.6. Guest virtual machine booting stalls with error: No boot device</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_Domain_Console.html" title="B.5. Internal error cannot find character device (null)" /><link rel="next" href="App_Virt_Net_Not_Starting.html" title="B.7. Virtual network default has not been started" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 a
ccesskey="p" href="App_Domain_Console.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_Virt_Net_Not_Starting.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_Domain_Not_Booting" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.6. Guest virtual machine booting stalls with error: <code class="computeroutput">No boot device</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ After building a guest virtual machine from an existing disk image, the guest booting stalls with the error message <code class="computeroutput">No boot device</code>. However, the guest virtual machine can start successfully using the <code class="command">QEMU</code> command directly.
+ </div></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ The disk's bus type is not specified in the command for importing the existing disk image:
+ </div><pre class="screen"># virt-install \
+--connect qemu:///system \
+--ram 2048 -n rhel_64 \
+--os-type=linux --os-variant=rhel5 \
+--disk path=/root/RHEL-Server-5.8-64-virtio.qcow2,device=disk,format=qcow2 \
+--vcpus=2 --graphics spice --noautoconsole --import
+</pre><div class="para">
+ However, the command line used to boot up the guest virtual machine using <span class="application"><strong>QEMU</strong></span> directly shows that it uses <code class="literal">virtio</code> for its bus type:
+ </div><pre class="screen"># ps -ef | grep qemu
+/usr/libexec/qemu-kvm -monitor stdio -drive file=/root/RHEL-Server-5.8-32-virtio.qcow2,index=0,<span class="bold bold"><strong>if=virtio</strong></span>,media=disk,cache=none,format=qcow2 -net nic,vlan=0,model=rtl8139,macaddr=00:30:91:aa:04:74 -net tap,vlan=0,script=/etc/qemu-ifup,downscript=no -m 2048 -smp 2,cores=1,threads=1,sockets=2 -cpu qemu64,+sse2 -soundhw ac97 -rtc-td-hack -M rhel5.6.0 -usbdevice tablet -vnc :10 -boot c -no-kvm-pit-reinjection</pre><div class="para">
+ Note the <em class="parameter"><code>bus=</code></em> in the guest's XML generated by <span class="application"><strong>libvirt</strong></span> for the imported guest:
+ </div><pre class="programlisting">
+<domain type='qemu'>
+ <name>rhel_64</name>
+ <uuid>6cd34d52-59e3-5a42-29e4-1d173759f3e7</uuid>
+ <memory>2097152</memory>
+ <currentMemory>2097152</currentMemory>
+ <vcpu>2</vcpu>
+ <os>
+ <type arch='x86_64' machine='rhel5.4.0'>hvm</type>
+ <boot dev='hd'/>
+ </os>
+ <features>
+ <acpi/>
+ <apic/>
+ <pae/>
+ </features>
+ <clock offset='utc'>
+ <timer name='pit' tickpolicy='delay'/>
+ </clock>
+ <on_poweroff>destroy</on_poweroff>
+ <on_reboot>restart</on_reboot>
+ <on_crash>restart</on_crash>
+ <devices>
+ <emulator>/usr/libexec/qemu-kvm</emulator>
+ <disk type='file' device='disk'>
+ <driver name='qemu' type='qcow2' cache='none'/>
+ <source file='/root/RHEL-Server-5.8-64-virtio.qcow2'/>
+ <emphasis role="bold"><target dev='hda' bus='ide'/></emphasis>
+ <address type='drive' controller='0' bus='0' unit='0'/>
+ </disk>
+ <controller type='ide' index='0'/>
+ <interface type='bridge'>
+ <mac address='54:52:00:08:3e:8c'/>
+ <source bridge='br0'/>
+ </interface>
+ <serial type='pty'>
+ <target port='0'/>
+ </serial>
+ <console type='pty'>
+ <target port='0'/>
+ </console>
+ <input type='mouse' bus='ps2'/>
+ <graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
+ <video>
+ <model type='cirrus' vram='9216' heads='1'/>
+ </video>
+ </devices>
+ </domain>
+</pre><div class="para">
+ The bus type for the disk is set as <em class="parameter"><code>ide</code></em>, which is the default value set by <span class="application"><strong>libvirt</strong></span>. This is the incorrect bus type, and has caused the unsuccessful boot for the imported guest.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="procedure"><h6>Procedure B.2. Correcting the disk bus type</h6><ol class="1"><li class="step"><div class="para">
+ Undefine the imported guest, then re-import it with <em class="parameter"><code>bus=virtio</code></em> and the following:
+ </div><pre class="screen"># virsh destroy rhel_64
+# virsh undefine rhel_64
+# virt-install \
+--connect qemu:///system \
+--ram 1024 -n rhel_64 -r 2048 \
+--os-type=linux --os-variant=rhel5 \
+--disk path=/root/RHEL-Server-5.8-64-virtio.qcow2,device=disk,<span class="bold bold"><strong>bus=virtio</strong></span>,format=qcow2 \
+--vcpus=2 --graphics spice --noautoconsole --import</pre></li><li class="step"><div class="para">
+ Edit the imported guest's XML using <code class="command">virsh edit</code> and correct the disk bus type.
+ </div></li></ol></div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_Domain_Console.html"><strong>Prev</strong>B.5. Internal error cannot find character device ...</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="App_Virt_Net_Not_Starting.html"><strong>Next</strong>B.7. Virtual network default has not been started</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Domain_Processor.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Domain_Processor.html
new file mode 100644
index 0000000..0b7bebf
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Domain_Processor.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.3. The guest virtual machine cannot be started: internal error guest CPU is not compatible with host CPU</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="Sect_Other_Connectivity_Errors.html" title="B.2.3. Other connectivity errors" /><link rel="next" href="App_Domain_Monitor_Socket.html" title="B.4. Guest starting fails with error: monitor socket did not show up" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="previo
us"><a accesskey="p" href="Sect_Other_Connectivity_Errors.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_Domain_Monitor_Socket.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_Domain_Processor" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.3. The guest virtual machine cannot be started: <code class="computeroutput">internal error guest CPU is not compatible with host CPU</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ Running on an Intel Core i7 processor (which <span class="application"><strong>virt-manager</strong></span> refers to as <code class="literal">Nehalem</code>, or the older Core 2 Duo, referred to as <code class="literal">Penryn</code>), a KVM guest (or domain) is created using <span class="application"><strong>virt-manager</strong></span>. After installation, the guest's processor is changed to match the host's CPU. The guest is then unable to start and reports this error:
+ </div><pre class="screen">2012-02-06 17:49:15.985+0000: 20757: error : qemuBuildCpuArgStr:3565 : internal error guest CPU is not compatible with host CPU</pre><div class="para">
+ Additionally, clicking <code class="literal">Copy host CPU configuration</code> in <span class="application"><strong>virt-manager</strong></span> shows Pentium III instead of <code class="literal">Nehalem</code> or <code class="literal">Penryn</code>.
+ </div></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ The <code class="filename">/usr/share/libvirt/cpu_map.xml</code> file lists the flags that define each CPU model. The <code class="literal">Nehalem</code> and <code class="literal">Penryn</code> definitions contain this:
+ </div><pre class="programlisting"><feature name='nx'/></pre><div class="para">
+ As a result, the <code class="literal">NX</code> (or <code class="literal">No eXecute</code>) flag needs to be presented to identify the CPU as <code class="literal">Nehalem</code> or <code class="literal">Penryn</code>. However, in <code class="filename">/proc/cpuinfo</code>, this flag is missing.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Nearly all new BIOSes allow enabling or disabling of the <code class="literal">No eXecute</code> bit. However, if disabled, some CPUs do not report this flag and thus <span class="application"><strong>libvirt</strong></span> detects a different CPU. Enabling this functionality instructs <span class="application"><strong>libvirt</strong></span> to report the correct CPU. Refer to your hardware documentation for further instructions on this subject.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="Sect_Other_Connectivity_Errors.html"><strong>Prev</strong>B.2.3. Other connectivity 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="App_Domain_Monitor_Socket.html"><strong>Next</strong>B.4. Guest starting fails with error: monitor soc...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Generic_Ethernet.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Generic_Ethernet.html
new file mode 100644
index 0000000..875f5e8
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Generic_Ethernet.html
@@ -0,0 +1,45 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.12. Guest is unable to start with error: warning: could not open /dev/net/tun</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_Bridge_Device.html" title="B.11. Unable to add bridge br0 port vnet0: No such device" /><link rel="next" href="App_Migration_Address.html" title="B.13. Migration fails with Error: unable to resolve address" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="previou
s"><a accesskey="p" href="App_Bridge_Device.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_Migration_Address.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_Generic_Ethernet" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.12. Guest is unable to start with error: <code class="computeroutput">warning: could not open /dev/net/tun</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The guest virtual machine does not start after configuring a <code class="code">type='ethernet'</code> (also known as 'generic ethernet') interface in the host system. An error appears either in <code class="filename">libvirtd.log</code>, <code class="filename">/var/log/libvirt/qemu/<em class="replaceable"><code>name_of_guest</code></em>.log</code>, or in both, similar to the below message:
+ </div><pre class="screen">warning: could not open /dev/net/tun: no virtual network emulation qemu-kvm: -netdev tap,script=/etc/my-qemu-ifup,id=hostnet0: Device 'tap' could not be initialized</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ Use of the generic ethernet interface type (<code class="code"><interface type='ethernet'></code>) is discouraged, because using it requires lowering the level of host protection against potential security flaws in <span class="application"><strong>QEMU</strong></span> and its guests. However, it is sometimes necessary to use this type of interface to take advantage of some other facility that is not yet supported directly in <span class="application"><strong>libvirt</strong></span>. For example, <span class="application"><strong>openvswitch</strong></span> was not supported in <span class="application"><strong>libvirt</strong></span> until <span class="package">libvirt-0.9.11</span>, so in older versions of <span class="application"><strong>libvirt</strong></span>, <code class="code"><interface type='ethernet'></code> was the only way to connect a guest to an <span class="application"><strong>openvswitch</strong></span> bridge.
+ </div><div class="para">
+ However, if you configure a <code class="code"><interface type='ethernet'></code> interface without making any other changes to the host system, the guest virtual machine will not start successfully.
+ </div><div class="para">
+ The reason for this failure is that for this type of interface, a script called by <span class="application"><strong>QEMU</strong></span> needs to manipulate the tap device. However, with <code class="code">type='ethernet'</code> configured, in an attempt to lock down <span class="application"><strong>QEMU</strong></span>, <span class="application"><strong>libvirt</strong></span> and SELinux have put in place several checks to prevent this. (Normally, <span class="application"><strong>libvirt</strong></span> performs all of the tap device creation and manipulation, and passes an open file descriptor for the tap device to <span class="application"><strong>QEMU</strong></span>.)
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Reconfigure the host system to be compatible with the generic ethernet interface.
+ </div><div class="procedure"><h6>Procedure B.4. Reconfiguring the host system to use the generic ethernet interface</h6><ol class="1"><li class="step"><div class="para">
+ Set SELinux to permissive by configuring <code class="code">SELINUX=permissive</code> in <code class="filename">/etc/selinux/config</code>:
+ </div><pre class="screen"># This file controls the state of SELinux on the system.
+# SELINUX= can take one of these three values:
+# enforcing - SELinux security policy is enforced.
+# permissive - SELinux prints warnings instead of enforcing.
+# disabled - No SELinux policy is loaded.
+SELINUX=permissive
+# SELINUXTYPE= can take one of these two values:
+# targeted - Targeted processes are protected,
+# mls - Multi Level Security protection.
+SELINUXTYPE=targeted</pre></li><li class="step"><div class="para">
+ From a root shell, run the command <code class="command">setenforce permissive</code>.
+ </div></li><li class="step"><div class="para">
+ In <code class="filename">/etc/libvirt/qemu.conf</code> add or edit the following lines:
+ </div><pre class="screen">clear_emulator_capabilities = 0</pre><pre class="screen">user = "root"</pre><pre class="screen">group = "root"</pre><pre class="screen">cgroup_device_acl = [
+ "/dev/null", "/dev/full", "/dev/zero",
+ "/dev/random", "/dev/urandom",
+ "/dev/ptmx", "/dev/kvm", "/dev/kqemu",
+ "/dev/rtc", "/dev/hpet", "/dev/net/tun",</pre></li><li class="step"><div class="para">
+ Restart <code class="filename">libvirtd</code>.
+ </div></li></ol></div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Since each of these steps significantly decreases the host's security protections against <span class="application"><strong>QEMU</strong></span> guest domains, this configuration should only be used if there is no alternative to using <code class="code"><interface type='ethernet'></code>.
+ </div></div></div></dd></dl></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ For more information on SELinux, refer to the <em class="citetitle">Fedora Security Guide</em>.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_Bridge_Device.html"><strong>Prev</strong>B.11. Unable to add bridge br0 port vnet0: No suc...</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="App_Migration_Address.html"><strong>Next</strong>B.13. Migration fails with Error: unable to resol...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Hypervisor_Connection_Fail.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Hypervisor_Connection_Fail.html
new file mode 100644
index 0000000..a092767
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Hypervisor_Connection_Fail.html
@@ -0,0 +1,26 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.2. The URI failed to connect to the hypervisor</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="next" href="Sect_Failed_to_connect_socket.html" title="B.2.2. Failed to connect socket ... : Permission denied" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 accessk
ey="p" href="apb.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="Sect_Failed_to_connect_socket.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_Hypervisor_Connection_Fail" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.2. The URI failed to connect to the hypervisor</h2></div></div></div><div class="para">
+ Several different errors can occur when connecting to the server (for example, when running <code class="command">virsh</code>).
+ </div><div class="section" id="Sect_Cannot_read_CA_certificate"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">B.2.1. Cannot read CA certificate</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ When running a command, the following error (or similar) appears:
+ </div><pre class="screen">$ virsh -c <em class="replaceable"><code>name_of_uri</code></em> list
+error: Cannot read CA certificate '/etc/pki/CA/cacert.pem': No such file or directory
+error: failed to connect to the hypervisor</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ The error message is misleading about the actual cause. This error can be caused by a variety of factors, such as an incorrectly specified URI, or a connection that is not configured.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Incorrectly specified URI</span></dt><dd><div class="para">
+ When specifying <em class="parameter"><code>qemu://system</code></em> or <em class="parameter"><code>qemu://session</code></em> as a connection URI, <code class="command">virsh</code> attempts to connect to hostnames <em class="parameter"><code>system</code></em> or <em class="parameter"><code>session</code></em> respectively. This is because <code class="command">virsh</code> recognizes the text after the second forward slash as the host.
+ </div><div class="para">
+ Use three forward slashes to connect to the local host. For example, specifying <em class="parameter"><code>qemu:///system</code></em> instructs <code class="command">virsh</code> connect to the <em class="parameter"><code>system</code></em> instance of <span class="application"><strong>libvirtd</strong></span> on the local host.
+ </div><div class="para">
+ When a hostname is specified, the <span class="application"><strong>QEMU</strong></span> transport defaults to <code class="systemitem">TLS</code>. This results in certificates.
+ </div></dd><dt class="varlistentry"><span class="term">Connection is not configured</span></dt><dd><div class="para">
+ The URI is correct (for example, <em class="parameter"><code>qemu[+tls]://server/system</code></em>) but the certificates are not set up properly on your machine. For information on configuring TLS, see <a href="http://wiki.libvirt.org/page/TLSSetup">Setting up <span class="application"><strong>libvirt</strong></span> for TLS</a> available from the <span class="application"><strong>libvirt</strong></span> website.
+ </div></dd></dl></div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apb.html"><strong>Prev</strong>Appendix B. Common libvirt errors and troubleshoo...</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_Failed_to_connect_socket.html"><strong>Next</strong>B.2.2. Failed to connect socket ... : Permission ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Macvtap.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Macvtap.html
new file mode 100644
index 0000000..146d289
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Macvtap.html
@@ -0,0 +1,44 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.9. Guest can reach outside network, but cannot reach host when using macvtap interface</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_PXE_Guest_Boot_Fail.html" title="B.8. PXE boot (or DHCP) on guest failed" /><link rel="next" href="App_DHCP_Response_Checksums.html" title="B.10. Could not add rule to fixup DHCP response checksums on network 'default'" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 c
lass="previous"><a accesskey="p" href="App_PXE_Guest_Boot_Fail.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_DHCP_Response_Checksums.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_Macvtap" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.9. Guest can reach outside network, but cannot reach host when using macvtap interface</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ A guest virtual machine can communicate with other guests, but cannot connect to the host machine after being configured to use a macvtap (also known as <em class="parameter"><code>type='direct'</code></em>) network interface.
+ </div></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ Even when not connecting to a Virtual Ethernet Port Aggregator (VEPA) or VN-Link capable switch, macvtap interfaces can be useful. Setting the mode of such an interface to <code class="option">bridge</code> allows the guest to be directly connected to the physical network in a very simple manner without the setup issues (or <span class="package">NetworkManager</span> incompatibility) that can accompany the use of a traditional host bridge device.
+ </div><div class="para">
+ However, when a guest virtual machine is configured to use a <em class="parameter"><code>type='direct'</code></em> network interface such as macvtap, despite having the ability to communicate with other guests and other external hosts on the network, the guest cannot communicate with its own host.
+ </div><div class="para">
+ This situation is actually not an error — it is the defined behavior of macvtap. Due to the way in which the host's physical Ethernet is attached to the macvtap bridge, traffic into that bridge from the guests that is forwarded to the physical interface cannot be bounced back up to the host's IP stack. Additionally, traffic from the host's IP stack that is sent to the physical interface cannot be bounced back up to the macvtap bridge for forwarding to the guests.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Use <span class="application"><strong>libvirt</strong></span> to create an isolated network, and create a second interface for each guest virtual machine that is connected to this network. The host and guests can then directly communicate over this isolated network, while also maintaining compatibility with <span class="package">NetworkManager</span>.
+ </div><div class="procedure"><h6>Procedure B.3. Creating an isolated network with <span class="application"><strong>libvirt</strong></span></h6><ol class="1"><li class="step"><div class="para">
+ Add and save the following XML in the <code class="filename">/tmp/isolated.xml</code> file. If the 192.168.254.0/24 network is already in use elsewhere on your network, you can choose a different network.
+ </div><pre class="programlisting"><network>
+ <name>isolated</name>
+ <ip address='192.168.254.1' netmask='255.255.255.0'>
+ <dhcp>
+ <range start='192.168.254.2' end='192.168.254.254' />
+ </dhcp>
+ </ip>
+</network></pre></li><li class="step"><div class="para">
+ Create the network with this command: <code class="command">virsh net-define /tmp/isolated.xml</code>
+ </div></li><li class="step"><div class="para">
+ Set the network to autostart with the <code class="command">virsh net-autostart isolated</code> command.
+ </div></li><li class="step"><div class="para">
+ Start the network with the <code class="command">virsh net-start isolated</code> command.
+ </div></li><li class="step"><div class="para">
+ Using <code class="command">virsh edit <em class="replaceable"><code>name_of_guest</code></em></code>, edit the configuration of each guest that uses macvtap for its network connection and add a new <em class="parameter"><code><interface></code></em> in the <em class="parameter"><code><devices></code></em> section similar to the following (note the <em class="parameter"><code><model type='virtio'/></code></em> line is optional to include):
+ </div><pre class="programlisting"><interface type='network'>
+ <source network='isolated'/>
+ <model type='virtio'/>
+</interface></pre></li><li class="step"><div class="para">
+ Shut down, then restart each of these guests.
+ </div></li></ol></div><div class="para">
+ The guests are now able to reach the host at the address 192.168.254.1, and the host will be able to reach the guests at the IP address they acquired from DHCP (alternatively, you can manually configure the IP addresses for the guests). Since this new network is isolated to only the host and guests, all other communication from the guests will use the macvtap interface.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_PXE_Guest_Boot_Fail.html"><strong>Prev</strong>B.8. PXE boot (or DHCP) on guest failed</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="App_DHCP_Response_Checksums.html"><strong>Next</strong>B.10. Could not add rule to fixup DHCP response c...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Migration_Address.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Migration_Address.html
new file mode 100644
index 0000000..f2be2ce
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Migration_Address.html
@@ -0,0 +1,34 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.13. Migration fails with Error: unable to resolve address</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_Generic_Ethernet.html" title="B.12. Guest is unable to start with error: warning: could not open /dev/net/tun" /><link rel="next" href="App_Migration_Disk_Image.html" title="B.14. Migration fails with Unable to allow access for disk path: No such file or directory" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="App_Generic_Ethernet.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_Migration_Disk_Image.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_Migration_Address" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.13. Migration fails with <code class="computeroutput">Error: unable to resolve address</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ <span class="application"><strong>QEMU</strong></span> guest migration fails and this error message appears:
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://192.168.122.12/system
+ error: Unable to resolve address <em class="replaceable"><code>name_of_host</code></em> service '49155': Name or service not known</pre><div class="para">
+ For example, if the destination hostname is "newyork", the error message will appear as:
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://192.168.122.12/system
+error: Unable to resolve address <em class="replaceable"><code>'newyork'</code></em> service '49155': Name or service not known</pre><div class="para">
+ However, this error looks strange as we did not use "newyork" hostname anywhere.
+ </div></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ During migration, <span class="application"><strong>libvirtd</strong></span> running on the destination host creates a URI from an address and port where it expects to receive migration data and sends it back to <span class="application"><strong>libvirtd</strong></span> running on the source host.
+ </div><div class="para">
+ In this case, the destination host (<code class="literal">192.168.122.12</code>) has its name set to <em class="replaceable"><code>'newyork'</code></em>. For some reason, <span class="application"><strong>libvirtd</strong></span> running on that host is unable to resolve the name to an IP address that could be sent back and still be useful. For this reason, it returned the <em class="replaceable"><code>'newyork'</code></em> hostname hoping the source <span class="application"><strong>libvirtd</strong></span> would be more successful with resolving the name. This can happen if DNS is not properly configured or <code class="filename">/etc/hosts</code> has the hostname associated with local loopback address (<code class="filename">127.0.0.1</code>).
+ </div><div class="para">
+ Note that the address used for migration data cannot be automatically determined from the address used for connecting to destination <span class="application"><strong>libvirtd</strong></span> (for example, from <code class="filename">qemu+tcp://192.168.122.12/system</code>). This is because to communicate with the destination <span class="application"><strong>libvirtd</strong></span>, the source <span class="application"><strong>libvirtd</strong></span> may need to use network infrastructure different from that which <span class="application"><strong>virsh</strong></span> (possibly running on a separate machine) requires.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ The best solution is to configure DNS correctly so that all hosts involved in migration are able to resolve all host names.
+ </div><div class="para">
+ If DNS cannot be configured to do this, a list of every host used for migration can be added manually to the <code class="filename">/etc/hosts</code> file on each of the hosts. However, it is difficult to keep such lists consistent in a dynamic environment.
+ </div><div class="para">
+ If the host names cannot be made resolvable by any means, <code class="command">virsh migrate</code> supports specifying the migration host:
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://192.168.122.12/system tcp://192.168.122.12</pre><div class="para">
+ Destination <span class="application"><strong>libvirtd</strong></span> will take the <code class="literal">tcp://192.168.122.12</code> URI and append an automatically generated port number. If this is not desirable (because of firewall configuration, for example), the port number can be specified in this command:
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://192.168.122.12/system tcp://192.168.122.12:12345</pre><div class="para">
+ Another option is to use tunnelled migration. Tunnelled migration does not create a separate connection for migration data, but instead tunnels the data through the connection used for communication with destination <span class="application"><strong>libvirtd</strong></span> (for example, <code class="filename">qemu+tcp://192.168.122.12/system</code>):
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://192.168.122.12/system --p2p --tunnelled</pre></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_Generic_Ethernet.html"><strong>Prev</strong>B.12. Guest is unable to start with error: warnin...</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="App_Migration_Disk_Image.html"><strong>Next</strong>B.14. Migration fails with Unable to allow access...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Migration_Disk_Image.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Migration_Disk_Image.html
new file mode 100644
index 0000000..13c62b3
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Migration_Disk_Image.html
@@ -0,0 +1,34 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.14. Migration fails with Unable to allow access for disk path: No such file or directory</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_Migration_Address.html" title="B.13. Migration fails with Error: unable to resolve address" /><link rel="next" href="App_No_Guest_Machines.html" title="B.15. No guest virtual machines are present when libvirtd is started" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="App_Migration_Address.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_No_Guest_Machines.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_Migration_Disk_Image" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.14. Migration fails with <code class="computeroutput">Unable to allow access for disk path: No such file or directory</code></h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ A guest virtual machine (or domain) cannot be migrated because <span class="application"><strong>libvirt</strong></span> cannot access the disk image(s):
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://<em class="replaceable"><code>name_of_host</code></em>/system
+error: Unable to allow access for disk path /var/lib/libvirt/images/qemu.img: No such file or directory</pre><div class="para">
+ For example, if the destination hostname is "newyork", the error message will appear as:
+ </div><pre class="screen"># virsh migrate qemu qemu+tcp://<em class="replaceable"><code>newyork</code></em>/system
+error: Unable to allow access for disk path /var/lib/libvirt/images/qemu.img: No such file or directory</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ By default, migration only transfers the in-memory state of a running guest (such as memory or CPU state). Although disk images are not transferred during migration, they need to remain accessible at the same path by both hosts.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Set up and mount shared storage at the same location on both hosts. The simplest way to do this is to use NFS:
+ </div><div class="procedure"><h6>Procedure B.5. Setting up shared storage</h6><ol class="1"><li class="step"><div class="para">
+ Set up an NFS server on a host serving as shared storage. The NFS server can be one of the hosts involved in the migration, as long as all hosts involved are accessing the shared storage through NFS.
+ </div><pre class="screen"># mkdir -p /exports/images
+# cat >>/etc/exports <<EOF
+/exports/images 192.168.122.0/24(rw,no_root_squash)
+EOF</pre></li><li class="step"><div class="para">
+ Mount the exported directory at a common location on all hosts running <span class="application"><strong>libvirt</strong></span>. For example, if the IP address of the NFS server is 192.168.122.1, mount the directory with the following commands:
+ </div><pre class="screen"># cat >>/etc/fstab <<EOF
+192.168.122.1:/exports/images /var/lib/libvirt/images nfs auto 0 0
+EOF
+# mount /var/lib/libvirt/images</pre></li></ol></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ It is not possible to export a local directory from one host using NFS and mount it at the same path on another host — the directory used for storing disk images must be mounted from shared storage on both hosts. If this is not configured correctly, the guest virtual machine may lose access to its disk images during migration, because the source host's <span class="application"><strong>libvirt</strong></span> daemon may change the owner, permissions, and SELinux labels on the disk images after it successfully migrates the guest to its destination.
+ </div><div class="para">
+ If <span class="application"><strong>libvirt</strong></span> detects that the disk images are mounted from a shared storage location, it will not make these changes.
+ </div></div></div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_Migration_Address.html"><strong>Prev</strong>B.13. Migration fails with Error: unable to resol...</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="App_No_Guest_Machines.html"><strong>Next</strong>B.15. No guest virtual machines are present when ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_No_Guest_Machines.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_No_Guest_Machines.html
new file mode 100644
index 0000000..d959bcc
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_No_Guest_Machines.html
@@ -0,0 +1,44 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.15. No guest virtual machines are present when libvirtd is started</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_Migration_Disk_Image.html" title="B.14. Migration fails with Unable to allow access for disk path: No such file or directory" /><link rel="next" href="App_TCP_Ports.html" title="B.16. Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="App_Migration_Disk_Image.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_TCP_Ports.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_No_Guest_Machines" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.15. No guest virtual machines are present when <span class="application"><strong>libvirtd</strong></span> is started</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The <span class="application"><strong>libvirt</strong></span> daemon is successfully started, but no guest virtual machines appear to be present.
+ </div><pre class="screen"># virsh list --all
+ Id Name State
+----------------------------------------------------
+#
+</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ There are various possible causes of this problem. Performing these tests will help to determine the cause of this situation:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Verify KVM kernel modules</span></dt><dd><div class="para">
+ Verify that KVM kernel modules are inserted in the kernel:
+ </div><pre class="screen"># lsmod | grep kvm
+kvm_intel 121346 0
+kvm 328927 1 kvm_intel</pre><div class="para">
+ If you are using an AMD machine, verify the <code class="systemitem">kvm_amd</code> kernel modules are inserted in the kernel instead, using the similar command <code class="command">lsmod | grep kvm_amd</code> in the root shell.
+ </div><div class="para">
+ If the modules are not present, insert them using the <code class="command">modprobe <em class="replaceable"><code><modulename></code></em></code> command.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Although it is uncommon, KVM virtualization support may be compiled into the kernel. In this case, modules are not needed.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">Verify virtualization extensions</span></dt><dd><div class="para">
+ Verify that virtualization extensions are supported and enabled on the host:
+ </div><pre class="screen"># egrep "(vmx|svm)" /proc/cpuinfo
+flags : fpu vme de pse tsc ... svm ... skinit wdt npt lbrv svm_lock nrip_save
+flags : fpu vme de pse tsc ... svm ... skinit wdt npt lbrv svm_lock nrip_save</pre><div class="para">
+ Enable virtualization extensions in your hardware's firmware configuration within the BIOS setup. Refer to your hardware documentation for further details on this.
+ </div></dd><dt class="varlistentry"><span class="term">Verify client URI configuration</span></dt><dd><div class="para">
+ Verify that the URI of the client is configured as desired:
+ </div><pre class="screen"># virsh uri
+vbox:///system</pre><div class="para">
+ For example, this message shows the URI is connected to the <span class="application"><strong>VirtualBox</strong></span> hypervisor, not <span class="application"><strong>QEMU</strong></span>, and reveals a configuration error for a URI that is otherwise set to connect to a <span class="application"><strong>QEMU</strong></span> hypervisor. If the URI was correctly connecting to <span class="application"><strong>QEMU</strong></span>, the same message would appear instead as:
+ </div><pre class="screen"># virsh uri
+qemu:///system</pre><div class="para">
+ This situation occurs when there are other hypervisors present, which <span class="application"><strong>libvirt</strong></span> may speak to by default.
+ </div></dd></dl></div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ After performing these tests, use the following command to view a list of guest virtual machines:
+ </div><pre class="screen"># virsh list --all</pre></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_Migration_Disk_Image.html"><strong>Prev</strong>B.14. Migration fails with Unable to allow 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="App_TCP_Ports.html"><strong>Next</strong>B.16. Unable to connect to server at 'host:16509'...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_PXE_Guest_Boot_Fail.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_PXE_Guest_Boot_Fail.html
new file mode 100644
index 0000000..4d0ed88
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_PXE_Guest_Boot_Fail.html
@@ -0,0 +1,71 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.8. PXE boot (or DHCP) on guest failed</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_Virt_Net_Not_Starting.html" title="B.7. Virtual network default has not been started" /><link rel="next" href="App_Macvtap.html" title="B.9. Guest can reach outside network, but cannot reach host when using macvtap interface" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="App_Virt_Net_Not_Starting.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_Macvtap.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_PXE_Guest_Boot_Fail" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.8. PXE boot (or DHCP) on guest failed</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ A guest virtual machine starts successfully, but is then either unable to acquire an IP address from DHCP or boot using the PXE protocol, or both. There are two common causes of this error: having a long forward delay time set for the bridge, and when the <span class="package">iptables</span> package and kernel do not support checksum mangling rules.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Long forward delay time on bridge</span></dt><dd><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This is the most common cause of this error. If the guest network interface is connecting to a bridge device that has STP (Spanning Tree Protocol) enabled, as well as a long forward delay set, the bridge will not forward network packets from the guest virtual machine onto the bridge until at least that number of forward delay seconds have elapsed since the guest connected to the bridge. This delay allows the bridge time to watch traffic from the interface and determine the MAC addresses behind it, and prevent forwarding loops in the network topology.
+ </div><div class="para">
+ If the forward delay is longer than the timeout of the guest's PXE or DHCP client, then the client's operation will fail, and the guest will either fail to boot (in the case of PXE) or fail to acquire an IP address (in the case of DHCP).
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ If this is the case, change the forward delay on the bridge to 0, disable STP on the bridge, or both.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ This solution applies only if the bridge is not used to connect multiple networks, but just to connect multiple endpoints to a single network (the most common use case for bridges used by <span class="application"><strong>libvirt</strong></span>).
+ </div></div></div><div class="para">
+ If the guest has interfaces connecting to a <span class="application"><strong>libvirt</strong></span>-managed virtual network, edit the definition for the network, and restart it. For example, edit the default network with the following command:
+ </div><pre class="screen"># virsh net-edit default</pre><div class="para">
+ Add the following attributes to the <code class="code"><bridge></code> element:
+ </div><pre class="programlisting"><<em class="replaceable"><code>name_of_bridge</code></em>='virbr0' <code class="code">delay='0' stp='on'</code>/></pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ <code class="code">delay='0'</code> and <code class="code">stp='on'</code> are the default settings for virtual networks, so this step is only necessary if the configuration has been modified from the default.
+ </div></div></div><div class="para">
+ If the guest interface is connected to a host bridge that was configured outside of <span class="application"><strong>libvirt</strong></span>, change the delay setting.
+ </div><div class="para">
+ Add or edit the following lines in the <code class="filename">/etc/sysconfig/network-scripts/ifcfg-<em class="replaceable"><code>name_of_bridge</code></em></code> file to turn STP on with a 0 second delay:
+ </div><pre class="programlisting">STP=on
+DELAY=0</pre><div class="para">
+ After changing the configuration file, restart the bridge device:
+ </div><pre class="programlisting">/sbin/ifdown <em class="replaceable"><code>name_of_bridge</code></em>
+/sbin/ifup <em class="replaceable"><code>name_of_bridge</code></em></pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If <em class="replaceable"><code>name_of_bridge</code></em> is not the root bridge in the network, that bridge's delay will eventually reset to the delay time configured for the root bridge. In this case, the only solution is to disable STP completely on <em class="replaceable"><code>name_of_bridge</code></em>.
+ </div></div></div></dd></dl></div></dd></dl></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">The <span class="package">iptables</span> package and kernel do not support checksum mangling rules</span></dt><dd><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This message is only a problem if all four of the following conditions are true:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The guest is using <span class="application"><strong>virtio</strong></span> network devices.
+ </div><div class="para">
+ If so, the configuration file will contain <code class="code">model type='virtio'</code>
+ </div></li><li class="listitem"><div class="para">
+ The host has the <code class="literal">vhost-net</code> module loaded.
+ </div><div class="para">
+ This is true if <code class="computeroutput"><code class="command">ls</code> <code class="filename">/dev/vhost-net</code></code> does not return an empty result.
+ </div></li><li class="listitem"><div class="para">
+ The guest is attempting to get an IP address from a DHCP server that is running directly on the host.
+ </div></li><li class="listitem"><div class="para">
+ The <span class="package">iptables</span> version on the host is older than 1.4.10.
+ </div><div class="para">
+ <span class="package">iptables</span> 1.4.10 was the first version to add the <code class="literal">libxt_CHECKSUM</code> extension. This is the case if the following message appears in the <span class="application"><strong>libvirtd</strong></span> logs:
+ </div><pre class="screen">warning: Could not add rule to fixup DHCP response checksums on network <em class="replaceable"><code>default</code></em>
+warning: May need to update iptables package and kernel to support CHECKSUM rule.</pre><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Unless all of the other three conditions in this list are also true, the above warning message can be disregarded, and is not an indicator of any other problems.
+ </div></div></div></li></ul></div><div class="para">
+ When these conditions occur, UDP packets sent from the host to the guest have uncomputed checksums. This makes the host's UDP packets seem invalid to the guest's network stack.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ To solve this problem, invalidate any of the four points above. The best solution is to update the host <span class="package">iptables</span> and kernel to <span class="package">iptables-1.4.10</span> or newer where possible. Otherwise, the most specific fix is to disable the <code class="literal">vhost-net</code> driver for this particular guest. To do this, edit the guest configuration with this command:
+ </div><pre class="screen">virsh edit <em class="replaceable"><code>name_of_guest</code></em></pre><div class="para">
+ Change or add a <code class="code"><driver></code> line to the <code class="code"><interface></code> section:
+ </div><pre class="programlisting"><interface type='network'>
+ <model type='virtio'/>
+ <driver name='qemu'/>
+ ...
+</interface></pre><div class="para">
+ Save the changes, shut down the guest, and then restart it.
+ </div><div class="para">
+ If this problem is still not resolved, the issue may be due to a conflict between <span class="application"><strong>firewalld</strong></span> and the default <span class="application"><strong>libvirt</strong></span> network.
+ </div><div class="para">
+ To fix this, stop <span class="application"><strong>firewalld</strong></span> with the <code class="command">service firewalld stop</code> command, then restart <span class="application"><strong>libvirt</strong></span> with the <code class="command">service libvirtd restart</code> command.
+ </div></dd></dl></div></dd></dl></div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_Virt_Net_Not_Starting.html"><strong>Prev</strong>B.7. Virtual network default has not been started</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="App_Macvtap.html"><strong>Next</strong>B.9. Guest can reach outside network, but cannot ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_TCP_Ports.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_TCP_Ports.html
new file mode 100644
index 0000000..e2ff703
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_TCP_Ports.html
@@ -0,0 +1,33 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.16. Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_No_Guest_Machines.html" title="B.15. No guest virtual machines are present when libvirtd is started" /><link rel="next" href="App_XML_Errors.html" title="B.17. Common XML errors" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="Ap
p_No_Guest_Machines.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_XML_Errors.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_TCP_Ports" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.16. Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ While <span class="application"><strong>libvirtd</strong></span> should listen on TCP ports for connections, the connections fail:
+ </div><pre class="screen"># virsh -c qemu+tcp://host/system
+error: unable to connect to server at 'host:16509': Connection refused
+error: failed to connect to the hypervisor</pre><div class="para">
+ The <span class="application"><strong>libvirt</strong></span> daemon is not listening on TCP ports even after changing configuration in <code class="filename">/etc/libvirt/libvirtd.conf</code>:
+ </div><pre class="screen"># grep listen_ /etc/libvirt/libvirtd.conf
+listen_tls = 1
+listen_tcp = 1
+listen_addr = "0.0.0.0"</pre><div class="para">
+ However, the TCP ports for <span class="application"><strong>libvirt</strong></span> are still not open after changing configuration:
+ </div><pre class="screen"># netstat -lntp | grep libvirtd
+#</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ The <span class="application"><strong>libvirt</strong></span> daemon was started without the <code class="option">--listen</code> option. Verify this by running this command:
+ </div><pre class="screen"># ps aux | grep libvirtd
+root 27314 0.0 0.0 1000920 18304 ? Sl Feb16 1:19 libvirtd --daemon</pre><div class="para">
+ The output does not contain the <code class="option">--listen</code> option.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Start the daemon with the <code class="option">--listen</code> option.
+ </div><div class="para">
+ To do this, modify the <code class="filename">/etc/sysconfig/libvirtd</code> file and uncomment the following line:
+ </div><pre class="screen">#LIBVIRTD_ARGS="--listen"</pre><div class="para">
+ Then restart the <span class="application"><strong>libvirtd</strong></span> service with this command:
+ </div><pre class="screen"># /etc/init.d/libvirtd restart</pre></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_No_Guest_Machines.html"><strong>Prev</strong>B.15. No guest virtual machines are present 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="App_XML_Errors.html"><strong>Next</strong>B.17. Common XML errors</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Virt_Net_Not_Starting.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Virt_Net_Not_Starting.html
new file mode 100644
index 0000000..edcb960
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_Virt_Net_Not_Starting.html
@@ -0,0 +1,40 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.7. Virtual network default has not been started</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_Domain_Not_Booting.html" title="B.6. Guest virtual machine booting stalls with error: No boot device" /><link rel="next" href="App_PXE_Guest_Boot_Fail.html" title="B.8. PXE boot (or DHCP) on guest failed" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="App_Domain_Not_Booting.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_PXE_Guest_Boot_Fail.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_Virt_Net_Not_Starting" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.7. Virtual network <em class="replaceable"><code>default</code></em> has not been started</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ Normally, the configuration for a virtual network named <em class="replaceable"><code>default</code></em> is installed as part of the <span class="package">libvirt</span> package, and is configured to autostart when <span class="application"><strong>libvirtd</strong></span> is started.
+ </div><div class="para">
+ If the <em class="replaceable"><code>default</code></em> network (or any other locally-created network) is unable to start, any virtual machine configured to use that network for its connectivity will also fail to start, resulting in this error message:
+ </div><pre class="screen">Virtual network <em class="replaceable"><code>default</code></em> has not been started</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ One of the most common reasons for a <span class="application"><strong>libvirt</strong></span> virtual network's failure to start is that the dnsmasq instance required to serve DHCP and DNS requests from clients on that network has failed to start.
+ </div><div class="para">
+ To determine if this is the cause, run <code class="command">virsh net-start default</code> from a root shell to start the <em class="replaceable"><code>default</code></em> virtual network.
+ </div><div class="para">
+ If this action does not successfully start the virtual network, open <code class="filename">/var/log/libvirt/libvirtd.log</code> to view the complete error log message.
+ </div><div class="para">
+ If a message similar to the following appears, the problem is likely a systemwide dnsmasq instance that is already listening on <span class="application"><strong>libvirt</strong></span>'s bridge, and is preventing <span class="application"><strong>libvirt</strong></span>'s own dnsmasq instance from doing so. The most important parts to note in the error message are <code class="literal">dnsmasq</code> and <code class="literal">exit status 2</code>:
+ </div><pre class="screen">Could not start virtual network <em class="replaceable"><code>default</code></em>: internal error
+Child process (/usr/sbin/dnsmasq --strict-order --bind-interfaces
+--pid-file=/var/run/libvirt/network/<em class="replaceable"><code>default</code></em>.pid --conf-file=
+--except-interface lo --listen-address 192.168.122.1
+--dhcp-range 192.168.122.2,192.168.122.254
+--dhcp-leasefile=/var/lib/libvirt/dnsmasq/<em class="replaceable"><code>default</code></em>.leases
+--dhcp-lease-max=253 --dhcp-no-override) status unexpected: exit status 2</pre></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ If the machine is not using dnsmasq to serve DHCP for the physical network, disable dnsmasq completely.
+ </div><div class="para">
+ If it is necessary to run dnsmasq to serve DHCP for the physical network, edit the <code class="filename">/etc/dnsmasq.conf</code> file. Add or uncomment the first line, as well as one of the two lines following that line. Do not add or uncomment all three lines:
+ </div><pre class="programlisting">bind-interfaces
+interface=<em class="replaceable"><code>name_of_physical_interface</code></em>
+listen-address=<em class="replaceable"><code>chosen_IP_address</code></em></pre><div class="para">
+ After making this change and saving the file, restart the systemwide dnsmasq service.
+ </div><div class="para">
+ Next, start the <em class="replaceable"><code>default</code></em> network with the <code class="command">virsh net-start default</code> command.
+ </div><div class="para">
+ Start the virtual machines.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_Domain_Not_Booting.html"><strong>Prev</strong>B.6. Guest virtual machine booting stalls with er...</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="App_PXE_Guest_Boot_Fail.html"><strong>Next</strong>B.8. PXE boot (or DHCP) on guest failed</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_XML_Errors.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_XML_Errors.html
new file mode 100644
index 0000000..4c76053
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/App_XML_Errors.html
@@ -0,0 +1,28 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.17. Common XML errors</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /><link rel="prev" href="App_TCP_Ports.html" title="B.16. Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor" /><link rel="next" href="apbs17s02.html" title="B.17.2. XML syntax errors" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="App_TCP_Ports.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apbs17s02.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="App_XML_Errors" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.17. Common XML errors</h2></div></div></div><div class="para">
+ The <span class="application"><strong>libvirt</strong></span> tool uses XML documents to store structured data. A variety of common errors occur with XML documents when they are passed to <span class="application"><strong>libvirt</strong></span> through the API. Several common XML errors — including misformatted XML, inappropriate values, and missing elements — are detailed below.
+ </div><div class="section" id="idm10882560"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm10882560">B.17.1. Editing domain definition</h3></div></div></div><div class="para">
+ Although it is not recommended, it is sometimes necessary to edit a guest virtual machine's (or a domain's) XML file manually. To access the guest's XML for editing, use the following command:
+ </div><pre class="screen"># virsh edit <em class="replaceable"><code>name_of_guest.xml</code></em></pre><div class="para">
+ This command opens the file in a text editor with the current definition of the guest virtual machine. After finishing the edits and saving the changes, the XML is reloaded and parsed by <span class="application"><strong>libvirt</strong></span>. If the XML is correct, the following message is displayed:
+ </div><pre class="screen"># virsh edit <em class="replaceable"><code>name_of_guest.xml</code></em>
+
+Domain <em class="replaceable"><code>name_of_guest.xml</code></em> XML configuration edited.</pre><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ When using the <code class="command">edit</code> command in <span class="application"><strong>virsh</strong></span> to edit an XML document, save all changes before exiting the editor.
+ </div></div></div><div class="para">
+ After saving the XML file, use the <code class="command">xmllint</code> command to validate that the XML is well-formed, or the <code class="command">virt-xml-validate</code> command to check for usage problems:
+ </div><pre class="screen"># xmllint --noout config.xml</pre><pre class="screen"># virt-xml-validate config.xml</pre><div class="para">
+ If no errors are returned, the XML description is well-formed and matches the <span class="application"><strong>libvirt</strong></span> schema. While the schema does not catch all constraints, fixing any reported errors will further troubleshooting.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">XML documents stored by <span class="application"><strong>libvirt</strong></span></span></dt><dd><div class="para">
+ These documents contain definitions of states and configurations for the guests. These documents are automatically generated and should not be edited manually. Errors in these documents contain the file name of the broken document. The file name is valid only on the host machine defined by the URI, which may refer to the machine the command was run on.
+ </div><div class="para">
+ Errors in files created by <span class="application"><strong>libvirt</strong></span> are rare. However, one possible source of these errors is a downgrade of <span class="application"><strong>libvirt</strong></span> — while newer versions of <span class="application"><strong>libvirt</strong></span> can always read XML generated by older versions, older versions of <span class="application"><strong>libvirt</strong></span> may be confused by XML elements added in a newer version.
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_TCP_Ports.html"><strong>Prev</strong>B.16. Unable to connect to server at 'host:16509'...</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="apbs17s02.html"><strong>Next</strong>B.17.2. XML syntax errors</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/common.css b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/common.css
new file mode 100644
index 0000000..d7dc3f2
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/common.css
@@ -0,0 +1,1528 @@
+* {
+ widows: 2 !important;
+ orphans: 2 !important;
+}
+
+body, h1, h2, h3, h4, h5, h6, pre, li, div {
+ line-height: 1.29em;
+}
+
+body {
+ background-color: white;
+ margin:0 auto;
+ font-family: "liberation sans", "Myriad ", "Bitstream Vera Sans", "Lucida Grande", "Luxi Sans", "Trebuchet MS", helvetica, verdana, arial, sans-serif;
+ font-size:12px;
+ max-width:55em;
+ color:black;
+}
+
+body.toc_embeded {
+ /*for web hosting system only*/
+ margin-left: 300px;
+}
+
+object.toc, iframe.toc {
+ /*for web hosting system only*/
+ border-style:none;
+ position:fixed;
+ width:290px;
+ height:99.99%;
+ top:0;
+ left:0;
+ z-index: 100;
+ border-style:none;
+ border-right:1px solid #999;
+}
+
+/* Hide web menu */
+
+body.notoc {
+ margin-left: 3em;
+}
+
+iframe.notoc {
+ border-style:none;
+ border: none;
+ padding: 0em;
+ position:fixed;
+ width: 21px;
+ height: 29px;
+ top: 0px;
+ left:0;
+ overflow: hidden;
+ margin: 0em;
+ margin-left: -3px;
+}
+/* End hide web menu */
+
+/* desktop styles */
+body.desktop {
+ margin-left: 26em;
+}
+
+body.desktop .book > .toc {
+ display:block;
+ width:24em;
+ height:99%;
+ position:fixed;
+ overflow:auto;
+ top:0px;
+ left:0px;
+ padding-left:1em;
+ background-color:#EEEEEE;
+}
+
+.toc {
+ line-height:1.35em;
+}
+
+.toc .glossary,
+.toc .chapter, .toc .appendix {
+ margin-top:1em;
+}
+
+.toc .part {
+ margin-top:1em;
+ display:block;
+}
+
+span.glossary,
+span.appendix {
+ display:block;
+ margin-top:0.5em;
+}
+
+div {
+ padding-top:0px;
+}
+
+div.section {
+ padding-top:1em;
+}
+
+p, div.para, div.formalpara {
+ padding-top:0px;
+ margin-top:0.3em;
+ padding-bottom:0px;
+ margin-bottom:1em;
+}
+
+/*Links*/
+a {
+ outline: none;
+}
+
+a:link {
+ text-decoration:none;
+ border-bottom: 1px dotted ;
+ color:#3366cc;
+}
+
+a:visited {
+ text-decoration:none;
+ border-bottom: 1px dotted ;
+ color:#003366;
+}
+
+div.longdesc-link {
+ float:right;
+ color:#999;
+}
+
+.toc a, .qandaset a {
+ font-weight:normal;
+ border:none;
+}
+
+.toc a:hover, .qandaset a:hover
+{
+ border-bottom: 1px dotted;
+}
+
+/*headings*/
+h1, h2, h3, h4, h5, h6 {
+ color: #336699;
+ margin-top: 0em;
+ margin-bottom: 0em;
+ background-color: transparent;
+ page-break-inside: avoid;
+ page-break-after: avoid;
+}
+
+h1 {
+ font-size:2.0em;
+}
+
+.titlepage h1.title {
+ font-size: 3.0em;
+ padding-top: 1em;
+ text-align:left;
+}
+
+.book > .titlepage h1.title {
+ text-align:center;
+}
+
+.article > .titlepage h1.title {
+ text-align:center;
+}
+
+.set .titlepage > div > div > h1.title {
+ text-align:center;
+}
+
+.producttitle {
+ margin-top: 0em;
+ margin-bottom: 0em;
+ font-size: 3.0em;
+ font-weight: bold;
+ background: #003d6e url(../images/h1-bg.png) top left repeat-x;
+ color: white;
+ text-align: center;
+ padding: 0.7em;
+}
+
+.titlepage .corpauthor {
+ margin-top: 1em;
+ text-align: center;
+}
+
+.section h1.title {
+ font-size: 1.6em;
+ padding: 0em;
+ color: #336699;
+ text-align: left;
+ background: white;
+}
+
+h2 {
+ font-size:1.6em;
+}
+
+
+h2.subtitle, h3.subtitle {
+ margin-top: 1em;
+ margin-bottom: 1em;
+ font-size: 1.4em;
+ text-align: center;
+}
+
+.preface > div > div > div > h2.title {
+ margin-top: 1em;
+ font-size: 2.0em;
+}
+
+.appendix h2 {
+ margin-top: 1em;
+ font-size: 2.0em;
+}
+
+
+
+h3 {
+ font-size:1.3em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+h4 {
+ font-size:1.1em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+
+h5 {
+ font-size:1em;
+}
+
+h6 {
+ font-size:1em;
+}
+
+h5.formalpara {
+ font-size:1em;
+ margin-top:2em;
+ margin-bottom:.8em;
+}
+
+.abstract h6 {
+ margin-top:1em;
+ margin-bottom:.5em;
+ font-size:2em;
+}
+
+/*element rules*/
+hr {
+ border-collapse: collapse;
+ border-style:none;
+ border-top: 1px dotted #ccc;
+ width:100%;
+ margin-top: 3em;
+}
+
+/* web site rules */
+ul.languages, .languages li {
+ display:inline;
+ padding:0em;
+}
+
+.languages li a {
+ padding:0em .5em;
+ text-decoration: none;
+}
+
+.languages li p, .languages li div.para {
+ display:inline;
+}
+
+.languages li a:link, .languages li a:visited {
+ color:#444;
+}
+
+.languages li a:hover, .languages li a:focus, .languages li a:active {
+ color:black;
+}
+
+ul.languages {
+ display:block;
+ background-color:#eee;
+ padding:.5em;
+}
+
+/*supporting stylesheets*/
+
+/*unique to the webpage only*/
+.books {
+ position:relative;
+}
+
+.versions li {
+ width:100%;
+ clear:both;
+ display:block;
+}
+
+a.version {
+ font-size:2em;
+ text-decoration:none;
+ width:100%;
+ display:block;
+ padding:1em 0em .2em 0em;
+ clear:both;
+}
+
+a.version:before {
+ content:"Version";
+ font-size:smaller;
+}
+
+a.version:visited, a.version:link {
+ color:#666;
+}
+
+a.version:focus, a.version:hover {
+ color:black;
+}
+
+.books {
+ display:block;
+ position:relative;
+ clear:both;
+ width:100%;
+}
+
+.books li {
+ display:block;
+ width:200px;
+ float:left;
+ position:relative;
+ clear: none ;
+}
+
+.books .html {
+ width:170px;
+ display:block;
+}
+
+.books .pdf {
+ position:absolute;
+ left:170px;
+ top:0px;
+ font-size:smaller;
+}
+
+.books .pdf:link, .books .pdf:visited {
+ color:#555;
+}
+
+.books .pdf:hover, .books .pdf:focus {
+ color:#000;
+}
+
+.books li a {
+ text-decoration:none;
+}
+
+.books li a:hover {
+ color:black;
+}
+
+/*products*/
+.products li {
+ display: block;
+ width:300px;
+ float:left;
+}
+
+.products li a {
+ width:300px;
+ padding:.5em 0em;
+}
+
+.products ul {
+ clear:both;
+}
+
+/*revision history*/
+.revhistory {
+ display:block;
+}
+
+.revhistory table {
+ background-color:transparent;
+ border-color:#fff;
+ padding:0em;
+ margin: 0;
+ border-collapse:collapse;
+ border-style:none;
+}
+
+.revhistory td {
+ text-align :left;
+ padding:0em;
+ border: none;
+ border-top: 1px solid #fff;
+ font-weight: bold;
+}
+
+.revhistory .simplelist td {
+ font-weight: normal;
+}
+
+.revhistory .simplelist {
+ margin-bottom: 1.5em;
+ margin-left: 1em;
+}
+
+.revhistory table th {
+ display: none;
+}
+
+
+/*credits*/
+.authorgroup div {
+ clear:both;
+ text-align: center;
+}
+
+h3.author {
+ margin: 0em;
+ padding: 0em;
+ padding-top: 1em;
+}
+
+.authorgroup h4 {
+ padding: 0em;
+ margin: 0em;
+ padding-top: 1em;
+ margin-top: 1em;
+}
+
+.author,
+.editor,
+.translator,
+.othercredit,
+.contrib {
+ display: block;
+}
+
+.revhistory .author {
+ display: inline;
+}
+
+.othercredit h3 {
+ padding-top: 1em;
+}
+
+
+.othercredit {
+ margin:0em;
+ padding:0em;
+}
+
+.releaseinfo {
+ clear: both;
+}
+
+.copyright {
+ margin-top: 1em;
+}
+
+/* qanda sets */
+.answer {
+ margin-bottom:1em;
+ border-bottom:1px dotted #ccc;
+}
+
+.qandaset .toc {
+ border-bottom:1px dotted #ccc;
+}
+
+.question {
+ font-weight:bold;
+}
+
+.answer .data, .question .data {
+ padding-left: 2.6em;
+}
+
+.answer label, .question label {
+ float:left;
+ font-weight:bold;
+}
+
+/* inline syntax highlighting */
+.perl_Alert {
+ color: #0000ff;
+}
+
+.perl_BaseN {
+ color: #007f00;
+}
+
+.perl_BString {
+ color: #5C3566;
+}
+
+.perl_Char {
+ color: #ff00ff;
+}
+
+.perl_Comment {
+ color: #FF00FF;
+}
+
+
+.perl_DataType {
+ color: #0000ff;
+}
+
+
+.perl_DecVal {
+ color: #00007f;
+}
+
+
+.perl_Error {
+ color: #ff0000;
+}
+
+
+.perl_Float {
+ color: #00007f;
+}
+
+
+.perl_Function {
+ color: #007f00;
+}
+
+
+.perl_IString {
+ color: #5C3566;
+}
+
+
+.perl_Keyword {
+ color: #002F5D;
+}
+
+
+.perl_Operator {
+ color: #ffa500;
+}
+
+
+.perl_Others {
+ color: #b03060;
+}
+
+
+.perl_RegionMarker {
+ color: #96b9ff;
+}
+
+
+.perl_Reserved {
+ color: #9b30ff;
+}
+
+
+.perl_String {
+ color: #5C3566;
+}
+
+
+.perl_Variable {
+ color: #0000ff;
+}
+
+
+.perl_Warning {
+ color: #0000ff;
+}
+
+/*Lists*/
+ul {
+ padding-left:1.6em;
+ list-style-image:url(../images/dot.png);
+ list-style-type: circle;
+}
+
+ul ul {
+ list-style-image:url(../images/dot2.png);
+ list-style-type: circle;
+}
+
+ol {
+ list-style-image:none;
+ list-style-type: decimal;
+}
+
+ol ol {
+ list-style-type: lower-alpha;
+}
+
+ol.arabic {
+ list-style-type: decimal;
+}
+
+ol.loweralpha {
+ list-style-type: lower-alpha;
+}
+
+ol.lowerroman {
+ list-style-type: lower-roman;
+}
+
+ol.upperalpha {
+ list-style-type: upper-alpha;
+}
+
+ol.upperroman {
+ list-style-type: upper-roman;
+}
+
+dt {
+ font-weight:bold;
+ margin-bottom:0em;
+ padding-bottom:0em;
+}
+
+dd {
+ margin:0em;
+ margin-left:2em;
+ padding-top:0em;
+ padding-bottom: 1em;
+}
+
+li {
+ padding-top:0px;
+ margin-top:0em;
+ padding-bottom:0px;
+ margin-bottom:0.4em;
+}
+
+li p, li div.para {
+ padding-top:0px;
+ margin-top:0em;
+ padding-bottom:0px;
+ margin-bottom:0.3em;
+}
+
+/*images*/
+img {
+ display:block;
+ margin: 2em 0;
+}
+
+.inlinemediaobject, .inlinemediaobject img {
+ display:inline;
+ margin:0em;
+}
+
+.figure img {
+ display:block;
+ margin:0;
+ page-break-inside: avoid;
+}
+
+.figure .title {
+ margin:0em;
+ margin-bottom:2em;
+ padding:0px;
+}
+
+/*document modes*/
+.confidential {
+ background-color:#900;
+ color:White;
+ padding:.5em .5em;
+ text-transform:uppercase;
+ text-align:center;
+}
+
+.longdesc-link {
+ display:none;
+}
+
+.longdesc {
+ display:none;
+}
+
+.prompt {
+ padding:0em .3em;
+}
+
+/*user interface styles*/
+.screen .replaceable {
+}
+
+.guibutton, .guilabel {
+ font-family: "liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight: bold;
+ white-space: nowrap;
+}
+
+.example {
+ background-color: #ffffff;
+ border-left: 3px solid #aaaaaa;
+ padding-top: 1em;
+ padding-bottom: 0.1em;
+}
+
+.example h6 {
+ padding-left: 10px;
+}
+
+.example-contents {
+ padding-left: 10px;
+ background-color: #ffffff;
+}
+
+.example-contents .para {
+/* padding: 10px;*/
+}
+
+/*terminal/console text*/
+.computeroutput,
+.option {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight:bold;
+}
+
+.replaceable {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-style: italic;
+}
+
+.command, .filename, .keycap, .classname, .literal {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight:bold;
+}
+
+/* no bold in toc */
+.toc * {
+ font-weight: inherit;
+}
+
+pre {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ display:block;
+ background-color: #f5f5f5;
+ color: #000000;
+ border: 1px solid #aaaaaa;
+ margin-bottom: 0.3em;
+ padding:.5em 1em;
+ white-space: pre-wrap; /* css-3 */
+ white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
+ white-space: -pre-wrap; /* Opera 4-6 */
+ white-space: -o-pre-wrap; /* Opera 7 */
+ word-wrap: break-word; /* Internet Explorer 5.5+ */
+ font-size: 0.9em;
+}
+
+pre .replaceable,
+pre .keycap {
+}
+
+code {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+/* white-space: nowrap;*/
+ white-space: pre-wrap;
+ word-wrap: break-word;
+ font-weight:bold;
+}
+
+.parameter code {
+ display: inline;
+ white-space: pre-wrap; /* css-3 */
+ white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
+ white-space: -pre-wrap; /* Opera 4-6 */
+ white-space: -o-pre-wrap; /* Opera 7 */
+ word-wrap: break-word; /* Internet Explorer 5.5+ */
+}
+
+/*Notifications*/
+div.warning:before {
+ content:url(../images/warning.png);
+ padding-left: 5px;
+}
+
+div.note:before {
+ content:url(../images/note.png);
+ padding-left: 5px;
+}
+
+div.important:before {
+ content:url(../images/important.png);
+ padding-left: 5px;
+}
+
+div.warning, div.note, div.important {
+ color: black;
+ margin: 0em;
+ padding: 0em;
+ background: none;
+ background-color: white;
+ margin-bottom: 1em;
+ border-bottom: 1px solid #aaaaaa;
+ page-break-inside: avoid;
+}
+
+div.warning h2, div.note h2,div.important h2 {
+ margin: 0em;
+ padding: 0em;
+ color: #eeeeec;
+ padding-top: 0px;
+ padding-bottom: 0px;
+ height: 1.4em;
+ line-height: 1.4em;
+ font-size: 1.4em;
+ display:inline;
+}
+
+div.admonition_header {
+ clear: both;
+ margin: 0em;
+ padding: 0em;
+ margin-top: -3.3em;
+ padding-left: 58px;
+ line-height: 1.0em;
+ font-size: 1.0em;
+}
+
+div.warning div.admonition_header {
+ background: url(../images/red.png) top left repeat-x;
+ background-color: #590000;
+}
+
+div.note div.admonition_header {
+ background: url(../images/green.png) top right repeat-x;
+ background-color: #597800;
+}
+
+div.important div.admonition_header {
+ background: url(../images/yellow.png) top right repeat-x;
+ background-color: #a6710f;
+}
+
+div.warning p, div.warning div.para,
+div.note p, div.note div.para,
+div.important p, div.important div.para {
+ padding: 0em;
+ margin: 0em;
+}
+
+div.admonition {
+ border: none;
+ border-left: 1px solid #aaaaaa;
+ border-right: 1px solid #aaaaaa;
+ padding:0em;
+ margin:0em;
+ padding-top: 1.5em;
+ padding-bottom: 1em;
+ padding-left: 2em;
+ padding-right: 1em;
+ background-color: #eeeeec;
+ -moz-border-radius: 0px;
+ -webkit-border-radius: 0px;
+ border-radius: 0px;
+}
+
+/*Page Title*/
+#title {
+ display:block;
+ height:45px;
+ padding-bottom:1em;
+ margin:0em;
+}
+
+#title a.left{
+ display:inline;
+ border:none;
+}
+
+#title a.left img{
+ border:none;
+ float:left;
+ margin:0em;
+ margin-top:.7em;
+}
+
+#title a.right {
+ padding-bottom:1em;
+}
+
+#title a.right img {
+ border:none;
+ float:right;
+ margin:0em;
+ margin-top:.7em;
+}
+
+/*Table*/
+div.table {
+ page-break-inside: avoid;
+}
+
+table {
+ border:1px solid #6c614b;
+ width:100%;
+ border-collapse:collapse;
+}
+
+table.simplelist, .calloutlist table {
+ border-style: none;
+}
+
+table th {
+ text-align:left;
+ background-color:#6699cc;
+ padding:.3em .5em;
+ color:white;
+}
+
+table td {
+ padding:.15em .5em;
+}
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+table th p:first-child, table td p:first-child, table li p:first-child,
+table th div.para:first-child, table td div.para:first-child, table li div.para:first-child {
+ margin-top:0em;
+ padding-top:0em;
+ display:inline;
+}
+
+th, td {
+ border-style:none;
+ vertical-align: top;
+ border: 1px solid #000;
+}
+
+.simplelist th, .simplelist td {
+ border: none;
+}
+
+table table td {
+ border-bottom:1px dotted #aaa;
+ background-color:white;
+ padding:.6em 0em;
+}
+
+table table {
+ border:1px solid white;
+}
+
+td.remarkval {
+ color:#444;
+}
+
+td.fieldval {
+ font-weight:bold;
+}
+
+.lbname, .lbtype, .lbdescr, .lbdriver, .lbhost {
+ color:white;
+ font-weight:bold;
+ background-color:#999;
+ width:120px;
+}
+
+td.remarkval {
+ width:230px;
+}
+
+td.tname {
+ font-weight:bold;
+}
+
+th.dbfield {
+ width:120px;
+}
+
+th.dbtype {
+ width:70px;
+}
+
+th.dbdefault {
+ width:70px;
+}
+
+th.dbnul {
+ width:70px;
+}
+
+th.dbkey {
+ width:70px;
+}
+
+span.book {
+ margin-top:4em;
+ display:block;
+ font-size:11pt;
+}
+
+span.book a{
+ font-weight:bold;
+}
+span.chapter {
+ display:block;
+ margin-top:0.5em;
+}
+
+table.simplelist td, .calloutlist table td {
+ border-style: none;
+}
+
+/*Breadcrumbs*/
+#breadcrumbs ul li.first:before {
+ content:" ";
+}
+
+#breadcrumbs {
+ color:#900;
+ padding:3px;
+ margin-bottom:25px;
+}
+
+#breadcrumbs ul {
+ margin-left:0;
+ padding-left:0;
+ display:inline;
+ border:none;
+}
+
+#breadcrumbs ul li {
+ margin-left:0;
+ padding-left:2px;
+ border:none;
+ list-style:none;
+ display:inline;
+}
+
+#breadcrumbs ul li:before {
+ content:"\0020 \0020 \0020 \00BB \0020";
+ color:#333;
+}
+
+/*index*/
+.glossary h3,
+.index h3 {
+ font-size: 2em;
+ color:#aaa;
+ margin:0em;
+}
+
+.indexdiv {
+ margin-bottom:1em;
+}
+
+.glossary dt,
+.index dt {
+ color:#444;
+ padding-top:.5em;
+}
+
+.glossary dl dl dt,
+.index dl dl dt {
+ color:#777;
+ font-weight:normal;
+ padding-top:0em;
+}
+
+.index dl dl dt:before {
+ content:"- ";
+ color:#ccc;
+}
+
+/*changes*/
+.footnote {
+ font-size: .7em;
+ margin:0em;
+ color:#222;
+}
+
+table .footnote {
+}
+
+sup {
+ color:#999;
+ margin:0em;
+ padding:0em;
+ line-height: .4em;
+ font-size: 1em;
+ padding-left:0em;
+}
+
+.footnote {
+ position:relative;
+}
+
+.footnote sup {
+ color:#e3dcc0;
+ position:absolute;
+ left: .4em;
+}
+
+.footnote sup a:link,
+.footnote sup a:visited {
+ color:#92917d;
+ text-decoration:none;
+}
+
+.footnote:hover sup a {
+ text-decoration:none;
+}
+
+.footnote p,.footnote div.para {
+ padding-left:2em;
+}
+
+.footnote a:link,
+.footnote a:visited {
+ color:#00537c;
+}
+
+.footnote a:hover {
+}
+
+/**/
+div.chapter {
+ margin-top:3em;
+ page-break-inside: avoid;
+}
+
+div.preface {
+ page-break-inside: avoid;
+}
+
+div.section {
+ margin-top:1em;
+ page-break-inside: auto;
+}
+
+div.note .replaceable,
+div.important .replaceable,
+div.warning .replaceable,
+div.note .keycap,
+div.important .keycap,
+div.warning .keycap
+{
+}
+
+ul li p:last-child, ul li div.para:last-child {
+ margin-bottom:0em;
+ padding-bottom:0em;
+}
+
+/*document navigation*/
+.docnav a, .docnav strong {
+ border:none;
+ text-decoration:none;
+ font-weight:normal;
+}
+
+.docnav {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+ position:relative;
+ width:100%;
+ padding-bottom:2em;
+ padding-top:1em;
+ border-top:1px dotted #ccc;
+}
+
+.docnav li {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+ display:inline;
+ font-size:.8em;
+}
+
+.docnav li:before {
+ content:" ";
+}
+
+.docnav li.previous, .docnav li.next {
+ position:absolute;
+ top:1em;
+}
+
+.docnav li.up, .docnav li.home {
+ margin:0em 1.5em;
+}
+
+.docnav li.previous {
+ left:0px;
+ text-align:left;
+}
+
+.docnav li.next {
+ right:0px;
+ text-align:right;
+}
+
+.docnav li.previous strong, .docnav li.next strong {
+ height:22px;
+ display:block;
+}
+
+.docnav {
+ margin:0 auto;
+ text-align:center;
+}
+
+.docnav li.next a strong {
+ background: url(../images/stock-go-forward.png) top right no-repeat;
+ padding-top:3px;
+ padding-bottom:4px;
+ padding-right:28px;
+ font-size:1.2em;
+}
+
+.docnav li.previous a strong {
+ background: url(../images/stock-go-back.png) top left no-repeat;
+ padding-top:3px;
+ padding-bottom:4px;
+ padding-left:28px;
+ padding-right:0.5em;
+ font-size:1.2em;
+}
+
+.docnav li.home a strong {
+ background: url(../images/stock-home.png) top left no-repeat;
+ padding:5px;
+ padding-left:28px;
+ font-size:1.2em;
+}
+
+.docnav li.up a strong {
+ background: url(../images/stock-go-up.png) top left no-repeat;
+ padding:5px;
+ padding-left:28px;
+ font-size:1.2em;
+}
+
+.docnav a:link, .docnav a:visited {
+ color:#666;
+}
+
+.docnav a:hover, .docnav a:focus, .docnav a:active {
+ color:black;
+}
+
+.docnav a {
+ max-width: 10em;
+ overflow:hidden;
+}
+
+.docnav a:link strong {
+ text-decoration:none;
+}
+
+.docnav {
+ margin:0 auto;
+ text-align:center;
+}
+
+ul.docnav {
+ margin-bottom: 1em;
+}
+/* Reports */
+.reports ul {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+}
+
+.reports li{
+ margin:0em;
+ padding:0em;
+}
+
+.reports li.odd {
+ background-color: #eeeeee;
+ margin:0em;
+ padding:0em;
+}
+
+.reports dl {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ float:right;
+ margin-right: 17em;
+ margin-top:-1.3em;
+}
+
+.reports dt {
+ display:inline;
+ margin:0em;
+ padding:0em;
+}
+
+.reports dd {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ padding-right:.5em;
+}
+
+.reports h2, .reports h3{
+ display:inline;
+ padding-right:.5em;
+ font-size:10pt;
+ font-weight:normal;
+}
+
+.reports div.progress {
+ display:inline;
+ float:right;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ margin:0em;
+ margin-top:-1.3em;
+ padding:0em;
+ border:none;
+}
+
+/*uniform*/
+body.results, body.reports {
+ max-width:57em ;
+ padding:0em;
+}
+
+/*Progress Bar*/
+div.progress {
+ display:block;
+ float:left;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ height:1em;
+}
+
+div.progress span {
+ height:1em;
+ float:left;
+}
+
+div.progress span.translated {
+ background:#6c3 url(../images/shine.png) top left repeat-x;
+}
+
+div.progress span.fuzzy {
+ background:#ff9f00 url(../images/shine.png) top left repeat-x;
+}
+
+
+/*Results*/
+
+.results ul {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+}
+
+.results li{
+ margin:0em;
+ padding:0em;
+}
+
+.results li.odd {
+ background-color: #eeeeee;
+ margin:0em;
+ padding:0em;
+}
+
+.results dl {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ float:right;
+ margin-right: 17em;
+ margin-top:-1.3em;
+}
+
+.results dt {
+ display:inline;
+ margin:0em;
+ padding:0em;
+}
+
+.results dd {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ padding-right:.5em;
+}
+
+.results h2, .results h3 {
+ display:inline;
+ padding-right:.5em;
+ font-size:10pt;
+ font-weight:normal;
+}
+
+.results div.progress {
+ display:inline;
+ float:right;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ margin:0em;
+ margin-top:-1.3em;
+ padding:0em;
+ border:none;
+}
+
+/* Dirty EVIL Mozilla hack for round corners */
+pre {
+ -moz-border-radius:11px;
+ -webkit-border-radius:11px;
+ border-radius: 11px;
+ page-break-inside: avoid;
+}
+
+.example {
+ -moz-border-radius:0px;
+ -webkit-border-radius:0px;
+ border-radius: 0px;
+ page-break-inside: avoid;
+}
+
+.package, .citetitle {
+ font-style: italic;
+}
+
+.titlepage .edition {
+ color: #336699;
+ background-color: transparent;
+ margin-top: 1em;
+ margin-bottom: 1em;
+ font-size: 1.4em;
+ font-weight: bold;
+ text-align: center;
+}
+
+span.remark {
+ background-color: #ff00ff;
+}
+
+.draft {
+ background-image: url(../images/watermark-draft.png);
+ background-repeat: repeat-y;
+ background-position: center;
+}
+
+.foreignphrase {
+ font-style: inherit;
+}
+
+dt {
+ clear:both;
+}
+
+dt img {
+ border-style: none;
+ max-width: 112px;
+}
+
+dt object {
+ max-width: 112px;
+}
+
+dt .inlinemediaobject, dt object {
+ display: inline;
+ float: left;
+ margin-bottom: 1em;
+ padding-right: 1em;
+ width: 112px;
+}
+
+dl:after {
+ display: block;
+ clear: both;
+ content: "";
+}
+
+.toc dd {
+ padding-bottom: 0em;
+ margin-bottom: 1em;
+ padding-left: 1.3em;
+ margin-left: 0em;
+}
+
+div.toc > dl > dt {
+ padding-bottom: 0em;
+ margin-bottom: 0em;
+ margin-top: 1em;
+}
+
+
+.strikethrough {
+ text-decoration: line-through;
+}
+
+.underline {
+ text-decoration: underline;
+}
+
+.calloutlist img, .callout {
+ padding: 0em;
+ margin: 0em;
+ width: 12pt;
+ display: inline;
+ vertical-align: middle;
+}
+
+.stepalternatives {
+ list-style-image: none;
+ list-style-type: none;
+}
+
+
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/default.css b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/default.css
new file mode 100644
index 0000000..bf38ebb
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/default.css
@@ -0,0 +1,3 @@
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/lang.css b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/lang.css
new file mode 100644
index 0000000..81c3115
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/lang.css
@@ -0,0 +1,2 @@
+/* place holder */
+
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/menu.css b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/menu.css
new file mode 100644
index 0000000..f574cc5
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/menu.css
@@ -0,0 +1,48 @@
+a:link {
+ color:#0066cc;
+}
+
+a:visited {
+ color:#6699cc;
+}
+
+h1,h2,h3,h4,h5,h6 {
+ color:#a70000;
+}
+
+div.producttitle {
+ color:#a70000;
+}
+
+.section h1.title {
+ color:#a70000;
+}
+
+table {
+ border:1px solid #aaa;
+}
+
+table th {
+ background-color:#900;
+}
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+.revhistory table th {
+ color:#a70000;
+}
+
+.titlepage .edition {
+ color: #a70000;
+}
+
+span.remark{
+ background-color: #ffff00;
+}
+
+.home{
+ color: #a70000;
+}
+
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/overrides.css b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/overrides.css
new file mode 100644
index 0000000..db64f48
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/overrides.css
@@ -0,0 +1,55 @@
+a:link {
+ color:#0066cc;
+}
+
+a:hover, a:active {
+ color:#003366;
+}
+
+a:visited {
+ color:#6699cc;
+}
+
+
+h1 {
+ color:#3c6eb4
+}
+
+.producttitle {
+ background: #3c6eb4 url(../images/h1-bg.png) top left repeat;
+}
+
+.section h1.title {
+ color:#3c6eb4;
+}
+
+
+h2,h3,h4,h5,h6 {
+ color:#3c6eb4;
+}
+
+table {
+ border:1px solid #3c6eb4;
+}
+
+table th {
+ background-color:#3c6eb4;
+}
+
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+.term{
+ color:#3c6eb4
+}
+
+.revhistory table th {
+ color:#3c6eb4;
+}
+
+.edition {
+ color: #3c6eb4;
+}
+
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/pdf.css b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/pdf.css
new file mode 100644
index 0000000..cbeab47
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/pdf.css
@@ -0,0 +1,138 @@
+
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
+
+/* Cover Page styles */
+
+html {
+ height: 260mm;
+}
+
+body.cover {
+ height: 100%;
+ background-color: white;
+/* margin-left: 10em;
+ margin-right: 10em;
+*/ padding: 0px;
+ font-family: "overpass", sans-serif;
+ font-weight:300;
+}
+
+body.cover > div {
+ height: 100%;
+}
+
+body.cover * {
+ text-align: left;
+ box-sizing: border-box;
+ -moz-box-sizing: border-box;
+ -webkit-box-sizing: border-box;
+}
+
+body.cover div.logo {
+ height: 30%;
+ background-position: 50% 0%;
+ margin-top: 15mm;
+ background-image: url(../images/title_logo.svg);
+ background-repeat: no-repeat;
+}
+
+
+body.cover div.leader {
+ display: inline-block;
+ font-size: 40px;
+ font-weight: 600;
+ margin-top: 2em;
+}
+
+body.cover div.product {
+ display: inline;
+}
+
+
+body.cover div.edition {
+ display: inline;
+}
+
+body.cover div.docname {
+ font-size: 40px;
+ font-weight: 600;
+ height: 10%;
+}
+
+body.cover div.subtitle {
+ height: 20%;
+ font-weight:300;
+ font-size: 20px;
+ color: black;
+ border-top: .1em solid black;
+ padding-top: 40px;
+}
+body.cover div.authors {
+}
+
+body.cover div.author {
+ float: left;
+ min-width: 33%;
+ font-weight: 300;
+ font-size: 20px;
+}
+
+div.draft {
+ background-image: url(../images/watermark-draft.png);
+ background-repeat: repeat-y;
+ background-position: center;
+}
+
+body.titlepages {
+ text-align: left;
+}
+
+body.titlepages > div {
+ height: 100%;
+}
+body.titlepages .legalnotice {
+ page-break-before: always;
+}
+
+body.titlepages .title {
+ font-size: 20px;
+ color: black;
+ font-weight: normal;
+ margin-bottom: 0.1em;
+}
+
+body.titlepages .subtitle {
+ color: black;
+ font-weight: normal;
+ text-align: left;
+ font-size: 12px;
+ margin-top: 0.1em;
+ margin-bottom: 2em;
+}
+
+body.titlepages .contributor {
+ margin-bottom: 1em;
+ font-size: 12px;
+}
+
+body.titlepages .abstract {
+ page-break-before: avoid !important;
+ font-size: 14px;
+}
+
+body.titlepages h1 {
+ color: black;
+ font-size: 14px;
+ font-weight: normal;
+}
+
+body.titlepages .editors h1,
+body.titlepages .othercredit h1,
+body.titlepages .legalnotice h1,
+body.titlepages .keywords h1,
+body.titlepages .abstract h1 {
+ font-weight: bold;
+}
+
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/print.css b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/print.css
new file mode 100644
index 0000000..773d8ae
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/css/print.css
@@ -0,0 +1,16 @@
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
+
+#tocframe {
+ display: none;
+}
+
+body.toc_embeded {
+ margin-left: 30px;
+}
+
+.producttitle {
+ color: #336699;
+}
+
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/1.png
new file mode 100644
index 0000000..1098dab
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/1.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/1.svg
new file mode 100644
index 0000000..3736523
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/1.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 17.993,22.013004 L 17.993,10.113004 L 15.239,10.113004 C 14.899001,11.218003 14.286999,11.643004 12.757,11.728004 L 12.757,13.819004 L 14.763,13.819004 L 14.763,22.013004 L 17.993,22.013004"
+ id="text2207"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/10.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/10.png
new file mode 100644
index 0000000..ef058e3
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/10.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/10.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/10.svg
new file mode 100644
index 0000000..84ee18f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/10.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 12.252562,22 L 12.252562,10.1 L 9.4985624,10.1 C 9.1585628,11.204999 8.5465609,11.63 7.0165624,11.715 L 7.0165624,13.806 L 9.0225624,13.806 L 9.0225624,22 L 12.252562,22 M 24.983438,16.033 C 24.983438,12.072004 22.705435,9.913 19.611438,9.913 C 16.517441,9.913 14.205438,12.106004 14.205438,16.067 C 14.205438,20.027996 16.483441,22.187 19.577438,22.187 C 22.671435,22.187 24.983438,19.993996 24.983438,16.033 M 21.600438,16.067 C 21.600438,18.242998 20.886437,19.348 19.611438,19.348 C 18.336439,19.348 17.588438,18.208998 17.588438,16.033 C 17.588438,13.857002 18.302439,12.752 19.577438,12.752 C 20.852437,12.752 21.600438,13.891002 21.600438,16.067"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/11.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/11.png
new file mode 100644
index 0000000..fa20ec4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/11.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/11.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/11.svg
new file mode 100644
index 0000000..47f0c80
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/11.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 14.623052,22 L 14.623052,10.1 L 11.869052,10.1 C 11.529053,11.204999 10.917051,11.63 9.3870527,11.715 L 9.3870527,13.806 L 11.393052,13.806 L 11.393052,22 L 14.623052,22 M 21.794928,22 L 21.794928,10.1 L 19.040928,10.1 C 18.700928,11.204999 18.088926,11.63 16.558928,11.715 L 16.558928,13.806 L 18.564928,13.806 L 18.564928,22 L 21.794928,22"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/12.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/12.png
new file mode 100644
index 0000000..84c132a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/12.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/12.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/12.svg
new file mode 100644
index 0000000..94ddaac
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/12.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 12.677562,22 L 12.677562,10.1 L 9.9235624,10.1 C 9.5835628,11.204999 8.9715609,11.63 7.4415624,11.715 L 7.4415624,13.806 L 9.4475624,13.806 L 9.4475624,22 L 12.677562,22 M 24.558438,22 L 24.558438,19.314 L 18.353438,19.314 C 18.608438,18.600001 19.27144,17.936999 21.651438,16.832 C 23.929436,15.778001 24.473438,14.825998 24.473438,13.262 C 24.473438,11.103002 22.926435,9.913 19.968438,9.913 C 17.92844,9.913 16.381436,10.491001 14.868438,11.46 L 16.381438,13.891 C 17.571437,13.092001 18.727439,12.684 19.917438,12.684 C 20.869437,12.684 21.243438,12.973001 21.243438,13.5 C 21.243438,13.976 21.056437,14.163001 19.798438,14.724 C 16.823441,16.049999 14.936438,17.988004 14.834438,22 L 24.558438,22"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/13.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/13.png
new file mode 100644
index 0000000..f41ec8f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/13.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/13.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/13.svg
new file mode 100644
index 0000000..040dd6c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/13.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 12.550062,22 L 12.550062,10.1 L 9.7960624,10.1 C 9.4560628,11.204999 8.8440609,11.63 7.3140624,11.715 L 7.3140624,13.806 L 9.3200624,13.806 L 9.3200624,22 L 12.550062,22 M 24.685938,18.226 C 24.685938,16.713002 23.716937,15.914 22.611938,15.659 C 23.427937,15.268 24.192938,14.638999 24.192938,13.33 C 24.192938,10.814003 22.288935,9.913 19.432938,9.913 C 17.35894,9.913 15.930937,10.610001 14.825938,11.46 L 16.389938,13.602 C 17.307937,12.939001 18.191939,12.582 19.347938,12.582 C 20.520937,12.582 20.996938,12.922001 20.996938,13.551 C 20.996938,14.332999 20.656937,14.554 19.619938,14.554 L 18.089938,14.554 L 18.089938,17.121 L 19.806938,17.121 C 21.013937,17.121 21.489938,17.427001 21.489938,18.26 C 21.489938,19.075999 20.911937,19.467 19.534938,19.467 C 18.225939,19.467 17.120937,18.973999 16.151938,18.226 L 14.451938,20.368 C 15.726937,21.489999 17.44394,22.187 19.466938,22.187 C 22.696935,22.187 24.685938,20.979997 24.685938,18.226"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/14.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/14.png
new file mode 100644
index 0000000..c491206
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/14.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/14.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/14.svg
new file mode 100644
index 0000000..7f4fcfd
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/14.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 12.040062,22 L 12.040062,10.1 L 9.2860624,10.1 C 8.9460628,11.204999 8.3340609,11.63 6.8040624,11.715 L 6.8040624,13.806 L 8.8100624,13.806 L 8.8100624,22 L 12.040062,22 M 25.195938,19.96 L 25.195938,17.172 L 23.665938,17.172 L 23.665938,10.1 L 20.401938,10.1 L 13.992938,17.461 L 13.992938,19.875 L 20.707938,19.875 L 20.707938,22 L 23.665938,22 L 23.665938,19.96 L 25.195938,19.96 M 20.758938,13.432 C 20.724938,13.992999 20.707938,15.302001 20.707938,15.999 L 20.707938,17.172 L 19.823938,17.172 C 19.007939,17.172 18.191937,17.189 17.596938,17.223 C 18.038938,16.798 18.531939,16.253999 19.160938,15.489 L 19.330938,15.285 C 20.112937,14.350001 20.435938,13.925 20.758938,13.432"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/15.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/15.png
new file mode 100644
index 0000000..7656c94
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/15.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/15.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/15.svg
new file mode 100644
index 0000000..a8eba4d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/15.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 12.388562,22 L 12.388562,10.1 L 9.6345624,10.1 C 9.2945628,11.204999 8.6825609,11.63 7.1525624,11.715 L 7.1525624,13.806 L 9.1585624,13.806 L 9.1585624,22 L 12.388562,22 M 24.847438,17.852 C 24.847438,15.200003 23.164435,13.908 20.597438,13.908 C 19.407439,13.908 18.693437,14.112 18.030438,14.435 L 18.132438,12.786 L 24.133438,12.786 L 24.133438,10.1 L 15.463438,10.1 L 15.055438,16.271 L 17.877438,17.223 C 18.472437,16.798 19.067439,16.543 20.070438,16.543 C 21.090437,16.543 21.668438,17.019001 21.668438,17.937 C 21.668438,18.888999 21.107436,19.45 19.577438,19.45 C 18.302439,19.45 16.891437,18.956999 15.752438,18.277 L 14.409438,20.742 C 15.871436,21.625999 17.43544,22.187 19.492438,22.187 C 22.875435,22.187 24.847438,20.622997 24.847438,17.852"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/16.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/16.png
new file mode 100644
index 0000000..1f2535a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/16.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/16.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/16.svg
new file mode 100644
index 0000000..1adc217
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/16.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 12.405562,22 L 12.405562,10.1 L 9.6515624,10.1 C 9.3115628,11.204999 8.6995609,11.63 7.1695624,11.715 L 7.1695624,13.806 L 9.1755624,13.806 L 9.1755624,22 L 12.405562,22 M 24.830438,17.903 C 24.830438,15.387003 23.096435,14.214 20.631438,14.214 C 19.203439,14.214 18.336437,14.486 17.571438,14.911 C 18.472437,13.534001 20.104441,12.616 23.215438,12.616 L 23.215438,9.913 C 16.415445,9.913 14.341438,14.112003 14.341438,17.257 C 14.341438,20.537997 16.415441,22.187 19.407438,22.187 C 22.773435,22.187 24.830438,20.588997 24.830438,17.903 M 21.651438,18.124 C 21.651438,19.075999 20.818437,19.586 19.577438,19.586 C 18.132439,19.586 17.486438,18.990999 17.486438,18.141 C 17.486438,17.206001 18.183439,16.645 19.645438,16.645 C 20.903437,16.645 21.651438,17.206001 21.651438,18.124"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/17.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/17.png
new file mode 100644
index 0000000..67fe7ce
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/17.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/17.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/17.svg
new file mode 100644
index 0000000..b007799
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/17.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 12.652062,22 L 12.652062,10.1 L 9.8980624,10.1 C 9.5580628,11.204999 8.9460609,11.63 7.4160624,11.715 L 7.4160624,13.806 L 9.4220624,13.806 L 9.4220624,22 L 12.652062,22 M 24.583938,12.48 L 24.583938,10.1 L 14.740938,10.1 L 14.740938,12.786 L 20.656938,12.786 C 18.36194,15.131998 17.239938,17.920004 17.205938,22 L 20.435938,22 C 20.435938,18.141004 21.098941,15.675997 24.583938,12.48"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/18.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/18.png
new file mode 100644
index 0000000..76aa05b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/18.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/18.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/18.svg
new file mode 100644
index 0000000..140c8ec
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/18.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 12.176062,22 L 12.176062,10.1 L 9.4220624,10.1 C 9.0820628,11.204999 8.4700609,11.63 6.9400624,11.715 L 6.9400624,13.806 L 8.9460624,13.806 L 8.9460624,22 L 12.176062,22 M 25.059938,18.294 C 25.059938,16.764002 23.971937,15.948 23.206938,15.642 C 23.954937,15.166 24.549938,14.519999 24.549938,13.449 C 24.549938,11.171002 22.526935,9.913 19.653938,9.913 C 16.780941,9.913 14.723938,11.171002 14.723938,13.449 C 14.723938,14.519999 15.352939,15.251 16.066938,15.676 C 15.301939,15.982 14.213938,16.764002 14.213938,18.294 C 14.213938,20.707998 16.287941,22.187 19.619938,22.187 C 22.951935,22.187 25.059938,20.707998 25.059938,18.294 M 21.387938,13.5 C 21.387938,14.094999 20.945937,14.639 19.653938,14.639 C 18.361939,14.639 17.885938,14.094999 17.885938,13.5 C 17.885938,12.905001 18.327939,12.31 19.619938,12.31 C 20.911937,12.31 21.387938,12.905001 21.387938,13.5 M 21.897938,18.26 C 21.897938,19.075999 21.149936,19.688 19.653938,19.688 C 18.157939,19.688 17.375938,19.07599
9 17.375938,18.26 C 17.375938,17.444001 18.106939,16.849 19.619938,16.849 C 21.115936,16.849 21.897938,17.444001 21.897938,18.26"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/19.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/19.png
new file mode 100644
index 0000000..5f5ada0
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/19.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/19.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/19.svg
new file mode 100644
index 0000000..ae864c4
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/19.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 12.414062,22 L 12.414062,10.1 L 9.6600624,10.1 C 9.3200628,11.204999 8.7080609,11.63 7.1780624,11.715 L 7.1780624,13.806 L 9.1840624,13.806 L 9.1840624,22 L 12.414062,22 M 24.821938,14.843 C 24.821938,11.562003 22.747935,9.913 19.755938,9.913 C 16.389941,9.913 14.332938,11.511003 14.332938,14.197 C 14.332938,16.712997 16.06694,17.886 18.531938,17.886 C 19.959937,17.886 20.826939,17.614 21.591938,17.189 C 20.690939,18.565999 19.058935,19.484 15.947938,19.484 L 15.947938,22.187 C 22.747931,22.187 24.821938,17.987997 24.821938,14.843 M 21.676938,13.959 C 21.676938,14.893999 20.979936,15.455 19.517938,15.455 C 18.259939,15.455 17.511938,14.893999 17.511938,13.976 C 17.511938,13.024001 18.344939,12.514 19.585938,12.514 C 21.030936,12.514 21.676938,13.109001 21.676938,13.959"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/2.png
new file mode 100644
index 0000000..8fe3709
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/2.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/2.svg
new file mode 100644
index 0000000..ee96128
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/2.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 20.862,22.013004 L 20.862,19.327004 L 14.657,19.327004 C 14.912,18.613005 15.575003,17.950003 17.955,16.845004 C 20.232998,15.791005 20.777,14.839003 20.777,13.275004 C 20.777,11.116006 19.229997,9.9260043 16.272,9.9260043 C 14.232002,9.9260043 12.684999,10.504005 11.172,11.473004 L 12.685,13.904004 C 13.874999,13.105005 15.031001,12.697004 16.221,12.697004 C 17.172999,12.697004 17.547,12.986005 17.547,13.513004 C 17.547,13.989004 17.359999,14.176005 16.102,14.737004 C 13.127003,16.063003 11.24,18.001008 11.138,22.013004 L 20.862,22.013004"
+ id="text2207"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/20.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/20.png
new file mode 100644
index 0000000..5e2ad33
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/20.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/20.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/20.svg
new file mode 100644
index 0000000..1678a9f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/20.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 14.685,22 L 14.685,19.314 L 8.4799999,19.314 C 8.7349997,18.600001 9.3980023,17.936999 11.778,16.832 C 14.055998,15.778001 14.6,14.825998 14.6,13.262 C 14.6,11.103002 13.052997,9.913 10.095,9.913 C 8.055002,9.913 6.5079984,10.491001 4.9949999,11.46 L 6.5079999,13.891 C 7.6979988,13.092001 8.8540011,12.684 10.044,12.684 C 10.995999,12.684 11.37,12.973001 11.37,13.5 C 11.37,13.976 11.182999,14.163001 9.9249999,14.724 C 6.9500029,16.049999 5.0629998,17.988004 4.9609999,22 L 14.685,22 M 27.421719,16.033 C 27.421719,12.072004 25.143716,9.913 22.049719,9.913 C 18.955722,9.913 16.643719,12.106004 16.643719,16.067 C 16.643719,20.027996 18.921722,22.187 22.015719,22.187 C 25.109716,22.187 27.421719,19.993996 27.421719,16.033 M 24.038719,16.067 C 24.038719,18.242998 23.324717,19.348 22.049719,19.348 C 20.77472,19.348 20.026719,18.208998 20.026719,16.033 C 20.026719,13.857002 20.74072,12.752 22.015719,12.752 C 23.290717,12.752 24.038719,13.891002 24.038719,16.067"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/21.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/21.png
new file mode 100644
index 0000000..cfafd1f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/21.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/21.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/21.svg
new file mode 100644
index 0000000..4199512
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/21.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 16.648141,22 L 16.648141,19.314 L 10.44314,19.314 C 10.69814,18.600001 11.361143,17.936999 13.741141,16.832 C 16.019139,15.778001 16.563141,14.825998 16.563141,13.262 C 16.563141,11.103002 15.016138,9.913 12.058141,9.913 C 10.018143,9.913 8.471139,10.491001 6.9581405,11.46 L 8.4711405,13.891 C 9.661139,13.092001 10.817142,12.684 12.007141,12.684 C 12.95914,12.684 13.333141,12.973001 13.333141,13.5 C 13.333141,13.976 13.14614,14.163001 11.88814,14.724 C 8.9131435,16.049999 7.0261404,17.988004 6.9241405,22 L 16.648141,22 M 23.82586,22 L 23.82586,10.1 L 21.07186,10.1 C 20.73186,11.204999 20.119858,11.63 18.58986,11.715 L 18.58986,13.806 L 20.59586,13.806 L 20.59586,22 L 23.82586,22"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/22.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/22.png
new file mode 100644
index 0000000..5415d35
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/22.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/22.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/22.svg
new file mode 100644
index 0000000..c1f4479
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/22.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 14.685,22 L 14.685,19.314 L 8.4799999,19.314 C 8.7349997,18.600001 9.3980023,17.936999 11.778,16.832 C 14.055998,15.778001 14.6,14.825998 14.6,13.262 C 14.6,11.103002 13.052997,9.913 10.095,9.913 C 8.055002,9.913 6.5079984,10.491001 4.9949999,11.46 L 6.5079999,13.891 C 7.6979988,13.092001 8.8540011,12.684 10.044,12.684 C 10.995999,12.684 11.37,12.973001 11.37,13.5 C 11.37,13.976 11.182999,14.163001 9.9249999,14.724 C 6.9500029,16.049999 5.0629998,17.988004 4.9609999,22 L 14.685,22 M 26.571719,22 L 26.571719,19.314 L 20.366719,19.314 C 20.621718,18.600001 21.284721,17.936999 23.664719,16.832 C 25.942716,15.778001 26.486719,14.825998 26.486719,13.262 C 26.486719,11.103002 24.939716,9.913 21.981719,9.913 C 19.941721,9.913 18.394717,10.491001 16.881719,11.46 L 18.394719,13.891 C 19.584718,13.092001 20.74072,12.684 21.930719,12.684 C 22.882718,12.684 23.256719,12.973001 23.256719,13.5 C 23.256719,13.976 23.069717,14.163001 21.811719,14.724 C 18.836722,16.049999 16.94971
9,17.988004 16.847719,22 L 26.571719,22"
+ id="number"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/23.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/23.png
new file mode 100644
index 0000000..658e22b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/23.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/23.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/23.svg
new file mode 100644
index 0000000..ea3c85a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/23.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 15.32239,22.013004 L 15.32239,19.327004 L 9.1173907,19.327004 C 9.3723904,18.613005 10.035393,17.950003 12.41539,16.845004 C 14.693388,15.791005 15.23739,14.839003 15.23739,13.275004 C 15.23739,11.116006 13.690387,9.9260043 10.73239,9.9260043 C 8.6923927,9.9260043 7.1453891,10.504005 5.6323906,11.473004 L 7.1453906,13.904004 C 8.3353896,13.105005 9.4913919,12.697004 10.68139,12.697004 C 11.633389,12.697004 12.00739,12.986005 12.00739,13.513004 C 12.00739,13.989004 11.820389,14.176005 10.56239,14.737004 C 7.5873937,16.063003 5.7003905,18.001008 5.5983906,22.013004 L 15.32239,22.013004 M 26.401609,18.239004 C 26.401609,16.726006 25.432608,15.927004 24.327609,15.672004 C 25.143608,15.281005 25.908609,14.652003 25.908609,13.343004 C 25.908609,10.827007 24.004606,9.9260043 21.148609,9.9260043 C 19.074611,9.9260043 17.646608,10.623005 16.541609,11.473004 L 18.105609,13.615004 C 19.023608,12.952005 19.90761,12.595004 21.063609,12.595004 C 22.236608,12.595004 22.712609,12.
935005 22.712609,13.564004 C 22.712609,14.346004 22.372608,14.567004 21.335609,14.567004 L 19.805609,14.567004 L 19.805609,17.134004 L 21.522609,17.134004 C 22.729608,17.134004 23.205609,17.440005 23.205609,18.273004 C 23.205609,19.089003 22.627608,19.480004 21.250609,19.480004 C 19.94161,19.480004 18.836608,18.987004 17.867609,18.239004 L 16.167609,20.381004 C 17.442608,21.503003 19.159611,22.200004 21.182609,22.200004 C 24.412606,22.200004 26.401609,20.993002 26.401609,18.239004"
+ id="text2207"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/24.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/24.png
new file mode 100644
index 0000000..863ce3b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/24.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/24.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/24.svg
new file mode 100644
index 0000000..27e1d39
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/24.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/25.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/25.png
new file mode 100644
index 0000000..cc23b9b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/25.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/25.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/25.svg
new file mode 100644
index 0000000..114e1a2
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/25.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/26.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/26.png
new file mode 100644
index 0000000..583fe34
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/26.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/26.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/26.svg
new file mode 100644
index 0000000..e9b5d23
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/26.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/27.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/27.png
new file mode 100644
index 0000000..d1c3dfa
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/27.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/27.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/27.svg
new file mode 100644
index 0000000..4a80177
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/27.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/28.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/28.png
new file mode 100644
index 0000000..f5db747
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/28.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/28.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/28.svg
new file mode 100644
index 0000000..d453f29
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/28.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/29.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/29.png
new file mode 100644
index 0000000..9a3141e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/29.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/29.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/29.svg
new file mode 100644
index 0000000..04b5c50
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/29.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/3.png
new file mode 100644
index 0000000..449ef5a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/3.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/3.svg
new file mode 100644
index 0000000..d3a7e73
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/3.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 21.117,18.239004 C 21.117,16.726006 20.147999,15.927004 19.043,15.672004 C 19.858999,15.281005 20.624,14.652003 20.624,13.343004 C 20.624,10.827007 18.719997,9.9260043 15.864,9.9260043 C 13.790002,9.9260043 12.361999,10.623005 11.257,11.473004 L 12.821,13.615004 C 13.738999,12.952005 14.623001,12.595004 15.779,12.595004 C 16.951999,12.595004 17.428,12.935005 17.428,13.564004 C 17.428,14.346004 17.087999,14.567004 16.051,14.567004 L 14.521,14.567004 L 14.521,17.134004 L 16.238,17.134004 C 17.444999,17.134004 17.921,17.440005 17.921,18.273004 C 17.921,19.089003 17.342999,19.480004 15.966,19.480004 C 14.657002,19.480004 13.551999,18.987004 12.583,18.239004 L 10.883,20.381004 C 12.157999,21.503003 13.875002,22.200004 15.898,22.200004 C 19.127997,22.200004 21.117,20.993002 21.117,18.239004"
+ id="text2207"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/30.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/30.png
new file mode 100644
index 0000000..9d3db24
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/30.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/30.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/30.svg
new file mode 100644
index 0000000..5cdcf65
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/30.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/31.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/31.png
new file mode 100644
index 0000000..9e2675d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/31.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/31.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/31.svg
new file mode 100644
index 0000000..f0fdb29
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/31.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/32.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/32.png
new file mode 100644
index 0000000..20f1bb2
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/32.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/32.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/32.svg
new file mode 100644
index 0000000..9382928
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/32.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c 0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141 0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801 0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648 -0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083 -1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l -1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/33.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/33.png
new file mode 100644
index 0000000..01407e6
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/33.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/33.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/33.svg
new file mode 100644
index 0000000..f46815f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/33.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883 -0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579 2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273 -0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534 -1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l 0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961 0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414 0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289 -0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032 -0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269 0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026 -0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l -1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868 0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393 1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/34.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/34.png
new file mode 100644
index 0000000..ba44352
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/34.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/34.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/34.svg
new file mode 100644
index 0000000..7bbdf5b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/34.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/35.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/35.png
new file mode 100644
index 0000000..21d4575
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/35.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/35.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/35.svg
new file mode 100644
index 0000000..8e19553
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/35.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/36.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/36.png
new file mode 100644
index 0000000..b5402b5
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/36.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/36.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/36.svg
new file mode 100644
index 0000000..d364dbf
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/36.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/37.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/37.png
new file mode 100644
index 0000000..9fd99d2
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/37.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/37.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/37.svg
new file mode 100644
index 0000000..771fa4d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/37.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/38.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/38.png
new file mode 100644
index 0000000..3ce6027
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/38.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/38.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/38.svg
new file mode 100644
index 0000000..487e0ef
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/38.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/39.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/39.png
new file mode 100644
index 0000000..d689450
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/39.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/39.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/39.svg
new file mode 100644
index 0000000..cea69f7
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/39.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/4.png
new file mode 100644
index 0000000..0a2634a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/4.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/4.svg
new file mode 100644
index 0000000..e6bbe8e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/4.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 20.573772,19.96 L 20.573772,17.172 L 19.043772,17.172 L 19.043772,10.1 L 15.779772,10.1 L 9.3707718,17.461 L 9.3707718,19.875 L 16.085772,19.875 L 16.085772,22 L 19.043772,22 L 19.043772,19.96 L 20.573772,19.96 M 16.136772,13.432 C 16.102772,13.992999 16.085772,15.302001 16.085772,15.999 L 16.085772,17.172 L 15.201772,17.172 C 14.385773,17.172 13.569771,17.189 12.974772,17.223 C 13.416772,16.798 13.909773,16.253999 14.538772,15.489 L 14.708772,15.285 C 15.490771,14.350001 15.813772,13.925 16.136772,13.432"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/40.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/40.png
new file mode 100644
index 0000000..0d3532e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/40.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/40.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/40.svg
new file mode 100644
index 0000000..bb4e1d7
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/40.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#336699" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.440535,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.0136719,0 0,-1.784668 5.1547849,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262863,0.520191 -0.42334,0.780274 l -2.0253904,3.071289 2.7558594,0"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/5.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/5.png
new file mode 100644
index 0000000..bc1d337
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/5.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/5.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/5.svg
new file mode 100644
index 0000000..d8578f2
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/5.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 21.219,17.852 C 21.219,15.200003 19.535997,13.908 16.969,13.908 C 15.779001,13.908 15.064999,14.112 14.402,14.435 L 14.504,12.786 L 20.505,12.786 L 20.505,10.1 L 11.835,10.1 L 11.427,16.271 L 14.249,17.223 C 14.843999,16.798 15.439001,16.543 16.442,16.543 C 17.461999,16.543 18.04,17.019001 18.04,17.937 C 18.04,18.888999 17.478998,19.45 15.949,19.45 C 14.674001,19.45 13.262999,18.956999 12.124,18.277 L 10.781,20.742 C 12.242999,21.625999 13.807002,22.187 15.864,22.187 C 19.246997,22.187 21.219,20.622997 21.219,17.852"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/6.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/6.png
new file mode 100644
index 0000000..68cb4b6
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/6.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/6.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/6.svg
new file mode 100644
index 0000000..14d62e0
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/6.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 21.2445,17.903 C 21.2445,15.387003 19.510497,14.214 17.0455,14.214 C 15.617501,14.214 14.750499,14.486 13.9855,14.911 C 14.886499,13.534001 16.518503,12.616 19.6295,12.616 L 19.6295,9.913 C 12.829507,9.913 10.7555,14.112003 10.7555,17.257 C 10.7555,20.537997 12.829503,22.187 15.8215,22.187 C 19.187497,22.187 21.2445,20.588997 21.2445,17.903 M 18.0655,18.124 C 18.0655,19.075999 17.232499,19.586 15.9915,19.586 C 14.546501,19.586 13.9005,18.990999 13.9005,18.141 C 13.9005,17.206001 14.597501,16.645 16.0595,16.645 C 17.317499,16.645 18.0655,17.206001 18.0655,18.124"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/7.png
new file mode 100644
index 0000000..3b6cc72
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/7.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/7.svg
new file mode 100644
index 0000000..8d71ee3
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/7.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 20.9215,12.48 L 20.9215,10.1 L 11.0785,10.1 L 11.0785,12.786 L 16.9945,12.786 C 14.699502,15.131998 13.5775,17.920004 13.5435,22 L 16.7735,22 C 16.7735,18.141004 17.436503,15.675997 20.9215,12.48"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/8.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/8.png
new file mode 100644
index 0000000..b092185
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/8.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/8.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/8.svg
new file mode 100644
index 0000000..1c31e86
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/8.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 21.423,18.294 C 21.423,16.764002 20.334999,15.948 19.57,15.642 C 20.317999,15.166 20.913,14.519999 20.913,13.449 C 20.913,11.171002 18.889997,9.913 16.017,9.913 C 13.144003,9.913 11.087,11.171002 11.087,13.449 C 11.087,14.519999 11.716001,15.251 12.43,15.676 C 11.665001,15.982 10.577,16.764002 10.577,18.294 C 10.577,20.707998 12.651003,22.187 15.983,22.187 C 19.314997,22.187 21.423,20.707998 21.423,18.294 M 17.751,13.5 C 17.751,14.094999 17.308999,14.639 16.017,14.639 C 14.725001,14.639 14.249,14.094999 14.249,13.5 C 14.249,12.905001 14.691001,12.31 15.983,12.31 C 17.274999,12.31 17.751,12.905001 17.751,13.5 M 18.261,18.26 C 18.261,19.075999 17.512998,19.688 16.017,19.688 C 14.521001,19.688 13.739,19.075999 13.739,18.26 C 13.739,17.444001 14.470002,16.849 15.983,16.849 C 17.478998,16.849 18.261,17.444001 18.261,18.26"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/9.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/9.png
new file mode 100644
index 0000000..7706583
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/9.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/9.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/9.svg
new file mode 100644
index 0000000..851e9a3
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/9.svg
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#aa0000" />
+ <path
+ d="M 22.128383,14.843 C 22.128383,11.562003 20.05438,9.913 17.062383,9.913 C 13.696386,9.913 11.639383,11.511003 11.639383,14.197 C 11.639383,16.712997 13.373385,17.886 15.838383,17.886 C 17.266382,17.886 18.133384,17.614 18.898383,17.189 C 17.997384,18.565999 16.36538,19.484 13.254383,19.484 L 13.254383,22.187 C 20.054376,22.187 22.128383,17.987997 22.128383,14.843 M 18.983383,13.959 C 18.983383,14.893999 18.286381,15.455 16.824383,15.455 C 15.566384,15.455 14.818383,14.893999 14.818383,13.976 C 14.818383,13.024001 15.651384,12.514 16.892383,12.514 C 18.337381,12.514 18.983383,13.109001 18.983383,13.959"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/bkgrnd_greydots.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/bkgrnd_greydots.png
new file mode 100644
index 0000000..2333a6d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/bkgrnd_greydots.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/bullet_arrowblue.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/bullet_arrowblue.png
new file mode 100644
index 0000000..c235534
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/bullet_arrowblue.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/documentation.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/documentation.png
new file mode 100644
index 0000000..79d0a80
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/documentation.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/dot.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/dot.png
new file mode 100644
index 0000000..36a6859
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/dot.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/dot2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/dot2.png
new file mode 100644
index 0000000..40aff92
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/dot2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/green.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/green.png
new file mode 100644
index 0000000..ebb3c24
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/green.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/h1-bg.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/h1-bg.png
new file mode 100644
index 0000000..a2aad24
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/h1-bg.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/image_left.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/image_left.png
new file mode 100644
index 0000000..e8fe7a4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/image_left.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/image_right.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/image_right.png
new file mode 100644
index 0000000..166cb79
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/image_right.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/important.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/important.png
new file mode 100644
index 0000000..f7594a3
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/important.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/important.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/important.svg
new file mode 100644
index 0000000..2d33045
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/important.svg
@@ -0,0 +1,106 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="important.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/important.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata2611">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="681"
+ inkscape:window-width="738"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="20"
+ inkscape:cy="20"
+ inkscape:window-x="0"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective2613" />
+ </defs>
+ <g
+ transform="matrix(0.4626799,0,0,0.4626799,-5.2934127,-3.3160376)"
+ id="g5485">
+ <path
+ d="M 29.97756,91.885882 L 55.586992,80.409826 L 81.231619,91.807015 L 78.230933,63.90468 L 96.995009,43.037218 L 69.531053,37.26873 L 55.483259,12.974592 L 41.510292,37.311767 L 14.064204,43.164717 L 32.892392,63.97442 L 29.97756,91.885882 z"
+ id="path6799"
+ style="fill:#f3de82;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.536215,56.538729 L 55.48324,12.974601 L 41.51028,37.311813 L 55.536215,56.538729 z"
+ id="path6824"
+ style="opacity:0.91005291;fill:#f9f2cb;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.57947,56.614318 L 78.241135,63.937979 L 96.976198,43.044318 L 55.57947,56.614318 z"
+ id="use6833"
+ style="opacity:1;fill:#d0bc64;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.523838,56.869126 L 55.667994,80.684281 L 81.379011,91.931065 L 55.523838,56.869126 z"
+ id="use6835"
+ style="opacity:1;fill:#e0c656;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.283346,56.742618 L 13.877363,43.200977 L 32.640089,64.069652 L 55.283346,56.742618 z"
+ id="use6831"
+ style="opacity:1;fill:#d1ba59;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.472076,56.869126 L 55.32792,80.684281 L 29.616903,91.931065 L 55.472076,56.869126 z"
+ id="use6837"
+ style="opacity:1;fill:#d2b951;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.57947,56.614318 L 96.976198,43.044318 L 69.504294,37.314027 L 55.57947,56.614318 z"
+ id="path7073"
+ style="opacity:1;fill:#f6e7a3;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.523838,56.869126 L 81.379011,91.931065 L 78.214821,64.046881 L 55.523838,56.869126 z"
+ id="path7075"
+ style="opacity:1;fill:#f6e7a3;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.283346,56.742618 L 41.341708,37.434209 L 13.877363,43.200977 L 55.283346,56.742618 z"
+ id="path7077"
+ style="opacity:1;fill:#f6e59d;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.472076,56.869126 L 29.616903,91.931065 L 32.781093,64.046881 L 55.472076,56.869126 z"
+ id="path7079"
+ style="opacity:1;fill:#f3df8b;fill-opacity:1;enable-background:new" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/logo.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/logo.png
new file mode 100644
index 0000000..66a3104
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/logo.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/note.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/note.png
new file mode 100644
index 0000000..d6c4518
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/note.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/note.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/note.svg
new file mode 100644
index 0000000..70e43b6
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/note.svg
@@ -0,0 +1,111 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="note.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/note.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata16">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="1024"
+ inkscape:window-width="1205"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="22.217181"
+ inkscape:cy="20"
+ inkscape:window-x="334"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective18" />
+ </defs>
+ <g
+ transform="matrix(0.468275,0,0,0.468275,-5.7626904,-7.4142703)"
+ id="layer1">
+ <g
+ transform="matrix(0.115136,0,0,0.115136,9.7283,21.77356)"
+ id="g8014"
+ style="enable-background:new">
+ <g
+ id="g8518"
+ style="opacity:1">
+ <path
+ d="M -2512.4524,56.33197 L 3090.4719,56.33197 L 3090.4719,4607.3813 L -2512.4524,4607.3813 L -2512.4524,56.33197 z"
+ transform="matrix(0.1104659,-2.3734892e-2,2.2163258e-2,0.1031513,308.46782,74.820675)"
+ id="rect8018"
+ style="fill:#ffe680;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.1;stroke-linecap:butt;stroke-miterlimit:4;stroke-dashoffset:0;stroke-opacity:1" />
+ </g>
+ <g
+ transform="matrix(0.5141653,-7.1944682e-2,7.1944682e-2,0.5141653,146.04015,-82.639785)"
+ id="g8020">
+ <path
+ d="M 511.14114,441.25315 C 527.3248,533.52772 464.31248,622.82928 370.39916,640.71378 C 276.48584,658.59828 187.23462,598.29322 171.05095,506.01865 C 154.86728,413.74408 217.8796,324.44253 311.79292,306.55803 C 405.70624,288.67353 494.95747,348.97858 511.14114,441.25315 z"
+ id="path8022"
+ style="opacity:1;fill:#e0c96f;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.0804934;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625 404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C 280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695 527.8214,324.97052 527.8214,393.1416 z"
+ transform="matrix(1.2585415,-0.2300055,0.2168789,1.1867072,-248.76141,68.254424)"
+ id="path8024"
+ style="opacity:1;fill:#c00000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.0804934;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 358.5625,281.15625 C 348.09597,281.05155 337.43773,281.94729 326.71875,283.90625 C 240.96686,299.57789 183.37901,377.92385 198.15625,458.78125 C 209.70749,521.98673 262.12957,567.92122 325.40625,577.5625 L 357.25,433.6875 L 509.34375,405.875 C 509.14405,404.58166 509.0804,403.29487 508.84375,402 C 495.91366,331.24978 431.82821,281.88918 358.5625,281.15625 z"
+ id="path8026"
+ style="opacity:1;fill:#b60000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.1;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 294.2107,361.9442 L 282.79367,370.38482 L 261.73414,386.13346 C 253.13706,404.40842 254.3359,423.7989 259.7176,444.39774 C 273.6797,497.83861 313.42636,523.96124 369.50989,517.58957 C 398.21848,514.32797 424.51832,504.67345 440.64696,484.15958 L 469.89512,447.48298 L 294.2107,361.9442 z"
+ id="path8028"
+ style="fill:#750000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.09999999;stroke-linecap:butt;stroke-miterlimit:4;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625 404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C 280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695 527.8214,324.97052 527.8214,393.1416 z"
+ transform="matrix(0.9837071,-0.1797787,0.1695165,0.9275553,-78.013985,79.234385)"
+ id="path8030"
+ style="opacity:1;fill:#d40000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.10298239;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625 404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C 280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695 527.8214,324.97052 527.8214,393.1416 z"
+ transform="matrix(0.9837071,-0.1797787,0.1695165,0.9275553,-69.306684,71.273294)"
+ id="path8032"
+ style="opacity:1;fill:#e11212;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.10298239;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ </g>
+ </g>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/red.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/red.png
new file mode 100644
index 0000000..d32d5e2
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/red.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/redhat-logo.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/redhat-logo.svg
new file mode 100644
index 0000000..1001776
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/redhat-logo.svg
@@ -0,0 +1,94 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://web.resource.org/cc/"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:xlink="http://www.w3.org/1999/xlink"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ width="300"
+ height="140"
+ id="svg2812"
+ sodipodi:version="0.32"
+ inkscape:version="0.45+devel"
+ version="1.0"
+ sodipodi:docname="redhat-logo.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape">
+ <defs
+ id="defs3" />
+ <sodipodi:namedview
+ inkscape:document-units="mm"
+ id="base"
+ pagecolor="#ffffff"
+ bordercolor="#666666"
+ borderopacity="1.0"
+ inkscape:pageopacity="0.0"
+ inkscape:pageshadow="2"
+ inkscape:zoom="1"
+ inkscape:cx="174.26394"
+ inkscape:cy="40.358463"
+ inkscape:current-layer="layer1"
+ inkscape:window-width="722"
+ inkscape:window-height="523"
+ inkscape:window-x="71"
+ inkscape:window-y="636"
+ width="300px"
+ height="140px" />
+ <metadata
+ id="metadata4">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <g
+ inkscape:label="Layer 1"
+ inkscape:groupmode="layer"
+ id="layer1"
+ transform="translate(-13.714282,-252.57246)">
+ <g
+ transform="matrix(2.1166666,0,0,2.1166666,-32.193429,187.76029)"
+ id="shadowman">
+ <path
+ d="M 55.68466,68.503937 C 55.68466,79.688581 46.617715,88.755526 35.433071,88.755526 C 24.248427,88.755526 15.181482,79.688581 15.181482,68.503937 C 15.181482,57.319293 24.248427,48.252348 35.433071,48.252348 C 46.617715,48.252348 55.68466,57.319293 55.68466,68.503937 z"
+ transform="matrix(1.10693,0,0,1.10693,5.005761,-12.00975)"
+ style="fill:#ffffff"
+ id="path4548" />
+ <path
+ d="M 147.81332,72.126073 C 147.81332,73.329962 147.86057,74.57586 148.03519,75.740362 L 146.64882,75.740362 L 146.42826,73.559712 L 146.35605,73.559712 C 145.61822,74.733404 143.92333,76.086957 141.50635,76.086957 C 138.4461,76.086957 137.02164,73.933874 137.02164,71.904202 C 137.02164,68.394942 140.11998,66.27862 146.30878,66.34295 L 146.30878,65.937278 C 146.30878,64.432747 146.01471,61.431561 142.41879,61.45388 C 141.08756,61.45388 139.70118,61.810976 138.5997,62.588186 L 138.1205,61.494579 C 139.51083,60.551948 141.20703,60.180411 142.58291,60.180411 C 146.97178,60.180411 147.81201,63.475677 147.81201,66.194597 L 147.81201,72.126073 L 147.81332,72.126073 z M 146.30878,67.609855 C 142.99645,67.514016 138.62333,68.015527 138.62333,71.667888 C 138.62333,73.853791 140.06616,74.835806 141.65077,74.835806 C 144.1859,74.835806 145.62742,73.266945 146.15124,71.786044 C 146.26152,71.460456 146.3101,71.134869 146.3101,70.874924 L 146.3101,67.609855 L 146.30878,67.609855 z
M 153.80387,57.175286 L 153.80387,60.527004 L 158.13891,60.527004 L 158.13891,61.747959 L 153.80387,61.747959 L 153.80387,71.635066 C 153.80387,73.568902 154.40385,74.780665 156.03835,74.780665 C 156.82343,74.780665 157.37877,74.676951 157.76606,74.541727 L 157.94856,75.707542 C 157.45754,75.912347 156.76567,76.072514 155.84798,76.072514 C 154.73862,76.072514 153.81831,75.723296 153.22358,74.994662 C 152.53566,74.195133 152.29934,72.917726 152.29934,71.365932 L 152.29934,61.746646 L 149.7314,61.746646 L 149.7314,60.525692 L 152.29934,60.525692 L 152.29934,57.729312 L 153.80387,57.175286 z M 129.02767,60.179099 C 127.87105,60.179099 126.8339,60.512563 125.96348,61.052146 C 125.05891,61.581226 124.3224,62.399135 123.88522,63.247239 L 123.8222,63.247239 L 123.8222,55.719331 L 122.31767,55.309721 L 122.31767,75.740362 L 123.8222,75.740362 L 123.8222,66.437475 C 123.8222,65.819121 123.86947,65.39113 124.02832,64.938196 C 124.67818,63.046372 126.45974,61.493265 128.61545,61.49326
5 C 131.72953,61.493265 132.80739,63.990315 132.80739,66.730242 L 132.80739,75.73905 L 134.31191,75.73905 L 134.31191,66.564822 C 134.31191,60.899855 130.4692,60.179099 129.02767,60.179099 z"
+ id="path620" />
+ <path
+ d="M 78.208384,65.270348 C 78.208384,63.205228 78.16506,61.686255 78.08235,60.311696 L 81.460325,60.311696 L 81.604739,63.240675 L 81.713705,63.240675 C 82.473849,61.069213 84.273772,59.961164 85.938472,59.961164 C 86.319199,59.961164 86.541071,59.976918 86.853532,60.045187 L 86.853532,63.719867 C 86.488557,63.648972 86.147215,63.609587 85.677213,63.609587 C 83.819525,63.609587 82.528988,64.792469 82.181081,66.560884 C 82.115438,66.904852 82.079992,67.318401 82.079992,67.738514 L 82.079992,75.73905 L 78.176875,75.73905 L 78.208384,65.270348 z M 91.56274,69.076313 C 91.666455,71.871381 93.83004,73.093647 96.328402,73.093647 C 98.123074,73.093647 99.405732,72.814009 100.58599,72.379455 L 101.16365,75.064243 C 99.842914,75.623519 98.010169,76.042319 95.771752,76.042319 C 90.763211,76.042319 87.82767,72.949234 87.82767,68.220332 C 87.82767,63.961432 90.411366,59.933594 95.372644,59.933594 C 100.38906,59.933594 102.02225,64.059896 102.02225,67.436558 C 102.02225,68.16256
6 101.95792,68.744161 101.88309,69.103883 L 91.56274,69.076313 z M 98.348885,66.358704 C 98.365952,64.929006 97.743659,62.59869 95.129766,62.59869 C 92.728556,62.59869 91.730785,64.778027 91.554863,66.358704 L 98.348885,66.358704 z M 118.82942,54.363153 L 114.93024,53.307617 L 114.93024,61.97377 L 114.8659,61.97377 C 114.17665,60.834212 112.65375,59.962477 110.54268,59.962477 C 106.83386,59.962477 103.60162,63.033244 103.62656,68.201952 C 103.62656,72.945296 106.54372,76.086957 110.22759,76.086957 C 112.45288,76.086957 114.31582,75.024857 115.23745,73.297141 L 115.30703,73.297141 L 115.48164,75.73905 L 118.95675,75.73905 C 118.88586,74.690078 118.82809,72.991246 118.82809,71.411881 L 118.82809,54.363153 L 118.82942,54.363153 z M 114.92893,69.050056 C 114.92893,69.459667 114.90136,69.840395 114.81077,70.189614 C 114.41823,71.877945 113.0371,72.966301 111.44198,72.966301 C 108.98563,72.966301 107.57957,70.894617 107.57957,68.060164 C 107.57957,65.198141 108.97382,62.983355 111
.48662,62.983355 C 113.2406,62.983355 114.49568,64.220064 114.84228,65.72197 C 114.90922,66.038368 114.92893,66.428286 114.92893,66.738119 L 114.92893,69.050056 L 114.92893,69.050056 z"
+ id="path616" />
+ <path
+ d="M 161.80517,73.528501 C 160.90479,73.528501 160.18937,74.243893 160.18939,75.144292 C 160.18939,76.044668 160.90478,76.760094 161.80517,76.760081 C 162.70554,76.760081 163.42095,76.041202 163.42097,75.144292 C 163.42097,74.24046 162.70554,73.528501 161.80517,73.528501 z M 161.80517,73.803529 C 162.54687,73.803529 163.14594,74.402585 163.14593,75.144292 C 163.14593,75.882533 162.54342,76.485053 161.80517,76.485053 C 161.06348,76.485053 160.46441,75.882523 160.46441,75.144292 C 160.46441,74.402596 161.06346,73.80354 161.80517,73.803529 z M 161.25512,74.319207 L 161.25512,75.969376 L 161.49577,75.969376 L 161.49577,75.247426 L 161.80517,75.247426 L 162.2521,75.969376 L 162.52712,75.969376 L 162.04582,75.247426 C 162.29078,75.216382 162.49274,75.06625 162.49274,74.766128 C 162.49273,74.438393 162.30159,74.319207 161.90832,74.319207 L 161.25512,74.319207 z M 161.49577,74.525479 L 161.83955,74.525479 C 162.0155,74.525467 162.21771,74.562596 162.21771,74.766128 C 162.21
773,75.02142 162.01906,75.041156 161.80517,75.041156 L 161.49577,75.041156 L 161.49577,74.525479 z"
+ id="path650" />
+ <path
+ d="M 63.115808,76.090895 C 60.810796,75.504093 58.522203,75.797079 56.285026,76.486064 C 56.010655,76.526189 56.159301,76.830359 56.114355,76.953441 C 56.240389,77.319727 56.032958,77.717522 54.998429,77.944646 C 53.465014,78.282048 52.496128,79.864039 51.942103,80.389181 C 51.290927,81.007536 49.45293,81.388262 49.729943,81.01935 C 49.946565,80.730522 50.773662,79.83253 51.276485,78.861018 C 51.726795,77.99322 52.127215,77.746405 52.678614,76.919305 C 52.841408,76.676428 53.46764,75.824385 53.650127,75.149578 C 53.854932,74.490525 53.786663,73.663427 53.865435,73.323398 C 53.97834,72.83239 54.440465,71.767665 54.477226,71.166377 C 54.496918,70.825035 53.056716,71.650821 52.372719,71.650821 C 51.688722,71.650821 51.024417,71.242523 50.412627,71.21364 C 49.657736,71.17688 49.17198,71.795235 48.489295,71.68758 C 48.098065,71.625877 47.769852,71.281909 47.087167,71.255652 C 46.115654,71.220205 44.928834,71.795235 42.698294,71.724341 C 40.507139,71.653447 38.480092,68.9
52905 38.204394,68.523601 C 37.880118,68.019465 37.484949,68.019465 37.054333,68.414634 C 36.622404,68.809804 36.090697,68.498657 35.939718,68.234773 C 35.652203,67.73195 34.882871,66.258927 33.692111,65.951719 C 32.044479,65.523729 31.210817,66.864153 31.31847,67.928878 C 31.427438,69.010669 32.127189,69.31394 32.451465,69.887656 C 32.77574,70.462687 32.94116,70.834225 33.54901,71.088919 C 33.980939,71.267467 34.142421,71.53529 34.013762,71.888448 C 33.900856,72.198281 33.451859,72.269175 33.156467,72.282304 C 31.933813,72.291845 31.468231,71.67907 30.76576,70.807968 C 30.388969,70.188301 29.79556,69.919166 29.103685,69.919166 C 28.774159,69.919166 28.465638,70.005814 28.191252,70.147603 C 27.106833,70.710817 25.817611,71.045595 24.429922,71.045595 L 22.863688,71.045595 C 22.102232,68.784859 21.688683,66.365268 21.688683,63.847213 C 21.688683,51.409229 31.770093,41.32782 44.208077,41.32782 C 56.646061,41.32782 66.72747,51.410542 66.72747,63.847213 C 66.730097,68.36212 65.40
1488,72.565881 63.115808,76.090895 z M 49.170707,74.025807 C 49.286239,74.138712 49.485793,74.518127 49.241602,75.001258 C 49.105065,75.257265 48.956712,75.437126 48.694141,75.647183 C 48.37643,75.900564 47.758075,76.194643 46.908658,75.65506 C 46.451785,75.364919 46.424215,75.267768 45.794044,75.349165 C 45.343735,75.408243 45.163874,74.953995 45.326668,74.575893 C 45.488149,74.199104 46.152454,73.893208 46.980865,74.378965 C 47.353716,74.598211 47.932685,75.059024 48.44076,74.649413 C 48.65213,74.481367 48.778164,74.368462 49.069618,74.031058 C 49.082746,74.015304 49.101126,74.007427 49.122132,74.007427 C 49.140512,74.007427 49.157579,74.013991 49.170707,74.025807 z"
+ id="path632" />
+ <path
+ d="M 63.115853,76.089615 C 65.401534,72.564599 66.72883,68.36215 66.72883,63.849868 C 66.72883,51.411879 56.647417,41.330466 44.209428,41.330466 C 31.77144,41.330466 21.690027,51.413192 21.690027,63.849868 C 21.690027,66.367923 22.103576,68.787515 22.865032,71.046939 C 25.868844,79.95466 34.290809,86.367957 44.209428,86.367957 C 52.133821,86.367957 59.101143,82.275788 63.115853,76.089615 z"
+ style="fill:none"
+ id="path646" />
+ <path
+ d="M 56.917822,57.857972 C 56.694636,58.606299 56.378238,59.562056 54.970858,60.285439 C 54.766053,60.390468 54.687282,60.218483 54.781807,60.057003 C 55.313513,59.151133 55.409352,58.925322 55.562956,58.568226 C 55.779577,58.047022 55.892482,57.303946 55.463179,55.754779 C 54.615075,52.707643 52.849285,48.633855 51.564001,47.31181 C 50.32598,46.037029 48.079686,45.677306 46.050011,46.19851 C 45.302998,46.390186 43.839164,47.151642 41.126807,46.539852 C 36.433353,45.483004 35.738853,47.833013 35.468405,48.857041 C 35.197956,49.881066 34.552032,52.791666 34.552032,52.791666 C 34.33541,53.977174 34.05446,56.038354 41.342116,57.426043 C 44.737158,58.071966 44.910455,58.950266 45.060119,59.58175 C 45.329254,60.712117 45.761183,61.360667 46.245627,61.682316 C 46.731383,62.006591 46.245627,62.274414 45.707356,62.329554 C 44.260592,62.480532 38.917273,60.947118 35.754607,59.151133 C 33.168283,57.570457 33.124958,56.147322 33.717056,54.939495 C 29.808689,54.516756 26.877084
,55.304469 26.345378,57.155594 C 25.431631,60.330077 33.324513,65.752165 42.311003,68.473712 C 51.741236,71.329172 61.440606,69.336258 62.519772,63.40872 C 63.012093,60.71343 60.74348,58.721829 56.917822,57.857972 z M 42.458041,52.053841 C 39.857276,52.241579 39.586829,52.52253 39.099759,53.041108 C 38.411824,53.772368 37.507268,52.090601 37.507268,52.090601 C 36.965059,51.976382 36.306006,51.100708 36.661789,50.2828 C 37.012321,49.474082 37.658246,49.71696 37.860425,49.969029 C 38.107242,50.274923 38.633697,50.777747 39.315068,50.759366 C 39.997753,50.7423 40.785465,50.597886 41.884324,50.597886 C 42.998938,50.597886 43.745953,51.014061 43.789276,51.371156 C 43.823411,51.675739 43.698689,51.964567 42.458041,52.053841 z M 45.191406,47.754243 C 45.187466,47.754243 45.183528,47.755556 45.179589,47.755556 C 45.138891,47.755556 45.107383,47.72536 45.107383,47.687287 C 45.107383,47.659717 45.123137,47.636085 45.14808,47.625583 C 45.652218,47.359073 46.404482,47.147704 47.265715,4
7.059743 C 47.524347,47.032172 47.776416,47.019045 48.019294,47.016418 C 48.062617,47.016418 48.103316,47.016418 48.147954,47.017731 C 49.592094,47.04924 50.746092,47.622957 50.729025,48.299078 C 50.711958,48.973884 49.527763,49.495088 48.084936,49.46358 C 47.617561,49.453076 47.179067,49.384807 46.800965,49.275842 C 46.756328,49.264025 46.723506,49.225952 46.723506,49.181315 C 46.723506,49.135365 46.756328,49.097292 46.802278,49.08679 C 47.702895,48.878046 48.310747,48.538016 48.268737,48.215055 C 48.212283,47.788376 47.03334,47.557315 45.637776,47.696476 C 45.484171,47.713544 45.334507,47.733237 45.191406,47.754243 z"
+ style="fill:#cc0000"
+ id="path648" />
+ <use
+ transform="translate(-94.61853,1.913321)"
+ id="use4312"
+ x="0"
+ y="0"
+ width="744.09448"
+ height="1052.3622"
+ xlink:href="#path650" />
+ </g>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/rhlogo.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/rhlogo.png
new file mode 100644
index 0000000..ecd4856
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/rhlogo.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/shade.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/shade.png
new file mode 100644
index 0000000..a73afdf
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/shade.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/shine.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/shine.png
new file mode 100644
index 0000000..a18f7c4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/shine.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-back.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-back.png
new file mode 100644
index 0000000..d320f26
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-back.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-forward.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-forward.png
new file mode 100644
index 0000000..1ee5a29
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-forward.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-up.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-up.png
new file mode 100644
index 0000000..1cd7332
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-go-up.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-home.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-home.png
new file mode 100644
index 0000000..122536d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/stock-home.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/title_logo.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/title_logo.png
new file mode 100644
index 0000000..d5182b4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/title_logo.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/title_logo.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/title_logo.svg
new file mode 100644
index 0000000..e84ee0e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/title_logo.svg
@@ -0,0 +1,109 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="220"
+ height="70"
+ id="svg6180"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="title_logo.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape">
+ <metadata
+ id="metadata16">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="990"
+ inkscape:window-width="1680"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ showguides="true"
+ inkscape:guide-bbox="true"
+ inkscape:zoom="7.4053365"
+ inkscape:cx="173.22629"
+ inkscape:cy="36.314321"
+ inkscape:window-x="-5"
+ inkscape:window-y="-3"
+ inkscape:current-layer="svg6180" />
+ <defs
+ id="defs6182">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 35 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="220 : 35 : 1"
+ inkscape:persp3d-origin="110 : 23.333333 : 1"
+ id="perspective18" />
+ </defs>
+ <g
+ transform="translate(-266.55899,-345.34488)"
+ id="layer1">
+ <path
+ d="M 316.7736,397.581 C 316.7736,397.581 316.7736,397.581 296.23471,397.581 C 296.56741,402.03345 300.15628,405.35709 304.94186,405.35709 C 308.33169,405.35709 311.25642,403.96093 313.5828,401.70202 C 314.04833,401.23523 314.58006,401.1024 315.17799,401.1024 C 315.9758,401.1024 316.7736,401.50172 317.30491,402.16628 C 317.63761,402.63181 317.83707,403.16354 317.83707,403.69485 C 317.83707,404.42603 317.50437,405.22342 316.90601,405.82219 C 314.11411,408.81271 309.39515,410.80722 304.74198,410.80722 C 296.30049,410.80722 289.52124,404.02755 289.52124,395.58564 C 289.52124,387.14415 296.10146,380.3649 304.54295,380.3649 C 312.91824,380.3649 319.16618,386.87807 319.16618,395.45239 C 319.16618,396.71657 318.03694,397.581 316.7736,397.581 z M 304.54295,385.81588 C 300.08966,385.81588 297.0321,388.74061 296.36796,392.99319 C 306.40422,392.99319 312.71879,392.99319 312.71879,392.99319 C 312.12043,388.93964 308.93005,385.81588 304.54295,385.81588 z"
+ id="path11"
+ style="fill:#3c6eb4" />
+ <path
+ d="M 375.46344,410.80807 C 367.02238,410.80807 360.2427,404.02839 360.2427,395.58648 C 360.2427,387.14499 367.02238,380.36574 375.46344,380.36574 C 383.90578,380.36574 390.68503,387.14499 390.68503,395.58648 C 390.68461,404.02797 383.90535,410.80807 375.46344,410.80807 z M 375.46344,386.14815 C 370.14656,386.14815 366.68967,390.40242 366.68967,395.58648 C 366.68967,400.77012 370.14656,405.02481 375.46344,405.02481 C 380.78075,405.02481 384.23848,400.77012 384.23848,395.58648 C 384.23806,390.40242 380.78075,386.14815 375.46344,386.14815 z"
+ id="path13"
+ style="fill:#3c6eb4" />
+ <path
+ d="M 412.66183,380.36574 C 408.2022,380.36574 405.25217,381.68474 402.64792,384.9953 L 402.40756,383.45535 L 402.40756,383.45535 C 402.20558,381.84792 400.8343,380.60609 399.17374,380.60609 C 397.37235,380.60609 395.91168,382.06509 395.91168,383.8669 C 395.91168,383.86943 395.91168,383.87196 395.91168,383.87449 L 395.91168,383.87449 L 395.91168,383.87744 L 395.91168,383.87744 L 395.91168,407.28456 C 395.91168,409.0792 397.37362,410.54199 399.16868,410.54199 C 400.96333,410.54199 402.42612,409.0792 402.42612,407.28456 L 402.42612,394.72247 C 402.42612,389.00626 407.41114,386.14815 412.66225,386.14815 C 414.25744,386.14815 415.51951,384.81862 415.51951,383.223 C 415.51951,381.62739 414.25744,380.36574 412.66183,380.36574 z"
+ id="path15"
+ style="fill:#3c6eb4" />
+ <path
+ d="M 447.02614,395.58648 C 447.09277,387.41107 441.24288,380.36574 431.80414,380.36574 C 423.36222,380.36574 416.51635,387.14499 416.51635,395.58648 C 416.51635,404.02839 423.16319,410.80807 431.2062,410.80807 C 435.22054,410.80807 438.83302,408.74186 440.44466,406.58289 L 441.23825,408.59723 L 441.23825,408.59723 C 441.66414,409.729 442.75585,410.5344 444.03605,410.5344 C 445.68606,410.5344 447.02361,409.19769 447.02614,407.54895 L 447.02614,407.54895 L 447.02614,399.74208 L 447.02614,399.74208 L 447.02614,395.58648 z M 431.80414,405.02481 C 426.48641,405.02481 423.02995,400.77012 423.02995,395.58648 C 423.02995,390.40242 426.48599,386.14815 431.80414,386.14815 C 437.12144,386.14815 440.57833,390.40242 440.57833,395.58648 C 440.57833,400.77012 437.12144,405.02481 431.80414,405.02481 z"
+ id="path17"
+ style="fill:#3c6eb4" />
+ <path
+ d="M 355.01479,368.3337 C 355.01479,366.5399 353.55285,365.14373 351.7582,365.14373 C 349.96398,365.14373 348.50077,366.54032 348.50077,368.3337 L 348.50077,385.4836 C 346.8398,382.42604 343.25051,380.36574 338.99582,380.36574 C 330.3553,380.36574 324.57246,386.87892 324.57246,395.58648 C 324.57246,404.29405 330.55475,410.80807 338.99582,410.80807 C 342.76137,410.80807 346.02639,409.25378 347.98169,406.55253 L 348.70486,408.38681 C 349.15268,409.64593 350.35403,410.54705 351.76537,410.54705 C 353.55158,410.54705 355.01521,409.0927 355.01521,407.2989 C 355.01521,407.29384 355.01521,407.29004 355.01521,407.28498 L 355.01521,407.28498 L 355.01521,368.3337 L 355.01479,368.3337 z M 339.79363,405.02481 C 334.47632,405.02481 331.08648,400.77012 331.08648,395.58648 C 331.08648,390.40242 334.47632,386.14815 339.79363,386.14815 C 345.11136,386.14815 348.50077,390.20255 348.50077,395.58648 C 348.50077,400.96957 345.11136,405.02481 339.79363,405.02481 z"
+ id="path19"
+ style="fill:#3c6eb4" />
+ <path
+ d="M 287.21553,365.34023 C 286.62139,365.25253 286.01587,365.20825 285.41456,365.20825 C 278.68338,365.20825 273.2071,370.68495 273.2071,377.41613 L 273.2071,381.22933 L 269.21807,381.22933 C 267.7557,381.22933 266.55899,382.42604 266.55899,383.88714 C 266.55899,385.35035 267.7557,386.82452 269.21807,386.82452 L 273.20626,386.82452 L 273.20626,407.28456 C 273.20626,409.0792 274.66862,410.54199 276.46284,410.54199 C 278.25791,410.54199 279.72028,409.0792 279.72028,407.28456 L 279.72028,386.82452 L 284.13014,386.82452 C 285.59208,386.82452 286.78837,385.35035 286.78837,383.88714 C 286.78837,382.42562 285.59208,381.22891 284.13014,381.22891 L 279.72281,381.22891 L 279.72281,377.41571 C 279.72281,374.27719 282.27604,371.30102 285.41456,371.30102 C 285.6975,371.30102 285.98213,371.3221 286.26128,371.363 C 288.04159,371.62655 289.69708,370.82031 289.96147,369.03958 C 290.22417,367.26054 288.99541,365.6042 287.21553,365.34023 z"
+ id="path21"
+ style="fill:#3c6eb4" />
+ <path
+ d="M 482.01243,363.57426 C 482.01243,353.50638 473.85135,345.34488 463.78346,345.34488 C 453.72064,345.34488 445.56167,353.49963 445.55492,363.56119 L 445.5545,363.56077 L 445.5545,377.66787 L 445.55492,377.66829 C 445.5604,379.95292 447.41324,381.80238 449.69955,381.80238 C 449.7063,381.80238 449.71221,381.80154 449.71895,381.80154 L 449.72022,381.80238 L 463.79105,381.80238 L 463.79105,381.80238 C 473.85514,381.79817 482.01243,373.63962 482.01243,363.57426 z"
+ id="path25"
+ style="fill:#294172" />
+ <path
+ d="M 469.13577,349.66577 C 464.41049,349.66577 460.58001,353.49626 460.58001,358.22154 C 460.58001,358.22322 460.58001,358.22533 460.58001,358.22744 L 460.58001,362.7558 L 456.06557,362.7558 C 456.06472,362.7558 456.06472,362.7558 456.0643,362.7558 C 451.33902,362.7558 447.50854,366.56773 447.50854,371.29258 C 447.50854,376.01786 451.33902,379.84835 456.0643,379.84835 C 460.78916,379.84835 464.61964,376.01786 464.61964,371.29258 C 464.61964,371.2909 464.61964,371.28879 464.61964,371.28668 L 464.61964,366.73935 L 469.13408,366.73935 C 469.13493,366.73935 469.13535,366.73935 469.13577,366.73935 C 473.86063,366.73935 477.69111,362.94639 477.69111,358.22154 C 477.69111,353.49626 473.86063,349.66577 469.13577,349.66577 z M 460.58001,371.3006 C 460.57621,373.79058 458.55555,375.80871 456.0643,375.80871 C 453.57052,375.80871 451.53004,373.78678 451.53004,371.29301 C 451.53004,368.7988 453.57052,366.73935 456.0643,366.73935 C 456.06641,366.73935 456.06852,366.73977 456.0702,3
66.73977 L 459.93991,366.73977 C 459.94117,366.73977 459.94201,366.73935 459.94286,366.73935 C 460.29495,366.73935 460.58085,367.0244 460.58085,367.3765 C 460.58085,367.37692 460.58043,367.37734 460.58043,367.37776 L 460.58043,371.3006 L 460.58001,371.3006 z M 469.13535,362.7558 C 469.13408,362.7558 469.1324,362.7558 469.13113,362.7558 L 465.2589,362.7558 C 465.25806,362.7558 465.25721,362.7558 465.25679,362.7558 C 464.90427,362.7558 464.61922,362.47074 464.61922,362.11822 L 464.61922,362.1178 L 464.61922,358.21437 C 464.62344,355.72354 466.64368,353.70583 469.13493,353.70583 C 471.62871,353.70583 473.66961,355.72776 473.66961,358.22196 C 473.67003,360.71532 471.62913,362.7558 469.13535,362.7558 z"
+ id="path29"
+ style="fill:#3c6eb4" />
+ <path
+ d="M 460.58001,362.7558 L 460.58001,358.22744 C 460.58001,358.22533 460.58001,358.22322 460.58001,358.22154 C 460.58001,353.49626 464.41049,349.66577 469.13577,349.66577 C 469.85262,349.66577 470.362,349.74631 471.02529,349.92046 C 471.99303,350.17431 472.78325,350.96664 472.78367,351.88968 C 472.78409,353.00543 471.97448,353.81589 470.76427,353.81589 C 470.18785,353.81589 469.97954,353.70541 469.13535,353.70541 C 466.6441,353.70541 464.62386,355.72312 464.61964,358.21395 L 464.61964,362.1178 L 464.61964,362.11822 C 464.61964,362.47074 464.90469,362.7558 465.25721,362.7558 C 465.25764,362.7558 465.25848,362.7558 465.25932,362.7558 L 468.22453,362.7558 C 469.32974,362.7558 470.222,363.64047 470.22285,364.74863 C 470.22285,365.85679 469.32932,366.73977 468.22453,366.73977 L 464.61964,366.73977 L 464.61964,371.2871 C 464.61964,371.28921 464.61964,371.29132 464.61964,371.29343 C 464.61964,376.01828 460.78916,379.84877 456.0643,379.84877 C 455.34746,379.84877 454.83807,379
.76823 454.17478,379.59408 C 453.20704,379.34065 452.4164,378.5479 452.41598,377.62528 C 452.41598,376.50953 453.22517,375.69865 454.4358,375.69865 C 455.0118,375.69865 455.22053,375.80913 456.0643,375.80913 C 458.55555,375.80913 460.57621,373.79142 460.58043,371.30102 C 460.58043,371.30102 460.58043,367.37734 460.58043,367.37692 C 460.58043,367.02524 460.29453,366.74019 459.94244,366.74019 C 459.94201,366.74019 459.94159,366.74019 459.94075,366.74019 L 456.97554,366.73977 C 455.87033,366.73977 454.97723,365.85763 454.97723,364.74947 C 454.9768,363.63414 455.87961,362.7558 456.99662,362.7558 L 460.58001,362.7558 L 460.58001,362.7558 z"
+ id="path31"
+ style="fill:#ffffff" />
+ <path
+ d="M 477.41661,378.55292 L 480.23219,378.55292 L 480.23219,378.9319 L 479.05067,378.9319 L 479.05067,381.88125 L 478.59813,381.88125 L 478.59813,378.9319 L 477.41661,378.9319 L 477.41661,378.55292 M 480.67805,378.55292 L 481.34906,378.55292 L 482.19843,380.81788 L 483.05224,378.55292 L 483.72326,378.55292 L 483.72326,381.88125 L 483.28409,381.88125 L 483.28409,378.95865 L 482.42581,381.24144 L 481.97326,381.24144 L 481.11499,378.95865 L 481.11499,381.88125 L 480.67805,381.88125 L 480.67805,378.55292"
+ id="text6223"
+ style="fill:#294172;enable-background:new" />
+ </g>
+ <path
+ d="M 181.98344,61.675273 L 184.79902,61.675273 L 184.79902,62.054253 L 183.6175,62.054253 L 183.6175,65.003603 L 183.16496,65.003603 L 183.16496,62.054253 L 181.98344,62.054253 L 181.98344,61.675273 M 185.24488,61.675273 L 185.91589,61.675273 L 186.76526,63.940233 L 187.61907,61.675273 L 188.29009,61.675273 L 188.29009,65.003603 L 187.85092,65.003603 L 187.85092,62.081003 L 186.99264,64.363793 L 186.54009,64.363793 L 185.68182,62.081003 L 185.68182,65.003603 L 185.24488,65.003603 L 185.24488,61.675273"
+ id="path2391"
+ style="fill:#294172;enable-background:new" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/warning.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/warning.png
new file mode 100644
index 0000000..ce09951
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/warning.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/warning.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/warning.svg
new file mode 100644
index 0000000..5f2612c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/warning.svg
@@ -0,0 +1,89 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="warning.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/warning.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata2482">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="910"
+ inkscape:window-width="1284"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="20"
+ inkscape:cy="20"
+ inkscape:window-x="0"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective2484" />
+ </defs>
+ <g
+ transform="matrix(0.4536635,0,0,0.4536635,-5.1836431,-4.6889387)"
+ id="layer1">
+ <g
+ transform="translate(2745.6887,-1555.5977)"
+ id="g8304"
+ style="enable-background:new">
+ <path
+ d="M -1603,1054.4387 L -1577.0919,1027.891 L -1540,1027.4387 L -1513.4523,1053.3468 L -1513,1090.4387 L -1538.9081,1116.9864 L -1576,1117.4387 L -1602.5477,1091.5306 L -1603,1054.4387 z"
+ transform="matrix(0.8233528,8.9983906e-3,-8.9983906e-3,0.8233528,-1398.5561,740.7914)"
+ id="path8034"
+ style="opacity:1;fill:#efd259;fill-opacity:1;stroke:#efd259;stroke-opacity:1" />
+ <path
+ d="M -1603,1054.4387 L -1577.0919,1027.891 L -1540,1027.4387 L -1513.4523,1053.3468 L -1513,1090.4387 L -1538.9081,1116.9864 L -1576,1117.4387 L -1602.5477,1091.5306 L -1603,1054.4387 z"
+ transform="matrix(0.6467652,7.0684723e-3,-7.0684723e-3,0.6467652,-1675.7492,927.16391)"
+ id="path8036"
+ style="opacity:1;fill:#a42324;fill-opacity:1;stroke:#a42324;stroke-opacity:1" />
+ <path
+ d="M -2686.7886,1597.753 C -2686.627,1596.5292 -2686.5462,1595.6987 -2686.5462,1595.218 C -2686.5462,1593.1637 -2688.0814,1592.0711 -2690.9899,1592.0711 C -2693.8985,1592.0711 -2695.4336,1593.12 -2695.4336,1595.218 C -2695.4336,1595.961 -2695.3528,1596.7914 -2695.1912,1597.753 L -2692.929,1614.4491 L -2689.0508,1614.4491 L -2686.7886,1597.753"
+ id="path8038"
+ style="font-size:107.13574219px;font-style:normal;font-weight:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream Charter" />
+ <path
+ d="M -2690.9899,1617.8197 C -2693.6124,1617.8197 -2695.8118,1619.9346 -2695.8118,1622.6416 C -2695.8118,1625.3486 -2693.6124,1627.4635 -2690.9899,1627.4635 C -2688.2829,1627.4635 -2686.168,1625.264 -2686.168,1622.6416 C -2686.168,1619.9346 -2688.2829,1617.8197 -2690.9899,1617.8197"
+ id="path8040"
+ style="font-size:107.13574219px;font-style:normal;font-weight:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream Charter" />
+ </g>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/watermark-draft.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/watermark-draft.png
new file mode 100644
index 0000000..0ead5af
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/watermark-draft.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/yellow.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/yellow.png
new file mode 100644
index 0000000..223865d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Common_Content/images/yellow.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Live_migration_and_RHEL_compatibility.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Live_migration_and_RHEL_compatibility.html
new file mode 100644
index 0000000..f007cf1
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Live_migration_and_RHEL_compatibility.html
@@ -0,0 +1,18 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.2. Live migration and Fedora version compatibility</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-KVM_live_migration.html" title="Chapter 20. KVM live migration" /><link rel="prev" href="chap-Virtualization_Administration_Guide-KVM_live_migration.html" title="Chapter 20. KVM live migration" /><link rel="next" href="shared-storage-nfs-migration.html" title="20.3. Shared storage example: NFS for a simple migration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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_Administration_Guide-KVM_live_migration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="shared-storage-nfs-migration.html"><strong>Next</strong></a></li></ul><div class="section" id="Live_migration_and_RHEL_compatibility"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.2. Live migration and Fedora version compatibility </h2></div></div></div><div class="para">
+ Live Migration should only be performed in cases where the guest virtual machine and the host physical machine are running the same version of Fedora. Should you perform a live migration using different versions be forwarned that the migration may fail.
+ </div><div class="para">
+ <span class="bold bold"><strong>Issues with the migration protocol</strong></span> — If backward migration ends with "unknown section error", repeating the migration process can repair the issue as it may be a transient error. If not, please report the problem.
+ </div><div class="formalpara" id="form-Virtualization-Live_migration_requirements-Configuring_network_storage"><h5 class="formalpara">Configuring network storage</h5>
+ Configure shared storage and install a guest on the shared storage.
+ </div><div class="para">
+ Alternatively, use the NFS example in <a class="xref" href="shared-storage-nfs-migration.html">Section 20.3, “Shared storage example: NFS for a simple migration”</a>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-KVM_live_migration.html"><strong>Prev</strong>Chapter 20. 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="shared-storage-nfs-migration.html"><strong>Next</strong>20.3. Shared storage example: NFS for a simple mi...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Sect_Failed_to_connect_socket.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Sect_Failed_to_connect_socket.html
new file mode 100644
index 0000000..b0a1f66
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Sect_Failed_to_connect_socket.html
@@ -0,0 +1,22 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.2.2. Failed to connect socket ... : Permission denied</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="App_Hypervisor_Connection_Fail.html" title="B.2. The URI failed to connect to the hypervisor" /><link rel="prev" href="App_Hypervisor_Connection_Fail.html" title="B.2. The URI failed to connect to the hypervisor" /><link rel="next" href="Sect_Other_Connectivity_Errors.html" title="B.2.3. Other connectivity errors" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="App_Hypervisor_Connection_Fail.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="Sect_Other_Connectivity_Errors.html"><strong>Next</strong></a></li></ul><div class="section" id="Sect_Failed_to_connect_socket"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">B.2.2. Failed to connect socket ... : Permission denied</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ When running a <code class="command">virsh</code> command, the following error (or similar) appears:
+ </div><pre class="screen">$ virsh -c qemu:///system list
+error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Permission denied
+error: failed to connect to the hypervisor</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ Without any hostname specified, the connection to <span class="application"><strong>QEMU</strong></span> uses UNIX sockets by default. If there is no error running this command as root, the UNIX socket options in <code class="filename">/etc/libvirt/libvirtd.conf</code> are likely misconfigured.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ To connect as a non-root user using UNIX sockets, configure the following options in <code class="filename">/etc/libvirt/libvirtd.conf</code>:
+ </div><pre class="programlisting">unix_sock_group = <code class="literal"><group></code>
+unix_sock_ro_perms = <perms>
+unix_sock_rw_perms = <perms></pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The user running <code class="command">virsh</code> must be a member of the <code class="literal">group</code> specified in the <code class="option">unix_sock_group</code> option.
+ </div></div></div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_Hypervisor_Connection_Fail.html"><strong>Prev</strong>B.2. The URI failed to connect to the 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_Other_Connectivity_Errors.html"><strong>Next</strong>B.2.3. Other connectivity errors</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Sect_Other_Connectivity_Errors.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Sect_Other_Connectivity_Errors.html
new file mode 100644
index 0000000..2de9a38
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/Sect_Other_Connectivity_Errors.html
@@ -0,0 +1,14 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.2.3. Other connectivity errors</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="App_Hypervisor_Connection_Fail.html" title="B.2. The URI failed to connect to the hypervisor" /><link rel="prev" href="Sect_Failed_to_connect_socket.html" title="B.2.2. Failed to connect socket ... : Permission denied" /><link rel="next" href="App_Domain_Processor.html" title="B.3. The guest virtual machine cannot be started: internal error guest CPU is not compatible with host CPU" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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_Failed_to_connect_socket.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_Domain_Processor.html"><strong>Next</strong></a></li></ul><div class="section" id="Sect_Other_Connectivity_Errors"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">B.2.3. Other connectivity errors</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Unable to connect to server at <code class="literal">server:port</code>: Connection refused</span></dt><dd><div class="para">
+ The daemon is not running on the server or is configured not to listen, using configuration option <code class="option">listen_tcp</code> or <code class="option">listen_tls</code>.
+ </div></dd><dt class="varlistentry"><span class="term">End of file while reading data: nc: using stream socket: Input/output error</span></dt><dd><div class="para">
+ If you specified <code class="systemitem">ssh</code> transport, the daemon is likely not running on the server. Solve this error by verifying that the daemon is running on the server.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="Sect_Failed_to_connect_socket.html"><strong>Prev</strong>B.2.2. Failed to connect socket ... : Permission ...</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="App_Domain_Processor.html"><strong>Next</strong>B.3. The guest virtual machine cannot be started:...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apas02.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apas02.html
new file mode 100644
index 0000000..ee30057
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apas02.html
@@ -0,0 +1,120 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.2. kvm_stat</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Troubleshooting.html" title="Appendix A. Troubleshooting" /><link rel="prev" href="chap-Virtualization_Administration_Guide-Troubleshooting.html" title="Appendix A. Troubleshooting" /><link rel="next" href="sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles.html" title="A.3. Troubleshooting with serial consoles" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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" a
lt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Troubleshooting.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles.html"><strong>Next</strong></a></li></ul><div class="section" id="idp1853360"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp1853360">A.2. kvm_stat</h2></div></div></div><div class="para">
+ The <code class="command">kvm_stat</code> command is a python script which retrieves runtime statistics from the <code class="systemitem">kvm</code> kernel module. The <code class="command">kvm_stat</code> command can be used to diagnose guest behavior visible to <code class="systemitem">kvm</code>. In particular, performance related issues with guests. Currently, the reported statistics are for the entire system; the behavior of all running guests is reported.
+ </div><div class="para">
+ The <code class="command">kvm_stat</code> command requires that the <code class="systemitem">kvm</code> kernel module is loaded and <code class="command">debugfs</code> is mounted. If either of these features are not enabled, the command will output the required steps to enable <code class="command">debugfs</code> or the <code class="systemitem">kvm</code> module. For example:
+ </div><pre class="screen"># kvm_stat
+Please mount debugfs ('mount -t debugfs debugfs /sys/kernel/debug')
+and ensure the kvm modules are loaded</pre><div class="para">
+ Mount <code class="command">debugfs</code> if required:
+ </div><pre class="screen"># mount -t debugfs debugfs /sys/kernel/debug</pre><div class="formalpara"><h5 class="formalpara" id="idm3265920">kvm_stat output</h5>
+ The <code class="command">kvm_stat</code> command outputs statistics for all guests and the host. The output is updated until the command is terminated (using <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>c</strong></span> or the <span class="keycap"><strong>q</strong></span> key).
+ </div><pre class="screen"># kvm_stat
+
+kvm statistics
+
+efer_reload 94 0
+exits 4003074 31272
+fpu_reload 1313881 10796
+halt_exits 14050 259
+halt_wakeup 4496 203
+host_state_reload 1638354 24893
+hypercalls 0 0
+insn_emulation 1093850 1909
+insn_emulation_fail 0 0
+invlpg 75569 0
+io_exits 1596984 24509
+irq_exits 21013 363
+irq_injections 48039 1222
+irq_window 24656 870
+largepages 0 0
+mmio_exits 11873 0
+mmu_cache_miss 42565 8
+mmu_flooded 14752 0
+mmu_pde_zapped 58730 0
+mmu_pte_updated 6 0
+mmu_pte_write 138795 0
+mmu_recycled 0 0
+mmu_shadow_zapped 40358 0
+mmu_unsync 793 0
+nmi_injections 0 0
+nmi_window 0 0
+pf_fixed 697731 3150
+pf_guest 279349 0
+remote_tlb_flush 5 0
+request_irq 0 0
+signal_exits 1 0
+tlb_flush 200190 0
+</pre><div class="variablelist"><h6>Explanation of variables:</h6><dl class="variablelist"><dt class="varlistentry"><span class="term">efer_reload</span></dt><dd><div class="para">
+ The number of Extended Feature Enable Register (EFER) reloads.
+ </div></dd><dt class="varlistentry"><span class="term">exits</span></dt><dd><div class="para">
+ The count of all <code class="computeroutput">VMEXIT</code> calls.
+ </div></dd><dt class="varlistentry"><span class="term">fpu_reload</span></dt><dd><div class="para">
+ The number of times a <code class="computeroutput">VMENTRY</code> reloaded the FPU state. The <code class="command">fpu_reload</code> is incremented when a guest is using the Floating Point Unit (FPU).
+ </div></dd><dt class="varlistentry"><span class="term">halt_exits</span></dt><dd><div class="para">
+ Number of guest exits due to <code class="computeroutput">halt</code> calls. This type of exit is usually seen when a guest is idle.
+ </div></dd><dt class="varlistentry"><span class="term">halt_wakeup</span></dt><dd><div class="para">
+ Number of wakeups from a <code class="computeroutput">halt</code>.
+ </div></dd><dt class="varlistentry"><span class="term">host_state_reload</span></dt><dd><div class="para">
+ Count of full reloads of the host state (currently tallies MSR setup and guest MSR reads).
+ </div></dd><dt class="varlistentry"><span class="term">hypercalls</span></dt><dd><div class="para">
+ Number of guest hypervisor service calls.
+ </div></dd><dt class="varlistentry"><span class="term">insn_emulation</span></dt><dd><div class="para">
+ Number of guest instructions emulated by the host.
+ </div></dd><dt class="varlistentry"><span class="term">insn_emulation_fail</span></dt><dd><div class="para">
+ Number of failed <code class="computeroutput">insn_emulation</code> attempts.
+ </div></dd><dt class="varlistentry"><span class="term">io_exits</span></dt><dd><div class="para">
+ Number of guest exits from I/O port accesses.
+ </div></dd><dt class="varlistentry"><span class="term">irq_exits</span></dt><dd><div class="para">
+ Number of guest exits due to external interrupts.
+ </div></dd><dt class="varlistentry"><span class="term">irq_injections</span></dt><dd><div class="para">
+ Number of interrupts sent to guests.
+ </div></dd><dt class="varlistentry"><span class="term">irq_window</span></dt><dd><div class="para">
+ Number of guest exits from an outstanding interrupt window.
+ </div></dd><dt class="varlistentry"><span class="term">largepages</span></dt><dd><div class="para">
+ Number of large pages currently in use.
+ </div></dd><dt class="varlistentry"><span class="term">mmio_exits</span></dt><dd><div class="para">
+ Number of guest exits due to memory mapped I/O (MMIO) accesses.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_cache_miss</span></dt><dd><div class="para">
+ Number of KVM MMU shadow pages created.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_flooded</span></dt><dd><div class="para">
+ Detection count of excessive write operations to an MMU page. This counts detected write operations not of individual write operations.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_pde_zapped</span></dt><dd><div class="para">
+ Number of page directory entry (PDE) destruction operations.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_pte_updated</span></dt><dd><div class="para">
+ Number of page table entry (PTE) destruction operations.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_pte_write</span></dt><dd><div class="para">
+ Number of guest page table entry (PTE) write operations.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_recycled</span></dt><dd><div class="para">
+ Number of shadow pages that can be reclaimed.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_shadow_zapped</span></dt><dd><div class="para">
+ Number of invalidated shadow pages.
+ </div></dd><dt class="varlistentry"><span class="term">mmu_unsync</span></dt><dd><div class="para">
+ Number of non-synchronized pages which are not yet unlinked.
+ </div></dd><dt class="varlistentry"><span class="term">nmi_injections</span></dt><dd><div class="para">
+ Number of Non-maskable Interrupt (NMI) injections to the guest.
+ </div></dd><dt class="varlistentry"><span class="term">nmi_window</span></dt><dd><div class="para">
+ Number of guest exits from (outstanding) Non-maskable Interrupt (NMI) windows.
+ </div></dd><dt class="varlistentry"><span class="term">pf_fixed</span></dt><dd><div class="para">
+ Number of fixed (non-paging) page table entry (PTE) maps.
+ </div></dd><dt class="varlistentry"><span class="term">pf_guest</span></dt><dd><div class="para">
+ Number of page faults injected into guests.
+ </div></dd><dt class="varlistentry"><span class="term">remote_tlb_flush</span></dt><dd><div class="para">
+ Number of remote (sibling CPU) Translation Lookaside Buffer (TLB) flush requests.
+ </div></dd><dt class="varlistentry"><span class="term">request_irq</span></dt><dd><div class="para">
+ Number of guest interrupt window request exits.
+ </div></dd><dt class="varlistentry"><span class="term">signal_exits</span></dt><dd><div class="para">
+ Number of guest exits due to pending signals from the host.
+ </div></dd><dt class="varlistentry"><span class="term">tlb_flush</span></dt><dd><div class="para">
+ Number of <code class="computeroutput">tlb_flush</code> operations performed by the hypervisor.
+ </div></dd></dl></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The output information from the <code class="command">kvm_stat</code> command is exported by the KVM hypervisor as pseudo files located in the <code class="filename">/sys/kernel/debug/kvm/</code> directory.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Troubleshooting.html"><strong>Prev</strong>Appendix A. 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-Troubleshooting_-Troubleshooting_with_serial_consoles.html"><strong>Next</strong>A.3. Troubleshooting with serial consoles</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apas04.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apas04.html
new file mode 100644
index 0000000..c0c395b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apas04.html
@@ -0,0 +1,14 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.4. Virtualization log files</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Troubleshooting.html" title="Appendix A. Troubleshooting" /><link rel="prev" href="sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles.html" title="A.3. Troubleshooting with serial consoles" /><link rel="next" href="sect-Virtualization-Troubleshooting-Loop_device_errors.html" title="A.5. Loop device errors" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="Doc
umentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Troubleshooting-Loop_device_errors.html"><strong>Next</strong></a></li></ul><div class="section" id="idm4711968"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm4711968">A.4. Virtualization log files</h2></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Each fully virtualized guest log is in the <code class="filename">/var/log/libvirt/qemu/</code> directory. Each guest log is named as <em class="replaceable"><code>GuestName</code></em>.log and will be periodically compressed once a size limit is reached.
+ </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">$HOME/.virt-manager</code> directory.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles.html"><strong>Prev</strong>A.3. 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-Troubleshooting-Loop_device_errors.html"><strong>Next</strong>A.5. Loop device errors</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apb.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apb.html
new file mode 100644
index 0000000..bba4c85
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apb.html
@@ -0,0 +1,173 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix B. Common libvirt errors and troubleshooting</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt03.html" title="Part III. Appendicies" /><link rel="prev" href="sec-known-issues-windows-xp-guests.html" title="A.10. Known Windows XP guest issues" /><link rel="next" href="App_Hypervisor_Connection_Fail.html" title="B.2. The URI failed to connect to the hypervisor" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sec-known-is
sues-windows-xp-guests.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="App_Hypervisor_Connection_Fail.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="appendix" id="idp3245424" lang="en-US"><div class="titlepage"><div><div><h1 id="idp3245424" class="title">Common <span class="application"><strong>libvirt</strong></span> errors and troubleshooting</h1></div></div></div><div class="para">
+ This appendix documents common <span class="application"><strong>libvirt</strong></span>-related problems and errors along with instructions for dealing with them.
+ </div><div class="para">
+ Locate the error on the table below and follow the corresponding link under <code class="literal">Solution</code> for detailed troubleshooting information.
+ </div><div class="table"><h6>Table B.1. Common <span class="application">libvirt</span> errors</h6><div class="table-contents"><table summary="Common libvirt errors" border="1"><colgroup><col align="left" class="c1" width="33%" /><col align="left" class="c2" width="33%" /><col align="left" class="c3" width="33%" /></colgroup><thead><tr><th class="" align="left">
+ Error
+ </th><th class="" align="left">
+ Description of problem
+ </th><th class="" align="left">
+ Solution
+ </th></tr></thead><tbody><tr><td class="" align="left">
+ <code class="computeroutput"><span class="application"><strong>libvirtd</strong></span> failed to start</code>
+ </td><td class="" align="left">
+ The <span class="application"><strong>libvirt</strong></span> daemon failed to start. However, there is no information about this error in <code class="filename">/var/log/messages</code>.
+ </td><td class="" align="left">
+ <a class="xref" href="apb.html#App_Libvirt_Daemon">Section B.1, “<span class="application"><strong>libvirtd</strong></span> failed to start”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Cannot read CA certificate</code>
+ </td><td class="" align="left">
+ This is one of several errors that occur when the URI fails to connect to the hypervisor.
+ </td><td class="" align="left">
+ <a class="xref" href="App_Hypervisor_Connection_Fail.html">Section B.2, “The URI failed to connect to the hypervisor”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Failed to connect socket ... : Permission denied</code>
+ </td><td class="" align="left">
+ This is one of several errors that occur when the URI fails to connect to the hypervisor.
+ </td><td class="" align="left">
+ <a class="xref" href="App_Hypervisor_Connection_Fail.html">Section B.2, “The URI failed to connect to the hypervisor”</a>
+ </td></tr><tr><td class="" align="left">
+ Other connectivity errors
+ </td><td class="" align="left">
+ These are other errors that occur when the URI fails to connect to the hypervisor.
+ </td><td class="" align="left">
+ <a class="xref" href="App_Hypervisor_Connection_Fail.html">Section B.2, “The URI failed to connect to the hypervisor”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Internal error guest CPU is not compatible with host CPU</code>
+ </td><td class="" align="left">
+ The guest virtual machine cannot be started because the host and guest processors are different.
+ </td><td class="" align="left">
+ <a class="xref" href="App_Domain_Processor.html">Section B.3, “The guest virtual machine cannot be started: <code class="computeroutput">internal error guest CPU is not compatible with host CPU</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Failed to create domain from vm.xml error: monitor socket did not show up.: Connection refused</code>
+ </td><td class="" align="left">
+ The guest virtual machine (or domain) starting fails and returns this error or similar.
+ </td><td class="" align="left">
+ <a class="xref" href="App_Domain_Monitor_Socket.html">Section B.4, “Guest starting fails with error: <code class="computeroutput">monitor socket did not show up</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Internal error cannot find character device (null)</code>
+ </td><td class="" align="left">
+ This error can occur when attempting to connect a guest's console. It reports that there is no serial console configured for the guest virtual machine.
+ </td><td class="" align="left">
+ <a class="xref" href="App_Domain_Console.html">Section B.5, “<code class="computeroutput">Internal error cannot find character device (null)</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">No boot device</code>
+ </td><td class="" align="left">
+ After building a guest virtual machine from an existing disk image, the guest booting stalls. However, the guest can start successfully using the <code class="command">QEMU</code> command directly.
+ </td><td class="" align="left">
+ <a class="xref" href="App_Domain_Not_Booting.html">Section B.6, “Guest virtual machine booting stalls with error: <code class="computeroutput">No boot device</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">The virtual network <em class="replaceable"><code>"default"</code></em> has not been started</code>
+ </td><td class="" align="left">
+ <div class="para">
+ If the <em class="replaceable"><code>default</code></em> network (or other locally-created network) is unable to start, any virtual machine configured to use that network for its connectivity will also fail to start.
+ </div>
+ </td><td class="" align="left">
+ <a class="xref" href="App_Virt_Net_Not_Starting.html">Section B.7, “Virtual network <em class="replaceable"><code>default</code></em> has not been started”</a>
+ </td></tr><tr><td class="" align="left">
+ PXE boot (or DHCP) on guest failed
+ </td><td class="" align="left">
+ A guest virtual machine starts successfully, but is unable to acquire an IP address from DHCP, boot using the PXE protocol, or both. This is often a result of a long forward delay time set for the bridge, or when the <span class="package">iptables</span> package and kernel do not support checksum mangling rules.
+ </td><td class="" align="left">
+ <a class="xref" href="App_PXE_Guest_Boot_Fail.html">Section B.8, “PXE boot (or DHCP) on guest failed”</a>
+ </td></tr><tr><td class="" align="left">
+ Guest can reach outside network, but cannot reach host when using macvtap interface
+ </td><td class="" align="left">
+ <div class="para">
+ A guest can communicate with other guests, but cannot connect to the host machine after being configured to use a macvtap (or <em class="parameter"><code>type='direct'</code></em>) network interface.
+ </div>
+ <div class="para">
+ This is actually not an error — it is the defined behavior of macvtap.
+ </div>
+ </td><td class="" align="left">
+ <a class="xref" href="App_Macvtap.html">Section B.9, “Guest can reach outside network, but cannot reach host when using macvtap interface”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Could not add rule to fixup DHCP response checksums on network <em class="replaceable"><code>'default'</code></em></code>
+ </td><td class="" align="left">
+ This warning message is almost always harmless, but is often mistakenly seen as evidence of a problem.
+ </td><td class="" align="left">
+ <a class="xref" href="App_DHCP_Response_Checksums.html">Section B.10, “Could not add rule to fixup DHCP response checksums on network <em class="replaceable"><code>'default'</code></em>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Unable to add bridge br0 port vnet0: No such device</code>
+ </td><td class="" align="left">
+ This error message or the similar <code class="computeroutput">Failed to add tap interface to bridge <em class="replaceable"><code>'br0'</code></em>: No such device</code> reveal that the bridge device specified in the guest's (or domain's) <code class="code"><interface></code> definition does not exist.
+ </td><td class="" align="left">
+ <a class="xref" href="App_Bridge_Device.html">Section B.11, “Unable to add bridge br0 port vnet0: No such device”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Warning: could not open /dev/net/tun: no virtual network emulation qemu-kvm: -netdev tap,script=/etc/my-qemu-ifup,id=hostnet0: Device 'tap' could not be initialized</code>
+ </td><td class="" align="left">
+ The guest virtual machine does not start after configuring a <code class="code">type='ethernet'</code> (or 'generic ethernet') interface in the host system. This error or similar appears either in <code class="filename">libvirtd.log</code>, <code class="filename">/var/log/libvirt/qemu/<em class="replaceable"><code>name_of_guest</code></em>.log</code>, or in both.
+ </td><td class="" align="left">
+ <a class="xref" href="App_Generic_Ethernet.html">Section B.12, “Guest is unable to start with error: <code class="computeroutput">warning: could not open /dev/net/tun</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Unable to resolve address <em class="replaceable"><code>name_of_host</code></em> service '49155': Name or service not known</code>
+ </td><td class="" align="left">
+ <span class="application"><strong>QEMU</strong></span> guest migration fails and this error message appears with an unfamiliar hostname.
+ </td><td class="" align="left">
+ <a class="xref" href="App_Migration_Address.html">Section B.13, “Migration fails with <code class="computeroutput">Error: unable to resolve address</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Unable to allow access for disk path /var/lib/libvirt/images/qemu.img: No such file or directory</code>
+ </td><td class="" align="left">
+ A guest virtual machine cannot be migrated because <span class="application"><strong>libvirt</strong></span> cannot access the disk image(s).
+ </td><td class="" align="left">
+ <a class="xref" href="App_Migration_Disk_Image.html">Section B.14, “Migration fails with <code class="computeroutput">Unable to allow access for disk path: No such file or directory</code>”</a>
+ </td></tr><tr><td class="" align="left">
+ No guest virtual machines are present when <span class="application"><strong>libvirtd</strong></span> is started
+ </td><td class="" align="left">
+ The <span class="application"><strong>libvirt</strong></span> daemon is successfully started, but no guest virtual machines appear to be present when running <code class="command">virsh list --all</code>.
+ </td><td class="" align="left">
+ <a class="xref" href="App_No_Guest_Machines.html">Section B.15, “No guest virtual machines are present when <span class="application"><strong>libvirtd</strong></span> is started”</a>
+ </td></tr><tr><td class="" align="left">
+ <code class="computeroutput">Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor</code>
+ </td><td class="" align="left">
+ While <span class="application"><strong>libvirtd</strong></span> should listen on TCP ports for connections, the connection to the hypervisor fails.
+ </td><td class="" align="left">
+ <a class="xref" href="App_TCP_Ports.html">Section B.16, “Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor”</a>
+ </td></tr><tr><td class="" align="left">
+ Common XML errors
+ </td><td class="" align="left">
+ <span class="application"><strong>libvirt</strong></span> uses XML documents to store structured data. Several common errors occur with XML documents when they are passed to <span class="application"><strong>libvirt</strong></span> through the API. This entry provides instructions for editing guest XML definitions, and details common errors in XML syntax and configuration.
+ </td><td class="" align="left">
+ <a class="xref" href="App_XML_Errors.html">Section B.17, “Common XML errors”</a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div xml:lang="en-US" class="section" id="App_Libvirt_Daemon" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">B.1. <span class="application"><strong>libvirtd</strong></span> failed to start</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The <span class="application"><strong>libvirt</strong></span> daemon does not start automatically. Starting the <span class="application"><strong>libvirt</strong></span> daemon manually fails as well:
+ </div><pre class="screen"># /etc/init.d/libvirtd start
+* Caching service dependencies ... [ ok ]
+* Starting libvirtd ...
+/usr/sbin/libvirtd: error: Unable to initialize network sockets. Check /var/log/messages or run without --daemon for more info.
+* start-stop-daemon: failed to start `/usr/sbin/libvirtd' [ !! ]
+* ERROR: libvirtd failed to start</pre><div class="para">
+ Moreover, there is not <code class="literal">'more info'</code> about this error in <code class="filename">/var/log/messages</code>.
+ </div></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ Change <span class="application"><strong>libvirt's</strong></span> logging in <code class="filename">/etc/libvirt/libvirtd.conf</code> by uncommenting the line below. To uncomment the line, open the <code class="filename">/etc/libvirt/libvirtd.conf</code> file in a text editor, remove the hash (or <code class="literal">#</code>) symbol from the beginning of the following line, and save the change:
+ </div><pre class="screen">log_outputs="3:syslog:libvirtd"</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ This line is commented out by default to prevent <span class="application"><strong>libvirt</strong></span> from producing excessive log messages. After diagnosing the problem, it is recommended to comment this line again in the <code class="filename">/etc/libvirt/libvirtd.conf</code> file.
+ </div></div></div><div class="para">
+ Restart <span class="application"><strong>libvirt</strong></span> to determine if this has solved the problem.
+ </div><div class="para">
+ If <code class="filename">libvirtd</code> still does not start successfully, an error similar to the following will be shown in the <code class="filename">/var/log/messages</code> file:
+ </div><pre class="programlisting">Feb 6 17:22:09 bart libvirtd: 17576: info : libvirt version: 0.9.9
+Feb 6 17:22:09 bart libvirtd: 17576: error : virNetTLSContextCheckCertFile:92: Cannot read CA certificate '/etc/pki/CA/cacert.pem': No such file or directory
+Feb 6 17:22:09 bart /etc/init.d/libvirtd[17573]: start-stop-daemon: failed to start `/usr/sbin/libvirtd'
+Feb 6 17:22:09 bart /etc/init.d/libvirtd[17565]: ERROR: libvirtd failed to start</pre><div class="para">
+ The <span class="application"><strong>libvirtd</strong></span> man page shows that the missing <code class="filename">cacert.pem</code> file is used as TLS authority when <span class="application"><strong>libvirt</strong></span> is run in <code class="literal">Listen for TCP/IP connections</code> mode. This means the <em class="parameter"><code>--listen</code></em> parameter is being passed.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Configure the <span class="application"><strong>libvirt</strong></span> daemon's settings with one of the following methods:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Install a CA certificate.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ For more information on CA certificates and configuring system authentication, refer to the Configuring Authentication chapter in the <em class="citetitle">Fedora Deployment Guide</em>.
+ </div></div></div></li><li class="listitem"><div class="para">
+ Do not use TLS; use bare TCP instead. In <code class="filename">/etc/libvirt/libvirtd.conf</code> set <code class="option">listen_tls = 0</code> and <code class="option">listen_tcp = 1</code>. The default values are <code class="option">listen_tls = 1</code> and <code class="option">listen_tcp = 0</code>.
+ </div></li><li class="listitem"><div class="para">
+ Do not pass the <em class="parameter"><code>--listen</code></em> parameter. In <code class="filename">/etc/sysconfig/libvirtd.conf</code> change the <em class="parameter"><code>LIBVIRTD_ARGS</code></em> variable.
+ </div></li></ul></div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-known-issues-windows-xp-guests.html"><strong>Prev</strong>A.10. Known Windows XP guest issues</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="App_Hypervisor_Connection_Fail.html"><strong>Next</strong>B.2. The URI failed to connect to the hypervisor</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apbs17s02.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apbs17s02.html
new file mode 100644
index 0000000..e46b22c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apbs17s02.html
@@ -0,0 +1,38 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.17.2. XML syntax errors</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="App_XML_Errors.html" title="B.17. Common XML errors" /><link rel="prev" href="App_XML_Errors.html" title="B.17. Common XML errors" /><link rel="next" href="apbs17s02s02.html" title="B.17.2.2. Unterminated attribute" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="App_XML_Errors.html"><strong>Prev</strong></a></li><li class="next"
><a accesskey="n" href="apbs17s02s02.html"><strong>Next</strong></a></li></ul><div class="section" id="idp15791936"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idp15791936">B.17.2. XML syntax errors</h3></div></div></div><div class="para">
+ Syntax errors are caught by the XML parser. The error message contains information for identifying the problem.
+ </div><div class="para">
+ This example error message from the XML parser consists of three lines — the first line denotes the error message, and the two following lines contain the context and location of the XML code containing the error. The third line contains an indicator showing approximately where the error lies on the line above it:
+ </div><pre class="screen">error: (<em class="replaceable"><code>name_of_guest.xml</code></em>):6: StartTag: invalid element name
+<vcpu>2</vcpu><
+-----------------^</pre><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Information contained in this message:</span></dt><dd><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">(<em class="replaceable"><code>name_of_guest.xml</code></em>)</span></dt><dd><div class="para">
+ This is the file name of the document that contains the error. File names in parentheses are symbolic names to describe XML documents parsed from memory, and do not directly correspond to files on disk. File names that are not contained in parentheses are local files that reside on the target of the connection.
+ </div></dd><dt class="varlistentry"><span class="term">6</span></dt><dd><div class="para">
+ This is the line number in the XML file that contains the error.
+ </div></dd><dt class="varlistentry"><span class="term">StartTag: invalid element name </span></dt><dd><div class="para">
+ This is the error message from the <span class="application"><strong>libxml2</strong></span> parser, which describes the specific XML error.
+ </div></dd></dl></div></dd></dl></div><div class="section" id="idp24928720"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idp24928720">B.17.2.1. Stray <code class="literal"><</code> in the document</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The following error occurs:
+ </div><pre class="screen">error: (<em class="replaceable"><code>name_of_guest.xml</code></em>):6: StartTag: invalid element name
+<vcpu>2</vcpu><
+-----------------^</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This error message shows that the parser expects a new element name after the <code class="literal"><</code> symbol on line 6 of a guest's XML file.
+ </div><div class="para">
+ Ensure line number display is enabled in your text editor. Open the XML file, and locate the text on line 6:
+ </div><pre class="screen"><domain type='kvm'>
+ <name><em class="replaceable"><code>name_of_guest</code></em></name>
+<memory>524288</memory>
+<vcpu>2</vcpu><
+</pre><div class="para">
+ This snippet of a guest's XML file contains an extra <code class="literal"><</code> in the document:
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Remove the extra <code class="literal"><</code> or finish the new element.
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="App_XML_Errors.html"><strong>Prev</strong>B.17. Common XML 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="apbs17s02s02.html"><strong>Next</strong>B.17.2.2. Unterminated attribute</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apbs17s02s02.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apbs17s02s02.html
new file mode 100644
index 0000000..cae13a7
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apbs17s02s02.html
@@ -0,0 +1,21 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.17.2.2. Unterminated attribute</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apbs17s02.html" title="B.17.2. XML syntax errors" /><link rel="prev" href="apbs17s02.html" title="B.17.2. XML syntax errors" /><link rel="next" href="apbs17s02s03.html" title="B.17.2.3. Opening and ending tag mismatch" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="apbs17s02.html"><strong>Prev</strong></a></li><li class="next"><
a accesskey="n" href="apbs17s02s03.html"><strong>Next</strong></a></li></ul><div class="section" id="idp12183440"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idp12183440">B.17.2.2. Unterminated attribute</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The following error occurs:
+ </div><pre class="screen">error: (<em class="replaceable"><code>name_of_guest.xml</code></em>):2: Unescaped '<' not allowed in attributes values
+<name><em class="replaceable"><code>name_of_guest</code></em></name>
+--^</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This snippet of a guest's XML file contains an unterminated element attribute value:
+ </div><pre class="screen"><domain type='kvm>
+<name><em class="replaceable"><code>name_of_guest</code></em></name></pre><div class="para">
+ In this case, <code class="literal">'kvm'</code> is missing a second quotation mark. Strings of attribute values, such as quotation marks and apostrophes, must be opened and closed, similar to XML start and end tags.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Correctly open and close all attribute value strings.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apbs17s02.html"><strong>Prev</strong>B.17.2. XML syntax 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="apbs17s02s03.html"><strong>Next</strong>B.17.2.3. Opening and ending tag mismatch</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apbs17s02s03.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apbs17s02s03.html
new file mode 100644
index 0000000..af04094
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apbs17s02s03.html
@@ -0,0 +1,41 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.17.2.3. Opening and ending tag mismatch</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apbs17s02.html" title="B.17.2. XML syntax errors" /><link rel="prev" href="apbs17s02s02.html" title="B.17.2.2. Unterminated attribute" /><link rel="next" href="apbs17s02s04.html" title="B.17.2.4. Typographical errors in tags" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="apbs17s02s02.html"><strong>Prev</strong></a></li><li clas
s="next"><a accesskey="n" href="apbs17s02s04.html"><strong>Next</strong></a></li></ul><div class="section" id="idm3318480"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm3318480">B.17.2.3. Opening and ending tag mismatch</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The following error occurs:
+ </div><pre class="screen">error: (<em class="replaceable"><code>name_of_guest.xml</code></em>):61: Opening and ending tag mismatch: clock line 16 and domain
+</domain>
+---------^</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ The error message above contains three clues to identify the offending tag:
+ </div><div class="para">
+ The message following the last colon, <code class="literal">clock line 16 and domain</code>, reveals that <code class="literal"><clock></code> contains a mismatched tag on line 16 of the document. The last hint is the pointer in the context part of the message, which identifies the second offending tag.
+ </div><div class="para">
+ Unpaired tags must be closed with <code class="literal">/></code>. The following snippet does not follow this rule and has produced the error message shown above:
+ </div><pre class="screen"><domain type='kvm'>
+ ...
+ <clock offset='utc'></pre><div class="para">
+ This error is caused by mismatched XML tags in the file. Every XML tag must have a matching start and end tag.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Other examples of mismatched XML tags</span></dt><dd><div class="para">
+ The following examples produce similar error messages and show variations of mismatched XML tags.
+ </div><div class="para">
+ This snippet contains an unended pair tag for <code class="literal"><features></code>:
+ </div><pre class="screen"><domain type='kvm'>
+ ...
+ <features>
+ <acpi/>
+ <pae/>
+ ...
+ </domain></pre><div class="para">
+ This snippet contains an end tag (<code class="literal"></name></code>) without a corresponding start tag:
+ </div><pre class="screen"><domain type='kvm'>
+ </name>
+ ...
+</domain></pre></dd></dl></div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Ensure all XML tags start and end correctly.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apbs17s02s02.html"><strong>Prev</strong>B.17.2.2. Unterminated attribute</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="apbs17s02s04.html"><strong>Next</strong>B.17.2.4. Typographical errors in tags</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apbs17s02s04.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apbs17s02s04.html
new file mode 100644
index 0000000..dc6335a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apbs17s02s04.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.17.2.4. Typographical errors in tags</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apbs17s02.html" title="B.17.2. XML syntax errors" /><link rel="prev" href="apbs17s02s03.html" title="B.17.2.3. Opening and ending tag mismatch" /><link rel="next" href="apbs17s03.html" title="B.17.3. Logic and configuration errors" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="apbs17s02s03.html"><strong>Prev</strong></a></li><l
i class="next"><a accesskey="n" href="apbs17s03.html"><strong>Next</strong></a></li></ul><div class="section" id="idp1208000"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idp1208000">B.17.2.4. Typographical errors in tags</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The following error message appears:
+ </div><pre class="screen">error: (name_of_guest.xml):1: Specification mandate value for attribute ty
+<domain ty pe='kvm'>
+-----------^</pre></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ XML errors are easily caused by a simple typographical error. This error message highlights the XML error — in this case, an extra white space within the word <code class="literal">type</code> — with a pointer.
+ </div><pre class="screen"><domain ty pe='kvm'></pre><div class="para">
+ These XML examples will not parse correctly because of typographical errors such as a missing special character, or an additional character:
+ </div><pre class="screen"><domain type 'kvm'></pre><pre class="screen"><dom#ain type='kvm'></pre></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ To identify the problematic tag, read the error message for the context of the file, and locate the error with the pointer. Correct the XML and save the changes.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apbs17s02s03.html"><strong>Prev</strong>B.17.2.3. Opening and ending tag mismatch</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="apbs17s03.html"><strong>Next</strong>B.17.3. Logic and configuration errors</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apbs17s03.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apbs17s03.html
new file mode 100644
index 0000000..575e2e2
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apbs17s03.html
@@ -0,0 +1,22 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.17.3. Logic and configuration errors</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="App_XML_Errors.html" title="B.17. Common XML errors" /><link rel="prev" href="apbs17s02s04.html" title="B.17.2.4. Typographical errors in tags" /><link rel="next" href="apbs17s03s02.html" title="B.17.3.2. Incorrect drive device type" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="apbs17s02s04.html"><strong>Prev</strong></a></li>
<li class="next"><a accesskey="n" href="apbs17s03s02.html"><strong>Next</strong></a></li></ul><div class="section" id="idm245472"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm245472">B.17.3. Logic and configuration errors</h3></div></div></div><div class="para">
+ A well-formatted XML document can contain errors that are correct in syntax but <span class="application"><strong>libvirt</strong></span> cannot parse. Many of these errors exist, with two of the most common cases outlined below.
+ </div><div class="section" id="idm6612336"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm6612336">B.17.3.1. Vanishing parts</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ Parts of the change you have made do not show up and have no effect after editing or defining the domain. The <code class="command">define</code> or <code class="command">edit</code> command works, but when dumping the XML once again, the change disappears.
+ </div></dd><dt class="varlistentry"><span class="term">Investigation</span></dt><dd><div class="para">
+ This error likely results from a broken construct or syntax that libvirt does not parse. The <span class="application"><strong>libvirt</strong></span> tool will generally only look for constructs it knows but ignore everything else, resulting in some of the XML changes vanishing after <span class="application"><strong>libvirt</strong></span> parses the input.
+ </div></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Validate the XML input before passing it to the <code class="command">edit</code> or <code class="command">define</code> commands. The <span class="application"><strong>libvirt</strong></span> developers maintain a set of XML schemas bundled with <span class="application"><strong>libvirt</strong></span> which define the majority of the constructs allowed in XML documents used by <span class="application"><strong>libvirt</strong></span>.
+ </div><div class="para">
+ Validate <span class="application"><strong>libvirt</strong></span> XML files using the following command:
+ </div><pre class="screen"># virt-xml-validate libvirt.xml</pre><div class="para">
+ If this command passes, <span class="application"><strong>libvirt</strong></span> will likely understand all constructs from your XML, except if the schemas cannot detect options which are valid only for a given hypervisor. Any XML generated by <span class="application"><strong>libvirt</strong></span> as a result of a <code class="command">virsh dump</code> command, for example, should validate without error.
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apbs17s02s04.html"><strong>Prev</strong>B.17.2.4. Typographical errors in tags</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="apbs17s03s02.html"><strong>Next</strong>B.17.3.2. Incorrect drive device type</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apbs17s03s02.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apbs17s03s02.html
new file mode 100644
index 0000000..c28bb98
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apbs17s03s02.html
@@ -0,0 +1,30 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>B.17.3.2. Incorrect drive device type</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="apbs17s03.html" title="B.17.3. Logic and configuration errors" /><link rel="prev" href="apbs17s03.html" title="B.17.3. Logic and configuration errors" /><link rel="next" href="netkvm-parameters.html" title="Appendix C. NetKVM Driver Parameters" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="apbs17s03.html"><strong>Prev</strong>
</a></li><li class="next"><a accesskey="n" href="netkvm-parameters.html"><strong>Next</strong></a></li></ul><div class="section" id="idm12376240"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm12376240">B.17.3.2. Incorrect drive device type</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Symptom</span></dt><dd><div class="para">
+ The definition of the source image for the CD-ROM virtual drive is not present, despite being added:
+ </div><pre class="screen"># virsh dumpxml domain
+<domain type='kvm'>
+ ...
+ <disk type='block' device='cdrom'>
+ <driver name='qemu' type='raw'/>
+ <target dev='hdc' bus='ide'/>
+ <readonly/>
+ </disk>
+ ...
+</domain></pre></dd><dt class="varlistentry"><span class="term">Solution</span></dt><dd><div class="para">
+ Correct the XML by adding the missing <code class="code"><source></code> parameter as follows:
+ </div><pre class="screen"><disk type='block' device='cdrom'>
+ <driver name='qemu' type='raw'/>
+ <source file='/path/to/image.iso'/>
+ <target dev='hdc' bus='ide'/>
+ <readonly/>
+</disk></pre><div class="para">
+ A <code class="code">type='block'</code> disk device expects that the source is a physical device. To use the disk with an image file, use <code class="code">type='file'</code> instead.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apbs17s03.html"><strong>Prev</strong>B.17.3. Logic and configuration 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="netkvm-parameters.html"><strong>Next</strong>Appendix C. NetKVM Driver Parameters</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds02.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds02.html
new file mode 100644
index 0000000..89b91ce
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds02.html
@@ -0,0 +1,62 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>D.2. Basic options</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html" title="Appendix D. qemu-kvm Whitelist" /><link rel="prev" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html" title="Appendix D. qemu-kvm Whitelist" /><link rel="next" href="apds03.html" title="D.3. Disk options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 ac
cesskey="p" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apds03.html"><strong>Next</strong></a></li></ul><div class="section" id="idp15454048"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp15454048">D.2. Basic options</h2></div></div></div><h4 id="idm17696656">Emulated machine</h4><div class="para">
+ <span class="application"><strong>-M</strong></span> <machine-type>
+ </div><h4 id="idm21115136">Processor type</h4><div class="para">
+ <span class="application"><strong>-cpu</strong></span> <model>[,<FEATURE>][...]
+ </div><div class="para">
+ We support exposing additional features and placing restrictions. Supported models are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>Opteron_G5</strong></span> - AMD Opteron 63xx class CPU
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Opteron_G4</strong></span> - AMD Opteron 62xx class CPU
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Opteron_G3</strong></span> - AMD Opteron 23xx (AMD Opteron Gen 3)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Opteron_G2</strong></span> - AMD Opteron 22xx (AMD Opteron Gen 2)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Opteron_G1</strong></span> - AMD Opteron 240 (AMD Opteron Gen 1)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Westmere</strong></span> - Westmere E56xx/L56xx/X56xx (Nehalem-C)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Haswell</strong></span> - Intel Core Processor (Haswell)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>SandyBridge</strong></span> - Intel Xeon E312xx (Sandy Bridge)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Nehalem</strong></span> - Intel Core i7 9xx (Nehalem Class Core i7)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Penryn</strong></span> - Intel Core 2 Duo P9xxx (Penryn Class Core 2)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>Conroe</strong></span> - Intel Celeron_4x0 (Conroe/Merom Class Core 2)
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>cpu64-rhel5</strong></span> - Red Hat Enterprise Linux 5 supported QEMU Virtual CPU version
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>cpu64-rhel6</strong></span> - Red Hat Enterprise Linux 6 supported QEMU Virtual CPU version
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>default</strong></span> - special option use default option from above.
+ </div></li></ul></div><h4 id="idm6650384">Processor Topology</h4><div class="para">
+ <span class="application"><strong>-smp</strong></span> <n>[,cores=<ncores>][,threads=<nthreads>][,sockets=<nsocks>][,maxcpus=<maxcpus>]
+ </div><div class="para">
+ Hypervisor and guest operating system limits on processor topology apply.
+ </div><h4 id="idp9769056">NUMA system</h4><div class="para">
+ <span class="application"><strong>-numa</strong></span> <nodes>[,mem=<size>][,cpus=<cpu[-cpu>]][,nodeid=<node>]
+ </div><div class="para">
+ Hypervisor and guest operating system limits on processor topology apply.
+ </div><h4 id="idp9771104">Memory size</h4><div class="para">
+ <span class="application"><strong>-m</strong></span> <megs>
+ </div><div class="para">
+ Supported values are limited by guest minimal and maximal values and hypervisor limits.
+ </div><h4 id="idp4640096">Keyboard layout</h4><div class="para">
+ <span class="application"><strong>-k</strong></span> <language>
+ </div><h4 id="idp4641728">Guest name</h4><div class="para">
+ <span class="application"><strong>-name</strong></span> <name>
+ </div><h4 id="idp4782352">Guest UUID</h4><div class="para">
+ <span class="application"><strong>-uuid</strong></span> <uuid>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html"><strong>Prev</strong>Appendix D. qemu-kvm Whitelist</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="apds03.html"><strong>Next</strong>D.3. Disk options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds03.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds03.html
new file mode 100644
index 0000000..553337b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds03.html
@@ -0,0 +1,72 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>D.3. Disk options</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html" title="Appendix D. qemu-kvm Whitelist" /><link rel="prev" href="apds02.html" title="D.2. Basic options" /><link rel="next" href="apds04.html" title="D.4. Display options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="apds02.html"><strong>Prev</strong></a></li><l
i class="next"><a accesskey="n" href="apds04.html"><strong>Next</strong></a></li></ul><div class="section" id="idp4784144"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp4784144">D.3. Disk options</h2></div></div></div><h4 id="idp4784944">Generic drive</h4><div class="para">
+ <span class="application"><strong>-drive</strong></span> <option>[,<option>[,<option>[,...]]]
+ </div><div class="para">
+ Supported with the following options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>readonly</strong></span>[on|off]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>werror</strong></span>[enospc|report|stop|ignore]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>rerror</strong></span>[report|stop|ignore]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>id</strong></span>=<id>
+ </div><div class="para">
+ Id of the drive has the following limitaton for if=none:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ IDE disk has to have <id> in following format: drive-ide0-<BUS>-<UNIT>
+ </div><div class="para">
+ Example of correct format:
+ </div><div class="para">
+ -drive if=none,id=drive-ide0-<BUS>-<UNIT>,... -device ide-drive,drive=drive-ide0-<BUS>-<UNIT>,bus=ide.<BUS>,unit=<UNIT>
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>file</strong></span>=<file>
+ </div><div class="para">
+ Value of <file> is parsed with the following rules:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Passing floppy device as <file> is not supported.
+ </div></li><li class="listitem"><div class="para">
+ Passing cd-rom device as <file> is supported only with cdrom media type (media=cdrom) and only as IDE drive (either if=ide or if=none + -device ide-drive).
+ </div></li><li class="listitem"><div class="para">
+ If <file> is neither block nor character device, it must not contain ':'.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>if</strong></span>=<interface>
+ </div><div class="para">
+ The following interfaces are supported: none, ide, virtio, floppy.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>index</strong></span>=<index>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>media</strong></span>=<media>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>cache</strong></span>=<cache>
+ </div><div class="para">
+ Supported values: none, writeback or writethrough.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>copy-on-read</strong></span>=[on|off]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>snapshot</strong></span>=[yes|no]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>serial</strong></span>=<serial>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>aio</strong></span>=<aio>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>format</strong></span>=<format>
+ </div><div class="para">
+ This option is not required and can be omitted. However, this is not recommended for raw images because it represents security risk. Supported formats are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>qcow2</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>raw</strong></span>
+ </div></li></ul></div></li></ul></div><h4 id="idp25593712">Boot option</h4><div class="para">
+ <span class="application"><strong>-boot</strong></span> [order=<drives>][,menu=[on|off]]
+ </div><h4 id="idp25595312">Snapshot mode</h4><div class="para">
+ <span class="application"><strong>-snapshot</strong></span>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apds02.html"><strong>Prev</strong>D.2. Basic options</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="apds04.html"><strong>Next</strong>D.4. Display options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds04.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds04.html
new file mode 100644
index 0000000..e7a104e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds04.html
@@ -0,0 +1,106 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>D.4. Display options</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html" title="Appendix D. qemu-kvm Whitelist" /><link rel="prev" href="apds03.html" title="D.3. Disk options" /><link rel="next" href="apds05.html" title="D.5. Network options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="apds03.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="apds05.html"><strong>Next</strong></a></li></ul><div class="section" id="idp25597104"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp25597104">D.4. Display options</h2></div></div></div><h4 id="idp25597904">Disable graphics</h4><div class="para">
+ <span class="application"><strong>-nographic</strong></span>
+ </div><h4 id="idp18419968">VGA card emulation</h4><div class="para">
+ <span class="application"><strong>-vga</strong></span> <type>
+ </div><div class="para">
+ Supported types:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>cirrus</strong></span> - Cirrus Logic GD5446 Video card.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>std</strong></span> - Standard VGA card with Bochs VBE extensions.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>qxl</strong></span> - Spice paravirtual card.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>none</strong></span> - Disable VGA card.
+ </div></li></ul></div><h4 id="idm12372800">VNC display</h4><div class="para">
+ <span class="application"><strong>-vnc</strong></span> <display>[,<option>[,<option>[,...]]]
+ </div><div class="para">
+ Supported display value:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ [<host>]:<port>
+ </div></li><li class="listitem"><div class="para">
+ unix:<path>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>share</strong></span>[allow-exclusive|force-shared|ignore]
+ </div></li><li class="listitem"><div class="para">
+ none - Supported with no other options specified.
+ </div></li></ul></div><div class="para">
+ Supported options are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>to</strong></span>=<port>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>reverse</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>password</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>tls</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>x509</strong></span>=</path/to/certificate/dir> - Supported when <span class="application"><strong>tls</strong></span> specified.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>x509verify</strong></span>=</path/to/certificate/dir> - Supported when <span class="application"><strong>tls</strong></span> specified.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>sasl</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>acl</strong></span>
+ </div></li></ul></div><h4 id="idm20269280">Spice desktop</h4><div class="para">
+ <span class="application"><strong>-spice</strong></span> option[,option[,...]]
+ </div><div class="para">
+ Supported options are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>port</strong></span>=<number>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>addr</strong></span>=<addr>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>ipv4</strong></span>
+ </div><div class="para">
+ <span class="application"><strong>ipv6</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>password</strong></span>=<secret>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>disable-ticketing</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>disable-copy-paste</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>tls-port</strong></span>=<number>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>x509-dir</strong></span>=</path/to/certificate/dir>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>x509-key-file</strong></span>=<file>
+ </div><div class="para">
+ <span class="application"><strong>x509-key-password</strong></span>=<file>
+ </div><div class="para">
+ <span class="application"><strong>x509-cert-file</strong></span>=<file>
+ </div><div class="para">
+ <span class="application"><strong>x509-cacert-file</strong></span>=<file>
+ </div><div class="para">
+ <span class="application"><strong>x509-dh-key-file</strong></span>=<file>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>tls-cipher</strong></span>=<list>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>tls-channel</strong></span>[main|display|cursor|inputs|record|playback]
+ </div><div class="para">
+ <span class="application"><strong>plaintext-channel</strong></span>[main|display|cursor|inputs|record|playback]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>image-compression</strong></span>=<compress>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>jpeg-wan-compression</strong></span>=<value>
+ </div><div class="para">
+ <span class="application"><strong>zlib-glz-wan-compression</strong></span>=<value>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>streaming-video</strong></span>=[off|all|filter]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>agent-mouse</strong></span>=[on|off]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>playback-compression</strong></span>=[on|off]
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>seamless-migratio</strong></span>=[on|off]
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apds03.html"><strong>Prev</strong>D.3. Disk options</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="apds05.html"><strong>Next</strong>D.5. Network options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds05.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds05.html
new file mode 100644
index 0000000..f9d5c5a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds05.html
@@ -0,0 +1,32 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>D.5. Network options</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html" title="Appendix D. qemu-kvm Whitelist" /><link rel="prev" href="apds04.html" title="D.4. Display options" /><link rel="next" href="apds06.html" title="D.6. Device options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="apds04.html"><strong>Prev</strong></a></li><
li class="next"><a accesskey="n" href="apds06.html"><strong>Next</strong></a></li></ul><div class="section" id="idm17451712"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm17451712">D.5. Network options</h2></div></div></div><h4 id="idm17450912">TAP network</h4><div class="para">
+ <span class="application"><strong>-netdev tap</strong></span>,id=<id>][,<options>...]
+ </div><div class="para">
+ The following options are supported (all use name=value format):
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ ifname
+ </div></li><li class="listitem"><div class="para">
+ fd
+ </div></li><li class="listitem"><div class="para">
+ script
+ </div></li><li class="listitem"><div class="para">
+ downscript
+ </div></li><li class="listitem"><div class="para">
+ sndbuf
+ </div></li><li class="listitem"><div class="para">
+ vnet_hdr
+ </div></li><li class="listitem"><div class="para">
+ vhost
+ </div></li><li class="listitem"><div class="para">
+ vhostfd
+ </div></li><li class="listitem"><div class="para">
+ vhostforce
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apds04.html"><strong>Prev</strong>D.4. Display options</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="apds06.html"><strong>Next</strong>D.6. Device options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds06.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds06.html
new file mode 100644
index 0000000..4de2392
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds06.html
@@ -0,0 +1,458 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>D.6. Device options</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html" title="Appendix D. qemu-kvm Whitelist" /><link rel="prev" href="apds05.html" title="D.5. Network options" /><link rel="next" href="apds07.html" title="D.7. Linux/Multiboot boot" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="apds05.html"><strong>Prev</strong></a>
</li><li class="next"><a accesskey="n" href="apds07.html"><strong>Next</strong></a></li></ul><div class="section" id="idp3249072"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp3249072">D.6. Device options</h2></div></div></div><h4 id="idp3249872">General device</h4><div class="para">
+ <span class="application"><strong>-device</strong></span> <driver>[,<prop>[=<value>][,...]]
+ </div><div class="para">
+ All drivers support following properties
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ id
+ </div></li><li class="listitem"><div class="para">
+ bus
+ </div></li></ul></div><div class="para">
+ Following drivers are supported (with available properties):
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>pci-assign</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ host
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ configfd
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li><li class="listitem"><div class="para">
+ rombar
+ </div></li><li class="listitem"><div class="para">
+ romfile
+ </div></li><li class="listitem"><div class="para">
+ multifunction
+ </div></li></ul></div><div class="para">
+ If the device has multiple functions, all of them need to be assigned to the same guest.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>rtl8139</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ mac
+ </div></li><li class="listitem"><div class="para">
+ netdev
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>e1000</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ mac
+ </div></li><li class="listitem"><div class="para">
+ netdev
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>virtio-net-pci</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ ioeventfd
+ </div></li><li class="listitem"><div class="para">
+ vectors
+ </div></li><li class="listitem"><div class="para">
+ indirect
+ </div></li><li class="listitem"><div class="para">
+ event_idx
+ </div></li><li class="listitem"><div class="para">
+ csum
+ </div></li><li class="listitem"><div class="para">
+ guest_csum
+ </div></li><li class="listitem"><div class="para">
+ gso
+ </div></li><li class="listitem"><div class="para">
+ guest_tso4
+ </div></li><li class="listitem"><div class="para">
+ guest_tso6
+ </div></li><li class="listitem"><div class="para">
+ guest_ecn
+ </div></li><li class="listitem"><div class="para">
+ guest_ufo
+ </div></li><li class="listitem"><div class="para">
+ host_tso4
+ </div></li><li class="listitem"><div class="para">
+ host_tso6
+ </div></li><li class="listitem"><div class="para">
+ host_ecn
+ </div></li><li class="listitem"><div class="para">
+ host_ufo
+ </div></li><li class="listitem"><div class="para">
+ mrg_rxbuf
+ </div></li><li class="listitem"><div class="para">
+ status
+ </div></li><li class="listitem"><div class="para">
+ ctrl_vq
+ </div></li><li class="listitem"><div class="para">
+ ctrl_rx
+ </div></li><li class="listitem"><div class="para">
+ ctrl_vlan
+ </div></li><li class="listitem"><div class="para">
+ ctrl_rx_extra
+ </div></li><li class="listitem"><div class="para">
+ mac
+ </div></li><li class="listitem"><div class="para">
+ netdev
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ x-txtimer
+ </div></li><li class="listitem"><div class="para">
+ x-txburst
+ </div></li><li class="listitem"><div class="para">
+ tx
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>qxl</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ ram_size
+ </div></li><li class="listitem"><div class="para">
+ vram_size
+ </div></li><li class="listitem"><div class="para">
+ revision
+ </div></li><li class="listitem"><div class="para">
+ cmdlog
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>ide-drive</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ unit
+ </div></li><li class="listitem"><div class="para">
+ drive
+ </div></li><li class="listitem"><div class="para">
+ physical_block_size
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ ver
+ </div></li><li class="listitem"><div class="para">
+ wwn
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>virtio-blk-pci</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ class
+ </div></li><li class="listitem"><div class="para">
+ drive
+ </div></li><li class="listitem"><div class="para">
+ logical_block_size
+ </div></li><li class="listitem"><div class="para">
+ physical_block_size
+ </div></li><li class="listitem"><div class="para">
+ min_io_size
+ </div></li><li class="listitem"><div class="para">
+ opt_io_size
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ ioeventfd
+ </div></li><li class="listitem"><div class="para">
+ vectors
+ </div></li><li class="listitem"><div class="para">
+ indirect_desc
+ </div></li><li class="listitem"><div class="para">
+ event_idx
+ </div></li><li class="listitem"><div class="para">
+ scsi
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>isa-debugcon</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>isa-serial</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ index
+ </div></li><li class="listitem"><div class="para">
+ iobase
+ </div></li><li class="listitem"><div class="para">
+ irq
+ </div></li><li class="listitem"><div class="para">
+ chardev
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>virtserialport</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ nr
+ </div></li><li class="listitem"><div class="para">
+ chardev
+ </div></li><li class="listitem"><div class="para">
+ name
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>virtconsole</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ nr
+ </div></li><li class="listitem"><div class="para">
+ chardev
+ </div></li><li class="listitem"><div class="para">
+ name
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>virtio-serial-pci</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ vectors
+ </div></li><li class="listitem"><div class="para">
+ class
+ </div></li><li class="listitem"><div class="para">
+ indirect_desc
+ </div></li><li class="listitem"><div class="para">
+ event_idx
+ </div></li><li class="listitem"><div class="para">
+ max_ports
+ </div></li><li class="listitem"><div class="para">
+ flow_control
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>ES1370</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>AC97</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>intel-hda</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>hda-duplex</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ cad
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>hda-micro</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ cad
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>hda-output</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ cad
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>i6300esb</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>ib700</strong></span> - no properties
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>sga</strong></span> - no properties
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>virtio-balloon-pci</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ indirect_desc
+ </div></li><li class="listitem"><div class="para">
+ event_idx
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-tablet</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ migrate
+ </div></li><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-kbd</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ migrate
+ </div></li><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-mouse</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ migrate
+ </div></li><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-ccid</strong></span> - supported since 6.2
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ port
+ </div></li><li class="listitem"><div class="para">
+ slot
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-host</strong></span> - tech preview since 6.2
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ hostbus
+ </div></li><li class="listitem"><div class="para">
+ hostaddr
+ </div></li><li class="listitem"><div class="para">
+ hostport
+ </div></li><li class="listitem"><div class="para">
+ vendorid
+ </div></li><li class="listitem"><div class="para">
+ productid
+ </div></li><li class="listitem"><div class="para">
+ isobufs
+ </div></li><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-hub</strong></span> - supported since 6.2
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-ehci</strong></span> - tech preview since 6.2
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ freq
+ </div></li><li class="listitem"><div class="para">
+ maxframes
+ </div></li><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-storage</strong></span> - tech preview since 6.2
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ drive
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ serial
+ </div></li><li class="listitem"><div class="para">
+ removable
+ </div></li><li class="listitem"><div class="para">
+ port
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>usb-redir</strong></span> - tech preview since 6.3
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ chardev
+ </div></li><li class="listitem"><div class="para">
+ filter
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>scsi-cd</strong></span> - tech preview for 6.3
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ drive
+ </div></li><li class="listitem"><div class="para">
+ logical_block_size
+ </div></li><li class="listitem"><div class="para">
+ physical_block_size
+ </div></li><li class="listitem"><div class="para">
+ min_io_size
+ </div></li><li class="listitem"><div class="para">
+ opt_io_size
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ ver
+ </div></li><li class="listitem"><div class="para">
+ serial
+ </div></li><li class="listitem"><div class="para">
+ scsi-id
+ </div></li><li class="listitem"><div class="para">
+ lun
+ </div></li><li class="listitem"><div class="para">
+ channel-scsi
+ </div></li><li class="listitem"><div class="para">
+ wwn
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>scsi-hd</strong></span> -tech preview for 6.3
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ drive
+ </div></li><li class="listitem"><div class="para">
+ logical_block_size
+ </div></li><li class="listitem"><div class="para">
+ physical_block_size
+ </div></li><li class="listitem"><div class="para">
+ min_io_size
+ </div></li><li class="listitem"><div class="para">
+ opt_io_size
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ ver
+ </div></li><li class="listitem"><div class="para">
+ serial
+ </div></li><li class="listitem"><div class="para">
+ scsi-id
+ </div></li><li class="listitem"><div class="para">
+ lun
+ </div></li><li class="listitem"><div class="para">
+ channel-scsi
+ </div></li><li class="listitem"><div class="para">
+ wwn
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>scsi-block</strong></span> -tech preview for 6.3
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ drive
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>scsi-disk</strong></span> -tech preview for 6.3
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ drive=drive
+ </div></li><li class="listitem"><div class="para">
+ logical_block_size
+ </div></li><li class="listitem"><div class="para">
+ physical_block_size
+ </div></li><li class="listitem"><div class="para">
+ min_io_size
+ </div></li><li class="listitem"><div class="para">
+ opt_io_size
+ </div></li><li class="listitem"><div class="para">
+ bootindex
+ </div></li><li class="listitem"><div class="para">
+ ver
+ </div></li><li class="listitem"><div class="para">
+ serial
+ </div></li><li class="listitem"><div class="para">
+ scsi-id
+ </div></li><li class="listitem"><div class="para">
+ lun
+ </div></li><li class="listitem"><div class="para">
+ channel-scsi
+ </div></li><li class="listitem"><div class="para">
+ wwn
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>piix3-usb-uhci</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>piix4-usb-uhci</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>ccid-card-passthru</strong></span>
+ </div></li></ul></div><h4 id="idp26729440">Global device setting</h4><div class="para">
+ <span class="application"><strong>-global</strong></span> <device>.<property>=<value>
+ </div><div class="para">
+ Supported devices and properties as in "General device" section with these additional devices:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>isa-fdc</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ driveA
+ </div></li><li class="listitem"><div class="para">
+ driveB
+ </div></li><li class="listitem"><div class="para">
+ bootindexA
+ </div></li><li class="listitem"><div class="para">
+ bootindexB
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>qxl-vga</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ ram_size
+ </div></li><li class="listitem"><div class="para">
+ vram_size
+ </div></li><li class="listitem"><div class="para">
+ revision
+ </div></li><li class="listitem"><div class="para">
+ cmdlog
+ </div></li><li class="listitem"><div class="para">
+ addr
+ </div></li></ul></div></li></ul></div><h4 id="idp7604560">Character device</h4><div class="para">
+ <span class="application"><strong>-chardev</strong></span> backend,id=<id>[,<options>]
+ </div><div class="para">
+ Supported backends are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>null</strong></span>,id=<id> - null device
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>socket</strong></span>,id=<id>,port=<port>[,host=<host>][,to=<to>][,ipv4][,ipv6][,nodelay][,server][,nowait][,telnet] - tcp socket
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>socket</strong></span>,id=<id>,path=<path>[,server][,nowait][,telnet] - unix socket
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>file</strong></span>,id=<id>,path=<path> - trafit to file.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>stdio</strong></span>,id=<id> - standard i/o
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>spicevmc</strong></span>,id=<id>,name=<name> - spice channel
+ </div></li></ul></div><h4 id="idm4508400">Enable USB</h4><div class="para">
+ <span class="application"><strong>-usb</strong></span>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apds05.html"><strong>Prev</strong>D.5. Network options</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="apds07.html"><strong>Next</strong>D.7. Linux/Multiboot boot </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds07.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds07.html
new file mode 100644
index 0000000..057f568
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds07.html
@@ -0,0 +1,18 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>D.7. Linux/Multiboot boot</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html" title="Appendix D. qemu-kvm Whitelist" /><link rel="prev" href="apds06.html" title="D.6. Device options" /><link rel="next" href="apds08.html" title="D.8. Expert options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="apds06.html"><strong>Prev</strong></a></li><l
i class="next"><a accesskey="n" href="apds08.html"><strong>Next</strong></a></li></ul><div class="section" id="idm4506608"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm4506608">D.7. Linux/Multiboot boot </h2></div></div></div><h4 id="idp25525504">Kernel file</h4><div class="para">
+ <span class="application"><strong>-kernel</strong></span> <bzImage>
+ </div><div class="para">
+ Note: multiboot images are not supported
+ </div><h4 id="idp25527584">Ram disk</h4><div class="para">
+ <span class="application"><strong>-initrd</strong></span> <file>
+ </div><h4 id="idp25529648">Command line parameter</h4><div class="para">
+ <span class="application"><strong>-append</strong></span> <cmdline>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apds06.html"><strong>Prev</strong>D.6. Device options</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="apds08.html"><strong>Next</strong>D.8. Expert options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds08.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds08.html
new file mode 100644
index 0000000..ce7f66c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds08.html
@@ -0,0 +1,60 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>D.8. Expert options</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html" title="Appendix D. qemu-kvm Whitelist" /><link rel="prev" href="apds07.html" title="D.7. Linux/Multiboot boot" /><link rel="next" href="apds09.html" title="D.9. Help and information options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="apds07.html"><strong>Prev
</strong></a></li><li class="next"><a accesskey="n" href="apds09.html"><strong>Next</strong></a></li></ul><div class="section" id="idm20678832"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm20678832">D.8. Expert options</h2></div></div></div><h4 id="idm20678032">KVM virtualization</h4><div class="para">
+ <span class="application"><strong>-enable-kvm</strong></span>
+ </div><div class="para">
+ Qemu-kvm supports only KVM virtualization and it is used by default if available. If -enable-kvm is used and KVM is not available, qemu-kvm fails. However, if -enable-kvm is not used and KVM is not available, qemu-kvm runs in TCG mode, which is not supported.
+ </div><h4 id="idm20675664">Disable kernel mode PIT reinjection</h4><div class="para">
+ <span class="application"><strong>-no-kvm-pit-reinjection</strong></span>
+ </div><h4 id="idp16944320">No shutdown</h4><div class="para">
+ <span class="application"><strong>-no-shutdown</strong></span>
+ </div><h4 id="idp16945952">No reboot</h4><div class="para">
+ <span class="application"><strong>-no-reboot</strong></span>
+ </div><h4 id="idp16947584">Serial port, monitor, QMP</h4><div class="para">
+ <span class="application"><strong>-serial</strong></span> <dev>
+ </div><div class="para">
+ <span class="application"><strong>-monitor</strong></span> <dev>
+ </div><div class="para">
+ <span class="application"><strong>-qmp</strong></span> <dev>
+ </div><div class="para">
+ Supported devices are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>stdio</strong></span> - standard input/output
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>null</strong></span> - null device
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>file</strong></span>:<filename> - output to file.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>tcp</strong></span>:[<host>]:<port>[,server][,nowait][,nodelay] - TCP Net console.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>unix</strong></span>:<path>[,server][,nowait] - Unix domain socket.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>mon</strong></span>:<dev_string> - Any device above, used to multiplex monitor too.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>none</strong></span> - disable, valid only for -serial.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>chardev</strong></span>:<id> - character device created with -chardev.
+ </div></li></ul></div><h4 id="idp11503840">Monitor redirect</h4><div class="para">
+ <span class="application"><strong>-mon</strong></span> <chardev_id>[,mode=[readline|control]][,default=[on|off]]
+ </div><h4 id="idp23779216">Manual CPU start</h4><div class="para">
+ <span class="application"><strong>-S</strong></span>
+ </div><h4 id="idp23780848">RTC</h4><div class="para">
+ <span class="application"><strong>-rtc</strong></span> [base=utc|localtime|date][,clock=host|vm][,driftfix=none|slew]
+ </div><h4 id="idp23782448">Watchdog</h4><div class="para">
+ <span class="application"><strong>-watchdog</strong></span> model
+ </div><h4 id="idm3796608">Watchdog reaction</h4><div class="para">
+ <span class="application"><strong>-watchdog-action</strong></span> <action>
+ </div><h4 id="idm3794976">Guest memory backing</h4><div class="para">
+ <span class="application"><strong>-mem-prealloc</strong></span> <span class="application"><strong>-mem-path</strong></span> /dev/hugepages
+ </div><h4 id="idm3792864">SMBIOS entry</h4><div class="para">
+ <span class="application"><strong>-smbios</strong></span> type=0[,vendor=<str>][,<version=str>][,date=<str>][,release=%d.%d]
+ </div><div class="para">
+ <span class="application"><strong>-smbios</strong></span> type=1[,manufacturer=<str>][,product=<str>][,version=<str>][,serial=<str>][,uuid=<uuid>][,sku=<str>][,family=<str>]
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apds07.html"><strong>Prev</strong>D.7. Linux/Multiboot 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="apds09.html"><strong>Next</strong>D.9. Help and information options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds09.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds09.html
new file mode 100644
index 0000000..797e508
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds09.html
@@ -0,0 +1,18 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>D.9. Help and information options</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html" title="Appendix D. qemu-kvm Whitelist" /><link rel="prev" href="apds08.html" title="D.8. Expert options" /><link rel="next" href="apds10.html" title="D.10. Miscellaneous options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="apds08.html"><strong>Prev</strong></a
></li><li class="next"><a accesskey="n" href="apds10.html"><strong>Next</strong></a></li></ul><div class="section" id="idp23667360"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp23667360">D.9. Help and information options</h2></div></div></div><h4 id="idp23668128">Help</h4><div class="para">
+ <span class="application"><strong>-h</strong></span>
+ </div><div class="para">
+ <span class="application"><strong>-help</strong></span>
+ </div><h4 id="idp23670720">Version</h4><div class="para">
+ <span class="application"><strong>-version</strong></span>
+ </div><h4 id="idp9152112">Audio help</h4><div class="para">
+ <span class="application"><strong>-audio-help</strong></span>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apds08.html"><strong>Prev</strong>D.8. Expert options</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="apds10.html"><strong>Next</strong>D.10. Miscellaneous options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds10.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds10.html
new file mode 100644
index 0000000..97bac64
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apds10.html
@@ -0,0 +1,24 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>D.10. Miscellaneous options</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html" title="Appendix D. qemu-kvm Whitelist" /><link rel="prev" href="apds09.html" title="D.9. Help and information options" /><link rel="next" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="apds09.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html"><strong>Next</strong></a></li></ul><div class="section" id="idp9153904"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp9153904">D.10. Miscellaneous options</h2></div></div></div><h4 id="idp9154704">Migration</h4><div class="para">
+ <span class="application"><strong>-incoming</strong></span>
+ </div><h4 id="idp12589136">No default configuration</h4><div class="para">
+ <span class="application"><strong>-nodefconfig</strong></span>
+ </div><div class="para">
+ <span class="application"><strong>-nodefaults</strong></span>
+ </div><div class="para">
+ Running without -nodefaults is not supported
+ </div><h4 id="idp12592144">Device configuration file</h4><div class="para">
+ <span class="application"><strong>-readconfig</strong></span> <file>
+ </div><div class="para">
+ <span class="application"><strong>-writeconfig</strong></span> <file>
+ </div><h4 id="idp1571856">Loaded saved state</h4><div class="para">
+ <span class="application"><strong>-loadvm</strong></span> <file>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apds09.html"><strong>Prev</strong>D.9. Help and information options</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_Administration_Guide-Managing_guests_with_virsh.html"><strong>Next</strong>Appendix E. Managing guests with virsh</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes05.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes05.html
new file mode 100644
index 0000000..1c0b54f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes05.html
@@ -0,0 +1,26 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.5. Suspending, resuming, saving and restoring a guest</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="prev" href="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html" title="E.4. Creating a virtual machine XML dump (configuration file)" /><link rel="next" href="apes06.html" title="E.6. Shutting down, rebooting and force-shutdown of a guest" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apes06.html"><strong>Next</strong></a></li></ul><div class="section" id="idp13626416"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp13626416">E.5. Suspending, resuming, saving and restoring a guest</h2></div></div></div><div class="formalpara"><h5 class="formalpara" id="idp13627184">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="apes05.html#form-Virtualization-Managing_guests_with_virsh-Resuming_a_guest">Resuming a guest</a>) option.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Resuming_a_guest"><h5 class="formalpara">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" id="form-Virtualization-Managing_guests_with_virsh-Save_a_guest"><h5 class="formalpara">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="apes05.html#form-Virtualization-Managing_guests_with_virsh-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" id="form-Virtualization-Managing_guests_with_virsh-Restore_a_guest"><h5 class="formalpara">Restore a guest</h5>
+ Restore a guest previously saved with the <code class="command">virsh save</code> command (<a class="xref" href="apes05.html#form-Virtualization-Managing_guests_with_virsh-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><ul class="docnav"><li class="previous"><a accesskey="p" href="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html"><strong>Prev</strong>E.4. Creating a virtual machine XML dump (configu...</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="apes06.html"><strong>Next</strong>E.6. Shutting down, rebooting and force-shutdown ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes06.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes06.html
new file mode 100644
index 0000000..696bed4
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes06.html
@@ -0,0 +1,22 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.6. Shutting down, rebooting and force-shutdown of a guest</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="prev" href="apes05.html" title="E.5. Suspending, resuming, saving and restoring a guest" /><link rel="next" href="apes07.html" title="E.7. Retrieving guest information" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="apes05.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apes07.html"><strong>Next</strong></a></li></ul><div class="section" id="idp23280224"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp23280224">E.6. Shutting down, rebooting and force-shutdown of a guest</h2></div></div></div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Shut_down_a_guest"><h5 class="formalpara">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.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Rebooting_a_guest"><h5 class="formalpara">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> element in the guest's configuration file.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Forcing_a_guest_to_stop"><h5 class="formalpara">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.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apes05.html"><strong>Prev</strong>E.5. Suspending, resuming, saving and restoring 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="apes07.html"><strong>Next</strong>E.7. Retrieving guest information</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes07.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes07.html
new file mode 100644
index 0000000..02ba173
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes07.html
@@ -0,0 +1,40 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.7. Retrieving guest information</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="prev" href="apes06.html" title="E.6. Shutting down, rebooting and force-shutdown of a guest" /><link rel="next" href="apes08.html" title="E.8. Retrieving node information" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="apes06.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apes08.html"><strong>Next</strong></a></li></ul><div class="section" id="idp9016176"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp9016176">E.7. Retrieving guest information</h2></div></div></div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Getting_the_domain_ID_of_a_guest"><h5 class="formalpara">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" id="form-Virtualization-Managing_guests_with_virsh-Getting_the_domain_name_of_a_guest"><h5 class="formalpara">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" id="form-Virtualization-Managing_guests_with_virsh-Getting_the_UUID_of_a_guest"><h5 class="formalpara">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" id="form-Virtualization-Managing_guests_with_virsh-Displaying_guest_Information_"><h5 class="formalpara">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 vr-rhel6u1-x86_64-kvm
+Id: 9
+Name: vr-rhel6u1-x86_64-kvm
+UUID: a03093a1-5da6-a2a2-3baf-a845db2f10b9
+OS Type: hvm
+State: running
+CPU(s): 1
+CPU time: 21.6s
+Max memory: 2097152 kB
+Used memory: 1025000 kB
+Persistent: yes
+Autostart: disable
+Security model: selinux
+Security DOI: 0
+Security label: system_u:system_r:svirt_t:s0:c612,c921 (permissive)
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apes06.html"><strong>Prev</strong>E.6. Shutting down, rebooting and force-shutdown ...</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="apes08.html"><strong>Next</strong>E.8. Retrieving node information</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes08.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes08.html
new file mode 100644
index 0000000..16acafd
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes08.html
@@ -0,0 +1,26 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.8. Retrieving node information</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="prev" href="apes07.html" title="E.7. Retrieving guest information" /><link rel="next" href="apes09.html" title="E.9. Storage pool information" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="apes0
7.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apes09.html"><strong>Next</strong></a></li></ul><div class="section" id="idp315888"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp315888">E.8. Retrieving node information</h2></div></div></div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Displaying_node_information"><h5 class="formalpara">Displaying node information</h5>
+ To display information about the node:
+ </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">
+ Returns basic information about the node, including the model number, number of CPUs, type of CPU, and size of the physical memory. The output corresponds to virNodeInfo structure. Specifically, the "CPU socket(s)" field indicates the number of CPU sockets per NUMA cell.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apes07.html"><strong>Prev</strong>E.7. Retrieving guest information</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="apes09.html"><strong>Next</strong>E.9. Storage pool information</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes09.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes09.html
new file mode 100644
index 0000000..93006f6
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes09.html
@@ -0,0 +1,19 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.9. Storage pool information</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="prev" href="apes08.html" title="E.8. Retrieving node information" /><link rel="next" href="apes10.html" title="E.10. Displaying per-guest information" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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" hre
f="apes08.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apes10.html"><strong>Next</strong></a></li></ul><div class="section" id="idp2515504"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp2515504">E.9. Storage pool information</h2></div></div></div><div class="formalpara" id="asfdqsdgasdfsadgwr"><h5 class="formalpara">Editing a storage pool definition</h5>
+ The <code class="command">virsh pool-edit</code> command takes the name or UUID for a storage pool and opens the XML definition file for a storage pool in the users default text editor.
+ </div><div class="para">
+ The <code class="command">virsh pool-edit</code> command is equivalent to running the following commands:
+ </div><pre class="screen"># virsh pool-dumpxml <em class="parameter"><code>pool</code></em> > <em class="parameter"><code>pool</code></em>.xml
+# vim <em class="parameter"><code>pool</code></em>.xml
+# virsh pool-define <em class="parameter"><code>pool</code></em>.xml
+</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The default editor is defined by the <code class="command">$VISUAL</code> or <code class="command">$EDITOR</code> environment variables, and default is <code class="command">vi</code>.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apes08.html"><strong>Prev</strong>E.8. Retrieving node information</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="apes10.html"><strong>Next</strong>E.10. Displaying per-guest information</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes10.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes10.html
new file mode 100644
index 0000000..fe5a587
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes10.html
@@ -0,0 +1,119 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.10. Displaying per-guest information</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="prev" href="apes09.html" title="E.9. Storage pool information" /><link rel="next" href="apes11.html" title="E.11. Managing virtual networks" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="apes09.
html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apes11.html"><strong>Next</strong></a></li></ul><div class="section" id="idm12158304"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm12158304">E.10. Displaying per-guest information</h2></div></div></div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Displaying_the_guests"><h5 class="formalpara">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">
+ There are seven states that can be visible using this command:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Running - The <code class="computeroutput">running</code> state refers to guests which are currently active on a CPU.
+ </div></li><li class="listitem"><div class="para">
+ Idle - The <code class="computeroutput">idle</code> state indicates that the domain is idle, and may not be running or able to run. This can be caused because the domain is waiting on IO (a traditional wait state) or has gone to sleep because there was nothing else for it to do.
+ </div></li><li class="listitem"><div class="para">
+ Paused - 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 class="listitem"><div class="para">
+ Shutdown - 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 class="listitem"><div class="para">
+ Shut off - The <code class="computeroutput">shut off</code> state indicates that the domain is not running. This can be caused when a domain completly shuts down or has not been started.
+ </div></li><li class="listitem"><div class="para">
+ Crashed - The <code class="computeroutput">crashed</code> state indicates that the domain has crashed and can only occur if the guest has been configured not to restart on crash.
+ </div></li><li class="listitem"><div class="para">
+ Dying - 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></ul></div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Displaying_virtual_CPU_information"><h5 class="formalpara">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" id="form-Virtualization-Managing_guests_with_virsh-Configuring_virtual_CPU_affinity"><h5 class="formalpara">Configuring virtual CPU affinity</h5>
+ To configure the affinity of virtual CPUs with physical CPUs:
+ </div><pre class="screen"># virsh vcpupin <em class="parameter"><code>domain-id vcpu cpulist</code></em></pre><div class="para">
+ The <code class="command">domain-id</code> parameter is the guest's ID number or name.
+ </div><div class="para">
+ The <code class="command">vcpu</code> parameter denotes the number of virtualized CPUs allocated to the guest.The <code class="command">vcpu</code> parameter must be provided.
+ </div><div class="para">
+ The <code class="command">cpulist</code> parameter is a list of physical CPU identifier numbers separated by commas. The <code class="command">cpulist</code> parameter determines which physical CPUs the VCPUs can run on.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Configuring_virtual_CPU_count"><h5 class="formalpara">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">
+ This <em class="parameter"><code>count</code></em> value cannot exceed the number of CPUs that were assigned to the guest when it was created.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Configuring_memory_allocation"><h5 class="formalpara">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><pre class="screen"># <code class="command">virsh setmem</code> <em class="replaceable"><code>vr-rhel6u1-x86_64-kvm</code></em> <em class="replaceable"><code>--kilobytes 1025000</code></em></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 does not affect active guests. If the new value is lower than the available memory, it will shrink possibly causing the guest to crash.
+ </div><div class="para">
+ This command has the following options
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ [--domain] <string> domain name, id or uuid
+ </div></li><li class="listitem"><div class="para">
+ [--size] <number> new memory size, as scaled integer (default KiB)
+ </div></li><li class="listitem"><div class="para">
+ --config takes affect next boot
+ </div></li><li class="listitem"><div class="para">
+ --live controls the memory of the running domain
+ </div></li><li class="listitem"><div class="para">
+ --current controls the memory on the current domain
+ </div></li></ul></div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Configuring_memory_tuning"><h5 class="formalpara">Configuring memory Tuning</h5>
+ The element memtune provides details regarding the memory tunable parameters for the domain. If this is omitted, it defaults to the OS provided defaults. For QEMU/KVM, the parameters are applied to the QEMU process as a whole. Thus, when counting them, one needs to add up guest RAM, guest video RAM, and some memory overhead of QEMU itself. The last piece is hard to determine so one needs guess and try. For each tunable, it is possible to designate which unit the number is in on input, using the same values as for <memory>. For backwards compatibility, output is always in KiB. units.
+ </div><div class="para">
+ Here is an example XML with the memtune options used:
+ </div><pre class="screen">
+<domain>
+
+ <memtune>
+ <hard_limit unit='G'>1</hard_limit>
+ <soft_limit unit='M'>128</soft_limit>
+ <swap_hard_limit unit='G'>2</swap_hard_limit>
+ <min_guarantee unit='bytes'>67108864</min_guarantee>
+ </memtune>
+ ...
+</domain>
+</pre><div class="para">
+ memtune has the following options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ hard_limit - The optional hard_limit element is the maximum memory the guest can use. The units for this value are kibibytes (i.e. blocks of 1024 bytes)
+ </div></li><li class="listitem"><div class="para">
+ soft_limit - The optional soft_limit element is the memory limit to enforce during memory contention. The units for this value are kibibytes (i.e. blocks of 1024 bytes)
+ </div></li><li class="listitem"><div class="para">
+ swap_hard_limit - The optional swap_hard_limit element is the maximum memory plus swap the guest can use. The units for this value are kibibytes (i.e. blocks of 1024 bytes). This has to be more than hard_limit value provided
+ </div></li><li class="listitem"><div class="para">
+ min_guarantee - The optional min_guarantee element is the guaranteed minimum memory allocation for the guest. The units for this value are kibibytes (i.e. blocks of 1024 bytes)
+ </div></li></ul></div><pre class="screen">
+# virsh memtune vr-rhel6u1-x86_64-kvm --hard-limit 512000
+
+# virsh memtune vr-rhel6u1-x86_64-kvm
+hard_limit : 512000 kB
+soft_limit : unlimited
+swap_hard_limit: unlimited
+</pre><div class="para">
+ hard_limit is 512000 kB, it is maximum memory the guest domain can use.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Displaying_guest_block_device_information"><h5 class="formalpara">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" id="form-Virtualization-Managing_guests_with_virsh-Displaying_guest_network_device_information"><h5 class="formalpara">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><ul class="docnav"><li class="previous"><a accesskey="p" href="apes09.html"><strong>Prev</strong>E.9. Storage pool information</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="apes11.html"><strong>Next</strong>E.11. Managing virtual networks</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes11.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes11.html
new file mode 100644
index 0000000..9caeb7f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes11.html
@@ -0,0 +1,55 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.11. Managing virtual networks</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="prev" href="apes10.html" title="E.10. Displaying per-guest information" /><link rel="next" href="migrating_guests-with-virsh.html" title="E.12. Migrating guests with virsh" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="apes10.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="migrating_guests-with-virsh.html"><strong>Next</strong></a></li></ul><div class="section" id="idp3110000"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp3110000">E.11. Managing virtual networks</h2></div></div></div><div class="para">
+ 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 class="listitem"><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 class="listitem"><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 class="listitem"><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 class="listitem"><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 class="listitem"><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 class="listitem"><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 class="listitem"><div class="para">
+ <code class="command">virsh net-start <em class="replaceable"><code>nameOfInactiveNetwork</code></em> </code> — starts an inactive network.
+ </div></li><li class="listitem"><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="apes10.html"><strong>Prev</strong>E.10. Displaying per-guest information</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="migrating_guests-with-virsh.html"><strong>Next</strong>E.12. Migrating guests with virsh</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes14s03.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes14s03.html
new file mode 100644
index 0000000..742383a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes14s03.html
@@ -0,0 +1,95 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.14.3. Determining a compatible CPU model to suit a pool of hosts</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-guest-cpu-model-config.html" title="E.14. Guest CPU model configuration" /><link rel="prev" href="sect-learn-about-host-cpu.html" title="E.14.2. Learning about the host CPU model" /><link rel="next" href="apes14s04.html" title="E.14.4. Configuring the guest CPU model" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-lear
n-about-host-cpu.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apes14s04.html"><strong>Next</strong></a></li></ul><div class="section" id="idp5364528"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idp5364528">E.14.3. Determining a compatible CPU model to suit a pool of hosts</h3></div></div></div><div class="para">
+ Now that it is possible to find out what CPU capabilities a single host has, the next step is to determine what CPU capabilities are best to expose to the guest. If it is known that the guest will never need to be migrated to another host, the host CPU model can be passed straight through unmodified. A virtualized data center may have a set of configurations that can guarantee all servers will have 100% identical CPUs. Again the host CPU model can be passed straight through unmodified. The more common case, though, is where there is variation in CPUs between hosts. In this mixed CPU environment, the lowest common denominator CPU must be determined. This is not entirely straightforward, so libvirt provides an API for exactly this task. If libvirt is provided a list of XML documents, each describing a CPU model for a host, libvirt will internally convert these to CPUID masks, calculate their intersection, and convert the CPUID mask result back into an XML CPU description.
Taking the CPU description from a server:
+ </div><pre class="screen">
+# virsh capabilities
+<capabilities>
+
+ <host>
+ <uuid>8e8e4e67-9df4-9117-bf29-ffc31f6b6abb</uuid>
+ <cpu>
+ <arch>x86_64</arch>
+ <model>Westmere</model>
+ <vendor>Intel</vendor>
+ <topology sockets='2' cores='4' threads='2'/>
+ <feature name='rdtscp'/>
+ <feature name='pdpe1gb'/>
+ <feature name='dca'/>
+ <feature name='xtpr'/>
+ <feature name='tm2'/>
+ <feature name='est'/>
+ <feature name='vmx'/>
+ <feature name='ds_cpl'/>
+ <feature name='monitor'/>
+ <feature name='pbe'/>
+ <feature name='tm'/>
+ <feature name='ht'/>
+ <feature name='ss'/>
+ <feature name='acpi'/>
+ <feature name='ds'/>
+ <feature name='vme'/>
+ </cpu>
+
+ ... snip ...
+
+</capabilities>
+</pre><div class="para">
+ A quick check can be made to see whether this CPU description is compatible with the previous workstation CPU description, using the <code class="command">virsh cpu-compare</code> command. To do so, the <code class="command">virsh capabilities > virsh-caps-workstation-full.xml</code> command was executed on the workstation. The file <code class="filename">virsh-caps-workstation-full.xml</code> was edited and reduced to just the following content:
+ </div><pre class="screen">
+<cpu>
+ <arch>x86_64</arch>
+ <model>core2duo</model>
+ <topology sockets='1' cores='4' threads='1'/>
+ <feature name='lahf_lm'/>
+ <feature name='sse4.1'/>
+ <feature name='xtpr'/>
+ <feature name='cx16'/>
+ <feature name='tm2'/>
+ <feature name='est'/>
+ <feature name='vmx'/>
+ <feature name='ds_cpl'/>
+ <feature name='pbe'/>
+ <feature name='tm'/>
+ <feature name='ht'/>
+ <feature name='ss'/>
+ <feature name='acpi'/>
+ <feature name='ds'/>
+ </cpu>
+</pre><div class="para">
+ The reduced content was stored in a file named <code class="filename">virsh-caps-workstation-cpu-only.xml</code> and the <code class="command">virsh cpu-compare</code> command can be executed using this file:
+ </div><pre class="screen">
+virsh cpu-compare virsh-caps-workstation-cpu-only.xml
+Host CPU is a superset of CPU described in virsh-caps-workstation-cpu-only.xml
+</pre><div class="para">
+ As seen in this output, libvirt is correctly reporting the CPUs are not strictly compatible, because there are several features in the server CPU that are missing in the workstation CPU. To be able to migrate between the workstation and the server, it will be necessary to mask out some features, but to determine which ones, libvirt provides an API for this, shown via the <code class="command">virsh cpu-baseline</code> command:
+ </div><pre class="screen">
+# virsh cpu-baseline virsh-cap-weybridge-strictly-cpu-only.xml
+<cpu match='exact'>
+ <model>Penryn</model>
+ <feature policy='require' name='xtpr'/>
+ <feature policy='require' name='tm2'/>
+ <feature policy='require' name='est'/>
+ <feature policy='require' name='vmx'/>
+ <feature policy='require' name='ds_cpl'/>
+ <feature policy='require' name='monitor'/>
+ <feature policy='require' name='pbe'/>
+ <feature policy='require' name='tm'/>
+ <feature policy='require' name='ht'/>
+ <feature policy='require' name='ss'/>
+ <feature policy='require' name='acpi'/>
+ <feature policy='require' name='ds'/>
+ <feature policy='require' name='vme'/>
+</cpu>
+</pre><div class="para">
+ Similarly, if the two <cpu>...</cpu> elements are put into a single file named <code class="filename">both-cpus.xml</code>, the following command would generate the same result:
+ </div><pre class="screen"> # virsh cpu-baseline both-cpus.xml</pre><div class="para">
+ In this case, libvirt has determined that in order to safely migrate a guest between the workstation and the server, it is necessary to mask out 3 features from the XML description for the server, and 3 features from the XML description for the workstation.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-learn-about-host-cpu.html"><strong>Prev</strong>E.14.2. Learning about the host CPU model</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="apes14s04.html"><strong>Next</strong>E.14.4. Configuring the guest CPU model</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes14s04.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes14s04.html
new file mode 100644
index 0000000..9bfb35a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apes14s04.html
@@ -0,0 +1,32 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.14.4. Configuring the guest CPU model</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-guest-cpu-model-config.html" title="E.14. Guest CPU model configuration" /><link rel="prev" href="apes14s03.html" title="E.14.3. Determining a compatible CPU model to suit a pool of hosts" /><link rel="next" href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="Appendix F. Managing guests with the Virtual Machine Manager (virt-manager)" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="apes14s03.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html"><strong>Next</strong></a></li></ul><div class="section" id="idm9873040"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm9873040">E.14.4. Configuring the guest CPU model</h3></div></div></div><div class="para">
+ For simple defaults, the guest CPU configuration accepts the same basic XML representation as the host capabilities XML exposes. In other words, the XML from the <code class="command">cpu-baseline</code> virsh command can now be copied directly into the guest XML at the top level under the <domain> element. As the observant reader will have noticed from the previous XML snippet, there are a few extra attributes available when describing a CPU in the guest XML. These can mostly be ignored, but for the curious here is a quick description of what they do. The top level <cpu> element has an attribute called <span class="emphasis"><em>match</em></span> with possible values of:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ match='minimum' - the host CPU must have at least the CPU features described in the guest XML. If the host has additional features beyond the guest configuration, these will also be exposed to the guest.
+ </div></li><li class="listitem"><div class="para">
+ match='exact' - the host CPU must have at least the CPU features described in the guest XML. If the host has additional features beyond the guest configuration, these will be masked out from the guest.
+ </div></li><li class="listitem"><div class="para">
+ match='strict' - the host CPU must have exactly the same CPU features described in the guest XML.
+ </div></li></ul></div><div class="para">
+ The next enhancement is that the <feature> elements can each have an extra 'policy' attribute with possible values of:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ policy='force' - expose the feature to the guest even if the host does not have it. This is usually only useful in the case of software emulation.
+ </div></li><li class="listitem"><div class="para">
+ policy='require' - expose the feature to the guest and fail if the host does not have it. This is the sensible default.
+ </div></li><li class="listitem"><div class="para">
+ policy='optional' - expose the feature to the guest if it happens to support it.
+ </div></li><li class="listitem"><div class="para">
+ policy='disable' - if the host has this feature, then hide it from the guest.
+ </div></li><li class="listitem"><div class="para">
+ policy='forbid' - if the host has this feature, then fail and refuse to start the guest.
+ </div></li></ul></div><div class="para">
+ The 'forbid' policy is for a niche scenario where an incorrectly functioning application will try to use a feature even if it is not in the CPUID mask, and you wish to prevent accidentally running the guest on a host with that feature. The 'optional' policy has special behavior with respect to migration. When the guest is initially started the flag is optional, but when the guest is live migrated, this policy turns into 'require', since you cannot have features disappearing across migration.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apes14s03.html"><strong>Prev</strong>E.14.3. Determining a compatible CPU model to sui...</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_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html"><strong>Next</strong>Appendix F. Managing guests with the Virtual Mach...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apjs14.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apjs14.html
new file mode 100644
index 0000000..b873c8f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/apjs14.html
@@ -0,0 +1,53 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.14. Hypervisor features</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sect-libvirt-dom-xml-pwr-man.html" title="J.13. Power Management" /><link rel="next" href="sect-libvirt-dom-xml-time-keep.html" title="J.15. Time keeping" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-libvirt-dom-xml-pwr-man.html
"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-libvirt-dom-xml-time-keep.html"><strong>Next</strong></a></li></ul><div class="section" id="idp13742448"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp13742448">J.14. Hypervisor features</h2></div></div></div><div class="para">
+ Hypervisors may allow certain CPU / machine features to be enabled (<code class="sgmltag-attvalue">state='on')</code> or disabled (<code class="sgmltag-attvalue">state='off'</code>).
+ </div><div class="figure" id="fig-libvirt-dom-xml-hypr-feat"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><features></span>
+ <span class="perl_Keyword"><pae/></span>
+ <span class="perl_Keyword"><acpi/></span>
+ <span class="perl_Keyword"><apic/></span>
+ <span class="perl_Keyword"><hap/></span>
+ <span class="perl_Keyword"><privnet/></span>
+ <span class="perl_Keyword"><hyperv></span>
+ <span class="perl_Keyword"><relaxed</span><span class="perl_Others"> state=</span><span class="perl_String">'on'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></hyperv></span>
+ <span class="perl_Keyword"></features></span>
+ ...
+
+</pre></div><h6>Figure J.21. Hypervisor features</h6></div><br class="figure-break" /><div class="para">
+ All features are listed within the <code class="sgmltag-starttag"><features></code> element, if a <code class="sgmltag-starttag"><state></code> is not specified it is disabled. The available features can be found by calling the <code class="filename">capabilities</code> XML, but a common set for fully virtualized domains are:
+ </div><div class="table" id="table-libvirt-dom-xml-hyp-feat-elem"><h6>Table J.11. Hypervisor features elements</h6><div class="table-contents"><table summary="Hypervisor features elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ State
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><pae></code>
+ </td><td class="">
+ Physical address extension mode allows 32-bit guests to address more than 4 GB of memory.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><acpi></code>
+ </td><td class="">
+ Useful for power management, for example, with KVM guests it is required for graceful shutdown to work.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><apic></code>
+ </td><td class="">
+ Allows the use of programmable IRQ management. For this element, there is an optional attribute <code class="sgmltag-attribute">eoi</code> with values <code class="sgmltag-attvalue">on</code> and <code class="sgmltag-attvalue">off</code> which sets the availability of EOI (End of Interrupt) for the guest.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><hap></code>
+ </td><td class="">
+ Enables the use of Hardware Assisted Paging if it is available in the hardware.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">hyperv</code>
+ </td><td class="">
+ Enables various features to improve the behavior of guests running Microsoft Windows. Using the optional attribute <code class="sgmltag-attribute">relaxed</code> with values <code class="sgmltag-attvalue">on</code> or <code class="sgmltag-attvalue">off</code> enables or disables the relax constraints on timers
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-pwr-man.html"><strong>Prev</strong>J.13. Power 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-libvirt-dom-xml-time-keep.html"><strong>Next</strong>J.15. Time keeping</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/appe-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Revision_History.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/appe-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Revision_History.html
new file mode 100644
index 0000000..fa6fcfc
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/appe-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Revision_History.html
@@ -0,0 +1,19 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix K. Revision History</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="prev" href="section-libvirt-dom-xml-example.html" title="J.23. Example domain XML configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="section-libvirt-dom-xml-example.html"><strong>Prev</strong></a></li><li class="next"></li></ul><div xml:
lang="en-US" class="appendix" id="appe-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Revision_History" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Revision History</h1></div></div></div><div class="para">
+ <div class="revhistory"><table summary="Revision History"><tr><th align="left" valign="top" colspan="3"><strong>Revision History</strong></th></tr><tr><td align="left">Revision 0.2-0</td><td align="left">Tue May 28 2013</td><td align="left"><span class="author"><span class="firstname">Laura</span> <span class="surname">Novich</span></span></td></tr><tr><td align="left" colspan="3">
+ <table border="0" summary="Simple list" class="simplelist"><tr><td>Completed merger of guides and prepared for final publishing.</td></tr></table>
+
+ </td></tr><tr><td align="left">Revision 0.1-0</td><td align="left">Tue Jan 15 2013</td><td align="left"><span class="author"><span class="firstname">Laura</span> <span class="surname">Bailey</span></span></td></tr><tr><td align="left" colspan="3">
+ <table border="0" summary="Simple list" class="simplelist"><tr><td>Combined F18 Virtualization Administration Guide and Virtualization Host Configuration and Guest Installation Guide for use in Fedora 19.</td></tr></table>
+
+ </td></tr></table></div>
+
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="section-libvirt-dom-xml-example.html"><strong>Prev</strong>J.23. Example domain XML 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></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/appe-Virtualization-Additional_resources.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/appe-Virtualization-Additional_resources.html
new file mode 100644
index 0000000..ff76fa5
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/appe-Virtualization-Additional_resources.html
@@ -0,0 +1,32 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix I. Additional resources</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt03.html" title="Part III. Appendicies" /><link rel="prev" href="sub-sect-limitations-filters-network-subsystem.html" title="H.10.12. Limitations" /><link rel="next" href="sect-Virtualization-Additional_resources-Installed_documentation.html" title="I.2. Installed documentation" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="s
ub-sect-limitations-filters-network-subsystem.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Additional_resources-Installed_documentation.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="appendix" id="appe-Virtualization-Additional_resources" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Additional resources</h1></div></div></div><div class="para">
+ To learn more about virtualization and Fedora, refer to the following resources.
+ </div><div class="section" id="sect-Virtualization-Additional_resources-Online_resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">I.1. Online resources</h2></div></div></div><a id="idm12153840" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><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 class="listitem"><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 class="listitem"><div class="para">
+ Open Virtualization Center
+ </div><div class="para">
+ <a href="http://www.openvirtualization.com/">http://www.openvirtualization.com</a>
+ </div></li><li class="listitem"><div class="para">
+ Fedora Documentation
+ </div><div class="para">
+ <a href="http://docs.fedoraproject.org">http://docs.fedoraproject.org</a>
+ </div></li><li class="listitem"><div class="para">
+ Virtualization technologies overview
+ </div><div class="para">
+ <a href="http://virt.kernelnewbies.org/">http://virt.kernelnewbies.org</a>
+ </div></li><li class="listitem"><div class="para">
+ Fedora Community
+ </div><div class="para">
+ <a href="https://fedoraproject.org/en/join-fedora">https://fedoraproject.org/en/join-fedora</a>
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-limitations-filters-network-subsystem.html"><strong>Prev</strong>H.10.12. Limitations</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-Additional_resources-Installed_documentation.html"><strong>Next</strong>I.2. Installed documentation</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch-lib-dom-xml.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch-lib-dom-xml.html
new file mode 100644
index 0000000..577ce84
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch-lib-dom-xml.html
@@ -0,0 +1,54 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix J. Manipulating the domain xml</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt03.html" title="Part III. Appendicies" /><link rel="prev" href="sect-Virtualization-Additional_resources-Installed_documentation.html" title="I.2. Installed documentation" /><link rel="next" href="sect-dom-xml-op-sys-boot.html" title="J.2. Operating system booting" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-Virtualiz
ation-Additional_resources-Installed_documentation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-dom-xml-op-sys-boot.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="appendix" id="ch-lib-dom-xml" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Manipulating the domain xml</h1></div></div></div><div class="para">
+ This section describes the XML format used to represent one or more libvirt domains. Whereas a libvirt domain refers to a specified guest virtual machine, here the term <em class="firstterm">domain</em> refers to the root <code class="sgmltag-starttag"><domain></code> element required for defining the parameters of all guest virtual machines. The <code class="sgmltag-starttag"><domain></code> element has two attributes: <code class="sgmltag-attribute">type</code> specifies the hypervisor used for running the domain. The allowed values are driver specific, but include <code class="sgmltag-attvalue"> KVM</code> and others. <code class="sgmltag-attribute">id</code> is a unique integer identifier for the running guest machine. Inactive machines have no id value. The sections in this chapter will address the components of the domain XML. Additional chapters in this manual may refer to this chapter when manipulation of the domain XML is required.
+ </div><div class="section" id="sect-gen-metadata"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.1. General information and metadata</h2></div></div></div><div class="para">
+ This information is in this part of the domain XML:
+ </div><div class="figure" id="ch-lib-dom-xml-example"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain</span><span class="perl_Others"> type=</span><span class="perl_String">'xen'</span><span class="perl_Others"> id=</span><span class="perl_String">'3'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><name></span>fv0<span class="perl_Keyword"></name></span>
+ <span class="perl_Keyword"><uuid></span>4dea22b31d52d8f32516782e98ab3fa0<span class="perl_Keyword"></uuid></span>
+ <span class="perl_Keyword"><title></span>A short description - title - of the domain<span class="perl_Keyword"></title></span>
+ <span class="perl_Keyword"><description></span>Some human readable description<span class="perl_Keyword"></description></span>
+ <span class="perl_Keyword"><metadata></span>
+ <span class="perl_Keyword"><app1:foo</span><span class="perl_Others"> xmlns:app1=</span><span class="perl_String">"http://app1.org/app1/"</span><span class="perl_Keyword">></span>..<span class="perl_Keyword"></app1:foo></span>
+ <span class="perl_Keyword"><app2:bar</span><span class="perl_Others"> xmlns:app2=</span><span class="perl_String">"http://app1.org/app2/"</span><span class="perl_Keyword">></span>..<span class="perl_Keyword"></app2:bar></span>
+ <span class="perl_Keyword"></metadata></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.1. Domain XML metadata</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-gen-metadata"><h6>Table J.1. General metadata elements</h6><div class="table-contents"><table summary="General metadata elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><name></code>
+ </td><td class="">
+ Assigns a name for the virtual machine. This name should consist only of alpha-numeric characters and is required to be unique within the scope of a single host. It is often used to form the filename for storing the persistent configuration files.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><uuid></code>
+ </td><td class="">
+ assigns a globally unique identifier for the virtual machine. The format must be RFC 4122 compliant, eg <code class="sgmltag-attvalue">3e3fce45-4f53-4fa7-bb32-11f34168b82b</code>. If omitted when defining/creating a new machine, a random UUID is generated. It is also possible to provide the UUID via a sysinfo specification.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><title></code>
+ </td><td class="">
+ <code class="sgmltag-element">title</code> Creates space for a short description of the domain. The title should not contain any newlines.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><description></code>
+ </td><td class="">
+ Different from the title, This data is not used by libvirt in any way, it can contain any information the user wants to display.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><metadata></code>
+ </td><td class="">
+ Can be used by applications to store custom metadata in the form of XML nodes/trees. Applications must use custom namespaces on their XML nodes/trees, with only one top-level element per namespace (if the application needs structure, they should have sub-elements to their namespace element)
+ </td></tr></tbody></table></div></div><br class="table-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Additional_resources-Installed_documentation.html"><strong>Prev</strong>I.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="sect-dom-xml-op-sys-boot.html"><strong>Next</strong>J.2. Operating system booting</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch01s02.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch01s02.html
new file mode 100644
index 0000000..bddc0ac
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch01s02.html
@@ -0,0 +1,46 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2. Virtualization Documentation Suite</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html" title="Chapter 1. Introduction" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html" title="Chapter 1. Introduction" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_Requirements.html" title="Chapter 2. System requirements" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 s
rc="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_Requirements.html"><strong>Next</strong></a></li></ul><div class="section" id="idp2921840"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp2921840">1.2. Virtualization Documentation Suite</h2></div></div></div><div class="para">
+ Fedora offers a wealth of documentation solutions across its various virtualization products. Coverage of Fedora and its inbuilt virtualization products include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="citetitle">Fedora — Virtualization Getting Started Guide</em>: This guide provides an introduction to virtualization concepts, advantages, and tools, and an overview of Red Hat virtualization documentation and products.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Fedora — Virtualization Deployment and Administration Guide</em> covers the installation, configuration, and maintenance of virtualization hosts and virtual machines.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Fedora — Virtualization Security Guide</em>: This guide provides an overview of virtualization security technologies provided by Red Hat. Also included are recommendations for securing hosts, guests, and shared infrastructure and resources in virtualized environments.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Fedora — Virtualization Tuning and Optimization Guide</em>: This guide provides tips, tricks and suggestions for making full use of virtualization performance features and options for your systems and guest virtual machines.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Fedora — V2V Guide</em> describes importing virtual machines from KVM, Xen and VMware ESX/ESX(i) hypervisors to Red Hat Enterprise Virtualization and KVM managed by libvirt.
+ </div></li></ul></div><div class="para">
+ The oVirt documentation suite provides information on installation, development of applications, configuration and usage of the Red Hat Enterprise Virtualization platform and its related products.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Administration Guide</em> describes how to set up, configure and manage Red Hat Enterprise Virtualization. It assumes that you have successfully installed the Red Hat Enterprise Virtualization Manager and hosts.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Command Line Shell Guide</em> contains information for installing and using the Red Hat Enterprise Virtualization Manager command line shell.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Developer Guide</em> explains how to use the REST API. It covers the fundamentals of the REST architectural concepts in the context of a virtualization environment and provides examples of the API in operation. It also documents the installation and use of the Python Software Development Kit.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Evaluation Guide</em> enables prospective customers to evaluate the features of Red Hat Enterprise Virtualization. Use this guide if you have an evaluation license.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Installation Guide</em> describes the installation prerequisites and procedures. Read this if you need to install Red Hat Enterprise Virtualization. The installation of hosts, Manager and storage are covered in this guide. You will need to refer to the <em class="citetitle">Red Hat Enterprise Virtualization Administration Guide</em> to configure the system before you can start using the platform.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Manager Release Notes</em> contain release specific information for Red Hat Enterprise Virtualization Managers.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Power User Portal Guide</em> describes how power users can create and manage virtual machines from the Red Hat Enterprise Virtualization User Portal.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Quick Start Guide</em> provides quick and simple instructions for first time users to set up a basic Red Hat Enterprise Virtualization environment.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">oVirt — Technical Notes</em> describe the changes made between the current release and the previous one.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Red Hat Enterprise Virtualization — Technical Reference Guide</em> describes the technical architecture of Red Hat Enterprise Virtualization and its interactions with existing infrastructure.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Red Hat Enterprise Virtualization — User Portal Guide</em> describes how users of the Red Hat Enterprise Virtualization system can access and use virtual desktops from the User Portal.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html"><strong>Prev</strong>Chapter 1. Introduction</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_Host_Configuration_and_Guest_Installation_Guide-System_Requirements.html"><strong>Next</strong>Chapter 2. System requirements</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch03s02.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch03s02.html
new file mode 100644
index 0000000..0842e13
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch03s02.html
@@ -0,0 +1,75 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2. Supported CPU Models</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html" title="Chapter 3. KVM guest virtual machine compatibility" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html" title="Chapter 3. KVM guest virtual machine compatibility" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html" title="Chapter 4. Virtualization restrictions" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html"><strong>Next</strong></a></li></ul><div class="section" id="idm6125200"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm6125200">3.2. Supported CPU Models</h2></div></div></div><div class="para">
+ Fedora 19 supports the use of the following QEMU CPU model definitions:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><em class="parameter"><code>Opteron_G4</code></em></span></dt><dd><div class="para">
+ AMD Opteron 62xx (Gen 4 Class Opteron)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Opteron_G3</code></em></span></dt><dd><div class="para">
+ AMD Opteron 23xx (Gen 3 Class Opteron)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Opteron_G2</code></em></span></dt><dd><div class="para">
+ AMD Opteron 22xx (Gen 2 Class Opteron)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Opteron_G1</code></em></span></dt><dd><div class="para">
+ AMD Opteron 240 (Gen 1 Class Opteron)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>SandyBridge</code></em></span></dt><dd><div class="para">
+ Intel Xeon E312xx (Sandy Bridge)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Nehalem</code></em></span></dt><dd><div class="para">
+ Intel Core i7 9xx (Nehalem Class Core i7)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Penryn</code></em></span></dt><dd><div class="para">
+ Intel Core 2 Duo P9xxx (Penryn Class Core 2)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Conroe</code></em></span></dt><dd><div class="para">
+ Intel Celeron_4x0 (Conroe/Merom Class Core 2)
+ </div></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>Westmere</code></em></span></dt><dd><div class="para">
+ Westmere E56xx/L56xx/X56xx (Nehalem-C)
+ </div></dd></dl></div><div class="section" id="para-CPU_Models"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.2.1. Guest CPU models</h3></div></div></div><div class="para">
+ Historically, CPU model definitions were hard-coded in <span class="application"><strong>qemu</strong></span>. This method of defining CPU models was inflexible, and made it difficult to create virtual CPUs with feature sets that matched existing physical CPUs. Typically, users modified a basic CPU model definition with feature flags in order to provide the CPU characteristics required by a virtual machine. Unless these feature sets were carefully controlled, safe migration — which requires feature sets between current and prospective hosts to match — was difficult to support.
+ </div><div class="para">
+ <span class="application"><strong>qemu-kvm</strong></span> has now replaced most hard-wired definitions with configuration file based CPU model definitions. Definitions for a number of current processor models are now included by default, allowing users to specify features more accurately and migrate more safely.
+ </div><div class="para">
+ A list of supported guest CPU models can be viewed with the <code class="command">/usr/libexec/qemu-kvm -cpu ?model</code> command. This command outputs the <em class="parameter"><code>name</code></em> used to select the CPU model at the command line, and a model identifier that corresponds to a commercial instance of that processor class.
+ </div><div class="para">
+ Configuration details for all of these CPU models can be viewed with the <code class="command">/usr/libexec/qemu-kvm -cpu ?dump</code> command, but they are also stored in the <code class="filename">/usr/share/qemu-kvm/cpu-model/cpu-x86_64.conf</code> file by default. Each CPU model definition begins with <code class="literal">[cpudef]</code>, as shown:
+ </div><pre class="screen">[cpudef]
+ name = "Nehalem"
+ level = "2"
+ vendor = "GenuineIntel"
+ family = "6"
+ model = "26"
+ stepping = "3"
+ feature_edx = "sse2 sse fxsr mmx clflush pse36 pat cmov mca \
+ pge mtrr sep apic cx8 mce pae msr tsc pse de fpu"
+ feature_ecx = "popcnt x2apic sse4.2 sse4.1 cx16 ssse3 sse3"
+ extfeature_edx = "i64 syscall xd"
+ extfeature_ecx = "lahf_lm"
+ xlevel = "0x8000000A"
+ model_id = "Intel Core i7 9xx (Nehalem Class Core i7)"</pre><div class="para">
+ The four CPUID fields, <code class="literal">feature_edx</code>, <code class="literal">feature_ecx</code>, <code class="literal">extfeature_edx</code> and <code class="literal">extfeature_ecx</code>, accept named flag values from the corresponding feature sets listed by the <code class="command">/usr/libexec/qemu-kvm -cpu ?cpuid</code> command, as shown:
+ </div><pre class="screen"># /usr/libexec/qemu-kvm -cpu ?cpuid
+Recognized CPUID flags:
+ f_edx: pbe ia64 tm ht ss sse2 sse fxsr mmx acpi ds clflush pn \
+ pse36 pat cmov mca pge mtrr sep apic cx8 mce pae msr tsc \
+ pse de vme fpu
+ f_ecx: hypervisor avx osxsave xsave aes popcnt movbe x2apic \
+ sse4.2|sse4_2 sse4.1|sse4_1 dca pdcm xtpr cx16 fma cid \
+ ssse3 tm2 est smx vmx ds_cpl monitor dtes64 pclmuldq \
+ pni|sse3
+ extf_edx: 3dnow 3dnowext lm rdtscp pdpe1gb fxsr_opt fxsr mmx \
+ mmxext nx pse36 pat cmov mca pge mtrr syscall apic cx8 \
+ mce pae msr tsc pse de vme fpu
+ extf_ecx: nodeid_msr cvt16 fma4 wdt skinit xop ibs osvw \
+ 3dnowprefetch misalignsse sse4a abm cr8legacy extapic svm \
+ cmp_legacy lahf_lm</pre><div class="para">
+ These feature sets are described in greater detail in the appropriate Intel and AMD specifications.
+ </div><div class="para">
+ It is important to use the <code class="code">check</code> flag to verify that all configured features are available.
+ </div><pre class="screen"># /usr/libexec/qemu-kvm -cpu Nehalem,check
+warning: host cpuid 0000_0001 lacks requested flag 'sse4.2|sse4_2' [0x00100000]
+warning: host cpuid 0000_0001 lacks requested flag 'popcnt' [0x00800000]</pre><div class="para">
+ If a defined feature is not available, those features will fail silently by default.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html"><strong>Prev</strong>Chapter 3. KVM guest virtual machine compatibility</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_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html"><strong>Next</strong>Chapter 4. Virtualization restrictions</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch07s02.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch07s02.html
new file mode 100644
index 0000000..94bca94
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch07s02.html
@@ -0,0 +1,34 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.2. Creating a Red Hat Enterprise Linux 6 guest with a network installation tree</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html" title="Chapter 7. Installing a Red Hat Enterprise Linux 6 guest virtual machine on a Red Hat Enterprise Linux 6 host" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html" title="Chapter 7. Installing a Red Hat Enterprise Linux 6 guest virtual machine on a Red Hat Enterprise Linux 6 host" /><link rel="next" href="ch07s03.html" title="7.3. Creating a Red Hat Enterprise Linux 6 guest with PXE" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Com
mon_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_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch07s03.html"><strong>Next</strong></a></li></ul><div class="section" id="idp10256"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp10256">7.2. Creating a Red Hat Enterprise Linux 6 guest with a network installation tree</h2></div></div></div><div class="procedure"><h6>Procedure 7.2. Creating a Red Hat Enterprise Linux 6 guest with virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Optional: Preparation</strong></p><div class="para">
+ Prepare the storage environment for the guest virtual machine. For more information on preparing storage, refer to the <em class="citetitle">Red Hat Enterprise Linux 6 Virtualization Administration Guide</em>.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ >Various storage types may be used for storing guest virtual machines. However, for a virtual machine to be able to use migration features the virtual machine must be created on networked storage.
+ </div></div></div><div class="para">
+ Red Hat Enterprise Linux 6 requires at least 1GB of storage space. However, Red Hat recommends at least 5GB of storage space for a Red Hat Enterprise Linux 6 installation and for the procedures in this guide.
+ </div></li><li class="step"><p class="title"><strong>Open virt-manager and start the wizard</strong></p><div class="para">
+ Open virt-manager by executing the <code class="command">virt-manager</code> command as root or opening <span class="guilabel"><strong>Applications</strong></span> → <span class="guilabel"><strong>System Tools</strong></span> → <span class="guilabel"><strong>Virtual Machine Manager</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt1-pic1.png" alt="The main virt-manager window" /></div></div><h6>Figure 7.11. The main virt-manager window</h6></div><br class="figure-break" /><div class="para">
+ Click on the <span class="guibutton"><strong>Create a new virtual machine</strong></span> button to start the new virtual machine wizard.
+ </div><div class="figure" id="gofigurego2"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_newicon.png" alt="The Create a new virtual machine button" /></div></div><h6>Figure 7.12. The Create a new virtual machine button</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guilabel"><strong>Create a new virtual machine</strong></span> window opens.
+ </div></li><li class="step"><p class="title"><strong>Name the virtual machine</strong></p><div class="para">
+ Virtual machine names can contain letters, numbers and the following characters: '<span class="keycap"><strong>_</strong></span>', '<span class="keycap"><strong>.</strong></span>' and '<span class="keycap"><strong>-</strong></span>'. Virtual machine names must be unique for migration and cannot consist only of numbers.
+ </div><div class="para">
+ Choose the installation method from the list of radio buttons.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/rhel6_Screenshot-step1.png" width="444" alt="The New VM window - Step 1" /></div></div><h6>Figure 7.13. The New VM window - Step 1</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><div class="para">
+ Provide the installation URL, and the Kickstart URL and Kernel options if required.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt2-pic3.png" alt="The New VM window - Step 2" /></div></div><h6>Figure 7.14. The New VM window - Step 2</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><div class="para">
+ The remaining steps are the same as the ISO installation procedure. Continue from <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html#RAM-and-VCPUs">Step 5</a> of the ISO installation procedure.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html"><strong>Prev</strong>Chapter 7. Installing a Red Hat Enterprise Linux ...</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="ch07s03.html"><strong>Next</strong>7.3. Creating a Red Hat Enterprise Linux 6 guest ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch07s03.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch07s03.html
new file mode 100644
index 0000000..41ecee5
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch07s03.html
@@ -0,0 +1,30 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3. Creating a Red Hat Enterprise Linux 6 guest with PXE</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html" title="Chapter 7. Installing a Red Hat Enterprise Linux 6 guest virtual machine on a Red Hat Enterprise Linux 6 host" /><link rel="prev" href="ch07s02.html" title="7.2. Creating a Red Hat Enterprise Linux 6 guest with a network installation tree" /><link rel="next" href="ch08.html" title="Chapter 8. Virtualizing Fedora on Other Platforms" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="ch07s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch08.html"><strong>Next</strong></a></li></ul><div class="section" id="idm21965056"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm21965056">7.3. Creating a Red Hat Enterprise Linux 6 guest with PXE</h2></div></div></div><div class="procedure"><h6>Procedure 7.3. Creating a Red Hat Enterprise Linux 6 guest with virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Optional: Preparation</strong></p><div class="para">
+ Prepare the storage environment for the virtual machine. For more information on preparing storage, refer to the <em class="citetitle">Red Hat Enterprise Linux 6 Virtualization Administration Guide</em>.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Various storage types may be used for storing guest virtual machines. However, for a virtual machine to be able to use migration features the virtual machine must be created on networked storage.
+ </div></div></div><div class="para">
+ Red Hat Enterprise Linux 6 requires at least 1GB of storage space. However, Red Hat recommends at least 5GB of storage space for a Red Hat Enterprise Linux 6 installation and for the procedures in this guide.
+ </div></li><li class="step"><p class="title"><strong>Open virt-manager and start the wizard</strong></p><div class="para">
+ Open virt-manager by executing the <code class="command">virt-manager</code> command as root or opening <span class="guilabel"><strong>Applications</strong></span> → <span class="guilabel"><strong>System Tools</strong></span> → <span class="guilabel"><strong>Virtual Machine Manager</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt1-pic1.png" alt="The main virt-manager window" /></div></div><h6>Figure 7.15. The main virt-manager window</h6></div><br class="figure-break" /><div class="para">
+ Click on the <span class="guibutton"><strong>Create new virtualized guest</strong></span> button to start the new virtualized guest wizard.
+ </div><div class="figure" id="gofigurego3"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_newicon.png" alt="The create new virtualized guest button" /></div></div><h6>Figure 7.16. The create new virtualized guest button</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guilabel"><strong>New VM</strong></span> window opens.
+ </div></li><li class="step"><p class="title"><strong>Name the virtual machine</strong></p><div class="para">
+ Virtual machine names can contain letters, numbers and the following characters: '<span class="keycap"><strong>_</strong></span>', '<span class="keycap"><strong>.</strong></span>' and '<span class="keycap"><strong>-</strong></span>'. Virtual machine names must be unique for migration and cannot consist only of numbers.
+ </div><div class="para">
+ Choose the installation method from the list of radio buttons.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt3-pic2.png" alt="The New VM window - Step 1" /></div></div><h6>Figure 7.17. The New VM window - Step 1</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><div class="para">
+ The remaining steps are the same as the ISO installation procedure. Continue from <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html#RAM-and-VCPUs">Step 5</a> of the ISO installation procedure. From this point, the only difference in this PXE procedure is on the final <span class="guilabel"><strong>New VM</strong></span> screen, which shows the <span class="guilabel"><strong>Install: PXE Install</strong></span> field.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt3-pic6.png" alt="The New VM window - Step 5 - PXE Install" /></div></div><h6>Figure 7.18. The New VM window - Step 5 - PXE Install</h6></div><br class="figure-break" /></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s02.html"><strong>Prev</strong>7.2. Creating a Red Hat Enterprise Linux 6 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="ch08.html"><strong>Next</strong>Chapter 8. Virtualizing Fedora on Other Platforms</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch08.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch08.html
new file mode 100644
index 0000000..90b8c2c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch08.html
@@ -0,0 +1,16 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 8. Virtualizing Fedora on Other Platforms</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="ch07s03.html" title="7.3. Creating a Red Hat Enterprise Linux 6 guest with PXE" /><link rel="next" href="ch08s02.html" title="8.2. On Hyper-V" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="ch07s03.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n
" href="ch08s02.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="idp1407312" lang="en-US"><div class="titlepage"><div><div><h2 class="title" id="idp1407312">Chapter 8. Virtualizing Fedora on Other Platforms</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch08.html#idp12886800">8.1. On VMWare</a></span></dt><dt><span class="section"><a href="ch08s02.html">8.2. On Hyper-V</a></span></dt></dl></div><div class="para">
+ This chapter contains useful reference material for customers running Fedora as a virtualized operating system on other virtualization hosts.
+ </div><div class="section" id="idp12886800"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp12886800">8.1. On VMWare</h2></div></div></div><div class="para">
+ Fedora 17 and onwards provide the <code class="systemitem">vmxnet3</code> driver, a para-virtualized network adapter used when running Red Hat Enterprise Linux on VMWare hosts. For further information about this driver, refer to <a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001805">http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001805</a>.
+ </div><div class="para">
+ Fedora 18 and onwards provide the <code class="systemitem">vmw_pvscsi</code> driver, a para-virtualized SCSI adapter used when running Red Hat Enterprise Linux on VMWare hosts. For further information about this driver, refer to <a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010398">http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010398</a>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch07s03.html"><strong>Prev</strong>7.3. Creating a Red Hat Enterprise Linux 6 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="ch08s02.html"><strong>Next</strong>8.2. On Hyper-V</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch08s02.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch08s02.html
new file mode 100644
index 0000000..9522afa
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch08s02.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.2. On Hyper-V</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch08.html" title="Chapter 8. Virtualizing Fedora on Other Platforms" /><link rel="prev" href="ch08.html" title="Chapter 8. Virtualizing Fedora on Other Platforms" /><link rel="next" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html" title="Chapter 9. Installing a fully-virtualized Windows guest" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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/ima
ges/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html"><strong>Next</strong></a></li></ul><div class="section" id="idm8211904"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm8211904">8.2. On Hyper-V</h2></div></div></div><div class="para">
+ Fedora 18 and onwards provide Microsoft's Linux Integration Services, a set of drivers that enable synthetic device support in supported virtualized operating systems. Fedora is a supported virtualized operating system under Linux Integration Services version 3.4. Further details about the drivers provided are available from <a href="http://www.microsoft.com/en-us/download/details.aspx?id=34603">http://www.microsoft.com/en-us/download/details.aspx?id=34603</a>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08.html"><strong>Prev</strong>Chapter 8. Virtualizing Fedora on Other Platforms</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_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html"><strong>Next</strong>Chapter 9. Installing a fully-virtualized Windows...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch10s04.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch10s04.html
new file mode 100644
index 0000000..aa0ac6c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch10s04.html
@@ -0,0 +1,69 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.4. Using the para-virtualized drivers with Red Hat Enterprise Linux 3.9 guests</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html" title="Chapter 10. KVM Para-virtualized Drivers" /><link rel="prev" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html" title="10.3. Installing drivers during the Windows installation" /><link rel="next" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices.html" title="10.5. Using KVM para-virtualized drivers for existing devices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe
></div><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="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices.html"><strong>Next</strong></a></li></ul><div class="section" id="idp24174912"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp24174912">10.4. Using the para-virtualized drivers with Red Hat Enterprise Linux 3.9 guests</h2></div></div
></div><div class="para">
+ Para-virtualized drivers for Red Hat Enterprise Linux 3.9 consist of five kernel modules: <code class="command">virtio</code>, <code class="command">virtio_blk</code>, <code class="command">virtio_net</code>, <code class="command">virtio_pci</code> and <code class="command">virtio_ring</code>. All five modules must be loaded to use both the para-virtualized block and network devices drivers.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ For Red Hat Enterprise Linux 3.9 guests, the <span class="package">kmod-virtio</span> package is a requirement for the <code class="command">virtio</code> module.
+ </div></div></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ To use the network device driver only, load the <code class="command">virtio</code>, <code class="command">virtio_net</code> and <code class="command">virtio_pci</code> modules. To use the block device driver only, load the <code class="command">virtio</code>, <code class="command">virtio_ring</code>, <code class="command">virtio_blk</code> and <code class="command">virtio_pci</code> modules.
+ </div></div></div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The <span class="package">virtio</span> package modifies the initrd RAM disk file in the <code class="filename">/boot</code> directory. The original initrd file is saved to <code class="filename">/boot/initrd-<em class="replaceable"><code>kernel-version</code></em>.img.virtio.orig</code>. The original initrd file is replaced with a new initrd RAM disk containing the <code class="command">virtio</code> driver modules. The initrd RAM disk is modified to allow the virtual machine to boot from a storage device using the para-virtualized drivers. To use a different initrd file, you must ensure that drivers are loaded with the <code class="filename">sysinit</code> script (<a class="xref" href="ch10s04.html#proc1">Loading the para-virtualized drivers with the sysinit script</a>) or when creating new initrd RAM disk (<a class="xref" href="ch10s04.html#proc2">Adding the para-virtualized drivers to the initrd RAM disk</a>).
+ </div></div></div><div class="formalpara" id="proc1"><h5 class="formalpara">Loading the para-virtualized drivers with the sysinit script</h5>
+ This procedure covers loading the para-virtualized driver modules during the boot sequence on a Red Hat Enterprise Linux 3.9 or newer guest with the <code class="filename">sysinit</code> script. Note that the guest virtual machine cannot use the para-virtualized drivers for the default boot disk if the modules are loaded with the <code class="filename">sysinit</code> script.
+ </div><div class="para">
+ The drivers must be loaded in the following order:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <code class="command">virtio</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">virtio_ring</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">virtio_pci</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">virtio_blk</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">virtio_net</code>
+ </div></li></ol></div><div class="para">
+ <code class="command">virtio_net</code> and <code class="command">virtio_blk</code> are the only drivers whose order can be changed. If other drivers are loaded in a different order, they will not work.
+ </div><div class="para">
+ Next, configure the modules. Locate the following section of the <code class="filename">/etc/rc.d/rc.sysinit</code> file.
+ </div><pre class="screen">if [ -f /etc/rc.modules ]; then
+ /etc/rc.modules
+fi</pre><div class="para">
+ Append the following lines after that section:
+ </div><pre class="screen">if [ -f /etc/rc.modules ]; then
+ /etc/rc.modules
+fi
+
+modprobe virtio
+modprobe virtio_ring # Comment this out if you do not need block driver
+modprobe virtio_blk # Comment this out if you do not need block driver
+modprobe virtio_net # Comment this out if you do not need net driver
+modprobe virtio_pci</pre><div class="para">
+ Reboot the guest virtual machine to load the kernel modules.
+ </div><div class="formalpara" id="proc2"><h5 class="formalpara">Adding the para-virtualized drivers to the initrd RAM disk</h5>
+ This procedure covers loading the para-virtualized driver modules with the kernel on a Red Hat Enterprise Linux 3.9 or newer guest by including the modules in the initrd RAM disk. The mkinitrd tool configures the initrd RAM disk to load the modules. Specify the additional modules with the <em class="parameter"><code>--with</code></em> parameter for the <code class="command">mkinitrd</code> command. Append following set of parameters, in the exact order, when using the <code class="command">mkinitrd</code> command to create a custom initrd RAM disk:
+ </div><pre class="screen">--with virtio --with virtio_ring --with virtio_blk --with virtio_net --with virtio_pci</pre><div class="formalpara"><h5 class="formalpara" id="idm10765056">AMD64 and Intel 64 issues</h5>
+ Use the <code class="filename">x86_64</code> version of the <span class="package">virtio</span> package for AMD64 systems.
+ </div><div class="para">
+ Use the <code class="filename">ia32e</code> version of the <span class="package">virtio</span> package for Intel 64 systems. Using the <code class="filename">x86_64</code> version of the <span class="package">virtio</span> may cause a '<code class="computeroutput">Unresolved symbol</code>' error during the boot sequence on Intel 64 systems.
+ </div><div class="formalpara"><h5 class="formalpara" id="idp23194720">Network performance issues</h5>
+ If you experience low performance with the para-virtualized network drivers, verify the setting for the GSO and TSO features on the host system. The para-virtualized network drivers require that the GSO and TSO options are disabled for optimal performance.
+ </div><div class="para">
+ Verify the status of the GSO and TSO settings, use the command on the host (replacing <em class="replaceable"><code>interface</code></em> with the network interface used by the guest):
+ </div><pre class="screen"># ethtool -k <em class="replaceable"><code>interface</code></em></pre><div class="para">
+ Disable the GSO and TSO options with the following commands on the host:
+ </div><pre class="screen"># ethtool -K <em class="replaceable"><code>interface</code></em> gso off
+# ethtool -K <em class="replaceable"><code>interface</code></em> tso off</pre><div class="formalpara"><h5 class="formalpara" id="idm8112800">Para-virtualized driver swap partition issue</h5>
+ After activating the para-virtualized block device driver the swap partition may not be available. This issue is may be caused by a change in disk device name. To fix this issue, open the <code class="filename">/etc/fstab</code> file and locate the lines containing swap partitions, for example:
+ </div><pre class="screen">/dev/hda3 swap swap defaults 0 0</pre><div class="para">
+ The para-virtualized drivers use the <code class="command">/dev/vd*</code> naming convention, not the <code class="command">/dev/hd*</code> naming convention. To resolve this issue modify the incorrect swap entries in the <code class="filename">/etc/fstab</code> file to use the <code class="command">/dev/vd*</code> convention, for the example above:
+ </div><pre class="screen">/dev/vda3 swap swap defaults 0 0</pre><div class="para">
+ Save the changes and reboot the guest virtual machine. The virtual machine should now have swap partitions.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html"><strong>Prev</strong>10.3. Installing drivers during the Windows insta...</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="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices.html"><strong>Next</strong>10.5. Using KVM para-virtualized drivers for exis...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch11s02.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch11s02.html
new file mode 100644
index 0000000..4c2fe8b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch11s02.html
@@ -0,0 +1,23 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.2. Disabling vhost-net</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html" title="Chapter 11. Network configuration" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html" title="Chapter 11. Network configuration" /><link rel="next" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html" title="11.3. Bridged networking with libvirt" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/i
mage_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_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html"><strong>Next</strong></a></li></ul><div class="section" id="idp5118224"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp5118224">11.2. Disabling vhost-net</h2></div></div></div><div class="para">
+ The <code class="command">vhost-net</code> module is a kernel-level backend for virtio networking that reduces virtualization overhead by moving virtio packet processing tasks out of user space (the qemu process) and into the kernel (the <code class="systemitem">vhost-net</code> driver). vhost-net is only available for virtio network interfaces. If the vhost-net kernel module is loaded, it is enabled by default for all virtio interfaces, but can be disabled in the interface configuration in the case that a particular workload experiences a degradation in performance when vhost-net is in use.
+ </div><div class="para">
+ Specifically, when UDP traffic is sent from a host machine to a guest virtual machine on that host, performance degradation can occur if the guest virtual machine processes incoming data at a rate slower than the host machine sends it. In this situation, enabling <code class="command">vhost-net</code> causes the UDP socket's receive buffer to overflow more quickly, which results in greater packet loss. It is therefore better to disable <code class="command">vhost-net</code> in this situation to slow the traffic, and improve overall performance.
+ </div><div class="para">
+ To disable <code class="command">vhost-net</code>, edit the <code class="code"><interface></code> sub-element in the guest virtual machine's XML configuration file and define the network as follows:
+ </div><pre class="screen"><interface type="network">
+ ...
+ <model type="virtio"/>
+ <driver name="qemu"/>
+ ...
+</interface></pre><div class="para">
+ Setting the driver name to <code class="literal">qemu</code> forces packet processing into qemu user space, effectively disabling vhost-net for that interface.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html"><strong>Prev</strong>Chapter 11. 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_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html"><strong>Next</strong>11.3. Bridged networking with libvirt</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch12s03.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch12s03.html
new file mode 100644
index 0000000..c6fc95d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch12s03.html
@@ -0,0 +1,87 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.3. PCI device assignment with virt-install</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html" title="Chapter 12. PCI device configuration" /><link rel="prev" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host.html" title="12.2. Assigning a PCI device with virt-manager" /><link rel="next" href="ch12s04.html" title="12.4. Detaching an assigned PCI device" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch12s04.html"><strong>Next</strong></a></li></ul><div class="section" id="idm20975856"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm20975856">12.3. PCI device assignment with virt-install</h2></div></div></div><div class="para">
+ To use <span class="application"><strong>virt-install</strong></span> to assign a PCI device, use the <em class="parameter"><code>--host-device</code></em> parameter.
+ </div><div class="procedure"><h6>Procedure 12.5. Assigning a PCI device to a virtual machine with virt-install</h6><ol class="1"><li class="step"><p class="title"><strong>Identify the device</strong></p><div class="para">
+ Identify the PCI device designated for device assignment to the guest virtual machine.
+ </div><pre class="screen"># lspci | grep Ethernet
+00:19.0 Ethernet controller: Intel Corporation 82567LM-2 Gigabit Network Connection
+01:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
+01:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)</pre><div class="para">
+ The <code class="command">virsh nodedev-list</code> command lists all devices attached to the system, and identifies each PCI device with a string. To limit output to only PCI devices, run the following command:
+ </div><pre class="screen"># virsh nodedev-list --cap pci
+pci_0000_00_00_0
+pci_0000_00_01_0
+pci_0000_00_03_0
+pci_0000_00_07_0
+pci_0000_00_10_0
+pci_0000_00_10_1
+pci_0000_00_14_0
+pci_0000_00_14_1
+pci_0000_00_14_2
+pci_0000_00_14_3
+pci_0000_00_19_0
+pci_0000_00_1a_0
+pci_0000_00_1a_1
+pci_0000_00_1a_2
+pci_0000_00_1a_7
+pci_0000_00_1b_0
+pci_0000_00_1c_0
+pci_0000_00_1c_1
+pci_0000_00_1c_4
+pci_0000_00_1d_0
+pci_0000_00_1d_1
+pci_0000_00_1d_2
+pci_0000_00_1d_7
+pci_0000_00_1e_0
+pci_0000_00_1f_0
+pci_0000_00_1f_2
+pci_0000_00_1f_3
+pci_0000_01_00_0
+pci_0000_01_00_1
+pci_0000_02_00_0
+pci_0000_02_00_1
+pci_0000_06_00_0
+pci_0000_07_02_0
+pci_0000_07_03_0</pre><div class="para">
+ Record the PCI device number; the number is needed in other steps.
+ </div><div class="para">
+ Information on the domain, bus and function are available from output of the <code class="command">virsh nodedev-dumpxml</code> command:
+ </div><pre class="screen"># virsh nodedev-dumpxml pci_0000_01_00_0
+<device>
+ <name>pci_0000_01_00_0</name>
+ <parent>pci_0000_00_01_0</parent>
+ <driver>
+ <name>igb</name>
+ </driver>
+ <capability type='pci'>
+ <domain>0</domain>
+ <bus>1</bus>
+ <slot>0</slot>
+ <function>0</function>
+ <product id='0x10c9'>82576 Gigabit Network Connection</product>
+ <vendor id='0x8086'>Intel Corporation</vendor>
+ <capability type='virt_functions'>
+ </capability>
+ </capability>
+</device></pre></li><li class="step"><p class="title"><strong>Add the device</strong></p><div class="para">
+ Use the PCI identifier output from the <code class="command">virsh nodedev</code> command as the value for the <em class="parameter"><code>--host-device</code></em> parameter.
+ </div><pre class="screen">virt-install \
+--name=guest1-F19 \
+--disk path=/var/lib/libvirt/images/guest1-F19.img,size=8 \
+--nonsparse --graphics spice \
+--vcpus=2 --ram=2048 \
+--location=http://example1.com/installation_tree/f19-Server-x86_64/os \
+--nonetworks \
+--os-type=linux \
+--os-variant=fedora
+--host-device=<span class="emphasis"><em>pci_0000_01_00_0</em></span></pre></li><li class="step"><p class="title"><strong>Complete the installation</strong></p><div class="para">
+ Complete the guest installation. The PCI device should be attached to the guest.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host.html"><strong>Prev</strong>12.2. Assigning a PCI device 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="ch12s04.html"><strong>Next</strong>12.4. Detaching an assigned PCI device</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch12s04.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch12s04.html
new file mode 100644
index 0000000..3a90a93
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch12s04.html
@@ -0,0 +1,28 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.4. Detaching an assigned PCI device</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html" title="Chapter 12. PCI device configuration" /><link rel="prev" href="ch12s03.html" title="12.3. PCI device assignment with virt-install" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html" title="Chapter 13. SR-IOV" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="Documentati
on Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch12s03.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html"><strong>Next</strong></a></li></ul><div class="section" id="idp16289264"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp16289264">12.4. Detaching an assigned PCI device</h2></div></div></div><div class="para">
+ When a host PCI device has been assigned to a guest machine, the host can no longer use the device. Read this section to learn how to detach the device from the guest with <code class="command">virsh</code> or <span class="application"><strong>virt-manager</strong></span> so it is available for host use.
+ </div><div class="procedure"><h6>Procedure 12.6. Detaching a PCI device from a guest with virsh</h6><ol class="1"><li class="step"><p class="title"><strong>Detach the device</strong></p><div class="para">
+ Use the following command to detach the PCI device from the guest by removing it in the guest's XML file:
+ </div><pre class="screen"># virsh detach-device <em class="replaceable"><code>name_of_guest</code></em> <em class="replaceable"><code>file.xml</code></em></pre></li><li class="step"><p class="title"><strong>Re-attach the device to the host (optional)</strong></p><div class="para">
+ If the device is in <em class="parameter"><code>managed</code></em> mode, skip this step. The device will be returned to the host automatically.
+ </div><div class="para">
+ If the device is not using <em class="parameter"><code>managed</code></em> mode, use the following command to re-attach the PCI device to the host machine:
+ </div><pre class="screen"># virsh nodedev-reattach <em class="replaceable"><code>device</code></em></pre><div class="para">
+ For example, to re-attach the <code class="literal">pci_0000_01_00_0</code> device to the host:
+ </div><pre class="screen">virsh nodedev-reattach pci_0000_01_00_0</pre><div class="para">
+ The device is now available for host use.
+ </div></li></ol></div><div class="procedure"><h6>Procedure 12.7. Detaching a PCI Device from a guest with virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Open the virtual hardware details screen</strong></p><div class="para">
+ In <span class="application"><strong>virt-manager</strong></span>, double-click on the virtual machine that contains the device. Select the <span class="guilabel"><strong>Show virtual hardware details</strong></span> button to display a list of virtual hardware.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/vm_info_button_new.png" alt="The Show virtual hardware details button." /></div></div><h6>Figure 12.4. The virtual hardware details button</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Select and remove the device</strong></p><div class="para">
+ Select the PCI device to be detached from the list of virtual devices in the left panel.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/PCIremoval.png" width="444" alt="The PCI device details and the Remove button." /></div></div><h6>Figure 12.5. Selecting the PCI device to be detached</h6></div><br class="figure-break" /><div class="para">
+ Click the <span class="guibutton"><strong>Remove</strong></span> button to confirm. The device is now available for host use.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch12s03.html"><strong>Prev</strong>12.3. PCI device assignment with virt-install</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_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html"><strong>Next</strong>Chapter 13. SR-IOV</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch13s03.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch13s03.html
new file mode 100644
index 0000000..df2d1ec
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch13s03.html
@@ -0,0 +1,29 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>13.3. Troubleshooting SR-IOV</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html" title="Chapter 13. SR-IOV" /><link rel="prev" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html" title="13.2. Using SR-IOV" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management.html" title="Chapter 14. KVM guest timing management" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management.html"><strong>Next</strong></a></li></ul><div class="section" id="idp1134160"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp1134160">13.3. Troubleshooting SR-IOV</h2></div></div></div><div class="para">
+ This section contains solutions for problems which may affect SR-IOV.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Error starting the guest</span></dt><dd><div class="para">
+ When starting a configured virtual machine, an error occurs as follows:
+ </div><pre class="screen"># virsh start test
+error: Failed to start domain test
+error: internal error unable to start guest: char device redirected to
+/dev/pts/2
+get_real_device: /sys/bus/pci/devices/0000:03:10.0/config: Permission denied
+init_assigned_device: Error: Couldn't get real device (03:10.0)!
+Failed to initialize assigned device host=03:10.0</pre><div class="para">
+ This error is often caused by a device that is already assigned to another guest or to the host itself.
+ </div></dd><dt class="varlistentry"><span class="term">Error migrating, saving, or dumping the guest</span></dt><dd><div class="para">
+ Attempts to migrate and dump the virtual machine cause an error similar to the following:
+ </div><pre class="screen"># virsh dump --crash 5 /tmp/vmcore
+error: Failed to core dump domain 5 to /tmp/vmcore
+error: internal error unable to execute QEMU command 'migrate': An undefined
+error has occurred</pre><div class="para">
+ Because device assignment uses hardware on the specific host where the virtual machine was started, guest migration and save are not supported when device assignment is in use. Currently, the same limitation also applies to core-dumping a guest; this may change in the future.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html"><strong>Prev</strong>13.2. Using SR-IOV</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_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management.html"><strong>Next</strong>Chapter 14. KVM guest timing management</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch15s02.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch15s02.html
new file mode 100644
index 0000000..aad2f2d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch15s02.html
@@ -0,0 +1,29 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.2. Booting a guest using PXE</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html" title="Chapter 15. Network booting with libvirt" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html" title="Chapter 15. Network booting with libvirt" /><link rel="next" href="ch15s02s02.html" title="15.2.2. Using a private libvirt network" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch15s02s02.html"><strong>Next</strong></a></li></ul><div class="section" id="idm3779936"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm3779936">15.2. Booting a guest using PXE</h2></div></div></div><div class="para">
+ This section demonstrates how to boot a guest virtual machine with PXE.
+ </div><div class="section" id="idm3778464"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm3778464">15.2.1. Using bridged networking</h3></div></div></div><div class="procedure"><h6>Procedure 15.2. Booting a guest using PXE and bridged networking</h6><ol class="1"><li class="step"><div class="para">
+ Ensure bridging is enabled such that the PXE boot server is available on the network.
+ </div></li><li class="step"><div class="para">
+ Boot a guest virtual machine with PXE booting enabled. You can use the <code class="command">virt-install</code> command to create a new virtual machine with PXE booting enabled, as shown in the following example command:
+ </div><pre class="screen">virt-install --pxe --network bridge=breth0 --prompt</pre><div class="para">
+ Alternatively, ensure that the guest network is configured to use your bridged network, and that the XML guest configuration file has a <code class="code"><boot dev='network'/></code> element inside the <code class="code"><os></code> element, as shown in the following example:
+ </div><pre class="screen"><os>
+ <type arch='x86_64' machine='rhel6.2.0'>hvm</type>
+ <boot dev='network'/>
+ <boot dev='hd'/>
+</os>
+<interface type='bridge'>
+ <mac address='52:54:00:5a:ad:cb'/>
+ <source bridge='breth0'/>
+ <target dev='vnet0'/>
+ <alias name='net0'/>
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
+</interface></pre></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html"><strong>Prev</strong>Chapter 15. Network booting 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="ch15s02s02.html"><strong>Next</strong>15.2.2. Using a private libvirt network</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch15s02s02.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch15s02s02.html
new file mode 100644
index 0000000..bd18ab5
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch15s02s02.html
@@ -0,0 +1,28 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.2.2. Using a private libvirt network</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch15s02.html" title="15.2. Booting a guest using PXE" /><link rel="prev" href="ch15s02.html" title="15.2. Booting a guest using PXE" /><link rel="next" href="qemu-ga.html" title="Chapter 16. QEMU Guest Agent" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="ch15s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey
="n" href="qemu-ga.html"><strong>Next</strong></a></li></ul><div class="section" id="idp8070016"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idp8070016">15.2.2. Using a private libvirt network</h3></div></div></div><div class="procedure"><h6>Procedure 15.3. Using a private libvirt network</h6><ol class="1"><li class="step"><div class="para">
+ Configure PXE booting on libvirt as shown in <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html#setting-up-server-private">Section 15.1.1, “Setting up a PXE boot server on a private libvirt network”</a>.
+ </div></li><li class="step"><div class="para">
+ Boot a guest virtual machine using libvirt with PXE booting enabled. You can use the <code class="command">virt-install</code> command to create/install a new virtual machine using PXE:
+ </div><pre class="screen">virt-install --pxe --network network=default --prompt</pre></li></ol></div><div class="para">
+ Alternatively, ensure that the guest network is configured to use your bridged network, and that the XML guest configuration file has a <code class="code"><boot dev='network'/></code> element inside the <code class="code"><os></code> element, as shown in the following example:
+ </div><pre class="screen"><os>
+ <type arch='x86_64' machine='rhel6.2.0'>hvm</type>
+ <boot dev='network'/>
+ <boot dev='hd'/>
+</os></pre><div class="para">
+ Also ensure that the guest virtual machine is connected to the private network:
+ </div><pre class="screen"><interface type='network'>
+ <mac address='52:54:00:66:79:14'/>
+ <source network='default'/>
+ <target dev='vnet0'/>
+ <alias name='net0'/>
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
+</interface></pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s02.html"><strong>Prev</strong>15.2. Booting a guest using 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="qemu-ga.html"><strong>Next</strong>Chapter 16. QEMU Guest Agent</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch18s04.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch18s04.html
new file mode 100644
index 0000000..12cbb7c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch18s04.html
@@ -0,0 +1,28 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>18.4. Virtualization firewall information</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization-Security_for_virtualization.html" title="Chapter 18. Security for virtualization" /><link rel="prev" href="sect-Virtualization-Security_for_virtualization-SELinux_considerations.html" title="18.3. SELinux" /><link rel="next" href="chap-sVirt.html" title="Chapter 19. sVirt" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 accessk
ey="p" href="sect-Virtualization-Security_for_virtualization-SELinux_considerations.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-sVirt.html"><strong>Next</strong></a></li></ul><div class="section" id="idm15778720"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm15778720">18.4. Virtualization firewall information</h2></div></div></div><div class="para">
+ Various ports are used for communication between virtualized guests and management utilities.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Any network service on a virtualized guest must have the applicable ports open on the guest to allow external access. If a network service on a guest is firewalled it will be inaccessible. Always verify the guests network configuration first.
+ </div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ ICMP requests must be accepted. ICMP packets are used for network testing. You cannot ping guests if ICMP packets are blocked.
+ </div></li><li class="listitem"><div class="para">
+ Port 22 should be open for SSH access and the initial installation.
+ </div></li><li class="listitem"><div class="para">
+ Ports 80 or 443 (depending on the security settings on the RHEV Manager) are used by the vdsm-reg service to communicate information about the host.
+ </div></li><li class="listitem"><div class="para">
+ Ports 5634 to 6166 are used for guest console access with the SPICE protocol.
+ </div></li><li class="listitem"><div class="para">
+ Ports 49152 to 49216 are used for migrations with KVM. Migration may use any port in this range depending on the number of concurrent migrations occurring.
+ </div></li><li class="listitem"><div class="para">
+ Enabling IP forwarding (<code class="computeroutput">net.ipv4.ip_forward = 1</code>) is also required for shared bridges and the default bridge. Note that installing libvirt enables this variable so it will be enabled when the virtualization packages are installed unless it was manually disabled.
+ </div></li></ul></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Note that enabling IP forwarding is <span class="bold bold"><strong>not</strong></span> required for physical bridge devices. When a guest is connected through a physical bridge, traffic only operates at a level that does not require IP configuration such as IP forwarding.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Security_for_virtualization-SELinux_considerations.html"><strong>Prev</strong>18.3. SELinux</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-sVirt.html"><strong>Next</strong>Chapter 19. sVirt</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch19s02.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch19s02.html
new file mode 100644
index 0000000..7345a77
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch19s02.html
@@ -0,0 +1,52 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2. sVirt labeling</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-sVirt.html" title="Chapter 19. sVirt" /><link rel="prev" href="chap-sVirt.html" title="Chapter 19. sVirt" /><link rel="next" href="chap-Virtualization_Administration_Guide-KVM_live_migration.html" title="Chapter 20. KVM live migration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-sVirt.html"><strong>Prev</strong><
/a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_Guide-KVM_live_migration.html"><strong>Next</strong></a></li></ul><div class="section" id="idm21685984"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm21685984">19.2. sVirt labeling</h2></div></div></div><div class="para">
+ Like other services under the protection of SELinux, sVirt uses process-based mechanisms and restrictions to provide an extra layer of security over guest instances. Under typical use, you should not even notice that sVirt is working in the background. This section describes the labeling features of sVirt.
+ </div><div class="para">
+ As shown in the following output, when using sVirt, each virtualized guest process is labeled and runs with a dynamically generated level. Each process is isolated from other VMs with different levels:
+ </div><pre class="screen">
+# ps -eZ | grep qemu
+
+system_u:system_r:svirt_t:s0:c87,c520 27950 ? 00:00:17 qemu-kvm
+</pre><div class="para">
+ The actual disk images are automatically labeled to match the processes, as shown in the following output:
+ </div><pre class="screen">
+# ls -lZ /var/lib/libvirt/images/*
+
+ system_u:object_r:svirt_image_t:s0:c87,c520 image1
+</pre><div class="para">
+ The following table outlines the different labels that can be assigned when using sVirt:
+ </div><div class="table"><h6>Table 19.1. sVirt labels</h6><div class="table-contents"><table summary="sVirt labels" border="1"><colgroup><col align="left" class="c1" width="50%" /><col align="left" class="c2" width="50%" /></colgroup><thead><tr><th class="" align="left">
+ Type/Description
+ </th><th class="" align="left">
+ SELinux Context
+ </th></tr></thead><tbody><tr><td class="" align="left">
+ Virtualized guest processes. MCS1 is a random MCS field. Approximately 500,000 labels are supported.
+ </td><td class="" align="left">
+ system_u:system_r:svirt_t:MCS1
+ </td></tr><tr><td class="" align="left">
+ Virtualized guest images. Only <span class="emphasis"><em>svirt_t</em></span> processes with the same MCS fields can read/write these images.
+ </td><td class="" align="left">
+ system_u:object_r:svirt_image_t:MCS1
+ </td></tr><tr><td class="" align="left">
+ Virtualized guest shared read/write content. All <span class="emphasis"><em>svirt_t</em></span> processes can write to the svirt_image_t:s0 files.
+ </td><td class="" align="left">
+ system_u:object_r:svirt_image_t:s0
+ </td></tr><tr><td class="" align="left">
+ Virtualized guest shared read only content. All svirt_t processes can read these files/devices.
+ </td><td class="" align="left">
+ system_u:object_r:svirt_content_t:s0
+ </td></tr><tr><td class="" align="left">
+ Virtualized guest images. Default label for when an image exits. No <span class="emphasis"><em>svirt_t</em></span> virtual processes can read files/devices with this label.
+ </td><td class="" align="left">
+ system_u:object_r:virt_content_t:s0
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ It is also possible to perform static labeling when using sVirt. Static labels allow the administrator to select a specific label, including the MCS/MLS field, for a virtualized guest. Administrators who run statically-labeled virtualized guests are responsible for setting the correct label on the image files. The virtualized guest will always be started with that label, and the sVirt system will never modify the label of a statically-labeled virtual machine's content. This allows the sVirt component to run in an MLS environment. You can also run multiple virtualized guests with different sensitivity levels on a system, depending on your requirements.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-sVirt.html"><strong>Prev</strong>Chapter 19. sVirt</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_Administration_Guide-KVM_live_migration.html"><strong>Next</strong>Chapter 20. KVM live migration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch24s02.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch24s02.html
new file mode 100644
index 0000000..5cf051c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch24s02.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>24.2. Hugepage support</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_GuideAdvanced.html" title="Chapter 24. Advanced virtualization administration" /><link rel="prev" href="chap-Virtualization_Administration_GuideAdvanced.html" title="Chapter 24. Advanced virtualization administration" /><link rel="next" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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_Administration_GuideAdvanced.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html"><strong>Next</strong></a></li></ul><div class="section" id="idm12234000"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm12234000">24.2. Hugepage support</h2></div></div></div><div class="formalpara"><h5 class="formalpara" id="idp9606208">Introduction</h5>
+ x86 CPUs usually address memory in 4kB pages, but they are capable of using larger pages known as <span class="bold bold"><strong>huge pages</strong></span>. KVM guests can be deployed with huge page memory support in order to reduce memory consumption and improve performance by reducing CPU cache usage.
+ </div><div class="para">
+ By using huge pages for a KVM guest, less memory is used for page tables and TLB (Translation Lookaside Buffer) misses are reduced, thereby significantly increasing performance, especially for memory-intensive situations.
+ </div><div class="para">
+ <span class="bold bold"><strong>Transparent Hugepage Support</strong></span> is a kernel feature that reduces TLB entries needed for an application. By also allowing all free memory to be used as cache, performance is increased.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm11938864">Using Transparent Hugepage Support</h5>
+ To use Transparent Hugepage Support, no special configuration in the <code class="filename">qemu.conf</code> file is required. Hugepages are used by default if <code class="filename">/sys/kernel/mm/redhat_transparent_hugepage/enabled</code> is set to <span class="bold bold"><strong>always</strong></span>.
+ </div><div class="para">
+ Transparent Hugepage Support does not prevent the use of hugetlbfs. However, when hugetlbfs is not used, KVM will use transparent hugepages instead of the regular 4kB page size.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_GuideAdvanced.html"><strong>Prev</strong>Chapter 24. Advanced virtualization 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_Administration_Guide-Tips_and_tricks.html"><strong>Next</strong>Chapter 25. Miscellaneous administration tasks</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch25s05.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch25s05.html
new file mode 100644
index 0000000..961757d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch25s05.html
@@ -0,0 +1,179 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.5. Setting KVM processor affinities</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions.html" title="25.4. Verifying virtualization extensions" /><link rel="next" href="sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address.html" title="25.6. Generating a new unique MAC address" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-Tips_and_tricks-Verifying_virtualization_extensions.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="idm6391728" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm6391728">25.5. Setting KVM processor affinities</h2></div></div></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ <span class="application"><strong>libvirt</strong></span> refers to a NUMA node as a <span class="emphasis"><em>cell</em></span>.
+ </div></div></div><div class="para">
+ This section covers setting processor and processing core affinities with <span class="application"><strong>libvirt</strong></span> and KVM guests.
+ </div><div class="para">
+ By default, libvirt provisions guests using the hypervisor's default policy. For most hypervisors, the policy is to run guests on any available processing core or CPU. There are times when an explicit policy may be better, particularly for systems with a NUMA (Non-Uniform Memory Access) architecture. A guest on a NUMA system can be pinned to a processing core so that its memory allocations are always local to the node it is running on. This avoids cross-node memory transports which have less bandwidth and can significantly degrade performance.
+ </div><div class="para">
+ On non-NUMA systems some form of explicit placement across the hosts’ sockets, cores and hyperthreads may be more efficient.
+ </div><div class="formalpara"><h5 class="formalpara" id="idp8748784">Identifying CPU and NUMA topology</h5>
+ The first step in deciding which policy to apply is to determine the host’s memory and CPU topology. The <code class="command">virsh nodeinfo</code> command provides information about how many sockets, cores and hyperthreads are attached to a host.
+ </div><pre class="screen"># virsh nodeinfo
+CPU model: x86_64
+CPU(s): 8
+CPU frequency: 1000 MHz
+CPU socket(s): 2
+Core(s) per socket: 4
+Thread(s) per core: 1
+NUMA cell(s): 2
+Memory size: 8179176 kB</pre><div class="para">
+ This output shows that the system has eight CPU cores and two sockets. Each CPU socket has four cores. This splitting of CPU cores across multiple sockets suggests that the system has Non-Uniform Memory Access (NUMA) architecture.
+ </div><div class="para">
+ NUMA architecture can be more complex than other architectures. Use the <code class="command">virsh capabilities</code> command to get additional output data about the CPU configuration.
+ </div><pre class="programlisting"># virsh capabilities
+<capabilities>
+ <host>
+ <cpu>
+ <arch>x86_64</arch>
+ </cpu>
+ <migration_features>
+ <live/>
+ <uri_transports>
+ <uri_transport>tcp</uri_transport>
+ </uri_transports>
+ </migration_features>
+ <topology>
+ <cells num='2'>
+ <cell id='0'>
+ <cpus num='4'>
+ <cpu id='0'/>
+ <cpu id='1'/>
+ <cpu id='2'/>
+ <cpu id='3'/>
+ </cpus>
+ </cell>
+ <cell id='1'>
+ <cpus num='4'>
+ <cpu id='4'/>
+ <cpu id='5'/>
+ <cpu id='6'/>
+ <cpu id='7'/>
+ </cpus>
+ </cell>
+ </cells>
+ </topology>
+ <secmodel>
+ <model>selinux</model>
+ <doi>0</doi>
+ </secmodel>
+ </host>
+
+ <span class="emphasis"><em>[ Additional XML removed ]</em></span>
+
+</capabilities></pre><div class="para">
+ This output shows two NUMA nodes (also know as NUMA cells), each containing four logical CPUs (four processing cores). This system has two sockets, therefore it can be inferred that each socket is a separate NUMA node. For a guest with four virtual CPUs, it is optimal to lock the guest to physical CPUs 0 to 3, or 4 to 7, to avoid accessing non-local memory, which is significantly slower than accessing local memory.
+ </div><div class="para">
+ If a guest requires eight virtual CPUs, you could run two sets of four virtual CPU guests and split the work between them, since each NUMA node only has four physical CPUs. Running across multiple NUMA nodes significantly degrades performance for physical and virtualized tasks.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm17801376">Decide which NUMA node can run the guest</h5>
+ Locking a guest to a particular NUMA node offers no benefit if that node does not have sufficient free memory for that guest. libvirt stores information on the free memory available on each node. Use the <code class="command">virsh freecell --all</code> command to display the free memory on all NUMA nodes.
+ </div><pre class="screen"># virsh freecell --all
+0: 2203620 kB
+1: 3354784 kB</pre><div class="para">
+ If a guest requires 3 GB of RAM allocated, then the guest should be run on NUMA node (cell) 1. Node 0 only has 2.2GB free which may not be sufficient for certain guests.
+ </div><div class="formalpara"><h5 class="formalpara" id="idp20401264">Lock a guest to a NUMA node or physical CPU set</h5>
+ Once you have determined which node to run the guest on, refer to the capabilities data (the output of the <code class="command">virsh capabilities</code> command) about NUMA topology.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Extract from the <code class="command">virsh capabilities</code> output.
+ </div><pre class="screen"><topology>
+ <cells num='2'>
+ <cell id='0'>
+ <cpus num='4'>
+ <cpu id='0'/>
+ <cpu id='1'/>
+ <cpu id='2'/>
+ <cpu id='3'/>
+ </cpus>
+ </cell>
+ <cell id='1'>
+ <cpus num='4'>
+ <cpu id='4'/>
+ <cpu id='5'/>
+ <cpu id='6'/>
+ <cpu id='7'/>
+ </cpus>
+ </cell>
+ </cells>
+</topology></pre></li><li class="step"><div class="para">
+ Observe that the node 1, <code class="computeroutput"><cell id='1'></code>, uses physical CPUs 4 to 7.
+ </div></li><li class="step"><div class="para">
+ The guest can be locked to a set of CPUs by appending the <code class="computeroutput">cpuset</code> attribute to the configuration file.
+ </div><ol class="a"><li class="step"><div class="para">
+ While the guest is offline, open the configuration file with <code class="command">virsh edit</code>.
+ </div></li><li class="step"><div class="para">
+ Locate the guest's virtual CPU count, defined in the <code class="computeroutput">vcpus</code> element.
+ </div><pre class="screen"><vcpus>4</vcpus></pre><div class="para">
+ The guest in this example has four CPUs.
+ </div></li><li class="step"><div class="para">
+ Add a <code class="computeroutput">cpuset</code> attribute with the CPU numbers for the relevant NUMA cell.
+ </div><pre class="screen"><vcpus cpuset='4-7'>4</vcpus></pre></li></ol></li><li class="step"><div class="para">
+ Save the configuration file and restart the guest.
+ </div></li></ol></div><div class="para">
+ The guest has been locked to CPUs 4 to 7.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm6689536">Automatically locking guests to CPUs with virt-install</h5>
+ The <code class="command">virt-install</code> provisioning tool provides a simple way to automatically apply a 'best fit' NUMA policy when guests are created.
+ </div><div class="para">
+ The <em class="parameter"><code>cpuset</code></em> option for <code class="command">virt-install</code> can use a CPU set of processors or the parameter <em class="parameter"><code>auto</code></em>. The <em class="parameter"><code>auto</code></em> parameter automatically determines the optimal CPU locking using the available NUMA data.
+ </div><div class="para">
+ For a NUMA system, use the <em class="parameter"><code>--cpuset=auto</code></em> with the <code class="command">virt-install</code> command when creating new guests.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm13789872">Tuning CPU affinity on running guests</h5>
+ There may be times where modifying CPU affinities on running guests is preferable to rebooting the guest. The <code class="command">virsh vcpuinfo</code> and <code class="command">virsh vcpupin</code> commands can perform CPU affinity changes on running guests.
+ </div><div class="para">
+ The <code class="command">virsh vcpuinfo</code> command gives up to date information about where each virtual CPU is running.
+ </div><div class="para">
+ In this example, <em class="replaceable"><code>guest1</code></em> is a guest with four virtual CPUs is running on a KVM host.
+ </div><pre class="screen"># virsh vcpuinfo <em class="replaceable"><code>guest1</code></em>
+VCPU: 0
+CPU: 3
+State: running
+CPU time: 0.5s
+CPU Affinity: yyyyyyyy
+VCPU: 1
+CPU: 1
+State: running
+CPU Affinity: yyyyyyyy
+VCPU: 2
+CPU: 1
+State: running
+CPU Affinity: yyyyyyyy
+VCPU: 3
+CPU: 2
+State: running
+CPU Affinity: yyyyyyyy</pre><div class="para">
+ The <code class="command">virsh vcpuinfo</code> output (the <code class="computeroutput">yyyyyyyy</code> value of <code class="computeroutput">CPU Affinity</code>) shows that the guest can presently run on any CPU.
+ </div><div class="para">
+ To lock the virtual CPUs to the second NUMA node (CPUs four to seven), run the following commands.
+ </div><pre class="screen"># virsh vcpupin <em class="replaceable"><code>guest1</code></em> 0 4
+# virsh vcpupin <em class="replaceable"><code>guest1</code></em> 1 5
+# virsh vcpupin <em class="replaceable"><code>guest1</code></em> 2 6
+# virsh vcpupin <em class="replaceable"><code>guest1</code></em> 3 7</pre><div class="para">
+ The <code class="command">virsh vcpuinfo</code> command confirms the change in affinity.
+ </div><pre class="screen"># virsh vcpuinfo <em class="replaceable"><code>guest1</code></em>
+VCPU: 0
+CPU: 4
+State: running
+CPU time: 32.2s
+CPU Affinity: ----y---
+VCPU: 1
+CPU: 5
+State: running
+CPU time: 16.9s
+CPU Affinity: -----y--
+VCPU: 2
+CPU: 6
+State: running
+CPU time: 11.9s
+CPU Affinity: ------y-
+VCPU: 3
+CPU: 7
+State: running
+CPU time: 14.6s
+CPU Affinity: -------y</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions.html"><strong>Prev</strong>25.4. 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-Tips_and_tricks-Generating_a_new_unique_MAC_address.html"><strong>Next</strong>25.6. Generating a new unique MAC address</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch25s07.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch25s07.html
new file mode 100644
index 0000000..0a864a4
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch25s07.html
@@ -0,0 +1,42 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.7. Improving guest response time</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address.html" title="25.6. Generating a new unique MAC address" /><link rel="next" href="sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html" title="25.8. Disable SMART disk monitoring for guests" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-Tips_and_tricks-Generating_a_new_unique_MAC_address.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html"><strong>Next</strong></a></li></ul><div class="section" id="idp4878768"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp4878768">25.7. Improving guest response time</h2></div></div></div><div class="para">
+ Guests can sometimes be slow to respond with certain workloads and usage patterns. Examples of situations which may cause slow or unresponsive guests:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Severely overcommitted memory.
+ </div></li><li class="listitem"><div class="para">
+ Overcommitted memory with high processor usage
+ </div></li><li class="listitem"><div class="para">
+ Other (not <code class="command">qemu-kvm</code> processes) busy or stalled processes on the host.
+ </div></li></ul></div><div class="para">
+ These types of workload may cause guests to appear slow or unresponsive. Usually, the guest's memory is eventually fully loaded into the host's main memory from swap. Once the guest is loaded in main memory, the guest will perform normally. Note, the process of loading a guest from swap to main memory may take several seconds per gigabyte of RAM assigned to the guest, depending on the type of storage used for swap and the performance of the components.
+ </div><div class="para">
+ KVM guests function as Linux processes. Linux processes are not permanently kept in main memory (physical RAM). The kernel scheduler swaps process memory into virtual memory (swap). Swap, with conventional hard disk drives, is thousands of times slower than main memory in modern computers. If a guest is inactive for long periods of time, the guest may be placed into swap by the kernel.
+ </div><div class="para">
+ KVM guests processes may be moved to swap regardless of whether memory is overcommitted or overall memory usage.
+ </div><div class="para">
+ Using unsafe overcommit levels or overcommitting with swap turned off guest processes or other critical processesis not recommended. Always ensure the host has sufficient swap space when overcommitting memory.
+ </div><div class="para">
+ For more information on overcommitting with KVM, refer to <a class="xref" href="sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM.html">Chapter 22, <em>Overcommitting with KVM</em></a>.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Virtual memory allows a Linux system to use more memory than there is physical RAM on the system. Underused processes are swapped out which allows active processes to use memory, improving memory utilization. Disabling swap reduces memory utilization as all processes are stored in physical RAM.
+ </div><div class="para">
+ If swap is turned off, do not overcommit guests. Overcommitting guests without any swap can cause guests or the host system to crash.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="idp16328768">Turning off swap</h5>
+ Swap usage can be completely turned off to prevent guests from being unresponsive while they are moved back to main memory. Swap may also not be desired for guests as it can be resource-intensive on some systems.
+ </div><div class="para">
+ The <code class="command">swapoff</code> command can disable all swap partitions and swap files on a system.
+ </div><pre class="screen"># swapoff -a</pre><div class="para">
+ To make this change permanent, remove <em class="parameter"><code>swap</code></em> lines from the <code class="filename">/etc/fstab</code> file and restart the host system.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm13287168">Using SSDs for swap</h5>
+ Using Solid State Drives (SSDs) for swap storage may improve the performance of guests.
+ </div><div class="para">
+ Using RAID arrays, faster disks or separate drives dedicated to swap may also improve performance.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address.html"><strong>Prev</strong>25.6. 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-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html"><strong>Next</strong>25.8. Disable SMART disk monitoring for guests</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch29s02.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch29s02.html
new file mode 100644
index 0000000..53cf128
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch29s02.html
@@ -0,0 +1,27 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>29.2. Configuration of vhostmd</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="vhostmd.html" title="Chapter 29. The Virtual Host Metrics Daemon (vhostmd)" /><link rel="prev" href="vhostmd.html" title="Chapter 29. The Virtual Host Metrics Daemon (vhostmd)" /><link rel="next" href="ch29s03.html" title="29.3. Starting and stopping the daemon" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="vhostmd.html"><str
ong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch29s03.html"><strong>Next</strong></a></li></ul><div class="section" id="idp156368"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp156368">29.2. Configuration of vhostmd</h2></div></div></div><div class="para">
+ After installing the package, but before starting the daemon, it is a good idea to understand exactly what metrics <span class="application"><strong>vhostmd</strong></span> will expose to guests, and how this happens.
+ </div><div class="para">
+ The metrics are controlled by the file <code class="filename">/etc/vhostmd/vhostmd.conf</code>.
+ </div><div class="para">
+ There are two parts of particular importance in this XML file. Firstly <em class="parameter"><code><update_period>60</update_period></code></em> controls how often the metrics are updated (in seconds). Since updating metrics can be an expensive operation, you can reduce the load on the host by increasing this period. Secondly, each <em class="parameter"><code><metric>...</metric></code></em> section controls what information is exposed by <span class="application"><strong>vhostmd</strong></span>. For example:
+ </div><pre class="screen"><metric type="string" context="host">
+ <name>HostName</name>
+ <action>hostname</action>
+</metric></pre><div class="para">
+ means that the hostname of the host is exposed to selected guests. To disable particular metrics, you can comment out <em class="parameter"><code><metric></code></em> sections by putting <code class="literal"><!-- ... --></code> around them. Note that disabling metrics may cause problems for guest software such as SAP that may rely on these metrics being available.
+ </div><div class="para">
+ When the daemon (also called <span class="application"><strong>vhostmd</strong></span>) is running, it writes the metrics into a temporary file called <code class="filename">/dev/shm/vhostmd0</code>. This file contains a small binary header followed by the selected metrics encoded as XML. In practice you can display this file with a tool like <span class="application"><strong>less</strong></span>. The file is updated every 60 seconds (or however often <em class="parameter"><code><update_period></code></em> was set).
+ </div><div class="para">
+ The vhostmd(8) man page contains a detailed description of the configuration file, as well as examples of the XML output in <code class="filename">/dev/shm/vhostmd0</code>. To read this, do:
+ </div><pre class="screen"># man vhostmd</pre><div class="para">
+ In addition, there is a README file which covers some of the same information:
+ </div><pre class="screen">less /usr/share/doc/vhostmd-*/README</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="vhostmd.html"><strong>Prev</strong>Chapter 29. The Virtual Host Metrics Daemon (vhos...</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="ch29s03.html"><strong>Next</strong>29.3. Starting and stopping the daemon</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch29s03.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch29s03.html
new file mode 100644
index 0000000..f0fa181
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch29s03.html
@@ -0,0 +1,18 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>29.3. Starting and stopping the daemon</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="vhostmd.html" title="Chapter 29. The Virtual Host Metrics Daemon (vhostmd)" /><link rel="prev" href="ch29s02.html" title="29.2. Configuration of vhostmd" /><link rel="next" href="ch29s04.html" title="29.4. Verifying that vhostmd is working from the host" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="ch29s02.html"><strong>Prev<
/strong></a></li><li class="next"><a accesskey="n" href="ch29s04.html"><strong>Next</strong></a></li></ul><div class="section" id="idp9772176"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp9772176">29.3. Starting and stopping the daemon</h2></div></div></div><div class="para">
+ The daemon (<span class="application"><strong>vhostmd</strong></span>) will not be started automatically. To enable it to be started at boot, run:
+ </div><pre class="screen"># /sbin/chkconfig vhostmd on</pre><div class="para">
+ To start the daemon running, do:
+ </div><pre class="screen"># /sbin/service vhostmd start</pre><div class="para">
+ To stop the daemon running, do:
+ </div><pre class="screen"># /sbin/service vhostmd stop</pre><div class="para">
+ To disable the daemon from being started at boot, do:
+ </div><pre class="screen"># /sbin/chkconfig vhostmd off</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch29s02.html"><strong>Prev</strong>29.2. Configuration of vhostmd</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="ch29s04.html"><strong>Next</strong>29.4. Verifying that vhostmd is working from the ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch29s04.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch29s04.html
new file mode 100644
index 0000000..1adc555
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch29s04.html
@@ -0,0 +1,19 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>29.4. Verifying that vhostmd is working from the host</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="vhostmd.html" title="Chapter 29. The Virtual Host Metrics Daemon (vhostmd)" /><link rel="prev" href="ch29s03.html" title="29.3. Starting and stopping the daemon" /><link rel="next" href="ch29s05.html" title="29.5. Configuring guests to see the metrics" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="ch29s03.html"><strong>Prev</s
trong></a></li><li class="next"><a accesskey="n" href="ch29s05.html"><strong>Next</strong></a></li></ul><div class="section" id="idp224496"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp224496">29.4. Verifying that vhostmd is working from the host</h2></div></div></div><div class="para">
+ A short time after the daemon has started, you should see a metrics disk appearing. Do:
+ </div><pre class="screen"># ls -l /dev/shm
+# less /dev/shm/vhostmd0</pre><div class="para">
+ This file has a short binary header, followed by XML. The <span class="application"><strong>less</strong></span> program identifies it as binary and asks:
+ </div><pre class="screen">"/dev/shm/vhostmd0" may be a binary file. See it anyway?</pre><div class="para">
+ Press the <span class="keycap"><strong>y</strong></span> key to indicate that you wish to view it.
+ </div><div class="para">
+ You should see the binary header appearing as garbled characters, followed by the <em class="parameter"><code><metrics></code></em> XML, and after that, many zero bytes (displayed as <code class="literal">^@^@^@</code>...).
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch29s03.html"><strong>Prev</strong>29.3. Starting and stopping the daemon</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="ch29s05.html"><strong>Next</strong>29.5. Configuring guests to see the metrics</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch29s05.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch29s05.html
new file mode 100644
index 0000000..52f985e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch29s05.html
@@ -0,0 +1,41 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>29.5. Configuring guests to see the metrics</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="vhostmd.html" title="Chapter 29. The Virtual Host Metrics Daemon (vhostmd)" /><link rel="prev" href="ch29s04.html" title="29.4. Verifying that vhostmd is working from the host" /><link rel="next" href="ch29s06.html" title="29.6. Using vm-dump-metrics in Fedora guests to verify operation" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="ch29s04.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch29s06.html"><strong>Next</strong></a></li></ul><div class="section" id="idm80112"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm80112">29.5. Configuring guests to see the metrics</h2></div></div></div><div class="para">
+ Although metrics are written to <code class="filename">/dev/shm/vhostmd0</code>, they are not made available to guests by default. The administrator must choose which guests get to see metrics, and must manually change the configuration of selected guests to see metrics.
+ </div><div class="para">
+ The guest must be shut down before the disk is attached. (Hot attaching the metrics disk is also possible, but only for a limited number of guest configurations. In particular it is NOT possible to hot-add the metrics disk to guests that do not have virtio / PV drivers installed. See the vhostmd README file for more information).
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ It is extremely important that the metrics disk is added in readonly mode to all guests. If this is not done, then it would be possible for a guest to modify the metrics and possibly subvert other guests that are reading it.
+ </div></div></div><div class="procedure"><h6>Procedure 29.1. Configuring KVM guests</h6><ol class="1"><li class="step"><div class="para">
+ Shut down the guest.
+ </div></li><li class="step"><div class="para">
+ Do:
+ </div><pre class="screen"># virsh edit GuestName</pre><div class="para">
+ and add the following section into <em class="parameter"><code><devices></code></em>:
+ </div><pre class="screen"><disk type='file' device='disk'>
+ <driver name='qemu' type='raw'/>
+ <source file='/dev/shm/vhostmd0'/>
+ <target dev='vdd' bus='virtio'/>
+ <readonly/>
+ </disk></pre></li><li class="step"><div class="para">
+ Reboot the guest.
+ </div></li></ol></div><div class="procedure"><h6>Procedure 29.2. Configuring Xen guests</h6><ol class="1"><li class="step"><div class="para">
+ Shut down the guest.
+ </div></li><li class="step"><div class="para">
+ Do:
+ </div><pre class="screen"># virsh edit GuestName</pre><div class="para">
+ and add the following section into <em class="parameter"><code><devices></code></em>:
+ </div><pre class="screen"><disk type='file' device='disk'>
+ <source dev='/dev/shm/vhostmd0'/>
+ <target dev='hdd' bus='ide'/>
+ <readonly/>
+ </disk></pre></li><li class="step"><div class="para">
+ Reboot the guest.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch29s04.html"><strong>Prev</strong>29.4. Verifying that vhostmd is working from the ...</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="ch29s06.html"><strong>Next</strong>29.6. Using vm-dump-metrics in Fedora guests to v...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch29s06.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch29s06.html
new file mode 100644
index 0000000..eca3f68
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/ch29s06.html
@@ -0,0 +1,24 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>29.6. Using vm-dump-metrics in Fedora guests to verify operation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="vhostmd.html" title="Chapter 29. The Virtual Host Metrics Daemon (vhostmd)" /><link rel="prev" href="ch29s05.html" title="29.5. Configuring guests to see the metrics" /><link rel="next" href="pt03.html" title="Part III. Appendicies" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="ch29s05.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="pt03.html"><strong>Next</strong></a></li></ul><div class="section" id="idm5823120"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm5823120">29.6. Using vm-dump-metrics in Fedora guests to verify operation</h2></div></div></div><div class="para">
+ Optionally, the <span class="package">vm-dump-metrics</span> package from the RHN Downloads area may be installed in Fedora guests. This package provides a simple command line tool (also called <span class="application"><strong>vm-dump-metrics</strong></span>) which allows host metrics to be displayed in the guest.
+ </div><div class="para">
+ This is useful for verifying correct operation of <span class="application"><strong>vhostmd</strong></span> from a guest.
+ </div><div class="para">
+ In the guest, run the following command as root:
+ </div><pre class="screen"># vm-dump-metrics</pre><div class="para">
+ If everything is working, this should print out a long XML document starting with <code class="literal"><metrics></code>.
+ </div><div class="para">
+ If this does not work, then verify that the metrics disk has appeared in the guest. It should appear as <code class="filename">/dev/vd*</code> (for example, <code class="filename">/dev/vdb</code>, <code class="filename">/dev/vdd</code>).
+ </div><div class="para">
+ On the host, verify that the libvirt configuration changes have been made by using the command:
+ </div><pre class="screen"># virsh dumpxml GuestName</pre><div class="para">
+ Verify that vhostmd is running on the host and the /dev/shm/vhostmd0 file exists.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch29s05.html"><strong>Prev</strong>29.5. Configuring guests to see the metrics</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="pt03.html"><strong>Next</strong>Part III. Appendicies</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-KSM.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-KSM.html
new file mode 100644
index 0000000..b78cc8b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-KSM.html
@@ -0,0 +1,101 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 23. KSM</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt02.html" title="Part II. Administration" /><link rel="prev" href="sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM.html" title="Chapter 22. Overcommitting with KVM" /><link rel="next" href="chap-Virtualization_Administration_GuideAdvanced.html" title="Chapter 24. Advanced virtualization administration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 cla
ss="previous"><a accesskey="p" href="sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_GuideAdvanced.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-KSM" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 23. KSM</h2></div></div></div><div class="para">
+ The concept of shared memory is common in modern operating systems. For example, when a program is first started it shares all of its memory with the parent program. When either the child or parent program tries to modify this memory, the kernel allocates a new memory region, copies the original contents and allows the program to modify this new region. This is known as copy on write.
+ </div><div class="para">
+ KSM is a new Linux feature which uses this concept in reverse. KSM enables the kernel to examine two or more already running programs and compare their memory. If any memory regions or pages are identical, KSM reduces multiple identical memory pages to a single page. This page is then marked copy on write. If the contents of the page is modified by a guest, a new page is created for that guest.
+ </div><div class="para">
+ This is useful for virtualization with KVM. When a guest is started, it only inherits the memory from the parent <code class="systemitem">qemu-kvm</code> process. Once the guest is running the contents of the guest operating system image can be shared when guests are running the same operating system or applications. KSM only identifies and merges identical pages which does not interfere with the guest or impact the security of the host or the guests. KSM allows KVM to request that these identical guest memory regions be shared.
+ </div><div class="para">
+ KSM provides enhanced memory speed and utilization. With KSM, common process data is stored in cache or in main memory. This reduces cache misses for the KVM guests which can improve performance for some applications and operating systems. Secondly, sharing memory reduces the overall memory usage of guests which allows for higher densities and greater utilization of resources.
+ </div><div class="para">
+ Starting in Fedora 18, KSM is NUMA aware
+ </div><div class="para">
+ Fedora uses two separate methods for controlling KSM:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <code class="systemitem">ksm</code> service starts and stops the KSM kernel thread.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="systemitem">ksmtuned</code> service controls and tunes the <code class="systemitem">ksm</code>, dynamically managing same-page merging. The <code class="systemitem">ksmtuned</code> service starts <code class="systemitem">ksm</code> and stops the <code class="systemitem">ksm</code> service if memory sharing is not necessary. The <code class="systemitem">ksmtuned</code> service must be told with the <em class="parameter"><code>retune</code></em> parameter to run when new guests are created or destroyed.
+ </div></li></ul></div><div class="para">
+ Both of these services are controlled with the standard service management tools.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm17948656">The KSM service</h5>
+ The <code class="systemitem">ksm</code> service is included in the <span class="package">qemu-kvm</span> package. KSM is off by default on Fedora. When using Fedora as a KVM host, however, it is likely turned on by the <code class="systemitem">ksm/ksmtuned</code> services.
+ </div><div class="para">
+ When the <code class="systemitem">ksm</code> service is not started, KSM shares only 2000 pages. This default is low and provides limited memory saving benefits.
+ </div><div class="para">
+ When the <code class="systemitem">ksm</code> service is started, KSM will share up to half of the host system's main memory. Start the <code class="systemitem">ksm</code> service to enable KSM to share more memory.
+ </div><pre class="screen"># service ksm start
+Starting ksm: [ OK ]</pre><div class="para">
+ The <code class="systemitem">ksm</code> service can be added to the default startup sequence. Make the <code class="systemitem">ksm</code> service persistent with the chkconfig command.
+ </div><pre class="screen"># chkconfig ksm on</pre><div class="formalpara"><h5 class="formalpara" id="idm17897504">The KSM tuning service</h5>
+ The <code class="systemitem">ksmtuned</code> service does not have any options. The <code class="systemitem">ksmtuned</code> service loops and adjusts <code class="systemitem">ksm</code>. The <code class="systemitem">ksmtuned</code> service is notified by libvirt when a guest is created or destroyed.
+ </div><pre class="screen"># service ksmtuned start
+Starting ksmtuned: [ OK ]</pre><div class="para">
+ The <code class="systemitem">ksmtuned</code> service can be tuned with the <em class="parameter"><code>retune</code></em> parameter. The <em class="parameter"><code>retune</code></em> parameter instructs <code class="systemitem">ksmtuned</code> to run tuning functions manually.
+ </div><div class="para">
+ The <code class="filename">/etc/ksmtuned.conf</code> file is the configuration file for the <code class="systemitem">ksmtuned</code> service. The file output below is the default <code class="filename">ksmtuned.conf</code> file.
+ </div><pre class="screen"># Configuration file for ksmtuned.
+
+# How long ksmtuned should sleep between tuning adjustments
+# KSM_MONITOR_INTERVAL=60
+
+# Millisecond sleep between ksm scans for 16Gb server.
+# Smaller servers sleep more, bigger sleep less.
+# KSM_SLEEP_MSEC=10
+
+# KSM_NPAGES_BOOST=300
+# KSM_NPAGES_DECAY=-50
+# KSM_NPAGES_MIN=64
+# KSM_NPAGES_MAX=1250
+
+# KSM_THRES_COEF=20
+# KSM_THRES_CONST=2048
+
+# uncomment the following to enable ksmtuned debug information
+# LOGFILE=/var/log/ksmtuned
+# DEBUG=1
+</pre><div class="formalpara"><h5 class="formalpara" id="idm11885424">KSM variables and monitoring</h5>
+ KSM stores monitoring data in the <code class="filename">/sys/kernel/mm/ksm/</code> directory. Files in this directory are updated by the kernel and are an accurate record of KSM usage and statistics.
+ </div><div class="para">
+ The variables in the list below are also configurable variables in the <code class="filename">/etc/ksmtuned.conf</code> file as noted below.
+ </div><div class="variablelist"><h6>The <code class="filename">/sys/kernel/mm/ksm/</code> files</h6><dl class="variablelist"><dt class="varlistentry"><span class="term">full_scans</span></dt><dd><div class="para">
+ Full scans run.
+ </div></dd><dt class="varlistentry"><span class="term">pages_shared</span></dt><dd><div class="para">
+ Total pages shared.
+ </div></dd><dt class="varlistentry"><span class="term">pages_sharing</span></dt><dd><div class="para">
+ Pages presently shared.
+ </div></dd><dt class="varlistentry"><span class="term">pages_to_scan</span></dt><dd><div class="para">
+ Pages not scanned.
+ </div></dd><dt class="varlistentry"><span class="term">pages_unshared</span></dt><dd><div class="para">
+ Pages no longer shared.
+ </div></dd><dt class="varlistentry"><span class="term">pages_volatile</span></dt><dd><div class="para">
+ Number of volatile pages.
+ </div></dd><dt class="varlistentry"><span class="term">run</span></dt><dd><div class="para">
+ Whether the KSM process is running.
+ </div></dd><dt class="varlistentry"><span class="term">sleep_millisecs</span></dt><dd><div class="para">
+ Sleep milliseconds.
+ </div></dd></dl></div><div class="para">
+ KSM tuning activity is stored in the <code class="filename">/var/log/ksmtuned</code> log file if the <em class="parameter"><code>DEBUG=1</code></em> line is added to the <code class="filename">/etc/ksmtuned.conf</code> file. The log file location can be changed with the <em class="parameter"><code>LOGFILE</code></em> parameter. Changing the log file location is not advised and may require special configuration of SELinux settings.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm133968">Deactivating KSM</h5>
+ KSM has a performance overhead which may be too large for certain environments or host systems.
+ </div><div class="para">
+ KSM can be deactivated by stopping the <code class="systemitem">ksmtuned</code> and the <code class="systemitem">ksm</code> service. Stopping the services deactivates KSM but does not persist after restarting.
+ </div><pre class="screen">
+# service ksmtuned stop
+Stopping ksmtuned: [ OK ]
+# service ksm stop
+Stopping ksm: [ OK ]
+
+</pre><div class="para">
+ Persistently deactivate KSM with the <code class="command">chkconfig</code> command. To turn off the services, run the following commands:
+ </div><pre class="screen"># chkconfig ksm off
+# chkconfig ksmtuned off</pre><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Ensure the swap size is sufficient for the committed RAM even with KSM. KSM reduces the RAM usage of identical or similar guests. Overcommitting guests with KSM without sufficient swap space may be possible but is not recommended because guest memory use can result in pages becoming unshared.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM.html"><strong>Prev</strong>Chapter 22. 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="chap-Virtualization_Administration_GuideAdvanced.html"><strong>Next</strong>Chapter 24. Advanced virtualization administration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization-Security_for_virtualization.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization-Security_for_virtualization.html
new file mode 100644
index 0000000..68b22a1
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization-Security_for_virtualization.html
@@ -0,0 +1,26 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 18. Security for virtualization</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt02.html" title="Part II. Administration" /><link rel="prev" href="chap-Virtualization_Administration_Guide-Server_best_practices.html" title="Chapter 17. Server best practices" /><link rel="next" href="sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization.html" title="18.2. SELinux and virtualization" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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_Administration_Guide-Server_best_practices.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization-Security_for_virtualization" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 18. Security for virtualization</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization-Security_for_virtualization.html#sect-Virtualization-Security_for_virtualization-Storage_security_issues">18.1. Storage security issues</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization.html">18.2. SELinux and virtualization</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Security_for_virtualizat
ion-SELinux_considerations.html">18.3. SELinux</a></span></dt><dt><span class="section"><a href="ch18s04.html">18.4. Virtualization firewall information</a></span></dt></dl></div><div class="para">
+ When deploying virtualization technologies, you must ensure that the host cannot be compromised. The host is a Fedora system that manages the system, devices, memory and networks as well as all virtualized guests. If the host is insecure, all guests 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 class="listitem"><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 class="listitem"><div class="para">
+ Enable SELinux on the hypervisor. Read <a class="xref" href="sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization.html">Section 18.2, “SELinux and virtualization”</a> for more information on using SELinux and virtualization.
+ </div></li><li class="listitem"><div class="para">
+ Use a firewall to restrict traffic to the host. You can setup a firewall with default-reject rules that will help secure the host from attacks. It is also important to limit network-facing services.
+ </div></li><li class="listitem"><div class="para">
+ Do not allow normal users to access the host. The host is privileged, and granting access to unprivileged accounts may compromise the level of security.
+ </div></li></ul></div><div class="section" id="sect-Virtualization-Security_for_virtualization-Storage_security_issues"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">18.1. Storage security issues</h2></div></div></div><div class="para">
+ Administrators of virtualized guests can change the partitions the host boots in certain circumstances. To prevent this administrators should follow these recommendations:
+ </div><div class="para">
+ The host should not use disk labels to identify file systems in the <code class="filename">fstab</code> file, the <code class="filename">initrd</code> file or used by the kernel command line. If less privileged users, especially virtualized guests, have write access to whole partitions or LVM volumes.
+ </div><div class="para">
+ Guests should not be given write access to whole disks or block devices (for example, <code class="filename">/dev/sdb</code>). Use partitions (for example, <code class="filename">/dev/sdb1</code>) or LVM volumes.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Server_best_practices.html"><strong>Prev</strong>Chapter 17. 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-Security_for_virtualization-SELinux_and_virtualization.html"><strong>Next</strong>18.2. SELinux and virtualization</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html
new file mode 100644
index 0000000..98d3f9d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html
@@ -0,0 +1,34 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix G. Guest disk access with offline tools</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt03.html" title="Part III. Appendicies" /><link rel="prev" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO.html" title="F.11. Displaying Network I/O" /><link rel="next" href="sect-Terminology-Guest_Disks_libguestfs.html" title="G.2. Terminology" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="previo
us"><a accesskey="p" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Terminology-Guest_Disks_libguestfs.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="appendix" id="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Guest disk access with offline tools</h1></div></div></div><div class="section" id="sect-introduction-Virtualization_Administration_Guide-Guest_Disks_libguestfs"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">G.1. Introduction</h2></div></div></div><div class="para">
+ Fedora comes with tools to access, edit and create guest disks or other disk images. There are several uses for these tools, including:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Viewing or downloading files located on a guest disk.
+ </div></li><li class="listitem"><div class="para">
+ Editing or uploading files onto a guest disk.
+ </div></li><li class="listitem"><div class="para">
+ Reading or writing guest configuration.
+ </div></li><li class="listitem"><div class="para">
+ Reading or writing the Windows Registry in Windows guests.
+ </div></li><li class="listitem"><div class="para">
+ Preparing new disk images containing files, directories, file systems, partitions, logical volumes and other options.
+ </div></li><li class="listitem"><div class="para">
+ Rescuing and repairing guests that fail to boot or those that need boot configuration changes.
+ </div></li><li class="listitem"><div class="para">
+ Monitoring disk usage of guests.
+ </div></li><li class="listitem"><div class="para">
+ Auditing compliance of guests, for example to organizational security standards.
+ </div></li><li class="listitem"><div class="para">
+ Deploying guests by cloning and modifying templates.
+ </div></li><li class="listitem"><div class="para">
+ Reading CD and DVD ISO and floppy disk images.
+ </div></li></ul></div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ You must <span class="bold bold"><strong>never</strong></span> use these tools to write to a guest or disk image which is attached to a running virtual machine, not even to open such a disk image in write mode. Doing so will result in disk corruption of the guest. The tools try to prevent you from doing this, however do not catch all cases. If there is any suspicion that a guest might be running, it is strongly recommended that the tools not be used, or at least <span class="bold bold"><strong>always</strong></span> use the tools in read-only mode.
+ </div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO.html"><strong>Prev</strong>F.11. Displaying Network I/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-Terminology-Guest_Disks_libguestfs.html"><strong>Next</strong>G.2. Terminology</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-KVM_live_migration.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-KVM_live_migration.html
new file mode 100644
index 0000000..6dcb0eb
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-KVM_live_migration.html
@@ -0,0 +1,64 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 20. KVM live migration</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt02.html" title="Part II. Administration" /><link rel="prev" href="ch19s02.html" title="19.2. sVirt labeling" /><link rel="next" href="Live_migration_and_RHEL_compatibility.html" title="20.2. Live migration and Fedora version compatibility" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="ch19s02.html"><strong>Prev</strong></a><
/li><li class="next"><a accesskey="n" href="Live_migration_and_RHEL_compatibility.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_Guide-KVM_live_migration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 20. KVM live migration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-KVM_live_migration.html#Live_migration_requirements">20.1. Live migration requirements</a></span></dt><dt><span class="section"><a href="Live_migration_and_RHEL_compatibility.html">20.2. Live migration and Fedora version compatibility </a></span></dt><dt><span class="section"><a href="shared-storage-nfs-migration.html">20.3. Shared storage example: NFS for a simple migration</a></span></dt><dt><span class="section"><a href="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html">20.4. Live KVM migration with virsh</a></spa
n></dt><dd><dl><dt><span class="section"><a href="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html#add-notes">20.4.1. Additonal tips for migration with virsh </a></span></dt><dt><span class="section"><a href="virsh-migration-arguements.html">20.4.2. Additional options for the virsh migrate command</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager.html">20.5. 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 describes the process of moving a guest from one host to another. This is possible because guests are running in a virtualized environment instead of directly on the hardware. Migration is useful for:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Load balancing - guests can be moved to hosts with lower usage when their host becomes overloaded, or another host is under-utilized.
+ </div></li><li class="listitem"><div class="para">
+ Hardware independence - when we need to upgrade, add, or remove hardware devices on the host, we can safely relocate guests to other hosts. This means that guests do not experience any downtime for hardware improvements.
+ </div></li><li class="listitem"><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 class="listitem"><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">
+ Migration works by sending the state of the guest's memory and any virtualized devices to a destination host. It is recommended to use shared, networked storage to store guest images to be migrated. It is also recommended to libvirt-managed storage pools for shared storage when migrating virtual machines.
+ </div><div class="para">
+ Migrations can be performed live or not.
+ </div><div class="para">
+ In a live migration, the guest continues to run on the source host while its memory pages are transferred, in order, to the destination host. During migration, KVM monitors the source for any changes in pages it has already transferred, and begins to transfer these changes when all of the initial pages have been transferred. KVM also estimates transfer speed during migration, so when the remaining amount of data to transfer will take a certain configurable period of time (10ms by default), KVM suspends the original guest, transfers the remaining data, and resumes the guest on the destination host.
+ </div><div class="para">
+ A migration that is not performed live, suspends the guest, then moves an image of the guest's memory to the destination host. The guest is then resumed on the destination host and the memory the guest used on the source host is freed. The time it takes to complete such a migration depends on network bandwidth and latency. If the network is experiencing heavy use or low bandwidth, the migration will take much longer.
+ </div><div class="para">
+ If the original guest modifies pages faster than KVM can transfer them to the destination host, offline migration must be used, as live migration would never complete.
+ </div><div class="section" id="Live_migration_requirements"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.1. Live migration requirements</h2></div></div></div><div class="para">
+ Migrating guests requires the following:
+ </div><div class="itemizedlist" id="item-Virtualization-Live_migration_requirements-Migration_requirements"><h6>Migration requirements</h6><ul><li class="listitem"><div class="para">
+ A guest installed on shared storage using one of the following protocols:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Fibre Channel-based LUNs
+ </div></li><li class="listitem"><div class="para">
+ iSCSI
+ </div></li><li class="listitem"><div class="para">
+ FCoE
+ </div></li><li class="listitem"><div class="para">
+ NFS
+ </div></li><li class="listitem"><div class="para">
+ GFS2
+ </div></li><li class="listitem"><div class="para">
+ SCSI RDMA protocols (SCSI RCP): the block export protocol used in Infiniband and 10GbE iWARP adapters
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Both systems must have the appropriate TCP/IP ports open.
+ </div></li><li class="listitem"><div class="para">
+ A separate system exporting the shared storage medium. Storage should not reside on either of the two hosts being used for migration.
+ </div></li><li class="listitem"><div class="para">
+ Shared storage must mount at the same location on source and destination systems. The mounted directory names must be identical. Although it is possible to keep the images using different paths, it is not recommended. Note that, if you are intending to use virt-manager to perform the migration, the path names must be identical. If however you intend to use virsh to perform the migration, different network configurations and mount directories can be used with the help of --xml option or pre-hooks when doing migrations. Even with out shared storage, migration can still succeed with the command <code class="command">--copy-storage-all</code>. For more information on <code class="command">prehooks</code>, refer to <a href="http://www.libvirt.org/hooks.html"> libvirt.org</a>, and for more information on the XML option, see the virsh manual.
+ </div></li><li class="listitem"><div class="para">
+ When migration is attempted on an existing guest in a public bridge+tap network, the source and destination hosts must be located in the same network. Otherwise, the guest network will not operate after migration.
+ </div></li></ul></div><div class="para">
+ Make sure that the <code class="filename">libvirtd</code> service is enabled (<code class="command"># chkconfig libvirtd on</code>) and running (<code class="command"># service libvirtd start</code>). It is also important to note that the ability to migrate effectively is dependent on the parameter settings in the <code class="filename">/etc/libvirt/libvirtd.conf</code> configuration file.
+ </div><div class="procedure" id="change-libvirt-config"><h6>Procedure 20.1. Configuring libvirtd.conf</h6><ol class="1"><li class="step"><div class="para">
+ Opening the <code class="filename">libvirtd.conf</code> requires running the command as root:
+ </div><pre class="screen"># vim /etc/libvirt/libvirtd.conf</pre></li><li class="step"><div class="para">
+ Change the parameters as needed and save the file.
+ </div></li><li class="step"><div class="para">
+ Restart the <code class="filename">libvirtd</code> service:
+ </div><pre class="screen"># service libvirtd restart</pre></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch19s02.html"><strong>Prev</strong>19.2. sVirt labeling</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="Live_migration_and_RHEL_compatibility.html"><strong>Next</strong>20.2. Live migration and Fedora version compatibi...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html
new file mode 100644
index 0000000..c3fcd80
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html
@@ -0,0 +1,38 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix F. Managing guests with the Virtual Machine Manager (virt-manager)</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt03.html" title="Part III. Appendicies" /><link rel="prev" href="apes14s04.html" title="E.14.4. Configuring the guest CPU model" /><link rel="next" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html" title="F.2. The Virtual Machine Manager main window" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="apes14s04.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="appendix" id="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Managing guests with the Virtual Machine Manager (virt-manager)</h1></div></div></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 guests on your host system and on remote host systems. <code class="command">virt-manager</code> can perform virtualization management tasks, including:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ defining and creating guests,
+ </div></li><li class="listitem"><div class="para">
+ assigning memory,
+ </div></li><li class="listitem"><div class="para">
+ assigning virtual CPUs,
+ </div></li><li class="listitem"><div class="para">
+ monitoring operational performance,
+ </div></li><li class="listitem"><div class="para">
+ saving and restoring, pausing and resuming, and shutting down and starting guests,
+ </div></li><li class="listitem"><div class="para">
+ links to the textual and graphical consoles, and
+ </div></li><li class="listitem"><div class="para">
+ live and offline migrations.
+ </div></li></ul></div><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Starting_virt_manager"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">F.1. 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_Administration_Guide-Starting_virt_manager-Starting_virt_manager"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt1.png" width="444" alt="Starting virt-manager" /></div></div><h6>Figure F.1. 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:
+ </div><pre class="screen">ssh -X <em class="replaceable"><code>host's address</code></em>
+[remotehost]# virt-manager
+</pre><div class="para">
+ Using <code class="command">ssh</code> to manage virtual machines and hosts is discussed further in <a class="xref" href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html#sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_with_SSH">Section 21.1, “Remote management with SSH”</a>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apes14s04.html"><strong>Prev</strong>E.14.4. Configuring the guest CPU model</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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html"><strong>Next</strong>F.2. The Virtual Machine Manager main window</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html
new file mode 100644
index 0000000..cb7f935
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html
@@ -0,0 +1,400 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix E. Managing guests with virsh</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt03.html" title="Part III. Appendicies" /><link rel="prev" href="apds10.html" title="D.10. Miscellaneous options" /><link rel="next" href="sect-Attaching_and_updating_a_device_with_virsh.html" title="E.2. Attaching and updating a device with virsh" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="apds10.html"><strong>Prev</stron
g></a></li><li class="next"><a accesskey="n" href="sect-Attaching_and_updating_a_device_with_virsh.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="appendix" id="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Managing guests with virsh</h1></div></div></div><div class="para">
+ <code class="command">virsh</code> is a command line interface tool for managing guests and the hypervisor. The <code class="command">virsh</code> command-line tool is built on the <code class="command">libvirt</code> management API and operates as an alternative to the <code class="command">qemu-kvm</code> command and the graphical <code class="command">virt-manager</code> application. The <code class="command">virsh</code> command can be used in read-only mode by unprivileged users or, with root access, full administration functionality. The <code class="command">virsh</code> command is ideal for scripting virtualization administration.
+ </div><div class="section" id="idp28563584"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp28563584">E.1. virsh command quick reference</h2></div></div></div><div class="para">
+ The following tables provide a quick reference for all virsh command line options.
+ </div><div class="table" id="tabl-Virtualization-Managing_guests_with_virsh-Guest_management_commands"><h6>Table E.1. Guest management commands</h6><div class="table-contents"><table summary="Guest management commands" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">help</code>
+ </td><td class="">
+ Prints basic help information.
+ </td></tr><tr><td class="">
+ <code class="command">list</code>
+ </td><td class="">
+ Lists all guests.
+ </td></tr><tr><td class="">
+ <code class="command">dumpxml</code>
+ </td><td class="">
+ Outputs the XML configuration file for the guest.
+ </td></tr><tr><td class="">
+ <code class="command">create</code>
+ </td><td class="">
+ Creates a guest from an XML configuration file and starts the new guest.
+ </td></tr><tr><td class="">
+ <code class="command">start</code>
+ </td><td class="">
+ Starts an inactive guest.
+ </td></tr><tr><td class="">
+ <code class="command">destroy</code>
+ </td><td class="">
+ Forces a guest to stop.
+ </td></tr><tr><td class="">
+ <code class="command">define</code>
+ </td><td class="">
+ Creates a guest from an XML configuration file without starting the new guest.
+ </td></tr><tr><td class="">
+ <code class="command">domid</code>
+ </td><td class="">
+ Displays the guest's ID.
+ </td></tr><tr><td class="">
+ <code class="command">domuuid</code>
+ </td><td class="">
+ Displays the guest's UUID.
+ </td></tr><tr><td class="">
+ <code class="command">dominfo</code>
+ </td><td class="">
+ Displays guest information.
+ </td></tr><tr><td class="">
+ <code class="command">domname</code>
+ </td><td class="">
+ Displays the guest's name.
+ </td></tr><tr><td class="">
+ <code class="command">domstate</code>
+ </td><td class="">
+ Displays the state of a guest.
+ </td></tr><tr><td class="">
+ <code class="command">quit</code>
+ </td><td class="">
+ Quits the interactive terminal.
+ </td></tr><tr><td class="">
+ <code class="command">reboot</code>
+ </td><td class="">
+ Reboots a guest.
+ </td></tr><tr><td class="">
+ <code class="command">restore</code>
+ </td><td class="">
+ Restores a previously saved guest stored in a file.
+ </td></tr><tr><td class="">
+ <code class="command">resume</code>
+ </td><td class="">
+ Resumes a paused guest.
+ </td></tr><tr><td class="">
+ <code class="command">save</code>
+ </td><td class="">
+ Saves the present state of a guest to a file.
+ </td></tr><tr><td class="">
+ <code class="command">shutdown</code>
+ </td><td class="">
+ Gracefully shuts down a guest.
+ </td></tr><tr><td class="">
+ <code class="command">suspend</code>
+ </td><td class="">
+ Pauses a guest.
+ </td></tr><tr><td class="">
+ <code class="command">undefine</code>
+ </td><td class="">
+ Deletes all files associated with a guest.
+ </td></tr><tr><td class="">
+ <code class="command">migrate</code>
+ </td><td class="">
+ Migrates a guest to another host.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The following <code class="command">virsh</code> command options manage guest and hypervisor resources:
+ </div><div class="table" id="tabl-Virtualization-Managing_guests_with_virsh-Resource_management_options"><h6>Table E.2. Resource management options</h6><div class="table-contents"><table summary="Resource management options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">setmem</code>
+ </td><td class="">
+ Sets the allocated memory for a guest. Refer to the <code class="command">virsh</code> manpage for more details.
+ </td></tr><tr><td class="">
+ <code class="command">setmaxmem</code>
+ </td><td class="">
+ Sets maximum memory limit for the hypervisor. Refer to the <code class="command">virsh</code> manpage for more details.
+ </td></tr><tr><td class="">
+ <code class="command">setvcpus</code>
+ </td><td class="">
+ Changes number of virtual CPUs assigned to a guest. Refer to the <code class="command">virsh</code> manpage for more details.
+ </td></tr><tr><td class="">
+ <code class="command">vcpuinfo</code>
+ </td><td class="">
+ Displays virtual CPU information about a guest.
+ </td></tr><tr><td class="">
+ <code class="command">vcpupin</code>
+ </td><td class="">
+ Controls the virtual CPU affinity of a guest.
+ </td></tr><tr><td class="">
+ <code class="command">domblkstat</code>
+ </td><td class="">
+ Displays block device statistics for a running guest.
+ </td></tr><tr><td class="">
+ <code class="command">domifstat</code>
+ </td><td class="">
+ Displays network interface statistics for a running guest.
+ </td></tr><tr><td class="">
+ <code class="command">attach-device</code>
+ </td><td class="">
+ Attach a device to a guest, using a device definition in an XML file.
+ </td></tr><tr><td class="">
+ <code class="command">attach-disk</code>
+ </td><td class="">
+ Attaches a new disk device to a guest.
+ </td></tr><tr><td class="">
+ <code class="command">attach-interface</code>
+ </td><td class="">
+ Attaches a new network interface to a guest.
+ </td></tr><tr><td class="">
+ <code class="command">update-device</code>
+ </td><td class="">
+ Detaches a disk image from a guest's CD-ROM drive. See <a class="xref" href="sect-Attaching_and_updating_a_device_with_virsh.html">Section E.2, “Attaching and updating a device with virsh”</a> for more details.
+ </td></tr><tr><td class="">
+ <code class="command">detach-device</code>
+ </td><td class="">
+ Detaches a device from a guest, takes the same kind of XML descriptions as command <code class="command">attach-device</code>.
+ </td></tr><tr><td class="">
+ <code class="command">detach-disk</code>
+ </td><td class="">
+ Detaches a disk device from a guest.
+ </td></tr><tr><td class="">
+ <code class="command">detach-interface</code>
+ </td><td class="">
+ Detach a network interface from a guest.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The <code class="command">virsh</code> commands for managing and creating storage pools and volumes.
+ </div><div class="para">
+ For more information on using storage pools with virsh, refer to <a href="http://libvirt.org/formatstorage.html">http://libvirt.org/formatstorage.html</a>
+ </div><div class="table" id="tabl-Virtualization-Managing_gunagement_options"><h6>Table E.3. Storage Pool options</h6><div class="table-contents"><table summary="Storage Pool options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">find-storage-pool-sources</code>
+ </td><td class="">
+ Returns the XML definition for all storage pools of a given type that could be found.
+ </td></tr><tr><td class="">
+ <code class="command">find-storage-pool-sources</code> <em class="parameter"><code>host port</code></em>
+ </td><td class="">
+ Returns data on all storage pools of a given type that could be found as XML. If the host and port are provided, this command can be run remotely.
+ </td></tr><tr><td class="">
+ <code class="command">pool-autostart </code>
+ </td><td class="">
+ Sets the storage pool to start at boot time.
+ </td></tr><tr><td class="">
+ <code class="command">pool-build</code>
+ </td><td class="">
+ The <code class="command">pool-build</code> command builds a defined pool. This command can format disks and create partitions.
+ </td></tr><tr><td class="">
+ <code class="command">pool-create</code>
+ </td><td class="">
+ <code class="command">pool-create</code> creates and starts a storage pool from the provided XML storage pool definition file.
+ </td></tr><tr><td class="">
+ <code class="command">pool-create-as name</code>
+ </td><td class="">
+ Creates and starts a storage pool from the provided parameters. If the <em class="parameter"><code>--print-xml</code></em> parameter is specified, the command prints the XML definition for the storage pool without creating the storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-define</code>
+ </td><td class="">
+ Creates a storage bool from an XML definition file but does not start the new storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-define-as name</code>
+ </td><td class="">
+ Creates but does not start, a storage pool from the provided parameters. If the <em class="parameter"><code>--print-xml</code></em> parameter is specified, the command prints the XML definition for the storage pool without creating the storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-destroy</code>
+ </td><td class="">
+ Permanently destroys a storage pool in <code class="command">libvirt</code>. The raw data contained in the storage pool is not changed and can be recovered with the <code class="command">pool-create</code> command.
+ </td></tr><tr><td class="">
+ <code class="command">pool-delete</code>
+ </td><td class="">
+ Destroys the storage resources used by a storage pool. This operation cannot be recovered. The storage pool still exists after this command but all data is deleted.
+ </td></tr><tr><td class="">
+ <code class="command">pool-dumpxml</code>
+ </td><td class="">
+ Prints the XML definition for a storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-edit</code>
+ </td><td class="">
+ Opens the XML definition file for a storage pool in the users default text editor.
+ </td></tr><tr><td class="">
+ <code class="command">pool-info</code>
+ </td><td class="">
+ Returns information about a storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-list</code>
+ </td><td class="">
+ Lists storage pools known to libvirt. By default, <code class="command">pool-list</code> lists pools in use by active guests. The <em class="parameter"><code>--inactive</code></em> parameter lists inactive pools and the <em class="parameter"><code>--all</code></em> parameter lists all pools.
+ </td></tr><tr><td class="">
+ <code class="command">pool-undefine</code>
+ </td><td class="">
+ Deletes the definition for an inactive storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-uuid</code>
+ </td><td class="">
+ Returns the UUID of the named pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-name </code>
+ </td><td class="">
+ Prints a storage pool's name when provided the UUID of a storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-refresh</code>
+ </td><td class="">
+ Refreshes the list of volumes contained in a storage pool.
+ </td></tr><tr><td class="">
+ <code class="command">pool-start</code>
+ </td><td class="">
+ Starts a storage pool that is defined but inactive.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><h6>Table E.4. Volume options</h6><div class="table-contents"><table summary="Volume options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">vol-create</code>
+ </td><td class="">
+ Create a volume from an XML file.
+ </td></tr><tr><td class="">
+ <code class="command">vol-create-from</code>
+ </td><td class="">
+ Create a volume using another volume as input.
+ </td></tr><tr><td class="">
+ <code class="command">vol-create-as</code>
+ </td><td class="">
+ Create a volume from a set of arguments.
+ </td></tr><tr><td class="">
+ <code class="command">vol-clone</code>
+ </td><td class="">
+ Clone a volume.
+ </td></tr><tr><td class="">
+ <code class="command">vol-delete</code>
+ </td><td class="">
+ Delete a volume.
+ </td></tr><tr><td class="">
+ <code class="command">vol-wipe</code>
+ </td><td class="">
+ Wipe a volume.
+ </td></tr><tr><td class="">
+ <code class="command">vol-dumpxml</code>
+ </td><td class="">
+ Show volume information in XML.
+ </td></tr><tr><td class="">
+ <code class="command">vol-info</code>
+ </td><td class="">
+ Show storage volume information.
+ </td></tr><tr><td class="">
+ <code class="command">vol-list</code>
+ </td><td class="">
+ List volumes.
+ </td></tr><tr><td class="">
+ <code class="command">vol-pool</code>
+ </td><td class="">
+ Returns the storage pool for a given volume key or path.
+ </td></tr><tr><td class="">
+ <code class="command">vol-path</code>
+ </td><td class="">
+ Returns the volume path for a given volume name or key.
+ </td></tr><tr><td class="">
+ <code class="command">vol-name</code>
+ </td><td class="">
+ Returns the volume name for a given volume key or path.
+ </td></tr><tr><td class="">
+ <code class="command">vol-key</code>
+ </td><td class="">
+ Returns the volume key for a given volume name or path.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><h6>Table E.5. Secret options</h6><div class="table-contents"><table summary="Secret options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">secret-define</code>
+ </td><td class="">
+ Define or modify a secret from an XML file.
+ </td></tr><tr><td class="">
+ <code class="command">secret-dumpxml</code>
+ </td><td class="">
+ Show secret attributes in XML.
+ </td></tr><tr><td class="">
+ <code class="command">secret-set-value</code>
+ </td><td class="">
+ Set a secret value.
+ </td></tr><tr><td class="">
+ <code class="command">secret-get-value</code>
+ </td><td class="">
+ Output a secret value.
+ </td></tr><tr><td class="">
+ <code class="command">secret-undefine</code>
+ </td><td class="">
+ Undefine a secret.
+ </td></tr><tr><td class="">
+ <code class="command">secret-list</code>
+ </td><td class="">
+ List secrets.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="table"><h6>Table E.6. Network filter options</h6><div class="table-contents"><table summary="Network filter options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">nwfilter-define</code>
+ </td><td class="">
+ Define or update a network filter from an XML file.
+ </td></tr><tr><td class="">
+ <code class="command">nwfilter-undefine</code>
+ </td><td class="">
+ Undefine a network filter.
+ </td></tr><tr><td class="">
+ <code class="command">nwfilter-dumpxml</code>
+ </td><td class="">
+ Show network filter information in XML.
+ </td></tr><tr><td class="">
+ <code class="command">nwfilter-list</code>
+ </td><td class="">
+ List network filters.
+ </td></tr><tr><td class="">
+ <code class="command">nwfilter-edit</code>
+ </td><td class="">
+ Edit XML configuration for a network filter.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ This table contains <code class="command">virsh</code> command options for snapshots:
+ </div><div class="table"><h6>Table E.7. Snapshot options</h6><div class="table-contents"><table summary="Snapshot options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">snapshot-create</code>
+ </td><td class="">
+ Create a snapshot.
+ </td></tr><tr><td class="">
+ <code class="command">snapshot-current</code>
+ </td><td class="">
+ Get the current snapshot.
+ </td></tr><tr><td class="">
+ <code class="command">snapshot-delete</code>
+ </td><td class="">
+ Delete a domain snapshot.
+ </td></tr><tr><td class="">
+ <code class="command">snapshot-dumpxml</code>
+ </td><td class="">
+ Dump XML for a domain snapshot.
+ </td></tr><tr><td class="">
+ <code class="command">snapshot-list</code>
+ </td><td class="">
+ List snapshots for a domain.
+ </td></tr><tr><td class="">
+ <code class="command">snapshot-revert</code>
+ </td><td class="">
+ Revert a domain to a snapshot.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ This table contains miscellaneous <code class="command">virsh</code> commands:
+ </div><div class="table" id="tabl-Virtualization-Managing_guests_with_virsh-Miscellaneous_options"><h6>Table E.8. Miscellaneous options</h6><div class="table-contents"><table summary="Miscellaneous options" border="1"><colgroup><col class="column1" width="50%" /><col class="column2" width="50%" /></colgroup><thead><tr><th class="">
+ Command
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="command">version</code>
+ </td><td class="">
+ Displays the version of <code class="command">virsh</code>.
+ </td></tr><tr><td class="">
+ <code class="command">nodeinfo</code>
+ </td><td class="">
+ Outputs information about the hypervisor.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apds10.html"><strong>Prev</strong>D.10. Miscellaneous options</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-Attaching_and_updating_a_device_with_virsh.html"><strong>Next</strong>E.2. Attaching and updating a device with virsh</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html
new file mode 100644
index 0000000..28fd824
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html
@@ -0,0 +1,22 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix D. qemu-kvm Whitelist</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt03.html" title="Part III. Appendicies" /><link rel="prev" href="netkvm-parameters.html" title="Appendix C. NetKVM Driver Parameters" /><link rel="next" href="apds02.html" title="D.2. Basic options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="netkvm-parameters.html"><strong>Prev</strong></a></li><li class="next"><a accessk
ey="n" href="apds02.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="appendix" id="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist" lang="en-US"><div class="titlepage"><div><div><h1 class="title">qemu-kvm Whitelist</h1></div></div></div><div class="section" id="idp4706576"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp4706576">D.1. Introduction</h2></div></div></div><h4 id="idp4243488">Product identification</h4><div class="para">
+ Fedora
+ </div><h4 id="idm4543424">Objectives</h4><div class="para">
+ The primary objective of this whitelist is to provide a complete list of the supported options of the <code class="command">qemu-kvm</code> utility used as an emulator and a virtualizer in Fedora. This is a comprehensive summary of the supported options.
+ </div><h4 id="idm12520320">Background</h4><div class="para">
+ Fedora uses KVM as an underlying virtualization technology. The machine emulator and virtualizer used is a modified version of QEMU called qemu-kvm. This version does not support all configuration options of the original QEMU and it adds some additional options.
+ </div><h4 id="idp23814992">Scope of the chapter</h4><h4 id="idm5787984">Used format</h4><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong><name></strong></span> - When used in a syntax description, this string shoud be replaced by user-defined value.
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>[a|b|c]</strong></span> - When used in a syntax description, only one of the strings separated by | is used.
+ </div></li><li class="listitem"><div class="para">
+ When no comment is present, an option is supported with all possible values.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="netkvm-parameters.html"><strong>Prev</strong>Appendix C. NetKVM Driver Parameters</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="apds02.html"><strong>Next</strong>D.2. Basic options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html
new file mode 100644
index 0000000..87c4a45
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html
@@ -0,0 +1,76 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 21. Remote management of guests</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt02.html" title="Part II. Administration" /><link rel="prev" href="sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager.html" title="20.5. Migrating with virt-manager" /><link rel="next" href="sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html" title="21.2. Remote management over TLS and SSL" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 21. Remote management of guests</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html#sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_with_SSH">21.1. Remote management with SSH</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Remote_management_of_virtualized_guests-Remote_ma
nagement_over_TLS_and_SSL.html">21.2. Remote management over TLS and SSL</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes.html">21.3. Transport modes</a></span></dt></dl></div><div class="para">
+ This section explains how to remotely manage your guests using <code class="command">ssh</code> or TLS and SSL. More information on SSH can be found in the <em class="citetitle">Fedora Deployment Guide</em>
+ </div><div class="section" id="sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_with_SSH"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">21.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 is tunneled over <span class="application"><strong>SSH</strong></span>.
+ </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><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ you require root log in access to the remote machine for managing virtual machines,
+ </div></li><li class="listitem"><div class="para">
+ the initial connection setup process may be slow,
+ </div></li><li class="listitem"><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 class="listitem"><div class="para">
+ ssh does not scale well with larger numbers of remote machines.
+ </div></li></ul></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Fedora enables remote management of large numbers of virtual machines. Refer to the oVirt documentation for further details.
+ </div></div></div><div class="para">
+ The following packages are required for ssh access:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="package">openssh</span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">openssh-askpass</span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">openssh-clients</span>
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">openssh-server</span>
+ </div></li></ul></div><div class="formalpara" id="form-Virtualization-Remote_management_with_SSH-Configuring_SSH_access_for_virt_manager"><h5 class="formalpara">Configuring password less or password managed <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. If you have SSH keys set up and copied to the other systems you can skip this procedure.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ SSH keys are user dependent and may only be used by their owners. A key's owner is the one who generated it. Keys may not be shared.
+ </div><div class="para">
+ <code class="command">virt-manager</code> must be run by the user who owns the keys to connect to the remote host. That means, if the remote systems are managed by a non-root user <code class="command">virt-manager</code> must be run in unprivileged mode. If the remote systems are managed by the local root user then the SSH keys must be owned and created by root.
+ </div><div class="para">
+ You cannot manage the local host as an unprivileged user with <code class="command">virt-manager</code>.
+ </div></div></div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Optional: Changing user</strong></p><div class="para">
+ Change user, if required. This example uses the local root user for remotely managing the other hosts and the local host.
+ </div><pre class="screen">$<code class="command"> su -</code></pre></li><li class="step"><p class="title"><strong>Generating the SSH key pair</strong></p><div class="para">
+ Generate a public key pair on the machine <code class="command">virt-manager</code> is used. This example uses the default key location, in the <code class="filename">~/.ssh/</code> directory.
+ </div><pre class="screen"># <code class="command">ssh-keygen -t rsa</code></pre></li><li class="step"><p class="title"><strong>Copying the keys to the remote hosts</strong></p><div class="para">
+ Remote login without a password, or with a passphrase, requires an SSH key to be distributed to the systems being managed. Use the <code class="command">ssh-copy-id</code> command to copy the key to root user at the system address provided (in the example, <em class="parameter"><code>root at host2.example.com</code></em>).
+ </div><pre class="screen"># <code class="command">ssh-copy-id -i ~/.ssh/id_rsa.pub root at host2.example.com</code>
+root at host2.example.com's password:
+</pre><div class="para">
+ Now try logging into the machine, with the <code class="command">ssh root at host2.example.com</code> command and check in the <code class="filename">.ssh/authorized_keys</code> file to make sure unexpected keys have not been added.
+ </div><div class="para">
+ Repeat for other systems, as required.
+ </div></li><li class="step"><p class="title"><strong>Optional: Add the passphrase to the ssh-agent</strong></p><div class="para">
+ The instructions below describe how to add a passphrase to an existing ssh-agent. It will fail to run if the ssh-agent is not running. To avoid errors or conflicts make sure that your SSH parameters are set correctly. Refer to the <em class="citetitle">Fedora Deployment Guide</em> for more information.
+ </div><div class="para">
+ Add the passphrase for the SSH key to the <code class="command">ssh-agent</code>, if required. On the local host, use the following command to add the passphrase (if there was one) to enable password-less login.
+ </div><pre class="screen"># <code class="command">ssh-add ~/.ssh/id_rsa.pub</code></pre><div class="para">
+ The SSH key is added to the remote system.
+ </div></li></ol></div><div class="formalpara" id="form-Virtualization-Remote_management_with_SSH-The_libvirt_daemon_libvirtd"><h5 class="formalpara">The <code class="command">libvirt</code> daemon (<code class="systemitem">libvirtd</code>)</h5>
+ The <code class="systemitem">libvirt</code> daemon provides an interface for managing virtual machines. You must have the <code class="systemitem">libvirtd</code> daemon installed and running on every remote host that needs managing.
+ </div><pre class="screen">$ <code class="command">ssh root@<em class="replaceable"><code>somehost</code></em></code>
+<code class="command"># chkconfig libvirtd on</code>
+<code class="command"># service libvirtd start</code></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 class="formalpara" id="form-Virtualization-Remote_management_with_SSH-Accessing_remote_hosts_with_virt_manager"><h5 class="formalpara">Accessing remote hosts with virt-manager</h5>
+ Remote hosts can be managed with the virt-manager GUI tool. SSH keys must belong to the user executing virt-manager for password-less login to work.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Start virt-manager.
+ </div></li><li class="step"><div class="para">
+ Open the <span class="guimenuitem"><strong>File</strong></span>-><span class="guimenuitem"><strong>Add Connection</strong></span> menu.
+ </div><div class="figure" id="add-connection"><div class="figure-contents"><div class="mediaobject"><img src="images/Virt-Manager-Add-Connection.png" alt="Add connection menu" /></div></div><h6>Figure 21.1. Add connection menu</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Use the drop down menu to select hypervisor type, and click the <span class="guimenuitem"><strong>Connect to remote host</strong></span> check box to open the Connection <span class="guimenuitem"><strong>Method</strong></span> (in this case Remote tunnel over SSH), and enter the desired <span class="guimenuitem"><strong>User name</strong></span> and <span class="guimenuitem"><strong>Hostname</strong></span>, then click <span class="guimenuitem"><strong>Connect</strong></span>.
+ </div></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager.html"><strong>Prev</strong>20.5. 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-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html"><strong>Next</strong>21.2. Remote management over TLS and SSL</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Server_best_practices.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Server_best_practices.html
new file mode 100644
index 0000000..c51af91
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Server_best_practices.html
@@ -0,0 +1,23 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 17. Server best practices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt02.html" title="Part II. Administration" /><link rel="prev" href="pt02.html" title="Part II. Administration" /><link rel="next" href="chap-Virtualization-Security_for_virtualization.html" title="Chapter 18. Security for virtualization" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="pt02.html"><strong>Prev</strong></a></li><
li class="next"><a accesskey="n" href="chap-Virtualization-Security_for_virtualization.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_Guide-Server_best_practices" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 17. 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 host.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Run SELinux in enforcing mode. Set SELinux to run in enforcing mode with the <code class="command">setenforce</code> command.
+ </div><pre class="screen"># setenforce 1
+</pre></li><li class="listitem"><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 class="listitem"><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 class="listitem"><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 class="listitem"><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. Use of shareable, network storage in a central location is highly recommended.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pt02.html"><strong>Prev</strong>Part II. 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-Security_for_virtualization.html"><strong>Next</strong>Chapter 18. Security for virtualization</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Storage_Concepts.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Storage_Concepts.html
new file mode 100644
index 0000000..c063981
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Storage_Concepts.html
@@ -0,0 +1,30 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 26. Storage concepts</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt02.html" title="Part II. Administration" /><link rel="prev" href="sect-dynamic-vNIC.html" title="25.16. Dynamically changing a host or a network bridge that is attached to a virtual NIC" /><link rel="next" href="sect-Virtualization-Storage_Concepts-Volumes.html" title="26.2. Volumes" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-dynamic-vNIC.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Storage_Concepts-Volumes.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_Guide-Storage_Concepts" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 26. Storage concepts</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Concepts.html#sect-Virtualization-Storage_Concepts-Storage_Pools">26.1. Storage pools</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Storage_Concepts-Volumes.html">26.2. Volumes </a></span></dt></dl></div><div class="para">
+ This chapter introduces the concepts used for describing and managing storage devices. Terms such as Storage Pools and Volumes are explained in the sections that follow.
+ </div><div class="section" id="sect-Virtualization-Storage_Concepts-Storage_Pools"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">26.1. Storage pools</h2></div></div></div><div class="para">
+ A <em class="firstterm">storage pool</em> is a file, directory, or storage device managed by libvirt for the purpose of providing storage to guests. The storage pool can be local or it can be shared over a network.
+ </div><div class="para">
+ libvirt uses a directory-based storage pool, the <code class="filename">/var/lib/libvirt/images/</code> directory, as the default storage pool. The default storage pool can be changed to another storage pool.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Local storage pools</strong></span> - Local storage pools are directly attached to the host server. Local storage pools include: local directories, directly attached disks, physical partitions, and LVM volume groups. These storage volumes store guest images or are attached to guests as additional storage. As local storage pools are directly attached to the host server, they are useful for development, testing and small deployments that do not require migration or large numbers of guests. Local storage pools are not suitable for many production environments as local storage pools do not support live migration.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>Networked (shared) storage pools</strong></span> - Networked storage pools include storage devices shared over a network using standard protocols. Networked storage is required when migrating virtual machines between hosts with virt-manager, but is optional when migrating with virsh. Networked storage pools are managed by libvirt. Supported protocols for networked storage pools include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Fibre Channel-based LUNs
+ </div></li><li class="listitem"><div class="para">
+ iSCSI
+ </div></li><li class="listitem"><div class="para">
+ NFS
+ </div></li><li class="listitem"><div class="para">
+ GFS2
+ </div></li><li class="listitem"><div class="para">
+ SCSI RDMA protocols (SCSI RCP), the block export protocol used in InfiniBand and 10GbE iWARP adapters.
+ </div></li></ul></div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-dynamic-vNIC.html"><strong>Prev</strong>25.16. Dynamically changing a host or a network b...</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-Storage_Concepts-Volumes.html"><strong>Next</strong>26.2. Volumes </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html
new file mode 100644
index 0000000..967aeca
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html
@@ -0,0 +1,793 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 27. Storage pools</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt02.html" title="Part II. Administration" /><link rel="prev" href="sect-Virtualization-Storage_Concepts-Volumes.html" title="26.2. Volumes" /><link rel="next" href="chap-Virtualization_Administration_Guide-Storage_Volumes.html" title="Chapter 28. Volumes" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-St
orage_Concepts-Volumes.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_Guide-Storage_Volumes.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 27. Storage pools</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating_Storage_Pools">27.1. Creating storage pools </a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-Dedicated_Disk_Devices">27.1.1. Disk-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Po
ols.html#sect-Virtualization-Storage_Pools-Creating-File_Systems">27.1.2. Partition-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-Local_Directories">27.1.3. Directory-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-LVM">27.1.4. LVM-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-iSCSI">27.1.5. iSCSI-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-NFS">27.1.6. NFS-based storage pools</a></span></dt></dl></dd></dl></div><div clas
s="para">
+ This chapter includes instructions on creating storage pools of assorted types. A <em class="firstterm">storage pool</em> is a quantity of storage set aside by an administrator, often a dedicated storage administrator, for use by virtual machines. Storage pools are often divided into storage volumes either by the storage administrator or the system administrator, and the volumes are assigned to guest virtual machines as block devices.
+ </div><div class="example"><h6>Example 27.1. NFS storage pool</h6><div class="example-contents"><div class="para">
+ Suppose a storage administrator responsible for an NFS server creates a share to store guest virtual machines' data. The system administrator defines a pool on the host with the details of the share (nfs.example.com:<code class="filename">/path/to/share</code> should be mounted on <code class="filename">/vm_data</code>). When the pool is started, libvirt mounts the share on the specified directory, just as if the system administrator logged in and executed <code class="command">mount nfs.example.com:/path/to/share /vmdata</code>. If the pool is configured to autostart, libvirt ensures that the NFS share is mounted on the directory specified when libvirt is started.
+ </div><div class="para">
+ Once the pool starts, the files that the NFS share, are reported as volumes, and the storage volumes' paths are then queried using the libvirt APIs. The volumes' paths can then be copied into the section of a guest virtual machine's XML definition file describing the source storage for the guest virtual machine's block devices. With NFS, applications using the libvirt APIs can create and delete volumes in the pool (files within the NFS share) up to the limit of the size of the pool (the maximum storage capacity of the share). Not all pool types support creating and deleting volumes. Stopping the pool negates the start operation, in this case, unmounts the NFS share. The data on the share is not modified by the destroy operation, despite the name. See man virsh for more details.
+ </div></div></div><br class="example-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Storage pools and volumes are not required for the proper operation of guest virtual machines. Pools and volumes provide a way for libvirt to ensure that a particular piece of storage will be available for a guest virtual machine, but some administrators will prefer to manage their own storage and guest virtual machines will operate properly without any pools or volumes defined. On systems that do not use pools, system administrators must ensure the availability of the guest virtual machines' storage using whatever tools they prefer, for example, adding the NFS share to the host's fstab so that the share is mounted at boot time.
+ </div></div></div><div class="section" id="sect-Virtualization-Storage_Pools-Creating_Storage_Pools"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">27.1. Creating storage pools </h2></div></div></div><div xml:lang="en-US" class="section" id="sect-Virtualization-Storage_Pools-Creating-Dedicated_Disk_Devices" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">27.1.1. Disk-based storage pools</h3></div></div></div><div class="para">
+ This section covers creating disk based storage devices for guest virtual machines.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Guests should not be given write access to whole disks or block devices (for example, <code class="filename">/dev/sdb</code>). Use partitions (for example, <code class="filename">/dev/sdb1</code>) or LVM volumes.
+ </div><div class="para">
+ If you pass an entire block device to the guest, the guest will likely partition it or create its own LVM groups on it. This can cause the host to detect these partitions or LVM groups and cause errors.
+ </div></div></div><div class="section" id="idm10178256"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm10178256">27.1.1.1. Creating a disk based storage pool using virsh</h4></div></div></div><div class="para">
+ This procedure creates a new storage pool using a disk device with the <code class="command">virsh</code> command.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Dedicating a disk to a storage pool will reformat and erase all data presently stored on the disk device! It is strongly recommended to back up the storage device before commencing with the following procedure:
+ </div></div></div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong> Create a GPT disk label on the disk </strong></p><div class="para">
+ The disk must be relabeled with a <em class="firstterm">GUID Partition Table</em> (GPT) disk label. GPT disk labels allow for creating a large numbers of partitions, up to 128 partitions, on each device. GPT partition tables can store partition data for far more partitions than the MS-DOS partition table.
+ </div><pre class="screen"># parted /dev/sdb
+GNU Parted 2.1
+Using /dev/sdb
+Welcome to GNU Parted! Type 'help' to view a list of commands.
+(parted) mklabel
+New disk label type? gpt
+(parted) quit
+Information: You may need to update /etc/fstab.
+#
+</pre></li><li class="step"><p class="title"><strong>Create the storage pool configuration file</strong></p><div class="para">
+ Create a temporary XML text file containing the storage pool information required for the new device.
+ </div><div class="para">
+ The file must be in the format shown below, and contain the following fields:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><name>guest_images_disk</name></span></dt><dd><div class="para">
+ The <em class="parameter"><code>name</code></em> parameter determines the name of the storage pool. This example uses the name <em class="replaceable"><code>guest_images_disk</code></em> in the example below.
+ </div></dd><dt class="varlistentry"><span class="term"> <device path='<em class="replaceable"><code>/dev/sdb</code></em>'/></span></dt><dd><div class="para">
+ The <em class="parameter"><code>device</code></em> parameter with the <em class="parameter"><code>path</code></em> attribute specifies the device path of the storage device. This example uses the device <em class="replaceable"><code>/dev/sdb</code></em>.
+ </div></dd><dt class="varlistentry"><span class="term"><target> <path><em class="replaceable"><code>/dev</code></em></path></target></span></dt><dd><div class="para">
+ The file system <em class="parameter"><code>target</code></em> parameter with the <em class="parameter"><code>path</code></em> sub-parameter determines the location on the host file system to attach volumes created with this storage pool.
+ </div><div class="para">
+ For example, sdb1, sdb2, sdb3. Using <em class="replaceable"><code>/dev/</code></em>, as in the example below, means volumes created from this storage pool can be accessed as <em class="replaceable"><code>/dev</code></em>/sdb1, <em class="replaceable"><code>/dev</code></em>/sdb2, <em class="replaceable"><code>/dev</code></em>/sdb3.
+ </div></dd><dt class="varlistentry"><span class="term"><format type='<em class="replaceable"><code>gpt</code></em>'/></span></dt><dd><div class="para">
+ The <em class="parameter"><code>format</code></em> parameter specifies the partition table type. This example uses the <em class="replaceable"><code>gpt</code></em> in the example below, to match the GPT disk label type created in the previous step.
+ </div></dd></dl></div><div class="para">
+ Create the XML file for the storage pool device with a text editor.
+ </div><div class="example"><h6>Example 27.2. Disk based storage device storage pool</h6><div class="example-contents"><pre class="screen">
+<pool type='disk'>
+ <name><em class="replaceable"><code>guest_images_disk</code></em></name>
+ <source>
+ <device path='<em class="replaceable"><code>/dev/sdb</code></em>'/>
+ <format type='<em class="replaceable"><code>gpt</code></em>'/>
+ </source>
+ <target>
+ <path><em class="replaceable"><code>/dev</code></em></path>
+ </target>
+</pool>
+</pre></div></div><br class="example-break" /></li><li class="step"><p class="title"><strong>Attach the device</strong></p><div class="para">
+ Add the storage pool definition using the <code class="command">virsh pool-define</code> command with the XML configuration file created in the previous step.
+ </div><pre class="screen"># virsh pool-define ~/guest_images_disk.xml
+Pool guest_images_disk defined from /root/guest_images_disk.xml
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_disk inactive no
+</pre></li><li class="step"><p class="title"><strong>Start the storage pool</strong></p><div class="para">
+ Start the storage pool with the <code class="command">virsh pool-start</code> command. Verify the pool is started with the <code class="command">virsh pool-list --all</code> command.
+ </div><pre class="screen"># virsh pool-start <em class="replaceable"><code>guest_images_disk</code></em>
+Pool guest_images_disk started
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_disk active no
+</pre></li><li class="step"><p class="title"><strong>Turn on autostart</strong></p><div class="para">
+ Turn on <em class="parameter"><code>autostart</code></em> for the storage pool. Autostart configures the <code class="systemitem">libvirtd</code> service to start the storage pool when the service starts.
+ </div><pre class="screen"># virsh pool-autostart <em class="replaceable"><code>guest_images_disk</code></em>
+Pool guest_images_disk marked as autostarted
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_disk active yes
+</pre></li><li class="step"><p class="title"><strong>Verify the storage pool configuration</strong></p><div class="para">
+ Verify the storage pool was created correctly, the sizes reported correctly, and the state reports as <code class="computeroutput">running</code>.
+ </div><pre class="screen"># virsh pool-info <em class="replaceable"><code>guest_images_disk</code></em>
+Name: guest_images_disk
+UUID: 551a67c8-5f2a-012c-3844-df29b167431c
+State: running
+Capacity: 465.76 GB
+Allocation: 0.00
+Available: 465.76 GB
+# ls -la /dev/sdb
+brw-rw----. 1 root disk 8, 16 May 30 14:08 /dev/sdb
+# virsh vol-list guest_images_disk
+Name Path
+-----------------------------------------
+</pre></li><li class="step"><p class="title"><strong>Optional: Remove the temporary configuration file</strong></p><div class="para">
+ Remove the temporary storage pool XML configuration file if it is not needed.
+ </div><pre class="screen"># rm ~/<em class="replaceable"><code>guest_images_disk</code></em>.xml</pre></li></ol></div><div class="para">
+ A disk based storage pool is now available.
+ </div></div><div class="section" id="delete-ded-disk-storage-pool"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">27.1.1.2. Deleting a storage pool using virsh</h4></div></div></div><div class="para">
+ The following demonstrates how to delete a storage pool using virsh:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it.
+ </div><pre class="screen"># virsh pool-destroy <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Remove the storage pool's definition
+ </div><pre class="screen"># virsh pool-undefine <em class="replaceable"><code>guest_images_disk</code></em></pre></li></ol></div></div></div><div xml:lang="en-US" class="section" id="sect-Virtualization-Storage_Pools-Creating-File_Systems" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">27.1.2. Partition-based storage pools</h3></div></div></div><div class="para">
+ This section covers using a pre-formatted block device, a partition, as a storage pool.
+ </div><div class="para">
+ For the following examples, a host has a 500GB hard drive (<code class="systemitem">/dev/sdc</code>) partitioned into one 500GB, ext4 formatted partition (<code class="systemitem">/dev/sdc1</code>). We set up a storage pool for it using the procedure below.
+ </div><div class="section" id="create-part-stor-pool"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">27.1.2.1. Creating a partition-based storage pool using virt-manager</h4></div></div></div><div class="para">
+ This procedure creates a new storage pool using a partition of a storage device.
+ </div><div class="procedure"><h6>Procedure 27.1. Creating a partition-based storage pool with virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Open the storage pool settings</strong></p><ol class="a"><li class="step"><div class="para">
+ In the <code class="command">virt-manager</code> graphical interface, select the host from the main window.
+ </div><div class="para">
+ Open the <span class="guilabel"><strong>Edit</strong></span> menu and select <span class="guilabel"><strong>Connection Details</strong></span>
+ </div><div class="figure" id="connection_details"><div class="figure-contents"><div class="mediaobject"><img src="images/Connection_Details.png" width="444" alt="Connection Details" /></div></div><h6>Figure 27.1. Connection Details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Click on the <span class="guilabel"><strong>Storage</strong></span> tab of the <span class="guilabel"><strong>Connection Details</strong></span> window.
+ </div><div class="figure" id="storage-tab"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Storage tab" /></div></div><h6>Figure 27.2. Storage tab</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Create the new storage pool</strong></p><ol class="a"><li class="step"><p class="title"><strong>Add a new pool (part 1)</strong></p><div class="para">
+ Press the <span class="guilabel"><strong>+</strong></span> button (the add pool button). The <span class="guilabel"><strong>Add a New Storage Pool</strong></span> wizard appears.
+ </div><div class="para">
+ Choose a <span class="guibutton"><strong>Name</strong></span> for the storage pool. This example uses the name <em class="replaceable"><code>guest_images_fs</code></em>. Change the <span class="guibutton"><strong>Type</strong></span> to <code class="command">fs: Pre-Formatted Block Device</code>.
+ </div><div class="figure" id="name-and-type"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_fs_step_1_name_and_type.png" width="444" alt="Storage pool name and type" /></div></div><h6>Figure 27.3. Storage pool name and type</h6></div><br class="figure-break" /><div class="para">
+ Press the <span class="guibutton"><strong>Forward</strong></span> button to continue.
+ </div></li><li class="step"><p class="title"><strong>Add a new pool (part 2)</strong></p><div class="para">
+ Change the <span class="guibutton"><strong>Target Path</strong></span>, <span class="guibutton"><strong>Format</strong></span>, and <span class="guibutton"><strong>Source Path</strong></span> fields.
+ </div><div class="figure" id="path-and-format"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_fs_step_2_paths_and_format.png" width="444" alt="Storage pool path and format" /></div></div><h6>Figure 27.4. Storage pool path and format</h6></div><br class="figure-break" /><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Target Path</span></dt><dd><div class="para">
+ Enter the location to mount the source device for the storage pool in the <span class="guibutton"><strong>Target Path</strong></span> field. If the location does not already exist, <code class="command">virt-manager</code> will create the directory.
+ </div></dd><dt class="varlistentry"><span class="term">Format</span></dt><dd><div class="para">
+ Select a format from the <span class="guibutton"><strong>Format</strong></span> list. The device is formatted with the selected format.
+ </div><div class="para">
+ This example uses the <em class="replaceable"><code>ext4</code></em> file system, the default Fedora file system.
+ </div></dd><dt class="varlistentry"><span class="term">Source Path</span></dt><dd><div class="para">
+ Enter the device in the <code class="command">Source Path</code> field.
+ </div><div class="para">
+ This example uses the <em class="replaceable"><code>/dev/sdc1</code></em> device.
+ </div></dd></dl></div><div class="para">
+ Verify the details and press the <span class="guibutton"><strong>Finish</strong></span> button to create the storage pool.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Verify the new storage pool</strong></p><div class="para">
+ The new storage pool appears in the storage list on the left after a few seconds. Verify the size is reported as expected, <em class="replaceable"><code>458.20 GB Free</code></em> in this example. Verify the <span class="guibutton"><strong>State</strong></span> field reports the new storage pool as <em class="replaceable"><code>Active</code></em>.
+ </div><div class="para">
+ Select the storage pool. In the <span class="guibutton"><strong>Autostart</strong></span> field, click the <span class="guibutton"><strong>On Boot</strong></span> checkbox. This will make sure the storage device starts whenever the <code class="systemitem">libvirtd</code> service starts.
+ </div><div class="figure" id="confirmation"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_fs_step_3_result.png" width="444" alt="Storage list confirmation" /></div></div><h6>Figure 27.5. Storage list confirmation</h6></div><br class="figure-break" /><div class="para">
+ The storage pool is now created, close the <span class="guilabel"><strong>Connection Details</strong></span> window.
+ </div></li></ol></div></div><div class="section" id="del-stor-pool-vmana-part"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">27.1.2.2. Deleting a storage pool using virt-manager</h4></div></div></div><div class="para">
+ This procedure demonstrates how to delete a storage pool.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it. To do this, select the storage pool you want to stop and click the red X icon at the bottom of the Storage window.
+ </div><div class="figure" id="stop-icon"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Stop Icon" /></div></div><h6>Figure 27.6. Stop Icon</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Delete the storage pool by clicking the Trash can icon. This icon is only enabled if you stop the storage pool first.
+ </div></li></ol></div></div><div class="section" id="idp11095424"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idp11095424">27.1.2.3. Creating a partition-based storage pool using virsh</h4></div></div></div><div class="para">
+ This section covers creating a partition-based storage pool with the <code class="command">virsh</code> command.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Do not use this procedure to assign an entire disk as a storage pool (for example, <code class="filename">/dev/sdb</code>). Guests should not be given write access to whole disks or block devices. Only use this method to assign partitions (for example, <code class="filename">/dev/sdb1</code>) to storage pools.
+ </div></div></div><div class="procedure"><h6>Procedure 27.2. Creating pre-formatted block device storage pools using virsh</h6><ol class="1"><li class="step"><p class="title"><strong> Create the storage pool definition </strong></p><div class="para">
+ Use the virsh <code class="command">pool-define-as</code> command to create a new storage pool definition. There are three options that must be provided to define a pre-formatted disk as a storage pool:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Partition name</span></dt><dd><div class="para">
+ The <em class="parameter"><code>name</code></em> parameter determines the name of the storage pool. This example uses the name <em class="replaceable"><code>guest_images_fs</code></em> in the example below.
+ </div></dd><dt class="varlistentry"><span class="term">device</span></dt><dd><div class="para">
+ The <em class="parameter"><code>device</code></em> parameter with the <em class="parameter"><code>path</code></em> attribute specifies the device path of the storage device. This example uses the partition <em class="replaceable"><code>/dev/sdc1</code></em>.
+ </div></dd><dt class="varlistentry"><span class="term">mountpoint</span></dt><dd><div class="para">
+ The <em class="parameter"><code>mountpoint</code></em> on the local file system where the formatted device will be mounted. If the mount point directory does not exist, the <code class="command">virsh</code> command can create the directory.
+ </div><div class="para">
+ The directory <em class="replaceable"><code>/guest_images</code></em> is used in this example.
+ </div></dd></dl></div><pre class="screen"># virsh pool-define-as <em class="replaceable"><code>guest_images_fs</code></em> fs - - <em class="replaceable"><code>/dev/sdc1</code></em> - "<em class="replaceable"><code>/guest_images</code></em>"
+Pool guest_images_fs defined
+</pre><div class="para">
+ The new pool and mount points are now created.
+ </div></li><li class="step"><p class="title"><strong>Verify the new pool</strong></p><div class="para">
+ List the present storage pools.
+ </div><pre class="screen">
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+<em class="replaceable"><code>guest_images_fs</code></em> inactive no
+</pre></li><li class="step"><p class="title"><strong> Create the mount point </strong></p><div class="para">
+ Use the <code class="command">virsh pool-build</code> command to create a mount point for a pre-formatted file system storage pool.
+ </div><pre class="screen">
+# virsh pool-build <em class="replaceable"><code>guest_images_fs</code></em>
+Pool guest_images_fs built
+# ls -la /<em class="replaceable"><code>guest_images</code></em>
+total 8
+drwx------. 2 root root 4096 May 31 19:38 .
+dr-xr-xr-x. 25 root root 4096 May 31 19:38 ..
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_fs inactive no
+</pre></li><li class="step"><p class="title"><strong> Start the storage pool </strong></p><div class="para">
+ Use the <code class="command">virsh pool-start</code> command to mount the file system onto the mount point and make the pool available for use.
+ </div><pre class="screen">
+# virsh pool-start <em class="replaceable"><code>guest_images_fs</code></em>
+Pool guest_images_fs started
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_fs active no
+</pre></li><li class="step"><p class="title"><strong> Turn on autostart </strong></p><div class="para">
+ By default, a storage pool is defined with <code class="command">virsh</code> is not set to automatically start each time <code class="systemitem">libvirtd</code> starts. Turn on automatic start with the <code class="command">virsh pool-autostart</code> command. The storage pool is now automatically started each time <code class="systemitem">libvirtd</code> starts.
+ </div><pre class="screen">
+# virsh pool-autostart <em class="replaceable"><code>guest_images_fs</code></em>
+Pool guest_images_fs marked as autostarted
+
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_fs active yes
+</pre></li><li class="step"><p class="title"><strong> Verify the storage pool </strong></p><div class="para">
+ Verify the storage pool was created correctly, the sizes reported are as expected, and the state is reported as <code class="command">running</code>. Verify there is a "lost+found" directory in the mount point on the file system, indicating the device is mounted.
+ </div><pre class="screen">
+# virsh pool-info <em class="replaceable"><code>guest_images_fs</code></em>
+Name: guest_images_fs
+UUID: c7466869-e82a-a66c-2187-dc9d6f0877d0
+State: running
+Persistent: yes
+Autostart: yes
+Capacity: 458.39 GB
+Allocation: 197.91 MB
+Available: 458.20 GB
+# mount | grep /guest_images
+/dev/sdc1 on /guest_images type ext4 (rw)
+# ls -la /guest_images
+total 24
+drwxr-xr-x. 3 root root 4096 May 31 19:47 .
+dr-xr-xr-x. 25 root root 4096 May 31 19:38 ..
+drwx------. 2 root root 16384 May 31 14:18 lost+found
+</pre></li></ol></div></div><div class="section" id="delete-ded-part-storage-pool-virsh"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">27.1.2.4. Deleting a storage pool using virsh</h4></div></div></div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it.
+ </div><pre class="screen"># virsh pool-destroy <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Optionally, if you want to remove the directory where the storage pool resides use the following command:
+ </div><pre class="screen"># virsh pool-delete <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Remove the storage pool's definition
+ </div><pre class="screen"># virsh pool-undefine <em class="replaceable"><code>guest_images_disk</code></em></pre></li></ol></div></div></div><div xml:lang="en-US" class="section" id="sect-Virtualization-Storage_Pools-Creating-Local_Directories" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">27.1.3. Directory-based storage pools</h3></div></div></div><div class="para">
+ This section covers storing guests in a directory on the host.
+ </div><div class="para">
+ Directory-based storage pools can be created with <code class="command">virt-manager</code> or the <code class="command">virsh</code> command line tools.
+ </div><div class="section" id="idm8401856"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm8401856">27.1.3.1. Creating a directory-based storage pool with virt-manager</h4></div></div></div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Create the local directory</strong></p><ol class="a"><li class="step"><p class="title"><strong>Optional: Create a new directory for the storage pool</strong></p><div class="para">
+ Create the directory on the host for the storage pool. This example uses a directory named <em class="replaceable"><code>/guest_images</code></em>.
+ </div><pre class="screen"># mkdir <em class="replaceable"><code>/guest_images</code></em></pre></li><li class="step"><p class="title"><strong>Set directory ownership</strong></p><div class="para">
+ Change the user and group ownership of the directory. The directory must be owned by the root user.
+ </div><pre class="screen"># chown root:root <em class="replaceable"><code>/guest_images</code></em></pre></li><li class="step"><p class="title"><strong>Set directory permissions</strong></p><div class="para">
+ Change the file permissions of the directory.
+ </div><pre class="screen"># chmod 700 <em class="replaceable"><code>/guest_images</code></em></pre></li><li class="step"><p class="title"><strong>Verify the changes</strong></p><div class="para">
+ Verify the permissions were modified. The output shows a correctly configured empty directory.
+ </div><pre class="screen"># ls -la <em class="replaceable"><code>/guest_images</code></em>
+total 8
+drwx------. 2 root root 4096 May 28 13:57 .
+dr-xr-xr-x. 26 root root 4096 May 28 13:57 ..
+</pre></li></ol></li><li class="step"><p class="title"><strong>Configure SELinux file contexts</strong></p><div class="para">
+ Configure the correct SELinux context for the new directory. Note that the name of the pool and the directory do not have to match. However, when you shutdown the guest virtual machine, libvirt has to set the context back to a default value. The context of the directory determines what this default value is. It is worth explicitly labelling the directory virt_image_t, so that when the guest virtual machine is shutdown, the images get labeled 'virt_image_t' and are thus isolated from other processes running on the host.
+ </div><pre class="screen">
+# semanage fcontext -a -t virt_image_t '/guest_images(/.*)?'
+# restorecon -R /guest_images
+</pre></li><li class="step"><p class="title"><strong>Open the storage pool settings</strong></p><ol class="a"><li class="step"><div class="para">
+ In the <code class="command">virt-manager</code> graphical interface, select the host from the main window.
+ </div><div class="para">
+ Open the <span class="guilabel"><strong>Edit</strong></span> menu and select <span class="guilabel"><strong>Connection Details</strong></span>
+ </div><div class="figure" id="conn-details-screenshot"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_select_host.png" width="444" alt="Connection details window" /></div></div><h6>Figure 27.7. Connection details window</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Click on the <span class="guilabel"><strong>Storage</strong></span> tab of the <span class="guilabel"><strong>Connection Details</strong></span> window.
+ </div><div class="figure" id="host-details-screenshot-storagepools-dir"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Storage tab" /></div></div><h6>Figure 27.8. Storage tab</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Create the new storage pool</strong></p><ol class="a"><li class="step"><p class="title"><strong>Add a new pool (part 1)</strong></p><div class="para">
+ Press the <span class="guilabel"><strong>+</strong></span> button (the add pool button). The <span class="guilabel"><strong>Add a New Storage Pool</strong></span> wizard appears.
+ </div><div class="para">
+ Choose a <span class="guibutton"><strong>Name</strong></span> for the storage pool. This example uses the name <em class="replaceable"><code>guest_images</code></em>. Change the <span class="guibutton"><strong>Type</strong></span> to <code class="command">dir: Filesystem Directory</code>.
+ </div><div class="figure" id="screenshot-pick-pool-name"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_dir_step_1_name_and_type.png" width="444" alt="Name the storage pool" /></div></div><h6>Figure 27.9. Name the storage pool</h6></div><br class="figure-break" /><div class="para">
+ Press the <span class="guibutton"><strong>Forward</strong></span> button to continue.
+ </div></li><li class="step"><p class="title"><strong>Add a new pool (part 2)</strong></p><div class="para">
+ Change the <span class="guibutton"><strong>Target Path</strong></span> field. For example, <em class="replaceable"><code>/guest_images</code></em>.
+ </div><div class="para">
+ Verify the details and press the <span class="guibutton"><strong>Finish</strong></span> button to create the storage pool.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Verify the new storage pool</strong></p><div class="para">
+ The new storage pool appears in the storage list on the left after a few seconds. Verify the size is reported as expected, <em class="replaceable"><code>36.41 GB Free</code></em> in this example. Verify the <span class="guibutton"><strong>State</strong></span> field reports the new storage pool as <em class="replaceable"><code>Active</code></em>.
+ </div><div class="para">
+ Select the storage pool. In the <span class="guibutton"><strong>Autostart</strong></span> field, confirm that the <span class="guibutton"><strong>On Boot</strong></span> checkbox is checked. This will make sure the storage pool starts whenever the <code class="systemitem">libvirtd</code> service starts.
+ </div><div class="figure" id="verify-pool-screenshot"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_dir_step_3_result.png" width="444" alt="Verify the storage pool information" /></div></div><h6>Figure 27.10. Verify the storage pool information</h6></div><br class="figure-break" /><div class="para">
+ The storage pool is now created, close the <span class="guilabel"><strong>Connection Details</strong></span> window.
+ </div></li></ol></div></div><div class="section" id="del-stor-pool-dir"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">27.1.3.2. Deleting a storage pool using virt-manager</h4></div></div></div><div class="para">
+ This procedure demonstrates how to delete a storage pool.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it. To do this, select the storage pool you want to stop and click the red X icon at the bottom of the Storage window.
+ </div><div class="figure" id="stop-icon2"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Stop Icon" /></div></div><h6>Figure 27.11. Stop Icon</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Delete the storage pool by clicking the Trash can icon. This icon is only enabled if you stop the storage pool first.
+ </div></li></ol></div></div><div class="section" id="idm22560"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm22560">27.1.3.3. Creating a directory-based storage pool with virsh</h4></div></div></div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong> Create the storage pool definition </strong></p><div class="para">
+ Use the <code class="command">virsh pool-define-as</code> command to define a new storage pool. There are two options required for creating directory-based storage pools:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <code class="command">name</code> of the storage pool.
+ </div><div class="para">
+ This example uses the name <em class="replaceable"><code>guest_images</code></em>. All further <code class="command">virsh</code> commands used in this example use this name.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="command">path</code> to a file system directory for storing guest image files. If this directory does not exist, <code class="command">virsh</code> will create it.
+ </div><div class="para">
+ This example uses the <em class="replaceable"><code>/guest_images</code></em> directory.
+ </div></li></ul></div><pre class="screen"> # virsh pool-define-as <em class="replaceable"><code>guest_images</code></em> dir - - - - "<em class="replaceable"><code>/guest_images</code></em>"
+Pool guest_images defined</pre></li><li class="step"><p class="title"><strong>Verify the storage pool is listed</strong></p><div class="para">
+ Verify the storage pool object is created correctly and the state reports it as <code class="computeroutput">inactive</code>.
+ </div><pre class="screen"># virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images inactive no</pre></li><li class="step"><p class="title"><strong> Create the local directory </strong></p><div class="para">
+ Use the <code class="command">virsh pool-build</code> command to build the directory-based storage pool for the directory <em class="replaceable"><code>guest_images</code></em> (for example), as shown:
+ </div><pre class="screen"># virsh pool-build <em class="replaceable"><code>guest_images</code></em>
+Pool guest_images built
+# ls -la /<em class="replaceable"><code>guest_images</code></em>
+total 8
+drwx------. 2 root root 4096 May 30 02:44 .
+dr-xr-xr-x. 26 root root 4096 May 30 02:44 ..
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images inactive no</pre></li><li class="step"><p class="title"><strong>Start the storage pool</strong></p><div class="para">
+ Use the virsh command <code class="command">pool-start</code> to enable a directory storage pool, thereby allowing allowing volumes of the pool to be used as guest disk images.
+ </div><pre class="screen"># virsh pool-start <em class="replaceable"><code>guest_images</code></em>
+Pool guest_images started
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images active no
+</pre></li><li class="step"><p class="title"><strong>Turn on autostart</strong></p><div class="para">
+ Turn on <em class="parameter"><code>autostart</code></em> for the storage pool. Autostart configures the <code class="systemitem">libvirtd</code> service to start the storage pool when the service starts.
+ </div><pre class="screen"># virsh pool-autostart <em class="replaceable"><code>guest_images</code></em>
+Pool guest_images marked as autostarted
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images active yes
+</pre></li><li class="step"><p class="title"><strong>Verify the storage pool configuration</strong></p><div class="para">
+ Verify the storage pool was created correctly, the size is reported correctly, and the state is reported as <code class="computeroutput">running</code>. If you want the pool to be accessible even if the guest is not running, make sure that <code class="computeroutput">Persistent</code> is reported as <code class="computeroutput">yes</code>. If you want the pool to start automatically when the service starts, make sure that <code class="computeroutput">Autostart</code> is reported as <code class="computeroutput">yes</code>.
+ </div><pre class="screen"># virsh pool-info <em class="replaceable"><code>guest_images</code></em>
+Name: guest_images
+UUID: 779081bf-7a82-107b-2874-a19a9c51d24c
+State: running
+Persistent: yes
+Autostart: yes
+Capacity: 49.22 GB
+Allocation: 12.80 GB
+Available: 36.41 GB
+
+# ls -la /guest_images
+total 8
+drwx------. 2 root root 4096 May 30 02:44 .
+dr-xr-xr-x. 26 root root 4096 May 30 02:44 ..
+#
+</pre></li></ol></div><div class="para">
+ A directory-based storage pool is now available.
+ </div></div><div class="section" id="delete-dir-storage-pool-virsh"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">27.1.3.4. Deleting a storage pool using virsh</h4></div></div></div><div class="para">
+ The following demonstrates how to delete a storage pool using virsh:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it.
+ </div><pre class="screen"># virsh pool-destroy <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Optionally, if you want to remove the directory where the storage pool resides use the following command:
+ </div><pre class="screen"># virsh pool-delete <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Remove the storage pool's definition
+ </div><pre class="screen"># virsh pool-undefine <em class="replaceable"><code>guest_images_disk</code></em></pre></li></ol></div></div></div><div xml:lang="en-US" class="section" id="sect-Virtualization-Storage_Pools-Creating-LVM" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">27.1.4. LVM-based storage pools</h3></div></div></div><div class="para">
+ This chapter covers using LVM volume groups as storage pools.
+ </div><div class="para">
+ LVM-based storage groups provide the full flexibility of LVM.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Please refer to the <em class="citetitle">Fedora Storage Administration Guide</em> for more details on LVM.
+ </div></div></div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ LVM-based storage pools require a full disk partition. If activating a new partition/device with these procedures, the partition will be formatted and all data will be erased. If using the host's existing Volume Group (VG) nothing will be erased. It is recommended to back up the storage device before commencing the following procedure.
+ </div></div></div><div class="section" id="idm4560016"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm4560016">27.1.4.1. Creating an LVM-based storage pool with virt-manager</h4></div></div></div><div class="para">
+ LVM-based storage pools can use existing LVM volume groups or create new LVM volume groups on a blank partition.
+ </div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Optional: Create new partition for LVM volumes</strong></p><div class="para">
+ These steps describe how to create a new partition and LVM volume group on a new hard disk drive.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ This procedure will remove all data from the selected storage device.
+ </div></div></div><ol class="a"><li class="step"><p class="title"><strong>Create a new partition</strong></p><div class="para">
+ Use the <code class="command">fdisk</code> command to create a new disk partition from the command line. The following example creates a new partition that uses the entire disk on the storage device <code class="computeroutput">/dev/sdb</code>.
+ </div><pre class="screen"># fdisk /dev/sdb
+Command (m for help):
+</pre><div class="para">
+ Press <em class="parameter"><code>n</code></em> for a new partition.
+ </div></li><li class="step"><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 class="step"><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 class="step"><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 class="step"><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 class="step"><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 class="step"><div class="para">
+ Choose the partition you created in the previous steps. In this example, the partition number is <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 class="step"><div class="para">
+ Enter <em class="parameter"><code>8e</code></em> for a Linux LVM partition.
+ </div><pre class="screen">Hex code (type L to list codes): <em class="parameter"><code>8e</code></em>
+</pre></li><li class="step"><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 class="step"><p class="title"><strong>Create a new LVM volume group</strong></p><div class="para">
+ Create a new LVM volume group with the <code class="command">vgcreate</code> command. This example creates a volume group named <em class="replaceable"><code>guest_images_lvm</code></em>.
+ </div><pre class="screen"># vgcreate <em class="replaceable"><code>guest_images_lvm</code></em> /dev/sdb1
+ Physical volume "/dev/vdb1" successfully created
+ Volume group "<em class="replaceable"><code>guest_images_lvm</code></em>" successfully created
+</pre></li></ol><div class="para">
+ The new LVM volume group, <em class="replaceable"><code>guest_images_lvm</code></em>, can now be used for an LVM-based storage pool.
+ </div></li><li class="step"><p class="title"><strong>Open the storage pool settings</strong></p><ol class="a"><li class="step"><div class="para">
+ In the <code class="command">virt-manager</code> graphical interface, select the host from the main window.
+ </div><div class="para">
+ Open the <span class="guilabel"><strong>Edit</strong></span> menu and select <span class="guilabel"><strong>Connection Details</strong></span>
+ </div><div class="figure" id="connection-details"><div class="figure-contents"><div class="mediaobject"><img src="images/Connection_Details.png" width="444" alt="Connection details" /></div></div><h6>Figure 27.12. Connection details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Click on the <span class="guilabel"><strong>Storage</strong></span> tab.
+ </div><div class="figure" id="lvm-storage-tab"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Storage tab" /></div></div><h6>Figure 27.13. Storage tab</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Create the new storage pool</strong></p><ol class="a"><li class="step"><p class="title"><strong>Start the Wizard</strong></p><div class="para">
+ Press the <span class="guilabel"><strong>+</strong></span> button (the add pool button). The <span class="guilabel"><strong>Add a New Storage Pool</strong></span> wizard appears.
+ </div><div class="para">
+ Choose a <span class="guibutton"><strong>Name</strong></span> for the storage pool. We use <em class="replaceable"><code>guest_images_lvm</code></em> for this example. Then change the <span class="guibutton"><strong>Type</strong></span> to <code class="command">logical: LVM Volume Group</code>, and
+ </div><div class="figure" id="lvm-add"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_lvm_step_1_name_and_type.png" width="444" alt="Add LVM storage pool" /></div></div><h6>Figure 27.14. Add LVM storage pool</h6></div><br class="figure-break" /><div class="para">
+ Press the <span class="guibutton"><strong>Forward</strong></span> button to continue.
+ </div></li><li class="step"><p class="title"><strong>Add a new pool (part 2)</strong></p><div class="para">
+ Change the <span class="guibutton"><strong>Target Path</strong></span> field. This example uses <em class="replaceable"><code>/guest_images</code></em>.
+ </div><div class="para">
+ Now fill in the <span class="guibutton"><strong>Target Path</strong></span> and <span class="guibutton"><strong>Source Path</strong></span> fields, then tick the <span class="guibutton"><strong>Build Pool</strong></span> check box.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Use the <span class="guibutton"><strong>Target Path</strong></span> field to <span class="emphasis"><em>either</em></span> select an existing LVM volume group or as the name for a new volume group. The default format is <code class="computeroutput">/dev/</code><em class="replaceable"><code>storage_pool_name</code></em>.
+ </div><div class="para">
+ This example uses a new volume group named <em class="replaceable"><code>/dev/guest_images_lvm</code></em>.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="command">Source Path</code> field is optional if an existing LVM volume group is used in the <span class="guibutton"><strong>Target Path</strong></span>.
+ </div><div class="para">
+ For new LVM volume groups, input the location of a storage device in the <code class="command">Source Path</code> field. This example uses a blank partition <em class="replaceable"><code>/dev/sdc</code></em>.
+ </div></li><li class="listitem"><div class="para">
+ The <span class="guibutton"><strong>Build Pool</strong></span> checkbox instructs <code class="command">virt-manager</code> to create a new LVM volume group. If you are using an existing volume group you should not select the <span class="guibutton"><strong>Build Pool</strong></span> checkbox.
+ </div><div class="para">
+ This example is using a blank partition to create a new volume group so the <span class="guibutton"><strong>Build Pool</strong></span> checkbox must be selected.
+ </div></li></ul></div><div class="figure" id="lvm-pool-step2"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_lvm_step_2a_paths_and_pool.png" width="444" alt="Add target and source" /></div></div><h6>Figure 27.15. Add target and source</h6></div><br class="figure-break" /><div class="para">
+ Verify the details and press the <span class="guibutton"><strong>Finish</strong></span> button format the LVM volume group and create the storage pool.
+ </div></li><li class="step"><p class="title"><strong>Confirm the device to be formatted</strong></p><div class="para">
+ A warning message appears.
+ </div><div class="figure" id="lvm-warning-message"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_lvm_step_2b_format_warning.png" alt="Warning message" /></div></div><h6>Figure 27.16. Warning message</h6></div><br class="figure-break" /><div class="para">
+ Press the <span class="guilabel"><strong>Yes</strong></span> button to proceed to erase all data on the storage device and create the storage pool.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Verify the new storage pool</strong></p><div class="para">
+ The new storage pool will appear in the list on the left after a few seconds. Verify the details are what you expect, <em class="replaceable"><code>465.76 GB Free</code></em> in our example. Also verify the <span class="guibutton"><strong>State</strong></span> field reports the new storage pool as <em class="replaceable"><code>Active</code></em>.
+ </div><div class="para">
+ It is generally a good idea to have the <span class="guibutton"><strong>Autostart</strong></span> check box enabled, to ensure the storage pool starts automatically with libvirtd.
+ </div><div class="figure" id="confirm-lvm-pool"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_storage_pools_add_lvm_step_3_result.png" width="444" alt="Confirm LVM storage pool details" /></div></div><h6>Figure 27.17. Confirm LVM storage pool details</h6></div><br class="figure-break" /><div class="para">
+ Close the Host Details dialog, as the task is now complete.
+ </div></li></ol></div></div><div class="section" id="del-stor-pool-lvm"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">27.1.4.2. Deleting a storage pool using virt-manager</h4></div></div></div><div class="para">
+ This procedure demonstrates how to delete a storage pool.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it. To do this, select the storage pool you want to stop and click the red X icon at the bottom of the Storage window.
+ </div><div class="figure" id="stop-icon3"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Stop Icon" /></div></div><h6>Figure 27.18. Stop Icon</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Delete the storage pool by clicking the Trash can icon. This icon is only enabled if you stop the storage pool first.
+ </div></li></ol></div></div><div class="section" id="idp9978784"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idp9978784">27.1.4.3. Creating an LVM-based storage pool with virsh</h4></div></div></div><div class="para">
+ This section outlines the steps required to create an LVM-based storage pool with the <code class="command">virsh</code> command. It uses the example of a pool named <span class="bold bold"><strong>guest_images_lvm</strong></span> from a single drive (<code class="filename">/dev/sdc</code>). This is only an example and your settings should be substituted as appropriate.
+ </div><div class="procedure"><h6>Procedure 27.3. Creating an LVM-based storage pool with virsh</h6><ol class="1"><li class="step"><div class="para">
+ Define the pool name <span class="bold bold"><strong>guest_images_lvm</strong></span>.
+ </div><pre class="screen"># virsh pool-define-as <em class="replaceable"><code>guest_images_lvm</code></em> logical - - <em class="replaceable"><code>/dev/sdc</code></em> <em class="replaceable"><code>libvirt_lvm</code></em> \ /dev/<em class="replaceable"><code>libvirt_lvm</code></em>
+Pool guest_images_lvm defined
+</pre></li><li class="step"><div class="para">
+ Build the pool according to the specified name.
+ </div><pre class="screen">
+# virsh pool-build <em class="replaceable"><code>guest_images_lvm</code></em>
+
+Pool guest_images_lvm built
+</pre></li><li class="step"><div class="para">
+ Initialize the new pool.
+ </div><pre class="screen">
+# virsh pool-start <em class="replaceable"><code>guest_images_lvm</code></em>
+
+Pool guest_images_lvm started
+</pre></li><li class="step"><div class="para">
+ Show the volume group information with the <code class="command">vgs</code> command.
+ </div><pre class="screen">
+# vgs
+VG #PV #LV #SN Attr VSize VFree
+libvirt_lvm 1 0 0 wz--n- 465.76g 465.76g
+</pre></li><li class="step"><div class="para">
+ Set the pool to start automatically.
+ </div><pre class="screen">
+# virsh pool-autostart <em class="replaceable"><code>guest_images_lvm</code></em>
+Pool guest_images_lvm marked as autostarted
+</pre></li><li class="step"><div class="para">
+ List the available pools with the <code class="command">virsh</code> command.
+ </div><pre class="screen">
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+guest_images_lvm active yes
+</pre></li><li class="step"><div class="para">
+ The following commands demonstrate the creation of three volumes (<span class="emphasis"><em>volume1</em></span>, <span class="emphasis"><em>volume2</em></span> and <span class="emphasis"><em>volume3</em></span>) within this pool.
+ </div><pre class="screen">
+# virsh vol-create-as <em class="replaceable"><code>guest_images_lvm</code></em> <em class="replaceable"><code>volume1</code></em> <em class="replaceable"><code>8G</code></em>
+Vol volume1 created
+
+# virsh vol-create-as <em class="replaceable"><code>guest_images_lvm</code></em> <em class="replaceable"><code>volume2</code></em> <em class="replaceable"><code>8G</code></em>
+Vol volume2 created
+
+# virsh vol-create-as <em class="replaceable"><code>guest_images_lvm</code></em> <em class="replaceable"><code>volume3</code></em> <em class="replaceable"><code>8G</code></em>
+Vol volume3 created
+</pre></li><li class="step"><div class="para">
+ List the available volumes in this pool with the <code class="command">virsh</code> command.
+ </div><pre class="screen">
+# virsh vol-list <em class="replaceable"><code>guest_images_lvm</code></em>
+Name Path
+-----------------------------------------
+volume1 /dev/libvirt_lvm/volume1
+volume2 /dev/libvirt_lvm/volume2
+volume3 /dev/libvirt_lvm/volume3
+</pre></li><li class="step"><div class="para">
+ The following two commands (<code class="command">lvscan</code> and <code class="command">lvs</code>) display further information about the newly created volumes.
+ </div><pre class="screen">
+# lvscan
+ACTIVE '/dev/libvirt_lvm/volume1' [8.00 GiB] inherit
+ACTIVE '/dev/libvirt_lvm/volume2' [8.00 GiB] inherit
+ACTIVE '/dev/libvirt_lvm/volume3' [8.00 GiB] inherit
+
+# lvs
+LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
+volume1 libvirt_lvm -wi-a- 8.00g
+volume2 libvirt_lvm -wi-a- 8.00g
+volume3 libvirt_lvm -wi-a- 8.00g
+</pre></li></ol></div></div><div class="section" id="delete-lvm-storage-pool-virsh"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">27.1.4.4. Deleting a storage pool using virsh</h4></div></div></div><div class="para">
+ The following demonstrates how to delete a storage pool using virsh:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it.
+ </div><pre class="screen"># virsh pool-destroy <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Optionally, if you want to remove the directory where the storage pool resides use the following command:
+ </div><pre class="screen"># virsh pool-delete <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Remove the storage pool's definition
+ </div><pre class="screen"># virsh pool-undefine <em class="replaceable"><code>guest_images_disk</code></em></pre></li></ol></div></div></div><div xml:lang="en-US" class="section" id="sect-Virtualization-Storage_Pools-Creating-iSCSI" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">27.1.5. iSCSI-based storage pools</h3></div></div></div><div class="para">
+ This section covers using iSCSI-based devices to store guests.
+ </div><div class="para">
+ iSCSI (Internet Small Computer System Interface) is a network protocol for sharing storage devices. iSCSI connects initiators (storage clients) to targets (storage servers) using SCSI instructions over the IP layer.
+ </div><div class="section" id="idp6987088"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idp6987088">27.1.5.1. Configuring a software iSCSI target</h4></div></div></div><div class="para">
+ The <span class="package">scsi-target-utils</span> package provides a tool for creating software-backed iSCSI targets.
+ </div><div class="procedure"><h6>Procedure 27.4. Creating an iSCSI target</h6><ol class="1"><li class="step"><p class="title"><strong>Install the required packages</strong></p><div class="para">
+ Install the <span class="package">scsi-target-utils</span> package and all dependencies
+ </div><pre class="screen"># yum install scsi-target-utils</pre></li><li class="step"><p class="title"><strong>Start the tgtd service</strong></p><div class="para">
+ The <code class="command">tgtd</code> service hosts SCSI targets and uses the iSCSI protocol to host targets. Start the <code class="command">tgtd</code> service and make the service persistent after restarting with the <code class="command">chkconfig</code> command.
+ </div><pre class="screen"># service tgtd start
+# chkconfig tgtd on</pre></li><li class="step"><p class="title"><strong>Optional: Create LVM volumes</strong></p><div class="para">
+ LVM volumes are useful for iSCSI backing images. LVM snapshots and resizing can be beneficial for guests. This example creates an LVM image named <em class="replaceable"><code>virtimage1</code></em> on a new volume group named <em class="replaceable"><code>virtstore</code></em> on a RAID5 array for hosting guests with iSCSI.
+ </div><ol class="a"><li class="step"><p class="title"><strong>Create the RAID array</strong></p><div class="para">
+ Creating software RAID5 arrays is covered by the <em class="citetitle">Fedora Deployment Guide</em>.
+ </div></li><li class="step"><p class="title"><strong>Create the LVM volume group</strong></p><div class="para">
+ Create a volume group named <em class="replaceable"><code>virtstore</code></em> with the <code class="command">vgcreate</code> command.
+ </div><pre class="screen"># vgcreate <em class="replaceable"><code>virtstore</code></em> /dev/md1</pre></li><li class="step"><p class="title"><strong>Create a LVM logical volume</strong></p><div class="para">
+ Create a logical volume group named <em class="replaceable"><code>virtimage1</code></em> on the <em class="replaceable"><code>virtstore</code></em> volume group with a size of 20GB using the <code class="command">lvcreate</code> command.
+ </div><pre class="screen"># lvcreate --size 20G -n <em class="replaceable"><code>virtimage1 virtstore</code></em></pre><div class="para">
+ The new logical volume, <em class="replaceable"><code>virtimage1</code></em>, is ready to use for iSCSI.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Optional: Create file-based images</strong></p><div class="para">
+ File-based storage is sufficient for testing but is not recommended for production environments or any significant I/O activity. This optional procedure creates a file based imaged named <em class="replaceable"><code>virtimage2.img</code></em> for an iSCSI target.
+ </div><ol class="a"><li class="step"><p class="title"><strong>Create a new directory for the image</strong></p><div class="para">
+ Create a new directory to store the image. The directory must have the correct SELinux contexts.
+ </div><pre class="screen"># mkdir -p /var/lib/tgtd/<em class="replaceable"><code>virtualization</code></em>
+</pre></li><li class="step"><p class="title"><strong>Create the image file</strong></p><div class="para">
+ Create an image named <em class="replaceable"><code>virtimage2.img</code></em> with a size of 10GB.
+ </div><pre class="screen"># dd if=/dev/zero of=/var/lib/tgtd/<em class="replaceable"><code>virtualization</code></em>/<em class="replaceable"><code>virtimage2.img</code></em> bs=1M seek=10000 count=0</pre></li><li class="step"><p class="title"><strong>Configure SELinux file contexts</strong></p><div class="para">
+ Configure the correct SELinux context for the new image and directory.
+ </div><pre class="screen"># restorecon -R /var/lib/tgtd</pre><div class="para">
+ The new file-based image, <em class="replaceable"><code>virtimage2.img</code></em>, is ready to use for iSCSI.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Create targets</strong></p><div class="para">
+ Targets can be created by adding a XML entry to the <code class="filename">/etc/tgt/targets.conf</code> file. The <code class="computeroutput">target</code> attribute requires an iSCSI Qualified Name (IQN). The IQN is in the format:
+ </div><pre class="screen">iqn.<em class="replaceable"><code>yyyy</code></em>-<em class="replaceable"><code>mm</code></em>.<em class="replaceable"><code>reversed domain name</code></em>:<em class="replaceable"><code>optional identifier text</code></em>
+</pre><div class="para">
+ Where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="replaceable"><code>yyyy</code></em>-<em class="replaceable"><code>mm</code></em> represents the year and month the device was started (for example: <em class="replaceable"><code>2010-05</code></em>);
+ </div></li><li class="listitem"><div class="para">
+ <em class="replaceable"><code>reversed domain name</code></em> is the hosts domain name in reverse (for example <em class="replaceable"><code>server1.example.com</code></em> in an IQN would be <em class="replaceable"><code>com.example.server1</code></em>); and
+ </div></li><li class="listitem"><div class="para">
+ <em class="replaceable"><code>optional identifier text</code></em> is any text string, without spaces, that assists the administrator in identifying devices or hardware.
+ </div></li></ul></div><div class="para">
+ This example creates iSCSI targets for the two types of images created in the optional steps on <em class="replaceable"><code>server1.example.com</code></em> with an optional identifier <em class="replaceable"><code>trial</code></em>. Add the following to the <code class="filename">/etc/tgt/targets.conf</code> file.
+ </div><pre class="screen">
+<target iqn.2010-05.com.example.<em class="replaceable"><code>server1</code></em>:<em class="replaceable"><code>trial</code></em>>
+ backing-store /dev/<em class="replaceable"><code>virtstore</code></em>/<em class="replaceable"><code>virtimage1</code></em> #LUN 1
+ backing-store /var/lib/tgtd/<em class="replaceable"><code>virtualization</code></em>/<em class="replaceable"><code>virtimage2.img</code></em> #LUN 2
+ write-cache off
+</target>
+</pre><div class="para">
+ Ensure that the <code class="filename">/etc/tgt/targets.conf</code> file contains the <code class="computeroutput">default-driver iscsi</code> line to set the driver type as iSCSI. The driver uses iSCSI by default.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ This example creates a globally accessible target without access control. Refer to the scsi-target-utils for information on implementing secure access.
+ </div></div></div></li><li class="step"><p class="title"><strong>Restart the tgtd service</strong></p><div class="para">
+ Restart the <code class="systemitem">tgtd</code> service to reload the configuration changes.
+ </div><pre class="screen"># service tgtd restart</pre></li><li class="step"><p class="title"><strong>iptables configuration</strong></p><div class="para">
+ Open port 3260 for iSCSI access with <code class="command">iptables</code>.
+ </div><pre class="screen"># iptables -I INPUT -p tcp -m tcp --dport 3260 -j ACCEPT
+# service iptables save
+# service iptables restart</pre></li><li class="step"><p class="title"><strong>Verify the new targets</strong></p><div class="para">
+ View the new targets to ensure the setup was successful with the <code class="command">tgt-admin --show</code> command.
+ </div><pre class="screen">
+# tgt-admin --show
+Target 1: iqn.2010-05.com.example.server1:trial
+System information:
+Driver: iscsi
+State: ready
+I_T nexus information:
+LUN information:
+LUN: 0
+ Type: controller
+ SCSI ID: IET 00010000
+ SCSI SN: beaf10
+ Size: 0 MB
+ Online: Yes
+ Removable media: No
+ Backing store type: rdwr
+ Backing store path: None
+LUN: 1
+ Type: disk
+ SCSI ID: IET 00010001
+ SCSI SN: beaf11
+ Size: 20000 MB
+ Online: Yes
+ Removable media: No
+ Backing store type: rdwr
+ Backing store path: /dev/<em class="replaceable"><code>virtstore</code></em>/<em class="replaceable"><code>virtimage1</code></em>
+LUN: 2
+ Type: disk
+ SCSI ID: IET 00010002
+ SCSI SN: beaf12
+ Size: 10000 MB
+ Online: Yes
+ Removable media: No
+ Backing store type: rdwr
+ Backing store path: /var/lib/tgtd/<em class="replaceable"><code>virtualization</code></em>/<em class="replaceable"><code>virtimage2.img</code></em>
+Account information:
+ACL information:
+ALL
+</pre><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ The ACL list is set to all. This allows all systems on the local network to access this device. It is recommended to set host access ACLs for production environments.
+ </div></div></div></li><li class="step"><p class="title"><strong>Optional: Test discovery</strong></p><div class="para">
+ Test whether the new iSCSI device is discoverable.
+ </div><pre class="screen"># iscsiadm --mode discovery --type sendtargets --portal server1.example.com
+127.0.0.1:3260,1 iqn.2010-05.com.example.server1:iscsirhel6guest</pre></li><li class="step"><p class="title"><strong>Optional: Test attaching the device</strong></p><div class="para">
+ Attach the new device (<em class="replaceable"><code>iqn.2010-05.com.example.server1:iscsirhel6guest</code></em>) to determine whether the device can be attached.
+ </div><pre class="screen"># iscsiadm -d2 -m node --login
+scsiadm: Max file limits 1024 1024
+
+Logging in to [iface: default, target: iqn.2010-05.com.example.server1:iscsirhel6guest, portal: 10.0.0.1,3260]
+Login to [iface: default, target: iqn.2010-05.com.example.server1:iscsirhel6guest, portal: 10.0.0.1,3260] successful.</pre><div class="para">
+ Detach the device.
+ </div><pre class="screen"># iscsiadm -d2 -m node --logout
+scsiadm: Max file limits 1024 1024
+
+Logging out of session [sid: 2, target: iqn.2010-05.com.example.server1:iscsirhel6guest, portal: 10.0.0.1,3260
+Logout of [sid: 2, target: iqn.2010-05.com.example.server1:iscsirhel6guest, portal: 10.0.0.1,3260] successful.</pre></li></ol></div><div class="para">
+ An iSCSI device is now ready to use for virtualization.
+ </div></div><div class="section" id="idm10885680"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm10885680">27.1.5.2. Adding an iSCSI target to virt-manager</h4></div></div></div><div class="para">
+ This procedure covers creating a storage pool with an iSCSI target in <code class="command">virt-manager</code>.
+ </div><div class="procedure"><h6>Procedure 27.5. Adding an iSCSI device to virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Open the host storage tab</strong></p><div class="para">
+ Open the <span class="guilabel"><strong>Storage</strong></span> tab in the <span class="guilabel"><strong>Host Details</strong></span> window.
+ </div><ol class="a"><li class="step"><div class="para">
+ Open <code class="command">virt-manager</code>.
+ </div></li><li class="step"><div class="para">
+ Select a host from the main <code class="command">virt-manager</code> window. Click <span class="guilabel"><strong>Edit menu</strong></span> and select <span class="guilabel"><strong>Connection Details</strong></span>.
+ </div><div class="figure" id="scsi-connection-details"><div class="figure-contents"><div class="mediaobject"><img src="images/Connection_Details.png" width="444" alt="Connection details" /></div></div><h6>Figure 27.19. Connection details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Click on the <span class="guilabel"><strong>Storage</strong></span> tab.
+ </div><div class="figure" id="scsi-storage-tab"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Storage menu" /></div></div><h6>Figure 27.20. Storage menu</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Add a new pool (part 1)</strong></p><div class="para">
+ Press the <span class="guilabel"><strong>+</strong></span> button (the add pool button). The <span class="guilabel"><strong>Add a New Storage Pool</strong></span> wizard appears.
+ </div><div class="figure" id="iscsi-storage-pool"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_add_storage_pool1.png" width="444" alt="Add an iscsi storage pool name and type" /></div></div><h6>Figure 27.21. Add an iscsi storage pool name and type</h6></div><br class="figure-break" /><div class="para">
+ Choose a name for the storage pool, change the Type to iscsi, and press <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Add a new pool (part 2)</strong></p><div class="para">
+ Enter the target path for the device, the host name of the target and the source path (the IQN). The <span class="guilabel"><strong>Format</strong></span> option is not available as formatting is handled by the guests. It is not advised to edit the <span class="guilabel"><strong>Target Path</strong></span>. The default target path value, <code class="filename">/dev/disk/by-path/</code>, adds the drive path to that directory. The target path should be the same on all hosts for migration.
+ </div><div class="para">
+ Enter the hostname or IP address of the iSCSI target. This example uses <code class="computeroutput">server1.example.com</code>.
+ </div><div class="para">
+ Enter the source path, for the iSCSI target. This example uses <code class="computeroutput">demo-target</code>.
+ </div><div class="para">
+ Check the <span class="guilabel"><strong>IQN</strong></span> checkbox to enter the IQN. This example uses <code class="computeroutput">iqn.2010-05.com.example.server1:iscsirhel6guest</code>.
+ </div><div class="figure" id="storage-pool-iscsi-add"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_add_storage_pool2.png" width="444" alt="Create an iscsi storage pool" /></div></div><h6>Figure 27.22. Create an iscsi storage pool</h6></div><br class="figure-break" /><div class="para">
+ Press <span class="guibutton"><strong>Finish</strong></span> to create the new storage pool.
+ </div></li></ol></div></div><div class="section" id="del-stor-pool-iscsi"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">27.1.5.3. Deleting a storage pool using virt-manager</h4></div></div></div><div class="para">
+ This procedure demonstrates how to delete a storage pool.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it. To do this, select the storage pool you want to stop and click the red X icon at the bottom of the Storage window.
+ </div><div class="figure" id="stop-icon4"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Stop Icon" /></div></div><h6>Figure 27.23. Stop Icon</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Delete the storage pool by clicking the Trash can icon. This icon is only enabled if you stop the storage pool first.
+ </div></li></ol></div></div><div class="section" id="idm762208"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm762208">27.1.5.4. Creating an iSCSI-based storage pool with virsh</h4></div></div></div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Use pool-define-as to define the pool from the command line</strong></p><div class="para">
+ Storage pool definitions can be created with the <code class="command">virsh</code> command line tool. Creating storage pools with <code class="command">virsh</code> is useful for systems administrators using scripts to create multiple storage pools.
+ </div><div class="para">
+ The <code class="command">virsh pool-define-as</code> command has several parameters which are accepted in the following format:
+ </div><pre class="screen">virsh pool-define-as <em class="parameter"><code>name type source-host source-path source-dev source-name</code></em> <em class="replaceable"><code>target</code></em>
+</pre><div class="para">
+ The parameters are explained as follows:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">type</span></dt><dd><div class="para">
+ defines this pool as a particular type, iscsi for example
+ </div></dd><dt class="varlistentry"><span class="term">name</span></dt><dd><div class="para">
+ must be unique and sets the name for the storage pool
+ </div></dd><dt class="varlistentry"><span class="term">source-host and source-path</span></dt><dd><div class="para">
+ the hostname and iSCSI IQN respectively
+ </div></dd><dt class="varlistentry"><span class="term">source-dev and source-name</span></dt><dd><div class="para">
+ these parameters are not required for iSCSI-based pools, use a <span class="keycap"><strong>-</strong></span> character to leave the field blank.
+ </div></dd><dt class="varlistentry"><span class="term">target</span></dt><dd><div class="para">
+ defines the location for mounting the iSCSI device on the host
+ </div></dd></dl></div><div class="para">
+ The example below creates the same iSCSI-based storage pool as the previous step.
+ </div><pre class="screen"># virsh pool-define-as --name scsirhel6guest --type iscsi \
+ --source-host server1.example.com \
+ --source-dev iqn.2010-05.com.example.server1:iscsirhel6guest
+ --target /dev/disk/by-path
+Pool iscsirhel6guest defined</pre></li><li class="step"><p class="title"><strong>Verify the storage pool is listed</strong></p><div class="para">
+ Verify the storage pool object is created correctly and the state reports as <code class="computeroutput">inactive</code>.
+ </div><pre class="screen"># virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+<em class="replaceable"><code>iscsirhel6guest</code></em> inactive no</pre></li><li class="step"><p class="title"><strong>Start the storage pool</strong></p><div class="para">
+ Use the virsh command <code class="command">pool-start</code> for this. <code class="command">pool-start</code> enables a directory storage pool, allowing it to be used for volumes and guests.
+ </div><pre class="screen"># virsh pool-start <em class="replaceable"><code>guest_images_disk</code></em>
+Pool guest_images_disk started
+# virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+<em class="replaceable"><code>iscsirhel6guest</code></em> active no
+</pre></li><li class="step"><p class="title"><strong>Turn on autostart</strong></p><div class="para">
+ Turn on <em class="parameter"><code>autostart</code></em> for the storage pool. Autostart configures the <code class="systemitem">libvirtd</code> service to start the storage pool when the service starts.
+ </div><pre class="screen"># virsh pool-autostart <em class="replaceable"><code>iscsirhel6guest</code></em>
+Pool iscsirhel6guest marked as autostarted</pre><div class="para">
+ Verify that the <em class="replaceable"><code>iscsirhel6guest</code></em> pool has autostart set:
+ </div><pre class="screen"># virsh pool-list --all
+Name State Autostart
+-----------------------------------------
+default active yes
+<em class="replaceable"><code>iscsirhel6guest</code></em> active yes
+</pre></li><li class="step"><p class="title"><strong>Verify the storage pool configuration</strong></p><div class="para">
+ Verify the storage pool was created correctly, the sizes reported correctly, and the state reports as <code class="computeroutput">running</code>.
+ </div><pre class="screen"># virsh pool-info <em class="replaceable"><code>iscsirhel6guest</code></em>
+Name: <em class="replaceable"><code>iscsirhel6guest</code></em>
+UUID: afcc5367-6770-e151-bcb3-847bc36c5e28
+State: running
+Persistent: unknown
+Autostart: yes
+Capacity: 100.31 GB
+Allocation: 0.00
+Available: 100.31 GB
+</pre></li></ol></div><div class="para">
+ An iSCSI-based storage pool is now available.
+ </div></div><div class="section" id="delete-iscsi-storage-pool-virsh"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">27.1.5.5. Deleting a storage pool using virsh</h4></div></div></div><div class="para">
+ The following demonstrates how to delete a storage pool using virsh:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it.
+ </div><pre class="screen"># virsh pool-destroy <em class="replaceable"><code>guest_images_disk</code></em></pre></li><li class="step"><div class="para">
+ Remove the storage pool's definition
+ </div><pre class="screen"># virsh pool-undefine <em class="replaceable"><code>guest_images_disk</code></em></pre></li></ol></div></div></div><div xml:lang="en-US" class="section" id="sect-Virtualization-Storage_Pools-Creating-NFS" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">27.1.6. NFS-based storage pools</h3></div></div></div><div class="para">
+ This procedure covers creating a storage pool with a NFS mount point in <code class="command">virt-manager</code>.
+ </div><div class="section" id="idm391904"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm391904">27.1.6.1. Creating a NFS-based storage pool with virt-manager</h4></div></div></div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Open the host storage tab</strong></p><div class="para">
+ Open the <span class="guilabel"><strong>Storage</strong></span> tab in the <span class="guilabel"><strong>Host Details</strong></span> window.
+ </div><ol class="a"><li class="step"><div class="para">
+ Open <code class="command">virt-manager</code>.
+ </div></li><li class="step"><div class="para">
+ Select a host from the main <code class="command">virt-manager</code> window. Click <span class="guilabel"><strong>Edit menu</strong></span> and select <span class="guilabel"><strong>Connection Details</strong></span>.
+ </div><div class="figure" id="nfs-connection-details"><div class="figure-contents"><div class="mediaobject"><img src="images/Connection_Details.png" width="444" alt="Connection details" /></div></div><h6>Figure 27.24. Connection details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Click on the Storage tab.
+ </div><div class="figure" id="nfs-storage-tab"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Storage tab" /></div></div><h6>Figure 27.25. Storage tab</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Create a new pool (part 1)</strong></p><div class="para">
+ Press the <span class="guilabel"><strong>+</strong></span> button (the add pool button). The <span class="guilabel"><strong>Add a New Storage Pool</strong></span> wizard appears.
+ </div><div class="figure" id="add-nfs-pool-1"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_add_nfs_step1.png" width="444" alt="Add an NFS name and type" /></div></div><h6>Figure 27.26. Add an NFS name and type</h6></div><br class="figure-break" /><div class="para">
+ Choose a name for the storage pool and press <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Create a new pool (part 2)</strong></p><div class="para">
+ Enter the target path for the device, the hostname and the NFS share path. Set the <span class="guilabel"><strong>Format</strong></span> option to <span class="guilabel"><strong>NFS</strong></span> or <span class="guilabel"><strong>auto</strong></span> (to detect the type). The target path must be identical on all hosts for migration.
+ </div><div class="para">
+ Enter the hostname or IP address of the NFS server. This example uses <code class="computeroutput">server1.example.com</code>.
+ </div><div class="para">
+ Enter the NFS path. This example uses <code class="computeroutput">/nfstrial</code>.
+ </div><div class="figure" id="nfs-add-pool-2"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_add_nfs_step2.png" width="444" alt="Create an NFS storage pool" /></div></div><h6>Figure 27.27. Create an NFS storage pool</h6></div><br class="figure-break" /><div class="para">
+ Press <span class="guibutton"><strong>Finish</strong></span> to create the new storage pool.
+ </div></li></ol></div></div><div class="section" id="del-stor-pool-nfs"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">27.1.6.2. Deleting a storage pool using virt-manager</h4></div></div></div><div class="para">
+ This procedure demonstrates how to delete a storage pool.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it. To do this, select the storage pool you want to stop and click the red X icon at the bottom of the Storage window.
+ </div><div class="figure" id="stop-icon5"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_host_details_storage.png" width="444" alt="Stop Icon" /></div></div><h6>Figure 27.28. Stop Icon</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Delete the storage pool by clicking the Trash can icon. This icon is only enabled if you stop the storage pool first.
+ </div></li></ol></div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Storage_Concepts-Volumes.html"><strong>Prev</strong>26.2. Volumes </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_Administration_Guide-Storage_Volumes.html"><strong>Next</strong>Chapter 28. Volumes </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Storage_Volumes.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Storage_Volumes.html
new file mode 100644
index 0000000..1826ad9
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Storage_Volumes.html
@@ -0,0 +1,39 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 28. Volumes</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt02.html" title="Part II. Administration" /><link rel="prev" href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html" title="Chapter 27. Storage pools" /><link rel="next" href="sect-Virtualization-Storage_Volumes-Cloning_volumes.html" title="28.2. Cloning volumes" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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_Administration_Guide-Storage_Pools-Storage_Pools.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Storage_Volumes-Cloning_volumes.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_Guide-Storage_Volumes" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 28. Volumes </h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Volumes.html#sect-Virtualization-Storage_Volumes-Creating_volumes">28.1. Creating volumes</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Storage_Volumes-Cloning_volumes.html">28.2. Cloning volumes</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html">28.3. Adding storage devices to guests</a></span></dt><dd><dl><dt><span
class="section"><a href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html#sect-Virtualization-Adding_storage_devices_to_guests-Adding_file_based_storage_to_a_guest">28.3.1. Adding file based storage to a guest</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html">28.3.2. Adding hard drives and other block devices to a guest</a></span></dt><dt><span class="section"><a href="sect-Managing_storage_controllers_in_a_guest.html">28.3.3. Managing storage controllers in a guest</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Virtualization-Storage_Volumes-Deleting_volumes.html">28.4. Deleting and removing volumes</a></span></dt></dl></div><div class="section" id="sect-Virtualization-Storage_Volumes-Creating_volumes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">28.1. Creating volume
s</h2></div></div></div><div class="para">
+ This section shows how to create disk volumes inside a block based storage pool. In the example below, the <code class="command">virsh vol-create-as</code> command will create a storage volume with a specific size in GB within the <em class="replaceable"><code>guest_images_disk</code></em> storage pool. As this command is repeated per volume needed, three volumes are created as shown in the example.
+ </div><pre class="screen"># virsh vol-create-as <em class="replaceable"><code>guest_images_disk</code></em> <em class="replaceable"><code>volume1</code></em> <em class="replaceable"><code>8</code></em>G
+Vol volume1 created
+
+# virsh vol-create-as <em class="replaceable"><code>guest_images_disk</code></em> <em class="replaceable"><code>volume2</code></em> <em class="replaceable"><code>8</code></em>G
+Vol volume2 created
+
+# virsh vol-create-as <em class="replaceable"><code>guest_images_disk</code></em> <em class="replaceable"><code>volume3</code></em> <em class="replaceable"><code>8</code></em>G
+Vol volume3 created
+
+# virsh vol-list <em class="replaceable"><code>guest_images_disk</code></em>
+Name Path
+-----------------------------------------
+volume1 /dev/sdb1
+volume2 /dev/sdb2
+volume3 /dev/sdb3
+
+# <code class="command">parted -s <em class="replaceable"><code>/dev/sdb</code></em> print</code>
+Model: ATA ST3500418AS (scsi)
+Disk /dev/sdb: 500GB
+Sector size (logical/physical): 512B/512B
+Partition Table: gpt
+
+Number Start End Size File system Name Flags
+2 17.4kB 8590MB 8590MB primary
+3 8590MB 17.2GB 8590MB primary
+1 21.5GB 30.1GB 8590MB primary
+
+</pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html"><strong>Prev</strong>Chapter 27. Storage pools</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-Storage_Volumes-Cloning_volumes.html"><strong>Next</strong>28.2. Cloning volumes</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Tips_and_tricks.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Tips_and_tricks.html
new file mode 100644
index 0000000..28ab807
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Tips_and_tricks.html
@@ -0,0 +1,26 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 25. Miscellaneous administration tasks</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt02.html" title="Part II. Administration" /><link rel="prev" href="ch24s02.html" title="24.2. Hugepage support" /><link rel="next" href="sect-mem-dump-off.html" title="25.2. Guest memory allocation" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="ch24s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href
="sect-mem-dump-off.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_Guide-Tips_and_tricks" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 25. Miscellaneous administration tasks</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html#sect-Virtualization-Tips_and_tricks-Automatically_starting_guests">25.1. Automatically starting guests</a></span></dt><dt><span class="section"><a href="sect-mem-dump-off.html">25.2. Guest memory allocation</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Using_qemu_img.html">25.3. Using qemu-img</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions.html">25.4. Verifying virtualization extensions</a></span></dt><dt><span class="section"><a href="ch25s05.html">25.5.
Setting KVM processor affinities</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address.html">25.6. Generating a new unique MAC address</a></span></dt><dt><span class="section"><a href="ch25s07.html">25.7. Improving guest response time</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html">25.8. Disable SMART disk monitoring for guests</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server.html">25.9. Configuring a VNC Server</a></span></dt><dt><span class="section"><a href="sect-gracefully-shut-down-guests.html">25.10. Gracefully shutting down guests</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers.html">25.11. Virtual machine timer management with libvirt</a></span></dt><dt><span class="section"><a href="sect-perf-mo
n.html">25.12. Using PMU to monitor guest performance</a></span></dt><dt><span class="section"><a href="sect-s3-s4.html">25.13. Guest virtual machine power management</a></span></dt><dt><span class="section"><a href="sect-qemu-ga.html">25.14. QEMU Guest Agent Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="sect-qemu-ga.html#sect-guest-synch">25.14.1. guest-sync</a></span></dt><dt><span class="section"><a href="subsect-guest-synch-delimited.html">25.14.2. guest-sync-delimited</a></span></dt></dl></dd><dt><span class="section"><a href="sect-limit-redirection.html">25.15. Setting a limit on device redirection</a></span></dt><dt><span class="section"><a href="sect-dynamic-vNIC.html">25.16. Dynamically changing a host or a network bridge that is attached to a virtual NIC</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" id="sect-Virtualization-Tips_and_tricks-Automatically_starting_guests"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.1. Automatically starting guests</h2></div></div></div><div class="para">
+ This section covers how to make 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="ch24s02.html"><strong>Prev</strong>24.2. Hugepage support</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-mem-dump-off.html"><strong>Next</strong>25.2. Guest memory allocation</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Troubleshooting.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Troubleshooting.html
new file mode 100644
index 0000000..9c05ecf
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Troubleshooting.html
@@ -0,0 +1,78 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix A. Troubleshooting</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt03.html" title="Part III. Appendicies" /><link rel="prev" href="pt03.html" title="Part III. Appendicies" /><link rel="next" href="apas02.html" title="A.2. kvm_stat" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="pt03.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apas02.html"><strong>Next</strong
></a></li></ul><div xml:lang="en-US" class="appendix" id="chap-Virtualization_Administration_Guide-Troubleshooting" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Troubleshooting</h1></div></div></div><div class="para">
+ This chapter covers common problems and solutions for Fedora virtualization issues.
+ </div><div class="para">
+ Read this chapter to develop an understanding of some of the common problems associated with virtualization technologies. Troubleshooting takes practice and experience which are difficult to learn from a book. It is recommended that you experiment and test virtualization on Fedora 19 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-Additional_resources.html#sect-Virtualization-Additional_resources-Online_resources">Section I.1, “Online resources”</a> for a list of Linux virtualization websites.
+ </div><div class="section" id="sect-Virtualization-Troubleshooting_-Debugging_and_troubleshooting_"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.1. Debugging and troubleshooting tools</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="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">kvm_stat</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">trace-cmd</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">vmstat</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">iostat</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">lsof</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">systemtap</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">crash</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">sysrq</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">sysrq t</code>
+ </div></li><li class="listitem"><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 class="listitem"><div class="para">
+ <code class="command">ifconfig</code>
+ </div></li><li class="listitem"><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 class="listitem"><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 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
+-----------------------------------------------------------------------------
+virtbr0 8000.feffffff yes eth0
+
+# brctl showmacs virtbr0
+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 virtbr0
+virtbr0
+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.
+ </div><div class="itemizedlist"><ul><li class="listitem"><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 class="listitem"><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 class="listitem"><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="pt03.html"><strong>Prev</strong>Part III. Appendicies</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="apas02.html"><strong>Next</strong>A.2. kvm_stat</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Virtual_Networking.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Virtual_Networking.html
new file mode 100644
index 0000000..82bd65d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Virtual_Networking.html
@@ -0,0 +1,34 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix H. Virtual Networking</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt03.html" title="Part III. Appendicies" /><link rel="prev" href="sect-libguestfs-more-docs.html" title="G.13. Where to find further documentation" /><link rel="next" href="sect-Network_Address_Translation-libvirt.html" title="H.2. Network Address Translation" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-libguestfs-more-
docs.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Network_Address_Translation-libvirt.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="appendix" id="chap-Virtualization_Administration_Guide-Virtual_Networking" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Virtual Networking</h1></div></div></div><div class="para">
+ This chapter introduces the concepts needed to create, start, stop, remove, and modify virtual networks with libvirt.
+ </div><div class="para">
+ Additional information can be found in the libvirt reference chapter
+ </div><div class="section" id="sect-virtual_network-switches-livbvirt"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">H.1. Virtual network switches</h2></div></div></div><div class="para">
+ Libvirt virtual networking uses the concept of a <span class="emphasis"><em>virtual network switch</em></span>. A virtual network switch is a software construct that operates on a host server, to which virtual machines (guests) connect. The network traffic for a guest is directed through this switch:
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-Switch_with_two_guests"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-02-switchandtwoguests.png" alt="Virtual network switch with two guests" /></div></div><h6>Figure H.1. Virtual network switch with two guests</h6></div><br class="figure-break" /><div class="para">
+ Linux host servers represent a virtual network switch as a network interface. When the libvirtd daemon (<code class="command">libvirtd</code>) is first installed and started, the default network interface representing the virtual network switch is <code class="command">virbr0</code>.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-Linux_host_with_switch"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-03-hostwithswitch.png" alt="Linux host with an interface to a virtual network switch" /></div></div><h6>Figure H.2. Linux host with an interface to a virtual network switch</h6></div><br class="figure-break" /><div class="para">
+ This <code class="command">virbr0</code> interface can be viewed with the <code class="command">ifconfig</code> and <code class="command">ip</code> commands like any other interface:
+ </div><pre class="screen">
+$ ifconfig virbr0
+ virbr0 Link encap:Ethernet HWaddr 1B:C4:94:CF:FD:17
+ inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
+ UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
+ RX packets:0 errors:0 dropped:0 overruns:0 frame:0
+ TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
+ collisions:0 txqueuelen:0
+ RX bytes:0 (0.0 b) TX bytes:3097 (3.0 KiB)
+</pre><pre class="screen">
+ $ ip addr show virbr0
+ 3: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
+ link/ether 1b:c4:94:cf:fd:17 brd ff:ff:ff:ff:ff:ff
+ inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
+</pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libguestfs-more-docs.html"><strong>Prev</strong>G.13. Where to find further 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="sect-Network_Address_Translation-libvirt.html"><strong>Next</strong>H.2. Network Address Translation</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_GuideAdvanced.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_GuideAdvanced.html
new file mode 100644
index 0000000..49dd92b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_GuideAdvanced.html
@@ -0,0 +1,18 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 24. Advanced virtualization administration</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt02.html" title="Part II. Administration" /><link rel="prev" href="chap-KSM.html" title="Chapter 23. KSM" /><link rel="next" href="ch24s02.html" title="24.2. Hugepage support" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-KSM.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch24s02.html"><stro
ng>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Administration_GuideAdvanced" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 24. Advanced virtualization administration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Administration_GuideAdvanced.html#idm804272">24.1. Control Groups (cgroups)</a></span></dt><dt><span class="section"><a href="ch24s02.html">24.2. Hugepage support</a></span></dt></dl></div><div class="para">
+ This chapter covers advanced administration tools for fine tuning and controlling guests and host system resources.
+ </div><div class="section" id="idm804272"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm804272">24.1. Control Groups (cgroups)</h2></div></div></div><div class="para">
+ Fedora 19 provides a new kernel feature: <em class="firstterm">control groups</em>, which are often referred to as <em class="firstterm">cgroups</em>. Cgroups allow you to allocate resources such as CPU time, system memory, network bandwidth, or combinations of these resources among user-defined groups of tasks (processes) running on a system. You can monitor the cgroups you configure, deny cgroups access to certain resources, and even reconfigure your cgroups dynamically on a running system.
+ </div><div class="para">
+ The cgroup functionality is fully supported by libvirt. By default, libvirt puts each guest into a separate control group for various controllers (such as memory, cpu, blkio, device).
+ </div><div class="para">
+ When a guest is started, it is already in a cgroup. The only configuration that may be required is the setting of policies on the cgroups. Refer to the <em class="citetitle">Fedora Resource Management Guide</em> for more information on cgroups.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-KSM.html"><strong>Prev</strong>Chapter 23. KSM</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="ch24s02.html"><strong>Next</strong>24.2. Hugepage support</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html
new file mode 100644
index 0000000..95443e9
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html
@@ -0,0 +1,28 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 6. Guest virtual machine installation overview</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html" title="5.2. Installing virtualization packages on an existing Fedora system" /><link rel="next" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install.html" title="6.2. Creating guests with virt-install" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 6. Guest virtual machine installation overview</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Gu
est_Installation_Guide-Guest_Installation.html#idp23296736">6.1. Guest virtual machine prerequisites and considerations</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install.html">6.2. Creating guests with virt-install</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html">6.3. Creating guests with virt-manager</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE.html">6.4. Installing guest virtual machines 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 guest virtual machines 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 in the following chapters for specific versions of Fedora and Microsoft Windows.
+ </div><div class="section" id="idp23296736"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp23296736">6.1. Guest virtual machine prerequisites and considerations</h2></div></div></div><div class="para">
+ Various factors should be considered before creating any guest virtual machines. Not only should the role of a virtual machine be considered before deployment, but regular ongoing monitoring and assessment based on variable factors (load, amount of clients) should be performed. Some factors include:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Performance</span></dt><dd><div class="para">
+ Guest virtual machines should be deployed and configured based on their intended tasks. Some guest systems (for instance, guests running a database server) may require special performance considerations. Guests may require more assigned CPUs or memory based on their role and projected system load.
+ </div></dd><dt class="varlistentry"><span class="term">Input/Output requirements and types of Input/Output</span></dt><dd><div class="para">
+ Some guest virtual machines may have a particularly high I/O requirement or may require further considerations or projections based on the type of I/O (for instance, typical disk block size access, or the amount of clients).
+ </div></dd><dt class="varlistentry"><span class="term">Storage</span></dt><dd><div class="para">
+ Some guest virtual machines may require higher priority access to storage or faster disk types, or may require exclusive access to areas of storage. The amount of storage used by guests should also be regularly monitored and taken into account when deploying and maintaining storage.
+ </div></dd><dt class="varlistentry"><span class="term">Networking and network infrastructure</span></dt><dd><div class="para">
+ Depending upon your environment, some guest virtual machines could require faster network links than other guests. Bandwidth or latency are often factors when deploying and maintaining guests, especially as requirements or load changes.
+ </div></dd><dt class="varlistentry"><span class="term">Request requirements</span></dt><dd><div class="para">
+ SCSI requests can only be issued to guest virtual machines on virtio drives if the virtio drives are backed by whole disks, and the disk device parameter is set to <code class="literal">lun</code>, as shown in the following example:
+ </div><pre class="screen"><devices>
+ <emulator>/usr/libexec/qemu-kvm</emulator>
+ <disk type='block' device='lun'></pre></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html"><strong>Prev</strong>5.2. Installing virtualization packages on an exi...</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_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install.html"><strong>Next</strong>6.2. Creating guests with virt-install</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html
new file mode 100644
index 0000000..89a94b6
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html
@@ -0,0 +1,62 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.3. Creating guests with virt-manager</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html" title="Chapter 6. Guest virtual machine installation overview" /><link rel="prev" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install.html" title="6.2. Creating guests with virt-install" /><link rel="next" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE.html" title="6.4. Installing guest virtual machines with PXE" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.3. 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 guest virtual machines.
+ </div><div class="procedure" id="proc-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_a_virtualized_guest_with_virt_manager"><h6>Procedure 6.1. Creating a guest virtual machine with <span class="application"><strong>virt-manager</strong></span></h6><ol class="1"><li class="step"><p class="title"><strong>Open virt-manager</strong></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 class="step"><p class="title"><strong>Optional: Open a remote hypervisor</strong></p><div class="para">
+ Select the hypervisor and press the <span class="guibutton"><strong>Connect</strong></span> button to connect to the remote hypervisor.
+ </div></li><li class="step"><p class="title"><strong>Create a new virtual machine</strong></p><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>Create a new virtual machine</strong></span> button (<a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html#virt-manager_main-png">Figure 6.1, “Virtual Machine Manager window”</a>) to open the <span class="guimenu"><strong>New VM</strong></span> wizard.
+ </div><div class="figure" id="virt-manager_main-png"><div class="figure-contents"><div class="mediaobject"><img src="images/rhel6_virt_manager.png" alt="Virtual Machine Manager window" /></div></div><h6>Figure 6.1. Virtual Machine Manager window</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guimenu"><strong>New VM</strong></span> wizard breaks down the virtual machine creation process into five steps:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Naming the guest virtual machine and choosing the installation type
+ </div></li><li class="listitem"><div class="para">
+ Locating and configuring the installation media
+ </div></li><li class="listitem"><div class="para">
+ Configuring memory and CPU options
+ </div></li><li class="listitem"><div class="para">
+ Configuring the virtual machine's storage
+ </div></li><li class="listitem"><div class="para">
+ Configuring networking, architecture, and other hardware settings
+ </div></li></ol></div><div class="para">
+ Ensure that <code class="command">virt-manager</code> can access the installation media (whether locally or over the network) before you continue.
+ </div></li><li class="step"><p class="title"><strong>Specify name and installation type</strong></p><div class="para">
+ The guest virtual machine creation process starts with the selection of a name and installation type. Virtual machine names can have underscores (<code class="computeroutput">_</code>), periods (<code class="computeroutput">.</code>), and hyphens (<code class="computeroutput">-</code>).
+ </div><div class="figure" id="Virtual_Machine_Name-guest-install-png"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt2-pic2.png" alt="Name virtual machine and select installation method" /></div></div><h6>Figure 6.2. Name virtual machine and select installation method</h6></div><br class="figure-break" /><div class="para">
+ Type in a virtual machine name and choose an installation type:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Local install media (ISO image or CDROM)</span></dt><dd><div class="para">
+ This method uses a CD-ROM, DVD, or image of an installation disk (for example, <code class="filename">.iso</code>).
+ </div></dd><dt class="varlistentry"><span class="term">Network Install (HTTP, FTP, or NFS)</span></dt><dd><div class="para">
+ Network installing involves the use of a mirrored Fedora installation tree to install a guest. The installation tree must be accessible through either HTTP, FTP, or NFS.
+ </div></dd><dt class="varlistentry"><span class="term">Network Boot (PXE)</span></dt><dd><div class="para">
+ This method uses a Preboot eXecution Environment (PXE) server to install the guest virtual machine. Setting up a PXE server is covered in the <em class="citetitle">Deployment Guide</em>. To install via network boot, the guest must have a routable IP address or shared network device. For information on the required networking configuration for PXE installation, refer to <a class="xref" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE.html">Section 6.4, “Installing guest virtual machines with PXE”</a>.
+ </div></dd><dt class="varlistentry"><span class="term">Import existing disk image</span></dt><dd><div class="para">
+ This method allows you to create a new guest virtual machine and import a disk image (containing a pre-installed, bootable operating system) to it.
+ </div></dd></dl></div><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Configure installation</strong></p><div class="para">
+ Next, configure the <span class="guimenuitem"><strong>OS type</strong></span> and <span class="guimenuitem"><strong>Version</strong></span> of the installation. Ensure that you select the appropriate OS type for your virtual machine. Depending on the method of installation, provide the install URL or existing storage path.
+ </div><div class="figure" id="Virtual_Machine_Name-guest-install_STEP2-local-png"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt2-pic3.png" alt="Remote installation URL" /></div></div><h6>Figure 6.3. Remote installation URL</h6></div><br class="figure-break" /><div class="figure" id="Virtual_Machine_Name-guest-install_STEP2-import-png"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt1-pic5.png" alt="Local ISO image installation" /></div></div><h6>Figure 6.4. Local ISO image installation</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Configure CPU and memory</strong></p><div class="para">
+ The next step involves configuring the number of CPUs and amount of memory to allocate to the virtual machine. The wizard shows the number of CPUs and amount of memory you can allocate; configure these settings and click <span class="guibutton"><strong>Forward</strong></span>.
+ </div><div class="figure" id="Virtual_Machine_Name-guest-install_STEP2-cpumem-png"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt1-pic6.png" alt="Configuring CPU and Memory" /></div></div><h6>Figure 6.5. Configuring CPU and Memory</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Configure storage</strong></p><div class="para">
+ Assign storage to the guest virtual machine.
+ </div><div class="figure" id="Virtual_Machine_Name-guest-install_STEP4-png"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt1-pic7.png" alt="Configuring virtual storage" /></div></div><h6>Figure 6.6. Configuring virtual storage</h6></div><br class="figure-break" /><div class="para">
+ If you chose to import an existing disk image during the first step, <code class="command">virt-manager</code> will skip this step.
+ </div><div class="para">
+ Assign sufficient space for your virtual machine and any applications it requires, then click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Final configuration</strong></p><div class="para">
+ Verify the settings of the virtual machine and click <span class="guibutton"><strong>Finish</strong></span> when you are satisfied; doing so will create the virtual machine with default networking settings, virtualization type, and architecture.
+ </div><div class="figure" id="Virtual_Machine_Name-guest-install_STEP5-finish-png"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt1-pic9-local-storage.png" alt="Verifying the configuration" /></div></div><h6>Figure 6.7. Verifying the configuration</h6></div><br class="figure-break" /><div class="para">
+ If you prefer to further configure the virtual machine's hardware first, check the <span class="guimenuitem"><strong>Customize configuration before install</strong></span> box first before clicking <span class="guibutton"><strong>Finish</strong></span>. Doing so will open another wizard that will allow you to add, remove, and configure the virtual machine's hardware settings.
+ </div><div class="para">
+ After configuring the virtual machine's hardware, click <span class="guibutton"><strong>Apply</strong></span>. <code class="command">virt-manager</code> will then create the virtual machine with your specified hardware settings.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install.html"><strong>Prev</strong>6.2. Creating guests with virt-install</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_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE.html"><strong>Next</strong>6.4. Installing guest virtual machines with PXE</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html
new file mode 100644
index 0000000..4f2c84e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html
@@ -0,0 +1,43 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 5. Installing the virtualization packages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions.html" title="4.3. Other restrictions" /><link rel="next" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html" title="5.2. Installing virtualization packages on an existing Fedora system" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 5. Installing the virtualization packages</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Insta
llation.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_with_a_new_Red_Hat_Enterprise_Linux_installation">5.1. Configuring a Virtualization Host installation</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html">5.2. Installing virtualization 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 your computer. Virtualization packages can be installed either during the host installation sequence or after host installation using the <code class="command">yum</code> command and the Fedora Project download page.
+ </div><div class="para">
+ The KVM hypervisor uses the default Fedora kernel with the <span class="package">kvm</span> kernel module.
+ </div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_with_a_new_Red_Hat_Enterprise_Linux_installation"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.1. Configuring a Virtualization Host installation</h2></div></div></div><div class="para">
+ This section covers installing virtualization tools and virtualization packages as part of a fresh Fedora installation.
+ </div><div class="procedure"><h6>Procedure 5.1. Installing the virtualization package group</h6><ol class="1"><li class="step"><p class="title"><strong>Launch the Fedora installation program</strong></p><div class="para">
+ Start an interactive Fedora installation from the Fedora Installation CD-ROM, DVD or PXE.
+ </div></li><li class="step"><p class="title"><strong>Continue installation up to package selection</strong></p><div class="para">
+ Complete the other steps up to the package selection step.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/RHELcustomize15.png" width="444" alt="The Fedora package selection screen showing options to select a different set of software from regular installation. Virtualization Host is selected in the upper menu, and Fedora is selected from the list of additional repositories. Customize now is selected at the bottom of the window, with Back and Next buttons shown at the bottom right corner of the window." /></div></div><h6>Figure 5.1. The Fedora package selection screen</h6></div><br class="figure-break" /><div class="para">
+ Select the <span class="guilabel"><strong>Virtualization Host</strong></span> server role to install a platform for guest virtual machines. Alternatively, ensure that the <span class="guilabel"><strong>Customize Now</strong></span> radio button is selected before proceeding, to specify individual packages.
+ </div></li><li class="step"><p class="title"><strong>Select the <span class="guilabel"><strong>Virtualization</strong></span> package group.</strong></p><div class="para">
+ This selects the qemu-kvm emulator, <code class="command">virt-manager</code>, <code class="command">libvirt</code> and <code class="command">virt-viewer</code> for installation.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/RHELkvmSelect.png" width="444" alt="The Fedora package selection screen with Virtualization selected in the left menu." /></div></div><h6>Figure 5.2. The Fedora package selection screen</h6></div><br class="figure-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If you wish to create virtual machines in a graphical user interface (<span class="application"><strong>virt-manager</strong></span>) later, you should also select the <code class="systemitem">General Purpose Desktop</code> package group.
+ </div></div></div></li><li class="step" id="step-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Customize_the_packages_if_required"><p class="title"><strong>Customize the packages (if required)</strong></p><div class="para">
+ Customize the <span class="guilabel"><strong>Virtualization</strong></span> group if you require other virtualization packages.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/RHELKVMpackages-2.png" width="444" alt="The Fedora package selection screen with a pop-up Packages in Virtualization window showing the packages available to be installed." /></div></div><h6>Figure 5.3. The Fedora package selection screen</h6></div><br class="figure-break" /><div class="para">
+ Click on the <span class="guilabel"><strong>Close</strong></span> button, then the <span class="guilabel"><strong>Next</strong></span> button to continue the installation.
+ </div></li></ol></div><div class="para">
+ When the installation is complete, reboot the system.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ You require a valid RHN virtualization entitlement to receive updates for the virtualization packages.
+ </div></div></div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_with_Kickstart_files"><h5 class="formalpara">Installing KVM packages with Kickstart files</h5>
+ Kickstart files allow for large, automated installations without a user manually installing each individual host system. This section describes how to create and use 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 groups:
+ </div><pre class="screen">@virtualization
+ at virtualization-client
+ at virtualization-platform
+ at virtualization-tools</pre><div class="para">
+ For more information about Kickstart files, refer to the Fedora <em class="citetitle">Installation Guide</em>, available from <a href="https://access.redhat.com/knowledge/docs/Red_Hat_Enterprise_Linux/">https://access.redhat.com/knowledge/docs/Red_Hat_Enterprise_Linux/</a>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions.html"><strong>Prev</strong>4.3. Other restrictions</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_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html"><strong>Next</strong>5.2. Installing virtualization packages on an exi...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html
new file mode 100644
index 0000000..b2b193e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html
@@ -0,0 +1,18 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 1. Introduction</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="pt01.html" title="Part I. Deployment" /><link rel="next" href="ch01s02.html" title="1.2. Virtualization Documentation Suite" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="pt01.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch01s02.html
"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 1. Introduction</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html#idp1238688">1.1. What is in this guide?</a></span></dt><dt><span class="section"><a href="ch01s02.html">1.2. Virtualization Documentation Suite</a></span></dt></dl></div><div class="section" id="idp1238688"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp1238688">1.1. What is in this guide?</h2></div></div></div><div class="para">
+ The <em class="citetitle">Virtualization Deployment and Administration Guide</em>, introduced in Fedora 19, resulted from the merger of the <em class="citetitle">Virtualization Host Installation and Guest Configuration Guide</em> and the <em class="citetitle">Virtualization Administration Guide</em>. This new guide provides complete information on both deploying a virtual setup on a Fedora virtualization host as well as how to administer and maintain the system. As such, this guide has 2 main parts:Deployment and Adminsitration. The appendix sections contain references and troubleshooting.
+ </div><div class="para">
+ The initial chapters in this guide outline the prerequisites to enable a Fedora host machine to deploy virtualization. System requirements, compatible hardware, support and product restrictions are covered in detail. The first part of this guide (Deployment) covers basic host configuration, including mandatory and optional virtualization packages, which are covered in <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html">Chapter 5, <em>Installing the virtualization packages</em></a>. Later chapters in this part include guest virtual machine installation, which is covered in detail starting from <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html">Chapter 6, <em>Guest virtual machine installation overview</em></a>, with procedures for installing fully virtualized Fedora guests and Windows para-virtualized guests using virt-manager and virsh. The part
concludes with More detailed information on networking, PCI device configuration, SR-IOV, KVM guest timing management, and troubleshooting help for libvirt and SR-IOV is included later in the guide.
+ </div><div class="para">
+ The second part of this guide (Administration) covers more advanced configuration tactics, creating various storage pools and volumes, manipulating and finetuning memory and other resources, as well as administration tasks that can be performed using virsh and virt-manager to administer both hosts and guests.
+ </div><div class="para">
+ The last part of this guide (Appendix) contains troubleshooting information with steps that should be done before getting technical support (if possible), detailed reference guides for using QEMU-KVM flags, describing the Domain XML, and a complete CLI description of the commands used in Virsh and the screens used in Virt-manager. Additional tools that may be useful are also described in this part as well.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pt01.html"><strong>Prev</strong>Part I. Deployment</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="ch01s02.html"><strong>Next</strong>1.2. Virtualization Documentation Suite</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html
new file mode 100644
index 0000000..bd7b88d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html
@@ -0,0 +1,24 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 3. KVM guest virtual machine compatibility</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_Requirements.html" title="Chapter 2. System requirements" /><link rel="next" href="ch03s02.html" title="3.2. Supported CPU Models" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-Virtual
ization_Host_Configuration_and_Guest_Installation_Guide-System_Requirements.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch03s02.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 3. KVM guest virtual machine compatibility</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html#idp986288">3.1. Fedora 6 support limits</a></span></dt><dt><span class="section"><a href="ch03s02.html">3.2. Supported CPU Models</a></span></dt><dd><dl><dt><span class="section"><a href="ch03s02.html#para-CPU_Models">3.2.1. Guest CPU models</a></span></dt></dl></dd></dl></div><div class="para">
+ To verify whether your processor supports the virtualization extensions and for information on enabling the virtualization extensions if they are disabled, refer to the <em class="citetitle">Fedora Virtualization Administration Guide</em>.
+ </div><div class="section" id="idp986288"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp986288">3.1. Fedora 6 support limits</h2></div></div></div><div class="para">
+ Fedora 19 servers have certain support limits.
+ </div><div class="para">
+ The following URLs explain the processor and memory amount limitations for Fedora 19:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ For host systems: <a href="http://www.redhat.com/resourcelibrary/articles/articles-red-hat-enterprise-linux-6-technology-capabilities-and-limits">http://www.redhat.com/resourcelibrary/articles/articles-red-hat-enterprise-linux-6-technology-capabilities-and-limits</a>
+ </div></li><li class="listitem"><div class="para">
+ For hypervisors: <a href="http://www.redhat.com/resourcelibrary/articles/virtualization-limits-rhel-hypervisors">http://www.redhat.com/resourcelibrary/articles/virtualization-limits-rhel-hypervisors</a>
+ </div></li></ul></div><div class="para">
+ The following URL is a complete reference showing supported operating systems and host and guest combinations:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.redhat.com/resourcelibrary/articles/enterprise-linux-virtualization-support">http://www.redhat.com/resourcelibrary/articles/enterprise-linux-virtualization-support</a>
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_Requirements.html"><strong>Prev</strong>Chapter 2. System requirements</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="ch03s02.html"><strong>Next</strong>3.2. Supported CPU Models</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management.html
new file mode 100644
index 0000000..d65b279
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management.html
@@ -0,0 +1,79 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 14. KVM guest timing management</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="ch13s03.html" title="13.3. Troubleshooting SR-IOV" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html" title="Chapter 15. Network booting with libvirt" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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" h
ref="ch13s03.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 14. KVM guest timing management</h2></div></div></div><div class="para">
+ Virtualization involves several intrinsic challenges for time keeping in guest virtual machines. Interrupts cannot always be delivered simultaneously and instantaneously to all guest virtual machines, because interrupts in virtual machines are not true interrupts; they are injected into the guest virtual machine by the host machine. The host may be running another guest virtual machine, or a different process, meaning that the precise timing typically required by interrupts may not always be possible.
+ </div><div class="para">
+ Guest virtual machines without accurate time keeping may experience issues with network applications and processes, as session validity, migration, and other network activities rely on timestamps to remain correct.
+ </div><div class="para">
+ KVM avoids these issues by providing guest virtual machines with a para-virtualized clock (<span class="application"><strong>kvm-clock</strong></span>). However, it is still vital to test timing before attempting activities that may be affected by time keeping inaccuracies.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Fedora 17 and newer, uses <span class="application"><strong>kvm-clock</strong></span> as their default clock source. Running without <span class="application"><strong>kvm-clock</strong></span> requires special configuration, and is not recommended.
+ </div></div></div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The Network Time Protocol (NTP) daemon should be running on the host and the guest virtual machines. 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">
+ The <code class="systemitem">ntpd</code> service will correct the effects of clock skew as long as the clock runs no more than 0.05% faster or slower than the reference time source. The <code class="systemitem">ntp</code> startup script adjusts the clock offset from the reference time by adjusting the system clock at startup time, if required.
+ </div></div></div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management-Determining_if_your_CPU_has_the_constant_Time_Stamp_Counter"><h5 class="formalpara">Constant Time Stamp Counter (TSC)</h5>
+ Modern Intel and AMD CPUs provide a constant Time Stamp Counter (TSC). The count frequency of the constant TSC does not vary when the CPU core itself changes frequency, for example, to comply with a power saving policy. A CPU with a constant TSC frequency is necessary in order to use the TSC as a clock source for KVM guests.
+ </div><div class="para">
+ 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" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management-Configuring_hosts_without_a_constant_Time_Stamp_Counter"><h5 class="formalpara">Configuring hosts without a constant Time Stamp Counter</h5>
+ Systems without a constant TSC frequency cannot use the TSC as a clock source for virtual machines, and require additional configuration. Power management features interfere with accurate time keeping and must be disabled for guest virtual machines to accurately keep time with KVM.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ These instructions are for AMD revision F CPUs only.
+ </div></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. Deep C sleep states can stop the TSC. To prevent the kernel using deep C states append <code class="command">processor.max_cstate=1</code> to the kernel boot options in the <code class="filename">grub.conf</code> file on the host:
+ </div><pre class="screen">title Fedora (2.6.32-330.x86_64)
+ root (hd0,0)
+ kernel /vmlinuz-2.6.32-330.x86_64 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" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management-Required_parameters_for_RHEL_guests"><h5 class="formalpara">Required parameters for Fedora Linux guests</h5>
+ For certain Fedroa guest virtual machines, additional kernel parameters are required. These parameters can be set by appending them to the end of the <code class="literal">/kernel</code> line in the <code class="filename">/boot/grub/grub.conf</code> file of the guest virtual machine.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The <em class="parameter"><code>lpj</code></em> parameter requires a numeric value equal to the <span class="emphasis"><em>loops per jiffy</em></span> value of the specific CPU on which the guest virtual machine runs. If you do not know this value, do not set the <em class="parameter"><code>lpj</code></em> parameter.
+ </div></div></div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ The <em class="parameter"><code>divider</code></em> kernel parameter was previously recommended for Fedora guest virtual machines that did not have high responsiveness requirements, or exist on systems with high guest density. It is no longer recommended for use with guests running Fedora versions prior to version 16.
+ </div></div></div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management-KVM_guest_timing_management-Using_the_Real_Time_Clock_with_Windows_guests"><h5 class="formalpara">Using the Real-Time Clock with Windows Server 2003 and Windows XP guests</h5>
+ Windows uses the both the Real-Time Clock (RTC) and the Time Stamp Counter (TSC). For Windows guest virtual machines the Real-Time Clock can be used instead of the TSC for all time sources which resolves guest timing issues.
+ </div><div class="para">
+ To enable the Real-Time Clock for the <code class="computeroutput">PMTIMER</code> clock source (the <code class="computeroutput">PMTIMER</code> usually uses the TSC), add the following option to the Windows boot settings. Windows boot settings are stored in the boot.ini file. Add the following option to the end of the Windows boot line in the <code class="filename">boot.ini</code> file:
+ </div><pre class="screen">/usepmtimer
+</pre><div class="para">
+ For more information on Windows boot settings and the usepmtimer 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 class="formalpara"><h5 class="formalpara" id="idm6374720">Using the Real-Time Clock with Windows Server 2008, Windows Server 2008 R2, and Windows 7 guests</h5>
+ Windows uses the both the Real-Time Clock (RTC) and the Time Stamp Counter (TSC). For Windows guest virtual machines the Real-Time Clock can be used instead of the TSC for all time sources, which resolves guest timing issues.
+ </div><div class="para">
+ The <code class="filename">boot.ini</code> file is no longer used as of Windows Server 2008 and newer. Windows Server 2008, Windows Server 2008 R2, and Windows 7 do not use the TSC as a time source if the <code class="literal">hypervisor-present</code> bit is set. The Fedora KVM hypervisor enables this CPUID bit by default, so it is no longer necessary to use the <span class="application"><strong>Boot Configuration Data Editor</strong></span> (<code class="command">bcdedit.exe</code>) to modify the Windows boot parameters.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Open the Windows guest virtual machine.
+ </div></li><li class="step"><div class="para">
+ Open the <span class="guimenuitem"><strong>Accessories</strong></span> menu of the <span class="guimenuitem"><strong>start</strong></span> menu. Right click on the <span class="application"><strong>Command Prompt</strong></span> application, select <span class="guilabel"><strong>Run as Administrator</strong></span>.
+ </div></li><li class="step"><div class="para">
+ Confirm the security exception, if prompted.
+ </div></li><li class="step"><div class="para">
+ Set the boot manager to use the platform clock. This should instruct Windows to use the PM timer for the primary clock source. The system UUID (<em class="parameter"><code>{default}</code></em> in the example below) should be changed if the system UUID is different than the default boot device.
+ </div><pre class="screen">C:\Windows\system32>bcdedit /set {default} USEPLATFORMCLOCK on
+The operation completed successfully</pre></li></ol></div><div class="para">
+ This fix should improve time keeping for Windows Server 2008 and Windows 7 guests.
+ </div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management-Steal_Time_Accounting"><h5 class="formalpara">Steal time accounting</h5>
+ Steal time is the amount of CPU time desired by a guest virtual machine that is not provided by the host. Steal time occurs when the host allocates these resources elsewhere: for example, to another guest.
+ </div><div class="para">
+ Steal time is reported in the CPU time fields in <code class="filename">/proc/stat</code> as <em class="parameter"><code>st</code></em>. It is automatically reported by utilities such as <code class="command">top</code> and <code class="command">vmstat</code>, and cannot be switched off.
+ </div><div class="para">
+ Large amounts of steal time indicate CPU contention, which can reduce guest performance. To relieve CPU contention, increase the guest's CPU priority or CPU quota, or run fewer guests on the host.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch13s03.html"><strong>Prev</strong>13.3. Troubleshooting SR-IOV</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_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html"><strong>Next</strong>Chapter 15. Network booting with libvirt</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html
new file mode 100644
index 0000000..642fb01
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html
@@ -0,0 +1,39 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 15. Network booting with libvirt</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management.html" title="Chapter 14. KVM guest timing management" /><link rel="next" href="ch15s02.html" title="15.2. Booting a guest using PXE" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch15s02.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 15. Network booting with libvirt</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html#idp27011888">15.1. Preparing the boot server</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html#idm9946464">15.1.1. Setting up a PXE boot server on a private libvirt network</a></span></dt></dl></dd><dt><span class="section"><a href="ch
15s02.html">15.2. Booting a guest using PXE</a></span></dt><dd><dl><dt><span class="section"><a href="ch15s02.html#idm3778464">15.2.1. Using bridged networking</a></span></dt><dt><span class="section"><a href="ch15s02s02.html">15.2.2. Using a private libvirt network</a></span></dt></dl></dd></dl></div><div class="para">
+ Guest virtual machines can be booted with PXE enabled. PXE allows guest virtual machines to boot and load their configuration off the network itself. This section demonstrates some basic configuration steps to configure PXE guests with libvirt.
+ </div><div class="para">
+ This section does not cover the creation of boot images or PXE servers. It is used to explain how to configure libvirt, in a private or bridged network, to boot a guest virtual machine with PXE booting enabled.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ These procedures are provided only as an example. Ensure that you have sufficient backups before proceeding.
+ </div></div></div><div class="section" id="idp27011888"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp27011888">15.1. Preparing the boot server</h2></div></div></div><div class="para">
+ To perform the steps in this chapter you will need:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ A PXE Server (DHCP and TFTP) - This can be a libvirt internal server, manually-configured dhcpd and tftpd, dnsmasq, a server configured by Cobbler, or some other server.
+ </div></li><li class="listitem"><div class="para">
+ Boot images - for example, PXELINUX configured manually or by Cobbler.
+ </div></li></ul></div><div class="section" id="idm9946464"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm9946464">15.1.1. Setting up a PXE boot server on a private libvirt network</h3></div></div></div><div class="para">
+ This example uses the <span class="emphasis"><em>default</em></span> network. Perform the following steps:
+ </div><div class="procedure"><h6>Procedure 15.1. Configuring the PXE boot server</h6><ol class="1"><li class="step"><div class="para">
+ Place the PXE boot images and configuration in <code class="filename">/var/lib/tftp</code>.
+ </div></li><li class="step"><div class="para">
+ Run the following commands:
+ </div><pre class="screen"># virsh net-destroy default
+# virsh net-edit default</pre></li><li class="step"><div class="para">
+ Edit the <code class="code"><ip></code> element in the configuration file for the <span class="emphasis"><em>default</em></span> network to include the appropriate address, network mask, DHCP address range, and boot file, where <em class="replaceable"><code>BOOT_FILENAME</code></em> represents the file name you are using to boot the guest virtual machine.
+ </div><pre class="screen"><ip address='192.168.122.1' netmask='255.255.255.0'>
+ <tftp root='/var/lib/tftp' />
+ <dhcp>
+ <range start='192.168.122.2' end='192.168.122.254' />
+ <bootp file='<em class="replaceable"><code>BOOT_FILENAME</code></em>' />
+ </dhcp>
+</ip></pre></li><li class="step"><div class="para">
+ Boot the guest using PXE (refer to <a class="xref" href="ch15s02.html#booting-guest-with-pxe">Section 15.2, “Booting a guest using PXE”</a>).
+ </div></li></ol></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management.html"><strong>Prev</strong>Chapter 14. 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="ch15s02.html"><strong>Next</strong>15.2. Booting a guest using PXE</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html
new file mode 100644
index 0000000..235e61d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html
@@ -0,0 +1,57 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 11. Network configuration</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html" title="10.6. Using KVM para-virtualized drivers for new devices" /><link rel="next" href="ch11s02.html" title="11.2. Disabling vhost-net" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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/i
mages/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch11s02.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 11. Network configuration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_address_translation_NAT_with_libvirt">11.1.
Network Address Translation (NAT) with libvirt</a></span></dt><dt><span class="section"><a href="ch11s02.html">11.2. Disabling vhost-net</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html">11.3. Bridged networking with libvirt</a></span></dt></dl></div><div class="para">
+ This chapter provides an introduction to the common networking configurations used by libvirt based guest virtual machines. For additional information, consult the libvirt network architecture documentation: <a href="http://libvirt.org/intro.html">http://libvirt.org/intro.html</a>.
+ </div><div class="para">
+ Fedora supports the following networking setups for virtualization:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ virtual networks using Network Address Translation (<em class="firstterm">NAT</em>)
+ </div></li><li class="listitem"><div class="para">
+ directly allocated physical devices using PCI device assignment
+ </div></li><li class="listitem"><div class="para">
+ directly allocated virtual functions using PCIe SR-IOV
+ </div></li><li class="listitem"><div class="para">
+ bridged networks
+ </div></li></ul></div><div class="para">
+ You must enable NAT, network bridging or directly assign a PCI device to allow external hosts access to network services on guest virtual machines.
+ </div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_address_translation_NAT_with_libvirt"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">11.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 known as virtual networks).
+ </div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_address_translation_NAT_with_libvirt-Host_configuration"><h5 class="formalpara">Host configuration</h5>
+ Every standard <code class="systemitem">libvirt</code> installation provides NAT-based connectivity to virtual machines as the 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. The new device uses NAT and IP forwarding to connect to the physical network. 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 guest virtual machines 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" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_address_translation_NAT_with_libvirt-Guest_configuration"><h5 class="formalpara">Guest virtual machine configuration</h5>
+ Once the host configuration is complete, a guest virtual machine can be connected to the virtual network based on its name. To connect a guest to the 'default' virtual network, the following could be used in the XML configuration file (such as <code class="filename">/etc/libvirtd/qemu/myguest.xml</code>) for the guest:
+ </div><pre class="screen"><interface type='network'>
+ <source network='default'/>
+</interface></pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Defining a MAC address is optional. If you do not define one, a MAC address is automatically generated and used as the MAC address of the bridge device used by the network. Manually setting the MAC address may be useful to maintain consistency or easy reference throughout your environment, or to avoid the very small chance of a conflict.
+ </div><pre class="screen"><interface type='network'>
+ <source network='default'/>
+ <mac address='00:16:3e:1a:b3:4a'/>
+</interface></pre></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html"><strong>Prev</strong>10.6. Using KVM para-virtualized drivers for new ...</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="ch11s02.html"><strong>Next</strong>11.2. Disabling vhost-net</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html
new file mode 100644
index 0000000..93f3003
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html
@@ -0,0 +1,161 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 12. PCI device configuration</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html" title="11.3. Bridged networking with libvirt" /><link rel="next" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host.html" title="12.2. Assigning a PCI device with virt-manager" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 12. PCI device configuration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html#sect-Virtualization_Host_Configuration
_and_Guest_Installation_Guide-PCI_Assignment-AI_device_to_a_host">12.1. Assigning a PCI device with virsh</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host.html">12.2. Assigning a PCI device with virt-manager</a></span></dt><dt><span class="section"><a href="ch12s03.html">12.3. PCI device assignment with virt-install</a></span></dt><dt><span class="section"><a href="ch12s04.html">12.4. Detaching an assigned PCI device</a></span></dt></dl></div><div class="para">
+ Red Hat Enterprise Linux 6 exposes three classes of device to its virtual machines:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="firstterm">Emulated devices</em> are purely virtual devices that mimic real hardware, allowing unmodified guest operating systems to work with them using their standard in-box drivers.
+ </div></li><li class="listitem"><div class="para">
+ <em class="firstterm">Virtio devices</em> are purely virtual devices designed to work optimally in a virtual machine. Virtio devices are similar to emulated devices, however, non-Linux virtual machines do not include the drivers they require by default. Virtualization management software like the Virtual Machine Manager (<span class="application"><strong>virt-manager</strong></span>) and the Red Hat Enterprise Virtualization Hypervisor install these drivers automatically for supported non-Linux guest operating systems.
+ </div></li><li class="listitem"><div class="para">
+ <em class="firstterm">Assigned devices</em> are physical devices that are exposed to the virtual machine. This method is also known as 'passthrough'. Device assignment allows virtual machines exclusive access to PCI devices for a range of tasks, and allows PCI devices to appear and behave as if they were physically attached to the guest operating system.
+ </div><div class="para">
+ Device assignment is supported on PCI Express devices, except graphics cards. Parallel PCI devices may be supported as assigned devices, but they have severe limitations due to security and system configuration conflicts.
+ </div></li></ul></div><div class="para">
+ Red Hat Enterprise Linux 6 supports 32 PCI device slots per virtual machine, and 8 PCI functions per device slot. This gives a theoretical maximum of 256 configurable PCI functions per guest.
+ </div><div class="para">
+ However, this theoretical maximum is subject to the following limitations:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Each virtual machine supports a maximum of 8 assigned device functions.
+ </div></li><li class="listitem"><div class="para">
+ 4 PCI device slots are configured with emulated devices by default. However, users can explicitly remove 2 of the emulated devices that are configured by default (the video adapter device in slot 2, and the memory balloon driver device in slot 3). This gives users a supported functional maximum of 30 PCI device slots per virtual machine.
+ </div></li></ul></div><div class="para">
+ Red Hat Enterprise Linux 6.0 and newer supports hot plugging assigned PCI devices into virtual machines. However, PCI device hot plugging operates at the slot level and therefore does not support multi-function PCI devices. Multi-function PCI devices are recommended for static device configuration only.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Red Hat Enterprise Linux 6.0 limited guest operating system driver access to a device's standard and extended configuration space. Limitations that were present in Red Hat Enterprise Linux 6.0 are significantly reduced in Red Hat Enterprise Linux 6.1, and enable a much larger set of PCI Express devices to be successfully assigned to KVM guests.
+ </div></div></div><div class="para">
+ Secure device assignment also requires interrupt remapping support. If a platform does not support interrupt remapping, device assignment will fail. To use device assignment without interrupt remapping support in a development environment, set the <em class="parameter"><code>allow_unsafe_assigned_interrupts</code></em> KVM module parameter to <code class="literal">1</code>.
+ </div><div class="para">
+ PCI device assignment is only available on hardware platforms supporting either Intel VT-d or AMD IOMMU. These Intel VT-d or AMD IOMMU specifications must be enabled in BIOS for PCI device assignment to function.
+ </div><div class="procedure" id="intel-prep"><h6>Procedure 12.1. Preparing an Intel system for PCI device assignment</h6><ol class="1"><li class="step"><p class="title"><strong>Enable the Intel VT-d specifications</strong></p><div class="para">
+ The Intel VT-d specifications provide hardware support for directly assigning a physical device to a virtual machine. These specifications are required to use PCI device assignment with Red Hat Enterprise Linux.
+ </div><div class="para">
+ The Intel VT-d specifications must be enabled in the BIOS. Some system manufacturers disable these specifications by default. The terms used to refer to these specifications can differ between manufacturers; consult your system manufacturer's documentation for the appropriate terms.
+ </div></li><li class="step"><p class="title"><strong>Activate Intel VT-d in the kernel</strong></p><div class="para">
+ Activate Intel VT-d in the kernel by adding the <em class="parameter"><code>intel_iommu=on</code></em> parameter to the kernel line in the <code class="filename">/boot/grub/grub.conf</code> file.
+ </div><div class="para">
+ The example below is a modified <code class="filename">grub.conf</code> file with Intel VT-d activated.
+ </div><pre class="screen">default=0
+timeout=5
+splashimage=(hd0,0)/grub/splash.xpm.gz
+hiddenmenu
+title Red Hat Enterprise Linux Server (2.6.32-330.x86_645)
+ root (hd0,0)
+ kernel /vmlinuz-2.6.32-330.x86_64 ro root=/dev/VolGroup00/LogVol00 rhgb quiet <span class="bold bold"><strong>intel_iommu=on</strong></span>
+ initrd /initrd-2.6.32-330.x86_64.img</pre></li><li class="step"><p class="title"><strong>Ready to use</strong></p><div class="para">
+ Reboot the system to enable the changes. Your system is now capable of PCI device assignment.
+ </div></li></ol></div><div class="procedure" id="amd-prep"><h6>Procedure 12.2. Preparing an AMD system for PCI device assignment</h6><ol class="1"><li class="step"><p class="title"><strong>Enable the AMD IOMMU specifications</strong></p><div class="para">
+ The AMD IOMMU specifications are required to use PCI device assignment in Red Hat Enterprise Linux. These specifications must be enabled in the BIOS. Some system manufacturers disable these specifications by default.
+ </div></li><li class="step"><p class="title"><strong>Enable IOMMU kernel support</strong></p><div class="para">
+ Append <em class="parameter"><code>amd_iommu=on</code></em> to the kernel command line in <code class="filename">/boot/grub/grub.conf</code> so that AMD IOMMU specifications are enabled at boot.
+ </div></li></ol></div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-AI_device_to_a_host"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">12.1. Assigning a PCI device with virsh</h2></div></div></div><div class="para">
+ These steps cover assigning a PCI device to a virtual machine on a KVM hypervisor.
+ </div><div class="para">
+ This example uses a PCIe network controller with the PCI identifier code, <code class="computeroutput">pci_0000_01_00_0</code>, and a fully virtualized guest machine named <em class="replaceable"><code>guest1-F19</code></em>.
+ </div><div class="procedure"><h6>Procedure 12.3. Assigning a PCI device to a guest virtual machine with virsh</h6><ol class="1"><li class="step"><p class="title"><strong>Identify the device</strong></p><div class="para">
+ First, identify the PCI device designated for device assignment to the virtual machine. Use the <code class="command">lspci</code> command to list the available PCI devices. You can refine the output of <code class="command">lspci</code> with <code class="command">grep</code>.
+ </div><div class="para">
+ This example uses the Ethernet controller highlighted in the following output:
+ </div><pre class="screen"># lspci | grep Ethernet
+<span class="bold bold"><strong>00:19.0 Ethernet controller: Intel Corporation 82567LM-2 Gigabit Network Connection</strong></span>
+01:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
+01:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)</pre><div class="para">
+ This Ethernet controller is shown with the short identifier <code class="literal">00:19.0</code>. We need to find out the full identifier used by <code class="command">virsh</code> in order to assign this PCI device to a virtual machine.
+ </div><div class="para">
+ To do so, combine the <code class="command">virsh nodedev-list</code> command with the <code class="command">grep</code> command to list all devices of a particular type (<code class="literal">pci</code>) that are attached to the host machine. Then look at the output for the string that maps to the short identifier of the device you wish to use.
+ </div><div class="para">
+ This example highlights the string that maps to the Ethernet controller with the short identifier <code class="literal">00:19.0</code>. Note that the <code class="literal">:</code> and <code class="literal">.</code> characters are replaced with underscores in the full identifier.
+ </div><pre class="screen"># virsh nodedev-list --cap pci
+pci_0000_00_00_0
+pci_0000_00_01_0
+pci_0000_00_03_0
+pci_0000_00_07_0
+pci_0000_00_10_0
+pci_0000_00_10_1
+pci_0000_00_14_0
+pci_0000_00_14_1
+pci_0000_00_14_2
+pci_0000_00_14_3
+pci_0000_<span class="bold bold"><strong>00_19_0</strong></span>
+pci_0000_00_1a_0
+pci_0000_00_1a_1
+pci_0000_00_1a_2
+pci_0000_00_1a_7
+pci_0000_00_1b_0
+pci_0000_00_1c_0
+pci_0000_00_1c_1
+pci_0000_00_1c_4
+pci_0000_00_1d_0
+pci_0000_00_1d_1
+pci_0000_00_1d_2
+pci_0000_00_1d_7
+pci_0000_00_1e_0
+pci_0000_00_1f_0
+pci_0000_00_1f_2
+pci_0000_00_1f_3
+pci_0000_01_00_0
+pci_0000_01_00_1
+pci_0000_02_00_0
+pci_0000_02_00_1
+pci_0000_06_00_0
+pci_0000_07_02_0
+pci_0000_07_03_0</pre><div class="para">
+ Record the PCI device number that maps to the device you want to use; this is required in other steps.
+ </div></li><li class="step"><p class="title"><strong>Review device information</strong></p><div class="para">
+ Information on the domain, bus, and function are available from output of the <code class="command">virsh nodedev-dumpxml</code> command:
+ </div><pre class="screen">virsh nodedev-dumpxml pci_0000_00_19_0
+<device>
+ <name>pci_0000_00_19_0</name>
+ <parent>computer</parent>
+ <driver>
+ <name>e1000e</name>
+ </driver>
+ <capability type='pci'>
+ <domain>0</domain>
+ <bus>0</bus>
+ <slot>25</slot>
+ <function>0</function>
+ <product id='0x1502'>82579LM Gigabit Network Connection</product>
+ <vendor id='0x8086'>Intel Corporation</vendor>
+ <capability type='virt_functions'>
+ </capability>
+ </capability>
+</device></pre></li><li class="step"><p class="title"><strong>Determine required configuration details</strong></p><div class="para">
+ Refer to the output from the <code class="command">virsh nodedev-dumpxml pci_0000_00_19_0</code> command for the values required for the configuration file.
+ </div><div class="para">
+ Optionally, convert slot and function values to hexadecimal values (from decimal) to get the PCI bus addresses. Append "0x" to the beginning of the output to tell the computer that the value is a hexadecimal number.
+ </div><div class="para">
+ The example device has the following values: bus = 0, slot = 25 and function = 0. The decimal configuration uses those three values:
+ </div><pre class="screen">bus='0'
+slot='25'
+function='0'</pre><div class="para">
+ If you want to convert to hexadecimal values, you can use the <code class="command">printf</code> utility to convert from decimal values, as shown in the following example:
+ </div><pre class="screen">$ printf %x 0
+0
+$ printf %x 25
+19
+$ printf %x 0
+0</pre><div class="para">
+ The example device would use the following hexadecimal values in the configuration file:
+ </div><pre class="screen">bus='0x0'
+slot='0x19'
+function='0x0'</pre></li><li class="step"><p class="title"><strong>Add configuration details</strong></p><div class="para">
+ Run <code class="command">virsh edit</code>, specifying the virtual machine name, and add a device entry in the <code class="computeroutput"><source></code> section to assign the PCI device to the guest virtual machine.
+ </div><pre class="screen"># virsh edit <em class="replaceable"><code>guest1-F19</code></em>
+<hostdev mode='subsystem' type='pci' managed='yes'>
+ <source>
+ <address domain='0x0' bus='0x0' slot='0x19' function='0x0'/>
+ </source>
+</hostdev></pre><div class="para">
+ Alternately, run <code class="command">virsh attach-device</code>, specifying the virtual machine name and the guest's XML file:
+ </div><pre class="screen">virsh attach-device <em class="replaceable"><code>guest1-F19</code></em> <code class="filename">file.xml</code></pre></li><li class="step"><p class="title"><strong>Allow device management</strong></p><div class="para">
+ Set an SELinux boolean to allow the management of the PCI device from the virtual machine:
+ </div><pre class="screen"># setsebool -P virt_use_sysfs 1</pre></li><li class="step"><p class="title"><strong>Start the virtual machine</strong></p><pre class="screen"># virsh start <em class="replaceable"><code>guest1-F19</code></em></pre></li></ol></div><div class="para">
+ The PCI device should now be successfully assigned to the virtual machine, and accessible to the guest operating system.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html"><strong>Prev</strong>11.3. 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_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host.html"><strong>Next</strong>12.2. Assigning a PCI device with virt-manager</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html
new file mode 100644
index 0000000..51e2721
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html
@@ -0,0 +1,76 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 10. KVM Para-virtualized Drivers</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html" title="Chapter 9. Installing a fully-virtualized Windows guest" /><link rel="next" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html" title="10.2. Installing the drivers on an installed Windows guest virtual machine" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 10. KVM Para-virtualized Drivers</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_
Guest_Installation_Guide-Para_virtualized_drivers.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers">10.1. Installing the KVM Windows para-virtualized drivers</a></span></dt><dt><span class="section"><a href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html">10.2. Installing the drivers on an installed Windows guest virtual machine</a></span></dt><dt><span class="section"><a href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html">10.3. Installing drivers during the Windows installation</a></span></dt><dt><span class="section"><a href="ch10s04.html">10.4. Using the para-virtualized drivers with Red Hat Enterprise Linux 3.9 guests</a></span></dt><dt><span class="section"><a href="form-Virtualization_Host_
Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices.html">10.5. Using KVM para-virtualized drivers for existing devices</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html">10.6. Using KVM para-virtualized drivers for new devices</a></span></dt></dl></div><div class="para">
+ Para-virtualized drivers are available for Windows guest virtual machines 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 the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Red Hat Enterprise Linux 4.8 and newer
+ </div></li><li class="listitem"><div class="para">
+ Red Hat Enterprise Linux 5.3 and newer
+ </div></li><li class="listitem"><div class="para">
+ Red Hat Enterprise Linux 6 and newer
+ </div></li><li class="listitem"><div class="para">
+ Some versions of Linux based on the 2.6.27 kernel or newer kernel versions.
+ </div></li></ul></div><div class="para">
+ Versions of Red Hat Enterprise Linux in the list above detect and install the drivers, additional installation steps are not required.
+ </div><div class="para">
+ In Red Hat Enterprise Linux 3 (3.9 and above), manual installation is required.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ PCI devices are limited by the virtualized system architecture. Refer to <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html">Chapter 12, <em>PCI device configuration</em></a> for additional limitations when using assigned devices.
+ </div></div></div><div class="para">
+ Using KVM para-virtualized drivers, the following Microsoft Windows versions are expected to run similarly to bare-metal-based systems.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Windows XP Service Pack 3 and newer (32-bit only)
+ </div></li><li class="listitem"><div class="para">
+ Windows Server 2003 (32-bit and 64-bit versions)
+ </div></li><li class="listitem"><div class="para">
+ Windows Server 2008 (32-bit and 64-bit versions)
+ </div></li><li class="listitem"><div class="para">
+ Windows Server 2008 R2 (64-bit only)
+ </div></li><li class="listitem"><div class="para">
+ Windows 7 (32-bit and 64-bit versions)
+ </div></li></ul></div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.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 a guest virtual machine using one of the following methods:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ hosting the installation files on a network accessible to the virtual machine,
+ </div></li><li class="listitem"><div class="para">
+ using a virtualized CD-ROM device of the driver installation disk .iso file, or
+ </div></li><li class="listitem"><div class="para">
+ using a virtualized floppy device to install the drivers during boot time.
+ </div></li></ul></div><div class="para">
+ This guide describes installation from the para-virtualized installer disk as a virtualized CD-ROM device.
+ </div><div class="procedure"><ol class="1"><li class="step" id="step-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Download_the_drivers"><p class="title"><strong>Download the drivers</strong></p><div class="para">
+ The <span class="package">virtio-win</span> package contains the para-virtualized block and network drivers for all supported Windows guest virtual machines.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The <span class="package">virtio-win</span> package can be found here in RHN: <a href="https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=602010">https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=602010</a>. It requires access to one of the following channels:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ RHEL Client Supplementary (v. 6)
+ </div></li><li class="listitem"><div class="para">
+ RHEL Server Supplementary (v. 6)
+ </div></li><li class="listitem"><div class="para">
+ RHEL Workstation Supplementary (v. 6)
+ </div></li></ul></div></div></div><div class="para">
+ Download and install the <span class="package">virtio-win</span> package on the host with the <code class="command">yum</code> command.
+ </div><pre class="screen"> # yum install virtio-win</pre><div class="para">
+ The list of virtio-win packages that are supported on Windows operating systems, and the current certified package version, can be found at the following URL: <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">
+ Note that the Red Hat Enterprise Virtualization Hypervisor and Red Hat Enterprise Linux are created on the same code base so the drivers for the same version (for example, Red Hat Enterprise Virtualization Hypervisor 3.0 and Red Hat Enterprise Linux 6) are supported for both environments.
+ </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 class="step" id="step-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Install_the_para_virtualized_drivers"><p class="title"><strong>Install the para-virtualized drivers</strong></p><div class="para">
+ It is recommended to install the drivers on the virtual machine 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 virtual machine, the drivers must be installed before the device is modified. If the drivers are not installed on the virtual machine and the driver is set to the virtio driver the virtual machine will not boot.
+ </div></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html"><strong>Prev</strong>Chapter 9. Installing a fully-virtualized Windows...</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="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html"><strong>Next</strong>10.2. Installing the drivers on an installed Wind...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html
new file mode 100644
index 0000000..762828d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html
@@ -0,0 +1,94 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 7. Installing a Red Hat Enterprise Linux 6 guest virtual machine on a Red Hat Enterprise Linux 6 host</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE.html" title="6.4. Installing guest virtual machines with PXE" /><link rel="next" href="ch07s02.html" title="7.2. Creating a Red Hat Enterprise Linux 6 guest with a network installation tree" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch07s02.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 7. Installing a Red Hat Enterprise Linux 6 guest virtual machine on a Red Hat Enterprise Linux 6 host</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html#idm9173792">7.1. Creating a Red Hat Enterprise Linux 6 guest with local installation media</a></span></dt><dt><span class="section"><a href="ch07s02.html">7.2. Creating a Red Hat Enterprise Linux 6
guest with a network installation tree</a></span></dt><dt><span class="section"><a href="ch07s03.html">7.3. Creating a Red Hat Enterprise Linux 6 guest with PXE</a></span></dt></dl></div><div class="para">
+ This chapter covers how to install a Red Hat Enterprise Linux 6 guest virtual machine on a Red Hat Enterprise Linux 6 host.
+ </div><div class="para">
+ These procedures assume that the KVM hypervisor and all other required packages are installed and the host is configured for virtualization.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ For more information on installing the virtualization packages, refer to <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html">Chapter 5, <em>Installing the virtualization packages</em></a>.
+ </div></div></div><div class="section" id="idm9173792"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm9173792">7.1. Creating a Red Hat Enterprise Linux 6 guest with local installation media</h2></div></div></div><div class="para">
+ This procedure covers creating a Red Hat Enterprise Linux 6 guest virtual machine with a locally stored installation DVD or DVD image. DVD images are available from <a href="http://access.redhat.com">http://access.redhat.com</a> for Red Hat Enterprise Linux 6.
+ </div><div class="procedure"><h6>Procedure 7.1. Creating a Red Hat Enterprise Linux 6 guest virtual machine with virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Optional: Preparation</strong></p><div class="para">
+ Prepare the storage environment for the virtual machine. For more information on preparing storage, refer to the <em class="citetitle">Red Hat Enterprise Linux 6 Virtualization Administration Guide</em>.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Various storage types may be used for storing guest virtual machines. However, for a virtual machine to be able to use migration features the virtual machine must be created on networked storage.
+ </div></div></div><div class="para">
+ Red Hat Enterprise Linux 6 requires at least 1GB of storage space. However, Red Hat recommends at least 5GB of storage space for a Red Hat Enterprise Linux 6 installation and for the procedures in this guide.
+ </div></li><li class="step"><p class="title"><strong>Open virt-manager and start the wizard</strong></p><div class="para">
+ Open virt-manager by executing the <code class="command">virt-manager</code> command as root or opening <span class="guilabel"><strong>Applications</strong></span> → <span class="guilabel"><strong>System Tools</strong></span> → <span class="guilabel"><strong>Virtual Machine Manager</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/1-7RHEL_local_install.png" width="444" alt="The Virtual Machine Manager window" /></div></div><h6>Figure 7.1. The Virtual Machine Manager window</h6></div><br class="figure-break" /><div class="para">
+ Click on the <span class="guibutton"><strong>Create a new virtual machine</strong></span> button to start the new virtualized guest wizard.
+ </div><div class="figure" id="gofigurego"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_newicon.png" alt="The Create a new virtual machine button" /></div></div><h6>Figure 7.2. The Create a new virtual machine button</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guilabel"><strong>New VM</strong></span> window opens.
+ </div></li><li class="step"><p class="title"><strong>Name the virtual machine</strong></p><div class="para">
+ Virtual machine names can contain letters, numbers and the following characters: '<span class="keycap"><strong>_</strong></span>', '<span class="keycap"><strong>.</strong></span>' and '<span class="keycap"><strong>-</strong></span>'. Virtual machine names must be unique for migration and cannot consist only of numbers.
+ </div><div class="para">
+ Choose the <span class="guilabel"><strong>Local install media (ISO image or CDROM)</strong></span> radio button.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/2-7RHEL_local_install.png" width="444" alt="The New VM window - Step 1" /></div></div><h6>Figure 7.3. The New VM window - Step 1</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Select the installation media</strong></p><div class="para">
+ Select the appropriate radio button for your installation media.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/3-7RHEL_local_install.png" width="444" alt="Locate your install media" /></div></div><h6>Figure 7.4. Locate your install media</h6></div><br class="figure-break" /><ul class="stepalternatives">
+ <li class="step"><div class="para">
+ If you wish to install from a CD-ROM or DVD, select the <span class="guilabel"><strong>Use CDROM or DVD</strong></span> radio button, and select the appropriate disk drive from the drop-down list of drives available.
+ </div></li>
+ <li class="step"><div class="para">
+ If you wish to install from an ISO image, select <span class="guilabel"><strong>Use ISO image</strong></span>, and then click the <span class="guibutton"><strong>Browse...</strong></span> button to open the <span class="guilabel"><strong>Locate media volume</strong></span> window.
+ </div><div class="para">
+ Select the installation image you wish to use, and click <span class="guibutton"><strong>Choose Volume</strong></span>.
+ </div><div class="para">
+ If no images are displayed in the <span class="guilabel"><strong>Locate media volume</strong></span> window, click on the <span class="guibutton"><strong>Browse Local</strong></span> button to browse the host machine for the installation image or DVD drive containing the installation disk. Select the installation image or DVD drive containing the installation disk and click <span class="guibutton"><strong>Open</strong></span>; the volume is selected for use and you are returned to the <span class="guilabel"><strong>Create a new virtual machine</strong></span> wizard.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ For ISO image files and guest storage images, the recommended location to use is <code class="filename">/var/lib/libvirt/images/</code>. Any other location may require additional configuration by SELinux. Refer to the Red Hat Enterprise Linux 6 <em class="citetitle">Virtualization Administration Guide</em> for more details on configuring SELinux.
+ </div></div></div></li>
+
+ </ul><div class="para">
+ Select the operating system type and version which match the installation media you have selected.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/5-7RHEL_local_install.png" width="444" alt="The New VM window - Step 2" /></div></div><h6>Figure 7.5. The New VM window - Step 2</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title" id="RAM-and-VCPUs"><strong>Set RAM and virtual CPUs</strong></p><div class="para">
+ Choose appropriate values for the virtual CPUs and RAM allocation. These values affect the host's and guest's performance. Memory and virtual CPUs can be overcommitted. For more information on overcommitting, refer to the <em class="citetitle">Red Hat Enterprise Linux 6 Virtualization Administration Guide</em>.
+ </div><div class="para">
+ Virtual machines require sufficient physical memory (RAM) to run efficiently and effectively. Red Hat supports a minimum of 512MB of RAM for a virtual machine. Red Hat recommends at least 1024MB of RAM for each logical core.
+ </div><div class="para">
+ Assign sufficient virtual CPUs for the virtual machine. If the virtual machine runs a multithreaded application, assign the number of virtual CPUs the guest virtual machine will require to run efficiently.
+ </div><div class="para">
+ You cannot assign more virtual CPUs than there are physical processors (or hyper-threads) available on the host system. The number of virtual CPUs available is noted in the <span class="guilabel"><strong>Up to <em class="replaceable"><code>X</code></em> available</strong></span> field.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/6-7RHEL_local_install.png" width="444" alt="The new VM window - Step 3" /></div></div><h6>Figure 7.6. The new VM window - Step 3</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Storage</strong></p><div class="para">
+ Enable and assign storage for the Red Hat Enterprise Linux 6 guest virtual machine. Assign at least 5GB for a desktop installation or at least 1GB for a minimal installation.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Live and offline migrations require virtual machines to be installed on shared network storage. For information on setting up shared storage for virtual machines, refer to the <em class="citetitle">Red Hat Enterprise Linux Virtualization Administration Guide</em>.
+ </div></div></div><ol class="a"><li class="step"><p class="title"><strong>With the default local storage</strong></p><div class="para">
+ Select the <span class="guilabel"><strong>Create a disk image on the computer's hard drive</strong></span> radio button to create a file-based image in the default storage pool, the <code class="filename">/var/lib/libvirt/images/</code> directory. Enter the size of the disk image to be created. If the <span class="guilabel"><strong>Allocate entire disk now</strong></span> check box is selected, a disk image of the size specified will be created immediately. If not, the disk image will grow as it becomes filled.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/7-7RHEL_local_install.png" width="444" alt="The New VM window - Step 4" /></div></div><h6>Figure 7.7. The New VM window - Step 4</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to create a disk image on the local hard drive. Alternatively, select <span class="guilabel"><strong>Select managed or other existing storage</strong></span>, then select <span class="guilabel"><strong>Browse</strong></span> to configure managed storage.
+ </div></li><li class="step"><p class="title"><strong>With a storage pool</strong></p><div class="para">
+ If you selected <span class="guilabel"><strong>Select managed or other existing storage</strong></span> in the previous step to use a storage pool and clicked <span class="guilabel"><strong>Browse</strong></span>, the <span class="guilabel"><strong>Locate or create storage volume</strong></span> window will appear.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/8-7RHEL_local_install.png" width="444" alt="The Locate or create storage volume window" /></div></div><h6>Figure 7.8. The Locate or create storage volume window</h6></div><br class="figure-break" /><ol class="i"><li class="step"><div class="para">
+ Select a storage pool from the <span class="guilabel"><strong>Storage Pools</strong></span> list.
+ </div></li><li class="step"><div class="para">
+ Optional: Click on the <span class="guilabel"><strong>New Volume</strong></span> button to create a new storage volume. The <span class="guilabel"><strong>Add a Storage Volume</strong></span> screen will appear. Enter the name of the new storage volume.
+ </div><div class="para">
+ Choose a format option from the <span class="guilabel"><strong>Format</strong></span> dropdown menu. Format options include raw, cow, qcow, qcow2, qed, vmdk, and vpc. Adjust other fields as desired.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/9-7RHEL_local_install.png" width="444" alt="The Add a Storage Volume window" /></div></div><h6>Figure 7.9. The Add a Storage Volume window</h6></div><br class="figure-break" /></li></ol></li></ol><div class="para">
+ Click <span class="guibutton"><strong>Finish</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Verify and finish</strong></p><div class="para">
+ Verify there were no errors made during the wizard and everything appears as expected.
+ </div><div class="para">
+ Select the <span class="guilabel"><strong>Customize configuration before install</strong></span> check box to change the guest's storage or network devices, to use the para-virtualized drivers or to add additional devices.
+ </div><div class="para">
+ Click on the <code class="systemitem">Advanced options</code> down arrow to inspect and modify advanced options. For a standard Red Hat Enterprise Linux 6 installation, none of these options require modification.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/11-7RHEL_local_install.png" width="444" alt="The New VM window - local storage" /></div></div><h6>Figure 7.10. The New VM window - local storage</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Finish</strong></span> to continue into the Red Hat Enterprise Linux installation sequence. For more information on installing Red Hat Enterprise Linux 6 refer to the Red Hat Enterprise Linux 6 <em class="citetitle">Installation Guide</em>.
+ </div></li></ol></div><div class="para">
+ A Red Hat Enterprise Linux 6 guest virtual machine is now created from an ISO installation disc image.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE.html"><strong>Prev</strong>6.4. Installing guest virtual machines 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="ch07s02.html"><strong>Next</strong>7.2. Creating a Red Hat Enterprise Linux 6 guest ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html
new file mode 100644
index 0000000..6163ffa
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html
@@ -0,0 +1,34 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 13. SR-IOV</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="ch12s04.html" title="12.4. Detaching an assigned PCI device" /><link rel="next" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html" title="13.2. Using SR-IOV" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="
ch12s04.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 13. SR-IOV</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html#idm16453008">13.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html">13.2. Using SR-IOV</a></span></dt><dt><span class="section"><a href="ch13s03.html">13.3. Troubleshooting SR-IOV</a></span></dt></dl></div><div class="section" id="idm16453008"><div class="titlepage"><div><div keep-t
ogether.within-column="always"><h2 class="title" id="idm16453008">13.1. Introduction</h2></div></div></div><div class="para">
+ Developed by the PCI-SIG (PCI Special Interest Group), the Single Root I/O Virtualization (SR-IOV) specification is a standard for a type of PCI device assignment that can share a single device to multiple virtual machines. SR-IOV improves device performance for virtual machines.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/SR-IOV_implementation_2.png" width="444" alt="How SR-IOV works" /></div></div><h6>Figure 13.1. How SR-IOV works</h6></div><br class="figure-break" /><div class="para">
+ SR-IOV enables a Single Root Function (for example, a single Ethernet port), to appear as multiple, separate, physical devices. A physical device with SR-IOV capabilities can be configured to appear in the PCI configuration space as multiple functions. Each device has its own configuration space complete with Base Address Registers (BARs).
+ </div><div class="para">
+ SR-IOV uses two PCI functions:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Physical Functions (PFs) are full PCIe devices that include the SR-IOV capabilities. Physical Functions are discovered, managed, and configured as normal PCI devices. Physical Functions configure and manage the SR-IOV functionality by assigning Virtual Functions.
+ </div></li><li class="listitem"><div class="para">
+ Virtual Functions (VFs) are simple PCIe functions that only process I/O. Each Virtual Function is derived from a Physical Function. The number of Virtual Functions a device may have is limited by the device hardware. A single Ethernet port, the Physical Device, may map to many Virtual Functions that can be shared to virtual machines.
+ </div></li></ul></div><div class="para">
+ The hypervisor can map one or more Virtual Functions to a virtual machine. The Virtual Function's configuration space is then mapped to the configuration space presented to the guest.
+ </div><div class="para">
+ Each Virtual Function can only be mapped to a single guest at a time, as Virtual Functions require real hardware resources. A virtual machine can have multiple Virtual Functions. A Virtual Function appears as a network card in the same way as a normal network card would appear to an operating system.
+ </div><div class="para">
+ The SR-IOV drivers are implemented in the kernel. The core implementation is contained in the PCI subsystem, but there must also be driver support for both the Physical Function (PF) and Virtual Function (VF) devices. An SR-IOV capable device can allocate VFs from a PF. The VFs appear as PCI devices which are backed on the physical PCI device by resources such as queues and register sets.
+ </div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-Libvirt_Strengths"><h5 class="formalpara">Advantages of SR-IOV</h5>
+ SR-IOV devices can share a single physical port with multiple virtual machines.
+ </div><div class="para">
+ Virtual Functions have near-native performance and provide better performance than para-virtualized drivers and emulated access. Virtual Functions provide data protection between virtual machines on the same physical server as the data is managed and controlled by the hardware.
+ </div><div class="para">
+ These features allow for increased virtual machine density on hosts within a data center.
+ </div><div class="para">
+ SR-IOV is better able to utilize the bandwidth of devices with multiple guests.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch12s04.html"><strong>Prev</strong>12.4. Detaching an assigned PCI device</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_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html"><strong>Next</strong>13.2. Using SR-IOV</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_Requirements.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_Requirements.html
new file mode 100644
index 0000000..48da67b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_Requirements.html
@@ -0,0 +1,62 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 2. System requirements</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="ch01s02.html" title="1.2. Virtualization Documentation Suite" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html" title="Chapter 3. KVM guest virtual machine compatibility" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="ch01s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_Requirements" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 2. System requirements</h2></div></div></div><div class="para">
+ This chapter lists system requirements for successfully running virtual machines, referred to as VMs on Fedora. Virtualization is available for Fedora on the Intel 64 and AMD64 architecture.
+ </div><div class="para">
+ The KVM hypervisor is provided with Fedora 16.
+ </div><div class="para">
+ For information on installing the virtualization packages, see <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html">Chapter 5, <em>Installing the virtualization packages</em></a>.
+ </div><div class="itemizedlist" id="item-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_requirements-Minimum_system_requirements"><h6>Minimum system requirements</h6><ul><li class="listitem"><div class="para">
+ 6 GB free disk space.
+ </div></li><li class="listitem"><div class="para">
+ 2 GB of RAM.
+ </div></li></ul></div><div class="itemizedlist" id="item-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_requirements-Recommended_system_requirements"><h6>Recommended system requirements</h6><ul><li class="listitem"><div class="para">
+ One processor core or hyper-thread for the maximum number of virtualized CPUs in a guest virtual machine and one for the host.
+ </div></li><li class="listitem"><div class="para">
+ 2 GB of RAM plus additional RAM for virtual machines.
+ </div></li><li class="listitem"><div class="para">
+ 6 GB disk space for the host, plus the required disk space for each virtual machine.
+ </div><div class="para">
+ Most guest operating systems will require at least 6GB of disk space, but the additional storage space required for each guest depends on its image format.
+ </div><div class="para">
+ For guest virtual machines using raw images, the guest's total required space <code class="literal">(total for raw format)</code> is equal to or greater than the sum of the space required by the guest's raw image files <code class="literal">(images)</code>, the 6GB space required by the host operating system <code class="literal">(host)</code>, and the swap space that guest will require <code class="literal">(swap)</code>.
+ </div><div class="equation"><h6>Equation 2.1. Calculating required space for guest virtual machines using raw images</h6><div class="equation-contents"><span class="mathphrase">total for raw format = images + host + swap</span></div></div><br class="equation-break" /><div class="para">
+ For qcow images, you must also calculate the expected maximum storage requirements of the guest <code class="literal">(total for qcow format)</code>, as qcow and qcow2 images grow as required. To allow for this expansion, first multiply the expected maximum storage requirements of the guest <code class="literal">(expected maximum guest storage)</code> by 1.01, and add to this the space required by the host <code class="literal">(host)</code>, and the necessary swap space <code class="literal">(swap)</code>.
+ </div><div class="equation"><h6>Equation 2.2. Calculating required space for guest virtual machines using qcow images</h6><div class="equation-contents"><span class="mathphrase">total for qcow format = (expected maximum guest storage * 1.01) + host + swap</span></div></div><br class="equation-break" /></li></ul></div><div class="para">
+ For more information on Guest virtual machine requirements refer to <a class="xref" href="sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM.html">Chapter 22, <em>Overcommitting with KVM</em></a>.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm4676928">Calculating swap space</h5>
+ Using swap space can provide additional memory beyond the available physical memory. 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 the physical RAM of the host.
+ </div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_requirements-KVM_requirements"><h5 class="formalpara">KVM requirements</h5>
+ The KVM hypervisor requires:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ an Intel processor with the Intel VT-x and Intel 64 extensions for x86-based systems, or
+ </div></li><li class="listitem"><div class="para">
+ an AMD processor with the AMD-V and the AMD64 extensions.
+ </div></li></ul></div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_requirements-Storage_support"><h5 class="formalpara">Storage support</h5>
+ The guest virtual machine storage methods are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ files on local storage,
+ </div></li><li class="listitem"><div class="para">
+ physical disk partitions,
+ </div></li><li class="listitem"><div class="para">
+ locally connected physical LUNs,
+ </div></li><li class="listitem"><div class="para">
+ LVM partitions,
+ </div></li><li class="listitem"><div class="para">
+ NFS shared file systems,
+ </div></li><li class="listitem"><div class="para">
+ iSCSI,
+ </div></li><li class="listitem"><div class="para">
+ GFS2 clustered file systems,
+ </div></li><li class="listitem"><div class="para">
+ Fibre Channel-based LUNs, and
+ </div></li><li class="listitem"><div class="para">
+ Fibre Channel over Ethernet (FCoE).
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch01s02.html"><strong>Prev</strong>1.2. Virtualization Documentation Suite</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_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html"><strong>Next</strong>Chapter 3. KVM guest virtual machine compatibility</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions.html
new file mode 100644
index 0000000..8e0a3b8
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions.html
@@ -0,0 +1,24 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2. Application restrictions</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html" title="Chapter 4. Virtualization restrictions" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html" title="Chapter 4. Virtualization restrictions" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions.html" title="4.3. Other restrictions" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions.html"><strong>Next</strong></a></li></ul><div class="section" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.2. Application restrictions</h2></div></div></div><div class="para">
+ There are aspects of virtualization which make it unsuitable for certain types of applications.
+ </div><div class="para">
+ Applications with high I/O throughput requirements should use the para-virtualized drivers for fully-virtualized guests. Without the para-virtualized drivers certain applications may be unpredictable under heavy I/O loads.
+ </div><div class="para">
+ The following applications should be avoided due to high I/O requirements:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>kdump</strong></span> server
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>netdump</strong></span> server
+ </div></li></ul></div><div class="para">
+ You should carefully evaluate applications and tools that heavily utilize I/O or those that require real-time performance. Consider the para-virtualized drivers or PCI device assignment for increased I/O performance. Refer to <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html">Chapter 10, <em>KVM Para-virtualized Drivers</em></a> for more information on the para-virtualized drivers for fully virtualized guests. Refer to <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html">Chapter 12, <em>PCI device configuration</em></a> for more information on PCI device assignment.
+ </div><div class="para">
+ Applications suffer a small performance loss from running in virtualized environments. The performance benefits of virtualization through consolidating to newer and faster hardware should be evaluated against the potential application performance issues associated with using virtualization.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html"><strong>Prev</strong>Chapter 4. Virtualization restrictions</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_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions.html"><strong>Next</strong>4.3. Other restrictions</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions.html
new file mode 100644
index 0000000..1219753
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.3. Other restrictions</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html" title="Chapter 4. Virtualization restrictions" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions.html" title="4.2. Application restrictions" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html" title="Chapter 5. Installing the virtualization packages" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_lef
t.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_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html"><strong>Next</strong></a></li></ul><div class="section" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.3. Other restrictions</h2></div></div></div><div class="para">
+ For the list of all other restrictions and issues affecting virtualization read the <em class="citetitle">Fedora 19 Release Notes</em>. The <em class="citetitle">Fedora 19 Release Notes</em> cover the present new features, known issues and restrictions as they are updated or discovered.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions.html"><strong>Prev</strong>4.2. Application restrictions</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_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html"><strong>Next</strong>Chapter 5. Installing the virtualization packages</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html
new file mode 100644
index 0000000..f2f0fa3
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html
@@ -0,0 +1,78 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 4. Virtualization restrictions</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="ch03s02.html" title="3.2. Supported CPU Models" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions.html" title="4.2. Application restrictions" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 a
ccesskey="p" href="ch03s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 4. Virtualization restrictions</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html#sect-chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-KVM_Restrictions">4.1. KVM restrictions</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Re
strictions.html">4.2. Application restrictions</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions.html">4.3. Other restrictions</a></span></dt></dl></div><div class="para">
+ This chapter covers additional support and product restrictions of the virtualization packages in Fedora 19.
+ </div><div class="section" id="sect-chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-KVM_Restrictions"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.1. KVM restrictions</h2></div></div></div><div class="para">
+ The following restrictions apply to the KVM hypervisor:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Maximum vCPUs per guest</span></dt><dd><div class="para">
+ Guest virtual machines support up to a maximum of 160 virtual CPUs in Fedora 19.
+ </div></dd><dt class="varlistentry"><span class="term">Constant TSC bit</span></dt><dd><div class="para">
+ Systems without a Constant Time Stamp Counter require additional configuration. Refer to <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management.html">Chapter 14, <em>KVM guest timing management</em></a> for details on determining whether you have a Constant Time Stamp Counter and configuration steps for fixing any related issues.
+ </div></dd><dt class="varlistentry"><span class="term">Memory overcommit</span></dt><dd><div class="para">
+ KVM supports memory overcommit and can store the memory of guest virtual machines in swap. A virtual machine will run slower if it is swapped frequently. Fedora Knowledgebase has an article on safely and efficiently determining the size of the swap partition, available here: <a href="https://access.redhat.com/knowledge/solutions/15244">https://access.redhat.com/knowledge/solutions/15244</a>. When KSM is used for memory overcommitting, make sure that the swap size follows the recommendations described in this article.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ When device assignment is in use, all virtual machine memory must be statically pre-allocated to enable DMA with the assigned device. Memory overcommit is therefore not supported with device assignment.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">CPU overcommit</span></dt><dd><div class="para">
+ It is not recommended to have more than 10 virtual CPUs per physical processor core. Customers are encouraged to use a capacity planning tool in order to determine the CPU overcommit ratio. Estimating an ideal ratio is difficult as it is highly dependent on each workload. For instance, a guest virtual machine may consume 100% CPU on one use case, and multiple guests may be completely idle on another.
+ </div><div class="para">
+ Fedora does not support running more vCPUs to a single guest than the amount of overall physical cores that exist on the system. While Hyperthreads can be considered as cores, their performance can also vary from one scenario to the next, and they should not be expected to perform as well as regular cores.
+ </div><div class="para">
+ Refer to the <em class="citetitle">Fedora Virtualization Administration Guide</em> for tips and recommendations on overcommitting CPUs.
+ </div></dd><dt class="varlistentry"><span class="term">Virtualized SCSI devices</span></dt><dd><div class="para">
+ SCSI emulation is not supported with KVM in Fedora.
+ </div></dd><dt class="varlistentry"><span class="term">Virtualized IDE devices</span></dt><dd><div class="para">
+ KVM is limited to a maximum of four virtualized (emulated) IDE devices per guest virtual machine.
+ </div></dd><dt class="varlistentry"><span class="term">Para-virtualized devices</span></dt><dd><div class="para">
+ Para-virtualized devices are also known as Virtio devices. They are purely virtual devices designed to work optimally in a virtual machine.
+ </div><div class="para">
+ Fedora 19 supports 32 PCI device slots per virtual machine, and 8 PCI functions per device slot. This gives a theoretical maximum of 256 PCI functions per guest when multi-function capabilities are enabled.
+ </div><div class="para">
+ However, this theoretical maximum is subject to the following limitations:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Each virtual machine supports a maximum of 8 assigned device functions.
+ </div></li><li class="listitem"><div class="para">
+ 4 PCI device slots are configured with emulated devices by default. However, users can explicitly remove 2 of the emulated devices that are configured by default (the video adapter device in slot 2, and the memory balloon driver device in slot 3). This gives users a supported functional maximum of 30 PCI device slots per virtual machine.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term">Migration restrictions</span></dt><dd><div class="para">
+ Device assignment refers to physical devices that have been exposed to a virtual machine, for the exclusive use of that virtual machine. Because device assignment uses hardware on the specific host where the virtual machine runs, migration and save/restore are not supported when device assignment is in use. If the guest operating system supports hot-plugging, assigned devices can be removed prior to the migration or save/restore operation to enable this feature.
+ </div><div class="para">
+ Live migration is only possible between hosts with the same CPU type (that is, Intel to Intel or AMD to AMD only).
+ </div><div class="para">
+ For live migration, both hosts must have the same value set for the No eXecution (NX) bit, either <code class="literal">on</code> or <code class="literal">off</code>.
+ </div><div class="para">
+ For migration to work, <code class="code">cache=none</code> must be specified for all block devices opened in write mode.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Failing to include the <code class="code">cache=none</code> option can result in disk corruption.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">Storage restrictions</span></dt><dd><div class="para">
+ There are risks associated with giving guest virtual machines write access to entire disks or block devices (such as <code class="filename">/dev/sdb</code>). If a guest virtual machine has access to an entire block device, it can share any volume label or partition table with the host machine. If bugs exist in the host system's partition recognition code, this can create a security risk. Avoid this risk by configuring the host machine to ignore devices assigned to a guest virtual machine.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Failing to adhere to storage restrictions can result in risks to security.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">SR-IOV restrictions</span></dt><dd><div class="para">
+ SR-IOV is only thoroughly tested with the following devices (other SR-IOV devices may work but have not been tested at the time of release):
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Intel® 82576NS Gigabit Ethernet Controller (<code class="command">igb</code> driver)
+ </div></li><li class="listitem"><div class="para">
+ Intel® 82576EB Gigabit Ethernet Controller (<code class="command">igb</code> driver)
+ </div></li><li class="listitem"><div class="para">
+ Intel® 82599ES 10 Gigabit Ethernet Controller (<code class="command">ixgbe</code> driver)
+ </div></li><li class="listitem"><div class="para">
+ Intel® 82599EB 10 Gigabit Ethernet Controller (<code class="command">ixgbe</code> driver)
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term">Core dumping restrictions</span></dt><dd><div class="para">
+ Because core dumping is currently implemented on top of migration, it is not supported when device assignment is in use.
+ </div></dd><dt class="varlistentry"><span class="term">PCI device assignment restrictions</span></dt><dd><div class="para">
+ PCI device assignment (attaching PCI devices to virtual machines) requires host systems to have AMD IOMMU or Intel VT-d support to enable device assignment of PCI-e devices.
+ </div><div class="para">
+ For parallel/legacy PCI, only single devices behind a PCI bridge are supported.
+ </div><div class="para">
+ Multiple PCIe endpoints connected through a non-root PCIe switch require ACS support in the PCIe bridges of the PCIe switch. To disable this restriction, edit the <code class="filename">/etc/libvirt/qemu.conf</code> file and insert the line:
+ </div><pre class="programlisting">relaxed_acs_check=1</pre><div class="para">
+ Fedora 19 has limited PCI configuration space access by guest device drivers. This limitation could cause drivers that are dependent on PCI configuration space to fail configuration.
+ </div><div class="para">
+ Fedora 17 introduced interrupt remapping as a requirement for PCI device assignment. If your platform does not provide support for interrupt remapping, circumvent the KVM check for this support with the following command as the root user at the command line prompt:
+ </div><pre class="screen"># echo 1 > /sys/module/kvm/parameters/allow_unsafe_assigned_interrupts</pre></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch03s02.html"><strong>Prev</strong>3.2. Supported CPU Models</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_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions.html"><strong>Next</strong>4.2. Application restrictions</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-sVirt.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-sVirt.html
new file mode 100644
index 0000000..9f2ea88
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-sVirt.html
@@ -0,0 +1,24 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 19. sVirt</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt02.html" title="Part II. Administration" /><link rel="prev" href="ch18s04.html" title="18.4. Virtualization firewall information" /><link rel="next" href="ch19s02.html" title="19.2. sVirt labeling" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="ch18s04.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href
="ch19s02.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="chap-sVirt" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 19. sVirt</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-sVirt.html#idp5009424">19.1. Security and Virtualization</a></span></dt><dt><span class="section"><a href="ch19s02.html">19.2. sVirt labeling</a></span></dt></dl></div><div class="para">
+ sVirt is a technology included in Fedora that integrates SELinux and virtualization. sVirt applies Mandatory Access Control (MAC) to improve security when using virtualized guests. The main reasons for integrating these technologies are to improve security and harden the system against bugs in the hypervisor that might be used as an attack vector aimed toward the host or to another virtualized guest.
+ </div><div class="para">
+ This chapter describes how sVirt integrates with virtualization technologies in Fedora.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm3206288">Non-virtualized environments</h5>
+ In a non-virtualized environment, hosts are separated from each other physically and each host has a self-contained environment, consisting of services such as a web server, or a DNS server. These services communicate directly to their own user space, host kernel and physical host, offering their services directly to the network. The following image represents a non-virtualized environment:
+ </div><div class="mediaobject"><img src="./images/before_virtualization.png" /></div><div class="formalpara"><h5 class="formalpara" id="idm6553872">Virtualized environments</h5>
+ In a virtualized environment, several operating systems can run on a single host kernel and physical host. The following image represents a virtualized environment:
+ </div><div class="mediaobject"><img src="./images/after_virtualization.png" /></div><div class="section" id="idp5009424"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp5009424">19.1. Security and Virtualization</h2></div></div></div><div class="para">
+ When services are not virtualized, machines are physically separated. Any exploit is usually contained to the affected machine, with the obvious exception of network attacks. When services are grouped together in a virtualized environment, extra vulnerabilities emerge in the system. If there is a security flaw in the hypervisor that can be exploited by a guest instance, this guest may be able to not only attack the host, but also other guests running on that host. These attacks can extend beyond the guest instance and could expose other guests to attack.
+ </div><div class="para">
+ sVirt is an effort to isolate guests and limit their ability to launch further attacks if exploited. This is demonstrated in the following image, where an attack can not break out of the virtualized guest and extend to another guest instance:
+ </div><div class="mediaobject"><img src="./images/selinux_uuid_block.png" /></div><div class="para">
+ SELinux introduces a pluggable security framework for virtualized instances in its implementation of Mandatory Access Control (MAC). The sVirt framework allows guests and their resources to be uniquely labeled. Once labeled, rules can be applied which can reject access between different guests.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch18s04.html"><strong>Prev</strong>18.4. Virtualization firewall information</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="ch19s02.html"><strong>Next</strong>19.2. sVirt labeling</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html
new file mode 100644
index 0000000..faab31d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html
@@ -0,0 +1,123 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.4. Creating a virtual machine XML dump (configuration file)</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="prev" href="sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor.html" title="E.3. Connecting to the hypervisor" /><link rel="next" href="apes05.html" title="E.5. Suspending, resuming, saving and restoring a guest" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="Doc
umentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apes05.html"><strong>Next</strong></a></li></ul><div class="section" id="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">E.4. Creating a virtual machine XML dump (configuration file)</h2></div></div></div><div class="para">
+ Output a guest's XML configuration file with <code class="command">virsh</code>:
+ </div><pre class="screen"># virsh dumpxml <em class="parameter"><code>{guest-id, guestname or 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>:
+ </div><pre class="screen"># virsh dumpxml <em class="replaceable"><code>GuestID</code></em> > <em class="replaceable"><code>guest.xml</code></em></pre><div class="para">
+ This file <code class="filename">guest.xml</code> can recreate the guest (refer to <a class="xref" href="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html#form-Virtualization-Managing_guests_with_virsh-Editing_a_guests_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.
+ </div><div class="para">
+ An example of <code class="command">virsh dumpxml</code> output:
+ </div><pre class="screen"># virsh dumpxml guest1-rhel6-64
+<domain type='kvm'>
+ <name>guest1-rhel6-64</name>
+ <uuid>b8d7388a-bbf2-db3a-e962-b97ca6e514bd</uuid>
+ <memory>2097152</memory>
+ <currentMemory>2097152</currentMemory>
+ <vcpu>2</vcpu>
+ <os>
+ <type arch='x86_64' machine='rhel6.2.0'>hvm</type>
+ <boot dev='hd'/>
+ </os>
+ <features>
+ <acpi/>
+ <apic/>
+ <pae/>
+ </features>
+ <clock offset='utc'/>
+ <on_poweroff>destroy</on_poweroff>
+ <on_reboot>restart</on_reboot>
+ <on_crash>restart</on_crash>
+ <devices>
+ <emulator>/usr/libexec/qemu-kvm</emulator>
+ <disk type='file' device='disk'>
+ <driver name='qemu' type='raw' cache='none' io='threads'/>
+ <source file='/home/guest-images/guest1-rhel6-64.img'/>
+ <target dev='vda' bus='virtio'/>
+ <shareable/<
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
+ </disk>
+ <interface type='bridge'>
+ <mac address='52:54:00:b9:35:a9'/>
+ <source bridge='br0'/>
+ <model type='virtio'/>
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
+ </interface>
+ <serial type='pty'>
+ <target port='0'/>
+ </serial>
+ <console type='pty'>
+ <target type='serial' port='0'/>
+ </console>
+ <input type='tablet' bus='usb'/>
+ <input type='mouse' bus='ps2'/>
+ <graphics type='vnc' port='-1' autoport='yes'/>
+ <sound model='ich6'>
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
+ </sound>
+ <video>
+ <model type='cirrus' vram='9216' heads='1'/>
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
+ </video>
+ <memballoon model='virtio'>
+ <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
+ </memballoon>
+ </devices>
+</domain>
+
+
+</pre><div class="para">
+ Note that the <shareable/> flag is set. This indicates the device is expected to be shared between domains (assuming the hypervisor and OS support this), which means that caching should be deactivated for that device.
+ </div><div class="formalpara" id="form-Virtualization-Managing_guests_with_virsh-Creating_a_guest_from_a_configuration_file"><h5 class="formalpara">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="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html">Section E.4, “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" id="form-Virtualization-Managing_guests_with_virsh-Editing_a_guests_configuration_file"><h5 class="formalpara">Editing a guest's configuration file</h5>
+ Instead of using the <code class="command">dumpxml</code> option (refer to <a class="xref" href="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html">Section E.4, “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="section" id="sect-multifunction-pci-install"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.4.1. Adding multifunction PCI devices to KVM guests</h3></div></div></div><div class="para">
+ This section will demonstrate how to add multi-function PCI devices to KVM guests.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Run the <code class="command">virsh edit <em class="replaceable"><code>[guestname]</code></em></code> command to edit the XML configuration file for the guest.
+ </div></li><li class="step"><div class="para">
+ In the address type tag, add a <code class="command">multifunction='on'</code> entry for <code class="command">function='0x0'</code>.
+ </div><div class="para">
+ This enables the guest to use the multifunction PCI devices.
+ </div><pre class="screen">
+<disk type='file' device='disk'>
+<driver name='qemu' type='raw' cache='none'/>
+<source file='/var/lib/libvirt/images/rhel62-1.img'/>
+<target dev='vda' bus='virtio'/>
+<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0' multifunction='on'/
+</disk>
+</pre><div class="para">
+ For a PCI device with two functions, amend the XML configuration file to include a second device with the same slot number as the first device and a different function number, such as <code class="command">function='0x1'</code>.
+ </div><div class="para">
+ For Example:
+ </div><pre class="screen">
+<disk type='file' device='disk'>
+<driver name='qemu' type='raw' cache='none'/>
+<source file='/var/lib/libvirt/images/rhel62-1.img'/>
+<target dev='vda' bus='virtio'/>
+<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0' multifunction='on'/>
+</disk>
+<disk type='file' device='disk'>
+<driver name='qemu' type='raw' cache='none'/>
+<source file='/var/lib/libvirt/images/rhel62-2.img'/>
+<target dev='vdb' bus='virtio'/>
+<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x1'/>
+</disk>
+</pre></li><li class="step"><div class="para">
+ <code class="command">lspci</code> output from the KVM guest shows:
+ </div><pre class="screen">
+$ lspci
+
+00:05.0 SCSI storage controller: Fedora, Inc Virtio block device
+00:05.1 SCSI storage controller: Fedora, Inc Virtio block device
+</pre></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor.html"><strong>Prev</strong>E.3. Connecting to the 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="apes05.html"><strong>Next</strong>E.5. Suspending, resuming, saving and restoring a...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html
new file mode 100644
index 0000000..5f6656e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html
@@ -0,0 +1,84 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.3. Installing drivers during the Windows installation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html" title="Chapter 10. KVM Para-virtualized Drivers" /><link rel="prev" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html" title="10.2. Installing the drivers on an installed Windows guest virtual machine" /><link rel="next" href="ch10s04.html" title="10.4. Using the para-virtualized drivers with Red Hat Enterprise Linux 3.9 guests" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch10s04.html"><strong>Next</strong></a></li></ul><div class="section" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.3. Installing drivers during the Windows installation</h2></div></div></div><div class="para">
+ This procedure covers installing the para-virtualized drivers during a Windows installation.
+ </div><div class="para">
+ This method allows a Windows guest virtual machine to use the para-virtualized (<code class="command">virtio</code>) drivers for the default storage device.
+ </div><div class="procedure"><h6>Procedure 10.3. Installing para-virtualized drivers during the Windows installation</h6><ol class="1"><li class="step"><div class="para">
+ Install the virtio-win package:
+ </div><pre class="screen"># yum install virtio-win</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The <span class="package">virtio-win</span> package can be found here in RHN: <a href="https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=602010">https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=602010</a>. It requires access to one of the following channels:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ RHEL Client Supplementary (v. 6)
+ </div></li><li class="listitem"><div class="para">
+ RHEL Server Supplementary (v. 6)
+ </div></li><li class="listitem"><div class="para">
+ RHEL Workstation Supplementary (v. 6)
+ </div></li></ul></div></div></div></li><li class="step"><p class="title"><strong>Creating the guest virtual machine</strong></p><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Create the virtual machine, as normal, without starting the virtual machine. Follow one of the procedures below.
+ </div></div></div><div class="para">
+ Select <span class="emphasis"><em>one</em></span> of the following guest-creation methods, and follow the instructions.
+ </div><ol class="a"><li class="step"><p class="title"><strong>Creating the guest virtual machine with virsh</strong></p><div class="para">
+ This method attaches the para-virtualized driver floppy disk to a Windows guest <span class="emphasis"><em>before</em></span> the installation.
+ </div><div class="para">
+ If the virtual machine is created from an XML definition file with <code class="command">virsh</code>, use the <code class="command">virsh define</code> command not the <code class="command">virsh create</code> command.
+ </div><ol class="i"><li class="step"><div class="para">
+ Create, but do not start, the virtual machine. Refer to the <em class="citetitle">Red Hat Enterprise Linux Virtualization Administration Guide</em> for details on creating virtual machines with the <code class="command">virsh</code> command.
+ </div></li><li class="step"><div class="para">
+ Add the driver disk as a virtualized floppy disk with the <code class="command">virsh</code> command. This example can be copied and used if there are no other virtualized floppy devices attached to the guest virtual machine. Note that <em class="replaceable"><code>vm_name</code></em> should be replaced with the name of the virtual machine.
+ </div><pre class="screen"># virsh attach-disk <em class="replaceable"><code>vm_name</code></em> /usr/share/virtio-win/virtio-win.vfd fda --type floppy</pre><div class="para">
+ You can now continue with <a class="xref" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html#aftercreation">Step 3</a>.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Creating the guest virtual machine with virt-manager and changing the disk type</strong></p><ol class="i"><li class="step"><div class="para">
+ At the final step of the virt-manager guest creation wizard, check the <span class="guilabel"><strong>Customize configuration before install</strong></span> checkbox.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-0-click-configure-before-install.png" alt="Step 5 of 5 of creating a new virtual machine with virt-manager, with a checkbox selected under Storage to customize configuration before install." /></div></div><h6>Figure 10.17. The virt-manager guest creation wizard</h6></div><br class="figure-break" /><div class="para">
+ Click on the <span class="guibutton"><strong>Finish</strong></span> button to continue.
+ </div></li><li class="step"><p class="title"><strong>Open the Add Hardware wizard</strong></p><div class="para">
+ Click the <span class="guilabel"><strong>Add Hardware</strong></span> button in the bottom left of the new panel.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-1-click-add-hardware.png" alt="The Add Hardware button." /></div></div><h6>Figure 10.18. The Add Hardware button</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Select storage device</strong></p><div class="para">
+ <span class="guilabel"><strong>Storage</strong></span> is the default selection in the <span class="guilabel"><strong>Hardware type</strong></span> list.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-2z-select-storage.png" width="444" alt="The Add new virtual hardware wizard with Storage selected in the Hardware type field." /></div></div><h6>Figure 10.19. The Add new virtual hardware wizard</h6></div><br class="figure-break" /><div class="para">
+ Ensure the <span class="guilabel"><strong>Select managed or other existing storage</strong></span> radio button is selected. Click <span class="guibutton"><strong>Browse...</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-2a-select-existing-storage.png" alt="The Add new virtual hardware wizard with Storage selected in the Hardware type field, and the Select managed or other existing storage radio button selected." /></div></div><h6>Figure 10.20. Select managed or existing storage</h6></div><br class="figure-break" /><div class="para">
+ In the new window that opens, click <span class="guilabel"><strong>Browse Local</strong></span>. Navigate to <code class="filename">/usr/share/virtio-win/virtio-win.vfd</code>, and click <span class="guibutton"><strong>Select</strong></span> to confirm.
+ </div><div class="para">
+ Change <span class="guilabel"><strong>Device type</strong></span> to <span class="guilabel"><strong>Floppy disk</strong></span>, and click <span class="guibutton"><strong>Finish</strong></span> to continue.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-select-device-type-floppy.png" alt="The Device type field, set to Floppy Disk." /></div></div><h6>Figure 10.21. Change the Device type</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Confirm settings</strong></p><div class="para">
+ Review the device settings.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-confirm-floppy-settings.png" width="444" alt="The virtual machine hardware information window with the target device (Floppy 1) selected." /></div></div><h6>Figure 10.22. The virtual machine hardware information window</h6></div><br class="figure-break" /><div class="para">
+ You have now created a removable device accessible by your virtual machine.
+ </div></li><li class="step"><p class="title"><strong>Change the hard disk type</strong></p><div class="para">
+ To change the hard disk type from <em class="replaceable"><code>IDE Disk</code></em> to <em class="replaceable"><code>Virtio Disk</code></em>, we must first remove the existing hard disk, Disk 1. Select the disk and click on the <span class="guibutton"><strong>Remove</strong></span> button.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-remove-disk1.png" width="444" alt="The virtual machine hardware information window with virtual disk Disk 1 selected, with the Remove button available at the bottom right corner of the window." /></div></div><h6>Figure 10.23. The virtual machine hardware information window</h6></div><br class="figure-break" /><div class="para">
+ Add a new virtual storage device by clicking <span class="guilabel"><strong>Add Hardware</strong></span>. Then, change the <span class="guilabel"><strong>Device type</strong></span> from <em class="replaceable"><code>IDE disk</code></em> to <em class="replaceable"><code>Virtio Disk</code></em>. Click <span class="guibutton"><strong>Finish</strong></span> to confirm the operation.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-device-type-virtio-finish.png" width="444" alt="The virtual machine hardware information window with the Floppy 1 target device selected, and the Add Hardware on the left bottom corner of the window." /></div></div><h6>Figure 10.24. The virtual machine hardware information window</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Ensure settings are correct</strong></p><div class="para">
+ Review the settings for <em class="replaceable"><code>VirtIO Disk 1</code></em>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-review-virtio-settings.png" width="444" alt="The virtual machine hardware information window with the Overview option selected, showing Basic Details, Hypervisor Details, plus expandable headings Machine Setting and Security, in the right part of the window." /></div></div><h6>Figure 10.25. The virtual machine hardware information window</h6></div><br class="figure-break" /><div class="para">
+ When you are satisfied with the configuration details, click the <span class="guilabel"><strong>Begin Installation</strong></span> button.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/paravirt-5-begin-installation.png" alt="The Begin Installation button." /></div></div><h6>Figure 10.26. The Begin Installation button</h6></div><br class="figure-break" /><div class="para">
+ You can now continue with <a class="xref" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html#aftercreation">Step 3</a>.
+ </div></li></ol></li><li class="step"><p class="title"><strong>Creating the guest virtual machine with virt-install</strong></p><div class="para">
+ Append the following parameter exactly as listed below to add the driver disk to the installation with the <code class="command">virt-install</code> command:
+ </div><pre class="screen">--disk path=/usr/share/virtio-win/virtio-win.vfd,device=floppy</pre><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ If the device you wish to add is a <code class="literal">disk</code> (that is, not a <code class="literal">floppy</code> or a <code class="literal">cdrom</code>), you will also need to add the <code class="code">bus=virtio</code> option to the end of the <em class="parameter"><code>--disk</code></em> parameter, like so:
+ </div><pre class="screen">--disk path=/usr/share/virtio-win/virtio-win.vfd,device=disk,bus=virtio</pre></div></div><div class="para">
+ According to the version of Windows you are installing, append one of the following options to the <code class="command">virt-install</code> command:
+ </div><pre class="screen">--os-variant winxp</pre><pre class="screen">--os-variant win2k3</pre><pre class="screen">--os-variant win7</pre><div class="para">
+ You can now continue with <a class="xref" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html#aftercreation">Step 3</a>.
+ </div></li></ol></li><li class="step" id="aftercreation"><p class="title"><strong>Additional steps for driver installation</strong></p><div class="para">
+ During the installation, additional steps are required to install drivers, depending on the type of Windows guest.
+ </div><ol class="a"><li class="step" id="step-Virtualization-Installing_the_KVM_Windows_para_virtualized_drivers-Windows_Server_2003"><p class="title"><strong>Windows Server 2003 and Windows XP</strong></p><div class="para">
+ Before the installation blue screen repeatedly press <span class="keycap"><strong>F6</strong></span> for third party drivers.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/XP-driver-capture.png" width="444" alt="The Windows pre-installation blue screen reads Window Setup at the top in plain text, and "Press F6 if you need to install a third party SCSI or RAID driver..." at the bottom." /></div></div><h6>Figure 10.27. The Windows Setup screen</h6></div><br class="figure-break" /><div class="para">
+ Press <span class="keycap"><strong>S</strong></span> to install additional device drivers.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/XP-driver-select2.png" width="444" alt="The next Windows pre-installation blue screen reads Window Setup at the top in plain text and details the option to install an additional device. Options at the bottom of the screen include S to "Specify Additional Device", ENTER to continue, or F3 to exit." /></div></div><h6>Figure 10.28. The Windows Setup screen</h6></div><br class="figure-break" /><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/XP-driver-select-driver.png" width="444" alt="The next Windows blue screen reads Window Setup at the top in plain text and provides options to select the SCSI Adapter to be installed. Options at the bottom of the screen include ENTER to select, or F3 to exit." /></div></div><h6>Figure 10.29. The Windows Setup screen</h6></div><br class="figure-break" /><div class="para">
+ Press <span class="keycap"><strong>Enter</strong></span> to continue the installation.
+ </div></li><li class="step" id="step-Virtualization-Installing_the_KVM_Windows_para_virtualized_drivers-Windows_Server_2008"><p class="title"><strong>Windows Server 2008</strong></p><div class="para">
+ Follow the same procedure for Windows Server 2003, but when the installer prompts you for the driver, click on <span class="guilabel"><strong>Load Driver</strong></span>, point the installer to <code class="systemitem">Drive A:</code> and pick the driver that suits your guest operating system and architecture.
+ </div></li></ol></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html"><strong>Prev</strong>10.2. Installing the drivers on an installed Wind...</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="ch10s04.html"><strong>Next</strong>10.4. Using the para-virtualized drivers with Red...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html
new file mode 100644
index 0000000..f2993cb
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html
@@ -0,0 +1,82 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.2. Installing the drivers on an installed Windows guest virtual machine</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html" title="Chapter 10. KVM Para-virtualized Drivers" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html" title="Chapter 10. KVM Para-virtualized Drivers" /><link rel="next" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html" title="10.3. Installing drivers during the Windows installation" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><im
g 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_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html"><strong>Next</strong></a></li></ul><div class="section" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.2. Installing the drivers on an installed Windows guest virtual machine</h2></div></div></div><div class="para">
+ This procedure covers installing the para-virtualized drivers with a virtualized CD-ROM after Windows is installed.
+ </div><div class="para">
+ Follow <a class="xref" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html#proc-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_virt_manager_to_mount_a_CD_ROM_image_for_a_Windows_guest">Procedure 10.1, “Installing from the driver CD-ROM image with virt-manager”</a> to add a CD-ROM image with <code class="command">virt-manager</code> and then install the drivers.
+ </div><div class="procedure" id="proc-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_virt_manager_to_mount_a_CD_ROM_image_for_a_Windows_guest"><h6>Procedure 10.1. Installing from the driver CD-ROM image with virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Open virt-manager and the guest virtual machine</strong></p><div class="para">
+ Open <code class="command">virt-manager</code>, then open the guest virtual machine from the list by double-clicking the guest name.
+ </div></li><li class="step"><p class="title"><strong>Open the hardware window</strong></p><div class="para">
+ Click the lightbulb icon on the toolbar at the top of the window to view virtual hardware details.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/vm_info_button_new.png" alt="The Show virtual hardware details button." /></div></div><h6>Figure 10.1. The virtual hardware details button</h6></div><br class="figure-break" /><div class="para">
+ Then click the <span class="guibutton"><strong>Add Hardware</strong></span> button at the bottom of the new view that appears.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/vm_add_hardware_new.png" alt="The Add Hardware button." /></div></div><h6>Figure 10.2. The virtual machine hardware information window</h6></div><br class="figure-break" /><div class="para">
+ This opens a wizard for adding the new device.
+ </div></li><li class="step"><p class="title"><strong>Select the device type — for Red Hat Enterprise Linux 6 versions prior to 6.2</strong></p><div class="para">
+ Skip this step if you are using Red Hat Enterprise Linux 6.2 or later.
+ </div><div class="para">
+ On Red Hat Enterprise Linux 6 versions prior to version 6.2, you must select the type of device you wish to add. In this case, select <span class="guilabel"><strong>Storage</strong></span> from the dropdown menu.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_hardware_wizard1.png" alt="The Add new virtual hardware wizard window in Red Hat Enterprise Linux 6.1 with Storage selected as the hardware type." /></div></div><h6>Figure 10.3. The Add new virtual hardware wizard in Red Hat Enterprise Linux 6.1</h6></div><br class="figure-break" /><div class="para">
+ Click the <span class="guibutton"><strong>Finish</strong></span> button to proceed.
+ </div></li><li class="step"><p class="title"><strong>Select the ISO file</strong></p><div class="para">
+ Ensure that the <span class="guilabel"><strong>Select managed or other existing storage</strong></span> radio button is selected, and browse to the para-virtualized driver's <code class="filename">.iso</code> image file. The default location for the latest version of the drivers is <code class="filename">/usr/share/virtio-win/virtio-win.iso</code>.
+ </div><div class="para">
+ Change the <span class="guilabel"><strong>Device type</strong></span> to <span class="guilabel"><strong>IDE cdrom</strong></span> and click the <span class="guibutton"><strong>Forward</strong></span> button to proceed.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/type_assigned-KVM_PV_new.png" width="444" alt="Selecting the ISO file in the Add new virtual hardware wizard window." /></div></div><h6>Figure 10.4. The Add new virtual hardware wizard</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Finish adding virtual hardware — for Red Hat Enterprise Linux 6 versions prior to 6.2</strong></p><div class="para">
+ If you are using Red Hat Enterprise Linux 6.2 or later, skip this step.
+ </div><div class="para">
+ On Red Hat Enterprise Linux 6 versions prior to version 6.2, click on the <span class="guibutton"><strong>Finish</strong></span> button to finish adding the virtual hardware and close the wizard.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/done-KVM_PV.png" alt="The final screen of the Add new virtual hardware wizard in Red Hat Enterprise Linux 6.1." /></div></div><h6>Figure 10.5. The Add new virtual hardware wizard in Red Hat Enterprise Linux 6.1</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Reboot</strong></p><div class="para">
+ Reboot or start the virtual machine to begin using the driver disc. Virtualized IDE devices require a restart to for the virtual machine to recognize the new device.
+ </div></li></ol></div><div class="para">
+ Once the CD-ROM with the drivers is attached and the virtual machine has started, proceed with <a class="xref" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html#wooras">Procedure 10.2, “Windows installation on a Windows 7 virtual machine”</a>.
+ </div><div class="procedure" id="wooras"><h6>Procedure 10.2. Windows installation on a Windows 7 virtual machine</h6><div class="para">
+ This procedure installs the drivers on a Windows 7 virtual machine as an example. Adapt the Windows installation instructions to your guest's version of Windows.
+ </div><ol class="1"><li class="step"><p class="title"><strong>Open the Computer Management window</strong></p><div class="para">
+ On the desktop of the Windows virtual machine, click the <span class="guibutton"><strong>Windows</strong></span> icon at the bottom corner of the screen to open the Start menu.
+ </div><div class="para">
+ Right-click on <span class="guilabel"><strong>Computer</strong></span> and select <span class="guilabel"><strong>Manage</strong></span> from the pop-up menu.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/StartDevManagerInVM_win7.png" width="444" alt="A menu window opens on the Computer Management window when right-clicking D the My Computer icon on the desktop." /></div></div><h6>Figure 10.6. The Computer Management window</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Open the Device Manager</strong></p><div class="para">
+ Select the <span class="guilabel"><strong>Device Manager</strong></span> from the left-most pane. This can be found under <span class="guilabel"><strong>Computer Management</strong></span> > <span class="guilabel"><strong>System Tools</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/DevManagerStart_win7.png" width="444" alt="Opening the Device Manager on the right hand side of the Computer Management window." /></div></div><h6>Figure 10.7. The Computer Management window</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Start the driver update wizard</strong></p><ol class="a"><li class="step"><p class="title"><strong>View available system devices</strong></p><div class="para">
+ Expand <span class="guilabel"><strong>System devices</strong></span> by clicking on the arrow to its left.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/DriverInstall-Expand.png" width="444" alt="Detail of viewing available system devices from the Computer Management window." /></div></div><h6>Figure 10.8. Viewing available system devices in the Computer Management window</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Locate the appropriate device</strong></p><div class="para">
+ There are up to four drivers available: the balloon driver, the serial driver, the network driver, and the block driver.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">Balloon</code>, the balloon driver, affects the <span class="guilabel"><strong>PCI standard RAM Controller</strong></span> in the <span class="guilabel"><strong>System devices</strong></span> group.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">vioserial</code>, the serial driver, affects the <span class="guilabel"><strong>PCI Simple Communication Controller</strong></span> in the <span class="guilabel"><strong>System devices</strong></span> group.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">NetKVM</code>, the network driver, affects the <span class="guilabel"><strong>Network adapters</strong></span> group. This driver is only available if a virtio NIC is configured. Configurable parameters for this driver are documented in <a class="xref" href="netkvm-parameters.html">Appendix C, <em>NetKVM Driver Parameters</em></a>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">viostor</code>, the block driver, affects the <span class="guilabel"><strong>Disk drives</strong></span> group. This driver is only available if a virtio disk is configured.
+ </div></li></ul></div><div class="para">
+ Right-click on the device whose driver you wish to update, and select <span class="guilabel"><strong>Update Driver...</strong></span> from the pop-up menu.
+ </div><div class="para">
+ This example installs the balloon driver, so right-click on <span class="guilabel"><strong>PCI standard RAM Controller</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/StartInstallingBalloon-1_win7.png" width="444" alt="Locate the appropriate device under the expanded System Devices entry in the Computer Management window." /></div></div><h6>Figure 10.9. The Computer Management window</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Open the driver update wizard</strong></p><div class="para">
+ From the drop-down menu, select <span class="guilabel"><strong>Update Driver Software...</strong></span> to access the driver update wizard.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/DriverInstall-OpenWizard_win7.png" alt="Open the driver update wizard by right-clicking the device to be updated and selecting the first menu option, Update Driver Software, in the Computer Management window." /></div></div><h6>Figure 10.10. Opening the driver update wizard</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Specify how to find the driver</strong></p><div class="para">
+ The first page of the driver update wizard asks how you want to search for driver software. Click on the second option, <span class="guilabel"><strong>Browse my computer for driver software</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/8-BrowseForDriver_win7.png" width="444" alt="The driver update wizard provides two options for searching for driver software." /></div></div><h6>Figure 10.11. The driver update wizard</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Select the driver to install</strong></p><ol class="a"><li class="step"><p class="title"><strong>Open a file browser</strong></p><div class="para">
+ Click on <span class="guilabel"><strong>Browse...</strong></span>
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/10-w7x86driverstart_win7.png" width="444" alt="The driver update wizard." /></div></div><h6>Figure 10.12. The driver update wizard</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Browse to the location of the driver</strong></p><div class="para">
+ A separate driver is provided for each of the various combinations of operating system and architecture. The drivers are arranged hierarchically according to their driver type, the operating system, and the architecture on which they will be installed: <code class="filename"><em class="replaceable"><code>driver_type</code></em>/<em class="replaceable"><code>os</code></em>/<em class="replaceable"><code>arch</code></em>/</code>. For example, the Balloon driver for a Windows 7 operating system with an x86 (32-bit) architecture, resides in the <code class="filename">Balloon/w7/x86</code> directory.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/9-BrowseToDirectory_win7.png" alt="The Browse For Folder window, which pops up after choosing "Browse" to search for driver software on your computer. Select the folder that contains drivers for your hardware from this window." /></div></div><h6>Figure 10.13. The Browse for driver software pop-up window</h6></div><br class="figure-break" /><div class="para">
+ Once you have navigated to the correct location, click <span class="guilabel"><strong>OK</strong></span>.
+ </div></li><li class="step"><p class="title"><strong>Click <span class="guilabel"><strong>Next</strong></span> to continue</strong></p><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/10-w7x86driverchosen_win7.png" width="444" alt="The Update Driver Software wizard, with the specified location to search for driver software selected, with the Browse button on the right, and the Next and Cancel buttons at the bottom right of the window." /></div></div><h6>Figure 10.14. The Update Driver Software wizard</h6></div><br class="figure-break" /><div class="para">
+ The following screen is displayed while the driver installs:
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/DuringInstallation.png" width="444" alt="As the driver software installs, a flashing bar in the Update Driver Software wizard window shows the system is busy." /></div></div><h6>Figure 10.15. The Update Driver Software wizard</h6></div><br class="figure-break" /></li></ol></li><li class="step"><p class="title"><strong>Close the installer</strong></p><div class="para">
+ The following screen is displayed when installation is complete:
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/12-DriverInstalled.png" width="444" alt="After the driver software installs, the Update Driver Software wizard window read "Windows has successfully updated your driver software"." /></div></div><h6>Figure 10.16. The Update Driver Software wizard</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guilabel"><strong>Close</strong></span> to close the installer.
+ </div></li><li class="step"><p class="title"><strong>Reboot</strong></p><div class="para">
+ Reboot the virtual machine to complete the driver installation.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html"><strong>Prev</strong>Chapter 10. 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="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html"><strong>Next</strong>10.3. Installing drivers during the Windows insta...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices.html
new file mode 100644
index 0000000..3419034
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices.html
@@ -0,0 +1,32 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.5. Using KVM para-virtualized drivers for existing devices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html" title="Chapter 10. KVM Para-virtualized Drivers" /><link rel="prev" href="ch10s04.html" title="10.4. Using the para-virtualized drivers with Red Hat Enterprise Linux 3.9 guests" /><link rel="next" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html" title="10.6. Using KVM para-virtualized drivers for new devices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedora
project.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="ch10s04.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html"><strong>Next</strong></a></li></ul><div class="section" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.5. Using KVM para-virtualized drivers for existing devices</h2></div></div></div><div class="para">
+ You can modify an existing hard disk device attached to the guest to use the <code class="command">virtio</code> driver instead of the virtualized IDE driver. The example shown in this section edits libvirt configuration files. Note that the guest virtual machine does not need to be shut down to perform these steps, however the change will not be applied until the guest is completely shut down and rebooted.
+ </div><div class="procedure"><h6>Procedure 10.4. Using KVM para-virtualized drivers for existing devices</h6><ol class="1"><li class="step"><div class="para">
+ Ensure that you have installed the appropriate driver (<code class="classname">viostor</code>), as described in <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers">Section 10.1, “Installing the KVM Windows para-virtualized drivers”</a>, before continuing with this procedure.
+ </div></li><li class="step"><div class="para">
+ Run the <code class="command">virsh edit <guestname></code> command as root to edit the XML configuration file for your device. For example, <code class="command">virsh edit guest1</code>. The configuration files are located in <code class="filename">/etc/libvirt/qemu</code>.
+ </div></li><li class="step"><div class="para">
+ Below is a file-based block device using the virtualized IDE driver. This is a typical entry for a virtual machine 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 class="step"><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>. Note that if the disk was previously IDE it will have a target similar to hda, hdb, or hdc and so on. When changing to <span class="bold bold"><strong>bus=virtio</strong></span> the target needs to be changed to vda, vdb, or vdc accordingly.
+ </div><pre class="screen"><disk type='file' device='disk'>
+ <source file='/var/lib/libvirt/images/disk1.img'/>
+ <target <span class="bold bold"><strong>dev='vda'</strong></span> <span class="bold bold"><strong>bus='virtio'/></strong></span>
+</disk></pre></li><li class="step"><div class="para">
+ Remove the <span class="bold bold"><strong>address</strong></span> tag inside the <span class="bold bold"><strong>disk</strong></span> tags. This must be done for this procedure to work. Libvirt will regenerate the <span class="bold bold"><strong>address</strong></span> tag appropriately the next time the virtual machine is started.
+ </div></li></ol></div><div class="para">
+ 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.
+ </div><div class="para">
+ Refer to the libvirt website for more details on using Virtio: <a href="http://www.linux-kvm.org/page/Virtio">http://www.linux-kvm.org/page/Virtio</a>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s04.html"><strong>Prev</strong>10.4. Using the para-virtualized drivers with Red...</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_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html"><strong>Next</strong>10.6. Using KVM para-virtualized drivers for new ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/1-7RHEL_local_install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/1-7RHEL_local_install.png
new file mode 100644
index 0000000..68ad5bb
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/1-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/1-Iso_general.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/1-Iso_general.png
new file mode 100644
index 0000000..564c85d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/1-Iso_general.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/1-files_PV-win.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/1-files_PV-win.png
new file mode 100644
index 0000000..bfb31dc
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/1-files_PV-win.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/10-7RHEL_local_install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/10-7RHEL_local_install.png
new file mode 100644
index 0000000..309f788
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/10-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverchosen.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverchosen.png
new file mode 100644
index 0000000..92e56a0
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverchosen.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverchosen_win7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverchosen_win7.png
new file mode 100644
index 0000000..abd28c8
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverchosen_win7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverstart.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverstart.png
new file mode 100644
index 0000000..83b8d25
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverstart.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverstart_win7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverstart_win7.png
new file mode 100644
index 0000000..e02377c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/10-w7x86driverstart_win7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/11-7RHEL_local_install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/11-7RHEL_local_install.png
new file mode 100644
index 0000000..c11a72a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/11-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/12-DriverInstalled.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/12-DriverInstalled.png
new file mode 100644
index 0000000..cb71880
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/12-DriverInstalled.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/14-StartInstallSerial.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/14-StartInstallSerial.png
new file mode 100644
index 0000000..ad1a744
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/14-StartInstallSerial.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/2-7RHEL_local_install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/2-7RHEL_local_install.png
new file mode 100644
index 0000000..5cc3eef
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/2-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/2-Iso_Balloon_Os.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/2-Iso_Balloon_Os.png
new file mode 100644
index 0000000..7280b22
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/2-Iso_Balloon_Os.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/3-7RHEL_local_install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/3-7RHEL_local_install.png
new file mode 100644
index 0000000..ec3adc0
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/3-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/3-Iso_Balloon_Os_arch.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/3-Iso_Balloon_Os_arch.png
new file mode 100644
index 0000000..72ed471
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/3-Iso_Balloon_Os_arch.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/3_PCI_Device.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/3_PCI_Device.png
new file mode 100644
index 0000000..6d45920
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/3_PCI_Device.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/4-7RHEL_local_install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/4-7RHEL_local_install.png
new file mode 100644
index 0000000..ba41670
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/4-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/4-Iso_balloon_files.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/4-Iso_balloon_files.png
new file mode 100644
index 0000000..bc73a65
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/4-Iso_balloon_files.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/4_finish.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/4_finish.png
new file mode 100644
index 0000000..92a37ea
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/4_finish.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/5-7RHEL_local_install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/5-7RHEL_local_install.png
new file mode 100644
index 0000000..05c4e27
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/5-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/6-7RHEL_local_install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/6-7RHEL_local_install.png
new file mode 100644
index 0000000..211498b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/6-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/6.4-2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/6.4-2.png
new file mode 100644
index 0000000..88f6dd9
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/6.4-2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/6.4-3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/6.4-3.png
new file mode 100644
index 0000000..985c268
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/6.4-3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/6.4-4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/6.4-4.png
new file mode 100644
index 0000000..ee00ec2
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/6.4-4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/7-7RHEL_local_install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/7-7RHEL_local_install.png
new file mode 100644
index 0000000..9bca57c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/7-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/8-7RHEL_local_install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/8-7RHEL_local_install.png
new file mode 100644
index 0000000..accbc04
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/8-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/8-BrowseForDriver.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/8-BrowseForDriver.png
new file mode 100644
index 0000000..9adc468
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/8-BrowseForDriver.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/8-BrowseForDriver_win7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/8-BrowseForDriver_win7.png
new file mode 100644
index 0000000..cdc6ad1
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/8-BrowseForDriver_win7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/9-7RHEL_local_install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/9-7RHEL_local_install.png
new file mode 100644
index 0000000..0b5c0eb
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/9-7RHEL_local_install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/9-BrowseToDirectory.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/9-BrowseToDirectory.png
new file mode 100644
index 0000000..fa98b9c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/9-BrowseToDirectory.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/9-BrowseToDirectory_win7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/9-BrowseToDirectory_win7.png
new file mode 100644
index 0000000..a41edd6
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/9-BrowseToDirectory_win7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/COPYME.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/COPYME.png
new file mode 100644
index 0000000..f99eaad
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/COPYME.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ChangeType.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ChangeType.png
new file mode 100644
index 0000000..5b78310
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ChangeType.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Connection_Details.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Connection_Details.png
new file mode 100644
index 0000000..27f542b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Connection_Details.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Create-1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Create-1.png
new file mode 100644
index 0000000..4e3e649
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Create-1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/DevManagerStart.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/DevManagerStart.png
new file mode 100644
index 0000000..930a787
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/DevManagerStart.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/DevManagerStart_win7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/DevManagerStart_win7.png
new file mode 100644
index 0000000..2fba9a8
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/DevManagerStart_win7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-Expand.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-Expand.png
new file mode 100644
index 0000000..3b49f18
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-Expand.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-OpenWizard.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-OpenWizard.png
new file mode 100644
index 0000000..74918fc
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-OpenWizard.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-OpenWizard_win7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-OpenWizard_win7.png
new file mode 100644
index 0000000..aeaa604
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/DriverInstall-OpenWizard_win7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/DriverInstallExpand_win7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/DriverInstallExpand_win7.png
new file mode 100644
index 0000000..d906057
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/DriverInstallExpand_win7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/DuringInstallation.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/DuringInstallation.png
new file mode 100644
index 0000000..389ed9a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/DuringInstallation.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Iso_Balloon_files.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Iso_Balloon_files.png
new file mode 100644
index 0000000..e024530
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Iso_Balloon_files.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Iso_general.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Iso_general.png
new file mode 100644
index 0000000..f99eaad
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Iso_general.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ManageStart.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ManageStart.png
new file mode 100644
index 0000000..3ab0161
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ManageStart.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Network_hardware.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Network_hardware.png
new file mode 100644
index 0000000..a4d305b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Network_hardware.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Network_hardware_virtio.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Network_hardware_virtio.png
new file mode 100644
index 0000000..4c18960
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Network_hardware_virtio.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/PCIremoval.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/PCIremoval.png
new file mode 100644
index 0000000..5817e55
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/PCIremoval.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/PXEguest_5of5.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/PXEguest_5of5.png
new file mode 100644
index 0000000..1348bf3
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/PXEguest_5of5.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_cpu+ram.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_cpu+ram.png
new file mode 100644
index 0000000..ad33769
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_cpu+ram.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_finish_advanced.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_finish_advanced.png
new file mode 100644
index 0000000..057d47d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_finish_advanced.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_storage.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_storage.png
new file mode 100644
index 0000000..fcd4b8a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_storage.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_storage_local.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_storage_local.png
new file mode 100644
index 0000000..613e684
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_storage_local.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_virt-manager_new_1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_virt-manager_new_1.png
new file mode 100644
index 0000000..73bf11f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6_virt-manager_new_1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6local_choose.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6local_choose.png
new file mode 100644
index 0000000..0178c2c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6local_choose.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6local_selectedISO.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6local_selectedISO.png
new file mode 100644
index 0000000..de74827
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHEL6local_selectedISO.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHELKVMpackages-2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHELKVMpackages-2.png
new file mode 100644
index 0000000..65aa27a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHELKVMpackages-2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHELKVMpackages.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHELKVMpackages.png
new file mode 100644
index 0000000..ef73b85
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHELKVMpackages.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHELcustomize14.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHELcustomize14.png
new file mode 100644
index 0000000..83050fc
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHELcustomize14.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHELcustomize15.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHELcustomize15.png
new file mode 100644
index 0000000..597f744
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHELcustomize15.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHELkvmSelect.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHELkvmSelect.png
new file mode 100644
index 0000000..6b897c6
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/RHELkvmSelect.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/SR-IOV_implementation.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/SR-IOV_implementation.png
new file mode 100644
index 0000000..7327f39
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/SR-IOV_implementation.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-VIrt-Manager-fig31pt18.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-VIrt-Manager-fig31pt18.png
new file mode 100644
index 0000000..1299ffa
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-VIrt-Manager-fig31pt18.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt1.png
new file mode 100644
index 0000000..2319393
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt11.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt11.png
new file mode 100644
index 0000000..8cad81e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt11.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt13.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt13.png
new file mode 100644
index 0000000..caf6608
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt13.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt14.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt14.png
new file mode 100644
index 0000000..3254d26
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt14.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt15.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt15.png
new file mode 100644
index 0000000..362e28b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt15.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt16.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt16.png
new file mode 100644
index 0000000..841484e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt16.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt17.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt17.png
new file mode 100644
index 0000000..cd88714
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt17.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt19.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt19.png
new file mode 100644
index 0000000..e0d075d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt19.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt2.png
new file mode 100644
index 0000000..95665bc
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt24.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt24.png
new file mode 100644
index 0000000..c1c6edf
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt24.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt24a.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt24a.png
new file mode 100644
index 0000000..48c1808
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt24a.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt27.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt27.png
new file mode 100644
index 0000000..541d6d9
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt27.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt28.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt28.png
new file mode 100644
index 0000000..fb670c0
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt28.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt29.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt29.png
new file mode 100644
index 0000000..4b1904b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt29.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt3.png
new file mode 100644
index 0000000..d19603a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt4.png
new file mode 100644
index 0000000..c4439e4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt5.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt5.png
new file mode 100644
index 0000000..9801530
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt5.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt6.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt6.png
new file mode 100644
index 0000000..baf2a69
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt6.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt7.png
new file mode 100644
index 0000000..955b48b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager-fig31pt7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt25.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt25.png
new file mode 100644
index 0000000..6cc2283
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt25.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt25a.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt25a.png
new file mode 100644
index 0000000..bd59c7e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt25a.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt26.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt26.png
new file mode 100644
index 0000000..08eca7b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-Virt-Manager_fig31pt26.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic1.png
new file mode 100644
index 0000000..7c133fa
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic10.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic10.png
new file mode 100644
index 0000000..2967923
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic10.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic11.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic11.png
new file mode 100644
index 0000000..ddd69b4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic11.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic2.png
new file mode 100644
index 0000000..52a4bec
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic3.png
new file mode 100644
index 0000000..7be870b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic4.png
new file mode 100644
index 0000000..79d74a5
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic5.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic5.png
new file mode 100644
index 0000000..67e8ac5
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic5.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic6.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic6.png
new file mode 100644
index 0000000..5a53e96
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic6.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic7.png
new file mode 100644
index 0000000..4e17f51
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic8.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic8.png
new file mode 100644
index 0000000..ceee7d9
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic8.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic9.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic9.png
new file mode 100644
index 0000000..97d8476
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-admin-18pt7-pic9.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic1-virt-mgr-guests.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic1-virt-mgr-guests.png
new file mode 100644
index 0000000..ea86b26
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic1-virt-mgr-guests.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic2-add-connection-pull-down.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic2-add-connection-pull-down.png
new file mode 100644
index 0000000..82c0542
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic2-add-connection-pull-down.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic3-Add Connection.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic3-Add Connection.png
new file mode 100644
index 0000000..ffff21f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic3-Add Connection.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic3-Add-Connection.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic3-Add-Connection.png
new file mode 100644
index 0000000..bc5028e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic3-Add-Connection.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic4-OpenSSH.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic4-OpenSSH.png
new file mode 100644
index 0000000..314c36a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic4-OpenSSH.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic5-guest-select-migrate.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic5-guest-select-migrate.png
new file mode 100644
index 0000000..70018bf
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic5-guest-select-migrate.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic6-final-before-migrate.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic6-final-before-migrate.png
new file mode 100644
index 0000000..f244ff7
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic6-final-before-migrate.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic7-Migrating-guest1-rhel6-64.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic7-Migrating-guest1-rhel6-64.png
new file mode 100644
index 0000000..12202b4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic7-Migrating-guest1-rhel6-64.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic8-migrated.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic8-migrated.png
new file mode 100644
index 0000000..3cce087
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-pic8-migrated.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-rhel6pv-virt-method.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-rhel6pv-virt-method.png
new file mode 100644
index 0000000..5f6957a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-rhel6pv-virt-method.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic1.png
new file mode 100644
index 0000000..604e0d8
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic2.png
new file mode 100644
index 0000000..7807aa3
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic4.png
new file mode 100644
index 0000000..09e2781
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic5.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic5.png
new file mode 100644
index 0000000..6950418
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic5.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic6.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic6.png
new file mode 100644
index 0000000..c267406
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic6.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic7-managed.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic7-managed.png
new file mode 100644
index 0000000..a635499
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic7-managed.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic7.png
new file mode 100644
index 0000000..c642653
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic8-create-lvm.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic8-create-lvm.png
new file mode 100644
index 0000000..010c7d0
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic8-create-lvm.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic8-new-storage-volume.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic8-new-storage-volume.png
new file mode 100644
index 0000000..542c15d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic8-new-storage-volume.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic9-local-storage.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic9-local-storage.png
new file mode 100644
index 0000000..8875f30
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic9-local-storage.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic9-storage-volume.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic9-storage-volume.png
new file mode 100644
index 0000000..9d58e09
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt1-pic9-storage-volume.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt2-pic2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt2-pic2.png
new file mode 100644
index 0000000..b6e48c8
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt2-pic2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt2-pic3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt2-pic3.png
new file mode 100644
index 0000000..135ac84
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt2-pic3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic2.png
new file mode 100644
index 0000000..b1b8667
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic3.png
new file mode 100644
index 0000000..17becd5
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic4.png
new file mode 100644
index 0000000..4d42817
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic5.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic5.png
new file mode 100644
index 0000000..c642653
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic5.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic6.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic6.png
new file mode 100644
index 0000000..2135749
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-sevenpt3-pic6.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-virtlab22-Host-Details.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-virtlab22-Host-Details.png
new file mode 100644
index 0000000..d5a3eb3
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Screenshot-virtlab22-Host-Details.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Section_11_pt_2_pt_2_step3_substep_c.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Section_11_pt_2_pt_2_step3_substep_c.png
new file mode 100644
index 0000000..1cb3707
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Section_11_pt_2_pt_2_step3_substep_c.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Section_11_pt_2_pt_2_step3_substep_d.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Section_11_pt_2_pt_2_step3_substep_d.png
new file mode 100644
index 0000000..650b0bb
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Section_11_pt_2_pt_2_step3_substep_d.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Select_storage_pools.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Select_storage_pools.png
new file mode 100644
index 0000000..7e4c07d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Select_storage_pools.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/StartDevManagerInVM.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/StartDevManagerInVM.png
new file mode 100644
index 0000000..438e32b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/StartDevManagerInVM.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/StartDevManagerInVM_win7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/StartDevManagerInVM_win7.png
new file mode 100644
index 0000000..4b59a25
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/StartDevManagerInVM_win7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/StartInstallingBalloon-1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/StartInstallingBalloon-1.png
new file mode 100644
index 0000000..e496e60
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/StartInstallingBalloon-1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/StartInstallingBalloon-1_win7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/StartInstallingBalloon-1_win7.png
new file mode 100644
index 0000000..c03a94a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/StartInstallingBalloon-1_win7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Virt-Manager-Add-Connection.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Virt-Manager-Add-Connection.png
new file mode 100644
index 0000000..44d5e61
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Virt-Manager-Add-Connection.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install.png
new file mode 100644
index 0000000..a7ef6cc
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-cpumem.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-cpumem.png
new file mode 100644
index 0000000..20afcae
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-cpumem.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-import.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-import.png
new file mode 100644
index 0000000..1b8a5c1
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-import.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-local.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-local.png
new file mode 100644
index 0000000..5cb5c11
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP2-local.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP4.png
new file mode 100644
index 0000000..304089a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP5-finish.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP5-finish.png
new file mode 100644
index 0000000..55f87df
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_STEP5-finish.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_final-hardware.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_final-hardware.png
new file mode 100644
index 0000000..def864d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/Virtual_Machine_Name-guest-install_final-hardware.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-capture.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-capture.png
new file mode 100644
index 0000000..aaf7cdb
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-capture.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-select-driver.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-select-driver.png
new file mode 100644
index 0000000..bc2449f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-select-driver.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-select2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-select2.png
new file mode 100644
index 0000000..22f75f7
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/XP-driver-select2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/after_virtualization.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/after_virtualization.png
new file mode 100644
index 0000000..96bd1ee
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/after_virtualization.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/before_virtualization.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/before_virtualization.png
new file mode 100644
index 0000000..e47e9e0
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/before_virtualization.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/block_finish-virtio-win.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/block_finish-virtio-win.png
new file mode 100644
index 0000000..61fb164
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/block_finish-virtio-win.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/block_start-virtio-win.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/block_start-virtio-win.png
new file mode 100644
index 0000000..35abf5e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/block_start-virtio-win.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/bridgePXE.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/bridgePXE.png
new file mode 100644
index 0000000..4c5945f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/bridgePXE.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/bridgefinish.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/bridgefinish.png
new file mode 100644
index 0000000..7ecb971
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/bridgefinish.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/bz734652-step3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/bz734652-step3.png
new file mode 100644
index 0000000..5f9cd87
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/bz734652-step3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/done-KVM_PV.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/done-KVM_PV.png
new file mode 100644
index 0000000..5176b1c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/done-KVM_PV.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/exception-virtio-win.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/exception-virtio-win.png
new file mode 100644
index 0000000..f7df9dd
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/exception-virtio-win.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/icon.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/icon.svg
new file mode 100644
index 0000000..b2f16d0
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/icon.svg
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<svg xmlns:svg="http://www.w3.org/2000/svg" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.0" width="32" height="32" id="svg3017">
+ <defs id="defs3019">
+ <linearGradient id="linearGradient2381">
+ <stop id="stop2383" style="stop-color:#ffffff;stop-opacity:1" offset="0"/>
+ <stop id="stop2385" style="stop-color:#ffffff;stop-opacity:0" offset="1"/>
+ </linearGradient>
+ <linearGradient x1="296.4996" y1="188.81061" x2="317.32471" y2="209.69398" id="linearGradient2371" xlink:href="#linearGradient2381" gradientUnits="userSpaceOnUse" gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)"/>
+ </defs>
+ <g transform="matrix(0.437808,-0.437808,0.437808,0.437808,-220.8237,43.55311)" id="g5089">
+ <path d="m 8.4382985,-6.28125 c -0.6073916,0 -4.3132985,5.94886271 -4.3132985,8.25 l 0,26.71875 c 0,0.846384 0.5818159,1.125 1.15625,1.125 l 25.5625,0 c 0.632342,0 1.125001,-0.492658 1.125,-1.125 l 0,-5.21875 0.28125,0 c 0.49684,0 0.906249,-0.409411 0.90625,-0.90625 l 0,-27.9375 c 0,-0.4968398 -0.40941,-0.90625 -0.90625,-0.90625 l -23.8117015,0 z" transform="translate(282.8327,227.1903)" id="path5091" style="fill:#5c5c4f;stroke:#000000;stroke-width:3.23021388;stroke-miterlimit:4;stroke-dasharray:none"/>
+ <rect width="27.85074" height="29.369793" rx="1.1414107" ry="1.1414107" x="286.96509" y="227.63805" id="rect5093" style="fill:#032c87"/>
+ <path d="m 288.43262,225.43675 25.2418,0 0,29.3698 -26.37615,0.0241 1.13435,-29.39394 z" id="rect5095" style="fill:#ffffff"/>
+ <path d="m 302.44536,251.73726 c 1.38691,7.85917 -0.69311,11.28365 -0.69311,11.28365 2.24384,-1.60762 3.96426,-3.47694 4.90522,-5.736 0.96708,2.19264 1.83294,4.42866 4.27443,5.98941 0,0 -1.59504,-7.2004 -1.71143,-11.53706 l -6.77511,0 z" id="path5097" style="fill:#a70000;fill-opacity:1;stroke-width:2"/>
+ <rect width="25.241802" height="29.736675" rx="0.89682275" ry="0.89682275" x="290.73544" y="220.92249" id="rect5099" style="fill:#809cc9"/>
+ <path d="m 576.47347,725.93939 6.37084,0.41502 0.4069,29.51809 c -1.89202,-1.31785 -6.85427,-3.7608 -8.26232,-1.68101 l 0,-26.76752 c 0,-0.82246 0.66212,-1.48458 1.48458,-1.48458 z" transform="matrix(0.499065,-0.866565,0,1,0,0)" id="rect5101" style="fill:#4573b3;fill-opacity:1"/>
+ <path d="m 293.2599,221.89363 20.73918,0 c 0.45101,0 0.8141,0.3631 0.8141,0.81411 0.21547,6.32836 -19.36824,21.7635 -22.36739,17.59717 l 0,-17.59717 c 0,-0.45101 0.3631,-0.81411 0.81411,-0.81411 z" id="path5103" style="opacity:0.65536726;fill:url(#linearGradient2371);fill-opacity:1"/>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio-add-hardware.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio-add-hardware.png
new file mode 100644
index 0000000..16c8abd
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio-add-hardware.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio-remove-dev.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio-remove-dev.png
new file mode 100644
index 0000000..d21be2c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio-remove-dev.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio1.png
new file mode 100755
index 0000000..4fe8553
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio1replacement.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio1replacement.png
new file mode 100644
index 0000000..e7f1805
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio1replacement.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio2.png
new file mode 100755
index 0000000..b31e7c7
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio3.png
new file mode 100755
index 0000000..3fbefbe
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio4.png
new file mode 100755
index 0000000..bbefebc
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio5.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio5.png
new file mode 100755
index 0000000..d3888d7
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio5.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio5replacement.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio5replacement.png
new file mode 100644
index 0000000..8941fd0
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio5replacement.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio6.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio6.png
new file mode 100755
index 0000000..a843646
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio6.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio6replacement.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio6replacement.png
new file mode 100644
index 0000000..530f0aa
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio6replacement.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio7.png
new file mode 100755
index 0000000..35fbb90
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio7replacement.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio7replacement.png
new file mode 100644
index 0000000..9fe1ad5
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/ide-to-virtio7replacement.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/infotabbutton.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/infotabbutton.png
new file mode 100644
index 0000000..31082a3
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/infotabbutton.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/installmedia-blank.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/installmedia-blank.png
new file mode 100644
index 0000000..365f435
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/installmedia-blank.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/installmedia-select-os1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/installmedia-select-os1.png
new file mode 100644
index 0000000..19b7495
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/installmedia-select-os1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/installmedia-select-volume.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/installmedia-select-volume.png
new file mode 100644
index 0000000..e6344cd
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/installmedia-select-volume.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/network_finish-virtio-win.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/network_finish-virtio-win.png
new file mode 100644
index 0000000..b387250
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/network_finish-virtio-win.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/network_performance-virtio-win.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/network_performance-virtio-win.png
new file mode 100644
index 0000000..130bd7e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/network_performance-virtio-win.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/network_start-virtio-win.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/network_start-virtio-win.png
new file mode 100644
index 0000000..0db3f0e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/network_start-virtio-win.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-0-click-configure-before-install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-0-click-configure-before-install.png
new file mode 100644
index 0000000..71783ad
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-0-click-configure-before-install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-0-click-configure-before-install_win7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-0-click-configure-before-install_win7.png
new file mode 100644
index 0000000..0a9ce10
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-0-click-configure-before-install_win7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-1-click-add-hardware.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-1-click-add-hardware.png
new file mode 100644
index 0000000..e8b7783
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-1-click-add-hardware.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-10-select-custom-installation.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-10-select-custom-installation.png
new file mode 100644
index 0000000..3b12745
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-10-select-custom-installation.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-11-load-driver.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-11-load-driver.png
new file mode 100644
index 0000000..94bb9a0
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-11-load-driver.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-12-insert-disk.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-12-insert-disk.png
new file mode 100644
index 0000000..8fe079e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-12-insert-disk.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-13-select-driver-arch.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-13-select-driver-arch.png
new file mode 100644
index 0000000..21e58f3
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-13-select-driver-arch.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-14-view-drivers-loaded.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-14-view-drivers-loaded.png
new file mode 100644
index 0000000..b6be79f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-14-view-drivers-loaded.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2-disk-type.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2-disk-type.png
new file mode 100644
index 0000000..940a1ec
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2-disk-type.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2a-select-existing-storage.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2a-select-existing-storage.png
new file mode 100644
index 0000000..eae4416
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2a-select-existing-storage.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2b-select-browse-local.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2b-select-browse-local.png
new file mode 100644
index 0000000..0068c9c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2b-select-browse-local.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2c-virtio-win-vfd.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2c-virtio-win-vfd.png
new file mode 100644
index 0000000..76529b4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2c-virtio-win-vfd.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2z-select-storage.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2z-select-storage.png
new file mode 100644
index 0000000..bf7cc17
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-2z-select-storage.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-3-floppy-advanced-options.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-3-floppy-advanced-options.png
new file mode 100644
index 0000000..2448048
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-3-floppy-advanced-options.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-4-after-adding-virtio-disk.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-4-after-adding-virtio-disk.png
new file mode 100644
index 0000000..3350be3
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-4-after-adding-virtio-disk.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-5-begin-installation.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-5-begin-installation.png
new file mode 100644
index 0000000..54eb223
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-5-begin-installation.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-6-windows-install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-6-windows-install.png
new file mode 100644
index 0000000..8df17e7
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-6-windows-install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-6a-select-installation-type.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-6a-select-installation-type.png
new file mode 100644
index 0000000..01196df
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-6a-select-installation-type.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-8-agree-to-license-terms.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-8-agree-to-license-terms.png
new file mode 100644
index 0000000..63a83f8
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-8-agree-to-license-terms.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-adding-virtio-disk.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-adding-virtio-disk.png
new file mode 100644
index 0000000..e87cc64
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-adding-virtio-disk.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-click-begin-installation.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-click-begin-installation.png
new file mode 100644
index 0000000..b5da7ee
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-click-begin-installation.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-floppy-settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-floppy-settings.png
new file mode 100644
index 0000000..f3a29de
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-floppy-settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-settings.png
new file mode 100644
index 0000000..3a2ea73
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-virtio-disk-in-use.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-virtio-disk-in-use.png
new file mode 100644
index 0000000..78d5e93
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-confirm-virtio-disk-in-use.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-device-type-virtio-finish.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-device-type-virtio-finish.png
new file mode 100644
index 0000000..2219703
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-device-type-virtio-finish.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-device-type-virtiodisk.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-device-type-virtiodisk.png
new file mode 100644
index 0000000..44ffd8e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-device-type-virtiodisk.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-remove-disk1-2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-remove-disk1-2.png
new file mode 100644
index 0000000..4f4f38d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-remove-disk1-2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-remove-disk1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-remove-disk1.png
new file mode 100644
index 0000000..634439d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-remove-disk1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-review-virtio-settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-review-virtio-settings.png
new file mode 100644
index 0000000..5c5f00c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-review-virtio-settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-select-device-type-floppy.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-select-device-type-floppy.png
new file mode 100644
index 0000000..c62349c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-select-device-type-floppy.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-storage-win7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-storage-win7.png
new file mode 100644
index 0000000..1236b8d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/paravirt-storage-win7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/pci_host_device.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/pci_host_device.png
new file mode 100644
index 0000000..a4a3ea2
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/pci_host_device.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_create_vm.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_create_vm.png
new file mode 100644
index 0000000..211647e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_create_vm.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_finish.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_finish.png
new file mode 100644
index 0000000..d76cba1
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_finish.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_finish_3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_finish_3.png
new file mode 100644
index 0000000..7fce9df
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_finish_3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_install_method.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_install_method.png
new file mode 100644
index 0000000..2f9d04f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_install_method.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_install_source_2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_install_source_2.png
new file mode 100644
index 0000000..2293268
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_install_source_2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_mem_n_cpu_alloc.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_mem_n_cpu_alloc.png
new file mode 100644
index 0000000..93dccd9
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_mem_n_cpu_alloc.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_network.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_network.png
new file mode 100644
index 0000000..56f4ec9
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_network.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_storage.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_storage.png
new file mode 100644
index 0000000..e71f549
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_storage.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_virt_install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_virt_install.png
new file mode 100644
index 0000000..c9c3557
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel5_rhel6pv_virt_install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6-Screenshot-step2-existing-disk-image.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6-Screenshot-step2-existing-disk-image.png
new file mode 100644
index 0000000..3805b84
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6-Screenshot-step2-existing-disk-image.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-guest1-rhel5-64-final.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-guest1-rhel5-64-final.png
new file mode 100644
index 0000000..a0685cd
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-guest1-rhel5-64-final.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step1.png
new file mode 100644
index 0000000..a2d0836
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step2.png
new file mode 100644
index 0000000..e55c49a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step3.png
new file mode 100644
index 0000000..f5bc777
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step4.png
new file mode 100644
index 0000000..4791de4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step5.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step5.png
new file mode 100644
index 0000000..5aa1fa0
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_Screenshot-step5.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_virt_manager.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_virt_manager.png
new file mode 100644
index 0000000..d2538a7
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/rhel6_virt_manager.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/selinux_uuid_block.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/selinux_uuid_block.png
new file mode 100644
index 0000000..d1a69a9
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/selinux_uuid_block.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-1.png
new file mode 100644
index 0000000..eddb949
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-2.png
new file mode 100644
index 0000000..3738c87
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-3.png
new file mode 100644
index 0000000..5f3de0f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-4.png
new file mode 100644
index 0000000..b17a6fb
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/shutter-9-3_win7-4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step-1-1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step-1-1.png
new file mode 100644
index 0000000..ed6dc3b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step-1-1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step1-1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step1-1.png
new file mode 100644
index 0000000..87a0e0b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step1-1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step1-2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step1-2.png
new file mode 100644
index 0000000..871e7bb
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step1-2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step2-1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step2-1.png
new file mode 100644
index 0000000..b7f01ae
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step2-1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step2-2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step2-2.png
new file mode 100644
index 0000000..25f3edd
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step2-2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step2-3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step2-3.png
new file mode 100644
index 0000000..99b51fc
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step2-3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step2-4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step2-4.png
new file mode 100644
index 0000000..8910ab3
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step2-4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step3-1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step3-1.png
new file mode 100644
index 0000000..689a2a7
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step3-1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step4-1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step4-1.png
new file mode 100644
index 0000000..f12e5fd
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step4-1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step4-2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step4-2.png
new file mode 100644
index 0000000..de53e6c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step4-2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step5-1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step5-1.png
new file mode 100644
index 0000000..d636dcd
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step5-1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step5-2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step5-2.png
new file mode 100644
index 0000000..b76a181
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step5-2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step5-3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step5-3.png
new file mode 100644
index 0000000..bd1e219
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/step5-3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/type_assigned-KVM_PV.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/type_assigned-KVM_PV.png
new file mode 100644
index 0000000..cdc7c6d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/type_assigned-KVM_PV.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/type_assigned-KVM_PV_new.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/type_assigned-KVM_PV_new.png
new file mode 100644
index 0000000..adb335f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/type_assigned-KVM_PV_new.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/v2v-add_storagepool.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/v2v-add_storagepool.png
new file mode 100644
index 0000000..82710ae
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/v2v-add_storagepool.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/v2v-select_host.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/v2v-select_host.png
new file mode 100644
index 0000000..b9b1c99
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/v2v-select_host.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/v2v-storage_tab.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/v2v-storage_tab.png
new file mode 100644
index 0000000..fea967c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/v2v-storage_tab.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager-enable-disk-io.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager-enable-disk-io.png
new file mode 100644
index 0000000..9840461
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager-enable-disk-io.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager-enable-networkio.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager-enable-networkio.png
new file mode 100644
index 0000000..6260da0
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager-enable-networkio.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_nfs_step1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_nfs_step1.png
new file mode 100644
index 0000000..43d4e7e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_nfs_step1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_nfs_step2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_nfs_step2.png
new file mode 100644
index 0000000..7e5d6c8
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_nfs_step2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_storage_pool1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_storage_pool1.png
new file mode 100644
index 0000000..3896a18
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_storage_pool1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_storage_pool2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_storage_pool2.png
new file mode 100644
index 0000000..1a29807
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_add_storage_pool2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_hardware.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_hardware.png
new file mode 100644
index 0000000..08568e6
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_hardware.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_hardware_wizard1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_hardware_wizard1.png
new file mode 100644
index 0000000..b45e590
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_hardware_wizard1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_home.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_home.png
new file mode 100644
index 0000000..62dbd94
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_home.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_host_details_storage.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_host_details_storage.png
new file mode 100644
index 0000000..e4c7c00
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_host_details_storage.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_main.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_main.png
new file mode 100644
index 0000000..e6b7b0d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_main.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_newicon.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_newicon.png
new file mode 100644
index 0000000..9c0a829
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_newicon.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_select_host.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_select_host.png
new file mode 100644
index 0000000..cf2fc41
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_select_host.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_1_name_and_type.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_1_name_and_type.png
new file mode 100644
index 0000000..4c1aa23
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_1_name_and_type.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_2_target_path.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_2_target_path.png
new file mode 100644
index 0000000..67d9310
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_2_target_path.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_3_result.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_3_result.png
new file mode 100644
index 0000000..c2dc6ba
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_dir_step_3_result.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_1_name_and_type.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_1_name_and_type.png
new file mode 100644
index 0000000..516a12c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_1_name_and_type.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_2_paths_and_format.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_2_paths_and_format.png
new file mode 100644
index 0000000..86a2e05
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_2_paths_and_format.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_3_result.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_3_result.png
new file mode 100644
index 0000000..20ee4b6
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_fs_step_3_result.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_1_name_and_type.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_1_name_and_type.png
new file mode 100644
index 0000000..7879370
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_1_name_and_type.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_2a_paths_and_pool.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_2a_paths_and_pool.png
new file mode 100644
index 0000000..1547ee7
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_2a_paths_and_pool.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_2b_format_warning.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_2b_format_warning.png
new file mode 100644
index 0000000..0b88899
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_2b_format_warning.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_3_result.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_3_result.png
new file mode 100644
index 0000000..9510682
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_storage_pools_add_lvm_step_3_result.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_virtualization_method.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_virtualization_method.png
new file mode 100644
index 0000000..6dab167
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virt-manager_virtualization_method.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-disk2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-disk2.png
new file mode 100644
index 0000000..cebc522
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-disk2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-finish3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-finish3.png
new file mode 100644
index 0000000..afaed72
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-finish3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-step1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-step1.png
new file mode 100644
index 0000000..1f8e7c4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-step1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-step2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-step2.png
new file mode 100644
index 0000000..bdef1fd
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-network-step2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-finish3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-finish3.png
new file mode 100644
index 0000000..700e4bc
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-finish3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step1-new.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step1-new.png
new file mode 100644
index 0000000..3c24dd8
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step1-new.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step1.png
new file mode 100644
index 0000000..3235be4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step2-new.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step2-new.png
new file mode 100644
index 0000000..293c735
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step2-new.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step2.png
new file mode 100644
index 0000000..f61cc79
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio-storage-step2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio0-customize.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio0-customize.png
new file mode 100644
index 0000000..49e56bb
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio0-customize.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio3-finished.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio3-finished.png
new file mode 100644
index 0000000..603725e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtio3-finished.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtual_machine_overview.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtual_machine_overview.png
new file mode 100644
index 0000000..8a60772
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/virtual_machine_overview.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vm-add_hardware1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vm-add_hardware1.png
new file mode 100644
index 0000000..e4e761d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vm-add_hardware1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vm_add_hardware.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vm_add_hardware.png
new file mode 100644
index 0000000..ca4b140
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vm_add_hardware.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vm_add_hardware_new.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vm_add_hardware_new.png
new file mode 100644
index 0000000..406dc05
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vm_add_hardware_new.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vm_info_button.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vm_info_button.png
new file mode 100644
index 0000000..7c080f7
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vm_info_button.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vm_info_button_new.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vm_info_button_new.png
new file mode 100644
index 0000000..4156307
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vm_info_button_new.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create1.png
new file mode 100644
index 0000000..1768ae8
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create2.png
new file mode 100644
index 0000000..6adb9fe
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create3_ipv4addspace.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create3_ipv4addspace.png
new file mode 100644
index 0000000..6b884c5
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create3_ipv4addspace.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create4_dhcprange.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create4_dhcprange.png
new file mode 100644
index 0000000..f72639a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create4_dhcprange.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create5_connectphysnet.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create5_connectphysnet.png
new file mode 100644
index 0000000..0219a18
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create5_connectphysnet.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create6_finish.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create6_finish.png
new file mode 100644
index 0000000..632def4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create6_finish.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create7_maintab.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create7_maintab.png
new file mode 100644
index 0000000..b7df642
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_create7_maintab.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_maintab.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_maintab.png
new file mode 100644
index 0000000..d2104e8
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_maintab.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_menuselect.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_menuselect.png
new file mode 100644
index 0000000..7a7623d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vmm_vnet_menuselect.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-01-switch.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-01-switch.png
new file mode 100644
index 0000000..9aa78c1
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-01-switch.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-02-switchandtwoguests.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-02-switchandtwoguests.png
new file mode 100644
index 0000000..9256a76
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-02-switchandtwoguests.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-03-hostwithswitch.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-03-hostwithswitch.png
new file mode 100644
index 0000000..d41424a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-03-hostwithswitch.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-04-hostwithnatswitch.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-04-hostwithnatswitch.png
new file mode 100644
index 0000000..e94c04d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-04-hostwithnatswitch.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-05-switchwithdnsmasq.jpg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-05-switchwithdnsmasq.jpg
new file mode 100644
index 0000000..204d854
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-05-switchwithdnsmasq.jpg differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-06-routed-switch.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-06-routed-switch.png
new file mode 100644
index 0000000..5b5af96
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-06-routed-switch.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-07-isolated-switch.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-07-isolated-switch.png
new file mode 100644
index 0000000..1c234cb
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-07-isolated-switch.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-08-network-overview.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-08-network-overview.png
new file mode 100644
index 0000000..61c1342
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-08-network-overview.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-09-routed-mode-DMZ.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-09-routed-mode-DMZ.png
new file mode 100644
index 0000000..f1ea4e9
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-09-routed-mode-DMZ.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-10-routed-mode-datacenter.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-10-routed-mode-datacenter.png
new file mode 100644
index 0000000..35cd345
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-10-routed-mode-datacenter.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-11-router-mode-mac-restricted.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-11-router-mode-mac-restricted.png
new file mode 100644
index 0000000..bbf3882
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-11-router-mode-mac-restricted.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-12-network-tab-default.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-12-network-tab-default.png
new file mode 100644
index 0000000..63d3582
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/vn-12-network-tab-default.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/w7x86driverchosen.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/w7x86driverchosen.png
new file mode 100644
index 0000000..3f1a832
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/w7x86driverchosen.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/win2003_select_hal.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/win2003_select_hal.png
new file mode 100644
index 0000000..c8d4ecd
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/win2003_select_hal.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/win7paravirt-click-configure-before-install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/win7paravirt-click-configure-before-install.png
new file mode 100644
index 0000000..b692e68
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/images/win7paravirt-click-configure-before-install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html
new file mode 100644
index 0000000..6028df9
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html
@@ -0,0 +1,37 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Virtualization Deployment and Administration Guide</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><meta name="description" content="This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a
preview. The included information and instructions should not be considered complete, and should be used with caution." /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="next" href="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html" title="Preface" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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><li class="next"><a accesskey="n" href="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="book
" id="idp47343280" lang="en-US"><div class="titlepage"><div><div class="producttitle" font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><span class="productname">Fedora Draft Documentation</span> <span class="productnumber"></span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="idp47343280" class="title">Virtualization Deployment and Administration Guide</h1></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h2 class="subtitle">Virtualization Documentation</h2></div><p class="edition">Edition 19.0.1</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 class="corpauthor">
+ <span class="inlinemediaobject"><object data="Common_Content/images/title_logo.svg" type="image/svg+xml"> </object></span>
+
+ </h3></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div xml:lang="en-US" class="authorgroup" lang="en-US"><div class="author"><h3 class="author"><span class="firstname">Laura</span> <span class="surname">Novich</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div></div><div class="author"><h3 class="author"><span class="firstname">Tahlia</span> <span class="surname">Richardson</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div></div><div class="author"><h3 class="author"><span class="firstname">Laura</span> <span class="surname">Bailey</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div></div><div class="author"><h3 class="author"><span class="firstname">Dayle</spa
n> <span class="surname">Parker</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div></div></div></div><hr /><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div id="idm3239984" class="legalnotice"><h1 class="legalnotice">Legal Notice</h1><div class="para">
+ Copyright <span class="trademark"></span>© 2013 Red Hat, Inc.
+ </div><div class="para">
+ The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at <a href="http://creativecommons.org/licenses/by-sa/3.0/">http://creativecommons.org/licenses/by-sa/3.0/</a>. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
+ </div><div class="para">
+ Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
+ </div><div class="para">
+ Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
+ </div><div class="para">
+ For guidelines on the permitted uses of the Fedora trademarks, refer to <a href="https://fedoraproject.org/wiki/Legal:Trademark_guidelines">https://fedoraproject.org/wiki/Legal:Trademark_guidelines</a>.
+ </div><div class="para">
+ <span class="trademark">Linux</span>® is the registered trademark of Linus Torvalds in the United States and other countries.
+ </div><div class="para">
+ <span class="trademark">Java</span>® is a registered trademark of Oracle and/or its affiliates.
+ </div><div class="para">
+ <span class="trademark">XFS</span>® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
+ </div><div class="para">
+ All other trademarks are the property of their respective owners.
+ </div></div></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div class="abstract"><h6>Abstract</h6><div class="para">
+
+ </div><div class="para">
+ This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization.
+ </div><div class="para">
+ Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.
+ </div></div></div></div><hr /></div><div class="toc"><dl><dt><span class="preface"><a href="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html">Preface</a></span></dt><dd><dl><dt><span class="section"><a href="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html#idm8806112">1. Document Conventions</a></span></dt><dd><dl><dt><span class="section"><a href="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html#idp9898400">1.1. Typographic Conventions</a></span></dt><dt><span class="section"><a href="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html#idp20487808">1.2. Pull-quote Conventions</a></span></dt><dt><span class="section"><a href="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html#idm16454224">1.3. Notes and Warnings</a></span></dt></dl></dd><dt><span class="section"><a href="pr01s02.html">2
. We Need Feedback!</a></span></dt></dl></dd><dt><span class="part"><a href="pt01.html">I. Deployment</a></span></dt><dd><dl><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html">1. Introduction</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html#idp1238688">1.1. What is in this guide?</a></span></dt><dt><span class="section"><a href="ch01s02.html">1.2. Virtualization Documentation Suite</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_Requirements.html">2. System requirements</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html">3. KVM guest virtual machine compatibility</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualizatio
n_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html#idp986288">3.1. Fedora 6 support limits</a></span></dt><dt><span class="section"><a href="ch03s02.html">3.2. Supported CPU Models</a></span></dt><dd><dl><dt><span class="section"><a href="ch03s02.html#para-CPU_Models">3.2.1. Guest CPU models</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html">4. Virtualization restrictions</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html#sect-chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-KVM_Restrictions">4.1. KVM restrictions</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions.
html">4.2. Application restrictions</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions.html">4.3. Other restrictions</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html">5. Installing the virtualization packages</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_with_a_new_Red_Hat_Enterprise_Linux_installation">5.1. Configuring a Virtualization Host installation</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html"
>5.2. Installing virtualization packages on an existing Fedora system</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html">6. Guest virtual machine installation overview</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html#idp23296736">6.1. Guest virtual machine prerequisites and considerations</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install.html">6.2. Creating guests with virt-install</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html">6.3. Creating guests with virt-manager</a></span></dt><dt><span class="section"><a href="s
ect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE.html">6.4. Installing guest virtual machines with PXE</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html">7. Installing a Red Hat Enterprise Linux 6 guest virtual machine on a Red Hat Enterprise Linux 6 host</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html#idm9173792">7.1. Creating a Red Hat Enterprise Linux 6 guest with local installation media</a></span></dt><dt><span class="section"><a href="ch07s02.html">7.2. Creating a Red Hat Enterprise Linux 6 guest with a network installation tree</a></span></dt><dt><span class="section"><a href="ch07s03.html">7.3. Creating a Red Hat Enterprise Linux 6 guest with PXE</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch08.htm
l">8. Virtualizing Fedora on Other Platforms</a></span></dt><dd><dl><dt><span class="section"><a href="ch08.html#idp12886800">8.1. On VMWare</a></span></dt><dt><span class="section"><a href="ch08s02.html">8.2. On Hyper-V</a></span></dt></dl></dd><dt><span class="chapter"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html">9. Installing a fully-virtualized Windows guest</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_virt-install">9.1. Using virt-install to create a guest</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized
_drivers.html">10. KVM Para-virtualized Drivers</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers">10.1. Installing the KVM Windows para-virtualized drivers</a></span></dt><dt><span class="section"><a href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html">10.2. Installing the drivers on an installed Windows guest virtual machine</a></span></dt><dt><span class="section"><a href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html">10.3. Installing drivers during the Windows installation</a></span></dt><dt><span class="section"><a href="ch10s04.html">10.4. Us
ing the para-virtualized drivers with Red Hat Enterprise Linux 3.9 guests</a></span></dt><dt><span class="section"><a href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices.html">10.5. Using KVM para-virtualized drivers for existing devices</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html">10.6. Using KVM para-virtualized drivers for new devices</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html">11. Network configuration</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html#sect
-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_address_translation_NAT_with_libvirt">11.1. Network Address Translation (NAT) with libvirt</a></span></dt><dt><span class="section"><a href="ch11s02.html">11.2. Disabling vhost-net</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html">11.3. Bridged networking with libvirt</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html">12. PCI device configuration</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-AI_device_to_a_host">12.1. Assigning a PCI device with virsh</a
></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host.html">12.2. Assigning a PCI device with virt-manager</a></span></dt><dt><span class="section"><a href="ch12s03.html">12.3. PCI device assignment with virt-install</a></span></dt><dt><span class="section"><a href="ch12s04.html">12.4. Detaching an assigned PCI device</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html">13. SR-IOV</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html#idm16453008">13.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html">13.2. Using SR-IOV</a></span></dt><dt><span class="section"><a href="ch13s03.html">1
3.3. Troubleshooting SR-IOV</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management.html">14. KVM guest timing management</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html">15. Network booting with libvirt</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html#idp27011888">15.1. Preparing the boot server</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html#idm9946464">15.1.1. Setting up a PXE boot server on a private libvirt network</a></span></dt></dl></dd><dt><span class="section"><a href="ch15s02.html">15.2. Booting a guest using PXE</a></span></dt><dd><dl><dt><span class="section
"><a href="ch15s02.html#idm3778464">15.2.1. Using bridged networking</a></span></dt><dt><span class="section"><a href="ch15s02s02.html">15.2.2. Using a private libvirt network</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="qemu-ga.html">16. QEMU Guest Agent</a></span></dt><dd><dl><dt><span class="section"><a href="qemu-ga.html#idm5352160">16.1. Set Up Communication between Guest Agent and Host</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="pt02.html">II. Administration</a></span></dt><dd><dl><dt><span class="chapter"><a href="chap-Virtualization_Administration_Guide-Server_best_practices.html">17. Server best practices</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization-Security_for_virtualization.html">18. Security for virtualization</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization-Security_for_virtualization.html#sect-Virtualization-Security_for_virtualization-Storage_security_issues"
>18.1. Storage security issues</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization.html">18.2. SELinux and virtualization</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Security_for_virtualization-SELinux_considerations.html">18.3. SELinux</a></span></dt><dt><span class="section"><a href="ch18s04.html">18.4. Virtualization firewall information</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-sVirt.html">19. sVirt</a></span></dt><dd><dl><dt><span class="section"><a href="chap-sVirt.html#idp5009424">19.1. Security and Virtualization</a></span></dt><dt><span class="section"><a href="ch19s02.html">19.2. sVirt labeling</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Administration_Guide-KVM_live_migration.html">20. KVM live migration</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-KVM_liv
e_migration.html#Live_migration_requirements">20.1. Live migration requirements</a></span></dt><dt><span class="section"><a href="Live_migration_and_RHEL_compatibility.html">20.2. Live migration and Fedora version compatibility </a></span></dt><dt><span class="section"><a href="shared-storage-nfs-migration.html">20.3. Shared storage example: NFS for a simple migration</a></span></dt><dt><span class="section"><a href="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html">20.4. Live KVM migration with virsh</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html#add-notes">20.4.1. Additonal tips for migration with virsh </a></span></dt><dt><span class="section"><a href="virsh-migration-arguements.html">20.4.2. Additional options for the virsh migrate command</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Virtualization-KVM_live_migration-Migrating_with_virt_manage
r.html">20.5. Migrating with virt-manager</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html">21. Remote management of guests</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html#sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_with_SSH">21.1. Remote management with SSH</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html">21.2. Remote management over TLS and SSL</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes.html">21.3. Transport modes</a></span></dt></dl></dd><dt><span class="chapter"><a href="sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM.html">22. Overcommitting with KVM</a>
</span></dt><dt><span class="chapter"><a href="chap-KSM.html">23. KSM</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization_Administration_GuideAdvanced.html">24. Advanced virtualization administration</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_GuideAdvanced.html#idm804272">24.1. Control Groups (cgroups)</a></span></dt><dt><span class="section"><a href="ch24s02.html">24.2. Hugepage support</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html">25. Miscellaneous administration tasks</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html#sect-Virtualization-Tips_and_tricks-Automatically_starting_guests">25.1. Automatically starting guests</a></span></dt><dt><span class="section"><a href="sect-mem-dump-off.html">25.2. Guest memory allocation</a></span></dt><dt><span class="section">
<a href="sect-Virtualization-Tips_and_tricks-Using_qemu_img.html">25.3. Using qemu-img</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions.html">25.4. Verifying virtualization extensions</a></span></dt><dt><span class="section"><a href="ch25s05.html">25.5. Setting KVM processor affinities</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address.html">25.6. Generating a new unique MAC address</a></span></dt><dt><span class="section"><a href="ch25s07.html">25.7. Improving guest response time</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html">25.8. Disable SMART disk monitoring for guests</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server.html">25.9. Configuring a VNC Server</a></span></dt><dt><span class=
"section"><a href="sect-gracefully-shut-down-guests.html">25.10. Gracefully shutting down guests</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers.html">25.11. Virtual machine timer management with libvirt</a></span></dt><dt><span class="section"><a href="sect-perf-mon.html">25.12. Using PMU to monitor guest performance</a></span></dt><dt><span class="section"><a href="sect-s3-s4.html">25.13. Guest virtual machine power management</a></span></dt><dt><span class="section"><a href="sect-qemu-ga.html">25.14. QEMU Guest Agent Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="sect-qemu-ga.html#sect-guest-synch">25.14.1. guest-sync</a></span></dt><dt><span class="section"><a href="subsect-guest-synch-delimited.html">25.14.2. guest-sync-delimited</a></span></dt></dl></dd><dt><span class="section"><a href="sect-limit-redirection.html">25.15. Setting a limit on device redirection</a></span></dt><dt><span clas
s="section"><a href="sect-dynamic-vNIC.html">25.16. Dynamically changing a host or a network bridge that is attached to a virtual NIC</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Administration_Guide-Storage_Concepts.html">26. Storage concepts</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Concepts.html#sect-Virtualization-Storage_Concepts-Storage_Pools">26.1. Storage pools</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Storage_Concepts-Volumes.html">26.2. Volumes </a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html">27. Storage pools</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating_Storage_Pools">27.1. Creating storage pools </a></span></dt><dd><dl><dt
><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-Dedicated_Disk_Devices">27.1.1. Disk-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-File_Systems">27.1.2. Partition-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-Local_Directories">27.1.3. Directory-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-LVM">27.1.4. LVM-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtual
ization-Storage_Pools-Creating-iSCSI">27.1.5. iSCSI-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-NFS">27.1.6. NFS-based storage pools</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Administration_Guide-Storage_Volumes.html">28. Volumes </a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Volumes.html#sect-Virtualization-Storage_Volumes-Creating_volumes">28.1. Creating volumes</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Storage_Volumes-Cloning_volumes.html">28.2. Cloning volumes</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html">28.3. Adding storage devices to guests</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Vi
rtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html#sect-Virtualization-Adding_storage_devices_to_guests-Adding_file_based_storage_to_a_guest">28.3.1. Adding file based storage to a guest</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html">28.3.2. Adding hard drives and other block devices to a guest</a></span></dt><dt><span class="section"><a href="sect-Managing_storage_controllers_in_a_guest.html">28.3.3. Managing storage controllers in a guest</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Virtualization-Storage_Volumes-Deleting_volumes.html">28.4. Deleting and removing volumes</a></span></dt></dl></dd><dt><span class="chapter"><a href="vhostmd.html">29. The Virtual Host Metrics Daemon (vhostmd)</a></span></dt><dd><dl><dt><span class="section"><a href="vhostmd.html#idp15936832">29.1. Installing vhostmd on the host</a></s
pan></dt><dt><span class="section"><a href="ch29s02.html">29.2. Configuration of vhostmd</a></span></dt><dt><span class="section"><a href="ch29s03.html">29.3. Starting and stopping the daemon</a></span></dt><dt><span class="section"><a href="ch29s04.html">29.4. Verifying that vhostmd is working from the host</a></span></dt><dt><span class="section"><a href="ch29s05.html">29.5. Configuring guests to see the metrics</a></span></dt><dt><span class="section"><a href="ch29s06.html">29.6. Using vm-dump-metrics in Fedora guests to verify operation</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="pt03.html">III. Appendicies</a></span></dt><dd><dl><dt><span class="appendix"><a href="chap-Virtualization_Administration_Guide-Troubleshooting.html">A. Troubleshooting</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Troubleshooting.html#sect-Virtualization-Troubleshooting_-Debugging_and_troubleshooting_">A.1. Debugging an
d troubleshooting tools</a></span></dt><dt><span class="section"><a href="apas02.html">A.2. kvm_stat</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles.html">A.3. Troubleshooting with serial consoles</a></span></dt><dt><span class="section"><a href="apas04.html">A.4. Virtualization log files</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Troubleshooting-Loop_device_errors.html">A.5. Loop device errors</a></span></dt><dt><span class="section"><a href="live-migration-errors.html">A.6. Live Migration Errors</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html">A.7. Enabling Intel VT-x and AMD-V virtualization hardware extensions in BIOS</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Troubleshooting-KVM_networking_performance.html">A.8. KVM networking per
formance</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard.html">A.9. Missing characters on guest console with Japanese keyboard</a></span></dt><dt><span class="section"><a href="sec-known-issues-windows-xp-guests.html">A.10. Known Windows XP guest issues</a></span></dt></dl></dd><dt><span class="appendix"><a href="apb.html">B. Common <span class="application"><strong>libvirt</strong></span> errors and troubleshooting</a></span></dt><dd><dl><dt><span class="section"><a href="apb.html#App_Libvirt_Daemon">B.1. <span class="application"><strong>libvirtd</strong></span> failed to start</a></span></dt><dt><span class="section"><a href="App_Hypervisor_Connection_Fail.html">B.2. The URI failed to connect to the hypervisor</a></span></dt><dd><dl><dt><span class="section"><a href="App_Hypervisor_Connection_Fail.html#Sect_Cannot_read_CA_certificate">B.2.1. Cannot read CA certificate</a></span></dt><
dt><span class="section"><a href="Sect_Failed_to_connect_socket.html">B.2.2. Failed to connect socket ... : Permission denied</a></span></dt><dt><span class="section"><a href="Sect_Other_Connectivity_Errors.html">B.2.3. Other connectivity errors</a></span></dt></dl></dd><dt><span class="section"><a href="App_Domain_Processor.html">B.3. The guest virtual machine cannot be started: <code class="computeroutput">internal error guest CPU is not compatible with host CPU</code></a></span></dt><dt><span class="section"><a href="App_Domain_Monitor_Socket.html">B.4. Guest starting fails with error: <code class="computeroutput">monitor socket did not show up</code></a></span></dt><dt><span class="section"><a href="App_Domain_Console.html">B.5. <code class="computeroutput">Internal error cannot find character device (null)</code></a></span></dt><dt><span class="section"><a href="App_Domain_Not_Booting.html">B.6. Guest virtual machine booting stalls with error: <code class="computeroutpu
t">No boot device</code></a></span></dt><dt><span class="section"><a href="App_Virt_Net_Not_Starting.html">B.7. Virtual network <em class="replaceable"><code>default</code></em> has not been started</a></span></dt><dt><span class="section"><a href="App_PXE_Guest_Boot_Fail.html">B.8. PXE boot (or DHCP) on guest failed</a></span></dt><dt><span class="section"><a href="App_Macvtap.html">B.9. Guest can reach outside network, but cannot reach host when using macvtap interface</a></span></dt><dt><span class="section"><a href="App_DHCP_Response_Checksums.html">B.10. Could not add rule to fixup DHCP response checksums on network <em class="replaceable"><code>'default'</code></em></a></span></dt><dt><span class="section"><a href="App_Bridge_Device.html">B.11. Unable to add bridge br0 port vnet0: No such device</a></span></dt><dt><span class="section"><a href="App_Generic_Ethernet.html">B.12. Guest is unable to start with error: <code class="computeroutput">warning: could not open /de
v/net/tun</code></a></span></dt><dt><span class="section"><a href="App_Migration_Address.html">B.13. Migration fails with <code class="computeroutput">Error: unable to resolve address</code></a></span></dt><dt><span class="section"><a href="App_Migration_Disk_Image.html">B.14. Migration fails with <code class="computeroutput">Unable to allow access for disk path: No such file or directory</code></a></span></dt><dt><span class="section"><a href="App_No_Guest_Machines.html">B.15. No guest virtual machines are present when <span class="application"><strong>libvirtd</strong></span> is started</a></span></dt><dt><span class="section"><a href="App_TCP_Ports.html">B.16. Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor</a></span></dt><dt><span class="section"><a href="App_XML_Errors.html">B.17. Common XML errors</a></span></dt><dd><dl><dt><span class="section"><a href="App_XML_Errors.html#idm10882560">B.17.1. Editing doma
in definition</a></span></dt><dt><span class="section"><a href="apbs17s02.html">B.17.2. XML syntax errors</a></span></dt><dt><span class="section"><a href="apbs17s03.html">B.17.3. Logic and configuration errors</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="netkvm-parameters.html">C. NetKVM Driver Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="netkvm-parameters.html#idp424208">C.1. Configurable parameters for NetKVM</a></span></dt></dl></dd><dt><span class="appendix"><a href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html">D. qemu-kvm Whitelist</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html#idp4706576">D.1. Introduction</a></span></dt><dt><span class="section"><a href="apds02.html">D.2. Basic options</a></span></dt><dt><span class="section"><a href="apds03.html">D.3. Disk options</a></span></dt><dt><span class="section"><a href="apds04.h
tml">D.4. Display options</a></span></dt><dt><span class="section"><a href="apds05.html">D.5. Network options</a></span></dt><dt><span class="section"><a href="apds06.html">D.6. Device options</a></span></dt><dt><span class="section"><a href="apds07.html">D.7. Linux/Multiboot boot </a></span></dt><dt><span class="section"><a href="apds08.html">D.8. Expert options</a></span></dt><dt><span class="section"><a href="apds09.html">D.9. Help and information options</a></span></dt><dt><span class="section"><a href="apds10.html">D.10. Miscellaneous options</a></span></dt></dl></dd><dt><span class="appendix"><a href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html">E. Managing guests with virsh</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html#idp28563584">E.1. virsh command quick reference</a></span></dt><dt><span class="section"><a href="sect-Attaching_and_updating_a_device_with
_virsh.html">E.2. Attaching and updating a device with virsh</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor.html">E.3. Connecting to the hypervisor</a></span></dt><dt><span class="section"><a href="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html">E.4. Creating a virtual machine XML dump (configuration file)</a></span></dt><dd><dl><dt><span class="section"><a href="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html#sect-multifunction-pci-install">E.4.1. Adding multifunction PCI devices to KVM guests</a></span></dt></dl></dd><dt><span class="section"><a href="apes05.html">E.5. Suspending, resuming, saving and restoring a guest</a></span></dt><dt><span class="section"><a href="apes06.html">E.6. Shutting down, rebooting and force-shutdown of a guest</a></span></dt><dt><span class="section
"><a href="apes07.html">E.7. Retrieving guest information</a></span></dt><dt><span class="section"><a href="apes08.html">E.8. Retrieving node information</a></span></dt><dt><span class="section"><a href="apes09.html">E.9. Storage pool information</a></span></dt><dt><span class="section"><a href="apes10.html">E.10. Displaying per-guest information</a></span></dt><dt><span class="section"><a href="apes11.html">E.11. Managing virtual networks</a></span></dt><dt><span class="section"><a href="migrating_guests-with-virsh.html">E.12. Migrating guests with virsh</a></span></dt><dt><span class="section"><a href="sect-man-disk-image.html">E.13. Disk image management with live block copy</a></span></dt><dd><dl><dt><span class="section"><a href="sect-man-disk-image.html#sect-blockcommit">E.13.1. Using blockcommit to shorten a backing chain</a></span></dt><dt><span class="section"><a href="sub-sect-blockpull.html">E.13.2. Using blockpull to shorten a backing chain</a></span></dt><dt><sp
an class="section"><a href="sub-sect-blkresize.html">E.13.3. Using blockresize to change the size of a domain path</a></span></dt></dl></dd><dt><span class="section"><a href="sect-guest-cpu-model-config.html">E.14. Guest CPU model configuration</a></span></dt><dd><dl><dt><span class="section"><a href="sect-guest-cpu-model-config.html#sect-guest-cpu-intro">E.14.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-learn-about-host-cpu.html">E.14.2. Learning about the host CPU model</a></span></dt><dt><span class="section"><a href="apes14s03.html">E.14.3. Determining a compatible CPU model to suit a pool of hosts</a></span></dt><dt><span class="section"><a href="apes14s04.html">E.14.4. Configuring the guest CPU model</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html">F. Managing guests with the Virtual Machine Manager (virt-manager)<
/a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Starting_virt_manager">F.1. Starting virt-manager</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html">F.2. The Virtual Machine Manager main window</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_.html">F.3. The virtual hardware details window</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html">F.4. Virtual Machine graphical console</a></span></dt><dt><span class="s
ection"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window.html">F.5. Adding a remote connection</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html">F.6. Displaying guest details</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html">F.7. Performance monitoring</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html">F.8. Displaying CPU usage for guests</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage.html">F.9. Displaying CPU usage for hosts</a></span></dt><dt><span class="section"><a href="se
ct-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO.html">F.10. Displaying Disk I/O</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO.html">F.11. Displaying Network I/O</a></span></dt></dl></dd><dt><span class="appendix"><a href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html">G. Guest disk access with offline tools</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html#sect-introduction-Virtualization_Administration_Guide-Guest_Disks_libguestfs">G.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-Terminology-Guest_Disks_libguestfs.html">G.2. Terminology</a></span></dt><dt><span class="section"><a href="sect-Guide-Guest_Disks_libguestfs-installation.html">G.3. Installation</a></span></dt><dt><span class="section">
<a href="sect-the_guestfish_shell.html">G.4. The guestfish shell</a></span></dt><dd><dl><dt><span class="section"><a href="sect-the_guestfish_shell.html#sect-Viewing_file_systems_with_guestfish">G.4.1. Viewing file systems with guestfish</a></span></dt><dt><span class="section"><a href="sect-Modifying-files-with-guestfish.html">G.4.2. Modifying files with guestfish</a></span></dt><dt><span class="section"><a href="sect-Other-actions-with-guestfish.html">G.4.3. Other actions with guestfish</a></span></dt><dt><span class="section"><a href="sect-Shell-scripting-with-guestfish.html">G.4.4. Shell scripting with guestfish</a></span></dt><dt><span class="section"><a href="sect-Augeas-and-libguestfs-scripting.html">G.4.5. Augeas and libguestfs scripting</a></span></dt></dl></dd><dt><span class="section"><a href="sect-other-commands.html">G.5. Other commands</a></span></dt><dt><span class="section"><a href="sect-virt-rescue.html">G.6. virt-rescue: The rescue shell</a></span></dt><dd>
<dl><dt><span class="section"><a href="sect-virt-rescue.html#sect-virt-rescue-intro">G.6.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-run-virt-rescue.html">G.6.2. Running virt-rescue</a></span></dt></dl></dd><dt><span class="section"><a href="sect-virt-df.html">G.7. virt-df: Monitoring disk usage</a></span></dt><dd><dl><dt><span class="section"><a href="sect-virt-df.html#sect-virt-df-intro">G.7.1. Introduction</a></span></dt><dt><span class="section"><a href="run-virt-df.html">G.7.2. Running virt-df</a></span></dt></dl></dd><dt><span class="section"><a href="sect-virt-resize.html">G.8. virt-resize: resizing guests offline</a></span></dt><dd><dl><dt><span class="section"><a href="sect-virt-resize.html#sect-virt-resize-intro">G.8.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-expand-disk-image.html">G.8.2. Expanding a disk image</a></span></dt></dl></dd><dt><span class="section"><a href="sect-virt-inspector.html">G.9. virt-insp
ector: inspecting guests</a></span></dt><dd><dl><dt><span class="section"><a href="sect-virt-inspector.html#sect-virt-inspector-intro">G.9.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-virt-inspector-install.html">G.9.2. Installation</a></span></dt><dt><span class="section"><a href="sect-virt-inspector-run.html">G.9.3. Running virt-inspector</a></span></dt></dl></dd><dt><span class="section"><a href="sect-virt-win-reg.html">G.10. virt-win-reg: Reading and editing the Windows Registry</a></span></dt><dd><dl><dt><span class="section"><a href="sect-virt-win-reg.html#sect-virt-win-reg-intro">G.10.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-virt-win-reg-install.html">G.10.2. Installation</a></span></dt><dt><span class="section"><a href="sect-virt-win-reg-use.html">G.10.3. Using virt-win-reg</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Using-API-Programming-Languages.html">G.11. Using the API from Programming
Languages</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Using-API-Programming-Languages.html#API-and-C">G.11.1. Interaction with the API via a C program</a></span></dt></dl></dd><dt><span class="section"><a href="sect-libguestfs-troubleshoot.html">G.12. Troubleshooting</a></span></dt><dt><span class="section"><a href="sect-libguestfs-more-docs.html">G.13. Where to find further documentation</a></span></dt></dl></dd><dt><span class="appendix"><a href="chap-Virtualization_Administration_Guide-Virtual_Networking.html">H. Virtual Networking</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Virtual_Networking.html#sect-virtual_network-switches-livbvirt">H.1. Virtual network switches</a></span></dt><dt><span class="section"><a href="sect-Network_Address_Translation-libvirt.html">H.2. Network Address Translation</a></span></dt><dt><span class="section"><a href="sect-network-protocols.html">H.3. Networking protocols</
a></span></dt><dd><dl><dt><span class="section"><a href="sect-network-protocols.html#sect-DNS_and_DHCP-protocols-libvirt">H.3.1. DNS and DHCP</a></span></dt><dt><span class="section"><a href="sub-sect-routed-mode-libvirt.html">H.3.2. Routed mode</a></span></dt><dt><span class="section"><a href="sub-sect-iso-mode.html">H.3.3. Isolated mode</a></span></dt></dl></dd><dt><span class="section"><a href="sect-the-Default_Configuration-libvirt.html">H.4. The default configuration</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Virtual_Networking-Example_scenarios.html">H.5. Examples of common scenarios</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Virtualization-Virtual_Networking-Example_scenarios.html#sub-sect-routed-mode">H.5.1. Routed mode</a></span></dt><dt><span class="section"><a href="sub-sect-nat-mode.html">H.5.2. NAT mode</a></span></dt><dt><span class="section"><a href="sub-sect-isolated-mode.html">H.5.3. Isolated mode</a></span></dt
></dl></dd><dt><span class="section"><a href="sect-Virtualization-Virtual_Networking-Managing_a_virtual_network.html">H.6. Managing a virtual network</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Virtual_Networking-Creating_a_virtual_network.html">H.7. Creating a virtual network</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest.html">H.8. Attaching a virtual network to a guest</a></span></dt><dt><span class="section"><a href="sect-attch-nic-physdev.html">H.9. Directly attaching to physical interface</a></span></dt><dt><span class="section"><a href="sect-applying-network-filtering.html">H.10. Applying network filtering</a></span></dt><dd><dl><dt><span class="section"><a href="sect-applying-network-filtering.html#intro-sub-sect-applying-network-filtering">H.10.1. Introduction</a></span></dt><dt><span class="section"><a href="sub-sect-filt-chain.html">H.10.2. Filtering chains</a></
span></dt><dt><span class="section"><a href="sub-sect-filt-chain-props.html">H.10.3. Filtering chain priorities</a></span></dt><dt><span class="section"><a href="sub-sect-vars-in-filters.html">H.10.4. Usage of variables in filters</a></span></dt><dt><span class="section"><a href="sub-sect-auto-IP-add-detect-dhcp-snoop.html">H.10.5. Automatic IP address detection and DHCP snooping</a></span></dt><dt><span class="section"><a href="sub-sect-vars-reserved.html">H.10.6. Reserved Variables</a></span></dt><dt><span class="section"><a href="sub-sect-element-oview.html">H.10.7. Element and attribute overview</a></span></dt><dt><span class="section"><a href="sub-sect-ref-filter.html">H.10.8. References to other filters</a></span></dt><dt><span class="section"><a href="sub-sect-filter-rules.html">H.10.9. Filter rules</a></span></dt><dt><span class="section"><a href="sub-sect-supp-pros.html">H.10.10. Supported protocols</a></span></dt><dt><span class="section"><a href="sub-sect-adv-filt
-topics.html">H.10.11. Advanced Filter Configuration Topics</a></span></dt><dt><span class="section"><a href="sub-sect-limitations-filters-network-subsystem.html">H.10.12. Limitations</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="appe-Virtualization-Additional_resources.html">I. Additional resources</a></span></dt><dd><dl><dt><span class="section"><a href="appe-Virtualization-Additional_resources.html#sect-Virtualization-Additional_resources-Online_resources">I.1. Online resources</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Additional_resources-Installed_documentation.html">I.2. Installed documentation</a></span></dt></dl></dd><dt><span class="appendix"><a href="ch-lib-dom-xml.html">J. Manipulating the domain xml</a></span></dt><dd><dl><dt><span class="section"><a href="ch-lib-dom-xml.html#sect-gen-metadata">J.1. General information and metadata</a></span></dt><dt><span class="section"><a href="sect-dom-xml-op-sys-boot.html"
>J.2. Operating system booting</a></span></dt><dd><dl><dt><span class="section"><a href="sect-dom-xml-op-sys-boot.html#sub-sect-op-sys-boot-bios-boot">J.2.1. BIOS bootloader</a></span></dt><dt><span class="section"><a href="sub-sect-op-sys-host-boot.html">J.2.2. Host bootloader</a></span></dt><dt><span class="section"><a href="sub-sect-op-sys-dir-kern-boot.html">J.2.3. Direct kernel boot</a></span></dt><dt><span class="section"><a href="sub-sect-op-sys-cont-boot.html">J.2.4. Container boot</a></span></dt></dl></dd><dt><span class="section"><a href="sect-smbios-sys-info.html">J.3. SMBIOS system information</a></span></dt><dt><span class="section"><a href="sect-cpu-allocation.html">J.4. CPU allocation</a></span></dt><dt><span class="section"><a href="sect-cpu-tuning.html">J.5. CPU tuning</a></span></dt><dt><span class="section"><a href="sect-mem-back.html">J.6. Memory backing</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-mem-tuning.html">J.7. Memory tu
ning</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-numa-node-tuning.html">J.8. NUMA node tuning</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-blk-io-tuning.html">J.9. Block I/O tuning</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-res-part.html">J.10. Resource partitioning</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-cpu-model-top.html">J.11. CPU model and topology</a></span></dt><dd><dl><dt><span class="section"><a href="sect-libvirt-dom-xml-cpu-model-top.html#sub-sect-libvirt-dom-xml-res-part-guest-numa">J.11.1. Guest NUMA topology</a></span></dt></dl></dd><dt><span class="section"><a href="sect-libvirt-dom-xml-event-config.html">J.12. Events configuration</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-pwr-man.html">J.13. Power Management</a></span></dt><dt><span class="section"><a href="apjs14.html">J.14. Hypervisor features</a></span></dt><dt><span
class="section"><a href="sect-libvirt-dom-xml-time-keep.html">J.15. Time keeping</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-devices.html">J.16. Devices</a></span></dt><dd><dl><dt><span class="section"><a href="sect-libvirt-dom-xml-devices.html#sub-sect-libvirt-dom-xml-devices">J.16.1. Hard drives, floppy disks, CDROMs</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-filesystems.html">J.16.2. Filesystems</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-device-addresses.html">J.16.3. Device addresses</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-controllers.html">J.16.4. Controllers</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-device-leases.html">J.16.5. Device leases</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-host-device-assignment.html">J.16.6. Host dev
ice assignment</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-redirected-devices.html">J.16.7. Redirected devices</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-smartcard.html">J.16.8. Smartcard devices</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html">J.16.9. Network interfaces</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-input-devices.html">J.16.10. Input devices</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-hub-devices.html">J.16.11. Hub devices</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-graphical-framebuffers.html">J.16.12. Graphical framebuffers</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-video.html">J.16.13. Video devices</a></span></dt><dt><span class="section"><a href
="sub-section-libvirt-dom-xml-devices-consoles.html">J.16.14. Consoles, serial, parallel, and channel devices</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-guest-interface.html">J.16.15. Guest interfaces</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-channel.html">J.16.16. Channel</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-host-interface.html">J.16.17. Host interface</a></span></dt></dl></dd><dt><span class="section"><a href="section-libvirt-dom-xml-sound-devices.html">J.17. Sound devices</a></span></dt><dt><span class="section"><a href="section-libvirt-dom-xml-watchdog.html">J.18. Watchdog device</a></span></dt><dt><span class="section"><a href="section-libvirt-dom-xml-memory-baloon-device.html">J.19. Memory balloon device</a></span></dt><dt><span class="section"><a href="section-libvirt-dom-xml-random-number-gen.html">J.20. Random number generator devic
e</a></span></dt><dt><span class="section"><a href="section-libvirt-dom-xml-tpm-device.html">J.21. TPM devices</a></span></dt><dt><span class="section"><a href="section-libvirt-dom-xml-security-label.html">J.22. Security label</a></span></dt><dt><span class="section"><a href="section-libvirt-dom-xml-example.html">J.23. Example domain XML configuration</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="appe-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Revision_History.html">K. Revision History</a></span></dt></dl></div></div><ul class="docnav"><li class="previous"></li><li class="next"><a accesskey="n" href="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html"><strong>Next</strong>Preface</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/live-migration-errors.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/live-migration-errors.html
new file mode 100644
index 0000000..f251ad7
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/live-migration-errors.html
@@ -0,0 +1,14 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.6. Live Migration Errors</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Troubleshooting.html" title="Appendix A. Troubleshooting" /><link rel="prev" href="sect-Virtualization-Troubleshooting-Loop_device_errors.html" title="A.5. Loop device errors" /><link rel="next" href="sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html" title="A.7. Enabling Intel VT-x and AMD-V virtualization hardware extensions in BIOS" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sect-Virtualization-Troubleshooting-Loop_device_errors.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html"><strong>Next</strong></a></li></ul><div class="section" id="live-migration-errors"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.6. Live Migration Errors</h2></div></div></div><div class="para">
+ There may be cases where a live migration causes the memory contents to be re-transfered over and over again This process causes the guest to be in a state where it is constantly writing to memory and therefore will slow down migration. If this should occur, and the guest is writing more than several tens of MBs per second, then live migration may fail to finish (converge). This issue is scheduled to be fixed in Fedora 19 or 20.
+ </div><div class="para">
+ The current live-migration implementation has a default migration time configured to 30ms. This value determines the guest pause time at the end of the migration in order to transfer the leftovers. Higher values increase the odds that live migration will converge
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Troubleshooting-Loop_device_errors.html"><strong>Prev</strong>A.5. 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-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html"><strong>Next</strong>A.7. Enabling Intel VT-x and AMD-V virtualization...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/migrating_guests-with-virsh.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/migrating_guests-with-virsh.html
new file mode 100644
index 0000000..90c2924
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/migrating_guests-with-virsh.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.12. Migrating guests with virsh</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="prev" href="apes11.html" title="E.11. Managing virtual networks" /><link rel="next" href="sect-man-disk-image.html" title="E.13. Disk image management with live block copy" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="apes11.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-man-disk-image.html"><strong>Next</strong></a></li></ul><div class="section" id="migrating_guests-with-virsh"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">E.12. Migrating guests with virsh</h2></div></div></div><div class="para">
+ Information on migration using virsh is located in the section entitled Live KVM Migration with virsh Refer to <a class="xref" href="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html">Section 20.4, “Live KVM migration with virsh”</a>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apes11.html"><strong>Prev</strong>E.11. Managing virtual networks</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-man-disk-image.html"><strong>Next</strong>E.13. Disk image management with live block copy</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/netkvm-parameters.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/netkvm-parameters.html
new file mode 100644
index 0000000..ca6d949
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/netkvm-parameters.html
@@ -0,0 +1,90 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix C. NetKVM Driver Parameters</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt03.html" title="Part III. Appendicies" /><link rel="prev" href="apbs17s03s02.html" title="B.17.3.2. Incorrect drive device type" /><link rel="next" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html" title="Appendix D. qemu-kvm Whitelist" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="apbs17s03s02.html"><
strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="appendix" id="netkvm-parameters" lang="en-US"><div class="titlepage"><div><div><h1 class="title">NetKVM Driver Parameters</h1></div></div></div><div class="para">
+ After the NetKVM driver is installed, you can configure it to better suit your environment. The parameters listed in this section can be configured in the Windows <span class="guilabel"><strong>Device Manager</strong></span> (<code class="filename">devmgmt.msc</code>).
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Modifying the driver's parameters causes Windows to re-load that driver. This interrupts existing network activity.
+ </div></div></div><div class="procedure"><h6>Procedure C.1. Configuring NetKVM Parameters</h6><ol class="1"><li class="step"><p class="title"><strong>Open <span class="guilabel"><strong>Device Manager</strong></span></strong></p><div class="para">
+ Click on the <span class="guibutton"><strong>Start</strong></span> button. In the right-hand pane, right-click on <span class="guilabel"><strong>Computer</strong></span>, and click <span class="guilabel"><strong>Manage</strong></span>. If prompted, click <span class="guibutton"><strong>Continue</strong></span> on the <span class="guilabel"><strong>User Account Control</strong></span> window. This opens the <span class="guilabel"><strong>Computer Management</strong></span> window.
+ </div><div class="para">
+ In the left-hand pane of the <span class="guilabel"><strong>Computer Management</strong></span> window, click <span class="guilabel"><strong>Device Manager</strong></span>.
+ </div></li><li class="step"><p class="title"><strong>Locate the correct device</strong></p><div class="para">
+ In the central pane of the <span class="guilabel"><strong>Computer Management</strong></span> window, click on the <span class="guilabel"><strong>+</strong></span> symbol beside <span class="guilabel"><strong>Network adapters</strong></span>.
+ </div><div class="para">
+ Under the list of <span class="guilabel"><strong>Fedora VirtIO Ethernet Adapter</strong></span> devices, double-click on <span class="guilabel"><strong>NetKVM</strong></span>. This opens the <span class="guilabel"><strong>Properties</strong></span> window for that device.
+ </div></li><li class="step"><p class="title"><strong>View device parameters</strong></p><div class="para">
+ In the <span class="guilabel"><strong>Properties</strong></span> window, click on the <span class="guilabel"><strong>Advanced</strong></span> tab.
+ </div></li><li class="step"><p class="title"><strong>Modify device parameters</strong></p><div class="para">
+ Click on the parameter you wish to modify to display the options for that parameter.
+ </div><div class="para">
+ Modify the options as appropriate, then click on <span class="guibutton"><strong>OK</strong></span> to save your changes.
+ </div></li></ol></div><div class="section" id="idp424208"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp424208">C.1. Configurable parameters for NetKVM</h2></div></div></div><div class="variablelist"><h6>Logging parameters</h6><dl class="variablelist"><dt class="varlistentry"><span class="term">Logging.Enable</span></dt><dd><div class="para">
+ A Boolean value that determines whether logging is enabled. The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">Logging.Level</span></dt><dd><div class="para">
+ An integer that defines the logging level. As the integer increases, so does the verbosity of the log. The default value is <code class="literal">0</code> (errors only). <code class="literal">1-2</code> adds configuration messages. <code class="literal">3-4</code> adds packet flow information. <code class="literal">5-6</code> adds interrupt and DPC level trace information.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ High logging levels will slow down your guest virtual machine.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">Logging.Statistics(sec)</span></dt><dd><div class="para">
+ An integer that defines whether log statistics are printed, and the time in seconds between each periodical statistics printout. The default value is <code class="literal">0</code> (no logging statistics).
+ </div></dd></dl></div><div class="variablelist"><h6>Initial parameters</h6><dl class="variablelist"><dt class="varlistentry"><span class="term">Assign MAC</span></dt><dd><div class="para">
+ A string that defines the locally-administered MAC address for the para-virtualized NIC. This is not set by default.
+ </div></dd><dt class="varlistentry"><span class="term">Init.ConnectionRate(Mb)</span></dt><dd><div class="para">
+ An integer that represents the connection rate in megabytes. The default value for Windows 2008 and later is <code class="literal">10000</code>.
+ </div></dd><dt class="varlistentry"><span class="term">Init.Do802.1PQ</span></dt><dd><div class="para">
+ A Boolean value that enables Priority/VLAN tag population and removal support. The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">Init.UseMergedBuffers</span></dt><dd><div class="para">
+ A Boolean value that enables merge-able RX buffers. The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">Init.UsePublishEvents</span></dt><dd><div class="para">
+ A Boolean value that enables published event use. The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">Init.MTUSize</span></dt><dd><div class="para">
+ An integer that defines the maximum transmission unit (MTU). The default value is <code class="literal">1500</code>. Any value from 500 to 65500 is acceptable.
+ </div></dd><dt class="varlistentry"><span class="term">Init.IndirectTx</span></dt><dd><div class="para">
+ Controls whether indirect ring descriptors are in use. The default value is <code class="literal">Disable</code>, which disables use of indirect ring descriptors. Other valid values are <code class="literal">Enable</code>, which enables indirect ring descriptor usage; and <code class="literal">Enable*</code>, which enables conditional use of indirect ring descriptors.
+ </div></dd><dt class="varlistentry"><span class="term">Init.MaxTxBuffers</span></dt><dd><div class="para">
+ An integer that represents the amount of TX ring descriptors that will be allocated. The default value is <code class="literal">1024</code>. Valid values are: 16, 32, 64, 128, 256, 512, or 1024.
+ </div></dd><dt class="varlistentry"><span class="term">Init.MaxRxBuffers</span></dt><dd><div class="para">
+ An integer that represents the amount of RX ring descriptors that will be allocated. The default value is <code class="literal">256</code>. Valid values are: 16, 32, 64, 128, 256, 512, or 1024.
+ </div></dd><dt class="varlistentry"><span class="term">Offload.Tx.Checksum</span></dt><dd><div class="para">
+ Specifies the TX checksum offloading mode.
+ </div><div class="para">
+ In Fedora 18 and onward, the valid values for this parameter are <code class="literal">All</code> (the default), which enables IP, TCP and UDP checksum offloading for both IPv4 and IPv6; <code class="literal">TCP/UDP(v4,v6)</code>, which enables TCP and UDP checksum offloading for both IPv4 and IPv6; <code class="literal">TCP/UDP(v4)</code>, which enables TCP and UDP checksum offloading for IPv4 only; and <code class="literal">TCP(v4)</code>, which enables only TCP checksum offloading for IPv4 only.
+ </div><div class="para">
+ In Fedora 17 and earlier, the valid values for this parameter are <code class="literal">TCP/UDP</code> (the default value), which enables TCP and UDP checksum offload; <code class="literal">TCP</code>, which enables only TCP checksum offload; or <code class="literal">Disable</code>, which disables TX checksum offload.
+ </div></dd><dt class="varlistentry"><span class="term">Offload.Tx.LSO</span></dt><dd><div class="para">
+ A Boolean value that enables TX TCP Large Segment Offload (LSO). The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">Offload.Rx.Checksum</span></dt><dd><div class="para">
+ Specifies the RX checksum offloading mode.
+ </div><div class="para">
+ In Fedora 18 and onward, the valid values for this parameter are <code class="literal">All</code> (the default), which enables IP, TCP and UDP checksum offloading for both IPv4 and IPv6; <code class="literal">TCP/UDP(v4,v6)</code>, which enables TCP and UDP checksum offloading for both IPv4 and IPv6; <code class="literal">TCP/UDP(v4)</code>, which enables TCP and UDP checksum offloading for IPv4 only; and <code class="literal">TCP(v4)</code>, which enables only TCP checksum offloading for IPv4 only.
+ </div><div class="para">
+ In Fedora 17 and earlier, the valid values are <code class="literal">Disable</code> (the default), which disables RX checksum offloading; <code class="literal">All</code>, which enables TCP, UDP, and IP checksum offloading; <code class="literal">TCP/UDP</code>, which enables TCP and UDP checksum offloading; and <code class="literal">TCP</code>, which enables only TCP checksum offloading.
+ </div></dd></dl></div><div class="variablelist"><h6>Test and debug parameters</h6><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Test and debug parameters should only be used for testing or debugging; they should not be used in production.
+ </div></div></div><dl class="variablelist"><dt class="varlistentry"><span class="term">TestOnly.DelayConnect(ms)</span></dt><dd><div class="para">
+ The period for which to delay connection upon startup, in milliseconds. The default value is <code class="literal">0</code>.
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.DPCChecking</span></dt><dd><div class="para">
+ Sets the DPC checking mode. <code class="literal">0</code> (the default) disables DPC checking. <code class="literal">1</code> enables DPC checking; each hang test verifies DPC activity and acts as if the DPC was spawned. <code class="literal">2</code> clears the device interrupt status and is otherwise identical to <code class="literal">1</code>.
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.Scatter-Gather</span></dt><dd><div class="para">
+ A Boolean value that determines whether scatter-gather functionality is enabled. The default value is <code class="literal">1</code> (enabled). Setting this value to <code class="literal">0</code> disables scatter-gather functionality and all dependent capabilities.
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.InterruptRecovery</span></dt><dd><div class="para">
+ A Boolean value that determines whether interrupt recovery is enabled. The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.PacketFilter</span></dt><dd><div class="para">
+ A Boolean value that determines whether packet filtering is enabled. The default value is <code class="literal">1</code> (enabled).
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.BatchReceive</span></dt><dd><div class="para">
+ A Boolean value that determines whether packets are received in batches, or singularly. The default value is <code class="literal">1</code>, which enables batched packet receipt.
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.Promiscuous</span></dt><dd><div class="para">
+ A Boolean value that determines whether promiscuous mode is enabled. The default value is <code class="literal">0</code> (disabled).
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.AnalyzeIPPackets</span></dt><dd><div class="para">
+ A Boolean value that determines whether the checksum fields of outgoing IP packets are tested and verified for debugging purposes. The default value is <code class="literal">0</code> (no checking).
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.RXThrottle</span></dt><dd><div class="para">
+ An integer that determines the number of receive packets handled in a single DPC. The default value is <code class="literal">1000</code>.
+ </div></dd><dt class="varlistentry"><span class="term">TestOnly.UseSwTxChecksum</span></dt><dd><div class="para">
+ A Boolean value that determines whether hardware checksumming is enabled. The default value is <code class="literal">0</code> (disabled).
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apbs17s03s02.html"><strong>Prev</strong>B.17.3.2. Incorrect drive device type</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_Administration_Guide-QEMU_KVM_Whitelist.html"><strong>Next</strong>Appendix D. qemu-kvm Whitelist</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/pr01s02.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/pr01s02.html
new file mode 100644
index 0000000..47e98a5
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/pr01s02.html
@@ -0,0 +1,16 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2. We Need Feedback!</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html" title="Preface" /><link rel="prev" href="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html" title="Preface" /><link rel="next" href="pt01.html" title="Part I. Deployment" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 access
key="p" href="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="pt01.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="idp19902480" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp19902480">2. We Need Feedback!</h2></div></div></div><a id="idp19903632" class="indexterm"></a><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>Documentation.</strong></span>
+ </div><div class="para">
+ When submitting a bug report, be sure to mention the manual's identifier: <em class="citetitle">doc-Virtualization_Deployment_and_Administration_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="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-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="pt01.html"><strong>Next</strong>Part I. Deployment</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html
new file mode 100644
index 0000000..a52c3f5
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html
@@ -0,0 +1,95 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Preface</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="prev" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="next" href="pr01s02.html" title="2. We Need Feedback!" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 clas
s="next"><a accesskey="n" href="pr01s02.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="preface" id="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Preface</h1></div></div></div><div xml:lang="en-US" class="section" id="idm8806112" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm8806112">1. 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" id="idp9898400"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idp9898400">1.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 keycaps 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 keycap, all presented in mono-spaced bold and all distinguishable thanks to context.
+ </div><div class="para">
+ Key combinations can be distinguished from keycaps 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>F2</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>F1</strong></span> to return to your X-Windows session.
+ </div></blockquote></div><div class="para">
+ The first paragraph highlights the particular keycap to press. The second highlights two key combinations (each a set of three keycaps with 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; dialog box text; labeled 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</strong></span> → <span class="guisubmenu"><strong>Preferences</strong></span> → <span class="guimenuitem"><strong>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</strong></span> → <span class="guisubmenu"><strong>Accessories</strong></span> → <span class="guimenuitem"><strong>Character Map</strong></span> from the main menu bar. Next, choose <span class="guimenu"><strong>Search</strong></span> → <span class="guimenuitem"><strong>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"><stron
g>Copy</strong></span> button. Now switch back to your document and choose <span class="guimenu"><strong>Edit</strong></span> → <span class="guimenuitem"><strong>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">
+ <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">
+ Publican is a <em class="firstterm">DocBook</em> publishing system.
+ </div></blockquote></div></div><div class="section" id="idp20487808"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idp20487808">1.2. Pull-quote Conventions</h3></div></div></div><div class="para">
+ Terminal output and source code listings 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 add syntax highlighting as follows:
+ </div><pre class="programlisting">package org.<span class="perl_Function">jboss</span>.<span class="perl_Function">book</span>.<span class="perl_Function">jca</span>.<span class="perl_Function">ex1</span>;
+
+<span class="perl_Keyword">import</span> javax.naming.InitialContext;
+
+<span class="perl_Keyword">public</span> <span class="perl_Keyword">class</span> ExClient
+{
+ <span class="perl_Keyword">public</span> <span class="perl_DataType">static</span> <span class="perl_DataType">void</span> <span class="perl_Function">main</span>(String args[])
+ <span class="perl_Keyword">throws</span> Exception
+ {
+ InitialContext iniCtx = <span class="perl_Keyword">new</span> InitialContext();
+ Object ref = iniCtx.<span class="perl_Function">lookup</span>(<span class="perl_String">"EchoBean"</span>);
+ EchoHome home = (EchoHome) ref;
+ Echo echo = home.<span class="perl_Function">create</span>();
+
+ System.<span class="perl_Function">out</span>.<span class="perl_Function">println</span>(<span class="perl_String">"Created Echo"</span>);
+
+ System.<span class="perl_Function">out</span>.<span class="perl_Function">println</span>(<span class="perl_String">"Echo.echo('Hello') = "</span> + echo.<span class="perl_Function">echo</span>(<span class="perl_String">"Hello"</span>));
+ }
+}</pre></div><div class="section" id="idm16454224"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm16454224">1.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"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Notes are tips, shortcuts or alternative approaches 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><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><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 a box labeled 'Important' will not cause data loss but may cause irritation and frustration.
+ </div></div></div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Warnings should not be ignored. Ignoring warnings will most likely cause data loss.
+ </div></div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="index.html"><strong>Prev</strong>Virtualization Deployment and Administration 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. We Need Feedback!</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/pt01.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/pt01.html
new file mode 100644
index 0000000..5bbd0f1
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/pt01.html
@@ -0,0 +1,10 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Part I. Deployment</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="prev" href="pr01s02.html" title="2. We Need Feedback!" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html" title="Chapter 1. Introduction" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html"><strong>Next</strong></a></li></ul><div class="part" id="idm16123616"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part I. Deployment</h1></div></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html">1. Introduction</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Introduction.html#idp1238688">1.1. What is in this guide?</a></span></dt><dt><span class="section"><a href="ch01s02.html">1.2. Virtualization Documentation Suite</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-System_Requirement
s.html">2. System requirements</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html">3. KVM guest virtual machine compatibility</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_Compatibility.html#idp986288">3.1. Fedora 6 support limits</a></span></dt><dt><span class="section"><a href="ch03s02.html">3.2. Supported CPU Models</a></span></dt><dd><dl><dt><span class="section"><a href="ch03s02.html#para-CPU_Models">3.2.1. Guest CPU models</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html">4. Virtualization restrictions</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions.html#sect-chap-Virtualiza
tion_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-KVM_Restrictions">4.1. KVM restrictions</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Application_Restrictions.html">4.2. Application restrictions</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Virtualization_Restrictions-Other_Restrictions.html">4.3. Other restrictions</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html">5. Installing the virtualization packages</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_with_a_new_Red_Hat_Ent
erprise_Linux_installation">5.1. Configuring a Virtualization Host installation</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html">5.2. Installing virtualization packages on an existing Fedora system</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html">6. Guest virtual machine installation overview</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html#idp23296736">6.1. Guest virtual machine prerequisites and considerations</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install.html">6.2. Creating guests with v
irt-install</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html">6.3. Creating guests with virt-manager</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE.html">6.4. Installing guest virtual machines with PXE</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html">7. Installing a Red Hat Enterprise Linux 6 guest virtual machine on a Red Hat Enterprise Linux 6 host</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html#idm9173792">7.1. Creating a Red Hat Enterprise Linux 6 guest with local installation media</a></span></dt><dt><span class="section"><a
href="ch07s02.html">7.2. Creating a Red Hat Enterprise Linux 6 guest with a network installation tree</a></span></dt><dt><span class="section"><a href="ch07s03.html">7.3. Creating a Red Hat Enterprise Linux 6 guest with PXE</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch08.html">8. Virtualizing Fedora on Other Platforms</a></span></dt><dd><dl><dt><span class="section"><a href="ch08.html#idp12886800">8.1. On VMWare</a></span></dt><dt><span class="section"><a href="ch08s02.html">8.2. On Hyper-V</a></span></dt></dl></dd><dt><span class="chapter"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html">9. Installing a fully-virtualized Windows guest</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html#sect-Virtualizati
on_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_virt-install">9.1. Using virt-install to create a guest</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html">10. KVM Para-virtualized Drivers</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers">10.1. Installing the KVM Windows para-virtualized drivers</a></span></dt><dt><span class="section"><a href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Mounting_the_image_with_virt_manager.html">10.2. Installing the drivers on an installed Windows guest virtual machine</a></span></dt><dt><span cla
ss="section"><a href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_with_a_virtualized_floppy_disk.html">10.3. Installing drivers during the Windows installation</a></span></dt><dt><span class="section"><a href="ch10s04.html">10.4. Using the para-virtualized drivers with Red Hat Enterprise Linux 3.9 guests</a></span></dt><dt><span class="section"><a href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices.html">10.5. Using KVM para-virtualized drivers for existing devices</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html">10.6. Using KVM para-virtualized drivers for new devices</a></span></dt></dl></dd><dt><span class="chapt
er"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html">11. Network configuration</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_address_translation_NAT_with_libvirt">11.1. Network Address Translation (NAT) with libvirt</a></span></dt><dt><span class="section"><a href="ch11s02.html">11.2. Disabling vhost-net</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html">11.3. Bridged networking with libvirt</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html">12. PCI device configuration</a>
</span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-AI_device_to_a_host">12.1. Assigning a PCI device with virsh</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host.html">12.2. Assigning a PCI device with virt-manager</a></span></dt><dt><span class="section"><a href="ch12s03.html">12.3. PCI device assignment with virt-install</a></span></dt><dt><span class="section"><a href="ch12s04.html">12.4. Detaching an assigned PCI device</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html">13. SR-IOV</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installatio
n_Guide-SR_IOV.html#idm16453008">13.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html">13.2. Using SR-IOV</a></span></dt><dt><span class="section"><a href="ch13s03.html">13.3. Troubleshooting SR-IOV</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-KVM_guest_timing_management.html">14. KVM guest timing management</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html">15. Network booting with libvirt</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Libvirt_network_booting.html#idp27011888">15.1. Preparing the boot server</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Host_Configurati
on_and_Guest_Installation_Guide-Libvirt_network_booting.html#idm9946464">15.1.1. Setting up a PXE boot server on a private libvirt network</a></span></dt></dl></dd><dt><span class="section"><a href="ch15s02.html">15.2. Booting a guest using PXE</a></span></dt><dd><dl><dt><span class="section"><a href="ch15s02.html#idm3778464">15.2.1. Using bridged networking</a></span></dt><dt><span class="section"><a href="ch15s02s02.html">15.2.2. Using a private libvirt network</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="qemu-ga.html">16. QEMU Guest Agent</a></span></dt><dd><dl><dt><span class="section"><a href="qemu-ga.html#idm5352160">16.1. Set Up Communication between Guest Agent and Host</a></span></dt></dl></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s02.html"><strong>Prev</strong>2. 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_Host_Configuration_and_Guest_Installation_Guide-Introduction.html"><strong>Next</strong>Chapter 1. Introduction</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/pt02.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/pt02.html
new file mode 100644
index 0000000..ab2a4fb
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/pt02.html
@@ -0,0 +1,10 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Part II. Administration</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="prev" href="qemu-ga.html" title="Chapter 16. QEMU Guest Agent" /><link rel="next" href="chap-Virtualization_Administration_Guide-Server_best_practices.html" title="Chapter 17. Server best practices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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=
"qemu-ga.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_Guide-Server_best_practices.html"><strong>Next</strong></a></li></ul><div class="part" id="idm4092784"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part II. Administration</h1></div></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl><dt><span class="chapter"><a href="chap-Virtualization_Administration_Guide-Server_best_practices.html">17. Server best practices</a></span></dt><dt><span class="chapter"><a href="chap-Virtualization-Security_for_virtualization.html">18. Security for virtualization</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization-Security_for_virtualization.html#sect-Virtualization-Security_for_virtualization-Storage_security_issues">18.1. Storage security issues</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Security_for_virtualization-SELinux
_and_virtualization.html">18.2. SELinux and virtualization</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Security_for_virtualization-SELinux_considerations.html">18.3. SELinux</a></span></dt><dt><span class="section"><a href="ch18s04.html">18.4. Virtualization firewall information</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-sVirt.html">19. sVirt</a></span></dt><dd><dl><dt><span class="section"><a href="chap-sVirt.html#idp5009424">19.1. Security and Virtualization</a></span></dt><dt><span class="section"><a href="ch19s02.html">19.2. sVirt labeling</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Administration_Guide-KVM_live_migration.html">20. KVM live migration</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-KVM_live_migration.html#Live_migration_requirements">20.1. Live migration requirements</a></span></dt><dt><span class="section"><a href="Live_m
igration_and_RHEL_compatibility.html">20.2. Live migration and Fedora version compatibility </a></span></dt><dt><span class="section"><a href="shared-storage-nfs-migration.html">20.3. Shared storage example: NFS for a simple migration</a></span></dt><dt><span class="section"><a href="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html">20.4. Live KVM migration with virsh</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html#add-notes">20.4.1. Additonal tips for migration with virsh </a></span></dt><dt><span class="section"><a href="virsh-migration-arguements.html">20.4.2. Additional options for the virsh migrate command</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager.html">20.5. Migrating with virt-manager</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Administration
_Guide-Remote_management_of_virtualized_guests.html">21. Remote management of guests</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html#sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_with_SSH">21.1. Remote management with SSH</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html">21.2. Remote management over TLS and SSL</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes.html">21.3. Transport modes</a></span></dt></dl></dd><dt><span class="chapter"><a href="sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM.html">22. Overcommitting with KVM</a></span></dt><dt><span class="chapter"><a href="chap-KSM.html">23. KSM</a></span></dt><dt><span class="chapter"><a href="chap-Virtualizat
ion_Administration_GuideAdvanced.html">24. Advanced virtualization administration</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_GuideAdvanced.html#idm804272">24.1. Control Groups (cgroups)</a></span></dt><dt><span class="section"><a href="ch24s02.html">24.2. Hugepage support</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html">25. Miscellaneous administration tasks</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html#sect-Virtualization-Tips_and_tricks-Automatically_starting_guests">25.1. Automatically starting guests</a></span></dt><dt><span class="section"><a href="sect-mem-dump-off.html">25.2. Guest memory allocation</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Using_qemu_img.html">25.3. Using qemu-img</a></span></dt><dt><span class="section"><a href=
"sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions.html">25.4. Verifying virtualization extensions</a></span></dt><dt><span class="section"><a href="ch25s05.html">25.5. Setting KVM processor affinities</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address.html">25.6. Generating a new unique MAC address</a></span></dt><dt><span class="section"><a href="ch25s07.html">25.7. Improving guest response time</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html">25.8. Disable SMART disk monitoring for guests</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server.html">25.9. Configuring a VNC Server</a></span></dt><dt><span class="section"><a href="sect-gracefully-shut-down-guests.html">25.10. Gracefully shutting down guests</a></span></dt><dt><span class="section
"><a href="sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers.html">25.11. Virtual machine timer management with libvirt</a></span></dt><dt><span class="section"><a href="sect-perf-mon.html">25.12. Using PMU to monitor guest performance</a></span></dt><dt><span class="section"><a href="sect-s3-s4.html">25.13. Guest virtual machine power management</a></span></dt><dt><span class="section"><a href="sect-qemu-ga.html">25.14. QEMU Guest Agent Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="sect-qemu-ga.html#sect-guest-synch">25.14.1. guest-sync</a></span></dt><dt><span class="section"><a href="subsect-guest-synch-delimited.html">25.14.2. guest-sync-delimited</a></span></dt></dl></dd><dt><span class="section"><a href="sect-limit-redirection.html">25.15. Setting a limit on device redirection</a></span></dt><dt><span class="section"><a href="sect-dynamic-vNIC.html">25.16. Dynamically changing a host or a network bridge that is attached to a virtual NIC</a
></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Administration_Guide-Storage_Concepts.html">26. Storage concepts</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Concepts.html#sect-Virtualization-Storage_Concepts-Storage_Pools">26.1. Storage pools</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Storage_Concepts-Volumes.html">26.2. Volumes </a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html">27. Storage pools</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating_Storage_Pools">27.1. Creating storage pools </a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Po
ols-Creating-Dedicated_Disk_Devices">27.1.1. Disk-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-File_Systems">27.1.2. Partition-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-Local_Directories">27.1.3. Directory-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-LVM">27.1.4. LVM-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-iSCSI">27.1.5. iSCSI-based storage pools</a></span></dt><dt><span class="section"><a href="chap-Virtualiz
ation_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-NFS">27.1.6. NFS-based storage pools</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="chap-Virtualization_Administration_Guide-Storage_Volumes.html">28. Volumes </a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Storage_Volumes.html#sect-Virtualization-Storage_Volumes-Creating_volumes">28.1. Creating volumes</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Storage_Volumes-Cloning_volumes.html">28.2. Cloning volumes</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html">28.3. Adding storage devices to guests</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html#sect-Virtualization-Adding_storage_devices_to_guests-Adding
_file_based_storage_to_a_guest">28.3.1. Adding file based storage to a guest</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html">28.3.2. Adding hard drives and other block devices to a guest</a></span></dt><dt><span class="section"><a href="sect-Managing_storage_controllers_in_a_guest.html">28.3.3. Managing storage controllers in a guest</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Virtualization-Storage_Volumes-Deleting_volumes.html">28.4. Deleting and removing volumes</a></span></dt></dl></dd><dt><span class="chapter"><a href="vhostmd.html">29. The Virtual Host Metrics Daemon (vhostmd)</a></span></dt><dd><dl><dt><span class="section"><a href="vhostmd.html#idp15936832">29.1. Installing vhostmd on the host</a></span></dt><dt><span class="section"><a href="ch29s02.html">29.2. Configuration of vhostmd</a></span></dt><dt><span class="section"><a hre
f="ch29s03.html">29.3. Starting and stopping the daemon</a></span></dt><dt><span class="section"><a href="ch29s04.html">29.4. Verifying that vhostmd is working from the host</a></span></dt><dt><span class="section"><a href="ch29s05.html">29.5. Configuring guests to see the metrics</a></span></dt><dt><span class="section"><a href="ch29s06.html">29.6. Using vm-dump-metrics in Fedora guests to verify operation</a></span></dt></dl></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="qemu-ga.html"><strong>Prev</strong>Chapter 16. QEMU Guest Agent</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_Administration_Guide-Server_best_practices.html"><strong>Next</strong>Chapter 17. Server best practices</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/pt03.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/pt03.html
new file mode 100644
index 0000000..ee356df
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/pt03.html
@@ -0,0 +1,10 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Part III. Appendicies</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="prev" href="ch29s06.html" title="29.6. Using vm-dump-metrics in Fedora guests to verify operation" /><link rel="next" href="chap-Virtualization_Administration_Guide-Troubleshooting.html" title="Appendix A. Troubleshooting" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="ch29s06.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_Guide-Troubleshooting.html"><strong>Next</strong></a></li></ul><div class="part" id="idm22963552"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part III. Appendicies</h1></div></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl><dt><span class="appendix"><a href="chap-Virtualization_Administration_Guide-Troubleshooting.html">A. Troubleshooting</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Troubleshooting.html#sect-Virtualization-Troubleshooting_-Debugging_and_troubleshooting_">A.1. Debugging and troubleshooting tools</a></span></dt><dt><span class="section"><a href="apas02.html">A.2. kvm_stat</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles.html">A.3. Troublesh
ooting with serial consoles</a></span></dt><dt><span class="section"><a href="apas04.html">A.4. Virtualization log files</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Troubleshooting-Loop_device_errors.html">A.5. Loop device errors</a></span></dt><dt><span class="section"><a href="live-migration-errors.html">A.6. Live Migration Errors</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html">A.7. Enabling Intel VT-x and AMD-V virtualization hardware extensions in BIOS</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Troubleshooting-KVM_networking_performance.html">A.8. KVM networking performance</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard.html">A.9. Missing characters on guest console with Japanese keyboard</a></span></dt><dt><span clas
s="section"><a href="sec-known-issues-windows-xp-guests.html">A.10. Known Windows XP guest issues</a></span></dt></dl></dd><dt><span class="appendix"><a href="apb.html">B. Common <span class="application"><strong>libvirt</strong></span> errors and troubleshooting</a></span></dt><dd><dl><dt><span class="section"><a href="apb.html#App_Libvirt_Daemon">B.1. <span class="application"><strong>libvirtd</strong></span> failed to start</a></span></dt><dt><span class="section"><a href="App_Hypervisor_Connection_Fail.html">B.2. The URI failed to connect to the hypervisor</a></span></dt><dd><dl><dt><span class="section"><a href="App_Hypervisor_Connection_Fail.html#Sect_Cannot_read_CA_certificate">B.2.1. Cannot read CA certificate</a></span></dt><dt><span class="section"><a href="Sect_Failed_to_connect_socket.html">B.2.2. Failed to connect socket ... : Permission denied</a></span></dt><dt><span class="section"><a href="Sect_Other_Connectivity_Errors.html">B.2.3. Other connectivity errors
</a></span></dt></dl></dd><dt><span class="section"><a href="App_Domain_Processor.html">B.3. The guest virtual machine cannot be started: <code class="computeroutput">internal error guest CPU is not compatible with host CPU</code></a></span></dt><dt><span class="section"><a href="App_Domain_Monitor_Socket.html">B.4. Guest starting fails with error: <code class="computeroutput">monitor socket did not show up</code></a></span></dt><dt><span class="section"><a href="App_Domain_Console.html">B.5. <code class="computeroutput">Internal error cannot find character device (null)</code></a></span></dt><dt><span class="section"><a href="App_Domain_Not_Booting.html">B.6. Guest virtual machine booting stalls with error: <code class="computeroutput">No boot device</code></a></span></dt><dt><span class="section"><a href="App_Virt_Net_Not_Starting.html">B.7. Virtual network <em class="replaceable"><code>default</code></em> has not been started</a></span></dt><dt><span class="section"><a hr
ef="App_PXE_Guest_Boot_Fail.html">B.8. PXE boot (or DHCP) on guest failed</a></span></dt><dt><span class="section"><a href="App_Macvtap.html">B.9. Guest can reach outside network, but cannot reach host when using macvtap interface</a></span></dt><dt><span class="section"><a href="App_DHCP_Response_Checksums.html">B.10. Could not add rule to fixup DHCP response checksums on network <em class="replaceable"><code>'default'</code></em></a></span></dt><dt><span class="section"><a href="App_Bridge_Device.html">B.11. Unable to add bridge br0 port vnet0: No such device</a></span></dt><dt><span class="section"><a href="App_Generic_Ethernet.html">B.12. Guest is unable to start with error: <code class="computeroutput">warning: could not open /dev/net/tun</code></a></span></dt><dt><span class="section"><a href="App_Migration_Address.html">B.13. Migration fails with <code class="computeroutput">Error: unable to resolve address</code></a></span></dt><dt><span class="section"><a href="App_
Migration_Disk_Image.html">B.14. Migration fails with <code class="computeroutput">Unable to allow access for disk path: No such file or directory</code></a></span></dt><dt><span class="section"><a href="App_No_Guest_Machines.html">B.15. No guest virtual machines are present when <span class="application"><strong>libvirtd</strong></span> is started</a></span></dt><dt><span class="section"><a href="App_TCP_Ports.html">B.16. Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor</a></span></dt><dt><span class="section"><a href="App_XML_Errors.html">B.17. Common XML errors</a></span></dt><dd><dl><dt><span class="section"><a href="App_XML_Errors.html#idm10882560">B.17.1. Editing domain definition</a></span></dt><dt><span class="section"><a href="apbs17s02.html">B.17.2. XML syntax errors</a></span></dt><dt><span class="section"><a href="apbs17s03.html">B.17.3. Logic and configuration errors</a></span></dt></dl></dd></dl></dd
><dt><span class="appendix"><a href="netkvm-parameters.html">C. NetKVM Driver Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="netkvm-parameters.html#idp424208">C.1. Configurable parameters for NetKVM</a></span></dt></dl></dd><dt><span class="appendix"><a href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html">D. qemu-kvm Whitelist</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-QEMU_KVM_Whitelist.html#idp4706576">D.1. Introduction</a></span></dt><dt><span class="section"><a href="apds02.html">D.2. Basic options</a></span></dt><dt><span class="section"><a href="apds03.html">D.3. Disk options</a></span></dt><dt><span class="section"><a href="apds04.html">D.4. Display options</a></span></dt><dt><span class="section"><a href="apds05.html">D.5. Network options</a></span></dt><dt><span class="section"><a href="apds06.html">D.6. Device options</a></span></dt><dt><span class="section"><a href="ap
ds07.html">D.7. Linux/Multiboot boot </a></span></dt><dt><span class="section"><a href="apds08.html">D.8. Expert options</a></span></dt><dt><span class="section"><a href="apds09.html">D.9. Help and information options</a></span></dt><dt><span class="section"><a href="apds10.html">D.10. Miscellaneous options</a></span></dt></dl></dd><dt><span class="appendix"><a href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html">E. Managing guests with virsh</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html#idp28563584">E.1. virsh command quick reference</a></span></dt><dt><span class="section"><a href="sect-Attaching_and_updating_a_device_with_virsh.html">E.2. Attaching and updating a device with virsh</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor.html">E.3. Connecting to the hypervisor</a></span></dt><dt
><span class="section"><a href="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html">E.4. Creating a virtual machine XML dump (configuration file)</a></span></dt><dd><dl><dt><span class="section"><a href="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html#sect-multifunction-pci-install">E.4.1. Adding multifunction PCI devices to KVM guests</a></span></dt></dl></dd><dt><span class="section"><a href="apes05.html">E.5. Suspending, resuming, saving and restoring a guest</a></span></dt><dt><span class="section"><a href="apes06.html">E.6. Shutting down, rebooting and force-shutdown of a guest</a></span></dt><dt><span class="section"><a href="apes07.html">E.7. Retrieving guest information</a></span></dt><dt><span class="section"><a href="apes08.html">E.8. Retrieving node information</a></span></dt><dt><span class="section"><a href="apes09.html">E.9. Storage pool informatio
n</a></span></dt><dt><span class="section"><a href="apes10.html">E.10. Displaying per-guest information</a></span></dt><dt><span class="section"><a href="apes11.html">E.11. Managing virtual networks</a></span></dt><dt><span class="section"><a href="migrating_guests-with-virsh.html">E.12. Migrating guests with virsh</a></span></dt><dt><span class="section"><a href="sect-man-disk-image.html">E.13. Disk image management with live block copy</a></span></dt><dd><dl><dt><span class="section"><a href="sect-man-disk-image.html#sect-blockcommit">E.13.1. Using blockcommit to shorten a backing chain</a></span></dt><dt><span class="section"><a href="sub-sect-blockpull.html">E.13.2. Using blockpull to shorten a backing chain</a></span></dt><dt><span class="section"><a href="sub-sect-blkresize.html">E.13.3. Using blockresize to change the size of a domain path</a></span></dt></dl></dd><dt><span class="section"><a href="sect-guest-cpu-model-config.html">E.14. Guest CPU model configuration<
/a></span></dt><dd><dl><dt><span class="section"><a href="sect-guest-cpu-model-config.html#sect-guest-cpu-intro">E.14.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-learn-about-host-cpu.html">E.14.2. Learning about the host CPU model</a></span></dt><dt><span class="section"><a href="apes14s03.html">E.14.3. Determining a compatible CPU model to suit a pool of hosts</a></span></dt><dt><span class="section"><a href="apes14s04.html">E.14.4. Configuring the guest CPU model</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html">F. Managing guests with the Virtual Machine Manager (virt-manager)</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html#sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manag
er-Starting_virt_manager">F.1. Starting virt-manager</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html">F.2. The Virtual Machine Manager main window</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_.html">F.3. The virtual hardware details window</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html">F.4. Virtual Machine graphical console</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window.html">F.5. Adding a remote connection</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_gu
ests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html">F.6. Displaying guest details</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html">F.7. Performance monitoring</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html">F.8. Displaying CPU usage for guests</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage.html">F.9. Displaying CPU usage for hosts</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO.html">F.10. Displaying Disk I/O</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Man
ager_virt_manager-Displaying_Network_IO.html">F.11. Displaying Network I/O</a></span></dt></dl></dd><dt><span class="appendix"><a href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html">G. Guest disk access with offline tools</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html#sect-introduction-Virtualization_Administration_Guide-Guest_Disks_libguestfs">G.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-Terminology-Guest_Disks_libguestfs.html">G.2. Terminology</a></span></dt><dt><span class="section"><a href="sect-Guide-Guest_Disks_libguestfs-installation.html">G.3. Installation</a></span></dt><dt><span class="section"><a href="sect-the_guestfish_shell.html">G.4. The guestfish shell</a></span></dt><dd><dl><dt><span class="section"><a href="sect-the_guestfish_shell.html#sect-Viewing_file_systems_with_guestfish">G.4.1. Viewing file systems with guestfish</a></sp
an></dt><dt><span class="section"><a href="sect-Modifying-files-with-guestfish.html">G.4.2. Modifying files with guestfish</a></span></dt><dt><span class="section"><a href="sect-Other-actions-with-guestfish.html">G.4.3. Other actions with guestfish</a></span></dt><dt><span class="section"><a href="sect-Shell-scripting-with-guestfish.html">G.4.4. Shell scripting with guestfish</a></span></dt><dt><span class="section"><a href="sect-Augeas-and-libguestfs-scripting.html">G.4.5. Augeas and libguestfs scripting</a></span></dt></dl></dd><dt><span class="section"><a href="sect-other-commands.html">G.5. Other commands</a></span></dt><dt><span class="section"><a href="sect-virt-rescue.html">G.6. virt-rescue: The rescue shell</a></span></dt><dd><dl><dt><span class="section"><a href="sect-virt-rescue.html#sect-virt-rescue-intro">G.6.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-run-virt-rescue.html">G.6.2. Running virt-rescue</a></span></dt></dl></dd><dt><span c
lass="section"><a href="sect-virt-df.html">G.7. virt-df: Monitoring disk usage</a></span></dt><dd><dl><dt><span class="section"><a href="sect-virt-df.html#sect-virt-df-intro">G.7.1. Introduction</a></span></dt><dt><span class="section"><a href="run-virt-df.html">G.7.2. Running virt-df</a></span></dt></dl></dd><dt><span class="section"><a href="sect-virt-resize.html">G.8. virt-resize: resizing guests offline</a></span></dt><dd><dl><dt><span class="section"><a href="sect-virt-resize.html#sect-virt-resize-intro">G.8.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-expand-disk-image.html">G.8.2. Expanding a disk image</a></span></dt></dl></dd><dt><span class="section"><a href="sect-virt-inspector.html">G.9. virt-inspector: inspecting guests</a></span></dt><dd><dl><dt><span class="section"><a href="sect-virt-inspector.html#sect-virt-inspector-intro">G.9.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-virt-inspector-install.html">G.9.2.
Installation</a></span></dt><dt><span class="section"><a href="sect-virt-inspector-run.html">G.9.3. Running virt-inspector</a></span></dt></dl></dd><dt><span class="section"><a href="sect-virt-win-reg.html">G.10. virt-win-reg: Reading and editing the Windows Registry</a></span></dt><dd><dl><dt><span class="section"><a href="sect-virt-win-reg.html#sect-virt-win-reg-intro">G.10.1. Introduction</a></span></dt><dt><span class="section"><a href="sect-virt-win-reg-install.html">G.10.2. Installation</a></span></dt><dt><span class="section"><a href="sect-virt-win-reg-use.html">G.10.3. Using virt-win-reg</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Using-API-Programming-Languages.html">G.11. Using the API from Programming Languages</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Using-API-Programming-Languages.html#API-and-C">G.11.1. Interaction with the API via a C program</a></span></dt></dl></dd><dt><span class="section"><a href="sect-libguestfs
-troubleshoot.html">G.12. Troubleshooting</a></span></dt><dt><span class="section"><a href="sect-libguestfs-more-docs.html">G.13. Where to find further documentation</a></span></dt></dl></dd><dt><span class="appendix"><a href="chap-Virtualization_Administration_Guide-Virtual_Networking.html">H. Virtual Networking</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Virtualization_Administration_Guide-Virtual_Networking.html#sect-virtual_network-switches-livbvirt">H.1. Virtual network switches</a></span></dt><dt><span class="section"><a href="sect-Network_Address_Translation-libvirt.html">H.2. Network Address Translation</a></span></dt><dt><span class="section"><a href="sect-network-protocols.html">H.3. Networking protocols</a></span></dt><dd><dl><dt><span class="section"><a href="sect-network-protocols.html#sect-DNS_and_DHCP-protocols-libvirt">H.3.1. DNS and DHCP</a></span></dt><dt><span class="section"><a href="sub-sect-routed-mode-libvirt.html">H.3.2. Routed mode
</a></span></dt><dt><span class="section"><a href="sub-sect-iso-mode.html">H.3.3. Isolated mode</a></span></dt></dl></dd><dt><span class="section"><a href="sect-the-Default_Configuration-libvirt.html">H.4. The default configuration</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Virtual_Networking-Example_scenarios.html">H.5. Examples of common scenarios</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Virtualization-Virtual_Networking-Example_scenarios.html#sub-sect-routed-mode">H.5.1. Routed mode</a></span></dt><dt><span class="section"><a href="sub-sect-nat-mode.html">H.5.2. NAT mode</a></span></dt><dt><span class="section"><a href="sub-sect-isolated-mode.html">H.5.3. Isolated mode</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Virtualization-Virtual_Networking-Managing_a_virtual_network.html">H.6. Managing a virtual network</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Virtual_Networking-Creati
ng_a_virtual_network.html">H.7. Creating a virtual network</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest.html">H.8. Attaching a virtual network to a guest</a></span></dt><dt><span class="section"><a href="sect-attch-nic-physdev.html">H.9. Directly attaching to physical interface</a></span></dt><dt><span class="section"><a href="sect-applying-network-filtering.html">H.10. Applying network filtering</a></span></dt><dd><dl><dt><span class="section"><a href="sect-applying-network-filtering.html#intro-sub-sect-applying-network-filtering">H.10.1. Introduction</a></span></dt><dt><span class="section"><a href="sub-sect-filt-chain.html">H.10.2. Filtering chains</a></span></dt><dt><span class="section"><a href="sub-sect-filt-chain-props.html">H.10.3. Filtering chain priorities</a></span></dt><dt><span class="section"><a href="sub-sect-vars-in-filters.html">H.10.4. Usage of variables in filters</a></span></dt
><dt><span class="section"><a href="sub-sect-auto-IP-add-detect-dhcp-snoop.html">H.10.5. Automatic IP address detection and DHCP snooping</a></span></dt><dt><span class="section"><a href="sub-sect-vars-reserved.html">H.10.6. Reserved Variables</a></span></dt><dt><span class="section"><a href="sub-sect-element-oview.html">H.10.7. Element and attribute overview</a></span></dt><dt><span class="section"><a href="sub-sect-ref-filter.html">H.10.8. References to other filters</a></span></dt><dt><span class="section"><a href="sub-sect-filter-rules.html">H.10.9. Filter rules</a></span></dt><dt><span class="section"><a href="sub-sect-supp-pros.html">H.10.10. Supported protocols</a></span></dt><dt><span class="section"><a href="sub-sect-adv-filt-topics.html">H.10.11. Advanced Filter Configuration Topics</a></span></dt><dt><span class="section"><a href="sub-sect-limitations-filters-network-subsystem.html">H.10.12. Limitations</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"
><a href="appe-Virtualization-Additional_resources.html">I. Additional resources</a></span></dt><dd><dl><dt><span class="section"><a href="appe-Virtualization-Additional_resources.html#sect-Virtualization-Additional_resources-Online_resources">I.1. Online resources</a></span></dt><dt><span class="section"><a href="sect-Virtualization-Additional_resources-Installed_documentation.html">I.2. Installed documentation</a></span></dt></dl></dd><dt><span class="appendix"><a href="ch-lib-dom-xml.html">J. Manipulating the domain xml</a></span></dt><dd><dl><dt><span class="section"><a href="ch-lib-dom-xml.html#sect-gen-metadata">J.1. General information and metadata</a></span></dt><dt><span class="section"><a href="sect-dom-xml-op-sys-boot.html">J.2. Operating system booting</a></span></dt><dd><dl><dt><span class="section"><a href="sect-dom-xml-op-sys-boot.html#sub-sect-op-sys-boot-bios-boot">J.2.1. BIOS bootloader</a></span></dt><dt><span class="section"><a href="sub-sect-op-sys-host-
boot.html">J.2.2. Host bootloader</a></span></dt><dt><span class="section"><a href="sub-sect-op-sys-dir-kern-boot.html">J.2.3. Direct kernel boot</a></span></dt><dt><span class="section"><a href="sub-sect-op-sys-cont-boot.html">J.2.4. Container boot</a></span></dt></dl></dd><dt><span class="section"><a href="sect-smbios-sys-info.html">J.3. SMBIOS system information</a></span></dt><dt><span class="section"><a href="sect-cpu-allocation.html">J.4. CPU allocation</a></span></dt><dt><span class="section"><a href="sect-cpu-tuning.html">J.5. CPU tuning</a></span></dt><dt><span class="section"><a href="sect-mem-back.html">J.6. Memory backing</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-mem-tuning.html">J.7. Memory tuning</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-numa-node-tuning.html">J.8. NUMA node tuning</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-blk-io-tuning.html">J.9. Block I/O tuning</a></span><
/dt><dt><span class="section"><a href="sect-libvirt-dom-xml-res-part.html">J.10. Resource partitioning</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-cpu-model-top.html">J.11. CPU model and topology</a></span></dt><dd><dl><dt><span class="section"><a href="sect-libvirt-dom-xml-cpu-model-top.html#sub-sect-libvirt-dom-xml-res-part-guest-numa">J.11.1. Guest NUMA topology</a></span></dt></dl></dd><dt><span class="section"><a href="sect-libvirt-dom-xml-event-config.html">J.12. Events configuration</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-pwr-man.html">J.13. Power Management</a></span></dt><dt><span class="section"><a href="apjs14.html">J.14. Hypervisor features</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-time-keep.html">J.15. Time keeping</a></span></dt><dt><span class="section"><a href="sect-libvirt-dom-xml-devices.html">J.16. Devices</a></span></dt><dd><dl><dt><span class="section"><a href="sect-li
bvirt-dom-xml-devices.html#sub-sect-libvirt-dom-xml-devices">J.16.1. Hard drives, floppy disks, CDROMs</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-filesystems.html">J.16.2. Filesystems</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-device-addresses.html">J.16.3. Device addresses</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-controllers.html">J.16.4. Controllers</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-device-leases.html">J.16.5. Device leases</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-host-device-assignment.html">J.16.6. Host device assignment</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-redirected-devices.html">J.16.7. Redirected devices</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-smartc
ard.html">J.16.8. Smartcard devices</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html">J.16.9. Network interfaces</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-input-devices.html">J.16.10. Input devices</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-hub-devices.html">J.16.11. Hub devices</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-graphical-framebuffers.html">J.16.12. Graphical framebuffers</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-video.html">J.16.13. Video devices</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-consoles.html">J.16.14. Consoles, serial, parallel, and channel devices</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-guest-interface.html">J.16.15. Guest interfaces</
a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-channel.html">J.16.16. Channel</a></span></dt><dt><span class="section"><a href="sub-section-libvirt-dom-xml-devices-host-interface.html">J.16.17. Host interface</a></span></dt></dl></dd><dt><span class="section"><a href="section-libvirt-dom-xml-sound-devices.html">J.17. Sound devices</a></span></dt><dt><span class="section"><a href="section-libvirt-dom-xml-watchdog.html">J.18. Watchdog device</a></span></dt><dt><span class="section"><a href="section-libvirt-dom-xml-memory-baloon-device.html">J.19. Memory balloon device</a></span></dt><dt><span class="section"><a href="section-libvirt-dom-xml-random-number-gen.html">J.20. Random number generator device</a></span></dt><dt><span class="section"><a href="section-libvirt-dom-xml-tpm-device.html">J.21. TPM devices</a></span></dt><dt><span class="section"><a href="section-libvirt-dom-xml-security-label.html">J.22. Security label</a></span></dt><dt
><span class="section"><a href="section-libvirt-dom-xml-example.html">J.23. Example domain XML configuration</a></span></dt></dl></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch29s06.html"><strong>Prev</strong>29.6. Using vm-dump-metrics in Fedora guests to v...</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_Administration_Guide-Troubleshooting.html"><strong>Next</strong>Appendix A. Troubleshooting</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/qemu-ga.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/qemu-ga.html
new file mode 100644
index 0000000..59370a6
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/qemu-ga.html
@@ -0,0 +1,30 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 16. QEMU Guest Agent</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="ch15s02s02.html" title="15.2.2. Using a private libvirt network" /><link rel="next" href="pt02.html" title="Part II. Administration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="ch15s02s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href
="pt02.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="qemu-ga" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 16. QEMU Guest Agent</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="qemu-ga.html#idm5352160">16.1. Set Up Communication between Guest Agent and Host</a></span></dt></dl></div><div class="para">
+ The QEMU Guest Agent allows the host machine to issue commands to the guest operating system. The guest operating system then responds to those commands asynchronously.
+ </div><div class="para">
+ This section covers the options and commands available to the guest agent in detail. It also covers how to run the guest agent in the foreground, or as a daemon in the background.
+ </div><div class="section" id="idm5352160"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm5352160">16.1. Set Up Communication between Guest Agent and Host</h2></div></div></div><div class="para">
+ The host machine communicates with the guest agent through a VirtIO serial connection between the host and guest machines. A VirtIO serial channel is connected to the host via a character device driver (typically a Unix socket), and the guest listens on this serial channel. The following procedure shows how to set up the host and guest machines for guest agent use.
+ </div><div class="procedure"><h6>Procedure 16.1. Set Up Host-Agent Communication</h6><ol class="1"><li class="step"><p class="title"><strong>Launch QEMU with a character device driver</strong></p><div class="para">
+ Launch QEMU as usual, with additional definitions for the character device driver required to communicate with the guest agent.
+ </div><div class="para">
+ The following example launches QEMU to communicate over the Unix socket <code class="filename">/tmp/qga.sock</code>.
+ </div><pre class="screen">/usr/libexec/qemu-kvm [...] -chardev socket,path=/tmp/qga.sock,server,nowait,id=qga0 \
+ -device virtio-serial \
+ -device virtserialport,chardev=qga0,name=org.qemu.guest_agent.0</pre></li><li class="step"><p class="title"><strong>Start the Guest Agent</strong></p><div class="para">
+ On the guest, run the following command to start the Guest Agent:
+ </div><pre class="screen">qemu-ga --path <em class="replaceable"><code>device_path</code></em> --method <em class="replaceable"><code>method</code></em></pre><div class="para">
+ The guest agent now parses incoming QMP messages for commands, and acts upon them if valid.
+ </div><div class="para">
+ If no other method or path is specified with the <code class="option">--method</code> or <code class="option">--path</code> options respectively, the Guest Agent listens over <code class="literal">virtio-serial</code>, through the <code class="filename">/dev/virtio-ports/org.qemu.guest_agent.0</code> device path.
+ </div></li></ol></div><div class="para">
+ You can now communicate with the guest by sending valid QMP commands over the established character device driver.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch15s02s02.html"><strong>Prev</strong>15.2.2. Using a private libvirt 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="pt02.html"><strong>Next</strong>Part II. Administration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/run-virt-df.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/run-virt-df.html
new file mode 100644
index 0000000..7b60915
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/run-virt-df.html
@@ -0,0 +1,44 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.7.2. Running virt-df</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-virt-df.html" title="G.7. virt-df: Monitoring disk usage" /><link rel="prev" href="sect-virt-df.html" title="G.7. virt-df: Monitoring disk usage" /><link rel="next" href="sect-virt-resize.html" title="G.8. virt-resize: resizing guests offline" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-virt-df.html"><strong>Prev</s
trong></a></li><li class="next"><a accesskey="n" href="sect-virt-resize.html"><strong>Next</strong></a></li></ul><div class="section" id="run-virt-df"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.7.2. Running virt-df</h3></div></div></div><div class="para">
+ To display file system usage for all file systems found in a disk image, enter the following:
+ </div><pre class="screen">
+# virt-df /dev/vg_guests/RHEL6
+ Filesystem 1K-blocks Used Available Use%
+ RHEL6:/dev/sda1 101086 10233 85634 11%
+ RHEL6:/dev/VolGroup00/LogVol00 7127864 2272744 4493036 32%
+</pre><div class="para">
+ (Where <code class="filename">/dev/vg_guests/RHEL6</code> is a Red Hat Enterprise Linux 4 guest disk image. The path in this case is the host logical volume where this disk image is located.)
+ </div><div class="para">
+ You can also use <code class="command">virt-df</code> on its own to list information about all of your guests (ie. those known to libvirt). The <code class="command">virt-df</code> command recognizes some of the same options as the standard <code class="command">df</code> such as <code class="command">-h</code> (human-readable) and <code class="command">-i</code> (show inodes instead of blocks).
+ </div><div class="para">
+ <code class="command">virt-df</code> also works on Windows guests:
+ </div><pre class="screen">
+# virt-df -h
+ Filesystem Size Used Available Use%
+ F14x64:/dev/sda1 484.2M 66.3M 392.9M 14%
+ F14x64:/dev/vg_f14x64/lv_root 7.4G 3.0G 4.4G 41%
+ RHEL6brewx64:/dev/sda1 484.2M 52.6M 406.6M 11%
+ RHEL6brewx64:/dev/vg_rhel6brewx64/lv_root
+ 13.3G 3.4G 9.2G 26%
+ Win7x32:/dev/sda1 100.0M 24.1M 75.9M 25%
+ Win7x32:/dev/sda2 19.9G 7.4G 12.5G 38%
+</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ You can use <code class="command">virt-df</code> safely on live guests, since it only needs read-only access. However, you should not expect the numbers to be precisely the same as those from a <code class="command">df</code> command running inside the guest. This is because what is on disk will be slightly out of synch with the state of the live guest. Nevertheless it should be a good enough approximation for analysis and monitoring purposes.
+ </div></div></div><div class="para">
+ virt-df is designed to allow you to integrate the statistics into monitoring tools, databases and so on. This allows system administrators to generate reports on trends in disk usage, and alerts if a guest is about to run out of disk space. To do this you should use the <code class="command">--csv</code> option to generate machine-readable Comma-Separated-Values (CSV) output. CSV output is readable by most databases, spreadsheet software and a variety of other tools and programming languages. The raw CSV looks like the following:
+ </div><pre class="screen">
+# virt-df --csv WindowsGuest
+ Virtual Machine,Filesystem,1K-blocks,Used,Available,Use%
+ Win7x32,/dev/sda1,102396,24712,77684,24.1%
+ Win7x32,/dev/sda2,20866940,7786652,13080288,37.3%
+</pre><div class="para">
+ For resources and ideas on how to process this output to produce trends and alerts, refer to the following URL: <a href=" http://virt-tools.org/learning/advanced-virt-df/"> http://virt-tools.org/learning/advanced-virt-df/</a>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-virt-df.html"><strong>Prev</strong>G.7. virt-df: Monitoring disk 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-virt-resize.html"><strong>Next</strong>G.8. virt-resize: resizing guests offline</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sec-known-issues-windows-xp-guests.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sec-known-issues-windows-xp-guests.html
new file mode 100644
index 0000000..906bac6
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sec-known-issues-windows-xp-guests.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.10. Known Windows XP guest issues</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Troubleshooting.html" title="Appendix A. Troubleshooting" /><link rel="prev" href="sect-Virtualization-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard.html" title="A.9. Missing characters on guest console with Japanese keyboard" /><link rel="next" href="apb.html" title="Appendix B. Common libvirt errors and troubleshooting" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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_righ
t.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apb.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-known-issues-windows-xp-guests"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.10. Known Windows XP guest issues</h2></div></div></div><div class="para">
+ If you perform device-add quickly followed by device-del using a Windows XP guest, the guest does not eject the device and instead it displays the following error: "The device (device name) cannot be stopped because of an unknown error. Since the device is still being used, do not remove it". It should be noted that newer Windows OS version guests as well as all known Linux guests do not experience this problem. To prevent this issue from happening, wait to delete a device that you just added.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard.html"><strong>Prev</strong>A.9. Missing characters on guest console with Jap...</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="apb.html"><strong>Next</strong>Appendix B. Common libvirt errors and troubleshoo...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Attaching_and_updating_a_device_with_virsh.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Attaching_and_updating_a_device_with_virsh.html
new file mode 100644
index 0000000..54f4a4a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Attaching_and_updating_a_device_with_virsh.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.2. Attaching and updating a device with virsh</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="prev" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="next" href="sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor.html" title="E.3. Connecting to the hypervisor" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Attaching_and_updating_a_device_with_virsh"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">E.2. Attaching and updating a device with virsh</h2></div></div></div><div class="para">
+ For information on this procedure refer to <a class="xref" href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html#sect-Virtualization-Adding_storage_devices_to_guests-Adding_file_based_storage_to_a_guest">Section 28.3.1, “Adding file based storage to a guest”</a>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html"><strong>Prev</strong>Appendix E. 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-Managing_guests_with_virsh-Connecting_to_the_hypervisor.html"><strong>Next</strong>E.3. Connecting to the hypervisor</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Augeas-and-libguestfs-scripting.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Augeas-and-libguestfs-scripting.html
new file mode 100644
index 0000000..4f9ec80
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Augeas-and-libguestfs-scripting.html
@@ -0,0 +1,53 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.4.5. Augeas and libguestfs scripting</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-the_guestfish_shell.html" title="G.4. The guestfish shell" /><link rel="prev" href="sect-Shell-scripting-with-guestfish.html" title="G.4.4. Shell scripting with guestfish" /><link rel="next" href="sect-other-commands.html" title="G.5. Other commands" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-Shell-scripting-with-g
uestfish.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-other-commands.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Augeas-and-libguestfs-scripting"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.4.5. Augeas and libguestfs scripting</h3></div></div></div><div class="para">
+ Combining libguestfs with Augeas can help when writing scripts to manipulate Linux guest configuration. For example, the following script uses Augeas to parse the keyboard configuration of a guest, and to print out the layout. Note that this example only works with guests running Red Hat Enterprise Linux:
+ </div><pre class="screen">
+#!/bin/bash -
+ set -e
+ guestname="$1"
+
+ guestfish -d "$1" -i --ro <<'EOF'
+ aug-init / 0
+ aug-get /files/etc/sysconfig/keyboard/LAYOUT
+ EOF
+</pre><div class="para">
+ Augeas can also be used to modify configuration files. You can modify the above script to <span class="bold bold"><strong>change</strong></span> the keyboard layout:
+ </div><pre class="screen">
+#!/bin/bash -
+ set -e
+ guestname="$1"
+
+ guestfish -d "$1" -i <<'EOF'
+ aug-init / 0
+ aug-set /files/etc/sysconfig/keyboard/LAYOUT '"gb"'
+ aug-save
+ EOF
+</pre><div class="para">
+ Note the three changes between the two scripts:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ The <code class="command">--ro</code> option has been removed in the second example, giving the ability to write to the guest.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="command">aug-get</code> command has been changed to <code class="command">aug-set</code> to modify the value instead of fetching it. The new value will be <code class="command">"gb"</code> (including the quotes).
+ </div></li><li class="listitem"><div class="para">
+ The <code class="command">aug-save</code> command is used here so Augeas will write the changes out to disk.
+ </div></li></ol></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ More information about Augeas can be found on the website <a href="http://augeas.net">http://augeas.net</a>.
+ </div></div></div><div class="para">
+ guestfish can do much more than we can cover in this introductory document. For example, creating disk images from scratch:
+ </div><pre class="screen">
+guestfish -N fs
+</pre><div class="para">
+ Or copying out whole directories from a disk image:
+ </div><pre class="screen">
+><fs> copy-out /home /tmp/home
+</pre><div class="para">
+ For more information see the man page guestfish(1).
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Shell-scripting-with-guestfish.html"><strong>Prev</strong>G.4.4. Shell scripting with guestfish</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-other-commands.html"><strong>Next</strong>G.5. Other commands</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Guide-Guest_Disks_libguestfs-installation.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Guide-Guest_Disks_libguestfs-installation.html
new file mode 100644
index 0000000..b422199
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Guide-Guest_Disks_libguestfs-installation.html
@@ -0,0 +1,18 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.3. Installation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /><link rel="prev" href="sect-Terminology-Guest_Disks_libguestfs.html" title="G.2. Terminology" /><link rel="next" href="sect-the_guestfish_shell.html" title="G.4. The guestfish shell" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="pre
vious"><a accesskey="p" href="sect-Terminology-Guest_Disks_libguestfs.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-the_guestfish_shell.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Guide-Guest_Disks_libguestfs-installation"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">G.3. Installation</h2></div></div></div><div class="para">
+ To install libguestfs, guestfish, the libguestfs tools, guestmount and support for Windows guests, subscribe to the RHEL V2WIN channel, go to the <a href="https://rhn.redhat.com/rhn/software/packages/details/Overview.do?pid=631818">Fedora Website</a> and run the following command:
+ </div><pre class="screen">
+# yum install libguestfs guestfish libguestfs-tools libguestfs-mount libguestfs-winsupport
+</pre><div class="para">
+ To install every libguestfs-related package including the language bindings, run the following command:
+ </div><pre class="screen">
+# yum install '*guestf*'
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Terminology-Guest_Disks_libguestfs.html"><strong>Prev</strong>G.2. Terminology</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-the_guestfish_shell.html"><strong>Next</strong>G.4. The guestfish shell</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Managing_storage_controllers_in_a_guest.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Managing_storage_controllers_in_a_guest.html
new file mode 100644
index 0000000..7c9f39e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Managing_storage_controllers_in_a_guest.html
@@ -0,0 +1,42 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>28.3.3. Managing storage controllers in a guest</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html" title="28.3. Adding storage devices to guests" /><link rel="prev" href="sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html" title="28.3.2. Adding hard drives and other block devices to a guest" /><link rel="next" href="sect-Virtualization-Storage_Volumes-Deleting_volumes.html" title="28.4. Deleting and removing volumes" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Storage_Volumes-Deleting_volumes.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Managing_storage_controllers_in_a_guest"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">28.3.3. Managing storage controllers in a guest</h3></div></div></div><div class="para">
+ Starting from Red Hat Enterprise Linux 6.3, SCSI devices are also supported inside guests.
+ </div><div class="para">
+ Unlike virtio disks, SCSI devices require the presence of a controller in the guest.
+ </div><div class="para">
+ This section details the necessary steps to create a virtual SCSI controller (also known as "Host Bus Adapter", or HBA), and to add SCSI storage to the guest.
+ </div><div class="procedure" id="proc-Creating_a_virtual_SCSI_controller"><h6>Procedure 28.3. Creating a virtual SCSI controller</h6><ol class="1"><li class="step"><div class="para">
+ Display the configuration of the guest (<code class="literal">Guest1</code>) and look for a pre-existing SCSI controller:
+ </div><pre class="screen">
+# virsh dumpxml Guest1 | grep controller.*scsi
+</pre><div class="para">
+ If a controller is present, the command will output one or more lines similar to the following:
+ </div><pre class="screen">
+<controller type='scsi' model='virtio-scsi' index='0'/>
+</pre></li><li class="step"><div class="para">
+ If the previous step did not show a controller, create the description for one in a new file and add it to the virtual machine, using the following steps:
+ </div><ol class="a"><li class="step"><div class="para">
+ Create the controller by writing a <code class="literal"><controller></code> element in a new file and save this file with an XML extension. <code class="filename">NewHBA.xml</code>, for example.
+ </div><pre class="screen">
+<controller type='scsi' model='virtio-scsi'/>
+</pre></li><li class="step"><div class="para">
+ Associate the device in the <code class="filename">NewHBA.xml</code> you just created with your guest:
+ </div><pre class="screen">
+# virsh attach-device --config Guest1 ~/NewHBA.xml
+</pre><div class="para">
+ In this example the <code class="literal">--config</code> option behaves the same as it does for disks. Refer to <a class="xref" href="sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html#proc-Virtualization-Adding_storage_devices_to_guests-Adding_physical_block_devices_to_virtualized_guests">Procedure 28.2, “Adding physical block devices to guests”</a> for more information.
+ </div></li></ol></li><li class="step"><div class="para">
+ Add a new SCSI disk or CD-ROM. The new disk can be added using the methods in sections <a class="xref" href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html#sect-Virtualization-Adding_storage_devices_to_guests-Adding_file_based_storage_to_a_guest">Section 28.3.1, “Adding file based storage to a guest”</a> and <a class="xref" href="sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html">Section 28.3.2, “Adding hard drives and other block devices to a guest”</a>. In order to create a SCSI disk, specify a target device name that starts with <em class="replaceable"><code>sd</code></em>.
+ </div><pre class="screen">
+# virsh attach-disk Guest1 /var/lib/libvirt/images/FileName.iso sdb --cache none
+</pre><div class="para">
+ Depending on the version of the driver in the guest, the new disk may not be detected immediately by a running guest. Follow the steps in the <em class="citetitle">Red Hat Enterprise Linux Storage Administration Guide</em>.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html"><strong>Prev</strong>28.3.2. Adding hard drives and other block device...</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-Storage_Volumes-Deleting_volumes.html"><strong>Next</strong>28.4. Deleting and removing volumes</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Modifying-files-with-guestfish.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Modifying-files-with-guestfish.html
new file mode 100644
index 0000000..8d233da
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Modifying-files-with-guestfish.html
@@ -0,0 +1,29 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.4.2. Modifying files with guestfish</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-the_guestfish_shell.html" title="G.4. The guestfish shell" /><link rel="prev" href="sect-the_guestfish_shell.html" title="G.4. The guestfish shell" /><link rel="next" href="sect-Other-actions-with-guestfish.html" title="G.4.3. Other actions with guestfish" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-the_guestfish_sh
ell.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Other-actions-with-guestfish.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Modifying-files-with-guestfish"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.4.2. Modifying files with guestfish</h3></div></div></div><div class="para">
+ To modify files, create directories or make other changes to a guest, first heed the warning at the beginning of this section: <span class="bol bol">your guest must be shut down</span>. Editing or changing a running disk with guestfish <span class="bold bold"><strong>will</strong></span> result in disk corruption. This section gives an example of editing the <code class="filename">/boot/grub/grub.conf</code> file. When you are sure the guest is shut down you can omit the <code class="command">--ro</code> flag in order to get write access via a command such as:
+ </div><pre class="screen">
+guestfish -d RHEL3 -i
+
+Welcome to guestfish, the libguestfs filesystem interactive shell for
+ editing virtual machine filesystems.
+
+ Type: 'help' for help on commands
+ 'man' to read the manual
+ 'quit' to quit the shell
+
+ Operating system: Red Hat Enterprise Linux AS release 3 (Taroon Update 9)
+ /dev/vda2 mounted on /
+ /dev/vda1 mounted on /boot
+
+><fs> edit /boot/grub/grub.conf
+</pre><div class="para">
+ Commands to edit files include <code class="command">edit</code>, <code class="command">vi</code> and <code class="command">emacs</code>. Many commands also exist for creating files and directories, such as <code class="command">write</code>, <code class="command">mkdir</code>, <code class="command">upload</code> and <code class="command">tar-in</code>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-the_guestfish_shell.html"><strong>Prev</strong>G.4. The guestfish shell</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-Other-actions-with-guestfish.html"><strong>Next</strong>G.4.3. Other actions with guestfish</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Network_Address_Translation-libvirt.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Network_Address_Translation-libvirt.html
new file mode 100644
index 0000000..5c944b8
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Network_Address_Translation-libvirt.html
@@ -0,0 +1,14 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.2. Network Address Translation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html" title="Appendix H. Virtual Networking" /><link rel="prev" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html" title="Appendix H. Virtual Networking" /><link rel="next" href="sect-network-protocols.html" title="H.3. Networking protocols" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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"><l
i class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-network-protocols.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Network_Address_Translation-libvirt"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">H.2. Network Address Translation</h2></div></div></div><div class="para">
+ By default, virtual network switches operate in NAT mode. They use IP masquerading rather than SNAT (Source-NAT) or DNAT (Destination-NAT). IP masquerading enables connected guests to use the host IP address for communication to any external network. By default, computers that are placed externally to the host cannot communicate to the guests inside when the virtual network switch is operating in NAT mode, as shown in the following diagram:
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-Network_Address_Translation-Switch_in_NAT_mode_with_two_guests"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-04-hostwithnatswitch.png" width="444" alt="Virtual network switch using NAT with two guests" /></div></div><h6>Figure H.3. Virtual network switch using NAT with two guests</h6></div><br class="figure-break" /><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Virtual network switches use NAT configured by iptables rules. Editing these rules while the switch is running is not recommended, as incorrect rules may result in the switch being unable to communicate.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html"><strong>Prev</strong>Appendix H. Virtual 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="sect-network-protocols.html"><strong>Next</strong>H.3. Networking protocols</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Other-actions-with-guestfish.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Other-actions-with-guestfish.html
new file mode 100644
index 0000000..7b180a7
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Other-actions-with-guestfish.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.4.3. Other actions with guestfish</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-the_guestfish_shell.html" title="G.4. The guestfish shell" /><link rel="prev" href="sect-Modifying-files-with-guestfish.html" title="G.4.2. Modifying files with guestfish" /><link rel="next" href="sect-Shell-scripting-with-guestfish.html" title="G.4.4. Shell scripting with guestfish" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-Modifying-files-with-guestfish.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Shell-scripting-with-guestfish.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Other-actions-with-guestfish"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.4.3. Other actions with guestfish</h3></div></div></div><div class="para">
+ You can also format file systems, create partitions, create and resize LVM logical volumes and much more, with commands such as <code class="command">mkfs</code>, <code class="command">part-add</code>, <code class="command">lvresize</code>, <code class="command">lvcreate</code>, <code class="command">vgcreate</code> and <code class="command">pvcreate</code>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Modifying-files-with-guestfish.html"><strong>Prev</strong>G.4.2. Modifying files with guestfish</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-Shell-scripting-with-guestfish.html"><strong>Next</strong>G.4.4. Shell scripting with guestfish</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-RedHat-We_Need_Feedback.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-RedHat-We_Need_Feedback.html
new file mode 100644
index 0000000..9d49e18
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-RedHat-We_Need_Feedback.html
@@ -0,0 +1,16 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2. We Need Feedback!</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect_RedHat-Getting_Help_and_Giving_Feedback.html" title="2. Getting Help and Giving Feedback" /><link rel="prev" href="sect_RedHat-Getting_Help_and_Giving_Feedback.html" title="2. Getting Help and Giving Feedback" /><link rel="next" href="pt01.html" title="Part I. Deployment" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect_RedHat-Gettin
g_Help_and_Giving_Feedback.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="pt01.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-RedHat-We_Need_Feedback"><div class="titlepage"><div><div><h3 class="title">2.2. We Need Feedback!</h3></div></div></div><a id="idp19149408" class="indexterm"></a><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/">http://bugzilla.redhat.com/</a> against the product <span class="application"><strong>Documentation.</strong></span>
+ </div><div class="para">
+ When submitting a bug report, be sure to mention the manual's identifier: <em class="citetitle">doc-Virtualization_Deployment_and_Administration_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="sect_RedHat-Getting_Help_and_Giving_Feedback.html"><strong>Prev</strong>2. Getting Help and Giving 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="pt01.html"><strong>Next</strong>Part I. Deployment</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Shell-scripting-with-guestfish.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Shell-scripting-with-guestfish.html
new file mode 100644
index 0000000..8c5131d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Shell-scripting-with-guestfish.html
@@ -0,0 +1,21 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.4.4. Shell scripting with guestfish</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-the_guestfish_shell.html" title="G.4. The guestfish shell" /><link rel="prev" href="sect-Other-actions-with-guestfish.html" title="G.4.3. Other actions with guestfish" /><link rel="next" href="sect-Augeas-and-libguestfs-scripting.html" title="G.4.5. Augeas and libguestfs scripting" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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" h
ref="sect-Other-actions-with-guestfish.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Augeas-and-libguestfs-scripting.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Shell-scripting-with-guestfish"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.4.4. Shell scripting with guestfish</h3></div></div></div><div class="para">
+ Once you are familiar with using guestfish interactively, according to your needs, writing shell scripts with it may be useful. The following is a simple shell script to add a new MOTD (message of the day) to a guest:
+ </div><pre class="screen">
+#!/bin/bash -
+ set -e
+ guestname="$1"
+
+ guestfish -d "$guestname" -i <<'EOF'
+ write /etc/motd "Welcome to Acme Incorporated."
+ chmod 0644 /etc/motd
+ EOF
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Other-actions-with-guestfish.html"><strong>Prev</strong>G.4.3. Other actions with guestfish</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-Augeas-and-libguestfs-scripting.html"><strong>Next</strong>G.4.5. Augeas and libguestfs scripting</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Terminology-Guest_Disks_libguestfs.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Terminology-Guest_Disks_libguestfs.html
new file mode 100644
index 0000000..6830d73
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Terminology-Guest_Disks_libguestfs.html
@@ -0,0 +1,22 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.2. Terminology</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /><link rel="prev" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /><link rel="next" href="sect-Guide-Guest_Disks_libguestfs-installation.html" title="G.3. Installation" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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.p
ng" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Guide-Guest_Disks_libguestfs-installation.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Terminology-Guest_Disks_libguestfs"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">G.2. Terminology</h2></div></div></div><div class="para">
+ This section explains the terms used throughout this chapter.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>libguestfs (GUEST FileSystem LIBrary)</strong></span> - the underlying C library that provides the basic functionality for opening disk images, reading and writing files and so on. You can write C programs directly to this API, but it is quite low level.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>guestfish (GUEST Filesystem Interactive SHell)</strong></span> is an interactive shell that you can use from the command line or from shell scripts. It exposes all of the functionality of the libguestfs API.
+ </div></li><li class="listitem"><div class="para">
+ Various virt tools are built on top of libguestfs, and these provide a way to perform specific single tasks from the command line. Tools include <span class="bold bold"><strong>virt-df</strong></span>, <span class="bold bold"><strong>virt-rescue</strong></span>, <span class="bold bold"><strong>virt-resize</strong></span> and <span class="bold bold"><strong>virt-edit</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>hivex</strong></span> and <span class="bold bold"><strong>Augeas</strong></span> are libraries for editing the Windows Registry and Linux configuration files respectively. Although these are separate from libguestfs, much of the value of libguestfs comes from the combination of these tools.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>guestmount</strong></span> is an interface between libguestfs and FUSE. It is primarily used to mount file systems from disk images on your host. This functionality is not necessary, but can be useful.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html"><strong>Prev</strong>Appendix G. Guest disk access with offline 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="sect-Guide-Guest_Disks_libguestfs-installation.html"><strong>Next</strong>G.3. Installation</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Using-API-Programming-Languages.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Using-API-Programming-Languages.html
new file mode 100644
index 0000000..ea07cbc
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Using-API-Programming-Languages.html
@@ -0,0 +1,243 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.11. Using the API from Programming Languages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /><link rel="prev" href="sect-virt-win-reg-use.html" title="G.10.3. Using virt-win-reg" /><link rel="next" href="sect-libguestfs-troubleshoot.html" title="G.12. Troubleshooting" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-virt-win-reg-use.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-libguestfs-troubleshoot.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Using-API-Programming-Languages"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">G.11. Using the API from Programming Languages</h2></div></div></div><div class="para">
+ The libguestfs API can be used directly from the following languages in Fedora 19: C, C++, Perl, Python, Java, Ruby and OCaml.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ To install C and C++ bindings, enter the following command:
+ </div><pre class="screen">
+# yum install libguestfs-devel
+</pre></li><li class="listitem"><div class="para">
+ To install Perl bindings:
+ </div><pre class="screen">
+# yum install 'perl(Sys::Guestfs)'
+</pre></li><li class="listitem"><div class="para">
+ To install Python bindings:
+ </div><pre class="screen">
+# yum install python-libguestfs
+</pre></li><li class="listitem"><div class="para">
+ To install Java bindings:
+ </div><pre class="screen">
+# yum install libguestfs-java libguestfs-java-devel libguestfs-javadoc
+</pre></li><li class="listitem"><div class="para">
+ To install Ruby bindings:
+ </div><pre class="screen">
+# yum install ruby-libguestfs
+</pre></li><li class="listitem"><div class="para">
+ To install OCaml bindings:
+ </div><pre class="screen">
+# yum install ocaml-libguestfs ocaml-libguestfs-devel
+</pre></li></ul></div><div class="para">
+ The binding for each language is essentially the same, but with minor syntactic changes. A C statement:
+ </div><pre class="screen">
+guestfs_launch (g);
+</pre><div class="para">
+ Would appear like the following in Perl:
+ </div><pre class="screen">
+$g->launch ()
+</pre><div class="para">
+ Or like the following in OCaml:
+ </div><pre class="screen">
+g#launch ()
+</pre><div class="para">
+ Only the API from C is detailed in this section.
+ </div><div class="para">
+ In the C and C++ bindings, you must manually check for errors. In the other bindings, errors are converted into exceptions; the additional error checks shown in the examples below are not necessary for other languages, but conversely you may wish to add code to catch exceptions. Refer to the following list for some points of interest regarding the architecture of the libguestfs API:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The libguestfs API is synchronous. Each call blocks until it has completed. If you want to make calls asynchronously, you have to create a thread.
+ </div></li><li class="listitem"><div class="para">
+ The libguestfs API is not thread safe: each handle should be used only from a single thread, or if you want to share a handle between threads you should implement your own mutex to ensure that two threads cannot execute commands on one handle at the same time.
+ </div></li><li class="listitem"><div class="para">
+ You should not open multiple handles on the same disk image. It is permissible if all the handles are read-only, but still not recommended.
+ </div></li><li class="listitem"><div class="para">
+ You should not add a disk image for writing if anything else could be using that disk image (eg. a live VM). Doing this will cause disk corruption.
+ </div></li><li class="listitem"><div class="para">
+ Opening a read-only handle on a disk image which is currently in use (eg. by a live VM) is possible; however, the results may be unpredictable or inconsistent particularly if the disk image is being heavily written to at the time you are reading it.
+ </div></li></ul></div><div class="section" id="API-and-C"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.11.1. Interaction with the API via a C program</h3></div></div></div><div class="para">
+ Your C program should start by including the <guestfs.h> header file, and creating a handle:
+ </div><pre class="screen">
+#include <stdio.h>
+#include <stdlib.h>
+#include <guestfs.h>
+
+int
+main (int argc, char *argv[])
+{
+ guestfs_h *g;
+
+ g = guestfs_create ();
+ if (g == NULL) {
+ perror ("failed to create libguestfs handle");
+ exit (EXIT_FAILURE);
+ }
+
+ /* ... */
+
+ guestfs_close (g);
+
+ exit (EXIT_SUCCESS);
+ }
+</pre><div class="para">
+ Save this program to a file (<code class="filename">test.c</code>). Compile this program and run it with the following two commands:
+ </div><pre class="screen">
+gcc -Wall test.c -o test -lguestfs
+./test
+</pre><div class="para">
+ At this stage it should print no output. The rest of this section demonstrates an example showing how to extend this program to create a new disk image, partition it, format it with an ext4 file system, and create some files in the file system. The disk image will be called <code class="filename">disk.img</code> and be created in the current directory.
+ </div><div class="para">
+ The outline of the program is:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Create the handle.
+ </div></li><li class="listitem"><div class="para">
+ Add disk(s) to the handle.
+ </div></li><li class="listitem"><div class="para">
+ Launch the libguestfs back end.
+ </div></li><li class="listitem"><div class="para">
+ Create the partition, file system and files.
+ </div></li><li class="listitem"><div class="para">
+ Close the handle and exit.
+ </div></li></ul></div><div class="para">
+ Here is the modified program:
+ </div><pre class="screen">
+#include <stdio.h>
+#include <stdlib.h>
+#include <string.h>
+#include <fcntl.h>
+#include <unistd.h>
+#include <guestfs.h>
+
+ int
+ main (int argc, char *argv[])
+ {
+ guestfs_h *g;
+ size_t i;
+
+ g = guestfs_create ();
+ if (g == NULL) {
+ perror ("failed to create libguestfs handle");
+ exit (EXIT_FAILURE);
+ }
+
+ /* Create a raw-format sparse disk image, 512 MB in size. */
+ int fd = open ("disk.img", O_CREAT|O_WRONLY|O_TRUNC|O_NOCTTY, 0666);
+ if (fd == -1) {
+ perror ("disk.img");
+ exit (EXIT_FAILURE);
+ }
+ if (ftruncate (fd, 512 * 1024 * 1024) == -1) {
+ perror ("disk.img: truncate");
+ exit (EXIT_FAILURE);
+ }
+ if (close (fd) == -1) {
+ perror ("disk.img: close");
+ exit (EXIT_FAILURE);
+ }
+
+ /* Set the trace flag so that we can see each libguestfs call. */
+ guestfs_set_trace (g, 1);
+
+ /* Set the autosync flag so that the disk will be synchronized
+ * automatically when the libguestfs handle is closed.
+ */
+ guestfs_set_autosync (g, 1);
+
+ /* Add the disk image to libguestfs. */
+ if (guestfs_add_drive_opts (g, "disk.img",
+ GUESTFS_ADD_DRIVE_OPTS_FORMAT, "raw", /* raw format */
+ GUESTFS_ADD_DRIVE_OPTS_READONLY, 0, /* for write */
+ -1 /* this marks end of optional arguments */ )
+ == -1)
+ exit (EXIT_FAILURE);
+
+ /* Run the libguestfs back-end. */
+ if (guestfs_launch (g) == -1)
+ exit (EXIT_FAILURE);
+
+ /* Get the list of devices. Because we only added one drive
+ * above, we expect that this list should contain a single
+ * element.
+ */
+ char **devices = guestfs_list_devices (g);
+ if (devices == NULL)
+ exit (EXIT_FAILURE);
+ if (devices[0] == NULL || devices[1] != NULL) {
+ fprintf (stderr,
+ "error: expected a single device from list-devices\n");
+ exit (EXIT_FAILURE);
+ }
+
+ /* Partition the disk as one single MBR partition. */
+ if (guestfs_part_disk (g, devices[0], "mbr") == -1)
+ exit (EXIT_FAILURE);
+
+ /* Get the list of partitions. We expect a single element, which
+ * is the partition we have just created.
+ */
+ char **partitions = guestfs_list_partitions (g);
+ if (partitions == NULL)
+ exit (EXIT_FAILURE);
+ if (partitions[0] == NULL || partitions[1] != NULL) {
+ fprintf (stderr,
+ "error: expected a single partition from list-partitions\n");
+ exit (EXIT_FAILURE);
+ }
+
+ /* Create an ext4 filesystem on the partition. */
+ if (guestfs_mkfs (g, "ext4", partitions[0]) == -1)
+ exit (EXIT_FAILURE);
+
+ /* Now mount the filesystem so that we can add files. */
+ if (guestfs_mount_options (g, "", partitions[0], "/") == -1)
+ exit (EXIT_FAILURE);
+
+ /* Create some files and directories. */
+ if (guestfs_touch (g, "/empty") == -1)
+ exit (EXIT_FAILURE);
+
+ const char *message = "Hello, world\n";
+ if (guestfs_write (g, "/hello", message, strlen (message)) == -1)
+ exit (EXIT_FAILURE);
+
+ if (guestfs_mkdir (g, "/foo") == -1)
+ exit (EXIT_FAILURE);
+
+ /* This uploads the local file /etc/resolv.conf into the disk image. */
+ if (guestfs_upload (g, "/etc/resolv.conf", "/foo/resolv.conf") == -1)
+ exit (EXIT_FAILURE);
+
+ /* Because 'autosync' was set (above) we can just close the handle
+ * and the disk contents will be synchronized. You can also do
+ * this manually by calling guestfs_umount_all and guestfs_sync.
+ */
+ guestfs_close (g);
+
+ /* Free up the lists. */
+ for (i = 0; devices[i] != NULL; ++i)
+ free (devices[i]);
+ free (devices);
+ for (i = 0; partitions[i] != NULL; ++i)
+ free (partitions[i]);
+ free (partitions);
+
+ exit (EXIT_SUCCESS);
+ }
+</pre><div class="para">
+ Compile and run this program with the following two commands:
+ </div><pre class="screen">
+gcc -Wall test.c -o test -lguestfs
+./test
+</pre><div class="para">
+ If the program runs to completion successfully then you should be left with a disk image called <code class="filename">disk.img</code>, which you can examine with guestfish:
+ </div><pre class="screen">
+guestfish --ro -a disk.img -m /dev/sda1
+><fs> ll /
+><fs> cat /foo/resolv.conf
+</pre><div class="para">
+ By default (for C and C++ bindings only), libguestfs prints errors to stderr. You can change this behavior by setting an error handler. The guestfs(3) man page discusses this in detail.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-virt-win-reg-use.html"><strong>Prev</strong>G.10.3. Using virt-win-reg</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-libguestfs-troubleshoot.html"><strong>Next</strong>G.12. Troubleshooting</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html
new file mode 100644
index 0000000..4bf47af
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html
@@ -0,0 +1,45 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>28.3.2. Adding hard drives and other block devices to a guest</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html" title="28.3. Adding storage devices to guests" /><link rel="prev" href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html" title="28.3. Adding storage devices to guests" /><link rel="next" href="sect-Managing_storage_controllers_in_a_guest.html" title="28.3.3. Managing storage controllers in a guest" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-Virtualized_block_devices-Adding_storage_devices_to_guests.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Managing_storage_controllers_in_a_guest.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">28.3.2. Adding hard drives and other block devices to a guest</h3></div></div></div><div class="para">
+ System administrators use additional hard drives to provide increased storage space for a guest, or to separate system data from user data.
+ </div><div class="procedure" id="proc-Virtualization-Adding_storage_devices_to_guests-Adding_physical_block_devices_to_virtualized_guests"><h6>Procedure 28.2. Adding physical block devices to guests</h6><ol class="1"><li class="step"><div class="para">
+ This procedure describes how to add a hard drive on the host to a guest. It applies to all physical block devices, including CD-ROM, DVD and floppy devices.
+ </div><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 class="step"><div class="para">
+ Do one of the following:
+ </div><ol class="a"><li class="step"><div class="para">
+ Create the additional storage by writing a <code class="command">disk</code> element in a new file. In this example, this file will be known as <code class="filename">NewStorage.xml</code>. The following example is a configuration file section which contains an additional device-based storage container for the host partition <code class="filename">/dev/sr0:</code>
+ </div><pre class="screen">
+<disk type='block' device='disk'>
+ <driver name='qemu' type='raw' cache='none'/>
+ <source dev='/dev/sr0'/>
+ <target dev='vdc' bus='virtio'/>
+</disk>
+</pre></li><li class="step"><div class="para">
+ Follow the instruction in the previous section to attach the device to the guest. Alternatively, you can use the <em class="parameter"><code>virsh attach-disk</code></em> command, as shown:
+ </div><pre class="screen">
+# virsh attach-disk Guest1 /dev/sr0 vdc
+</pre><div class="para">
+ Note that the following options are available:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The<code class="command">virsh attach-disk</code> command also accepts the <em class="parameter"><code>--config</code></em>, <em class="parameter"><code>--type</code></em>, and <em class="parameter"><code>--mode</code></em> options, as shown:
+ </div><pre class="screen">
+# <code class="command">virsh attach-disk Guest1 /dev/sr0 vdc --config --type cdrom --mode readonly</code></pre></li><li class="listitem"><div class="para">
+ Additionally, <em class="parameter"><code> --type</code></em> also accepts <em class="parameter"><code>--type disk</code></em> in cases where the device is a hard drive.
+ </div></li></ul></div></li></ol></li><li class="step"><div class="para">
+ The guest now has a new hard disk device called <code class="filename">/dev/vdc</code> on Linux (or something similar, depending on what the guest OS chooses) or <code class="filename">D: drive</code> (for example) on Windows. You can now initialize the disk from the guest, following the standard procedures for the guest's operating system. Refer to <a class="xref" href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html#proc-Virtualization-Adding_storage_devices">Procedure 28.1, “Adding file-based storage”</a> and <a class="xref" href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html#step-partition_disk">Step 6</a> for an example.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ The host should not use filesystem labels to identify file systems in the <code class="filename">fstab</code> file, the <code class="filename">initrd</code> file or on the kernel command line. Doing so presents a security risk if less privileged users, such as guests, have write access to whole partitions or LVM volumes, because a guest could potentially write a filesystem label belonging to the host, to its own block device storage. Upon reboot of the host, the host could then mistakenly use the guest's disk as a system disk, which would compromise the host system.
+ </div><div class="para">
+ It is preferable to use the UUID of a device to identify it in the <code class="filename">fstab</code> file, the <code class="filename">initrd</code> file or on the kernel command line. While using UUIDs is still not completely secure on certain file systems, a similar compromise with UUID is significantly less feasible.
+ </div></div></div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Guests should not be given write access to whole disks or block devices (for example, <code class="filename">/dev/sdb</code>). Guests with access to whole block devices may be able to modify volume labels, which can be used to compromise the host system. Use partitions (for example, <code class="filename">/dev/sdb1</code>) or LVM volumes to prevent this issue.
+ </div></div></div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html"><strong>Prev</strong>28.3. 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-Managing_storage_controllers_in_a_guest.html"><strong>Next</strong>28.3.3. Managing storage controllers in a guest</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Additional_resources-Installed_documentation.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Additional_resources-Installed_documentation.html
new file mode 100644
index 0000000..891e744
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Additional_resources-Installed_documentation.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>I.2. Installed documentation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="appe-Virtualization-Additional_resources.html" title="Appendix I. Additional resources" /><link rel="prev" href="appe-Virtualization-Additional_resources.html" title="Appendix I. Additional resources" /><link rel="next" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 acces
skey="p" href="appe-Virtualization-Additional_resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-lib-dom-xml.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Additional_resources-Installed_documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">I.2. Installed documentation</h2></div></div></div><a id="idp16144688" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><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 class="listitem"><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 class="listitem"><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 class="listitem"><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 distributions inside of virtual machines.
+ </div></li><li class="listitem"><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-Additional_resources.html"><strong>Prev</strong>Appendix I. 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="ch-lib-dom-xml.html"><strong>Next</strong>Appendix J. Manipulating the domain xml</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html
new file mode 100644
index 0000000..2521e3e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html
@@ -0,0 +1,120 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.4. Live KVM migration with virsh</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-KVM_live_migration.html" title="Chapter 20. KVM live migration" /><link rel="prev" href="shared-storage-nfs-migration.html" title="20.3. Shared storage example: NFS for a simple migration" /><link rel="next" href="virsh-migration-arguements.html" title="20.4.2. Additional options for the virsh migrate command" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="shared-storage-nfs-migration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="virsh-migration-arguements.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.4. 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">
+ Note that the <em class="replaceable"><code>--live</code></em> option may be eliminated when live migration is not desired. Additional options are listed in <a class="xref" href="virsh-migration-arguements.html">Section 20.4.2, “Additional options for the virsh migrate command”</a>.
+ </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 connection URL of the destination host. 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="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The <em class="parameter"><code>DestinationURL</code></em> parameter for normal migration and peer2peer migration has different semantics:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ normal migration: the <em class="parameter"><code>DestinationURL</code></em> is the URL of the target host as seen from the source guest.
+ </div></li><li class="listitem"><div class="para">
+ peer2peer migration: <em class="parameter"><code>DestinationURL</code></em> is the URL of the target host as seen from the source host.
+ </div></li></ul></div></div></div><div class="para">
+ Once the command is entered, you will be prompted for the root password of the destination system.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ An entry for the destination host, in the <code class="filename">/etc/hosts</code> file on the source server is required for migration to succeed. Enter the IP address and hostname for the destination host in this file as shown in the following example, substituting your destination host's IP address and hostname:
+<pre class="screen">
+10.0.0.20 host2.example.com
+</pre>
+ </div></div></div><div class="formalpara" id="form-Virtualization-Live_KVM_migration_with_virsh-Example_live_migration_with_virsh"><h5 class="formalpara">Example: live migration with virsh</h5>
+ This example migrates from <code class="systemitem">host1.example.com</code> to <code class="systemitem">host2.example.com</code>. Change the host names for your environment. This example migrates a virtual machine named <code class="filename">guest1-F19</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_Administration_Guide-KVM_live_migration.html#item-Virtualization-Live_migration_requirements-Migration_requirements">Migration requirements</a>).
+ </div><div class="procedure"><ol class="1"><li class="step" id="step-Virtualization_Administration_Guide-Live_KVM_migration_with_virsh-Verify_the_guest_is_running"><p class="title"><strong>Verify the guest is running</strong></p><div class="para">
+ From the source system, <code class="systemitem">host1.example.com</code>, verify <code class="systemitem">guest1-F19</code> is running:
+ </div><pre class="screen">[root at host1 ~]# virsh list
+Id Name State
+----------------------------------
+ 10 guest1-F19 running
+</pre></li><li class="step" id="step-Virtualization_Administration_Guide-Live_KVM_migration_with_virsh-Migrate_the_guest"><p class="title"><strong>Migrate the guest</strong></p><div class="para">
+ Execute the following command to live migrate the guest to the destination, <code class="systemitem">host2.example.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>guest1-F19 qemu+ssh://host2.example.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 class="step" id="step-Virtualization_Administration_Guide-Live_KVM_migration_with_virsh-Wait"><p class="title"><strong>Wait</strong></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 class="step" id="step-Virtualization_Administration_Guide-Live_KVM_migration_with_virsh-Verify_the_guest_has_arrived_at_the_destination_host"><p class="title"><strong>Verify the guest has arrived at the destination host</strong></p><div class="para">
+ From the destination system, <code class="systemitem">host2.example.com</code>, verify <code class="systemitem">guest1-F19</code> is running:
+ </div><pre class="screen">[root at host2 ~]# virsh list
+Id Name State
+----------------------------------
+ 10 guest1-F19 running
+</pre></li></ol></div><div class="para">
+ The live migration is now complete.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ libvirt supports a variety of networking methods including TLS/SSL, UNIX sockets, SSH, and unencrypted TCP. Refer to <a class="xref" href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html">Chapter 21, <em>Remote management of guests</em></a> for more information on using other methods.
+ </div></div></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Non-running guests cannot be migrated with the <code class="command">virsh migrate</code> command. To migrate a non-running guest, the following script should be used:
+<pre class="screen">
+virsh dumpxml Guest1 > Guest1.xml
+virsh -c qemu+ssh://<target-system-FQDN> define Guest1.xml
+virsh undefine Guest1
+</pre>
+ </div></div></div><div class="section" id="add-notes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.4.1. Additonal tips for migration with virsh </h3></div></div></div><div class="para">
+ It is possible to perform multiple, concurrent live migrations where each migration runs in a separate command shell. However, this should be done with caution and should involve careful calculations as each migration instance uses one MAX_CLIENT from each side (source and target). As the default setting is 20, there is enough to run 10 instances without changing the settings. Should you need to change the settings, refer to the procedure <a class="xref" href="chap-Virtualization_Administration_Guide-KVM_live_migration.html#change-libvirt-config">Procedure 20.1, “Configuring libvirtd.conf”</a>.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Open the libvirtd.conf file as described in <a class="xref" href="chap-Virtualization_Administration_Guide-KVM_live_migration.html#change-libvirt-config">Procedure 20.1, “Configuring libvirtd.conf”</a>.
+ </div></li><li class="step"><div class="para">
+ Look for the Processing controls section.
+ </div><pre class="screen">
+#################################################################
+#
+# Processing controls
+#
+
+# The maximum number of concurrent client connections to allow
+# over all sockets combined.
+#max_clients = 20
+
+
+# The minimum limit sets the number of workers to start up
+# initially. If the number of active clients exceeds this,
+# then more threads are spawned, upto max_workers limit.
+# Typically you'd want max_workers to equal maximum number
+# of clients allowed
+#min_workers = 5
+#max_workers = 20
+
+
+# The number of priority workers. If all workers from above
+# pool will stuck, some calls marked as high priority
+# (notably domainDestroy) can be executed in this pool.
+#prio_workers = 5
+
+# Total global limit on concurrent RPC calls. Should be
+# at least as large as max_workers. Beyond this, RPC requests
+# will be read into memory and queued. This directly impact
+# memory usage, currently each request requires 256 KB of
+# memory. So by default upto 5 MB of memory is used
+#
+# XXX this isn't actually enforced yet, only the per-client
+# limit is used so far
+#max_requests = 20
+
+# Limit on concurrent requests from a single client
+# connection. To avoid one client monopolizing the server
+# this should be a small fraction of the global max_requests
+# and max_workers parameter
+#max_client_requests = 5
+
+#################################################################
+</pre></li><li class="step"><div class="para">
+ Change the <em class="parameter"><code>max_clients</code></em> and <em class="parameter"><code>max_workers</code></em> parameters settings. It is recommended that the number be the same in both parameters. The <em class="parameter"><code>max_clients</code></em> will use 2 clients per migration (one per side) and <em class="parameter"><code>max_workers</code></em> will use 1 worker on the source and 0 workers on the destination during the perform phase and 1 worker on the destination during the finish phase.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The <em class="parameter"><code>max_clients</code></em> and <em class="parameter"><code>max_workers</code></em> parameters settings are effected by all guest connections to the libvirtd service. This means that any user that is using the same guest and is performing a migration at the same time will also beholden to the limits set in the the <em class="parameter"><code>max_clients</code></em> and <em class="parameter"><code>max_workers</code></em> parameters settings. This is why the maximum value needs to be considered carefully before performing a concurrent live migration.
+ </div></div></div></li><li class="step"><div class="para">
+ Save the file and restart the service.
+ </div></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="shared-storage-nfs-migration.html"><strong>Prev</strong>20.3. Shared storage example: NFS for a simple mi...</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="virsh-migration-arguements.html"><strong>Next</strong>20.4.2. Additional options for the virsh migrate ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager.html
new file mode 100644
index 0000000..79b1342
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager.html
@@ -0,0 +1,57 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.5. Migrating with virt-manager</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-KVM_live_migration.html" title="Chapter 20. KVM live migration" /><link rel="prev" href="virsh-migration-arguements.html" title="20.4.2. Additional options for the virsh migrate command" /><link rel="next" href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html" title="Chapter 21. Remote management of guests" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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_ri
ght.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="virsh-migration-arguements.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.5. Migrating with virt-manager</h2></div></div></div><div class="para">
+ This section covers migrating a KVM guest with <code class="command">virt-manager</code> from one host to another.
+ </div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Open virt-manager</strong></p><div class="para">
+ Open <code class="command">virt-manager</code>. Choose <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>Virtual Machine Manager</strong></span> from the main menu bar to launch <code class="command">virt-manager</code>.
+ </div><div class="figure" id="launch-virt-man-mig-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic1-virt-mgr-guests.png" width="444" alt="Virt-Manager main menu" /></div></div><h6>Figure 20.1. Virt-Manager main menu</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Connect to the target host</strong></p><div class="para">
+ Connect to the target host by clicking on the <span class="guimenu"><strong>File</strong></span> menu, then click <span class="guimenuitem"><strong>Add Connection</strong></span>.
+ <div class="figure" id="add-conn-mig-screen-step1"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic2-add-connection-pull-down.png" width="444" alt="Open Add Connection window" /></div></div><h6>Figure 20.2. Open Add Connection window</h6></div><br class="figure-break" />
+
+ </div></li><li class="step"><p class="title"><strong>Add connection</strong></p><div class="para">
+ The <span class="guilabel"><strong>Add Connection</strong></span> window appears.
+ </div><div class="figure" id="add-conn-mig-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic3-Add-Connection.png" alt="Adding a connection to the target host" /></div></div><h6>Figure 20.3. Adding a connection to the target host</h6></div><br class="figure-break" /><div class="para">
+ Enter the following details:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Hypervisor</strong></span>: Select <span class="guimenuitem"><strong>QEMU/KVM</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Method</strong></span>: Select the connection method.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Username</strong></span>: Enter the username for the remote host.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Hostname</strong></span>: Enter the hostname for the remote host.
+ </div></li></ul></div><div class="para">
+ Click the <span class="guibutton"><strong>Connect</strong></span> button. An SSH connection is used in this example, so the specified user's password must be entered in the next step.
+ </div><div class="figure" id="pass-ssh-mig-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic4-OpenSSH.png" alt="Enter password" /></div></div><h6>Figure 20.4. Enter password</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Migrate guest</strong></p><div class="para">
+ Right-click on the host to be migrated (<span class="bold bold"><strong>guest1-F19</strong></span> in this example) and click <span class="guimenuitem"><strong>Migrate</strong></span>.
+ </div><div class="figure" id="choose-host-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic5-guest-select-migrate.png" width="444" alt="Choosing the host to migrate" /></div></div><h6>Figure 20.5. Choosing the host to migrate</h6></div><br class="figure-break" /><div class="para">
+ Select the host you wish to migrate to and click <span class="guimenuitem"><strong>Migrate</strong></span>.
+ </div><div class="figure" id="mig-last-step-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic6-final-before-migrate.png" alt="Migrating the host" /></div></div><h6>Figure 20.6. Migrating the host</h6></div><br class="figure-break" /><div class="para">
+ A progress window will appear.
+ </div><div class="figure" id="mig-status-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic7-Migrating-guest1-rhel6-64.png" alt="Progress window" /></div></div><h6>Figure 20.7. Progress window</h6></div><br class="figure-break" /><div class="para">
+ <code class="command">virt-manager</code> now displays the newly migrated guest.
+ </div><div class="figure" id="mig-results-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-pic8-migrated.png" width="444" alt="Migrated guest status" /></div></div><h6>Figure 20.8. Migrated guest status</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>View the storage details for the host</strong></p><div class="para">
+ In the <span class="guimenu"><strong>Edit</strong></span> menu, click <span class="guimenuitem"><strong>Connection Details</strong></span>, the Connection Details window appears.
+ </div><div class="para">
+ Click the <span class="guibutton"><strong>Storage</strong></span> tab. The iSCSI target details for this host is shown.
+ </div><div class="figure" id="host-details-screenshot"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-virtlab22-Host-Details.png" width="444" alt="Storage details" /></div></div><h6>Figure 20.9. Storage details</h6></div><br class="figure-break" /><div class="para">
+ This host was defined by the following XML configuration:
+ </div><pre class="screen">
+<pool type='iscsi'>
+ <name>iscsirhel6guest</name>
+ <source>
+ <host name='virtlab22.example.com.'/>
+ <device path='iqn.2001-05.com.iscsivendor:0-8a0906-fbab74a06-a700000017a4cc89-rhevh'/>
+ </source>
+ <target>
+ <path>/dev/disk/by-path</path>
+ </target>
+</pool>
+</pre></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="virsh-migration-arguements.html"><strong>Prev</strong>20.4.2. Additional options for the virsh migrate ...</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_Administration_Guide-Remote_management_of_virtualized_guests.html"><strong>Next</strong>Chapter 21. Remote management of guests</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html
new file mode 100644
index 0000000..344174d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html
@@ -0,0 +1,16 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.8. Displaying CPU usage for guests</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="Appendix F. Managing guests with the Virtual Machine Manager (virt-manager)" /><link rel="prev" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html" title="F.7. Performance monitoring" /><link rel="next" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage.html" title="F.9. Displaying CPU usage for hosts" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Com
mon_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-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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">F.8. Displaying CPU usage for guests</h2></div></div></div><div class="para">
+ To view the CPU usage for all guests on your system:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ From the <span class="guilabel"><strong>View</strong></span> menu, select <span class="guilabel"><strong>Graph</strong></span>, then the <span class="guilabel"><strong>Guest CPU Usage</strong></span> check box.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_CPU_usage-Selecting_guest-CPU_usage"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt24.png" width="444" alt="Enabling guest CPU usage statistics graphing" /></div></div><h6>Figure F.18. Enabling guest CPU usage statistics graphing</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ The Virtual Machine Manager shows a graph of CPU usage for all virtual machines on your system.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_CPU_usage-Displaying_CPU_usage"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager_fig31pt25.png" width="444" alt="Guest CPU usage graph" /></div></div><h6>Figure F.19. Guest CPU usage graph</h6></div><br class="figure-break" /></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html"><strong>Prev</strong>F.7. Performance 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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage.html"><strong>Next</strong>F.9. Displaying CPU usage for hosts</a></li></ul></bo
dy></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO.html
new file mode 100644
index 0000000..e6109aa
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.10. Displaying Disk I/O</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="Appendix F. Managing guests with the Virtual Machine Manager (virt-manager)" /><link rel="prev" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage.html" title="F.9. Displaying CPU usage for hosts" /><link rel="next" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO.html" title="F.11. Displaying Network I/O" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">F.10. Displaying Disk I/O</h2></div></div></div><div class="para">
+ To view the disk I/O for all virtual machines on your system:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Make sure that the Disk I/O statisctics collection is enabled. To do this, from the <span class="guilabel"><strong>Edit</strong></span> menu, select <span class="guilabel"><strong>Preferences</strong></span> and click the <span class="guilabel"><strong>Stats</strong></span>tab.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Disk I/O </strong></span>checkbox.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-enabling_Disk_IO-stats"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager-enable-disk-io.png" alt="Enabling Disk I/O" /></div></div><h6>Figure F.22. Enabling Disk I/O</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ To enable the Disk I.O display, from the <span class="guilabel"><strong>View</strong></span> menu, select <span class="guilabel"><strong>Graph</strong></span>, then the <span class="guilabel"><strong>Disk I/O</strong></span> check box.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_Disk_IO-Selecting_Disk_IO"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager_fig31pt26.png" width="444" alt="Selecting Disk I/O" /></div></div><h6>Figure F.23. Selecting Disk I/O</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ The Virtual Machine Manager shows a graph of Disk I/O for all virtual machines on your system.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_Disk_IO-Displaying_Disk_IO"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt27.png" width="444" alt="Displaying Disk I/O" /></div></div><h6>Figure F.24. Displaying Disk I/O</h6></div><br class="figure-break" /></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage.html"><strong>Prev</strong>F.9. Displaying CPU usage for hosts</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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO.html"><strong>Next</strong>F.11. Displaying Network I/O</a></li></ul></body>
</html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO.html
new file mode 100644
index 0000000..944bf45
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.11. Displaying Network I/O</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="Appendix F. Managing guests with the Virtual Machine Manager (virt-manager)" /><link rel="prev" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO.html" title="F.10. Displaying Disk I/O" /><link rel="next" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Network_IO"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">F.11. Displaying Network I/O</h2></div></div></div><div class="para">
+ To view the network I/O for all virtual machines on your system:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Make sure that the Network I/O statisctics collection is enabled. To do this, from the <span class="guilabel"><strong>Edit</strong></span> menu, select <span class="guilabel"><strong>Preferences</strong></span> and click the <span class="guilabel"><strong>Stats</strong></span>tab.
+ </div></li><li class="step"><div class="para">
+ Select the <span class="guilabel"><strong>Network I/O </strong></span>checkbox.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-enabling_network_IO-stats"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager-enable-networkio.png" alt="Enabling Network I/O" /></div></div><h6>Figure F.25. Enabling Network I/O</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ To display the Network I/O statistics, from the <span class="guilabel"><strong>View</strong></span> menu, select <span class="guilabel"><strong>Graph</strong></span>, then the <span class="guilabel"><strong>Network I/O</strong></span> check box.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_Network_IO-Selecting_Network_IO"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt28.png" width="444" alt="Selecting Network I/O" /></div></div><h6>Figure F.26. Selecting Network I/O</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ The Virtual Machine Manager shows a graph of Network I/O for all virtual machines on your system.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_Network_IO-Displaying_Network_IO"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt29.png" width="444" alt="Displaying Network I/O" /></div></div><h6>Figure F.27. Displaying Network I/O</h6></div><br class="figure-break" /></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO.html"><strong>Prev</strong>F.10. Displaying Disk I/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="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html"><strong>Next</strong>Appendix G. Guest disk access with offline tools</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html
new file mode 100644
index 0000000..c207aab
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html
@@ -0,0 +1,34 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.6. Displaying guest details</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="Appendix F. Managing guests with the Virtual Machine Manager (virt-manager)" /><link rel="prev" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window.html" title="F.5. Adding a remote connection" /><link rel="next" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html" title="F.7. Performance monitoring" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">F.6. Displaying guest details</h2></div></div></div><div class="para">
+ You can use the Virtual Machine Monitor to view activity 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 class="step"><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_Administration_Guide-Displaying_guest_details-Selecting_a_virtual_machine_to_display_"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt1.png" width="444" alt="Selecting a virtual machine to display" /></div></div><h6>Figure F.8. Selecting a virtual machine to display </h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ From the Virtual Machine Manager <span class="guilabel"><strong>Edit</strong></span> menu, select <span class="guilabel"><strong>Virtual Machine Details</strong></span>.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Displaying_virtual_machine_details_menu"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt11.png" width="444" alt="Displaying the virtual machine details" /></div></div><h6>Figure F.9. Displaying the virtual machine details</h6></div><br class="figure-break" /><div class="para">
+ When the Virtual Machine details window opens, there may be a console displayed. Should this happen, clikc <span class="guilabel"><strong>View</strong></span> and then select <span class="guilabel"><strong>Details</strong></span>. The Overview window opens first by default. To go back to this window, select <span class="guilabel"><strong>Overview</strong></span> from the navigation pane on the left hand side.
+ </div><div class="para">
+ The <span class="guilabel"><strong>Overview</strong></span> view shows a summary of configuration details for the guest.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Displaying_guest_details_overview"><div class="figure-contents"><div class="mediaobject"><img src="images/virtual_machine_overview.png" width="444" alt="Displaying guest details overview" /></div></div><h6>Figure F.10. Displaying guest details overview</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Select <span class="guilabel"><strong>Performance</strong></span> from the navigation pane on the left hand side.
+ </div><div class="para">
+ The <span class="guilabel"><strong>Performance</strong></span> view shows a summary of guest performance, including CPU and Memory usage.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Displaying_guest_performance"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt13.png" width="444" alt="Displaying guest performance details" /></div></div><h6>Figure F.11. Displaying guest performance details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Select <span class="guilabel"><strong>Processor</strong></span> from the navigation pane on the left hand side. The <span class="guilabel"><strong>Processor</strong></span> view allows you to view or change the current processor allocation.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Processor_allocation_panel"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt14.png" width="444" alt="Processor allocation panel" /></div></div><h6>Figure F.12. Processor allocation panel</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Select <span class="guilabel"><strong>Memory</strong></span> from the navigation pane on the left hand side. The <span class="guilabel"><strong>Memory</strong></span> view allows you to view or change the current memory allocation.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Displaying_memory_allocation"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt15.png" width="444" alt="Displaying memory allocation" /></div></div><h6>Figure F.13. Displaying memory allocation</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Each virtual disk attached to the virtual machine is displayed in the navigation pane. Click on a virtual disk to modify or remove it.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Displaying_disk_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt16.png" width="444" alt="Displaying disk configuration" /></div></div><h6>Figure F.14. Displaying disk configuration</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Each virtual network interface attached to the virtual machine is displayed in the navigation pane. Click on a virtual network interface to modify or remove it.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_guest_details-Displaying_network_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt17.png" width="444" alt="Displaying network configuration" /></div></div><h6>Figure F.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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window.html"><strong>Prev</strong>F.5. Adding a remote connection</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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html"><strong>Next</strong>F.7. Perfo
rmance monitoring</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage.html
new file mode 100644
index 0000000..a8cffdc
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage.html
@@ -0,0 +1,16 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.9. Displaying CPU usage for hosts</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="Appendix F. Managing guests with the Virtual Machine Manager (virt-manager)" /><link rel="prev" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html" title="F.8. Displaying CPU usage for guests" /><link rel="next" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO.html" title="F.10. Displaying Disk I/O" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_C
ontent/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-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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_host-CPU_usage"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">F.9. Displaying CPU usage for hosts</h2></div></div></div><div class="para">
+ To view the CPU usage for all hosts on your system:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ From the <span class="guilabel"><strong>View</strong></span> menu, select <span class="guilabel"><strong>Graph</strong></span>, then the <span class="guilabel"><strong>Host CPU Usage</strong></span> check box.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_Host-CPU_usage-Selecting_CPU_usage"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt24a.png" width="444" alt="Enabling host CPU usage statistics graphing" /></div></div><h6>Figure F.20. Enabling host CPU usage statistics graphing</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ The Virtual Machine Manager shows a graph of host CPU usage on your system.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Displaying_host-CPU_usage-Displaying_CPU_usage"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager_fig31pt25a.png" width="444" alt="Host CPU usage graph" /></div></div><h6>Figure F.21. Host CPU usage graph</h6></div><br class="figure-break" /></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html"><strong>Prev</strong>F.8. Displaying CPU usage 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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_Disk_IO.html"><strong>Next</strong>F.10. Displaying Disk I/O</a></li></ul></bod
y></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html
new file mode 100644
index 0000000..cf54fc5
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.7. Performance monitoring</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="Appendix F. Managing guests with the Virtual Machine Manager (virt-manager)" /><link rel="prev" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html" title="F.6. Displaying guest details" /><link rel="next" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html" title="F.8. Displaying CPU usage for guests" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Status_monitoring"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">F.7. Performance monitoring</h2></div></div></div><div class="para">
+ Performance monitoring preferences can be modified with <code class="command">virt-manager</code>'s preferences window.
+ </div><div class="para">
+ To configure performance monitoring:
+ </div><div class="procedure"><ol class="1"><li class="step"><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_Administration_Guide-Status_monitoring-Modifying_guest_preferences"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-VIrt-Manager-fig31pt18.png" width="444" alt="Modifying guest preferences" /></div></div><h6>Figure F.16. Modifying guest preferences</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guilabel"><strong>Preferences</strong></span> window appears.
+ </div></li><li class="step"><div class="para">
+ From the <span class="guilabel"><strong>Stats</strong></span> tab specify the time in seconds or stats polling options.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Status_monitoring-Configuring_status_monitoring"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt19.png" alt="Configuring performance monitoring" /></div></div><h6>Figure F.17. Configuring performance monitoring</h6></div><br class="figure-break" /></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html"><strong>Prev</strong>F.6. 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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_CPU_usage.html"><strong>Next</strong>F.8. Displaying CPU usage for
guests</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_.html
new file mode 100644
index 0000000..7934cba
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_.html
@@ -0,0 +1,14 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.3. The virtual hardware details window</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="Appendix F. Managing guests with the Virtual Machine Manager (virt-manager)" /><link rel="prev" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html" title="F.2. The Virtual Machine Manager main window" /><link rel="next" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html" title="F.4. Virtual Machine graphical console" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">F.3. The virtual hardware details window</h2></div></div></div><div class="para"
>
+ The virtual hardware details window displays information about the virtual hardware configured for the guest. Virtual hardware resources can be added, removed and modified in this window. To access the virtual hardware details window, click on the icon in the toolbar.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-The_Virtual_Machine_Manager_details_window_-virt_manager_details_button"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt3.png" width="444" alt="The virtual hardware details icon" /></div></div><h6>Figure F.3. The virtual hardware details icon</h6></div><br class="figure-break" /><div class="para">
+ Clicking the icon displays the virtual hardware details window.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-The_Virtual_Machine_Manager_details_window_-virt_manager_details_window"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt4.png" width="444" alt="The virtual hardware details window" /></div></div><h6>Figure F.4. The virtual hardware details window</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html"><strong>Prev</strong>F.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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_cons
ole_.html"><strong>Next</strong>F.4. Virtual Machine graphical console</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html
new file mode 100644
index 0000000..3005cdc
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.2. The Virtual Machine Manager main window</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="Appendix F. Managing guests with the Virtual Machine Manager (virt-manager)" /><link rel="prev" href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="Appendix F. Managing guests with the Virtual Machine Manager (virt-manager)" /><link rel="next" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_.html" title="F.3. The virtual hardware details window" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p i
d="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_Administration_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-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" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_main_window"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">F.2. The Virtual Machine Manager main window</h2></div></div></div><di
v class="para">
+ This main window displays all the running guests and resources used by guests. Select a guest by double clicking the guest's name.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-The_Virtual_Machine_Manager_main_window-Virtual_Machine_Manager_main_window"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt2.png" width="444" alt="Virtual Machine Manager main window" /></div></div><h6>Figure F.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_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html"><strong>Prev</strong>Appendix F. 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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_
window_.html"><strong>Next</strong>F.3. The virtual hardware details window</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window.html
new file mode 100644
index 0000000..e7f405a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.5. Adding a remote connection</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="Appendix F. Managing guests with the Virtual Machine Manager (virt-manager)" /><link rel="prev" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html" title="F.4. Virtual Machine graphical console" /><link rel="next" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html" title="F.6. Displaying guest details" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproje
ct.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-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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">F.5. Adding a remote connection</h2></div></div></div><div class="para">
+ This procedure covers how to set up a connection to a remote system using <code class="command">virt-manager</code>.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To create a new connection open the <span class="guilabel"><strong>File</strong></span> menu and select the <span class="guilabel"><strong>Add Connection...</strong></span> menu item.
+ </div></li><li class="step"><div class="para">
+ The <span class="guilabel"><strong>Add Connection</strong></span> wizard appears. Select the hypervisor. For Fedora systems select <span class="guilabel"><strong>QEMU/KVM</strong></span>. Select Local for the local system or one of the remote connection options and click <span class="guilabel"><strong>Connect</strong></span>. This example uses Remote tunnel over SSH which works on default installations. For more information on configuring remote connections refer to <a class="xref" href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html">Chapter 21, <em>Remote management of guests</em></a>
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Remote_management-Add_connection"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt6.png" alt="Add Connection" /></div></div><h6>Figure F.6. Add Connection</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Enter the root password for the selected host when prompted.
+ </div></li></ol></div><div class="para">
+ A remote host is now connected and appears in the main <code class="command">virt-manager</code> window.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Remote_management-Remove_host_in_the_main_virt-manager_window"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt7.png" width="444" alt="Remote host in the main virt-manager window" /></div></div><h6>Figure F.7. Remote host in the main virt-manager window</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html"><strong>Prev</strong>F.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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Displaying_guest_details.html"><str
ong>Next</strong>F.6. Displaying guest details</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html
new file mode 100644
index 0000000..3b6ad3c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>F.4. Virtual Machine graphical console</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager.html" title="Appendix F. Managing guests with the Virtual Machine Manager (virt-manager)" /><link rel="prev" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_.html" title="F.3. The virtual hardware details window" /><link rel="next" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window.html" title="F.5. Adding a remote connection" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-Virtual_Machine_graphical_console_"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">F.4. Virtual Machine graphical console</h2></div></div></div><div class="para">
+ This window displays a guest's graphical console. Guests can use several different protocols to export their graphical framebuffers: <code class="command">virt-manager</code> supports <span class="application"><strong>VNC</strong></span> and <span class="application"><strong>SPICE</strong></span>. 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_Administration_Guide-Virtual_Machine_graphical_console_-Graphical_console_window"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt5.png" width="444" alt="Graphical console window" /></div></div><h6>Figure F.5. Graphical console window</h6></div><br class="figure-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><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'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. Although virt-manager is configured to listen to other public network interfaces and alternative methods can be configured, it is not recommended.
+ </div><div class="para">
+ Remote administration can be performed by tunneling over SSH which encrypts the traffic. Although VNC can be configured to access remotely without tunneling over SSH, for security reasons, it is not recommended. To remotely administer the guest follow the instructions in: <a class="xref" href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html">Chapter 21, <em>Remote management of guests</em></a>. TLS can provide enterprise level security for managing guest and host systems.
+ </div></div></div><div class="para">
+ Your local desktop can intercept key combinations (for example, Ctrl+Alt+F1) to prevent them from being sent to the guest machine. You can use the <span class="guimenuitem"><strong>Send key</strong></span> menu option to send these sequences. From the guest machine window, click the <span class="guimenuitem"><strong>Send key</strong></span> menu and select the key sequence to send. In addition, from this menu you can also capture the screen output.
+ </div><div class="para">
+ SPICE is an alternative to VNC available for Fedora.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_Virtual_Machine_Manager_details_window_.html"><strong>Prev</strong>F.3. The virtual hardware 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-Managing_guests_with_the_Virtual_Machine_Manager_virt_manager-The_open_connection_window.html"><strong>Next</strong>F.5. Adding a remote connection</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor.html
new file mode 100644
index 0000000..eb512a9
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor.html
@@ -0,0 +1,14 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.3. Connecting to the hypervisor</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="prev" href="sect-Attaching_and_updating_a_device_with_virsh.html" title="E.2. Attaching and updating a device with virsh" /><link rel="next" href="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html" title="E.4. Creating a virtual machine XML dump (configuration file)" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-Attaching_and_updating_a_device_with_virsh.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Managing_guests_with_virsh-Connecting_to_the_hypervisor"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">E.3. Connecting to the hypervisor</h2></div></div></div><div class="para">
+ Connect to a hypervisor session with <code class="command">virsh</code>:
+ </div><pre class="screen"># virsh connect <em class="parameter"><code>{name}</code></em></pre><div class="para">
+ Where <em class="parameter"><code>{name}</code></em> is the machine name (hostname) or URL (the output of the <code class="command">virsh uri</code> command) of the hypervisor. To initiate a read-only connection, append the above command with <code class="command">--readonly</code>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Attaching_and_updating_a_device_with_virsh.html"><strong>Prev</strong>E.2. Attaching and updating a device 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="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html"><strong>Next</strong>E.4. Creating a virtual machine XML dump (configu...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html
new file mode 100644
index 0000000..8a9a869
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html
@@ -0,0 +1,90 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>21.2. Remote management over TLS and SSL</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html" title="Chapter 21. Remote management of guests" /><link rel="prev" href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html" title="Chapter 21. Remote management of guests" /><link rel="next" href="sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes.html" title="21.3. Transport modes" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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.o
rg"><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_Administration_Guide-Remote_management_of_virtualized_guests.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">21.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_Administration_Guide-Remote_management_of_virtualized_guests.html#sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_with_SSH">Section 21.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. The procedures that follow provide instructions on creating and deploying authentication certificates for TLS and SSL management.
+ </div><div class="procedure" id="createCA-key"><h6>Procedure 21.1. Creating a certificate authority (CA) key for TLS management</h6><ol class="1"><li class="step"><div class="para">
+ Before you begin, confirm that <code class="command">certtool</code> is installed. If not:
+ </div><pre class="screen">#<code class="command"> yum install certtool</code></pre></li><li class="step"><div class="para">
+ Generate a private key, using the following command:
+ </div><pre class="screen"># <code class="command">certtool --generate-privkey > cakey.pem</code></pre></li><li class="step"><div class="para">
+ Once the key generates, the next step is to create a signature file so the key can be self-signed. To do this, create a file with signature details and name it <code class="filename">ca.info</code>. This file should contain the following:
+ </div><pre class="screen"># <code class="command">vim ca.info</code></pre><pre class="screen">
+cn = Name of your organization
+ca
+cert_signing_key
+</pre></li><li class="step"><div class="para">
+ Generate the self-signed key with the following command:
+ </div><pre class="screen"># <code class="command">certtool --generate-self-signed --load-privkey cakey.perm --template ca.info --outfile cacert.pem</code></pre><div class="para">
+ Once the file generates, the ca.info file may be deleted using the <code class="command">rm</code> command. The file that results from the generation process is named <code class="filename">cacert.pem</code>. This file is the public key (certificate). The loaded file <code class="filename">cakey.pem</code> is the private key. This file should not be kept in a shared space. Keep this key private.
+ </div></li><li class="step"><div class="para">
+ Install the <code class="filename">cacert.pem</code> Certificate Authority Certificate file on all clients and servers in the <code class="filename">/etc/pki/CA/cacert.pem</code> directory to let them know that the certificate issued by your CA can be trusted. To view the contents of this file, run:
+<pre class="screen"># <code class="command">certtool -i --infile cacert.pem</code></pre>
+
+ </div><div class="para">
+ This is all that is required to set up your CA. Keep the CA's private key safe as you will need it in order to issue certificates for your clients and servers.
+ </div></li></ol></div><div class="procedure" id="issue-server-cetificate-ca"><h6>Procedure 21.2. Issuing a server certificate</h6><div class="para">
+ This procedure demonstrates how to issue a certificate with the X.509 CommonName (CN)field set to the hostname of the server. The CN must match the hostname which clients will be using to connect to the server. In this example, clients will be connecting to the server using the URI: <code class="filename">qemu://mycommonname/system</code>, so the CN field should be identical, ie mycommoname.
+ </div><ol class="1"><li class="step"><div class="para">
+ Create a private key for the server.
+ </div><pre class="screen"># <code class="command">certtool --generate-privkey > serverkey.pem</code></pre></li><li class="step"><div class="para">
+ Generate a signature for the CA's private key by first creating a template file called <code class="filename">server.info </code>. Make sure that the CN is set to be the same as the server's hostname:
+ </div><pre class="screen">
+organization = Name of your organization
+cn = mycommonname
+tls_www_server
+encryption_key
+signing_key
+</pre></li><li class="step"><div class="para">
+ Create the certificate with the following command:
+ </div><pre class="screen">
+# <code class="command">certtool --generate-certificate --load-privkey serverkey.pem --load-ca-certificate cacert.pem --load-ca-privkey cakey.pem \ --template server.info --outfile servercert.pem</code></pre></li><li class="step"><div class="para">
+ This results in two files being generated:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ serverkey.pem - The server's private key
+ </div></li><li class="listitem"><div class="para">
+ servercert.pem - The server's public key
+ </div></li></ul></div><div class="para">
+ Make sure to keep the location of the private key secret. To view the contents of the file, perform the following command:
+ </div><pre class="screen">
+# <code class="command">certtool -i -inifile servercert.pem</code></pre><div class="para">
+ When opening this file the <code class="filename">CN=</code> parameter should be the same as the CN that you set earlier. For example, <code class="filename">mycommonname</code>.
+ </div></li><li class="step"><div class="para">
+ Install the two files in the following locations:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">serverkey.pem</code> - the server's private key. Place this file in the following location: <code class="filename">/etc/pki/libvirt/private/serverkey.pem</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">servercert.pem</code> - the server's certificate. Install it in the following location on the server:<code class="filename"> /etc/pki/libvirt/servercert.pem</code>
+ </div></li></ul></div></li></ol></div><div class="procedure" id="pro-issue-client-certs-CA"><h6>Procedure 21.3. Issuing a client certificate</h6><ol class="1"><li class="step"><div class="para">
+ For every client (ie. any program linked with libvirt, such as virt-manager), you need to issue a certificate with the X.509 Distinguished Name (DN) set to a suitable name. This needs to be decided on a corporate level.
+ </div><div class="para">
+ For example purposes the following information will be used:
+ </div><pre class="screen"><em class="replaceable"><code>C=USA,ST=North Carolina,L=Raleigh,O=Fedora,CN=name_of_client</code></em></pre><div class="para">
+ This process is quite similar to <a class="xref" href="sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html#issue-server-cetificate-ca">Procedure 21.2, “Issuing a server certificate”</a>, with the following exceptions noted.
+ </div></li><li class="step"><div class="para">
+ Make a private key with the following command:
+ </div><pre class="screen"># <code class="command">certtool --generate-privkey > clientkey.pem</code></pre></li><li class="step"><div class="para">
+ Generate a signature for the CA's private key by first creating a template file called <code class="filename">client.info </code>. The file should contain the following (fields should be customized to reflect your region/location):
+ </div><pre class="screen">
+country = USA
+state = North Carolina
+locality = Raleigh
+organization = Fedora
+cn = client1
+tls_www_client
+encryption_key
+signing_key
+</pre></li><li class="step"><div class="para">
+ Sign the certificate with the following command:
+ </div><pre class="screen">
+# <code class="command">certtool --generate-certificate --load-privkey clientkey.pem --load-ca-certificate cacert.pem \ --load-ca-privkey cakey.pem --template client.info --outfile clientcert.pem</code></pre></li><li class="step"><div class="para">
+ Install the certificates on the client machine:
+ </div><pre class="screen">
+# <code class="command">cp clientkey.pem /etc/pki/libvirt/private/clientkey.pem</code>
+# <code class="command">cp clientcert.pem /etc/pki/libvirt/clientcert.pem</code></pre></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html"><strong>Prev</strong>Chapter 21. Remote management of 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-Remote_management_of_virtualized_guests-Transport_modes.html"><strong>Next</strong>21.3. Transport modes</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes.html
new file mode 100644
index 0000000..d334fc7
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes.html
@@ -0,0 +1,109 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>21.3. Transport modes</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Remote_management_of_virtualized_guests.html" title="Chapter 21. Remote management of guests" /><link rel="prev" href="sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html" title="21.2. Remote management over TLS and SSL" /><link rel="next" href="sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM.html" title="Chapter 22. Overcommitting with KVM" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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.fe
doraproject.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-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">21.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" id="form-Virtualization-Transport_modes-Transport_Layer_Security_TLS"><h5 class="formalpara">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" id="form-Virtualization-Transport_modes-UNIX_sockets"><h5 class="formalpara">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" id="form-Virtualization-Transport_modes-SSH"><h5 class="formalpara">SSH</h5>
+ Transported over a 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" id="form-Virtualization-Transport_modes-ext"><h5 class="formalpara">ext</h5>
+ The <em class="parameter"><code>ext</code></em> parameter is used for any external program which can make a connection to the remote machine by means outside the scope of libvirt. This parameter is unsupported.
+ </div><div class="formalpara" id="form-Virtualization-Transport_modes-tcp"><h5 class="formalpara">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" id="form-Virtualization-Transport_modes-Remote_URIs"><h5 class="formalpara">Remote URIs</h5>
+ A Uniform Resource Identifier (URI) is used by <code class="command">virsh</code> and <span class="package">libvirt</span> 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.
+ </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">
+ The transport method or the hostname must be provided to target an external location.
+ </div><div class="itemizedlist" id="item-Virtualization-Transport_modes-Examples_of_remote_management_parameters"><h6>Examples of remote management parameters</h6><ul><li class="listitem"><div class="para">
+ Connect to a remote KVM host named <code class="systemitem">host2</code>, using SSH transport and the SSH username <code class="systemitem">virtuser</code>.
+ </div><pre class="screen"><code class="command">qemu+ssh://virtuser@host2/</code></pre></li><li class="listitem"><div class="para">
+ Connect to a remote KVM hypervisor on the host named <code class="systemitem">host2</code> using TLS.
+ </div><pre class="screen"><code class="command">qemu://host2/</code></pre></li></ul></div><div class="itemizedlist" id="item-Virtualization-Transport_modes-Testing_examples"><h6>Testing examples</h6><ul><li class="listitem"><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"><code class="command">qemu+unix:///system?socket=/opt/libvirt/run/libvirt/libvirt-sock</code></pre></li><li class="listitem"><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"><code class="command">test+tcp://10.1.1.10:5000/default</code></pre></li></ul></div><div class="formalpara" id="form-Virtualization-Transport_modes-Extra_URI_parameters"><h5 class="formalpara">Extra URI parameters</h5>
+ Extra parameters can be appended to remote URIs. The table below <a class="xref" href="sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes.html#tabl-Virtualization-Transport_modes-Extra_URI_parameters">Table 21.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-Transport_modes-Extra_URI_parameters"><h6>Table 21.1. Extra URI parameters</h6><div class="table-contents"><table summary="Extra URI parameters" border="1"><colgroup><col width="25%" /><col width="25%" /><col width="25%" /><col width="25%" /></colgroup><thead><tr><th class="">
+ Name
+ </th><th class="">
+ Transport mode
+ </th><th class="">
+ Description
+ </th><th class="">
+ Example usage
+ </th></tr></thead><tbody><tr><td class="">
+ name
+ </td><td class="">
+ all modes
+ </td><td class="">
+ 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 class="">
+ name=qemu:///system
+ </td></tr><tr><td class="">
+ command
+ </td><td class="">
+ ssh and ext
+ </td><td class="">
+ The external command. For ext transport this is required. For ssh the default is ssh. The PATH is searched for the command.
+ </td><td class="">
+ command=/opt/openssh/bin/ssh
+ </td></tr><tr><td class="">
+ socket
+ </td><td class="">
+ unix and ssh
+ </td><td class="">
+ 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 class="">
+ socket=/opt/libvirt/run/libvirt/libvirt-sock
+ </td></tr><tr><td class="">
+ netcat
+ </td><td class="">
+ ssh
+ </td><td class="">
+ <div class="para">
+ The <code class="command">netcat</code> command can be used to connect to remote systems. The default netcat parameter uses the <code class="command">nc</code> command. For SSH transport, libvirt constructs an SSH command using the form below:
+ </div>
+ <div class="para">
+ <em class="parameter"><code>command</code></em> -p <em class="parameter"><code>port</code></em> [-l <em class="parameter"><code>username</code></em>] <em class="parameter"><code>hostname</code></em>
+ </div>
+ <div class="para">
+ <em class="parameter"><code>netcat</code></em> -U socket
+ </div>
+ <div class="para">
+ The <em class="parameter"><code>port</code></em>, <em class="parameter"><code>username</code></em> and <em class="parameter"><code>hostname</code></em> parameters can be specified as part of the remote URI. The <em class="parameter"><code>command</code></em>, <em class="parameter"><code>netcat</code></em> and <em class="parameter"><code>socket</code></em> come from other extra parameters.
+ </div>
+
+ </td><td class="">
+ netcat=/opt/netcat/bin/nc
+ </td></tr><tr><td class="">
+ no_verify
+ </td><td class="">
+ tls
+ </td><td class="">
+ 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 class="">
+ no_verify=1
+ </td></tr><tr><td class="">
+ no_tty
+ </td><td class="">
+ ssh
+ </td><td class="">
+ 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 class="">
+ no_tty=1
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Remote_management_of_virtualized_guests-Remote_management_over_TLS_and_SSL.html"><strong>Prev</strong>21.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="sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM.html"><strong>Next</strong>Chapter 22. Overcommitting with KVM</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization.html
new file mode 100644
index 0000000..dfa2894
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization.html
@@ -0,0 +1,43 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>18.2. SELinux and virtualization</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization-Security_for_virtualization.html" title="Chapter 18. Security for virtualization" /><link rel="prev" href="chap-Virtualization-Security_for_virtualization.html" title="Chapter 18. Security for virtualization" /><link rel="next" href="sect-Virtualization-Security_for_virtualization-SELinux_considerations.html" title="18.3. SELinux" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-Security_for_virtualization.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Security_for_virtualization-SELinux_considerations.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">18.2. 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 attacker's abilities and works to prevent many common security exploits such as buffer overflow attacks and privilege escalation. It is because of these benefits that all Fedora systems should run with SELinux enabled and in enforcing mode.
+ </div><div class="formalpara" id="form-Virtualization-SELinux_and_virtualization-Adding_LVM_based_storage_with_SELinux_in_enforcing_mode"><h5 class="formalpara">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-SELinux_and_virtualization-Creating_and_mounting_a_logical_volume_on_a_virtualized_guest_with_SELinux_enabled"><h6>Procedure 18.1. Creating and mounting a logical volume on a virtualized guest with SELinux enabled</h6><ol class="1"><li class="step"><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 class="step"><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 class="step"><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 class="step"><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 class="step"><div class="para">
+ Set the correct SELinux type for the libvirt image location.
+ </div><pre class="screen"># semanage fcontext -a -t virt_image_t "/virtstorage(/.*)?"
+</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:virt_image_t:s0
+</pre></li><li class="step"><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">virt_image_t</code> (the <code class="command">restorecon</code> and <code class="command">setfiles</code> commands read the files in <code class="filename">/etc/selinux/targeted/contexts/files/</code>).
+ </div><pre class="screen"># restorecon -R -v /virtstorage
+</pre></li></ol></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Create a new file (using the <code class="command">touch</code> command) on the file system.
+ </div><pre class="screen"># touch <em class="replaceable"><code>/virtstorage/newfile</code></em></pre><div class="para">
+ Verify the file has been relabeled using the following command:
+ </div><pre class="screen"># sudo ls -Z <em class="replaceable"><code>/virtstorage</code></em>
+-rw-------. root root system_u:object_r:virt_image_t:s0 <em class="replaceable"><code>newfile</code></em></pre><div class="para">
+ The output shows that the new file has the correct attribute, <code class="filename">virt_image_t</code>.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization-Security_for_virtualization.html"><strong>Prev</strong>Chapter 18. 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="sect-Virtualization-Security_for_virtualization-SELinux_considerations.html"><strong>Next</strong>18.3. SELinux</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Security_for_virtualization-SELinux_considerations.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Security_for_virtualization-SELinux_considerations.html
new file mode 100644
index 0000000..d0adfde
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Security_for_virtualization-SELinux_considerations.html
@@ -0,0 +1,16 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>18.3. SELinux</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization-Security_for_virtualization.html" title="Chapter 18. Security for virtualization" /><link rel="prev" href="sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization.html" title="18.2. SELinux and virtualization" /><link rel="next" href="ch18s04.html" title="18.4. Virtualization firewall information" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch18s04.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Security_for_virtualization-SELinux_considerations"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">18.3. SELinux</h2></div></div></div><div class="para">
+ This section contains topics to consider when using SELinux with 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. Make sure that you have installed the <code class="filename">policycoreutilis-python</code> package (<code class="command">yum install policycoreutilis-python</code>) before running the command.
+ </div><pre class="screen"># semanage fcontext -a -t virt_image_t -f -b /dev/sda2
+# restorecon /dev/sda2
+</pre><div class="formalpara"><h5 class="formalpara" id="idm15986720">KVM and SELinux</h5>
+ The following table shows the SELinux Booleans which affect KVM when launched by libvirt.
+ </div><div class="segmentedlist"><div class="title"><strong><span class="title">KVM SELinux Booleans</span></strong></div><table border="0"><thead><tr class="segtitle"><th>SELinux Boolean</th><th>Description</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">virt_use_comm</td><td class="seg">Allow virt to use serial/parallel communication ports.</td></tr><tr class="seglistitem"><td class="seg">virt_use_fusefs</td><td class="seg">Allow virt to read fuse files.</td></tr><tr class="seglistitem"><td class="seg">virt_use_nfs</td><td class="seg">Allow virt to manage NFS files.</td></tr><tr class="seglistitem"><td class="seg">virt_use_samba</td><td class="seg">Allow virt to manage CIFS files.</td></tr><tr class="seglistitem"><td class="seg">virt_use_sanlock</td><td class="seg">Allow sanlock to manage virt lib files.</td></tr><tr class="seglistitem"><td class="seg">virt_use_sysfs</td><td class="seg">Allow virt to manage device configuration (PCI).</td></tr><tr class=
"seglistitem"><td class="seg">virt_use_xserver</td><td class="seg">Allow virtual machine to interact with the xserver.</td></tr><tr class="seglistitem"><td class="seg">virt_use_usb</td><td class="seg">Allow virt to use USB devices.</td></tr></tbody></table></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Security_for_virtualization-SELinux_and_virtualization.html"><strong>Prev</strong>18.2. SELinux 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="ch18s04.html"><strong>Next</strong>18.4. Virtualization firewall information</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Storage_Concepts-Volumes.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Storage_Concepts-Volumes.html
new file mode 100644
index 0000000..aaab497
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Storage_Concepts-Volumes.html
@@ -0,0 +1,63 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>26.2. Volumes</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Storage_Concepts.html" title="Chapter 26. Storage concepts" /><link rel="prev" href="chap-Virtualization_Administration_Guide-Storage_Concepts.html" title="Chapter 26. Storage concepts" /><link rel="next" href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html" title="Chapter 27. Storage pools" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="Documentatio
n Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Storage_Concepts.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Storage_Concepts-Volumes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">26.2. Volumes </h2></div></div></div><div class="para">
+ Storage pools are divided into storage volumes. Storage volumes are an abstraction of physical partitions, LVM logical volumes, file-based disk images and other storage types handled by libvirt. Storage volumes are presented to guests as local storage devices regardless of the underlying hardware.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm808928"> Referencing volumes</h5>
+ To reference a specific volume, three approaches are possible:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">The name of the volume and the storage pool</span></dt><dd><div class="para">
+ A volume may be referred to by name, along with an identifier for the storage pool it belongs in. On the virsh command line, this takes the form <em class="parameter"><code>--pool</code></em> <em class="replaceable"><code>storage_pool</code></em> <em class="replaceable"><code>volume_name</code></em>.
+ </div><div class="para">
+ For example, a volume named <em class="replaceable"><code>firstimage</code></em> in the <em class="replaceable"><code>guest_images</code></em> pool.
+ </div><pre class="screen"># virsh vol-info --pool <em class="replaceable"><code>guest_images</code></em> <em class="replaceable"><code>firstimage</code></em>
+Name: <em class="replaceable"><code>firstimage</code></em>
+Type: block
+Capacity: 20.00 GB
+Allocation: 20.00 GB
+
+virsh #</pre></dd><dt class="varlistentry"><span class="term">The full path to the storage on the host system</span></dt><dd><div class="para">
+ A volume may also be referred to by its full path on the file system. When using this approach, a pool identifier does not need to be included.
+ </div><div class="para">
+ For example, a volume named <em class="replaceable"><code>secondimage.img</code></em>, visible to the host system as <em class="replaceable"><code>/images/secondimage.img</code></em>. The image can be referred to as <em class="replaceable"><code>/images/secondimage.img</code></em>.
+ </div><pre class="screen"># virsh vol-info <em class="replaceable"><code>/images/secondimage.img</code></em>
+Name: <em class="replaceable"><code>secondimage.img</code></em>
+Type: file
+Capacity: 20.00 GB
+Allocation: 136.00 kB
+</pre></dd><dt class="varlistentry"><span class="term">The unique volume key</span></dt><dd><div class="para">
+ When a volume is first created in the virtualization system, a unique identifier is generated and assigned to it. The unique identifier is termed the <em class="firstterm">volume key</em>. The format of this volume key varies upon the storage used.
+ </div><div class="para">
+ When used with block based storage such as LVM, the volume key may follow this format:
+ </div><pre class="screen">c3pKz4-qPVc-Xf7M-7WNM-WJc8-qSiz-mtvpGn</pre><div class="para">
+ When used with file based storage, the volume key may instead be a copy of the full path to the volume storage.
+ </div><pre class="screen">/images/secondimage.img</pre><div class="para">
+ For example, a volume with the volume key of <em class="replaceable"><code>Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr</code></em>:
+ </div><pre class="screen"># virsh vol-info Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr
+Name: <em class="replaceable"><code>firstimage</code></em>
+Type: block
+Capacity: 20.00 GB
+Allocation: 20.00 GB
+</pre></dd></dl></div><div class="para">
+ <code class="command">virsh</code> provides commands for converting between a volume name, volume path, or volume key:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> vol-name </span></dt><dd><div class="para">
+ Returns the volume name when provided with a volume path or volume key.
+ </div><pre class="screen"># virsh vol-name /dev/<em class="replaceable"><code>guest_images</code></em>/<em class="replaceable"><code>firstimage</code></em>
+<em class="replaceable"><code>firstimage</code></em>
+# virsh vol-name <em class="replaceable"><code>Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr</code></em></pre></dd><dt class="varlistentry"><span class="term">vol-path</span></dt><dd><div class="para">
+ Returns the volume path when provided with a volume key, or a storage pool identifier and volume name.
+ </div><pre class="screen"># virsh vol-path Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr
+/dev/<em class="replaceable"><code>guest_images</code></em>/<em class="replaceable"><code>firstimage</code></em>
+# virsh vol-path --pool <em class="replaceable"><code>guest_images</code></em> <em class="replaceable"><code>firstimage</code></em>
+/dev/<em class="replaceable"><code>guest_images</code></em>/<em class="replaceable"><code>firstimage</code></em></pre></dd><dt class="varlistentry"><span class="term">The vol-key command</span></dt><dd><div class="para">
+ Returns the volume key when provided with a volume path, or a storage pool identifier and volume name.
+ </div><pre class="screen"># virsh vol-key /dev/<em class="replaceable"><code>guest_images</code></em>/<em class="replaceable"><code>firstimage</code></em>
+Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr
+# virsh vol-key --pool <em class="replaceable"><code>guest_images</code></em> <em class="replaceable"><code>firstimage</code></em>
+Wlvnf7-a4a3-Tlje-lJDa-9eak-PZBv-LoZuUr
+</pre></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Storage_Concepts.html"><strong>Prev</strong>Chapter 26. Storage concepts</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_Administration_Guide-Storage_Pools-Storage_Pools.html"><strong>Next</strong>Chapter 27. Storage pools</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Storage_Volumes-Cloning_volumes.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Storage_Volumes-Cloning_volumes.html
new file mode 100644
index 0000000..6f0e53d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Storage_Volumes-Cloning_volumes.html
@@ -0,0 +1,36 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>28.2. Cloning volumes</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Storage_Volumes.html" title="Chapter 28. Volumes" /><link rel="prev" href="chap-Virtualization_Administration_Guide-Storage_Volumes.html" title="Chapter 28. Volumes" /><link rel="next" href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html" title="28.3. Adding storage devices to guests" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="chap-Virtualization_Administration_Guide-Storage_Volumes.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Storage_Volumes-Cloning_volumes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">28.2. Cloning volumes</h2></div></div></div><div class="para">
+ The new volume will be allocated from storage in the same storage pool as the volume being cloned. The <code class="command"> virsh vol-clone</code> must have the <code class="literal">--pool</code> argument which dictates the name of the storage pool that contains the volume to be cloned. The rest of the command names the volume to be cloned (volume3) and the name of the new volume that was cloned (clone1). The <code class="command">virsh vol-list</code> command lists the volumes that are present in the storage pool (guest_images_disk).
+ </div><pre class="screen"># virsh vol-clone --pool <em class="replaceable"><code>guest_images_disk</code></em> <em class="replaceable"><code>volume3</code></em> <em class="replaceable"><code>clone1</code></em>
+Vol clone1 cloned from volume3
+
+# <code class="command">virsh vol-list <em class="replaceable"><code>guest_images_disk</code></em></code>
+Name Path
+-----------------------------------------
+volume1 /dev/sdb1
+volume2 /dev/sdb2
+volume3 /dev/sdb3
+clone1 /dev/sdb4
+
+
+# <code class="command">parted -s <em class="replaceable"><code>/dev/sdb</code></em> print</code>
+Model: ATA ST3500418AS (scsi)
+Disk /dev/sdb: 500GB
+Sector size (logical/physical): 512B/512B
+Partition Table: msdos
+
+Number Start End Size File system Name Flags
+1 4211MB 12.8GB 8595MB primary
+2 12.8GB 21.4GB 8595MB primary
+3 21.4GB 30.0GB 8595MB primary
+4 30.0GB 38.6GB 8595MB primary
+
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Storage_Volumes.html"><strong>Prev</strong>Chapter 28. Volumes </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-Virtualized_block_devices-Adding_storage_devices_to_guests.html"><strong>Next</strong>28.3. Adding storage devices to guests</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Storage_Volumes-Deleting_volumes.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Storage_Volumes-Deleting_volumes.html
new file mode 100644
index 0000000..4a5efe9
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Storage_Volumes-Deleting_volumes.html
@@ -0,0 +1,15 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>28.4. Deleting and removing volumes</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Storage_Volumes.html" title="Chapter 28. Volumes" /><link rel="prev" href="sect-Managing_storage_controllers_in_a_guest.html" title="28.3.3. Managing storage controllers in a guest" /><link rel="next" href="vhostmd.html" title="Chapter 29. The Virtual Host Metrics Daemon (vhostmd)" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-Managing_storage_controllers_in_a_guest.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="vhostmd.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Storage_Volumes-Deleting_volumes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">28.4. Deleting and removing volumes</h2></div></div></div><div class="para">
+ This section shows how to delete a disk volume from a block based storage pool using the <code class="command">virsh vol-delete</code> command. In this example, the volume is <em class="replaceable"><code>volume 1</code></em> and the storage pool is <em class="replaceable"><code>guest_images</code></em>.
+ </div><pre class="screen">
+# virsh vol-delete --pool guest_images volume1
+Vol volume1 deleted
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Managing_storage_controllers_in_a_guest.html"><strong>Prev</strong>28.3.3. Managing storage controllers in a 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="vhostmd.html"><strong>Next</strong>Chapter 29. The Virtual Host Metrics Daemon (vhos...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server.html
new file mode 100644
index 0000000..e3c7161
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server.html
@@ -0,0 +1,16 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.9. Configuring a VNC Server</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html" title="25.8. Disable SMART disk monitoring for guests" /><link rel="next" href="sect-gracefully-shut-down-guests.html" title="25.10. Gracefully shutting down guests" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-gracefully-shut-down-guests.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.9. 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">
+ Use the following step set up a dedicated VNC server session:
+ </div><div class="para">
+ If needed, Create and then 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. For more information on vnc server files refer to the <em class="citetitle">Fedora Installation Guide</em>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html"><strong>Prev</strong>25.8. 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-gracefully-shut-down-guests.html"><strong>Next</strong>25.10. Gracefully shutting down guests</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html
new file mode 100644
index 0000000..963d05a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests.html
@@ -0,0 +1,14 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.8. Disable SMART disk monitoring for guests</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="ch25s07.html" title="25.7. Improving guest response time" /><link rel="next" href="sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server.html" title="25.9. Configuring a VNC Server" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="ch25s07.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Tips_and_tricks-Disable_SMART_disk_monitoring_for_guests"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.8. Disable SMART disk monitoring for guests</h2></div></div></div><div class="para">
+ SMART disk monitoring can be safely disabled as virtual disks and the physical storage devices are managed by the host.
+ </div><pre class="screen"># service smartd stop
+# chkconfig --del smartd
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch25s07.html"><strong>Prev</strong>25.7. Improving guest response time</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-Tips_and_tricks-Configuring_a_VNC_Server.html"><strong>Next</strong>25.9. Configuring a VNC Server</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address.html
new file mode 100644
index 0000000..2f806f9
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address.html
@@ -0,0 +1,41 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.6. Generating a new unique MAC address</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="ch25s05.html" title="25.5. Setting KVM processor affinities" /><link rel="next" href="ch25s07.html" title="25.7. Improving guest response time" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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" h
ref="ch25s05.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch25s07.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Tips_and_tricks-Generating_a_new_unique_MAC_address"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.6. Generating a new unique MAC address</h2></div></div></div><div class="para">
+ In some cases you will need to generate a new and unique MAC address 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</pre><pre class="screen">#!/usr/bin/python
+# macgen.py script to generate a MAC address for guests
+#
+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" id="form-Virtualization-Generating_a_new_unique_MAC_address-Another_method_to_generate_a_new_MAC_for_your_guest"><h5 class="formalpara">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="ch25s05.html"><strong>Prev</strong>25.5. Setting KVM 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="ch25s07.html"><strong>Next</strong>25.7. Improving guest response time</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers.html
new file mode 100644
index 0000000..03fd313
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers.html
@@ -0,0 +1,156 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.11. Virtual machine timer management with libvirt</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="sect-gracefully-shut-down-guests.html" title="25.10. Gracefully shutting down guests" /><link rel="next" href="sect-perf-mon.html" title="25.12. Using PMU to monitor guest performance" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-gracefully-shut-down-guests.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-perf-mon.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.11. Virtual machine timer management with libvirt</h2></div></div></div><div class="para">
+ Accurate time keeping on guests is a key challenge for virtualization platforms. Different hypervisors attempt to handle the problem of time keeping in a variety of ways. Libvirt provides hypervisor independent configuration settings for time management, using the <clock> and <timer> elements in the domain XML. The domain XML can be edited using the <code class="command">virsh edit</code> command. See <a class="xref" href="form-Virtualization-Managing_guests_with_virsh-Creating_a_virtual_machine_XML_dump_configuration_file.html#form-Virtualization-Managing_guests_with_virsh-Editing_a_guests_configuration_file">Editing a guest's configuration file</a> for details.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm5367664"><clock></h5>
+ The clock element is used to determine how the guest clock is synchronized with the host clock. The clock element has the following attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idp13783072">offset</h5>
+ Determines how the guest clock is offset from the host clock. The offset attribute has the following possible values:
+ </div><div class="table" id="clock_element_offset_attribute_values"><h6>Table 25.1. Offset attribute values</h6><div class="table-contents"><table summary="Offset attribute values" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Value
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ utc
+ </td><td class="">
+ The guest clock will be synchronized to UTC when booted.
+ </td></tr><tr><td class="">
+ localtime
+ </td><td class="">
+ The guest clock will be synchronized to the host's configured timezone when booted, if any.
+ </td></tr><tr><td class="">
+ timezone
+ </td><td class="">
+ The guest clock will be synchronized to a given timezone, specified by the <em class="parameter"><code>timezone</code></em> attribute.
+ </td></tr><tr><td class="">
+ variable
+ </td><td class="">
+ The guest clock will be synchronized to an arbitrary offset from UTC. The delta relative to UTC is specified in seconds, using the <em class="parameter"><code>adjustment</code></em> attribute. The guest is free to adjust the Real Time Clock (RTC) over time and expect that it will be honored following the next reboot. This is in contrast to <em class="parameter"><code>utc</code></em> mode, where any RTC adjustments are lost at each reboot.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The value <span class="bold bold"><strong>utc</strong></span> is set as the clock offset in a virtual machine by default. However, if the guest clock is run with the <span class="bold bold"><strong>localtime</strong></span> value, the clock offset needs to be changed to a different value in order to have the guest clock synchronized with the host clock.
+ </div></div></div></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm6691888">timezone</h5>
+ The timezone to which the guest clock is to be synchronized.
+ </div></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm8193152">adjustment</h5>
+ The delta for guest clock synchronization. In seconds, relative to UTC.
+ </div></li></ul></div><div class="example"><h6>Example 25.1. Always synchronize to UTC</h6><div class="example-contents"><pre class="screen"><clock offset="utc" /></pre></div></div><br class="example-break" /><div class="example"><h6>Example 25.2. Always synchronize to the host timezone</h6><div class="example-contents"><pre class="screen"><clock offset="localtime" /></pre></div></div><br class="example-break" /><div class="example"><h6>Example 25.3. Synchronize to an arbitrary timezone</h6><div class="example-contents"><pre class="screen"><clock offset="timezone" timezone="Europe/Paris" /></pre></div></div><br class="example-break" /><div class="example"><h6>Example 25.4. Synchronize to UTC + arbitrary offset</h6><div class="example-contents"><pre class="screen"><clock offset="variable" adjustment="123456" /></pre></div></div><br class="example-break" /><div class="formalpara"><h5 class="formalpara" id="idm5374656"><timer></h5>
+ A clock element can have zero or more timer elements as children. The timer element specifies a time source used for guest clock synchronization. The timer element has the following attributes. Only the <em class="parameter"><code>name</code></em> is required, all other attributes are optional.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idp4728304">name</h5>
+ The name of the time source to use.
+ </div><div class="table" id="timer_element_name_attribute_values"><h6>Table 25.2. name attribute values</h6><div class="table-contents"><table summary="name attribute values" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Value
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ platform
+ </td><td class="">
+ The master virtual time source which may be used to drive the policy of other time sources.
+ </td></tr><tr><td class="">
+ pit
+ </td><td class="">
+ Programmable Interval Timer - a timer with periodic interrupts.
+ </td></tr><tr><td class="">
+ rtc
+ </td><td class="">
+ Real Time Clock - a continuously running timer with periodic interrupts.
+ </td></tr><tr><td class="">
+ hpet
+ </td><td class="">
+ High Precision Event Timer - multiple timers with periodic interrupts.
+ </td></tr><tr><td class="">
+ tsc
+ </td><td class="">
+ Time Stamp Counter - counts the number of ticks since reset, no interrupts.
+ </td></tr><tr><td class="">
+ kvmclock
+ </td><td class="">
+ KVM clock - recommended clock source for KVM guests. KVM pvclock, or kvm-clock lets guests read the host’s wall clock time.
+ </td></tr></tbody></table></div></div><br class="table-break" /></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm7143776">track</h5>
+ The <span class="emphasis"><em>track</em></span> attribute specifies what is tracked by the timer. Only valid for a name value of <em class="parameter"><code>platform</code></em> or <em class="parameter"><code>rtc</code></em>.
+ </div><div class="table" id="timer_element_track_attribute_values"><h6>Table 25.3. track attribute values</h6><div class="table-contents"><table summary="track attribute values" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Value
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ boot
+ </td><td class="">
+ Corresponds to old <span class="emphasis"><em>host</em></span> option, this is an unsupported tracking option.
+ </td></tr><tr><td class="">
+ guest
+ </td><td class="">
+ RTC always tracks guest time.
+ </td></tr><tr><td class="">
+ wall
+ </td><td class="">
+ RTC always tracks host time.
+ </td></tr></tbody></table></div></div><br class="table-break" /></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm21356896">tickpolicy</h5>
+ The policy used to pass ticks on to the guest.
+ </div><div class="table" id="timer_element_policy_attribute_values"><h6>Table 25.4. tickpolicy attribute values</h6><div class="table-contents"><table summary="tickpolicy attribute values" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Value
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ delay
+ </td><td class="">
+ Continue to deliver at normal rate (i.e. ticks are delayed).
+ </td></tr><tr><td class="">
+ catchup
+ </td><td class="">
+ Deliver at a higher rate to catch up.
+ </td></tr><tr><td class="">
+ merge
+ </td><td class="">
+ Ticks merged into one single tick.
+ </td></tr><tr><td class="">
+ discard
+ </td><td class="">
+ All missed ticks are discarded.
+ </td></tr></tbody></table></div></div><br class="table-break" /></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idp4873440">frequency</h5>
+ Used to set a fixed frequency, measured in Hz. This attribute is only relevant for a name value of <em class="parameter"><code>tsc</code></em>. All other timers operate at a fixed frequency (<em class="parameter"><code>pit</code></em>, <em class="parameter"><code>rtc</code></em>), or at a frequency fully controlled by the guest (<em class="parameter"><code>hpet</code></em>).
+ </div></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idm17799760">mode</h5>
+ Determines how the time source is exposed to the guest. This attribute is only relevant for a name value of <em class="parameter"><code>tsc</code></em>. All other timers are always emulated. Command is as follows: <code class="command"><timer name='tsc' frequency='NNN' mode='auto|native|emulate|smpsafe'/></code>. Mode definitions are given in the table.
+ </div><div class="table" id="timer_element_mode_attribute_values"><h6>Table 25.5. mode attribute values</h6><div class="table-contents"><table summary="mode attribute values" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Value
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ auto
+ </td><td class="">
+ Native if TSC is unstable, otherwise allow native TSC access.
+ </td></tr><tr><td class="">
+ native
+ </td><td class="">
+ Always allow native TSC access.
+ </td></tr><tr><td class="">
+ emulate
+ </td><td class="">
+ Always emulate TSC.
+ </td></tr><tr><td class="">
+ smpsafe
+ </td><td class="">
+ Always emulate TSC and interlock SMP
+ </td></tr></tbody></table></div></div><br class="table-break" /></li><li class="listitem"><div class="formalpara"><h5 class="formalpara" id="idp10644832">present</h5>
+ Used to override the default set of timers visible to the guest. For example, to enable or disable the HPET.
+ </div><div class="table" id="timer_element_present_attribute_values"><h6>Table 25.6. present attribute values</h6><div class="table-contents"><table summary="present attribute values" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Value
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ yes
+ </td><td class="">
+ Force this timer to the visible to the guest.
+ </td></tr><tr><td class="">
+ no
+ </td><td class="">
+ Force this timer to not be visible to the guest.
+ </td></tr></tbody></table></div></div><br class="table-break" /></li></ul></div><div class="example"><h6>Example 25.5. Clock synchronizing to local time with RTC and PIT timers, and the HPET timer disabled</h6><div class="example-contents"><pre class="screen"><clock offset="localtime">
+ <timer name="rtc" tickpolicy="catchup" track="guest" />
+ <timer name="pit" tickpolicy="delay" />
+ <timer name="hpet" present="no" />
+</clock></pre></div></div><br class="example-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-gracefully-shut-down-guests.html"><strong>Prev</strong>25.10. Gracefully shutting down 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-perf-mon.html"><strong>Next</strong>25.12. Using PMU to monitor guest performance</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM.html
new file mode 100644
index 0000000..f86ae8f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM.html
@@ -0,0 +1,44 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 22. Overcommitting with KVM</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt02.html" title="Part II. Administration" /><link rel="prev" href="sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes.html" title="21.3. Transport modes" /><link rel="next" href="chap-KSM.html" title="Chapter 23. KSM" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-Remote_management
_of_virtualized_guests-Transport_modes.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-KSM.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="sect-Virtualization-Tips_and_tricks-Overcommitting_with_KVM" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 22. 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 a number of system resources, with the net effect of less power, cooling, and investment in server hardware.
+ </div><div class="formalpara" id="form-Virtualization-Overcommitting_with_KVM-Overcommitting_memory"><h5 class="formalpara">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. KVM can allocate more memory for guests than the host has physically available. Overcommitting requires sufficient swap space for all guests and all host processes.
+ </div><div class="para">
+ With KVM, virtual machines are Linux processes. Guests on the KVM hypervisor do not have dedicated blocks of physical RAM assigned to them, instead guests function as Linux processes. The Linux kernel allocates each process memory when the process requests more memory. KVM guests are allocated memory when requested by the guest operating system.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Ensure that the total sum of swap and memory space is greater than or equal to all the memory configured for running guests. A shortage less than this sum can cause a guest to be forcibly shut down.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="idp3224656">Configuring swap for overcommitting memory</h5>
+ 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 the physical RAM of the host.
+ </div><div class="para">
+ Red Hat <a href="http://kbase.redhat.com/faq/docs/DOC-15252">Knowledgebase</a> has an article on safely and efficiently determining the size of the swap partition.
+ </div><div class="para">
+ The swap partition must be large enough to provide virtual memory for all guests and the host system.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The example below is provided as a guide for configuring swap only. The settings listed may not be appropriate for your environment.
+ </div></div></div><div class="example"><h6>Example 22.1. Memory overcommit example</h6><div class="example-contents"><div class="para">
+ ExampleServer1 has 32GB of physical RAM. The system is being configured to run 56 guests, each with 1GB of virtualized memory. The host system itself needs a maximum of 3GB (apart from the guests).
+ </div><div class="para">
+ The total maximum memory consumption is 56GB + 3GB = 59GB. The system's physical RAM is 32GB, which leaves 27GB. Therefore, the minimum amount of swap that the host should have configured is 27GB.
+ </div></div></div><br class="example-break" /><div class="para">
+ It is possible to overcommit memory over ten times the amount of physical RAM in the system. This only works with certain types of guest, for example, desktop virtualization with minimal intensive usage or running several identical guests with KSM. Configuring swap and memory overcommit is not a formula, each environment and setup is different. Your environment must be tested and customized to ensure stability and performance.
+ </div><div class="para">
+ For more information on KSM and overcommitting, refer to <a class="xref" href="chap-KSM.html">Chapter 23, <em>KSM</em></a>.
+ </div><div class="formalpara" id="form-Virtualization-Overcommitting_with_KVM-Overcommitting_virtualized_CPUs"><h5 class="formalpara">Overcommitting virtualized CPUs</h5>
+ The KVM hypervisor supports overcommitting virtualized CPUs. Virtualized CPUs can be overcommitted as far as load limits of 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 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 five VCPUs. Overcommitting single VCPU 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 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"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><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></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Remote_management_of_virtualized_guests-Transport_modes.html"><strong>Prev</strong>21.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-KSM.html"><strong>Next</strong>Chapter 23. KSM</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Using_qemu_img.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Using_qemu_img.html
new file mode 100644
index 0000000..08aa52a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Using_qemu_img.html
@@ -0,0 +1,103 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.3. Using qemu-img</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="sect-mem-dump-off.html" title="25.2. Guest memory allocation" /><link rel="next" href="sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions.html" title="25.4. Verifying virtualization extensions" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sect-mem-dump-off.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Tips_and_tricks-Using_qemu_img"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.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, modifying and verifying various file systems used by KVM. <code class="command">qemu-img</code> options and usages are listed below.
+ </div><div class="formalpara"><h5 class="formalpara" id="idp11733088">Check</h5>
+ Perform a consistency check on the disk image <em class="replaceable"><code>filename</code></em>.
+ </div><pre class="screen">
+# qemu-img check [-f <em class="parameter"><code>format</code></em>] <em class="replaceable"><code>filename</code></em></pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Only the <em class="replaceable"><code>qcow2</code></em> and <em class="replaceable"><code>vdi</code></em> formats support consistency checks.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="idp15561504">Commit</h5>
+ Commit any changes recorded in the specified file (<em class="replaceable"><code>filename</code></em>) to the file's base image with the <code class="command">qemu-img commit</code> command. Optionally, specify the file's format type (<em class="replaceable"><code>fmt</code></em>).
+ </div><pre class="screen"> # qemu-img commit [-f <em class="parameter"><code>fmt</code></em>] [-t <em class="parameter"><code>cache</code></em>] <em class="replaceable"><code>filename</code></em>
+</pre><div class="formalpara" id="form-Virtualization-Using_qemu_img-Convert_an_existing_image_to_another_format"><h5 class="formalpara">Convert</h5>
+ The <em class="parameter"><code>convert</code></em> option is used to convert one recognized image format to another image format.
+ </div><div class="para">
+ Command format:
+ </div><pre class="screen"># qemu-img convert [-c] [-p] [-f <em class="parameter"><code>fmt</code></em>] [-t <em class="parameter"><code>cache</code></em>] [-O <em class="parameter"><code>output_fmt</code></em>] [-o <em class="parameter"><code>options</code></em>] [-S <em class="parameter"><code>sparse_size</code></em>] <em class="replaceable"><code>filename</code></em> <em class="replaceable"><code>output_filename</code></em></pre><div class="para">
+ The <em class="parameter"><code>-p</code></em> parameter shows the progress of the command (optional and not for every command) and <em class="parameter"><code>-S</code></em> indicates the consecutive number of bytes that must contain only zeros for <code class="command">qemu-img</code> to create a sparse image during conversion.
+ </div><div class="para">
+ Convert the disk image <em class="parameter"><code>filename</code></em> to disk image <em class="parameter"><code>output_filename</code></em> using format <em class="parameter"><code>output_format</code></em>. The disk image can be optionally compressed with the <em class="parameter"><code>-c</code></em> option, or encrypted with the <em class="parameter"><code>-o</code></em> option by setting <code class="code">-o encryption</code>. Note that the options available with the <em class="parameter"><code>-o</code></em> parameter differ with the selected format.
+ </div><div class="para">
+ Only the <code class="filename">qcow2</code> format supports encryption or compression. <code class="filename">qcow2</code> encryption uses the AES format with secure 128-bit keys. <code class="filename">qcow2</code> compression is read-only, so if a compressed sector is converted from <code class="filename">qcow2</code> format, it is written to the new format as uncompressed data.
+ </div><div class="para">
+ Image conversion is also useful to get a 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" id="form-Virtualization-Using_qemu_img-Formatting_and_creating_new_images_or_devices"><h5 class="formalpara">Create</h5>
+ Create the new disk image <em class="replaceable"><code>filename</code></em> of size <em class="parameter"><code>size</code></em> and format <em class="parameter"><code>format</code></em>.
+ </div><pre class="screen"># qemu-img create [-f <em class="parameter"><code>format</code></em>] [-o <em class="replaceable"><code>options</code></em>] <em class="replaceable"><code>filename</code></em> [<em class="parameter"><code>size</code></em>]
+</pre><div class="para">
+ If a base image is specified with <code class="code">-o backing_file=<em class="replaceable"><code>filename</code></em></code>, the image will only record differences between itself and the base image. The backing file will not be modified unless you use the <code class="command">commit</code> command. No size needs to be specified in this case.
+ </div><div class="formalpara" id="form-Virtualization-Using_qemu_img-getting_image_information"><h5 class="formalpara">Info</h5>
+ The <code class="command">info</code> parameter displays information about a disk image <em class="replaceable"><code>filename</code></em>. The format for the <code class="command">info</code> option is as follows:
+ </div><pre class="screen"># qemu-img info [-f <em class="replaceable"><code>format</code></em>] <em class="replaceable"><code>filename</code></em></pre><div class="para">
+ This command is often used to discover the size reserved on disk which can be different from the displayed size. If snapshots are stored in the disk image, they are displayed also.
+ </div><div class="formalpara"><h5 class="formalpara" id="idm2165552">Rebase</h5>
+ Changes the backing file of an image.
+ </div><pre class="screen">
+# qemu-img rebase [-f <em class="replaceable"><code>fmt</code></em>] [-t <em class="replaceable"><code>cache</code></em>] [-p] [-u] -b <em class="replaceable"><code>backing_file</code></em> [-F <em class="replaceable"><code>backing_fmt</code></em>] <em class="replaceable"><code>filename</code></em></pre><div class="para">
+ The backing file is changed to <em class="replaceable"><code>backing_file</code></em> and (if the format of <em class="replaceable"><code>filename</code></em> supports the feature), the backing file format is changed to <em class="replaceable"><code>backing_format</code></em>.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Only the <em class="replaceable"><code>qcow2</code></em> format supports changing the backing file (rebase).
+ </div></div></div><div class="para">
+ There are two different modes in which <em class="replaceable"><code>rebase</code></em> can operate: <span class="bold bold"><strong>Safe</strong></span> and <span class="bold bold"><strong>Unsafe</strong></span>.
+ </div><div class="para">
+ <span class="bold bold"><strong>Safe mode</strong></span> is used by default and performs a real rebase operation. The new backing file may differ from the old one and the <code class="command">qemu-img rebase</code> command will take care of keeping the guest-visible content of <em class="replaceable"><code>filename</code></em> unchanged. In order to achieve this, any clusters that differ between <em class="replaceable"><code>backing_file</code></em> and old backing file of <em class="replaceable"><code>filename</code></em> are merged into <em class="replaceable"><code>filename</code></em> before making any changes to the backing file.
+ </div><div class="para">
+ Note that safe mode is an expensive operation, comparable to converting an image. The old backing file is required for it to complete successfully.
+ </div><div class="para">
+ <span class="bold bold"><strong>Unsafe mode</strong></span> is used if the <em class="replaceable"><code>-u</code></em> option is passed to <code class="command">qemu-img rebase</code>. In this mode, only the backing file name and format of <em class="replaceable"><code>filename</code></em> is changed, without any checks taking place on the file contents. Make sure the new backing file is specified correctly or the guest-visible content of the image will be corrupted.
+ </div><div class="para">
+ This mode is useful for renaming or moving the backing file. It can be used without an accessible old backing file. For instance, it can be used to fix an image whose backing file has already been moved or renamed.
+ </div><div class="formalpara"><h5 class="formalpara" id="idp1372048">Resize</h5>
+ Change the disk image <em class="replaceable"><code>filename</code></em> as if it had been created with size <em class="replaceable"><code>size</code></em>. Only images in raw format can be resized regardless of version. Fedora 17 and later adds the ability to grow (but not shrink) images in qcow2 format.
+ </div><div class="para">
+ Use the following to set the size of the disk image <em class="replaceable"><code>filename</code></em> to <em class="replaceable"><code>size</code></em> bytes:
+ </div><pre class="screen"># qemu-img resize <em class="replaceable"><code>filename</code></em> <em class="replaceable"><code>size</code></em></pre><div class="para">
+ You can also resize relative to the current size of the disk image. To give a size relative to the current size, prefix the number of bytes with <code class="literal">+</code> to grow, or <code class="literal">-</code> to reduce the size of the disk image by that number of bytes. Adding a unit suffix allows you to set the image size in kilobytes (K), megabytes (M), gigabytes (G) or terabytes (T).
+ </div><pre class="screen"># qemu-img resize <em class="replaceable"><code>filename</code></em> [+|-]<em class="replaceable"><code>size</code></em>[K|M|G|T]</pre><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Before using this command to shrink a disk image, you <span class="emphasis"><em>must</em></span> use file system and partitioning tools inside the VM itself to reduce allocated file systems and partition sizes accordingly. Failure to do so will result in data loss.
+ </div><div class="para">
+ After using this command to grow a disk image, you must use file system and partitioning tools inside the VM to actually begin using the new space on the device.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="idp15839952">Snapshot</h5>
+ List, apply, create, or delete an existing snapshot (<em class="replaceable"><code>snapshot</code></em>) of an image (<em class="replaceable"><code>filename</code></em>).
+ </div><pre class="screen"># qemu-img snapshot [ -l | -a <em class="replaceable"><code>snapshot</code></em> | -c <em class="replaceable"><code>snapshot</code></em> | -d <em class="replaceable"><code>snapshot</code></em> ] <em class="replaceable"><code>filename</code></em>
+</pre><div class="para">
+ <code class="command">-l</code> lists all snapshots associated with the specified disk image. The apply option, <code class="command">-a</code>, reverts the disk image (<em class="replaceable"><code>filename</code></em>) to the state of a previously saved <em class="replaceable"><code>snapshot</code></em>. <code class="command">-c</code> creates a snapshot (<em class="replaceable"><code>snapshot</code></em>) of an image (<em class="replaceable"><code>filename</code></em>). <code class="command">-d</code> deletes the specified snapshot.
+ </div><div class="formalpara" id="form-Virtualization-Using_qemu_img-Supported_formats"><h5 class="formalpara">Supported formats</h5>
+ <span class="application"><strong>qemu-img</strong></span> is designed to convert files to one of the following formats:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="command">raw</code> </span></dt><dd><div class="para">
+ Raw disk image format (default). This can be the fastest file-based format. 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 obtain the real size used by the image or <code class="command">ls -ls</code> on Unix/Linux. Although Raw images give optimal performance, only very basic features are available with a Raw image (no snapshots etc.).
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">qcow2</code> </span></dt><dd><div class="para">
+ QEMU image format, the most versatile format with the best feature set. Use it to have optional AES encryption, zlib-based compression, support of multiple VM snapshots, and smaller images, which are useful on file systems that do not support holes (non-NTFS file systems on Windows). Note that this expansive feature set comes at the cost of performance.
+ </div></dd></dl></div><div class="para">
+ Although only the formats above can be used to run on a guest or host machine, <span class="application"><strong>qemu-img</strong></span> also recognizes and supports the following formats in order to convert from them into either <code class="command">raw</code> or <code class="command">qcow2</code> format. The format of an image is usually detected automatically. In addition to converting these formats into <code class="command">raw</code> or <code class="command">qcow2</code> , they can be converted back from <code class="command">raw</code> or <code class="command">qcow2</code> to the original format.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="command">bochs</code></span></dt><dd><div class="para">
+ Bochs disk image format.
+ </div></dd><dt class="varlistentry"><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><dt class="varlistentry"><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 class="varlistentry"><span class="term"><code class="command">dmg</code></span></dt><dd><div class="para">
+ Mac disk image format.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">nbd</code></span></dt><dd><div class="para">
+ Network block device.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">parallels</code></span></dt><dd><div class="para">
+ Parallels virtualization disk image format.
+ </div></dd><dt class="varlistentry"><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 class="varlistentry"><span class="term"><code class="command">vdi</code></span></dt><dd><div class="para">
+ Oracle VM VirtualBox hard disk image format.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">vmdk</code></span></dt><dd><div class="para">
+ VMware 3 and 4 compatible image format.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">vpc</code></span></dt><dd><div class="para">
+ Windows Virtual PC disk image format. Also referred to as <code class="literal">vhd</code>, or Microsoft virtual hard disk image format.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">vvfat</code></span></dt><dd><div class="para">
+ Virtual VFAT disk image format.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-mem-dump-off.html"><strong>Prev</strong>25.2. Guest memory allocation</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-Tips_and_tricks-Verifying_virtualization_extensions.html"><strong>Next</strong>25.4. Verifying virtualization extensions</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions.html
new file mode 100644
index 0000000..647888b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions.html
@@ -0,0 +1,39 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.4. Verifying virtualization extensions</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="sect-Virtualization-Tips_and_tricks-Using_qemu_img.html" title="25.3. Using qemu-img" /><link rel="next" href="ch25s05.html" title="25.5. Setting KVM processor affinities" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-Tips_and_tricks-Using_qemu_img.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch25s05.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Tips_and_tricks-Verifying_virtualization_extensions"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.4. 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-x or AMD-V) are required for full virtualization.
+ </div><div class="procedure"><ol class="1"><li class="step"><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></li><li class="step"><div class="para">
+ Analyze the output.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The following output contains a <code class="computeroutput">vmx</code> entry indicating an Intel processor with the Intel VT-x extension:
+ </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></li><li class="listitem"><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></li></ul></div><div class="para">
+ If any output is received, the processor has the hardware virtualization extensions. However in some circumstances manufacturers disable the virtualization extensions in BIOS.
+ </div><div class="para">
+ The "<code class="computeroutput">flags:</code>" output content may appear multiple times, once for each hyperthread, core or CPU on 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-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html#proc-Virtualization-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS-Enabling_virtualization_extensions_in_BIOS">Procedure A.1, “Enabling virtualization extensions in BIOS”</a>.
+ </div></li><li class="step"><p class="title"><strong>Ensure KVM subsystem is loaded</strong></p><div class="para">
+ As an additional check, verify that the <code class="computeroutput">kvm</code> modules are loaded in the kernel:
+ </div><pre class="screen"># lsmod | grep kvm</pre><div class="para">
+ If the output includes <code class="computeroutput">kvm_intel</code> or <code class="computeroutput">kvm_amd</code> then the <code class="computeroutput">kvm</code> hardware virtualization modules are loaded and your system meets requirements.
+ </div></li></ol></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If the <span class="package">libvirt</span> package is installed, the <code class="command">virsh</code> command can output a full list of virtualization system capabilities. Run <code class="command">virsh capabilities </code> as root to receive the complete list.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Tips_and_tricks-Using_qemu_img.html"><strong>Prev</strong>25.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="ch25s05.html"><strong>Next</strong>25.5. Setting KVM processor affinities</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html
new file mode 100644
index 0000000..2902514
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html
@@ -0,0 +1,36 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.7. Enabling Intel VT-x and AMD-V virtualization hardware extensions in BIOS</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Troubleshooting.html" title="Appendix A. Troubleshooting" /><link rel="prev" href="live-migration-errors.html" title="A.6. Live Migration Errors" /><link rel="next" href="sect-Virtualization-Troubleshooting-KVM_networking_performance.html" title="A.8. KVM networking performance" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 c
lass="previous"><a accesskey="p" href="live-migration-errors.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Troubleshooting-KVM_networking_performance.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.7. Enabling Intel VT-x 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-x extensions can be disabled in the BIOS. Certain laptop vendors have disabled the Intel VT-x extensions by default in their CPUs.
+ </div><div class="para">
+ The virtualization extensions cannot be disabled in the BIOS for AMD-V.
+ </div><div class="para">
+ Refer to the following section for instructions on enabling disabled virtualization extensions.
+ </div><div class="para">
+ Verify the virtualization extensions are enabled in BIOS. The BIOS settings for Intel 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-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS-Enabling_virtualization_extensions_in_BIOS"><h6>Procedure A.1. Enabling virtualization extensions in BIOS</h6><ol class="1"><li class="step"><div class="para">
+ Reboot the computer and open the system's BIOS menu. This can usually be done by pressing the <span class="guibutton"><strong>delete</strong></span> key, the <span class="keycap"><strong>F1</strong></span> key or <span class="keycap"><strong>Alt</strong></span> and <span class="keycap"><strong>F4</strong></span> keys depending on the system.
+ </div></li><li class="step"><p class="title"><strong>Enabling the virtualization extensions in BIOS</strong></p><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Many of the steps below may vary depending on your motherboard, processor type, chipset and OEM. Refer to your system's accompanying documentation for the correct information on configuring your system.
+ </div></div></div><ol class="a"><li class="step"><div class="para">
+ Open the <span class="guilabel"><strong>Processor</strong></span> submenu The processor settings menu may be hidden in the <span class="guilabel"><strong>Chipset</strong></span>, <span class="guilabel"><strong>Advanced CPU Configuration</strong></span> or <span class="guilabel"><strong>Northbridge</strong></span>.
+ </div></li><li class="step"><div class="para">
+ Enable <span class="guilabel"><strong>Intel Virtualization Technology</strong></span> (also known as Intel VT-x). <span class="guilabel"><strong>AMD-V</strong></span> extensions cannot be disabled in the BIOS and should already be enabled. The virtualization extensions may be labeled <span class="guilabel"><strong>Virtualization Extensions</strong></span>, <span class="guilabel"><strong>Vanderpool</strong></span> or various other names depending on the OEM and system BIOS.
+ </div></li><li class="step"><div class="para">
+ Enable Intel VT-d or AMD IOMMU, if the options are available. Intel VT-d and AMD IOMMU are used for PCI device assignment.
+ </div></li><li class="step"><div class="para">
+ Select <span class="guilabel"><strong>Save & Exit</strong></span>.
+ </div></li></ol></li><li class="step"><div class="para">
+ Reboot the machine.
+ </div></li><li class="step"><div class="para">
+ When the machine has booted, run <code class="command">cat /proc/cpuinfo |grep -E "vmx|svm"</code>. Specifying <em class="parameter"><code>--color</code></em> is optional, but useful if you want the search term highlighted. 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="live-migration-errors.html"><strong>Prev</strong>A.6. Live Migration 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-Troubleshooting-KVM_networking_performance.html"><strong>Next</strong>A.8. KVM networking performance</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting-KVM_networking_performance.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting-KVM_networking_performance.html
new file mode 100644
index 0000000..663ab41
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting-KVM_networking_performance.html
@@ -0,0 +1,60 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.8. KVM networking performance</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Troubleshooting.html" title="Appendix A. Troubleshooting" /><link rel="prev" href="sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html" title="A.7. Enabling Intel VT-x and AMD-V virtualization hardware extensions in BIOS" /><link rel="next" href="sect-Virtualization-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard.html" title="A.9. Missing characters on guest console with Japanese keyboard" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-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-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Troubleshooting-KVM_networking_performance"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.8. KVM networking performance</h2></div></div></div><div class="para">
+ By default, KVM virtual machines are assigned a virtual Realtek 8139 (rtl8139) NIC (network interface controller) if they are Windows guests or the guest type is not specified. Fedora guests are assigned a virtio NIC by default.
+ </div><div class="para">
+ The rtl8139 virtualized NIC works fine in most environments. However, this device can suffer from performance degradation problems on some networks, for example, a 10 Gigabit Ethernet network.
+ </div><div class="para">
+ To improve performance switch to the para-virtualized network driver.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Note that the virtualized Intel PRO/1000 (<code class="systemitem">e1000</code>) driver is also supported as an emulated driver choice. To use the <code class="computeroutput">e1000</code> driver, replace <code class="computeroutput">virtio</code> in the procedure below with <code class="computeroutput">e1000</code>. For the best performance it is recommended to use the <code class="computeroutput">virtio</code> driver.
+ </div></div></div><div class="procedure"><h6>Procedure A.2. Switching to the virtio driver</h6><ol class="1"><li class="step"><div class="para">
+ Shutdown the guest operating system.
+ </div></li><li class="step"><div class="para">
+ Edit the guest's configuration file with the <code class="command">virsh</code> command (where <em class="parameter"><code>GUEST</code></em> is the guest's name):
+ </div><pre class="screen"># virsh edit <em class="parameter"><code>GUEST</code></em>
+</pre><div class="para">
+ The <code class="command">virsh edit</code> command uses the <code class="command">$EDITOR</code> shell variable to determine which editor to use.
+ </div></li><li class="step"><div class="para">
+ Find the network interface section of the configuration. This section resembles the snippet below:
+ </div><pre class="screen"><interface type='network'>
+ <span class="emphasis"><em>[output truncated]</em></span>
+ <model type='rtl8139' />
+</interface>
+</pre></li><li class="step"><div class="para">
+ Change the type attribute of the model element from <em class="parameter"><code>'rtl8139'</code></em> to <em class="parameter"><code>'virtio'</code></em>. This will change the driver from the rtl8139 driver to the e1000 driver.
+ </div><pre class="screen"><interface type='network'>
+ <span class="emphasis"><em>[output truncated]</em></span>
+ <model type=<em class="parameter"><code>'virtio'</code></em> />
+</interface>
+</pre></li><li class="step"><div class="para">
+ Save the changes and exit the text editor
+ </div></li><li class="step"><div class="para">
+ Restart the guest operating system.
+ </div></li></ol></div><div class="formalpara"><h5 class="formalpara" id="idm250704">Creating new guests using other network drivers</h5>
+ Alternatively, new guests can be created with a different network driver. This may be required if you are having difficulty installing guests over a network connection. This method requires you to have at least one guest already created (possibly installed from CD or DVD) to use as a template.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Create an XML template from an existing guest (in this example, named <em class="replaceable"><code>Guest1</code></em>):
+ </div><pre class="screen"># virsh dumpxml <em class="replaceable"><code>Guest1</code></em> > /tmp/<em class="replaceable"><code>guest-template</code></em>.xml
+</pre></li><li class="step"><div class="para">
+ Copy and edit the XML file and update the unique fields: virtual machine name, UUID, disk image, MAC address, and any other unique parameters. Note that you can delete the UUID and MAC address lines and virsh will generate a UUID and MAC address.
+ </div><pre class="screen"># cp /tmp/<em class="replaceable"><code>guest-template</code></em>.xml /tmp/<em class="replaceable"><code>new-guest</code></em>.xml
+# vi /tmp/<em class="replaceable"><code>new-guest</code></em>.xml
+</pre><div class="para">
+ Add the model line in the network interface section:
+ </div><pre class="screen"> <interface type='network'>
+ <span class="emphasis"><em>[output truncated]</em></span>
+ <model type='virtio' />
+</interface>
+</pre></li><li class="step"><div class="para">
+ Create the new virtual machine:
+ </div><pre class="screen"># virsh define /tmp/new-guest.xml
+# virsh start new-guest
+</pre></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS.html"><strong>Prev</strong>A.7. Enabling Intel VT-x 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-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard.html"><strong>Next</strong>A.9. Missing characters on guest console with Jap...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting-Loop_device_errors.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting-Loop_device_errors.html
new file mode 100644
index 0000000..cdb1625
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting-Loop_device_errors.html
@@ -0,0 +1,15 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.5. Loop device errors</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Troubleshooting.html" title="Appendix A. Troubleshooting" /><link rel="prev" href="apas04.html" title="A.4. Virtualization log files" /><link rel="next" href="live-migration-errors.html" title="A.6. Live Migration Errors" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="apas04.html"><stron
g>Prev</strong></a></li><li class="next"><a accesskey="n" href="live-migration-errors.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Troubleshooting-Loop_device_errors"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.5. 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 eight active loop devices. If more than eight file-based guests or loop devices are needed the number of loop devices configured can be adjusted in the <code class="filename">/etc/modprobe.d/</code>directory. Add the following line:
+ </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 use a 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="apas04.html"><strong>Prev</strong>A.4. Virtualization log 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="live-migration-errors.html"><strong>Next</strong>A.6. Live Migration Errors</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard.html
new file mode 100644
index 0000000..cf91bbd
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard.html
@@ -0,0 +1,38 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.9. Missing characters on guest console with Japanese keyboard</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Troubleshooting.html" title="Appendix A. Troubleshooting" /><link rel="prev" href="sect-Virtualization-Troubleshooting-KVM_networking_performance.html" title="A.8. KVM networking performance" /><link rel="next" href="sec-known-issues-windows-xp-guests.html" title="A.10. Known Windows XP guest issues" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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><u
l class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Troubleshooting-KVM_networking_performance.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-known-issues-windows-xp-guests.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Troubleshooting-Missing_Characters_Guest_Console_Japanese_Keyboard"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.9. Missing characters on guest console with Japanese keyboard</h2></div></div></div><div class="para">
+ On a Fedora host, connecting a Japanese keyboard locally to a machine may result in typed characters such as the underscore (the <span class="bold bold"><strong>_</strong></span> character) not being displayed correctly in guest consoles. This occurs because the required keymap is not set correctly by default.
+ </div><div class="para">
+ When Using Fedora with Red Hat Enterprise Linux 6 guests, there is usually no error message produced when pressing the associated key. However, Red Hat Enterprise Linux 4 and Red Hat Enterprise Linux 5 guests may display an error similar to the following:
+ </div><pre class="screen">
+atkdb.c: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0).
+atkbd.c: Use 'setkeycodes 00 <keycode>' to make it known.
+</pre><div class="para">
+ To fix this issue in <code class="command">virt-manager</code>, perform the following steps:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Open the affected guest in <code class="command">virt-manager</code>.
+ </div></li><li class="listitem"><div class="para">
+ Click <span class="guimenu"><strong>View</strong></span> → <span class="guisubmenu"><strong>Details</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ Select <span class="guilabel"><strong>Display VNC</strong></span> in the list.
+ </div></li><li class="listitem"><div class="para">
+ Change <span class="bold bold"><strong>Auto</strong></span> to <span class="bold bold"><strong>ja</strong></span> in the <span class="guilabel"><strong>Keymap</strong></span> pull-down menu.
+ </div></li><li class="listitem"><div class="para">
+ Click the <span class="guilabel"><strong>Apply</strong></span> button.
+ </div></li></ul></div><div class="para">
+ Alternatively, to fix this issue using the <code class="command">virsh edit</code> command on the target guest:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Run <code class="command">virsh edit <target guest></code>
+ </div></li><li class="listitem"><div class="para">
+ Add the following attribute to the <graphics> tag: <span class="bold bold"><strong>keymap='ja'</strong></span>. For example:
+<pre class="screen">
+ <graphics type='vnc' port='-1' autoport='yes' <span class="bold bold"><strong>keymap='ja'</strong></span>/>
+</pre>
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Troubleshooting-KVM_networking_performance.html"><strong>Prev</strong>A.8. KVM networking performance</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="sec-known-issues-windows-xp-guests.html"><strong>Next</strong>A.10. Known Windows XP guest issues</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles.html
new file mode 100644
index 0000000..0044434
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles.html
@@ -0,0 +1,38 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.3. Troubleshooting with serial consoles</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Troubleshooting.html" title="Appendix A. Troubleshooting" /><link rel="prev" href="apas02.html" title="A.2. kvm_stat" /><link rel="next" href="apas04.html" title="A.4. Virtualization log files" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="apas02.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="apas04.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Troubleshooting_-Troubleshooting_with_serial_consoles"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.3. 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 Fedora virtualization kernels and their guests.
+ </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 class="listitem"><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. Append the following to the <em class="parameter"><code>kernel</code></em> line: <em class="parameter"><code>console=tty0 console=ttyS0,115200</code></em>.
+ </div><pre class="screen">title Fedora Server (2.6.32-36.x86-64)
+ root (hd0,0)
+ kernel /vmlinuz-2.6.32-36.x86-64 ro root=/dev/volgroup00/logvol00 \
+ <em class="parameter"><code>console=tty0 console=ttyS0,115200</code></em>
+ initrd /initrd-2.6.32-36.x86-64.img
+</pre><div class="para">
+ Reboot the guest.
+ </div><div class="para">
+ On the host, 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 guest console window, select <span class="guilabel"><strong>Serial 1</strong></span> in <span class="guilabel"><strong>Text Consoles</strong></span> from the <span class="guilabel"><strong>View</strong></span> menu.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apas02.html"><strong>Prev</strong>A.2. kvm_stat</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="apas04.html"><strong>Next</strong>A.4. Virtualization log files</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest.html
new file mode 100644
index 0000000..2e8c885
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest.html
@@ -0,0 +1,22 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.8. Attaching a virtual network to a guest</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html" title="Appendix H. Virtual Networking" /><link rel="prev" href="sect-Virtualization-Virtual_Networking-Creating_a_virtual_network.html" title="H.7. Creating a virtual network" /><link rel="next" href="sect-attch-nic-physdev.html" title="H.9. Directly attaching to physical interface" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-Virtual_Networking-Creating_a_virtual_network.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-attch-nic-physdev.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">H.8. Attaching a virtual network to a guest</h2></div></div></div><div class="para">
+ To attach a virtual network to a guest:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ In the <span class="guilabel"><strong>Virtual Machine Manager</strong></span> window, highlight the guest that will have the network assigned.
+ </div><div class="figure" id="guest4network"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt1.png" width="444" alt="Selecting a virtual machine to display" /></div></div><h6>Figure H.20. Selecting a virtual machine to display</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ From the Virtual Machine Manager <span class="guilabel"><strong>Edit</strong></span> menu, select <span class="guilabel"><strong>Virtual Machine Details</strong></span>.
+ </div><div class="figure" id="showdetails"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt11.png" width="444" alt="Displaying the virtual machine details" /></div></div><h6>Figure H.21. Displaying the virtual machine details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Click the <span class="guilabel"><strong>Add Hardware</strong></span> button on the Virtual Machine Details window.
+ </div><div class="figure" id="vmdetailswindow"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-Virt-Manager-fig31pt4.png" width="444" alt="The Virtual Machine Details window" /></div></div><h6>Figure H.22. The Virtual Machine Details window</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ In the <span class="guilabel"><strong>Add new virtual hardware</strong></span> window, select <span class="guilabel"><strong>Network</strong></span> from the left pane, and select your network name (<span class="emphasis"><em>network1</em></span> in this example) from the <span class="guilabel"><strong>Host device</strong></span> menu and click <span class="guibutton"><strong>Finish</strong></span>.
+ </div><div class="figure" id="select_network"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic10.png" width="444" alt="Select your network from the Add new virtual hardware window" /></div></div><h6>Figure H.23. Select your network from the Add new virtual hardware window</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ The new network is now displayed as a virtual network interface that will be presented to the guest upon launch.
+ </div><div class="figure" id="newnetworkishown"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic11.png" width="444" alt="New network shown in guest hardware list" /></div></div><h6>Figure H.24. New network shown in guest hardware list</h6></div><br class="figure-break" /></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Virtual_Networking-Creating_a_virtual_network.html"><strong>Prev</strong>H.7. 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="sect-attch-nic-physdev.html"><strong>Next</strong>H.9. Directly attaching to physical interface</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtual_Networking-Creating_a_virtual_network.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtual_Networking-Creating_a_virtual_network.html
new file mode 100644
index 0000000..a1a8d43
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtual_Networking-Creating_a_virtual_network.html
@@ -0,0 +1,32 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.7. Creating a virtual network</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html" title="Appendix H. Virtual Networking" /><link rel="prev" href="sect-Virtualization-Virtual_Networking-Managing_a_virtual_network.html" title="H.6. Managing a virtual network" /><link rel="next" href="sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest.html" title="H.8. Attaching a virtual network to a guest" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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/image
s/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Virtual_Networking-Managing_a_virtual_network.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Virtual_Networking-Creating_a_virtual_network"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">H.7. 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 class="step"><div class="para">
+ Open the <span class="guilabel"><strong>Virtual Networks</strong></span> tab from within the <span class="guilabel"><strong>Connection Details</strong></span> menu. Click the <span class="guibutton"><strong>Add Network</strong></span> button, identified by a plus sign (+) icon. For more information, refer to <a class="xref" href="sect-Virtualization-Virtual_Networking-Managing_a_virtual_network.html">Section H.6, “Managing a virtual network”</a>.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Virtual_network_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic1.png" width="444" alt="Virtual network configuration" /></div></div><h6>Figure H.13. 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> window. Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Creating_a_new_virtual_network"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic2.png" width="444" alt="Creating a new virtual network" /></div></div><h6>Figure H.14. Creating a new virtual network</h6></div><br class="figure-break" /></li><li class="step"><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_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Naming_your_virtual_network"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic3.png" width="444" alt="Naming your virtual network" /></div></div><h6>Figure H.15. Naming your virtual network</h6></div><br class="figure-break" /></li><li class="step"><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_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Choosing_an_IPv4_address_space"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic4.png" width="444" alt="Choosing an IPv4 address space" /></div></div><h6>Figure H.16. Choosing an IPv4 address space</h6></div><br class="figure-break" /></li><li class="step"><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_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Selecting_the_DHCP_range"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic5.png" width="444" alt="Selecting the DHCP range" /></div></div><h6>Figure H.17. Selecting the DHCP range</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ Select how the virtual network should connect to the physical network.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Connecting_to_physical_network"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic6.png" width="444" alt="Connecting to physical network" /></div></div><h6>Figure H.18. 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>Any physical device</strong></span> or a specific physical device. Also select whether the <span class="guilabel"><strong>Mode</strong></span> should be <span class="guilabel"><strong>NAT</strong></span> or <span class="guilabel"><strong>Routed</strong></span>.
+ </div><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><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_Administration_Guide-Virtual_Networking-Creating_a_virtual_network-Ready_to_create_network"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic7.png" width="444" alt="Ready to create network" /></div></div><h6>Figure H.19. Ready to create network</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ The new virtual network is now available in the <span class="guilabel"><strong>Virtual Networks</strong></span> tab of the <span class="guilabel"><strong>Connection Details</strong></span> window.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Virtual_Networking-Managing_a_virtual_network.html"><strong>Prev</strong>H.6. 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="sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest.html"><strong>Next</strong>H.8. Attaching a virtual network to a guest</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtual_Networking-Example_scenarios.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtual_Networking-Example_scenarios.html
new file mode 100644
index 0000000..4b5438f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtual_Networking-Example_scenarios.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.5. Examples of common scenarios</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html" title="Appendix H. Virtual Networking" /><link rel="prev" href="sect-the-Default_Configuration-libvirt.html" title="H.4. The default configuration" /><link rel="next" href="sub-sect-nat-mode.html" title="H.5.2. NAT mode" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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" h
ref="sect-the-Default_Configuration-libvirt.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-nat-mode.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Virtual_Networking-Example_scenarios"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">H.5. Examples of common scenarios</h2></div></div></div><div class="para">
+ This section demonstrates different virtual networking modes and provides some example scenarios.
+ </div><div class="section" id="sub-sect-routed-mode"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.5.1. Routed mode</h3></div></div></div><div class="formalpara"><h5 class="formalpara" id="idm20377696">DMZ</h5>
+ Consider a network where one or more nodes are placed in a controlled subnetwork for security reasons. The deployment of a special subnetwork such as this is a common practice, and the subnetwork is known as a DMZ. Refer to the following diagram for more details on this layout:
+ </div><div class="figure" id="dmz-example-diagram"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-09-routed-mode-DMZ.png" width="444" alt="Sample DMZ configuration" /></div></div><h6>Figure H.8. Sample DMZ configuration</h6></div><br class="figure-break" /><div class="para">
+ Hosts in a DMZ typically provide services to WAN (external) hosts as well as LAN (internal) hosts. As this requires them to be accessible from multiple locations, and considering that these locations are controlled and operated in different ways based on their security and trust level, routed mode is the best configuration for this environment.
+ </div><div class="formalpara"><h5 class="formalpara" id="idp17982400">Virtual Server hosting</h5>
+ Consider a virtual server hosting company that has several hosts, each with two physical network connections. One interface is used for management and accounting, the other is for the virtual machines to connect through. Each guest has its own public IP address, but the hosts use private IP address as management of the guests can only be performed by internal administrators. Refer to the following diagram to understand this scenario:
+ </div><div class="figure" id="virt-serv-host-diagram"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-10-routed-mode-datacenter.png" width="444" alt="Virtual server hosting sample configuration" /></div></div><h6>Figure H.9. Virtual server hosting sample configuration</h6></div><br class="figure-break" /><div class="para">
+ When the host has a public IP address and the virtual machines have static public IP addresses, bridged networking cannot be used, as the provider only accepts packets from the MAC address of the public host. The following diagram demonstrates this:
+ </div><div class="figure" id="static-ip-diagram"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-11-router-mode-mac-restricted.png" width="444" alt="Virtual server using static IP addresses" /></div></div><h6>Figure H.10. Virtual server using static IP addresses</h6></div><br class="figure-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-the-Default_Configuration-libvirt.html"><strong>Prev</strong>H.4. The default 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="sub-sect-nat-mode.html"><strong>Next</strong>H.5.2. NAT mode</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtual_Networking-Managing_a_virtual_network.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtual_Networking-Managing_a_virtual_network.html
new file mode 100644
index 0000000..0ccda61
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtual_Networking-Managing_a_virtual_network.html
@@ -0,0 +1,18 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.6. Managing a virtual network</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html" title="Appendix H. Virtual Networking" /><link rel="prev" href="sub-sect-isolated-mode.html" title="H.5.3. Isolated mode" /><link rel="next" href="sect-Virtualization-Virtual_Networking-Creating_a_virtual_network.html" title="H.7. Creating a virtual network" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sect-isolated-mode.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Virtual_Networking-Creating_a_virtual_network.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Virtual_Networking-Managing_a_virtual_network"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">H.6. 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 class="step"><div class="para">
+ From the <span class="guilabel"><strong>Edit</strong></span> menu, select <span class="guilabel"><strong>Connection Details</strong></span>.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Selecting_a_hosts_details"><div class="figure-contents"><div class="mediaobject"><img src="images/vmm_vnet_menuselect.png" width="444" alt="Selecting a host's details" /></div></div><h6>Figure H.11. Selecting a host's details</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ This will open the <span class="guimenu"><strong>Connection Details</strong></span> menu. Click the <span class="guilabel"><strong>Virtual Networks</strong></span> tab.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-admin-18pt7-pic1.png" width="444" alt="Virtual network configuration" /></div></div><h6>Figure H.12. Virtual network configuration</h6></div><br class="figure-break" /></li><li class="step"><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="sub-sect-isolated-mode.html"><strong>Prev</strong>H.5.3. Isolated mode</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-Virtual_Networking-Creating_a_virtual_network.html"><strong>Next</strong>H.7. Creating a virtual network</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html
new file mode 100644
index 0000000..ba0555c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html
@@ -0,0 +1,99 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>28.3. Adding storage devices to guests</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Storage_Volumes.html" title="Chapter 28. Volumes" /><link rel="prev" href="sect-Virtualization-Storage_Volumes-Cloning_volumes.html" title="28.2. Cloning volumes" /><link rel="next" href="sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html" title="28.3.2. Adding hard drives and other block devices to a guest" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-Storage_Volumes-Cloning_volumes.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">28.3. Adding storage devices to guests</h2></div></div></div><div class="para">
+ This section covers adding storage devices to a guest. Additional storage can only be added as needed.
+ </div><div class="section" id="sect-Virtualization-Adding_storage_devices_to_guests-Adding_file_based_storage_to_a_guest"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">28.3.1. Adding file based storage to a guest</h3></div></div></div><div class="para">
+ File-based storage is a collection of files that are stored on the hosts file system that act as virtualized hard drives for guests. To add file-based storage, perform the following steps:
+ </div><div class="procedure" id="proc-Virtualization-Adding_storage_devices"><h6>Procedure 28.1. Adding file-based storage</h6><ol class="1"><li class="step"><div class="para">
+ Create a storage file or use an existing file (such as an ISO file). Note that both of the following commands create a 4GB file which can be used as additional storage for a guest:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Pre-allocated files are recommended for file-based storage images. Create a pre-allocated file using the following <code class="command">dd</code> command as shown:
+ </div><pre class="screen"># dd if=/dev/zero of=/var/lib/libvirt/images/FileName.iso bs=1M count=4096</pre></li><li class="listitem"><div class="para">
+ Alternatively, create a sparse file instead of a pre-allocated file. Sparse files are created much faster and can be used for testing, but are not recommended for production environments due to data integrity and performance issues.
+ </div><pre class="screen"># dd if=/dev/zero of=/var/lib/libvirt/images/FileName.iso bs=1M seek=4096 count=0</pre></li></ul></div></li><li class="step"><div class="para">
+ Create the additional storage by writing a <em class="replaceable"><code><disk></code></em> element in a new file. In this example, this file will be known as <code class="filename">NewStorage.xml</code>.
+ </div><div class="para">
+ A <code class="literal"><disk></code> element describes the source of the disk, and a device name for the virtual block device. The device name should be unique across all devices in the guest, and identifies the bus on which the guest will find the virtual block device. The following example defines a virtio block device whose source is a file-based storage container named <code class="filename">FileName.img</code>:
+ </div><pre class="screen">
+<disk type='file' device='disk'>
+ <driver name='qemu' type='raw' cache='none'/>
+ <source file='/var/lib/libvirt/images/FileName.img'/>
+ <target dev='vdb'/>
+</disk>
+</pre><div class="para">
+ Device names can also start with "hd" or "sd", identifying respectively an IDE and a SCSI disk. The configuration file can also contain an <code class="literal"><address></code> sub-element that specifies the position on the bus for the new device. In the case of virtio block devices, this should be a PCI address. Omitting the <code class="literal"><address></code> sub-element lets libvirt locate and assign the next available PCI slot.
+ </div></li><li class="step"><div class="para">
+ Attach the CD-ROM as follows:
+ </div><pre class="screen">
+<disk type='file' device='cdrom'>
+ <driver name='qemu' type='raw' cache='none'/>
+ <source file='/var/lib/libvirt/images/FileName.iso'/>
+ <readonly/>
+ <target dev='hdc'/>
+</disk >
+</pre></li><li class="step"><div class="para">
+ Add the device defined in <code class="filename">NewStorage.xml</code> with your guest (<code class="literal">Guest1</code>):
+ </div><pre class="screen"># virsh attach-device --config Guest1 ~/NewStorage.xml</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ This change will only apply after the guest has been destroyed and restarted. In addition, persistent devices can only be added to a persistent domain, that is a domain whose configuration has been saved with <code class="command"> virsh define </code> command.
+ </div></div></div><div class="para">
+ If the guest is running, and you want the new device to be added temporarily until the guest is destroyed, omit the <code class="literal">--config</code> option:
+ </div><pre class="screen"># virsh attach-device Guest1 ~/NewStorage.xml</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The <code class="command">virsh</code> command allows for an <code class="command">attach-disk</code> command that can set a limited number of parameters with a simpler syntax and without the need to create an XML file. The <code class="command">attach-disk</code> command is used in a similar manner to the <code class="command">attach-device</code> command mentioned previously, as shown:
+ </div><pre class="screen">
+# virsh attach-disk Guest1 /var/lib/libvirt/images/FileName.iso vdb --cache none
+</pre><div class="para">
+ Note that the <code class="command">virsh attach-disk</code> command also accepts the <code class="literal">--config</code> option.
+ </div></div></div></li><li class="step"><div class="para">
+ Start the guest machine (if it is currently not running):
+ </div><pre class="screen"># virsh start Guest1</pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The following steps are Linux guest specific. Other operating systems handle new storage devices in different ways. For other systems, refer to that operating system's documentation.
+ </div></div></div></li><li class="step" id="step-partition_disk"><p class="title"><strong>Partitioning the disk drive</strong></p><div class="para">
+ The guest now has a hard disk device called <code class="filename">/dev/vdb</code>. If required, partition this disk drive and format the partitions. If you do not see the device that you added, then it indicates that there is an issue with the disk hotplug in your guest's operating system.
+ </div><ol class="a"><li class="step"><div class="para">
+ Start <code class="command">fdisk</code> for the new device:
+ </div><pre class="screen">
+# fdisk /dev/vdb
+Command (m for help):
+</pre></li><li class="step"><div class="para">
+ Type <em class="parameter"><code>n</code></em> for a new partition.
+ </div></li><li class="step"><div class="para">
+ The following appears:
+ </div><pre class="screen">
+Command action
+e extended
+p primary partition (1-4)
+</pre><div class="para">
+ Type <em class="parameter"><code>p</code></em> for a primary partition.
+ </div></li><li class="step"><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): 1</pre></li><li class="step"><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 class="step"><div class="para">
+ Select the size of the partition. In this example the entire disk is allocated by pressing <code class="command">Enter</code>.
+ </div><pre class="screen">Last cylinder or +size or +sizeM or +sizeK (2-400, default 400):</pre></li><li class="step"><div class="para">
+ Enter <code class="command">t</code> to configure the partition type.
+ </div><pre class="screen">Command (m for help): t</pre></li><li class="step"><div class="para">
+ Select the partition you created in the previous steps. In this example, the partition number is <code class="command">1</code> as there was only one partition created and fdisk automatically selected partition 1.
+ </div><pre class="screen">Partition number (1-4): 1</pre></li><li class="step"><div class="para">
+ Enter <code class="command">83</code> for a Linux partition.
+ </div><pre class="screen">Hex code (type L to list codes): 83</pre></li><li class="step"><div class="para">
+ Enter <code class="command">w</code> to write changes and quit.
+ </div><pre class="screen">
+Command (m for help): w
+</pre></li><li class="step"><div class="para">
+ Format the new partition with the <code class="systemitem">ext3</code> file system.
+ </div><pre class="screen"># mke2fs -j /dev/vdb1</pre></li></ol></li><li class="step"><div class="para">
+ Create a mount directory, and mount the disk on the guest. In this example, the directory is located in <em class="replaceable"><code>myfiles</code></em>.
+ </div><pre class="screen">
+# mkdir /myfiles
+# mount /dev/vdb1 /myfiles
+</pre><div class="para">
+ The guest now has an additional virtualized file-based storage device. Note however, that this storage will not mount persistently across reboot unless defined in the guest's <code class="filename">/etc/fstab</code> file:
+ </div><pre class="screen">/dev/vdb1 <em class="replaceable"><code>/myfiles</code></em> ext3 defaults 0 0</pre></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Storage_Volumes-Cloning_volumes.html"><strong>Prev</strong>28.2. Cloning volumes</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-Adding_storage_devices_to_guests-Adding_hard_drives_and_other_block_devices_to_a_guest.html"><strong>Next</strong>28.3.2. Adding hard drives and other block device...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install.html
new file mode 100644
index 0000000..f697415
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install.html
@@ -0,0 +1,37 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.2. Creating guests with virt-install</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html" title="Chapter 6. Guest virtual machine installation overview" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html" title="Chapter 6. Guest virtual machine installation overview" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html" title="6.3. Creating guests with virt-manager" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img s
rc="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_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Creating_guests_with_virt_install"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.2. 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 guest virtual machines 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 that can be passed on the command line. To see a complete list of options run the following command:
+ </div><pre class="screen"># virt-install --help</pre><div class="para">
+ Note that you need root privileges in order for <code class="command">virt-install</code> commands to complete successfully. 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>--graphics</code></em> option which allows graphical installation of a virtual machine.
+ </div><div class="example" id="exam-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Using_virt_install_with_KVM_to_create_a_Red_Hat_Enterprise_Linux_3_guest"><h6>Example 6.1. Using virt-install to install a Fedora 19 guest virtual machine</h6><div class="example-contents"><div class="para">
+ This example creates a Fedora 19 guest:
+ </div><pre class="screen">virt-install \
+ --name=guest1-rhel5-64 \
+ --file=/var/lib/libvirt/images/guest1-rhel5-64.dsk \
+ --file-size=8 \
+ --nonsparse --graphics spice \
+ --vcpus=2 --ram=2048 \
+ --location=http://example1.com/installation_tree/RHEL5.6-Server-x86_64/os \
+ --network bridge=br0 \
+ --os-type=linux \
+ --os-variant=rhel5.4</pre></div></div><br class="example-break" /><div class="para">
+ Ensure that you select the correct <em class="parameter"><code>os-type</code></em> for your operating system when running this command.
+ </div><div class="para">
+ Refer to <code class="command">man virt-install</code> for more examples.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ When installing a Windows guest with <code class="command">virt-install</code>, the <code class="command">--os-type=<em class="replaceable"><code>windows</code></em></code> option is recommended. This option prevents the CD-ROM from disconnecting when rebooting during the installation procedure. The <code class="command">--os-variant</code> option further optimizes the configuration for a specific guest operating system.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html"><strong>Prev</strong>Chapter 6. Guest virtual machine installation ove...</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_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html"><strong>Next</strong>6.3. Creating guests with virt-manager</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE.html
new file mode 100644
index 0000000..49e7cb2
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE.html
@@ -0,0 +1,28 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.4. Installing guest virtual machines with PXE</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html" title="Chapter 6. Guest virtual machine installation overview" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html" title="6.3. Creating guests with virt-manager" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html" title="Chapter 7. Installing a Red Hat Enterprise Linux 6 guest virtual machine on a Red Hat Enterprise Linux 6 host" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.4. Installing guest virtual machines with PXE</h2></div></div></div><div class="formalpara"><h5 class="form
alpara" id="idm8196848">Requirements</h5>
+ PXE guest installation requires a PXE server running on the same subnet as the guest virtual machines you wish to install. The method of accomplishing this depends on how the virtual machines are connected to the network. Contact Support if you require assistance setting up a PXE server.
+ </div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE-PXE_installation_with_virt_install"><h5 class="formalpara">PXE installation with virt-install</h5>
+ <code class="command">virt-install</code> PXE installations require both the <code class="command">--network=bridge:installation</code> parameter, where <em class="parameter"><code>installation</code></em> is the name of your bridge, and the <em class="parameter"><code>--pxe</code></em> parameter.
+ </div><div class="para">
+ By default, if no network is found, the guest virtual machine attempts to boot from alternative bootable devices. If there is no other bootable device found, the guest pauses. You can use the <span class="application"><strong>qemu-kvm</strong></span> boot parameter <em class="parameter"><code>reboot-timeout</code></em> to allow the guest to retry booting if no bootable device is found, like so:
+ </div><pre class="screen"># qemu-kvm -boot reboot-timeout=1000</pre><div class="example" id="exam-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE-PXE_installation_with_virt_install"><h6>Example 6.2. Fully-virtualized PXE installation with virt-install</h6><div class="example-contents"><pre class="screen"># virt-install --hvm --connect qemu:///system \
+--network=bridge:installation --pxe --graphics spice \
+--name rhel6-machine --ram=756 --vcpus=4 \
+--os-type=linux --os-variant=rhel6 \
+--disk path=/var/lib/libvirt/images/rhel6-machine.img,size=10</pre><div class="para">
+ Note that the command above cannot be executed in a text-only environment. A fully-virtualized (<em class="parameter"><code>--hvm</code></em>) guest can only be installed in a text-only environment if the <em class="parameter"><code>--location</code></em> and <em class="parameter"><code>--extra-args "console=<em class="replaceable"><code>console_type</code></em>"</code></em> are provided instead of the <em class="parameter"><code>--graphics spice</code></em> parameter.
+ </div></div></div><br class="example-break" /><div class="procedure" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE-PXE_installation_with_virt_manager"><h6>Procedure 6.2. PXE installation with virt-manager</h6><ol class="1"><li class="step" id="step-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Installing_guests_with_PXE-Select_PXE"><p class="title"><strong>Select PXE</strong></p><div class="para">
+ Select PXE as the installation method and follow the rest of the steps to configure the OS type, memory, CPU and storage settings.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt3-pic2.png" alt="Step 1 of 5 for creating a new virtual machine with virt-manager, with Network Boot (PXE) chosen for the method of installation." /></div></div><h6>Figure 6.8. Selecting the installation method</h6></div><br class="figure-break" /><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt3-pic3.png" alt="Step 2 of 5 for creating a new virtual machine with virt-manager, with Linux chosen as OS Type and Fedora 19 chosen for version." /></div></div><h6>Figure 6.9. Selecting the installation type</h6></div><br class="figure-break" /><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt3-pic4.png" alt="Step 3 of 5 for creating a new virtual machine with virt-manager showing memory and CPU settings, with 1024MB of RAM and 2 CPUs selected
." /></div></div><h6>Figure 6.10. Specifying virtualized hardware details</h6></div><br class="figure-break" /><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Screenshot-sevenpt3-pic5.png" alt="Step 4 of 5 for creating a new virtual machine with virt-manager, with checkboxes selected next to "Enable storage for this virtual machine" and "Allocate entire disk now". 8GB is selected under the heading "Create a disk image on the computer's hard drive"." /></div></div><h6>Figure 6.11. Specifying storage details</h6></div><br class="figure-break" /></li><li class="step" id="step-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation-Start_the_installation"><p class="title"><strong>Start the installation</strong></p><div class="para">
+ The installation is ready to start.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/PXEguest_5of5.png" width="444" alt="Step 5 of 5 for creating a new virtual machine with virt-manager reads "Ready to begin installation of (guest name)" with a summary of options already chosen, and advanced options to choose from." /></div></div><h6>Figure 6.12. Finalizing virtual machine details</h6></div><br class="figure-break" /></li></ol></div><div class="para">
+ A DHCP request is sent and if a valid PXE server is found the guest virtual machine's installation processes will start.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation_Virt_Manager-Creating_guests_with_virt_manager.html"><strong>Prev</strong>6.3. 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_Host_Configuration_and_Guest_Installation_Guide-RHEL6_Install.html"><strong>Next</strong>Chapter 7. Installing a Red Hat Enterprise Linux ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html
new file mode 100644
index 0000000..15d631d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system.html
@@ -0,0 +1,84 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.2. Installing virtualization packages on an existing Fedora system</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html" title="Chapter 5. Installing the virtualization packages" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html" title="Chapter 5. Installing the virtualization packages" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html" title="Chapter 6. Guest virtual machine installation overview" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_KVM_packages_on_an_existing_Red_Hat_Enterprise_Linux_system"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.2. Installing virtualization packages on an existing Fedora system</h2></div></div></div><div class="para">
+ This section describes the steps for installing the KVM hypervisor on a working Fedora 16 or newer system.
+ </div><div class="para">
+ To install the packages, your machines must be registered. There are two methods of registering an unregistered installation of Fedora:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ To register via RHN Classic, run the <code class="command">rhn_register</code> command and follow the prompts.
+ </div></li><li class="listitem"><div class="para">
+ To register via Fedora, run the <code class="command">subscription-manager register</code> command and follow the prompts.
+ </div></li></ol></div><div class="para">
+ If you do not have a valid Fedora subscription, visit the <a href="https://www.redhat.com/wapps/store/catalog.html">Fedora online store</a> to obtain one.
+ </div><div class="formalpara" id="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Installing_the_KVM_hypervisor_with_yum"><h5 class="formalpara">Installing the virtualization packages with <code class="command">yum</code></h5>
+ To use virtualization on Fedora you require at least the <code class="filename">qemu-kvm</code> and <code class="filename">qemu-img</code> packages. These packages provide the user-level KVM emulator and disk image manager on the host Fedora system.
+ </div><div class="para">
+ To install the <code class="filename">qemu-kvm</code> and <code class="filename">qemu-img</code> packages, run the following command:
+ </div><pre class="screen"># yum install qemu-kvm qemu-img</pre><div class="para">
+ Several additional virtualization management packages are also available:
+ </div><div class="variablelist" id="vari-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation-Recommended_virtualization_packages"><h6>Recommended virtualization packages</h6><dl class="variablelist"><dt class="varlistentry"><span class="term"><span class="package">python-virtinst</span></span></dt><dd><div class="para">
+ Provides the <code class="command">virt-install</code> command for creating virtual machines.
+ </div></dd><dt class="varlistentry"><span class="term"><span class="package">libvirt</span></span></dt><dd><div class="para">
+ The <span class="package">libvirt</span> package provides the server and host side libraries for interacting with hypervisors and host systems. The <span class="package">libvirt</span> package provides the <code class="systemitem">libvirtd</code> daemon that handles the library calls, manages virtual machines and controls the hypervisor.
+ </div></dd><dt class="varlistentry"><span class="term"><span class="package">libvirt-python</span></span></dt><dd><div class="para">
+ The <span class="package">libvirt-python</span> package contains a module that permits applications written in the Python programming language to use the interface supplied by the <span class="package">libvirt</span> API.
+ </div></dd><dt class="varlistentry"><span class="term"><span class="package">virt-manager</span></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 <span class="package">libvirt-client</span> library as the management API.
+ </div></dd><dt class="varlistentry"><span class="term"><span class="package">libvirt-client</span></span></dt><dd><div class="para">
+ The <span class="package">libvirt-client</span> package provides the client-side APIs and libraries for accessing <span class="package">libvirt</span> servers. The <span class="package">libvirt-client</span> package includes the <code class="command">virsh</code> command line tool to manage and control virtual machines and hypervisors from the command line or a special virtualization shell.
+ </div></dd></dl></div><div class="para">
+ Install all of these recommended virtualization packages with the following command:
+ </div><pre class="screen"># yum install virt-manager libvirt libvirt-python python-virtinst libvirt-client</pre><div class="formalpara"><h5 class="formalpara" id="idm12237232">Installing Virtualization package groups</h5>
+ The virtualization packages can also be installed from package groups. The following table describes the virtualization package groups and what they provide.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Note that the <code class="command">qemu-img</code> package is installed as a dependency of the <code class="literal">Virtualization</code> package group if it is not already installed on the system. It can also be installed manually with the <code class="command">yum install qemu-img</code> command as described previously.
+ </div></div></div><div class="table"><h6>Table 5.1. Virtualization Package Groups</h6><div class="table-contents"><table summary="Virtualization Package Groups" border="1"><colgroup><col align="left" class="c1" width="25%" /><col align="left" class="c2" width="25%" /><col align="left" class="c3" width="25%" /><col align="left" class="c4" width="25%" /></colgroup><thead><tr><th class="" align="left">
+ Package Group
+ </th><th class="" align="left">
+ Description
+ </th><th class="" align="left">
+ Mandatory Packages
+ </th><th class="" align="left">
+ Optional Packages
+ </th></tr></thead><tbody><tr><td class="" align="left">
+ Virtualization
+ </td><td class="" align="left">
+ Provides an environment for hosting virtual machines
+ </td><td class="" align="left">
+ qemu-kvm
+ </td><td class="" align="left">
+ qemu-guest-agent, qemu-kvm-tools
+ </td></tr><tr><td class="" align="left">
+ Virtualization Client
+ </td><td class="" align="left">
+ Clients for installing and managing virtualization instances
+ </td><td class="" align="left">
+ python-virtinst, virt-manager, virt-viewer
+ </td><td class="" align="left">
+ virt-top
+ </td></tr><tr><td class="" align="left">
+ Virtualization Platform
+ </td><td class="" align="left">
+ Provides an interface for accessing and controlling virtual machines and containers
+ </td><td class="" align="left">
+ libvirt, libvirt-client, virt-who, virt-what
+ </td><td class="" align="left">
+ fence-virtd-libvirt, fence-virtd-multicast, fence-virtd-serial, libvirt-cim, libvirt-java, libvirt-qmf, libvirt-snmp, perl-Sys-Virt
+ </td></tr><tr><td class="" align="left">
+ Virtualization Tools
+ </td><td class="" align="left">
+ Tools for offline virtual image management
+ </td><td class="" align="left">
+ libguestfs
+ </td><td class="" align="left">
+ libguestfs-java, libguestfs-tools, virt-v2v
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ To install a package group, run the <code class="command">yum groupinstall <groupname></code> command. For instance, to install the <span class="bold bold"><strong>Virtualization Tools</strong></span> package group, run the <code class="command">yum groupinstall "Virtualization Tools"</code> command.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Host_Installation.html"><strong>Prev</strong>Chapter 5. 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="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html"><strong>Next</strong>Chapter 6. Guest virtual machine installation ove...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html
new file mode 100644
index 0000000..b2a982e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt.html
@@ -0,0 +1,21 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.3. Bridged networking with libvirt</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html" title="Chapter 11. Network configuration" /><link rel="prev" href="ch11s02.html" title="11.2. Disabling vhost-net" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html" title="Chapter 12. PCI device configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="ch11s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration-Network_Configuration-Bridged_networking_with_libvirt"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">11.3. Bridged networking with libvirt</h2></div></div></div><div class="para">
+ Bridged networking (also known as physical device sharing) is used to dedicate 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="para">
+ To create a bridge (<code class="literal">br0</code>) based on the <code class="literal">eth0</code> interface, execute the following command on the host:
+ </div><pre class="screen"># virsh iface-bridge eth0 br0</pre><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ NetworkManager does not support bridging. NetworkManager must be disabled to use networking with the network scripts (located in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory).
+ </div><pre class="screen"># chkconfig NetworkManager off
+# chkconfig network on
+# service NetworkManager stop
+# service network start</pre><div class="para">
+ If you do not want to disable <span class="application"><strong>NetworkManager</strong></span> entirely, add "<em class="parameter"><code>NM_CONTROLLED=no</code></em>" to the <code class="filename">ifcfg-*</code> network script being used for the bridge.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch11s02.html"><strong>Prev</strong>11.2. Disabling vhost-net</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_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html"><strong>Next</strong>Chapter 12. PCI device configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host.html
new file mode 100644
index 0000000..238c11c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.2. Assigning a PCI device with virt-manager</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html" title="Chapter 12. PCI device configuration" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html" title="Chapter 12. PCI device configuration" /><link rel="next" href="ch12s03.html" title="12.3. PCI device assignment with virt-install" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch12s03.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Assignment-Adding_a_PCI_device_to_a_host"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">12.2. Assigning a PCI device with virt-manager</h2></div></div></div><div class="para">
+ PCI devices can be added to guest virtual machines using the graphical <code class="command">virt-manager</code> tool. The following procedure adds a Gigabit Ethernet controller to a guest virtual machine.
+ </div><div class="procedure"><h6>Procedure 12.4. Assigning a PCI device to a guest virtual machine using virt-manager</h6><ol class="1"><li class="step"><p class="title"><strong>Open the hardware settings</strong></p><div class="para">
+ Open the guest virtual machine and click the <span class="guibutton"><strong>Add Hardware</strong></span> button to add a new device to the virtual machine.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/virt-manager_hardware.png" width="444" alt="The virtual machine hardware window with the Information button selected on the top taskbar and Overview selected on the left menu pane." /></div></div><h6>Figure 12.1. The virtual machine hardware information window</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Select a PCI device</strong></p><div class="para">
+ Select <span class="application"><strong>PCI Host Device</strong></span> from the <span class="guilabel"><strong>Hardware</strong></span> list on the left.
+ </div><div class="para">
+ Select an unused PCI device. Note that selecting PCI devices presently in use on the host causes errors. In this example, a spare 82576 network device is used. Click <span class="guilabel"><strong>Finish</strong></span> to complete setup.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/3_PCI_Device.png" width="444" alt="The Add new virtual hardware wizard with PCI Host Device selected on the left menu pane, showing a list of host devices for selection in the right menu pane." /></div></div><h6>Figure 12.2. The Add new virtual hardware wizard</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Add the new device</strong></p><div class="para">
+ The setup is complete and the guest virtual machine now has direct access to the PCI device.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/pci_host_device.png" width="444" alt="The virtual machine hardware window with the Information button selected on the top taskbar and Overview selected on the left menu pane, displaying the newly added PCI Device in the list of virtual machine devices in the left menu pane." /></div></div><h6>Figure 12.3. The virtual machine hardware information window</h6></div><br class="figure-break" /></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html"><strong>Prev</strong>Chapter 12. PCI device 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="ch12s03.html"><strong>Next</strong>12.3. PCI device assig
nment with virt-install</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html
new file mode 100644
index 0000000..8b1a485
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html
@@ -0,0 +1,56 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.6. Using KVM para-virtualized drivers for new devices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html" title="Chapter 10. KVM Para-virtualized Drivers" /><link rel="prev" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices.html" title="10.5. Using KVM para-virtualized drivers for existing devices" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html" title="Chapter 11. Network configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.6. Using KVM para-virtualized drivers f
or new devices</h2></div></div></div><div class="para">
+ 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"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><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><div class="procedure"><h6>Procedure 10.5. Starting the new device wizard</h6><ol class="1"><li class="step"><div class="para">
+ Open the guest virtual machine by double clicking on the name of the guest in <code class="command">virt-manager</code>.
+ </div></li><li class="step"><div class="para">
+ Open the <span class="guilabel"><strong>Show virtual hardware details</strong></span> tab by clicking the <span class="guibutton"><strong>lightbulb</strong></span> button.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/vm_info_button_new.png" alt="The Show virtual hardware details tab" /></div></div><h6>Figure 10.30. The Show virtual hardware details tab</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ In the <span class="guilabel"><strong>Show virtual hardware details</strong></span> tab, click on the <span class="guilabel"><strong>Add Hardware</strong></span> button.
+ </div></li><li class="step"><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. The storage and network device wizards are covered in procedures <a class="xref" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html#procstore">Procedure 10.6, “Adding a storage device using the para-virtualized storage driver”</a> and <a class="xref" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_new_devices.html#procnet">Procedure 10.7, “Adding a network device using the para-virtualized network driver”</a>.
+ </div></li></ol></div><div class="procedure" id="procstore"><h6>Procedure 10.6. Adding a storage device using the para-virtualized storage driver</h6><ol class="1"><li class="step"><div class="para">
+ Open the guest virtual machine by double clicking on the name of the guest in <code class="command">virt-manager</code>.
+ </div></li><li class="step"><div class="para">
+ Open the <span class="guilabel"><strong>Show virtual hardware details</strong></span> tab by clicking the <span class="guibutton"><strong>lightbulb</strong></span> button.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/vm_info_button_new.png" alt="The Show virtual hardware details tab" /></div></div><h6>Figure 10.31. The Show virtual hardware details tab</h6></div><br class="figure-break" /></li><li class="step"><div class="para">
+ In the <span class="guilabel"><strong>Show virtual hardware details</strong></span> tab, click on the <span class="guilabel"><strong>Add Hardware</strong></span> button.
+ </div></li><li class="step"><p class="title"><strong>Select hardware type</strong></p><div class="para">
+ Select <span class="guilabel"><strong>Network</strong></span> as the <span class="guilabel"><strong>Hardware type</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Network_hardware.png" width="444" alt="The Add new virtual hardware wizard with Storage selected as the hardware type." /></div></div><h6>Figure 10.32. The Add new virtual hardware wizard</h6></div><br class="figure-break" /></li><li class="step"><p class="title"><strong>Select the network device and driver</strong></p><div class="para">
+ Create a new disk image or select a storage pool volume.
+ </div><div class="para">
+ Set the <span class="guilabel"><strong>Device type</strong></span> to <span class="guilabel"><strong>Virtio Disk</strong></span> to use the para-virtualized drivers. Choose the desired <span class="guilabel"><strong>Host device</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/Network_hardware_virtio.png" width="444" alt="The Add new virtual hardware wizard Storage window, with "Select managed or other existing storage" selected and specified in the field below." /></div></div><h6>Figure 10.33. The Add new virtual hardware wizard</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guilabel"><strong>Finish</strong></span> to complete the procedure.
+ </div></li></ol></div><div class="procedure" id="procnet"><h6>Procedure 10.7. Adding a network device using the para-virtualized network driver</h6><ol class="1"><li class="step"><p class="title"><strong>Select hardware type</strong></p><div class="para">
+ Select <span class="guilabel"><strong>Network</strong></span> as the <span class="guilabel"><strong>Hardware type</strong></span>.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/virtio-network-step1.png" alt="The Add new virtual hardware wizard with Network selected as the hardware type." /></div></div><h6>Figure 10.34. The Add new virtual hardware wizard</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guilabel"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Select the network device and driver</strong></p><div class="para">
+ Select the network device from the <span class="guilabel"><strong>Host device</strong></span> list.
+ </div><div class="para">
+ Create a custom MAC address or use the one provided.
+ </div><div class="para">
+ Set the <span class="guilabel"><strong>Device model</strong></span> to <span class="guilabel"><strong>virtio</strong></span> to use the para-virtualized drivers.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/virtio-network-step2.png" alt="The Add new virtual hardware wizard Network setup, with options for selecting the network device and driver." /></div></div><h6>Figure 10.35. The Add new virtual hardware wizard</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guilabel"><strong>Forward</strong></span> to continue.
+ </div></li><li class="step"><p class="title"><strong>Finish the procedure</strong></p><div class="para">
+ Confirm the details for the new device are correct.
+ </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/virtio-network-finish3.png" alt="The Add new virtual hardware wizard showing the details of the newly created network, and the Finish button at the bottom right corner of the window." /></div></div><h6>Figure 10.36. The Add new virtual hardware wizard</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guilabel"><strong>Finish</strong></span> to complete the procedure.
+ </div></li></ol></div><div class="para">
+ Once all new devices are added, reboot the virtual machine. Windows virtual machines may not recognize the devices until the guest is rebooted.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="form-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Using_KVM_para_virtualized_drivers_for_existing_devices.html"><strong>Prev</strong>10.5. Using KVM para-virtualized drivers for exis...</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_Host_Configuration_and_Guest_Installation_Guide-Network_Configuration.html"><strong>Next</strong>Chapter 11. Network configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html
new file mode 100644
index 0000000..ac6fd33
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html
@@ -0,0 +1,169 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>13.2. Using SR-IOV</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html" title="Chapter 13. SR-IOV" /><link rel="prev" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html" title="Chapter 13. SR-IOV" /><link rel="next" href="ch13s03.html" title="13.3. Troubleshooting SR-IOV" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 clas
s="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch13s03.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">13.2. Using SR-IOV</h2></div></div></div><div class="para">
+ This section covers the use of PCI passthrough to assign a Virtual Function of an SR-IOV capable multiport network card to a virtual machine as a network device.
+ </div><div class="para">
+ SR-IOV Virtual Functions (VFs) can be assigned to virtual machines by adding a device entry in <em class="parameter"><code><hostdev></code></em> with the <code class="command">virsh edit</code> or <code class="command">virsh attach-device</code> command. However, this can be problematic because unlike a regular network device, an SR-IOV VF network device does not have a permanent unique MAC address, and is assigned a new MAC address each time the host is rebooted. Because of this, even if the guest is assigned the same VF after a reboot, when the host is rebooted the guest determines its network adapter to have a new MAC address. As a result, the guest believes there is new hardware connected each time, and will usually require re-configuration of the guest's network settings.
+ </div><div class="para">
+ <span class="package">libvirt-0.9.10</span> and newer contains the <em class="parameter"><code><interface type='hostdev'></code></em> interface device. Using this interface device, <span class="application"><strong>libvirt</strong></span> will first perform any network-specific hardware/switch initialization indicated (such as setting the MAC address, VLAN tag, or 802.1Qbh virtualport parameters), then perform the PCI device assignment to the guest.
+ </div><div class="para">
+ Using the <em class="parameter"><code><interface type='hostdev'></code></em> interface device requires:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ an SR-IOV-capable network card,
+ </div></li><li class="listitem"><div class="para">
+ host hardware that supports either the Intel VT-d or the AMD IOMMU extensions, and
+ </div></li><li class="listitem"><div class="para">
+ the PCI address of the VF to be assigned.
+ </div></li></ul></div>
+
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Assignment of an SR-IOV device to a virtual machine requires that the host hardware supports the Intel VT-d or the AMD IOMMU specification.
+ </div></div></div><div class="para">
+ To attach an SR-IOV network device on an Intel or an AMD system, follow this procedure:
+ </div><div class="procedure"><h6>Procedure 13.1. Attach an SR-IOV network device on an Intel or AMD system</h6><ol class="1"><li class="step"><p class="title"><strong>Enable Intel VT-d or the AMD IOMMU specifications in the BIOS and kernel</strong></p><div class="para">
+ On an Intel system, enable Intel VT-d in the BIOS if it is not enabled already. Refer to <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html#intel-prep">Procedure 12.1, “Preparing an Intel system for PCI device assignment”</a> for procedural help on enabling Intel VT-d in the BIOS and kernel.
+ </div><div class="para">
+ Skip this step if Intel VT-d is already enabled and working.
+ </div><div class="para">
+ On an AMD system, enable the AMD IOMMU specifications in the BIOS if they are not enabled already. Refer to <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-PCI_Device_Config.html#amd-prep">Procedure 12.2, “Preparing an AMD system for PCI device assignment”</a> for procedural help on enabling IOMMU in the BIOS.
+ </div></li><li class="step"><p class="title"><strong>Verify support</strong></p><div class="para">
+ Verify if the PCI device with SR-IOV capabilities is detected. This example lists an Intel 82576 network interface card which supports SR-IOV. Use the <code class="command">lspci</code> command to verify whether the device was detected.
+ </div><pre class="screen"># lspci
+03:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
+03:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)</pre><div class="para">
+ Note that the output has been modified to remove all other devices.
+ </div></li><li class="step"><p class="title"><strong>Start the SR-IOV kernel modules</strong></p><div class="para">
+ If the device is supported the driver kernel module should be loaded automatically by the kernel. Optional parameters can be passed to the module using the <code class="command">modprobe</code> command. The Intel 82576 network interface card uses the <code class="command">igb</code> driver kernel module.
+ </div><pre class="screen"># modprobe igb [<option>=<VAL1>,<VAL2>,]
+# lsmod |grep igb
+igb 87592 0
+dca 6708 1 igb</pre></li><li class="step"><p class="title"><strong>Activate Virtual Functions</strong></p><div class="para">
+ The <em class="parameter"><code>max_vfs</code></em> parameter of the <code class="command">igb</code> module allocates the maximum number of Virtual Functions. The <em class="parameter"><code>max_vfs</code></em> parameter causes the driver to spawn, up to the value of the parameter in, Virtual Functions. For this particular card the valid range is <em class="parameter"><code>0</code></em> to <em class="parameter"><code>7</code></em>.
+ </div><div class="para">
+ Remove the module to change the variable.
+ </div><pre class="screen"># modprobe -r igb</pre><div class="para">
+ Restart the module with the <em class="parameter"><code>max_vfs</code></em> set to <em class="parameter"><code>7</code></em> or any number of Virtual Functions up to the maximum supported by your device.
+ </div><pre class="screen"># modprobe igb max_vfs=7</pre></li><li class="step"><p class="title"><strong>Make the Virtual Functions persistent</strong></p><div class="para">
+ Add the line <code class="option">options igb max_vfs=7</code> to any file in <code class="filename">/etc/modprobe.d</code> to make the Virtual Functions persistent. For example:
+ </div><pre class="screen"># echo "options igb max_vfs=7" >>/etc/modprobe.d/igb.conf</pre></li><li class="step"><p class="title"><strong>Inspect the new Virtual Functions</strong></p><div class="para">
+ Using the <code class="command">lspci</code> command, list the newly added Virtual Functions attached to the Intel 82576 network device. (Alternatively, use <code class="command">grep</code> to search for <code class="literal">Virtual Function</code>, to search for devices that support Virtual Functions.)
+ </div><pre class="screen"># lspci | grep 82576
+0b:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
+0b:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
+0b:10.0 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.1 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.2 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.3 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.4 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.5 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.6 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:10.7 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:11.0 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:11.1 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:11.2 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:11.3 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:11.4 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
+0b:11.5 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)</pre><div class="para">
+ The identifier for the PCI device is found with the <em class="parameter"><code>-n</code></em> parameter of the <code class="command">lspci</code> command. The Physical Functions correspond to <code class="computeroutput">0b:00.0</code> and <code class="computeroutput">0b:00.1</code>. All Virtual Functions have <code class="computeroutput">Virtual Function</code> in the description.
+ </div></li><li class="step"><p class="title"><strong>Verify devices exist with virsh</strong></p><div class="para">
+ The <code class="systemitem">libvirt</code> service must recognize the device before adding a device to a virtual machine. <code class="systemitem">libvirt</code> uses a similar notation to the <code class="command">lspci</code> output. All punctuation characters, <span class="keycap"><strong>;</strong></span> and <span class="keycap"><strong>.</strong></span>, in <code class="command">lspci</code> output are changed to underscores (<span class="keycap"><strong>_</strong></span>).
+ </div><div class="para">
+ Use the <code class="command">virsh nodedev-list</code> command and the <code class="command">grep</code> command to filter the Intel 82576 network device from the list of available host devices. <em class="parameter"><code>0b</code></em> is the filter for the Intel 82576 network devices in this example. This may vary for your system and may result in additional devices.
+ </div><pre class="screen"># virsh nodedev-list | grep <em class="parameter"><code>0b</code></em>
+pci_0000_0b_00_0
+pci_0000_0b_00_1
+pci_0000_0b_10_0
+pci_0000_0b_10_1
+pci_0000_0b_10_2
+pci_0000_0b_10_3
+pci_0000_0b_10_4
+pci_0000_0b_10_5
+pci_0000_0b_10_6
+pci_0000_0b_11_7
+pci_0000_0b_11_1
+pci_0000_0b_11_2
+pci_0000_0b_11_3
+pci_0000_0b_11_4
+pci_0000_0b_11_5</pre><div class="para">
+ The serial numbers for the Virtual Functions and Physical Functions should be in the list.
+ </div></li><li class="step"><p class="title"><strong>Get device details with virsh</strong></p><div class="para">
+ The <code class="computeroutput">pci_0000_0b_00_0</code> is one of the Physical Functions and <code class="computeroutput">pci_0000_0b_10_0</code> is the first corresponding Virtual Function for that Physical Function. Use the <code class="command">virsh nodedev-dumpxml</code> command to get advanced output for both devices.
+ </div><pre class="screen"># virsh nodedev-dumpxml pci_0000_0b_00_0
+<device>
+ <name>pci_0000_0b_00_0</name>
+ <parent>pci_0000_00_01_0</parent>
+ <driver>
+ <name>igb</name>
+ </driver>
+ <capability type='pci'>
+ <domain>0</domain>
+ <bus>11</bus>
+ <slot>0</slot>
+ <function>0</function>
+ <product id='0x10c9'>Intel Corporation</product>
+ <vendor id='0x8086'>82576 Gigabit Network Connection</vendor>
+ </capability>
+</device></pre><pre class="screen"># virsh nodedev-dumpxml pci_0000_0b_10_0
+<device>
+ <name>pci_0000_0b_10_0</name>
+ <parent>pci_0000_00_01_0</parent>
+ <driver>
+ <name>igbvf</name>
+ </driver>
+ <capability type='pci'>
+ <domain>0</domain>
+ <bus>11</bus>
+ <slot>16</slot>
+ <function>0</function>
+ <product id='0x10ca'>Intel Corporation</product>
+ <vendor id='0x8086'>82576 Virtual Function</vendor>
+ </capability>
+</device></pre><div class="para">
+ This example adds the Virtual Function <code class="systemitem">pci_0000_0b_10_0</code> to the virtual machine in <a class="xref" href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV-How_SR_IOV_Libvirt_Works.html#step9">Step 9</a>. Note the <code class="computeroutput">bus</code>, <code class="computeroutput">slot</code> and <code class="computeroutput">function</code> parameters of the Virtual Function: these are required for adding the device.
+ </div><div class="para">
+ Copy these parameters into a temporary XML file, such as <code class="filename">/tmp/new-interface.xml</code> for example.
+ </div><pre class="programlisting">
+ <interface type='hostdev' managed='yes'>
+ <source>
+ <address type='pci' domain='0' bus='11' slot='16' function='0'/>
+ </source>
+ </interface></pre><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If you do not specify a MAC address, one will be automatically generated. The <em class="parameter"><code><virtualport></code></em> element is only used when connecting to an 802.11Qbh hardware switch. The <em class="parameter"><code><vlan></code></em> element was introduced for Fedora 18 and this will transparently put the guest's device on the VLAN tagged <em class="parameter"><code>42</code></em>.
+ </div><div class="para">
+ When the virtual machine starts, it should see a network device of the type provided by the physical adapter, with the configured MAC address. This MAC address will remain unchanged across host and guest reboots.
+ </div><div class="para">
+ The following <em class="parameter"><code><interface></code></em> example shows the syntax for the optional <em class="parameter"><code><mac address></code></em>, <em class="parameter"><code><virtualport></code></em>, and <em class="parameter"><code><vlan></code></em> elements. In practice, use either the <em class="parameter"><code><vlan></code></em> or <em class="parameter"><code><virtualport></code></em> element, not both simultaneously as shown in the example:
+ </div><pre class="programlisting">...
+ <devices>
+ ...
+ <interface type='hostdev' managed='yes'>
+ <source>
+ <address type='pci' domain='0' bus='11' slot='16' function='0'/>
+ </source>
+ <mac address='52:54:00:6d:90:02'>
+ <vlan>
+ <tag id='42'/>
+ </vlan>
+ <virtualport type='802.1Qbh'>
+ <parameters profileid='finance'/>
+ </virtualport>
+ </interface>
+ ...
+ </devices></pre></div></div></li><li class="step" id="step9"><p class="title"><strong>Add the Virtual Function to the virtual machine</strong></p><div class="para">
+ Add the Virtual Function to the virtual machine using the following command with the temporary file created in the previous step. This attaches the new device immediately and saves it for subsequent guest restarts.
+ </div><pre class="screen">
+virsh attach-device <em class="replaceable"><code>MyGuest</code></em> <code class="filename">/tmp/new-interface.xml</code> --live --config
+</pre><div class="para">
+ Specifying the <code class="option">--live</code> option with <code class="command">virsh attach-device</code> attaches the new device to the running guest. Using the <code class="option">--config</code> option ensures the new device is available after future guest restarts.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The <code class="option">--live</code> option is only accepted when the guest is running. <code class="command">virsh</code> will return an error if the <code class="option">--live</code> option is used on a non-running guest.
+ </div></div></div></li></ol></div><div class="para">
+ The virtual machine detects a new network interface card. This new card is the Virtual Function of the SR-IOV device.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-SR_IOV.html"><strong>Prev</strong>Chapter 13. SR-IOV</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="ch13s03.html"><strong>Next</strong>13.3. Troubleshooting SR-IOV</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html
new file mode 100644
index 0000000..238a41b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html
@@ -0,0 +1,46 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 9. Installing a fully-virtualized Windows guest</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt01.html" title="Part I. Deployment" /><link rel="prev" href="ch08s02.html" title="8.2. On Hyper-V" /><link rel="next" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html" title="Chapter 10. KVM Para-virtualized Drivers" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="ch08s02
.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 9. Installing a fully-virtualized Windows guest</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_XP_as_a_fully_virtualized_guest.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_virt-install">9.1. Using virt-install to create a guest</a></span></dt></dl></div><div class="para">
+ This chapter describes how to create a fully-virtualized Windows guest using the command-line (<code class="command">virt-install</code>), launch the operating system's installer inside the guest, and access the installer through <code class="command">virt-viewer</code>.
+ </div><div class="para">
+ To install a Windows operating system on the guest, use the <code class="command">virt-viewer</code> tool. This tool allows you to display the graphical console of a virtual machine (via the VNC protocol). In doing so, <code class="command">virt-viewer</code> allows you to install a fully-virtualized guest's operating system with that operating system's installer (for example, the Windows XP installer).
+ </div><div class="para">
+ Installing a Windows operating system involves two major steps:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Creating the guest virtual machine, using either <code class="command">virt-install</code> or <code class="command">virt-manager</code>.
+ </div></li><li class="listitem"><div class="para">
+ Installing the Windows operating system on the guest virtual machine, using <code class="command">virt-viewer</code>.
+ </div></li></ol></div><div class="para">
+ Refer to <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Guest_Installation.html">Chapter 6, <em>Guest virtual machine installation overview</em></a> for details about creating a guest virtual machine with <code class="command">virt-install</code> or <code class="command">virt-manager</code>.
+ </div><div class="para">
+ Note that this chapter does not describe how to install a Windows operating system on a fully-virtualized guest. Rather, it only covers how to create the guest and launch the installer within the guest. For information on how to install a Windows operating system, refer to the relevant Microsoft installation documentation.
+ </div><div class="section" id="sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Windows_Installations-Installing_Windows_virt-install"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">9.1. Using virt-install to create a guest</h2></div></div></div><div class="para">
+ The <code class="command">virt-install</code> command allows you to create a fully-virtualized guest from a terminal, for example, without a GUI.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Before creating the guest, consider first if the guest needs to use KVM Windows para-virtualized drivers. If it does, keep in mind that you can do so <span class="emphasis"><em>during</em></span> or <span class="emphasis"><em>after</em></span> installing the Windows operating system on the guest. For more information about para-virtualized drivers, refer to <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html">Chapter 10, <em>KVM Para-virtualized Drivers</em></a>.
+ </div><div class="para">
+ For instructions on how to install KVM para-virtualized drivers, refer to <a class="xref" href="chap-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html#sect-Virtualization_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers-Installing_the_KVM_Windows_para_virtualized_drivers">Section 10.1, “Installing the KVM Windows para-virtualized drivers”</a>.
+ </div></div></div><div class="para">
+ It is possible to create a fully-virtualized guest with only a single command. To do so, run the following program (replace the values accordingly):
+ </div><pre class="screen"># virt-install \
+ --name=<em class="replaceable"><code>guest-name</code></em> \
+ --os-type=<em class="replaceable"><code>windows</code></em> \
+ --network network=default \
+ --disk path=<em class="replaceable"><code>path-to-disk</code></em>,size=<em class="replaceable"><code>disk-size</code></em> \
+ --cdrom=<em class="replaceable"><code>path-to-install-disk</code></em> \
+ --graphics spice --ram=1024</pre><div class="para">
+ The <code class="command"><em class="replaceable"><code>path-to-disk</code></em></code> must be a device (e.g. <code class="filename">/dev/sda3</code>) or image file (<code class="filename">/var/lib/libvirt/images/<em class="replaceable"><code>name</code></em>.img</code>). It must also have enough free space to support the <code class="command"><em class="replaceable"><code>disk-size</code></em></code>.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ All image files are stored in <code class="filename">/var/lib/libvirt/images/</code> by default. Other directory locations for file-based images are possible, but may require SELinux configuration. If you run SELinux in enforcing mode.
+ </div></div></div><div class="para">
+ You can also run <code class="command">virt-install</code> interactively. To do so, use the <code class="command">--prompt</code> command, as in:
+ </div><pre class="screen"># virt-install --prompt</pre><div class="para">
+ Once the fully-virtualized guest is created, <code class="command">virt-viewer</code> will launch the guest and run the operating system's installer. Refer to to the relevant Microsoft installation documentation for instructions on how to install the operating system.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch08s02.html"><strong>Prev</strong>8.2. On Hyper-V</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_Host_Configuration_and_Guest_Installation_Guide-Para_virtualized_drivers.html"><strong>Next</strong>Chapter 10. KVM Para-virtualized Drivers</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-applying-network-filtering.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-applying-network-filtering.html
new file mode 100644
index 0000000..12723f8
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-applying-network-filtering.html
@@ -0,0 +1,52 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10. Applying network filtering</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html" title="Appendix H. Virtual Networking" /><link rel="prev" href="sect-attch-nic-physdev.html" title="H.9. Directly attaching to physical interface" /><link rel="next" href="sub-sect-filt-chain.html" title="H.10.2. Filtering chains" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 acces
skey="p" href="sect-attch-nic-physdev.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-filt-chain.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-applying-network-filtering"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">H.10. Applying network filtering</h2></div></div></div><div class="para">
+ This section provides an introduction to libvirt's network filters, their goals, concepts and XML format.
+ </div><div class="section" id="intro-sub-sect-applying-network-filtering"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.10.1. Introduction</h3></div></div></div><div class="para">
+ The goal of the network filtering, is to enable administrators of a virtualized system to configure and enforce network traffic filtering rules on virtual machines and manage the parameters of network traffic that virtual machines are allowed to send or receive. The network traffic filtering rules are applied on the host when a virtual machine is started. Since the filtering rules cannot be circumvented from within the virtual machine, it makes them mandatory from the point of view of a virtual machine user.
+ </div><div class="para">
+ From the point of view of the guest, the network filtering system allows each virtual machine's network traffic filtering rules to be configured individually on a per interface basis. These rules are applied on the host when the virtual machine is started and can be modified while the virtual machine is running. The latter can be achieved by modifying the XML description of a network filter.
+ </div><div class="para">
+ Multiple virtual machines can make use of the same generic network filter. When such a filter is modified, the network traffic filtering rules of all running virtual machines that reference this filter are updated. The machines that are not running will update on start.
+ </div><div class="para">
+ As previously mentioned, applying network traffic filtering rules can be done on individual network interfaces that are configured for certain types of network configurations. Supported network types include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ network
+ </div></li><li class="listitem"><div class="para">
+ ethernet -- must be used in bridging mode
+ </div></li><li class="listitem"><div class="para">
+ bridge
+ </div></li></ul></div><div class="example" id="ex-net-filtering"><h6>Example H.1. An example of network filtering</h6><div class="example-contents"><div class="para">
+ The interface XML is used to reference a top-level filter. In the following example, the interface description references the filter clean-traffic.
+ </div><pre class="screen">
+ <devices>
+ <interface type='bridge'>
+ <mac address='00:16:3e:5d:c7:9e'/>
+ <filterref filter='clean-traffic'/>
+ </interface>
+ </devices>
+</pre><div class="para">
+ Network filters are written in XML and may either contain: references to other filters, rules for traffic filtering, or hold a combination of both. The above referenced filter clean-traffic is a filter that only contains references to other filters and no actual filtering rules. Since references to other filters can be used, a tree of filters can be built. The clean-traffic filter can be viewed using the command: <code class="command"># virsh nwfilter-dumpxml clean-traffic</code>.
+ </div><div class="para">
+ As previously mentioned, a single network filter can be referenced by multiple virtual machines. Since interfaces will typically have individual parameters associated with their respective traffic filtering rules, the rules described in a filter's XML can be generalized using variables. In this case, the variable name is used in the filter XML and the name and value are provided at the place where the filter is referenced.
+ </div></div></div><br class="example-break" /><div class="example"><h6>Example H.2. Description extended</h6><div class="example-contents"><div class="para">
+ In the following example, the interface description has been extended with the parameter IP and a dotted IP address as a value.
+ </div><pre class="screen">
+ <devices>
+ <interface type='bridge'>
+ <mac address='00:16:3e:5d:c7:9e'/>
+ <filterref filter='clean-traffic'>
+ <parameter name='IP' value='10.0.0.1'/>
+ </filterref>
+ </interface>
+ </devices>
+</pre><div class="para">
+ In this particular example, the clean-traffic network traffic filter will be represented with the IP address parameter 10.0.0.1 and as per the rule dictates that all traffic from this interface will always be using 10.0.0.1 as the source IP address, which is one of the purpose of this particular filter.
+ </div></div></div><br class="example-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-attch-nic-physdev.html"><strong>Prev</strong>H.9. Directly attaching to physical interface</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="sub-sect-filt-chain.html"><strong>Next</strong>H.10.2. Filtering chains</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-attch-nic-physdev.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-attch-nic-physdev.html
new file mode 100644
index 0000000..3c3a7c9
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-attch-nic-physdev.html
@@ -0,0 +1,70 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.9. Directly attaching to physical interface</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html" title="Appendix H. Virtual Networking" /><link rel="prev" href="sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest.html" title="H.8. Attaching a virtual network to a guest" /><link rel="next" href="sect-applying-network-filtering.html" title="H.10. Applying network filtering" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-applying-network-filtering.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-attch-nic-physdev"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">H.9. Directly attaching to physical interface</h2></div></div></div><div class="para">
+ The instructions provided in this chapter will assist in the direct attachment of the virtual machine's NIC to the given physical interface of the host. This setup requires the Linux macvtap driver to be available. There are four modes that you can choose for the operation mode of the macvtap device, with 'vepa' being the default mode. Their behavior is as follows:
+ </div><div class="variablelist"><h6>Physical interface delivery modes</h6><dl class="variablelist"><dt class="varlistentry"><span class="term">vepa</span></dt><dd><div class="para">
+ All VMs' packets are sent to the external bridge. Packets whose destination is a VM on the same host as where the packet originates from are sent back to the host by the VEPA capable bridge (today's bridges are typically not VEPA capable).
+ </div></dd><dt class="varlistentry"><span class="term">bridge</span></dt><dd><div class="para">
+ Packets whose destination is on the same host as where they originate from are directly delivered to the target macvtap device. Both origin and destination devices need to be in bridge mode for direct delivery. If either one of them is in vepa mode, a VEPA capable bridge is required.
+ </div></dd><dt class="varlistentry"><span class="term">private</span></dt><dd><div class="para">
+ All packets are sent to the external bridge and will only be delivered to a target VM on the same host if they are sent through an external router or gateway and that device sends them back to the host. This procedure is followed if either the source or destination device is in private mode.
+ </div></dd><dt class="varlistentry"><span class="term">passthrough</span></dt><dd><div class="para">
+ This feature attaches a virtual function of a SRIOV capable NIC directly to a VM without losing the migration capability. All packets are sent to the VF/IF of the configured network device. Depending on the capabilities of the device additional prerequisites or limitations may apply; for example, on Linux this requires kernel 2.6.38 or newer.
+ </div></dd></dl></div><div class="para">
+ Each of the four modes is configured by changing the domain xml file. Once this file is opened, change the mode setting as shown:
+ </div><pre class="screen">
+ <devices>
+ ...
+ <interface type='direct'>
+ <source dev='eth0' mode='vepa'/>
+ </interface>
+ </devices>
+</pre><div class="para">
+ The network access of direct attached guest virtual machines can be managed by the hardware switch to which the physical interface of the host machine is connected to.
+ </div><div class="para">
+ The interface can have additional parameters as shown below, if the switch is conforming to the IEEE 802.1Qbg standard. The parameters of the virtualport element are documented in more detail in the IEEE 802.1Qbg standard. The values are network specific and should be provided by the network administrator. In 802.1Qbg terms, the Virtual Station Interface (VSI) represents the virtual interface of a virtual machine.
+ </div><div class="para">
+ Note that IEEE 802.1Qbg requires a non-zero value for the VLAN ID. Also if the switch is conforming to the IEEE 802.1Qbh standard, the values are network specific and should be provided by the network administrator.
+ </div><div class="variablelist"><h6>Virtual Station Interface types</h6><dl class="variablelist"><dt class="varlistentry"><span class="term">managerid</span></dt><dd><div class="para">
+ The VSI Manager ID identifies the database containing the VSI type and instance definitions. This is an integer value and the value 0 is reserved.
+ </div></dd><dt class="varlistentry"><span class="term">typeid</span></dt><dd><div class="para">
+ The VSI Type ID identifies a VSI type characterizing the network access. VSI types are typically managed by network administrator. This is an integer value.
+ </div></dd><dt class="varlistentry"><span class="term">typeidversion</span></dt><dd><div class="para">
+ The VSI Type Version allows multiple versions of a VSI Type. This is an integer value.
+ </div></dd><dt class="varlistentry"><span class="term">instanceid</span></dt><dd><div class="para">
+ The VSI Instance ID Identifier is generated when a VSI instance (i.e. a virtual interface of a virtual machine) is created. This is a globally unique identifier.
+ </div></dd><dt class="varlistentry"><span class="term">profileid</span></dt><dd><div class="para">
+ The profile ID contains the name of the port profile that is to be applied onto this interface. This name is resolved by the port profile database into the network parameters from the port profile, and those network parameters will be applied to this interface.
+ </div></dd></dl></div><div class="para">
+ Each of the four types is configured by changing the domain xml file. Once this file is opened, change the mode setting as shown:
+ </div><pre class="screen">
+ <devices>
+ ...
+ <interface type='direct'>
+ <source dev='eth0.2' mode='vepa'/>
+ <virtualport type="802.1Qbg">
+ <parameters managerid="11" typeid="1193047" typeidversion="2" instanceid="09b11c53-8b5c-4eeb-8f00-d84eaa0aaa4f"/>
+ </virtualport>
+ </interface>
+ </devices>
+</pre><div class="para">
+ The profile ID is shown here:
+ </div><pre class="screen">
+ <devices>
+ ...
+ <interface type='direct'>
+ <source dev='eth0' mode='private'/>
+ <virtualport type='802.1Qbh'>
+ <parameters profileid='finance'/>
+ </virtualport>
+ </interface>
+ </devices>
+ ...
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Virtual_Networking-Attaching_virtual_network_to_guest.html"><strong>Prev</strong>H.8. Attaching a virtual network to a 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-applying-network-filtering.html"><strong>Next</strong>H.10. Applying network filtering</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-cpu-allocation.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-cpu-allocation.html
new file mode 100644
index 0000000..29568af
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-cpu-allocation.html
@@ -0,0 +1,26 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.4. CPU allocation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sect-smbios-sys-info.html" title="J.3. SMBIOS system information" /><link rel="next" href="sect-cpu-tuning.html" title="J.5. CPU tuning" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-smbios-sys-info.html"><strong>Prev</strong></a
></li><li class="next"><a accesskey="n" href="sect-cpu-tuning.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-cpu-allocation"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.4. CPU allocation</h2></div></div></div><div class="figure"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain></span>
+ ...
+ <span class="perl_Keyword"><vcpu</span><span class="perl_Others"> placement=</span><span class="perl_String">'static'</span><span class="perl_Others"> cpuset=</span><span class="perl_String">"1-4,^3,6"</span><span class="perl_Others"> current=</span><span class="perl_String">"1"</span><span class="perl_Keyword">></span>2<span class="perl_Keyword"></vcpu></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.7. CPU allocation</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-starttag"><cpu></code> element defines the maximum number of virtual CPUs allocated for the guest OS, which must be between 1 and the maximum supported by the hypervisor. This element can contain an optional <code class="sgmltag-attribute">cpuset</code> attribute, which is a comma-separated list of physical CPU numbers that domain process and virtual CPUs can be pinned to by default.
+ </div><div class="para">
+ Note that the pinning policy of domain process and virtual CPUs can be specified separately by using the <code class="sgmltag-attribute">cputune</code> attribute. If attribute <code class="sgmltag-attribute">emulatorpin</code> of <code class="sgmltag-starttag"><cputune></code> is specified, <code class="sgmltag-attribute">cpuset</code> specified by <code class="sgmltag-starttag"><vcpu></code> will be ingored.
+ </div><div class="para">
+ Similarly, virtual CPUs that have set a value for <code class="sgmltag-attribute">vcpupin</code> cause <code class="sgmltag-attribute">cpuset</code> settings to be ignored. For virtual CPUs where <code class="sgmltag-attribute">vcpupin</code> is not specified, it will be pinned to the physical CPUs specified by <code class="sgmltag-attribute">cpuset</code>. Each element in the <code class="sgmltag-attribute">cpuset</code> list is either a single CPU number, a range of CPU numbers, or a caret (^) followed by a CPU number to be excluded from a previous range. The sgmltagal attribute <code class="sgmltag-attribute">current</code> can be used to specify whether fewer than the maximum number of virtual CPUs should be enabled.
+ </div><div class="para">
+ The optional attribute <code class="sgmltag-attribute">placement</code> can be used to indicate the CPU placement mode for domain process, its value can be either <code class="sgmltag-attvalue">static</code> or <code class="sgmltag-attvalue">auto</code>, which defaults to <code class="sgmltag-attvalue">placement</code>, or <code class="sgmltag-attvalue">numatune</code>, or <code class="sgmltag-attvalue">static</code> if <code class="sgmltag-element">cpuset</code> is specified. <code class="sgmltag-attvalue">auto</code> indicates the domain process will be pinned to the advisory nodeset from querying numad, and the value of attribute <code class="sgmltag-attribute">cpuset</code> will be ignored if it's specified. If both <code class="sgmltag-attribute">cpuset</code> and <code class="sgmltag-attribute">placement</code> are not specified, or if placement is <code class="sgmltag-attvalue">static</code>, but no <code class="sgmltag-attribute">cpuset</code> is specified, the do
main process will be pinned to all the available physical CPUs.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-smbios-sys-info.html"><strong>Prev</strong>J.3. SMBIOS system information</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-cpu-tuning.html"><strong>Next</strong>J.5. CPU tuning</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-cpu-tuning.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-cpu-tuning.html
new file mode 100644
index 0000000..f15d70e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-cpu-tuning.html
@@ -0,0 +1,67 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.5. CPU tuning</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sect-cpu-allocation.html" title="J.4. CPU allocation" /><link rel="next" href="sect-mem-back.html" title="J.6. Memory backing" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-cpu-allocation.html"><strong>Prev</strong></a></li><li c
lass="next"><a accesskey="n" href="sect-mem-back.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-cpu-tuning"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.5. CPU tuning</h2></div></div></div><div class="figure" id="fig-cpu-tuning"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain></span>
+ ...
+ <span class="perl_Keyword"><cputune></span>
+ <span class="perl_Keyword"><vcpupin</span><span class="perl_Others"> vcpu=</span><span class="perl_String">"0"</span><span class="perl_Others"> cpuset=</span><span class="perl_String">"1-4,^2"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><vcpupin</span><span class="perl_Others"> vcpu=</span><span class="perl_String">"1"</span><span class="perl_Others"> cpuset=</span><span class="perl_String">"0,1"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><vcpupin</span><span class="perl_Others"> vcpu=</span><span class="perl_String">"2"</span><span class="perl_Others"> cpuset=</span><span class="perl_String">"2,3"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><vcpupin</span><span class="perl_Others"> vcpu=</span><span class="perl_String">"3"</span><span class="perl_Others"> cpuset=</span><span class="perl_String">"0,4"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><emulatorpin</span><span class="perl_Others"> cpuset=</span><span class="perl_String">"1-3"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><shares></span>2048<span class="perl_Keyword"></shares></span>
+ <span class="perl_Keyword"><period></span>1000000<span class="perl_Keyword"></period></span>
+ <span class="perl_Keyword"><quota></span>-1<span class="perl_Keyword"></quota></span>
+ <span class="perl_Keyword"><emulator_period></span>1000000<span class="perl_Keyword"></emulator_period></span>
+ <span class="perl_Keyword"><emulator_quota></span>-1<span class="perl_Keyword"></emulator_quota></span>
+ <span class="perl_Keyword"></cputune></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.8. CPU tuning</h6></div><br class="figure-break" /><div class="para">
+ Although all are optional, the components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-cpu-turn-elem"><h6>Table J.5. CPU tuning elements</h6><div class="table-contents"><table summary="CPU tuning elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><cputune></code>
+ </td><td class="">
+ Provides details regarding the CPU tunable parameters for the domain. This is optional.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><vcpupin></code>
+ </td><td class="">
+ Specifies which of host's physical CPUs the domain VCPU will be pinned to. If this is omitted, and attribute <code class="sgmltag-attribute">cpuset</code> of element <code class="sgmltag-starttag"><vcpu></code> is not specified, the vCPU is pinned to all the physical CPUs by default. It contains two required attributes, the attribute <code class="sgmltag-element">vcpu</code> specifies <code class="sgmltag-attribute">id</code>, and the attribute <code class="sgmltag-attribute">cpuset</code> is same as attribute <code class="sgmltag-attribute">cpuset</code> of element <code class="sgmltag-starttag"><vCPU></code>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><emulatorpin></code>
+ </td><td class="">
+ Specifies which of the host physical CPUs, the "emulator", a subset of a domains not including vcpu, will be pinned to. If this is omitted, and attribute <code class="sgmltag-attribute">cpuset</code> of element <code class="sgmltag-starttag"><vcpu></code> is not specified, the "emulator" is pinned to all the physical CPUs by default. It contains one required attribute <code class="sgmltag-attribute">cpuset</code> specifying which physical CPUs to pin to. <code class="sgmltag-element">emulatorpin</code> is not allowed if attribute <code class="sgmltag-attribute">placement</code> of element <code class="sgmltag-starttag"><vcpu></code> is <code class="sgmltag-attvalue">auto</code>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><shares></code>
+ </td><td class="">
+ Specifies the proportional weighted share for the domain. If this is omitted, it defaults to the OS provided defaults. If there is no unit for the value, itn is calculated relative to the setting of other guest virtual machines. For example, if a guest virtual machine is configured with value 2048 will get twice as much CPU time as a guest virtual machine configured with value 1024.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><period></code>
+ </td><td class="">
+ Specifies the enforcement intervalin microseconds. By using <code class="sgmltag-attribute">period</code>, each of the domain's vcpu will not be allowed to consume more than its alloted quota worth of runtime. This value should be within the following range: <code class="literal">1000-1000000</code>. A <code class="sgmltag-attribute">period></code> with a value of <code class="sgmltag-attvalue">0</code> means no value.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><quota></code>
+ </td><td class="">
+ Specifies the maximum allowed bandwidth in microseconds. A domain with <code class="sgmltag-element">quota</code> as any negative value indicates that the domain has infinite bandwidth, which means that it is not bandwidth controlled. The value should be within the following range:<code class="sgmltag-attvalue">1000 - 18446744073709551</code> or less than <code class="sgmltag-attvalue">0</code>. A <code class="sgmltag-attribute">quota</code> with value of <code class="sgmltag-attvalue">0</code> means no value. You can use this feature to ensure that all vcpus run at the same speed.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><emulator_period></code>
+ </td><td class="">
+ Specifies the enforcement interval in microseconds. Within an <code class="sgmltag-starttag"><emulator_period></code>, emulator threads (those excluding vcpus) of the domain will not be allowed to consume more than the <code class="sgmltag-starttag"><emulator_quota></code> worth of runtime. The <code class="sgmltag-starttag"><emulator_period></code> value should be in the following range: <code class="sgmltag-attvalue">1000 - 1000000</code>. An <code class="sgmltag-starttag"><emulator_period></code> with value of <code class="sgmltag-attvalue">0</code>, means no value.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><emulator_quota></code>
+ </td><td class="">
+ Specifies the maximum allowed bandwidth in microseconds for the domain's emulator threads (those excluding vcpus). A domain with an <code class="sgmltag-starttag"><emulator_quota></code> as a negative value indicates that the domain has infinite bandwidth for emulator threads (those excluding vcpus), which means that it is not bandwidth controlled. The value should be in the following range: <code class="sgmltag-attvalue">1000 - 18446744073709551</code>, or less than <code class="sgmltag-attvalue">0</code>. An <code class="sgmltag-starttag"><emulator_quota></code> with value <code class="sgmltag-attvalue">0</code> means no value.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-cpu-allocation.html"><strong>Prev</strong>J.4. CPU allocation</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-mem-back.html"><strong>Next</strong>J.6. Memory backing</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-dom-xml-op-sys-boot.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-dom-xml-op-sys-boot.html
new file mode 100644
index 0000000..8824bc4
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-dom-xml-op-sys-boot.html
@@ -0,0 +1,57 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.2. Operating system booting</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="next" href="sub-sect-op-sys-host-boot.html" title="J.2.2. Host bootloader" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="ch-lib-dom-xml.html"><strong>P
rev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-op-sys-host-boot.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-dom-xml-op-sys-boot"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.2. Operating system booting</h2></div></div></div><div class="para">
+ There are a number of different ways to boot virtual machines each with their own pros and cons. Each one is described in the sub-sections that follow and include: BIOS bootloader, Host bootloader, direct kerel boot, and container boot.
+ </div><div class="section" id="sub-sect-op-sys-boot-bios-boot"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.2.1. BIOS bootloader</h3></div></div></div><div class="para">
+ Booting via the BIOS is available for hypervisors supporting full virtualization. In this case the BIOS has a boot order priority (floppy, harddisk, cdrom, network) determining where to obtain/find the boot image. The OS section of the domain XML contatins the information as follows:
+ </div><div class="figure" id="fig-op-sys-boot-bios-boot"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><os></span>
+ <span class="perl_Keyword"><type></span>hvm<span class="perl_Keyword"></type></span>
+ <span class="perl_Keyword"><loader></span>/usr/lib/xen/boot/hvmloader<span class="perl_Keyword"></loader></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> dev=</span><span class="perl_String">'hd'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> dev=</span><span class="perl_String">'cdrom'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><bootmenu</span><span class="perl_Others"> enable=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><smbios</span><span class="perl_Others"> mode=</span><span class="perl_String">'sysinfo'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><bios</span><span class="perl_Others"> useserial=</span><span class="perl_String">'yes'</span><span class="perl_Others"> rebootTimeout=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></os></span>
+ ...
+</pre></div><h6>Figure J.2. BOIS bootloader domain XML</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-biosbootloader-os"><h6>Table J.2. BIOS bootloader elements</h6><div class="table-contents"><table summary="BIOS bootloader elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><type></code>
+ </td><td class="">
+ Specifies the type of operating system to be booted on the guest virtual machine. <code class="sgmltag-attvalue">hvm</code> indicates that the OS is one designed to run on bare metal, so requires full virtualization. <code class="sgmltag-attvalue">linux</code> refers to an OS that supports the Xen 3 hypervisor guest ABI. There are also two optional attributes, <code class="sgmltag-attribute">arch</code> specifying the CPU architecture to virtualization, and <code class="sgmltag-attribute">machine</code> referring to the machine type. Refer to <a href="http://libvirt.org/formatcaps.html"><em class="citetitle">Driver Capabilities</em></a> for more information.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><loader></code>
+ </td><td class="">
+ refers to a piece of firmware that is used to assist the domain creation process. It is only needed for using Xen fully virtualized domains.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><boot></code>
+ </td><td class="">
+ takes one of the values:<code class="sgmltag-attvalue">fd</code>, <code class="sgmltag-attvalue">hd</code>, <code class="sgmltag-attvalue">cdrom</code> or <code class="sgmltag-attvalue">network</code> and is used to specify the next boot device to consider. The boot element can be repeated multiple times to setup a priority list of boot devices to try in turn. Multiple devices of the same type are sorted according to their targets while preserving the order of buses. After defining the domain, its XML configuration returned by libvirt (through virDomainGetXMLDesc) lists devices in the sorted order. Once sorted, the first device is marked as bootable. For more information see <a href="http://libvirt.org/formatdomain.html#elements"><em class="citetitle">BIOS bootloader</em></a>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><bootmenu></code>
+ </td><td class="">
+ determines whether or not to enable an interactive boot menu prompt on guest startup. The <code class="sgmltag-attribute">enable</code> attribute can be either <code class="sgmltag-attvalue">yes</code> or <code class="sgmltag-attvalue">no</code>. If not specified, the hypervisor default is used
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><smbios></code>
+ </td><td class="">
+ determines how SMBIOS information is made visible in the guest. The <code class="sgmltag-attribute">mode</code> attribute must be specified, as either <code class="sgmltag-attvalue">emulate</code> (lets the hypervisor generate all values), <code class="sgmltag-attvalue">host</code>(copies all of Block 0 and Block 1, except for the UUID, from the host's SMBIOS values; the virConnectGetSysinfo call can be used to see what values are copied), or <code class="sgmltag-attvalue">sysinfo</code> (uses the values in the sysinfo element). If not specified, the hypervisor default setting is used.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><bios></code>
+ </td><td class="">
+ This element has attribute <code class="sgmltag-attribute">useserial</code> with possible values <code class="sgmltag-attvalue">yes</code> or <code class="sgmltag-attvalue">no</code>. The attribute enables or disables Serial Graphics Adapter which allows users to see BIOS messages on a serial port. Therefore, one needs to have serial port defined. Note there is another attribute, <code class="sgmltag-attribute">rebootTimeout</code> that controls whether and after how long the guest should start booting again in case the boot fails (according to BIOS). The value is in milliseconds with maximum of <code class="sgmltag-attvalue">65535</code> and special value <code class="sgmltag-attvalue">-1</code> disables the reboot.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-lib-dom-xml.html"><strong>Prev</strong>Appendix J. Manipulating the domain xml</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="sub-sect-op-sys-host-boot.html"><strong>Next</strong>J.2.2. Host bootloader</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-dynamic-vNIC.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-dynamic-vNIC.html
new file mode 100644
index 0000000..ab08a6d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-dynamic-vNIC.html
@@ -0,0 +1,51 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.16. Dynamically changing a host or a network bridge that is attached to a virtual NIC</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="sect-limit-redirection.html" title="25.15. Setting a limit on device redirection" /><link rel="next" href="chap-Virtualization_Administration_Guide-Storage_Concepts.html" title="Chapter 26. Storage concepts" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-limit-redirection.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_Guide-Storage_Concepts.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-dynamic-vNIC"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.16. Dynamically changing a host or a network bridge that is attached to a virtual NIC</h2></div></div></div><div class="para">
+ This section demonstrates how to move the vNIC of a guest from one bridge to another while the guest is running without compromising the guest
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Prepare guest with a configuration similar to the following:
+ </div><pre class="screen">
+<interface type='bridge'>
+ <mac address='52:54:00:4a:c9:5e'/>
+ <source bridge='virbr0'/>
+ <model type='virtio'/>
+</interface>
+</pre></li><li class="step"><div class="para">
+ Prepare an XML file for interface update:
+ </div><pre class="screen">#<code class="command"> cat br1.xml</code></pre><pre class="screen">
+<interface type='bridge'>
+ <mac address='52:54:00:4a:c9:5e'/>
+ <source bridge='virbr1'/>
+ <model type='virtio'/>
+</interface>
+</pre></li><li class="step"><div class="para">
+ Start the guest, confirm the guest's network functionality, and check that the guest's vnetX is connected to the bridge you indicated.
+ </div><pre class="screen">
+<code class="command"># brctl show</code>
+bridge name bridge id STP enabled interfaces
+virbr0 8000.5254007da9f2 yes virbr0-nic
+
+vnet0
+virbr1 8000.525400682996 yes virbr1-nic
+</pre></li><li class="step"><div class="para">
+ Update the guest's network with the new interface parameters with the following command:
+ </div><pre class="screen">
+<code class="command"># virsh update-device test1 br1.xml </code>
+
+Device updated successfully
+
+</pre></li><li class="step"><div class="para">
+ On the guest, run <code class="command">service network restart</code>. The guest gets a new IP address for virbr1. Check the guest's vnet0 is connected to the new bridge(virbr1)
+ </div><pre class="screen">
+# <code class="command">brctl show</code>
+bridge name bridge id STP enabled interfaces
+virbr0 8000.5254007da9f2 yes virbr0-nic
+virbr1 8000.525400682996 yes virbr1-nic vnet0
+</pre></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-limit-redirection.html"><strong>Prev</strong>25.15. Setting a limit on device redirection</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_Administration_Guide-Storage_Concepts.html"><strong>Next</strong>Chapter 26. Storage concepts</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-expand-disk-image.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-expand-disk-image.html
new file mode 100644
index 0000000..8a58896
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-expand-disk-image.html
@@ -0,0 +1,84 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.8.2. Expanding a disk image</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-virt-resize.html" title="G.8. virt-resize: resizing guests offline" /><link rel="prev" href="sect-virt-resize.html" title="G.8. virt-resize: resizing guests offline" /><link rel="next" href="sect-virt-inspector.html" title="G.9. virt-inspector: inspecting guests" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-virt-resi
ze.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-virt-inspector.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-expand-disk-image"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.8.2. Expanding a disk image</h3></div></div></div><div class="para">
+ This section demonstrates a simple case of expanding a disk image:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Locate the disk image to be resized. You can use the command <code class="command">virsh dumpxml GuestName</code> for a libvirt guest.
+ </div></li><li class="listitem"><div class="para">
+ Decide on how you wish to expand the guest. Run <code class="command">virt-df -h</code> and <code class="command">virt-list-partitions -lh</code> on the guest disk, as shown in the following output:
+ </div><pre class="screen">
+# virt-df -h /dev/vg_guests/RHEL6
+Filesystem Size Used Available Use%
+RHEL6:/dev/sda1 98.7M 10.0M 83.6M 11%
+RHEL6:/dev/VolGroup00/LogVol00 6.8G 2.2G 4.3G 32%
+
+# virt-list-partitions -lh /dev/vg_guests/RHEL6
+/dev/sda1 ext3 101.9M
+/dev/sda2 pv 7.9G
+</pre></li></ol></div><div class="para">
+ This example will demonstrate how to:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Increase the size of the first (boot) partition, from approximately 100MB to 500MB.
+ </div></li><li class="listitem"><div class="para">
+ Increase the total disk size from 8GB to 16GB.
+ </div></li><li class="listitem"><div class="para">
+ Expand the second partition to fill the remaining space.
+ </div></li><li class="listitem"><div class="para">
+ Expand <code class="filename">/dev/VolGroup00/LogVol00</code> to fill the new space in the second partition.
+ </div></li></ul></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Make sure the guest is shut down.
+ </div></li><li class="listitem"><div class="para">
+ Rename the original disk as the backup. How you do this depends on the host storage environment for the original disk. If it is stored as a file, use the <code class="command">mv</code> command. For logical volumes (as demonstrated in this example), use <code class="command">lvrename</code>:
+ </div><pre class="screen">
+# lvrename /dev/vg_guests/RHEL6 /dev/vg_guests/RHEL6.backup
+</pre></li><li class="listitem"><div class="para">
+ Create the new disk. The requirements in this example are to expand the total disk size up to 16GB. Since logical volumes are used here, the following command is used:
+ </div><pre class="screen">
+# lvcreate -L 16G -n RHEL6 /dev/vg_guests
+Logical volume "RHEL6" created
+</pre></li><li class="listitem"><div class="para">
+ The requirements from step 2 are expressed by this command:
+ </div><pre class="screen">
+# virt-resize \
+ /dev/vg_guests/RHEL6.backup /dev/vg_guests/RHEL6 \
+ --resize /dev/sda1=500M \
+ --expand /dev/sda2 \
+ --LV-expand /dev/VolGroup00/LogVol00
+</pre><div class="para">
+ The first two arguments are the input disk and output disk. <code class="command">--resize /dev/sda1=500M</code> resizes the first partition up to 500MB. <code class="command">--expand /dev/sda2</code> expands the second partition to fill all remaining space. <code class="command">--LV-expand /dev/VolGroup00/LogVol00</code> expands the guest logical volume to fill the extra space in the second partition.
+ </div><div class="para">
+ <code class="command">virt-resize</code> describes what it is doing in the output:
+ </div><pre class="screen">
+Summary of changes:
+ /dev/sda1: partition will be resized from 101.9M to 500.0M
+ /dev/sda1: content will be expanded using the 'resize2fs' method
+ /dev/sda2: partition will be resized from 7.9G to 15.5G
+ /dev/sda2: content will be expanded using the 'pvresize' method
+ /dev/VolGroup00/LogVol00: LV will be expanded to maximum size
+ /dev/VolGroup00/LogVol00: content will be expanded using the 'resize2fs' method
+ Copying /dev/sda1 ...
+ [#####################################################]
+ Copying /dev/sda2 ...
+ [#####################################################]
+ Expanding /dev/sda1 using the 'resize2fs' method
+ Expanding /dev/sda2 using the 'pvresize' method
+ Expanding /dev/VolGroup00/LogVol00 using the 'resize2fs' method
+</pre></li><li class="listitem"><div class="para">
+ Try to boot the virtual machine. If it works (and after testing it thoroughly) you can delete the backup disk. If it fails, shut down the virtual machine, delete the new disk, and rename the backup disk back to its original name.
+ </div></li><li class="listitem"><div class="para">
+ Use <code class="command">virt-df</code> and/or <code class="command">virt-list-partitions</code> to show the new size:
+ </div><pre class="screen">
+# virt-df -h /dev/vg_pin/RHEL6
+ Filesystem Size Used Available Use%
+ RHEL6:/dev/sda1 484.4M 10.8M 448.6M 3%
+ RHEL6:/dev/VolGroup00/LogVol00 14.3G 2.2G 11.4G 16%
+</pre></li></ol></div><div class="para">
+ Resizing guests is not an exact science. If <code class="command">virt-resize</code> fails, there are a number of tips that you can review and attempt in the virt-resize(1) man page. For some older Red Hat Enterprise Linux guests, you may need to pay particular attention to the tip regarding GRUB.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-virt-resize.html"><strong>Prev</strong>G.8. virt-resize: resizing guests offline</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-virt-inspector.html"><strong>Next</strong>G.9. virt-inspector: inspecting guests</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-gracefully-shut-down-guests.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-gracefully-shut-down-guests.html
new file mode 100644
index 0000000..27bb40a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-gracefully-shut-down-guests.html
@@ -0,0 +1,27 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.10. Gracefully shutting down guests</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server.html" title="25.9. Configuring a VNC Server" /><link rel="next" href="sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers.html" title="25.11. Virtual machine timer management with libvirt" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-gracefully-shut-down-guests"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.10. Gracefully shutting down guests</h2></div></div></div><div class="para">
+ Installing virtualized Fedora 19 guests with the <code class="option">Minimal installation</code> option will not install the <span class="package">acpid</span> package.
+ </div><div class="para">
+ Without the <span class="package">acpid</span> package, the Fedora guest does not shut down when the <code class="command">virsh shutdown</code> command is executed. The <code class="command">virsh shutdown</code> command is designed to gracefully shut down guests.
+ </div><div class="para">
+ Using <code class="command">virsh shutdown</code> is easier and safer for system administration. Without graceful shut down with the <code class="command">virsh shutdown</code> command a system administrator must log into a guest manually or send the <span class="keycap"><strong>Ctrl</strong></span>-<span class="keycap"><strong>Alt</strong></span>-<span class="keycap"><strong>Del</strong></span> key combination to each guest.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Other virtualized operating systems may be affected by this issue. The <code class="command">virsh shutdown</code> command requires that the guest operating system is configured to handle ACPI shut down requests. Many operating systems require additional configuration on the guest operating system to accept ACPI shut down requests.
+ </div></div></div><div class="procedure"><h6>Procedure 25.1. Workaround for Fedora</h6><ol class="1"><li class="step"><p class="title"><strong>Install the acpid package</strong></p><div class="para">
+ The <code class="command">acpid</code> service listen and processes ACPI requests.
+ </div><div class="para">
+ Log into the guest and install the <span class="package">acpid</span> package on the guest:
+ </div><pre class="screen"># yum install acpid</pre></li><li class="step"><p class="title"><strong>Enable the acpid service</strong></p><div class="para">
+ Set the <code class="systemitem">acpid</code> service to start during the guest boot sequence and start the service:
+ </div><pre class="screen"># chkconfig acpid on
+# service acpid start</pre></li></ol></div><div class="para">
+ The guest is now configured to shut down when the <code class="command">virsh shutdown</code> command is used.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Tips_and_tricks-Configuring_a_VNC_Server.html"><strong>Prev</strong>25.9. 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-Tips_and_tricks-Libvirt_Managed_Timers.html"><strong>Next</strong>25.11. Virtual machine timer management with libv...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-guest-cpu-model-config.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-guest-cpu-model-config.html
new file mode 100644
index 0000000..a261f97
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-guest-cpu-model-config.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.14. Guest CPU model configuration</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="prev" href="sub-sect-blkresize.html" title="E.13.3. Using blockresize to change the size of a domain path" /><link rel="next" href="sect-learn-about-host-cpu.html" title="E.14.2. Learning about the host CPU model" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sect-blkresize.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-learn-about-host-cpu.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-guest-cpu-model-config"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">E.14. Guest CPU model configuration</h2></div></div></div><div class="section" id="sect-guest-cpu-intro"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.14.1. Introduction</h3></div></div></div><div class="para">
+ Every hypervisor has its own policy for what a guest will see for its CPUs by default. Whereas some hypervisors decide which CPU host features will be available for the guest, QEMU/KVM presents the guest with a generic model named <span class="bold bold"><strong>qemu32</strong></span> or <span class="bold bold"><strong>qemu64</strong></span>. These hypervisors perform more advanced filtering, classifying all physical CPUs into a handful of groups and have one baseline CPU model for each group that is presented to the guest. Such behavior enables the safe migration of guests between hosts, provided they all have physical CPUs that classify into the same group. libvirt does not typically enforce policy itself, rather it provides the mechanism on which the higher layers define their own desired policy. Understanding how to obtain CPU model information and define a suitable guest CPU model is critical to ensure guest migration is successful between hosts. Note that a hypervi
sor can only emulate features that it is aware of and features that were created after the hypervisor was released may not be emulated.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-blkresize.html"><strong>Prev</strong>E.13.3. Using blockresize to change the size of 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-learn-about-host-cpu.html"><strong>Next</strong>E.14.2. Learning about the host CPU model</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-learn-about-host-cpu.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-learn-about-host-cpu.html
new file mode 100644
index 0000000..507c76e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-learn-about-host-cpu.html
@@ -0,0 +1,44 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.14.2. Learning about the host CPU model</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-guest-cpu-model-config.html" title="E.14. Guest CPU model configuration" /><link rel="prev" href="sect-guest-cpu-model-config.html" title="E.14. Guest CPU model configuration" /><link rel="next" href="apes14s03.html" title="E.14.3. Determining a compatible CPU model to suit a pool of hosts" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 access
key="p" href="sect-guest-cpu-model-config.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apes14s03.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-learn-about-host-cpu"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.14.2. Learning about the host CPU model</h3></div></div></div><div class="para">
+ The <code class="command">virsh capabilities</code> command displays an XML document describing the capabilities of the hypervisor connection and host. The XML schema displayed has been extended to provide information about the host CPU model. One of the big challenges in describing a CPU model is that every architecture has a different approach to exposing their capabilities. On x86, the capabilities of a modern CPU are exposed via the CPUID instruction. Essentially this comes down to a set of 32-bit integers with each bit given a specific meaning. Fortunately AMD and Intel agree on common semantics for these bits. Other hypervisors expose the notion of CPUID masks directly in their guest configuration format. However, QEMU/KVM supports far more than just the x86 architecture, so CPUID is clearly not suitable as the canonical configuration format. QEMU ended up using a scheme which combines a CPU model name string, with a set of named flags. On x86, the CPU model maps t
o a baseline CPUID mask, and the flags can be used to then toggle bits in the mask on or off. libvirt decided to follow this lead and uses a combination of a model name and flags. Here is an example of what libvirt reports as the capabilities on a development workstation:
+ </div><pre class="screen">
+# virsh capabilities
+<capabilities>
+
+ <host>
+ <uuid>c4a68e53-3f41-6d9e-baaf-d33a181ccfa0</uuid>
+ <cpu>
+ <arch>x86_64</arch>
+ <model>core2duo</model>
+ <topology sockets='1' cores='4' threads='1'/>
+ <feature name='lahf_lm'/>
+ <feature name='sse4.1'/>
+ <feature name='xtpr'/>
+ <feature name='cx16'/>
+ <feature name='tm2'/>
+ <feature name='est'/>
+ <feature name='vmx'/>
+ <feature name='ds_cpl'/>
+ <feature name='pbe'/>
+ <feature name='tm'/>
+ <feature name='ht'/>
+ <feature name='ss'/>
+ <feature name='acpi'/>
+ <feature name='ds'/>
+ </cpu>
+
+ ... snip ...
+ </host>
+
+</capabilities>
+</pre><div class="para">
+ It is not practical to have a database listing all known CPU models, so libvirt has a small list of baseline CPU model names. It chooses the one that shares the greatest number of CPUID bits with the actual host CPU and then lists the remaining bits as named features. Notice that libvirt does not display which features the baseline CPU contains. This might seem like a flaw at first, but as will be explained in this section, it is not actually necessary to know this information.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-guest-cpu-model-config.html"><strong>Prev</strong>E.14. Guest CPU model 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="apes14s03.html"><strong>Next</strong>E.14.3. Determining a compatible CPU model to sui...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libguestfs-more-docs.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libguestfs-more-docs.html
new file mode 100644
index 0000000..6503f9c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libguestfs-more-docs.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.13. Where to find further documentation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /><link rel="prev" href="sect-libguestfs-troubleshoot.html" title="G.12. Troubleshooting" /><link rel="next" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html" title="Appendix H. Virtual Networking" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-libguestfs-troubleshoot.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-libguestfs-more-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">G.13. Where to find further documentation</h2></div></div></div><div class="para">
+ The primary source for documentation for libguestfs and the tools are the Unix man pages. The API is documented in guestfs(3). guestfish is documented in guestfish(1). The virt tools are documented in their own man pages (eg. virt-df(1)).
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libguestfs-troubleshoot.html"><strong>Prev</strong>G.12. 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="chap-Virtualization_Administration_Guide-Virtual_Networking.html"><strong>Next</strong>Appendix H. Virtual Networking</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libguestfs-troubleshoot.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libguestfs-troubleshoot.html
new file mode 100644
index 0000000..60fea9a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libguestfs-troubleshoot.html
@@ -0,0 +1,16 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.12. Troubleshooting</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /><link rel="prev" href="sect-Using-API-Programming-Languages.html" title="G.11. Using the API from Programming Languages" /><link rel="next" href="sect-libguestfs-more-docs.html" title="G.13. Where to find further documentation" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-Using-API-Programming-Languages.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-libguestfs-more-docs.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-libguestfs-troubleshoot"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">G.12. Troubleshooting</h2></div></div></div><div class="para">
+ A test tool is available to check that libguestfs is working. Run the following command after installing libguestfs (root access not required) to test for normal operation:
+ </div><pre class="screen">
+$ libguestfs-test-tool
+</pre><div class="para">
+ This tool prints a large amount of text to test the operation of libguestfs. If the test is successful, the following text will appear near the end of the output:
+ </div><pre class="screen">===== TEST FINISHED OK =====</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Using-API-Programming-Languages.html"><strong>Prev</strong>G.11. Using the API from Programming Languages</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-libguestfs-more-docs.html"><strong>Next</strong>G.13. Where to find further documentation</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-blk-io-tuning.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-blk-io-tuning.html
new file mode 100644
index 0000000..2e58542
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-blk-io-tuning.html
@@ -0,0 +1,46 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.9. Block I/O tuning</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sect-libvirt-dom-xml-numa-node-tuning.html" title="J.8. NUMA node tuning" /><link rel="next" href="sect-libvirt-dom-xml-res-part.html" title="J.10. Resource partitioning" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-libvirt-dom-
xml-numa-node-tuning.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-libvirt-dom-xml-res-part.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-libvirt-dom-xml-blk-io-tuning"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.9. Block I/O tuning</h2></div></div></div><div class="figure" id="fig-blk-io-tuning"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain></span>
+ ...
+ <span class="perl_Keyword"><blkiotune></span>
+ <span class="perl_Keyword"><weight></span>800<span class="perl_Keyword"></weight></span>
+ <span class="perl_Keyword"><device></span>
+ <span class="perl_Keyword"><path></span>/dev/sda<span class="perl_Keyword"></path></span>
+ <span class="perl_Keyword"><weight></span>1000<span class="perl_Keyword"></weight></span>
+ <span class="perl_Keyword"></device></span>
+ <span class="perl_Keyword"><device></span>
+ <span class="perl_Keyword"><path></span>/dev/sdb<span class="perl_Keyword"></path></span>
+ <span class="perl_Keyword"><weight></span>500<span class="perl_Keyword"></weight></span>
+ <span class="perl_Keyword"></device></span>
+ <span class="perl_Keyword"></blkiotune></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.12. Block I/O tuning</h6></div><br class="figure-break" /><div class="para">
+ Although all are optional, the components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-blk-io-elem"><h6>Table J.8. Block I/O tuning elements</h6><div class="table-contents"><table summary="Block I/O tuning elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><blkiotune></code>
+ </td><td class="">
+ This optional element provides the ability to tune Blkio cgroup tunable parameters for the domain. If this is omitted, it defaults to the OS provided defaults.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><weight></code>
+ </td><td class="">
+ This optional weight element is the overall I/O weight of the guest. The value should be within the range 100 - 1000.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><device></code>
+ </td><td class="">
+ The domain may have multiple <code class="sgmltag-starttag"><device></code> elements that further tune the weights for each host block device in use by the domain. Note that multiple guest disks can share a single host block device. In addition, as they are backed by files within the same host file system, this tuning parameter is at the global domain level, rather than being associated with each guest disk device (contrast this to the <code class="sgmltag-starttag"><iotune></code> element which can be applied to a single <code class="sgmltag-starttag"><disk></code>). Each device element has two mandatory sub-elements, <code class="sgmltag-starttag"><path></code> describing the absolute path of the device, and <code class="sgmltag-starttag"><weight></code> giving the relative weight of that device, which has an acceptable range of 100 - 1000.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-numa-node-tuning.html"><strong>Prev</strong>J.8. NUMA node tuning</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-libvirt-dom-xml-res-part.html"><strong>Next</strong>J.10. Resource partitioning</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-cpu-model-top.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-cpu-model-top.html
new file mode 100644
index 0000000..334dfe8
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-cpu-model-top.html
@@ -0,0 +1,124 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.11. CPU model and topology</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sect-libvirt-dom-xml-res-part.html" title="J.10. Resource partitioning" /><link rel="next" href="sect-libvirt-dom-xml-event-config.html" title="J.12. Events configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-libvirt-dom
-xml-res-part.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-libvirt-dom-xml-event-config.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-libvirt-dom-xml-cpu-model-top"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.11. CPU model and topology</h2></div></div></div><div class="para">
+ This section covers the requirements for CPU model. Its features and topology is specified using the following elements from the domain XML:
+ </div><div class="figure" id="fig-xml-cpu-model-top"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><cpu</span><span class="perl_Others"> match=</span><span class="perl_String">'exact'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><model</span><span class="perl_Others"> fallback=</span><span class="perl_String">'allow'</span><span class="perl_Keyword">></span>core2duo<span class="perl_Keyword"></model></span>
+ <span class="perl_Keyword"><vendor></span>Intel<span class="perl_Keyword"></vendor></span>
+ <span class="perl_Keyword"><topology</span><span class="perl_Others"> sockets=</span><span class="perl_String">'1'</span><span class="perl_Others"> cores=</span><span class="perl_String">'2'</span><span class="perl_Others"> threads=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><feature</span><span class="perl_Others"> policy=</span><span class="perl_String">'disable'</span><span class="perl_Others"> name=</span><span class="perl_String">'lahf_lm'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></cpu></span>
+ ...
+
+</pre></div><h6>Figure J.14. CPU model and topology example 1</h6></div><br class="figure-break" /><div class="figure" id="fig-xml-cpu-model-top2"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><cpu</span><span class="perl_Others"> mode=</span><span class="perl_String">'host-model'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><model</span><span class="perl_Others"> fallback=</span><span class="perl_String">'forbid'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><topology</span><span class="perl_Others"> sockets=</span><span class="perl_String">'1'</span><span class="perl_Others"> cores=</span><span class="perl_String">'2'</span><span class="perl_Others"> threads=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+<span class="perl_Keyword"></cpu></span>
+ ...
+</pre></div><h6>Figure J.15. CPU model and topology example 2</h6></div><br class="figure-break" /><div class="figure" id="fig-xml-cpu-model-top3"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><cpu</span><span class="perl_Others"> mode=</span><span class="perl_String">'host-passthrough'</span><span class="perl_Keyword">/></span>
+
+</pre></div><h6>Figure J.16. CPU model and topology example 3</h6></div><br class="figure-break" /><div class="para">
+ In cases where no restrictions are to be put on either the CPU model nor its features, a simpler cpu element such as the following may be used.
+ </div><div class="figure" id="fig-xml-cpu-model-top4"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><cpu></span>
+ <span class="perl_Keyword"><topology</span><span class="perl_Others"> sockets=</span><span class="perl_String">'1'</span><span class="perl_Others"> cores=</span><span class="perl_String">'2'</span><span class="perl_Others"> threads=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></cpu></span>
+ ...
+
+</pre></div><h6>Figure J.17. CPU model and topology example 4</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-cpu-model-elem"><h6>Table J.9. CPU model and topology elements</h6><div class="table-contents"><table summary="CPU model and topology elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><cpu></code>
+ </td><td class="">
+ This is the main container for describing guest CPU requirements.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><match></code>
+ </td><td class="">
+ Specifies how the virtual CPU is provided to the guest match for these requirements. The <code class="sgmltag-attribute">match</code> attribute can be omitted if topology is the only element within <code class="sgmltag-starttag"><cpu></code>. Possible values for the <code class="sgmltag-attribute">match</code> attribute are:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">minimum</code> - the specified CPU model and features describes the minimum requested CPU.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">exact</code> - the virtual CPU provided to the guest will exactly match the specification
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">strict</code> - the guest will not be created unless the host CPU exactly matches the specification.
+ </div></li></ul></div>
+ Note that the <code class="sgmltag-attribute">match</code> attribute can be omitted and will default to <code class="sgmltag-attvalue">exact</code>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><mode></code>
+ </td><td class="">
+ This optional attribute may be used to make it easier to configure a guest CPU to be as close to the host CPU as possible. Possible values for the mode attribute are:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">custom</code> - describes how the CPU is presented to the guest. This is the default setting when the <code class="sgmltag-attribute">mode</code> attribute is not specified. This mode makes it so that a persistent guest will see the same hardware no matter what host the guest is booted on.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">host-model</code> - this is essentially a shortcut to copying host CPU definition from the capabilities XML into the domain XML. As the CPU definition is copied just before starting a domain, the same XML can be used on different hosts while still providing the best guest CPU each host supports. Neither the <code class="sgmltag-attribute">match</code> attribute nor any feature elements can be used in this mode. For more information see <a href="http://libvirt.org/formatdomain.html">libvirt domain XML CPU models</a>
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">host-passthrough</code> With this mode, the CPU visible to the guest is exactly the same as the host CPU including elements that cause errors within libvirt. The obvious the downside of this mode is that the guest environment cannot be reproduced on different hardware and therefore this mode is recommended with great caution. Neither <code class="sgmltag-element">model</code> nor <code class="sgmltag-element">feature</code> elements are allowed in this mode.
+ </div></li><li class="listitem"><div class="para">
+ Note that in both <code class="sgmltag-element">host-model</code> and <code class="sgmltag-element">host-passthrough</code> mode, the real (approximate in host-passthrough mode) CPU definition which would be used on current host can be determined by specifying VIR_DOMAIN_XML_UPDATE_CPU flag when calling virDomainGetXMLDesc API. When running a guest that might be prone to operating system reactivation when presented with different hardware, and which will be migrated between hosts with different capabilities, you can use this output to rewrite XML to the custom mode for more robust migration.
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><model></code>
+ </td><td class="">
+ Specifies CPU model requested by the guest. The list of available CPU models and their definition can be found in <code class="filename">cpu_map.xml</code> file installed in libvirt's data directory. If a hypervisor is not able to use the exact CPU model, libvirt automatically falls back to a closest model supported by the hypervisor while maintaining the list of CPU features. An optional <code class="sgmltag-attribute">fallback</code> attribute can be used to forbid this behavior, in which case an attempt to start a domain requesting an unsupported CPU model will fail. Supported values for fallback attribute are: <code class="sgmltag-attvalue">allow</code> (this is the default), and <code class="sgmltag-attvalue">forbid</code>. The optional <code class="sgmltag-attribute">vendor_id</code> attribute can be used to set the vendor id seen by the guest. It must be exactly 12 characters long. If not set, the vendor id of the host is used. Typical possible values are <code
class="sgmltag-attvalue">AuthenticAMD</code> and <code class="sgmltag-attvalue">GenuineIntel</code>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><vendor></code>
+ </td><td class="">
+ Specifies CPU vendor requested by the guest. If this element is missing, the guest runs on a CPU matching given features regardless of its vendor. The list of supported vendors can be found in <code class="filename">cpu_map.xml</code>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><topology></code>
+ </td><td class="">
+ Specifies requested topology of virtual CPU provided to the guest. Three non-zero values have to be given for sockets, cores, and threads: total number of CPU sockets, number of cores per socket, and number of threads per core, respectively.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><feature></code>
+ </td><td class="">
+ Can contain zero or more elements used to fine-tune features provided by the selected CPU model. The list of known feature names can be found in the same file as CPU models. The meaning of each feature element depends on its policy attribute, which has to be set to one of the following values:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">force</code> - forces the virtual to be supported regardless of whether it is actually supported by host CPU.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">require</code> - dictates that guest creation will fail unless the feature is supported by host CPU. This is the default setting
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">optional</code> - this feature is supported by virtual CPU but and only if it is supported by host CPU.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">disable</code> - this is not supported by virtual CPU.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">forbid</code> - guest creation will fail if the feature is supported by host CPU.
+ </div></li></ul></div>
+
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="section" id="sub-sect-libvirt-dom-xml-res-part-guest-numa"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.11.1. Guest NUMA topology</h3></div></div></div><div class="para">
+ Guest NUMA topology can be specifed using the numa element and the following from the domain XML:
+ </div><div class="figure" id="fig-xml-cpu-model-top-numa"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><cpu></span>
+ ...
+ <span class="perl_Keyword"><numa></span>
+ <span class="perl_Keyword"><cell</span><span class="perl_Others"> cpus=</span><span class="perl_String">'0-3'</span><span class="perl_Others"> memory=</span><span class="perl_String">'512000'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><cell</span><span class="perl_Others"> cpus=</span><span class="perl_String">'4-7'</span><span class="perl_Others"> memory=</span><span class="perl_String">'512000'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></numa></span>
+ ...
+ <span class="perl_Keyword"></cpu></span>
+ ...
+</pre></div><h6>Figure J.18. Guest NUMA topology</h6></div><br class="figure-break" /><div class="para">
+ Each cell element specifies a NUMA cell or a NUMA node. <code class="sgmltag-attribute">cpus</code> specifies the CPU or range of CPUs that are part of the node. <code class="sgmltag-attribute">memory</code> specifies the node memory in kibibytes (i.e. blocks of 1024 bytes). Each cell or node is assigned <code class="sgmltag-attribute">cellid</code> or <code class="sgmltag-attribute">nodeid</code> in increasing order starting from 0.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-res-part.html"><strong>Prev</strong>J.10. Resource partitioning</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-libvirt-dom-xml-event-config.html"><strong>Next</strong>J.12. Events configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-devices.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-devices.html
new file mode 100644
index 0000000..edbc409
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-devices.html
@@ -0,0 +1,201 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16. Devices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sect-libvirt-dom-xml-time-keep.html" title="J.15. Time keeping" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-filesystems.html" title="J.16.2. Filesystems" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-libvirt-dom-
xml-time-keep.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-filesystems.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-libvirt-dom-xml-devices"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.16. Devices</h2></div></div></div><div class="para">
+ This set of XML elements are all used to describe devices provided to the guest domain. All of the devices below are indicated as children of the main devices element.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><emulator></span>/usr/lib/xen/bin/qemu-dm<span class="perl_Keyword"></emulator></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.23. Devices - child elements</h6></div><br class="figure-break" /><div class="para">
+ The contents of the <code class="sgmltag-starttag"><emulator></code> element specify the fully qualified path to the device model emulator binary. The capabilities XML specifies the recommended default emulator to use for each particular domain type or architecture combination.
+ </div><div class="section" id="sub-sect-libvirt-dom-xml-devices"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.1. Hard drives, floppy disks, CDROMs</h3></div></div></div><div class="para">
+ This section of the domain XML specifies any device that looks like a disk, be it a floppy, harddisk, cdrom, or paravirtualized driver is specified via the disk element.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-cds"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'file'</span><span class="perl_Others"> snapshot=</span><span class="perl_String">'external'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">"tap"</span><span class="perl_Others"> type=</span><span class="perl_String">"aio"</span><span class="perl_Others"> cache=</span><span class="perl_String">"default"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> file=</span><span class="perl_String">'/var/lib/xen/images/fv0'</span><span class="perl_Others"> startupPolicy=</span><span class="perl_String">'optional'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><seclabel</span><span class="perl_Others"> relabel=</span><span class="perl_String">'no'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></source></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hda'</span><span class="perl_Others"> bus=</span><span class="perl_String">'ide'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><iotune></span>
+ <span class="perl_Keyword"><total_bytes_sec></span>10000000<span class="perl_Keyword"></total_bytes_sec></span>
+ <span class="perl_Keyword"><read_iops_sec></span>400000<span class="perl_Keyword"></read_iops_sec></span>
+ <span class="perl_Keyword"><write_iops_sec></span>100000<span class="perl_Keyword"></write_iops_sec></span>
+ <span class="perl_Keyword"></iotune></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'2'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><encryption</span><span class="perl_Others"> type=</span><span class="perl_String">'...'</span><span class="perl_Keyword">></span>
+ ...
+ <span class="perl_Keyword"></encryption></span>
+ <span class="perl_Keyword"><shareable/></span>
+ <span class="perl_Keyword"><serial></span>
+ ...
+ <span class="perl_Keyword"></serial></span>
+ <span class="perl_Keyword"></disk></span>
+ ...
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">"qemu"</span><span class="perl_Others"> type=</span><span class="perl_String">"raw"</span><span class="perl_Others"> io=</span><span class="perl_String">"threads"</span><span class="perl_Others"> ioeventfd=</span><span class="perl_String">"on"</span><span class="perl_Others"> event_idx=</span><span class="perl_String">"off"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> protocol=</span><span class="perl_String">"sheepdog"</span><span class="perl_Others"> name=</span><span class="perl_String">"image_name"</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><host</span><span class="perl_Others"> name=</span><span class="perl_String">"hostname"</span><span class="perl_Others"> port=</span><span class="perl_String">"7000"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></source></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">"hdb"</span><span class="perl_Others"> bus=</span><span class="perl_String">"ide"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><transient/></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'drive'</span><span class="perl_Others"> controller=</span><span class="perl_String">'0'</span><span class="perl_Others"> bus=</span><span class="perl_String">'1'</span><span class="perl_Others"> unit=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">"qemu"</span><span class="perl_Others"> type=</span><span class="perl_String">"raw"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> protocol=</span><span class="perl_String">"rbd"</span><span class="perl_Others"> name=</span><span class="perl_String">"image_name2"</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><host</span><span class="perl_Others"> name=</span><span class="perl_String">"hostname"</span><span class="perl_Others"> port=</span><span class="perl_String">"7000"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></source></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">"hdd"</span><span class="perl_Others"> bus=</span><span class="perl_String">"ide"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><auth</span><span class="perl_Others"> username=</span><span class="perl_String">'myuser'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><secret</span><span class="perl_Others"> type=</span><span class="perl_String">'ceph'</span><span class="perl_Others"> usage=</span><span class="perl_String">'mypassid'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></auth></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'block'</span><span class="perl_Others"> device=</span><span class="perl_String">'cdrom'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">'qemu'</span><span class="perl_Others"> type=</span><span class="perl_String">'raw'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hdc'</span><span class="perl_Others"> bus=</span><span class="perl_String">'ide'</span><span class="perl_Others"> tray=</span><span class="perl_String">'open'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><readonly/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'block'</span><span class="perl_Others"> device=</span><span class="perl_String">'lun'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">'qemu'</span><span class="perl_Others"> type=</span><span class="perl_String">'raw'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> dev=</span><span class="perl_String">'/dev/sda'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'sda'</span><span class="perl_Others"> bus=</span><span class="perl_String">'scsi'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'drive'</span><span class="perl_Others"> controller=</span><span class="perl_String">'0'</span><span class="perl_Others"> bus=</span><span class="perl_String">'0'</span><span class="perl_Others"> target=</span><span class="perl_String">'3'</span><span class="perl_Others"> unit=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'block'</span><span class="perl_Others"> device=</span><span class="perl_String">'disk'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">'qemu'</span><span class="perl_Others"> type=</span><span class="perl_String">'raw'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> dev=</span><span class="perl_String">'/dev/sda'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><geometry</span><span class="perl_Others"> cyls=</span><span class="perl_String">'16383'</span><span class="perl_Others"> heads=</span><span class="perl_String">'16'</span><span class="perl_Others"> secs=</span><span class="perl_String">'63'</span><span class="perl_Others"> trans=</span><span class="perl_String">'lba'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><blockio</span><span class="perl_Others"> logical_block_size=</span><span class="perl_String">'512'</span><span class="perl_Others"> physical_block_size=</span><span class="perl_String">'4096'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hda'</span><span class="perl_Others"> bus=</span><span class="perl_String">'ide'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'volume'</span><span class="perl_Others"> device=</span><span class="perl_String">'disk'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">'qemu'</span><span class="perl_Others"> type=</span><span class="perl_String">'raw'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> pool=</span><span class="perl_String">'blk-pool0'</span><span class="perl_Others"> volume=</span><span class="perl_String">'blk-pool0-vol0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hda'</span><span class="perl_Others"> bus=</span><span class="perl_String">'ide'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.24. Devices - Hard drives, floppy disks, CDROMs</h6></div><br class="figure-break" /><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-disk"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.1.1. Disk element</h4></div></div></div><div class="para">
+ The <code class="sgmltag-starttag"><disk></code> element is the main container for describing disks. The attribute <code class="sgmltag-attribute">type</code> can be used with the <code class="sgmltag-starttag"><disk></code> element. The following types are allowed:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">file</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">block</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">dir</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">network</code>
+ </div></li></ul></div><div class="para">
+ For more information, see <a href="http://libvirt.org/formatdomain.html">Disk Elements</a>
+ </div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-source"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.1.2. Source element</h4></div></div></div><div class="para">
+ If the <code class="sgmltag-starttag"><disk type='file''></code>, then the <code class="sgmltag-attribute">file</code> attribute specifies the fully-qualified path to the file holding the disk. If the <code class="sgmltag-starttag"><disk type='block'></code>, then the <code class="sgmltag-attribute">dev</code> attribute specifies the path to the host device to serve as the disk. With both <code class="sgmltag-attvalue">file</code> and <code class="sgmltag-attvalue">block</code>, one or more optional sub-elements <code class="sgmltag-element">seclabel</code>, described below, can be used to override the domain security labeling policy for just that source file. If the disk type is <code class="sgmltag-attvalue">dir</code>, then the <code class="sgmltag-attribute">dir</code> attribute specifies the fully-qualified path to the directory to use as the disk. If the disk type is <code class="sgmltag-attvalue">network</code>, then the protocol attribute specifies t
he protocol to access to the requested image; possible values are <code class="sgmltag-attvalue">nbd</code>, <code class="sgmltag-attvalue">rbd</code>, <code class="sgmltag-attvalue">sheepdog</code> or <code class="sgmltag-attvalue">gluster</code>.
+ </div><div class="para">
+ If the protocol attribute is <code class="sgmltag-attvalue">rbd</code>, <code class="sgmltag-attvalue">sheepdog</code> or <code class="sgmltag-attvalue">gluster</code>, an additional attribute <code class="sgmltag-attvalue">name</code> is mandatory to specify which volume and or image will be used. When the disk type is <code class="sgmltag-attvalue">network</code>, the <code class="sgmltag-attvalue">source</code> may have zero or more <code class="sgmltag-element">host</code> sub-elements used to specify the hosts to connect, including: <code class="sgmltag-attvalue">type='dir'</code> and <code class="sgmltag-attvalue">type='network'</code>. For a <code class="sgmltag-attvalue">file</code> disk type which represents a cdrom or floppy (the device attribute), it is possible to define policy what to do with the disk if the source file is not accessible. This is done by manipulating the <code class="sgmltag-attribute">startupPolicy</code> attribute, with the following valu
es:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">mandatory</code> causes a failure if missing for any reason. This is the default setting.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">requisite</code> causes a failure if missing on boot up, drops if missing on migrate/restore/revert
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">optional</code> drops if missing at any start attempt
+ </div></li></ul></div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-mirror"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.1.3. Mirror element</h4></div></div></div><div class="para">
+ This element is present if the hypervisor has started a <code class="command">BlockCopy</code> operation, where the <code class="sgmltag-starttag"><mirror></code> location in the attribute file will eventually have the same contents as the source, and with the file format in attribute format (which might differ from the format of the source). If an attribute ready is present, then it is known the disk is ready to pivot; otherwise, the disk is probably still copying. For now, this element only valid in output; it is ignored on input.
+ </div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-target"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.1.4. Target element</h4></div></div></div><div class="para">
+ The <code class="sgmltag-starttag"><target></code> element controls the bus / device under which the disk is exposed to the guest OS. The dev attribute indicates the logical device name. The actual device name specified is not guaranteed to map to the device name in the guest OS. The optional bus attribute specifies the type of disk device to emulate; possible values are driver specific, with typical values being <code class="sgmltag-attvalue">ide</code>, <code class="sgmltag-attvalue">scsi</code>, <code class="sgmltag-attvalue">virtio</code>, <code class="sgmltag-attvalue">xen</code>, <code class="sgmltag-attvalue">usb</code> or <code class="sgmltag-attvalue">sata</code>. If omitted, the bus type is inferred from the style of the device name. eg, a device named <code class="filename">'sda'</code> will typically be exported using a SCSI bus. The optional attribute <code class="sgmltag-attribute">tray</code> indicates the tray status of the removable disks (i.e. CD
ROM or Floppy disk), the value can be either <code class="sgmltag-attvalue">open</code> or <code class="sgmltag-attvalue">closed</code>. The default setting is <code class="sgmltag-attvalue">closed</code>. For more information, see <a href="http://libvirt.org/formatdomain.html">target Elements</a>
+ </div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-iotune"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.1.5. iotune</h4></div></div></div><div class="para">
+ The optional <code class="sgmltag-starttag"><iotune></code> element provides the ability to provide additional per-device I/O tuning, with values that can vary for each device (contrast this to the <code class="sgmltag-attvalue">blkiotune</code> element, which applies globally to the domain). This element has the following optional sub-elements. Note that any sub-element not specified or at all or specified with a value of <code class="sgmltag-attvalue">0</code> implies no limit.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><total_bytes_sec></code> - the total throughput limit in bytes per second. This element cannot be used with <code class="sgmltag-starttag"><read_bytes_sec></code> or <code class="sgmltag-starttag"><write_bytes_sec></code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><read_bytes_sec></code> - the read throughput limit in bytes per second.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><write_bytes_sec></code> - the write throughput limit in bytes per second.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><total_iops_sec></code> - the total I/O operations per second. This element cannot be used with <code class="sgmltag-starttag"><read_iops_sec></code> or <code class="sgmltag-starttag"><write_iops_sec></code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><read_iops_sec></code> - the read I/O operations per second.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><write_iops_sec></code> - the write I/O operations per second.
+ </div></li></ul></div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-driver"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.1.6. driver</h4></div></div></div><div class="para">
+ The optional <code class="sgmltag-starttag"><driver></code> element allows specifying further details related to the hypervisor driver that is used to provide the disk. The following options may be used:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If the hypervisor supports multiple backend drivers, then the <code class="sgmltag-attribute">name</code> attribute selects the primary backend driver name, while the optional type attribute provides the sub-type. For a list of possible types refer to <a href="http://libvirt.org/formatdomain.html">Driver Elements</a>
+ </div></li><li class="listitem"><div class="para">
+ The optional <code class="sgmltag-attribute">cache</code> attribute controls the cache mechanism, possible values are: <code class="sgmltag-attvalue">default</code>, <code class="sgmltag-attvalue">none</code>, <code class="sgmltag-attvalue">writethrough</code>, <code class="sgmltag-attvalue">writeback</code>, <code class="sgmltag-attvalue">directsync</code> (similar to <code class="sgmltag-element">writethrough</code>, but it bypasses the host page cache) and <code class="sgmltag-attvalue">unsafe</code> (host may cache all disk io, and sync requests from guest are ignored).
+ </div></li><li class="listitem"><div class="para">
+ The optional <code class="sgmltag-attribute">error_policy</code> attribute controls how the hypervisor behaves on a disk read or write error, possible values are <code class="sgmltag-attvalue">stop</code>, <code class="sgmltag-attvalue">report</code>, <code class="sgmltag-attvalue">ignore</code>, and <code class="sgmltag-attvalue">enospace</code>. The default setting of <code class="sgmltag-attribute">error_policy</code> is <code class="sgmltag-attvalue">report</code>. There is also an optional <code class="sgmltag-attribute">rerror_policy</code> that controls behavior for read errors only. If no <code class="sgmltag-attribute">rerror_policy</code> is given, <code class="sgmltag-attribute">error_policy</code> is used for both read and write errors. If <code class="sgmltag-attribute">rerror_policy</code> is given, it overrides the <code class="sgmltag-attribute">error_policy</code> for read errors. Also note that <code class="sgmltag-attvalue">enospace</code> is not a
valid policy for read errors, so if <code class="sgmltag-attribute">error_policy</code> is set to <code class="sgmltag-attvalue">enospace</code> and <code class="sgmltag-attribute">no rerror_policy</code> is given, the read error the default setting, <code class="sgmltag-attvalue">report</code> will be used.
+ </div></li><li class="listitem"><div class="para">
+ The optional <code class="sgmltag-attribute">io</code> attribute controls specific policies on I/O; <code class="sgmltag-attribute">qemu</code> guests support <code class="sgmltag-attvalue">threads</code> and <code class="sgmltag-attvalue">native</code>. The optional <code class="sgmltag-attribute">ioeventfd</code> attribute allows users to set domain I/O asynchronous handling for disk device. The default is left to the discretion of the hypervisor. Accepted values are <code class="sgmltag-attvalue">on</code> and <code class="sgmltag-attvalue">off</code>. Enabling this allows the guest virtual machine to be executed while a separate thread handles I/O. Typically guests experiencing high system CPU utilization during I/O will benefit from this. On the other hand, an overloaded host can increase guest I/O latency. Unless you are absolutely certian that the <code class="sgmltag-attribute">io</code> needs to be manipulated, it is highly recommended that you not change the
default setting and allow the hypervisor to dictate the setting.
+ </div></li><li class="listitem"><div class="para">
+ The optional <code class="sgmltag-attribute">event_idx</code> attribute controls some aspects of device event processing and can be set to either <code class="sgmltag-attvalue">on</code> or <code class="sgmltag-attvalue">off</code> - if it is on, it will reduce the number of interrupts and exits for the guest. The default is determined by the hypervisor and the default setting is <code class="sgmltag-attvalue">on</code>. In cases that there is a situation where this behavior is suboptimal, this attribute provides a way to force the feature <code class="sgmltag-attvalue">off</code>. Unless you are absolutely certian that the <code class="sgmltag-attribute">event_idx</code> needs to be manipulated, it is highly recommended that you not change the default setting and allow the hypervisor to dictate the setting.
+ </div></li><li class="listitem"><div class="para">
+ The optional <code class="sgmltag-attribute">copy_on_read</code> attribute controls whether to copy the read backing file into the image file. The accepted values can be either <code class="sgmltag-attvalue">on</code> or <code class="sgmltag-starttag"><off></code>. <code class="sgmltag-attribute">copy-on-read</code> avoids accessing the same backing file sectors repeatedly and is useful when the backing file is over a slow network. By default <code class="sgmltag-attribute">copy-on-read</code> is <code class="sgmltag-attvalue">off</code>.
+ </div></li></ul></div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-misc"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.1.7. Additional Device Elements</h4></div></div></div><div class="para">
+ The following attributes may be used within the <code class="sgmltag-element">device</code> element:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><boot></code> - Specifies that the disk is bootable.
+ </div><div class="itemizedlist"><h6>Additional boot values</h6><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><order></code> - Determines the order in which devices will be tried during boot sequence.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><per-device></code> boot elements cannot be used together with general boot elements in BIOS bootloader section
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><encryption></code> - Specifies how the volume is encrypted. See the Storage Encryption page for more information.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><readonly></code> - Indicates the device cannot be modified by the guest. This setting is the default for disks with <code class="sgmltag-attribute">attribute</code> <code class="sgmltag-attvalue">device='cdrom'</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">shareable</code> Indicates the device is expected to be shared between domains (as long as hypervisor and OS support this). If <code class="sgmltag-element">shareable</code> is used, <code class="sgmltag-attvalue">cache='no'</code> should be used for that device.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><transient></code>- Indicates that changes to the device contents should be reverted automatically when the guest exits. With some hypervisors, marking a disk <code class="sgmltag-attvalue">transient</code> prevents the domain from participating in migration or snapshots.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><serial></code>- Specifies the serial number of guest virtual machine's hard drive. For example, <code class="sgmltag-starttag"><serial></code>WD-WMAP9A966149<code class="sgmltag-endtag"></serial></code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><wwn></code> - Specifies the WWN (World Wide Name) of a virtual hard disk or CD-ROM drive. It must be composed of 16 hexadecimal digits.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><vendor></code> - Specifies the vendor of a virtual hard disk or CD-ROM device. It must not be longer than 8 printable characters.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><product></code> - Specifies the product of a virtual hard disk or CD-ROM device. It must not be longer than 16 printable characters
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><host></code> - Supports 4 attributes: <code class="sgmltag-element">viz</code>, <code class="sgmltag-element">name</code>, <code class="sgmltag-element">port</code>, <code class="sgmltag-element">transport</code> and <code class="sgmltag-element">socket</code>, which specify the hostname, the port number, transport type and path to socket, respectively. The meaning of this element and the number of the elements depend on the <code class="sgmltag-element">protocol</code> attribute as shown here:
+ </div><div class="itemizedlist"><h6>additional host attributes</h6><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">nbd</code> - Specifies a server running nbd-server and may only be used for only one host
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">rbd</code> - Monitors servers of RBD type and may be used for one or more hosts
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">sheepdog</code> - Specifies one of the sheepdog servers (default is localhost:7000) and can be used one or none of the hosts
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">gluster</code> - Specifies a server running a glusterd daemon and may be used for only only one host. The valid values for transport attribute are <code class="sgmltag-attvalue">tcp</code>, <code class="sgmltag-attvalue">rdma</code> or <code class="sgmltag-attvalue">unix</code>. If nothing is specified, <code class="sgmltag-attvalue">tcp</code> is assumed. If transport is <code class="sgmltag-attvalue">unix</code>, the <code class="sgmltag-attvalue">socket</code> attribute specifies path to unix socket.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><address></code> - Ties the disk to a given slot of a controller. The actual <code class="sgmltag-starttag"><controller></code> device can often be inferred by but it can also be explicitly specified. The <code class="sgmltag-attribute">type</code> attribute is mandatory, and is typically <code class="sgmltag-attvalue">pci</code> or <code class="sgmltag-attvalue">drive</code>. For a <code class="sgmltag-attribute">pci</code> controller, additional attributes for <code class="sgmltag-element">bus</code>, <code class="sgmltag-element">slot</code>, and <code class="sgmltag-element">function</code> must be present, as well as optional <code class="sgmltag-element">domain</code> and <code class="sgmltag-attvalue">multifunction</code>. <code class="sgmltag-attvalue">multifunction</code> defaults to <code class="sgmltag-attvalue">off</code>. For a <code class="sgmltag-attribute">drive</code> controller, additional attributes <code c
lass="sgmltag-attvalue">controller</code>, <code class="sgmltag-attvalue">bus</code>, <code class="sgmltag-attvalue">target</code>, and <code class="sgmltag-attvalue">unit</code> are available, each with a default setting of <code class="sgmltag-attvalue">0</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">auth</code> - Provides the authentication credentials needed to access the source. It includes a mandatory attribute username, which identifies the username to use during authentication, as well as a sub-element <code class="sgmltag-attvalue">secret</code> with mandatory attribute <code class="sgmltag-attribute">type</code>. More information can be found here at <a href="http://libvirt.org/formatdomain.html">Device Elements</a>
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">geometry</code> - Provides the ability to override geometry settings. This mostly useful for S390 DASD-disks or older DOS-disks.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">cyls</code> - Specifies the number of cylinders.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">heads</code> - Specifies the number of heads.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">secs</code> - Specifies the number of sectors per track.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">trans</code> - Specifies the BIOS-Translation-Modus and can have the following values:<code class="sgmltag-element">none</code>, <code class="sgmltag-element">lba</code> or <code class="sgmltag-element">auto</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">blockio</code> - Allows the block device to be overridden with any of the block device properties listed below:
+ </div><div class="itemizedlist"><h6>blockio options</h6><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">logical_block_size</code>- reports to the guest OS and describes the smallest units for disk I/O.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">physical_block_size</code> - reports to the guest OS and describes the disk's hardware sector size which can be relevant for the alignment of disk data.
+ </div></li></ul></div></li></ul></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-time-keep.html"><strong>Prev</strong>J.15. Time keeping</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="sub-section-libvirt-dom-xml-devices-filesystems.html"><strong>Next</strong>J.16.2. Filesystems</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-event-config.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-event-config.html
new file mode 100644
index 0000000..1b981bd
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-event-config.html
@@ -0,0 +1,91 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.12. Events configuration</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sect-libvirt-dom-xml-cpu-model-top.html" title="J.11. CPU model and topology" /><link rel="next" href="sect-libvirt-dom-xml-pwr-man.html" title="J.13. Power Management" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-libvirt-dom-xm
l-cpu-model-top.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-libvirt-dom-xml-pwr-man.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-libvirt-dom-xml-event-config"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.12. Events configuration</h2></div></div></div><div class="para">
+ Using the following sections of domain XML it is possible to override the default actions taken on various events.
+ </div><div class="figure" id="fig-xml-cpu-model-events-config"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><on_poweroff></span>destroy<span class="perl_Keyword"></on_poweroff></span>
+ <span class="perl_Keyword"><on_reboot></span>restart<span class="perl_Keyword"></on_reboot></span>
+ <span class="perl_Keyword"><on_crash></span>restart<span class="perl_Keyword"></on_crash></span>
+ <span class="perl_Keyword"><on_lockfailure></span>poweroff<span class="perl_Keyword"></on_lockfailure></span>
+ ..
+
+</pre></div><h6>Figure J.19. Events Configuration</h6></div><br class="figure-break" /><div class="para">
+ The following collections of elements allow the actions to be specified when a guest OS triggers a lifecycle operation. A common use case is to force a reboot to be treated as a poweroff when doing the initial OS installation. This allows the VM to be re-configured for the first post-install bootup.
+ </div><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-event-config-elem"><h6>Table J.10. Event configurtation elements</h6><div class="table-contents"><table summary="Event configurtation elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ State
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><on_poweroff></code>
+ </td><td class="">
+ Specifies the action that is to be executed when the guest requests a poweroff. Four possible arguements are possible:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">destroy</code> - this action terminates the domain completely and releases all resources
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">restart</code> - this action terminates the domain completely and restarts it with the same configuration
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">preserve</code> - this action terminates the domain completely but and its resources are preserved to allow for future analysis.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">rename-restart</code> - this action terminates the domain completely and then restarts it with a new name
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><on_reboot></code>
+ </td><td class="">
+ Specifies the action that is to be executed when the guest requests a reboot.Four possible arguements are possible:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">destroy</code> - this action terminates the domain completely and releases all resources
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">restart</code> - this action terminates the domain completely and restarts it with the same configuration
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">preserve</code> - this action terminates the domain completely but and its resources are preserved to allow for future analysis.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">rename-restart</code> - this action terminates the domain completely and then restarts it with a new name
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><on_crash></code>
+ </td><td class="">
+ Specifies the action that is to be executed when the guest crashes. In addition, it supports these additional actions:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">coredump-destroy</code> - the crashed domain's core is dumped, domain is terminated completely, and all resources are released.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">coredump-restart</code> - the crashed domain's core is dumped, and the domain is restarted with the same configuration settings
+ </div></li></ul></div>
+ Four possible arguements are possible:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">destroy</code> - this action terminates the domain completely and releases all resources
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">restart</code> - this action terminates the domain completely and restarts it with the same configuration
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">preserve</code> - this action terminates the domain completely but and its resources are preserved to allow for future analysis.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">rename-restart</code> - this action terminates the domain completely and then restarts it with a new name
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><on_lockfailure></code>
+ </td><td class="">
+ Specifies what action should be taken when a lock manager loses resource locks. The following actions are recognized by libvirt, although not all of them need to be supported by individual lock managers. When no action is specified, each lock manager will take its default action. The following arguements are possible:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">poweroff</code> - forcefully powers off the domain
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">restart</code> - restarts the domain to reacquire its locks.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">pause</code> - pauses the domain so that it can be manually resumed when lock issues are solved.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">ignore</code> - keeps the domain running as if nothing happened.
+ </div></li></ul></div>
+
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-cpu-model-top.html"><strong>Prev</strong>J.11. CPU model and topology</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-libvirt-dom-xml-pwr-man.html"><strong>Next</strong>J.13. Power Management</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-mem-tuning.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-mem-tuning.html
new file mode 100644
index 0000000..1a4184b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-mem-tuning.html
@@ -0,0 +1,49 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.7. Memory tuning</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sect-mem-back.html" title="J.6. Memory backing" /><link rel="next" href="sect-libvirt-dom-xml-numa-node-tuning.html" title="J.8. NUMA node tuning" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-mem-back.html"><strong>Prev</strong>
</a></li><li class="next"><a accesskey="n" href="sect-libvirt-dom-xml-numa-node-tuning.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-libvirt-dom-xml-mem-tuning"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.7. Memory tuning</h2></div></div></div><div class="figure" id="fig-dom-xml-mem-tuning"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain></span>
+ ...
+ <span class="perl_Keyword"><memtune></span>
+ <span class="perl_Keyword"><hard_limit</span><span class="perl_Others"> unit=</span><span class="perl_String">'G'</span><span class="perl_Keyword">></span>1<span class="perl_Keyword"></hard_limit></span>
+ <span class="perl_Keyword"><soft_limit</span><span class="perl_Others"> unit=</span><span class="perl_String">'M'</span><span class="perl_Keyword">></span>128<span class="perl_Keyword"></soft_limit></span>
+ <span class="perl_Keyword"><swap_hard_limit</span><span class="perl_Others"> unit=</span><span class="perl_String">'G'</span><span class="perl_Keyword">></span>2<span class="perl_Keyword"></swap_hard_limit></span>
+ <span class="perl_Keyword"><min_guarantee</span><span class="perl_Others"> unit=</span><span class="perl_String">'bytes'</span><span class="perl_Keyword">></span>67108864<span class="perl_Keyword"></min_guarantee></span>
+ <span class="perl_Keyword"></memtune></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.10. Memory tuning</h6></div><br class="figure-break" /><div class="para">
+ Although all are optional, the components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-mem-tun-elem"><h6>Table J.6. Memory tuning elements</h6><div class="table-contents"><table summary="Memory tuning elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><memtune></code>
+ </td><td class="">
+ Provides details regarding the memory tunable parameters for the domain. If this is omitted, it defaults to the OS provided defaults. The parameters are applied to the process as a whole therefore when setting limits, one needs to add up guest RAM, guest video RAM, and allow for some memory overhead. The last piece is hard to determine so one use trial and error. For each tunable, it is possible to designate which unit the number is in on input, using the same values as for <code class="sgmltag-starttag"><memory></code>. For backwards compatibility, output is always in KiB.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><hard_limit></code>
+ </td><td class="">
+ This is the maximum memory the guest can use. The <code class="sgmltag-attribute">unit</code> for this value is expressed in <code class="literal">kibibytes</code> (i.e. blocks of 1024 bytes)
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><soft_limit></code>
+ </td><td class="">
+ This is the memory limit to enforce during memory contention. The <code class="sgmltag-attribute">unit</code> for this value is expressed in kibibytes (i.e. blocks of 1024 bytes)
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><swap_hard_limit></code>
+ </td><td class="">
+ This is the maximum memory plus swap the guest can use. The <code class="sgmltag-attribute">unit</code> for this value is expressed in kibibytes (i.e. blocks of 1024 bytes). This has to be more than <code class="sgmltag-starttag"><hard_limit></code> value provided
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><min_guarantee></code>
+ </td><td class="">
+ This is the guaranteed minimum memory allocation for the guest. The units for this value is expressed in kibibytes (i.e. blocks of 1024 bytes)
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-mem-back.html"><strong>Prev</strong>J.6. Memory backing</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-libvirt-dom-xml-numa-node-tuning.html"><strong>Next</strong>J.8. NUMA node tuning</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-numa-node-tuning.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-numa-node-tuning.html
new file mode 100644
index 0000000..93bc31b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-numa-node-tuning.html
@@ -0,0 +1,36 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.8. NUMA node tuning</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sect-libvirt-dom-xml-mem-tuning.html" title="J.7. Memory tuning" /><link rel="next" href="sect-libvirt-dom-xml-blk-io-tuning.html" title="J.9. Block I/O tuning" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-libvirt-dom-xml-mem-tu
ning.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-libvirt-dom-xml-blk-io-tuning.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-libvirt-dom-xml-numa-node-tuning"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.8. NUMA node tuning</h2></div></div></div><div class="para">
+ Once NUMA node tuning is done using conventional managment tools the following domain XML parameters are effected:
+ </div><div class="figure" id="fig-dom-xml-numa-node-tuning"><div class="figure-contents"><pre class="programlisting">
+>
+<span class="perl_Keyword"><domain></span>
+ ...
+ <span class="perl_Keyword"><numatune></span>
+ <span class="perl_Keyword"><memory</span><span class="perl_Others"> mode=</span><span class="perl_String">"strict"</span><span class="perl_Others"> nodeset=</span><span class="perl_String">"1-4,^3"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></numatune></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.11. NUMA node tuning</h6></div><br class="figure-break" /><div class="para">
+ Although all are optional, the components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-numa-tun-elem"><h6>Table J.7. NUMA node tuning elements</h6><div class="table-contents"><table summary="NUMA node tuning elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><numatune></code>
+ </td><td class="">
+ Provides details of how to tune the performance of a NUMA host via controlling NUMA policy for domain process.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><memory></code>
+ </td><td class="">
+ Specifies how to allocate memory for the domain process on a NUMA host. It contains several optional attributes. Attribute <code class="sgmltag-attribute">mode</code> is either <code class="sgmltag-attvalue">interleave</code>, <code class="sgmltag-attvalue">strict</code>, or <code class="sgmltag-attvalue">preferred</code>. If no value is given it defaults to <code class="sgmltag-attvalue">strict</code>. Attribute <code class="sgmltag-attribute">nodeset</code> specifies the NUMA nodes, using the same syntax as attribute <code class="sgmltag-attribute">cpuset</code> of element <code class="sgmltag-starttag"><vcpu></code>. Attribute <code class="sgmltag-attribute">placement</code> can be used to indicate the memory placement mode for the domain process. Its value can be either <code class="sgmltag-attvalue">static</code> or <code class="sgmltag-attvalue">auto</code>. If attribute <code class="sgmltag-starttag"><nodeset></code> is specified it defaults to the
<code class="sgmltag-starttag"><placement></code> of <code class="sgmltag-starttag"><vcpu></code>, or <code class="sgmltag-attvalue">static</code>. <code class="sgmltag-attvalue">auto</code> indicates the domain process will only allocate memory from the advisory nodeset returned from querying numad and the value of attribute nodeset will be ignored if it's specified. If attribute <code class="sgmltag-attribute">placement</code> of <code class="sgmltag-element">vcpu</code> is <code class="sgmltag-attvalue">auto</code>, and attribute <code class="sgmltag-starttag"><numatune></code> is not specified, a default numatune with <code class="sgmltag-starttag"><placement></code> <code class="sgmltag-attvalue">auto</code> and mode <code class="sgmltag-attvalue">strict</code> will be added implicitly.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-mem-tuning.html"><strong>Prev</strong>J.7. Memory tuning</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-libvirt-dom-xml-blk-io-tuning.html"><strong>Next</strong>J.9. Block I/O tuning</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-pwr-man.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-pwr-man.html
new file mode 100644
index 0000000..88eebfa
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-pwr-man.html
@@ -0,0 +1,23 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.13. Power Management</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sect-libvirt-dom-xml-event-config.html" title="J.12. Events configuration" /><link rel="next" href="apjs14.html" title="J.14. Hypervisor features" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-libvirt-dom-xml-event-config.html"><
strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apjs14.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-libvirt-dom-xml-pwr-man"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.13. Power Management</h2></div></div></div><div class="para">
+ It is possible to forcibly enable or disable BIOS advertisements to the guest OS using conventional management tools which effects the following section of the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-pwr-man"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><pm></span>
+ <span class="perl_Keyword"><suspend-to-disk</span><span class="perl_Others"> enabled=</span><span class="perl_String">'no'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><suspend-to-mem</span><span class="perl_Others"> enabled=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></pm></span>
+ ...
+
+</pre></div><h6>Figure J.20. Power Management</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-starttag"><pm></code> element can be enabled using the arguement <code class="sgmltag-attvalue">yes</code> or disabled using the arguement <code class="sgmltag-attvalue">no</code>. BIOS support can be implemented for S3 using the arguement <code class="sgmltag-attribute">suspend-to-disk</code> and S4 using the arguement <code class="sgmltag-attribute">suspend-to-mem</code> ACPI sleep states. If nothing is specified, the hypervisor will be left with its default value.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-event-config.html"><strong>Prev</strong>J.12. Events 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="apjs14.html"><strong>Next</strong>J.14. Hypervisor features</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-res-part.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-res-part.html
new file mode 100644
index 0000000..0f925cf
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-res-part.html
@@ -0,0 +1,23 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.10. Resource partitioning</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sect-libvirt-dom-xml-blk-io-tuning.html" title="J.9. Block I/O tuning" /><link rel="next" href="sect-libvirt-dom-xml-cpu-model-top.html" title="J.11. CPU model and topology" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-libvirt-d
om-xml-blk-io-tuning.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-libvirt-dom-xml-cpu-model-top.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-libvirt-dom-xml-res-part"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.10. Resource partitioning</h2></div></div></div><div class="para">
+ Hypervisors may allow for virtual machines to be placed into resource partitions, potentially with nesting of said partitions. The <code class="sgmltag-starttag"><resource></code> element groups together configuration related to resource partitioning. It currently supports a child element partition whose content defines the path of the resource partition in which to place the domain. If no partition is listed, then the domain will be placed in a default partition. It is the responsibility of the app/admin to ensure that the partition exists prior to starting the guest. Only the (hypervisor specific) default partition can be assumed to exist by default.
+ </div><div class="figure" id="fig-res-part"><div class="figure-contents"><pre class="programlisting">
+
+
+ ...
+ <span class="perl_Keyword"><resource></span>
+ <span class="perl_Keyword"><partition></span>/virtualmachines/production<span class="perl_Keyword"></partition></span>
+ <span class="perl_Keyword"></resource></span>
+ ...
+
+</pre></div><h6>Figure J.13. Resource partitioning</h6></div><br class="figure-break" /><div class="para">
+ Resource partitions are currently supported by the QEMU and LXC drivers, which map partition paths to cgroups directories in all mounted controllers.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-blk-io-tuning.html"><strong>Prev</strong>J.9. Block I/O tuning</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-libvirt-dom-xml-cpu-model-top.html"><strong>Next</strong>J.11. CPU model and topology</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-time-keep.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-time-keep.html
new file mode 100644
index 0000000..3f028e0
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-libvirt-dom-xml-time-keep.html
@@ -0,0 +1,74 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.15. Time keeping</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="apjs14.html" title="J.14. Hypervisor features" /><link rel="next" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="apjs14.html"><strong>Prev</strong></a></li><li class="next"
><a accesskey="n" href="sect-libvirt-dom-xml-devices.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-libvirt-dom-xml-time-keep"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.15. Time keeping</h2></div></div></div><div class="para">
+ The guest clock is typically initialized from the host clock. Most operating systems expect the hardware clock to be kept in UTC, which is the default setting. Note that for Windows guests the guest must be set in <code class="sgmltag-attvalue">localtime</code>.
+ </div><div class="figure" id="fig-libvirt-dom-xml-time-keep"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><clock</span><span class="perl_Others"> offset=</span><span class="perl_String">'localtime'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><timer</span><span class="perl_Others"> name=</span><span class="perl_String">'rtc'</span><span class="perl_Others"> tickpolicy=</span><span class="perl_String">'catchup'</span><span class="perl_Others"> track=</span><span class="perl_String">'guest'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><catchup</span><span class="perl_Others"> threshold=</span><span class="perl_String">'123'</span><span class="perl_Others"> slew=</span><span class="perl_String">'120'</span><span class="perl_Others"> limit=</span><span class="perl_String">'10000'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></timer></span>
+ <span class="perl_Keyword"><timer</span><span class="perl_Others"> name=</span><span class="perl_String">'pit'</span><span class="perl_Others"> tickpolicy=</span><span class="perl_String">'delay'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></clock></span>
+ ...
+
+</pre></div><h6>Figure J.22. Time keeping</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-time-keep-elem"><h6>Table J.12. Time keeping elements</h6><div class="table-contents"><table summary="Time keeping elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ State
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><clock></code>
+ </td><td class="">
+ The <code class="sgmltag-attribute">offset</code> attribute takes four possible values, allowing for fine grained control over how the guest clock is synchronized to the host. Note that hypervisors are not required to support all policies across all time sources <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">utc</code> - Synchronizes the clock to UTC when booted. <code class="sgmltag-attvalue">utc</code> mode can be converted to <code class="sgmltag-attvalue">variable</code> mode, which can be controlled by using the adjustment attribute. If the value is <code class="sgmltag-attvalue">reset</code>, the conversion is not done. A numeric value forces the conversion to <code class="sgmltag-attvalue">variable</code> mode using the value as the initial adjustment. The default adjustment is hypervisor specific.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">localtime</code> - Synchronizes the guest clock with the host's configured timezone when booted. The adjustment attribute behaves the same as in 'utc' mode.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">timezone</code> - Synchronizes the guest clock to the requested timezone using the timezone attribute.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">variable</code> - Gives the guest clock an arbitrary offset applied relative to UTC or localtime, depending on the basis attribute. The delta relative to UTC (or localtime) is specified in seconds, using the <code class="sgmltag-attribute">adjustment</code> attribute. The guest is free to adjust the RTC over time and expect that it will be honored at next reboot. This is in contrast to <code class="sgmltag-attvalue">utc</code> and <code class="sgmltag-attvalue">localtime</code> mode (with the optional attribute <code class="sgmltag-attvalue">adjustment='reset'</code>), where the RTC adjustments are lost at each reboot. In addition the <code class="sgmltag-attribute">basis</code> attribute can be either <code class="sgmltag-attvalue">utc</code> (default) or <code class="sgmltag-attvalue">localtime</code>. The <code class="sgmltag-element">clock</code> element may have zero or more <code class="sgmltag-starttag"><timer></code> ele
ments.
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><timer></code>
+ </td><td class="">
+ See Note
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><frequency></code>
+ </td><td class="">
+ This is an unsigned integer specifying the frequency at which <code class="sgmltag-attribute">name</code>=<code class="sgmltag-attvalue">"tsc"</code> runs.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><mode></code>
+ </td><td class="">
+ The <code class="sgmltag-attribute">mode</code> attribute controls how the <code class="sgmltag-attvalue">name="tsc"</code> <code class="sgmltag-starttag"><timer></code> is managed, and can be set to: <code class="sgmltag-attvalue">auto</code>, <code class="sgmltag-attvalue">native</code>, <code class="sgmltag-attvalue">emulate</code>, <code class="sgmltag-attvalue">paravirt</code>, or <code class="sgmltag-attvalue">smpsafe</code>. Other timers are always emulated.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><present></code>
+ </td><td class="">
+ Specifies whether a particular timer is available to the guest. Can be set to <code class="sgmltag-attvalue">yes</code> or <code class="sgmltag-attvalue">no</code>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="note"><div class="admonition_header"><h2>Additional information about the <code class="sgmltag-starttag"><timer></code> element</h2></div><div class="admonition"><div class="para">
+ Each <code class="sgmltag-starttag"><timer></code> element must contain a <code class="sgmltag-attribute">name</code> attribute, and may have the following attributes depending on the name specified.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><name></code> - selects which <code class="sgmltag-element">timer</code> is being modified. The following values are acceptable:<code class="sgmltag-attvalue">platform</code>, <code class="sgmltag-attvalue">hpet</code>, <code class="sgmltag-attvalue">kvmclock</code>, <code class="sgmltag-attvalue">pit</code>, <code class="sgmltag-attvalue">rtc</code>, or <code class="sgmltag-attvalue">tsc</code>.
+ </div></li><li class="listitem"><div class="para">
+ track - specifies the timer track. The following values are acceptable: <code class="sgmltag-attvalue">boot</code>, <code class="sgmltag-attvalue">guest</code>, or <code class="sgmltag-attvalue">wall</code>. <code class="sgmltag-element">track</code> is only valid for <code class="sgmltag-attvalue">name="rtc"</code> or <code class="sgmltag-attvalue">name="platform"</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-element">tickpolicy</code> - determines what happens whens the deadline for injecting a tick to the guest is missed. The following values can be assigned:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">delay</code> -will continue to deliver ticks at the normal rate. The guest time will be delayed due to the late tick
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">catchup</code> - delivers ticks at a higher rate in order to catch up with the missed tick. The guest time is not displayed once catchup is complete. In addition, there can be three optional attributes, each a positive integer, as follows: threshold, slew, and limit.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">merge</code> - merges the missed tick(s) into one tick and injects them. The guest time may be delayed, depending on how the merge is done.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">discard</code> - throws away the missed tick(s) and continues with future injection at its default interval setting. The guest time may be delayed, unless the there is an explicit statement for handling lost ticks
+ </div></li></ul></div></li></ul></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apjs14.html"><strong>Prev</strong>J.14. Hypervisor features</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-libvirt-dom-xml-devices.html"><strong>Next</strong>J.16. Devices</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-limit-redirection.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-limit-redirection.html
new file mode 100644
index 0000000..5442011
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-limit-redirection.html
@@ -0,0 +1,45 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.15. Setting a limit on device redirection</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="subsect-guest-synch-delimited.html" title="25.14.2. guest-sync-delimited" /><link rel="next" href="sect-dynamic-vNIC.html" title="25.16. Dynamically changing a host or a network bridge that is attached to a virtual NIC" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="Documentatio
n Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="subsect-guest-synch-delimited.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-dynamic-vNIC.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-limit-redirection"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.15. Setting a limit on device redirection</h2></div></div></div><div class="para">
+ To filter out certain devices from redirection, pass the filter property to <em class="parameter"><code>-device usb-redir</code></em>. The filter property takes a string consisting of filter rules, the format for a rule is:
+ </div><pre class="screen"><code class="command"><class>:<vendor>:<product>:<version>:<allow></code></pre><div class="para">
+ Use the value <em class="parameter"><code>-1 </code></em> to designate it to accept any value for a particular field. You may use multiple rules on the same command line using | as a separator. Note that if a device matches none of the passed in rules, redirecting it will not be allowed!
+ </div><div class="example" id="exam-limit-redirect"><h6>Example 25.6. An example of limiting redirection with a windows guest virtual machine </h6><div class="example-contents"><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Prepare a Windows 7 guest.
+ </div></li><li class="step"><div class="para">
+ Add the following code excerpt to the guest's' domain xml file:
+ </div><pre class="screen">
+ <redirdev bus='usb' type='spicevmc'>
+ <alias name='redir0'/>
+ <address type='usb' bus='0' port='3'/>
+ </redirdev>
+ <redirfilter>
+ <usbdev class='0x08' vendor='0x1234' product='0xBEEF' version='2.0' allow='yes'/>
+ <usbdev class='-1' vendor='-1' product='-1' version='-1' allow='no'/>
+ </redirfilter>
+</pre></li><li class="step"><div class="para">
+ Start the guest and confirm the setting changes by running the following:
+ </div><pre class="screen">#<code class="command">ps -ef | grep $guest_name</code></pre><pre class="screen"><code class="command">-device usb-redir,chardev=charredir0,id=redir0,</code>/
+<code class="command">filter=0x08:0x1234:0xBEEF:0x0200:1|-1:-1:-1:-1:0,bus=usb.0,port=3</code></pre></li><li class="step"><div class="para">
+ Plug a USB device into host, and use virt-viewer to connect to the guest.
+ </div></li><li class="step"><div class="para">
+ Click <span class="guimenuitem"><strong>USB device selection</strong></span> in the menu, which will produce the following message: "Some USB devices are blocked by host policy". Click <span class="guimenuitem"><strong>OK</strong></span> to confirm and continue.
+ </div><div class="para">
+ The filter takes effect.
+ </div></li><li class="step"><div class="para">
+ To make sure that the filter captures properly check the USB device vendor and product, then make the following changes in the host's domain XML to allow for USB redirection.
+ </div><pre class="screen">
+ <redirfilter>
+ <usbdev class='0x08' vendor='0x0951' product='0x1625' version='2.0' allow='yes'/>
+ <usbdev allow='no'/>
+ </redirfilter>
+</pre></li><li class="step"><div class="para">
+ Restart the guest, then use <span class="application"><strong>virt-viewer</strong></span> to connect to the guest. The USB device will now redirect traffic to the guest.
+ </div></li></ol></div></div></div><br class="example-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="subsect-guest-synch-delimited.html"><strong>Prev</strong>25.14.2. guest-sync-delimited</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-dynamic-vNIC.html"><strong>Next</strong>25.16. Dynamically changing a host or a network b...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-man-disk-image.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-man-disk-image.html
new file mode 100644
index 0000000..9395452
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-man-disk-image.html
@@ -0,0 +1,74 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.13. Disk image management with live block copy</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Managing_guests_with_virsh.html" title="Appendix E. Managing guests with virsh" /><link rel="prev" href="migrating_guests-with-virsh.html" title="E.12. Migrating guests with virsh" /><link rel="next" href="sub-sect-blockpull.html" title="E.13.2. Using blockpull to shorten a backing chain" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="doc
nav"><li class="previous"><a accesskey="p" href="migrating_guests-with-virsh.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-blockpull.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-man-disk-image"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">E.13. Disk image management with live block copy</h2></div></div></div><div class="para">
+ Live block copy allows you to copy an in use guest disk image to a destination image and switches the guest disk image to the destination guest image while the guest is running. Whilst live migration moves the memory and registry state of the host, the guest is kept in shared storage. Live block copy allows you to move the entire guest contents to another host on the fly while the guest is running. Live block copy may also be used for live migration without requiring permanent share storage. In this method the disk image is copied to the destination host after migration, but while the guest is running.
+ </div><div class="para">
+ Live block copy is especially useful for the following applications:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ moving the guest image from local storage to a central location
+ </div></li><li class="listitem"><div class="para">
+ when maintenance is required, guests can be transferred to another location, with no loss of performance
+ </div></li><li class="listitem"><div class="para">
+ allows for management of guest images for speed and efficiency
+ </div></li><li class="listitem"><div class="para">
+ image format conversions can be done without having to shut down the guest
+ </div></li></ul></div><div class="example" id="live-blk-cpy-example"><h6>Example E.1. Example (live block copy)</h6><div class="example-contents"><div class="para">
+ This example shows what happens when live block copy is performed. The example has a backing file (base) that is shared between a source and destination. It also has two overlays (sn1 and sn2) that are only present on the source and must be copied.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ The backing file chain at the beginning looks like this:
+ </div><div class="para">
+ <code class="command"> base ← sn1 ← sn2</code>
+ </div><div class="para">
+ The components are as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ base - the original disk image
+ </div></li><li class="listitem"><div class="para">
+ sn1 - the first snapshot that was taken of the base disk image
+ </div></li><li class="listitem"><div class="para">
+ sn2 - the most current snapshot
+ </div></li><li class="listitem"><div class="para">
+ active - the copy of the disk
+ </div></li></ul></div></li><li class="step"><div class="para">
+ When a copy of the image is created as a new image on top of sn2 the result is this:
+ </div><div class="para">
+ <code class="command">base ← sn1 ← sn2 ← active </code>
+ </div></li><li class="step"><div class="para">
+ At this point the read permissions are all in the correct order and are set automatically. To make sure write permissions are set properly, a mirror mechanism redirects all writes to both sn2 and active, so that sn2 and active read the same at any time (and this mirror mechanism is the essential difference between live block copy and image streaming).
+ </div></li><li class="step"><div class="para">
+ A background task that loops over all disk clusters is executed. For each cluster, there are the following possible cases and actions:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The cluster is already allocated in active and there is nothing to do.
+ </div></li><li class="listitem"><div class="para">
+ Use <code class="command">bdrv_is_allocated()</code> to follow the backing file chain. If the cluster is read from base (which is shared) there is nothing to do.
+ </div></li><li class="listitem"><div class="para">
+ If <code class="command">bdrv_is_allocated()</code> variant is not feasible, rebase the image and compare the read data with write data in base in order to decide if a copy is needed.
+ </div></li><li class="listitem"><div class="para">
+ In all other cases, copy the cluster into <code class="filename">active</code>
+ </div></li></ul></div></li><li class="step"><div class="para">
+ When the copy has completed, the backing file of active is switched to base (similar to rebase)
+ </div></li></ol></div></div></div><br class="example-break" /><div class="para">
+ To reduce the length of a backing chain after a series of snapshots, the following commands are helpful: <code class="command">blockcommit</code> and <code class="command">blockpull</code>. See <a class="xref" href="sect-man-disk-image.html#sect-blockcommit">Section E.13.1, “Using blockcommit to shorten a backing chain”</a> for more information.
+ </div><div class="section" id="sect-blockcommit"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.13.1. Using blockcommit to shorten a backing chain</h3></div></div></div><div class="para">
+ This section demonstrates how to use <code class="command">blockcommit</code> to shorten a backing chain. For more background on backing chains, see <a class="xref" href="sect-man-disk-image.html">Section E.13, “Disk image management with live block copy”</a>.
+ </div><div class="para">
+ <code class="command">blockcommit</code> copies data from one part of the chain down into a backing file, allowing you to pivot the rest of the chain in order to bypass the committed portions. For example, suppose this is the current state:
+ </div><pre class="screen">
+ <code class="command">base ← snap1 ← snap2 ← active</code>.
+</pre><div class="para">
+ Using <code class="command">blockcommit</code> moves the contents of snap2 into snap1, allowing you to delete snap2 from the chain, making backups much quicker.
+ </div><div class="procedure" id="pro-blockcommit"><h6>Procedure E.1. virsh blockcommit</h6><ul><li class="step"><div class="para">
+ Run the following command:
+ </div><pre class="screen">#<code class="command"> virsh blockcommit $dom $disk --base snap1 --top snap2 --wait --verbose</code></pre><div class="para">
+ The contents of snap2 are moved into snap1, resulting in:
+ </div><div class="para">
+ <code class="command">base ← snap1 ← active</code>. Snap2 is no longer valid and can be deleted
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ <code class="command">blockcommit</code> will corrupt any file that depends on the <em class="parameter"><code>--base</code></em> argument (other than files that depended on the <em class="parameter"><code>--top</code></em> argument, as those files now point to the base). To prevent this, do not commit changes into files shared by more than one guest. The <em class="parameter"><code>--verbose</code></em> option will allow the progress to be printed on the screen.
+ </div></div></div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="migrating_guests-with-virsh.html"><strong>Prev</strong>E.12. Migrating 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="sub-sect-blockpull.html"><strong>Next</strong>E.13.2. Using blockpull to shorten a backing chain</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-mem-back.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-mem-back.html
new file mode 100644
index 0000000..b9f0fe8
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-mem-back.html
@@ -0,0 +1,24 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.6. Memory backing</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sect-cpu-tuning.html" title="J.5. CPU tuning" /><link rel="next" href="sect-libvirt-dom-xml-mem-tuning.html" title="J.7. Memory tuning" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-cpu-tuning.html"><strong>Prev</strong></a></li>
<li class="next"><a accesskey="n" href="sect-libvirt-dom-xml-mem-tuning.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-mem-back"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.6. Memory backing</h2></div></div></div><div class="para">
+ Memory backing allows the hypervisor to properly manage large pages within the guest. Once confured the following domain XML is effected:
+ </div><div class="figure" id="fig-mem-back"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain></span>
+ ...
+ <span class="perl_Keyword"><memoryBacking></span>
+ <span class="perl_Keyword"><hugepages/></span>
+ <span class="perl_Keyword"></memoryBacking></span>
+ ...
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.9. Memory backing</h6></div><br class="figure-break" /><div class="para">
+ The optional <code class="sgmltag-starttag"><memoryBacking></code> element, may have an <code class="sgmltag-starttag"><hugepages></code> element set within it. This tells the hypervisor that the guest should have its memory allocated using hugepages instead of the normal native page size.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-cpu-tuning.html"><strong>Prev</strong>J.5. CPU tuning</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-libvirt-dom-xml-mem-tuning.html"><strong>Next</strong>J.7. Memory tuning</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-mem-dump-off.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-mem-dump-off.html
new file mode 100644
index 0000000..f501be9
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-mem-dump-off.html
@@ -0,0 +1,49 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.2. Guest memory allocation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="next" href="sect-Virtualization-Tips_and_tricks-Using_qemu_img.html" title="25.3. Using qemu-img" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="Do
cumentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Tips_and_tricks-Using_qemu_img.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-mem-dump-off"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.2. Guest memory allocation</h2></div></div></div><div class="para">
+ The following procedure shows how to allocate memory for a guest. This allocation and assignement works only at boot time and any changes to any of the memory values will not take effect until the next reboot.
+ </div><div class="para">
+ Valid memory units include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="parameter"><code>b</code></em> or <em class="parameter"><code>bytes</code></em> for bytes
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>KB</code></em> for kilobytes (10<sup>3</sup> or blocks of 1,000 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>k</code></em> or <em class="parameter"><code>KiB</code></em> for kibibytes (2<sup>10</sup> or blocks of 1024 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>MB</code></em> for megabytes (10<sup>6</sup> or blocks of 1,000,000 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>M</code></em> or <em class="parameter"><code>MiB</code></em> for mebibytes (2<sup>20</sup> or blocks of 1,048,576 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>GB</code></em> for gigabytes (10<sup>9</sup> or blocks of 1,000,000,000 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>G</code></em> or <em class="parameter"><code>GiB</code></em> for gibibytes (2<sup>30</sup> or blocks of 1,073,741,824 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>TB</code></em> for terabytes (10<sup>12</sup> or blocks of 1,000,000,000,000 bytes)
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>T</code></em> or <em class="parameter"><code>TiB</code></em> for tebibytes (2<sup>40</sup> or blocks of 1,099,511,627,776 bytes)
+ </div></li></ul></div><div class="para">
+ Note that all values will be rounded up to the nearest kibibyte by libvirt, and may be further rounded to the granularity supported by the hypervisor. Some hypervisors also enforce a minimum, such as 4000KiB (or 4000 x 2<sup>10</sup> or 4,096,000 bytes). The units for this value are determined by the optional attribute <em class="parameter"><code>memory unit</code></em>, which defaults to the kibibytes (KiB) as a unit of measure where the value given is multiplied by 2<sup>10</sup> or blocks of 1024 bytes.
+ </div><div class="para">
+ In the cases where the guest crashes the optional attribute <em class="parameter"><code>dumpCore</code></em> can be used to control whether the guest's memory should be included in the generated coredump (<em class="parameter"><code>dumpCore='on'</code></em>) or not included (<em class="parameter"><code>dumpCore='off'</code></em>). Note that the default setting is <em class="parameter"><code>on</code></em> so if the parameter is not set to <em class="parameter"><code>off</code></em>, the guest memory will be included in the coredump file.
+ </div><div class="para">
+ The <em class="parameter"><code>currentMemory</code></em> attribute determines the actual memory allocation for a guest. This value can be less than the maximum allocation, to allow for ballooning up the guests memory on the fly. If this is omitted, it defaults to the same value as the memory element. The unit attribute behaves the same as for memory.
+ </div><div class="para">
+ In all cases for this section, the domain XML needs to be altered as follows:
+ </div><pre class="screen">
+<domain>
+
+ <memory unit='KiB' dumpCore='off'>524288</memory>
+ <!-- changes the memory unit to KiB and does not allow the guest's memory to be included in the generated coredump file -->
+ <currentMemory unit='KiB'>524288</currentMemory>
+ <!-- makes the current memory unit 524288 KiB -->
+ ...
+</domain>
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html"><strong>Prev</strong>Chapter 25. Miscellaneous administration tasks</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-Tips_and_tricks-Using_qemu_img.html"><strong>Next</strong>25.3. Using qemu-img</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-network-protocols.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-network-protocols.html
new file mode 100644
index 0000000..79f1955
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-network-protocols.html
@@ -0,0 +1,14 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.3. Networking protocols</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html" title="Appendix H. Virtual Networking" /><link rel="prev" href="sect-Network_Address_Translation-libvirt.html" title="H.2. Network Address Translation" /><link rel="next" href="sub-sect-routed-mode-libvirt.html" title="H.3.2. Routed mode" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-Network_Address_Translation-libvirt.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-routed-mode-libvirt.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-network-protocols"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">H.3. Networking protocols</h2></div></div></div><div class="para">
+ The following sections describe individual networking protocols and how they are used in libvirt
+ </div><div class="section" id="sect-DNS_and_DHCP-protocols-libvirt"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.3.1. DNS and DHCP</h3></div></div></div><div class="para">
+ IP information can be assigned to guests via DHCP. A pool of addresses can be assigned to a virtual network switch for this purpose. Libvirt uses the <code class="command">dnsmasq</code> program for this. An instance of dnsmasq is automatically configured and started by libvirt for each virtual network switch that needs it.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-Network_Address_Translation-Switch_with_DNSDHCP"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-05-switchwithdnsmasq.jpg" width="444" alt="Virtual network switch running dnsmasq" /></div></div><h6>Figure H.4. Virtual network switch running dnsmasq</h6></div><br class="figure-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Network_Address_Translation-libvirt.html"><strong>Prev</strong>H.2. Network Address Translation</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="sub-sect-routed-mode-libvirt.html"><strong>Next</strong>H.3.2. Routed mode</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-other-commands.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-other-commands.html
new file mode 100644
index 0000000..9efb3f5
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-other-commands.html
@@ -0,0 +1,29 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.5. Other commands</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /><link rel="prev" href="sect-Augeas-and-libguestfs-scripting.html" title="G.4.5. Augeas and libguestfs scripting" /><link rel="next" href="sect-virt-rescue.html" title="G.6. virt-rescue: The rescue shell" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="d
ocnav"><li class="previous"><a accesskey="p" href="sect-Augeas-and-libguestfs-scripting.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-virt-rescue.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-other-commands"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">G.5. Other commands</h2></div></div></div><div class="para">
+ This section describes tools that are simpler equivalents to using guestfish to view and edit guest disk images.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">virt-cat</code> is similar to the guestfish <code class="command">download</code> command. It downloads and displays a single file to the guest. For example:
+ </div><pre class="screen">
+# virt-cat RHEL3 /etc/ntp.conf | grep ^server
+ server 127.127.1.0 # local clock
+</pre></li><li class="listitem"><div class="para">
+ <code class="command">virt-edit</code> is similar to the guestfish <code class="command">edit</code> command. It can be used to interactively edit a single file within a guest. For example, you may need to edit the <code class="filename">grub.conf</code> file in a Linux-based guest that will not boot:
+ </div><pre class="screen">
+# virt-edit LinuxGuest /boot/grub/grub.conf
+</pre><div class="para">
+ <code class="command">virt-edit</code> has another mode where it can be used to make simple non-interactive changes to a single file. For this, the <span class="bold bold"><strong>-e</strong></span> option is used. This command, for example, changes the root password in a Linux guest to having no password:
+ </div><pre class="screen">
+# virt-edit LinuxGuest /etc/passwd -e 's/^root:.*?:/root::/'
+</pre></li><li class="listitem"><div class="para">
+ <code class="command">virt-ls</code> is similar to the guestfish <code class="command">ls</code>, <code class="command">ll</code> and <code class="command">find</code> commands. It is used to list a directory or directories (recursively). For example, the following command would recursively list files and directories under /home in a Linux guest:
+ </div><pre class="screen">
+# virt-ls -R LinuxGuest /home/ | less
+</pre></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Augeas-and-libguestfs-scripting.html"><strong>Prev</strong>G.4.5. Augeas and libguestfs scripting</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-virt-rescue.html"><strong>Next</strong>G.6. virt-rescue: The rescue shell</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-perf-mon.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-perf-mon.html
new file mode 100644
index 0000000..e00aaf8
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-perf-mon.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.12. Using PMU to monitor guest performance</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers.html" title="25.11. Virtual machine timer management with libvirt" /><link rel="next" href="sect-s3-s4.html" title="25.13. Guest virtual machine power management" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="Documentat
ion Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-s3-s4.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-perf-mon"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.12. Using PMU to monitor guest performance</h2></div></div></div><div class="para">
+ In Fedora 18 and onward, vPMU (virtual PMU )was introduced as technical-preview. vPMU is based on Intel's PMU (Performance Monitoring Units) and may only be used on Intel machines. PMU allows the tracking of statistics which indicate how a guest virtual machine is functioning.
+ </div><div class="para">
+ Using performance monitoring, allows developers to use the CPU's PMU counter while using the performance tool for profiling. The virtual performance monitoring unit feature allows virtual machine users to identify sources of possible performance problems in their guest virtual machines, thereby improving the ability to profile a KVM guest virtual machine.
+ </div><div class="para">
+ To enable the feature, the <code class="command">-cpu host </code>flag must be set.
+ </div><div class="para">
+ This feature is only supported with guests running Fedora and is disabled by default. This feature only works using the Linux perf tool. Make sure the <span class="package">perf</span> package is installed using the command:
+ </div><pre class="screen">#<code class="command"> yum install perf</code>.</pre><div class="para">
+ See the man page on <code class="command">perf</code> for more information on the perf commands.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers.html"><strong>Prev</strong>25.11. Virtual machine timer management with libv...</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-s3-s4.html"><strong>Next</strong>25.13. Guest virtual machine power management</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-qemu-ga.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-qemu-ga.html
new file mode 100644
index 0000000..f5a2d75
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-qemu-ga.html
@@ -0,0 +1,35 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.14. QEMU Guest Agent Protocol</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="sect-s3-s4.html" title="25.13. Guest virtual machine power management" /><link rel="next" href="subsect-guest-synch-delimited.html" title="25.14.2. guest-sync-delimited" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="pr
evious"><a accesskey="p" href="sect-s3-s4.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="subsect-guest-synch-delimited.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-qemu-ga"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.14. QEMU Guest Agent Protocol</h2></div></div></div><div class="para">
+ The QEMU guest agent protocol (QEMU-ga), uses the same protocol as QMP. <span class="package">qemu-ga</span>. There are a couple issues regarding its isa-serial/virtio-serial transport, and the following caveats have been noted:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ There is no way for <span class="package">qemu-ga</span> to detect whether or not a client has connected to the channel.
+ </div></li><li class="listitem"><div class="para">
+ There is no way for a client to detect whether or not <span class="package">qemu-ga</span> has disconnected or reconnected to the backend.
+ </div></li><li class="listitem"><div class="para">
+ If the virtio-serial device resets and <span class="package">qemu-ga</span> has not connected to the channel as a result, (generally caused by a reboot or hotplug), data from the client will be dropped.
+ </div></li><li class="listitem"><div class="para">
+ If <span class="package">qemu-ga</span> has connected to the channel following a virtio-serial device reset, data from the client will be queued (and eventually throttled if available buffers are exhausted), regardless of whether or not <span class="package">qemu-ga</span> is still running/connected.
+ </div></li></ul></div><div class="para">
+ qemu-ga uses the guest-sync or guest-sync-delimited command to address the problem of re-synchronizing the channel after re-connection or client-side timeouts. These are described below.
+ </div><div class="section" id="sect-guest-synch"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">25.14.1. guest-sync</h3></div></div></div><div class="para">
+ The guest-sync request/response exchange is simple. The client provides a unique numerical token, the agent sends it back in a response:
+ </div><pre class="screen">
+ > { "execute": "guest-sync", "arguments": { "id": 123456 } }
+ < { "return": 123456}
+</pre><div class="para">
+ A successful exchange guarantees that the channel is now in sync and no unexpected data/responses will be sent. Note that for the reasons mentioned above there's no guarantee this request will be answered, so a client should implement a timeout and re-issue this periodically until a response is received for the most recent request.
+ </div><div class="para">
+ This alone does not handle synchronization issues in all cases. For example, if <span class="package">qemu-ga</span>'s parser previously received a partial request from a previous client connection, subsequent attempts to issue the guest-sync request can be misconstrued as being part of the previous partial request. Eventually <span class="package">qemu-ga</span> will hit it's recursion or token size limit and flush its parser state, at which point it will begin processing the backlog of requests, but there's no guarantee this will occur before the channel is throttled due to exhausting all available buffers. Thus, there is a potential for a deadlock situation occurring for certain instances.
+ </div><div class="para">
+ To avoid this, <span class="package">qemu-ga/QEMU</span>'s JSON parser has special handling for the 0xFF byte, which is an invalid UTF-8 character. Client requests should precede the guest-sync request with to ensure that <span class="package">qemu-ga</span> flushes it's parser state as soon as possible. As long as all clients abide by this, the deadlock state should be reliably avoidable.
+ </div><div class="para">
+ For more information see the qemu-ga wiki page on <a href="http://wiki.qemu.org/Features/QAPI/GuestAgent">wiki.qemu.org</a>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-s3-s4.html"><strong>Prev</strong>25.13. Guest virtual machine power 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="subsect-guest-synch-delimited.html"><strong>Next</strong>25.14.2. guest-sync-delimited</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-run-virt-rescue.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-run-virt-rescue.html
new file mode 100644
index 0000000..e647eaf
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-run-virt-rescue.html
@@ -0,0 +1,57 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.6.2. Running virt-rescue</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-virt-rescue.html" title="G.6. virt-rescue: The rescue shell" /><link rel="prev" href="sect-virt-rescue.html" title="G.6. virt-rescue: The rescue shell" /><link rel="next" href="sect-virt-df.html" title="G.7. virt-df: Monitoring disk usage" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-virt-rescue.html"><strong>Prev</s
trong></a></li><li class="next"><a accesskey="n" href="sect-virt-df.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-run-virt-rescue"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.6.2. Running virt-rescue</h3></div></div></div><div class="para">
+ Before you use <code class="command">virt-rescue</code> on a guest, make sure the guest is not running, otherwise disk corruption will occur. When you are sure the guest is not live, enter:
+ </div><pre class="screen">
+virt-rescue GuestName
+</pre><div class="para">
+ (where GuestName is the guest name as known to libvirt), or:
+ </div><pre class="screen">
+virt-rescue /path/to/disk/image
+</pre><div class="para">
+ (where the path can be any file, any logical volume, LUN, or so on) containing a guest disk.
+ </div><div class="para">
+ You will first see output scroll past, as virt-rescue boots the rescue VM. In the end you will see:
+ </div><pre class="screen">
+Welcome to virt-rescue, the libguestfs rescue shell.
+
+ Note: The contents of / are the rescue appliance.
+ You have to mount the guest's partitions under /sysroot
+ before you can examine them.
+
+ bash: cannot set terminal process group (-1): Inappropriate ioctl for device
+ bash: no job control in this shell
+ ><rescue>
+</pre><div class="para">
+ The shell prompt here is an ordinary bash shell, and a reduced set of ordinary Fedora commands is available. For example, you can enter:
+ </div><pre class="screen">
+><rescue> fdisk -l /dev/vda
+</pre><div class="para">
+ The previous command will list disk partitions. To mount a file system, it is suggested that you mount it under <code class="filename">/sysroot</code>, which is an empty directory in the rescue machine for the user to mount anything you like. Note that the files under <code class="filename">/</code> are files from the rescue VM itself:
+ </div><pre class="screen">
+><rescue> mount /dev/vda1 /sysroot/
+EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
+><rescue> ls -l /sysroot/grub/
+ total 324
+ -rw-r--r--. 1 root root 63 Sep 16 18:14 device.map
+ -rw-r--r--. 1 root root 13200 Sep 16 18:14 e2fs_stage1_5
+ -rw-r--r--. 1 root root 12512 Sep 16 18:14 fat_stage1_5
+ -rw-r--r--. 1 root root 11744 Sep 16 18:14 ffs_stage1_5
+ -rw-------. 1 root root 1503 Oct 15 11:19 grub.conf
+ [...]
+</pre><div class="para">
+ When you are finished rescuing the guest, exit the shell by entering <code class="command">exit</code> or <code class="command">Ctrl+d</code>.
+ </div><div class="para">
+ <code class="command">virt-rescue</code> has many command line options. The options most often used are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>--ro</strong></span>: Operate in read-only mode on the guest. No changes will be saved. You can use this to experiment with the guest. As soon as you exit from the shell, all of your changes are discarded.
+ </div></li><li class="listitem"><div class="para">
+ <span class="bold bold"><strong>--network</strong></span>: Enable network access from the rescue shell. Use this if you need to, for example, download RPM or other files into the guest.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-virt-rescue.html"><strong>Prev</strong>G.6. virt-rescue: The rescue shell</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-virt-df.html"><strong>Next</strong>G.7. virt-df: Monitoring disk usage</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-s3-s4.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-s3-s4.html
new file mode 100644
index 0000000..7451326
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-s3-s4.html
@@ -0,0 +1,21 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.13. Guest virtual machine power management</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Tips_and_tricks.html" title="Chapter 25. Miscellaneous administration tasks" /><link rel="prev" href="sect-perf-mon.html" title="25.12. Using PMU to monitor guest performance" /><link rel="next" href="sect-qemu-ga.html" title="25.14. QEMU Guest Agent Protocol" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-perf-mon.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-qemu-ga.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-s3-s4"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">25.13. Guest virtual machine power management</h2></div></div></div><div class="para">
+ It is possible to forcibly enable or disable BIOS advertisements to the guest virtual machine's operating system by changing the following parameters in the Domain XML for Libvirt:
+ </div><pre class="screen">
+...
+ <pm>
+ <suspend-to-disk enabled='no'/>
+ <suspend-to-mem enabled='yes'/>
+ </pm>
+ ...
+</pre><div class="para">
+ The element <em class="parameter"><code>pm</code></em> enables ('yes') or disables ('no') BIOS support for S3 (suspend-to-disk) and S4 (suspend-to-mem) ACPI sleep states. If nothing is specified, then the hypervisor will be left with its default value.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-perf-mon.html"><strong>Prev</strong>25.12. Using PMU to monitor guest performance</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-qemu-ga.html"><strong>Next</strong>25.14. QEMU Guest Agent Protocol</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-smbios-sys-info.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-smbios-sys-info.html
new file mode 100644
index 0000000..ecd8da6
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-smbios-sys-info.html
@@ -0,0 +1,38 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.3. SMBIOS system information</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sub-sect-op-sys-cont-boot.html" title="J.2.4. Container boot" /><link rel="next" href="sect-cpu-allocation.html" title="J.4. CPU allocation" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sect-op-sys-cont-boot.html"><strong>Prev</s
trong></a></li><li class="next"><a accesskey="n" href="sect-cpu-allocation.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-smbios-sys-info"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.3. SMBIOS system information</h2></div></div></div><div class="para">
+ Some hypervisors allow control over what system information is presented to the guest (for example, SMBIOS fields can be populated by a hypervisor and inspected via the dmidecode command in the guest). The optional sysinfo element covers all such categories of information.
+ </div><div class="figure"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><os></span>
+ <span class="perl_Keyword"><smbios</span><span class="perl_Others"> mode=</span><span class="perl_String">'sysinfo'</span><span class="perl_Keyword">/></span>
+ ...
+ <span class="perl_Keyword"></os></span>
+ <span class="perl_Keyword"><sysinfo</span><span class="perl_Others"> type=</span><span class="perl_String">'smbios'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><bios></span>
+ <span class="perl_Keyword"><entry</span><span class="perl_Others"> name=</span><span class="perl_String">'vendor'</span><span class="perl_Keyword">></span>LENOVO<span class="perl_Keyword"></entry></span>
+ <span class="perl_Keyword"></bios></span>
+ <span class="perl_Keyword"><system></span>
+ <span class="perl_Keyword"><entry</span><span class="perl_Others"> name=</span><span class="perl_String">'manufacturer'</span><span class="perl_Keyword">></span>Fedora<span class="perl_Keyword"></entry></span>
+ <span class="perl_Keyword"><entry</span><span class="perl_Others"> name=</span><span class="perl_String">'vendor'</span><span class="perl_Keyword">></span>Virt-Manager<span class="perl_Keyword"></entry></span>
+ <span class="perl_Keyword"></system></span>
+ <span class="perl_Keyword"></sysinfo></span>
+ ...
+
+</pre></div><h6>Figure J.6. SMBIOS system information</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-starttag"><sysinfo></code> element has a mandatory attribute <code class="sgmltag-attribute">type</code> that determines the layout of sub-elements, and may be defined as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">smbios</code> - Sub-elements call out specific SMBIOS values, which will affect the guest if used in conjunction with the smbios sub-element of the os element. Each sub-element of sysinfo names a SMBIOS block, and within those elements can be a list of entry elements that describe a field within the block. The following blocks and entries are recognized:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">bios</code> - This is block 0 of SMBIOS, with entry names drawn from <code class="sgmltag-attribute">vendor</code>, <code class="sgmltag-attribute">version</code>, <code class="sgmltag-attribute">date</code>, and <code class="sgmltag-attribute">release</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><system></code> - This is block 1 of SMBIOS, with entry names drawn from <code class="sgmltag-attribute">manufacturer</code>, <code class="sgmltag-attribute">product</code>, <code class="sgmltag-attribute">version</code>, <code class="sgmltag-attribute">serial</code>, <code class="sgmltag-attribute">uuid</code>, <code class="sgmltag-attribute">sku</code>, and <code class="sgmltag-attribute">family</code>. If a <code class="sgmltag-attribute">uuid</code> entry is provided alongside a top-level uuid element, the two values must match.
+ </div></li></ul></div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-op-sys-cont-boot.html"><strong>Prev</strong>J.2.4. Container 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-cpu-allocation.html"><strong>Next</strong>J.4. CPU allocation</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-the-Default_Configuration-libvirt.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-the-Default_Configuration-libvirt.html
new file mode 100644
index 0000000..8a396eb
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-the-Default_Configuration-libvirt.html
@@ -0,0 +1,14 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.4. The default configuration</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Virtual_Networking.html" title="Appendix H. Virtual Networking" /><link rel="prev" href="sub-sect-iso-mode.html" title="H.3.3. Isolated mode" /><link rel="next" href="sect-Virtualization-Virtual_Networking-Example_scenarios.html" title="H.5. Examples of common scenarios" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="pr
evious"><a accesskey="p" href="sub-sect-iso-mode.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Virtual_Networking-Example_scenarios.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-the-Default_Configuration-libvirt"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">H.4. The default configuration</h2></div></div></div><div class="para">
+ When the libvirtd daemon (<code class="command">libvirtd</code>) is first installed, it contains an initial virtual network switch configuration in NAT mode. This configuration is used so that installed guests can communicate to the external network, through the host. The following image demonstrates this default configuration for <code class="systemitem">libvirtd</code>:
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-the_default_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-08-network-overview.png" width="444" alt="Default libvirt network configuration" /></div></div><h6>Figure H.7. Default libvirt network configuration</h6></div><br class="figure-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ A virtual network can be restricted to a specific physical interface. This may be useful on a physical system that has several interfaces (for example, <code class="filename">eth0</code>, <code class="filename">eth1</code> and <code class="filename">eth2</code>). This is only useful in routed and NAT modes, and can be defined in the <code class="command">dev=<interface></code> option, or in <code class="command">virt-manager</code> when creating a new virtual network.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-iso-mode.html"><strong>Prev</strong>H.3.3. Isolated mode</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-Virtual_Networking-Example_scenarios.html"><strong>Next</strong>H.5. Examples of common scenarios</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-the_guestfish_shell.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-the_guestfish_shell.html
new file mode 100644
index 0000000..c8b6056
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-the_guestfish_shell.html
@@ -0,0 +1,122 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.4. The guestfish shell</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /><link rel="prev" href="sect-Guide-Guest_Disks_libguestfs-installation.html" title="G.3. Installation" /><link rel="next" href="sect-Modifying-files-with-guestfish.html" title="G.4.2. Modifying files with guestfish" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-Guide-Guest_Disks_libguestfs-installation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Modifying-files-with-guestfish.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-the_guestfish_shell"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">G.4. The guestfish shell</h2></div></div></div><div class="para">
+ <span class="bold bold"><strong>guestfish</strong></span> is an interactive shell that you can use from the command line or from shell scripts to access guest file systems. All of the functionality of the libguestfs API is available from the shell.
+ </div><div class="para">
+ To begin viewing or editing a virtual machine disk image, run the following command, substituting the path to your desired disk image:
+ </div><pre class="screen">
+guestfish --ro -a /path/to/disk/image
+</pre><div class="para">
+ <span class="bold bold"><strong>--ro</strong></span> means that the disk image is opened read-only. This mode is always safe but does not allow write access. Only omit this option when you are <span class="bold bold"><strong>certain</strong></span> that the guest is not running, or the disk image is not attached to a live guest. It is not possible to use libguestfs to edit a live guest, and attempting to will assuredly result in irreversible disk corruption.
+ </div><div class="para">
+ <span class="bold bold"><strong>/path/to/disk/image</strong></span> is the path to the disk. This can be a file, a host logical volume (such as /dev/VG/LV), a host device (/dev/cdrom) or a SAN LUN (/dev/sdf3).
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ libguestfs and guestfish do not require root privileges. You only need to run them as root if the disk image being accessed needs root to read and/or write.
+ </div></div></div><div class="para">
+ When you start guestfish interactively, it will display this prompt:
+ </div><pre class="screen">
+ guestfish --ro -a /path/to/disk/image
+
+Welcome to guestfish, the libguestfs filesystem interactive shell for editing virtual machine filesystems.
+
+ Type: 'help' for help on commands
+ 'man' to read the manual
+ 'quit' to quit the shell
+
+><fs>
+</pre><div class="para">
+ At the prompt, type <span class="bold bold"><strong>run</strong></span> to initiate the library and attach the disk image. This can take up to 30 seconds the first time it is done. Subsequent starts will complete much faster.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ libguestfs will use hardware virtualization acceleration such as KVM (if available) to speed up this process.
+ </div></div></div><div class="para">
+ Once the <span class="bold bold"><strong>run</strong></span> command has been entered, other commands can be used, as the following section demonstrates.
+ </div><div class="section" id="sect-Viewing_file_systems_with_guestfish"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.4.1. Viewing file systems with guestfish</h3></div></div></div><div class="section" id="sect-Manual-listing-and-viewing"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">G.4.1.1. Manual listing and viewing</h4></div></div></div><div class="para">
+ The <code class="command">list-filesystems</code> command will list file systems found by libguestfs. This output shows a Red Hat Enterprise Linux 4 disk image:
+ </div><pre class="screen">
+><fs> run
+><fs> list-filesystems
+/dev/vda1: ext3
+/dev/VolGroup00/LogVol00: ext3
+/dev/VolGroup00/LogVol01: swap
+</pre><div class="para">
+ This output shows a Windows disk image:
+ </div><pre class="screen">
+><fs> run
+><fs> list-filesystems
+/dev/vda1: ntfs
+/dev/vda2: ntfs
+</pre><div class="para">
+ Other useful commands are <code class="command">list-devices</code>, <code class="command">list-partitions</code>, <code class="command">lvs</code>, <code class="command">pvs</code>, <code class="command">vfs-type</code> and <code class="command">file</code>. You can get more information and help on any command by typing <code class="command">help</code> <span class="emphasis"><em>command</em></span>, as shown in the following output:
+ </div><pre class="screen">
+><fs> help vfs-type
+ NAME
+ vfs-type - get the Linux VFS type corresponding to a mounted device
+
+ SYNOPSIS
+ vfs-type device
+
+ DESCRIPTION
+ This command gets the filesystem type corresponding to the filesystem on
+ "device".
+
+ For most filesystems, the result is the name of the Linux VFS module
+ which would be used to mount this filesystem if you mounted it without
+ specifying the filesystem type. For example a string such as "ext3" or
+ "ntfs".
+</pre><div class="para">
+ To view the actual contents of a file system, it must first be mounted. This example uses one of the Windows partitions shown in the previous output (<code class="filename">/dev/vda2</code>), which in this case is known to correspond to the <span class="bold bold"><strong>C:\</strong></span> drive:
+ </div><pre class="screen">
+><fs> mount-ro /dev/vda2 /
+><fs> ll /
+total 1834753
+ drwxrwxrwx 1 root root 4096 Nov 1 11:40 .
+ drwxr-xr-x 21 root root 4096 Nov 16 21:45 ..
+ lrwxrwxrwx 2 root root 60 Jul 14 2009 Documents and Settings
+ drwxrwxrwx 1 root root 4096 Nov 15 18:00 Program Files
+ drwxrwxrwx 1 root root 4096 Sep 19 10:34 Users
+ drwxrwxrwx 1 root root 16384 Sep 19 10:34 Windows
+</pre><div class="para">
+ You can use guestfish commands such as <code class="command">ls</code>, <code class="command">ll</code>, <code class="command">cat</code>, <code class="command">more</code>, <code class="command">download</code> and <code class="command">tar-out</code> to view and download files and directories.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ There is no concept of a current working directory in this shell. Unlike ordinary shells, you cannot for example use the <code class="command">cd</code> command to change directories. All paths must be fully qualified starting at the top with a forward slash (<span class="bold bold"><strong>/</strong></span>) character. Use the <span class="emphasis"><em>Tab</em></span> key to complete paths.
+ </div></div></div><div class="para">
+ To exit from the guestfish shell, type <code class="command">exit</code> or enter <code class="command">Ctrl+d</code>.
+ </div></div><div class="section" id="sect-Via_guestfish_inspection"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">G.4.1.2. Via guestfish inspection</h4></div></div></div><div class="para">
+ Instead of listing and mounting file systems by hand, it is possible to let guestfish itself inspect the image and mount the file systems as they would be in the guest. To do this, add the <span class="bold bold"><strong>-i</strong></span> option on the command line:
+ </div><pre class="screen">
+guestfish --ro -a /path/to/disk/image -i
+
+Welcome to guestfish, the libguestfs filesystem interactive shell for
+ editing virtual machine filesystems.
+
+ Type: 'help' for help on commands
+ 'man' to read the manual
+ 'quit' to quit the shell
+
+ Operating system: Red Hat Enterprise Linux AS release 4 (Nahant Update 8)
+ /dev/VolGroup00/LogVol00 mounted on /
+ /dev/vda1 mounted on /boot
+
+ ><fs> ll /
+ total 210
+ drwxr-xr-x. 24 root root 4096 Oct 28 09:09 .
+ drwxr-xr-x 21 root root 4096 Nov 17 15:10 ..
+ drwxr-xr-x. 2 root root 4096 Oct 27 22:37 bin
+ drwxr-xr-x. 4 root root 1024 Oct 27 21:52 boot
+ drwxr-xr-x. 4 root root 4096 Oct 27 21:21 dev
+ drwxr-xr-x. 86 root root 12288 Oct 28 09:09 etc
+ [etc]
+</pre><div class="para">
+ Because guestfish needs to start up the libguestfs back end in order to perform the inspection and mounting, the <code class="command">run</code> command is not necessary when using the <code class="command">-i</code> option. The <code class="command">-i</code> option works for many common Linux and Windows guests.
+ </div></div><div class="section" id="sect-Accessing-aguesT-by-name"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">G.4.1.3. Accessing a guest by name</h4></div></div></div><div class="para">
+ A guest can be accessed from the command line when you specify its name as known to libvirt (in other words, as it appears in <code class="command">virsh list --all</code>). Use the <code class="command">-d</code> option to access a guest by its name, with or without the <code class="command">-i</code> option:
+ </div><pre class="screen">
+guestfish --ro -d GuestName -i
+</pre></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Guide-Guest_Disks_libguestfs-installation.html"><strong>Prev</strong>G.3. 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-Modifying-files-with-guestfish.html"><strong>Next</strong>G.4.2. Modifying files with guestfish</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-df.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-df.html
new file mode 100644
index 0000000..d727922
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-df.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.7. virt-df: Monitoring disk usage</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /><link rel="prev" href="sect-run-virt-rescue.html" title="G.6.2. Running virt-rescue" /><link rel="next" href="run-virt-df.html" title="G.7.2. Running virt-df" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-run-virt-rescue.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="run-virt-df.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-virt-df"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">G.7. virt-df: Monitoring disk usage</h2></div></div></div><div class="section" id="sect-virt-df-intro"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.7.1. Introduction</h3></div></div></div><div class="para">
+ This section describes <code class="command">virt-df</code>, which displays file system usage from a disk image or a guest. It is similar to the Linux <code class="command">df</code> command, but for virtual machines.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-run-virt-rescue.html"><strong>Prev</strong>G.6.2. Running virt-rescue</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="run-virt-df.html"><strong>Next</strong>G.7.2. Running virt-df</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-inspector-install.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-inspector-install.html
new file mode 100644
index 0000000..8cae049
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-inspector-install.html
@@ -0,0 +1,16 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.9.2. Installation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-virt-inspector.html" title="G.9. virt-inspector: inspecting guests" /><link rel="prev" href="sect-virt-inspector.html" title="G.9. virt-inspector: inspecting guests" /><link rel="next" href="sect-virt-inspector-run.html" title="G.9.3. Running virt-inspector" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-virt-inspector
.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-virt-inspector-run.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-virt-inspector-install"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.9.2. Installation</h3></div></div></div><div class="para">
+ To install virt-inspector and the documentation, enter the following command:
+ </div><pre class="screen">
+# yum install libguestfs-tools libguestfs-devel
+</pre><div class="para">
+ To process Windows guests you must also install <span class="package">libguestfs-winsupport</span>. Refer to <a class="xref" href="sect-virt-win-reg-install.html">Section G.10.2, “Installation”</a> for details. The documentation, including example XML output and a Relax-NG schema for the output, will be installed in <code class="filename">/usr/share/doc/libguestfs-devel-*/</code> where "*" is replaced by the version number of libguestfs.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-virt-inspector.html"><strong>Prev</strong>G.9. virt-inspector: inspecting 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-virt-inspector-run.html"><strong>Next</strong>G.9.3. Running virt-inspector</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-inspector-run.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-inspector-run.html
new file mode 100644
index 0000000..77bcb88
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-inspector-run.html
@@ -0,0 +1,82 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.9.3. Running virt-inspector</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-virt-inspector.html" title="G.9. virt-inspector: inspecting guests" /><link rel="prev" href="sect-virt-inspector-install.html" title="G.9.2. Installation" /><link rel="next" href="sect-virt-win-reg.html" title="G.10. virt-win-reg: Reading and editing the Windows Registry" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-
virt-inspector-install.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-virt-win-reg.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-virt-inspector-run"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.9.3. Running virt-inspector</h3></div></div></div><div class="para">
+ You can run <code class="command">virt-inspector</code> against any disk image or libvirt guest as shown in the following example:
+ </div><pre class="screen">
+virt-inspector --xml disk.img > report.xml
+</pre><div class="para">
+ Or as shown here:
+ </div><pre class="screen">
+virt-inspector --xml GuestName > report.xml
+</pre><div class="para">
+ The result will be an XML report (<code class="filename">report.xml</code>). The main components of the XML file are a top-level <operatingsytems> element containing usually a single <operatingsystem> element, similar to the following:
+ </div><pre class="screen">
+ <operatingsystems>
+ <operatingsystem>
+
+ <!-- the type of operating system and Linux distribution -->
+ <name>linux</name>
+ <distro>rhel</distro>
+ <!-- the name, version and architecture -->
+ <product_name>Red Hat Enterprise Linux Server release 6.4 </product_name>
+ <major_version>6</major_version>
+ <minor_version>4</minor_version>
+ <package_format>rpm</package_format>
+ <package_management>yum</package_management>
+ <root>/dev/VolGroup/lv_root</root>
+ <!-- how the filesystems would be mounted when live -->
+ <mountpoints>
+ <mountpoint dev="/dev/VolGroup/lv_root">/</mountpoint>
+ <mountpoint dev="/dev/sda1">/boot</mountpoint>
+ <mountpoint dev="/dev/VolGroup/lv_swap">swap</mountpoint>
+ </mountpoints>
+
+ < !-- filesystems-->
+ <filesystem dev="/dev/VolGroup/lv_root">
+ <label></label>
+ <uuid>b24d9161-5613-4ab8-8649-f27a8a8068d3</uuid>
+ <type>ext4</type>
+ <content>linux-root</content>
+ <spec>/dev/mapper/VolGroup-lv_root</spec>
+ </filesystem>
+ <filesystem dev="/dev/VolGroup/lv_swap">
+ <type>swap</type>
+ <spec>/dev/mapper/VolGroup-lv_swap</spec>
+ </filesystem>
+ <!-- packages installed -->
+ <applications>
+ <application>
+ <name>firefox</name>
+ <version>3.5.5</version>
+ <release>1.fc12</release>
+ </application>
+ </applications>
+
+ </operatingsystem>
+ </operatingsystems>
+</pre><div class="para">
+ Processing these reports is best done using W3C standard XPath queries. Fedora comes with a command line program (<code class="command">xpath</code>) which can be used for simple instances; however, for long-term and advanced usage, you should consider using an XPath library along with your favorite programming language.
+ </div><div class="para">
+ As an example, you can list out all file system devices using the following XPath query:
+ </div><pre class="screen">
+virt-inspector --xml GuestName | xpath //filesystem/@dev
+ Found 3 nodes:
+ -- NODE --
+ dev="/dev/sda1"
+ -- NODE --
+ dev="/dev/vg_f12x64/lv_root"
+ -- NODE --
+ dev="/dev/vg_f12x64/lv_swap"
+</pre><div class="para">
+ Or list the names of all applications installed by entering:
+ </div><pre class="screen">
+ virt-inspector --xml GuestName | xpath //application/name
+ [...long list...]
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-virt-inspector-install.html"><strong>Prev</strong>G.9.2. 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-virt-win-reg.html"><strong>Next</strong>G.10. virt-win-reg: Reading and editing the Windo...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-inspector.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-inspector.html
new file mode 100644
index 0000000..7a2edc9
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-inspector.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.9. virt-inspector: inspecting guests</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /><link rel="prev" href="sect-expand-disk-image.html" title="G.8.2. Expanding a disk image" /><link rel="next" href="sect-virt-inspector-install.html" title="G.9.2. Installation" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-expand-disk-image.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-virt-inspector-install.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-virt-inspector"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">G.9. virt-inspector: inspecting guests</h2></div></div></div><div class="section" id="sect-virt-inspector-intro"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.9.1. Introduction</h3></div></div></div><div class="para">
+ <code class="command">virt-inspector</code> is a tool for inspecting a disk image to find out what operating system it contains.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-expand-disk-image.html"><strong>Prev</strong>G.8.2. Expanding a 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-virt-inspector-install.html"><strong>Next</strong>G.9.2. Installation</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-rescue.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-rescue.html
new file mode 100644
index 0000000..fb28659
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-rescue.html
@@ -0,0 +1,16 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.6. virt-rescue: The rescue shell</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /><link rel="prev" href="sect-other-commands.html" title="G.5. Other commands" /><link rel="next" href="sect-run-virt-rescue.html" title="G.6.2. Running virt-rescue" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-other-commands.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-run-virt-rescue.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-virt-rescue"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">G.6. virt-rescue: The rescue shell</h2></div></div></div><div class="section" id="sect-virt-rescue-intro"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.6.1. Introduction</h3></div></div></div><div class="para">
+ This section describes <code class="command">virt-rescue</code>, which can be considered analogous to a rescue CD for virtual machines. It boots a guest into a rescue shell so that maintenance can be performed to correct errors and the guest can be repaired.
+ </div><div class="para">
+ There is some overlap between virt-rescue and guestfish. It is important to distinguish their differing uses. virt-rescue is for making interactive, ad-hoc changes using ordinary Linux file system tools. It is particularly suited to rescuing a guest that has gone wrong. virt-rescue cannot be scripted.
+ </div><div class="para">
+ In contrast, guestfish is particularly useful for making scripted, structured changes through a formal set of commands (the libguestfs API), although it can also be used interactively.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-other-commands.html"><strong>Prev</strong>G.5. Other commands</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-run-virt-rescue.html"><strong>Next</strong>G.6.2. Running virt-rescue</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-resize.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-resize.html
new file mode 100644
index 0000000..44d97d8
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-resize.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.8. virt-resize: resizing guests offline</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /><link rel="prev" href="run-virt-df.html" title="G.7.2. Running virt-df" /><link rel="next" href="sect-expand-disk-image.html" title="G.8.2. Expanding a disk image" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="run-virt-df.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-expand-disk-image.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-virt-resize"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">G.8. virt-resize: resizing guests offline</h2></div></div></div><div class="section" id="sect-virt-resize-intro"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.8.1. Introduction</h3></div></div></div><div class="para">
+ This section describes <code class="command">virt-resize</code>, a tool for expanding or shrinking guests. It only works for guests which are offline (shut down). It works by copying the guest image and leaving the original disk image untouched. This is ideal because you can use the original image as a backup, however there is a trade-off as you need twice the amount of disk space.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="run-virt-df.html"><strong>Prev</strong>G.7.2. Running virt-df</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-expand-disk-image.html"><strong>Next</strong>G.8.2. Expanding a disk image</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-win-reg-install.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-win-reg-install.html
new file mode 100644
index 0000000..9a4ca94
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-win-reg-install.html
@@ -0,0 +1,14 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.10.2. Installation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-virt-win-reg.html" title="G.10. virt-win-reg: Reading and editing the Windows Registry" /><link rel="prev" href="sect-virt-win-reg.html" title="G.10. virt-win-reg: Reading and editing the Windows Registry" /><link rel="next" href="sect-virt-win-reg-use.html" title="G.10.3. Using virt-win-reg" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 acce
sskey="p" href="sect-virt-win-reg.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-virt-win-reg-use.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-virt-win-reg-install"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.10.2. Installation</h3></div></div></div><div class="para">
+ To use <code class="command">virt-win-reg</code> you must run the following:
+ </div><pre class="screen">
+# yum install libguestfs-tools libguestfs-winsupport
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-virt-win-reg.html"><strong>Prev</strong>G.10. virt-win-reg: Reading and editing the Windo...</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-virt-win-reg-use.html"><strong>Next</strong>G.10.3. Using virt-win-reg</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-win-reg-use.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-win-reg-use.html
new file mode 100644
index 0000000..2d67b21
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-win-reg-use.html
@@ -0,0 +1,29 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.10.3. Using virt-win-reg</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-virt-win-reg.html" title="G.10. virt-win-reg: Reading and editing the Windows Registry" /><link rel="prev" href="sect-virt-win-reg-install.html" title="G.10.2. Installation" /><link rel="next" href="sect-Using-API-Programming-Languages.html" title="G.11. Using the API from Programming Languages" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 a
ccesskey="p" href="sect-virt-win-reg-install.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Using-API-Programming-Languages.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-virt-win-reg-use"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.10.3. Using virt-win-reg</h3></div></div></div><div class="para">
+ To read out Registry keys, specify the name of the guest (or its disk image) and the name of the Registry key. You must use single quotes to surround the name of the desired key:
+ </div><pre class="screen">
+# virt-win-reg WindowsGuest \
+ 'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall' \
+ | less
+</pre><div class="para">
+ The output is in the standard text-based format used by <code class="filename">.REG</code> files on Windows.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Hex-quoting is used for strings because the format does not properly define a portable encoding method for strings. This is the only way to ensure fidelity when transporting <code class="filename">.REG</code> files from one machine to another.
+ </div><div class="para">
+ You can make hex-quoted strings printable by piping the output of <code class="command">virt-win-reg</code> through this simple Perl script:
+ </div><pre class="screen">perl -MEncode -pe's?hex\((\d+)\):(\S+)?$t=$1;$_=$2;s,\,,,g;"str($t):\"".decode(utf16le=>pack("H*",$_))."\""?eg'
+</pre></div></div><div class="para">
+ To merge changes into the Windows Registry of an offline guest, you must first prepare a <code class="filename">.REG</code> file. There is a great deal of documentation about doing this available from MSDN, and there is a good summary in the following Wikipedia page: <a href="https://secure.wikimedia.org/wikipedia/en/wiki/Windows_Registry#.REG_files">https://secure.wikimedia.org/wikipedia/en/wiki/Windows_Registry#.REG_files</a>. When you have prepared a <code class="filename">.REG</code> file, enter the following:
+ </div><pre class="screen">
+# virt-win-reg --merge WindowsGuest input.reg
+</pre><div class="para">
+ This will update the registry in the guest.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-virt-win-reg-install.html"><strong>Prev</strong>G.10.2. 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-Using-API-Programming-Languages.html"><strong>Next</strong>G.11. Using the API from Programming Languages</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-win-reg.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-win-reg.html
new file mode 100644
index 0000000..6641d68
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect-virt-win-reg.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>G.10. virt-win-reg: Reading and editing the Windows Registry</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-Guest_Disks_libguestfs.html" title="Appendix G. Guest disk access with offline tools" /><link rel="prev" href="sect-virt-inspector-run.html" title="G.9.3. Running virt-inspector" /><link rel="next" href="sect-virt-win-reg-install.html" title="G.10.2. Installation" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-virt-inspector-run.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-virt-win-reg-install.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-virt-win-reg"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">G.10. virt-win-reg: Reading and editing the Windows Registry</h2></div></div></div><div class="section" id="sect-virt-win-reg-intro"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">G.10.1. Introduction</h3></div></div></div><div class="para">
+ <code class="command">virt-win-reg</code> is a tool that manipulates the Registry in Windows guests. It can be used to read out registry keys. You can also use it to make changes to the Registry, but you must <span class="bold bold"><strong>never</strong></span> try to do this for live/running guests, as it will result in disk corruption.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-virt-inspector-run.html"><strong>Prev</strong>G.9.3. Running virt-inspector</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-virt-win-reg-install.html"><strong>Next</strong>G.10.2. Installation</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect_RedHat-Getting_Help_and_Giving_Feedback.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect_RedHat-Getting_Help_and_Giving_Feedback.html
new file mode 100644
index 0000000..ab04fa4
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sect_RedHat-Getting_Help_and_Giving_Feedback.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2. Getting Help and Giving Feedback</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-Virtualization_Deployment_and_Administration_Guide-19-en-US-1.0-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.19');
+
+ addID('Fedora.19.books');
+ addID('Fedora.19.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html" title="Preface" /><link rel="prev" href="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html" title="Preface" /><link rel="next" href="sect-RedHat-We_Need_Feedback.html" title="2.2. We Need Feedback!" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.redhat.com"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.redhat.com"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previo
us"><a accesskey="p" href="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Preface.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-RedHat-We_Need_Feedback.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="sect_RedHat-Getting_Help_and_Giving_Feedback" lang="en-US"><div class="titlepage"><div><div><h2 class="title">2. Getting Help and Giving Feedback</h2></div></div></div><div class="section" id="sect_RedHat-Do_You_Need_Help"><div class="titlepage"><div><div><h3 class="title">2.1. Do You Need Help?</h3></div></div></div><a id="idm13196032" class="indexterm"></a><div class="para">
+ If you experience difficulty with a procedure described in this documentation, visit the Red Hat Customer Portal at <a href="http://access.redhat.com">http://access.redhat.com</a>. Through the customer portal, you can:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ search or browse through a knowledgebase of technical support articles about Red Hat products.
+ </div></li><li class="listitem"><div class="para">
+ submit a support case to Red Hat Global Support Services (GSS).
+ </div></li><li class="listitem"><div class="para">
+ access other product documentation.
+ </div></li></ul></div><div class="para">
+ Red Hat also hosts a large number of electronic mailing lists for discussion of Red Hat software and technology. You can find a list of publicly available mailing lists at <a href="https://www.redhat.com/mailman/listinfo">https://www.redhat.com/mailman/listinfo</a>. Click on the name of any mailing list to subscribe to that list or to access the list archives.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pref-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-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="sect-RedHat-We_Need_Feedback.html"><strong>Next</strong>2.2. We Need Feedback!</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-example.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-example.html
new file mode 100644
index 0000000..65a2417
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-example.html
@@ -0,0 +1,69 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.23. Example domain XML configuration</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="section-libvirt-dom-xml-security-label.html" title="J.22. Security label" /><link rel="next" href="appe-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Revision_History.html" title="Appendix K. Revision History" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="docna
v"><li class="previous"><a accesskey="p" href="section-libvirt-dom-xml-security-label.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="appe-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Revision_History.html"><strong>Next</strong></a></li></ul><div class="section" id="section-libvirt-dom-xml-example"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.23. Example domain XML configuration</h2></div></div></div><div class="para">
+ QEMU emulated guest on x86_64
+ </div><div class="figure" id="fig-dom-xml-example-qemu"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain</span><span class="perl_Others"> type=</span><span class="perl_String">'qemu'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><name></span>QEmu-fedora-i686<span class="perl_Keyword"></name></span>
+ <span class="perl_Keyword"><uuid></span>c7a5fdbd-cdaf-9455-926a-d65c16db1809<span class="perl_Keyword"></uuid></span>
+ <span class="perl_Keyword"><memory></span>219200<span class="perl_Keyword"></memory></span>
+ <span class="perl_Keyword"><currentMemory></span>219200<span class="perl_Keyword"></currentMemory></span>
+ <span class="perl_Keyword"><vcpu></span>2<span class="perl_Keyword"></vcpu></span>
+ <span class="perl_Keyword"><os></span>
+ <span class="perl_Keyword"><type</span><span class="perl_Others"> arch=</span><span class="perl_String">'i686'</span><span class="perl_Others"> machine=</span><span class="perl_String">'pc'</span><span class="perl_Keyword">></span>hvm<span class="perl_Keyword"></type></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> dev=</span><span class="perl_String">'cdrom'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></os></span>
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><emulator></span>/usr/bin/qemu-system-x86_64<span class="perl_Keyword"></emulator></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'file'</span><span class="perl_Others"> device=</span><span class="perl_String">'cdrom'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> file=</span><span class="perl_String">'/home/user/boot.iso'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hdc'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><readonly/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'file'</span><span class="perl_Others"> device=</span><span class="perl_String">'disk'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> file=</span><span class="perl_String">'/home/user/fedora.img'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hda'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'vnc'</span><span class="perl_Others"> port=</span><span class="perl_String">'-1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.72. Example domain XML config</h6></div><br class="figure-break" /><div class="para">
+ KVM hardware accelerated guest on i686
+ </div><div class="figure" id="fig-dom-xml-example-kvm"><div class="figure-contents"><pre class="programlisting">
+
+<span class="perl_Keyword"><domain</span><span class="perl_Others"> type=</span><span class="perl_String">'kvm'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><name></span>demo2<span class="perl_Keyword"></name></span>
+ <span class="perl_Keyword"><uuid></span>4dea24b3-1d52-d8f3-2516-782e98a23fa0<span class="perl_Keyword"></uuid></span>
+ <span class="perl_Keyword"><memory></span>131072<span class="perl_Keyword"></memory></span>
+ <span class="perl_Keyword"><vcpu></span>1<span class="perl_Keyword"></vcpu></span>
+ <span class="perl_Keyword"><os></span>
+ <span class="perl_Keyword"><type</span><span class="perl_Others"> arch=</span><span class="perl_String">"i686"</span><span class="perl_Keyword">></span>hvm<span class="perl_Keyword"></type></span>
+ <span class="perl_Keyword"></os></span>
+ <span class="perl_Keyword"><clock</span><span class="perl_Others"> sync=</span><span class="perl_String">"localtime"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><emulator></span>/usr/bin/qemu-kvm<span class="perl_Keyword"></emulator></span>
+ <span class="perl_Keyword"><disk</span><span class="perl_Others"> type=</span><span class="perl_String">'file'</span><span class="perl_Others"> device=</span><span class="perl_String">'disk'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> file=</span><span class="perl_String">'/var/lib/libvirt/images/demo2.img'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'hda'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></disk></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">'24:42:53:21:52:45'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'vnc'</span><span class="perl_Others"> port=</span><span class="perl_String">'-1'</span><span class="perl_Others"> keymap=</span><span class="perl_String">'de'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+<span class="perl_Keyword"></domain></span>
+
+</pre></div><h6>Figure J.73. Example domain XML config</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="section-libvirt-dom-xml-security-label.html"><strong>Prev</strong>J.22. Security label</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-Red_Hat_Enterprise_Linux-Virtualization_Deployment_and_Administration-Revision_History.html"><strong>Next</strong>Appendix K. Revision History</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-memory-baloon-device.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-memory-baloon-device.html
new file mode 100644
index 0000000..e67f069
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-memory-baloon-device.html
@@ -0,0 +1,34 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.19. Memory balloon device</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="section-libvirt-dom-xml-watchdog.html" title="J.18. Watchdog device" /><link rel="next" href="section-libvirt-dom-xml-random-number-gen.html" title="J.20. Random number generator device" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="s
ection-libvirt-dom-xml-watchdog.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="section-libvirt-dom-xml-random-number-gen.html"><strong>Next</strong></a></li></ul><div class="section" id="section-libvirt-dom-xml-memory-baloon-device"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.19. Memory balloon device</h2></div></div></div><div class="para">
+ A virtual memory balloon device is added to all Xen and KVM/QEMU guests. It will be seen as <code class="sgmltag-starttag"><memballoon></code> element. It will be automatically added when appropriate, so there is no need to explicitly add this element in the guest XML unless a specific PCI slot needs to be assigned. Note that if the memballoon device needs to be explicitly disabled, <code class="sgmltag-attribute">model='none'</code> may be used.
+ </div><div class="para">
+ The following example automatically added device with KVM
+ </div><div class="figure" id="fig-dom-xml-memory-baloon-device"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><memballoon</span><span class="perl_Others"> model=</span><span class="perl_String">'virtio'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.67. Memory balloon device</h6></div><br class="figure-break" /><div class="para">
+ Here is an example where the device is added manually with static PCI slot 2 requested
+ </div><div class="figure" id="fig-dom-xml-memory-baloon-device2"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><memballoon</span><span class="perl_Others"> model=</span><span class="perl_String">'virtio'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'pci'</span><span class="perl_Others"> domain=</span><span class="perl_String">'0x0000'</span><span class="perl_Others"> bus=</span><span class="perl_String">'0x00'</span><span class="perl_Others"> slot=</span><span class="perl_String">'0x02'</span><span class="perl_Others"> function=</span><span class="perl_String">'0x0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></memballoon></span>
+ <span class="perl_Keyword"></devices></span>
+<span class="perl_Error"><</span>/domain>
+</pre></div><h6>Figure J.68. Memory balloon device added manually</h6></div><br class="figure-break" /><div class="para">
+ The required <code class="sgmltag-element">model</code> attribute specifies what type of balloon device is provided. Valid values are specific to the virtualization platform are: <code class="sgmltag-element">'virtio'</code> which is the default setting with the KVM hypervisor or <code class="sgmltag-element">'xen'</code> which is the default setting with the Xen hypervisor.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="section-libvirt-dom-xml-watchdog.html"><strong>Prev</strong>J.18. Watchdog device</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="section-libvirt-dom-xml-random-number-gen.html"><strong>Next</strong>J.20. Random number generator device</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-random-number-gen.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-random-number-gen.html
new file mode 100644
index 0000000..5511c27
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-random-number-gen.html
@@ -0,0 +1,37 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.20. Random number generator device</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="section-libvirt-dom-xml-memory-baloon-device.html" title="J.19. Memory balloon device" /><link rel="next" href="section-libvirt-dom-xml-tpm-device.html" title="J.21. TPM devices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="section-l
ibvirt-dom-xml-memory-baloon-device.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="section-libvirt-dom-xml-tpm-device.html"><strong>Next</strong></a></li></ul><div class="section" id="section-libvirt-dom-xml-random-number-gen"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.20. Random number generator device</h2></div></div></div><div class="para">
+ The virtual random number generator device allows the host to pass through entropy to guest operating systems.
+ </div><div class="figure" id="fig--dom-xml-random-number-gen"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><rng</span><span class="perl_Others"> model=</span><span class="perl_String">'virtio'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><rate</span><span class="perl_Others"> period=</span><span class="perl_String">"2000"</span><span class="perl_Others"> bytes=</span><span class="perl_String">"1234"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><backend</span><span class="perl_Others"> model=</span><span class="perl_String">'random'</span><span class="perl_Keyword">></span>/dev/random<span class="perl_Keyword"></backend></span>
+ <span class="perl_Comment"><!-- OR --></span>
+ <span class="perl_Keyword"><backend</span><span class="perl_Others"> model=</span><span class="perl_String">'egd'</span><span class="perl_Others"> type=</span><span class="perl_String">'udp'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'bind'</span><span class="perl_Others"> service=</span><span class="perl_String">'1234'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'connect'</span><span class="perl_Others"> host=</span><span class="perl_String">'1.2.3.4'</span><span class="perl_Others"> service=</span><span class="perl_String">'1234'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"></backend></span>
+ <span class="perl_Keyword"></rng></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.69. Random number generator device</h6></div><br class="figure-break" /><div class="para">
+ The random number generator device allows the following attributes/elements:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">model</code> - The required <code class="sgmltag-attribute">model</code> attribute specifies what type of RNG device is provided. <code class="sgmltag-attvalue">'virtio'</code> — supported by qemu and virtio-rng kernel module
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><backend></code> - The <code class="sgmltag-starttag"><backend></code> element specifies the source of entropy to be used for the domain. The source model is configured using the <code class="sgmltag-attribute">model</code> attribute. Supported source models include <code class="sgmltag-attvalue">'random'</code> — <code class="filename">/dev/random</code> (default setting) or similar device as source and <code class="sgmltag-attvalue">'egd'</code> which sets a EGD protocol backend.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">backend type='random'</code> - This <code class="sgmltag-starttag"><backend></code> type expects a non-blocking character device as input. Examples of such devices are <code class="filename">/dev/random</code> and <code class="filename">/dev/urandom</code>. The file name is specified as contents of the <code class="sgmltag-starttag"><backend></code> element. When no file name is specified the hypervisor default is used.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><backend type='egd'></code> - This backend connects to a source using the EGD protocol. The source is specified as a character device. Refer to character device host interface for more information.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="section-libvirt-dom-xml-memory-baloon-device.html"><strong>Prev</strong>J.19. Memory balloon device</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="section-libvirt-dom-xml-tpm-device.html"><strong>Next</strong>J.21. TPM devices</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-security-label.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-security-label.html
new file mode 100644
index 0000000..9978eb5
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-security-label.html
@@ -0,0 +1,53 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.22. Security label</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="section-libvirt-dom-xml-tpm-device.html" title="J.21. TPM devices" /><link rel="next" href="section-libvirt-dom-xml-example.html" title="J.23. Example domain XML configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="section-lib
virt-dom-xml-tpm-device.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="section-libvirt-dom-xml-example.html"><strong>Next</strong></a></li></ul><div class="section" id="section-libvirt-dom-xml-security-label"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.22. Security label</h2></div></div></div><div class="para">
+ The <code class="sgmltag-starttag"><seclabel></code> element allows control over the operation of the security drivers. There are three basic modes of operation, <code class="sgmltag-attvalue">'dynamic'</code> where libvirt automatically generates a unique security label, <code class="sgmltag-attvalue">'static'</code> where the application/administrator chooses the labels, or <code class="sgmltag-element">'none'</code> where confinement is disabled. With dynamic label generation, libvirt will always automatically relabel any resources associated with the virtual machine. With static label assignment, by default, the administrator or application must ensure labels are set correctly on any resources, however, automatic relabeling can be enabled if desired.
+ </div><div class="para">
+ If more than one security driver is used by libvirt, multiple seclabel tags can be used, one for each driver and the security driver referenced by each tag can be defined using the attribute <code class="sgmltag-attribute">model</code> Valid input XML configurations for the top-level security label are:
+ </div><div class="figure" id="fig-libvirt-dom-xml-security-label"><div class="figure-contents"><pre class="programlisting">
+
+ <span class="perl_Keyword"><seclabel</span><span class="perl_Others"> type=</span><span class="perl_String">'dynamic'</span><span class="perl_Others"> model=</span><span class="perl_String">'selinux'</span><span class="perl_Keyword">/></span>
+
+ <span class="perl_Keyword"><seclabel</span><span class="perl_Others"> type=</span><span class="perl_String">'dynamic'</span><span class="perl_Others"> model=</span><span class="perl_String">'selinux'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><baselabel></span>system_u:system_r:my_svirt_t:s0<span class="perl_Keyword"></baselabel></span>
+ <span class="perl_Keyword"></seclabel></span>
+
+ <span class="perl_Keyword"><seclabel</span><span class="perl_Others"> type=</span><span class="perl_String">'static'</span><span class="perl_Others"> model=</span><span class="perl_String">'selinux'</span><span class="perl_Others"> relabel=</span><span class="perl_String">'no'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><label></span>system_u:system_r:svirt_t:s0:c392,c662<span class="perl_Keyword"></label></span>
+ <span class="perl_Keyword"></seclabel></span>
+
+ <span class="perl_Keyword"><seclabel</span><span class="perl_Others"> type=</span><span class="perl_String">'static'</span><span class="perl_Others"> model=</span><span class="perl_String">'selinux'</span><span class="perl_Others"> relabel=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><label></span>system_u:system_r:svirt_t:s0:c392,c662<span class="perl_Keyword"></label></span>
+ <span class="perl_Keyword"></seclabel></span>
+
+ <span class="perl_Keyword"><seclabel</span><span class="perl_Others"> type=</span><span class="perl_String">'none'</span><span class="perl_Keyword">/></span>
+</pre></div><h6>Figure J.71. Security label</h6></div><br class="figure-break" /><div class="para">
+ If no <code class="sgmltag-attribute">'type'</code> attribute is provided in the input XML, then the security driver default setting will be used, which may be either <code class="sgmltag-attvalue">'none'</code> or <code class="sgmltag-attvalue">'dynamic'</code>. If a <code class="sgmltag-starttag"><baselabel></code> is set but no <code class="sgmltag-attribute">'type'</code> is set, then the type is presumed to be <code class="sgmltag-attribute">'dynamic'</code>. When viewing the XML for a running guest with automatic resource relabeling active, an additional XML element, <code class="sgmltag-attribute">imagelabel</code>, will be included. This is an output-only element, so will be ignored in user supplied XML documents.
+ </div><div class="para">
+ The following elements can be manipulated with the following values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">type</code> - Either <code class="sgmltag-element">static</code>, <code class="sgmltag-element">dynamic</code> or <code class="sgmltag-element">none</code> to determine whether libvirt automatically generates a unique security label or not.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">model</code> - A valid security model name, matching the currently activated security model
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">relabel</code> - Either <code class="sgmltag-attvalue">yes</code> or <code class="sgmltag-attvalue">no</code>. This must always be <code class="sgmltag-attvalue">yes</code> if dynamic label assignment is used. With static label assignment it will default to <code class="sgmltag-attvalue">no</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><label></code> - If static labelling is used, this must specify the full security label to assign to the virtual domain. The format of the content depends on the security driver in use:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">SELinux</code>: a SELinux context.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">AppArmor</code>: an AppArmor profile.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">DAC</code>: owner and group separated by colon. They can be defined both as user/group names or uid/gid. The driver will first try to parse these values as names, but a leading plus sign can used to force the driver to parse them as uid or gid.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><baselabel></code> - If dynamic labelling is used, this can optionally be used to specify the base security label. The format of the content depends on the security driver in use.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><imagelabel></code> - This is an output only element, which shows the security label used on resources associated with the virtual domain. The format of the content depends on the security driver in use When relabeling is in effect, it is also possible to fine-tune the labeling done for specific source file names, by either disabling the labeling (useful if the file lives on NFS or other file system that lacks security labeling) or requesting an alternate label (useful when a management application creates a special label to allow sharing of some, but not all, resources between domains). When a seclabel element is attached to a specific path rather than the top-level domain assignment, only the attribute relabel or the sub-element label are supported.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="section-libvirt-dom-xml-tpm-device.html"><strong>Prev</strong>J.21. TPM 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="section-libvirt-dom-xml-example.html"><strong>Next</strong>J.23. Example domain XML configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-sound-devices.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-sound-devices.html
new file mode 100644
index 0000000..6487f8c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-sound-devices.html
@@ -0,0 +1,32 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.17. Sound devices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-host-interface.html" title="J.16.17. Host interface" /><link rel="next" href="section-libvirt-dom-xml-watchdog.html" title="J.18. Watchdog device" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-s
ection-libvirt-dom-xml-devices-host-interface.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="section-libvirt-dom-xml-watchdog.html"><strong>Next</strong></a></li></ul><div class="section" id="section-libvirt-dom-xml-sound-devices"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.17. Sound devices</h2></div></div></div><div class="para">
+ A virtual sound card can be attached to the host via the sound element.
+ </div><div class="figure" id="fig-dom-xml-sound-devices"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><sound</span><span class="perl_Others"> model=</span><span class="perl_String">'es1370'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.64. Virtual sound card</h6></div><br class="figure-break" /><div class="para">
+ The sound element has one mandatory attribute, <code class="sgmltag-attribute">model</code>, which specifies what real sound device is emulated. Valid values are specific to the underlying hypervisor, though typical choices are <code class="sgmltag-attvalue">'es1370'</code>, <code class="sgmltag-attvalue">'sb16'</code>, <code class="sgmltag-attvalue">'ac97'</code>, and <code class="sgmltag-attvalue">'ich6'</code>. In addition, a sound element with ich6 model can have optional sub-elements <code class="sgmltag-element">codec</code> to attach various audio codecs to the audio device. If not specified, a default codec will be attached to allow playback and recording. Valid values are <code class="sgmltag-attvalue">'duplex'</code> (advertises a line-in and a line-out) and <code class="sgmltag-attvalue">'micro'</code> (advertises a speaker and a microphone).
+ </div><div class="figure" id="fig-dom-xml-sound-devices2"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><sound</span><span class="perl_Others"> model=</span><span class="perl_String">'ich6'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><codec</span><span class="perl_Others"> type=</span><span class="perl_String">'micro'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><sound/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.65. Sound devices</h6></div><br class="figure-break" /><div class="para">
+ Each sound element has an optional sub-element <code class="sgmltag-starttag"><address></code> which can tie the device to a particular PCI slot, documented above.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-host-interface.html"><strong>Prev</strong>J.16.17. Host interface</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="section-libvirt-dom-xml-watchdog.html"><strong>Next</strong>J.18. Watchdog device</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-tpm-device.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-tpm-device.html
new file mode 100644
index 0000000..7c0e485
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-tpm-device.html
@@ -0,0 +1,26 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.21. TPM devices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="section-libvirt-dom-xml-random-number-gen.html" title="J.20. Random number generator device" /><link rel="next" href="section-libvirt-dom-xml-security-label.html" title="J.22. Security label" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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" hr
ef="section-libvirt-dom-xml-random-number-gen.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="section-libvirt-dom-xml-security-label.html"><strong>Next</strong></a></li></ul><div class="section" id="section-libvirt-dom-xml-tpm-device"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.21. TPM devices</h2></div></div></div><div class="para">
+ The TPM device enables a QEMU guest to have access to TPM functionality. The TPM passthrough device type provides access to the host's TPM for one QEMU guest. No other software may be is using the TPM device, typically <code class="filename">/dev/tpm0</code>, at the time the QEMU guest is started. The following domain XML example shows the usage of the TPM passthrough device
+ </div><div class="figure" id="fig-libvirt-dom-xml-tpm-device"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><tpm</span><span class="perl_Others"> model=</span><span class="perl_String">'tpm-tis'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><backend</span><span class="perl_Others"> type=</span><span class="perl_String">'passthrough'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><backend</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/tpm0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></backend></span>
+ <span class="perl_Keyword"></tpm></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+
+</pre></div><h6>Figure J.70. TPM devices</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-attribute">model</code> attribute specifies what device model QEMU provides to the guest. If no model name is provided, tpm-tis will automatically be chosen. The <code class="sgmltag-starttag"><backend></code> element specifies the type of TPM device. The following types are supported: <code class="sgmltag-attvalue">'passthrough'</code> — uses the host's TPM device and <code class="sgmltag-attvalue">'passthrough'</code>. This backend type requires exclusive access to a TPM device on the host. An example for such a device is <code class="filename">/dev/tpm0</code>. The filename is specified as path attribute of the source element. If no file name is specified then <code class="filename">/dev/tpm0</code> is automatically used.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="section-libvirt-dom-xml-random-number-gen.html"><strong>Prev</strong>J.20. Random number generator device</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="section-libvirt-dom-xml-security-label.html"><strong>Next</strong>J.22. Security label</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-watchdog.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-watchdog.html
new file mode 100644
index 0000000..e3253d6
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/section-libvirt-dom-xml-watchdog.html
@@ -0,0 +1,51 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.18. Watchdog device</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="ch-lib-dom-xml.html" title="Appendix J. Manipulating the domain xml" /><link rel="prev" href="section-libvirt-dom-xml-sound-devices.html" title="J.17. Sound devices" /><link rel="next" href="section-libvirt-dom-xml-memory-baloon-device.html" title="J.19. Memory balloon device" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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
ion-libvirt-dom-xml-sound-devices.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="section-libvirt-dom-xml-memory-baloon-device.html"><strong>Next</strong></a></li></ul><div class="section" id="section-libvirt-dom-xml-watchdog"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">J.18. Watchdog device</h2></div></div></div><div class="para">
+ A virtual hardware watchdog device can be added to the guest via the <code class="sgmltag-starttag"><watchdog></code> element. The watchdog device requires an additional driver and management daemon in the guest. As merely enabling the watchdog in the libvirt configuration does not do anything useful on its own. Currently there is no support notification when the watchdog fires.
+ </div><div class="figure" id="fig--dom-xml-watchdog"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><watchdog</span><span class="perl_Others"> model=</span><span class="perl_String">'i6300esb'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><watchdog</span><span class="perl_Others"> model=</span><span class="perl_String">'i6300esb'</span><span class="perl_Others"> action=</span><span class="perl_String">'poweroff'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+<span class="perl_Error"><</span>/domain>
+</pre></div><h6>Figure J.66. Watchdog device</h6></div><br class="figure-break" /><div class="para">
+ The following attributes are declared in this XML:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">model</code> - The required <code class="sgmltag-attribute">model</code> attribute specifies what real watchdog device is emulated. Valid values are specific to the underlying hypervisor.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="sgmltag-attribute">model</code> attribute may take the following values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">i6300esb</code> — the recommended device, emulating a PCI Intel 6300ESB
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">ib700</code> — emulates an ISA iBase IB700
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">action</code> - The optional <code class="sgmltag-attribute">action</code> attribute describes what action to take when the watchdog expires. Valid values are specific to the underlying hypervisor. The <code class="sgmltag-attribute">action</code> attribute can have the following values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">reset</code> — default setting, forcefully resets the guest
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">shutdown</code> — gracefully shuts down the guest (not recommended)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">poweroff</code> — forcefully powers off the guest
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">pause</code> — pauses the guest
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">none</code> — does nothing
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">dump</code> — automatically dumps the guest.
+ </div></li></ul></div></li></ul></div><div class="para">
+ Note that the 'shutdown' action requires that the guest is responsive to ACPI signals. In the sort of situations where the watchdog has expired, guests are usually unable to respond to ACPI signals. Therefore using 'shutdown' is not recommended. In addition, the directory to save dump files can be configured by auto_dump_path in file /etc/libvirt/qemu.conf.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="section-libvirt-dom-xml-sound-devices.html"><strong>Prev</strong>J.17. Sound 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="section-libvirt-dom-xml-memory-baloon-device.html"><strong>Next</strong>J.19. Memory balloon device</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/shared-storage-nfs-migration.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/shared-storage-nfs-migration.html
new file mode 100644
index 0000000..4dbcf69
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/shared-storage-nfs-migration.html
@@ -0,0 +1,33 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.3. Shared storage example: NFS for a simple migration</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="chap-Virtualization_Administration_Guide-KVM_live_migration.html" title="Chapter 20. KVM live migration" /><link rel="prev" href="Live_migration_and_RHEL_compatibility.html" title="20.2. Live migration and Fedora version compatibility" /><link rel="next" href="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html" title="20.4. Live KVM migration with virsh" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="Live_migration_and_RHEL_compatibility.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html"><strong>Next</strong></a></li></ul><div class="section" id="shared-storage-nfs-migration"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.3. Shared storage example: NFS for a simple migration</h2></div></div></div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ This example uses NFS to share guest images with other KVM hosts. Although not practical for large installations, it is presented to demonstrate migration techniques only. Do not use this example for migrating or running more than a few guests.
+ </div><div class="para">
+ iSCSI storage is a better choice for large deployments. Refer to <a class="xref" href="chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html#sect-Virtualization-Storage_Pools-Creating-iSCSI">Section 27.1.5, “iSCSI-based storage pools”</a> for configuration details.
+ </div></div></div><div class="para">
+ Also note, that the instructions provided herin are not meant to replace the detailed instructions found in <em class="citetitle">Red Hat Linux Storage Administration Guide</em>. Refer to this guide for information on configuring NFS, opening IP tables, and configuring the firewall.
+ </div><div class="para">
+ Make sure that NFS filelocking is not used as it is not supported in KVM.
+ </div><div class="procedure"><ol class="1"><li class="step"><p class="title"><strong>Export your libvirt image directory</strong></p><div class="para">
+ Migration requires storage to reside on a system that is separate to the migration target systems. On this separate system, export the storage by adding 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>*.example.com</code></em>(rw,no_root_squash,sync)</pre><div class="para">
+ Change the hostname parameter as required for your environment.
+ </div></li><li class="step"><p class="title"><strong>Start NFS</strong></p><ol class="a"><li class="step"><div class="para">
+ Install the NFS packages if they are not yet installed:
+ </div><pre class="screen"># yum install nfs</pre></li><li class="step"><div class="para">
+ Make sure that the ports for NFS in <code class="command">iptables</code> (2049, for example) are opened and add NFS to the <code class="filename">/etc/hosts.allow</code> file.
+ </div></li><li class="step"><div class="para">
+ Start the NFS service:
+ </div><pre class="screen"># service nfs start</pre></li></ol></li><li class="step"><p class="title"><strong>Mount the shared storage on the destination</strong></p><div class="para">
+ On the migration destination system, mount the <code class="filename">/var/lib/libvirt/images</code> directory:
+ </div><pre class="screen"># mount <em class="parameter"><code>storage_host</code></em>:/var/lib/libvirt/images /var/lib/libvirt/images
+</pre><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Whichever directory is chosen for the guests must be exactly the same on host and guest. This applies to all types of shared storage. The directory must be the same or the migration with virt-manager will fail.
+ </div></div></div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="Live_migration_and_RHEL_compatibility.html"><strong>Prev</strong>20.2. Live migration and Fedora version compatibi...</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-KVM_live_migration-Live_KVM_migration_with_virsh.html"><strong>Next</strong>20.4. Live KVM migration with virsh</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-adv-filt-topics.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-adv-filt-topics.html
new file mode 100644
index 0000000..faf7072
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-adv-filt-topics.html
@@ -0,0 +1,24 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.11. Advanced Filter Configuration Topics</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-applying-network-filtering.html" title="H.10. Applying network filtering" /><link rel="prev" href="sub-sub-sect-igmp-esp-ah-udplite-over-ipv6.html" title="H.10.10.12. IGMP, ESP, AH, UDPLITE, 'ALL' over IPv6" /><link rel="next" href="sub-sub-sect-lim-numb-conns.html" title="H.10.11.2. Limiting Number of Connections" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 c
lass="previous"><a accesskey="p" href="sub-sub-sect-igmp-esp-ah-udplite-over-ipv6.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-lim-numb-conns.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-adv-filt-topics"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.10.11. Advanced Filter Configuration Topics</h3></div></div></div><div class="para">
+ The following sections discuss advanced filter configuration topics.
+ </div><div class="section" id="sub-sub-sect-conn-track"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.11.1. Connection tracking</h4></div></div></div><div class="para">
+ The network filtering subsystem (on Linux) makes use of the connection tracking support of IP tables. This helps in enforcing the directionality of network traffic (state match) as well as counting and limiting the number of simultaneous connections towards a guest. As an example, if a guest has TCP port 8080 open as a server, clients may connect to the guest on port 8080. Connection tracking and enforcement of directionality then prevents the guest from initiating a connection from (TCP client) port 8080 to the host back to a remote host. More importantly, tracking helps to prevent remote attackers from establishing a connection back to a guest. For example, if the user inside the guest established a connection to port 80 on an attacker site, then the attacker will not be able to initiate a connection from TCP port 80 back towards the guest. By default the connection state match that enables connection tracking and then enforcement of directionality of traffic is turne
d on.
+ </div><div class="example"><h6>Example H.9. XML example for turning off connections to the TCP port</h6><div class="example-contents"><div class="para">
+ The following shows an example XML fragement where this feature has been turned off for incoming connections to TCP port 12345.
+ </div><pre class="screen">
+ [...]
+ <rule direction='in' action='accept' statematch='false'>
+ <cp dstportstart='12345'/>
+ </rule>
+ [...]
+</pre><div class="para">
+ This now allows incoming traffic to TCP port 12345, but would also enable the initiation from (client) TCP port 12345 within the VM, which may or may not be desirable.
+ </div></div></div><br class="example-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-igmp-esp-ah-udplite-over-ipv6.html"><strong>Prev</strong>H.10.10.12. IGMP, ESP, AH, UDPLITE, 'ALL' over IP...</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="sub-sub-sect-lim-numb-conns.html"><strong>Next</strong>H.10.11.2. Limiting Number of Connections</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-auto-IP-add-detect-dhcp-snoop.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-auto-IP-add-detect-dhcp-snoop.html
new file mode 100644
index 0000000..efd3f11
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-auto-IP-add-detect-dhcp-snoop.html
@@ -0,0 +1,18 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.5. Automatic IP address detection and DHCP snooping</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-applying-network-filtering.html" title="H.10. Applying network filtering" /><link rel="prev" href="sub-sect-vars-in-filters.html" title="H.10.4. Usage of variables in filters" /><link rel="next" href="sub-sub-sect-DHCP-snooping.html" title="H.10.5.2. DHCP snooping" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sect-var
s-in-filters.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-DHCP-snooping.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-auto-IP-add-detect-dhcp-snoop"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.10.5. Automatic IP address detection and DHCP snooping</h3></div></div></div><div class="section" id="sub-sub-sect-intro-dhcp-snoop"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.5.1. Introduction</h4></div></div></div><div class="para">
+ The detection of IP addresses used on a virtual machine's interface is automatically activated if the variable IP is referenced but no value has been assigned to it. The variable <em class="parameter"><code>CTRL_IP_LEARNING</code></em> can be used to specify the IP address learning method to use. Valid values include: <em class="replaceable"><code>any</code></em>, <em class="replaceable"><code>dhcp</code></em>, or <em class="replaceable"><code>none</code></em>.
+ </div><div class="para">
+ The value <em class="replaceable"><code>any</code></em> instructs libvirt to use any packet to determine the address in use by a virtual machine, which is the default setting if the variable <em class="parameter"><code>TRL_IP_LEARNING</code></em> is not set. This method will only detect a single IP address per interface. Once a guest's IP address has been detected, its IP network traffic will be locked to that address, if for example, IP address spoofing is prevented by one of its filters. In that case, the user of the VM will not be able to change the IP address on the interface inside the guest, which would be considered IP address spoofing. When a guest is migrated to another host or resumed after a suspend operation, the first packet sent by the guest will again determine the IP address that the guest can use on a particular interface.
+ </div><div class="para">
+ The value of <em class="replaceable"><code>dhcp</code></em> instucts libvirt to only honor DHCP server-assigned addresses with valid leases. This method supports the detection and usage of multiple IP address per interface. When a guest resumes after a suspend operation, any valid IP address leases are applied to its filters. Otherwise the guest is expected to use DHCP to obtain a new IP addresses. When a guest migrates to another physical host, the guest is required to re-run the DHCP protocol.
+ </div><div class="para">
+ If CTRL_IP_LEARNING is set to <em class="replaceable"><code>none</code></em>, libvirt does not do IP address learning and referencing IP without assigning it an explicit value is an error.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-vars-in-filters.html"><strong>Prev</strong>H.10.4. Usage of variables in filters</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="sub-sub-sect-DHCP-snooping.html"><strong>Next</strong>H.10.5.2. DHCP snooping</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-blkresize.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-blkresize.html
new file mode 100644
index 0000000..076025b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-blkresize.html
@@ -0,0 +1,20 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.13.3. Using blockresize to change the size of a domain path</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-man-disk-image.html" title="E.13. Disk image management with live block copy" /><link rel="prev" href="sub-sect-blockpull.html" title="E.13.2. Using blockpull to shorten a backing chain" /><link rel="next" href="sect-guest-cpu-model-config.html" title="E.14. Guest CPU model configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 accesske
y="p" href="sub-sect-blockpull.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-guest-cpu-model-config.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-blkresize"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.13.3. Using blockresize to change the size of a domain path</h3></div></div></div><div class="para">
+ <code class="command">blockresize</code> can be used to re-size a block device of a domain while the domain is running, using the absolute path of the block device which also corresponds to a unique target name (<code class="command"><target dev="name"/></code>) or source file (<code class="command"><source file="name"/></code>). This can be applied to one of the disk devices attached to domain (you can use the command <code class="command">domblklist</code> to print a table showing the brief information of all block devices associated with a given domain).
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Live image re-sizing will always resize the image, but may not immediately be picked up by guests. With recent guest kernels, the size of virtio-blk devices is automatically updated (older kernels require a guest reboot). With SCSI devices, it is required to manually trigger a re-scan in the guest with the command, <code class="command">echo > /sys/class/scsi_device/0:0:0:0/device/rescan</code>. In addition, with IDE it is required to reboot the guest before it picks up the new size.
+ </div></div></div><div class="procedure"><ul><li class="step"><div class="para">
+ Run the following command: <code class="command">blockresize [domain] [path size]</code> where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Domain is the unique target name or source file of the domain whose size you want to change
+ </div></li><li class="listitem"><div class="para">
+ Path size is a scaled integer which defaults to KiB (blocks of 1024 bytes) if there is no suffix. You must use a suffix of "B" to for bytes.
+ </div></li></ul></div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-blockpull.html"><strong>Prev</strong>E.13.2. Using blockpull to shorten a backing chain</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-guest-cpu-model-config.html"><strong>Next</strong>E.14. Guest CPU model configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-blockpull.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-blockpull.html
new file mode 100644
index 0000000..90c02f1
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-blockpull.html
@@ -0,0 +1,58 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.13.2. Using blockpull to shorten a backing chain</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-man-disk-image.html" title="E.13. Disk image management with live block copy" /><link rel="prev" href="sect-man-disk-image.html" title="E.13. Disk image management with live block copy" /><link rel="next" href="sub-sect-blkresize.html" title="E.13.3. Using blockresize to change the size of a domain path" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="previ
ous"><a accesskey="p" href="sect-man-disk-image.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-blkresize.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-blockpull"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">E.13.2. Using blockpull to shorten a backing chain</h3></div></div></div><div class="para">
+ <code class="command">blockpull</code> can be used in in the following applications:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Flattens an image by populating it with data from its backing image chain. This makes the image file self-contained so that it no longer depends on backing images and looks like this:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Before: base.img ← Active
+ </div></li><li class="listitem"><div class="para">
+ After: base.img is no longer used by the guest and Active contains all of the data.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Flattens part of the backing image chain. This can be used to flatten snapshots into the top-level image and looks like this:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Before: base ← sn1 ←sn2 ← active
+ </div></li><li class="listitem"><div class="para">
+ After: base.img ← active. Note that active now contains all data from sn1 and sn2 and neither sn1 nor sn2 are used by the guest.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Moves the disk image to a new file system on the host. This is allows image files to be moved while the guest is running and looks like this:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Before (The original image file): <code class="filename">/fs1/base.vm.img</code>
+ </div></li><li class="listitem"><div class="para">
+ After: <code class="filename">/fs2/active.vm.qcow2</code> is now the new file system and <code class="filename">/fs1/base.vm.img</code> is no longer used.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ Useful in live migration with post-copy storage migration. The disk image is copied from the source host to the destination host after live migration completes.
+ </div><div class="para">
+ In short this is what happens: Before:<code class="filename">/source-host/base.vm.img</code> After:<code class="filename">/destination-host/active.vm.qcow2</code>.<code class="filename">/source-host/base.vm.img</code> is no longer used.
+ </div></li></ul></div><div class="procedure" id="virsh-blk-pull-pro"><h6>Procedure E.2. Using blockpull to shorten a backing chain</h6><ol class="1"><li class="step"><div class="para">
+ It may be helpful to run this command prior to running <code class="command">blockpull</code>:
+ </div><pre class="screen">#<code class="command"> virsh snapshot-create-as $dom $name -- disk-only</code></pre></li><li class="step"><div class="para">
+ If the chain looks like this: <code class="command">base ← snap1 ← snap2 ← active</code> run the following:
+ </div><pre class="screen">#<code class="command"> virsh blockpull $dom $disk snap1</code></pre><div class="para">
+ This command makes 'snap1' the backing file of active, by pulling data from snap2 into active resulting in: base ← snap1 ← active.
+ </div></li><li class="step"><div class="para">
+ Once the <code class="command">blockpull</code> is complete, the <span class="application"><strong>libvirt</strong></span> tracking of the snapshot that created the extra image in the chain is no longer useful. Delete the tracking on the outdated snapshot with this command:
+ </div><pre class="screen">#<code class="command"> virsh snapshot-delete $dom $name -- metadata</code></pre></li></ol></div><div class="para">
+ Additional applications of <code class="command">blockpull</code> can be done as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ To flatten a single image and populate it with data from its backing image chain:<code class="command"># virsh blockpull example-domain vda -- wait</code>
+ </div></li><li class="listitem"><div class="para">
+ To flatten part of the backing image chain:<code class="command"># virsh blockpull example-domain vda -- base /path/to/base.img -- wait</code>
+ </div></li><li class="listitem"><div class="para">
+ To move the disk image to a new file system on the host:<code class="command"># virsh snapshot-create example-domain -- xmlfile /path/to/new.xml -- disk-only</code> followed by <code class="command"># virsh blockpull example-domain vda -- wait</code>
+ </div></li><li class="listitem"><div class="para">
+ To use live migration with post-copy storage migration:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ On the destination run:
+ </div><pre class="screen"><code class="command"> # qemu-img create -f qcow2 -o backing_file=/source-host/vm.img /destination-host/vm.qcow2</code></pre></li><li class="listitem"><div class="para">
+ On the source run:
+ </div><pre class="screen"><code class="command"># virsh migrate example-domain</code></pre></li><li class="listitem"><div class="para">
+ On the destination run:
+ </div><pre class="screen"><code class="command"># virsh blockpull example-domain vda -- wait</code></pre></li></ul></div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-man-disk-image.html"><strong>Prev</strong>E.13. Disk image management with live block copy</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="sub-sect-blkresize.html"><strong>Next</strong>E.13.3. Using blockresize to change the size of a...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-element-oview.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-element-oview.html
new file mode 100644
index 0000000..56c7c4a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-element-oview.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.7. Element and attribute overview</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-applying-network-filtering.html" title="H.10. Applying network filtering" /><link rel="prev" href="sub-sect-vars-reserved.html" title="H.10.6. Reserved Variables" /><link rel="next" href="sub-sect-ref-filter.html" title="H.10.8. References to other filters" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sect-vars-reserv
ed.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-ref-filter.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-element-oview"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.10.7. Element and attribute overview</h3></div></div></div><div class="para">
+ The root element required for all network filters is named filter with two possible attributes. The name attribute provides a unique name of the given filter. The chain attribute is optional but allows certain filters to be better organized for more efficient processing by the firewall subsystem of the underlying host. Currently the system only supports the chains root, ipv4, ipv6, arp and rarp.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-vars-reserved.html"><strong>Prev</strong>H.10.6. Reserved Variables</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="sub-sect-ref-filter.html"><strong>Next</strong>H.10.8. References to other filters</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-filt-chain-props.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-filt-chain-props.html
new file mode 100644
index 0000000..aacef5d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-filt-chain-props.html
@@ -0,0 +1,48 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.3. Filtering chain priorities</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-applying-network-filtering.html" title="H.10. Applying network filtering" /><link rel="prev" href="sub-sect-filt-chain.html" title="H.10.2. Filtering chains" /><link rel="next" href="sub-sect-vars-in-filters.html" title="H.10.4. Usage of variables in filters" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sect-filt-chai
n.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-vars-in-filters.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-filt-chain-props"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.10.3. Filtering chain priorities</h3></div></div></div><div class="para">
+ As previously mentioned, when creating a filtering rule, all chains are connected to the root chain. The order in which those chains are accessed is influenced by the priority of the chain. The following table shows the chains that can be assigned a priority and their default priorities.
+ </div><div class="table" id="tab-filtering-chain-priorities"><h6>Table H.1. Filtering chain default priorities values</h6><div class="table-contents"><table summary="Filtering chain default priorities values" border="1"><colgroup><col class="1" width="50%" /><col class="2" width="50%" /></colgroup><thead><tr><th class="">
+ Chain (prefix)
+ </th><th class="">
+ Default priority
+ </th></tr></thead><tbody><tr><td class="">
+ stp
+ </td><td class="">
+ -810
+ </td></tr><tr><td class="">
+ mac
+ </td><td class="">
+ -800
+ </td></tr><tr><td class="">
+ vlan
+ </td><td class="">
+ -750
+ </td></tr><tr><td class="">
+ ipv4
+ </td><td class="">
+ -700
+ </td></tr><tr><td class="">
+ ipv6
+ </td><td class="">
+ -600
+ </td></tr><tr><td class="">
+ arp
+ </td><td class="">
+ -500
+ </td></tr><tr><td class="">
+ rarp
+ </td><td class="">
+ -400
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ A chain with a lower priority value is accessed before one with a higher value.
+ </div><div class="para">
+ The chains listed in <a class="xref" href="sub-sect-filt-chain-props.html#tab-filtering-chain-priorities">Table H.1, “Filtering chain default priorities values”</a> can be also be assigned custom priorities by writing a value in the range [-1000 to 1000] into the priority (XML) attribute in the filter node. <a class="xref" href="sub-sect-filt-chain.html">Section H.10.2, “Filtering chains”</a>filter shows the default priority of -500 for arp chains, for example.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-filt-chain.html"><strong>Prev</strong>H.10.2. Filtering chains</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="sub-sect-vars-in-filters.html"><strong>Next</strong>H.10.4. Usage of variables in filters</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-filt-chain.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-filt-chain.html
new file mode 100644
index 0000000..634087f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-filt-chain.html
@@ -0,0 +1,67 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.2. Filtering chains</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-applying-network-filtering.html" title="H.10. Applying network filtering" /><link rel="prev" href="sect-applying-network-filtering.html" title="H.10. Applying network filtering" /><link rel="next" href="sub-sect-filt-chain-props.html" title="H.10.3. Filtering chain priorities" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-applying-network-filtering.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-filt-chain-props.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-filt-chain"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.10.2. Filtering chains</h3></div></div></div><div class="para">
+ Filtering rules are organized in filter chains. These chains can be thought of as having a tree structure with packet filtering rules as entries in individual chains (branches).
+ </div><div class="para">
+ Packets start their filter evaluation in the root chain and can then continue their evaluation in other chains, return from those chains back into the root chain or be dropped or accepted by a filtering rule in one of the traversed chains.
+ </div><div class="para">
+ Libvirt's network filtering system automatically creates individual root chains for every virtual machine's network interface on which the user chooses to activate traffic filtering. The user may write filtering rules that are either directly instantiated in the root chain or may create protocol-specific filtering chains for efficient evaluation of protocol-specific rules.
+ </div><div class="para">
+ The following chains exist:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ root
+ </div></li><li class="listitem"><div class="para">
+ mac
+ </div></li><li class="listitem"><div class="para">
+ stp (spanning tree protocol)
+ </div></li><li class="listitem"><div class="para">
+ vlan
+ </div></li><li class="listitem"><div class="para">
+ arp and rarp
+ </div></li><li class="listitem"><div class="para">
+ ipv4
+ </div></li><li class="listitem"><div class="para">
+ ipv6
+ </div></li></ul></div><div class="para">
+ Multiple chains evaluating the mac, stp, vlan, arp, rarp, ipv4, or ipv6 protocol can be created using the protocol name only as a prefix in the chain's name.
+ </div><div class="example" id="arp-pro-example"><h6>Example H.3. ARP traffic filtering</h6><div class="example-contents"><div class="para">
+ This example allows chains with names arp-xyz or arp-test to be specified and have their ARP protocol packets evaluated in those chains.
+ </div><div class="para">
+ The following filter XML shows an example of filtering ARP traffic in the arp chain.
+ </div><pre class="screen">
+<filter name='no-arp-spoofing' chain='arp' priority='-500'>
+ <uuid>f88f1932-debf-4aa1-9fbe-f10d3aa4bc95</uuid>
+ <rule action='drop' direction='out' priority='300'>
+ <mac match='no' srcmacaddr='$MAC'/>
+ </rule>
+ <rule action='drop' direction='out' priority='350'>
+ <arp match='no' arpsrcmacaddr='$MAC'/>
+ </rule>
+ <rule action='drop' direction='out' priority='400'>
+ <arp match='no' arpsrcipaddr='$IP'/>
+ </rule>
+ <rule action='drop' direction='in' priority='450'>
+ <arp opcode='Reply'/>
+ <arp match='no' arpdstmacaddr='$MAC'/>
+ </rule>
+ <rule action='drop' direction='in' priority='500'>
+ <arp match='no' arpdstipaddr='$IP'/>
+ </rule>
+ <rule action='accept' direction='inout' priority='600'>
+ <arp opcode='Request'/>
+ </rule>
+ <rule action='accept' direction='inout' priority='650'>
+ <arp opcode='Reply'/>
+ </rule>
+ <rule action='drop' direction='inout' priority='1000'/>
+</filter>
+</pre><div class="para">
+ The consequence of putting ARP-specific rules in the arp chain, rather than for example in the root chain, is that packets protocols other than ARP do not need to be evaluated by ARP protocol-specific rules. This improves the efficiency of the traffic filtering. However, one must then pay attention to only putting filtering rules for the given protocol into the chain since other rules will not be evaluated. For example, an IPv4 rule will not be evaluated in the ARP chain since IPv4 protocol packets will not traverse the ARP chain.
+ </div></div></div><br class="example-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-applying-network-filtering.html"><strong>Prev</strong>H.10. Applying network filtering</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="sub-sect-filt-chain-props.html"><strong>Next</strong>H.10.3. Filtering chain priorities</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-filter-rules.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-filter-rules.html
new file mode 100644
index 0000000..ac08c45
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-filter-rules.html
@@ -0,0 +1,51 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.9. Filter rules</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-applying-network-filtering.html" title="H.10. Applying network filtering" /><link rel="prev" href="sub-sect-ref-filter.html" title="H.10.8. References to other filters" /><link rel="next" href="sub-sect-supp-pros.html" title="H.10.10. Supported protocols" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sect-ref-filter.ht
ml"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-supp-pros.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-filter-rules"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.10.9. Filter rules</h3></div></div></div><div class="para">
+ The following XML shows a simple example of a network traffic filter implementing a rule to drop traffic if the IP address (provided through the value of the variable IP) in an outgoing IP packet is not the expected one, thus preventing IP address spoofing by the VM.
+ </div><div class="example" id="filter-rules-example"><h6>Example H.8. Example of network traffic filtering</h6><div class="example-contents"><pre class="screen">
+<filter name='no-ip-spoofing' chain='ipv4'>
+ <uuid>fce8ae33-e69e-83bf-262e-30786c1f8072</uuid>
+ <rule action='drop' direction='out' priority='500'>
+ <ip match='no' srcipaddr='$IP'/>
+ </rule>
+</filter>
+</pre></div></div><br class="example-break" /><div class="para">
+ The traffic filtering rule starts with the rule node. This node may contain up to three of the following attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ action is mandatory can have the following values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ drop (matching the rule silently discards the packet with no further analysis)
+ </div></li><li class="listitem"><div class="para">
+ reject (matching the rule generates an ICMP reject message with no further analysis)
+ </div></li><li class="listitem"><div class="para">
+ accept (matching the rule accepts the packet with no further analysis)
+ </div></li><li class="listitem"><div class="para">
+ return (matching the rule passes this filter, but returns control to the calling filter for further analysis)
+ </div></li><li class="listitem"><div class="para">
+ continue (matching the rule goes on to the next rule for further analysis)
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ direction is mandatory can have the following values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ in for incomming traffic
+ </div></li><li class="listitem"><div class="para">
+ out for outgoing traffic
+ </div></li><li class="listitem"><div class="para">
+ inout for incoming and outgoing traffic
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ priority is optional. The priority of the rule controls the order in which the rule will be instantiated relative to other rules. Rules with lower values will be instantiated before rules with higher values. Valid values are in the range of -1000 to 1000. If this attribute is not provided, priority 500 will be assigned by default. Note that filtering rules in the root chain are sorted with filters connected to the root chain following their priorities. This allows to interleave filtering rules with access to filter chains. Refer to <a class="xref" href="sub-sect-filt-chain-props.html">Section H.10.3, “Filtering chain priorities”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ statematch is optional. Possible values are '0' or 'false' to turn the underlying connection state matching off. The default setting is 'true' or 1
+ </div></li></ul></div><div class="para">
+ For more information see <a class="xref" href="sub-sect-adv-filt-topics.html">Section H.10.11, “Advanced Filter Configuration Topics”</a>.
+ </div><div class="para">
+ The above example <a class="xref" href="sub-sect-ref-filter.html#exam-clean-traffic">Example H.7, “An Example of a clean traffic filter”</a> indicates that the traffic of <em class="replaceable"><code>type ip</code></em> will be associated with the chain <em class="replaceable"><code>ipv4</code></em> and the rule will have <code class="command">priority=<em class="replaceable"><code>500</code></em></code>. If for example another filter is referenced whose traffic of <em class="replaceable"><code>type ip</code></em> is also associated with the chain <em class="replaceable"><code>ipv4</code></em> then that filter's rules will be ordered relative to the <code class="command">priority=<em class="replaceable"><code>500</code></em></code> of the shown rule.
+ </div><div class="para">
+ A rule may contain a single rule for filtering of traffic. The above example shows that traffic of type ip is to be filtered.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-ref-filter.html"><strong>Prev</strong>H.10.8. References to other filters</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="sub-sect-supp-pros.html"><strong>Next</strong>H.10.10. Supported protocols</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-iso-mode.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-iso-mode.html
new file mode 100644
index 0000000..7ed4026
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-iso-mode.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.3.3. Isolated mode</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-network-protocols.html" title="H.3. Networking protocols" /><link rel="prev" href="sub-sect-routed-mode-libvirt.html" title="H.3.2. Routed mode" /><link rel="next" href="sect-the-Default_Configuration-libvirt.html" title="H.4. The default configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sect-routed-mode-lib
virt.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-the-Default_Configuration-libvirt.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-iso-mode"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.3.3. Isolated mode</h3></div></div></div><div class="para">
+ When using <span class="emphasis"><em>Isolated mode</em></span>, guests connected to the virtual switch can communicate with each other, and with the host, but their traffic will not pass outside of the host, nor can they receive traffic from outside the host. Using dnsmasq in this mode is required for basic functionality such as DHCP. However, even if this network is isolated from any physical network, DNS names are still resolved. Therefore a situation can arise when DNS names resolve but ICMP echo request (ping) commands fail.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-Other_routing_types-Isolated_mode"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-07-isolated-switch.png" width="444" alt="Virtual network switch in isolated mode" /></div></div><h6>Figure H.6. Virtual network switch in isolated mode</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-routed-mode-libvirt.html"><strong>Prev</strong>H.3.2. Routed mode</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-the-Default_Configuration-libvirt.html"><strong>Next</strong>H.4. The default configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-isolated-mode.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-isolated-mode.html
new file mode 100644
index 0000000..9731a09
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-isolated-mode.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.5.3. Isolated mode</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-Virtualization-Virtual_Networking-Example_scenarios.html" title="H.5. Examples of common scenarios" /><link rel="prev" href="sub-sect-nat-mode.html" title="H.5.2. NAT mode" /><link rel="next" href="sect-Virtualization-Virtual_Networking-Managing_a_virtual_network.html" title="H.6. Managing a virtual network" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="p
revious"><a accesskey="p" href="sub-sect-nat-mode.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-Virtual_Networking-Managing_a_virtual_network.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-isolated-mode"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.5.3. Isolated mode</h3></div></div></div><div class="para">
+ Isolated mode allows virtual machines to communicate with each other only. They are unable to interact with the physical network.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-nat-mode.html"><strong>Prev</strong>H.5.2. NAT mode</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-Virtual_Networking-Managing_a_virtual_network.html"><strong>Next</strong>H.6. Managing a virtual network</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-limitations-filters-network-subsystem.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-limitations-filters-network-subsystem.html
new file mode 100644
index 0000000..238c28c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-limitations-filters-network-subsystem.html
@@ -0,0 +1,18 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.12. Limitations</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-applying-network-filtering.html" title="H.10. Applying network filtering" /><link rel="prev" href="sub-sub-sect-samp-filter.html" title="H.10.11.6. Sample custom filter" /><link rel="next" href="appe-Virtualization-Additional_resources.html" title="Appendix I. Additional resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sub-sect-samp-filter.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="appe-Virtualization-Additional_resources.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-limitations-filters-network-subsystem"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.10.12. Limitations</h3></div></div></div><div class="para">
+ The following is a list of the currently known limitations of the network filtering subsystem.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ VM migration is only supported if the whole filter tree that is referenced by a guest's top level filter is also available on the target host. The network filter <code class="filename">clean-traffic</code> for example should be available on all libvirt installations and thus enable migration of guests that reference this filter. To assure version compatibility is not a problem make sure you are using the most current version of libvirt by updating the package regurally.
+ </div></li><li class="listitem"><div class="para">
+ Migration must occur between libvirt insallations of version 0.8.1 or later in order not to lose the network traffic filters associated with an interface.
+ </div></li><li class="listitem"><div class="para">
+ VLAN (802.1Q) packets, if sent by a guest, cannot be filtered with rules for protocol IDs arp, rarp, ipv4 and ipv6. They can only be filtered with protocol IDs, MAC and VLAN. Therefore, the example filter clean-traffic <a class="xref" href="sect-applying-network-filtering.html#ex-net-filtering">Example H.1, “An example of network filtering”</a> will not work as expected.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-samp-filter.html"><strong>Prev</strong>H.10.11.6. Sample custom filter</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-Additional_resources.html"><strong>Next</strong>Appendix I. Additional resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-nat-mode.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-nat-mode.html
new file mode 100644
index 0000000..43a6a88
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-nat-mode.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.5.2. NAT mode</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-Virtualization-Virtual_Networking-Example_scenarios.html" title="H.5. Examples of common scenarios" /><link rel="prev" href="sect-Virtualization-Virtual_Networking-Example_scenarios.html" title="H.5. Examples of common scenarios" /><link rel="next" href="sub-sect-isolated-mode.html" title="H.5.3. Isolated mode" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-Virtual_Networking-Example_scenarios.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-isolated-mode.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-nat-mode"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.5.2. NAT mode</h3></div></div></div><div class="para">
+ NAT (Network Address Translation) mode is the default mode. It can be used for testing when there is no need for direct network visibility.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Virtual_Networking-Example_scenarios.html"><strong>Prev</strong>H.5. Examples of common scenarios</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="sub-sect-isolated-mode.html"><strong>Next</strong>H.5.3. Isolated mode</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-op-sys-cont-boot.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-op-sys-cont-boot.html
new file mode 100644
index 0000000..0acdd93
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-op-sys-cont-boot.html
@@ -0,0 +1,25 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.2.4. Container boot</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-dom-xml-op-sys-boot.html" title="J.2. Operating system booting" /><link rel="prev" href="sub-sect-op-sys-dir-kern-boot.html" title="J.2.3. Direct kernel boot" /><link rel="next" href="sect-smbios-sys-info.html" title="J.3. SMBIOS system information" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sect-op-sys-dir-kern-boo
t.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-smbios-sys-info.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-op-sys-cont-boot"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.2.4. Container boot</h3></div></div></div><div class="para">
+ When booting a domain using container based virtualization, instead of a kernel or boot image, a path to the init binary is required, using the init element. By default this will be launched with no arguments. To specify the initial argv, use the <code class="sgmltag-element">initarg</code> element, repeated as many times as required. The <code class="sgmltag-element">cmdline</code> element, provides an equivalent to <code class="filename">/proc/cmdline</code> but will not effect <code class="sgmltag-starttag"><initarg></code>.
+ </div><div class="figure" id="fig-op-sys-cont-boot"><div class="figure-contents"><pre class="programlisting">
+>
+ ...
+ <span class="perl_Keyword"><os></span>
+ <span class="perl_Keyword"><type></span>hvm<span class="perl_Keyword"></type></span>
+ <span class="perl_Keyword"><loader></span>/usr/lib/xen/boot/hvmloader<span class="perl_Keyword"></loader></span>
+ <span class="perl_Keyword"><kernel></span>/root/f8-i386-vmlinuz<span class="perl_Keyword"></kernel></span>
+ <span class="perl_Keyword"><initrd></span>/root/f8-i386-initrd<span class="perl_Keyword"></initrd></span>
+ <span class="perl_Keyword"><cmdline></span>console=ttyS0 ks=http://example.com/f8-i386/os/<span class="perl_Keyword"></cmdline></span>
+ <span class="perl_Keyword"><dtb></span>/root/ppc.dtb<span class="perl_Keyword"></dtb></span>
+ <span class="perl_Keyword"></os></span>
+ ...
+
+</pre></div><h6>Figure J.5. Container boot</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-op-sys-dir-kern-boot.html"><strong>Prev</strong>J.2.3. Direct kernel 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-smbios-sys-info.html"><strong>Next</strong>J.3. SMBIOS system information</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-op-sys-dir-kern-boot.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-op-sys-dir-kern-boot.html
new file mode 100644
index 0000000..ddfc357
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-op-sys-dir-kern-boot.html
@@ -0,0 +1,51 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.2.3. Direct kernel boot</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-dom-xml-op-sys-boot.html" title="J.2. Operating system booting" /><link rel="prev" href="sub-sect-op-sys-host-boot.html" title="J.2.2. Host bootloader" /><link rel="next" href="sub-sect-op-sys-cont-boot.html" title="J.2.4. Container boot" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sect-op-sys-host-boot.html"><strong
>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-op-sys-cont-boot.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-op-sys-dir-kern-boot"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.2.3. Direct kernel boot</h3></div></div></div><div class="para">
+ When installing a new guest OS, it is often useful to boot directly from a kernel and initrd stored in the host OS, allowing command line arguments to be passed directly to the installer. This capability is usually available for both para and full virtualized guests.
+ </div><div class="figure" id="fig-op-sys-dir-kern-boot"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><os></span>
+ <span class="perl_Keyword"><type></span>hvm<span class="perl_Keyword"></type></span>
+ <span class="perl_Keyword"><loader></span>/usr/lib/xen/boot/hvmloader<span class="perl_Keyword"></loader></span>
+ <span class="perl_Keyword"><kernel></span>/root/f8-i386-vmlinuz<span class="perl_Keyword"></kernel></span>
+ <span class="perl_Keyword"><initrd></span>/root/f8-i386-initrd<span class="perl_Keyword"></initrd></span>
+ <span class="perl_Keyword"><cmdline></span>console=ttyS0 ks=http://example.com/f8-i386/os/<span class="perl_Keyword"></cmdline></span>
+ <span class="perl_Keyword"><dtb></span>/root/ppc.dtb<span class="perl_Keyword"></dtb></span>
+ <span class="perl_Keyword"></os></span>
+ ...
+
+</pre></div><h6>Figure J.4. Direct kernel boot</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-dir-kernelboot-os"><h6>Table J.4. Direct kernel boot elements</h6><div class="table-contents"><table summary="Direct kernel boot elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><type></code>
+ </td><td class="">
+ same as described in the BIOS boot section
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><loader></code>
+ </td><td class="">
+ same as described in the BIOS boot section
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><kernel></code>
+ </td><td class="">
+ secifies the fully-qualified path to the kernel image in the host OS
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><initrd></code>
+ </td><td class="">
+ specifies the fully-qualified path to the (optional) ramdisk image in the host OS.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><cmdline></code>
+ </td><td class="">
+ specifies arguments to be passed to the kernel (or installer) at boot time. This is often used to specify an alternate primary console (eg serial port), or the installation media source / kickstart file
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-op-sys-host-boot.html"><strong>Prev</strong>J.2.2. Host bootloader</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="sub-sect-op-sys-cont-boot.html"><strong>Next</strong>J.2.4. Container boot</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-op-sys-host-boot.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-op-sys-host-boot.html
new file mode 100644
index 0000000..5b3c6e0
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-op-sys-host-boot.html
@@ -0,0 +1,31 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.2.2. Host bootloader</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-dom-xml-op-sys-boot.html" title="J.2. Operating system booting" /><link rel="prev" href="sect-dom-xml-op-sys-boot.html" title="J.2. Operating system booting" /><link rel="next" href="sub-sect-op-sys-dir-kern-boot.html" title="J.2.3. Direct kernel boot" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-dom-xml-op-sys-boot.
html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-op-sys-dir-kern-boot.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-op-sys-host-boot"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.2.2. Host bootloader</h3></div></div></div><div class="para">
+ Hypervisors employing paravirtualization do not usually emulate a BIOS, but instead the host is responsible for the operating system boot. This may use a pseudo-bootloader in the host to provide an interface to choose a kernel for the guest. An example is pygrub with Xen.
+ </div><div class="figure" id="fig-op-sys-host-boot"><div class="figure-contents"><pre class="programlisting">
+ ...
+ <span class="perl_Keyword"><bootloader></span>/usr/bin/pygrub<span class="perl_Keyword"></bootloader></span>
+ <span class="perl_Keyword"><bootloader_args></span>--append single<span class="perl_Keyword"></bootloader_args></span>
+ ...
+</pre></div><h6>Figure J.3. Host bootloader domain XML</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-hostbootloader-os"><h6>Table J.3. BIOS bootloader elements</h6><div class="table-contents"><table summary="BIOS bootloader elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-starttag"><bootloader></code>
+ </td><td class="">
+ provides a fully qualified path to the bootloader executable in the host OS. This bootloader will choose which kernel to boot. The required output of the bootloader is dependent on the hypervisor in use.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-starttag"><bootloader_args></code>
+ </td><td class="">
+ allows command line arguments to be passed to the bootloader (optional command)
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-dom-xml-op-sys-boot.html"><strong>Prev</strong>J.2. Operating system booting</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="sub-sect-op-sys-dir-kern-boot.html"><strong>Next</strong>J.2.3. Direct kernel boot</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-ref-filter.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-ref-filter.html
new file mode 100644
index 0000000..42a6723
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-ref-filter.html
@@ -0,0 +1,28 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.8. References to other filters</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-applying-network-filtering.html" title="H.10. Applying network filtering" /><link rel="prev" href="sub-sect-element-oview.html" title="H.10.7. Element and attribute overview" /><link rel="next" href="sub-sect-filter-rules.html" title="H.10.9. Filter rules" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sect-element-ovie
w.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-filter-rules.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-ref-filter"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.10.8. References to other filters</h3></div></div></div><div class="para">
+ Any filter may hold references to other filters. Individual filters may be referenced multiple times in a filter tree but references between filters must not introduce loops.
+ </div><div class="example" id="exam-clean-traffic"><h6>Example H.7. An Example of a clean traffic filter</h6><div class="example-contents"><div class="para">
+ The following shows the XML of the clean-traffic network filter referencing several other filters.
+ </div><pre class="screen">
+<filter name='clean-traffic'>
+ <uuid>6ef53069-ba34-94a0-d33d-17751b9b8cb1</uuid>
+ <filterref filter='no-mac-spoofing'/>
+ <filterref filter='no-ip-spoofing'/>
+ <filterref filter='allow-incoming-ipv4'/>
+ <filterref filter='no-arp-spoofing'/>
+ <filterref filter='no-other-l2-traffic'/>
+ <filterref filter='qemu-announce-self'/>
+</filter>
+</pre><div class="para">
+ To reference another filter, the XML node filterref needs to be provided inside a filter node. This node must have the attribute filter whose value contains the name of the filter to be referenced.
+ </div></div></div><br class="example-break" /><div class="para">
+ New network filters can be defined at any time and may contain references to network filters that are not known to libvirt, yet. However, once a virtual machine is started or a network interface referencing a filter is to be hotplugged, all network filters in the filter tree must be available. Otherwise the virtual machine will not start or the network interface cannot be attached.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-element-oview.html"><strong>Prev</strong>H.10.7. Element and attribute 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="sub-sect-filter-rules.html"><strong>Next</strong>H.10.9. Filter rules</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-routed-mode-libvirt.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-routed-mode-libvirt.html
new file mode 100644
index 0000000..1435b34
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-routed-mode-libvirt.html
@@ -0,0 +1,12 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.3.2. Routed mode</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-network-protocols.html" title="H.3. Networking protocols" /><link rel="prev" href="sect-network-protocols.html" title="H.3. Networking protocols" /><link rel="next" href="sub-sect-iso-mode.html" title="H.3.3. Isolated mode" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-network-protocols.html"><strong>Prev</strong></a>
</li><li class="next"><a accesskey="n" href="sub-sect-iso-mode.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-routed-mode-libvirt"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.3.2. Routed mode</h3></div></div></div><div class="para">
+ When using <span class="emphasis"><em>routed mode</em></span>, the virtual switch connects to the physical LAN connected to the host, passing traffic back and forth without the use of NAT. The virtual switch can examine all traffic and use the information contained within the network packets to make routing decisions. When using this mode, all of the virtual machines are in their own subnet, routed through a virtual switch. This situation is not always ideal as no other hosts on the physical network are aware of the virtual machines without manual physical router configuration, and cannot access the virtual machines. Routed mode operates at Layer 3 of the OSI networking model.
+ </div><div class="figure" id="figu-Virtualization_Administration_Guide-Virtual_Networking-Managing_a_virtual_network-Virtual_network_switches-Other_routing_types-Routed_mode"><div class="figure-contents"><div class="mediaobject"><img src="images/vn-06-routed-switch.png" width="444" alt="Virtual network switch in routed mode" /></div></div><h6>Figure H.5. Virtual network switch in routed mode</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-network-protocols.html"><strong>Prev</strong>H.3. Networking protocols</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="sub-sect-iso-mode.html"><strong>Next</strong>H.3.3. Isolated mode</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-supp-pros.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-supp-pros.html
new file mode 100644
index 0000000..5750e46
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-supp-pros.html
@@ -0,0 +1,97 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.10. Supported protocols</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-applying-network-filtering.html" title="H.10. Applying network filtering" /><link rel="prev" href="sub-sect-filter-rules.html" title="H.10.9. Filter rules" /><link rel="next" href="sub-sub-sect-vlan.html" title="H.10.10.2. VLAN (802.1Q)" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sect-filter-rules.html"><strong>Prev
</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-vlan.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-supp-pros"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.10.10. Supported protocols</h3></div></div></div><div class="para">
+ The following sections list and give some details about the protocols that are supported by the network filtering subsystem. This type of traffic rule is provided in the rule node as a nested node. Depending on the traffic type a rule is filtering, the attributes are different. The above example showed the single attribute <em class="parameter"><code>srcipaddr</code></em> that is valid inside the ip traffic filtering node. The following sections show what attributes are valid and what type of data they are expecting. The following datatypes are available:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ UINT8 : 8 bit integer; range 0-255
+ </div></li><li class="listitem"><div class="para">
+ UINT16: 16 bit integer; range 0-65535
+ </div></li><li class="listitem"><div class="para">
+ MAC_ADDR: MAC address in dotted decimal format, i.e., 00:11:22:33:44:55
+ </div></li><li class="listitem"><div class="para">
+ MAC_MASK: MAC address mask in MAC address format, i.e., FF:FF:FF:FC:00:00
+ </div></li><li class="listitem"><div class="para">
+ IP_ADDR: IP address in dotted decimal format, i.e., 10.1.2.3
+ </div></li><li class="listitem"><div class="para">
+ IP_MASK: IP address mask in either dotted decimal format (255.255.248.0) or CIDR mask (0-32)
+ </div></li><li class="listitem"><div class="para">
+ IPV6_ADDR: IPv6 address in numbers format, i.e., FFFF::1
+ </div></li><li class="listitem"><div class="para">
+ IPV6_MASK: IPv6 mask in numbers format (FFFF:FFFF:FC00::) or CIDR mask (0-128)
+ </div></li><li class="listitem"><div class="para">
+ STRING: A string
+ </div></li><li class="listitem"><div class="para">
+ BOOLEAN: 'true', 'yes', '1' or 'false', 'no', '0'
+ </div></li><li class="listitem"><div class="para">
+ IPSETFLAGS: The source and destination flags of the ipset described by up to 6 'src' or 'dst' elements selecting features from either the source or destination part of the packet header; example: src,src,dst. The number of 'selectors' to provide here depends on the type of ipset that is referenced
+ </div></li></ul></div><div class="para">
+ Every attribute except for those of type <em class="parameter"><code>IP_MASK</code></em> or <em class="parameter"><code>IPV6_MASK</code></em> can be negated using the match attribute with value <em class="replaceable"><code>no</code></em>. Multiple negated attributes may be grouped together. The following XML fragment shows such an example using abstract attributes.
+ </div><pre class="screen">
+[...]
+ <rule action='drop' direction='in'>
+ <protocol match='no' attribute1='value1' attribute2='value2'/>
+ <protocol attribute3='value3'/>
+ </rule>
+[...]
+</pre><div class="para">
+ Rules behave evaluate the rule as well as look at it logically within the boundaries of the given protocol attributes. Thus, if a single attribute's value does not match the one given in the rule, the whole rule will be skipped during the evaluation process. Therefore, in the above example incoming traffic will only be dropped if: the protocol property <em class="parameter"><code>attribute1</code></em> does not match both <em class="parameter"><code>value1</code></em> and the protocol property <em class="parameter"><code>attribute2</code></em> does not match <em class="parameter"><code>value2</code></em> and the protocol property <em class="parameter"><code>attribute3</code></em> matches <em class="parameter"><code>value3</code></em>.
+ </div><div class="section" id="sub-sub-sect-mac-filter-rules"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.10.1. MAC (Ethernet)</h4></div></div></div><div class="para">
+ Protocol ID: mac
+ </div><div class="para">
+ Rules of this type should go into the root chain.
+ </div><div class="table" id="table-mac-vars"><h6>Table H.3. MAC protocol types</h6><div class="table-contents"><table summary="MAC protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of destination
+ </td></tr><tr><td class="">
+ protocolid
+ </td><td class="">
+ UINT16 (0x600-0xffff), STRING
+ </td><td class="">
+ Layer 3 protocol ID. Valid strings include [arp, rarp, ipv4, ipv6]
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The filter can be written as such:
+ </div><pre class="screen">
+[...]
+<mac match='no' srcmacaddr='$MAC'/>
+[...]
+</pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-filter-rules.html"><strong>Prev</strong>H.10.9. Filter rules</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="sub-sub-sect-vlan.html"><strong>Next</strong>H.10.10.2. VLAN (802.1Q)</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-vars-in-filters.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-vars-in-filters.html
new file mode 100644
index 0000000..1f58abb
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-vars-in-filters.html
@@ -0,0 +1,72 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.4. Usage of variables in filters</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-applying-network-filtering.html" title="H.10. Applying network filtering" /><link rel="prev" href="sub-sect-filt-chain-props.html" title="H.10.3. Filtering chain priorities" /><link rel="next" href="sub-sect-auto-IP-add-detect-dhcp-snoop.html" title="H.10.5. Automatic IP address detection and DHCP snooping" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="pr
evious"><a accesskey="p" href="sub-sect-filt-chain-props.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-auto-IP-add-detect-dhcp-snoop.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-vars-in-filters"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.10.4. Usage of variables in filters</h3></div></div></div><div class="para">
+ There are two variables that have been reserved for usage by the network traffic filtering subsystem: MAC and IP.
+ </div><div class="para">
+ <em class="parameter"><code>MAC</code></em> is designated for the MAC address of the network interface. A filtering rule that references this variable will automatically be replaced with the MAC address of the interface. This works without the user having to explicitly provide the MAC parameter. Even though it is possible to specify the MAC parameter similar to the IP parameter above, it is discouraged since libvirt knows what MAC address an interface will be using.
+ </div><div class="para">
+ The parameter <em class="parameter"><code>IP</code></em> represents the IP address that the operating system inside the virtual machine is expected to use on the given interface. The IP parameter is special in so far as the libvirt daemon will try to determine the IP address (and thus the IP parameter's value) that is being used on an interface if the parameter is not explicitly provided but referenced. For current limitations on IP address detection, consult the section on limitations <a class="xref" href="sub-sect-limitations-filters-network-subsystem.html">Section H.10.12, “Limitations”</a> on how to use this feature and what to expect when using it. The XML file shown in <a class="xref" href="sub-sect-filt-chain.html">Section H.10.2, “Filtering chains”</a> contains the filter <em class="parameter"><code>no-arp-spoofing</code></em>, which is an example of using a network filter XML to reference the MAC and IP variables.
+ </div><div class="para">
+ Note that referenced variables are always prefixed with the character <em class="parameter"><code>$</code></em>. The format of the value of a variable must be of the type expected by the filter attribute identified in the XML. In the above example, the <em class="parameter"><code>IP</code></em> parameter must hold a legal IP address in standard format. Failure to provide the correct structure will result in the filter variable not being replaced with a value and will prevent a virtual machine from starting or will prevent an interface from attaching when hotplugging is being used. Some of the types that are expected for each XML attribute are shown in the example <a class="xref" href="sub-sect-vars-in-filters.html#example-vars-xml-iptraffic-filter">Example H.4, “Sample variable types”</a>.
+ </div><div class="example" id="example-vars-xml-iptraffic-filter"><h6>Example H.4. Sample variable types</h6><div class="example-contents"><div class="para">
+ As variables can contain lists of elements, (the variable IP can contain multiple IP addresses that are valid on a particular interface, for example), the notation for providing multiple elements for the IP variable is:
+ </div><pre class="screen">
+ <devices>
+ <interface type='bridge'>
+ <mac address='00:16:3e:5d:c7:9e'/>
+ <filterref filter='clean-traffic'>
+ <parameter name='IP' value='10.0.0.1'/>
+ <parameter name='IP' value='10.0.0.2'/>
+ <parameter name='IP' value='10.0.0.3'/>
+ </filterref>
+ </interface>
+ </devices>
+</pre><div class="para">
+ This XML file creates filters to enable multiple IP addresses per interface. Each of the IP addresses will result in a seperate filtering rule. Therefore using the XML above and the the following rule, three individual filtering rules (one for each IP address) will be created:
+ </div><pre class="screen">
+ <rule action='accept' direction='in' priority='500'>
+ <tcp srpipaddr='$IP'/>
+ </rule>
+</pre><div class="para">
+ As it is possible to access individual elements of a variable holding a list of elements, a filtering rule like the following accesses the 2nd element of the variable <em class="replaceable"><code>DSTPORTS</code></em>.
+ </div><pre class="screen">
+ <rule action='accept' direction='in' priority='500'>
+ <udp dstportstart='$DSTPORTS[1]'/>
+ </rule>
+</pre></div></div><br class="example-break" /><div class="example" id="exam-fil-rules-combo"><h6>Example H.5. Using a variety of variables</h6><div class="example-contents"><div class="para">
+ As it is possible to create filtering rules that represent all possible combinations of rules from different lists using the notation <code class="command">$VARIABLE[@<iterator id="x">]</code>. The following rule allows a virtual machine to receive traffic on a set of ports, which are specified in <em class="replaceable"><code>DSTPORTS</code></em>, from the set of source IP address specified in <em class="replaceable"><code>SRCIPADDRESSES</code></em>. The rule generates all combinations of elements of the variable <em class="replaceable"><code>DSTPORTS</code></em> with those of <em class="replaceable"><code>SRCIPADDRESSES</code></em> by using two independent iterators to access their elements.
+ </div><pre class="screen">
+ <rule action='accept' direction='in' priority='500'>
+ <ip srcipaddr='$SRCIPADDRESSES[@1]' dstportstart='$DSTPORTS[@2]'/>
+ </rule>
+</pre><div class="para">
+ Assign concrete values to <em class="replaceable"><code>SRCIPADDRESSES</code></em> and <em class="replaceable"><code>DSTPORTS</code></em> as shown:
+ </div><pre class="screen">
+ SRCIPADDRESSES = [ 10.0.0.1, 11.1.2.3 ]
+ DSTPORTS = [ 80, 8080 ]
+</pre><div class="para">
+ Assigning values to the variables using <code class="command">$SRCIPADDRESSES[@1]</code> and <code class="command">$DSTPORTS[@2]</code> would then result in all combinations of addresses and ports being created as shown:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ 10.0.0.1, 80
+ </div></li><li class="listitem"><div class="para">
+ 10.0.0.1, 8080
+ </div></li><li class="listitem"><div class="para">
+ 11.1.2.3, 80
+ </div></li><li class="listitem"><div class="para">
+ 11.1.2.3, 8080
+ </div></li></ul></div><div class="para">
+ Accessing the same variables using a single iterator, for example by using the notation <code class="command">$SRCIPADDRESSES[@1]</code> and <code class="command">$DSTPORTS[@1]</code>, would result in parallel access to both lists and result in the following combinations:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ 10.0.0.1, 80
+ </div></li><li class="listitem"><div class="para">
+ 11.1.2.3, 8080
+ </div></li></ul></div></div></div><br class="example-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ <code class="command">$VARIABLE</code> is short-hand for <code class="command">$VARIABLE[@0]</code>. The former notation always assumes the role of iterator with <code class="command">iterator id="0"</code> added as shown in the opening paragraph at the top of this section.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-filt-chain-props.html"><strong>Prev</strong>H.10.3. Filtering chain priorities</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="sub-sect-auto-IP-add-detect-dhcp-snoop.html"><strong>Next</strong>H.10.5. Automatic IP address detection and DHCP s...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-vars-reserved.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-vars-reserved.html
new file mode 100644
index 0000000..95c7c16
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sect-vars-reserved.html
@@ -0,0 +1,40 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.6. Reserved Variables</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-applying-network-filtering.html" title="H.10. Applying network filtering" /><link rel="prev" href="sub-sub-sect-DHCP-snooping.html" title="H.10.5.2. DHCP snooping" /><link rel="next" href="sub-sect-element-oview.html" title="H.10.7. Element and attribute overview" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sub-sect-
DHCP-snooping.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-element-oview.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sect-vars-reserved"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">H.10.6. Reserved Variables</h3></div></div></div><div class="para">
+ <a class="xref" href="sub-sect-vars-reserved.html#table-res-vars">Table H.2, “Reserved variables”</a> shows the variables that are considered reserved and are used by libvirt:
+ </div><div class="table" id="table-res-vars"><h6>Table H.2. Reserved variables</h6><div class="table-contents"><table summary="Reserved variables" border="1"><colgroup><col class="1" width="50%" /><col class="2" width="50%" /></colgroup><thead><tr><th class="">
+ Variable Name
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ MAC
+ </td><td class="">
+ The MAC address of the interface
+ </td></tr><tr><td class="">
+ IP
+ </td><td class="">
+ The list of IP addresses in use by an interface
+ </td></tr><tr><td class="">
+ IPV6
+ </td><td class="">
+ Not currently implemented: the list of IPV6 addresses in use by an interface
+ </td></tr><tr><td class="">
+ DHCPSERVER
+ </td><td class="">
+ The list of IP addresses of trusted DHCP servers
+ </td></tr><tr><td class="">
+ DHCPSERVERV6
+ </td><td class="">
+ Not currently implemented: The list of IPv6 addresses of trusted DHCP servers
+ </td></tr><tr><td class="">
+ CTRL_IP_LEARNING
+ </td><td class="">
+ The choice of the IP address detection mode
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-DHCP-snooping.html"><strong>Prev</strong>H.10.5.2. DHCP snooping</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="sub-sect-element-oview.html"><strong>Next</strong>H.10.7. Element and attribute overview</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-Network-interfaces.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-Network-interfaces.html
new file mode 100644
index 0000000..4fb2a98
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-Network-interfaces.html
@@ -0,0 +1,56 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9. Network interfaces</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-smartcard.html" title="J.16.8. Smartcard devices" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-bridge-to-lan.html" title="J.16.9.2. Bridge to LAN" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-section-libvirt-dom-xml-devices-smartcard.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-bridge-to-lan.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-Network-interfaces"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.9. Network interfaces</h3></div></div></div><div class="para">
+ The network interface devices are modified using managment tools that will configure the following part of the Domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'bridge'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> bridge=</span><span class="perl_String">'xenbr0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">'00:16:3e:5d:c7:9e'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><script</span><span class="perl_Others"> path=</span><span class="perl_String">'vif-bridge'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><rom</span><span class="perl_Others"> bar=</span><span class="perl_String">'off'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.36. Devices - network interfaces</h6></div><br class="figure-break" /><div class="para">
+ There are several possibilities for specifying a network interface visible to the guest. Each subsection below provides more details about common setup options. Additionally, each <code class="sgmltag-starttag"><interface></code> element has an optional <code class="sgmltag-starttag"><address></code> sub-element that can tie the interface to a particular pci slot, with attribute <code class="sgmltag-attribute">type='pci'</code> (Refer to <a class="xref" href="sub-section-libvirt-dom-xml-devices-device-addresses.html">Section J.16.3, “Device addresses”</a>).
+ </div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-virtual-network"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.1. Virtual networks</h4></div></div></div><div class="para">
+ This is the recommended configuration for general guest connectivity on hosts with dynamic / wireless networking configurations (or multi-host environments where the host hardware details are described separately in a <code class="sgmltag-starttag"><network></code> definition). In addition, it provides a connection whose details are described by the named network definition. Depending on the virtual network's <code class="sgmltag-attribute">forward mode</code> configuration, the network may be totally isolated (no <code class="sgmltag-starttag"><forward></code> element given), NAT'ing to an explicit network device or to the default route (<code class="sgmltag-attribute">forward mode='nat'</code>), routed with no NAT (<code class="sgmltag-attribute">forward mode='route'/</code>), or connected directly to one of the host's network interfaces (via macvtap) or bridge devices (<code class="sgmltag-attribute">forward mode='bridge|private|vepa|passthrough'/</code>)
+ </div><div class="para">
+ For networks with a forward mode of bridge, private, vepa, and passthrough, it is assumed that the host has any necessary DNS and DHCP services already setup outside the scope of libvirt. In the case of isolated, nat, and routed networks, DHCP and DNS are provided on the virtual network by libvirt, and the IP range can be determined by examining the virtual network config with <code class="command">virsh net-dumpxml [networkname]</code>. There is one virtual network called 'default' setup out of the box which does NAT'ing to the default route and has an IP range of 192.168.122.0/255.255.255.0. Each guest will have an associated tun device created with a name of vnetN, which can also be overridden with the <code class="sgmltag-starttag"><target></code> element (refer to <a class="xref" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element.html">Section J.16.9.10, “Overriding the target element”</a>).
+ </div><div class="para">
+ When the source of an interface is a network, a portgroup can be specified along with the name of the network; one network may have multiple portgroups defined, with each portgroup containing slightly different configuration information for different classes of network connections. Also, similar to <code class="sgmltag-starttag"><direct></code> network connections (described below), a connection of type <code class="sgmltag-attribute">network</code> may specify a <code class="sgmltag-starttag"><virtualport></code> element, with configuration data to be forwarded to a vepa (802.1Qbg) or 802.1Qbh compliant switch, or to an Open vSwitch virtual switch.
+ </div><div class="para">
+ Since the actual type of switch may vary depending on the configuration in the <code class="sgmltag-starttag"><network></code> on the host, it is acceptable to omit the virtualport type attribute, and specify attributes from multiple different virtualport types (and also to leave out certain attributes); at domain startup time, a complete <code class="sgmltag-starttag"><virtualport></code> element will be constructed by merging together the type and attributes defined in the network and the portgroup referenced by the interface. The newly-constructed virtualport is a combination of both. The attributes from lower virtualport can't make changes on the ones defined in higher virtualport. Interfaces take the highest priority, portgroup is lowest priority.
+ </div><div class="para">
+ For example, in order to work properly with both an 802.1Qbh switch and an Open vSwitch switch, you may choose to specify no type, but both an <code class="sgmltag-attribute">profileid</code> (in case the switch is 802.1Qbh) and an <code class="sgmltag-attribute">interfaceid</code> (in case the switch is Open vSwitch) (you may also omit the other attributes, such as <code class="sgmltag-attribute">managerid</code>, <code class="sgmltag-attribute">typeid</code>, or <code class="sgmltag-attribute">profileid</code>, to be filled in from the network's <code class="sgmltag-attribute">virtualport</code>). If you want to limit a guest to connecting only to certain types of switches, you can specify the virtualport type, but still omit some/all of the parameters - in this case if the host's network has a different type of virtualport, connection of the interface will fail. The virtual network parameters are defined using management tools that modify the following part of the do
main XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-virt-net"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Others"> portgroup=</span><span class="perl_String">'engineering'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet7'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">"00:11:22:33:44:55"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><virtualport></span>
+ <span class="perl_Keyword"><parameters</span><span class="perl_Others"> instanceid=</span><span class="perl_String">'09b11c53-8b5c-4eeb-8f00-d84eaa0aaa4f'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></virtualport></span>
+
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.37. Devices - network interfaces- virtual networks</h6></div><br class="figure-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-smartcard.html"><strong>Prev</strong>J.16.8. Smartcard 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="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-bridge-to-lan.html"><strong>Next</strong>J.16.9.2. Bridge to LAN</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-channel.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-channel.html
new file mode 100644
index 0000000..bc886a9
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-channel.html
@@ -0,0 +1,42 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.16. Channel</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-guest-interface.html" title="J.16.15. Guest interfaces" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-host-interface.html" title="J.16.17. Host interface" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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" h
ref="sub-section-libvirt-dom-xml-devices-guest-interface.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-host-interface.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-channel"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.16. Channel</h3></div></div></div><div class="para">
+ This represents a private communication channel between the host and the guest and is manipulated by making changes to your guest virtual machine using a management tool that results in changes made to the following section of the domain xml
+ </div><div class="figure" id="fig-dom-xml-devices-channel"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> type=</span><span class="perl_String">'unix'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'bind'</span><span class="perl_Others"> path=</span><span class="perl_String">'/tmp/guestfwd'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'guestfwd'</span><span class="perl_Others"> address=</span><span class="perl_String">'10.0.2.1'</span><span class="perl_Others"> port=</span><span class="perl_String">'4600'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></channel></span>
+
+ <span class="perl_Comment"><!-- KVM virtio channel --></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio'</span><span class="perl_Others"> name=</span><span class="perl_String">'arbitrary.virtio.serial.port.name'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></channel></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> type=</span><span class="perl_String">'unix'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'bind'</span><span class="perl_Others"> path=</span><span class="perl_String">'/var/lib/libvirt/qemu/f16x86_64.agent'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio'</span><span class="perl_Others"> name=</span><span class="perl_String">'org.qemu.guest_agent.0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></channel></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> type=</span><span class="perl_String">'spicevmc'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio'</span><span class="perl_Others"> name=</span><span class="perl_String">'com.redhat.spice.0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></channel></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.63. Channel</h6></div><br class="figure-break" /><div class="para">
+ This can be implemented in a variety of ways. The specific type of <code class="sgmltag-starttag"><channel></code> is given in the <code class="sgmltag-attribute">type</code> attribute of the <code class="sgmltag-starttag"><target></code> element. Different channel types have different target attributes as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">guestfwd</code> - Dictates that TCP traffic sent by the guest to a given IP address and port is forwarded to the channel device on the host. The <code class="sgmltag-element">target</code> element must have address and port attributes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">virtio</code> - Paravirtualized virtio channel. <code class="sgmltag-starttag"><channel></code> is exposed in the guest under <code class="filename">/dev/vport*</code>, and if the optional element <code class="sgmltag-attribute">name</code>is specified, <code class="filename">/dev/virtio-ports/$name</code> (for more info, please see http://fedoraproject.org/wiki/Features/VirtioSerial). The optional element <code class="sgmltag-attribute">address</code> can tie the channel to a particular <code class="sgmltag-attribute">type='virtio-serial'</code> controller, documented above. With QEMU, if name is "org.qemu.guest_agent.0", then libvirt can interact with a guest agent installed in the guest, for actions such as guest shutdown or file system quiescing.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">spicevmc</code> - Paravirtualized SPICE channel. The domain must also have a SPICE server as a graphics device, at which point the host piggy-backs messages across the main channel. The <code class="sgmltag-element">target</code> element must be present, with attribute <code class="sgmltag-attribute">type='virtio';</code> an optional attribute <code class="sgmltag-attribute">name</code> controls how the guest will have access to the channel, and defaults to <code class="sgmltag-attribute">name='com.redhat.spice.0'</code>. The optional <code class="sgmltag-starttag"><address></code> element can tie the channel to a particular <code class="sgmltag-attribute">type='virtio-serial'</code> controller.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-guest-interface.html"><strong>Prev</strong>J.16.15. Guest interfaces</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="sub-section-libvirt-dom-xml-devices-host-interface.html"><strong>Next</strong>J.16.17. Host interface</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-consoles.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-consoles.html
new file mode 100644
index 0000000..f94cd8e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-consoles.html
@@ -0,0 +1,38 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.14. Consoles, serial, parallel, and channel devices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-video.html" title="J.16.13. Video devices" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-guest-interface.html" title="J.16.15. Guest interfaces" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-s
ection-libvirt-dom-xml-devices-video.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-guest-interface.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-consoles"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.14. Consoles, serial, parallel, and channel devices</h3></div></div></div><div class="para">
+ A character device provides a way to interact with the virtual machine. Paravirtualized consoles, serial ports, parallel ports and channels are all classed as character devices and so represented using the same syntax.
+ </div><div class="para">
+ To specify the consols, channel and other devices configuration settings, use a mangement tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-dom-xml-devices-consoles"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><parallel</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/2'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></parallel></span>
+ <span class="perl_Keyword"><serial</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/3'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></serial></span>
+ <span class="perl_Keyword"><console</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/4'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></console></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> type=</span><span class="perl_String">'unix'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'bind'</span><span class="perl_Others"> path=</span><span class="perl_String">'/tmp/guestfwd'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'guestfwd'</span><span class="perl_Others"> address=</span><span class="perl_String">'10.0.2.1'</span><span class="perl_Others"> port=</span><span class="perl_String">'4600'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></channel></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.59. Consoles, serial, parallel, and channel devices</h6></div><br class="figure-break" /><div class="para">
+ In each of these directives, the top-level element name (parallel, serial, console, channel) describes how the device is presented to the guest. The guest interface is configured by the target element. The interface presented to the host is given in the type attribute of the top-level element. The host interface is configured by the source element. The source element may contain an optional seclabel to override the way that labelling is done on the socket path. If this element is not present, the security label is inherited from the per-domain setting. Each character device element has an optional sub-element <code class="sgmltag-element">address</code> which can tie the device to a particular controller or PCI slot.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-video.html"><strong>Prev</strong>J.16.13. Video 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="sub-section-libvirt-dom-xml-devices-guest-interface.html"><strong>Next</strong>J.16.15. Guest interfaces</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-controllers.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-controllers.html
new file mode 100644
index 0000000..4fec7e6
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-controllers.html
@@ -0,0 +1,44 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.4. Controllers</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-device-addresses.html" title="J.16.3. Device addresses" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-device-leases.html" title="J.16.5. Device leases" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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
="sub-section-libvirt-dom-xml-devices-device-addresses.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-device-leases.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-controllers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.4. Controllers</h3></div></div></div><div class="para">
+ Depending on the guest architecture, some device busses can appear more than once, with a group of virtual devices tied to a virtual controller. Normally, libvirt can automatically infer such controllers without requiring explicit XML markup, but sometimes it is necessary to provide an explicit controller element.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-controllers"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><controller</span><span class="perl_Others"> type=</span><span class="perl_String">'ide'</span><span class="perl_Others"> index=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><controller</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio-serial'</span><span class="perl_Others"> index=</span><span class="perl_String">'0'</span><span class="perl_Others"> ports=</span><span class="perl_String">'16'</span><span class="perl_Others"> vectors=</span><span class="perl_String">'4'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><controller</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio-serial'</span><span class="perl_Others"> index=</span><span class="perl_String">'1'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'pci'</span><span class="perl_Others"> domain=</span><span class="perl_String">'0x0000'</span><span class="perl_Others"> bus=</span><span class="perl_String">'0x00'</span><span class="perl_Others"> slot=</span><span class="perl_String">'0x0a'</span><span class="perl_Others"> function=</span><span class="perl_String">'0x0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></controller></span>
+ ...
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.26. Devices - controllers</h6></div><br class="figure-break" /><div class="para">
+ Each controller has a mandatory attribute<code class="sgmltag-attribute">type</code>, which must be one of <code class="sgmltag-element">"ide", "fdc", "scsi", "sata", "usb", "ccid", or "virtio-serial"</code>, and a mandatory attribute <code class="sgmltag-attribute">index</code> which is the decimal integer describing in which order the bus controller is encountered (for use in controller attributes of <code class="sgmltag-element">address</code>elements). The "virtio-serial" controller has two additional optional attributes ports and vectors, which control how many devices can be connected through the controller. A "scsi" controller has an optional attribute <code class="sgmltag-element">model</code>, which is one of <code class="sgmltag-element">"auto", "buslogic", "ibmvscsi", "lsilogic", "lsias1068", "virtio-scsi" or "vmpvscsi"</code>. A "usb" controller has an optional attribute <code class="sgmltag-attribute">model</code>, which is one of <code class="sgmltag-elemen
t">"piix3-uhci", "piix4-uhci", "ehci", "ich9-ehci1", "ich9-uhci1", "ich9-uhci2", "ich9-uhci3", "vt82c686b-uhci", "pci-ohci" or "nec-xhci"</code>. Additionally, if the USB bus needs to be explicitly disabled for the guest, <code class="sgmltag-attribute">model='none'</code> may be used. The PowerPC64 "spapr-vio" addresses do not have an associated controller.
+ </div><div class="para">
+ For controllers that are themselves devices on a PCI or USB bus, an optional sub-element <code class="sgmltag-element">address</code> can specify the exact relationship of the controller to its master bus, with semantics given above.
+ </div><div class="para">
+ USB companion controllers have an optional sub-element <code class="sgmltag-element">master</code> to specify the exact relationship of the companion to its master controller. A companion controller is on the same bus as its master, so the companion index value should be equal.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-controllers2"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><controller</span><span class="perl_Others"> type=</span><span class="perl_String">'usb'</span><span class="perl_Others"> index=</span><span class="perl_String">'0'</span><span class="perl_Others"> model=</span><span class="perl_String">'ich9-ehci1'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'pci'</span><span class="perl_Others"> domain=</span><span class="perl_String">'0'</span><span class="perl_Others"> bus=</span><span class="perl_String">'0'</span><span class="perl_Others"> slot=</span><span class="perl_String">'4'</span><span class="perl_Others"> function=</span><span class="perl_String">'7'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></controller></span>
+ <span class="perl_Keyword"><controller</span><span class="perl_Others"> type=</span><span class="perl_String">'usb'</span><span class="perl_Others"> index=</span><span class="perl_String">'0'</span><span class="perl_Others"> model=</span><span class="perl_String">'ich9-uhci1'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><master</span><span class="perl_Others"> startport=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'pci'</span><span class="perl_Others"> domain=</span><span class="perl_String">'0'</span><span class="perl_Others"> bus=</span><span class="perl_String">'0'</span><span class="perl_Others"> slot=</span><span class="perl_String">'4'</span><span class="perl_Others"> function=</span><span class="perl_String">'0'</span><span class="perl_Others"> multifunction=</span><span class="perl_String">'on'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></controller></span>
+ ...
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.27. Devices - controllers - USB</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-device-addresses.html"><strong>Prev</strong>J.16.3. Device addresses</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="sub-section-libvirt-dom-xml-devices-device-leases.html"><strong>Next</strong>J.16.5. Device leases</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-device-addresses.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-device-addresses.html
new file mode 100644
index 0000000..17d1c88
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-device-addresses.html
@@ -0,0 +1,58 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.3. Device addresses</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-filesystems.html" title="J.16.2. Filesystems" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-controllers.html" title="J.16.4. Controllers" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-section-
libvirt-dom-xml-devices-filesystems.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-controllers.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-device-addresses"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.3. Device addresses</h3></div></div></div><div class="para">
+ Many devices have an optional <code class="sgmltag-starttag"><address></code> sub-element to describe where the device placed on the virtual bus is presented to the guest. If an address (or any optional attribute within an address) is omitted on input, libvirt will generate an appropriate address; but an explicit address is required if more control over layout is required. See below for device examples including an address element.
+ </div><div class="para">
+ Every address has a mandatory attribute <em class="parameter"><code>type</code></em> that describes which bus the device is on. The choice of which address to use for a given device is constrained in part by the device and the architecture of the guest. For example, a disk device uses <code class="sgmltag-attribute">type='disk'</code>, while a console device would use <code class="sgmltag-attribute">type='pci'</code> on i686 or x86_64 guests, or <code class="sgmltag-attribute">type='spapr-vio'</code> on PowerPC64 pseries guests. Each address <code class="sgmltag-starttag"><type></code> has additional optional attributes that control where on the bus the device will be placed. The additional attributes are as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type='pci'</code> - PCI addresses have the following additional attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">domain</code> (a 2-byte hex integer, not currently used by qemu)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">bus</code> (a hex value between 0 and 0xff, inclusive)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">slot</code> (a hex value between 0x0 and 0x1f, inclusive)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">function</code> (a value between 0 and 7, inclusive)
+ </div></li><li class="listitem"><div class="para">
+ Also available is the <code class="sgmltag-attribute">multifunction</code> attribute, which controls turning on the multifunction bit for a particular slot/function in the PCI control register. This multifunction attribute defaults to <code class="sgmltag-attvalue">'off'</code>, but should be set to <code class="sgmltag-attvalue">'on'</code> for function 0 of a slot that will have multiple functions used.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type='drive</code> - drive addresses have the following additional attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">controller</code>- (a 2-digit controller number)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">bus</code> - (a 2-digit bus number)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">target</code> - (a 2-digit bus number)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">unit</code> - (a 2-digit unit number on the bus)
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type='virtio-serial'</code> - Each virtio-serial address has the following additional attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">controller</code> - (a 2-digit controller number)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">bus</code> - (a 2-digit bus number)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">slot</code> - (a 2-digit slot within the bus)
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type='ccid'</code> - A CCID address, used for smart-cards, has the following additional attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">bus</code> - (a 2-digit bus number)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">slot</code> attribute - (a 2-digit slot within the bus)
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type='usb'</code> - USB addresses have the following additional attributes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">bus</code> - (a hex value between 0 and 0xfff, inclusive)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">port</code> - (a dotted notation of up to four octets, such as 1.2 or 2.1.3.1)
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type='spapr-vio</code> - On PowerPC pseries guests, devices can be assigned to the SPAPR-VIO bus. It has a flat 64-bit address space; by convention, devices are generally assigned at a non-zero multiple of 0x1000, but other addresses are valid and permitted by libvirt. The additional attribute: reg (the hex value address of the starting register) can be assigned to this attribute.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-filesystems.html"><strong>Prev</strong>J.16.2. Filesystems</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="sub-section-libvirt-dom-xml-devices-controllers.html"><strong>Next</strong>J.16.4. Controllers</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-device-leases.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-device-leases.html
new file mode 100644
index 0000000..b6a92ce
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-device-leases.html
@@ -0,0 +1,33 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.5. Device leases</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-controllers.html" title="J.16.4. Controllers" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-host-device-assignment.html" title="J.16.6. Host device assignment" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-section-libvirt-dom-xml-devices-controllers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-host-device-assignment.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-device-leases"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.5. Device leases</h3></div></div></div><div class="para">
+ When using a lock manager, you have the option to record device leases against a guest virtual machine. The lock manager will ensure that the guest virtual machine doesn't start unless the leases can be acquired. When configured using conventional management tools, the following section of the domain xml is effected:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-device-leases"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ ...
+ <span class="perl_Keyword"><lease></span>
+ <span class="perl_Keyword"><lockspace></span>somearea<span class="perl_Keyword"></lockspace></span>
+ <span class="perl_Keyword"><key></span>somekey<span class="perl_Keyword"></key></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> path=</span><span class="perl_String">'/some/lease/path'</span><span class="perl_Others"> offset=</span><span class="perl_String">'1024'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></lease></span>
+ ...
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.28. Devices - device leases</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-element">lease</code> section can have the following arguements:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-element">lockspace</code> - an arbitrary string that identifies lockspace within which the key is held. Lock managers may impose extra restrictions on the format, or length of the lockspace name.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-element">key</code> - an arbitrary string, that uniquely identies the lease to be acquired. Lock managers may impose extra restrictions on the format, or length of the key.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-element">target</code> - the fully qualified path of the file associated with the lockspace. The offset specifies where the lease is stored within the file. If the lock manager does not require a offset, set this value to <code class="sgmltag-element">0</code>.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-controllers.html"><strong>Prev</strong>J.16.4. Controllers</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="sub-section-libvirt-dom-xml-devices-host-device-assignment.html"><strong>Next</strong>J.16.6. Host device assignment</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-filesystems.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-filesystems.html
new file mode 100644
index 0000000..67e60e4
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-filesystems.html
@@ -0,0 +1,62 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.2. Filesystems</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-device-addresses.html" title="J.16.3. Device addresses" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-libvirt-dom-xml-device
s.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-device-addresses.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-filesystems"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.2. Filesystems</h3></div></div></div><div class="para">
+ A filesystems directory on the host that can be accessed directly from the guest
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-filesystems"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><filesystem</span><span class="perl_Others"> type=</span><span class="perl_String">'template'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> name=</span><span class="perl_String">'my-vm-template'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dir=</span><span class="perl_String">'/'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></filesystem></span>
+ <span class="perl_Keyword"><filesystem</span><span class="perl_Others"> type=</span><span class="perl_String">'mount'</span><span class="perl_Others"> accessmode=</span><span class="perl_String">'passthrough'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> type=</span><span class="perl_String">'path'</span><span class="perl_Others"> wrpolicy=</span><span class="perl_String">'immediate'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> dir=</span><span class="perl_String">'/export/to/guest'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dir=</span><span class="perl_String">'/import/from/host'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><readonly/></span>
+ <span class="perl_Keyword"></filesystem></span>
+ ...
+ <span class="perl_Keyword"></devices></span>
+ ...
+
+</pre></div><h6>Figure J.25. Devices - filesystems</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-attribute">filesystem</code> attribute has the following possible values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='mount'</code> - Specifies the host directory to mount in the guest. This is the default type if one is not specified. This mode also has an optional sub-element <code class="sgmltag-element">driver</code>, with an attribute <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='path'</code> or <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='handle'</code>. The driver block has an optional attribute <code class="sgmltag-attribute">wrpolicy</code> that further controls interaction with the host page cache; omitting the attribute reverts to the default setting, while specifying a value immediate means that a host writeback is immediately triggered for all pages touched during a guest file write operation
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='template'</code> - Specifies the OpenVZ filesystem template and is only used by OpenVZ driver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='file'</code> - Specifies that a host file will be treated as an image and mounted in the guest. This filesystem format will be autodetected and is only used by LXC driver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='block'</code> - Specifies the host block device to mount in the guest. The filesystem format will be autodetected and is only used by LXC driver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='ram'</code> - Specifies that an in-memory filesystem, using memory from the host OS will be used. The source element has a single attribute <code class="sgmltag-attribute">usage</code> which gives the memory usage limit in kibibytes and is only used by LXC driver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code><code class="sgmltag-element">='bind'</code> - Specifies a directory inside the guest which will be bound to another directory inside the guest. This element is only used by LXC driver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">accessmode</code> which specifies the security mode for accessing the source. Currently this only works with type='mount' for the QEMU/KVM driver. The possible values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">passthrough</code> - Specifies that the source is accessed with the User's permission settings that are set from inside the virtual guest machine. This is the default accessmode if one is not specified.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">mapped</code> - Specifies that the source is accessed with the permission settings of the hypervisor.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attvalue">squash</code> - Similar to <code class="sgmltag-attvalue">'passthrough'</code>, the exception is that failure of privileged operations like <code class="sgmltag-attvalue">chown</code> are ignored. This makes a passthrough-like mode usable for people who run the hypervisor as non-root.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-starttag"><source></code> - Specifies that the resource on the host that is being accessed in the guest virtual machine. The <code class="sgmltag-attribute">name</code> attribute must be used with <code class="sgmltag-starttag"><type='template'></code>, and the <code class="sgmltag-attribute">dir</code> attribute must be used with <code class="sgmltag-starttag"><type='mount'></code>. The <code class="sgmltag-attribute">usage</code> attribute is used with <code class="sgmltag-starttag"><type='ram'></code> to set the memory limit in KB.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-element">target</code> - Dictates where the source drivers can be accessed in the guest virtual machine. For most drivers this is an automatic mount point, but for QEMU-KVM this is merely an arbitrary string tag that is exported to the guest as a hint for where to mount.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">readonly</code> - Enables exporting the filesytem as a readonly mount for guest virtual machine, by default <code class="sgmltag-element">read-write</code> access is given.
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">space_hard_limit</code> - Specifies the maximum space available to this guest's filesystem
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">space_soft_limit</code> - Specifies the maximum space available to this guest's filesystem. The container is permitted to exceed its soft limits for a grace period of time. Afterwards the hard limit is enforced.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-libvirt-dom-xml-devices.html"><strong>Prev</strong>J.16. 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="sub-section-libvirt-dom-xml-devices-device-addresses.html"><strong>Next</strong>J.16.3. Device addresses</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-graphical-framebuffers.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-graphical-framebuffers.html
new file mode 100644
index 0000000..75ec232
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-graphical-framebuffers.html
@@ -0,0 +1,95 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.12. Graphical framebuffers</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-hub-devices.html" title="J.16.11. Hub devices" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-video.html" title="J.16.13. Video devices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-section-li
bvirt-dom-xml-devices-hub-devices.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-video.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-graphical-framebuffers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.12. Graphical framebuffers</h3></div></div></div><div class="para">
+ A graphics device allows for graphical interaction with the guest OS. A guest will typically have either a framebuffer or a text console configured to allow interaction with the admin.
+ </div><div class="para">
+ To specify the graphical framebuffer devices configuration settings, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig--xml-devices-graphical-framebuffers"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'sdl'</span><span class="perl_Others"> display=</span><span class="perl_String">':0.0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'vnc'</span><span class="perl_Others"> port=</span><span class="perl_String">'5904'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><listen</span><span class="perl_Others"> type=</span><span class="perl_String">'address'</span><span class="perl_Others"> address=</span><span class="perl_String">'1.2.3.4'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></graphics></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'rdp'</span><span class="perl_Others"> autoport=</span><span class="perl_String">'yes'</span><span class="perl_Others"> multiUser=</span><span class="perl_String">'yes'</span> <span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'desktop'</span><span class="perl_Others"> fullscreen=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'spice'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><listen</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Others"> network=</span><span class="perl_String">'rednet'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></graphics></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.56. Graphical framebuffers</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-element">graphics</code> element has a mandatory <code class="sgmltag-attribute">type</code> attribute which takes the value <code class="sgmltag-element">sdl</code>, <code class="sgmltag-element">vnc</code>, <code class="sgmltag-element">rdp</code> or <code class="sgmltag-element">desktop</code> as explained below:
+ </div><div class="table" id="table--libvirt-dom-xml-devices-Network-interfaces-setting-graphical-framebuffer-sgmltags"><h6>Table J.20. Graphical framebuffer elements</h6><div class="table-contents"><table summary="Graphical framebuffer elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-element">sdl</code>
+ </td><td class="">
+ This displays a window on the host desktop, it can take 3 optional arguments: a <code class="sgmltag-attribute">display</code> attribute for the display to use, an <code class="sgmltag-attribute">xauth</code> attribute for the authentication identifier, and an optional <code class="sgmltag-attribute">fullscreen</code> attribute accepting values <code class="sgmltag-element">yes</code> or <code class="sgmltag-element">no</code>
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">vnc</code>
+ </td><td class="">
+ Starts a VNC server. The <code class="sgmltag-attribute">port</code> attribute specifies the TCP port number (with <code class="sgmltag-element">-1</code> as legacy syntax indicating that it should be auto-allocated). The <code class="sgmltag-attribute">autoport</code> attribute is the new preferred syntax for indicating autoallocation of the TCP port to use. The <code class="sgmltag-attribute">listen</code> attribute is an IP address for the server to listen on. The <code class="sgmltag-attribute">passwd</code> attribute provides a VNC password in clear text. The <code class="sgmltag-attribute">keymap</code> attribute specifies the keymap to use. It is possible to set a limit on the validity of the password be giving an <code class="sgmltag-element">timestamp passwdValidTo='2010-04-09T15:51:00'</code> assumed to be in UTC. The <code class="sgmltag-attribute">connected</code> attribute allows control of connected client during password changes. VNC accepts <code clas
s="sgmltag-element">keep</code> value only and note that it may not be supported by all hypervisors. Rather than using listen/port, QEMU supports a socket attribute for listening on a unix domain socket path.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">spice</code>
+ </td><td class="">
+ Starts a SPICE server. The <code class="sgmltag-attribute">port</code> attribute specifies the TCP port number (with -1 as legacy syntax indicating that it should be auto-allocated), while <code class="sgmltag-element">tlsPort</code> gives an alternative secure port number. The <code class="sgmltag-attribute">autoport</code> attribute is the new preferred syntax for indicating autoallocation of both port numbers. The <code class="sgmltag-attribute">listen</code> attribute is an IP address for the server to listen on. The <code class="sgmltag-attribute">passwd</code> attribute provides a SPICE password in clear text. The <code class="sgmltag-attribute">keymap</code> attribute specifies the keymap to use. It is possible to set a limit on the validity of the password be giving an <code class="sgmltag-attribute">timestamp passwdValidTo='2010-04-09T15:51:00'</code> assumed to be in UTC. The <code class="sgmltag-attribute">connected</code> attribute allows control of conne
cted client during password changes. SPICE accepts keep to keep client connected, disconnect to disconnect client and fail to fail changing password. Note it is not be supported by all hypervisors. The <code class="sgmltag-attribute">defaultMode</code> attribute sets the default channel security policy, valid values are <code class="sgmltag-element">secure</code>, <code class="sgmltag-element">insecure</code> and the default <code class="sgmltag-element">any</code> (which is <code class="sgmltag-element">secure</code> if possible, but falls back to <code class="sgmltag-element">insecure</code> rather than erroring out if no secure path is available).
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ When SPICE has both a normal and TLS secured TCP port configured, it may be desirable to restrict what channels can be run on each port. This is achieved by adding one or more <code class="sgmltag-element">channel</code> elements inside the main <code class="sgmltag-element">graphics</code> element. Valid channel names include <code class="sgmltag-element">main</code>, <code class="sgmltag-element">display</code>, <code class="sgmltag-element">inputs</code>, <code class="sgmltag-element">cursor</code>, <code class="sgmltag-element">playback</code>, <code class="sgmltag-element">record</code>; <code class="sgmltag-element">smartcard</code>; and <code class="sgmltag-element">usbredir</code>.
+ </div><div class="para">
+ To specify the SPICE configuration settings, use a mangement tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-:devices-Network-interfaces-setting-graphical-framebuffer-sgmltags-spice-cfg"><div class="figure-contents"><pre class="programlisting">
+
+ <span class="perl_Keyword"><graphics</span><span class="perl_Others"> type=</span><span class="perl_String">'spice'</span><span class="perl_Others"> port=</span><span class="perl_String">'-1'</span><span class="perl_Others"> tlsPort=</span><span class="perl_String">'-1'</span><span class="perl_Others"> autoport=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> name=</span><span class="perl_String">'main'</span><span class="perl_Others"> mode=</span><span class="perl_String">'secure'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><channel</span><span class="perl_Others"> name=</span><span class="perl_String">'record'</span><span class="perl_Others"> mode=</span><span class="perl_String">'insecure'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><image</span><span class="perl_Others"> compression=</span><span class="perl_String">'auto_glz'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><streaming</span><span class="perl_Others"> mode=</span><span class="perl_String">'filter'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><clipboard</span><span class="perl_Others"> copypaste=</span><span class="perl_String">'no'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><mouse</span><span class="perl_Others"> mode=</span><span class="perl_String">'client'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></graphics></span>
+</pre></div><h6>Figure J.57. SPICE configuration</h6></div><br class="figure-break" /><div class="para">
+ SPICE supports variable compression settings for audio, images and streaming. These settings are accessible via the compression attribute in all following elements: <code class="sgmltag-element">image</code> to set image compression (accepts auto_glz, auto_lz, quic, glz, lz, off), <code class="sgmltag-element">jpeg</code> for JPEG compression for images over wan (accepts auto, never, always), <code class="sgmltag-element">zlib</code> for configuring wan image compression (accepts auto, never, always) and <code class="sgmltag-element">playback</code> for enabling audio stream compression (accepts on or off).
+ </div><div class="para">
+ Streaming mode is set by the <code class="sgmltag-element">streaming</code> element, settings its <code class="sgmltag-attribute">mode</code> attribute to one of <code class="sgmltag-element">filter</code>, <code class="sgmltag-element">all</code> or <code class="sgmltag-element">off</code>.
+ </div><div class="para">
+ In addition, Copy and paste functionality (via the SPICE agent) is set by the <code class="sgmltag-element">clipboard</code> element. It is enabled by default, and can be disabled by setting the <code class="sgmltag-attribute">copypaste</code> property to <code class="sgmltag-element">no</code>.
+ </div><div class="para">
+ Mouse mode is set by the <code class="sgmltag-element">mouse</code> element, setting its <code class="sgmltag-attribute">mode</code> attribute to one of <code class="sgmltag-element">server</code> or <code class="sgmltag-element">client</code>. If no mode is specified, the qemu default will be used (<code class="sgmltag-element">client</code> mode).
+ </div><div class="para">
+ Additional elements include:
+ </div><div class="table" id="table-libvirt-dom-xml-devices-Network-interfaces-setting-graphical-framebuffer-options2"><h6>Table J.21. Additional graphical framebuffer elements</h6><div class="table-contents"><table summary="Additional graphical framebuffer elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-element">rdp</code>
+ </td><td class="">
+ Starts a RDP server. The port attribute specifies the TCP port number (with -1 as legacy syntax indicating that it should be auto-allocated). The autoport attribute is the new preferred syntax for indicating autoallocation of the TCP port to use. The replaceUser attribute is a boolean deciding whether multiple simultaneous connections to the VM are permitted. The multiUser whether the existing connection must be dropped and a new connection must be established by the VRDP server, when a new client connects in single connection mode.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">desktop</code>
+ </td><td class="">
+ This value is reserved for VirtualBox domains for the moment. It displays a window on the host desktop, similarly to "sdl", but uses the VirtualBox viewer. Just like "sdl", it accepts the optional attributes display and fullscreen.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">listen</code>
+ </td><td class="">
+ Rather than putting the address information used to set up the listening socket for graphics types vnc and spice in the <code class="sgmltag-element">graphics</code>, the <code class="sgmltag-element">listen</code> attribute, a separate subelement of <code class="sgmltag-element">graphics</code>, called <code class="sgmltag-element">listen</code> can be specified (see the examples above). <code class="sgmltag-element">listen</code> accepts the following attributes:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">type</code> - Set to either address or network. This tells whether this listen element is specifying the address to be used directly, or by naming a network (which will then be used to determine an appropriate address for listening).
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-attribute">address</code> - this attribute will contain either an IP address or hostname (which will be resolved to an IP address via a DNS query) to listen on. In the "live" XML of a running domain, this attribute will be set to the IP address used for listening, even if <code class="sgmltag-attribute">type='network'</code>.
+ </div></li><li class="listitem"><div class="para">
+ network - if <code class="sgmltag-attribute">type='network'</code>, the network attribute will contain the name of a network in libvirt's list of configured networks. The named network configuration will be examined to determine an appropriate listen address. For example, if the network has an IPv4 address in its configuration (e.g. if it has a forward type of route, nat, or no forward type (isolated)), the first IPv4 address listed in the network's configuration will be used. If the network is describing a host bridge, the first IPv4 address associated with that bridge device will be used, and if the network is describing one of the 'direct' (macvtap) modes, the first IPv4 address of the first forward dev will be used.
+ </div></li></ul></div>
+
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-hub-devices.html"><strong>Prev</strong>J.16.11. Hub 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="sub-section-libvirt-dom-xml-devices-video.html"><strong>Next</strong>J.16.13. Video devices</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-guest-interface.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-guest-interface.html
new file mode 100644
index 0000000..9916f99
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-guest-interface.html
@@ -0,0 +1,82 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.15. Guest interfaces</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-consoles.html" title="J.16.14. Consoles, serial, parallel, and channel devices" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-channel.html" title="J.16.16. Channel" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 acces
skey="p" href="sub-section-libvirt-dom-xml-devices-consoles.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-channel.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-guest-interface"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.15. Guest interfaces</h3></div></div></div><div class="para">
+ A character device presents itself to the guest as one of the following types.
+ </div><div class="para">
+ To set the parallel port, use a management tool to make the following change to the domain XML
+ </div><div class="figure" id="fig--devices-guest-interface"><div class="figure-contents"><pre class="programlisting">
+
+...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><parallel</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/2'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></parallel></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.60. Guest interface Parallel Port</h6></div><br class="figure-break" /><div class="para">
+ <code class="sgmltag-starttag"><target></code> can have a <code class="sgmltag-attribute">port</code> attribute, which specifies the port number. Ports are numbered starting from 0. There are usually 0, 1 or 2 parallel ports.
+ </div><div class="para">
+ To set the serial port use a management tool to make the following change to the domain XML:
+ </div><div class="figure" id="fig-devices-guest-interface-serial-port"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><serial</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/3'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></serial></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.61. Guest Interface Serial port</h6></div><br class="figure-break" /><div class="para">
+ <code class="sgmltag-starttag"><target></code> can have a <code class="sgmltag-attribute">port</code> attribute, which specifies the port number. Ports are numbered starting from 0. There are usually 0, 1 or 2 serial ports. There is also an optional <code class="sgmltag-attribute">type</code> attribute, which has two choices for its value, one is <code class="sgmltag-attvalue">isa-serial</code>, the other is <code class="sgmltag-attvalue">usb-serial</code>. If <code class="sgmltag-attribute">type</code> is missing, <code class="sgmltag-attvalue">isa-serial</code> will be used by default. For usb-serial an optional sub-element <code class="sgmltag-starttag"><address></code> with <code class="sgmltag-attribute">type='usb'</code> can tie the device to a particular controller, documented above.
+ </div><div class="para">
+ The <code class="sgmltag-starttag"><console></code> element is used to represent interactive consoles. Depending on the type of guest in use, the consoles might be paravirtualized devices, or they might be a clone of a serial device, according to the following rules:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If no <code class="sgmltag-attribute">targetType</code> attribute is set, then the default device <code class="sgmltag-attribute">type</code> is according to the hypervisor's rules. The default <code class="sgmltag-attribute">type</code> will be added when re-querying the XML fed into libvirt. For fully virtualized guests, the default device type will usually be a serial port.
+ </div></li><li class="listitem"><div class="para">
+ If the <code class="sgmltag-attribute">targetType</code> attribute is <code class="sgmltag-element">serial</code>, and if no <code class="sgmltag-starttag"><serial></code> element exists, the console element will be copied to the <code class="sgmltag-starttag"><serial></code> element. If a <code class="sgmltag-starttag"><serial></code> element does already exist, the console element will be ignored.
+ </div></li><li class="listitem"><div class="para">
+ If the <code class="sgmltag-attribute">targetType</code> attribute is not <code class="sgmltag-element">serial</code>, it will be treated normally.
+ </div></li><li class="listitem"><div class="para">
+ Only the first <code class="sgmltag-starttag"><console></code> element may use a <code class="sgmltag-attribute">targetType</code> of <code class="sgmltag-attvalue">serial</code>. Secondary consoles must all be paravirtualized.
+ </div></li><li class="listitem"><div class="para">
+ On s390, the console element may use a targetType of sclp or sclplm (line mode). SCLP is the native console type for s390. There's no controller associated to SCLP consoles.
+ </div></li></ul></div><div class="para">
+ In the example below, a virtio console device is exposed in the guest as /dev/hvc[0-7] (for more information, see http://fedoraproject.org/wiki/Features/VirtioSerial):
+ </div><div class="figure" id="fig-devices-guest-interface-serial-port-virtio-console-device"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><console</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/4'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></console></span>
+
+ <span class="perl_Comment"><!-- KVM virtio console --></span>
+ <span class="perl_Keyword"><console</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/5'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio'</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></console></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Comment"><!-- KVM s390 sclp console --></span>
+ <span class="perl_Keyword"><console</span><span class="perl_Others"> type=</span><span class="perl_String">'pty'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> path=</span><span class="perl_String">'/dev/pts/1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> type=</span><span class="perl_String">'sclp'</span><span class="perl_Others"> port=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></console></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.62. Guest Interface - virtio console device</h6></div><br class="figure-break" /><div class="para">
+ If the console is presented as a serial port, the <code class="sgmltag-starttag"><target></code> element has the same attributes as for a serial port. There is usually only one console.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-consoles.html"><strong>Prev</strong>J.16.14. Consoles, serial, parallel, and channel ...</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="sub-section-libvirt-dom-xml-devices-channel.html"><strong>Next</strong>J.16.16. Channel</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-host-device-assignment.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-host-device-assignment.html
new file mode 100644
index 0000000..0c7c53b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-host-device-assignment.html
@@ -0,0 +1,78 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.6. Host device assignment</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-device-leases.html" title="J.16.5. Device leases" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-host-device-assignment-block-character-devices.html" title="J.16.6.2. Block / character devices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="docna
v"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-device-leases.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-host-device-assignment-block-character-devices.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-host-device-assignment"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.6. Host device assignment</h3></div></div></div><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-host-device-assignment-usb-pci-devices"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.6.1. USB / PCI devices</h4></div></div></div><div class="para">
+ The host's USB and PCI devices can be passed through to the guest using the <code class="sgmltag-element">hostdev</code> element, by modifying the host using a management tool the following section of the domain xml file is configured:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-host-device-assignment"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><hostdev</span><span class="perl_Others"> mode=</span><span class="perl_String">'subsystem'</span><span class="perl_Others"> type=</span><span class="perl_String">'usb'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> startupPolicy=</span><span class="perl_String">'optional'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><vendor</span><span class="perl_Others"> id=</span><span class="perl_String">'0x1234'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><product</span><span class="perl_Others"> id=</span><span class="perl_String">'0xbeef'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></source></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'2'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></hostdev></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.29. Devices - host device assignment</h6></div><br class="figure-break" /><div class="para">
+ Alternatively the following can also be done:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-host-device-assignment2"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><hostdev</span><span class="perl_Others"> mode=</span><span class="perl_String">'subsystem'</span><span class="perl_Others"> type=</span><span class="perl_String">'pci'</span><span class="perl_Others"> managed=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> bus=</span><span class="perl_String">'0x06'</span><span class="perl_Others"> slot=</span><span class="perl_String">'0x02'</span><span class="perl_Others"> function=</span><span class="perl_String">'0x0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></source></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><rom</span><span class="perl_Others"> bar=</span><span class="perl_String">'on'</span><span class="perl_Others"> file=</span><span class="perl_String">'/etc/fake/boot.bin'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></hostdev></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.30. Devices - host device assignment alternative</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-pci-managed-devices"><h6>Table J.13. Host device assignment elements</h6><div class="table-contents"><table summary="Host device assignment elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-element">hostdev</code>
+ </td><td class="">
+ This is the main container for describing host devices. For USB device passthrough <code class="sgmltag-element">mode</code> is always <code class="sgmltag-element">subsystem</code> and <code class="sgmltag-element">type</code> is <code class="sgmltag-element">usb</code> for a USB device and <code class="sgmltag-element">pci</code> for a PCI device. When <code class="sgmltag-element">managed</code> is <code class="sgmltag-element">yes</code> for a PCI device, it is detached from the host before being passed on to the guest, and reattached to the host after the guest exits. If <code class="sgmltag-element">managed</code> is omitted or <code class="sgmltag-element">no</code> for PCI and for USB devices, the user is responsible to use the arguement <code class="sgmltag-element">virNodeDeviceDettach</code> (or <code class="command">virsh nodedev-dettach</code>) before starting the guest or hot-plugging the device, and <code class="sgmltag-element">virNodeDeviceReAttach<
/code> (or <code class="command">virsh nodedev-reattach</code>) after hot-unplug or stopping the guest.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">source</code>
+ </td><td class="">
+ Describes the device as seen from the host. The USB device can either be addressed by vendor / product id using the <code class="sgmltag-element">vendor</code> and <code class="sgmltag-element">product</code> elements or by the device's address on the hosts using the <code class="sgmltag-element">address</code> element. PCI devices on the other hand can only be described by their address. Note that the source element of USB devices may contain a <code class="sgmltag-attribute">startupPolicy</code> attribute which can be used to define a rule for what to do if the specified host USB device is not found. The attribute accepts the following values:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="sgmltag-element">mandatory</code> - fails if missing for any reason (the default)
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-element">requisite</code> - fails if missing on boot up, drops if missing on migrate/restore/revert
+ </div></li><li class="listitem"><div class="para">
+ <code class="sgmltag-element">optional</code> - drops if missing at any start attempt
+ </div></li></ul></div>
+
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">vendor, product</code>
+ </td><td class="">
+ These elements each have an <code class="sgmltag-attribute">id</code> attribute that specifies the USB vendor and product id. The IDs can be given in decimal, hexadecimal (starting with 0x) or octal (starting with 0) form.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">boot</code>
+ </td><td class="">
+ Specifies that the device is bootable. The attribute's order determines the order in which devices will be tried during boot sequence. The per-device boot elements cannot be used together with general boot elements in BIOS bootloader section.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">rom</code>
+ </td><td class="">
+ Used to change how a PCI device's ROM is presented to the guest. The optional <code class="sgmltag-attribute">bar</code> attribute can be set to <code class="sgmltag-element">on</code> or <code class="sgmltag-element">off</code>, and determines whether or not the device's ROM will be visible in the guest's memory map. (In PCI documentation, the <code class="sgmltag-element">rombar</code> setting controls the presence of the Base Address Register for the ROM). If no rom bar is specified, the default setting will be used. The optional <code class="sgmltag-attribute">file</code> attribute is used to point to a binary file to be presented to the guest as the device's ROM BIOS. This can be useful, for example, to provide a PXE boot ROM for a virtual function of an sr-iov capable ethernet device (which has no boot ROMs for the VFs).
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">address</code>
+ </td><td class="">
+ Also has a <code class="sgmltag-attribute">bus</code> and <code class="sgmltag-attribute">device</code> attribute to specify the USB bus and device number the device appears at on the host. The values of these attributes can be given in decimal, hexadecimal (starting with 0x) or octal (starting with 0) form. For PCI devices the element carries 3 attributes allowing to designate the device as can be found with <code class="command">lspci</code> or with <code class="command">virsh nodedev-list</code>
+ </td></tr></tbody></table></div></div><br class="table-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-device-leases.html"><strong>Prev</strong>J.16.5. Device leases</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="sub-sub-section-libvirt-dom-xml-devices-host-device-assignment-block-character-devices.html"><strong>Next</strong>J.16.6.2. Block / character devices </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-host-interface.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-host-interface.html
new file mode 100644
index 0000000..abfd8be
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-host-interface.html
@@ -0,0 +1,193 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.17. Host interface</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-channel.html" title="J.16.16. Channel" /><link rel="next" href="section-libvirt-dom-xml-sound-devices.html" title="J.17. Sound devices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-section-libvirt-dom-xml-d
evices-channel.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="section-libvirt-dom-xml-sound-devices.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-host-interface"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.17. Host interface</h3></div></div></div><div class="para">
+ A character device presents itself to the host as one of the following types:
+ </div><div class="table" id="table--libvirt-dom-xml-devices-host-interfaces-character-device-options"><h6>Table J.23. Character device elements</h6><div class="table-contents"><table summary="Character device elements" border="1"><colgroup><col width="33%" /><col width="33%" /><col width="33%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th><th class="">
+ XML snippet
+ </th></tr></thead><tbody><tr><td class="">
+ Domain logfile
+ </td><td class="">
+ Disables all input on the character device, and sends output into the virtual machine's logfile
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><console type='stdio'></code>
+ <code class="sgmltag-starttag"><target port='1'/></code>
+ <code class="sgmltag-endtag"></console></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ Device logfile
+ </td><td class="">
+ A file is opened and all data sent to the character device is written to the file.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="file"></code>
+ <code class="sgmltag-starttag"><source path="/var/log/vm/vm-serial.log"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ Virtual console
+ </td><td class="">
+ Connects the character device to the graphical framebuffer in a virtual console. This is typically accessed via a special hotkey sequence such as "ctrl+alt+3"
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type='vc'></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ Null device
+ </td><td class="">
+ Connects the character device to the void. No data is ever provided to the input. All data written is discarded.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type='null'></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ Pseudo TTY
+ </td><td class="">
+ A Pseudo TTY is allocated using <code class="filename">/dev/ptmx</code>. A suitable client such as <code class="command">virsh console</code> can connect to interact with the serial port locally.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="pty"></code>
+ <code class="sgmltag-starttag"><source path="/dev/pts/3"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ NB Special case
+ </td><td class="">
+ NB special case if <code class="sgmltag-starttag"><console type='pty'></code>, then the TTY path is also duplicated as an attribute <code class="sgmltag-attribute">tty='/dev/pts/3'</code> on the top level <code class="sgmltag-starttag"><console></code> tag. This provides compat with existing syntax for <code class="sgmltag-starttag"><console></code> tags.
+ </td><td class="auto-generated"> </td></tr><tr><td class="">
+ Host device proxy
+ </td><td class="">
+ The character device is passed through to the underlying physical character device. The device types must match, eg the emulated serial port should only be connected to a host serial port - don't connect a serial port to a parallel port.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="dev"></code>
+ <code class="sgmltag-starttag"><source path="/dev/ttyS0"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ Named pipe
+ </td><td class="">
+ The character device writes output to a named pipe. See pipe(7) MAN page for more info.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="pipe"></code>
+ <code class="sgmltag-starttag"><source path="/tmp/mypipe"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ TCP client/server
+ </td><td class="">
+ The character device acts as a TCP client connecting to a remote server.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="tcp"></code>
+ <code class="sgmltag-starttag"><source mode="connect" host="0.0.0.0" service="2445"/></code>
+ <code class="sgmltag-starttag"><protocol type="raw"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ <div class="para">
+ Or as a TCP server waiting for a client connection.
+ </div>
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="tcp"></code>
+ <code class="sgmltag-starttag"><source mode="bind" host="127.0.0.1" service="2445"/></code>
+ <code class="sgmltag-starttag"><protocol type="raw"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ <div class="para">
+ Alternatively you can use telnet instead of raw TCP. In addition, you can also use telnets (secure telnet) and tls.
+ </div>
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="tcp"></code>
+ <code class="sgmltag-starttag"><source mode="connect" host="0.0.0.0" service="2445"/></code>
+ <code class="sgmltag-starttag"><protocol type="telnet"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-starttag"><serial type="tcp"></code>
+ <code class="sgmltag-starttag"><source mode="bind" host="127.0.0.1" service="2445"/></code>
+ <code class="sgmltag-starttag"><protocol type="telnet"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+
+ </td></tr><tr><td class="">
+ UDP network console
+ </td><td class="">
+ The character device acts as a UDP netconsole service, sending and receiving packets. This is a lossy service.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="udp"></code>
+ <code class="sgmltag-starttag"><source mode="bind" host="0.0.0.0" service="2445"/></code>
+ <code class="sgmltag-starttag"><source mode="connect" host="0.0.0.0" service="2445"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr><tr><td class="">
+ UNIX domain socket client/server
+ </td><td class="">
+ The character device acts as a UNIX domain socket server, accepting connections from local clients.
+ </td><td class="">
+
+<pre class="screen">
+ <code class="sgmltag-starttag"><devices></code>
+ <code class="sgmltag-starttag"><serial type="unix"></code>
+ <code class="sgmltag-starttag"><source mode="bind" path="/tmp/foo"/></code>
+ <code class="sgmltag-starttag"><target port="1"/></code>
+ <code class="sgmltag-endtag"></serial></code>
+ <code class="sgmltag-endtag"></devices></code>
+</pre>
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-channel.html"><strong>Prev</strong>J.16.16. Channel</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="section-libvirt-dom-xml-sound-devices.html"><strong>Next</strong>J.17. Sound devices</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-hub-devices.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-hub-devices.html
new file mode 100644
index 0000000..8b1f0ca
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-hub-devices.html
@@ -0,0 +1,23 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.11. Hub devices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-input-devices.html" title="J.16.10. Input devices" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-graphical-framebuffers.html" title="J.16.12. Graphical framebuffers" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 acce
sskey="p" href="sub-section-libvirt-dom-xml-devices-input-devices.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-graphical-framebuffers.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-hub-devices"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.11. Hub devices</h3></div></div></div><div class="para">
+ A hub is a device that expands a single port into several so that there are more ports available to connect devices to a host system.
+ </div><div class="para">
+ To specify the hub devices configuration settings, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-xml-devices-hub-devices"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><hub</span><span class="perl_Others"> type=</span><span class="perl_String">'usb'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.55. Hub devices</h6></div><br class="figure-break" /><div class="para">
+ The hub element has one mandatory attribute, the type whose value can only be <code class="sgmltag-element">usb</code>. The hub element has an optional sub-element <code class="sgmltag-element">address</code> with <code class="sgmltag-attribute">type='usb'</code>which can tie the device to a particular controller.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-input-devices.html"><strong>Prev</strong>J.16.10. Input 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="sub-section-libvirt-dom-xml-devices-graphical-framebuffers.html"><strong>Next</strong>J.16.12. Graphical framebuffers</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-input-devices.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-input-devices.html
new file mode 100644
index 0000000..06d6be2
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-input-devices.html
@@ -0,0 +1,26 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.10. Input devices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-modifying-virtual-link-state.html" title="J.16.9.15. Modifying virtual link state" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-hub-devices.html" title="J.16.11. Hub devices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="pre
vious"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-modifying-virtual-link-state.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-hub-devices.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-input-devices"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.10. Input devices</h3></div></div></div><div class="para">
+ Input devices allow interaction with the graphical framebuffer in the guest virtual machine. When enabling the framebuffer, an input device is automatically provided. It may be possible to add additional devices explicitly, for example, to provide a graphics tablet for absolute cursor movement.
+ </div><div class="para">
+ To specify the input devices configuration settings, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-input-devices"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><input</span><span class="perl_Others"> type=</span><span class="perl_String">'mouse'</span><span class="perl_Others"> bus=</span><span class="perl_String">'usb'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+
+</pre></div><h6>Figure J.54. Input devices</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-starttag"><input></code> element has one mandatory attribute: <code class="sgmltag-attribute">type</code> which can be set to: <code class="sgmltag-attvalue">mouse</code> or <code class="sgmltag-attvalue">tablet</code>. The latter provides absolute cursor movement, while the former uses relative movement. The optional <code class="sgmltag-attribute">bus</code> attribute can be used to refine the exact device type and can be set to: <code class="sgmltag-attvalue">xen</code> (paravirtualized), <code class="sgmltag-attvalue">ps2</code>, and <code class="sgmltag-attvalue">usb</code>.
+ </div><div class="para">
+ The input element has an optional sub-element <code class="sgmltag-starttag"><address></code>, which can tie the device to a particular PCI slot, as documented above.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-modifying-virtual-link-state.html"><strong>Prev</strong>J.16.9.15. Modifying virtual link state</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="sub-section-libvirt-dom-xml-devices-hub-devices.html"><strong>Next</strong>J.16.11. Hub devices</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-redirected-devices.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-redirected-devices.html
new file mode 100644
index 0000000..a1b68e8
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-redirected-devices.html
@@ -0,0 +1,44 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.7. Redirected devices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-host-device-assignment-block-character-devices.html" title="J.16.6.2. Block / character devices" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-smartcard.html" title="J.16.8. Smartcard devices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="docna
v"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-host-device-assignment-block-character-devices.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-smartcard.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-redirected-devices"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.7. Redirected devices</h3></div></div></div><div class="para">
+ USB device redirection through a character device is supported by configuring it with managment tools that modify the following section of the domain xml:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-redirected-devices"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><redirdev</span><span class="perl_Others"> bus=</span><span class="perl_String">'usb'</span><span class="perl_Others"> type=</span><span class="perl_String">'tcp'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'connect'</span><span class="perl_Others"> host=</span><span class="perl_String">'localhost'</span><span class="perl_Others"> service=</span><span class="perl_String">'4000'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></redirdev></span>
+ <span class="perl_Keyword"><redirfilter></span>
+ <span class="perl_Keyword"><usbdev</span><span class="perl_Others"> class=</span><span class="perl_String">'0x08'</span><span class="perl_Others"> vendor=</span><span class="perl_String">'0x1234'</span><span class="perl_Others"> product=</span><span class="perl_String">'0xbeef'</span><span class="perl_Others"> version=</span><span class="perl_String">'2.00'</span><span class="perl_Others"> allow=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><usbdev</span><span class="perl_Others"> allow=</span><span class="perl_String">'no'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></redirfilter></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.34. Devices - redirected devices</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-host-device-assignement-redirected-devices"><h6>Table J.15. Redirected device elements</h6><div class="table-contents"><table summary="Redirected device elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-element">redirdev</code>
+ </td><td class="">
+ This is the main container for describing redirected devices. <code class="sgmltag-attribute">bus</code> must be <code class="sgmltag-element">usb</code> for a USB device. An additional attribute type is required, matching one of the supported serial device types, to describe the host side of the tunnel; <code class="sgmltag-attribute">type='tcp'</code> or <code class="sgmltag-attribute">type='spicevmc'</code> (which uses the usbredir channel of a SPICE graphics device) are typical. The redirdev element has an optional sub-element <code class="sgmltag-element">address</code> which can tie the device to a particular controller. Further sub-elements, such as <code class="sgmltag-element">source</code>, may be required according to the given <code class="sgmltag-attribute">type</code>, although a<code class="sgmltag-element">target</code> sub-element is not required (since the consumer of the character device is the hypervisor itself, rather than a device visible in the
guest).
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">boot</code>
+ </td><td class="">
+ Specifies that the device is bootable. The order attribute determines the order in which devices will be tried during boot sequence. The per-device boot elements cannot be used together with general boot elements in BIOS bootloader section.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">redirfilter</code>
+ </td><td class="">
+ This is used for creating the filter rule to filter out certain devices from redirection. It uses sub-element <code class="sgmltag-element">usbdev</code> to define each filter rule. The <code class="sgmltag-attribute">class</code> attribute is the USB Class code.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-host-device-assignment-block-character-devices.html"><strong>Prev</strong>J.16.6.2. Block / character 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="sub-section-libvirt-dom-xml-devices-smartcard.html"><strong>Next</strong>J.16.8. Smartcard devices</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-smartcard.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-smartcard.html
new file mode 100644
index 0000000..96151ce
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-smartcard.html
@@ -0,0 +1,55 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.8. Smartcard devices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-redirected-devices.html" title="J.16.7. Redirected devices" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 acce
sskey="p" href="sub-section-libvirt-dom-xml-devices-redirected-devices.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-smartcard"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.8. Smartcard devices</h3></div></div></div><div class="para">
+ A virtual smartcard device can be supplied to the guest via the <code class="sgmltag-element">smartcard</code> element. A USB smartcard reader device on the host cannot be used on a guest with simple device passthrough, as it cannot be made available to both the host and guest and can possibly lock the host computer when it is removed from the guest. Therefore, some hypervisors provide a specialized virtual device that can present a smartcard interface to the guest, with several modes for describing how the credentials are obtained from the host or even a from a channel created to a third-party smartcard provider. To set these parameters use a managment tool that will edit the following section of the domain XML:
+ </div><div class="para">
+ USB device redirection through a character device is supported by configuring it with managment tools that modify the following section of the domain xml:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-smartcard"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><smartcard</span><span class="perl_Others"> mode=</span><span class="perl_String">'host'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><smartcard</span><span class="perl_Others"> mode=</span><span class="perl_String">'host-certificates'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><certificate></span>cert1<span class="perl_Keyword"></certificate></span>
+ <span class="perl_Keyword"><certificate></span>cert2<span class="perl_Keyword"></certificate></span>
+ <span class="perl_Keyword"><certificate></span>cert3<span class="perl_Keyword"></certificate></span>
+ <span class="perl_Keyword"><database></span>/etc/pki/nssdb/<span class="perl_Keyword"></database></span>
+ <span class="perl_Keyword"></smartcard></span>
+ <span class="perl_Keyword"><smartcard</span><span class="perl_Others"> mode=</span><span class="perl_String">'passthrough'</span><span class="perl_Others"> type=</span><span class="perl_String">'tcp'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> mode=</span><span class="perl_String">'bind'</span><span class="perl_Others"> host=</span><span class="perl_String">'127.0.0.1'</span><span class="perl_Others"> service=</span><span class="perl_String">'2001'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><protocol</span><span class="perl_Others"> type=</span><span class="perl_String">'raw'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'ccid'</span><span class="perl_Others"> controller=</span><span class="perl_String">'0'</span><span class="perl_Others"> slot=</span><span class="perl_String">'0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></smartcard></span>
+ <span class="perl_Keyword"><smartcard</span><span class="perl_Others"> mode=</span><span class="perl_String">'passthrough'</span><span class="perl_Others"> type=</span><span class="perl_String">'spicevmc'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.35. Devices - smartcard devices</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-element">smartcard</code> element has a mandatory attribute <code class="sgmltag-attribute">mode</code>. The following modes are supported; in each mode, the guest sees a device on its USB bus that behaves like a physical USB CCID (Chip/Smart Card Interface Device) card.
+ </div><div class="para">
+ The mode attributes are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-host-device-assignement-smartcard-modes"><h6>Table J.16. Smartcard mode elements</h6><div class="table-contents"><table summary="Smartcard mode elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-attribute">mode='host'</code>
+ </td><td class="">
+ In this mode, the hypervisor relays all requests from the guest into direct access to the host's smartcard via NSS. No other attributes or sub-elements are required. See below about the use of an optional <code class="sgmltag-element">address</code> sub-element.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">mode='host-certificates'</code>
+ </td><td class="">
+ This mode allows you to provide three NSS certificate names residing in a database on the host, rather than requiring a smartcard to be plugged into the host. These certificates can be generated via the command <code class="sgmltag-element">certutil -d /etc/pki/nssdb -x -t CT,CT,CT -S -s CN=cert1 -n cert1,</code> and the resulting three certificate names must be supplied as the content of each of three <code class="sgmltag-element">certificate</code> sub-elements. An additional sub-element <code class="sgmltag-element">database</code> can specify the absolute path to an alternate directory (matching the <code class="sgmltag-element">-d</code> flag of the <code class="command">certutil</code> command when creating the certificates); if not present, it defaults to <code class="filename">/etc/pki/nssdb</code>.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">mode='passthrough'</code>
+ </td><td class="">
+ Using this mode allows you to tunnel all requests through a secondary character device to a third-party provider (which may in turn be talking to a smartcard or using three certificate files, rather than having the hypervisor directly communicate with the host. In this mode of operation, an additional attribute <code class="sgmltag-attribute">type</code> is required, matching one of the supported serial device types, to describe the host side of the tunnel; <code class="sgmltag-attribute">type='tcp'</code> or <code class="sgmltag-attribute">type='spicevmc'</code> (which uses the smartcard channel of a SPICE graphics device) are typical. Further sub-elements, such as <code class="sgmltag-element">source</code>, may be required according to the given type, although a <code class="sgmltag-element">target</code> sub-element is not required (since the consumer of the character device is the hypervisor itself, rather than a device visible in the guest).
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Each mode supports an optional sub-element <code class="sgmltag-element">address</code>, which fine-tunes the correlation between the smartcard and a ccid bus controller (Refer to <a class="xref" href="sub-section-libvirt-dom-xml-devices-device-addresses.html">Section J.16.3, “Device addresses”</a>).
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-redirected-devices.html"><strong>Prev</strong>J.16.7. Redirected 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="sub-section-libvirt-dom-xml-devices-Network-interfaces.html"><strong>Next</strong>J.16.9. Network interfaces</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-video.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-video.html
new file mode 100644
index 0000000..49bd223
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-section-libvirt-dom-xml-devices-video.html
@@ -0,0 +1,47 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.13. Video devices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-libvirt-dom-xml-devices.html" title="J.16. Devices" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-graphical-framebuffers.html" title="J.16.12. Graphical framebuffers" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-consoles.html" title="J.16.14. Consoles, serial, parallel, and channel devices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-section-libvirt-dom-xml-devices-graphical-framebuffers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-consoles.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-section-libvirt-dom-xml-devices-video"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">J.16.13. Video devices</h3></div></div></div><div class="para">
+ A video device.
+ </div><div class="para">
+ To specify the video devices configuration settings, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-devices-video"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><video></span>
+ <span class="perl_Keyword"><model</span><span class="perl_Others"> type=</span><span class="perl_String">'vga'</span><span class="perl_Others"> vram=</span><span class="perl_String">'8192'</span><span class="perl_Others"> heads=</span><span class="perl_String">'1'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><acceleration</span><span class="perl_Others"> accel3d=</span><span class="perl_String">'yes'</span><span class="perl_Others"> accel2d=</span><span class="perl_String">'yes'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></model></span>
+ <span class="perl_Keyword"></video></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.58. Video devices</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-element">graphics</code> element has a mandatory <code class="sgmltag-attribute">type</code> attribute which takes the value "sdl", "vnc", "rdp" or "desktop" as explained below:
+ </div><div class="table" id="table-libvirt-dom-xml-devices-Network-interfaces-setting-graphical-framebuffer-options"><h6>Table J.22. Graphical framebuffer elements</h6><div class="table-contents"><table summary="Graphical framebuffer elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-element">video</code>
+ </td><td class="">
+ The <code class="sgmltag-element">video</code> element is the container for describing video devices. For backwards compatibility, if no video is set but there is a <code class="sgmltag-element">graphics</code> element in domain xml, then libvirt will add a default <code class="sgmltag-element">video</code> according to the guest type. If "ram" or "vram" are not supplied a default value is used.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">model</code>
+ </td><td class="">
+ This has a mandatory <code class="sgmltag-attribute">type</code> attribute which takes the value <code class="sgmltag-element">vga</code>, <code class="sgmltag-element">cirrus</code>, <code class="sgmltag-element">vmvga</code>, <code class="sgmltag-element">xen</code>, <code class="sgmltag-element">vbox</code>, or <code class="sgmltag-element">qxl</code> depending on the hypervisor features available. You can also provide the amount of video memory in kibibytes (blocks of 1024 bytes) using vram and the number of figure with heads.
+ </td></tr><tr><td class="">
+ acceleration
+ </td><td class="">
+ If acceleration is supported it should be enabled using the <code class="sgmltag-attribute">accel3d</code> and <code class="sgmltag-attribute">accel2d</code> attributes in the <code class="sgmltag-element">acceleration</code> element.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">address</code>
+ </td><td class="">
+ The optional address sub-element can be used to tie the video device to a particular PCI slot.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-graphical-framebuffers.html"><strong>Prev</strong>J.16.12. Graphical framebuffers</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="sub-section-libvirt-dom-xml-devices-consoles.html"><strong>Next</strong>J.16.14. Consoles, serial, parallel, and channel ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-DHCP-snooping.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-DHCP-snooping.html
new file mode 100644
index 0000000..c15321f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-DHCP-snooping.html
@@ -0,0 +1,25 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.5.2. DHCP snooping</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-auto-IP-add-detect-dhcp-snoop.html" title="H.10.5. Automatic IP address detection and DHCP snooping" /><link rel="prev" href="sub-sect-auto-IP-add-detect-dhcp-snoop.html" title="H.10.5. Automatic IP address detection and DHCP snooping" /><link rel="next" href="sub-sect-vars-reserved.html" title="H.10.6. Reserved Variables" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="d
ocnav"><li class="previous"><a accesskey="p" href="sub-sect-auto-IP-add-detect-dhcp-snoop.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-vars-reserved.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-DHCP-snooping"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.5.2. DHCP snooping</h4></div></div></div><div class="para">
+ <code class="command">CTRL_IP_LEARNING=<em class="replaceable"><code>dhcp</code></em></code> (DHCP snooping) provides additional anti-spoofing security, especially when combined with a filter allowing only trusted DHCP servers to assign IP addresses. To enable this, set the variable <em class="parameter"><code>DHCPSERVER</code></em> to the IP address of a valid DHCP server and provide filters that use this variable to filter incoming DHCP responses.
+ </div><div class="para">
+ When DHCP snooping is enabled and the DHCP lease expires, the guest will no longer be able to use the IP address until it acquires a new, valid lease from a DHCP server. If the guest is migrated, it must get a new valid DHCP lease to use an IP address (e.g., by bringing the VM interface down and up again).
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Automatic DHCP detection listens to the DHCP traffic the guest exchanges with the DHCP server of the infrastructure. To avoid denial-of-service attacks on libvirt, the evaluation of those packets is rate-limited, meaning that a guest sending an excessive number of DHCP packets per second on an interface will not have all of those packets evaluated and thus filters may not get adapted. Normal DHCP client behavior is assumed to send a low number of DHCP packets per second. Further, it is important to setup appropriate filters on all guests in the infrastructure to avoid them being able to send DHCP packets. Therefore guests must either be prevented from sending UDP and TCP traffic from port 67 to port 68 or the DHCPSERVER variable should be used on all guests to restrict DHCP server messages to only be allowed to originate from trusted DHCP servers. At the same time anti-spoofing prevention must be enabled on all guests in the subnet.
+ </div></div></div><div class="example" id="exam-dhcp-snoop"><h6>Example H.6. Activating IPs for DHCP snooping</h6><div class="example-contents"><div class="para">
+ The following XML provides an example for the activation of IP address learning using the DHCP snooping method:
+ </div><pre class="screen">
+ <interface type='bridge'>
+ <source bridge='virbr0'/>
+ <filterref filter='clean-traffic'>
+ <parameter name='CTRL_IP_LEARNING' value='dhcp'/>
+ </filterref>
+ </interface>
+</pre></div></div><br class="example-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-auto-IP-add-detect-dhcp-snoop.html"><strong>Prev</strong>H.10.5. Automatic IP address detection and DHCP 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="sub-sect-vars-reserved.html"><strong>Next</strong>H.10.6. Reserved Variables</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-chars-IPv6.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-chars-IPv6.html
new file mode 100644
index 0000000..b47c1a2
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-chars-IPv6.html
@@ -0,0 +1,104 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.10.6. IPv6</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-supp-pros.html" title="H.10.10. Supported protocols" /><link rel="prev" href="sub-sub-sect-prot-Ipv4-explained.html" title="H.10.10.5. IPv4" /><link rel="next" href="sub-sub-sect-chars-tcp-udp.html" title="H.10.10.7. TCP/UDP/SCTP" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sub-sect-prot-Ipv4-explained.html"><str
ong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-chars-tcp-udp.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-chars-IPv6"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.10.6. IPv6</h4></div></div></div><div class="para">
+ Protocol ID: ipv6
+ </div><div class="para">
+ Rules of this type should either go into the root or ipv6 chain.
+ </div><div class="table" id="table-ipv6-vars"><h6>Table H.8. IPv6 protocol types</h6><div class="table-contents"><table summary="IPv6 protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of destination
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ protocol
+ </td><td class="">
+ UINT8, STRING
+ </td><td class="">
+ Layer 4 protocol identifier. Valid strings for protocol are: tcp, udp, udplite, esp, ah, icmpv6, sctp
+ </td></tr><tr><td class="">
+ scrportstart
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ Start of range of valid source ports; requires protocol
+ </td></tr><tr><td class="">
+ srcportend
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ End of range of valid source ports; requires protocol
+ </td></tr><tr><td class="">
+ dstportstart
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ Start of range of valid destination ports; requires protocol
+ </td></tr><tr><td class="">
+ dstportend
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ End of range of valid destination ports; requires protocol
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-prot-Ipv4-explained.html"><strong>Prev</strong>H.10.10.5. IPv4</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="sub-sub-sect-chars-tcp-udp.html"><strong>Next</strong>H.10.10.7. TCP/UDP/SCTP</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-chars-tcp-udp.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-chars-tcp-udp.html
new file mode 100644
index 0000000..4ccfa30
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-chars-tcp-udp.html
@@ -0,0 +1,128 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.10.7. TCP/UDP/SCTP</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-supp-pros.html" title="H.10.10. Supported protocols" /><link rel="prev" href="sub-sub-sect-chars-IPv6.html" title="H.10.10.6. IPv6" /><link rel="next" href="sub-sub-sect-icmp.html" title="H.10.10.8. ICMP" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sub-sect-chars-IPv6.html"><strong>Prev</strong></a></li><li class
="next"><a accesskey="n" href="sub-sub-sect-icmp.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-chars-tcp-udp"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.10.7. TCP/UDP/SCTP</h4></div></div></div><div class="para">
+ Protocol ID: tcp, udp, sctp
+ </div><div class="para">
+ The chain parameter is ignored for this type of traffic and should either be omitted or set to root. .
+ </div><div class="table" id="table-tcp-udp-vars"><h6>Table H.9. TCP/UDP/SCTP protocol types</h6><div class="table-contents"><table summary="TCP/UDP/SCTP protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ scripto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of source IP address
+ </td></tr><tr><td class="">
+ srcipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of source IP address
+ </td></tr><tr><td class="">
+ dstipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of destination IP address
+ </td></tr><tr><td class="">
+ dstipto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of destination IP address
+ </td></tr><tr><td class="">
+ scrportstart
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ Start of range of valid source ports; requires protocol
+ </td></tr><tr><td class="">
+ srcportend
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ End of range of valid source ports; requires protocol
+ </td></tr><tr><td class="">
+ dstportstart
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ Start of range of valid destination ports; requires protocol
+ </td></tr><tr><td class="">
+ dstportend
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ End of range of valid destination ports; requires protocol
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr><tr><td class="">
+ state
+ </td><td class="">
+ STRING
+ </td><td class="">
+ comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE
+ </td></tr><tr><td class="">
+ flags
+ </td><td class="">
+ STRING
+ </td><td class="">
+ TCP-only: format of mask/flags with mask and flags each being a comma separated list of SYN,ACK,URG,PSH,FIN,RST or NONE or ALL
+ </td></tr><tr><td class="">
+ ipset
+ </td><td class="">
+ STRING
+ </td><td class="">
+ The name of an IPSet managed outside of libvirt
+ </td></tr><tr><td class="">
+ ipsetflags
+ </td><td class="">
+ IPSETFLAGS
+ </td><td class="">
+ flags for the IPSet; requires ipset attribute
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-chars-IPv6.html"><strong>Prev</strong>H.10.10.6. IPv6</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="sub-sub-sect-icmp.html"><strong>Next</strong>H.10.10.8. ICMP</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-icmp.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-icmp.html
new file mode 100644
index 0000000..a4c5d11
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-icmp.html
@@ -0,0 +1,128 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.10.8. ICMP</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-supp-pros.html" title="H.10.10. Supported protocols" /><link rel="prev" href="sub-sub-sect-chars-tcp-udp.html" title="H.10.10.7. TCP/UDP/SCTP" /><link rel="next" href="sub-sub-sect-igmp-esp-ah-etc.html" title="H.10.10.9. IGMP, ESP, AH, UDPLITE, 'ALL'" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sub-sect-chars-tcp
-udp.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-igmp-esp-ah-etc.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-icmp"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.10.8. ICMP</h4></div></div></div><div class="para">
+ Protocol ID: icmp
+ </div><div class="para">
+ Note: The chain parameter is ignored for this type of traffic and should either be omitted or set to root.
+ </div><div class="table" id="table-icmp-vars"><h6>Table H.10. ICMP protocol types</h6><div class="table-contents"><table summary="ICMP protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to the MAC address of the sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAD_ADDR
+ </td><td class="">
+ MAC address of the destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to the MAC address of the destination
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ srcipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ start of range of source IP address
+ </td></tr><tr><td class="">
+ scripto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ end of range of source IP address
+ </td></tr><tr><td class="">
+ dstipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of destination IP address
+ </td></tr><tr><td class="">
+ dstipto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of destination IP address
+ </td></tr><tr><td class="">
+ type
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ ICMP type
+ </td></tr><tr><td class="">
+ code
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ ICMP code
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr><tr><td class="">
+ state
+ </td><td class="">
+ STRING
+ </td><td class="">
+ comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE
+ </td></tr><tr><td class="">
+ ipset
+ </td><td class="">
+ STRING
+ </td><td class="">
+ The name of an IPSet managed outside of libvirt
+ </td></tr><tr><td class="">
+ ipsetflags
+ </td><td class="">
+ IPSETFLAGS
+ </td><td class="">
+ flags for the IPSet; requires ipset attribute
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-chars-tcp-udp.html"><strong>Prev</strong>H.10.10.7. TCP/UDP/SCTP</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="sub-sub-sect-igmp-esp-ah-etc.html"><strong>Next</strong>H.10.10.9. IGMP, ESP, AH, UDPLITE, 'ALL'</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-icmpv6.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-icmpv6.html
new file mode 100644
index 0000000..cf01b05
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-icmpv6.html
@@ -0,0 +1,110 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.10.11. ICMPv6</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-supp-pros.html" title="H.10.10. Supported protocols" /><link rel="prev" href="sub-sub-sect-tcp-utp-sctp-over-ipv6.html" title="H.10.10.10. TCP/UDP/SCTP over IPV6" /><link rel="next" href="sub-sub-sect-igmp-esp-ah-udplite-over-ipv6.html" title="H.10.10.12. IGMP, ESP, AH, UDPLITE, 'ALL' over IPv6" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sub-sect-tcp-utp-sctp-over-ipv6.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-igmp-esp-ah-udplite-over-ipv6.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-icmpv6"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.10.11. ICMPv6</h4></div></div></div><div class="para">
+ Protocol ID: icmpv6
+ </div><div class="para">
+ The chain parameter is ignored for this type of traffic and should either be omitted or set to root.
+ </div><div class="table" id="table-icmpv6-protcol-types"><h6>Table H.13. ICMPv6 protocol types</h6><div class="table-contents"><table summary="ICMPv6 protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ srcipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ start of range of source IP address
+ </td></tr><tr><td class="">
+ scripto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ end of range of source IP address
+ </td></tr><tr><td class="">
+ dstipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of destination IP address
+ </td></tr><tr><td class="">
+ dstipto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of destination IP address
+ </td></tr><tr><td class="">
+ type
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ ICMPv6 type
+ </td></tr><tr><td class="">
+ code
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ ICMPv6 code
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr><tr><td class="">
+ state
+ </td><td class="">
+ STRING
+ </td><td class="">
+ comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE
+ </td></tr><tr><td class="">
+ ipset
+ </td><td class="">
+ STRING
+ </td><td class="">
+ The name of an IPSet managed outside of libvirt
+ </td></tr><tr><td class="">
+ ipsetflags
+ </td><td class="">
+ IPSETFLAGS
+ </td><td class="">
+ flags for the IPSet; requires ipset attribute
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-tcp-utp-sctp-over-ipv6.html"><strong>Prev</strong>H.10.10.10. TCP/UDP/SCTP over IPV6</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="sub-sub-sect-igmp-esp-ah-udplite-over-ipv6.html"><strong>Next</strong>H.10.10.12. IGMP, ESP, AH, UDPLITE, 'ALL' over IP...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-igmp-esp-ah-etc.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-igmp-esp-ah-etc.html
new file mode 100644
index 0000000..b374253
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-igmp-esp-ah-etc.html
@@ -0,0 +1,116 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.10.9. IGMP, ESP, AH, UDPLITE, 'ALL'</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-supp-pros.html" title="H.10.10. Supported protocols" /><link rel="prev" href="sub-sub-sect-icmp.html" title="H.10.10.8. ICMP" /><link rel="next" href="sub-sub-sect-tcp-utp-sctp-over-ipv6.html" title="H.10.10.10. TCP/UDP/SCTP over IPV6" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sub-sect-icmp.html"><strong>Prev</
strong></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-tcp-utp-sctp-over-ipv6.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-igmp-esp-ah-etc"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.10.9. IGMP, ESP, AH, UDPLITE, 'ALL'</h4></div></div></div><div class="para">
+ Protocol ID: igmp, esp, ah, udplite, all
+ </div><div class="para">
+ The chain parameter is ignored for this type of traffic and should either be omitted or set to root.
+ </div><div class="table" id="table-igmp-esp-ah-vars"><h6>Table H.11. IGMP, ESP, AH, UDPLITE, 'ALL'</h6><div class="table-contents"><table summary="IGMP, ESP, AH, UDPLITE, 'ALL'" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to the MAC address of the sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAD_ADDR
+ </td><td class="">
+ MAC address of the destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to the MAC address of the destination
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ srcipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ start of range of source IP address
+ </td></tr><tr><td class="">
+ scripto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ end of range of source IP address
+ </td></tr><tr><td class="">
+ dstipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of destination IP address
+ </td></tr><tr><td class="">
+ dstipto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of destination IP address
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr><tr><td class="">
+ state
+ </td><td class="">
+ STRING
+ </td><td class="">
+ comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE
+ </td></tr><tr><td class="">
+ ipset
+ </td><td class="">
+ STRING
+ </td><td class="">
+ The name of an IPSet managed outside of libvirt
+ </td></tr><tr><td class="">
+ ipsetflags
+ </td><td class="">
+ IPSETFLAGS
+ </td><td class="">
+ flags for the IPSet; requires ipset attribute
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-icmp.html"><strong>Prev</strong>H.10.10.8. ICMP</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="sub-sub-sect-tcp-utp-sctp-over-ipv6.html"><strong>Next</strong>H.10.10.10. TCP/UDP/SCTP over IPV6</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-igmp-esp-ah-udplite-over-ipv6.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-igmp-esp-ah-udplite-over-ipv6.html
new file mode 100644
index 0000000..bf5254f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-igmp-esp-ah-udplite-over-ipv6.html
@@ -0,0 +1,98 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.10.12. IGMP, ESP, AH, UDPLITE, 'ALL' over IPv6</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-supp-pros.html" title="H.10.10. Supported protocols" /><link rel="prev" href="sub-sub-sect-icmpv6.html" title="H.10.10.11. ICMPv6" /><link rel="next" href="sub-sect-adv-filt-topics.html" title="H.10.11. Advanced Filter Configuration Topics" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sub-sect-icmpv6.html"><strong
>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-adv-filt-topics.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-igmp-esp-ah-udplite-over-ipv6"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.10.12. IGMP, ESP, AH, UDPLITE, 'ALL' over IPv6</h4></div></div></div><div class="para">
+ Protocol ID: igmp-ipv6, esp-ipv6, ah-ipv6, udplite-ipv6, all-ipv6
+ </div><div class="para">
+ The chain parameter is ignored for this type of traffic and should either be omitted or set to root.
+ </div><div class="table" id="table-igmp-esp-ah-udplite-over-ipv6-vars"><h6>Table H.14. IGMP, ESP, AH, UDPLITE, 'ALL' over IPv protocol types</h6><div class="table-contents"><table summary="IGMP, ESP, AH, UDPLITE, 'ALL' over IPv protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ srcipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ start of range of source IP address
+ </td></tr><tr><td class="">
+ scripto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ end of range of source IP address
+ </td></tr><tr><td class="">
+ dstipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of destination IP address
+ </td></tr><tr><td class="">
+ dstipto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of destination IP address
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr><tr><td class="">
+ state
+ </td><td class="">
+ STRING
+ </td><td class="">
+ comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE
+ </td></tr><tr><td class="">
+ ipset
+ </td><td class="">
+ STRING
+ </td><td class="">
+ The name of an IPSet managed outside of libvirt
+ </td></tr><tr><td class="">
+ ipsetflags
+ </td><td class="">
+ IPSETFLAGS
+ </td><td class="">
+ flags for the IPSet; requires ipset attribute
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-icmpv6.html"><strong>Prev</strong>H.10.10.11. ICMPv6</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="sub-sect-adv-filt-topics.html"><strong>Next</strong>H.10.11. Advanced Filter Configuration Topics</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-lim-numb-conns.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-lim-numb-conns.html
new file mode 100644
index 0000000..2922938
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-lim-numb-conns.html
@@ -0,0 +1,43 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.11.2. Limiting Number of Connections</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-adv-filt-topics.html" title="H.10.11. Advanced Filter Configuration Topics" /><link rel="prev" href="sub-sect-adv-filt-topics.html" title="H.10.11. Advanced Filter Configuration Topics" /><link rel="next" href="sub-sub-subsect-command-line-tools.html" title="H.10.11.3. Command line tools" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 acce
sskey="p" href="sub-sect-adv-filt-topics.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-subsect-command-line-tools.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-lim-numb-conns"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.11.2. Limiting Number of Connections</h4></div></div></div><div class="para">
+ To limit the number of connections a guest may establish, a rule must be provided that sets a limit of connections for a given type of traffic. If for example a VM is supposed to be allowed to only ping one other IP address at a time and is supposed to have only one active incoming ssh connection at a time.
+ </div><div class="example" id="ex-xml-frag-limits"><h6>Example H.10. XML sample file that sets limits to connections</h6><div class="example-contents"><div class="para">
+ The following XML fragment can be used to limit connections
+ </div><pre class="screen">
+ [...]
+ <rule action='drop' direction='in' priority='400'>
+ <tcp connlimit-above='1'/>
+ </rule>
+ <rule action='accept' direction='in' priority='500'>
+ <tcp dstportstart='22'/>
+ </rule>
+ <rule action='drop' direction='out' priority='400'>
+ <icmp connlimit-above='1'/>
+ </rule>
+ <rule action='accept' direction='out' priority='500'>
+ <icmp/>
+ </rule>
+ <rule action='accept' direction='out' priority='500'>
+ <udp dstportstart='53'/>
+ </rule>
+ <rule action='drop' direction='inout' priority='1000'>
+ <all/>
+ </rule>
+ [...]
+</pre></div></div><br class="example-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Limitation rules must be listed in the XML prior to the rules for accepting traffic. According to the XML file in <a class="xref" href="sub-sub-sect-lim-numb-conns.html#ex-xml-frag-limits">Example H.10, “XML sample file that sets limits to connections”</a>, an additional rule for allowing DNS traffic sent to port 22 go out the guest, has been added to avoid ssh sessions not getting established for reasons related to DNS lookup failures by the ssh daemon. Leaving this rule out may result in the ssh client hanging unexpectedly as it tries to connect. Additional caution should be used in regards to handling timeouts related to tracking of traffic. An ICMP ping that the user may have terminated inside the guest may have a long timeout in the host's connection tracking system and will therefore not allow another ICMP ping to go through.
+ </div><div class="para">
+ The best solution is to tune the timeout in the host's <code class="filename">sysfs</code> with the following command:# <code class="command">echo 3 > /proc/sys/net/netfilter/nf_conntrack_icmp_timeout</code>. This command sets the ICMP connection tracking timeout to 3 seconds. The effect of this is that once one ping is terminated, another one can start after 3 seconds.
+ </div><div class="para">
+ If for any reason the guest has not properly closed its TCP connection, the connection to be held open for a longer period of time, especially if the TCP timeout value was set for a large amount of time on the host. In addition, any idle connection may result in a time out in the connection tracking system which can be re-activated once packets are exchanged.
+ </div><div class="para">
+ However, if the limit is set too low, newly initiated connections may force an idle connection into TCP backoff. Therefore, the limit of connections should be set rather high so that fluctuations in new TCP connections don't cause odd traffic behavior in relation to idle connections.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-adv-filt-topics.html"><strong>Prev</strong>H.10.11. Advanced Filter Configuration Topics</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="sub-sub-subsect-command-line-tools.html"><strong>Next</strong>H.10.11.3. Command line tools</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-pre-exist-net-filter.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-pre-exist-net-filter.html
new file mode 100644
index 0000000..879fa03
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-pre-exist-net-filter.html
@@ -0,0 +1,42 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.11.4. Pre-existing network filters</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-adv-filt-topics.html" title="H.10.11. Advanced Filter Configuration Topics" /><link rel="prev" href="sub-sub-subsect-command-line-tools.html" title="H.10.11.3. Command line tools" /><link rel="next" href="sub-sub-sect-write-own-filters.html" title="H.10.11.5. Writing your own filters" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 accesske
y="p" href="sub-sub-subsect-command-line-tools.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-write-own-filters.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-pre-exist-net-filter"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.11.4. Pre-existing network filters</h4></div></div></div><div class="para">
+ The following is a list of example network filters that are automatically installed with libvirt:
+ </div><div class="table" id="table-icmpv6-vars"><h6>Table H.15. ICMPv6 protocol types</h6><div class="table-contents"><table summary="ICMPv6 protocol types" border="1"><colgroup><col class="1" width="50%" /><col class="2" width="50%" /></colgroup><thead><tr><th class="">
+ Command Name
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ no-arp-spoofing
+ </td><td class="">
+ Prevents a guest from spoofing ARP traffic; this filter only allows ARP request and reply messages and enforces that those packets contain the MAC and IP addresses of the guest.
+ </td></tr><tr><td class="">
+ allow-dhcp
+ </td><td class="">
+ Allows a guest to request an IP address via DHCP (from any DHCP server)
+ </td></tr><tr><td class="">
+ allow-dhcp-server
+ </td><td class="">
+ Allows a guest to request an IP address from a specified DHCP server. The dotted decimal IP address of the DHCP server must be provided in a reference to this filter. The name of the variable must be <em class="replaceable"><code>DHCPSERVER</code></em>.
+ </td></tr><tr><td class="">
+ no-ip-spoofing
+ </td><td class="">
+ Prevents a guest from sending IP packets with a source IP address different from the one inside the packet.
+ </td></tr><tr><td class="">
+ no-ip-multicast
+ </td><td class="">
+ Prevents a guest from sending IP multicast packets.
+ </td></tr><tr><td class="">
+ clean-traffic
+ </td><td class="">
+ Prevents MAC, IP and ARP spoofing. This filter references several other filters as building blocks.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ These filters are only building blocks and require a combination with other filters to provide useful network traffic filtering. The most used one in the above list is the <em class="replaceable"><code>clean-traffic</code></em> filter. This filter itself can for example be combined with the <em class="replaceable"><code>no-ip-multicast</code></em> filter to prevent virtual machines from sending IP multicast traffic on top of the prevention of packet spoofing.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-subsect-command-line-tools.html"><strong>Prev</strong>H.10.11.3. Command line 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="sub-sub-sect-write-own-filters.html"><strong>Next</strong>H.10.11.5. Writing your own filters</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-prot-ARP-RARP-explained.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-prot-ARP-RARP-explained.html
new file mode 100644
index 0000000..6f2fd60
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-prot-ARP-RARP-explained.html
@@ -0,0 +1,98 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.10.4. ARP/RARP</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-supp-pros.html" title="H.10.10. Supported protocols" /><link rel="prev" href="sub-sub-sect-prot-STP-explained.html" title="H.10.10.3. STP (Spanning Tree Protocol)" /><link rel="next" href="sub-sub-sect-prot-Ipv4-explained.html" title="H.10.10.5. IPv4" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sub-sect-prot-STP-
explained.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-prot-Ipv4-explained.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-prot-ARP-RARP-explained"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.10.4. ARP/RARP</h4></div></div></div><div class="para">
+ Protocol ID: arp or rarp
+ </div><div class="para">
+ Rules of this type should either go into the root or arp/rarp chain.
+ </div><div class="table" id="table-arp-vars"><h6>Table H.6. ARP and RARP protocol types</h6><div class="table-contents"><table summary="ARP and RARP protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of destination
+ </td></tr><tr><td class="">
+ hwtype
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Hardware type
+ </td></tr><tr><td class="">
+ protocoltype
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Protocol type
+ </td></tr><tr><td class="">
+ opcode
+ </td><td class="">
+ UINT16, STRING
+ </td><td class="">
+ Opcode valid strings are: Request, Reply, Request_Reverse, Reply_Reverse, DRARP_Request, DRARP_Reply, DRARP_Error, InARP_Request, ARP_NAK
+ </td></tr><tr><td class="">
+ arpsrcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ Source MAC address in ARP/RARP packet
+ </td></tr><tr><td class="">
+ arpdstmacaddr
+ </td><td class="">
+ MAC _ADDR
+ </td><td class="">
+ Destination MAC address in ARP/RARP packet
+ </td></tr><tr><td class="">
+ arpsrcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address in ARP/RARP packet
+ </td></tr><tr><td class="">
+ arpdstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address in ARP/RARP packet
+ </td></tr><tr><td class="">
+ gratututous
+ </td><td class="">
+ BOOLEAN
+ </td><td class="">
+ Boolean indiating whether to check for a gratuitous ARP packet
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-prot-STP-explained.html"><strong>Prev</strong>H.10.10.3. STP (Spanning Tree Protocol) </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="sub-sub-sect-prot-Ipv4-explained.html"><strong>Next</strong>H.10.10.5. IPv4</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-prot-Ipv4-explained.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-prot-Ipv4-explained.html
new file mode 100644
index 0000000..00480f7
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-prot-Ipv4-explained.html
@@ -0,0 +1,104 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.10.5. IPv4</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-supp-pros.html" title="H.10.10. Supported protocols" /><link rel="prev" href="sub-sub-sect-prot-ARP-RARP-explained.html" title="H.10.10.4. ARP/RARP" /><link rel="next" href="sub-sub-sect-chars-IPv6.html" title="H.10.10.6. IPv6" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sub-sect-prot-ARP-RARP-explained.html"><st
rong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-chars-IPv6.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-prot-Ipv4-explained"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.10.5. IPv4</h4></div></div></div><div class="para">
+ Protocol ID: ip
+ </div><div class="para">
+ Rules of this type should either go into the root or ipv4 chain.
+ </div><div class="table" id="table-ipv4-vars"><h6>Table H.7. IPv4 protocol types</h6><div class="table-contents"><table summary="IPv4 protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of destination
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ protocol
+ </td><td class="">
+ UINT8, STRING
+ </td><td class="">
+ Layer 4 protocol identifier. Valid strings for protocol are: tcp, udp, udplite, esp, ah, icmp, igmp, sctp
+ </td></tr><tr><td class="">
+ srcportstart
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Start of range of valid source ports; requires protocol
+ </td></tr><tr><td class="">
+ srcportend
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ End of range of valid source ports; requires protocol
+ </td></tr><tr><td class="">
+ dstportstart
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ Start of range of valid destination ports; requires protocol
+ </td></tr><tr><td class="">
+ dstportend
+ </td><td class="">
+ UNIT16
+ </td><td class="">
+ End of range of valid destination ports; requires protocol
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-prot-ARP-RARP-explained.html"><strong>Prev</strong>H.10.10.4. ARP/RARP</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="sub-sub-sect-chars-IPv6.html"><strong>Next</strong>H.10.10.6. IPv6</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-prot-STP-explained.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-prot-STP-explained.html
new file mode 100644
index 0000000..08c2f95
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-prot-STP-explained.html
@@ -0,0 +1,158 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.10.3. STP (Spanning Tree Protocol)</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-supp-pros.html" title="H.10.10. Supported protocols" /><link rel="prev" href="sub-sub-sect-vlan.html" title="H.10.10.2. VLAN (802.1Q)" /><link rel="next" href="sub-sub-sect-prot-ARP-RARP-explained.html" title="H.10.10.4. ARP/RARP" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sub-sect-vlan.html"><strong>Prev</stron
g></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-prot-ARP-RARP-explained.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-prot-STP-explained"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.10.3. STP (Spanning Tree Protocol) </h4></div></div></div><div class="para">
+ Protocol ID: stp
+ </div><div class="para">
+ Rules of this type should go either into the root or stp chain.
+ </div><div class="table" id="table-stp-vars"><h6>Table H.5. STP protocol types</h6><div class="table-contents"><table summary="STP protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of sender
+ </td></tr><tr><td class="">
+ type
+ </td><td class="">
+ UINT8
+ </td><td class="">
+ Bridge Protocol Data Unit (BPDU) type
+ </td></tr><tr><td class="">
+ flags
+ </td><td class="">
+ UINT8
+ </td><td class="">
+ BPDU flagdstmacmask
+ </td></tr><tr><td class="">
+ root-priority
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Root priority range start
+ </td></tr><tr><td class="">
+ root-priority-hi
+ </td><td class="">
+ UINT16 (0x0-0xfff, 0 - 4095)
+ </td><td class="">
+ Root priority range end
+ </td></tr><tr><td class="">
+ root-address
+ </td><td class="">
+ MAC _ADDRESS
+ </td><td class="">
+ root MAC Address
+ </td></tr><tr><td class="">
+ root-address-mask
+ </td><td class="">
+ MAC _MASK
+ </td><td class="">
+ root MAC Address mask
+ </td></tr><tr><td class="">
+ roor-cost
+ </td><td class="">
+ UINT32
+ </td><td class="">
+ Root path cost (range start)
+ </td></tr><tr><td class="">
+ root-cost-hi
+ </td><td class="">
+ UINT32
+ </td><td class="">
+ Root path cost range end
+ </td></tr><tr><td class="">
+ sender-priority-hi
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Sender prioriry range end
+ </td></tr><tr><td class="">
+ sender-address
+ </td><td class="">
+ MAC_ADDRESS
+ </td><td class="">
+ BPDU sender MAC address
+ </td></tr><tr><td class="">
+ sender-address-mask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ BPDU sender MAC address mask
+ </td></tr><tr><td class="">
+ port
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Port identifier (range start)
+ </td></tr><tr><td class="">
+ port_hi
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Port identifier range end
+ </td></tr><tr><td class="">
+ msg-age
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Message age timer (range start)
+ </td></tr><tr><td class="">
+ msg-age-hi
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Message age timer range end
+ </td></tr><tr><td class="">
+ max-age-hi
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Maximum age time range end
+ </td></tr><tr><td class="">
+ hello-time
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Hello time timer (range start)
+ </td></tr><tr><td class="">
+ hello-time-hi
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Hello time timer range end
+ </td></tr><tr><td class="">
+ forward-delay
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Forward delay (range start)
+ </td></tr><tr><td class="">
+ forward-delay-hi
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Forward delay range end
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-vlan.html"><strong>Prev</strong>H.10.10.2. VLAN (802.1Q)</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="sub-sub-sect-prot-ARP-RARP-explained.html"><strong>Next</strong>H.10.10.4. ARP/RARP</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-samp-filter.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-samp-filter.html
new file mode 100644
index 0000000..66d7afa
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-samp-filter.html
@@ -0,0 +1,146 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.11.6. Sample custom filter</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-adv-filt-topics.html" title="H.10.11. Advanced Filter Configuration Topics" /><link rel="prev" href="sub-sub-sect-write-own-filters.html" title="H.10.11.5. Writing your own filters" /><link rel="next" href="sub-sect-limitations-filters-network-subsystem.html" title="H.10.12. Limitations" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 acces
skey="p" href="sub-sub-sect-write-own-filters.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sect-limitations-filters-network-subsystem.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-samp-filter"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.11.6. Sample custom filter</h4></div></div></div><div class="para">
+ Although one of the rules in the above XML contains the IP address of the guest as either a source or a destination address, the filtering of the traffic works correctly. The reason is that whereas the rule's evaluation occurrs internally on a per-interface basis, the rules are additionaly evaluated based on which (tap) interface has sent or will receive the packet, rather than what their source or destination IP address may be.
+ </div><div class="example"><h6>Example H.12. Sample XML for network interface descriptions</h6><div class="example-contents"><div class="para">
+ An XML fragment for a possible network interface description inside the domain XML of the test guest could then look like this:
+ </div><pre class="screen">
+ [...]
+ <interface type='bridge'>
+ <source bridge='mybridge'/>
+ <filterref filter='test-eth0'/>
+ </interface>
+ [...]
+</pre><div class="para">
+ To more strictly control the ICMP traffic and enforce that only ICMP echo requests can be sent from the guest and only ICMP echo responses be received by the guest, the above ICMP rule can be replaced with the following two rules:
+ </div><pre class="screen">
+ <!- - enable outgoing ICMP echo requests- ->
+ <rule action='accept' direction='out'>
+ <icmp type='8'/>
+ </rule>
+</pre><pre class="screen">
+ <!- - enable incoming ICMP echo replies- ->
+ <rule action='accept' direction='in'>
+ <icmp type='0'/>
+ </rule>
+</pre></div></div><br class="example-break" /><div class="example"><h6>Example H.13. Second example custom filter</h6><div class="example-contents"><div class="para">
+ This example demonstrates how to build a similar filter as in the example above, but extends the list of requirements with an ftp server located inside the guest. The requirements for this filter are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ prevents a guest's interface from MAC, IP, and ARP spoofing
+ </div></li><li class="listitem"><div class="para">
+ opens only TCP ports 22 and 80 in a guest's interface
+ </div></li><li class="listitem"><div class="para">
+ allows the guest to send ping traffic from an interface but does not allow the guest to be pinged on the interface
+ </div></li><li class="listitem"><div class="para">
+ allows the guest to do DNS lookups (UDP towards port 53)
+ </div></li><li class="listitem"><div class="para">
+ enables the ftp server (in active mode) so it can run inside the guest
+ </div></li></ul></div><div class="para">
+ The additional requirement of allowing an FTP server to be run inside the guest maps into the requirement of allowing port 21 to be reachable for FTP control traffic as well as enabling the guest to establish an outgoing TCP connection originating from the guest's TCP port 20 back to the FTP client (FTP active mode). There are several ways of how this filter can be written and two possible solutions are included in this example.
+ </div><div class="para">
+ The first solution makes use of the state attribute of the TCP protocol that provides a hook into the connection tracking framework of the Linux host. For the guest-initiated FTP data connection (FTP active mode) the RELATED state is used to enable detection that the guest-initiated FTP data connection is a consequence of ( or 'has a relationship with' ) an existing FTP control connection, thereby allowing it to pass packets through the firewall. The RELATED state, however, is only valid for the very first packet of the outgoing TCP connection for the FTP data path. Afterwards, the state is ESTABLISHED, which then applies equally to the incoming and outgoing direction. All this is related to the FTP data traffic originating from TCP port 20 of the guest. This then leads to the following solution:
+ </div><pre class="screen">
+<filter name='test-eth0'>
+ <!- - This filter (eth0) references the <code class="filename">clean traffic</code> filter to prevent MAC, IP, and ARP spoofing. By not providing an IP address parameter, libvirt will detect the IP address the guest is using. - ->
+ <filterref filter='clean-traffic'/>
+
+ <!- - This rule enables TCP port 21 (FTP-control) to be reachable - ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='21'/>
+ </rule>
+
+ <!- - This rule enables TCP port 20 for guest-initiated FTP data connection related to an existing FTP control connection - ->
+ <rule action='accept' direction='out'>
+ <tcp srcportstart='20' state='RELATED,ESTABLISHED'/>
+ </rule>
+
+ <!- - This rule accepts all packets from a client on the FTP data connection - ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='20' state='ESTABLISHED'/>
+ </rule>
+
+ <!- - This rule enables TCP port 22 (SSH) to be reachable - ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='22'/>
+ </rule>
+
+ <!- -This rule enables TCP port 80 (HTTP) to be reachable - ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='80'/>
+ </rule>
+
+ <!- - This rule enables general ICMP traffic to be initiated by the guest, including ping traffic - ->
+ <rule action='accept' direction='out'>
+ <icmp/>
+ </rule>
+
+ <!- - This rule enables outgoing DNS lookups using UDP - ->
+ <rule action='accept' direction='out'>
+ <udp dstportstart='53'/>
+ </rule>
+
+ <!- - This rule drops all other traffic - ->
+ <rule action='drop' direction='inout'>
+ <all/>
+ </rule>
+
+</filter>
+</pre><div class="para">
+ Before trying out a filter using the RELATED state, you have to make sure that the appropriate connection tracking module has been loaded into the host's kernel. Depending on the version of the kernel, you must run either one of the following two commands before the FTP connection with the guest is established:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ #<code class="command">modprobe nf_conntrack_ftp</code> - where available OR
+ </div></li><li class="listitem"><div class="para">
+ #<code class="command">modprobe ip_conntrack_ftp</code> if above is not available
+ </div></li></ul></div><div class="para">
+ If protocols other than FTP are used in conjunction with the RELATED state, their corresponding module must be loaded. Modules are available for the protocols: ftp, tftp, irc, sip, sctp, and amanda.
+ </div><div class="para">
+ The second solution makes use of the state flags of connections more than the previous solution did. This solution takes advantage of the fact that the NEW state of a connection is valid when the very first packet of a traffic flow is detected. Subsequently, if the very first packet of a flow is accepted, the flow becomes a connection and thus enters into the ESTABLISHED state. Therefore a general rule can be written for allowing packets of ESTABLISHED connections to reach the guest or be sent by the guest. This is done writing specific rules for the very first packets identified by the NEW state and dictates the ports that the data is acceptable. All packets meant for ports that are not explicitly accepted are dropped, thus not reaching an ESTABLISHED state. Any subsequent packets sent from that port are dropped as well.
+ </div><pre class="screen">
+<filter name='test-eth0'>
+ <!- - This filter references the <code class="filename">clean traffic</code> filter to prevent MAC, IP and ARP spoofing. By not providing and IP address parameter, libvirt will detect the IP address the VM is using. - ->
+ <filterref filter='clean-traffic'/>
+
+ <!- - This rule allows the packets of all previously accepted connections to reach the guest - ->
+ <rule action='accept' direction='in'>
+ <all state='ESTABLISHED'/>
+ </rule>
+
+ <!- - This rule allows the packets of all previously accepted and related connections be sent from the guest - ->
+ <rule action='accept' direction='out'>
+ <all state='ESTABLISHED,RELATED'/>
+ </rule>
+
+ <!- - This rule enables traffic towards port 21 (FTP) and port 22 (SSH)- ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='21' dstportend='22' state='NEW'/>
+ </rule>
+
+ <!- - This rule enables traffic towards port 80 (HTTP) - ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='80' state='NEW'/>
+ </rule>
+
+ <!- - This rule enables general ICMP traffic to be initiated by the guest, including ping traffic - ->
+ <rule action='accept' direction='out'>
+ <icmp state='NEW'/>
+ </rule>
+
+ <!- - This rule enables outgoing DNS lookups using UDP - ->
+ <rule action='accept' direction='out'>
+ <udp dstportstart='53' state='NEW'/>
+ </rule>
+
+ <!- - This rule drops all other traffic - ->
+ <rule action='drop' direction='inout'>
+ <all/>
+ </rule>
+
+</filter>
+</pre></div></div><br class="example-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-write-own-filters.html"><strong>Prev</strong>H.10.11.5. Writing your own filters</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="sub-sect-limitations-filters-network-subsystem.html"><strong>Next</strong>H.10.12. Limitations</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-tcp-utp-sctp-over-ipv6.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-tcp-utp-sctp-over-ipv6.html
new file mode 100644
index 0000000..2db9b99
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-tcp-utp-sctp-over-ipv6.html
@@ -0,0 +1,122 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.10.10. TCP/UDP/SCTP over IPV6</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-supp-pros.html" title="H.10.10. Supported protocols" /><link rel="prev" href="sub-sub-sect-igmp-esp-ah-etc.html" title="H.10.10.9. IGMP, ESP, AH, UDPLITE, 'ALL'" /><link rel="next" href="sub-sub-sect-icmpv6.html" title="H.10.10.11. ICMPv6" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sub-sect-igmp-esp-ah-etc.html"
><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-icmpv6.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-tcp-utp-sctp-over-ipv6"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.10.10. TCP/UDP/SCTP over IPV6</h4></div></div></div><div class="para">
+ Protocol ID: tcp-ipv6, udp-ipv6, sctp-ipv6
+ </div><div class="para">
+ The chain parameter is ignored for this type of traffic and should either be omitted or set to root.
+ </div><div class="table" id="table-tcp-udp-over-IPv6-vars"><h6>Table H.12. TCP, UDP, SCTP over IPv6 protocol types</h6><div class="table-contents"><table summary="TCP, UDP, SCTP over IPv6 protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Source IP address
+ </td></tr><tr><td class="">
+ srcipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to source IP address
+ </td></tr><tr><td class="">
+ dstipaddr
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Destination IP address
+ </td></tr><tr><td class="">
+ dstipmask
+ </td><td class="">
+ IP_MASK
+ </td><td class="">
+ Mask applied to destination IP address
+ </td></tr><tr><td class="">
+ srcipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ start of range of source IP address
+ </td></tr><tr><td class="">
+ scripto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ end of range of source IP address
+ </td></tr><tr><td class="">
+ dstipfrom
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ Start of range of destination IP address
+ </td></tr><tr><td class="">
+ dstipto
+ </td><td class="">
+ IP_ADDR
+ </td><td class="">
+ End of range of destination IP address
+ </td></tr><tr><td class="">
+ srcportstart
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Start of range of valid source ports
+ </td></tr><tr><td class="">
+ srcportend
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ End of range of valid source ports
+ </td></tr><tr><td class="">
+ dstportstart
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ Start of range of valid destination ports
+ </td></tr><tr><td class="">
+ dstportend
+ </td><td class="">
+ UINT16
+ </td><td class="">
+ End of range of valid destination ports
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr><tr><td class="">
+ state
+ </td><td class="">
+ STRING
+ </td><td class="">
+ comma separated list of NEW,ESTABLISHED,RELATED,INVALID or NONE
+ </td></tr><tr><td class="">
+ ipset
+ </td><td class="">
+ STRING
+ </td><td class="">
+ The name of an IPSet managed outside of libvirt
+ </td></tr><tr><td class="">
+ ipsetflags
+ </td><td class="">
+ IPSETFLAGS
+ </td><td class="">
+ flags for the IPSet; requires ipset attribute
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-igmp-esp-ah-etc.html"><strong>Prev</strong>H.10.10.9. IGMP, ESP, AH, UDPLITE, 'ALL'</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="sub-sub-sect-icmpv6.html"><strong>Next</strong>H.10.10.11. ICMPv6</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-vlan.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-vlan.html
new file mode 100644
index 0000000..c327c28
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-vlan.html
@@ -0,0 +1,62 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.10.2. VLAN (802.1Q)</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-supp-pros.html" title="H.10.10. Supported protocols" /><link rel="prev" href="sub-sect-supp-pros.html" title="H.10.10. Supported protocols" /><link rel="next" href="sub-sub-sect-prot-STP-explained.html" title="H.10.10.3. STP (Spanning Tree Protocol)" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sect-supp-pros.html
"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-prot-STP-explained.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-vlan"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.10.2. VLAN (802.1Q)</h4></div></div></div><div class="para">
+ Protocol ID: vlan
+ </div><div class="para">
+ Rules of this type should go either into the root or vlan chain.
+ </div><div class="table" id="table-vlan-vars"><h6>Table H.4. VLAN protocol types</h6><div class="table-contents"><table summary="VLAN protocol types" border="1"><colgroup><col class="1" width="33%" /><col class="2" width="33%" /><col class="3" width="33%" /></colgroup><thead><tr><th class="">
+ Attribute Name
+ </th><th class="">
+ Datatype
+ </th><th class="">
+ Definition
+ </th></tr></thead><tbody><tr><td class="">
+ srcmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of sender
+ </td></tr><tr><td class="">
+ srcmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of sender
+ </td></tr><tr><td class="">
+ dstmacaddr
+ </td><td class="">
+ MAC_ADDR
+ </td><td class="">
+ MAC address of destination
+ </td></tr><tr><td class="">
+ dstmacmask
+ </td><td class="">
+ MAC_MASK
+ </td><td class="">
+ Mask applied to MAC address of destination
+ </td></tr><tr><td class="">
+ vlan-id
+ </td><td class="">
+ UINT16 (0x0-0xfff, 0 - 4095)
+ </td><td class="">
+ VLAN ID
+ </td></tr><tr><td class="">
+ encap-protocol
+ </td><td class="">
+ UINT16 (0x03c-0xfff), String
+ </td><td class="">
+ Encapsulated layer 3 protocol ID, valid strings are arp, ipv4, ipv6
+ </td></tr><tr><td class="">
+ comment
+ </td><td class="">
+ STRING
+ </td><td class="">
+ text string up to 256 characters
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sect-supp-pros.html"><strong>Prev</strong>H.10.10. Supported protocols</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="sub-sub-sect-prot-STP-explained.html"><strong>Next</strong>H.10.10.3. STP (Spanning Tree Protocol) </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-write-own-filters.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-write-own-filters.html
new file mode 100644
index 0000000..f8f3c8d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-sect-write-own-filters.html
@@ -0,0 +1,80 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.11.5. Writing your own filters</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-adv-filt-topics.html" title="H.10.11. Advanced Filter Configuration Topics" /><link rel="prev" href="sub-sub-sect-pre-exist-net-filter.html" title="H.10.11.4. Pre-existing network filters" /><link rel="next" href="sub-sub-sect-samp-filter.html" title="H.10.11.6. Sample custom filter" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sub-sect-pre-exist-net-filter.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-samp-filter.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-sect-write-own-filters"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.11.5. Writing your own filters</h4></div></div></div><div class="para">
+ Since libvirt only provides a couple of example networking filters, you may consider writing your own. When planning on doing so there are a couple of things you may need to know regarding the network filtering subsystem and how it works internally. Certainly you also have to know and understand the protocols very well that you want to be filtering on so that no further traffic than what you want can pass and that in fact the traffic you want to allow does pass.
+ </div><div class="para">
+ The network filtering subsystem is currently only available on Linux hosts and only works for Qemu and KVM type of virtual machines. On Linux, it builds upon the support for ebtables, iptables and ip6tables and makes use of their features. Considering the list found in <a class="xref" href="sub-sect-supp-pros.html">Section H.10.10, “Supported protocols”</a> the following protolcols can be implemented using ebtables:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ mac
+ </div></li><li class="listitem"><div class="para">
+ stp (spanning tree protocol)
+ </div></li><li class="listitem"><div class="para">
+ vlan (802.1Q)
+ </div></li><li class="listitem"><div class="para">
+ arp, rarp
+ </div></li><li class="listitem"><div class="para">
+ ipv4
+ </div></li><li class="listitem"><div class="para">
+ ipv6
+ </div></li></ul></div><div class="para">
+ Any protocol that runs over IPv4 is supported using iptables, those over IPv6 are implemented using ip6tables.
+ </div><div class="para">
+ Using a Linux host, all traffic filtering rules created by libvirt's network filtering subsystem first passes through the filtering support implemented by ebtables and only afterwards through iptables or ip6tables filters. If a filter tree has rules with the protocols including: mac, stp, vlan arp, rarp, ipv4, or ipv6; the ebtable rules and values listed will automatically be used first.
+ </div><div class="para">
+ Multiple chains for the same protocol can be created. The name of the chain must have a prefix of one of the previously enumerated protocols. To create an additional chain for handling of ARP traffic, a chain with name arp-test, can for example be specified.
+ </div><div class="para">
+ As an example, it is possible to filter on UDP traffic by source and destination ports using the ip protocol filter and specifying attributes for the protocol, source and destination IP addresses and ports of UDP packets that are to be accepted. This allows early filtering of UDP traffic with ebtables. However, once an IP or IPv6 packet, such as a UDP packet, has passed the ebtables layer and there is at least one rule in a filter tree that instantiates iptables or ip6tables rules, a rule to let the UDP packet pass will also be necessary to be provided for those filtering layers. This can be achieved with a rule containing an appropriate udp or udp-ipv6 traffic filtering node.
+ </div><div class="example"><h6>Example H.11. Creating a custom filter</h6><div class="example-contents"><div class="para">
+ Suppose a filter is needed to fulfill the following list of requirements:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ prevents a VM's interface from MAC, IP and ARP spoofing
+ </div></li><li class="listitem"><div class="para">
+ opens only TCP ports 22 and 80 of a VM's interface
+ </div></li><li class="listitem"><div class="para">
+ allows the VM to send ping traffic from an interface but not let the VM be pinged on the interface
+ </div></li><li class="listitem"><div class="para">
+ allows the VM to do DNS lookups (UDP towards port 53)
+ </div></li></ul></div><div class="para">
+ The requirement to prevent spoofing is fulfilled by the existing <em class="parameter"><code>clean-traffic</code></em> network filter, thus the way to do this is to reference it from a custom filter.
+ </div><div class="para">
+ To enable traffic for TCP ports 22 and 80, two rules are added to enable this type of traffic. To allow the guest to send ping traffic a rule is added for ICMP traffic. For simplicity reasons, general ICMP traffic will be allowed to be initated from the guest, and will not be specified to ICMP echo request and response messages. All other traffic will be prevented to reach or be initated by the guest. To do this a rule will be added that drops all other traffic. Assuming the guest is called <code class="filename">test</code> and the interface to associate our filter with is called <code class="filename">eth0</code>, a filter is created named <code class="filename">test-eth0</code>.
+ </div><div class="para">
+ The result of these considerations is the following network filter XML:
+ </div><pre class="screen">
+<filter name='test-eth0'>
+ <!- - This rule references the clean traffic filter to prevent MAC, IP and ARP spoofing. By not providing an IP address parameter, libvirt will detect the IP address the guest is using. - ->
+ <filterref filter='clean-traffic'/>
+
+ <!- - This rule enables TCP ports 22 (ssh) and 80 (http) to be reachable - ->
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='22'/>
+ </rule>
+
+ <rule action='accept' direction='in'>
+ <tcp dstportstart='80'/>
+ </rule>
+
+ <!- - This rule enables general ICMP traffic to be initiated by the guest including ping traffic - ->
+ <rule action='accept' direction='out'>
+ <icmp/>
+ </rule>>
+
+ <!- - This rule enables outgoing DNS lookups using UDP - ->
+ <rule action='accept' direction='out'>
+ <udp dstportstart='53'/>
+ </rule>
+
+ <!- - This rule drops all other traffic - ->
+ <rule action='drop' direction='inout'>
+ <all/>
+ </rule>
+
+</filter>
+</pre></div></div><br class="example-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-pre-exist-net-filter.html"><strong>Prev</strong>H.10.11.4. Pre-existing network filters</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="sub-sub-sect-samp-filter.html"><strong>Next</strong>H.10.11.6. Sample custom filter</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-boot-order.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-boot-order.html
new file mode 100644
index 0000000..5371c07
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-boot-order.html
@@ -0,0 +1,25 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.11. Specifying boot order</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element.html" title="J.16.9.10. Overriding the target element" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-interface-ROM-BIOS-configuration.html" title="J.16.9.12. Interface ROM BIOS configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-interface-ROM-BIOS-configuration.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-boot-order"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.11. Specifying boot order</h4></div></div></div><div class="para">
+ To specify the boot order, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig--libvirt-dom-xml-devices-Network-interfaces-boot-order"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><boot</span><span class="perl_Others"> order=</span><span class="perl_String">'1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.49. Specifying boot order</h6></div><br class="figure-break" /><div class="para">
+ For hypervisors which support it, you can set a specific NIC to be used for the network boot. The order of attributes determine the order in which devices will be tried during boot sequence. Note that the per-device boot elements cannot be used together with general boot elements in BIOS bootloader section.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element.html"><strong>Prev</strong>J.16.9.10. Overriding the target element</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="sub-sub-section-libvirt-dom-xml-devices-interface-ROM-BIOS-configuration.html"><strong>Next</strong>J.16.9.12. Interface ROM BIOS configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-bridge-to-lan.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-bridge-to-lan.html
new file mode 100644
index 0000000..001d770
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-bridge-to-lan.html
@@ -0,0 +1,37 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.2. Bridge to LAN</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-userspace-slirp-stack.html" title="J.16.9.3. Userspace SLIRP stack" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-section-libvirt-dom-xml-devices-Network-interfaces.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-userspace-slirp-stack.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-bridge-to-lan"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.2. Bridge to LAN</h4></div></div></div><div class="para">
+ Note that this is the recommended configuration setting for general guest connectivity on hosts with static wired networking configurations.
+ </div><div class="para">
+ Bridge to LAN provides a bridge from the guest virtual machine directly onto the LAN. This assumes there is a bridge device on the host which has one or more of the hosts physical NICs enslaved. The guest virtual machine will have an associated <code class="sgmltag-attribute">tun</code> device created with a name of <code class="sgmltag-starttag"><vnetN></code>, which can also be overridden with the <code class="sgmltag-starttag"><target></code> element (refer to <a class="xref" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element.html">Section J.16.9.10, “Overriding the target element”</a>). The <code class="sgmltag-starttag"><tun></code> device will be enslaved to the bridge. The IP range / network configuration is whatever is used on the LAN. This provides the guest virtual machine full incoming and outgoing net access just like a physical machine.
+ </div><div class="para">
+ On Linux systems, the bridge device is normally a standard Linux host bridge. On hosts that support Open vSwitch, it is also possible to connect to an open vSwitch bridge device by adding a <code class="sgmltag-attribute">virtualport type='openvswitch'/</code> to the interface definition. The Open vSwitch type virtualport accepts two parameters in its <code class="sgmltag-element">parameters</code> element - an <code class="sgmltag-element">interfaceid</code> which is a standard uuid used to uniquely identify this particular interface to Open vSwitch (if you do no specify one, a random <code class="sgmltag-attribute">interfaceid</code> will be generated for you when you first define the interface), and an optional <code class="sgmltag-element">profileid</code> which is sent to Open vSwitch as the interfaces <code class="sgmltag-starttag"><port-profile></code>. To set the bridge to LAN settings, use a managment tool that will configure the following part of the dom
ain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-br2lan"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'bridge'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> bridge=</span><span class="perl_String">'br0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'bridge'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> bridge=</span><span class="perl_String">'br1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet7'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">"00:11:22:33:44:55"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'bridge'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> bridge=</span><span class="perl_String">'ovsbr'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><virtualport</span><span class="perl_Others"> type=</span><span class="perl_String">'openvswitch'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><parameters</span><span class="perl_Others"> profileid=</span><span class="perl_String">'menial'</span><span class="perl_Others"> interfaceid=</span><span class="perl_String">'09b11c53-8b5c-4eeb-8f00-d84eaa0aaa4f'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></virtualport></span>
+ <span class="perl_Keyword"></interface></span>
+ ...
+ <span class="perl_Keyword"></devices></span>
+</pre></div><h6>Figure J.38. Devices - network interfaces- bridge to LAN</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html"><strong>Prev</strong>J.16.9. Network interfaces</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="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-userspace-slirp-stack.html"><strong>Next</strong>J.16.9.3. Userspace SLIRP stack</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-direct-attachment-to-physical-device.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-direct-attachment-to-physical-device.html
new file mode 100644
index 0000000..ca5da1d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-direct-attachment-to-physical-device.html
@@ -0,0 +1,114 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.5. Direct attachment to physical interfaces</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-generic-ethernet-connection.html" title="J.16.9.4. Generic Ethernet connection" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-pci-passthrough.html" title="J.16.9.6. PCI passthrough" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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/image
s/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-generic-ethernet-connection.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-pci-passthrough.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-direct-attachment-to-physical-device"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.5. Direct attachment to physical interfaces</h4></div></div></div><div class="para">
+ Manipulating the direct attachment to physical interfaces provides direct attachment of the guest virtual machine's NIC to the given taht the physial interface of the host is specified.
+ </div><div class="para">
+ This setup requires the Linux macvtap driver to be available. One of the modes <code class="sgmltag-element">vepa</code> ( 'Virtual Ethernet Port Aggregator'), <code class="sgmltag-element">bridge</code> or <code class="sgmltag-element">private</code> can be chosen for the operation mode of the macvtap device, <code class="sgmltag-element">vepa</code> being the default mode.
+ </div><div class="para">
+ Manipulating direct attachment to physical interfaces involves setting the following parameters in the following part of the domain XML.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-dir-att-2phys"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'direct'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> dev=</span><span class="perl_String">'eth0'</span><span class="perl_Others"> mode=</span><span class="perl_String">'vepa'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.41. Devices - network interfaces- direct attachment to physical interfaces</h6></div><br class="figure-break" /><div class="para">
+ The individual modes cause the delivery of packets to behave as shown in <a class="xref" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-direct-attachment-to-physical-device.html#table-libvirt-dom-xml-gen-direct-attachment-physical-interface">Table J.17, “Direct attachment to physical interface elements”</a>:
+ </div><div class="table" id="table-libvirt-dom-xml-gen-direct-attachment-physical-interface"><h6>Table J.17. Direct attachment to physical interface elements</h6><div class="table-contents"><table summary="Direct attachment to physical interface elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-attribute">vepa</code>
+ </td><td class="">
+ All of the guest virtual machines' packets are sent to the external bridge. Packets whose destination is a guest virtual machine on the same host as where the packet originates from are sent back to the host by the VEPA capable bridge (today's bridges are typically not VEPA capable).
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">bridge</code>
+ </td><td class="">
+ Packets whose destination is on the same host as where they originate from are directly delivered to the target macvtap device. Both origin and destination devices need to be in bridge mode for direct delivery. If either one of them is in <code class="sgmltag-attribute">vepa</code> mode, a VEPA capable bridge is required.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">private</code>
+ </td><td class="">
+ All packets are sent to the external bridge and will only be delivered to a target VM on the same host if they are sent through an external router or gateway and that device sends them back to the host. This procedure is followed if either the source or destination device is in private mode.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">passthrough</code>
+ </td><td class="">
+ This feature attaches a virtual function of a SRIOV capable NIC directly to a guest virtual machine without losing the migration capability. All packets are sent to the VF/IF of the configured network device. Depending on the capabilities of the device additional prerequisites or limitations may apply; for example, this requires kernel 2.6.38 or newer.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The network access of direct attached virtual machines can be managed by the hardware switch to which the physical interface of the host machine is connected to.
+ </div><div class="para">
+ The interface can have additional parameters as shown below, if the switch is conforming to the IEEE 802.1Qbg standard. The parameters of the virtualport element are documented in more detail in the IEEE 802.1Qbg standard. The values are network specific and should be provided by the network administrator. In 802.1Qbg terms, the Virtual Station Interface (VSI) represents the virtual interface of a virtual machine.
+ </div><div class="para">
+ Note that IEEE 802.1Qbg requires a non-zero value for the VLAN ID.
+ </div><div class="para">
+ Additional elements that can be manipulated are described in <a class="xref" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-direct-attachment-to-physical-device.html#table-libvirt-dom-xml-gen-direct-attachment-physical-interface2">Table J.18, “Direct attachment to physical interface additional elements”</a>:
+ </div><div class="table" id="table-libvirt-dom-xml-gen-direct-attachment-physical-interface2"><h6>Table J.18. Direct attachment to physical interface additional elements</h6><div class="table-contents"><table summary="Direct attachment to physical interface additional elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Element
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-attribute">managerid</code>
+ </td><td class="">
+ The VSI Manager ID identifies the database containing the VSI type and instance definitions. This is an integer value and the value <code class="sgmltag-element">0</code> is reserved.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">typeid</code>
+ </td><td class="">
+ The VSI Type ID identifies a VSI type characterizing the network access. VSI types are typically managed by network administrator. This is an integer value.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">typeidversion</code>
+ </td><td class="">
+ The VSI Type Version allows multiple versions of a VSI Type. This is an integer value.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">instanceid</code>
+ </td><td class="">
+ The VSI Instance ID Identifier is generated when a VSI instance (i.e. a virtual interface of a virtual machine) is created. This is a globally unique identifier.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">profileid</code>
+ </td><td class="">
+ The profile ID contains the name of the port profile that is to be applied onto this interface. This name is resolved by the port profile database into the network parameters from the port profile, and those network parameters will be applied to this interface.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Additional parameters in the domain XML include:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-dir-att-2phys2"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'direct'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> dev=</span><span class="perl_String">'eth0.2'</span><span class="perl_Others"> mode=</span><span class="perl_String">'vepa'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><virtualport</span><span class="perl_Others"> type=</span><span class="perl_String">"802.1Qbg"</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><parameters</span><span class="perl_Others"> managerid=</span><span class="perl_String">"11"</span><span class="perl_Others"> typeid=</span><span class="perl_String">"1193047"</span><span class="perl_Others"> typeidversion=</span><span class="perl_String">"2"</span><span class="perl_Others"> instanceid=</span><span class="perl_String">"09b11c53-8b5c-4eeb-8f00-d84eaa0aaa4f"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></virtualport></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.42. Devices - network interfaces- direct attachment to physical interfaces additional parameters</h6></div><br class="figure-break" /><div class="para">
+ The interface can have additional parameters as shown below if the switch is conforming to the IEEE 802.1Qbh standard. The values are network specific and should be provided by the network administrator.
+ </div><div class="para">
+ Additional parameters in the domain XML include:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-dir-att-2phys3"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'direct'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> dev=</span><span class="perl_String">'eth0'</span><span class="perl_Others"> mode=</span><span class="perl_String">'private'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><virtualport</span><span class="perl_Others"> type=</span><span class="perl_String">'802.1Qbh'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><parameters</span><span class="perl_Others"> profileid=</span><span class="perl_String">'finance'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></virtualport></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.43. Devices - network interfaces- direct attachment to physical interfaces more additional parameters</h6></div><br class="figure-break" /><div class="para">
+ The <code class="sgmltag-attribute">profileid</code> attribute, contains the name of the port profile that is to be applied to this interface. This name is resolved by the port profile database into the network parameters from the port profile, and those network parameters will be applied to this interface.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-generic-ethernet-connection.html"><strong>Prev</strong>J.16.9.4. Generic Ethernet connection</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="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-pci-passthrough.html"><strong>Next</strong>J.16.9.6. PCI passthrough</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-generic-ethernet-connection.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-generic-ethernet-connection.html
new file mode 100644
index 0000000..f77520f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-generic-ethernet-connection.html
@@ -0,0 +1,26 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.4. Generic Ethernet connection</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-userspace-slirp-stack.html" title="J.16.9.3. Userspace SLIRP stack" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-direct-attachment-to-physical-device.html" title="J.16.9.5. Direct attachment to physical interfaces" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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.o
rg"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-userspace-slirp-stack.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-direct-attachment-to-physical-device.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-generic-ethernet-connection"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.4. Generic Ethernet connection</h4></div></div></div><div class="para">
+ Provides a means for the administrator to execute an arbitrary script to connect the guest's network to the LAN. The guest will have a <code class="sgmltag-element">tun</code> device created with a name of <code class="sgmltag-element">vnetN</code>, which can also be overridden with the <code class="sgmltag-element">target</code> element. After creating the <code class="sgmltag-element">tun</code> device a shell script will be run which is expected to do whatever host network integration is required. By default this script is called <code class="filename">/etc/qemu-ifup</code> but can be overridden (refer to <a class="xref" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element.html">Section J.16.9.10, “Overriding the target element”</a>).
+ </div><div class="para">
+ The generic Ethernet connection parameters are defined in the following part of the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-gen-eth-con"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'ethernet'</span><span class="perl_Keyword">/></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'ethernet'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet7'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><script</span><span class="perl_Others"> path=</span><span class="perl_String">'/etc/qemu-ifup-mynet'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.40. Devices - network interfaces- generic Ethernet connection</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-userspace-slirp-stack.html"><strong>Prev</strong>J.16.9.3. Userspace SLIRP stack</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="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-direct-attachment-to-physical-device.html"><strong>Next</strong>J.16.9.5. Direct attachment to physical interfaces</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-multicast-tunnel.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-multicast-tunnel.html
new file mode 100644
index 0000000..b7c0478
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-multicast-tunnel.html
@@ -0,0 +1,22 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.7. Multicast tunnel</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-pci-passthrough.html" title="J.16.9.6. PCI passthrough" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-tcp-tunnel.html" title="J.16.9.8. TCP tunnel" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="Documentat
ion Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-pci-passthrough.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-tcp-tunnel.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-multicast-tunnel"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.7. Multicast tunnel</h4></div></div></div><div class="para">
+ A multicast group may be used to represent a virtual network. Any guest virtual machine whose network devices are within the same multicast group will talk to each other, even if they reside across miltiple physical hosts. This mode may be used as an unprivileged user. There is no default DNS or DHCP support and no outgoing network access. To provide outgoing network access, one of the guest virtual machines should have a second NIC which is connected to one of the first 4 network types in order to provide appropriate routing. The multicast protocol is compatible with protocols used by <code class="command">user mode</code> linux guests as well. Note that the source address used must be from the multicast address block. A multicast tunnel is created by manipulating the <code class="command">interface type</code> using a management tool and setting/changing it to <code class="sgmltag-element">mcast</code>, and providing a mac and source address. The result is shown in ch
anges made to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-multi-cast-tun"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'mcast'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">'52:54:00:6d:90:01'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> address=</span><span class="perl_String">'230.0.0.1'</span><span class="perl_Others"> port=</span><span class="perl_String">'5558'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.45. Devices - network interfaces- multicast tunnel</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-pci-passthrough.html"><strong>Prev</strong>J.16.9.6. PCI passthrough</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="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-tcp-tunnel.html"><strong>Next</strong>J.16.9.8. TCP tunnel</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element.html
new file mode 100644
index 0000000..504fb74
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element.html
@@ -0,0 +1,24 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.10. Overriding the target element</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-setting-nic-driver-specific-options.html" title="J.16.9.9. Setting NIC driver-specific options" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-boot-order.html" title="J.16.9.11. Specifying boot order" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-setting-nic-driver-specific-options.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-boot-order.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.10. Overriding the target element</h4></div></div></div><div class="para">
+ To override the target element, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-overriding-the-target-element"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.48. Devices - network interfaces- overriding the target element</h6></div><br class="figure-break" /><div class="para">
+ If no target is specified, certain hypervisors will automatically generate a name for the created tun device. This name can be manually specifed, however the name must not start with either 'vnet' or 'vif', which are prefixes reserved by libvirt and certain hypervisors. Manually specified targets using these prefixes will be ignored.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-setting-nic-driver-specific-options.html"><strong>Prev</strong>J.16.9.9. Setting NIC driver-specific options</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="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-boot-order.html"><strong>Next</strong>J.16.9.11. Specifying boot order</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-pci-passthrough.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-pci-passthrough.html
new file mode 100644
index 0000000..ebefe18
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-pci-passthrough.html
@@ -0,0 +1,30 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.6. PCI passthrough</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-direct-attachment-to-physical-device.html" title="J.16.9.5. Direct attachment to physical interfaces" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-multicast-tunnel.html" title="J.16.9.7. Multicast tunnel" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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 s
rc="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-direct-attachment-to-physical-device.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-multicast-tunnel.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-pci-passthrough"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.6. PCI passthrough</h4></div></div></div><div class="para">
+ A PCI network device (specified by the <code class="sgmltag-element">source</code> element) is directly assigned to the guest using generic device passthrough, after first optionally setting the device's MAC address to the configured value, and associating the device with an 802.1Qbh capable switch using an optionally specified <code class="sgmltag-element">virtualport</code> element (see the examples of virtualport given above for type='direct' network devices). Note that - due to limitations in standard single-port PCI ethernet card driver design - only SR-IOV (Single Root I/O Virtualization) virtual function (VF) devices can be assigned in this manner; to assign a standard single-port PCI or PCIe ethernet card to a guest, use the traditional <code class="sgmltag-element">hostdev</code> device definition
+ </div><div class="para">
+ Note that this "intelligent passthrough" of network devices is very similar to the functionality of a standard <code class="sgmltag-element">hostdev</code> device, the difference being that this method allows specifying a MAC address and <code class="sgmltag-attribute">virtualport</code> for the passed-through device. If these capabilities are not required, if you have a standard single-port PCI, PCIe, or USB network card that doesn't support SR-IOV (and hence would anyway lose the configured MAC address during reset after being assigned to the guest domain), or if you are using a version of libvirt older than 0.9.11, you should use standard <code class="sgmltag-attribute">hostdev</code> to assign the device to the guest instead of <code class="sgmltag-attribute">interface type='hostdev'/</code>.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-pci-pass"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'hostdev'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">'vfio'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><source></span>
+ <span class="perl_Keyword"><address</span><span class="perl_Others"> type=</span><span class="perl_String">'pci'</span><span class="perl_Others"> domain=</span><span class="perl_String">'0x0000'</span><span class="perl_Others"> bus=</span><span class="perl_String">'0x00'</span><span class="perl_Others"> slot=</span><span class="perl_String">'0x07'</span><span class="perl_Others"> function=</span><span class="perl_String">'0x0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></source></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">'52:54:00:6d:90:02'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><virtualport</span><span class="perl_Others"> type=</span><span class="perl_String">'802.1Qbh'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><parameters</span><span class="perl_Others"> profileid=</span><span class="perl_String">'finance'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></virtualport></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.44. Devices - network interfaces- PCI passthrough</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-direct-attachment-to-physical-device.html"><strong>Prev</strong>J.16.9.5. Direct attachment to physical interfaces</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="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-multicast-tunnel.html"><strong>Next</strong>J.16.9.7. Multicast tunnel</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-setting-nic-driver-specific-options.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-setting-nic-driver-specific-options.html
new file mode 100644
index 0000000..7f27c63
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-setting-nic-driver-specific-options.html
@@ -0,0 +1,45 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.9. Setting NIC driver-specific options</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-tcp-tunnel.html" title="J.16.9.8. TCP tunnel" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element.html" title="J.16.9.10. Overriding the target element" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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/ima
ge_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-tcp-tunnel.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-setting-nic-driver-specific-options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.9. Setting NIC driver-specific options</h4></div></div></div><div class="para">
+ Some NICs may have tunable driver-specific options. These options are set as attributes of the <code class="sgmltag-element">driver</code> sub-element of the interface definition. These options are set by using management toools to configuring the following sections of the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-nic-driver-options"><div class="figure-contents"><pre class="programlisting">
+
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><model</span><span class="perl_Others"> type=</span><span class="perl_String">'virtio'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><driver</span><span class="perl_Others"> name=</span><span class="perl_String">'vhost'</span><span class="perl_Others"> txmode=</span><span class="perl_String">'iothread'</span><span class="perl_Others"> ioeventfd=</span><span class="perl_String">'on'</span><span class="perl_Others"> event_idx=</span><span class="perl_String">'off'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.47. Devices - network interfaces- setting NIC driver-specific options</h6></div><br class="figure-break" /><div class="para">
+ Currently the following attributes are available for the "virtio" NIC driver:
+ </div><div class="table" id="table--libvirt-dom-xml-devices-Network-interfaces-setting-nic-driver-specific-options"><h6>Table J.19. virtio NIC driver elements</h6><div class="table-contents"><table summary="virtio NIC driver elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-attribute">name</code>
+ </td><td class="">
+ The optional <code class="sgmltag-attribute">name</code> attribute forces which type of backend driver to use. The value can be either <code class="sgmltag-attribute">qemu</code> (a user-space backend) or <code class="sgmltag-attribute">vhost</code> (a kernel backend, which requires the vhost module to be provided by the kernel); an attempt to require the vhost driver without kernel support will be rejected. The default setting is <code class="sgmltag-attribute">vhost</code> if the vhost driver present, but will silently fall back to <code class="sgmltag-attribute">qemu</code> if not.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">txmode</code>
+ </td><td class="">
+ Specifies how to handle transmission of packets when the transmit buffer is full. The value can be either <code class="sgmltag-attribute">iothread</code> or <code class="sgmltag-attribute">timer</code>. If set to <code class="sgmltag-attribute">iothread</code>, packet tx is all done in an iothread in the bottom half of the driver (this option translates into adding <code class="sgmltag-attvalue">"tx=bh"</code> to the <code class="sgmltag-attribute">qemu</code> commandline -device virtio-net-pci option). If set to <code class="sgmltag-attvalue">timer</code>, tx work is done in qemu, and if there is more tx data than can be sent at the present time, a timer is set before qemu moves on to do other things; when the timer fires, another attempt is made to send more data. In general you should leave this option alone, unless you are very certain you that changing it is an absolute necessity.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">ioeventfd</code>
+ </td><td class="">
+ Allows users to set domain I/O asynchronous handling for interface device. The default is left to the discretion of the hypervisor. Accepted values are <code class="sgmltag-attvalue">on</code> and <code class="sgmltag-attvalue">off </code>. Enabling this option allows qemu to execute a guest virtual machine while a separate thread handles I/O. Typically guest virtual machines experiencing high system CPU utilization during I/O will benefit from this. On the other hand, overloading the physical host may also increase guest I/O latency. Therefore, you should leave this option alone, unless you are very certain you that changing it is an absolute necessity.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-element">event_idx</code>
+ </td><td class="">
+ The event_idx attribute controls some aspects of device event processing. The value can be either <code class="sgmltag-attvalue">on</code> or <code class="sgmltag-attvalue">off</code>. Choosing <code class="sgmltag-attvalue">on</code>, reduces the number of interrupts and exits for the guest virtual machine. The default is <code class="sgmltag-attvalue">on</code>. In case there is a situation where this behavior is suboptimal, this attribute provides a way to force the feature off. You should leave this option alone, unless you are very certain you that changing it is an absolute necessity.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-tcp-tunnel.html"><strong>Prev</strong>J.16.9.8. TCP tunnel</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="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-overriding-the-target-element.html"><strong>Next</strong>J.16.9.10. Overriding the target element</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-tcp-tunnel.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-tcp-tunnel.html
new file mode 100644
index 0000000..1927c8a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-tcp-tunnel.html
@@ -0,0 +1,27 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.8. TCP tunnel</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-multicast-tunnel.html" title="J.16.9.7. Multicast tunnel" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-setting-nic-driver-specific-options.html" title="J.16.9.9. Setting NIC driver-specific options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-multicast-tunnel.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-setting-nic-driver-specific-options.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-tcp-tunnel"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.8. TCP tunnel</h4></div></div></div><div class="para">
+ Creating a TCP client/server architecture is another way to provide a virtual network wher one guest virtual machine provides the server end of the network and all other guest virtual machines are configured as clients. All network traffic between the guest virtual machines is routed via the guest virtual machine that is configrured as the server. This model is also available for use to unprivileged users. There is no default DNS or DHCP support and no outgoing network access. To provide outgoing network access, one of the guest virtual machines should have a second NIC which is connected to one of the first 4 network types thereby providing the appropriate routing. A TCP tunnel is created by manipulating the <code class="sgmltag-element">interface type</code> using a management tool and setting/changing it to <code class="sgmltag-element">server</code> or <code class="sgmltag-element">client</code>, and providing a mac and source address. The result is shown in changes
made to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-tcp-tun"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'server'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">'52:54:00:22:c9:42'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> address=</span><span class="perl_String">'192.168.0.1'</span><span class="perl_Others"> port=</span><span class="perl_String">'5558'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'client'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">'52:54:00:8b:c9:51'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> address=</span><span class="perl_String">'192.168.0.1'</span><span class="perl_Others"> port=</span><span class="perl_String">'5558'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.46. Devices - network interfaces- TCP tunnel</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-multicast-tunnel.html"><strong>Prev</strong>J.16.9.7. Multicast tunnel</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="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-setting-nic-driver-specific-options.html"><strong>Next</strong>J.16.9.9. Setting NIC driver-specific options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-userspace-slirp-stack.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-userspace-slirp-stack.html
new file mode 100644
index 0000000..f141b94
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-userspace-slirp-stack.html
@@ -0,0 +1,25 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.3. Userspace SLIRP stack</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-bridge-to-lan.html" title="J.16.9.2. Bridge to LAN" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-generic-ethernet-connection.html" title="J.16.9.4. Generic Ethernet connection" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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/im
age_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-bridge-to-lan.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-generic-ethernet-connection.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-userspace-slirp-stack"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.3. Userspace SLIRP stack</h4></div></div></div><div class="para">
+ Setting the userspace SLIRP stack parameters provides a virtual LAN with NAT to the outside world. The virtual network has DHCP and DNS services and will give the guest virtual machine an IP addresses starting from 10.0.2.15. The default router will be 10.0.2.2 and the DNS server will be 10.0.2.3. This networking is the only option for unprivileged users who need their guest virtual machines to have outgoing access.
+ </div><div class="para">
+ The userspace SLIP stack parameters are defined in the following part of the domain XML::
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-network-int-usr-spc-slip"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'user'</span><span class="perl_Keyword">/></span>
+ ...
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'user'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><mac</span><span class="perl_Others"> address=</span><span class="perl_String">"00:11:22:33:44:55"</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.39. Devices - network interfaces- Userspace SLIRP stack</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-bridge-to-lan.html"><strong>Prev</strong>J.16.9.2. Bridge to LAN</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="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-generic-ethernet-connection.html"><strong>Next</strong>J.16.9.4. Generic Ethernet connection</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-host-device-assignment-block-character-devices.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-host-device-assignment-block-character-devices.html
new file mode 100644
index 0000000..1fca32a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-host-device-assignment-block-character-devices.html
@@ -0,0 +1,61 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.6.2. Block / character devices</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-host-device-assignment.html" title="J.16.6. Host device assignment" /><link rel="prev" href="sub-section-libvirt-dom-xml-devices-host-device-assignment.html" title="J.16.6. Host device assignment" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-redirected-devices.html" title="J.16.7. Redirected devices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-section-libvirt-dom-xml-devices-host-device-assignment.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-redirected-devices.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-host-device-assignment-block-character-devices"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.6.2. Block / character devices </h4></div></div></div><div class="para">
+ The host's block / character devices can be passed through to the guest by using managment tools to modify the domain xml <code class="sgmltag-element">hostdev</code> element. Note that this is only possible with container based virtualization.
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-host-device-assignment-blk"><div class="figure-contents"><pre class="programlisting">
+
+...
+<span class="perl_Keyword"><hostdev</span><span class="perl_Others"> mode=</span><span class="perl_String">'capabilities'</span><span class="perl_Others"> type=</span><span class="perl_String">'storage'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source></span>
+ <span class="perl_Keyword"><block></span>/dev/sdf1<span class="perl_Keyword"></block></span>
+ <span class="perl_Keyword"></source></span>
+<span class="perl_Keyword"></hostdev></span>
+...
+
+</pre></div><h6>Figure J.31. Devices - host device assignment block character devices</h6></div><br class="figure-break" /><div class="para">
+ An alternative approach is this:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-host-device-assignment-blk2"><div class="figure-contents"><pre class="programlisting">
+
+...
+<span class="perl_Keyword"><hostdev</span><span class="perl_Others"> mode=</span><span class="perl_String">'capabilities'</span><span class="perl_Others"> type=</span><span class="perl_String">'misc'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source></span>
+ <span class="perl_Keyword"><char></span>/dev/input/event3<span class="perl_Keyword"></char></span>
+ <span class="perl_Keyword"></source></span>
+<span class="perl_Keyword"></hostdev></span>
+...
+
+</pre></div><h6>Figure J.32. Devices - host device assignment block character devices alternative 1</h6></div><br class="figure-break" /><div class="para">
+ Another alternative approach is this:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-host-device-assignment-blk3"><div class="figure-contents"><pre class="programlisting">
+
+...
+<span class="perl_Keyword"><hostdev</span><span class="perl_Others"> mode=</span><span class="perl_String">'capabilities'</span><span class="perl_Others"> type=</span><span class="perl_String">'net'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source></span>
+ <span class="perl_Keyword"><interface></span>eth0<span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></source></span>
+<span class="perl_Keyword"></hostdev></span>
+...
+
+
+</pre></div><h6>Figure J.33. Devices - host device assignment block character devices alternative 2</h6></div><br class="figure-break" /><div class="para">
+ The components of this section of the domain XML are as follows:
+ </div><div class="table" id="table-libvirt-dom-xml-host-device-assignement-block-character-devices"><h6>Table J.14. Block / character device elements</h6><div class="table-contents"><table summary="Block / character device elements" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="">
+ Parameter
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="sgmltag-element">hostdev</code>
+ </td><td class="">
+ This is the main container for describing host devices. For block/character devices passthrough <code class="sgmltag-attribute">mode</code> is always <code class="sgmltag-element">capabilities</code> and <code class="sgmltag-attribute">type</code> is <code class="sgmltag-element">block</code> for a block device and <code class="sgmltag-element">char</code> for a character device.
+ </td></tr><tr><td class="">
+ <code class="sgmltag-attribute">source</code>
+ </td><td class="">
+ This describes the device as seen from the host. For block devices, the path to the block device in the host OS is provided in the nested <code class="sgmltag-element">block</code> element, while for character devices the <code class="sgmltag-element">char</code> element is used
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-section-libvirt-dom-xml-devices-host-device-assignment.html"><strong>Prev</strong>J.16.6. Host device assignment</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="sub-section-libvirt-dom-xml-devices-redirected-devices.html"><strong>Next</strong>J.16.7. Redirected devices</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-interface-ROM-BIOS-configuration.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-interface-ROM-BIOS-configuration.html
new file mode 100644
index 0000000..91cd8ba
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-interface-ROM-BIOS-configuration.html
@@ -0,0 +1,25 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.12. Interface ROM BIOS configuration</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-boot-order.html" title="J.16.9.11. Specifying boot order" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-qos.html" title="J.16.9.13. Quality of service" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-boot-order.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-qos.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-interface-ROM-BIOS-configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.12. Interface ROM BIOS configuration</h4></div></div></div><div class="para">
+ To specify the ROM BIOS configuration settings, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-interface-ROM-BIOS-configuration"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet1'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><rom</span><span class="perl_Others"> bar=</span><span class="perl_String">'on'</span><span class="perl_Others"> file=</span><span class="perl_String">'/etc/fake/boot.bin'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"></devices></span>
+ ...
+</pre></div><h6>Figure J.50. Interface ROM BIOS configuration</h6></div><br class="figure-break" /><div class="para">
+ For hypervisors which support it, you can change how a PCI Network device's ROM is presented to the guest virtual machine. The <code class="sgmltag-attribute">bar</code> attribute can be set to <code class="sgmltag-element">on</code> or <code class="sgmltag-element">off</code>, and determines whether or not the device's ROM will be visible in the guest's memory map. (In PCI documentation, the "rombar" setting controls the presence of the Base Address Register for the ROM). If no rom bar is specified, the qemu default will be used (older versions of qemu used a default of <code class="sgmltag-element">off</code>, while newer qemus have a default of <code class="sgmltag-element">on</code>). The optional <code class="sgmltag-element">file</code> attribute is used to point to a binary file to be presented to the guest as the device's ROM BIOS. This can be useful to provide an alternative boot ROM for a network device.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-Network-interfaces-boot-order.html"><strong>Prev</strong>J.16.9.11. Specifying boot order</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="sub-sub-section-libvirt-dom-xml-devices-qos.html"><strong>Next</strong>J.16.9.13. Quality of service</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-modifying-virtual-link-state.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-modifying-virtual-link-state.html
new file mode 100644
index 0000000..61d7797
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-modifying-virtual-link-state.html
@@ -0,0 +1,25 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.15. Modifying virtual link state</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-setting-vlan-tag.html" title="J.16.9.14. Setting VLAN tag (on supported network types only)" /><link rel="next" href="sub-section-libvirt-dom-xml-devices-input-devices.html" title="J.16.10. Input devices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="Documentat
ion Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-setting-vlan-tag.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-section-libvirt-dom-xml-devices-input-devices.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-modifying-virtual-link-state"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.15. Modifying virtual link state</h4></div></div></div><div class="para">
+ This element provides means of setting state of the virtual network link. Possible values for attribute <code class="sgmltag-attribute">state</code> are <code class="sgmltag-attvalue">up</code> and <code class="sgmltag-attvalue">down</code>. If <code class="sgmltag-attvalue">down</code> is specified as the value, the interface behaves as if it had the network cable disconnected. Default behavior if this element is unspecified is to have the link state <code class="sgmltag-attvalue">up</code>.
+ </div><div class="para">
+ To specify the virtual link state configuration settings, use a management tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-dom-xml-devices-modifying-virtual-link-state"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><link</span><span class="perl_Others"> state=</span><span class="perl_String">'down'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><devices></span>
+ ...
+</pre></div><h6>Figure J.53. Modifying virtual link state</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-setting-vlan-tag.html"><strong>Prev</strong>J.16.9.14. Setting VLAN tag (on supported 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="sub-section-libvirt-dom-xml-devices-input-devices.html"><strong>Next</strong>J.16.10. Input devices</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-qos.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-qos.html
new file mode 100644
index 0000000..cb3caed
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-qos.html
@@ -0,0 +1,32 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.13. Quality of service</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-interface-ROM-BIOS-configuration.html" title="J.16.9.12. Interface ROM BIOS configuration" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-setting-vlan-tag.html" title="J.16.9.14. Setting VLAN tag (on supported network types only)" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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_Con
tent/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-interface-ROM-BIOS-configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-setting-vlan-tag.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-qos"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.13. Quality of service</h4></div></div></div><div class="para">
+ This section of the domain XML provides setting quality of service. Incoming and outgoing traffic can be shaped independently. The <code class="sgmltag-element">bandwidth</code> element can have at most one inbound and at most one outbound child elements. Leaving any of these children element out results in no QoS being applied on that traffic direction. Therefore, when you want to shape only domain's incoming traffic, use inbound only, and vice versa.
+ </div><div class="para">
+ Each of these elements has one mandatory attribute <code class="sgmltag-attribute">average</code> (or <code class="sgmltag-attribute">floor</code> as described below). <code class="sgmltag-attribute">average</code> specifies average bit rate on the interface being shaped. Then there are two optional attributes: <code class="sgmltag-attribute">peak</code>, which specifies maximum rate at which interface can send data, and <code class="sgmltag-attribute">burst</code>, which specifies the amount of bytes that can be burst at peak speed. Accepted values for attributes are integer numbers.
+ </div><div class="para">
+ The units for <code class="sgmltag-attribute">average</code> and <code class="sgmltag-attribute">peak</code> attributes are kilobytes per second, whereas <code class="sgmltag-attribute">burst</code> is only set in kilobytes. In addtion, inbound traffic can optionally have a <code class="sgmltag-attribute">floor</code> attribute. This guarantees minimal throughput for shaped interfaces. Using the <code class="sgmltag-attribute">floor</code> requires that all traffic goes through one point where QoS decisions can take place. As such it may only be used in cases where the <code class="sgmltag-element">interface type='network'/</code> with a <code class="sgmltag-element">forward</code> type of <code class="sgmltag-element">route</code>, <code class="sgmltag-element">nat</code>, or no forward at all). It should be noted that within a virtual network, all connected interfaces are required to have at least the inbound QoS set (<code class="sgmltag-element">average</code> at le
ast) but the floor attribute doesn't require specifying <code class="sgmltag-element">average</code>. However, <code class="sgmltag-element">peak</code> and <code class="sgmltag-element">burst</code> attributes still require <code class="sgmltag-element">average</code>. At the present time, ingress qdiscs may not have any classes, and therefore <code class="sgmltag-attribute">floor</code> may only be applied only on inbound and not outbound traffic.
+ </div><div class="para">
+ To specify the QoS configuration settings, use a managment tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-qos"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'network'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> network=</span><span class="perl_String">'default'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><target</span><span class="perl_Others"> dev=</span><span class="perl_String">'vnet0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><bandwidth></span>
+ <span class="perl_Keyword"><inbound</span><span class="perl_Others"> average=</span><span class="perl_String">'1000'</span><span class="perl_Others"> peak=</span><span class="perl_String">'5000'</span><span class="perl_Others"> floor=</span><span class="perl_String">'200'</span><span class="perl_Others"> burst=</span><span class="perl_String">'1024'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><outbound</span><span class="perl_Others"> average=</span><span class="perl_String">'128'</span><span class="perl_Others"> peak=</span><span class="perl_String">'256'</span><span class="perl_Others"> burst=</span><span class="perl_String">'256'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></bandwidth></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><devices></span>
+ ...
+</pre></div><h6>Figure J.51. Quality of service</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-interface-ROM-BIOS-configuration.html"><strong>Prev</strong>J.16.9.12. Interface ROM BIOS 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="sub-sub-section-libvirt-dom-xml-devices-setting-vlan-tag.html"><strong>Next</strong>J.16.9.14. Setting VLAN tag (on supported network...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-setting-vlan-tag.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-setting-vlan-tag.html
new file mode 100644
index 0000000..f1305e4
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-section-libvirt-dom-xml-devices-setting-vlan-tag.html
@@ -0,0 +1,30 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>J.16.9.14. Setting VLAN tag (on supported network types only)</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-section-libvirt-dom-xml-devices-Network-interfaces.html" title="J.16.9. Network interfaces" /><link rel="prev" href="sub-sub-section-libvirt-dom-xml-devices-qos.html" title="J.16.9.13. Quality of service" /><link rel="next" href="sub-sub-section-libvirt-dom-xml-devices-modifying-virtual-link-state.html" title="J.16.9.15. Modifying virtual link state" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sub-section-libvirt-dom-xml-devices-qos.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-section-libvirt-dom-xml-devices-modifying-virtual-link-state.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-section-libvirt-dom-xml-devices-setting-vlan-tag"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">J.16.9.14. Setting VLAN tag (on supported network types only)</h4></div></div></div><div class="para">
+ To specify the VLAN tag configuration settings, use a mangement tool to make the following changes to the domain XML:
+ </div><div class="figure" id="fig-libvirt-dom-xml-devices-setting-vlan-tag"><div class="figure-contents"><pre class="programlisting">
+
+ ...
+ <span class="perl_Keyword"><devices></span>
+ <span class="perl_Keyword"><interface</span><span class="perl_Others"> type=</span><span class="perl_String">'bridge'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><vlan></span>
+ <span class="perl_Keyword"><tag</span><span class="perl_Others"> id=</span><span class="perl_String">'42'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></vlan></span>
+ <span class="perl_Keyword"><source</span><span class="perl_Others"> bridge=</span><span class="perl_String">'ovsbr0'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"><virtualport</span><span class="perl_Others"> type=</span><span class="perl_String">'openvswitch'</span><span class="perl_Keyword">></span>
+ <span class="perl_Keyword"><parameters</span><span class="perl_Others"> interfaceid=</span><span class="perl_String">'09b11c53-8b5c-4eeb-8f00-d84eaa0aaa4f'</span><span class="perl_Keyword">/></span>
+ <span class="perl_Keyword"></virtualport></span>
+ <span class="perl_Keyword"></interface></span>
+ <span class="perl_Keyword"><devices></span>
+ ...
+
+</pre></div><h6>Figure J.52. Setting VLAN tag (on supported network types only)</h6></div><br class="figure-break" /><div class="para">
+ If (and only if) the network connection used by the guest supports vlan tagging transparent to the guest, an optional <code class="sgmltag-element">vlan</code> element can specify one or more vlan tags to apply to the guest's network traffic (openvswitch and <code class="sgmltag-element">type='hostdev'</code> SR-IOV interfaces do support transparent vlan tagging of guest traffic; everything else, including standard linux bridges and libvirt's own virtual networks, do not support it. 802.1Qbh (vn-link) and 802.1Qbg (VEPA) switches provide their own way (outside of libvirt) to tag guest traffic onto specific vlans.) To allow for specification of multiple tags (in the case of vlan trunking), a subelement, <code class="sgmltag-element">tag</code>, specifies which vlan tag to use (for example: <code class="sgmltag-attribute">tag id='42'/</code>. If an interface has more than one <code class="sgmltag-element">vlan</code> element defined, it is assumed that the user wants to d
o VLAN trunking using all the specified tags. In the case that vlan trunking with a single tag is desired, the optional attribute <code class="sgmltag-attribute">trunk='yes'</code> can be added to the toplevel vlan element.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-section-libvirt-dom-xml-devices-qos.html"><strong>Prev</strong>J.16.9.13. Quality of service</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="sub-sub-section-libvirt-dom-xml-devices-modifying-virtual-link-state.html"><strong>Next</strong>J.16.9.15. Modifying virtual link state</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-subsect-command-line-tools.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-subsect-command-line-tools.html
new file mode 100644
index 0000000..4f13ecf
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/sub-sub-subsect-command-line-tools.html
@@ -0,0 +1,22 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>H.10.11.3. Command line tools</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sub-sect-adv-filt-topics.html" title="H.10.11. Advanced Filter Configuration Topics" /><link rel="prev" href="sub-sub-sect-lim-numb-conns.html" title="H.10.11.2. Limiting Number of Connections" /><link rel="next" href="sub-sub-sect-pre-exist-net-filter.html" title="H.10.11.4. Pre-existing network filters" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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="sub-sub-sect-lim-numb-conns.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sub-sub-sect-pre-exist-net-filter.html"><strong>Next</strong></a></li></ul><div class="section" id="sub-sub-subsect-command-line-tools"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">H.10.11.3. Command line tools</h4></div></div></div><div class="para">
+ virsh has been extended with life-cycle support for network filters. All commands related to the network filtering subsystem start with the prefix <em class="parameter"><code>nwfilter</code></em>. The following commands are available:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">nwfilter-list</code> : lists UUIDs and names of all network filters
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">nwfilter-define</code> : defines a new network filter or updates an existing one (must supply a name)
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">nwfilter-undefine</code> : deletes a specified network filter (must supply a name). In addition, it cannot currently be in use
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">nwfilter-dumpxml</code> : displays a specified network filter (must supply a name)
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">nwfilter-edit</code> : edits a specified network filter (must supply a name)
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sub-sub-sect-lim-numb-conns.html"><strong>Prev</strong>H.10.11.2. Limiting Number of Connections</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="sub-sub-sect-pre-exist-net-filter.html"><strong>Next</strong>H.10.11.4. Pre-existing network filters</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/subsect-guest-synch-delimited.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/subsect-guest-synch-delimited.html
new file mode 100644
index 0000000..09a7053
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/subsect-guest-synch-delimited.html
@@ -0,0 +1,26 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.14.2. guest-sync-delimited</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-qemu-ga.html" title="25.14. QEMU Guest Agent Protocol" /><link rel="prev" href="sect-qemu-ga.html" title="25.14. QEMU Guest Agent Protocol" /><link rel="next" href="sect-limit-redirection.html" title="25.15. Setting a limit on device redirection" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-qemu-ga.html"><strong>Prev
</strong></a></li><li class="next"><a accesskey="n" href="sect-limit-redirection.html"><strong>Next</strong></a></li></ul><div class="section" id="subsect-guest-synch-delimited"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">25.14.2. guest-sync-delimited</h3></div></div></div><div class="para">
+ If <span class="package">qemu-ga</span> attempts to communicate with a client, and the client receives a partial response from a previous <span class="package">qemu-ga</span> instance, the client might misconstrue responses to guest-sync as being part of this previous request. For client implementations that treat newlines as a delimiter for <span class="package">qemu-ga</span> responses, use <code class="command">guest-synch-delimited</code>.
+ </div><div class="para">
+ Even in some cases where there are JSON stream-based implementations that do not rely on newline delimiters, it may be considered invasive to implement a client's response/JSON handling, as it is the same deadlock scenario described previously. Using the <code class="command">guest-sync-delimited</code> on the client, tells qemu-ga to place the same 0xFF character in front of the response, thereby preventing confusion.
+ </div><pre class="screen">
+> { "execute": "guest-sync-delimited", "arguments": { "id": 123456 } }
+< { "return": 123456}
+</pre><div class="para">
+ Actual hex values sent:
+ </div><pre class="screen">
+> 7b 27 65 78 65 63 75 74 65 27 3a 27 67 75 65 73 74 2d 73 79 6e 63 2d 64 65
+ 6c 69 6d 69 74 65 64 27 2c 27 61 72 67 75 6d 65 6e 74 73 27 3a 7b 27 69 64
+ 27 3a 31 32 33 34 35 36 7d 7d 0a
+< ff 7b 22 72 65 74 75 72 6e 22 3a 20 31 32 33 34 35 36 7d 0a
+</pre><div class="para">
+ As stated above, the request should also be preceded with a 0xFF to flush <span class="package">qemu-ga</span>'s parser state.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-qemu-ga.html"><strong>Prev</strong>25.14. QEMU Guest Agent Protocol</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-limit-redirection.html"><strong>Next</strong>25.15. Setting a limit on device redirection</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/vhostmd.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/vhostmd.html
new file mode 100644
index 0000000..d78a68a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/vhostmd.html
@@ -0,0 +1,18 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 29. The Virtual Host Metrics Daemon (vhostmd)</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="pt02.html" title="Part II. Administration" /><link rel="prev" href="sect-Virtualization-Storage_Volumes-Deleting_volumes.html" title="28.4. Deleting and removing volumes" /><link rel="next" href="ch29s02.html" title="29.2. Configuration of vhostmd" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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-Storage_Volum
es-Deleting_volumes.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch29s02.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="vhostmd" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 29. The Virtual Host Metrics Daemon (vhostmd)</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="vhostmd.html#idp15936832">29.1. Installing vhostmd on the host</a></span></dt><dt><span class="section"><a href="ch29s02.html">29.2. Configuration of vhostmd</a></span></dt><dt><span class="section"><a href="ch29s03.html">29.3. Starting and stopping the daemon</a></span></dt><dt><span class="section"><a href="ch29s04.html">29.4. Verifying that vhostmd is working from the host</a></span></dt><dt><span class="section"><a href="ch29s05.html">29.5. Configuring guests to see the metrics</a></span></dt><dt><span class="section"><a href="ch29s06.html">29.6. Using vm-dump-metrics in Fedora guests
to verify operation</a></span></dt></dl></div><div class="para">
+ <span class="application"><strong>vhostmd</strong></span> (the Virtual Host Metrics Daemon) allows virtual machines to see limited information about the host they are running on.
+ </div><div class="para">
+ In the host, a daemon (<span class="application"><strong>vhostmd</strong></span>) runs which writes metrics periodically into a disk image. This disk image is exported read-only to guests. Guests can read the disk image to see metrics. Simple synchronization stops guests from seeing out of date or corrupt metrics.
+ </div><div class="para">
+ The system administrator chooses which metrics the guests can see, and also which guests get to see the metrics at all.
+ </div><div class="section" id="idp15936832"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idp15936832">29.1. Installing vhostmd on the host</h2></div></div></div><div class="para">
+ The <span class="application"><strong>vhostmd</strong></span> package is available from RHN and is located in the Downloads area. It must be installed on each host where guests are required to get host metrics.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-Storage_Volumes-Deleting_volumes.html"><strong>Prev</strong>28.4. Deleting and removing volumes</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="ch29s02.html"><strong>Next</strong>29.2. Configuration of vhostmd</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/virsh-migration-arguements.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/virsh-migration-arguements.html
new file mode 100644
index 0000000..81095e7
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/virsh-migration-arguements.html
@@ -0,0 +1,46 @@
+<?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><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.4.2. Additional options for the virsh migrate command</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora_Draft_Documentation-Virtualization_Deployment_and_Administration_Guide-0.1-en-US-19.0.1-1" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora_Draft_Documentation');
+
+ addID('Fedora_Draft_Documentation.0.1');
+
+ addID('Fedora_Draft_Documentation.0.1.books');
+ addID('Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide');
+ </script><link rel="home" href="index.html" title="Virtualization Deployment and Administration Guide" /><link rel="up" href="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html" title="20.4. Live KVM migration with virsh" /><link rel="prev" href="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html" title="20.4. Live KVM migration with virsh" /><link rel="next" href="sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager.html" title="20.5. Migrating with virt-manager" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><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/im
ages/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager.html"><strong>Next</strong></a></li></ul><div class="section" id="virsh-migration-arguements"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.4.2. Additional options for the virsh migrate command</h3></div></div></div><div class="para">
+ In addition to <em class="replaceable"><code>--live</code></em>, virsh migrate accepts the following options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ --direct - used for direct migration
+ </div></li><li class="listitem"><div class="para">
+ --p2p - used for peer-2-peer migration
+ </div></li><li class="listitem"><div class="para">
+ --tunnelled - used for tunnelled migration
+ </div></li><li class="listitem"><div class="para">
+ --persistent - leaves the domain persistent on destination host
+ </div></li><li class="listitem"><div class="para">
+ --undefinesource - undefines the domain on the source host
+ </div></li><li class="listitem"><div class="para">
+ --suspend - leaves the domain paused on the destination host
+ </div></li><li class="listitem"><div class="para">
+ --copy-storage-all - indicates migration with non-shared storage with full disk copy
+ </div></li><li class="listitem"><div class="para">
+ --copy-storage-inc - indicates migration with non-shared storage with incremental copy (same base image shared between source and destination). In both cases the disk images have to exist on the destination host, the --copy-storage-.options only tell libvirt to transfer data from the images on source host to the images found at the same place on the destination host
+ </div></li><li class="listitem"><div class="para">
+ --change-protection - enforces that no incompatible configuration changes will be made to the domain while the migration is underway; this flag is implicitly enabled when supported by the hypervisor, but can be explicitly used to reject the migration if the hypervisor lacks change protection support.
+ </div></li><li class="listitem"><div class="para">
+ --unsafe - forces the migration to occur, ignoring all safety procedures.
+ </div></li><li class="listitem"><div class="para">
+ --verbose displays the progress of migration as it is occurring
+ </div></li><li class="listitem"><div class="para">
+ migrateuri - the migration URI which is usually omitted.
+ </div></li><li class="listitem"><div class="para">
+ --timeout seconds - forces a guest to suspend when the live migration counter exceeds N seconds. It can only be used with a live migration. Once the timeout is initiated, the migration continues on the suspended guest.
+ </div></li><li class="listitem"><div class="para">
+ dname - is used for renaming the domain to new name during migration, which also usually can be omitted
+ </div></li><li class="listitem"><div class="para">
+ s
+ </div></li><li class="listitem"><div class="para">
+ --xml file can be used to supply an alternative XML file for use on the destination to supply a larger set of changes to any host-specific portions of the domain XML, such as accounting for naming differences between source and destination in accessing underlying storage. This option is usually omitted.
+ </div></li></ul></div><div class="para">
+ Refer to the virsh man page for more information.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Virtualization-KVM_live_migration-Live_KVM_migration_with_virsh.html"><strong>Prev</strong>20.4. 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="sect-Virtualization-KVM_live_migration-Migrating_with_virt_manager.html"><strong>Next</strong>20.5. Migrating with virt-manager</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf b/public_html/en-US/Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf
new file mode 100644
index 0000000..fc89ce3
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf b/public_html/en-US/Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf
new file mode 100644
index 0000000..1fd4c7d
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf differ
diff --git a/public_html/en-US/Site_Statistics.html b/public_html/en-US/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/en-US/Site_Statistics.html
+++ b/public_html/en-US/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/en-US/opds-Community_Services_Infrastructure.xml b/public_html/en-US/opds-Community_Services_Infrastructure.xml
index f58cca2..f652413 100644
--- a/public_html/en-US/opds-Community_Services_Infrastructure.xml
+++ b/public_html/en-US/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:18</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds-Fedora.xml b/public_html/en-US/opds-Fedora.xml
index 21ee7a8..a34ec23 100644
--- a/public_html/en-US/opds-Fedora.xml
+++ b/public_html/en-US/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:18</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds-Fedora_Contributor_Documentation.xml b/public_html/en-US/opds-Fedora_Contributor_Documentation.xml
index e703652..62d59b9 100644
--- a/public_html/en-US/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/en-US/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:18</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds-Fedora_Core.xml b/public_html/en-US/opds-Fedora_Core.xml
index 0846f31..8827b456 100644
--- a/public_html/en-US/opds-Fedora_Core.xml
+++ b/public_html/en-US/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:18</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds-Fedora_Draft_Documentation.xml b/public_html/en-US/opds-Fedora_Draft_Documentation.xml
index 3551fd9..3e5ee00 100644
--- a/public_html/en-US/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/en-US/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:18</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>en-US</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/en-US/opds-Fedora_Security_Team.xml b/public_html/en-US/opds-Fedora_Security_Team.xml
index 6135f31..0dea03d 100644
--- a/public_html/en-US/opds-Fedora_Security_Team.xml
+++ b/public_html/en-US/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:18</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds.xml b/public_html/en-US/opds.xml
index 2d8480b..dead641 100644
--- a/public_html/en-US/opds.xml
+++ b/public_html/en-US/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/en-US/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:18</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/en-US/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:18</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:18</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:18</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:18</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:18</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:18</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/en-US/toc.html b/public_html/en-US/toc.html
index c195832..5a3b348 100644
--- a/public_html/en-US/toc.html
+++ b/public_html/en-US/toc.html
@@ -1382,7 +1382,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1.Amateur_Radio_Guide' class="book collapsed">
<a class="type" href="Fedora_Draft_Documentation/0.1/html/Amateur_Radio_Guide/index.html" onclick="window.top.location='./Fedora_Draft_Documentation/0.1/html/Amateur_Radio_Guide/index.html'"><span class="book">Amateur Radio Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.Amateur_Radio_Guide.types' class="types" onclick="work=0;">
@@ -1461,6 +1463,15 @@
<a class="type" href="./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed">
+ <a class="type" href="Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types" onclick="work=0;">
+ <a class="type" href="./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
<div id='Fedora_Draft_Documentation.' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation..books');">
diff --git a/public_html/es-ES/Site_Statistics.html b/public_html/es-ES/Site_Statistics.html
index 1752e89..f7c07a7 100644
--- a/public_html/es-ES/Site_Statistics.html
+++ b/public_html/es-ES/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Idiomas totales: </b>44<br />
- <b>Paquetes totales: </b>861
+ <b>Paquetes totales: </b>862
</div>
</body>
</html>
diff --git a/public_html/es-ES/opds-Community_Services_Infrastructure.xml b/public_html/es-ES/opds-Community_Services_Infrastructure.xml
index 4cf50ea..c6704a6 100644
--- a/public_html/es-ES/opds-Community_Services_Infrastructure.xml
+++ b/public_html/es-ES/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:18</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds-Fedora.xml b/public_html/es-ES/opds-Fedora.xml
index 3ef57b9..fc1b712 100644
--- a/public_html/es-ES/opds-Fedora.xml
+++ b/public_html/es-ES/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds-Fedora_15.xml b/public_html/es-ES/opds-Fedora_15.xml
index 596e52a..afa2406 100644
--- a/public_html/es-ES/opds-Fedora_15.xml
+++ b/public_html/es-ES/opds-Fedora_15.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora_15.xml</id>
<title>Fedora 15</title>
<subtitle>Fedora 15</subtitle>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml b/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml
index 0338b13..73f4beb 100644
--- a/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Documentación de Contribuyente</title>
<subtitle>Fedora Documentación de Contribuyente</subtitle>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds-Fedora_Core.xml b/public_html/es-ES/opds-Fedora_Core.xml
index 95f4ca3..4314cbf 100644
--- a/public_html/es-ES/opds-Fedora_Core.xml
+++ b/public_html/es-ES/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds-Fedora_Draft_Documentation.xml b/public_html/es-ES/opds-Fedora_Draft_Documentation.xml
index 798d26b..91bc664 100644
--- a/public_html/es-ES/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/es-ES/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>es-ES</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/es-ES/opds-Fedora_Security_Team.xml b/public_html/es-ES/opds-Fedora_Security_Team.xml
index 77416a2..49b59a8 100644
--- a/public_html/es-ES/opds-Fedora_Security_Team.xml
+++ b/public_html/es-ES/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds.xml b/public_html/es-ES/opds.xml
index 47f9142..d646d2d 100644
--- a/public_html/es-ES/opds.xml
+++ b/public_html/es-ES/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/es-ES/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/es-ES/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:18</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora 15</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora_15/opds-Fedora_15.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_15.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Documentación de Contribuyente</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/es-ES/toc.html b/public_html/es-ES/toc.html
index a31b789..a659bb4 100644
--- a/public_html/es-ES/toc.html
+++ b/public_html/es-ES/toc.html
@@ -1678,7 +1678,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Aún sin traducir</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1760,6 +1762,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/fa-IR/Site_Statistics.html b/public_html/fa-IR/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/fa-IR/Site_Statistics.html
+++ b/public_html/fa-IR/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/fa-IR/opds-Community_Services_Infrastructure.xml b/public_html/fa-IR/opds-Community_Services_Infrastructure.xml
index 07aea59..b81fb7e 100644
--- a/public_html/fa-IR/opds-Community_Services_Infrastructure.xml
+++ b/public_html/fa-IR/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds-Fedora.xml b/public_html/fa-IR/opds-Fedora.xml
index ec4008f..781c9ac 100644
--- a/public_html/fa-IR/opds-Fedora.xml
+++ b/public_html/fa-IR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml b/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml
index e7fce89..55a0fce 100644
--- a/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Fedora_Contributor_Documentation.xml</id>
<title>مستندات مشارکت کننده فدورا</title>
<subtitle>مستندات مشارکت کننده فدورا</subtitle>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds-Fedora_Core.xml b/public_html/fa-IR/opds-Fedora_Core.xml
index 258422b..dfdc33b 100644
--- a/public_html/fa-IR/opds-Fedora_Core.xml
+++ b/public_html/fa-IR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds-Fedora_Draft_Documentation.xml b/public_html/fa-IR/opds-Fedora_Draft_Documentation.xml
index 5fde5f9..2cc6453 100644
--- a/public_html/fa-IR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/fa-IR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>fa-IR</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/fa-IR/opds-Fedora_Security_Team.xml b/public_html/fa-IR/opds-Fedora_Security_Team.xml
index c840129..b6acb15 100644
--- a/public_html/fa-IR/opds-Fedora_Security_Team.xml
+++ b/public_html/fa-IR/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds.xml b/public_html/fa-IR/opds.xml
index f33560e..0f8e9a8 100644
--- a/public_html/fa-IR/opds.xml
+++ b/public_html/fa-IR/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/fa-IR/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/fa-IR/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/fa-IR/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>مستندات مشارکت کننده فدورا</title>
<id>http://docs.fedoraproject.org/fa-IR/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/fa-IR/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/fa-IR/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/fa-IR/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/fa-IR/toc.html b/public_html/fa-IR/toc.html
index 4d85859..04f6b8b 100644
--- a/public_html/fa-IR/toc.html
+++ b/public_html/fa-IR/toc.html
@@ -1480,7 +1480,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1562,6 +1564,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/fi-FI/Site_Statistics.html b/public_html/fi-FI/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/fi-FI/Site_Statistics.html
+++ b/public_html/fi-FI/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/fi-FI/opds-Community_Services_Infrastructure.xml b/public_html/fi-FI/opds-Community_Services_Infrastructure.xml
index b543aa3..624d369 100644
--- a/public_html/fi-FI/opds-Community_Services_Infrastructure.xml
+++ b/public_html/fi-FI/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds-Fedora.xml b/public_html/fi-FI/opds-Fedora.xml
index b52bef3..4065877 100644
--- a/public_html/fi-FI/opds-Fedora.xml
+++ b/public_html/fi-FI/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml b/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml
index 4e35f3a..2fb6911 100644
--- a/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds-Fedora_Core.xml b/public_html/fi-FI/opds-Fedora_Core.xml
index 7e743ce..ea1ab36 100644
--- a/public_html/fi-FI/opds-Fedora_Core.xml
+++ b/public_html/fi-FI/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds-Fedora_Draft_Documentation.xml b/public_html/fi-FI/opds-Fedora_Draft_Documentation.xml
index fc6776c..77556e5 100644
--- a/public_html/fi-FI/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/fi-FI/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:20</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>fi-FI</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/fi-FI/opds-Fedora_Security_Team.xml b/public_html/fi-FI/opds-Fedora_Security_Team.xml
index e87c2d5..4ce9390 100644
--- a/public_html/fi-FI/opds-Fedora_Security_Team.xml
+++ b/public_html/fi-FI/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds.xml b/public_html/fi-FI/opds.xml
index fa9b8bf..5dc5f23 100644
--- a/public_html/fi-FI/opds.xml
+++ b/public_html/fi-FI/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/fi-FI/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:20</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/fi-FI/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/fi-FI/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:20</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/fi-FI/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:20</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/fi-FI/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:20</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/fi-FI/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:20</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/fi-FI/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:20</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/fi-FI/toc.html b/public_html/fi-FI/toc.html
index 1675fe2..ed9443c 100644
--- a/public_html/fi-FI/toc.html
+++ b/public_html/fi-FI/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/fr-FR/Site_Statistics.html b/public_html/fr-FR/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/fr-FR/Site_Statistics.html
+++ b/public_html/fr-FR/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/fr-FR/opds-Community_Services_Infrastructure.xml b/public_html/fr-FR/opds-Community_Services_Infrastructure.xml
index 86862e0..331e0c2 100644
--- a/public_html/fr-FR/opds-Community_Services_Infrastructure.xml
+++ b/public_html/fr-FR/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds-Fedora.xml b/public_html/fr-FR/opds-Fedora.xml
index 3c1cf45..875b94a 100644
--- a/public_html/fr-FR/opds-Fedora.xml
+++ b/public_html/fr-FR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml b/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml
index 2abc9a8..fdad6b9 100644
--- a/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds-Fedora_Core.xml b/public_html/fr-FR/opds-Fedora_Core.xml
index 550f8ec..6813d76 100644
--- a/public_html/fr-FR/opds-Fedora_Core.xml
+++ b/public_html/fr-FR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds-Fedora_Draft_Documentation.xml b/public_html/fr-FR/opds-Fedora_Draft_Documentation.xml
index 917762d..db998cc 100644
--- a/public_html/fr-FR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/fr-FR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>fr-FR</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/fr-FR/opds-Fedora_Security_Team.xml b/public_html/fr-FR/opds-Fedora_Security_Team.xml
index bd56ce1..42e2261 100644
--- a/public_html/fr-FR/opds-Fedora_Security_Team.xml
+++ b/public_html/fr-FR/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds.xml b/public_html/fr-FR/opds.xml
index 92051cf..09bc8b1 100644
--- a/public_html/fr-FR/opds.xml
+++ b/public_html/fr-FR/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/fr-FR/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/fr-FR/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:20</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/fr-FR/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/fr-FR/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/fr-FR/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/fr-FR/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/fr-FR/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/fr-FR/toc.html b/public_html/fr-FR/toc.html
index 096f8a0..2e9521d 100644
--- a/public_html/fr-FR/toc.html
+++ b/public_html/fr-FR/toc.html
@@ -1478,7 +1478,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1.Cloud_Guide' class="book collapsed">
<a class="type" href="Fedora_Draft_Documentation/0.1/html/Cloud_Guide/index.html" onclick="window.top.location='./Fedora_Draft_Documentation/0.1/html/Cloud_Guide/index.html'"><span class="book">Cloud Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.Cloud_Guide.types' class="types" onclick="work=0;">
@@ -1560,6 +1562,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/gu-IN/Site_Statistics.html b/public_html/gu-IN/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/gu-IN/Site_Statistics.html
+++ b/public_html/gu-IN/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/gu-IN/opds-Community_Services_Infrastructure.xml b/public_html/gu-IN/opds-Community_Services_Infrastructure.xml
index 5a1c2ae..3fee1d2 100644
--- a/public_html/gu-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/gu-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds-Fedora.xml b/public_html/gu-IN/opds-Fedora.xml
index 73c3f6a..94d1550 100644
--- a/public_html/gu-IN/opds-Fedora.xml
+++ b/public_html/gu-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml
index 2657628..b3aad9e 100644
--- a/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds-Fedora_Core.xml b/public_html/gu-IN/opds-Fedora_Core.xml
index d4652ba..62e084d 100644
--- a/public_html/gu-IN/opds-Fedora_Core.xml
+++ b/public_html/gu-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds-Fedora_Draft_Documentation.xml b/public_html/gu-IN/opds-Fedora_Draft_Documentation.xml
index d9d152f..a15e996 100644
--- a/public_html/gu-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/gu-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>gu-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/gu-IN/opds-Fedora_Security_Team.xml b/public_html/gu-IN/opds-Fedora_Security_Team.xml
index 50a5f0f..af11dc1 100644
--- a/public_html/gu-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/gu-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds.xml b/public_html/gu-IN/opds.xml
index ac716ec..00eb9f4 100644
--- a/public_html/gu-IN/opds.xml
+++ b/public_html/gu-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/gu-IN/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/gu-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/gu-IN/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/gu-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/gu-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/gu-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/gu-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/gu-IN/toc.html b/public_html/gu-IN/toc.html
index 49a5140..dce60d2 100644
--- a/public_html/gu-IN/toc.html
+++ b/public_html/gu-IN/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/he-IL/Site_Statistics.html b/public_html/he-IL/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/he-IL/Site_Statistics.html
+++ b/public_html/he-IL/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/he-IL/opds-Community_Services_Infrastructure.xml b/public_html/he-IL/opds-Community_Services_Infrastructure.xml
index 3a1f7a0..a564ff0 100644
--- a/public_html/he-IL/opds-Community_Services_Infrastructure.xml
+++ b/public_html/he-IL/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds-Fedora.xml b/public_html/he-IL/opds-Fedora.xml
index 0395884..4e394db 100644
--- a/public_html/he-IL/opds-Fedora.xml
+++ b/public_html/he-IL/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml b/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml
index fba0c64..f2e8e82 100644
--- a/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds-Fedora_Core.xml b/public_html/he-IL/opds-Fedora_Core.xml
index 7a68715..9edb5b7 100644
--- a/public_html/he-IL/opds-Fedora_Core.xml
+++ b/public_html/he-IL/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds-Fedora_Draft_Documentation.xml b/public_html/he-IL/opds-Fedora_Draft_Documentation.xml
index 81969b5..646b736 100644
--- a/public_html/he-IL/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/he-IL/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>he-IL</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/he-IL/opds-Fedora_Security_Team.xml b/public_html/he-IL/opds-Fedora_Security_Team.xml
index 278730f..4f83018 100644
--- a/public_html/he-IL/opds-Fedora_Security_Team.xml
+++ b/public_html/he-IL/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds.xml b/public_html/he-IL/opds.xml
index 14e6908..8a91a13 100644
--- a/public_html/he-IL/opds.xml
+++ b/public_html/he-IL/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/he-IL/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/he-IL/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/he-IL/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/he-IL/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/he-IL/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/he-IL/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/he-IL/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/he-IL/toc.html b/public_html/he-IL/toc.html
index 50cbf74..b119da3 100644
--- a/public_html/he-IL/toc.html
+++ b/public_html/he-IL/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/hi-IN/Site_Statistics.html b/public_html/hi-IN/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/hi-IN/Site_Statistics.html
+++ b/public_html/hi-IN/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/hi-IN/opds-Community_Services_Infrastructure.xml b/public_html/hi-IN/opds-Community_Services_Infrastructure.xml
index cabda73..d8eed57 100644
--- a/public_html/hi-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/hi-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds-Fedora.xml b/public_html/hi-IN/opds-Fedora.xml
index f7dc196..6888237 100644
--- a/public_html/hi-IN/opds-Fedora.xml
+++ b/public_html/hi-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml
index a69f6ce..738ae5a 100644
--- a/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds-Fedora_Core.xml b/public_html/hi-IN/opds-Fedora_Core.xml
index 68cdff6..cfc5cf1 100644
--- a/public_html/hi-IN/opds-Fedora_Core.xml
+++ b/public_html/hi-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds-Fedora_Draft_Documentation.xml b/public_html/hi-IN/opds-Fedora_Draft_Documentation.xml
index 0fe2689..4f5f963 100644
--- a/public_html/hi-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/hi-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>hi-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/hi-IN/opds-Fedora_Security_Team.xml b/public_html/hi-IN/opds-Fedora_Security_Team.xml
index ee395ff..cd2e4ef 100644
--- a/public_html/hi-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/hi-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds.xml b/public_html/hi-IN/opds.xml
index 78fdb83..53fc32c 100644
--- a/public_html/hi-IN/opds.xml
+++ b/public_html/hi-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/hi-IN/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/hi-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/hi-IN/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/hi-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/hi-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/hi-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/hi-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/hi-IN/toc.html b/public_html/hi-IN/toc.html
index 7e55d9c..17c488e 100644
--- a/public_html/hi-IN/toc.html
+++ b/public_html/hi-IN/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/hu-HU/Site_Statistics.html b/public_html/hu-HU/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/hu-HU/Site_Statistics.html
+++ b/public_html/hu-HU/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/hu-HU/opds-Community_Services_Infrastructure.xml b/public_html/hu-HU/opds-Community_Services_Infrastructure.xml
index 46c00ac..4ac3bff 100644
--- a/public_html/hu-HU/opds-Community_Services_Infrastructure.xml
+++ b/public_html/hu-HU/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds-Fedora.xml b/public_html/hu-HU/opds-Fedora.xml
index 0929697..47a1edd 100644
--- a/public_html/hu-HU/opds-Fedora.xml
+++ b/public_html/hu-HU/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml b/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml
index 37f4f7f..3765346 100644
--- a/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds-Fedora_Core.xml b/public_html/hu-HU/opds-Fedora_Core.xml
index efcbd87..1441dde 100644
--- a/public_html/hu-HU/opds-Fedora_Core.xml
+++ b/public_html/hu-HU/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds-Fedora_Draft_Documentation.xml b/public_html/hu-HU/opds-Fedora_Draft_Documentation.xml
index 0af7850..17865b3 100644
--- a/public_html/hu-HU/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/hu-HU/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>hu-HU</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/hu-HU/opds-Fedora_Security_Team.xml b/public_html/hu-HU/opds-Fedora_Security_Team.xml
index 42b905a..631f0df 100644
--- a/public_html/hu-HU/opds-Fedora_Security_Team.xml
+++ b/public_html/hu-HU/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds.xml b/public_html/hu-HU/opds.xml
index 1cd658a..0cb1086 100644
--- a/public_html/hu-HU/opds.xml
+++ b/public_html/hu-HU/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/hu-HU/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/hu-HU/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/hu-HU/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/hu-HU/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/hu-HU/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/hu-HU/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/hu-HU/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/hu-HU/toc.html b/public_html/hu-HU/toc.html
index a830b43..322c271 100644
--- a/public_html/hu-HU/toc.html
+++ b/public_html/hu-HU/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/ia/Site_Statistics.html b/public_html/ia/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/ia/Site_Statistics.html
+++ b/public_html/ia/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/ia/opds-Community_Services_Infrastructure.xml b/public_html/ia/opds-Community_Services_Infrastructure.xml
index d2b1ab2..eea8893 100644
--- a/public_html/ia/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ia/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ia/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ia/opds-Fedora.xml b/public_html/ia/opds-Fedora.xml
index 27b7b72..38f7515 100644
--- a/public_html/ia/opds-Fedora.xml
+++ b/public_html/ia/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ia/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ia/opds-Fedora_Contributor_Documentation.xml b/public_html/ia/opds-Fedora_Contributor_Documentation.xml
index e890474..b5d0d90 100644
--- a/public_html/ia/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ia/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ia/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ia/opds-Fedora_Core.xml b/public_html/ia/opds-Fedora_Core.xml
index d47b3ad..ca091cb 100644
--- a/public_html/ia/opds-Fedora_Core.xml
+++ b/public_html/ia/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ia/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ia/opds-Fedora_Draft_Documentation.xml b/public_html/ia/opds-Fedora_Draft_Documentation.xml
index 88bbf66..23da735 100644
--- a/public_html/ia/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ia/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ia/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>ia</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/ia/opds-Fedora_Security_Team.xml b/public_html/ia/opds-Fedora_Security_Team.xml
index acc091d..a9a3458 100644
--- a/public_html/ia/opds-Fedora_Security_Team.xml
+++ b/public_html/ia/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ia/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ia/opds.xml b/public_html/ia/opds.xml
index 419d3b5..8387628 100644
--- a/public_html/ia/opds.xml
+++ b/public_html/ia/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ia/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/ia/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ia/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ia/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ia/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ia/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/ia/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ia/toc.html b/public_html/ia/toc.html
index a19037e..4ff6d45 100644
--- a/public_html/ia/toc.html
+++ b/public_html/ia/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/id-ID/Site_Statistics.html b/public_html/id-ID/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/id-ID/Site_Statistics.html
+++ b/public_html/id-ID/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/id-ID/opds-Community_Services_Infrastructure.xml b/public_html/id-ID/opds-Community_Services_Infrastructure.xml
index 99499d1..b1dcc5a 100644
--- a/public_html/id-ID/opds-Community_Services_Infrastructure.xml
+++ b/public_html/id-ID/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds-Fedora.xml b/public_html/id-ID/opds-Fedora.xml
index ccd323a..e97cf92 100644
--- a/public_html/id-ID/opds-Fedora.xml
+++ b/public_html/id-ID/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml b/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml
index 54e0018..d81a84d 100644
--- a/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds-Fedora_Core.xml b/public_html/id-ID/opds-Fedora_Core.xml
index d47add9..9193f64 100644
--- a/public_html/id-ID/opds-Fedora_Core.xml
+++ b/public_html/id-ID/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds-Fedora_Draft_Documentation.xml b/public_html/id-ID/opds-Fedora_Draft_Documentation.xml
index 1ce45a0..8dd7ea6 100644
--- a/public_html/id-ID/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/id-ID/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>id-ID</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/id-ID/opds-Fedora_Security_Team.xml b/public_html/id-ID/opds-Fedora_Security_Team.xml
index cfa14fa..32d395b 100644
--- a/public_html/id-ID/opds-Fedora_Security_Team.xml
+++ b/public_html/id-ID/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds.xml b/public_html/id-ID/opds.xml
index b6ed48b..7c01fdf 100644
--- a/public_html/id-ID/opds.xml
+++ b/public_html/id-ID/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/id-ID/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/id-ID/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/id-ID/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/id-ID/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/id-ID/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/id-ID/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/id-ID/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/id-ID/toc.html b/public_html/id-ID/toc.html
index 9d8f146..094fa57 100644
--- a/public_html/id-ID/toc.html
+++ b/public_html/id-ID/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/it-IT/Site_Statistics.html b/public_html/it-IT/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/it-IT/Site_Statistics.html
+++ b/public_html/it-IT/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/it-IT/opds-Community_Services_Infrastructure.xml b/public_html/it-IT/opds-Community_Services_Infrastructure.xml
index 109be73..ed2d223 100644
--- a/public_html/it-IT/opds-Community_Services_Infrastructure.xml
+++ b/public_html/it-IT/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds-Fedora.xml b/public_html/it-IT/opds-Fedora.xml
index 18a786e..9a0cc7e 100644
--- a/public_html/it-IT/opds-Fedora.xml
+++ b/public_html/it-IT/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml b/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml
index 9189462..8c47cbc 100644
--- a/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Fedora_Contributor_Documentation.xml</id>
<title>Documentazione Collaboratori Fedora</title>
<subtitle>Documentazione Collaboratori Fedora</subtitle>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds-Fedora_Core.xml b/public_html/it-IT/opds-Fedora_Core.xml
index 4ea8f11..98b9516 100644
--- a/public_html/it-IT/opds-Fedora_Core.xml
+++ b/public_html/it-IT/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds-Fedora_Draft_Documentation.xml b/public_html/it-IT/opds-Fedora_Draft_Documentation.xml
index 9e516a9..f7cc0de 100644
--- a/public_html/it-IT/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/it-IT/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>it-IT</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/it-IT/opds-Fedora_Security_Team.xml b/public_html/it-IT/opds-Fedora_Security_Team.xml
index edf63c9..bbd15fa 100644
--- a/public_html/it-IT/opds-Fedora_Security_Team.xml
+++ b/public_html/it-IT/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds.xml b/public_html/it-IT/opds.xml
index b9ed2c6..99e1c2e 100644
--- a/public_html/it-IT/opds.xml
+++ b/public_html/it-IT/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/it-IT/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/it-IT/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Documentazione Collaboratori Fedora</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/it-IT/toc.html b/public_html/it-IT/toc.html
index 48c8d89..6da7872 100644
--- a/public_html/it-IT/toc.html
+++ b/public_html/it-IT/toc.html
@@ -1670,7 +1670,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1752,6 +1754,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/ja-JP/Site_Statistics.html b/public_html/ja-JP/Site_Statistics.html
index cd6fe44..59ea500 100644
--- a/public_html/ja-JP/Site_Statistics.html
+++ b/public_html/ja-JP/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>言語数の合計: </b>44<br />
- <b>パッケージ数の合計: </b>861
+ <b>パッケージ数の合計: </b>862
</div>
</body>
</html>
diff --git a/public_html/ja-JP/opds-Community_Services_Infrastructure.xml b/public_html/ja-JP/opds-Community_Services_Infrastructure.xml
index 5b1a59d..a6902b8 100644
--- a/public_html/ja-JP/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ja-JP/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds-Fedora.xml b/public_html/ja-JP/opds-Fedora.xml
index a29695c..1d139f5 100644
--- a/public_html/ja-JP/opds-Fedora.xml
+++ b/public_html/ja-JP/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:11</updated>
+ <updated>2013-05-28T13:53:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml b/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml
index e9babb7..96ee01d 100644
--- a/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora コントリビュータ用ドキュメント</title>
<subtitle>Fedora コントリビュータ用ドキュメント</subtitle>
- <updated>2013-05-27T08:01:11</updated>
+ <updated>2013-05-28T13:53:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds-Fedora_Core.xml b/public_html/ja-JP/opds-Fedora_Core.xml
index 44bcecf..e4c85b9 100644
--- a/public_html/ja-JP/opds-Fedora_Core.xml
+++ b/public_html/ja-JP/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:11</updated>
+ <updated>2013-05-28T13:53:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds-Fedora_Draft_Documentation.xml b/public_html/ja-JP/opds-Fedora_Draft_Documentation.xml
index 5e5096e..fbebe25 100644
--- a/public_html/ja-JP/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ja-JP/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora ドラフト文書</title>
<subtitle>Fedora ドラフト文書</subtitle>
- <updated>2013-05-27T08:01:11</updated>
+ <updated>2013-05-28T13:53:22</updated>
<!--author>
<name></name>
<uri></uri>
@@ -180,6 +180,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>ja-JP</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/ja-JP/opds-Fedora_Security_Team.xml b/public_html/ja-JP/opds-Fedora_Security_Team.xml
index 73255dc..3f06359 100644
--- a/public_html/ja-JP/opds-Fedora_Security_Team.xml
+++ b/public_html/ja-JP/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:11</updated>
+ <updated>2013-05-28T13:53:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds.xml b/public_html/ja-JP/opds.xml
index 74e310b..2d3db3f 100644
--- a/public_html/ja-JP/opds.xml
+++ b/public_html/ja-JP/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ja-JP/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:11</updated>
+ <updated>2013-05-28T13:53:22</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/ja-JP/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:11</updated>
+ <updated>2013-05-28T13:53:22</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora コントリビュータ用ドキュメント</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:11</updated>
+ <updated>2013-05-28T13:53:22</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:11</updated>
+ <updated>2013-05-28T13:53:22</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora ドラフト文書</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:11</updated>
+ <updated>2013-05-28T13:53:22</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:11</updated>
+ <updated>2013-05-28T13:53:22</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ja-JP/toc.html b/public_html/ja-JP/toc.html
index 94b8bc9..d08a8cf 100644
--- a/public_html/ja-JP/toc.html
+++ b/public_html/ja-JP/toc.html
@@ -1528,7 +1528,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora ドラフト文書</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1.Cloud_Guide' class="book collapsed">
<a class="type" href="Fedora_Draft_Documentation/0.1/html/Cloud_Guide/index.html" onclick="window.top.location='./Fedora_Draft_Documentation/0.1/html/Cloud_Guide/index.html'"><span class="book">Cloud Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.Cloud_Guide.types' class="types" onclick="work=0;">
@@ -1612,6 +1614,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/kn-IN/Site_Statistics.html b/public_html/kn-IN/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/kn-IN/Site_Statistics.html
+++ b/public_html/kn-IN/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/kn-IN/opds-Community_Services_Infrastructure.xml b/public_html/kn-IN/opds-Community_Services_Infrastructure.xml
index c58c6b3..e97e49d 100644
--- a/public_html/kn-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/kn-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:11</updated>
+ <updated>2013-05-28T13:53:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds-Fedora.xml b/public_html/kn-IN/opds-Fedora.xml
index 2be6388..f2222f7 100644
--- a/public_html/kn-IN/opds-Fedora.xml
+++ b/public_html/kn-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:11</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml
index 2137634..558592f 100644
--- a/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:11</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds-Fedora_Core.xml b/public_html/kn-IN/opds-Fedora_Core.xml
index eda6c35..fa6f2ac 100644
--- a/public_html/kn-IN/opds-Fedora_Core.xml
+++ b/public_html/kn-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:11</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds-Fedora_Draft_Documentation.xml b/public_html/kn-IN/opds-Fedora_Draft_Documentation.xml
index 56d0cfd..3bc1fe5 100644
--- a/public_html/kn-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/kn-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:11</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>kn-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/kn-IN/opds-Fedora_Security_Team.xml b/public_html/kn-IN/opds-Fedora_Security_Team.xml
index 87fd411..aa8856e 100644
--- a/public_html/kn-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/kn-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:11</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds.xml b/public_html/kn-IN/opds.xml
index 664a257..8532131 100644
--- a/public_html/kn-IN/opds.xml
+++ b/public_html/kn-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/kn-IN/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:11</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/kn-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:11</updated>
+ <updated>2013-05-28T13:53:22</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/kn-IN/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:11</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/kn-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:11</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/kn-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:11</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/kn-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:11</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/kn-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:11</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/kn-IN/toc.html b/public_html/kn-IN/toc.html
index e7f61e1..63021fc 100644
--- a/public_html/kn-IN/toc.html
+++ b/public_html/kn-IN/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/ko-KR/Site_Statistics.html b/public_html/ko-KR/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/ko-KR/Site_Statistics.html
+++ b/public_html/ko-KR/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/ko-KR/opds-Community_Services_Infrastructure.xml b/public_html/ko-KR/opds-Community_Services_Infrastructure.xml
index 04acada..a2004fd 100644
--- a/public_html/ko-KR/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ko-KR/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds-Fedora.xml b/public_html/ko-KR/opds-Fedora.xml
index de18a2b..219dd05 100644
--- a/public_html/ko-KR/opds-Fedora.xml
+++ b/public_html/ko-KR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml b/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml
index c4a1d6f..e546b68 100644
--- a/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds-Fedora_Core.xml b/public_html/ko-KR/opds-Fedora_Core.xml
index f11193c..13c51b6 100644
--- a/public_html/ko-KR/opds-Fedora_Core.xml
+++ b/public_html/ko-KR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds-Fedora_Draft_Documentation.xml b/public_html/ko-KR/opds-Fedora_Draft_Documentation.xml
index 6aa7bd1..9e8beb6 100644
--- a/public_html/ko-KR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ko-KR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>ko-KR</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/ko-KR/opds-Fedora_Security_Team.xml b/public_html/ko-KR/opds-Fedora_Security_Team.xml
index c81d344..20977ab 100644
--- a/public_html/ko-KR/opds-Fedora_Security_Team.xml
+++ b/public_html/ko-KR/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds.xml b/public_html/ko-KR/opds.xml
index 68a02b5..212c94c 100644
--- a/public_html/ko-KR/opds.xml
+++ b/public_html/ko-KR/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ko-KR/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/ko-KR/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ko-KR/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ko-KR/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ko-KR/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ko-KR/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/ko-KR/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ko-KR/toc.html b/public_html/ko-KR/toc.html
index 60774a7..66e54d0 100644
--- a/public_html/ko-KR/toc.html
+++ b/public_html/ko-KR/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/ml-IN/Site_Statistics.html b/public_html/ml-IN/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/ml-IN/Site_Statistics.html
+++ b/public_html/ml-IN/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/ml-IN/opds-Community_Services_Infrastructure.xml b/public_html/ml-IN/opds-Community_Services_Infrastructure.xml
index 6f6e95b..095a779 100644
--- a/public_html/ml-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ml-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds-Fedora.xml b/public_html/ml-IN/opds-Fedora.xml
index bc26d08..58979e8 100644
--- a/public_html/ml-IN/opds-Fedora.xml
+++ b/public_html/ml-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml
index 5301acb..e6bb191 100644
--- a/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds-Fedora_Core.xml b/public_html/ml-IN/opds-Fedora_Core.xml
index 2dc9364..6e50e0d 100644
--- a/public_html/ml-IN/opds-Fedora_Core.xml
+++ b/public_html/ml-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds-Fedora_Draft_Documentation.xml b/public_html/ml-IN/opds-Fedora_Draft_Documentation.xml
index a3c1631..654d8ce 100644
--- a/public_html/ml-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ml-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>ml-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/ml-IN/opds-Fedora_Security_Team.xml b/public_html/ml-IN/opds-Fedora_Security_Team.xml
index 9bbe479..02fba5c 100644
--- a/public_html/ml-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/ml-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds.xml b/public_html/ml-IN/opds.xml
index ecae324..97df60a 100644
--- a/public_html/ml-IN/opds.xml
+++ b/public_html/ml-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ml-IN/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/ml-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ml-IN/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ml-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ml-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ml-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/ml-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ml-IN/toc.html b/public_html/ml-IN/toc.html
index 78c4683..4848fa9 100644
--- a/public_html/ml-IN/toc.html
+++ b/public_html/ml-IN/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/mr-IN/Site_Statistics.html b/public_html/mr-IN/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/mr-IN/Site_Statistics.html
+++ b/public_html/mr-IN/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/mr-IN/opds-Community_Services_Infrastructure.xml b/public_html/mr-IN/opds-Community_Services_Infrastructure.xml
index a4d4ecf..fa4d97f 100644
--- a/public_html/mr-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/mr-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds-Fedora.xml b/public_html/mr-IN/opds-Fedora.xml
index 2a49efd..9e3f9eb 100644
--- a/public_html/mr-IN/opds-Fedora.xml
+++ b/public_html/mr-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml
index 9648fc9..dad981d 100644
--- a/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds-Fedora_Core.xml b/public_html/mr-IN/opds-Fedora_Core.xml
index 2e2abcc..f06f868 100644
--- a/public_html/mr-IN/opds-Fedora_Core.xml
+++ b/public_html/mr-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds-Fedora_Draft_Documentation.xml b/public_html/mr-IN/opds-Fedora_Draft_Documentation.xml
index 097a124..12bf9e5 100644
--- a/public_html/mr-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/mr-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>mr-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/mr-IN/opds-Fedora_Security_Team.xml b/public_html/mr-IN/opds-Fedora_Security_Team.xml
index 76d91d1..bccfeed 100644
--- a/public_html/mr-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/mr-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds.xml b/public_html/mr-IN/opds.xml
index 3b70b8e..5105955 100644
--- a/public_html/mr-IN/opds.xml
+++ b/public_html/mr-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/mr-IN/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/mr-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/mr-IN/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/mr-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/mr-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/mr-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/mr-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/mr-IN/toc.html b/public_html/mr-IN/toc.html
index 3310bc0..a4ac4e7 100644
--- a/public_html/mr-IN/toc.html
+++ b/public_html/mr-IN/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/nb-NO/Site_Statistics.html b/public_html/nb-NO/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/nb-NO/Site_Statistics.html
+++ b/public_html/nb-NO/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/nb-NO/opds-Community_Services_Infrastructure.xml b/public_html/nb-NO/opds-Community_Services_Infrastructure.xml
index 2732e8b..e3660b5 100644
--- a/public_html/nb-NO/opds-Community_Services_Infrastructure.xml
+++ b/public_html/nb-NO/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds-Fedora.xml b/public_html/nb-NO/opds-Fedora.xml
index 5649619..a5cdcc7 100644
--- a/public_html/nb-NO/opds-Fedora.xml
+++ b/public_html/nb-NO/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml b/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml
index 5cbba1c..9e9536c 100644
--- a/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds-Fedora_Core.xml b/public_html/nb-NO/opds-Fedora_Core.xml
index 042cf78..d87e57f 100644
--- a/public_html/nb-NO/opds-Fedora_Core.xml
+++ b/public_html/nb-NO/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds-Fedora_Draft_Documentation.xml b/public_html/nb-NO/opds-Fedora_Draft_Documentation.xml
index 12333aa..2d7aee7 100644
--- a/public_html/nb-NO/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/nb-NO/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>nb-NO</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/nb-NO/opds-Fedora_Security_Team.xml b/public_html/nb-NO/opds-Fedora_Security_Team.xml
index 50b5427..aeaf456 100644
--- a/public_html/nb-NO/opds-Fedora_Security_Team.xml
+++ b/public_html/nb-NO/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds.xml b/public_html/nb-NO/opds.xml
index 6860e27..6fecfc1 100644
--- a/public_html/nb-NO/opds.xml
+++ b/public_html/nb-NO/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/nb-NO/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:23</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/nb-NO/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/nb-NO/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/nb-NO/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/nb-NO/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/nb-NO/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/nb-NO/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/nb-NO/toc.html b/public_html/nb-NO/toc.html
index 01bc186..0aad4cc 100644
--- a/public_html/nb-NO/toc.html
+++ b/public_html/nb-NO/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/nl-NL/Site_Statistics.html b/public_html/nl-NL/Site_Statistics.html
index 21e6d4f..1b9f278 100644
--- a/public_html/nl-NL/Site_Statistics.html
+++ b/public_html/nl-NL/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Totaal talen: </b>44<br />
- <b>Totaal pakketten: </b>861
+ <b>Totaal pakketten: </b>862
</div>
</body>
</html>
diff --git a/public_html/nl-NL/opds-Community_Services_Infrastructure.xml b/public_html/nl-NL/opds-Community_Services_Infrastructure.xml
index b3f955c..2d62b7d 100644
--- a/public_html/nl-NL/opds-Community_Services_Infrastructure.xml
+++ b/public_html/nl-NL/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds-Fedora.xml b/public_html/nl-NL/opds-Fedora.xml
index a58b7a5..4ac0027 100644
--- a/public_html/nl-NL/opds-Fedora.xml
+++ b/public_html/nl-NL/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml b/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml
index d81afea..4947c02 100644
--- a/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds-Fedora_Core.xml b/public_html/nl-NL/opds-Fedora_Core.xml
index 3d43857..46aac1c 100644
--- a/public_html/nl-NL/opds-Fedora_Core.xml
+++ b/public_html/nl-NL/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds-Fedora_Draft_Documentation.xml b/public_html/nl-NL/opds-Fedora_Draft_Documentation.xml
index 002c97e..929f236 100644
--- a/public_html/nl-NL/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/nl-NL/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>nl-NL</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/nl-NL/opds-Fedora_Security_Team.xml b/public_html/nl-NL/opds-Fedora_Security_Team.xml
index b24534e..83b52b9 100644
--- a/public_html/nl-NL/opds-Fedora_Security_Team.xml
+++ b/public_html/nl-NL/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds.xml b/public_html/nl-NL/opds.xml
index 8515a71..50d9deb 100644
--- a/public_html/nl-NL/opds.xml
+++ b/public_html/nl-NL/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/nl-NL/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/nl-NL/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/nl-NL/toc.html b/public_html/nl-NL/toc.html
index 8c830c2..1a9a0db 100644
--- a/public_html/nl-NL/toc.html
+++ b/public_html/nl-NL/toc.html
@@ -1706,7 +1706,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Onvertaald</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1788,6 +1790,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/opds.xml b/public_html/opds.xml
index d86bbc8..d72ee1f 100644
--- a/public_html/opds.xml
+++ b/public_html/opds.xml
@@ -7,7 +7,7 @@
<link rel="start" href="http://docs.fedoraproject.org/opds.xml" type="application/atom+xml;type=feed;profile=opds-catalog"/>
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<title>Fedora Documentation</title>
- <updated>2013-05-27T08:01:18</updated>
+ <updated>2013-05-28T13:53:28</updated>
<!--author>
<name></name>
<uri></uri>
@@ -16,7 +16,7 @@
<entry>
<title>অসমীয়া</title>
<id>as-IN/opds.xml</id>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="as-IN/opds.xml"/>
@@ -24,7 +24,7 @@
<entry>
<title>български</title>
<id>bg-BG/opds.xml</id>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="bg-BG/opds.xml"/>
@@ -32,7 +32,7 @@
<entry>
<title>বাংলা</title>
<id>bn-IN/opds.xml</id>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:15</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="bn-IN/opds.xml"/>
@@ -40,7 +40,7 @@
<entry>
<title>Bosanski</title>
<id>bs-BA/opds.xml</id>
- <updated>2013-05-27T08:01:04</updated>
+ <updated>2013-05-28T13:53:16</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="bs-BA/opds.xml"/>
@@ -48,7 +48,7 @@
<entry>
<title>Català</title>
<id>ca-ES/opds.xml</id>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:16</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ca-ES/opds.xml"/>
@@ -56,7 +56,7 @@
<entry>
<title>Čeština</title>
<id>cs-CZ/opds.xml</id>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:17</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="cs-CZ/opds.xml"/>
@@ -64,7 +64,7 @@
<entry>
<title>Dansk</title>
<id>da-DK/opds.xml</id>
- <updated>2013-05-27T08:01:05</updated>
+ <updated>2013-05-28T13:53:17</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="da-DK/opds.xml"/>
@@ -72,7 +72,7 @@
<entry>
<title>Deutsch</title>
<id>de-DE/opds.xml</id>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:17</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="de-DE/opds.xml"/>
@@ -80,7 +80,7 @@
<entry>
<title>Ελληνικά</title>
<id>el-GR/opds.xml</id>
- <updated>2013-05-27T08:01:06</updated>
+ <updated>2013-05-28T13:53:18</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="el-GR/opds.xml"/>
@@ -88,7 +88,7 @@
<entry>
<title>English</title>
<id>en-US/opds.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:18</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="en-US/opds.xml"/>
@@ -96,7 +96,7 @@
<entry>
<title>Español</title>
<id>es-ES/opds.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="es-ES/opds.xml"/>
@@ -104,7 +104,7 @@
<entry>
<title>فارسی</title>
<id>fa-IR/opds.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:19</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="fa-IR/opds.xml"/>
@@ -112,7 +112,7 @@
<entry>
<title>Suomi</title>
<id>fi-FI/opds.xml</id>
- <updated>2013-05-27T08:01:07</updated>
+ <updated>2013-05-28T13:53:20</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="fi-FI/opds.xml"/>
@@ -120,7 +120,7 @@
<entry>
<title>Français</title>
<id>fr-FR/opds.xml</id>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="fr-FR/opds.xml"/>
@@ -128,7 +128,7 @@
<entry>
<title>ગુજરાતી</title>
<id>gu-IN/opds.xml</id>
- <updated>2013-05-27T08:01:08</updated>
+ <updated>2013-05-28T13:53:20</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="gu-IN/opds.xml"/>
@@ -136,7 +136,7 @@
<entry>
<title>עברית</title>
<id>he-IL/opds.xml</id>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="he-IL/opds.xml"/>
@@ -144,7 +144,7 @@
<entry>
<title>हिन्दी</title>
<id>hi-IN/opds.xml</id>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="hi-IN/opds.xml"/>
@@ -152,7 +152,7 @@
<entry>
<title>Magyar</title>
<id>hu-HU/opds.xml</id>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="hu-HU/opds.xml"/>
@@ -160,7 +160,7 @@
<entry>
<title>Interlingua</title>
<id>ia/opds.xml</id>
- <updated>2013-05-27T08:01:09</updated>
+ <updated>2013-05-28T13:53:21</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ia/opds.xml"/>
@@ -168,7 +168,7 @@
<entry>
<title>Indonesia</title>
<id>id-ID/opds.xml</id>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="id-ID/opds.xml"/>
@@ -176,7 +176,7 @@
<entry>
<title>Italiano</title>
<id>it-IT/opds.xml</id>
- <updated>2013-05-27T08:01:10</updated>
+ <updated>2013-05-28T13:53:22</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="it-IT/opds.xml"/>
@@ -184,7 +184,7 @@
<entry>
<title>日本語</title>
<id>ja-JP/opds.xml</id>
- <updated>2013-05-27T08:01:11</updated>
+ <updated>2013-05-28T13:53:22</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ja-JP/opds.xml"/>
@@ -192,7 +192,7 @@
<entry>
<title>ಕನ್ನಡ</title>
<id>kn-IN/opds.xml</id>
- <updated>2013-05-27T08:01:11</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="kn-IN/opds.xml"/>
@@ -200,7 +200,7 @@
<entry>
<title>한국어</title>
<id>ko-KR/opds.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ko-KR/opds.xml"/>
@@ -208,7 +208,7 @@
<entry>
<title>മലയാളം</title>
<id>ml-IN/opds.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ml-IN/opds.xml"/>
@@ -216,7 +216,7 @@
<entry>
<title>मराठी</title>
<id>mr-IN/opds.xml</id>
- <updated>2013-05-27T08:01:12</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="mr-IN/opds.xml"/>
@@ -224,7 +224,7 @@
<entry>
<title>Norsk (bokmål)</title>
<id>nb-NO/opds.xml</id>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:23</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="nb-NO/opds.xml"/>
@@ -232,7 +232,7 @@
<entry>
<title>Nederlands</title>
<id>nl-NL/opds.xml</id>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="nl-NL/opds.xml"/>
@@ -240,7 +240,7 @@
<entry>
<title>ଓଡ଼ିଆ</title>
<id>or-IN/opds.xml</id>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="or-IN/opds.xml"/>
@@ -248,7 +248,7 @@
<entry>
<title>ਪੰਜਾਬੀ</title>
<id>pa-IN/opds.xml</id>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pa-IN/opds.xml"/>
@@ -256,7 +256,7 @@
<entry>
<title>Polski</title>
<id>pl-PL/opds.xml</id>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pl-PL/opds.xml"/>
@@ -264,7 +264,7 @@
<entry>
<title>Português Brasileiro</title>
<id>pt-BR/opds.xml</id>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pt-BR/opds.xml"/>
@@ -272,7 +272,7 @@
<entry>
<title>Português</title>
<id>pt-PT/opds.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pt-PT/opds.xml"/>
@@ -280,7 +280,7 @@
<entry>
<title>Romanian</title>
<id>ro/opds.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ro/opds.xml"/>
@@ -288,7 +288,7 @@
<entry>
<title>Русский</title>
<id>ru-RU/opds.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ru-RU/opds.xml"/>
@@ -296,7 +296,7 @@
<entry>
<title>Slovenščina</title>
<id>sk-SK/opds.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sk-SK/opds.xml"/>
@@ -304,7 +304,7 @@
<entry>
<title>Srpski (latinica)</title>
<id>sr-Latn-RS/opds.xml</id>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sr-Latn-RS/opds.xml"/>
@@ -312,7 +312,7 @@
<entry>
<title>Српски</title>
<id>sr-RS/opds.xml</id>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sr-RS/opds.xml"/>
@@ -320,7 +320,7 @@
<entry>
<title>Svenska</title>
<id>sv-SE/opds.xml</id>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sv-SE/opds.xml"/>
@@ -328,7 +328,7 @@
<entry>
<title>தமிழ்</title>
<id>ta-IN/opds.xml</id>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ta-IN/opds.xml"/>
@@ -336,7 +336,7 @@
<entry>
<title>తెలుగు</title>
<id>te-IN/opds.xml</id>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="te-IN/opds.xml"/>
@@ -344,7 +344,7 @@
<entry>
<title>Українська</title>
<id>uk-UA/opds.xml</id>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="uk-UA/opds.xml"/>
@@ -352,7 +352,7 @@
<entry>
<title>简体中文</title>
<id>zh-CN/opds.xml</id>
- <updated>2013-05-27T08:01:18</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="zh-CN/opds.xml"/>
@@ -360,7 +360,7 @@
<entry>
<title>繁體中文</title>
<id>zh-TW/opds.xml</id>
- <updated>2013-05-27T08:01:18</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="zh-TW/opds.xml"/>
diff --git a/public_html/or-IN/Site_Statistics.html b/public_html/or-IN/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/or-IN/Site_Statistics.html
+++ b/public_html/or-IN/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/or-IN/opds-Community_Services_Infrastructure.xml b/public_html/or-IN/opds-Community_Services_Infrastructure.xml
index 6a6ea1f..a963fa8 100644
--- a/public_html/or-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/or-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds-Fedora.xml b/public_html/or-IN/opds-Fedora.xml
index e285175..40862d4 100644
--- a/public_html/or-IN/opds-Fedora.xml
+++ b/public_html/or-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml
index 025639a..075ee93 100644
--- a/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds-Fedora_Core.xml b/public_html/or-IN/opds-Fedora_Core.xml
index 97db723..6d9833a 100644
--- a/public_html/or-IN/opds-Fedora_Core.xml
+++ b/public_html/or-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds-Fedora_Draft_Documentation.xml b/public_html/or-IN/opds-Fedora_Draft_Documentation.xml
index 7dedcb1..f7783f0 100644
--- a/public_html/or-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/or-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>or-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/or-IN/opds-Fedora_Security_Team.xml b/public_html/or-IN/opds-Fedora_Security_Team.xml
index cf5f2cb..361c554 100644
--- a/public_html/or-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/or-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds.xml b/public_html/or-IN/opds.xml
index e3ece48..a01ec89 100644
--- a/public_html/or-IN/opds.xml
+++ b/public_html/or-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/or-IN/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/or-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/or-IN/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/or-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/or-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/or-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/or-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/or-IN/toc.html b/public_html/or-IN/toc.html
index 135fce2..d890933 100644
--- a/public_html/or-IN/toc.html
+++ b/public_html/or-IN/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/pa-IN/Site_Statistics.html b/public_html/pa-IN/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/pa-IN/Site_Statistics.html
+++ b/public_html/pa-IN/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/pa-IN/opds-Community_Services_Infrastructure.xml b/public_html/pa-IN/opds-Community_Services_Infrastructure.xml
index 969f0bb..1dff4ac 100644
--- a/public_html/pa-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/pa-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds-Fedora.xml b/public_html/pa-IN/opds-Fedora.xml
index bfda68e..c031dc9 100644
--- a/public_html/pa-IN/opds-Fedora.xml
+++ b/public_html/pa-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml
index c7c6eb5..9869949 100644
--- a/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds-Fedora_Core.xml b/public_html/pa-IN/opds-Fedora_Core.xml
index ffd1e12..92f1d49 100644
--- a/public_html/pa-IN/opds-Fedora_Core.xml
+++ b/public_html/pa-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds-Fedora_Draft_Documentation.xml b/public_html/pa-IN/opds-Fedora_Draft_Documentation.xml
index 7b7eb66..5c14189 100644
--- a/public_html/pa-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pa-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>pa-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/pa-IN/opds-Fedora_Security_Team.xml b/public_html/pa-IN/opds-Fedora_Security_Team.xml
index 8abae43..4faf63c 100644
--- a/public_html/pa-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/pa-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds.xml b/public_html/pa-IN/opds.xml
index 9f19cae..5c6e2e9 100644
--- a/public_html/pa-IN/opds.xml
+++ b/public_html/pa-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/pa-IN/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/pa-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:13</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/pa-IN/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/pa-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/pa-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/pa-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/pa-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/pa-IN/toc.html b/public_html/pa-IN/toc.html
index 37e5041..88def7b 100644
--- a/public_html/pa-IN/toc.html
+++ b/public_html/pa-IN/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/pl-PL/Site_Statistics.html b/public_html/pl-PL/Site_Statistics.html
index ca57178..7856112 100644
--- a/public_html/pl-PL/Site_Statistics.html
+++ b/public_html/pl-PL/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Razem języków: </b>44<br />
- <b>Razem pakietów: </b>861
+ <b>Razem pakietów: </b>862
</div>
</body>
</html>
diff --git a/public_html/pl-PL/opds-Community_Services_Infrastructure.xml b/public_html/pl-PL/opds-Community_Services_Infrastructure.xml
index db4408f..7d6fdbc 100644
--- a/public_html/pl-PL/opds-Community_Services_Infrastructure.xml
+++ b/public_html/pl-PL/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds-Fedora.xml b/public_html/pl-PL/opds-Fedora.xml
index 93de3d8..594768c 100644
--- a/public_html/pl-PL/opds-Fedora.xml
+++ b/public_html/pl-PL/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml b/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml
index 503398c..31d7d29 100644
--- a/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Fedora_Contributor_Documentation.xml</id>
<title>Dokumentacja dla współtwórców Fedory</title>
<subtitle>Dokumentacja dla współtwórców Fedory</subtitle>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds-Fedora_Core.xml b/public_html/pl-PL/opds-Fedora_Core.xml
index 1ef2799..9e5580c 100644
--- a/public_html/pl-PL/opds-Fedora_Core.xml
+++ b/public_html/pl-PL/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds-Fedora_Draft_Documentation.xml b/public_html/pl-PL/opds-Fedora_Draft_Documentation.xml
index 8fe9c2b..aa500dc 100644
--- a/public_html/pl-PL/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pl-PL/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>pl-PL</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/pl-PL/opds-Fedora_Security_Team.xml b/public_html/pl-PL/opds-Fedora_Security_Team.xml
index d0baabf..76eda24 100644
--- a/public_html/pl-PL/opds-Fedora_Security_Team.xml
+++ b/public_html/pl-PL/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds.xml b/public_html/pl-PL/opds.xml
index d19e08b..4fdafb5 100644
--- a/public_html/pl-PL/opds.xml
+++ b/public_html/pl-PL/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/pl-PL/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/pl-PL/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/pl-PL/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Dokumentacja dla współtwórców Fedory</title>
<id>http://docs.fedoraproject.org/pl-PL/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/pl-PL/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/pl-PL/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/pl-PL/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:24</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/pl-PL/toc.html b/public_html/pl-PL/toc.html
index 46c446e..bae2083 100644
--- a/public_html/pl-PL/toc.html
+++ b/public_html/pl-PL/toc.html
@@ -1554,7 +1554,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Nieprzetłumaczone</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1636,6 +1638,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/pt-BR/Site_Statistics.html b/public_html/pt-BR/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/pt-BR/Site_Statistics.html
+++ b/public_html/pt-BR/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/pt-BR/opds-Community_Services_Infrastructure.xml b/public_html/pt-BR/opds-Community_Services_Infrastructure.xml
index 59dc107..9099ebc 100644
--- a/public_html/pt-BR/opds-Community_Services_Infrastructure.xml
+++ b/public_html/pt-BR/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds-Fedora.xml b/public_html/pt-BR/opds-Fedora.xml
index ba7de7d..2e312f4 100644
--- a/public_html/pt-BR/opds-Fedora.xml
+++ b/public_html/pt-BR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml b/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml
index b293eb5..e1fa357 100644
--- a/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds-Fedora_Core.xml b/public_html/pt-BR/opds-Fedora_Core.xml
index 7a85c6c..e2c81b1 100644
--- a/public_html/pt-BR/opds-Fedora_Core.xml
+++ b/public_html/pt-BR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds-Fedora_Draft_Documentation.xml b/public_html/pt-BR/opds-Fedora_Draft_Documentation.xml
index 29de2bb..5738fd7 100644
--- a/public_html/pt-BR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pt-BR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>pt-BR</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/pt-BR/opds-Fedora_Security_Team.xml b/public_html/pt-BR/opds-Fedora_Security_Team.xml
index 01b60c2..ff85381 100644
--- a/public_html/pt-BR/opds-Fedora_Security_Team.xml
+++ b/public_html/pt-BR/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds.xml b/public_html/pt-BR/opds.xml
index 6e87536..8a51d63 100644
--- a/public_html/pt-BR/opds.xml
+++ b/public_html/pt-BR/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/pt-BR/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/pt-BR/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/pt-BR/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/pt-BR/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/pt-BR/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/pt-BR/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/pt-BR/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/pt-BR/toc.html b/public_html/pt-BR/toc.html
index 7b2f3fa..e8fd9ff 100644
--- a/public_html/pt-BR/toc.html
+++ b/public_html/pt-BR/toc.html
@@ -1491,7 +1491,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1573,6 +1575,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/pt-PT/Site_Statistics.html b/public_html/pt-PT/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/pt-PT/Site_Statistics.html
+++ b/public_html/pt-PT/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/pt-PT/opds-Community_Services_Infrastructure.xml b/public_html/pt-PT/opds-Community_Services_Infrastructure.xml
index 4c9bd0f..5adbc70 100644
--- a/public_html/pt-PT/opds-Community_Services_Infrastructure.xml
+++ b/public_html/pt-PT/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds-Fedora.xml b/public_html/pt-PT/opds-Fedora.xml
index a553f78..86ea76a 100644
--- a/public_html/pt-PT/opds-Fedora.xml
+++ b/public_html/pt-PT/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml b/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml
index 6b3efeb..d6bb5dc 100644
--- a/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds-Fedora_Core.xml b/public_html/pt-PT/opds-Fedora_Core.xml
index e878c64..7396005 100644
--- a/public_html/pt-PT/opds-Fedora_Core.xml
+++ b/public_html/pt-PT/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds-Fedora_Draft_Documentation.xml b/public_html/pt-PT/opds-Fedora_Draft_Documentation.xml
index 8e95475..3c20829 100644
--- a/public_html/pt-PT/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pt-PT/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>pt-PT</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/pt-PT/opds-Fedora_Security_Team.xml b/public_html/pt-PT/opds-Fedora_Security_Team.xml
index f246c02..b48c4aa 100644
--- a/public_html/pt-PT/opds-Fedora_Security_Team.xml
+++ b/public_html/pt-PT/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds.xml b/public_html/pt-PT/opds.xml
index 2530b41..6afef78 100644
--- a/public_html/pt-PT/opds.xml
+++ b/public_html/pt-PT/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/pt-PT/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/pt-PT/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:14</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/pt-PT/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/pt-PT/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/pt-PT/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/pt-PT/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/pt-PT/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/pt-PT/toc.html b/public_html/pt-PT/toc.html
index bcdf7fc..9477927 100644
--- a/public_html/pt-PT/toc.html
+++ b/public_html/pt-PT/toc.html
@@ -1481,7 +1481,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1563,6 +1565,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/ro/Site_Statistics.html b/public_html/ro/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/ro/Site_Statistics.html
+++ b/public_html/ro/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/ro/opds-Community_Services_Infrastructure.xml b/public_html/ro/opds-Community_Services_Infrastructure.xml
index fd0e20d..5c96bb7 100644
--- a/public_html/ro/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ro/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ro/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ro/opds-Fedora.xml b/public_html/ro/opds-Fedora.xml
index 774f3d7..001a002 100644
--- a/public_html/ro/opds-Fedora.xml
+++ b/public_html/ro/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ro/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ro/opds-Fedora_Contributor_Documentation.xml b/public_html/ro/opds-Fedora_Contributor_Documentation.xml
index ba0c30d..922a0e1 100644
--- a/public_html/ro/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ro/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ro/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ro/opds-Fedora_Core.xml b/public_html/ro/opds-Fedora_Core.xml
index feeb2d9..1ff12fe 100644
--- a/public_html/ro/opds-Fedora_Core.xml
+++ b/public_html/ro/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ro/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ro/opds-Fedora_Draft_Documentation.xml b/public_html/ro/opds-Fedora_Draft_Documentation.xml
index 9b263c0..b96bf46 100644
--- a/public_html/ro/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ro/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ro/opds-Fedora_Draft_Documentation.xml</id>
<title>Schiță Documentație Fedora</title>
<subtitle>Schiță Documentație Fedora</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -164,6 +164,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>ro</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/ro/opds-Fedora_Security_Team.xml b/public_html/ro/opds-Fedora_Security_Team.xml
index d6a55cb..85e60a0 100644
--- a/public_html/ro/opds-Fedora_Security_Team.xml
+++ b/public_html/ro/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ro/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ro/opds.xml b/public_html/ro/opds.xml
index de460ac..89c8e69 100644
--- a/public_html/ro/opds.xml
+++ b/public_html/ro/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ro/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/ro/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ro/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ro/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ro/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Schiță Documentație Fedora</title>
<id>http://docs.fedoraproject.org/ro/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/ro/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ro/toc.html b/public_html/ro/toc.html
index 02b1d52..7a13e9b 100644
--- a/public_html/ro/toc.html
+++ b/public_html/ro/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Schiță Documentație Fedora</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed">
<a class="type" href="Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='./Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">Ghid RPM</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.types' class="types" onclick="work=0;">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/ru-RU/Site_Statistics.html b/public_html/ru-RU/Site_Statistics.html
index 6b4d4ba..5a1df93 100644
--- a/public_html/ru-RU/Site_Statistics.html
+++ b/public_html/ru-RU/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Всего языков: </b>44<br />
- <b>Всего пакетов: </b>861
+ <b>Всего пакетов: </b>862
</div>
</body>
</html>
diff --git a/public_html/ru-RU/opds-Community_Services_Infrastructure.xml b/public_html/ru-RU/opds-Community_Services_Infrastructure.xml
index 8d51c32..897d1bb 100644
--- a/public_html/ru-RU/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ru-RU/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds-Fedora.xml b/public_html/ru-RU/opds-Fedora.xml
index 406be44..10d86fb 100644
--- a/public_html/ru-RU/opds-Fedora.xml
+++ b/public_html/ru-RU/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml b/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml
index f6fea77..ed42f88 100644
--- a/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Fedora_Contributor_Documentation.xml</id>
<title>Документация участника Fedora</title>
<subtitle>Документация участника Fedora</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds-Fedora_Core.xml b/public_html/ru-RU/opds-Fedora_Core.xml
index 07adc9c..07b1ae8 100644
--- a/public_html/ru-RU/opds-Fedora_Core.xml
+++ b/public_html/ru-RU/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds-Fedora_Draft_Documentation.xml b/public_html/ru-RU/opds-Fedora_Draft_Documentation.xml
index b04a6b3..684afb2 100644
--- a/public_html/ru-RU/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ru-RU/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>ru-RU</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/ru-RU/opds-Fedora_Security_Team.xml b/public_html/ru-RU/opds-Fedora_Security_Team.xml
index 9ef146c..b138141 100644
--- a/public_html/ru-RU/opds-Fedora_Security_Team.xml
+++ b/public_html/ru-RU/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds.xml b/public_html/ru-RU/opds.xml
index 28d9495..a949951 100644
--- a/public_html/ru-RU/opds.xml
+++ b/public_html/ru-RU/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ru-RU/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/ru-RU/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ru-RU/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Документация участника Fedora</title>
<id>http://docs.fedoraproject.org/ru-RU/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ru-RU/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ru-RU/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/ru-RU/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ru-RU/toc.html b/public_html/ru-RU/toc.html
index ece8504..e1c8d71 100644
--- a/public_html/ru-RU/toc.html
+++ b/public_html/ru-RU/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Не переведено</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/sk-SK/Site_Statistics.html b/public_html/sk-SK/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/sk-SK/Site_Statistics.html
+++ b/public_html/sk-SK/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/sk-SK/opds-Community_Services_Infrastructure.xml b/public_html/sk-SK/opds-Community_Services_Infrastructure.xml
index d49983e..0c7a41f 100644
--- a/public_html/sk-SK/opds-Community_Services_Infrastructure.xml
+++ b/public_html/sk-SK/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds-Fedora.xml b/public_html/sk-SK/opds-Fedora.xml
index f62c8db..0a55ab1 100644
--- a/public_html/sk-SK/opds-Fedora.xml
+++ b/public_html/sk-SK/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml b/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml
index a267ae2..76a1377 100644
--- a/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds-Fedora_Core.xml b/public_html/sk-SK/opds-Fedora_Core.xml
index 7bb64f1..baaea20 100644
--- a/public_html/sk-SK/opds-Fedora_Core.xml
+++ b/public_html/sk-SK/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds-Fedora_Draft_Documentation.xml b/public_html/sk-SK/opds-Fedora_Draft_Documentation.xml
index 4270ae6..dd8d490 100644
--- a/public_html/sk-SK/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sk-SK/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>sk-SK</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/sk-SK/opds-Fedora_Security_Team.xml b/public_html/sk-SK/opds-Fedora_Security_Team.xml
index bc2eede..276f6eb 100644
--- a/public_html/sk-SK/opds-Fedora_Security_Team.xml
+++ b/public_html/sk-SK/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds.xml b/public_html/sk-SK/opds.xml
index 2d13bb9..3ebc646 100644
--- a/public_html/sk-SK/opds.xml
+++ b/public_html/sk-SK/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/sk-SK/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/sk-SK/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/sk-SK/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/sk-SK/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/sk-SK/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/sk-SK/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/sk-SK/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:25</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/sk-SK/toc.html b/public_html/sk-SK/toc.html
index 1a72a92..71f04a0 100644
--- a/public_html/sk-SK/toc.html
+++ b/public_html/sk-SK/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/sr-Latn-RS/Site_Statistics.html b/public_html/sr-Latn-RS/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/sr-Latn-RS/Site_Statistics.html
+++ b/public_html/sr-Latn-RS/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/sr-Latn-RS/opds-Community_Services_Infrastructure.xml b/public_html/sr-Latn-RS/opds-Community_Services_Infrastructure.xml
index 0903c45..75b6f4b 100644
--- a/public_html/sr-Latn-RS/opds-Community_Services_Infrastructure.xml
+++ b/public_html/sr-Latn-RS/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-Latn-RS/opds-Fedora.xml b/public_html/sr-Latn-RS/opds-Fedora.xml
index 30021f8..ab94cb1 100644
--- a/public_html/sr-Latn-RS/opds-Fedora.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml b/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml
index 9005f16..4be1848 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-Latn-RS/opds-Fedora_Core.xml b/public_html/sr-Latn-RS/opds-Fedora_Core.xml
index fa133a0..7814074 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Core.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml b/public_html/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml
index f551b47..9e4e415 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>sr-Latn-RS</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/sr-Latn-RS/opds-Fedora_Security_Team.xml b/public_html/sr-Latn-RS/opds-Fedora_Security_Team.xml
index 241bad3..fe6e823 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Security_Team.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-Latn-RS/opds.xml b/public_html/sr-Latn-RS/opds.xml
index fc304a9..6f12115 100644
--- a/public_html/sr-Latn-RS/opds.xml
+++ b/public_html/sr-Latn-RS/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:15</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/sr-Latn-RS/toc.html b/public_html/sr-Latn-RS/toc.html
index bfd5c84..4494b63 100644
--- a/public_html/sr-Latn-RS/toc.html
+++ b/public_html/sr-Latn-RS/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/sr-RS/Site_Statistics.html b/public_html/sr-RS/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/sr-RS/Site_Statistics.html
+++ b/public_html/sr-RS/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/sr-RS/opds-Community_Services_Infrastructure.xml b/public_html/sr-RS/opds-Community_Services_Infrastructure.xml
index 256313d..4a5f862 100644
--- a/public_html/sr-RS/opds-Community_Services_Infrastructure.xml
+++ b/public_html/sr-RS/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds-Fedora.xml b/public_html/sr-RS/opds-Fedora.xml
index 30667a9..a6ed46f 100644
--- a/public_html/sr-RS/opds-Fedora.xml
+++ b/public_html/sr-RS/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml b/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml
index 5f16dc8..6069810 100644
--- a/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds-Fedora_Core.xml b/public_html/sr-RS/opds-Fedora_Core.xml
index 3b4b183..847934d 100644
--- a/public_html/sr-RS/opds-Fedora_Core.xml
+++ b/public_html/sr-RS/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds-Fedora_Draft_Documentation.xml b/public_html/sr-RS/opds-Fedora_Draft_Documentation.xml
index 3bed34c..2af83c8 100644
--- a/public_html/sr-RS/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sr-RS/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>sr-RS</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/sr-RS/opds-Fedora_Security_Team.xml b/public_html/sr-RS/opds-Fedora_Security_Team.xml
index 80f66df..7af109b 100644
--- a/public_html/sr-RS/opds-Fedora_Security_Team.xml
+++ b/public_html/sr-RS/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds.xml b/public_html/sr-RS/opds.xml
index 91a3eb4..38a9f3e 100644
--- a/public_html/sr-RS/opds.xml
+++ b/public_html/sr-RS/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/sr-RS/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/sr-RS/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/sr-RS/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/sr-RS/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/sr-RS/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/sr-RS/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/sr-RS/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/sr-RS/toc.html b/public_html/sr-RS/toc.html
index 600076a..836be01 100644
--- a/public_html/sr-RS/toc.html
+++ b/public_html/sr-RS/toc.html
@@ -1491,7 +1491,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1573,6 +1575,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/sv-SE/Site_Statistics.html b/public_html/sv-SE/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/sv-SE/Site_Statistics.html
+++ b/public_html/sv-SE/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/sv-SE/opds-Community_Services_Infrastructure.xml b/public_html/sv-SE/opds-Community_Services_Infrastructure.xml
index 0392da5..79f3a24 100644
--- a/public_html/sv-SE/opds-Community_Services_Infrastructure.xml
+++ b/public_html/sv-SE/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds-Fedora.xml b/public_html/sv-SE/opds-Fedora.xml
index 6a05a36..5ae49ec 100644
--- a/public_html/sv-SE/opds-Fedora.xml
+++ b/public_html/sv-SE/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml b/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml
index e3ce4b2..770484b 100644
--- a/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds-Fedora_Core.xml b/public_html/sv-SE/opds-Fedora_Core.xml
index bb12d50..da8ea0e 100644
--- a/public_html/sv-SE/opds-Fedora_Core.xml
+++ b/public_html/sv-SE/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds-Fedora_Draft_Documentation.xml b/public_html/sv-SE/opds-Fedora_Draft_Documentation.xml
index 1141a32..4587711 100644
--- a/public_html/sv-SE/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sv-SE/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>sv-SE</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/sv-SE/opds-Fedora_Security_Team.xml b/public_html/sv-SE/opds-Fedora_Security_Team.xml
index 1f25ef9..d1c30b7 100644
--- a/public_html/sv-SE/opds-Fedora_Security_Team.xml
+++ b/public_html/sv-SE/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds.xml b/public_html/sv-SE/opds.xml
index 4ca6b95..180040a 100644
--- a/public_html/sv-SE/opds.xml
+++ b/public_html/sv-SE/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/sv-SE/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/sv-SE/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/sv-SE/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/sv-SE/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/sv-SE/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/sv-SE/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/sv-SE/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/sv-SE/toc.html b/public_html/sv-SE/toc.html
index 0ced705..1b76dc5 100644
--- a/public_html/sv-SE/toc.html
+++ b/public_html/sv-SE/toc.html
@@ -1527,7 +1527,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1609,6 +1611,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/ta-IN/Site_Statistics.html b/public_html/ta-IN/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/ta-IN/Site_Statistics.html
+++ b/public_html/ta-IN/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/ta-IN/opds-Community_Services_Infrastructure.xml b/public_html/ta-IN/opds-Community_Services_Infrastructure.xml
index 0d7de9d..a3a948d 100644
--- a/public_html/ta-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ta-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds-Fedora.xml b/public_html/ta-IN/opds-Fedora.xml
index e985ec5..2f8aa38 100644
--- a/public_html/ta-IN/opds-Fedora.xml
+++ b/public_html/ta-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml
index e098e3d..92d0e5a 100644
--- a/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds-Fedora_Core.xml b/public_html/ta-IN/opds-Fedora_Core.xml
index 153224e..b55a85d 100644
--- a/public_html/ta-IN/opds-Fedora_Core.xml
+++ b/public_html/ta-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds-Fedora_Draft_Documentation.xml b/public_html/ta-IN/opds-Fedora_Draft_Documentation.xml
index fe45d69..66e1be6 100644
--- a/public_html/ta-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ta-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>ta-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/ta-IN/opds-Fedora_Security_Team.xml b/public_html/ta-IN/opds-Fedora_Security_Team.xml
index c43d235..c5b4ced 100644
--- a/public_html/ta-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/ta-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds.xml b/public_html/ta-IN/opds.xml
index ed918f7..076801a 100644
--- a/public_html/ta-IN/opds.xml
+++ b/public_html/ta-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ta-IN/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/ta-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ta-IN/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ta-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ta-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ta-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/ta-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ta-IN/toc.html b/public_html/ta-IN/toc.html
index a874cdc..4720351 100644
--- a/public_html/ta-IN/toc.html
+++ b/public_html/ta-IN/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/te-IN/Site_Statistics.html b/public_html/te-IN/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/te-IN/Site_Statistics.html
+++ b/public_html/te-IN/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/te-IN/opds-Community_Services_Infrastructure.xml b/public_html/te-IN/opds-Community_Services_Infrastructure.xml
index 8e63de6..96cf53b 100644
--- a/public_html/te-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/te-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:16</updated>
+ <updated>2013-05-28T13:53:26</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds-Fedora.xml b/public_html/te-IN/opds-Fedora.xml
index 19c4e17..cda27f2 100644
--- a/public_html/te-IN/opds-Fedora.xml
+++ b/public_html/te-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml
index c2c66e8..2782ac3 100644
--- a/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds-Fedora_Core.xml b/public_html/te-IN/opds-Fedora_Core.xml
index a3d4f37..ec08df1 100644
--- a/public_html/te-IN/opds-Fedora_Core.xml
+++ b/public_html/te-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds-Fedora_Draft_Documentation.xml b/public_html/te-IN/opds-Fedora_Draft_Documentation.xml
index 8e386f5..706c42d 100644
--- a/public_html/te-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/te-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>te-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/te-IN/opds-Fedora_Security_Team.xml b/public_html/te-IN/opds-Fedora_Security_Team.xml
index 26fccea..e0e508c 100644
--- a/public_html/te-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/te-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds.xml b/public_html/te-IN/opds.xml
index 39b6e3c..8674d4d 100644
--- a/public_html/te-IN/opds.xml
+++ b/public_html/te-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/te-IN/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/te-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:26</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/te-IN/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/te-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/te-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/te-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/te-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/te-IN/toc.html b/public_html/te-IN/toc.html
index 621178e..8f31d3a 100644
--- a/public_html/te-IN/toc.html
+++ b/public_html/te-IN/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/toc.html b/public_html/toc.html
index 9e9e4d1..d696842 100644
--- a/public_html/toc.html
+++ b/public_html/toc.html
@@ -3568,7 +3568,8 @@
<div class="product">
<span id="Fedora_Draft_Documentation" class="product">Fedora Draft Documentation</span>
<div class="versions">
- <div class="books">
+ <div class="version">
+ <span class="version">0.1</span> <div class="books">
<div class="book">
<span id="Amateur_Radio_Guide" class="book">Amateur Radio Guide</span>
@@ -3699,7 +3700,22 @@
</div>
</div>
- </div> <div class="version">
+ <div class="book">
+ <span id="Virtualization_Deployment_and_Administration_Guide" class="book">Virtualization Deployment and Administration Guide</span>
+ <div class="types">
+
+ <a class="type" href="./en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">epub</a>
+
+ <a class="type" href="./en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html">html</a>
+
+ <a class="type" href="./en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html">html-single</a>
+
+ <a class="type" href="./en-US/Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf">pdf</a>
+
+ </div>
+ </div>
+
+ </div> </div> <div class="version">
<span class="version"></span> <div class="books">
<div class="book">
@@ -5801,7 +5817,8 @@
<div class="product">
<span id="Fedora_Draft_Documentation" class="product">Fedora Draft Documentation</span>
<div class="versions">
- <div class="books">
+ <div class="version">
+ <span class="version">0.1</span> <div class="books">
<div class="book">
<span id="Cloud_Guide" class="book">Cloud Guide</span>
@@ -5818,7 +5835,7 @@
</div>
</div>
- </div>
+ </div> </div>
</div>
</div>
@@ -7931,7 +7948,8 @@
<div class="product">
<span id="Fedora_Draft_Documentation" class="product">Fedora ドラフト文書</span>
<div class="versions">
- <div class="books">
+ <div class="version">
+ <span class="version">0.1</span> <div class="books">
<div class="book">
<span id="Cloud_Guide" class="book">Cloud Guide</span>
@@ -7961,7 +7979,7 @@
</div>
</div>
- </div>
+ </div> </div>
</div>
</div>
@@ -11101,7 +11119,8 @@
<div class="product">
<span id="Fedora_Draft_Documentation" class="product">Schiță Documentație Fedora</span>
<div class="versions">
- <div class="books">
+ <div class="version">
+ <span class="version">0.1</span> <div class="books">
<div class="book">
<span id="RPM_Guide" class="book">Ghid RPM</span>
@@ -11118,7 +11137,7 @@
</div>
</div>
- </div>
+ </div> </div>
</div>
</div>
@@ -13684,7 +13703,8 @@
</div>
</div>
- </div> <div class="books">
+ </div> <div class="version">
+ <span class="version">0.1</span> <div class="books">
<div class="book">
<span id="User_Guide" class="book">Інструкція користувача</span>
@@ -13701,7 +13721,7 @@
</div>
</div>
- </div>
+ </div> </div>
</div>
</div>
diff --git a/public_html/uk-UA/Site_Statistics.html b/public_html/uk-UA/Site_Statistics.html
index 8eebf26..4558900 100644
--- a/public_html/uk-UA/Site_Statistics.html
+++ b/public_html/uk-UA/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Загалом мов: </b>44<br />
- <b>Загалом пакунків: </b>861
+ <b>Загалом пакунків: </b>862
</div>
</body>
</html>
diff --git a/public_html/uk-UA/opds-Community_Services_Infrastructure.xml b/public_html/uk-UA/opds-Community_Services_Infrastructure.xml
index 15b6d42..cb5474c 100644
--- a/public_html/uk-UA/opds-Community_Services_Infrastructure.xml
+++ b/public_html/uk-UA/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds-Fedora.xml b/public_html/uk-UA/opds-Fedora.xml
index 6a4ecf2..3a4bc91 100644
--- a/public_html/uk-UA/opds-Fedora.xml
+++ b/public_html/uk-UA/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml b/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml
index ef409d2..82b5cbe 100644
--- a/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Fedora_Contributor_Documentation.xml</id>
<title>Документація для учасника розробки Fedora</title>
<subtitle>Документація для учасника розробки Fedora</subtitle>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds-Fedora_Core.xml b/public_html/uk-UA/opds-Fedora_Core.xml
index ea3a4f7..9b72516 100644
--- a/public_html/uk-UA/opds-Fedora_Core.xml
+++ b/public_html/uk-UA/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds-Fedora_Draft_Documentation.xml b/public_html/uk-UA/opds-Fedora_Draft_Documentation.xml
index 50ad8b3..4cb0f6a 100644
--- a/public_html/uk-UA/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/uk-UA/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Fedora_Draft_Documentation.xml</id>
<title>Чернетки документації з Fedora</title>
<subtitle>Чернетки документації з Fedora</subtitle>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
@@ -182,6 +182,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>uk-UA</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/uk-UA/opds-Fedora_Security_Team.xml b/public_html/uk-UA/opds-Fedora_Security_Team.xml
index aaa8f07..8755bb9 100644
--- a/public_html/uk-UA/opds-Fedora_Security_Team.xml
+++ b/public_html/uk-UA/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds.xml b/public_html/uk-UA/opds.xml
index f1f7fff..0e11cc4 100644
--- a/public_html/uk-UA/opds.xml
+++ b/public_html/uk-UA/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/uk-UA/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/uk-UA/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Документація для учасника розробки Fedora</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Чернетки документації з Fedora</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/uk-UA/toc.html b/public_html/uk-UA/toc.html
index 456a742..7a5595e 100644
--- a/public_html/uk-UA/toc.html
+++ b/public_html/uk-UA/toc.html
@@ -1494,7 +1494,9 @@
</div>
</div>
</div>
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1.User_Guide' class="book collapsed">
<a class="type" href="Fedora_Draft_Documentation/0.1/html/User_Guide/index.html" onclick="window.top.location='./Fedora_Draft_Documentation/0.1/html/User_Guide/index.html'"><span class="book">Інструкція користувача</span></a>
<div id='Fedora_Draft_Documentation.0.1.User_Guide.types' class="types" onclick="work=0;">
@@ -1576,6 +1578,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Technical_Notes/Fedora_Draft_Documentation-0.1-Technical_Notes-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Technical_Notes/Fedora_Draft_Documentation-0.1-Technical_Notes-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/zh-CN/Site_Statistics.html b/public_html/zh-CN/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/zh-CN/Site_Statistics.html
+++ b/public_html/zh-CN/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/zh-CN/opds-Community_Services_Infrastructure.xml b/public_html/zh-CN/opds-Community_Services_Infrastructure.xml
index 5f22095..f12e0c9 100644
--- a/public_html/zh-CN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/zh-CN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds-Fedora.xml b/public_html/zh-CN/opds-Fedora.xml
index 7c555b6..2730418 100644
--- a/public_html/zh-CN/opds-Fedora.xml
+++ b/public_html/zh-CN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml b/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml
index 5260aed..a689c72 100644
--- a/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds-Fedora_Core.xml b/public_html/zh-CN/opds-Fedora_Core.xml
index d65d4c8..59e7c1f 100644
--- a/public_html/zh-CN/opds-Fedora_Core.xml
+++ b/public_html/zh-CN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds-Fedora_Draft_Documentation.xml b/public_html/zh-CN/opds-Fedora_Draft_Documentation.xml
index b184850..99b0197 100644
--- a/public_html/zh-CN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/zh-CN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>zh-CN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/zh-CN/opds-Fedora_Security_Team.xml b/public_html/zh-CN/opds-Fedora_Security_Team.xml
index 2b5bb81..1e9bd7e 100644
--- a/public_html/zh-CN/opds-Fedora_Security_Team.xml
+++ b/public_html/zh-CN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds.xml b/public_html/zh-CN/opds.xml
index 116bb5e..16bc361 100644
--- a/public_html/zh-CN/opds.xml
+++ b/public_html/zh-CN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/zh-CN/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:18</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/zh-CN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:17</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/zh-CN/toc.html b/public_html/zh-CN/toc.html
index 7fb3e87..11c8b5f 100644
--- a/public_html/zh-CN/toc.html
+++ b/public_html/zh-CN/toc.html
@@ -1552,7 +1552,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1634,6 +1636,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
diff --git a/public_html/zh-TW/Site_Statistics.html b/public_html/zh-TW/Site_Statistics.html
index e4a5485..041fffd 100644
--- a/public_html/zh-TW/Site_Statistics.html
+++ b/public_html/zh-TW/Site_Statistics.html
@@ -26,9 +26,9 @@
<td>English</td>
<td>en-US</td>
<td>6</td>
- <td>41</td>
+ <td>42</td>
<td>20</td>
- <td>146</td>
+ <td>147</td>
</tr>
<tr>
@@ -421,7 +421,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>44<br />
- <b>Total Packages: </b>861
+ <b>Total Packages: </b>862
</div>
</body>
</html>
diff --git a/public_html/zh-TW/opds-Community_Services_Infrastructure.xml b/public_html/zh-TW/opds-Community_Services_Infrastructure.xml
index b5c4c54..12689b0 100644
--- a/public_html/zh-TW/opds-Community_Services_Infrastructure.xml
+++ b/public_html/zh-TW/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2013-05-27T08:01:18</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds-Fedora.xml b/public_html/zh-TW/opds-Fedora.xml
index f4d5444..713a2cd 100644
--- a/public_html/zh-TW/opds-Fedora.xml
+++ b/public_html/zh-TW/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2013-05-27T08:01:18</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml b/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml
index 56c5b54..bbc628d 100644
--- a/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2013-05-27T08:01:18</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds-Fedora_Core.xml b/public_html/zh-TW/opds-Fedora_Core.xml
index 7778811..f2ab08b7 100644
--- a/public_html/zh-TW/opds-Fedora_Core.xml
+++ b/public_html/zh-TW/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2013-05-27T08:01:18</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml b/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml
index 9b20790..1e9437a 100644
--- a/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2013-05-27T08:01:18</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
@@ -163,6 +163,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Virtualization Deployment and Administration Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2013-05-28</updated>
+ <dc:language>zh-TW</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Virtualization Documentation
+</summary>
+ <content type="text">This document is a draft resulting from two guides which have been merged. It uses the Fedora Deployment Guide and the Virtualization Administration Guide. This guide included information on how to configure a Fedora machine as a virtualization host, and install and configure virtual machines under Fedora virtualization. Note: This document is under development, is subject to substantial change, and is provided only as a preview. The included information and instructions should not be considered complete, and should be used with caution.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>User Guide</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation//epub/User_Guide/Fedora_Draft_Documentation--User_Guide-en-US.epub</id>
<!--author>
diff --git a/public_html/zh-TW/opds-Fedora_Security_Team.xml b/public_html/zh-TW/opds-Fedora_Security_Team.xml
index ba3737d..8e3e08f 100644
--- a/public_html/zh-TW/opds-Fedora_Security_Team.xml
+++ b/public_html/zh-TW/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2013-05-27T08:01:18</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds.xml b/public_html/zh-TW/opds.xml
index c25e0c4..70b806e 100644
--- a/public_html/zh-TW/opds.xml
+++ b/public_html/zh-TW/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/zh-TW/opds.xml</id>
<title>Product List</title>
- <updated>2013-05-27T08:01:18</updated>
+ <updated>2013-05-28T13:53:27</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/zh-TW/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2013-05-27T08:01:18</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/zh-TW/Fedora/opds-Fedora.xml</id>
- <updated>2013-05-27T08:01:18</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/zh-TW/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2013-05-27T08:01:18</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/zh-TW/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2013-05-27T08:01:18</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/zh-TW/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2013-05-27T08:01:18</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/zh-TW/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2013-05-27T08:01:18</updated>
+ <updated>2013-05-28T13:53:27</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/zh-TW/toc.html b/public_html/zh-TW/toc.html
index 6e6072e..4ab004f 100644
--- a/public_html/zh-TW/toc.html
+++ b/public_html/zh-TW/toc.html
@@ -1482,7 +1482,9 @@
<div class="product collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation');work=1;">
<span class="product">Fedora Draft Documentation</span>
<div id='Fedora_Draft_Documentation' class="versions hidden">
- <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');"> <div id='Fedora_Draft_Documentation.0.1.books' class="books">
+ <div id='Fedora_Draft_Documentation.0.1' class="version collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.books');">
+ <span class="version">UNUSED.</span>
+ <div id='Fedora_Draft_Documentation.0.1.books' class="books hidden">
<div id='Fedora_Draft_Documentation.0.1' class="version collapsed untranslated" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.untrans_books');">
<span class="version">Untranslated</span>
<div id='Fedora_Draft_Documentation.0.1.untrans_books' class="books hidden">
@@ -1564,6 +1566,15 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/User_Guide/Fedora_Draft_Documentation-0.1-User_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html'"><span class="book">Virtualization Deployment and Administration Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Virtualization_Deployment_and_Administration_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
</div>
</div>
</div>
More information about the docs-commits
mailing list